NETCONF
7450 ESS System Mangement Guide Page 359
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-info>
<err-element>get-config</err-element>
</error-info>
<error-message>
command failed - 'configure router interface "abc" "def"'
</error-message>
</rpc-error>
</rpc-reply>
]]>]]>
The full configuration (equivalent to the CLI command 'admin display-config') can be
obtained via a <get-config> request:
• A — when the <filter> tag is not present
Example:
<get-config>
<source>
<running/>
</source>
</get-config>
• B — when only the <configure> tag is present inside a <filter> tag
Example:
<get-config>
<source>
<running/>
</source>
<filter>
<configure/>
</filter>
</get-config>
<get-config> requests that specify a non-existent list node or presence container will result in
a reply that contains no data for those list nodes or containers. An rpc-error is not sent in this
case.
XML Content Layer Examples
The following examples can be used after a NETCONF session has been established including
the exchange of the <hello> messages.
Below is an example of a <get-config> request and response to check on whether netconf is
shut down or not on the router:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
To Next Page
Loading...
