HPE FlexNetwork 10500 SERIES, Configuration Manual

Page: 177 / 407

166
Rolling back the configuration based on a rollback point
You can roll back the running configuration based on a rollback point when one of the following
situations occurs:
•
A NETCONF client sends a rollback request.
•
The NETCONF session idle time is longer than the rollback idle timeout time.
•
A NETCONF client is unexpectedly disconnected from the device.
To roll back the configuration based on a rollback point, perform the following tasks:
1. Lock the system.
Multiple users might simultaneously use NETCONF to configure the device. As a best practice,
lock the system before rolling back the configuration to prevent other users from modifying the
running configuration.
2. Mark the beginning of a rollback operation. For more information, see " Performing the
save-point/begin operation ."
3. Edit the device configuration. For more information, see " Performing the edit-config operation ."
4. Configure the rollback point. For more information, see " Performing the save-point/commit
operation ."
You can repeat this step to configure multiple rollback points.
5. Roll back the configuration based on the rollback point. For more information, see " Performing
the save-point/rollback operation ."
The configuration can also be automatically rolled back based on the most recently configured
rollback point when the NETCONF session idle time is longer than the rollback idle timeout
time.
6. End the rollback configuration. For more information, see " Performing the save-point/end
operation ."
7. Release the lock.
Performing the save-point/begin operation
# Copy the following text to the client to mark the beginning of a rollback operation based on a
rollback point:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<save-point>
<begin>
<confirm-timeout>100</confirm-timeout>
</begin>
</save-point>
</rpc>
The <confirm-timeout> parameter specifies the rollback idle timeout time in the range of 1 to 65535
seconds (the default is 600 seconds). This parameter is optional.
After receiving the begin request, the device returns a response in the following format if the begin
operation is successful:
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<save-point>
<commit>
<commit-id>1</commit-id>
</commit>
</save-point>