This page is designed for:
CAUTION All of these steps should be done using an out of band connection. This process is disruptive and will require downtime.
All this information can be found in the switch External User Guides.
It is recommended to do a show run on each switch and save that configuration before attempting the following procedures.
Maximum number of checkpoints:
Save the configuration to a checkpoint.
sw-spine-001(config)# copy running-config checkpoint CSM1_0
Example output:
Note: checkpoint name with special characters not allowed (only
alphanumeric, hyphen, and underscore are allowed)
Check on the saved checkpoints.
sw-spine-001(config)# show checkpoint
Example output:
NAME TYPE WRITER DATE(YYYY/MM/DD) IMAGE VERSION
CSM1_0 latest User 2022-01-13T16:51:37Z GL.10.08.1021
CSM1_2 latest User 2022-01-13T16:51:48Z GL.10.08.1021
startup-config startup User 2021-12-20T17:35:58Z GL.10.08.1021
Copying the existing checkpoint point to the startup config to switch between CSM 1.0 and CSM 1.2 configuration.
Copying the checkpoint to startup:
sw-spine-001(config)# copy checkpoint CSM1_2 startup-config
Boot the system to start with configuration from different CSM version.
sw-spine-001(config)# boot system
The switch will now boot to the desired configuration.
This should only need to be done once (unless hardware is added or PoR config has changed). Once this configuration file has been saved, the administrator should be able to switch between the two configuration files.
The following example is a 1.0 system that is going to 1.2.
Save the startup config to new XML config.
sw-leaf-bmc-001(config)# copy config://startup.xml config://csm1.0.xml
Erase the startup config and reboot.
Erase the startup config.
delete startup-configuration
Example output:
Proceed to delete startup-configuration [confirm yes/no(default)]:yes
Reboot after erasing the config.
reload
Example output:
System configuration has been modified. Save? [yes/no]:no
Continuing without saving system configuration
Proceed to reboot the system? [confirm yes/no]:yes
This will boot the switch to factory defaults.
Paste in the new CANU generated config once the switch boots into the factory defaults.
Save the config.
sw-cdu-001(config)# do write memory
sw-cdu-001(config)# copy config://startup.xml config://csm1.2.xml
Copy completed will be returned if successful.
Verify that both configs exist.
sw-cdu-001(config)# dir config
Example output:
Directory contents for folder: config
Date (modified) Size (bytes) Name
--------------------- ------------
------------------------------------------
2022-01-12T22:21:35Z 53441 csm1.0.xml
2022-01-12T22:34:03Z 97654 csm1.2.xml
2022-01-12T22:33:47Z 97654 startup.xml
This process should be used when configuration files for the desired CSM version are currently on the switch.
The following example shows going from CSM 1.2 to CSM 1.0 switch configuration.
View the current switch configuration files.
OS10(config)# dir config
Example output:
Directory contents for folder: config
Date (modified) Size (bytes) Name
--------------------- ------------
------------------------------------------
2022-01-12T22:21:35Z 53441 csm1.0.xml
2022-01-12T22:34:03Z 97654 csm1.2.xml
2022-01-12T22:40:58Z 53441 startup.xml
Copy the desired switch config to the startup config and reload.
(config)# copy config://csm1.0.xml config://startup.xml
(config)# reload
System configuration has been modified. Save? [yes/no]:no
The switch will then boot to the desired configuration.
This should only need to be done once (unless hardware is added or PoR config has changed). Once this configuration file has been saved, the administrator should be able to switch between the two configuration files.
The following example is a 1.0 system that is going to 1.2.
Write the current configuration to a file. This copies the current running config to a binary config file.
(config) # configuration write to csm1.0
Verify the new configuration file was created.
(config) # show configuration
Example output:
files
csm1.0 (active)
initial
initial.bak
Active configuration: csm1.0
Unsaved changes : no
Create a new config file for CSM 1.2.
When a new config file is created, no data is written to it. The administrator will boot to this new config file and paste the CANU generated config to it.
(config) # configuration new csm1.2
Check that the configuration files contain the new csm1.2 blank config that was just created.
(config) # show configuration
Example output:
files
csm1.0 (active)
csm1.2
initial
initial.bak
Active configuration: csm1.0
Unsaved changes : no
Switch to the new config, which requires a reboot.
(config) # configuration switch-to csm1.2
This requires a reboot.
Type 'yes' to confirm: yes
Once the switch is rebooted, verify the config file is correct. It should reboot without any configuration.
switch-cc30b4 [standalone: master] # show configuration files
Example output:
csm1.0
csm1.2 (active)
initial
initial.bak
Active configuration: csm1.2
Unsaved changes : yes
Paste in the new CANU generated 1.2 config.
Save the config.
(config) # write memory
This process should be used when configuration files for the desired CSM version are currently on the switch.
In the following example, the switch configuration will go from CSM 1.2 to CSM 1.0.
Verify that the correct configuration file exists on the switch.
sw-spine-001 [mlag-domain: master] (config) # show configuration files
Example output:
csm1.0
csm1.2 (active)
csm1.2.bak
initial
initial.bak
Active configuration: csm1.2
Unsaved changes : no
Switch to desired config version, which requires a reboot.
(config) # configuration switch-to csm1.0
This requires a reboot.
Type 'yes' to confirm: yes
The switch should boot to the config version typed in the previous command.
Verify the config version after the switch is booted.
# show configuration files
Example output:
csm1.0 (active)
csm1.2
csm1.2.bak
initial
initial.bak
Active configuration: csm1.0
Unsaved changes : yes