Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 116 / 148

Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
104 Configuring OSPF Parameters
<candidate/>
</target>
<config>
<routing xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="http://ruggedcom.com/ns/
rmf_routing">
<dynamic>
<ospf>
<interface>
<ifname>switch.0022</ifname>
<passive>false</passive>
</interface>
</ospf>
</dynamic>
</routing>
</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>]]>]]>
Section 7.28
Configuring OSPF Parameters
In this example, multiple <rpc> requests configure OSPF parameters in the candidate configuration and then
commit the changes.
The following is the recommended procedure for making configuration changes on a device.
1. Lock the running configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="230">
<lock>
<target>
<running/>
</target>
</lock>
</rpc>]]>]]>