Thanks! So as I understand, the general idea is that it doesn't matter much for Junos if the command is executed in the CLI or from the remote(management server) NETCONF manager, i.e. Junos is basically built around the NETCONF? However, local calls(for example if one executes "show version" in Junos CLI) do not travel internally over SSH as remote calls would, do they?
thanks, Martin On Mon, Dec 21, 2015 at 9:24 AM, Alexander Marhold <[email protected]> wrote: > Hi ! > > Yes, if you want to see how the request command looks like > Then do a > " show version brief | display xml rpc" > > Using XSLT or SLAX the language create and uses exatly that XML information. > > Regards > > Alexander > > -----Ursprüngliche Nachricht----- > Von: juniper-nsp [mailto:[email protected]] Im Auftrag von > Martin T > Gesendet: Montag, 21. Dezember 2015 02:26 > An: juniper-nsp > Betreff: [j-nsp] NETCONF in Junos > > Hi, > > if I execute for example "show version brief | display xml" command, then > the router returns: > > <rpc-reply xmlns:junos="http://xml.juniper.net/junos/12.3R6/junos";> > <software-information> > <host-name>r1</host-name> > <product-model>m10i</product-model> > <product-name>m10i</product-name> > <package-information> > <name>junos</name> > <comment>JUNOS Base OS boot [12.3R6.6]</comment> > </package-information> > > /* additional data removed for brevity */ > > </software-information> > <cli> > <banner>{master}</banner> > </cli> > </rpc-reply> > > Is it a reply to NETCONF <get> operation? Does this mean that each for > example "show" command in Junos is a communication (over TCP/IP) between the > NETCONF manager(sends the <get>) and agent(sends the > <rpc-reply>) in the same router? > > > thanks, > Martin > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
