Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 109 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Retrieving Static Multicast Status on a Layer 3 Device 97
4. Enable static multicast routing:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<routing xmlns="http://ruggedcom.com/ns/rmf_routing">
<multicast>
<static>
<enabled/>
</static>
</multicast>
</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.22
Retrieving Static Multicast Status on a Layer 3
Device
In this example, a single
<rpc>
request retrieves the static multicast status information from the device.
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">
<multicast>