Usage Scenario
If the configuration file becomes inapplicable due to software upgrade, run the startup saved-configuration command to specify a new configuration file to be loaded at the next startup of the system.
The extension of the configuration file name must be .zip, .cfg or .dat. The system configuration file must be saved in the root directory of the storage device.
- A .cfg file is a text file. You can directly view the content of a .cfg file. After a .cfg file is specified as the configuration file, the system restores the commands in the file one by one when startup.
- A .zip file is the compression of a .cfg file, occupying less space. After a .zip file is specified as the configuration file, the system decompresses the file into a .cfg file, and then restores the commands in the file one by one when startup.
- A .dat file is a binary file. If the startup software version and the .dat file version are the same, the system restores all configurations in the .dat file in batches when the device starts. This speeds up the system startup.
This command is supported only by a physical system (PS).
Configuration Impact
The configuration file to be loaded at the next startup of the system is changed.
Precautions
- The specified configuration file has been created.
- *.dat file cannot be modified manually. Otherwise, the configuration file will fail to be loaded when the device stars, and the device will start with no configurations.
- If the autosave function is enabled and the startup saved-configuration command is run to modify the next-startup configuration file, a save operation is automatically triggered when the autosave interval expires. As a result, the configured next-startup configuration file is overwritten by the current configuration file. To prevent the incorrect overwriting, run the undo set save-configuration command to disable the autosave function before you configure the next-startup configuration file.