173
Parameters
file-url: Specifies a file path for saving the running configuration. The file name must use the .cfg
extension. Excluding the .cfg extension, the file path is a string of 1 to 255 characters. If you specify
the all keyword or the slot slot-number option, the file path cannot include a member ID. If the file
path includes a folder name, the folder must already exist on all IRF member devices.
all: Saves the running configuration to all member devices. If you do not specify this keyword or the
slot slot-number option, the command saves the running configuration only to the master.
slot slot-number: Specifies a subordinate device by its member ID. If you do not specify a
subordinate device or the all keyword, this command saves the running configuration only to the
master.
safely: Saves the configuration file in safe mode. If you do not specify this keyword, the device saves
the configuration file in fast mode.
backup: Saves the running configuration to a configuration file, and specifies the file as the backup
next-startup configuration file. If you do not specify this keyword or the main keyword, the command
specifies the saved file as the main next-startup configuration file.
main: Saves the running configuration to a configuration file, and specifies the file as the main
next-startup configuration file. If you do not specify this keyword or the backup keyword, the
command specifies the saved file as the main next-startup configuration file.
force: Saves the running configuration to the existing next-startup configuration file without
prompting for confirmation. If you do not specify this keyword, the system prompts you to confirm the
operation. If you do not confirm the operation within 30 seconds, the system automatically aborts the
operation. If you enter Y within the time limit, you can continue the save process and change the
target file name during the process.
changed: Overwrites the target configuration file with the running configuration if an inconsistency is
detected between the settings in the configuration file and the running configuration. The save
command does not take effect if no inconsistency is detected. If you do not specify this keyword, the
save command always overwrites the target configuration file with the running configuration.
Usage guidelines
If the file specified for this command does not exist, the system creates the file before saving the
configuration. If the file already exists, the system prompts you to confirm whether to overwrite the
file. If you choose to not overwrite the file, the system cancels the save operation.
This command saves the running configuration to an .mdb binary file as well as a .cfg text file. The
two files use the same file name. An .mdb file takes less time to load than a .cfg file.
When you use the save [ safely ] [ backup | main ] [ force ] [ changed ] command, follow these
guidelines:
• In safe mode, the system saves configuration in a temporary file and starts overwriting the
target next-startup configuration file after the save operation is complete. If a reboot, power
failure, out of memory, or out of storage space event occurs during the save operation, the
next-startup configuration file is retained.
• In fast mode, the device directly overwrites the target next-startup configuration file. If a reboot,
power failure, out of memory, or out of storage space event occurs during this process, all
settings in the next-startup configuration file are lost.
Safe mode is slower than fast mode, but more secure. As a best practice, specify the safely keyword
for reliable configuration saving.
Examples
# Save the running configuration to backup.cfg, without specifying the file as a next-startup
configuration file.
<Sysname> save backup.cfg
The current configuration will be saved to flash:/backup.cfg. Continue? [Y/N]:y
To Next Page
Loading...
Need help?
General