167
</data>
</rpc-reply>
Performing the save-point/commit operation
The system supports a maximum of 50 rollback points. When the limit is reached, you must specify
the
force
attribute to overwrite the earliest rollback point.
# Copy the following text to the client to configure the rollback point:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<save-point>
<commit>
<label>SUPPORT VLAN<label>
<comment>vlan 1 to 100 and interfaces. Each vlan used for different custom as
fllows: ……</comment>
</commit>
</save-point>
</rpc>
The <label> and <comment> parameters are optional.
After receiving the commit request, the device returns a response in the following format if the
commit operation is successful:
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<save-point>
<commit>
<commit-id>2</commit-id>
</commit>
</save-point>
</data>
</rpc-reply>
Performing the save-point/rollback operation
# Copy the following text to the client to roll back the configuration:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<save-point>
<rollback>
<commit-id/>
<commit-index/>
<commit-label/>
</rollback>
</save-point>
</rpc>
The <commit-id> parameter uniquely identifies a rollback point.
The <commit-index> parameter specifies 50 most recently configured rollback points. The value of 0
indicates the most recently configured one and 49 indicates the earliest configured one.
The <commit-label> parameter exclusively specifies a label for a rollback point. The label is not
required for a rollback point.
Specify one of these parameters to roll back the specified configuration. If no parameter is specified,
this operation rolls back configuration based on the most recently configured rollback point.
After receiving the rollback request, the device returns a response in the following format if the
rollback operation is successful:
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">