netconf | Mirror of the OpenDaylight netconf gerrit project

Consider using namespaces when referencing XML elements:

XPath is not a valid filter type for get-config.

— Enclose the tag element. The mandatory type attribute indicates the kind of syntax used to represent the requested configuration elements; the only acceptable value is subtree.

https://www.juniper.net/documentation/en_US/junos/topics/reference/tag-summary/netconf-get-config.html

You can use the filter type subtree instead as outlined below.

NOTE: GET-CONF does not have an attribute for inheritance. If you need to pull what would be the final configuration, i.e. you are using the "Groups" stanza, you will need to use GET-CONFIGURATION. I will show the difference in an additional output below. https://www.juniper.net/documentation/en_US/junos/topics/reference/tag-summary/junos-xml-protocol-get-configuration.html

Contents of get-interfaces.xml using get-conf

This is how you would do it with python, using lxml as the xml parser:

First you need to determine if netconf has been enabled on your router.

You can do so by just issue an SSH command telnet 10.0.0.1 830 from your machine.

If the telnet connects successfully, then it means that you lack SSH modules in python.

You can fix this by installing Paramiko using the command pip install paramiko

If the telnet fails, then just enable netconf on your Cisco Router with the command netconf-yang and try again.

Both case and choice are what the RFC refers to as schema nodes, but they are not also data nodes - schema nodes that may be instantiated. Therefore choice and case nodes never appear in a valid instance document, they only impose restrictions on what a valid instance document is.

In your case, that would mean an optional choice (XOR) between:

• the (logical) group of elements containing (list) and/or (container),
• container.

To put it another way, if appears in the instance document, may also appear (and vice versa), but may not appear.

Here's a valid document (did not actually test).

Actually, it's pretty simple, but maybe not obvious. Build all the projects you want locally, then build the integration/distribution project. Any artifacts it finds in the local m2 repo will be used for the final int/dist karaf that will get created.

in other words, for every project you want to customize, pull that repo, make your changes, build it. Then as a last step, build the int/dist project.

Unless I'm missing something you shouldn't even be getting that original output you're showing us. Not with how you select your property.

However, I believe the following does what you are asking.

Or are you asking on how to exclude IPv6 in your output as well?

Edited to add a few different variants.

It looks like the config subsystem endpoint was deprecated back in Flourine--but the documentation has not been updated--even the latest release notes for Sodium indicate that they still maintain a CSS NETCONF server as part of their standard set of questions the dev team answers. I found this here:

https://jira.opendaylight.org/browse/NETCONF-535

I believe the MDSAL server is the only one available now, and it does (in its HELLO response) seem to indicate that it maintains the capabilities for all YANG-compliant modules. However, I cannot access these elements using the netopeer2-cli as the libyang parsing seems to issue a lot of errors. I suspect this is an issue related to netopeer2-cli and its requesting/parsing of the various YANG files after the initial HELLO and how it works with libyang to construct a local version of the model for the purposes of handling various NETCONF requests.

Not with Mojolicious directly (or any Mojo::* modules I could find) however I know at least that XML::Twig comes with the xml_pp executable.

Extracting the most basic code from that script gives you this...