Management and Configuration Guide Switch 2600 Series Switch 2600-PWR Series Switch 2800 Series Switch 4100 Series Switch 6108 www.hp.
HP ProCurve Switch 2600 Series Switch 2600-PWR Series Switch 2800 Series Switch 4100gl Series Switch 6108 October 2004 Management and Configuration Guide
© Copyright 2000-2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents 1 Getting Started Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 About the Feature Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Using the Menu Interface Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Starting and Ending a Menu Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 How To Start a Menu Interface Session . . . . . . . . . . . . . . . . . . . . . . . . .
Starting an HP Web Browser Interface Session with the Switch . . . . . . . . 5-4 Using a Standalone Web Browser in a PC or UNIX Workstation . . . . 5-4 Using HP ProCurve Manager (PCM) or HP ProCurve Manager Plus (PCM+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Tasks for Your First HP Web Browser Interface Session . . . . . . . . . . . . . . 5-7 Viewing the “First Time Install” Window . . . . . . . . . . . . . . . . . . . . . . . .
Using Primary and Secondary Flash Image Options . . . . . . . . . . . . . . . . . 6-12 Displaying the Current Flash Image Data . . . . . . . . . . . . . . . . . . . . . . 6-12 Switch Software Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 Local Switch Software Replacement and Removal . . . . . . . . . . . . . . 6-15 Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Operating Notes . . . . . . . . . . . . . . . . . . . .
Operating Rules for IP Preserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16 9 Time Protocols Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 TimeP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 SNTP Time Synchronization . . . . . . . . . . . . . .
CLI: Viewing Port Status and Configuring Port Parameters . . . . . . . 10-7 Using the CLI To View Port Status . . . . . . . . . . . . . . . . . . . . . . . . 10-8 Using the CLI To Configure Ports . . . . . . . . . . . . . . . . . . . . . . . . Using the CLI To Configure a Broadcast Limit . . . . . . . . . . . . . . Configuring HP Auto-MDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Auto-MDIX Override on the Series 2600/2600-PWR and 2800 Switches . . . . . . . . . . . . . . . . . . . .
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Applicable Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trunk Configuration Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5 Menu: Viewing and Configuring a Static Trunk Group . . . . . . . . . . . 12-10 CLI: Viewing and Configuring a Static or Dynamic Port Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12 Using the CLI To View Port Trunks . . . . . . . . . . . . . . . . . . . . . . . 12-12 Using the CLI To Configure a Static or Dynamic Trunk Group 12-15 Web: Viewing Existing Port Trunk Groups . . . .
General CDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27 Outgoing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27 Incoming CDP Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28 Configuring CDP on the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31 CLI: Viewing and Configuring CDP . . . . . . . . . . . . . . . . . . . . . . .
Using HP PCM+ to Update Switch Software . . . . . . . . . . . . . . . . . . . A-16 Troubleshooting TFTP Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17 Transferring Switch Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18 Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation . Copying Command Output to a Destination Device . . . . . . . . . Copying Event Log Output to a Destination Device . . . . . . . . .
VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21 Web Browser Interface Status Information . . . . . . . . . . . . . . . . . . . . B-23 Port and Static Trunk Monitoring Features . . . . . . . . . . . . . . . . . . . . . . . B-24 Switch 6108 and Series 4100gl Switches . . . . . . . . . . . . . . . . . . . . . . B-24 Series 2600, 2600-PWR, and 2800 Switches . . . . . . . . . . . . . . . . . . . . B-24 Menu: Configuring Port and Static Trunk Monitoring . .
Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34 Port Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34 Ping and Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-35 Web: Executing Ping or Link Tests . . . . . . . . . . . . . . . . . . . . . . . C-36 CLI: Ping or Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Getting Started Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 About the Feature Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Command Prompts . . . . . . . . . . . . . . . .
Getting Started Introduction Introduction This Management and Configuration Guide is intended to support the following switches: ■ HP ProCurve Series 2600 ■ HP ProCurve Series 2600-PWR ■ HP ProCurve Series 2800 ■ HP ProCurve Series 4100gl ■ HP ProCurve Switch 6108 This guide describes how to use the command line interface (CLI), Menu interface, and web browser interface to configure, manage, and monitor switch operation. A troubleshooting chapter is also included.
Getting Started Conventions Conventions This guide uses the following conventions for command syntax and displayed information. Command Syntax Statements Syntax: aaa port-access authenticator < port-list > [ control < authorized | auto | unauthorized >] ■ Vertical bars ( | ) separate alternative, mutually exclusive elements. ■ Square brackets ( [ ] ) indicate optional elements. ■ Braces ( < > ) enclose required elements.
Getting Started Port Identity Convention for Examples Screen Simulations Figures containing simulated screen text and command output look like this: Figure 1-1. Example of a Figure Showing a Simulated Screen In some cases, brief command-output sequences appear outside of a num bered figure. For example: HPswitch(config)# ip default-gateway 18.28.152.1/24 HPswitch(config)# vlan 1 ip address 18.28.36.
Getting Started Related Publications Advanced Traffic Management Guide. Use the Advanced Traffic Man agement Guide for information on: ■ VLANs: Static port-based and protocol VLANs, and dynamic GVRP VLANs ■ Multicast traffic control (IGMP) ■ Spanning-Tree: 802.1D (STP), 802.1w (RSTP), and 802.1s (MSTP) ■ Quality-of-Service (QoS) ■ IP routing Access Security Guide.
Getting Started Getting Documentation From the Web Getting Documentation From the Web 1. Go to the HP ProCurve website at http://www.hp.com/go/hpprocurve 2 2. Click on technical support. 3. Click on manuals. 4. Click on the product for which you want to view or download a manual. 3 4 Figure 1-2.
Getting Started Sources for More Information Sources for More Information ■ If you need information on specific parameters in the menu interface, refer to the online help provided in the interface. For example: Online Help for Menu Figure 1-3. Getting Help in the Menu Interface ■ If you need information on a specific command in the CLI, type the command name followed by “help”. For example: Figure 1-4.
Getting Started Need Only a Quick Start? Need Only a Quick Start? IP Addressing If you just want to give the switch an IP address so that it can communicate on your network, or if you are not using VLANs, HP recommends that you use the Switch Setup screen to quickly configure IP addressing. To do so, do one of the following: ■ Enter setup at the CLI Manager level prompt. HPswitch# setup ■ In the Main Menu of the Menu interface, select 8.
2 Selecting a Management Interface Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Understanding Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Advantages of Using the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Advantages of Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Management Interface Overview Overview This chapter describes the following: ■ Switch management interfaces ■ Advantages of using each interface type Understanding Management Interfaces Management interfaces enable you to reconfigure the switch and to monitor switch status and performance.
Selecting a Management Interface Advantages of Using the Menu Interface To use HP ProCurve Manager or HP ProCurve Manager Plus, refer to the Getting Started Guide and the Administrator’s Guide, which are available electronically with the software for these applications. For more information, visit the HP ProCurve web site at http://www.hp.com/go/hpprocurve. Advantages of Using the Menu Interface Figure 2-1.
Selecting a Management Interface Advantages of Using the CLI ■ Offers out-of-band access (through the RS-232 connection) to the switch, so network bottlenecks, crashes, lack of configured or correct IP address, and network downtime do not slow or prevent access ■ Enables Telnet (in-band) access to the menu functionality. ■ Allows faster navigation, avoiding delays that occur with slower display of graphical objects over a web browser interface.
Selecting a Management Interface Advantages of Using the HP Web Browser Interface ■ For information on individual CLI commands, refer to the Index or to the online Help provided in the CLI interface. Advantages of Using the HP Web Browser Interface Figure 2-3.
Selecting a Management Interface Advantages of Using HP ProCurve Manager or HP ProCurve Manager Plus ■ Display of acceptable ranges of values available in configuration list boxes Advantages of Using HP ProCurve Manager or HP ProCurve Manager Plus You can operate HP ProCurve Manager and HP ProCurve Manager Plus (PCM and PCM+) from a PC on the network to monitor traffic, manage your hubs and switches, and proactively recommend network changes to increase network uptime and optimize performance.
Selecting a Management Interface Advantages of Using HP ProCurve Manager or HP ProCurve Manager Plus PCM and PCM+ enable greater control, uptime, and performance in your network: ■ ■ Features and benefits of HP ProCurve Manager: • Network Status Summary: Upon boot-up, a network status screen displays high-level information on network devices, end nodes, events, and traffic levels. From here, users can research any one of these areas to get more details.
Selecting a Management Interface Advantages of Using HP ProCurve Manager or HP ProCurve Manager Plus 2-8 • Device Software Updates: This feature automatically obtains new device software images from HP and updates devices, allowing users to download the latest version or choose the desired version. Updates can be scheduled easily across large groups of devices, all at userspecified times.
3 Using the Menu Interface Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Starting and Ending a Menu Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 How To Start a Menu Interface Session . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 How To End a Menu Session and Exit from the Console: . . . . . . . . . . 3-5 Main Menu Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Menu Interface Overview Overview This chapter describes the following: ■ Overview of the Menu Interface ■ Starting and ending a Menu session (page 3-3)) ■ The Main Menu (page 3-7)) ■ Screen structure and navigation (page 3-9)) ■ Rebooting the switch (page 3-12)) The menu interface operates through the switch console to provide you with a subset of switch commands in an easy-to-use menu format enabling you to: ■ Perform a “quick configuration” of basic parameters, such as the IP address
Using the Menu Interface Starting and Ending a Menu Session Note If the switch has neither a Manager nor an Operator password, anyone having access to the console interface can operate the console with full manager privileges. Also, if you configure only an Operator password, entering the Operator password enables full manager privileges. For more information on passwords, see the chapter on local passwords in the Access Security Guide for your switch.
Using the Menu Interface Starting and Ending a Menu Session How To Start a Menu Interface Session In its factory default configuration, the switch console starts with the CLI prompt. To use the menu interface with Manager privileges, go to the Manager level prompt and enter the menu command. 1. Use one of these methods to connect to the switch: • A PC terminal emulator or terminal • Telnet (You can also use the stack Commander if the switch is a stack member. See ). 2. 3.
Using the Menu Interface Starting and Ending a Menu Session Figure 3-1. The Main Menu with Manager Privileges For a description of Main Menu features, see “Main Menu Features” on page 3-7). Note To configure the switch to start with the menu interface instead of the CLI, go to the Manager level prompt in the CLI, enter the setup command, and in the resulting display, change the Logon Default parameter to Menu.
Using the Menu Interface Starting and Ending a Menu Session Asterisk indicates a configuration change that requires a reboot to activate. Figure 3-2. An Asterisk Indicates a Configuration Change Requiring a Reboot 1. In the current session, if you have not made configuration changes that require a switch reboot to activate, return to the Main Menu and press [0] (zero) to log out. Then just exit from the terminal program, turn off the terminal, or quit the Telnet session. 2.
Using the Menu Interface Main Menu Features Main Menu Features Figure 3-3. The Main Menu View with Manager Privileges The Main Menu gives you access to these Menu interface features: ■ Status and Counters: Provides access to display screens showing switch information, port status and counters, port and VLAN address tables, and spanning tree information. (See Appendix B, “Monitoring and Analyzing Switch Operation”.
Using the Menu Interface Main Menu Features 3-8 ■ Command Line (CLI): Selects the Command Line Interface at the same level (Manager or Operator) that you are accessing in the Menu interface. (See chapter 4, “Using the Command Line Interface (CLI)”.) ■ Reboot Switch: Performs a “warm” reboot of the switch, which clears most temporary error conditions, resets the network activity counters to zero, and resets the system up-time to zero.
Using the Menu Interface Screen Structure and Navigation Screen Structure and Navigation Menu interface screens include these three elements: ■ Parameter fields and/or read-only information such as statistics ■ Navigation and configuration actions, such as Save, Edit, and Cancel ■ Help line to describe navigation options, individual parameters, and readonly data For example, in the following System Information screen: Screen title – identifies the location within the menu structure Parameter fields
Using the Menu Interface Screen Structure and Navigation Table 3-1. 3-10 How To Navigate in the Menu Interface Task: Actions: Execute an action from the “Actions –>” list at the bottom of the screen: Use either of the following methods: • Use the arrow keys ([<] or [>]) to highlight the action you want to execute, then press [Enter]. • Press the key corresponding to the capital letter in the action name.
Using the Menu Interface Screen Structure and Navigation To get Help on individual parameter descriptions. In most screens there is a Help option in the Actions line. Whenever any of the items in the Actions line is highlighted, press [H], and a separate help screen is displayed. For example: Pressing [H] or highlighting Help and pressing [Enter] displays Help for the parameters listed in the upper part of the screen Highlight on any item in the Actions line indicates that the Actions line is active.
Using the Menu Interface Rebooting the Switch Rebooting the Switch Rebooting the switch from the menu interface ■ Terminates all current sessions and performs a reset of the operating system ■ Activates any menu interface configuration changes that require a reboot ■ Resets statistical counters to zero (Note that statistical counters can be reset to zero without rebooting the switch.) To Reboot the switch, use the Reboot Switch option in the Main Menu.
Using the Menu Interface Rebooting the Switch Rebooting To Activate Configuration Changes. Configuration changes for most parameters in the menu interface become effective as soon as you save them. However, you must reboot the switch in order to implement a change in the Maximum VLANs to support parameter. (To access this parameter, go to the Main Menu and select: 2. Switch Configuration 8. VLAN Menu 1. VLAN Support.
Using the Menu Interface Menu Features List Menu Features List Status and Counters • General System Information • Switch Management Address Information • Port Status • Port Counters • Address Table • Port Address Table • Spanning Tree Information Switch Configuration • System Information • Port/Trunk Settings • Network Monitoring Port • Spanning Tree Operation • IP Configuration • SNMP Community Names • IP authorized Managers • VLAN Menu Console Passwords Event Log Command Lin
Using the Menu Interface Where To Go From Here Where To Go From Here This chapter provides an overview of the menu interface and how to use it. The following table indicates where to turn for detailed information on how to use the individual features available through the menu interface. Option: Turn to: To use the Run Setup option Refer to the Installation and Getting Started Guide shipped with the switch.
Using the Menu Interface Where To Go From Here — This page is intentionally unused.
4 Using the Command Line Interface (CLI) Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Privilege Levels at Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Command Line Interface (CLI) Overview Overview The CLI is a text-based command interface for configuring and monitoring the switch. The CLI gives you access to the switch’s full set of commands while providing the same password protection that is used in the web browser interface and the menu interface. Accessing the CLI Like the menu interface, the CLI is accessed through the switch console, and, in the switch’s factory default state, is the default interface when you start a console session.
Using the Command Line Interface (CLI) Using the CLI Startup Config file in non-volatile memory. If you reboot the switch without first using write memory, all changes made since the last reboot or write memory (whichever is later) will be lost. For more on switch memory and saving configuration changes, see Chapter 6, “Switch Memory and Configuration”. Privilege Levels at Logon Privilege levels control the type of access to the CLI. To implement this control, you must set at least a Manager password.
Using the Command Line Interface (CLI) Using the CLI Caution HP strongly recommends that you configure a Manager password. If a Man ager password is not configured, then the Manager level is not passwordprotected, and anyone having in-band or out-of-band access to the switch may be able to reach the Manager level and compromise switch and network security. Note that configuring only an Operator password does not prevent access to the Manager level by intruders who have the Operator password.
Using the Command Line Interface (CLI) Using the CLI Manager Privileges Manager privileges give you three additional levels of access: Manager, Global Configuration, and Context Configuration. (See figure .) A "#" character delimits any Manager prompt. For example: HPswitch#_ ■ Example of the Manager prompt. Manager level: Provides all Operator level privileges plus the ability to perform system-level actions that do not require saving changes to the system configuration file.
Using the Command Line Interface (CLI) Using the CLI Changing Interfaces. If you change from the CLI to the menu interface, or the reverse, you will remain at the same privilege level. For example, entering the menu command from the Operator level of the CLI takes you to the Operator privilege level in the menu interface. Table 4-1.
Using the Command Line Interface (CLI) Using the CLI How To Move Between Levels Change in Levels Example of Prompt, Command, and Result Operator level to Manager level HPswitch> enable Password:_ After you enter enable, the Password prompt appears.
Using the Command Line Interface (CLI) Using the CLI For example, if you use the menu interface to configure an IP address of “X” for VLAN 1 and later use the CLI to configure a different IP address of “Y” for VLAN 1, then “Y” replaces “X” as the IP address for VLAN 1 in the running config file. If you subsequently execute write memory in the CLI, then the switch also stores “Y” as the IP address for VLAN 1 in the startup-config file.
Using the Command Line Interface (CLI) Using the CLI Typing ? at the Manager level produces this listing: When - - MORE - - appears, use the Space bar or [Return] to list additional commands. Figure 4-4. Example of the Manager-Level Command Listing When - - MORE - - appears, there are more commands in the listing. To list the next set of commands, press the Space bar. To list the remaining commands one-by-one, repeatedly press [Enter].
Using the Command Line Interface (CLI) Using the CLI telnet terminal HPswitch(config)# t As mentioned above, if you type part of a command word and press [Tab], the CLI completes the current word (if you have typed enough of the word for the CLI to distinguish it from other possibilities), including hyphenated exten sions. For example: HPswitch(config)# port [Tab] HPswitch(config)# port-security _ Pressing [Tab] after a completed command word lists the further options for that command.
Using the Command Line Interface (CLI) Using the CLI Listing Command Options. You can use the CLI to remind you of the options available for a command by entering command keywords followed by?. For example, suppose you want to see the command options for config uring port C5: This example displays the command options for configuring the switch’s console settings. Figure 4-5.
Using the Command Line Interface (CLI) Using the CLI Figure 4-6. Example of Context-Sensitive Command-List Help Displaying Help for an Individual Command. You can display Help for any command that is available at the current context level by entering enough of the command string to identify the command, along with help. Syntax: < command-string > help For example, to list the Help for the interface command in the Global Configuration privilege level: Figure 4-7.
Using the Command Line Interface (CLI) Using the CLI Figure 4-8. Example of Help for a Specific Instance of a Command Note that trying to list the help for an individual command from a privilege level that does not include that command results in an error message.
Using the Command Line Interface (CLI) Using the CLI HPswitch(eth-C5-C8)#? HPswitch(eth-C5-C8)#? Lists the commands you can use in the port or static trunk context, plus the Manager, Operator, and context commands you can execute at this level. In the port context, the first block of commands in the "?" listing show the context-specific commands that will affect only ports C3-C6. The remaining commands in the listing are Manager, Operator, and context commands. Figure 4-9.
Using the Command Line Interface (CLI) Using the CLI VLAN Context . Includes VLAN-specific commands that apply only to the selected VLAN, plus Manager and Operator commands. The prompt for this mode includes the VLAN ID of the selected VLAN. For example, if you had already configured a VLAN with an ID of 100 in the switch: HPswitch(config)# vlan 100 Command executed at configura tion level to enter VLAN 100 context. HPswitch(vlan-100)# Resulting prompt showing VLAN 100 context.
Using the Command Line Interface (CLI) CLI Control and Editing CLI Control and Editing 4-16 Keystrokes Function [Ctrl] [A] Jumps to the first character of the command line. [Ctrl] [B] or [<] Moves the cursor back one character. [Ctrl] [C] Terminates a task and displays the command prompt. [Ctrl] [D] Deletes the character at the cursor. [Ctrl] [E] Jumps to the end of the current command line. [Ctrl] [F] or [>] Moves the cursor forward one character.
5 Using the HP Web Browser Interface Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting an HP Web Browser Interface Session with the Switch . . . . . . . . 5-4 Using a Standalone Web Browser in a PC or UNIX Workstation . . . . 5-4 Using HP ProCurve Manager (PCM) or HP ProCurve Manager Plus (PCM+) . . . . . .
Using the HP Web Browser Interface Overview Overview The HP web browser interface built into the switch lets you easily access the switch from a browser-based PC on your network. This lets you do the following: ■ Optimize your network uptime by using the Alert Log and other diagnostic tools ■ Make configuration changes to the switch ■ Maintain security by configuring usernames and passwords This chapter covers the following: ■ General features (page 5-3).
Using the HP Web Browser Interface General Features General Features The switch includes these web browser interface features: Switch Configuration: • Ports • VLANs and Primary VLAN • Fault detection • Port monitoring (mirroring) • System information • Enable/Disable Multicast Filtering (IGMP) and Spanning Tree • IP • Stacking • Support and management URLs Switch Security: Usernames and passwords Switch Diagnostics: • Ping/Link Test • Device reset • Configuration report Switch statu
Using the HP Web Browser Interface Starting an HP Web Browser Interface Session with the Switch Starting an HP Web Browser Interface Session with the Switch You can start a web browser session in the following ways: ■ ■ Using a standalone web browser on a network connection from a PC or UNIX workstation: • Directly connected to your network • Connected through remote access to your network Using a management station running HP ProCurve Manager on your network Using a Standalone Web Browser in a PC o
Using the HP Web Browser Interface Starting an HP Web Browser Interface Session with the Switch Using HP ProCurve Manager (PCM) or HP ProCurve Manager Plus (PCM+) HP ProCurve Manager and HP ProCurve Manager Plus are designed for installation on a network management workstation. For this reason, the system requirements are different from the system requirements for accessing the switch’s web browser interface from a non-management PC or worksta tion.
Using the HP Web Browser Interface Starting an HP Web Browser Interface Session with the Switch Alert Log First-Time Install Alert Figure 5-1. Example of Status Overview Screen Note 5-6 The above screen appears somewhat different if the switch is configured as a stack Commander. For an example, see figure 2-3 on page 2-5.
Using the HP Web Browser Interface Tasks for Your First HP Web Browser Interface Session Tasks for Your First HP Web Browser Interface Session The first time you access the web browser interface, there are three tasks that you should perform: ■ Review the “First Time Install” window ■ Set Manager and Operator passwords ■ Set access to the web browser interface online help Viewing the “First Time Install” Window When you access the switch’s web browser interface for the first time, the Alert log conta
Using the HP Web Browser Interface Tasks for Your First HP Web Browser Interface Session This window is the launching point for the basic configuration you need to perform to set web browser interface passwords to maintain security and Fault Detection policy, which determines the types of messages that will be displayed in the Alert Log. To set web browser interface passwords, click on secure access to the device to display the Device Passwords screen, and then go to the next page.
Using the HP Web Browser Interface Tasks for Your First HP Web Browser Interface Session Figure 5-3. The Device Passwords Window To set the passwords: 1. 2. Access the Device Passwords screen by one of the following methods: • If the Alert Log includes a “First Time Install” event entry, double click on this event, then, in the resulting display, click on the secure access to the device link. • Select the Security tab.
Using the HP Web Browser Interface Tasks for Your First HP Web Browser Interface Session Note Passwords you assign in the web browser interface will overwrite previous passwords assigned in either the web browser interface, the Command Prompt, or the switch console. That is, the most recently assigned passwords are the switch’s passwords, regardless of which interface was used to assign the string. Using the Passwords Figure 5-4.
Using the HP Web Browser Interface Tasks for Your First HP Web Browser Interface Session If You Lose a Password If you lose the passwords, you can clear them by pressing the Clear button on the front of the switch. This action deletes all password and user name protection from all of the switch’s interfaces.
Using the HP Web Browser Interface Support/Mgmt URLs Feature Support/Mgmt URLs Feature The Support/Mgmt URLs window enables you to change the World Wide Web Universal Resource Locator (URL) for two functions: ■ Support URL – a support information site for your switch ■ Management Server URL – The web site for web browser online Help. 1. Click Here 2. Click Here 3.
Using the HP Web Browser Interface Support/Mgmt URLs Feature Support URL This is the site that the switch accesses when you click on the Support tab on the web browser interface. The default URL is: http://www.hp.com/go/procurve which is the World Wide Web site for Hewlett-Packard’s networking products. Click on the [Support] button on that page and you can get to support informa tion regarding your switch, including white papers, operating system (OS) updates, and more.
Using the HP Web Browser Interface Support/Mgmt URLs Feature In the default configuration, the switch uses the URL for accessing the web browser interface help files on the HP ProCurve World Wide Web site. Figure 5-7.
Using the HP Web Browser Interface Status Reporting Features Status Reporting Features Browser elements covered in this section include: ■ The Overview window (below) ■ Port utilization and status (page 5-16) ■ The Alert log (page 5-19) ■ The Status bar (page 5-22) The Overview Window The Overview Window is the home screen for any entry into the web browser interface.The following figure identifies the various parts of the screen.
Using the HP Web Browser Interface Status Reporting Features The Port Utilization and Status Displays The Port Utilization and Status displays show an overview of the status of the switch and the amount of network activity on each port. The following figure shows a sample reading of the Port Utilization and Port Status. Port Utilization Bar Graphs Bandwidth Display Control Port Status Indicators Legend Figure 5-9.
Using the HP Web Browser Interface Status Reporting Features ■ Maximum Activity Indicator: As the bars in the graph area change height to reflect the level of network activity on the corresponding port, they leave an outline to identify the maximum activity level that has been observed on the port. Utilization Guideline. A network utilization of 40% is considered the maximum that a typical Ethernet-type network can experience before encoun tering performance difficulties.
Using the HP Web Browser Interface Status Reporting Features Port Status Port Status Indicators Legend Figure 5-12. The Port Status Indicators and Legend The Port Status indicators show a symbol for each port that indicates the general status of the port. There are four possible statuses: 5-18 ■ Port Connected – the port is enabled and is properly connected to an active network device. ■ Port Not Connected – the port is enabled but is not connected to an active network device.
Using the HP Web Browser Interface Status Reporting Features The Alert Log The web browser interface Alert Log, shown in the lower half of the screen, shows a list of network occurrences, or alerts, that were detected by the switch. Typical alerts are Broadcast Storm, indicating an excessive number of broadcasts received on a port, and Problem Cable, indicating a faulty cable. For more information on alerts, see “Alert Types and Detailed Views” on page 5-20 Figure 5-13.
Using the HP Web Browser Interface Status Reporting Features Alert Types and Detailed Views As of April, 2004, the web browser interface generates the following alert types: • • • • • • • • • Note Auto Partition Backup Transition Excessive broadcasts Excessive CRC/alignment errors Excessive jabbering Excessive late collisions First Time Install Full-Duplex Mismatch Half-Duplex Mismatch • • • • • • • • High collision or drop rate Loss of Link Mis-Configured SQE Network Loop Polarity Reversal Security Vi
Using the HP Web Browser Interface Status Reporting Features Figure 5-14.
Using the HP Web Browser Interface Status Reporting Features The Status Bar The Status Bar is displayed in the upper left corner of the web browser interface screen. Figure 5-15 shows an expanded view of the status bar. Status Indicator Most Critical Alert Description Product Name Figure 5-15. Example of the Status Bar The Status bar consists of four objects: ■ Status Indicator. Indicates, by icon, the severity of the most critical alert in the current display of the Alert Log.
Using the HP Web Browser Interface Status Reporting Features ■ Product Name. The product name of the switch to which you are connected in the current web browser interface session. Setting Fault Detection Policy One of the powerful features in the web browser interface is the Fault Detection facility. For your switch, this feature controls the types of alerts reported to the Alert Log based on their level of severity. Set this policy in the Fault Detection window (figure 5-16). Figure 5-16.
Using the HP Web Browser Interface Status Reporting Features ■ High Sensitivity. This policy directs the switch to send all alerts to the Alert Log. This setting is most effective on networks that have none or few problems. ■ Medium Sensitivity. This policy directs the switch to send alerts related to network problems to the Alert Log. If you want to be notified of problems which cause a noticeable slowdown on the network, use this setting. ■ Low Sensitivity.
6 Switch Memory and Configuration Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Overview of Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Using the CLI To Implement Configuration Changes . . . . . . . . . . . . . . . . . 6-5 Using the Menu and Web Browser Interfaces To Implement Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Memory and Configuration Overview Overview This chapter describes: ■ How switch memory manages configuration changes ■ How the CLI implements configuration changes ■ How the menu interface and web browser interface implement configu ration changes ■ How the switch provides software options through primary/secondary flash image options ■ How to use the switch’s primary and secondary flash options, including displaying flash information, booting or restarting the switch, and other topics Ov
Switch Memory and Configuration Overview of Configuration File Management ■ Running Config File: Exists in volatile memory and controls switch operation. If no configuration changes have been made in the CLI since the switch was last booted, the running-config file is identical to the startup-config file. ■ Startup-config File: Exists in flash (non-volatile) memory and is used to preserve the most recently-saved configuration as the "permanent" configuration.
Switch Memory and Configuration Overview of Configuration File Management “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: HPswitch(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.
Switch Memory and Configuration Using the CLI To Implement Configuration Changes 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 perma nent 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.
Switch Memory and Configuration Using the CLI To Implement Configuration Changes 3. Observe the switch’s performance with the new parameter settings to verify the effect of your changes. 4. When you are satisfied that you have the correct parameter settings, use the write memory command to copy the changes to the startup-config file. Syntax: write memory For example, the default port mode setting is auto.
Switch Memory and Configuration Using the CLI To Implement Configuration Changes Disables port 1 in the running configuration, which causes port 1 to block all traffic. HPswitch(config)# interface e 1 disable HPswitch(config)# boot Device will be rebooted, do you want to continue [y/n]? y Press [Y] to continue the rebooting process. You will then see this prompt. Do you want to save current configuration [y/n]? Figure 6-2.
Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes 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.
Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes Note The only exception to this operation are two VLAN-related parameter changes that require a reboot—described under “Rebooting To Activate Configuration Changes” on page 6-11. Using Save and Cancel in the Menu Interface For any configuration screen in the menu interface, the Save command: 1. Implements the changes in the running-config file. 2. Saves your changes to the startup-config file.
Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes Note If you reconfigure a parameter in the CLI and then go to the menu interface without executing a write memory command, those changes are stored only in the running configuration. If you then execute a switch reboot command in the menu interface, the switch discards the configuration changes made while using the CLI.
Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes Rebooting To Activate Configuration Changes. Configuration changes for most parameters become effective as soon as you save them. However, you must reboot the switch in order to implement a change in the Maximum VLANs to support parameter. (To access these parameters, go to the Main menu and select 2. Switch Configuration, then 8. VLAN Menu, then 1. VLAN Support.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Using Primary and Secondary Flash Image Options The switch features two flash memory locations for storing switch software image files: ■ Primary Flash: The default storage for a switch software image. ■ Secondary Flash: The additional storage for either a redundant or an alternate switch software image.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, if the switch is using a software version of G.01.01 stored in Primary flash, show version produces the following: Figure 6-7. Example Showing the Identity of the Current Flash Image Determining Whether the Flash Images Are Different Versions. If the flash image sizes in primary and secondary are the same, then in almost every case, the primary and secondary images are identical.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options 1. In this example show version indicates the switch has version G.05.01 in primary flash. 2. After the boot system command, show version indicates that version G.05.00 is in secondary flash. Figure 6-9.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Local Switch Software Replacement and Removal This section describes commands for erasing a software version and copying an existing software version between primary and secondary flash. Note It is not necessary to erase the content of a flash location before downloading another software file. The process automatically overwrites the previous file with the new file.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options 1. Verify that there is a valid flash image in the secondary flash location. The following figure indicates that a software image is present in secondary flash. (If you are unsure whether the image is secondary flash is valid, try booting from it before you proceed, by using boot system flash secondary.) The unequal code size, differing dates, and differing version numbers indicates two different versions of the software.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options The prompt shows which flash location will be erased. Figure 6-11. Example of Erase Flash Prompt 3. Type y at the prompt to complete the flash erase. 4. Use show flash to verify erasure of the selected software flash image The "0" here shows that primary flash has been erased. Figure 6-12.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Booting from Primary Flash. This command always boots the switch from primary flash, and executes the complete set of subsystem self-tests. Syntax: boot For example, to boot the switch from primary flash with pending configuration changes in the running-config file: Figure 6-13. Example of Boot Command (Default Primary Flash) In the above example, typing either a y or n at the second prompt initiates the reboot operation.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Booting from the Current Software Version. Reload reboots the switch from the flash image on which the switch is currently running, and saves to the startup-config file any configuration changes currently in the running config file. Because reload bypasses some subsystem self-tests, the switch reboots faster than if you use either of the boot command options.
Switch Memory and Configuration Using Primary and Secondary Flash Image Options — This page is intentionally unused.
7 Interface Access and System Information Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Interface Access: Console/Serial Link, Web, and Telnet . . . . . . . . . . . . . . . 7-3 Menu: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 CLI: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Access and System Information Overview Overview This chapter describes how to: ■ View and modify the configuration for switch interface access ■ Use the CLI kill command to terminate a remote session ■ View and modify switch system information For help on how to actually use the interfaces built into the switch, refer to: ■ Chapter 2, “Using the Menu Interface” ■ Chapter 4, “Using the Command Line Interface (CLI)” ■ Chapter 5, Using the HP Web Browser Interface” Why Configure Interfac
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Interface Access: Console/Serial Link, Web, and Telnet Interface Access Features Feature Inactivity Time Inbound Telnet Access Outbound Telnet Access Web Browser Interface Access Terminal type Event Log event types to list (Displayed Events) Baud Rate Flow Control Default Menu CLI Web 0 Minutes (disabled) page 7-4 page 7-6 — Enabled page 7-4 page 7-5 — n/a — page 7-6 — Enabled page 7-4 page 7-6
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Menu: Modifying the Interface Access The menu interface enables you to modify these parameters: ■ Inactivity Time-out ■ Inbound Telnet Enabled ■ Web Agent Enabled To Access the Interface Access Parameters: 1. From the Main Menu, Select... 2. Switch Configuration... 1. System Information Interface Access Parameters Figure 7-1. The Default Interface Access Parameters Available in the Menu Interface 2.
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet CLI: Modifying the Interface Access Interface Access Commands Used in This Section show console below [no] telnet-server below [no] web-management page 7-6 console page 7-6 Listing the Current Console/Serial Link Configuration. This com mand lists the current interface access parameter settings. Syntax: show console This example shows the switch’s default console/serial configuration.
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Outbound Telnet to Another Device. This feature operates indepen dently of the telnet-server status and enables you to Telnet to another device that has an IP address. Syntax: telnet < ip-address > For example: HPswitch # telnet 10.28.27.204 Reconfigure Web Browser Access. In the default configuration, web browser access is enabled.
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet For example, to use one command to configure the switch with the following: ■ VT100 operation ■ 19,200 baud ■ No flow control ■ 10-minute inactivity time ■ Critical log events you would use the following command sequence: The switch implements the Event Log change immediately. The switch implements the other console changes after executing write memory and reload. Figure 7-3.
Interface Access and System Information Denying Interface Access by Terminating Remote Management Sessions Denying Interface Access by Terminating Remote Management Sessions The switch supports up to four management sessions. You can use show ip ssh to list the current management sessions, and kill to terminate a currently running remote session. (Kill does not terminate a Console session on the serial port, either through a direct connection or via a modem.
Interface Access and System Information System Information System Information System Information Features Feature Default Menu CLI Web System Name switch product name page 7-10 page 7-12 page 7-14 System Contact n/a page 7-10 page 7-12 page 7-14 System Location n/a page 7-10 page 7-12 page 7-14 MAC Age Time 300 seconds page 7-10 page 7-13 — Time Sync Method None See Chapter 9, “Time Protocols”.
Interface Access and System Information System Information Time Zone: The number of minutes your time zone location is to the West (-) or East (+) of Coordinated Universal Time (formerly GMT). The default 0 means no time zone is configured. For example, Berlin, Germany is in the +1 zone, while Vancouver, Canada is in the -8 zone. Daylight Time Rule: Specifies the daylight savings time rule to apply for your location. The default is None.
Interface Access and System Information System Information 3. 4. Refer to the online help provided with this screen for further information on configuration options for these features. When you have finished making changes to the above parameters, press [Enter], then press [S] (for Save) and return to the Main Menu.
Interface Access and System Information System Information Configure a System Name, Contact, and Location for the Switch. To help distinguish one switch from another, configure a plain-language identity for the switch. Syntax: hostname snmp-server [contact ] [location ] Both fields allow up to 48 characters. Blank spaces are not allowed in the variables for these commands.
Interface Access and System Information System Information Reconfigure the Age Time for Learned MAC Addresses. This com mand corresponds to the MAC Age Interval in the menu interface, and is expressed in seconds. Syntax: mac-age-time <10 . . 1000000> (seconds) For example, to configure the age time to seven minutes: HPswitch(config)# mac-age-time 420 Configure the Time Zone and Daylight Time Rule.
Interface Access and System Information System Information Web: Configuring System Parameters In the web browser interface, you can enter the following system information: ■ System Name ■ System Location ■ System Contact For access to the MAC Age Interval and the Time parameters, use the menu interface or the CLI. Configure System Parameters in the Web Browser Interface. 1. Click on the Configuration tab. 2. Click on System Info. 3. Enter the data you want in the displayed fields. 4.
8 Configuring IP Addressing Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Just Want a Quick Start with IP Addressing? . . . . . . . . . . . . . . . . . . . . 8-4 IP Addressing with Multiple VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 IP Addressing in a Stacking Environment . . . . . . . .
Configuring IP Addressing Overview Overview You can configure IP addressing through all of the switch’s interfaces. You can also: ■ Easily edit a switch configuration file to allow downloading the file to multiple switches without overwriting each switch’s unique gateway and VLAN 1 IP addressing.
Configuring IP Addressing IP Configuration IP Configuration IP Configuration Features Feature IP Address and Subnet Mask Multiple IP Addresses on a VLAN Default Menu CLI Web DHCP/Bootp page 8-5 page 8-7 page 8-11 n/a page 8-9 Default Gateway Address none page 8-5 page 8-7 page 8-11 Packet Time-To-Live (TTL) 64 seconds page 8-5 page 8-7 n/a DHCP page 8-5 page 8-7 n/a Time Server (Timep) IP Address and Subnet Mask.
Configuring IP Addressing IP Configuration then the switch uses this gateway, even if a different gateway is received via DHCP or Bootp on the primary VLAN. (This is also true for TimeP and a nondefault Time-To-Live.) See “Notes” on page 8-4 and refer to the chapter on Virtual LANs in the Advanced Traffic Management Guide. Packet Time-To-Live (TTL) . This parameter specifies how long in sec onds an outgoing packet should exist in the network. In most cases, the default setting (64 seconds) is adequate.
Configuring IP Addressing IP Configuration ■ The IP addressing used in the switch should be compatible with your network. That is, the IP address must be unique and the subnet mask must be appropriate for your IP network. ■ If you change the IP address through either Telnet access or the web browser interface, the connection to the switch will be lost. You can reconnect by either restarting Telnet with the new IP address or entering the new address as the URL in your web browser.
Configuring IP Addressing IP Configuration For descriptions of these parameters, see the online Help for this screen. Before using the DHCP/ Bootp option, refer to “DHCP/Bootp Operation” on page 8-12. Figure 8-1. Example of the IP Service Configuration Screen without Multiple VLANs Configured 8-6 2. Press [E] (for Edit). 3. If the switch needs to access a router, for example, to reach off-subnet destinations, select the Default Gateway field and enter the IP address of the gateway router. 4.
Configuring IP Addressing IP Configuration CLI: Configuring IP Address, Gateway, and Time-ToLive (TTL) IP Commands Used in This Section show ip page 8-7 vlan ip address page 8-8 ip default-gateway page 8-11 ip ttl page 8-11 Viewing the Current IP Configuration. The following command displays the IP addressing for each VLAN configured in the switch. If only the DEFAULT_VLAN exists, then its IP configuration applies to all ports in the switch.
Configuring IP Addressing IP Configuration Figure 8-3. Example of Show IP Listing with Non-Default IP Addressing Configured Configure an IP Address and Subnet Mask. The following command includes both the IP address and the subnet mask. You must either include the ID of the VLAN for which you are configuring IP addressing or go to the context configuration level for that VLAN. (If you are not using VLANs on the switch—that is, if the only VLAN is the default VLAN—then the VLAN ID is always “1”.
Configuring IP Addressing IP Configuration Configure Multiple IP Addresses on a VLAN (Multinetting). You can configure one primary IP address per VLAN and up to seven secondary IP addresses for the same VLAN. That is, the switch enables you to assign up to eight networks to a VLAN. ■ Each IP address on a VLAN must be for a separate subnet. ■ The switch assigns the first IP address manually configured on a VLAN as the primary IP address.
Configuring IP Addressing IP Configuration If you then wanted to multinet the default VLAN, you would do the following: The secondary IP addresses in a VLAN are listed immediately after the primary IP address for the VLAN. Figure 8-5. Example of Multinetting on the Default VLAN Note The Internet (IP) Service screen in the Menu interface (figure 8-1 on page 8-6) displays only the primary IP address for each VLAN.
Configuring IP Addressing IP Configuration Configure the Optional Default Gateway. Using the Global configura tion level, you can assign one default gateway to the switch. Syntax: ip default-gateway For example: HPswitch(config)# ip default-gateway 10.28.227.115 Note The switch uses the IP default gateway only while operating as a Layer 2 device. While routing is enabled on the switch, the IP default gateway is not used.
Configuring IP Addressing IP Configuration switch, configure the switch with an IP address and subnet mask compatible with your network. The following table lists the general features available with and without a network-compatible IP address configured. Table 8-1. Features Available With and Without IP Addressing on the Switch Features Available Without an IP Address Additional Features Available with an IP Address and Subnet Mask • Direct-connect access to the CLI and the menu interface.
Configuring IP Addressing IP Configuration The DHCP/Bootp Process. Whenever the IP Config parameter in the switch or in an individual VLAN in the switch is configured to DHCP/Bootp (the default), or when the switch is rebooted with this configuration: Note 1. DHCP/Bootp requests are automatically broadcast on the local network. (The switch sends one type of request to which either a DHCP or Bootp server can respond.) 2.
Configuring IP Addressing IP Configuration For more information on either of these procedures, refer to the documenta tion provided with the DHCP server. Bootp Operation. When a Bootp server receives a request it searches its Bootp database for a record entry that matches the MAC address in the Bootp request from the switch. If a match is found, the configuration data in the associated database record is returned to the switch.
Configuring IP Addressing IP Configuration Note ip is the IP address to be assigned to the switch (or VLAN). sm is the subnet mask of the subnet in which the switch (or VLAN) is installed. gw is the IP address of the default gateway. lg TFTP server address (source of final configuration file) T144 is the vendor-specific “tag” identifying the configuration file to download. vm is a required entry that specifies the Bootp report format.
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads connectivity to the TFTP file server specified in the reply, that the config uration file is correctly named, and that the configuration file exists in the TFTP directory.
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Entering "ip preserve" in the last line of a configuration file implements IP Preserve when the file is downloaded to the switch and the switch reboots. Figure 8-6. Example of Implementing IP Preserve in a Switch Configuration File For example, consider Figure 8-7: DHCP Server TFTP Server Management Station config. IP Address Switch 1 Switch 2 Switch 3 Switch 4 VLAN 1: 10.31.22.
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Using figure 8-7, above, switches 1 - 3 ignore these entries because the file implements IP Preserve and their current IP addressing was not acquired through DHCP/Bootp. IP Preserve Command Switch 4 ignores IP Preserve and implements the DHCP/Bootp addressing and IP Gateway specified in this file (because its last IP addressing was acquired from a DHCP/Bootp server). Figure 8-8.
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Because switch 4 (figure 8-7) received its most recent IP addressing from a DHCP/Bootp server, the switch ignores the ip preserve command and implements the IP addressing included in this file. Figure 8-9.
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads — This page is intentionally unused.
9 Time Protocols Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 TimeP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 SNTP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Overview: Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time Protocols Overview Overview This chapter describes: ■ SNTP Time Protocol Operation ■ Timep Time Protocol Operation Using time synchronization ensures a uniform time among inter operating devices. This helps you to manage and troubleshoot switch operation by attaching meaningful time data to event and error messages. The switch offers TimeP and SNTP (Simple Network Time Protocol) and a timesync command for changing the time protocol selection (or turning off time protocol operation).
Time Protocols Overview: Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation ular server, it ignores time broadcasts from other SNTP servers unless the configurable Poll Interval expires three consecutive times without an update received from the first-detected server. Note To use Broadcast mode, the switch and the SNTP server must be in the same subnet. ■ Unicast Mode: The switch requests a time update from the config ured SNTP server.
Time Protocols SNTP: Viewing, Selecting, and Configuring Note that simply selecting a time synchronization protocol does not enable that protocol on the switch unless you also enable the protocol itself (step 2, above). For example, in the factory-default configuration, TimeP is the selected time synchronization method. However, because TimeP is disabled in the factory-default configuration, no time synchronization protocol is running.
Time Protocols SNTP: Viewing, Selecting, and Configuring Table 9-1.SNTP Parameters SNTP Parameter Operation Time Sync Method Used to select either SNTP, TIMEP, or None as the time synchronization method. SNTP Mode Disabled The Default. SNTP does not operate, even if specified by the Menu interface Time Sync Method parameter or the CLI timesync command. Unicast Directs the switch to poll a specific server for SNTP time synchronization. Requires at least one server address.
Time Protocols SNTP: Viewing, Selecting, and Configuring Time Protocol Selection Parameter – TIMEP – SNTP – None Figure 9-1. The System Information Screen (Default Values) 2. Press [E] (for Edit). The cursor moves to the System Name field. 3. Use [v] to move the cursor to the Time Sync Method field. 4. Use the Space bar to select SNTP, then press [v] once to display and move to the SNTP Mode field. 5.
Time Protocols SNTP: Viewing, Selecting, and Configuring ii. Enter the IP address of the SNTP server you want the switch to use for time synchronization. Note: This step replaces any previously configured server IP address. If you will be using backup SNTP servers (requires use of the CLI), then see “SNTP Unicast Time Polling with Multiple SNTP Servers” on page 9-21. iii. Press [v] to move the cursor to the Server Version field.
Time Protocols SNTP: Viewing, Selecting, and Configuring CLI: Viewing and Configuring SNTP CLI Commands Described in this Section show sntp page 9-8 [no] timesync pages 9-9 and ff., 9-12 sntp broadcast page 9-9 sntp unicast page 9-10 sntp server pages 9-10 and ff. Protocol Version page 9-12 poll-interval page 9-12 no sntp page 9-13 This section describes how to use the CLI to view, enable, and configure SNTP parameters.
Time Protocols SNTP: Viewing, Selecting, and Configuring Even though, in this example, TimeP is the current time synchronous method, the switch maintains the SNTP configuration. Figure 9-3. Example of SNTP Configuration When SNTP Is Not the Selected Time Synchronization Method Configuring (Enabling or Disabling) the SNTP Mode Enabling the SNTP mode means to configure it for either broadcast or unicast mode.
Time Protocols SNTP: Viewing, Selecting, and Configuring 2. Select SNTP as the time synchronization mode. 3. Enable SNTP for Broadcast mode. 4. View the SNTP configuration again to verify the configuration. The commands and output would appear as follows: 1 show sntp displays the SNTP configuration and also shows that TimeP is the currently active time synchronization mode.
Time Protocols SNTP: Viewing, Selecting, and Configuring Note Deleting an SNTP server when only one is configured disables SNTP unicast operation. For example, to select SNTP and configure it with unicast mode and an SNTP server at 10.28.227.141 with the default server version (3) and default poll interval (720 seconds): HPswitch(config)# timesync sntp Selects SNTP. HPswitch(config)# sntp unicast Activates SNTP in Unicast mode. HPswitch(config)# sntp server 10.28.227.
Time Protocols SNTP: Viewing, Selecting, and Configuring Deletes unicast SNTP server entry. Re-enters the unicast server with a nondefault protocol version. show sntp displays the result. Figure 9-6. Example of Specifying the SNTP Protocol Version Number Changing the SNTP Poll Interval. Syntax: sntp poll-interval < 30 . . 720 > Specifies how long the switch waits between time polling intervals. The default is 720 seconds and the range is 30 to 720 seconds.
Time Protocols SNTP: Viewing, Selecting, and Configuring Figure 9-7. Example of SNTP with Time Sychronization Disabled Disabling the SNTP Mode. If you want to prevent SNTP from being used even if selected by timesync (or the Menu interface’s Time Sync Method param eter), configure the SNTP mode as disabled. Syntax: no sntp Disables SNTP by changing the SNTP mode configuration to Disabled. For example, if the switch is running SNTP in Unicast mode with an SNTP server at 10.28.227.
Time Protocols TimeP: Viewing, Selecting, and Configuring TimeP: Viewing, Selecting, and Configuring TimeP Feature view the Timep time synchronization configuration select Timep as the time synchronization method disable time synchronization enable the Timep mode Default Menu CLI n/a page 9-15 page 9-17 Web — TIMEP page 9-13 pages 9-18 ff.
Time Protocols TimeP: Viewing, Selecting, and Configuring Menu: Viewing and Configuring TimeP To View, Enable, and Modify the TimeP Protocol: 1. From the Main Menu, select: 2. Switch Configuration... 1. System Information Time Protocol Selection Parameter – TIMEP (the default) – SNTP – None Figure 9-9. The System Information Screen (Default Values) 2. Press [E] (for Edit). The cursor moves to the System Name field. 3. Use [v] to move the cursor to the Time Sync Method field. 4.
Time Protocols TimeP: Viewing, Selecting, and Configuring • Use the Space bar to select the Manual mode. i. Press [>] to move the cursor to the Server Address field. ii. Enter the IP address of the TimeP server you want the switch to use for time synchronization. Note: This step replaces any previously configured TimeP server IP address. iii. Press [>] to move the cursor to the Poll Interval field, then go to step 6. 6.
Time Protocols TimeP: Viewing, Selecting, and Configuring This section describes how to use the CLI to view, enable, and configure TimeP parameters. Viewing the Current TimeP Configuration This command lists both the time synchronization method (TimeP, SNTP, or None) and the TimeP configuration, even if SNTP is not the selected time protocol.
Time Protocols TimeP: Viewing, Selecting, and Configuring Configuring (Enabling or Disabling) the TimeP Mode Enabling the TimeP mode means to configure it for either broadcast or unicast mode. Remember that to run TimeP as the switch’s time synchronization protocol, you must also select TimeP as the time synchronization method by using the CLI timesync command (or the Menu interface Time Sync Method parameter). Syntax: timesync timep Selects TimeP as the time protocol.
Time Protocols TimeP: Viewing, Selecting, and Configuring The commands and output would appear as follows: 1 show timep displays the TimeP configuration and also shows that SNTP is the currently active time synchronization mode. 2 3 4 show timep again displays the TimeP configuration and shows that TimeP is now the currently active time synchronization mode. Figure 9-12. Example of Enabling TimeP Operation in DHCP Mode Enabling Timep in Manual Mode.
Time Protocols TimeP: Viewing, Selecting, and Configuring HPswitch(config)# timesync timep Selects TimeP. HPswitch(config)# ip timep manual 10.28.227.141 Activates TimeP in Manual mode. Figure 9-13. Example of Configuring Timep for Manual Operation Changing the TimeP Poll Interval. This command lets you specify how long the switch waits between time polling intervals. The default is 720 minutes and the range is 1 to 9999 minutes.
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers Figure 9-14. Example of TimeP with Time Sychronization Disabled Disabling the TimeP Mode. Disabling the TimeP mode means to configure it as disabled. (Disabling TimeP prevents the switch from using it as the time synchronization protocol, even if it is the selected Time Sync Method option.) Syntax: no ip timep Disables TimeP by changing the TimeP mode configuration to Disabled.
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers all servers in the list without success, it sends an error message to the Event Log and reschedules to try the address list again after the configured Poll Interval time has expired. Address Prioritization If you use the CLI to configure multiple SNTP servers, the switch prioritizes them according to the decimal values of their IP addresses.
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers Prioritized list of SNTP Server IP Addresses Figure 9-16. Example of SNTP Server Address Prioritization Note If there are already three SNTP server addresses configured on the switch, and you want to use the CLI to replace one of the existing addresses with a new one, you must delete the unwanted address before you configure the new one. Deleting Addresses. To delete an address, you must use the CLI.
Time Protocols SNTP Messages in the Event Log Menu Interface Operation with Multiple SNTP Server Addresses Configured When you use the Menu interface to configure an SNTP server IP address, the new address writes over the current primary address, if one is configured. If there are multiple addresses configured, the switch re-orders the addresses according to the criteria described under “Address Prioritization” on page 922.
10 Port Status and Basic Configuration Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 Viewing Port Status and Configuring Port Parameters . . . . . . . . . . . . . . . 10-3 Menu: Viewing Port Status and Configuring Port Parameters . . . . . 10-6 CLI: Viewing Port Status and Configuring Port Parameters . . . . . . . 10-7 Using the CLI To View Port Status . . . . . . . . . . . . . . . . . . . . . . . . 10-8 . . . . . . . . . .
Port Status and Basic Configuration Contents Outbound Port Queues and Packet Priority Settings . . . . . . . . . . . . 10-30 Operating Rules for Port-Based Priority . . . . . . . . . . . . . . . . . . . . . . 10-31 Configuring and Viewing Port-Based Priority . . . . . . . . . . . . . . . . . . 10-32 Messages Related to Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33 Troubleshooting Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Status and Basic Configuration Overview Overview This chapter describes how to view the current port configuration and how to configure ports to non-default settings, including ■ Enable/Disable ■ Mode (speed and duplex) ■ Flow Control ■ Broadcast Limit ■ Auto-MDIX ■ Jumbo Packets on the Series 2800 Switches ■ QoS Pass-Through Mode for Series 2800 Switches ■ Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches ■ Using Friendly (Optional) Port Names View
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Table 10-1. Status and Parameters for Each Port Type Status or Parameter Description Enabled Yes (default): The port is ready for a network connection. No: The port will not operate, even if properly connected in a network. Use this setting, for example, if the port needs to be shut down for diagnostic purposes or while you are making topology changes. Status (read-only) Up: The port senses a linkbeat.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Status or Parameter Description Mode (Continued) 10/100/1000Base-T: • Auto-10: Allows the port to negotiate between half-duplex (HDx) and full-duplex (FDx) while keeping speed at 10 Mbps. Also negotiates flow control (enabled or disabled). HP recommends Auto-10 for links between 10/100 autosensing ports connected with Cat 3 cabling. (Cat 5 cabling is required for 100 Mbps links.).
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Status or Parameter Description Type This parameter appears in the CLI show trunk listing and, for a port in a trunk group, specifies the type of trunk group. The default Type is passive LACP, which can be displayed by using the CLI show lacp command. For more on port trunking, see “Port Trunking” on page Chapter 12, “Port Trunking” .
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Using the Menu To Configure Ports. Note The menu interface uses the same screen for configuring both individual ports and port trunk groups. For information on port trunk groups, see Chapter 12, “Port Trunking” . 1. From the Main Menu, Select: 2. Switch Configuration... 2. Port/Trunk Settings Figure 10-2. Example of Port/Trunk Settings with a Trunk Group Configured 2. Press [E] (for Edit).
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters From the CLI, you can configure and view all port parameter settings and view all port status indicators. Using the CLI To View Port Status Use the following commands to display port status and configuration: ■ show interfaces brief: Lists the full status and configuration for all ports on the switch.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Current Operating Mode Figure 10-3. Example Show Interface Command Listing, 4100gl Switch Current Configured Mode Figure 10-4.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters HPswitch(config)# show interface config P ort Settings Port ------1 2 3 4 5 6 7 Current Configured Mode Type | Enabled Mode F low Ctrl --------- + - ------ ------------ --------10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable 10/100TX | Y es Au to D isable MDI ---MDIX MDIX MDIX MDIX
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters If port C8 was disabled, and you wanted to enable it and configure it for 100FDx with flow-control active, you could do so with either of the following command sets.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters For example, to configure a broadcast limit of 20% for all ports on the switch: Figure 10-7. Example of Configuring a Global Broadcast Limit To display the current broadcast limit setting, use either show config or show running: Displays the startup-config file. The broadcast limit setting appears here if configured and saved to the startup-config file by a write memory command.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters For example, to configure a broadcast limit of 45% on ports 1 - 10 in a Series 2800 Switch: Configures a broadcast limit of 45% on ports 5 - 7 in the running configuration. Displays the broadcastlimit in the running-config file. Figure 10-1.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Using the above ports: ■ If you connect a copper port using a straight-through cable to a port on another switch or hub that uses MDI-X ports, the switch port automati cally operates as an MDI port. ■ If you connect a copper port using a straight-through cable to a port on an end node, such as a server or PC, that uses MDI ports, the switch port automatically operates as an MDI-X port.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters . Syntax: interface < port-list > mdix-mode < automdix | mdi | mdix > automdix is the automatic, default setting. This configures the port for automatic detection of the cable (either straight-through or crossover). mdi is the manual mode setting that configures the port for connecting to either a PC or other MDI device with a crossover cable, or to a switch, hub, or other MDI-X device with a straightthrough cable.
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Per-Port MDI Configuration Figure 10-2. Example of Displaying the Current MDI Configuration Per-Port MDI Operating Mode Figure 10-3. Example of Displaying the Current MDI Operating Mode Note Port Response to Switch Software Updates ■ Series 2600 or 2600-PWR Switch software updated from H_07.XX or earlier ■ Series 2800 Switch software updated from I_07.XX or earlier 1.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches Web: Viewing Port Status and Configuring Port Parameters In the web browser interface: 1. Click on the Configuration tab. 2. Click on Port Configuration. 3. Select the ports you want to modify and click on Modify Selected Ports. 4. After you make the desired changes, click on Apply Settings. Note that the web browser interface displays an existing port trunk group.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches Terminology Jumbo Packet: On the Series 2800 switches, an IP packet exceeding 1522 bytes in size. The maximum Jumbo packet size is 9220 bytes. (This size includes 4 bytes for the VLAN tag.) Jumbo VLAN: A VLAN configured to allow inbound jumbo traffic. All ports belonging to a jumbo and operating at 1 Gbps or higher can receive jumbo packets from external devices.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches traffic from devices on either VLAN. For a method to allow only some ports in a VLAN to receive jumbo traffic, refer to “Operating Notes for Jumbo Traffic-Handling” on page 10-22. Configuring Jumbo Packet Operation Command Page show vlans 10-20 show vlans ports < port-list > 10-21 show vlans < vid > 10-22 jumbo 10-22 Overview 1.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches Viewing the Current Jumbo Configuration Syntax: show vlans Lists the static VLANs configured on the switch and includes a Jumbo column to indicate which VLANs are configured to support inbound jumbo traffic. All ports belonging to a jumbo-enabled VLAN can receive jumbo traffic. (For more information refer to “Operating Notes for Jumbo TrafficHandling” on page 10-22.) See figure 10-4, below.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches Indicates which static VLANs are configured to enable jumbo packets. Figure 10-5. Example of Listing the VLAN Memberships for a Range of Ports Syntax: show vlans < vid > This command shows port membership and jumbo configuration for the specified < vid >. Lists the ports belonging to VLAN 100 and whether the VLAN is enabled for jumbo packet traffic. Figure 10-6.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches Enabling or Disabling Jumbo Traffic on a VLAN Syntax: vlan < vid > jumbo [ no ] vlan < vid > jumbo Configures the specified VLAN to allow jumbo packets on all ports on the switch that belong to that VLAN. If the VLAN is not already configured on the switch, vlan < vid > jumbo also creates the VLAN.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches ■ When a port is not a member of any jumbo-enabled VLAN, it drops all jumbo traffic. If the port is receiving “excessive” inbound jumbo traffic, the port generates an Event Log message to notify you of this condition. This same condition generates a Fault-Finder message in the Alert log of the switch’s web browser interface, and also increments the switch’s “Giant Rx” counter.
Port Status and Basic Configuration Jumbo Packets on the Series 2800 Switches 1 2 3 4 5 6 Jumbo-Enabled VLAN Non-Jumbo VLAN VLAN 10 VLAN 20 Port 3 belongs to both VLAN 10 and VLAN 20. Jumbo packets received inbound on port 3 can be forwarded out the Non-Jumbo ports 4, 5, and 6. Figure 10-7.
Port Status and Basic Configuration QoS Pass-Through Mode on the Series 2800 Switches Troubleshooting A VLAN is configured to allow jumbo packets, but one or more ports drops all inbound jumbo packets. The port may not be operating at 1 gigabit or higher. Regardless of a port’s configuration, if it is actually operating at a speed lower than 1 gigabit, it drops inbound jumbo packets.
Port Status and Basic Configuration QoS Pass-Through Mode on the Series 2800 Switches cant performance improvement for high-bandwidth traffic flows through the 2800 switches, particularly when running traffic flows from 1000Base to either 100Base or 10Base connections. QoS Pass-Through mode is OFF by default, and must be enabled via the “config” context of the CLI by entering the CLI command qos-passthrough mode, followed by write memory and rebooting the switch.
Port Status and Basic Configuration QoS Pass-Through Mode on the Series 2800 Switches An 802.1Q VLAN tagged packet carries an 802.1p priority setting (0-7). If the switch receives a tagged packet, it is placed into the appropriate queue based on the frame's 802.1p priority setting. The mapping with/without QoS PassThrough Mode is as follows: 802.
Port Status and Basic Configuration QoS Pass-Through Mode on the Series 2800 Switches This command can be enabled and disabled only from the switch's CLI. QoS passthrough mode cannot be enabled or disabled through either the switch's menu or web browser interfaces. Once enabled, this feature adds qos-passthrough-mode to the switch’s startup config file.
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches Feature Default Assigning a priority level to traffic on the basis of incoming port Disabled Menu n/a CLI Web page 10-32 n/a When network congestion occurs, it is important to move traffic on the basis of relative importance.
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches member of the VLAN, the packet carries its priority setting to the next, downstream device. If the outbound port is not configured as a tagged member of the VLAN, then the tag is stripped from the packet, which then exits from the switch without a priority setting.
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches For example, suppose you have configured port A10 to assign a priority level of 1 (low): Note ■ An untagged packet coming into the switch on port A10 and leaving the switch through any other port configured as a tagged VLAN member would leave the switch as a tagged packet with a priority level of 1. ■ A tagged packet with an 802.
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches ■ On a given port, an inbound, tagged packet received on the port with a preset priority of 1 - 7 in its tag keeps that priority and is assigned an outbound queue on the basis of that priority (regardless of the port-based priority configured on the port). (Refer to table 10-3, “Mapping Priority Settings to Device Queues” on page 10-30.
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets on the 4100gl and 6108 Switches For example, suppose you wanted to configure ports A10 -A12 on the switch to prioritize all untagged, inbound VLAN traffic as "Low" (priority level = 1; refer to table 10-3 on page 10-30). Configures port-based priority on ports A9 -A12 to "1" (Low) and saves the configuration changes to the startup config file.
Port Status and Basic Configuration Using Friendly (Optional) Port Names Using Friendly (Optional) Port Names Feature Configure Friendly Port Names Display Friendly Port Names Default Menu CLI Web Standard Port Numbering n/a page 35 n/a n/a n/a page 37 n/a This feature enables you to assign alphanumeric port names of your choosing to augment automatically assigned numeric port names.
Port Status and Basic Configuration Using Friendly (Optional) Port Names ■ To retain friendly port names across reboots, you must save the current running-configuration to the startup-config file after entering the friendly port names. (In the CLI, use the write memory command.) Configuring Friendly Port Names Syntax: interface name Assigns a port name to port-list. no interface name Deletes the port name from port-list. Configuring a Single Port Name.
Port Status and Basic Configuration Using Friendly (Optional) Port Names Configuring the Same Name for Multiple Ports. Suppose that you want to use ports A5 through A8 as a trunked link to a server used by a drafting group. In this case you might configure ports A5 through A8 with the name “Draft-Server:Trunk”. Figure 10-11.
Port Status and Basic Configuration Using Friendly (Optional) Port Names Displaying Friendly Port Names with Other Port Data You can display friendly port name data in the following combinations: ■ show name: Displays a listing of port numbers with their corresponding friendly port names and also quickly shows you which ports do not have friendly name assignments. (show name data comes from the running config file.
Port Status and Basic Configuration Using Friendly (Optional) Port Names Port Without a "Friendly" Name Friendly port names assigned in previous examples. Figure 10-13. Example of Friendly Port Name Data for Specific Ports on the Switch Including Friendly Port Names in Per-Port Statistics Listings. A friendly port name configured to a port is automatically included when you display the port’s statistics output.
Port Status and Basic Configuration Using Friendly (Optional) Port Names For a given port, if a friendly port name does not exist in the running-config file, the Name line in the above command output appears as: Name : not assigned To Search the Configuration for Ports with Friendly Port Names. This option tells you which friendly port names have been saved to the startup config file. (show config does not include ports that have only default settings in the startup-config file.
Port Status and Basic Configuration Using Friendly (Optional) Port Names — This page is intentionally unused.
11 Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Contents Applicable Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Applicable Switch Models Applicable Switch Models The Power Over Ethernet (PoE) feature described in this chapter operates on these switches: ■ HP ProCurve Switch 2626-PWR (J8164A) ■ HP ProCurve Switch 2650-PWR (J8165A) Introduction PoE technology allows IP telephones, wireless LAN access points, and other appliances to receive power and transfer data over existing LAN cabling.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Terminology ■ Enable or disable PoE operation on individual ports. (In the default configuration, the switch enables PoE on all 10/100-TX ports, subject to PoE priority in the case of oversubscription of PoE resources.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches General PoE Operation Term Use in this Manual MPS Maintenance Power Signature; the signal a PD sends to the switch to indicate that the PD is connected and requires power. Refer to figure 3 on page 14. PD Powered Device. This is an IEEE 802.3af-compliant device that receives its power through a direct connection to a 10/100Base-TX PoE RJ-45 port on the switch.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches General PoE Operation links. Thus, you can connect either a non-PoE device or a PD to a PoE-enabled port without reconfiguring the port. PD Support The switch must have a minimum of 15.4 watts of unused PoE power available when you connect an 802.3af-compliant PD, regardless of how much power the PD actually uses. On the Switch 2626-PWR, there will always be enough power available to connect and support 802.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches General PoE Operation Disconnecting a PD from a port causes the switch to stop providing PoE power to that port and makes the power available to other ports configured for PoE operation. If the PoE demand becomes greater than the available power, the switch transfers power from lower-priority ports to higher-priority ports. (Ports not currently providing power to PDs are not affected.) Note 15.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches General PoE Operation Note ■ The number of switches drawing external PoE power from the HP 600 RPS/EPS or HP 610 EPS unit. If only a single switch is using external PoE power the HP 600 RPS/EPS or HP 610 EPS provides 408 watts of PoE power. If two switches are using external PoE power from the HP 600 RPS/EPS or two switches are connected to the same pair on the HP 610 EPS, a switch receives 204 watts of PoE power.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches General PoE Operation Table 2. Example of PoE Priority Operation Port Priority Setting Configuration Command1 and Resulting Operation 25 - 48 Critical This priority class always receives power. If there is not enough power to provision PDs on all of the ports configured for this class, then no power goes to ports configured for High and Low priority.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Configuring PoE Operation Configuring PoE Operation In its default configuration, PoE support is enabled on the switch’s 10/100BaseTX ports, with Priority set to Low and the power threshold set to 80 (%). Syntax: power threshold < 1 - 99 > The power threshold is a configurable percentage of the total PoE power available on the switch.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Configuring PoE Operation Syntax: interface [e] < port-list > power [ critical | high | low ] Reconfigures the PoE priority level on < port-list >. For a given level, the switch automatically prioritizes ports by port number (in ascending order). If there is not enough power available to provision all active PoE ports at a given priority level, then the lowest-numbered port at that level will be provisioned first, and so on.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Viewing PoE Configuration and Status Viewing PoE Configuration and Status Displaying the Switch’s Global PoE Power Status Syntax:show power-management Displays the switch’s global PoE power status, including: • Max Power: Lists the maximum PoE wattage available to provision active PoE ports on the switch. • Power In Use: Lists the amount of PoE power presentlyin use.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Viewing PoE Configuration and Status Displaying an Overview of PoE Status on All Ports Syntax:show power-management brief Displays the following port power status: • Port: Lists all PoE-capable ports on the switch. Power Enable: Shows Yes for ports enabled to support PoE (the default) and No for ports on which PoE is disabled. • Priority: Lists the power priority (Low, High, and Critical) configured on ports enabled for PoE.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Viewing PoE Configuration and Status Displaying the PoE Status on Specific Ports Syntax:show power-management [e] < port-list > Displays the following PoE status and statistics (since the last reboot) for each port in < port-list >: • Power Enable: Shows Yes for ports enabled to support PoE (the default) and No for ports on which PoE is disabled.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Viewing PoE Configuration and Status • Power Denied Cnt: Shows the number of times PDs requesting power on the port have been denied due to insufficient power available. Each occurrence generates an Event Log message. • Voltage: The total voltage, in dV, being delivered to PDs. • Power: The total power, in mW, being delivered to PDs. • Configured Type: Shows the type of PD detected on the port.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches Planning and Implementing a PoE Configuration Planning and Implementing a PoE Configuration This section provides an overview of some considerations for planning a PoE application. For additional information on this topic, refer to the HP ProCurve PoE Planning and Implementation Guide. Assigning PoE Ports to VLANs If your network includes VLANs, you may want to assign various PoE-config ured ports to specific VLANs.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches PoE Operating Notes PoE Operating Notes ■ Simply disabling a PoE port does not affect power delivery through that port. To cycle the power on a PD receiving power from a PoE port on the switch, disable, then re-enable the power to that port.
PoE Event Log Messages PoE operation generates these Event Log messages. You can also configure the switch to send these messages to a configured debug destination (terminal device or SyslogD server. I 1MM/DD/YY HH:MM:SS chassis: Message header, with severity, date, system time, and system module type. For more information on Event Log operation, refer to the “Troubleshooting” appendix in the Management and Configuration Guide for your switch.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches PoE Event Log Messages W MM/DD/YY HH:MM:SS chassis: Message header, with severity, date, system time, and system module type. For more information on Event Log operation, refer to the “Troubleshooting” appendix in the Management and Configuration Guide for your switch. Ext Power Supply connected but not responding. The switch detects an external power supply, but is not receiving power from the device.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches PoE Event Log Messages Port < port-# > PD MPS Absent indication. The switch no longer detects a device on < port-# >. The device may have been disconnected, powered down, or stopped functioning. Port < port-# > PD Other Fault indication. There is a problem with the PD connected to the port. Port < port-# > PD Over Current indication. The PD connected to < port-# > has requested more than 15.4 watts of power.
Power Over Ethernet (PoE) Operation for the Series 2600-PWR Switches PoE Event Log Messages — This page is intentionally unused.
12 Port Trunking Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 Port Status and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 Port Connections and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . Link Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Trunking Overview Overview This chapter describes creating and modifying port trunk groups. This includes non-protocol trunks, LACP (802.3ad) trunks, and FEC trunks.
Port Trunking Port Status and Configuration The multiple physical links in a trunk behave as one logical link port a1 port a2 port a3 port a4 port a5 port a6 port a7 port c1 port c2 port c3 port c4 port c5 port c6 port c7 Switch 1: Ports c1 - c4 configured as a port trunk group. ... ... port n port n Switch 2: Ports a2 and a4 - a6 are configured as a port trunk group Figure 12-1.
Port Trunking Port Status and Configuration For example: HPswitch(config)# trunk 1-8 trk1 This command is valid in all cases (switching or routing) because all of the ports are in the same port group. HPswitch(config)# trunk 9-14 trk2 This command is NOT valid if IP routing is enabled on the switch (because the selected ports are in different port groups and IP routing is enabled). If IP routing is enabled, this command generates an error message and will not be executed.
Port Trunking Port Status and Configuration Caution To avoid broadcast storms or loops in your network while configuring a trunk, first disable or disconnect all ports you want to add to or remove from the trunk. After you configure the trunk, enable or re-connect the ports. Port Trunk Options and Operation The switch offers these options for port trunking: ■ LACP (IEEE 802.
Port Trunking Port Status and Configuration Note 1. Go to the port context for ports c1 - c4 and disable these ports. HPswitch(config)# interface c1-c4 HPswitch(eth-c1-c4)#_ HPswitch(eth-c1-c4)# disable 2. Change all four ports to LACP-passive and re-enable the ports. HPswitch(eth-c1-c4)# lacp passive HPswitch(eth-c1-c4)# enable If you change the port trunk configuration on a link, ensure that the port trunk configuration on the other end of the link matches the new configuration.
Port Trunking Port Status and Configuration Table 12-2. Trunk Configuration Protocols Protocol Trunking Options LACP (802.3ad) Provides dynamic and static LACP trunking options. • Dynamic LACP — Use the switch-negotiated dynamic LACP trunk when: – The port on the other end of the trunk link is configured for Active or Passive LACP.
Port Trunking Port Status and Configuration Table 12-3. General Operating Rules for Port Trunks Media: All ports on both ends of a trunk group must have the same media type and mode (speed and duplex). The switch blocks any trunked links that do not conform to this rule. (For the switches covered in this guide, HP recommends leaving the port Mode setting at Auto or, in networks using Cat 3 cabling, Auto-10.
Port Trunking Port Status and Configuration Trunk Group Boundary Requirement for the Series 4100gl Switch 10/100/1000 Module (J4908A): Trunks must be created, manually or dynamically, with ports from the same group, Group1 or Group2. Group1: Ports 1-5, 7-11, 16 Group2: Ports 6, 12-15, 17-22 For example, a trunk made up of ports 3 - 5 is valid; a trunk made up of ports 4 - 6 is not (port 6 is a member of Group2, not Group 1. Ports 21 and 22, for use with mini-GBICs, may be used to form a trunk.
Port Trunking Port Status and Configuration Menu: Viewing and Configuring a Static Trunk Group Important Configure port trunking before you connect the trunked links to another switch, routing switch, or server. Otherwise, a broadcast storm could occur. (If you need to connect the ports before configuring them for trunking, you can temporarily disable the ports until the trunk is configured. See “Using the CLI To Configure Ports” on page 10-10.
Port Trunking Port Status and Configuration • All ports in a trunk must have the same media type and mode (such as 10/100TX set to 100FDx, or 100FX set to 100FDx). The flow control settings must also be the same for all ports in a given trunk. To verify these settings, see “Viewing Port Status and Configuring Port Param eters” on page 10-3.
Port Trunking Port Status and Configuration During the Save process, traffic on the ports configured for trunking will be delayed for several seconds. If the Spanning Tree Protocol is enabled, the delay may be up to 30 seconds. 8. Connect the trunked ports on the switch to the corresponding ports on the opposite device. If you previously disabled any of the trunked ports on the switch, enable them now. (See “Viewing Port Status and Configur ing Port Parameters” on page 10-3.
Port Trunking Port Status and Configuration Using a port list specifies, for switch ports in a static trunk group, only the ports you want to view. In this case, the command specifies ports A5 through A7. However, because port A6 is not in a static trunk group, it does not appear in the resulting listing: Port A5 appears with an example of a name that you can optionally assign using the Friendly Port Names feature. (See “Using Friendly (Optional) Port Names” on page 10-34.
Port Trunking Port Status and Configuration Listing Static LACP and Dynamic LACP Trunk Data. This command lists data for only the LACP-configured ports. Syntax: show lacp In the following example, ports A1 and A2 have been previously configured for a static LACP trunk. (For more on “Active”, see table 12-5 on page 12-22.) Figure 12-8. Example of a Show LACP Listing Dynamic LACP Standby Links.
Port Trunking Port Status and Configuration “Up” Links Standby Link Figure 12-9. Example of a Dynamic LACP Trunk with One Standby Link Using the CLI To Configure a Static or Dynamic Trunk Group Important Configure port trunking before you connect the trunked links between switches. Otherwise, a broadcast storm could occur. (If you need to connect the ports before configuring them for trunking, you can temporarily disable the ports until the trunk is configured.
Port Trunking Port Status and Configuration Configuring a Static Trunk, Static FEC, or Static LACP Trunk Group. For 2600, 2600-PWR, 4100gl, and 6108 switches: Syntax: trunk < trk1 | trk2 | trk3 | trk4 | trk5 | trk6 > < trunk | fec | lacp > For 2800 switches: Syntax: trunk < trk1 ... trk24 > < trunk | fec | lacp > This example uses ports C4 - C6 to create a non-protocol static trunk group with the group name of Trk2.
Port Trunking Port Status and Configuration Switch “A” with ports set to LACP passive (the default). Switch “B” with ports set to LACP passive (the default). Dynamic LACP trunk cannot automatically form because both ends of the links are LACP passive. (In this case STP blocking is needed to prevent a loop. Switch “A” with ports set to LACP active. Switch “B” with ports set to LACP passive (the default).
Port Trunking Port Status and Configuration Syntax: no interface lacp In this example, port C6 belongs to an operating, dynamic LACP trunk.
Port Trunking Port Status and Configuration Note Dynamic LACP trunks operate only in the default VLAN (unless GVRP is enabled and Forbid is used to prevent the trunked ports from joining the default VLAN). Thus, if an LACP dynamic trunk forms using ports that are not in the default VLAN, the trunk will automatically move to the default VLAN unless GVRP operation is configured to prevent this from occurring. In some cases, this can create a traffic loop in your network.
Port Trunking Port Status and Configuration Table 12-4. LACP Trunk Types LACP Port Trunk Operation Configuration Dynamic LACP This option automatically establishes an 802.3ad-compliant trunk group, with LACP for the port Type parameter and DynX for the port Group name, where X is an automatically assigned value from 1 to 6 (2600, 2600-PWR, 4100gl, and 6108) or 1 to 24 (2800), depending on how many dynamic and static trunks are currently on the switch.
Port Trunking Port Status and Configuration Default Port Operation In the default configuration, all ports are configured for passive LACP. However, if LACP is not configured, the port will not try to detect a trunk config uration and will operate as a standard, untrunked port. Note Passive and active LACP port will pause and listen for LACP packets once a link is established. Once this pause is complete then the port, if a trunk is not detected, will be placed in forwarding mode.
Port Trunking Port Status and Configuration Table 12-5. LACP Port Status Data Status Name Meaning Port Numb Shows the physical port number for each port configured for LACP operation (C1, C2, C3 . . .). Unlisted port numbers indicate that the missing ports are assigned to a static Trunk group, an FEC trunk group, or are not configured for any trunking. LACP Enabled Active: The port automatically sends LACP protocol packets.
Port Trunking Port Status and Configuration LACP Notes and Restrictions 802.1X (Port-Based Access Control) Configured on a Port. To main tain security, LACP is not allowed on ports configured for 802.1X authenticator operation. If you configure port security on a port on which LACP (active or passive) is configured, the switch removes the LACP configuration, displays a notice that LACP is disabled on the port(s), and enables 802.1X on that port.
Port Trunking Port Status and Configuration Static LACP Trunks. Where a port is configured for LACP (Active or Passive), but does not belong to an existing trunk group, you can add that port to a static trunk. Doing so disables dynamic LACP on that port, which means you must manually configure both ends of the trunk. Dynamic LACP Trunks. You can configure a port for LACP-active or LACPpassive, but on a dynamic LACP trunk you cannot configure the other options that you can on static trunks.
Port Trunking Port Status and Configuration Half-Duplex and/or Different Port Speeds Not Allowed in LACP Trunks. The ports on both sides of an LACP trunk must be configured for the same speed and for full-duplex (FDx). The 802.3ad LACP standard speci fies a full-duplex (FDx) requirement for LACP trunking. A port configured as LACP passive and not assigned to a port trunk can be configured to half-duplex (HDx).
Port Trunking Port Status and Configuration ■ Depending on the capabilities of the device on the other end of the trunk, negotiate the forwarding mechanism on the trunk to the non-protocol option. ■ When auto-negotiated to the SA/DA forwarding mechanism, provide higher performance on the trunk for broadcast, multicast, and flooded traffic through distribution in the same manner as non-protocol trunking. ■ Support FEC automatic trunk configuration mode on other devices.
Port Trunking Port Status and Configuration source address to the same destination address through the same trunked link, and sends traffic from the same source address to a different destination address through a different link, depending on the rotation of path assign ments among the links in the trunk. Likewise, the switch distributes traffic for the same destination address but from different source addresses through different links.
Port Trunking Port Status and Configuration — This page is intentionally unused.
13 Configuring for Network Management Applications Contents Using SNMP Tools To Manage the Switch . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 SNMP Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 Configuring for SNMP Access to the Switch . . . . . . . . . . . . . . . . . . . . 13-4 Configuring for SNMP Version 3 Access to the Switch . . . . .
Configuring for Network Management Applications Contents Configuring CDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34 Effect of Spanning Tree (STP) On CDP Packet Transmission . . . . 13-36 How the Switch Selects the IP Address To Include in Outbound CDP Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37 CDP Neighbor Data and MIB Objects . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Using SNMP Tools To Manage the Switch Overview You can manage the switch via SNMP from a network management station running an application such as HP ProCurve Manager (PCM) or HP ProCurve Manager Plus (PCM+). For more on PCM and PCM+, visit the HP ProCurve web site at: http://www.hp.com/go/hpprocurve Click on products index in the sidebar, then click on the appropriate link appearing under the Network Management heading.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Management Features SNMP management features on the switch include: ■ SNMP version 1, version 2c or version 3 over IP ■ Security via configuration of SNMP communities (page 13-4) ■ Security via authentication and privacy for SNMP Version 3 access ■ Event reporting via SNMP • Version 1 traps • RMON ■ HP ProCurve Manager/Plus support ■ Flow sampling using either EASE or sFlow (ProCurve 2800 only) ■ Stan
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch If you want to restrict access to one or more specific nodes, you can use the switch’s IP Authorized Manager feature. (Refer to the Access Security Guide for your switch.) Caution The “public” community exists by default and is used by HP’s network man agement applications.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Commands SNMP version 3 (SNMPv3) adds a new command to the CLI for configuring SNMPv3 functions. To enable SMNPv3 operation on the switch you must: Caution a. Enable SNMPv3 with the snmpv3 enable command. An initial user entry will be generated with MD5 authentication and DES privacy. b. You may restrict access to only SNMPv3 agents with the snmpv3 only command.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMPv3 Enable The snmpv3 enable command starts a dialog that performs three functions: enabling the switch to receive SNMPv3 messages, configuring the initial users, and, optionally, to restrict non version-3 messages to “read only”. Figure 13-1 shows and example of this dialog.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Users The second step to using SNMPv3 on the switch is to configure the users that you assign to different groups. To establish users on the switch: Caution a. Add the users to the User table. This is done with the snmpv3 user command. To view the users in the list you use the show snmpv3 user command. b. Assign users to Security Groups based on their security model.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 group group_name user user_name sec-model (— Continued —) user user_name This is the user to be added to the access group. This must match the user name added with the snmpv3 user command. sec-model This defines which security model to use for the added user. A SNMPv3 access Group should only use the ver3 security model.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Then you must set the group access level to the user. This is done with the snmpv3 group command. For more details on the MIBs access for a give group see “Group Access Levels” on page 13-11. Add NetworkAdmin to operator noauth group Add NetwrokMgr to managerpriv group Pre-assigned groups for access by Version 2c and version 1 management applications Figure 13-3.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Group Access Levels The switch supports eight predefined group access levels. There are four levels for use with version 3 users and four are used for access by version 2c or version 1 management applications.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Communities SNMP commuities are supported by the switch to allow management applica tion that use version 2c or version 1 to access the switch. The communities are mapped to Group Access Levels that are used for version 2c or version 1 support. For more information see “Group Access Levels” on page 13-11.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Figure 13-4 shows the assigning of the Operator community on MgrStation1 to the CommunityOperatorReadWrite group. Any other Operator only has an access level of CommunityOperatorReadOnly. Add mapping to allow write access for Operator community on MgrStation1 Two Operator Access Levels Figure 13-4. Assigning a Community to a Group Access Level Table 13-1.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Caution Deleting or changing the community named “public” prevents network man agement applications (such as auto-discovery, traffic monitoring, SNMP trap generation, and threshold setting) from operating in the switch. (Changing or deleting the “public” name also generates an Event Log message.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch If you are adding a community, the fields in this screen are blank. If you are editing an existing community, the values for the currently selected Community appear in the fields. Type the value for this field. Use the Space bar to select values for other fields Figure 13-6.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch CLI: Viewing and Configuring SNMP Community Names Community Name Commands Page show snmp-server [] 13-16 [no] snmp-server 13-17 [community ] 13-17 [host ] [] 13-22 [enable traps 13-23 Listing Community Names and Values.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Configuring Community Names and Values. The snmp-server command enables you to add SNMP communities with either default or specific access attributes, and to delete specific communities. Syntax: [no] snmp-server community < community-name > Configures a new community name. If you do not also specify operator or manager, the switch automatically assigns the community to the operator MIB view.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Notification and Traps The switches covered in this guide support the SNMPv3 notification process. They also support version 1or version 2c traps. For more information on version 1or version2c traps, see “Trap Features” on page 13-20. The SNMPv3 notification process allows for the messages passed to be authenticated and encrypted if you choose. To set up a SNMPv3 notification there are three steps: 1.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 targetaddress < addr-name > params < parms-name> < IP-Addr > ( — Continued — ) max-msg-size The maximum number of bytes of length a message to this target can be. ( Default:1472) taglist < tag-params > Set list of values used to select this entry from snmpNotifyTable. [no] snmpv3 params < params-name > user < user-name > Add or delete a user parameter for use with target address.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Trap Features Feature Default Menu CLI Web snmp-server host (trap receiver) public — page 13-22 — snmp-server enable (authentication trap) none — page 13-23 — A trap receiver is a management station designated by the switch to receive SNMP traps sent from the switch. An authentication trap is a specialized SNMP trap sent to trap receivers when an unauthorized management station tries to access the switch.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Using the CLI To List Current SNMP Trap Receivers. This command lists the currently configured trap receivers and the setting for authentication traps (along with the current SNMP community name data — see “SNMP Communities” on page 13-12). Syntax: show snmp-server Displays current community and trap receiver data.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Configuring Trap Receivers. This command specifies trap receivers by community membership, management station IP address, and the type of Event Log messages to send to the trap receiver. Note If you specify a community name that does not exist—that is, has not yet been configured on the switch—the switch still accepts the trap receiver assign ment.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch For example, to configure a trap receiver in a community named "red-team" with an IP address of 10.28.227.130 to receive only "critical" log messages: HPswitch(config)# snmp-server trap-receiver red-team 10.28.227.130 critical Notes To replace one community name with another for the same IP address, you must use no snmp-server host < community-name> < ip-address > to delete the unwanted community name.
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Advanced Management: RMON The switches covered in this guide support RMON (Remote Monitoring) on all connected network segments. This allows for troubleshooting and optimiz ing your network.
Configuring for Network Management Applications CDP CDP CDP Features CLI Web view the switch’s CDP configuration Feature Default n/a Menu — page 13-32 — view the switch’s CDP Neighbors table n/a — page 13-32 — clear (reset) the CDP Neighbors table n/a — page 13-33 — enable or disable CDP on the switch enabled — page 13-34 — enable or disable CDP operation on an individual port enabled — page 13-35 — change the transmit interval for the switch’s 60 seconds CDP packets — page 13
Configuring for Network Management Applications CDP An SNMP utility can progressively discover CDP devices in a network by: 1. Reading a given device’s CDP Neighbor table (in the Management Infor mation Base, or MIB) to learn about other, neighbor CDP devices 2. Using the information learned in step 1 to go to and read the neighbor devices’ CDP Neighbors tables to learn about additional CDP devices, and so on This section describes CDP operation in the switches covered in this guide.
Configuring for Network Management Applications CDP General CDP Operation The switch stores information about adjacent CDP devices in a CDP Neigh bors table maintained in the switch’s MIB (Management Information Base). This data is available to SNMP-based applications designed to read CDP data from the MIB.
Configuring for Network Management Applications CDP Switch "B" CDP-Aware Switch with CDP Running Switch "C" CDP-Aware Switch with CDP Disabled Accepts, but does not forward CDP packets describing Switch "A". Also transmits CDP packets describing itself (Switch "B") out all ports. Drops CDP packets describing Switch "A". Also, does not transmit any CDP packets describing itself (Switch "C").
Configuring for Network Management Applications CDP and “E” are not neighbors because the intervening CDP-disabled switch “D” does not forward CDP packets; i.e. is not transparent to CDP traffic. (For the same reason, switch “E” does not have any CDP neighbors.
Configuring for Network Management Applications CDP Using the example in figure 13-12, the CDP Neighbor table for switches “A” and “B” would appear similar to these: Switch A: Switch B: (Note that no CDP devices appear on port B5, which is connected to a device on which CDP is present, but disabled.) Figure 13-13.
Configuring for Network Management Applications CDP CDP-disabled switch) does not forward CDP packets; i.e. is not transparent to CDP traffic. (For the same reason, switch “E” does not have any CDP neighbors.) Figure 13-12 (page 13-29) illustrates how multiple CDP neighbors can appear on a single port.
Configuring for Network Management Applications CDP Viewing the Switch’s Current CDP Configuration Syntax: show cdp Lists the switch’s global and per-port CDP configuration. This example shows the default CDP configuration. CDP Enable/Disable on the Switch Packet Hold Time in CDP Neighbor Table Interval for Transmitting Outbound CDP Packets on All Ports Per-Port CDP Enable/Disable Figure 13-14.
Configuring for Network Management Applications CDP Figure 13-15 lists six CDP devices (four switches and two workstations) that the switch has detected by receiving their CDP packets. Figure 13-15. Example of CDP Neighbors Table Listing Figure 13-16 illustrates a topology of CDP-enabled devices for the CDP Neigh bors table listing in figure 13-15.
Configuring for Network Management Applications CDP Note that the table will again list entries after the switch receives new CDP packets from neighboring CDP devices. Figure 13-17. View of the CDP Neighbors Table Immediately After Executing cdp clear Configuring CDP Operation Enabling or Disabling CDP Operation on the Switch.
Configuring for Network Management Applications CDP Enabling or Disabling CDP Operation on Individual Ports. In the factory-default configuration, the switch has all ports enabled and transmit ting CDP packets. Disabling CDP on a port prevents that port from sending outbound CDP packets and causes it to drop inbound CDP packets without recording their data in the CDP Neighbors table.
Configuring for Network Management Applications CDP Changing the Transmission Interval for Outbound CDP Packets. Syntax: cdp timer < 5 . . 254 > Changes the interval the switch uses to transmit CDP packets describing itself to neighbor devices.
Configuring for Network Management Applications CDP Switch "A" CDP Enabled CDP Neighbor Table Port A3 Switch "B" CDP Enabled Port B1 Port C5 Port | Data ------|-----------------A3 | Switch "B"data C5 CDP Packets from Switch "A" to Switch "B" CDP Packets from Switch "B" to Switch "A" STP Root Device CDP Neighbor Table | Switch "B" data STP block on port C5 of switch "A" blocks outbound transmission of CDP packets from switch "A", but does not block inbound packets to switch "A" from switch "B".
Configuring for Network Management Applications CDP 4. If a CDP switch does not detect an IP address on the connecting port of a CDP neighbor, then the loopback IP address is used (127.0.0.1). For example, in figure 13-20, port A1 on CDP switch “X” is connected to port C5 on CDP neighbor switch “Y”, with the indicated VLAN configuration on port C5: VLAN Membership in Port C5 of Switch "Y" VID IP Address? DEFAULT_VLAN (Primary VLAN) 1 No Blue_VLAN 200 10.28.227.103 Red VLAN 300 10.28.227.
Configuring for Network Management Applications CDP Table 13-4. CDP Neighbors Data CDP Neighbor Data Displayed Neighbors Table MIB Address Type No Yes Always "1" (IP address only). CDP Cache Address No Yes IP address of source device. Software Version Yes Yes ASCII String Device Name (ASCII string) Yes Yes In HP ProCurve switches, this is the value configured for the System Name parameter. Device MAC Address Yes Yes Included in the Device Name entry.
Configuring for Network Management Applications CDP CDP MIB data is grouped by type. That is, the Address Types for all detected CDP devices are listed first, then the IP addressesof the source devices, and so on. The first number after the MIB string is the switch port on which the data point for that entry was received. In this case, the switch CDP packets on ports A1 and A3. (For CDP purposes, port numbering is consecutive, from 1 to n, where n is the last consecutive port on the switch.
Configuring for Network Management Applications CDP CDP-Capable Hubs. Some hubs are capable of running CDP, but also forward CDP packets as if the hub itself were transparent to CDP. Such hubs will appear in the switch’s CDP Neighbor table and will also maintain a CDP neighbor table similar to that for switches. For more information, refer to the documentation provided for the specific hub. Troubleshooting CDP Operation. Turn to “Using Logging To Identify Problem Sources” on page C-23.
Configuring for Network Management Applications CDP — This page is intentionally unused.
A File Transfers Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Downloading Switch Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 General Switch Software Download Rules . . . . . . . . . . . . . . . . . . . . . A-3 Using TFTP To Download Switch Software from a Server . . . . . . . . A-3 Menu: TFTP Download from a Server to Primary Flash . . . . . . .
File Transfers Overview Overview You can download new switch software and upload or download switch configuration files. These features are useful for acquiring periodic switch software upgrades and for storing or retrieving a switch configuration.
File Transfers Downloading Switch Software General Switch Software Download Rules Note ■ A switch software image downloaded through the menu interface always goes to primary flash. ■ After a switch software download, you must reboot the switch to imple ment the newly downloaded code. Until a reboot occurs, the switch continues to run on the software it was using before the download started. Downloading new switch software does not change the current switch configuration.
File Transfers Downloading Switch Software Note If your TFTP server is a Unix workstation, ensure that the case (upper or lower) that you specify for the filename is the same case as the characters in the switch software filenames on the server. Menu: TFTP Download from a Server to Primary Flash Note that the menu interface accesses only the primary flash. 1. In the console Main Menu, select Download OS to display this screen: Figure A-1. A-4 Example of the Download OS Screen (Default Values) 2.
File Transfers Downloading Switch Software Progress Bar Figure A-2. Example of the Download OS Screen During a Download A “progress” bar indicates the progress of the download. When the entire switch software file has been received, all activity on the switch halts and you will see Validating and writing system software to FLASH... 7. After the primary flash memory has been updated with the new switch software, you must reboot the switch to implement the newly downloaded code.
File Transfers Downloading Switch Software CLI: TFTP Download from a Server to Primary or Secondary Flash This command automatically downloads a switch software image to primary or secondary flash. Syntax: copy tftp flash < ip-address > < remote-os-file > [< primary | secondary >] Note that if you do not specify the flash destination, the Xmodem download defaults to primary flash. For example, to download a switch software file named G0502.swi from a TFTP server with the IP address of 10.28.227.
File Transfers Downloading Switch Software Using Secure Copy and SFTP This feature is available only on the Series 2600, 2600-PWR, and 2800 Switches. For some situations you may want to use a secure method to issue commands or copy files to the switch. By opening a secure, encrypted SSH session you can then use a third-party software application to take advantage of Secure Copy (SCP) and Secure ftp (SFTP).
File Transfers Downloading Switch Software Note SFTP over SSH version 1 (SSH v1) is not supported. A request from either the client or the switch (or both) using SSH v1 generates an error message. The actual text of the error message differs, depending on the client software in use. Some examples are: Protocol major versions differ: 2 vs. 1 Connection closed Protocol major versions differ: 1 vs.
File Transfers Downloading Switch Software The SCP/SFTP Process To use SCP and SFTP: 1. Open an SSH session as you normally would to establish a secure encrypted tunnel between your computer and the switch. For more detailed directions on how to open an SSH session see the chapter titled “Configuring Secure Shell (SSH)” in the Access Security Guide for your switch. Please note that this is a one-time procedure for new switches or connections.
File Transfers Downloading Switch Software Authentication Switch memory allows up to ten public keys. This means the authentication and encryption keys you use for your third-party client SCP/SFTP software can differ from the keys you use for the SSH session, even though both SCP and SFTP use a secure SSH tunnel. Note SSH authentication through a TACACS+ server and use of SCP or SFTP through an SSH tunnel are mutually exclusive.
File Transfers Downloading Switch Software ■ All files have read-write permission. Several SFTP commands, such as create or remove, are not allowed and return an error message.
File Transfers Downloading Switch Software 1. From the console Main Menu, select 7. Download OS 2. Press [E] (for Edit). 3. Use the Space bar to select XMODEM in the Method field. 4. Press [Enter], then [X] (for eXecute) to begin the switch software download. The following message then appears: Press enter and then initiate Xmodem transfer from the attached computer..... 5. Press [Enter] and then execute the terminal emulator command(s) to begin Xmodem binary transfer.
File Transfers Downloading Switch Software Note that if you do not specify the flash destination, the Xmodem download defaults to primary flash. For example, to download a switch software file named G0103.swi from a PC (running a terminal emulator program such as HyperTerminal) to primary flash: 1. Execute the following command in the CLI: Figure A-4. 2. Example of the Command to Download Switch Software Using Xodem Execute the terminal emulator commands to begin the Xmodem transfer.
File Transfers Downloading Switch Software Switch-to-Switch Download You can use TFTP to transfer a switch software file between two HP ProCurve switches that use the same software code base. The menu interface enables you to transfer primary-to-primary or secondary-to-primary. The CLI enables all combinations of flash location options.
File Transfers Downloading Switch Software General System Information b. Check the Firmware revision line. CLI: Switch-To-Switch Downloads You can download a switch software file between two switches that use the same code base and which are connected on your LAN. To do so, use a copy tftp command from the destination switch.The options for this CLI feature include: ■ Copy from primary flash in the source to either primary or secondary in the destination.
File Transfers Downloading Switch Software If you do not specify either a primary or secondary flash location for the destination, the download automatically goes to primary flash. For example, to download switch software from secondary flash in a switch with an IP address of 10.28.227.103 to the secondary flash in the destination switch, you would execute the following command in the destination switch’s CLI: Figure A-6.
File Transfers Troubleshooting TFTP Downloads Troubleshooting TFTP Downloads When using the menu interface, if a TFTP download fails, the Download OS screen indicates the failure. Message Indicating cause of TFTP Download Failure Figure A-7.
File Transfers Transferring Switch Configurations Note ■ For a Unix TFTP server, the file permissions for the switch software file do not allow the file to be copied. ■ Another console session (through either a direct connection to a terminal device or through Telnet) was already running when you started the session in which the download was attempted. If an error occurs in which normal switch operation cannot be restored, the switch automatically reboots itself.
File Transfers Transferring Switch Configurations TFTP: Copying a Configuration File to a Remote Host. Syntax: copy < startup-config | running-config > tftp < ip-addr > < remote-file > This command copies the switch’s startup configuration (startup-config file) to a remote TFTP host. For example, to upload the current startup configuration to a file named sw4100 in the configs directory on drive "d" in a remote host having an IP address of 10.28.227.105: HPswitch# copy startup-config tftp 10.28.227.
File Transfers Transferring Switch Configurations Xmodem: Copying a Configuration File from a Serially Connected PC or Unix Workstation. To use this method, the switch must be connected via the serial port to a PC or Unix workstation on which is stored the configuration file you want to copy. To complete the copying, you will need to know the name of the file to copy and the drive and directory location of the file.
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation You can use the CLI to copy the following types of switch data to a text file in a management device: ■ Command Output: Sends the output of a switch CLI command as a file on the destination device. ■ Event Log: Copies the switch’s Event Log into a file on the destination device.
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Event Log Output to a Destination Device This command uses TFTP or Xmodem to copy the Event Log content to a PC or UNIX workstation on the network. Syntax: copy event-log tftp < ip-address > < filepath and filename > copy event-log xmodem For example, to copy the event log to a PC connected to the switch: At this point, press [Enter] and start the Xmodem command sequence in your terminal emulator. Figure A-9.
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Crash Log Data Content to a Destination Device This command uses TFTP or Xmodem to copy the Crash Log content to a PC or UNIX workstation on the network. You can copy individual slot information or the master switch information. If you do not specify either, the command defaults to the master data.
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation — This page is intentionally unused.
B Monitoring and Analyzing Switch Operation Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Status and Counters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Menu Access To Status and Counters . . . . . . . . . . . . . . . . . . . . . . . . . B-5 General System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6 Menu Access . . . . . . . . . . . . . . . . . .
Monitoring and Analyzing Switch Operation Contents Switch 6108 and Series 4100gl Switches . . . . . . . . . . . . . . . . . . . . . . B-24 Series 2600, 2600-PWR, and 2800 Switches . . . . . . . . . . . . . . . . . . . . B-24 Menu: Configuring Port and Static Trunk Monitoring . . . . . . . . . . . B-25 CLI: Configuring Port and Static Trunk Monitoring . . . . . . . . . . . . . B-27 Web: Configuring Port Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring and Analyzing Switch Operation Overview Overview The switch has several built-in tools for monitoring, analyzing, and troubleshooting switch and network operation: Note ■ Status: Includes options for displaying general switch information, man agement address data, port status, port and trunk group statistics, MAC addresses detected on each port or VLAN, and STP, IGMP, and VLAN data (page B-4). ■ Counters: Display details of traffic volume on individual ports (page B-10).
Monitoring and Analyzing Switch Operation Status and Counters Data Status and Counters Data This section describes the status and counters screens available through the switch console interface and/or the web browser interface. Note Status or Counters Type You can access all console screens from the web browser interface via Telnet to the console. Telnet access to the switch is available in the Device View window under the Configuration tab.
Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access To Status and Counters Beginning at the Main Menu, display the Status and Counters menu by select ing: 1. Status and Counters Figure B-1. The Status and Counters Menu Each of the above menu items accesses the read-only screens described on the following pages. Refer to the online help for a description of the entries displayed in these screens.
Monitoring and Analyzing Switch Operation Status and Counters Data General System Information Menu Access From the console Main Menu, select: 1. Status and Counters 1. General System Information Figure B-2. Example of General Switch Information This screen dynamically indicates how individual switch resources are being used. See the online Help for details.
Monitoring and Analyzing Switch Operation Status and Counters Data Switch Management Address Information Menu Access From the Main Menu, select: 1 Status and Counters . . . 2. Switch Management Address Information Figure B-3. Example of Management Address Information with VLANs Configured This screen displays addresses that are important for management of the switch. If multiple VLANs are not configured, this screen displays a single IP address for the entire switch. See the online Help for details.
Monitoring and Analyzing Switch Operation Status and Counters Data Module Information Use this feature to determine which slots have modules installed and which type(s) of modules are installed. Menu: Displaying Port Status From the Main Menu, select: 1. Status and Counters . . . 3. Module Information Figure B-4.
Monitoring and Analyzing Switch Operation Status and Counters Data Port Status The web browser interface and the console interface show the same port status data. Menu: Displaying Port Status From the Main Menu, select: 1. Status and Counters . . . 4. Port Status Figure B-5. Example of Port Status on the Menu Interface CLI Access Syntax: show interfaces brief Web Access 1. Click on the Status tab. 2. Click on Port Status.
Monitoring and Analyzing Switch Operation Status and Counters Data Viewing Port and Trunk Group Statistics and Flow Control Status Feature Default Menu CLI Web viewing port and trunk statistics for all ports, and flow control status n/a page B-11 page B-12 page B-12 viewing a detailed summary for a particular port or trunk n/a page B-11 page B-12 page B-12 resetting counters n/a page B-11 page B-12 page B-12 These features enable you to determine the traffic patterns for each port since
Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access to Port and Trunk Statistics To access this screen from the Main Menu, select: 1. Status and Counters . . . 4. Port Counters Figure B-6. Example of Port Counters on the Menu Interface To view details about the traffic on a particular port, use the [v] key to highlight that port number, then select Show Details. For example, selecting port A2 displays a screen similar to figure B-7, below. Figure B-7.
Monitoring and Analyzing Switch Operation Status and Counters Data CLI Access To Port and Trunk Group Statistics To Display the Port Counter Summary Report. This command provides an overview of port activity for all ports on the switch. Syntax: show interfaces To Display a Detailed Traffic Summary for Specific Ports. This com mand provides traffic details for the port(s) you specify. Syntax: show interfaces [ethernet] < port-list > To Reset the Port Counters for a Specific Port.
Monitoring and Analyzing Switch Operation Status and Counters Data Viewing the Switch’s MAC Address Tables Feature Default Menu CLI Web viewing MAC addresses on all ports on a specific VLAN n/a page B-14 page B-16 — viewing MAC addresses on a specific port n/a page B-15 page B-16 — searching for a MAC address n/a page B-15 page B-17 — These features help you to view: ■ The MAC addresses that the switch has learned from network devices attached to the switch ■ The port on which each M
Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access to the MAC Address Views and Searches Per-VLAN MAC-Address Viewing and Searching. This feature lets you determine which switch port on a selected VLAN is being used to communi cate with a specific device on the network. The per-VLAN listing includes: ■ The MAC addresses that the switch has learned from network devices attached to the switch ■ The port on which each MAC address was learned 1. From the Main Menu, select: 1.
Monitoring and Analyzing Switch Operation Status and Counters Data Finding the Port Connection for a Specific Device on a VLAN. This feature uses a device’s MAC address that you enter to identify the port used by that device. 1. Proceeding from figure B-8, press [S] (for Search), to display the following prompt: Enter MAC address: _ 2. Type the MAC address you want to locate and press [Enter]. The address and port number are highlighted if found.
Monitoring and Analyzing Switch Operation Status and Counters Data Prompt for Selecting the Port To Search Figure B-10. Listing MAC Addresses for a Specific Port 2. Use the Space bar to select the port you want to list or search for MAC addresses, then press [Enter] to list the MAC addresses detected on that port. Determining Whether a Specific Device Is Connected to the Selected Port. Proceeding from step 2, above: 1. Press [S] (for Search), to display the following prompt: Enter MAC address: _ 2.
Monitoring and Analyzing Switch Operation Status and Counters Data Corresponding Port Numbers. For example, to list the learned MAC address on ports A1 through A4 and port A6: HPswitch> show mac-address a1-a4,a6 To List All Learned MAC Addresses on a VLAN, with Their Port Numbers. This command lists the MAC addresses associated with the ports for a given VLAN. For example: HPswitch> show mac-address vlan 100 Note The switch operates with a multiple forwarding database architecture.
Monitoring and Analyzing Switch Operation Status and Counters Data Spanning Tree Protocol (STP) Information Menu Access to STP Data From the Main Menu, select: 1. Status and Counters . . . 8. Spanning Tree Information STP must be enabled on the switch to display the following data: Figure B-12. Example of Spanning Tree Information Use this screen to determine current switch-level STP parameter settings and statistics.
Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-13. Example of STP Port Information CLI Access to STP Data This option lists the STP configuration, root data, and per-port data (cost, priority, state, and designated bridge).
Monitoring and Analyzing Switch Operation Status and Counters Data Internet Group Management Protocol (IGMP) Status The switch uses the CLI to display the following IGMP status on a per-VLAN basis: Show Command Output show ip igmp Global command listing IGMP status for all VLANs configured in the switch: • VLAN ID (VID) and name • Active group addresses per VLAN • Number of report and query packets per group • Querier access port per VLAN show ip igmp Per-VLAN command listing above IGMP stat
Monitoring and Analyzing Switch Operation Status and Counters Data VLAN Information The switch uses the CLI to display the following VLAN status: Syntax: show vlan Lists: • Maximum number of VLANs to support • Existing VLANs • Status (static or dynamic) • Primary VLAN Syntax: show vlan < vlan-id > For the specified VLAN, lists: • Name, VID, and status (static/dynamic) • Per-Port mode (tagged, untagged, forbid, no/ auto) • “Unknown VLAN” setting (Learn, Block, Disable) • Port status (up/down) For examp
Monitoring and Analyzing Switch Operation Status and Counters Data Listing the VLAN ID (VID) and Status for ALL VLANs in the Switch. Figure B-15. Example of VLAN Listing for the Entire Switch Listing the VLAN ID (VID) and Status for Specific Ports. Because ports A1 and A2 are not members of VLAN44, it does not appear in this listing. Figure B-16. Example of VLAN Listing for Specific Ports Listing Individual VLAN Status. Figure B-17.
Monitoring and Analyzing Switch Operation Status and Counters Data Web Browser Interface Status Information The “home” screen for the web browser interface is the Status Overview screen, as shown below. As the title implies, it provides an overview of the status of the switch, including summary graphs indicating the network utili zation on each of the switch ports, symbolic port status indicators, and the Alert Log, which informs you of any problems that may have occurred on the switch.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Port and Static Trunk Monitoring Features Port Monitoring Features Feature Default Menu CLI Web display monitoring configuration disabled page B-25 page B-27 page B-29 configure the monitor port(s) ports: none page B-25 page B-27 page B-29 selecting or removing ports page B-25 page B-28 page B-29 none selected Switch 6108 and Series 4100gl Switches You can designate a port for monitoring inbound (ingress) traff
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Menu: Configuring Port and Static Trunk Monitoring This procedure describes configuring the switch for monitoring when moni toring is disabled. (If monitoring has already been enabled, the screens will appear differently than shown in this procedure.) 1. From the Console Main Menu, Select: 2. Switch Configuration... 3. Network Monitoring Port Enable monitoring by setting this parameter to “Yes”. Figure B-19.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Move the cursor to the Monitoring Port parameter. Port where monitored traffic exits the switch. Figure B-20. How To Select a Monitoring Port B-26 5. Use the Space bar to select the port to use for monitoring. 6. Use the downarrow key to move the cursor to the Action column for the individual ports and position the cursor at a port you want to monitor. 7.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features CLI: Configuring Port and Static Trunk Monitoring Port and Static Trunk Monitoring Commands Used in This Section show monitor mirror-port monitor below page B-27 page B-28 You must use the following configuration sequence to configure port and static trunk monitoring in the CLI: 1. Assign a monitoring (mirror) port. 2. Designate the port(s) and static trunk(s) to monitor. Displaying the Monitoring Configuration.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features To turn off monitoring: HPswitch(config)# no mirror-port Selecting or Removing Ports and Static Trunks As Monitoring Sources. After you configure a monitor port you can use either the global configuration level or the interface context level to select ports and static trunks as monitoring sources. You can also use either level to remove moni toring sources.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Web: Configuring Port Monitoring To enable port monitoring: 1. Click on the Configuration tab. 2. Click on Monitor Port. 3. To monitor one or more ports. 4. a. Click on the radio button for Monitor Selected Ports. b. Select the port(s) to monitor. Click on Apply Changes. To remove port monitoring: 1. Click on the Monitoring Off radio button. 2. Click on Apply Changes.
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features — This page is intentionally unused.
C Troubleshooting Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Troubleshooting Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Chassis Over-Temperature Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 Browser or Telnet Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6 Unusual Network Activity . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Contents Displaying the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLI: Viewing the Configuration File . . . . . . . . . . . . . . . . . . . . . . Web: Viewing the Configuration File . . . . . . . . . . . . . . . . . . . . . . Listing Switch Configuration and Operation Details for Help in Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-39 C-39 C-39 C-40 CLI Administrative and Troubleshooting Commands . . . . .
Troubleshooting Overview Overview This chapter addresses performance-related network problems that can be caused by topology, switch configuration, and the effects of other devices or their configurations on switch operation. (For switch-specific information on hardware problems indicated by LED behavior, cabling requirements, and other potential hardware-related problems, refer to the installation guide you received with the switch.
Troubleshooting Troubleshooting Approaches C-4 ■ Check the network cables – Cabling problems are a frequent cause of network faults. Check the cables for damage, correct type, and proper connections. You should also use a cable tester to check your cables for compliance to the relevant IEEE 802.3 specification. See the Installation Guide shipped with the switch for correct cable types and connector pinouts.
Troubleshooting Chassis Over-Temperature Detection Chassis Over-Temperature Detection If a Switch 2800 Series device reaches an over-temperature condition, it generates a chassis-module Warning message in the Event Log and in any optionally configured debug destinations (console session and SyslogD serv ers). If the switch later returns to its acceptable temperature range, it signals this event with a chassis module Information message to the same destina tions.
Troubleshooting Browser or Telnet Access Problems Browser or Telnet Access Problems Cannot access the web browser interface: ■ Access may be disabled by the Web Agent Enabled parameter in the switch console. Check the setting on this parameter by selecting: 2. Switch Configuration . . . 1. System Information ■ The switch may not have the correct IP address, subnet mask or gateway. Verify by connecting a console to the switch’s Console port and selecting: 2. Switch Configuration . . . 5.
Troubleshooting Browser or Telnet Access Problems Cannot Telnet into the switch console from a station on the network: ■ Telnet access may be disabled by the Inbound Telnet Enabled parameter in the System Information screen of the menu interface: 2. Switch Configuration 1. System Information ■ The switch may not have the correct IP address, subnet mask, or gateway. Verify by connecting a console to the switch’s Console port and selecting: 2. Switch Configuration 5.
Troubleshooting Unusual Network Activity Unusual Network Activity Network activity that fails to meet accepted norms may indicate a hardware problem with one or more of the network components, possibly including the switch. Such problems can also be caused by a network loop or simply too much traffic for the network as it is currently designed and implemented.
Troubleshooting Unusual Network Activity This can also happen, for example, if the server is first configured to issue IP addresses with an unlimited duration, then is subsequently configured to issue IP addresses that will expire after a limited duration. One solution is to configure “reservations” in the DHCP server for specific IP addresses to be assigned to devices having specific MAC addresses. For more information, refer to the documentation for the DHCP server.
Troubleshooting Unusual Network Activity ■ If there is more than one physical path between the switch and the other CDP device and STP is running on the switch, then STP will block the redundant link(s). In this case, the switch port on the remaining open link may not be a member of an untagged VLAN, or any untagged VLANs to which the port belongs may not have an IP address. ■ The adjacent device’s CDP Neighbors table may be full.
Troubleshooting Unusual Network Activity ■ Using the Switch Console Interface: From the Main Menu, check the Management Address Information screen by clicking on 1. Status and Counters 2. Switch Management Address Information LACP-Related Problems Unable to enable LACP on a port with the interface [e] < port-number > lacp command. In this case, the switch displays the following message: Operation is not allowed for a trunked port.
Troubleshooting Unusual Network Activity ■ Ensure that the radius-server timeout period is long enough for network conditions. The switch does not authenticate a client even though the RADIUS server is properly configured and providing a response to the authentication request. If the RADIUS server configuration for authenti cating the client includes a VLAN assignment, ensure that the VLAN exists as a static VLAN on the switch. See “How 802.
Troubleshooting Unusual Network Activity Port A9 shows an “Open” status even though Access Control is set to Unauthorized (Force Auth). This is because the port-access authenticator has not yet been activated. Figure C-2. Example of a Port Remaining Open After Being Configured with “Control Unauthorized” RADIUS server fails to respond to a request for service, even though the server’s IP address is correctly configured in the switch.
Troubleshooting Unusual Network Activity Also, ensure that the switch port used to access the RADIUS server is not blocked by an 802.1X configuration on that port. For example, show portaccess authenticator < port-list > gives you the status for the specified ports. Also, ensure that other factors, such as port security or any 802.1X configura tion on the RADIUS server are not blocking the link. The authorized MAC address on a port that is configured for both 802.
Troubleshooting Unusual Network Activity it either must match the server key or you must configure a server-specific key. If the switch already has a server-specific key assigned to the server’s IP address, then it overrides the global key and must match the server key. Global RADIUS Encryption Key Unique RADIUS Encryption Key for the RADIUS server at 10.33.18.119 Figure C-4.
Troubleshooting Unusual Network Activity Fast-Uplink Troubleshooting. Some of the problems that can result from incorrect usage of Fast-Uplink STP include temporary loops and generation of duplicate packets. Problem sources can include: ■ Fast-Uplink is configured on a switch that is the STP root device. ■ Either the Hello Time or the Max Age setting (or both) is too long on one or more switches.
Troubleshooting Unusual Network Activity Switch does not detect a client’s public key that does appear in the switch’s public key file (show ip client-public-key). The client’s public key entry in the public key file may be preceded by another entry that does not terminate with a new line (CR). In this case, the switch interprets the next sequential key entry as simply a comment attached to the preceding key entry.
Troubleshooting Unusual Network Activity TACACS-Related Problems Event Log. When troubleshooting TACACS+ operation, check the switch’s Event Log for indications of problem areas. All Users Are Locked Out of Access to the Switch. If the switch is func tioning properly, but no username/password pairs result in console or Telnet access to the switch, the problem may be due to how the TACACS+ server and/or the switch are configured.
Troubleshooting Unusual Network Activity ■ The encryption key configured in the server does not match the encryption key configured in the switch (by using the tacacs-server key command). Verify the key in the server and compare it to the key configured in the switch. (Use show tacacs-server to list the global key. Use show config or show config running to list any server-specific keys.) ■ The accessible TACACS+ servers are not configured to provide service to the switch.
Troubleshooting Unusual Network Activity TimeP, SNTP, or Gateway Problems The Switch Cannot Find the Time Server or the Configured Gateway . TimeP, SNTP, and Gateway access are through the primary VLAN, which in the default configuration is the DEFAULT_VLAN. If the primary VLAN has been moved to another VLAN, it may be disabled or does not have ports assigned to it. VLAN-Related Problems Monitor Port.
Troubleshooting Unusual Network Activity Link supporting VLAN_1 and VLAN_2 Switch “X” Port X-3 Switch “Y” Port Y- 7 VLAN Port Assignment VLAN Port Assignment Port VLAN_1 Port VLAN_1 X-3 VLAN_2 Untagged Tagged Y-7 VLAN_2 Untagged Tagged Figure C-5. Example of Correct VLAN Port Assignments on a Link 1. If VLAN_1 (VID=1) is configured as “Untagged” on port 3 on switch “X”, then it must also be configured as “Untagged” on port 7 on switch “Y”.
Troubleshooting Unusual Network Activity MAC Address “A”; VLAN 1 Server MAC Address “A”; VLAN 2 HP ProCurve Switches Covered by this Guide (Multiple Forwarding Database) VLAN 1 VLAN 2 Switch with Single Forwarding Database Problem: This switch detects continual moves of MAC address “A” between ports. Figure C-6.
Troubleshooting Using Logging To Identify Problem Sources Using Logging To Identify Problem Sources Event Log Operation The Event Log records operating events as single-line entries listed in chrono logical order, and serves as a tool for isolating problems. Each Event Log entry is composed of five fields: Severity I Date 08/05/01 Time System Module 10:52:32 ports: Event Message port A1 enabled Figure C-7.
Troubleshooting Using Logging To Identify Problem Sources (The event log is not erased by using the Reboot Switch command in the Main Menu.) Table C-1.
Troubleshooting Using Logging To Identify Problem Sources Menu: Entering and Navigating in the Event Log From the Main Menu, select Event Log. Range of Events in the Log Range of Log Events Displayed Log Status Line Figure C-8. Example of an Event Log Display The log status line at the bottom of the display identifies where in the sequence of event messages the display is currently positioned.
Troubleshooting Using Logging To Identify Problem Sources CLI: Using the CLI, you can list ■ Events recorded since the last boot of the switch ■ All events recorded ■ Event entries containing a specific keyword, either since the last boot or all events recorded Syntax: show logging [-a] [] HPswitch> show logging Lists recorded log messages since last reboot. HPswitch> show logging -a Lists all recorded log messages, including those before the last reboot.
Troubleshooting Using Logging To Identify Problem Sources Debug and Syslog Operation You can direct switch debug (Event log) messages to these destinations: ■ Up to six SyslogD servers ■ One management-access session through: • A direct-connect RS-232 console CLI session • A Telnet session • An SSH session Figure C-9.
Troubleshooting Using Logging To Identify Problem Sources Debug Types. This section describes the types of debug messages the switch can send to configured debug destinations. Syntax: [no] debug < debug-type > all Configures the switch to send all debug types to the config ured debug destination(s). (Default: Disabled) event Configures the switch to send Event Log messages to the configured debug destination(s).
Troubleshooting Using Logging To Identify Problem Sources Configuring the Switch To Send Debug Messages to One or More SyslogD Servers. Use the logging command to configure the switch to send Syslog messages to a SyslogD server, or to remove a SyslogD server from the switch configuration.
Troubleshooting Using Logging To Identify Problem Sources For example, on a switch where there are no SyslogD servers configured, you would do the following to configure SyslogD servers 18.120.38.155 and 18.120.43.125 and automatically enable Syslog logging (with user as the default logging facility): logging < syslog-ip-addr > configures the Syslog server(s) to use and enables Syslog debug logging.
Troubleshooting Using Logging To Identify Problem Sources Enabling or Disabling Logging to Management Sessions and SyslogD Servers. Use this command when you want to do any of the following: ■ Disable Syslog logging on all currently configured SyslogD servers without removing the servers from the switch configuration. ■ Re-enable Syslog logging if it is disabled and there is at least one SyslogD server currently configured in the switch.
Troubleshooting Using Logging To Identify Problem Sources Shows that Syslog (Destination) logging is enabled and transmitting log messages to IP address 18.120.38.155. Also shows that the logging facility is set to user (the default), and that session logging is enabled.) Disables Syslog logging (but retains the Syslog IP address in the switch configuration). Does not affect Session logging. Shows Syslog (Destination) logging now disabled. Session logging continues to operate. Figure C-11.
Troubleshooting Using Logging To Identify Problem Sources Syntax: show debug List the current debug status for both Syslog logging and Session logging. Shows that Syslog logging is enabled and sending event messages to the user facility on the SyslogD server at IP address 18.120.38.155. Shows that session logging is operating through another session. (You can take control of session logging by executing debug destination session in the session you are currently using.) Figure C-13.
Troubleshooting Diagnostic Tools ■ Ensure that your Syslog server(s) will accept Debug messages. All Syslog messages the switch generates carry the configured facility. All Syslog messages resulting from debug operation carry a “debug” severity. If you configure the switch to transmit debug messages to a SyslogD server, ensure that the server’s Syslog application is configured to accept the “debug” severity level. (The default configuration for some Syslog applications ignores the “debug” severity level.
Troubleshooting Diagnostic Tools 2. If the attached end-node does not have an Auto mode setting, then you must manually configure the switch port to the same setting as the endnode port. See Chapter 10, “Port Status and Basic Configuration”. Ping and Link Tests The Ping test and the Link test are point-to-point tests between your switch and another IEEE 802.3-compliant device on your network. These tests can tell you whether the switch is communicating properly with another device.
Troubleshooting Diagnostic Tools Web: Executing Ping or Link Tests 1. Click here. 2. Click here. 3. Select Ping Test (the default) or Link Test 4. For a Ping test, enter the IP address of the target device. For a Link test, enter the MAC address of the target device. 5. Select the number of tries (packets) and the timeout for each try from the drop-down menus. 6. Click on Start to begin the test. Figure C-14.
Troubleshooting Diagnostic Tools Timeout in Seconds is the number of seconds to allow per attempt to test a connection before determining that the current attempt has failed. To halt a Link or Ping test before it concludes, click on the Stop button. To reset the screen to its default settings, click on the Defaults button. CLI: Ping or Link Tests Ping Tests. You can issue single or multiple ping tests with varying repeti tions and timeout periods.
Troubleshooting Diagnostic Tools Link Tests. You can issue single or multiple link tests with varying repeti tions and timeout periods. The defaults are: ■ Repetitions: 1 (1 - 999) ■ Timeout: 5 seconds (1 - 256 seconds) Syntax: Basic Link Test Link Test with Repetitions Link Test with Repetitions and Timeout Link Test Over a Specific VLAN Link Test Over a Specific VLAN; Test Fail Figure C-16.
Troubleshooting Diagnostic Tools Displaying the Configuration File The complete switch configuration is contained in a file that you can browse from either the web browser interface or the CLI. It may be useful in some troubleshooting scenarios to view the switch configuration. CLI: Viewing the Configuration File Using the CLI, you can display either the running configuration or the startup configuration. (For more on these topics, see appendix C, “Switch Memory and Configuration”.
Troubleshooting Diagnostic Tools Listing Switch Configuration and Operation Details for Help in Troubleshooting Release G.04.05 and greater includes the show tech command.
Troubleshooting Diagnostic Tools 1. In Hyperterminal, click on Transfer | Capture Text... Figure C-17. The Capture Text window of the Hypertext Application Used with Microsoft Windows Software 2. In the File field, enter the path and file name under which you want to store the show tech output. Figure C-18. Example of a Path and Filename for Creating a Text File from show tech Output 3. Click [Start] to create and open the text file. 4. Execute show tech: HPswitch# show tech Note a.
Troubleshooting Diagnostic Tools CLI Administrative and Troubleshooting Commands These commands provide information or perform actions that you may find helpful in troubleshooting operating problems with the switch. Note For more on the CLI, refer to “Using the Command Line Interface (CLI)” on page 4-1. Syntax: show version Shows the software version currently running on the switch, and the flash image from which the switch booted (primary or secondary).
Troubleshooting Restoring the Factory-Default Configuration Restoring the Factory-Default Configuration As part of your troubleshooting process, it may become necessary to return the switch configuration to the factory default settings.
Troubleshooting Restoring a Flash Image Restoring a Flash Image The switch can lose its operating system if either the primary or secondary flash image location is empty or contains a corrupted OS file and an operator uses the erase flash command to erase a good OS image file from the opposite flash location. To Recover from an Empty or Corrupted Flash State.
Troubleshooting Restoring a Flash Image 4. Since the OS file is large, you can increase the speed of the download by changing the switch console and terminal emulator baud rates to a high speed. For example: a. Change the switch baud rate to 115,200 Bps. => sp 115200 b. 5. Change the terminal emulator baud rate to match the switch speed: i. In HyperTerminal, select Call | Disconnect. ii. Select File | Properties. iii. Click on Configure . . .. iv. Change the baud rate to 115200. v. Click on [OK].
Troubleshooting Restoring a Flash Image Figure C-19. Example of Xmodem Download in Progress 8. C-46 When the download completes, the switch reboots from primary flash using the OS image you downloaded in the preceding steps, plus the most recent startup-config file.
D MAC Address Management Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2 Determining MAC Addresses in the Switch . . . . . . . . . . . . . . . . . . . . . . . . D-2 Menu: Viewing the Switch’s MAC Addresses . . . . . . . . . . . . . . . . . . . . D-3 CLI: Viewing the Port and VLAN MAC Addresses . . . . . . . . . . . . . . . . D-4 Viewing theMAC Addresses of Connected Devices on Series 2600/2600-PWR, 2800 and 4100gl Switches . . .
MAC Address Management Overview Overview The switch assigns MAC addresses in these areas: ■ ■ For management functions: • One Base MAC address assigned to the default VLAN (VID = 1) • Additional MAC address(es) corresponding to additional VLANs you configure in the switch For internal switch operations: One MAC address per port (See "CLI: Viewing the Port and VLAN MAC Addresses" on page D-4.) MAC addresses are assigned at the factory.
MAC Address Management Determining MAC Addresses in the Switch ■ Use the CLI to view the switch’s port MAC addresses in hexadecimal format. Menu: Viewing the Switch’s MAC Addresses The Management Address Information screen lists the MAC addresses for: ■ Base switch (default VLAN; VID = 1) ■ Any additional VLANs configured on the switch. Also, the Base MAC address appears on a label on the back of the switch. Note The Base MAC address is used by the first (default) VLAN in the switch.
MAC Address Management Determining MAC Addresses in the Switch CLI: Viewing the Port and VLAN MAC Addresses The MAC address assigned to each switch port is used internally by such features as Flow Control and the Spanning Tree Protocol. Using the walkmib command to determine the MAC address assignments for individual ports can sometimes be useful when diagnosing switch operation. The switch allots 24 MAC addresses per slot.
MAC Address Management Determining MAC Addresses in the Switch ifPhysAddress.1 - 6: Ports A1 - A6 in Slot 1 (Addresses 7 - 24 in slot 1 and 25 - 48 in slot 2 are unused.) ifPhysAddress.49 - 51: Ports C1 - C3 in Slot 3 (Addresses 52 - 72 in slot 3 are unused.) ifPhysAddress.205 ifPhysAddress.226 & 237 Base MAC Address (MAC Address for default VLAN; VID = 1) MAC Addresses for non-default VLANs. Figure D-2.
MAC Address Management Viewing theMAC Addresses of Connected Devices on Series 2600/2600-PWR, 2800 and 4100gl Switches Viewing theMAC Addresses of Connected Devices on Series 2600/ 2600-PWR, 2800 and 4100gl Switches Syntax: show mac-address [ | mac-addr | Lists the MAC addresses of the devices the switch has detected, along with the number of the specific port on which each MAC address was detected. [ port-list ] Lists the MAC addresses of the devices the switch has detected, on the specified port(s).
E Daylight Savings Time on HP ProCurve Switches Configuring Daylight Savings Time This information applies to the following HP ProCurve switches: • • • • • • • • 2512 2524 2626 2650 2626-PWR 2650-PWR 2824 2848 • • • • • • 3400cl 4108gl 4104gl 6108 5304xl 5308xl • • • • • • • 1600M 2400M 2424M 4000M 8000M 212M 224M • HP AdvanceStack Switches • HP AdvanceStack Routers HP ProCurve switches provide a way to automatically adjust the system clock for Daylight Savings Time (DST) changes.
Daylight Savings Time on HP ProCurve Switches Configuring Daylight Savings Time Canada and Continental US: • Begin DST at 2am the first Sunday on or after April 1st. • End DST at 2am the first Sunday on or after October 25th. Middle Europe and Portugal: • Begin DST at 2am the first Sunday on or after March 25th. • End DST at 2am the first Sunday on or after September 24th. Southern Hemisphere: • Begin DST at 2am the first Sunday on or after October 25th.
Daylight Savings Time on HP ProCurve Switches Configuring Daylight Savings Time Before configuring a "User defined" Daylight Time Rule, it is important to understand how the switch treats the entries. The switch knows which dates are Sundays, and uses an algorithm to determine on which date to change the system clock, given the configured "Beginning day" and "Ending day": ■ If the configured day is a Sunday, the time changes at 2am on that day.
Daylight Savings Time on HP ProCurve Switches Configuring Daylight Savings Time — This page is intentionally unused.
Index Symbols => prompt … C-44 Numerics 802.3u auto negotiation standard … 10-4 A access manager … 13-13 operator … 13-13 ACL debug See also debug command. Actions line … 3-9, 3-10, 3-11 location on screen … 3-9 address table, port … B-14 address, network manager … 13-4, 13-5 alert log … 5-19 alert types … 5-20 disabling … 5-24 setting the sensitivity level … 5-23 sorting the entries … 5-19 applicable products … 1-ii asterisk … 3-10, 3-13 authentication trap … 13-20, 13-23 See also SNMP.
priority settings mapped to downstream devices … 10-30 Clear button … 5-11 restoring factory default configuration … C-43 CLI context level … 10-10 command line interface See CLI.
effect of priority settings … 10-30 duplicate MAC address See MAC address Dyn1 See LACP. E ending a console session … 3-5 event log … 3-7, C-23 navigation … C-25 See also debug logging.
removing or replacing … 8-10 IP preserve DHCP server … 8-16 overview … 8-16 rules, operating … 8-16 summary of effect … 8-19 IPX network number … B-7 J Java … 5-4, 5-5 jumbo packets configuration … 10-19 excessive inbound … 10-23 flow control … 10-18, 10-22 GVRP operation … 10-18 management VLAN … 10-22 maximum size … 10-17 MTU … 10-17 port adds and moves … 10-18 port speed … 10-18 security concerns … 10-23 standard MTU … 10-18 through non-jumbo ports … 10-24 traffic sources … 10-18 troubleshooting … 10-25
startup configuration … 3-10 menu interface configuration changes, saving … 3-10 MIB … 13-4 MIB listing … 13-4 MIB, HP proprietary … 13-4 MIB, standard … 13-4 mirroring See port monitoring.
enabling dynamic LACP … 12-16 FEC … 12-7, 12-25 IGMP … 12-9 LACP … 10-5 LACP, full duplex required … 12-5 link requirements … 12-3 logical port … 12-9 media requirements … 12-8 media type … 12-3 menu access to static trunk … 12-10 monitor port restrictions … 12-9 nonconsecutive ports … 12-2 number of trunks … 12-5 port groups for Series 2800 … 12-3, 12-4, 12-8 port groups for Series 4100 10/100/1000 Module … 12-9 port security restriction … 12-9 removing port from static trunk … 12-16 requirements … 12-8 SA
secure copy See SCP/SFTP. secure FTP See SCP/SFTP. security … 5-11, 7-3 Self Test LED behavior during factory default reset … C-43 serial number … B-6 session See debug logging.
URL … 5-12 URL Window … 5-12 switch console See console. switch setup menu … 3-8 switch software See OS. switch-to-switch download … A-14 Syslog facility, user … C-34 See debug logging.
URL browser interface online help location … 5-13 HP Procurve … 5-13, 13-4 management … 5-13 management server … 5-12, 5-13 support … 5-12, 5-13 user name, using for browser or console access … 5-8, 5-10 users, SNMPv3 See SNMPv3.
10 – Index
Technical information in this document is subject to change without notice. ©Copyright 2000, 2004. Hewlett-Packard Development Company, L.P. Reproduction, adaptation, or translation without prior written permission is prohibited except as allowed under the copyright laws.