Cisco Systems IE 2000 Clearing Configuration Information, Replacing and Rolling Back Configurations

A-19
Cisco IE 2000 Switch Software Configuration Guide
OL-25866-01
Appendix A Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Clearing Configuration Information
You can clear the configuration information from the startup configuration. If you reboot the swi tch with
no startup configuration, the switch enters the setup program so that you can r econfigure the switch with
all new settings.
Clearing the Startup Configuration File
To clear the contents of your startup configuration, use the erase nvram: or the erase startup-config
privileged EXEC command.
Caution You cannot restore the startup configuration file after it has been deleted.
Deleting a Stored Configuration File
To delete a saved configuration from flash memory, use the delete flash:filename privileged EXEC
command. Depending on the setting of the file prompt global configuration command, you might be
prompted for confirmation before you delete a file. By default, the switch promp ts for confirmation on
destructive file operations. For more information about the file prompt command, see the Cisco IOS
Command Reference for Release 12.2.
Caution You cannot restore a file after it has been deleted.
Replacing and Rolling Back Configurations
The configuration replacement and rollback feature repla ces the running configuration with any saved
Cisco IOS configuration file. You can use the rollback function to roll back to a previous configuration.
Understanding Configuration Replacement and Rollback
Archiving a Configuration
The configuration archive provides a mechanism to store, organize, and manage an archive of
configuration files. The configure replace privileged EXEC command increases the configuration
rollback capability. As an alternative, you can save copies of the running configuration by using the copy
running-config destination-url privileged EXEC command, storing the replacement file either locally
or remotely. However, this method lacks any automated file management. The configuration replacement
and rollback feature can automatically save copies of the running configuration to the configurati on
archive.
You use the archive config privileged EXEC command to save configurations in the configuration
archive by using a standard location and filename prefix that is automatically appended with an
incremental version number (and optional timestamp) as each consecutive file is saved. You can specify
how many versions of the running configuration are kept in the archive. After the maximum number of
files are saved, the oldest file is automatically deleted when the next, most recent file is saved. The show
archive privileged EXEC command displays information for all the configuration files saved in the
configuration archive.