HP 2910AL - Manual (Page 112)

Switch Memory and Configuration
Configuration File Management
■ Startup-config File: Exists in flash (non-volatile) memory and is used
to preserve the most recently-saved configuration as the “permanent”
configuration.
Booting the switch replaces the current running-config file with a new run­
ning-config file that is an exact copy of the current startup-config file.
N o t e Any of the following actions boots the switch:
• Executing the boot or the reload command in the CLI
• Executing the boot command in the menu interface
• Pressing the Reset button on the front of the switch
• Removing, then restoring power to the switch
For more on reboots and the switch’s dual-flash images, refer to “Using
Primary and Secondary Flash Image Options” on page 6-13.
Options for Saving a New Configuration. Making one or more changes
to the running-config file creates a new operating configuration. Saving a new
configuration means to overwrite (replace) the current startup-config file with
the current running-config file. This means that if the switch subsequently
reboots for any reason, it will resume operation using the new configuration
instead of the configuration previously defined in the startup-config file. There
are three ways to save a new configuration:
■ In the CLI: Use the write memory command. This overwrites the current
startup-config file with the contents of the current running-config file.
■ In the menu interface: Use the Save command. This overwrites both the
running-config file and the startup-config file with the changes you have
specified in the menu interface screen.
■ In the web browser interface: Use the [Apply Changes] button or other
appropriate button. This overwrites both the running-config file and the
startup-config file with the changes you have specified in the web browser
interface window.
Note that using the CLI instead of the menu or web browser interface gives
you the option of changing the running configuration without affecting the
startup configuration. This allows you to test the change without making it
“permanent”. When you are satisfied that the change is satisfactory, you can
make it permanent by executing the
write memory command. For example,
suppose you use the following command to disable port 5:
ProCurve(config)# interface ethernet 5 disable
6-4