Basic Operation Guide 2013/06
Table Of Contents
- Switch Software
- Contents
- 1 Commands found in the Basic Operation Guide
- 2 Getting started
- 3 Using the Menu Interface
- 4 Using the Command Line Interface (CLI)
- Overview
- Accessing the CLI
- Using the CLI
- Return message types with CLI commands
- CLI interactive commands
- CLI control and editing
- 5 Using the HP WebAgent
- 6 Switch memory and configuration
- Overview
- Configuration file management
- Using the CLI to implement configuration changes
- Creating a custom default configuration
- Using the menu and WebAgent to implement configuration changes configuration file
- Zeroization
- Using Primary and Secondary flash image options
- Multiple configuration files
- Display configuration of selected interface
- Automatic configuration update with DHCP Option 66
- 7 Interface access and system information
- 8 Configuring IP addressing
- Overview
- IP configuration
- Loopback interfaces
- IP Preserve: retaining VLAN-1 IP addressing across configuration file downloads
- Configuring a single source IP address
- 9 Software management
- Downloading switch documentation and software from the web
- Viewing or downloading the software manual set
- Downloading software updates for your switch
- Software signing and verification
- Saving configurations while using the CLI
- Important: Best Practices for software updates
- Updating the switch: overview
- Updating the switch: detailed steps
- Rolling back switch software
- Viewing or transferring alternate configuration files
- Downloading switch documentation and software from the web
- Index

NOTE: If you use the CLI to make a change to the running-config file, you should either use the
write memory command or select the save option allowed during a reboot (Figure 17, above) to
save the change to the startup-config file. That is, if you use the CLI to change a parameter setting,
but then reboot the switch from either the CLI or the menu interface without first executing the write
memory command in the CLI, the current startup-config file will replace the running-config file, and
any changes in the running-config file will be lost.
Using the Save command in the menu interface does not save a change made to the running config
by the CLI unless you have also made a configuration change in the menu interface. Also, the
menu interface displays the current running-config values. Thus, where a parameter setting is
accessible from both the CLI and the menu interface, if you change the setting in the CLI, the new
value will appear in the menu interface display for that parameter. However, as indicated above,
unless you also make a configuration change in the menu interface, only the write memory command
in the CLI will actually save the change to the startup-config file.
How to reset the startup-config and running-config files to the factory default configuration. This
command reboots the switch, replacing the contents of the current startup-config and running-config
files with the factory-default startup configuration.
Syntax:
erase startup-config
Example 27 The erase startup-config command
HP Switch(config)# erase startup-config
Configuration will be deleted and device rebooted, continue [y/n]?
Press [y] to replace the current configuration with the factory default configuration and reboot the
switch. Press [n] to retain the current configuration and prevent a reboot.
In a redundant management system, this command erases the startup config file on both the active
and the standby management modules as long as redundancy has not been disabled. If the standby
management module is not in standby mode or has failed selftest, the startup config file is not
erased.
Creating a custom default configuration
NOTE: This feature is not supported on the HP 3800 switches.
The custom default configuration feature provides the ability to initialize a switch to a different
state from the factory default state when you delete the active configuration file. The factory default
configuration is not changed. If a custom configuration file has been created and the active
configuration file is deleted, the switch will boot up using the custom configuration file.
The feature provides the ability to:
• Use a customized configuration file as a default configuration file
• Enable the switch to start up with the specified default configuration
The existence of a custom default configuration file does not affect the results of loading a remotely
stored configuration file onto the switch.
Using a custom default configuration, you can configure the features you want to be in the default
configuration. When the active configuration is deleted using the erase startup command, the
active configuration is removed and the custom default configuration file will be used upon bootup.
The standard default configuration file remains and is used if there is no custom default configuration.
54 Switch memory and configuration










