Skip to content
This repository has been archived by the owner on Oct 11, 2020. It is now read-only.

Different payloads #2

Open
singhaniashrinkhala opened this issue Jul 21, 2017 · 1 comment
Open

Different payloads #2

singhaniashrinkhala opened this issue Jul 21, 2017 · 1 comment

Comments

@singhaniashrinkhala
Copy link

Hi,

I am testing different OpenConfig payloads, however I am not sure of the xml namespaces.

eg, in your description of BGP OpenConfig format over ssh, you sent in the payload below:

<rpc>
    <get-config>
        <source><running/></source>
        <filter type="subtree">
            <bgp xmlns="http://openconfig.net/yang/bgp">
            </bgp>
        </filter>
    </get-config>
</rpc>
]]>]]>

Could you share some more examples of the payload, for eg. for interface? Juniper documentation doesn't have a wide coverage of this.

Also could you suggest of a console to communicate with the NETCONF agent on the Juniper device. Eg. something like this https://github.com/OpenNetworkingFoundation/configuration/tree/master/netconf-console

@vnitinv
Copy link

vnitinv commented Sep 7, 2017

@singhaniashrinkhala wrt to netconf-console, they also are using ssh only. if you are looking for other transport mode for netconf, check PyEZ which support serial/telnet too apart from ssh.
https://groups.google.com/forum/#!topic/junos-python-ez/CIAG9oLh8WU

We also have PyEZ OpenConfig examples at https://github.com/ksator/openconfig-demo-with-juniper-devices/wiki/10.-PyEZ-python-library-and-OpenConfig-integration

namespace are required to segregate between Juniper config and OpenConfig.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants