Overview
This chapter describes:
■
How switch memory manages configuration changes
How the CLI implements configuration changes
■
■
How the menu interface and web browser interface implement configu-
ration changes
■
How the switch provides software options through primary/secondary
flash images
How to use the switch's primary and secondary flash options, including
■
displaying flash information, booting or restarting the switch, and other
topics
Configuration File Management
The switch maintains two configuration files, the running-config file and the
startup-config file.
Volatile Memory
Running-Config File
(Controls switch operation. When the switch boots, the
contents of this file are erased and replaced by the
contents of the startup-config file.)
Flash (Non-Volatile) Memory
Startup-Config File
(Preserves the most recently saved configuration
through any subsequent reboot.)
Figure 6-1.
Conceptual Illustration of Switch Memory Operation
Running Config File: Exists in volatile memory and controls switch
■
operation. If no configuration changes have been made in the CLI since
the switch was last booted, the running-config file is identical to the
startup-config file.
Switch Memory and Configuration
Overview
CLI configuration
changes are written to
this file. To use the CLI to
save the latest version of
this file to the startup-
config file, you must
execute the write
memory command.
Menu interface configu-
ration changes are simul-
taneously written to both
of these files.
6-3