Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 122 / 148

Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
110
Configure the DHCP Server Port Listening for DHCP Client
Requests
<config>
<services xmlns="http://ruggedcom.com/ns/rmf_services">
<dhcpserver>
<subnet>
<name>192.168.3.0/24</name>
<network-ip>192.168.3.0/24</network-ip>
<options>
<iprange>
<start>192.168.3.30</start>
<end>192.168.3.35</end>
</iprange>
</options>
</subnet>
</dhcpserver>
</services>
</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.34
Configure the DHCP Server Port Listening for DHCP
Client Requests
In this example, multiple <rpc> requests configure the DHCP listen port 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/>