NETCONF
7450 ESS System Mangement Guide Page 343
<source> <running/> </source>
<filter>
<configure xmlns="urn:alcatel-lucent.com:sros:ns:yang:conf-r13">
<router>
<interface>
<interface-name>"system"</interface-name>
</interface>
</router>
</configure>
</filter>
</get-config>
</rpc>
]]>]]>
Reply (an error message: An unexpected namespace is present):
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:alu="urn:alcatel-
lucent.com:sros:ns:yang:conf-r13">
<rpc-error>
<error-type>protocol</error-type>
<error-tag>unknown-element</error-tag>
<error-severity>error</error-severity>
<error-info>
<bad-element></bad-element>
<bad-namespace>urn:alcatel-lucent.com:sros:ns:yang:conf-r13</bad-namespace>
</error-info>
<error-message>
An unexpected namespace is present.
</error-message>
</rpc-error>
</rpc-reply>
Example 3 — A non-standard NETCONF namespace used in one of the tags but not defined
in the rpc tag:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:alu="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source> <running/> </source>
<filter>
<configure>
<router>
<interface xmlns:alu="urn:alcatel-lucent.com:sros:ns:yang:conf-r13">
<interface-name>"system"</interface-name>
</interface>
</router>
</configure>
</filter>
</get-config>
</rpc>
]]>]]>
Reply (non-standard namespace used in tag is ignored):