Basic System Configuration Guide CLI Usage
Edition: 01 3HE 11010 AAAC TQZZA 45
If a rollback reversion process includes any commands that will remove, rebuild, or
reboot an adapter card or fixed platform, the impacted adapter cards and platforms
are listed in a warning and the operator is asked whether to proceed or not with a y/
n prompt. There is no prompt if the rollback reversion is initiated via SNMP, or if the
now keyword is used. The following are examples of adapter card and fixed platform
commands that may generate a warning:
• config>card>card-type
• config>card>mda
• config>card>mda>mda-type
While the 7705 SAR is processing a rollback revert command, CLI and SNMP
commands from other users are still accepted and applied to the system. The only
commands that are blocked during this process are other rollback commands
including revert, save, and compare. Only one rollback command can be processed
at a time.
Performing a rollback reversion does not have any effect on existing rollback
checkpoint and rescue files; files are not renumbered or deleted. For example, if an
operator reverts to rollback checkpoint file 3, the file remains as *.rb.3. If the operator
then executes a rollback save command, the current configuration is saved as the
latest rollback (extension *.rb) and *.rb.3 is incremented to *.rb.4. In this scenario,
both the latest rollback checkpoint file and checkpoint file 3 will have the same
configuration information.
Currently running or scheduled CRON jobs are handled like all other configurations
during a rollback reversion. The CRON configuration will revert to the configuration
at the time the checkpoint was created.
The boot-good-exec or boot-bad-exec commands must be manually executed
after a rollback reversion; they are not automatically run.
3.8.2.1 Rollback Restrictions
Some hardware or software changes can prevent operators from performing the
rollback, or can affect the operation of the node following the reversion.
If hardware is removed or changed after a rollback checkpoint file is saved, the node
may not function as expected after the system reverts to that configuration. There is
no effect if new hardware is added into previously empty slots.