113
Specifying a startup configuration file
To specify a startup configuration file, you can:
•
Use the
save
command. If you save the running configuration to the specified configuration file in
the interactive mode, the system automatically sets the file as the main startup configuration file.
•
Use the command dedicated to specify a startup configuration file, which is described in the
following table:
Follow the step below to specify a startup configuration file:
To do…
Use the command…
Remarks
Specify a startup configuration file
of all member switches
startup
saved-configuration
cfgfile
[
backup
|
main
]
Required
Available in user view
CAUTION:
A configuration file must use
.cfg
as its extension name. The startup configuration file must be saved in the
storage media’s root directory.
Backing up the startup configuration file
The backup function allows you to copy the startup configuration file from the device to the TFTP server.
The backup operation backs up the main startup configuration file to the TFTP server.
Follow the step below to back up the startup configuration file:
To do…
Use the command…
Remarks
Back up the startup configuration
file to the specified TFTP server
backup startup-configuration to
dest-addr
[
dest-
filename
]
Required
Available in user view
NOTE:
Before the backup operation, perform the following steps:
•
Make sure that the server is reachable and enabled with TFTP service, and the client has the read and
write permission.
•
Use the
display startup
command (in user view) to check whether you have specified a startup
configuration file. If the file is set as NULL or does not exist, the backup operation fails.
Deleting a startup configuration file
You can delete a startup configuration file at the CLI. You can choose to delete either the main, the
backup, or both. If the device has only one startup configuration file, the system only sets the startup
configuration file to NULL.
You may need to delete a startup configuration file for one of the following reasons:
•
After you upgrade system software, the existing startup configuration files do not match the new
system software.
•
Startup configuration files are corrupted, which is often caused by loading an incorrect
configuration file.
