Basic Operation Guide 2014/02

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 WebAgent: Click on Save. This overwrites both the running-config file and the
startup-config file with the changes you have specified in the WebAgent screen.
Note that using the CLI instead of the menu or WebAgent 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:
HP Switch(config)# interface ethernet 5 disable
The above command disables port 5 in the running-config file, but not in the startup-config file.
Port 5 remains disabled only until the switch reboots. If you want port 5 to remain disabled through
the next reboot, use write memory to save the current running-config file to the startup-config file
in flash memory.
HP Switch(config)# write memory
If you use the CLI to make a configuration change and then change from the CLI to the Menu
interface without first using write memory to save the change to the startup-config file, then the
switch prompts you to save the change. For example, if you use the CLI to create VLAN 20, and
then select the menu interface, VLAN 20 is configured in the running-config file, but not in the
startup-config file. In this case you will see:
HP Switch(config)# vlan 20
HP Switch(config)# menu
Do you want to save current configuration [y/n]?
If you type ‘y’, the switch overwrites the startup-config file with the runningconfig file, and your
configuration change(s) will be preserved across reboots. If you type ‘n’, your configuration
change(s) will remain only in the runningconfig file. In this case, if you do not subsequently save
the running-config file, your unsaved configuration changes will be lost if the switch reboots for
any reason.
Storing and retrieving configuration files. You can store or retrieve a backup copy of the
startup-config file on another device. For more information, see "Transferring Switch Configurations"
in the Management and Configuration Guide for your switch.
USB autorun. This feature supports the ability to auto execute CLI commands stored on a USB flash
drive (for example, to configure the switch, update software, retrieve diagnostics, etc.). For more
information, see "Using USB to Download Switch Software" in the Management and Configuration
Guide for your switch.
Using the CLI to implement configuration changes
The CLI offers these capabilities:
• Access to the full set of switch configuration features
• The option of testing configuration changes before making them permanent
How to use the CLI to view the current configuration files. Use show commands to view the
configuration for individual features, such as port status or Spanning Tree Protocol. However, to
view either the entire startupconfig file or the entire running-config file, use the following commands:
• show config— Displays a listing of the current startup-config file.
• show running–config— Displays a listing of the current running-config file.
48 Switch Memory and Configuration