Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 121 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Retrieving All Data from the Routing Namespace 109
Section 7.32
Retrieving All Data from the Routing Namespace
In this example, a single <rpc> request retrieves all configuration data from the Routing namespace.
The following is the typical procedure for querying data from the running configuration.
•
Request the data from the running configuration:
<rpc message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter type="subtree">
<routing xmlns="http://ruggedcom.com/ns/rmf_routing">
<status></status>
</routing>
</filter>
</get>
</rpc>]]>]]>
Section 7.33
Configuring DHCP Server
In this example, multiple
<rpc>
requests configure the DHCP server service 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>]]>]]>
2. Lock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="231">
<lock>
<target>
<candidate/>
</target>
</lock>
</rpc>]]>]]>
3. Discard uncommitted changes:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="232">
<discard-changes/>
</rpc>]]>]]>
4. Configure the DHCP server:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>