Switch Memory and Configuration

Multiple Configuration Files

If you wanted to experiment with configuration changes to the software version in secondary flash, you could create and assign a separate startup- config file for this purpose.

 

 

 

 

 

 

 

 

The first two commands copy the config1

 

 

 

 

startup-config file to config2, and then

 

 

 

 

make config2 the default startup-config

 

 

 

 

file for booting from secondary flash.

 

 

 

 

 

 

 

 

 

 

 

Figure 6-21. Example of Creating and Assigning a New Startup-Config File

 

 

 

 

 

N o t e

 

You can also generate a new startup-config file by booting the switch from a

 

 

flash memory location from which you have erased the currently assigned

 

 

startup-config file. Refer to “Erasing a Startup-Config File” in the next section.

 

 

 

 

 

Erasing a Startup-Config File

You can erase any of the startup-config files in the switch’s memory slots. In some cases, erasing a file causes the switch to generate a new, default- configuration file for the affected memory slot.

In a redundant management system, this command erases the config or startup config file on both the active and the standby management modules as long as redundancy has not been disabled. If the standby management module is not in standby mode or has failed selftest, the config or startup config file is not erased.

Syntax: erase < config < filename >> startup-config >

config < filename >: This option erases the specified startup- config file. If the specified file is not the currently active startup-config file, then the file is simply deleted from the memory slot it occupies. If the specified file is the currently active startup-config file, then the switch creates a new, default startup-config file with the same name as the erased file, and boots using this file. (This new startup-config file contains only the default configuration for the software version used in the reboot.)

6-35