Saving a Configuration File
To save the current configuration to the active configuration file, you can either use the “configuration write” command (requires running in Config mode) or the “write memory” command (requires running in Enable mode).
To save the configuration to the active configuration file, run:
switch (config) # configuration write
To save the configuration to a user-specified file without making the new file the active configuration file, run:
switch (config) # configuration write to myconf no-switch
To save the configuration to a user-specified file and make the new file the active configuration file, run:
switch (config) # configuration write to myconf
To display the available configuration files and the active file, run:
switch (config) # show configuration files initial myconf (active) switch (config) #
Loading a Configuration File
By default, or after a system reset, the system loads the default “initial” configuration file.
To load a different configuration file and make it the active configuration:
switch > switch > enable switch # configure terminal switch (config) # configuration switch-to myconfig switch (config) #
On director switch systems with dual management modules, load the configuration file according to the following:
- Power cycle the system.
Load the configuration on the top CPU that serves as the chassis master according to the procedure described above.
If the configuration file is loaded on a different CPU than the SM HA master (SM HA master that servers the VIP), the SM configuration is overwritten.
Restoring Factory Default Configuration
If system configuration becomes corrupted, it is suggested to restore factory default configuration.
To restore factory default configuration on a single management module system, run:
switch (config) # reset factory keep-basic
To restore factory default configuration on a dual management module system:
If the system configuration ever becomes corrupted it is suggested to restore the factory default configuration.
- Connect to a remote console/serial connection.
- Remove the slave management module.
Run "reset factory":
switch (config) # reset factory keep-basic
Please wait for reboot to complete before moving to the next step.
Log in as “admin” and start running the Mellanox Configuration Wizard.
- Insert the slave management module.
Remove the master management module.
A takeover will occur changing the Slave management module role to Master.Repeat Step 3 on the new Master management module.
- Insert the other management module. No takeover will occur at this stage.
- Power cycle the system.
Managing Configuration Files
There are two types of configuration files that can be applied on the switch, BIN files (binary) and text-based configuration files.
BIN Configuration Files
BIN configuration files are not human readable. Additionally, these files are encrypted and contain integrity verification preventing them from being edited and used on the switch.
To create a new BIN configuration file:
switch (config) # configuration new my-filename
A newly created BIN configuration file is always empty and is not created from the running-config.
To upload a BIN configuration file from a switch to an external file server:
switch (config) # configuration upload my-filename scp://myusername@my-server/path/to/my/<file>
To fetch a BIN configuration file:
switch (config) # configuration fetch scp://myusername@my-server/path/to/my/<file>
To see the available configuration files:
switch (config) # show configuration files initial (active) my-filename Active configuration: initial Unsaved changes: no switch (config) #
To load a BIN configuration file:
switch (config) # configuration switch-to my-filename This requires a reboot. Type 'yes' to confirm: yes
Applying a new BIN configuration file changes the whole switch’s configuration and requires system reboot which can be performed using the command "reload".
A binary configuration file uploaded from the switch is encrypted and has integrity verification. If the file is modified in any manner, the fetch to the switch fails.
Text Configuration Files
Text configuration files are text based and editable. It is similar in form to the output of the command “show running-config expanded”.
To create a new text-based configuration file:
switch (config) # configuration text generate active running save my-filename
A newly created text configuration file is always created from the running-config.
To apply a text-based configuration file:
switch (config) # configuration text file my-filename apply
Applying a text-based configuration file to an existing/running data port configuration may result in unpredictable behavior. It is therefore suggested to first clear the switch’s configuration by applying a specific configuration file (following the procedure in "BIN Configuration File") or by resetting the switch back to factory default.
To upload a text-based configuration file from a switch to an external file server:
switch (config) # configuration text file my-filename upload scp://root@my-server/root/tmp/my-filename
To fetch a text-based configuration file from an external file server to a switch:
switch (config) # configuration text fetch scp://root@my-server/root/tmp/my-filename
To apply a text-based configuration file:
switch (config) # configuration text file my-filename apply
When applying a text-based configuration file, the configuration is appended to the switch’s existing configuration. Only new or changed configuration is added. Reboot is not required.
