Siemens RX1400 - Changing the System Name by Locking and Committing

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Changing the System Name by Locking and Committing 83
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<action xmlns="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<admin xmlns="http://ruggedcom.com/ns/rmf_admin">
<restore-factory-defaults/>
</admin>
</data>
</action>
</rpc>]]>]]>
Section7.9
Changing the System Name by Locking and
Committing
In this example, multiple <rpc> requests change the system name in the candidate configuration and then
commit the changes.
The following is the recommended procedure for making configuration changes on a device:
1. Discard uncommitted changes:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="232">
<discard-changes/>
</rpc>]]>]]>
2. Lock the running configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="230">
<lock>
<target>
<running/>
</target>
</lock>
</rpc>]]>]]>
3. Lock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="231">
<lock>
<target>
<candidate/>
</target>
</lock>
</rpc>]]>]]>
4. Change the system-name setting:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<admin xmlns="http://ruggedcom.com/ns/rmf_admin">
<system-name>Substation 24 Locker 2 Router 1</system-name>
</admin>
</config>
</edit-config>
</rpc>]]>]]>