Alcatel-Lucent 7450 - Edit-Config> with XML Content Layer

NETCONF
7450 ESS System Mangement Guide Page 353
<edit-config> with XML Content Layer
An <edit-config> operation is supported with the <running> datastore only. The following
<edit-config> operation attribute values are supported:
•merge
•remove
•delete
∅ A 'delete' operation for a leaf or a presence container will not return an error if the
item is already deleted.
∅ An error is returned if attempting to delete a list node that doesn't exist.
∅ A 'delete' operation for a container without presence will return an error
• create
∅ A 'create' operation for a leaf or a presence container will not return an error if the
item is being set to the same value.
∅ An error is returned if attempting to create a list node that already exists.
∅ A 'create' operation for a container without presence will result in an "OK"
response (no error) but will be silently ignored.
'replace' is not supported as an attribute value for the <edit-config> operation.
Both 'delete' and 'remove' operations have the following behavior:
• Delete or remove operations are not supported for boolean leafs. For example, any of
the following samples will return an error:
∅ <shutdown operation="delete"/>
∅ <shutdown operation="delete">false</shutdown>
∅ <interface operation="delete">
<interface-name>abc</interface-name>
<shutdown>true</shutdown>
</interface>
(For this last case <shutdown operation="merge">true</shutdown> could be used
instead to make the request valid.)
• A delete or remove operation is the equivalent of 'no xyz' in CLI. This 'no xyz' is
applied whether the default for xyz is enabled ('xyz'), disabled ('no xyz') or some
specific value. The delete operation is not aware of the default value of the object/leaf
being deleted.
• A delete or remove for a leaf, where the request also specifies a value for the leaf, will
result in an error.