264
<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/> parameters 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 roll backs 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">
<ok></ok>
</rpc-reply>
Performing the save-point/end operation
# Copy the following text to the client to end the rollback configuration:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<save-point>
<end/>
</save-point>
</rpc>
After receiving the end request, the device returns a response in the following format if the end
operation is successful:
<rpc-reply message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Performing the save-point/get-commits operation
# Copy the following text to the client to get the rollback point configuration records:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<save-point>
<get-commits>
<commit-id/>
<commit-index/>
To Next Page
Loading...
Need help?
General