System Management
Basic System Configuration Guide 315
For example, assume the config-backup count is set to 5 and the configuration file is called
xyz.cfg. When a save command is executed, the file xyz.cfg is saved with a .1 extension. Each
subsequent config-backup command increments the numeric extension until the maximum
count is reached. The oldest file (5) is deleted as more recent files are saved.
xyz.cfg
xyz.cfg.1
xyz.cfg.2
xyz.cfg.3
xyz.cfg.4
xyz.cfg.5
xyz.ndx
Each persistent index file is updated at the same time as the associated configuration file.
When the index file is updated, then the save is performed to xyz .cfg and the index file is
created as xyz.ndx. Synchronization between the active and standby SF/CPMSF/CPM is
performed for all configurations and their associated persistent index files.
CLI Syntax: config>system
config-backup count
Example: config>system#
config>system# config-backup 7
The following example shows the config-backup configuration.
A:ALA-12>config>system>time# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
name "ALA-12"
contact "Fred Information Technology"
location "Bldg.1-floor 2-Room 201"
clli-code "abcdefg1234"
coordinates "N 45 58 23, W 34 56 12"
config-backup 7
...
----------------------------------------------
A:ALA-12>config>system>time#
Post-Boot Configuration Extension Files
Two post-boot configuration extension files are supported and are triggered when either a
successful or failed boot configuration file is processed. The commands specify URLs for the
CLI scripts to be run following the completion of the boot-up configuration. A URL must be
specified or no action is taken. The commands are persistent between router (re)boots and are
included in the configuration saves (admin>save).
To Next Page
Loading...
