Get-Config> With Xml Content Layer - Alcatel-Lucent 7450 System Management Manual

XML Content Layer
The <edit-config> <default-operation> parameter is supported with the following values:
merge, none. The 'replace' value is not supported. An operation of "none" on a leaf node
(inherited or direct) causes that leaf statement to be ignored. No error will be returned if the
leaf does not exist in the data model.
For 'merge' and 'create' operations the operations and tags specified in an <edit-config>
request are order-aware and order-dependant and the sequence of operations must follow the
required sequence of the equivalent CLI commands. The <edit-config> is processed and
executed in a top-down order. The same leaf can be enabled, disabled, enabled and then
disabled and the final result is whatever was last specified for that leaf in the <edit-config>
request.
For 'delete' and 'remove' operations the SR OS NETCONF server will recursively "unwind"
any children of the node being deleted or removed first before removing the node itself. The
'deepest' child branch of the request is examined first and any leafs are processed, after which
the server works backwards out of the deepest branches back up to the object where the delete
operation was specified. Note that if children branches of an object are required to be removed
before deleting the object in CLI, then the equivalent delete request in a NETCONF <edit-
config> must contain all those children if they exist, such as if the children are configured in
the config datastore). For example:
In the example above, SR OS will first shutdown the test interface, then delete the interface,
then shutdown the VPLS and then finally remove it.
Note that the 'operation="merge"' is required in the shutdown nodes because otherwise the
inherited operation is delete which is not supported on boolean leafs.
If other children of vpls 11 exist in the config besides the interface 'test' specified in the delete
request above, and those children are required in CLI to be deleted before removing vpls 11,
then the deletion request above will fail. All configured children must be specified in the
delete request.
<get-config> with XML Content Layer
Page 354
<config>
<configure>
<service>
<vpls operation="delete">
<service-id>11</service-id>
<interface>
<ip-int-name>test</ip-int-name>
<shutdown operation="merge">true</shutdown>
</interface>
<shutdown operation="merge">true</shutdown>
</vpls>
</service>
</configure>
</config>
7450 ESS System Mangement Guide