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
For example, suppose:
• Software release “A” is stored in primary flash and a later software release is stored in
secondary flash.
• The system operator is using memory slot 1 for a reliable, minimal configuration (named
minconfig) for the software version in the primary flash, and slot 2 for a modified
startup-config file (named newconfig) that includes untested changes for improved network
operation with the software version in secondary flash.
The operator wants to ensure that in case of a need to reboot by pressing the Reset button, or if a
power failure occurs, the switch will automatically reboot with the minimal startup-config file in
memory slot 1. Since a reboot due to pressing the Reset button or to a power cycle always uses
the software version in primary flash, the operator needs to configure the switch to always boot
from primary flash with the startup-config file named minconfig (in memory slot 1). Also, whenever
the switch boots from secondary flash, the operator also wants the startup-config named newconfig
to be used. The following two commands configure the desired behavior.
HP Switch(config)# startup-default pri config minconfig
HP Switch(config) # startup-default sec config newconfig
Overriding the default reboot configuration policy. This command provides a method for manually
rebooting with a specific startup-config file other than the file specified in the default reboot
configuration policy.
Syntax:
boot system flash <primary | secondary>
config <filename>
Specifies the name of the startup-config file to apply for the immediate boot instance
only. This command overrides the current reboot policy.
Using reload to reboot from the current flash image and startup-config file.
Syntax:
reload
This command boots the switch from the currently active flash image and
startup-config file. Because reload bypasses some subsystem self-tests, the switch
boots faster than if you use a boot command.
Note: To identify the currently active startup-config file, use the show config files
command.
Managing startup-config files in the switch
PageCommand
79rename config <current-filename> <newname-str>
79copy config <source-filename>
config <dest-filename>
81erase config [ <filename> | startup-config ]
82Erase startup-config using the front-panel Clear + Reset Buttons
Renaming an existing startup-config file
Syntax:
rename config <current-filename> <newname-str>
Multiple configuration files 79