Hey Martin, I’m not sure NETCONF is involved as such, but I think that’s the general idea. From a Juniper automation doc:
> Junos management “under the hood” is based in XML. When you enter commands on > the Junos CLI, commands are actually converted to XML-based Remote Procedure > Calls (RPCs) and executed by the Junos management daemon. The Junos > configuration file is also represented as an XML file. Regards, Luke > On 21 Dec 2015, at 12:25, Martin T <m4rtn...@gmail.com> wrote: > > 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 juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp