Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 96 / 148

Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
84 Changing the System Name Directly
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.10
Changing the System Name Directly
In this example, a single
<rpc>
request changes the system name directly in the running configuration.
This example shows how to change configuration data on the running configuration directly without locking the
datastores. Changes made in this manner are applied to the running configuration immediately.
CAUTION!
Exercise caution when making changes directly to the running configuration. Making an error in the
configuration settings may interrupt service.
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<admin xmlns="http://ruggedcom.com/ns/rmf_admin">
<system-name>REAL-Test</system-name>
</admin>
</config>
</edit-config>
</rpc>]]>]]>