Siemens RUGGEDCOM MX5000RE, Справочное руководство

Страница: 54 / 148

Chapter 5
Changing Configuration Data
RUGGEDCOM NETCONF
Reference Guide
42 Changing Data in the Candidate Configuration
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
{path}
</config>
</edit-config>
</rpc>]]>]]>
•
{path}
The XML elements describing the path to and the data for the element to be edited.
For example, to create a static VLAN:
<rpc message-id="233" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<switch xmlns="http://ruggedcom.com/ns/rmf_ifswitch">
<vlans>
<static-vlan>
<vid>0086</vid>
</static-vlan>
</vlans>
</switch>
</config>
</edit-config>
</rpc>]]>]]>
After making changes to the running configuration, you can use the validate command to check the syntax on the
configuration. For instructions on how to validate a configuration, refer to Section 5.2.5, “Validating Changes” .
Section 5.2
Changing Data in the Candidate Configuration
The recommended approach for changing data is to make your changes to the candidate configuration before
committing the changes to the running configuration. Making changes to the candidate configuration provides
the opportunity to validate the syntax of the configuration and to discard the changes if required.
As illustrated in
Section 1.5.3, “Sample Session: Editing Data” , editing data in the candidate configuration and
committing it involves a multi-step workflow:
1. Connect to the device and say hello.
2. Lock the candidate and running configuration datastores.
3. Discard any stray changes to restore the configurations to a known state.
4. Edit the candidate configuration.
5. Validate the candidate configuration.
6. Commit the changes.
7. Unlock the datastores.
8. Close the session.