Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 61 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 5
Changing Configuration Data
Deleting Data 49
</edit-config>
</rpc>]]>]]>
•
{root element}
The top level element in the data model under which the data is located. Note that you need to declare the
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" namespace at this point.
•
{namespace}
The URL to the RUGGEDCOM namespace for the top level element.
•
{configuration data with nc:operation="delete" attribute}
The path to the data to be deleted, with the nc:operation="delete" attribute on the element
containing the data to be deleted.
For example, to clear the Passive Interface setting on an interface in OSPF, issue the following request.
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<routing xmlns="http://ruggedcom.com/ns/rmf_routing"
xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0 ">
<dynamic>
<ospf>
<interface>
<ifname>switch.0022</ifname>
<passive nc:operation="delete"/>
</interface>
</ospf>
</dynamic>
</routing>
</config>
</edit-config>
</rpc>]]>]]>
6. Commit the change:
<rpc message-id="234" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit/>
</rpc>]]>]]>
7. Unlock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="235">
<unlock>
<target>
<candidate/>
</target>
</unlock>
</rpc>]]>]]>
8. Unlock the target configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="236">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>]]>]]>