Switch Memory and Configuration

Multiple Configuration Files

Note: Where a file is assigned to either the primary or the secondary flash, but is not the currently active startup- config file, erasing the file does not remove the flash assignment from the memory slot for that file. Thus, if the switch boots using a flash location that does not have an assigned startup-config, then the switch creates a new, default startup-config file and uses this file in the reboot. (This new startup-config file contains only the default configuration for the software version used in the reboot.) Executing write memory after the reboot causes a switch- generated filename of configx to appear in the show config files display for the new file, where x corresponds to the memory slot number.

startup-config:This option erases the currently active startup- config file and reboots the switch from the currently active flash memory location. The erased startup-config file is replaced with a new startup-config file. The new file has the same filename as the erased file, but contains only the default configuration for the software version in the flash location (primary or secondary) used for the reboot. For example, suppose the last reboot was from primary flash using a configuration file named minconfig. Executing erase startup-configreplaces the current content of minconfig with a default configuration and reboots the switch from primary flash.

Figure 6-22illustrates using erase config < filename > to remove a startup-config file.

Figure 6-22. Example of Erasing a Non-Active Startup-Config File

6-36