Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
98
Replacing an IP Address
<static>
<status></status>
</static>
</multicast>
</routing>
</filter>
</get>
</rpc>]]>]]>
Section 7.23
Replacing an IP Address
In this example, multiple
<rpc>
requests replace an IP address in the candidate configuration and then commit
the changes.
The following is the recommended procedure for making configuration changes on a device. This example also
shows how to use the
nc:operation="replace"
attribute to replace an existing value with a new value.
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. Replace the IP address:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<ip xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="http://ruggedcom.com/ns/rmf_ip">
<ifname>fe-4-2</ifname>
<ipv4 nc:operation="replace">
<address>
<ipaddress>192.168.114.5/24</ipaddress>
</address>
</ipv4>
</ip>
</config>
</edit-config>
Summary of Contents for RUGGEDCOM MX5000RE
Page 8: ...Table of Contents RUGGEDCOM NETCONF Reference Guide viii ...
Page 12: ...Preface RUGGEDCOM NETCONF Reference Guide xii Customer Support ...
Page 26: ...Chapter 1 Introduction RUGGEDCOM NETCONF Reference Guide 14 Sample Session Editing Data ...
Page 40: ...Chapter 3 NETCONF Sessions RUGGEDCOM NETCONF Reference Guide 28 Killing a Session ...
Page 64: ...Chapter 5 Changing Configuration Data RUGGEDCOM NETCONF Reference Guide 52 Committing Changes ...
Page 148: ...Chapter 8 NETCONF XML Elements RUGGEDCOM NETCONF Reference Guide 136 validate ...