HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
iv Upgrading Boot ROM through a system reboot ··················\ ··················\ ··················\ ··················\ ············ ·········· 100 Upgrading system software through system reboot (method 1) ··················\ ··················\ ··················\ ·············· · 100 Upgrading system software through system reboot (method 2) ··················\ ··················\ ··················\ ·············· · 101 Upgrading software by installing hotfixes ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ····· 101 Basic concepts ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ···· ··················\ ··················\ · 101 Patch state ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ······· ··················\ ··················\ ····· 102 Hotfix configuration task list ··················\ ··················\ ··················\ ··················\ ··················\ ······ ··················\ ············· 104 Installation prerequisites ··················\ ··················\ ··················\ ··················\ ··················\ ·········· ··················\ ··············· 105 Installing a patch in one step ··················\ ··················\ ··················\ ··················\ ··················\ ······ ··················\ ··········· 105 Installing a patch step-by-step ··················\ ··················\ ··················\ ··················\ ··················\ ····· ··················\ ··········· 106 Uninstalling a patch step-by-step ··················\ ··················\ ··················\ ··················\ ··················\ ··· ··················\ ········ 107 Displaying and maintain ing software upgrade ··················\ ··················\ ··················\ ··················\ ··········· ··················\ ··· 108 Software upgrade examples ··················\ ··················\ ··················\ ··················\ ··················\ ··········· ··················\ ················ 108 Immediate upgrade conf iguration example ··················\ ··················\ ··················\ ··················\ ··············· ·············· 108 Hotfix configuration example ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ················· 110 Performing ISSU ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··· ··················\ ··················\ ··· 112 ISSU overview ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ····· ··················\ ··················\ ········· 112 ISSU upgrade procedure ··················\ ··················\ ··················\ ··················\ ··················\ ·············· ··················\ ·········· 112 ISSU states ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ···················\ ··········· 113 System software version rollback ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··········· 114 Performing an ISSU ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ······ 114 ISSU upgrade task list ··················\ ··················\ ··················\ ··················\ ··················\ ·············· ··················\ ··············· 114 ISSU upgrade prerequisites ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·· 115 Displaying version compatibility ··················\ ··················\ ··················\ ··················\ ··················\ ···· ··················\ ········ 116 Performing an ISSU for a compatible version ··················\ ··················\ ··················\ ··················\ ··········· ··············· 116 Performing an ISSU for an incompatible version ··················\ ··················\ ··················\ ··················\ ········ ············· 117 Setting the ISSU vers ion rollback timer ··················\ ··················\ ··················\ ··················\ ··············· ··················\ ···· 118 Performing a manual version rollback ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·· 118 Displaying and maintaining ISSU ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·········· 119 ISSU upgrade example ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ············· 120 Network status ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ···· ··················\ ··················\ ·········· 120 Network requirements ··················\ ··················\ ··················\ ··················\ ··················\ ················ ··················\ ··················\ ··· 120 Upgrade procedure ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ · ··················\ ··················\ ···· 121 Configuring link aggregation ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ················· 121 Configuring the TFTP server ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·· 123 Downloading the new system software image ··················\ ··················\ ··················\ ··················\ ··················\ ······· 123 Checking all IRF member switches before the ISSU upgrade ··················\ ··················\ ··················\ ··················\ · 124 Viewing the version compatibility ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·········· 126 Performing compatible ISSU upgrade ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··· 127 Performing incompatible ISSU upgrade ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ 128 Managing the device ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ················ 130 Configuring the device name ··················\ ··················\ ··················\ ··················\ ··················\ ········· ··················\ ················ 130 Changing the system time ··················\ ··················\ ··················\ ··················\ ··················\ ············ ··················\ ··················\ · 130 Configuration guidelines ··················\ ··················\ ··················\ ··················\ ··················\ ············ ··················\ ············ 130 Configuration procedure ··················\ ··················\ ··················\ ··················\ ··················\ ············· ··················\ ··········· 133 Enabling displaying the copyright statement ··················\ ··················\ ··················\ ··················\ ··········· ··················\ ······· 133 Changing the brand name ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ············ 134 Configuration preparation ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ···· 134 Configuration guidelines ··················\ ··················\ ··················\ ··················\ ··················\ ············ ··················\ ············ 135 Configuration procedure ··················\ ··················\ ··················\ ··················\ ··················\ ············· ··················\ ··········· 135 Configuring banners ··················\ ··················\ ··················\ ··················\ ··················\ ················· ··················\ ··················\ ····· 135 Banner message input modes ··················\ ··················\ ··················\ ··················\ ··················\ ·········· ··················\ ······ 136 Configuration procedure ··················\ ··················\ ··················\ ··················\ ··················\ ············· ··················\ ··········· 137Â
v Configuring the exception handling method ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ · 137 Rebooting the device ··················\ ··················\ ··················\ ··················\ ··················\ ················ ··················\ ··················\ ····· 137 Rebooting devices imme diately at the CLI ··················\ ··················\ ··················\ ··················\ ·············· ··················\ 138 Scheduling a device reboot ··················\ ··················\ ··················\ ··················\ ··················\ ·········· ··················\ ········· 138 Scheduling jobs ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··· ··················\ ··················\ ········· 139 Job configuration approaches ··················\ ··················\ ··················\ ··················\ ··················\ ········ ··················\ ······· 139 Configuration guidelines ··················\ ··················\ ··················\ ··················\ ··················\ ············ ··················\ ············ 139 Scheduling a job in th e non-modular approach ··················\ ··················\ ··················\ ··················\ ·········· ············ 140 Scheduling a job in the modular approach ··················\ ··················\ ··················\ ··················\ ·············· ··············· 140 Disabling Boot ROM access ··················\ ··················\ ··················\ ··················\ ··················\ ··········· ··················\ ················ 141 Configuring the port st atus detection timer··················\ ··················\ ··················\ ··················\ ············ ··················\ ·········· 141 Configuring temperature th resholds for a device ··················\ ··················\ ··················\ ··················\ ······· ··················\ ···· 141 Clearing unused 16-bit interface indexes ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ······ 142 Verifying and diagnosing transceiver modules ··················\ ··················\ ··················\ ··················\ ·········· ··················\ ···· 142 Diagnosing transc eiver modules ··················\ ··················\ ··················\ ··················\ ··················\ ······ ··················\ ······ 143 Displaying and maintainin g device management ··················\ ··················\ ··················\ ··················\ ·········· ··················\ 143 Automatic configuration introduction ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ········· 145 Typical application scenario ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ········· 145 How automatic configuration works ··················\ ··················\ ··················\ ··················\ ··················\ ··· ··················\ ··········· 146 Automatic configurati on work flow ··················\ ··················\ ··················\ ··················\ ··················\ ··· ··················\ ···· 146 Using DHCP to obtain an IP address and other configuration information ··················\ ··················\ ·············· 147 Obtaining the configuration file from the TFTP server ··················\ ··················\ ··················\ ··················\ · ············ 148 Executing the configuration file ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ·············· 150 Index ··················\ ··················\ ··················\ ··················\ ··················\ ··················\ ············· ··················\ ··················\ ··········· 151Â
1 Using the CLI At the command-line interface (CLI), you can enter text commands to configure, manage, and monitor your device. Figure 1 CLI example Logging in to the CLI You can log in to the CLI in a variety of ways. For example, you can log in through the console port, or by using Telnet or SSH. For more information about login methods, see Logging in to the CLI Command conventions Command conventions help you understand the sy ntax of commands. Commands in product manuals comply with the conventions listed in Table 1. Table 1 Command conventions Convention Descri ption Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [ ] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choi ces separated by vertical bars, from which you select one.
2 Convention Description [ x | y | ... ] Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none. { x | y | ... } * Asterisk marked braces enclose a set of requ ired syntax choices separated by vertical bars, from which you select at least one. [ x | y | ... ] * Asterisk marked square bracke ts enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none. & The argument or keyword and argument comb ination before the ampersand (&) sign can be entered 1 to n times. # A line that starts with a pound (#) sign is comments. Command keywords are case insensitive. The following example analyzes the syntax of the clock datetime time date command according to Tabl e 1 . Figure 2 Understanding command-line parameter s For example, to set the system time to 10:30:20, February 23, 201 1, enter the following command line at the CLI and press Enter: clock datetime 10:30:20 2/23/2011 Using the undo form of a command Most configuration commands have an undo form for canceling a configuration, restoring the default, or disabling a feature. For example, the info-center enable command enables the information center, and the undo info-center enable command disables the information center. CLI views Commands are grouped in different views by function. To use a command, you must enter the view of the command. CLI views are organized in a hierarchical structure, as shown in Figure 3 . E ach view has a unique prompt, from which you can identify where you are and what you can do. For example, the prompt [Sysname-vlan100] shows that you are in the view of VLAN 100 and can configure attributes for the VLAN. You are placed in user view immediately after you ar e logged in to the CLI. The user view prompt is < Device-name >, where the Device-name argument defaults to HP and can be changed by using the sysname command. In user view, you can perform some basic operations, including display, debug, file
3 management, FTP, Telnet, clock setting, and reboot. For more information about the sysname command, see Fundamentals Command Reference . Fro m u s e r vi ew, yo u c a n e n t e r sys t e m vi e w t o c o n f i g u re g l o b a l s e t t i n g s , i n c l u d i n g t h e d a yl i g h t s a vi n g t i m e, banners, and hotkeys. The system view prompt is [ Device-name]. From system view, you can enter different function vi ews. For example, you can enter interface view to configure interface parameters, enter VLAN view to add ports to the specific VLAN, enter user interface view to configure login user attributes, or create a local user and enter local user view to configure attributes for the local user. To display all commands available in a view, enter a question mark (?) at the view prompt. Figure 3 CLI view hierarchy Entering system view from user view Task Command Enter system view from user view. system-view Returning to the upper-level view from any view Task Command Return to the upper-level view from any view. quit Executing the quit command in user view terminates your connection to the device. NOTE: In public key code view, use the public-key-code end command to return to the upper-level view (public key view). In public key view, use the peer-public-key end command to return to system view.
4 Returning to user view from any other view You can return to user view from any other view by using the return command, instead of using the quit command repeatedly. Pressing Ctrl+Z has the same effect. To return to user view from any other view: Task Command Return to user view. return Accessing the CLI online help The CLI online help is context sensitive. You can enter a question mark at any point of a command to display all available options. To access the CLI online help, use one of the following methods: • Enter a question mark at a view prompt to display the first keywords of all commands available in the view. For example: ? User view commands: archive Specify archive settings backup Backup next startup-configuration file to TFTP serve\ r boot-loader Set boot loader bootrom Update/read/backup/restore bootrom cd Change current directory … • Enter some keywords of a command and a ques tion mark separated by a space to display available keywords and arguments. { Example 1: The question mark is in the place of a keyword, and the CLI displays all possible keywords with a brief description for each keyword. terminal ? debugging Send debug information to terminal logging Send log information to terminal monitor Send information output to current terminal trapping Send trap information to terminal { Example 2: The question mark is in the place of an argument, and the CLI displays the description of the argument. system-view [Sysname] interface vlan-interface ? VLAN interface [Sysname] interface vlan-interface 1 ? [Sysname] interface vlan-interface 1 The string indicates that the command is complete, and you can press Enter to execute the command. • Enter an incomplete keyword string followed by a question mark to display all keywords starting with the string. For example:
5 f? fixdisk format free ftp display ftp? ftp ftp-server ftp-user Entering a command When you enter a command, you can use some keys or hotkeys to edit the command line, or use abbreviated keywords or keyword aliases. Editing a command line You can use the keys listed in Tabl e 2 or the hotkeys listed in Tabl e 3 to edit a command line. Table 2 Keys for editing a command line Ke y Function Common keys If the edit buffer is not full, pressing a common key inserts the character at the position of the cursor and moves the cursor to the right. Backspace Deletes the character to the left of the cursor and moves the cursor back one character. Left arrow key or Ctrl+B Moves the cursor one character to the left. Right arrow key or Ctrl+F Moves the cursor one character to the right. Tab If you press Tab after entering part of a keyword, the system automatically completes the keyword: • If a unique match is found, the system substitutes the complete keyword for the incomplete one and displays what you entered in the next line. • If there is more than one match, you can press Tab repeatedly to choose the keyword you want to enter. • If there is no match, the system does not modify what you entered but displays it again in the next line. Entering a STRING type value for an argument Generally, a STRING type argument value can contai n any printable character (in the ASCII code range of 32 to 126) other than the question mark (?), quotation mark (), backward slash (\), and space. However, a specific STRING type argument might have more strict requirements. For example, the domain name is of the STRING type. Invalid characters for it include the vertical bar (|), slash (/), colon ( : ) , as te ri s k ( * ) , l e ss - t h a n s ig n ( < ) , g re a te r- th a n s ig n ( > ) , a n d a t s ig n ( @ ) , as we l l as t h e qu es t io n m a rk ( ? ) , quotation mark (), backward slash (\), and space. For more information about the specific requirements for a STRING type argument, see the relevant command reference. system-view [Sysname] domain ?
6 STRING Domain name Abbreviating commands You can enter a command line quickly by entering incomplete keywords that can uniquely identify the complete command. In user view, for example, commands starting with an s include startup saved-configuration and system-view. To enter system view, you only need to enter sy. To set the configuration file to be used at the next startup, you can enter st s. You can also press Tab to have an incomplete keyword automatically completed. Configuring and using command keyword aliases The command keyword alias function allows you to replace the first keyword of a non-undo command or the second keyword of an undo command with your preferred keyword when you execute the command. For example, if you configure show as the alias for the display keyword, you can enter show to execute a display command. Usage guidelines • After you successfully execute a command by using a keyword alias, the system saves the keyword, instead of its alias, to the running configuration. • If you press Tab after entering part of an alias, the keyword is displayed. • If a string you entered partially matches a keyword and an alias, the command indicated by the alias is executed. To execute the command indicated by the keyword, enter the complete keyword. • If a string you entered exactly matches a keyword but partially matches an alias, the command indicated by the keyword is executed. To execute the command indicated by the alias, enter the complete alias. • If you enter a string that partially matches multiple aliases, the system gives you a prompt. Configuration procedure To configure a command keyword alias: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable the command keyword alias function. command-alias enable By default, the command keyword alias function is disabled. 3. Configure a command keyword alias. command-alias mapping cmdkey alias By default, no command keyword alias is configured. You must enter the cmdkey and alias arguments in their complete form. Configuring and using hotkeys To facilitate CLI operation, the system defines some hotkeys and provides five configurable command hotkeys. Pressing a command hotkey equals entering a command. For system-reserved hotkeys, see Tabl e 3 . To c o n fig u re ho t keys :
7 Step Command Remarks 1. Enter system view. system-view N/A 2. Configure hotkeys. hotkey { CTRL_G | CTRL_L | CTRL_O | CTRL_T | CTRL_U } command By default: • Ctrl+G is assigned the display current-configuration command. • Ctrl+L is assigned the display ip routing-table command. • Ctrl+O is assigned the undo debugging all command. No command is assigned to Ctrl+T or Ctrl+U. 3. Display hotkeys. display hotkey [ | { begin | exclude | include } regular-expression ] Optional. Available in any view. See Table 3 for hotkeys reserved by the syst em. The hotkeys in Table 3 are defined by the device. If a hotkey is also de fined by the terminal software that you are using to interact with the device, the definition of the terminal software takes effect. Table 3 Hotkeys reserved by the system Hotke y Function Ctrl+A Moves the cursor to the beginning of the line. Ctrl+B Moves the cursor one character to the left. Ctrl+C Stops the current command. Ctrl+D Deletes the character at the cursor. Ctrl+E Moves the cursor to the end of the line. Ctrl+F Moves the cursor one character to the right. Ctrl+H Deletes the character to the left of the cursor. Ctrl+K Aborts the connection request. Ctrl+N Displays the next command in the command history buffer. Ctrl+P Displays the previous command in the command history buffer. Ctrl+R Redisplays the current line. Ctrl+V Pastes text from the clipboard. Ctrl+W Deletes the word to the left of the cursor. Ctrl+X Deletes all characters to the left of the cursor. Ctrl+Y Deletes all characters to the right of the cursor. Ctrl+Z Returns to user view. Ctrl+] Terminates an incoming connection or a redirect connection. Esc+B Moves the cursor back one word. Esc+D Deletes all characters from the cursor to the end of the word. Esc+F Moves the cursor forward one word.
8 Hotkey Function Esc+N Moves the cursor down one line (available before you press Enter) Esc+P Moves the cursor up one line (available before you press Enter) Esc+< Moves the cursor to the beginning of the clipboard. Esc+> Moves the cursor to the ending of the clipboard. Enabling redisplaying entered-but-not-submitted commands After you enable redisplaying entered-but-not-submitted commands: • If you entered nothing at the command-line prompt before the system outputs system information such as logs, the system does not displa y the command-line prompt after the output. • If you entered some information (except Yes or No for confirmation), the system displays a line break and then display what you have entered after the output. To enable redisplaying entered-but-not-submitted commands: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable redisplaying entered-but-not-submitted commands. info-center synchronous By default, the feature is disabled. For more information about this command, see Network Management and Monitoring Command Reference . Understanding command-line error messages If a command line fails the syntax check, the CLI displays error messages. Table 4 Common command-line error messages Error messa ge Cause % Unrecognized command found at ^ position. The keyword in the marked position is invalid. % Incomplete command found at ^ position. One or more required keywords or arguments are missing. % Ambiguous command found at ^ position. The entered character sequence matches more than one command. Too many parameters The entered character sequence contains excessive keywords or arguments. % Wrong parameter found at ^ position. The ar gument in the marked position is invalid.