Siemens RUGGEDCOM MX5000RE, Reference Manual

Page: 97 / 148

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Creating a Static VLAN 85
Section 7.11
Creating a Static VLAN
In this example, multiple <rpc> requests create a static VLAN in the candidate configuration and then commit the
changes.
The following shows 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 static VLAN parameters:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<switch xmlns="http://ruggedcom.com/ns/rmf_ifswitch">
<vlans>
<static-vlan>
<vid>0086</vid>
</static-vlan>
</vlans>
</switch>
</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>