Alcatel-Lucent 7450 System Management Manual page 342

NETCONF in SR OS
declared (or assigned to a prefix) in the rpc tag then the SR OS server will reply with an error.
XML namespace or prefix declarations in the rest of the request are accepted but ignored and
unused. The SR OS NETCONF server puts correct namespace declarations in all replies. The
SR OS NETCONF implementation does not support XML namespaces (xmlns).
Example 1 — The standard NETCONF namespace
"urn:ietf:params:xml:ns:netconf:base:1.0" defined more than once 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>
</filter>
</get-config>
</rpc>
]]>]]>
Reply (no error message):
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101" xmlns:alu="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
</rpc-reply>
]]>]]>
Example 2 — A non-standard NETCONF namespace 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:alcatel-lucent.com:sros:ns:yang:conf-r13">
<get-config>
Page 342
<configure>
<router>
<interface>
<interface-name>"system"</interface-name>
</interface>
</router>
</configure>
<data>
<configure xmlns="urn:alcatel-lucent.com:sros:ns:yang:conf-r13">
<router>
<router-name>Base</router-name>
<interface>
<interface-name>system</interface-name>
<address>
<ip-address-mask>144.23.63.5/32</ip-address-mask>
</address>
<shutdown>false</shutdown>
</interface>
</router>
</configure>
</data>
7450 ESS System Mangement Guide