Basic System Configuration Guide System Management
Edition: 01 3HE 11010 AAAC TQZZA 215
6.3.4.2 Specifying Post-Boot Configuration Files
Two post-boot configuration extension files are supported and are triggered when
either a successful or failed boot configuration file is processed. The boot-bad-exec
and boot-good-exec 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.
For example, after a configuration file is successfully loaded, the specified URL can
contain a nearly identical configuration file with certain commands enabled or
disabled, or particular parameters specified and according to the script which loads
that file.
6.3.5 Automatic Synchronization
Use the CLI syntax displayed below to configure synchronization components
relating to active-to-standby CSM switchover. In redundant systems, synchronization
ensures that the active and standby CSMs have identical operational parameters,
including the active configuration, CSM, and IOM images in the event of a failure or
reset of the active CSM.
The force-switchover command forces a switchover to the standby CSM card.
To enable automatic synchronization, either the boot-env parameter or the config
parameter must be specified. The synchronization occurs when the admin save or
bof save commands are executed.
When the boot-env parameter of the synchronize command is specified, the BOF,
boot.ldr, config, and image files are automatically synchronized. When the config
parameter is specified, only the configuration files are automatically synchronized.
Synchronization also occurs whenever the BOF is modified with persistence on and
when an admin>save command is entered with no filename specified.
6.3.5.1 Boot-Env Option
The boot-env option enables a synchronization of all the files used in system
initialization.
To Next Page
Loading...
