Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 107 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Configuring Static Multicast Routing on a Layer 3 Device 95
Section 7.20
Configuring Static Multicast Routing on a Layer 3
Device
In this example, multiple <rpc> requests enable static multicast routing 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 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>
<mcast-groups>
<description>Ruggedtest</description>
<source-ip>192.168.1.155</source-ip>
<multicast-ip>229.0.0.100</multicast-ip>
<in-interface>fe-cm-1</in-interface>
<if-change>-</if-change>
<out-interface>
<ifname>switch.0021</ifname>
</out-interface>
</mcast-groups>
</static>
</multicast>
</routing>
</config>
</edit-config>
</rpc>]]>]]>