Saves the current configuration from the switch's runtime memory to non-volatile memory.
| primary | Specifies the primary saved configuration. |
| secondary | Specifies the secondary saved configuration. |
| existing-config | Specifies an existing user-defined configuration. |
| new-config | Specifies a new user-defined configuration. |
Saves the current configuration to the location used on the last reboot.
The configuration takes effect on the next reboot.
Each file name must be unique and can be up to 32 characters long but cannot include any spaces, commas, or special characters.
Configuration files have a .cfg file extension. When you enter the name of the file in the CLI, the system automatically adds the .cfg file extension. Do not use this command with ASCII-formatted configuration files. Those configuration files have an .xsf file extension. For more information about using ASCII-formatted configuration files see the upload configuration [hostname | ipaddress] filename {vr vr-name} and the load script filename {arg1} {arg2} ... {arg9} commands.
This command also displays in alphabetical order a list of available configurations. The following is sample output that displays the primary, secondary, and user-created and defined configurations (“test” and “XOS1” are the names of the user-created and defined configurations):
exsh.9 # save configuration <cr> Execute the command primary Primary configuration file secondary Secondary configuration file <existing-config> Existing configuration file name "test" "XOS1" <new-config> New configuration file name
The switch prompts you to save your configuration changes. Enter y to save the changes or n to cancel the process.
If you enter n, the switch displays a message similar to the following:
Save configuration cancelled.
If you enter y, the switch saves the configuration and displays a series of messages. The following sections provide information about the messages displayed when you save a configuration on your switch.
Note
Configuration files are forward-compatible only and not backward-compatible. That is, configuration files created in a newer release, such as ExtremeXOS 12.4, might contain commands that do not work properly in an older release, such as ExtremeXOS 12.1.This section provides information about the characters supported by the switch for local filenames.
When naming a local file, remember the requirements listed above.
If you create and save a configuration with a new file name, the switch saves the new configuration and then prompts you to select the newly created configuration as the switch‘s default configuration.
The following sample output is similar to the message displayed:
Do you want to save configuration to test1.cfg? (y/n) Yes Saving configuration................................. done! Configuration saved to test1.cfg successfully.
The switch then prompts you to select which configuration to use to bootup the system. The following sample output is similar to the message displayed:
The current selected default configuration database to boot up the system (primary.cfg) is different than the one just saved (test.cfg). Do you want to make test.cfg the default database? (y/n)
Enter y to use the new configuration as the default configuration. Enter n to cancel the operation and keep using the current default, active configuration.
If you make and save changes to an existing configuration, the switch prompts you to save and override the existing configuration.
The following sample output is similar to the message displayed:
The configuration file test.cfg already exists. Do you want to save configuration to test.cfg and overwrite it? (y/n) Yes Saving configuration ............................... done! Configuration saved to test.cfg successfully.
The following sample output on a SummitStack is similar to the output displayed:
The configuration file primary.cfg already exists. Do you want to save configuration to primary.cfg and overwrite it? (y/N) Yes Saving configuration on primary ........... done! Synchronizing configuration to backup .... done! Saving config on Standbys (Slots: 1). ... Configuration saved on Standby (Slot 1): done!
If you override an existing configuration that is not the current default, active configuration, the switch prompts you to select which configuration to use to bootup the system. The following sample output is similar to the message displayed:
The current selected default configuration database to boot up the system (primary.cfg) is different than the one just saved (test.cfg). Do you want to make test.cfg the default database? (y/n) No Default configuration database selection cancelled.
Enter y to use the updated configuration as the default configuration. Enter n to cancel the operation and keep using the current default, active configuration.
The following command saves the current switch configuration to the configuration file named XOS1:
save configuration XOS1
The following command save the current switch configuration to the secondary configuration file:
save configuration secondary
This command was first available in ExtremeXOS 10.1.
The status messages displayed by the switch were updated in ExtremeXOS 11.1.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB