CX11x, CX31x, CX710 (Earlier Than V6.03) , and CX91x Series Switch Modules V100R001C10 Command Reference 17
This document provides the configuration commands of each feature supported by the CX11x&CX31x&CX91x series switches module, including the syntax, view, default level, description, parameters, usage guideline, related commands, and example of each command.
This document provides the configuration commands of each feature supported by the CX11x&CX31x&CX91x series switches module, including the syntax, view, default level, description, parameters, usage guideline, related commands, and example of each command.
startup saved-configuration
Function
The startup saved-configuration command specifies the system configuration file for next startup.
Parameters
Parameter | Description | Value |
---|---|---|
configuration-file | Specifies the name of a configuration file. Make sure that the file exists. | The value is a string of 5 to 64 case-sensitive characters without spaces. The file name extension can be .zip, .dat, or .cfg. |
slot slot-id | Specifies a member device in a stack. | The value is an integer. The range of the integer is dependent on the specific device. |
Usage Guidelines
Usage Scenario
When the original configuration file cannot be used due to the software upgrade, run the startup saved-configuration command to specify another configuration file for the next startup. The startup configuration file must be saved in the root directory of the storage device.
Follow-up Procedure
Run the reboot command to restart the device.
Precautions
The configuration file specified for the next startup must exist.
- The configuration file name extension must be .zip, .dat, or .cfg.
- A configuration file with the file name extension .cfg is a text file, and you can view the file content in the text file. After the file is specified as the configuration file for the next startup, the system restores all commands in the file one by one during a startup.
- A .cfg file is compressed to a .zip file that occupies less space. After being specified as the configuration file, the .zip file is decompressed to the .cfg file and the system restores all commands in the .cfg file one by one during 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. If the configuration file is a .dat file, the configuration cannot be synchronized to the management module, even if the display config-sync command output indicates a synchronization mode (Configurations are usually synchronized to the management module in this mode). The management module cannot manage .dat configuration files in a centralized manner. Therefore, the .dat file format is recommended.
Running the command triggers configuration synchronization.
After centralized switch management is enabled on the management module, the switch configuration file synchronization function is unavailable. If centralized switch management is enabled, a system of version 5.27 or later displays the message "Failed to synchronize configuration to the management modules, because the easyLink feature is enabled on the management modules." or the warning " The easyLink feature is enabled on the management modules, so all configuration commands executed on the switch module CLI cannot be saved to the management modules. After the switch module is restarted, the configuration commands will be lost." This phenomenon is normal.
- After the startup saved-configuration command
is executed, the switch module configuration is synchronized to the
management module:
begin synchronize configuration to SMM ...
Each switch module synchronizes the working mode in the background and returns the synchronization result in the slot id:describe format.
In the results:
id indicates the board number and ranges from 1 to 16.
describe indicates the synchronization result, which can be any of the following:
- "upload configuration to SMM successfully." This indicates a normal situation.
- "configuration is the same with SMM, needn't sync to SMM." This indicates a normal situation.
- "config-sync has been disabled." This indicates that synchronization is disabled. You can run the undo config-sync disable command to enable synchronization.
- "Failed to synchronize configuration to the management modules, because the easyLink feature is enabled on the management modules." This indicates that the switch module configuration fails to be uploaded to the management module because switch centralized management is enabled on the management module.
- "can't communicate with SMM." You need to check whether the management module is present and whether the switch module communicates with the management module properly.
- "synchronize configuration to SMM failed." You need to check whether the management module is present, whether centralized switch management is enabled (for versions earlier than 5.27), and whether the switch module communicates with the management module properly.
Note:
If switch centralized management is enabled, switch module configuration must be synchronized to the management module. The following describes when the switch module configuration is synchronized to the management module:
- The save command is executed.
- After the startup saved-configuration command is executed, the specified configuration file will be synchronized to the management module.
- Every 5 minutes.
- A reboot command is executed.
- After the reset saved-configuration command is executed and confirmed, the configuration is deleted and synchronized to the management module.
- After the working mode command is executed and confirmed, the working mode and the corresponding system configuration are synchronized to the management module.
If a system of a version earlier than 5.27 performs any of the first three types of synchronization, the command-line interface (CLI) does not display any information.
If any of the last three types of synchronization is performed on any system version or any of the first three types of synchronization is performed on a system of version 5.27 or later, the CLI is blocked (no input supported) until the synchronization is complete.