Service Management Tasks
208 Basic System Configuration Guide
• Specify the file URL location to save the running configuration. If a destination is not
specified, the files are saved to the location where the files were found for that boot
sequence. The same configuration can be saved with different file names to the same
location or to different locations.
•The detail option adds the default parameters to the saved configuration.
•The index option forces a save of the index file.
• Changing the active and standby addresses without reboot standby CPM may cause
a boot-env sync to fail.
The following command saves a configuration:
CLI Syntax: bof# save [cflash-id]
Example: A:ALA-1# bof
A:ALA-1>bof# save cf3:
A:ALA-1>bof#
The following command saves the system configuration:
CLI Syntax: admin# save [file-url] [detail] [index]
Example: A:ALA-1# admin save cf3:\test123.cfg
Saving config.# Saved to cf3:\test123.cfg
... complete
A:ALA-1#
Deleting BOF Parameters
You can delete specific BOF parameters. The no form of these commands removes the
parameter from configuration. The changes remain in effect only during the current power
cycle unless a save command is executed. Changes are lost if the system is powered down or
the router is rebooted without saving.
Deleting a BOF address entry is not allowed from a Telnet session.
Use the following CLI syntax to save and remove BOF configuration parameters:
CLI Syntax: bof# save [cflash-id]
Note: If the persist option is enabled and the admin save file-url command is executed with
an FTP path used as the file-url parameter, two FTP sessions simultaneously open to the
FTP server. The FTP server must be configured to allow multiple sessions from the same
login, otherwise, the configuration and index files will not be saved correctly.
To Next Page
Loading...
