Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
88 Configuring an IP Address on a Specific Port
3. Discard uncommitted changes:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="232">
<discard-changes/>
</rpc>]]>]]>
4. Disable spanning tree with the nc:delete attribute:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<interface xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="http://ruggedcom.com/ns/
rmf_if">
<switch>
<slot>lm4</slot>
<port>6</port>
<spanning-tree>
<enabled nc:operation="delete"/>
</spanning-tree>
</switch>
</interface>
</config>
</edit-config>
</rpc>]]>]]>
5. Commit the changes:
<rpc message-id="234" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit/>
</rpc>]]>]]>
6. Unlock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="235">
<unlock>
<target>
<candidate/>
</target>
</unlock>
</rpc>]]>]]>
7. Unlock the running configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="236">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>]]>]]>
Section7.14
Configuring an IP Address on a Specific Port
In this example, multiple <rpc> requests configure an IP address on a specified port in the candidate
configuration and then commit the changes.
The following is the recommended procedure for making configuration changes on a device: