compare [to checkpoint2]
compare checkpoint1 to checkpoint2
admin>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command displays the differences between rollback checkpoints and the active operational configuration, with checkpoint1 as the base/first file to which checkpoint2 is compared.
When no parameters are defined, this command compares the active configuration to the most recent rollback file. when the checkpoint2 parameter is defined, this command compares the active configuration to the specified file. When both checkpoint parameters are defined, this command compares one specified file to another specified file.
A compare operation does not check authorization of each line of output. Permission to execute the compare command should only be given to users who are allowed to view the entire system configuration.
The defaults for checkpoint1 and checkpoint2 are context-aware and differ based on the branch in which the command is executed. In general, the default for checkpoint1 matches the context from which the command is issued.
Specifies the configuration files to use as comparison sources.
delete checkpoint | rescue
admin>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command deletes a rollback checkpoint file and decrements the suffix ID numbers of all older rollback checkpoint files.
If the config redundancy rollback-sync command is enabled, the rollback delete command will also delete the equivalent checkpoint in the standby checkpoint file and shuffle the suffixes on the standby CF.
It is not advised to manually delete a rollback checkpoint (for example, using the file delete command). If a rollback checkpoint file is manually deleted without using the admin rollback delete command then the suffixes of the checkpoint files are NOT shuffled, nor is the equivalent checkpoint file deleted from the standby CF. This manual deletion creates a ‟hole” in the checkpoint file list until enough new checkpoints have been created to roll the ‟hole” off the end of the list.
Specifies the rollback checkpoint or rescue file to delete.
revert checkpoint | rescue [now]
admin>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command initiates a configuration rollback revert operation that will return the configuration state of the node to a previously saved checkpoint. The rollback revert minimizes impacts to running services. There are no impacts in areas of configuration that did not change since the checkpoint. Configuration parameters that changed (or items on which changed configuration have dependencies) are first removed (revert to default) and the previous values are then restored (can be briefly service impacting in changed areas).
Specifies the rollback checkpoint or rescue file to revert to.
Keyword to force a rollback reversion without prompting for confirmation.
save [comment comment] [rescue]
admin>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command saves the current operational configuration as a rollback checkpoint file at the configured rollback location, using the filename specified by the rollback-location command, with the suffix *.rb. The suffixes of all previously saved rollback checkpoint files are automatically incremented by one (*.rb becomes *.rb.1, *.rb.1 becomes *.rb.2, and so on).
If the optional rescue keyword is not used, this command saves a rollback checkpoint at the location and with the filename specified by the rollback location with a suffix of ".rb". The previously saved checkpoints will have their suffixes incremented by one (.rb.1 becomes.rb.2, and so on). If there are already as many checkpoint files as the maximum number supported, the last checkpoint file is deleted.
By default, there can be a maximum of 10 rollback checkpoint files, the latest with suffix *.rb and nine older files with suffixes *.rb.1 through *.rb.9. If the maximum number of checkpoint files is reached and a new one is saved, the oldest checkpoint file is deleted. The maximum number of rollback checkpoint files that can be saved can be configured with the local-max-checkpoints and remote-max-checkpoints commands.
If the rescue keyword is used, this command saves the current operational configuration as a rescue rollback file at the location and with the filename specified by the rescue-location command. The rescue file uses the suffix *.rc. There can be only one rescue file saved at a time. Saving a new rescue file deletes and replaces any existing rescue file.
A valid rollback checkpoint and rescue location must be configured with the rollback-location and rescue-location commands before saving a checkpoint or rescue file.
See rollback-location, rescue-location, local-max-checkpoints and remote-max-checkpoints for more information.
Specifies a string, up to 255 characters, describing the associated rollback checkpoint file.
Keyword to save the current operational configuration as a rescue file.
view [checkpoint | rescue]
admin>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command displays the configuration settings saved in a rollback checkpoint or rescue file, or the active operational system configuration.
Specifies the configuration file to view.
local-max-checkpoints [1..50]
no local-max-checkpoints
config>system>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command configures the maximum number of rollback checkpoint files when the rollback location is on the local compact flash.
10
Specifies the maximum number of rollback checkpoint files.
remote-max-checkpoints [1..200]
no remote-max-checkpoints
config>system>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command configures the maximum number of rollback checkpoint files that can be saved on a remote device.
10
Specifies the maximum number of rollback checkpoint files.
no rescue-location file-url
config>system>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
The location and filename of the rescue configuration is configurable to be local (on the compact flash) or remote. The suffix ‟.rc” will be automatically appended to the filename when a rescue configuration file is saved. Trivial FTP (tftp) is not supported for remote locations.
A valid rescue location must be configured before a rescue configuration is saved.
no rollback-location file-url
config>system>rollback
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command configures the location and generic filename of the rollback rescue configuration file.
A rescue file can be saved locally on the compact flash or on a remote device. The file URL must not contain a suffix, just a path/directory and filename. The suffixes for rollback checkpoint files are ‟.rb”, ".rb.1", ..., ".rb.9" and are automatically appended to rollback checkpoint files.
A valid rollback-location must be configured before a rollback save command is executed.
Specifies the local or remote file path for the rollback rescue configuration file.