| |
|
|
checkpoint
Provides an alternative configuration to be used by the NSR® backup route controller.
Syntax: checkpoint [filename]
filename
Specify the name of the file to be used as the checkpoint configuration. Default Name: startup.chk
Description: The checkpoint configuration file provides for the loading of an alternative configuration on to the NSR® backup server. This alternative configuration is only written to the backup server as a one-time startup file named startup.chk. If an NSR® failover takes place, whether intentional or not, the backup becomes the new primary and the checkpoint configuration is used. If for any reason another failover takes place on the primary containing the checkpoint configuration, after the second failover, the checkpoint configuration does not reside on the new primary route controller and the standard startup.cfg file is used.
NOTE The checkpoint function does not replace the need for a startup.cfg file. The standard configuration file must exist for checkpoint to work.
NOTE It is recommended that you use the default name of startup.chk and not rename the checkpoint file.
The checkpoint functionality allows the administrator to have a configuration that will survive a single failover only. This is useful if an administrator wishes to implement a new feature, but is unsure of the feature's stability. Upon the first failover, the system returns to the known stable configuration.
Factory Default: None.
Command Mode: Privileged.
Example 1: The following example sets the checkpoint function to use the checkpoint function startup.chk file:
router#checkpoint
router#
Related Commands: write
show boot
show running-config
show startup-config
| |
|
|
Copyright © 2005
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: sys_mgmt.fm
HTML File Name: sys_mgmt9.html
Last Updated: 02/25/05 at 14:26:49