Alcatel-Lucent 7450 - XML Content Layer

XML Content Layer
Page 352 7450 ESS System Mangement Guide
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:capability:writable-running:1.0</capabil-
ity>
<capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:validate:1.1</capability>
<capability>urn:ietf:params:netconf:capability:startup:1.0</capability>
<capability>urn:ietf:params:netconf:capability:url:1.0?scheme=ftp,tftp,file</
capability>
<capability>urn:ietf:params:netconf:capability:with-defaults:1.0?basic-
mode=trim</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-net-
conf&amp;revision=2015-02-27&amp;features=writable-running,vali-
date,startup,url&amp;deviations=alu-netconf-deviations-r13</capability>
<capability>urn:alcatel-lucent.com:sros:ns:yang:netconf-deviations-r13?mod-
ule=alu-netconf-deviations-r13&amp;revision=2015-02-27</capability>
<capability>urn:alcatel-lucent.com:sros:ns:yang:cli-content-layer-r13?mod-
ule=alu-cli-content-layer-r13&amp;revision=2015-02-27</capability>
<capability>urn:alcatel-lucent.com:sros:ns:yang:conf-r13?module=conf-
r13&amp;revision=2015-02-27</capability>
<capability>urn:alcatel-lucent.com:sros:ns:yang:conf-aaa-r13?module=conf-aaa-
r13&amp;revision=2015-02-27</capability>
...
...
...
...
<capability>urn:alcatel-lucent.com:sros:ns:yang:conf-vsm-r13?module=conf-vsm-
r13&amp;revision=2015-02-27</capability>
</capabilities>
<session-id>54</session-id>
</hello>
]]>]]>
From a client:
<?xml version="1.0" encoding="UTF-8"?>
<hello>
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
</capabilities>
</hello>
]]>]]>
XML Content Layer
XML is the default content layer format for the SR OS NETCONF server. When using the
XML format at the NETCONF content layer, configuration changes and configuration
information retrieved are expressed as XML tags.
The XML formatted configuration information must be correctly ordered and has the same
dependencies and behavior as the equivalent CLI commands.