System information

ManualsBrandsProCurve ManualsComputer equipment2510G Series

Management and

Configuration Guide

2510

www.procurve.com

ProCurve Switches

Q.11. (2510-24)

U.11. (2510-48)

Summary of content (412 pages)

PAGE 1
Management and Configuration Guide 2510 ProCurve Switches Q.11.XX (2510-24) U.11.XX (2510-48) www.procurve.
PAGE 2
PAGE 3
ProCurve Series 2510 Switches January 2008 Management and Configuration Guide
PAGE 4
© Copyright 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Publication Number 5991-4761 January 2008 Applicable Products ProCurve Switch 2510-24 (J9019B) ProCurve Switch 2510-48 (J9020A) Trademark Credits Microsoft, Windows, and Windows NT are US registered trademarks of Microsoft Corporation.
PAGE 5
Contents Product Documentation About Your Switch Manual Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Feature Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi 1 Getting Started Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
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 . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
5 Using the Web Browser Interface Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting a Web Browser Interface Session with the Switch . . . . . . . . . . . .
PAGE 8
Using the Menu and Web Browser Interfaces To Implement Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Configuration Changes Using the Menu Interface . . . . . . . . . . . . . . . . 6-8 Using Save and Cancel in the Menu Interface . . . . . . . . . . . . . . . . 6-9 Rebooting from the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . 6-10 Configuration Changes Using the Web Browser Interface . . . . . . . .
PAGE 9
Menu: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . 8-5 CLI: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . . . 8-7 Web: Configuring IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 How IP Addressing Affects Switch Operation . . . . . . . . . . . . . . . . . . . 8-11 DHCP/Bootp Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12 Network Preparations for Configuring DHCP/Bootp . . . . . . . . .
PAGE 10
Port Status and Basic Configuration Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Viewing Port Status and Configuring Port Parameters . . . . . . . . . . . . . . . 10-2 Menu: Viewing Port Status and Configuring Port Parameters . . . . . 10-4 CLI: Viewing Port Status and Configuring Port Parameters . . . . . . .
PAGE 11
Port Trunking Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Port Status and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Port Connections and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 Link Connections . . . . . . . . . . . . . . . . . . . .
PAGE 12
SNMP Notification and Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18 Trap Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20 Using the CLI To Enable Authentication Traps . . . . . . . . . . . . . 12-23 Advanced Management: RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24 LLDP (Link-Layer Discovery Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25 Terminology . . . . . . . . . . . . . . . . . .
PAGE 13
A File Transfers Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Downloading Switch Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 General Switch Software Download Rules . . . . . . . . . . . . . . . . . . . . . A-3 Using TFTP To Download Switch Software from a Server . . . . . . . .
PAGE 14
B Monitoring and Analyzing Switch Operation Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Status and Counters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Menu Access To Status and Counters . . . . . . . . . . . . . . . . . . . . . . . . . B-5 General System Information . . .
PAGE 15
C Troubleshooting Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Troubleshooting Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Chassis Over-Temperature Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 Browser or Telnet Access Problems . . . . . . . . . .
PAGE 16
Restoring the Factory-Default Configuration . . . . . . . . . . . . . . . . . . . . . . C-43 Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-43 Using the Clear/Reset Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . C-43 Restoring a Flash Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-44 D MAC Address Management Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
Product Documentation About Your Switch Manual Set The switch manual set includes the following: Note ■ Read Me First - a printed guide shipped with your switch. Provides software update information, product notes, and other information. ■ Installation and Getting Started Guide - a printed guide shipped with your switch. This guide explains how to prepare for and perform the physical installation and connection to your network.
PAGE 18
Product Documentation Feature Index For the manual set supporting your switch model, the following feature index indicates which manual to consult for information on a given software feature. (Note that some software features are not supported on all switch models.) Feature Management and Configuration Advanced Traffic Management Access Security Guide 802.1Q VLAN Tagging - X - 802.1p Priority X - - 802.
PAGE 19
Product Documentation Feature Management and Configuration Advanced Traffic Management Access Security Guide Link X - - LLDP X - - MAC Address Management X - - Monitoring and Analysis X - - Multicast Filtering - X - Network Management Applications (LLDP, SNMP) X - - Passwords - - X Ping X - - Port Configuration X - - Port Security - - X Port Status X - - Port Trunking (LACP) X - - Port-Based Access Control - - X Port-Based Priority (802.
PAGE 20
Product Documentation Feature Management and Configuration Advanced Traffic Management Access Security Guide TACACS+ Authentication - - X Telnet Access X - - TFTP X - - Time Protocols (TimeP, SNTP) X - - Troubleshooting X - - VLANs - X - Xmodem X - - xviii
PAGE 21
1 Getting Started Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Feature Descriptions by Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Prompts . . . . . . . . . . . . . . . . . . .
PAGE 22
Getting Started Introduction Introduction This Management and Configuration Guide is intended to support the following switches: ■ ProCurve Series 2510-24 ■ ProCurve Series 2510-48 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. For an overview of other product documentation for the above switches, refer to “Product Documentation” on page xv.
PAGE 23
Getting Started Conventions 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. ■ Braces within square brackets ( [ < > ] ) indicate a required element within an optional choice.
PAGE 24
Getting Started Sources for More Information Screen Simulations Figures containing simulated screen text and command output look similar to this: ProCurve(config)# show version Image stamp: /sw/code/build/dosx(ndx) Dec 11 2007 11:44:02 U.11.03 1340 Boot Image: Primary Figure 1-1. Example of a Figure Showing a Simulated Screen In some cases, brief command-output sequences appear outside of a numbered figure. For example: ProCurve(config)# ip default-gateway 18.28.152.
PAGE 25
Getting Started Sources for More Information Note For the latest version of all ProCurve switch documentation, including release notes covering recently added features, visit the ProCurve Networking website at www.procurve.com. Click on Technical support, and then click on Product manuals (all). ■ For 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-2.
PAGE 26
Getting Started Need Only a Quick Start? ■ For further information on ProCurve Networking switch technology, visit the ProCurve website at: www.procurve.com 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 multiple VLANs, ProCurve 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.
PAGE 27
2 Selecting a Management Interface Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Advantages of Using the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Advantages of Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Advantages of Using the Web Browser Interface . . . . . . . . . . . . . . . . . . . . .
PAGE 28
Selecting a Management Interface Overview Overview Management interfaces enable you to reconfigure the switch and to monitor switch status and performance.
PAGE 29
Selecting a Management Interface Advantages of Using the Menu Interface Advantages of Using the Menu Interface Figure 2-1.
PAGE 30
Selecting a Management Interface Advantages of Using the CLI ■ Allows faster navigation, avoiding delays that occur with slower display of graphical objects over a web browser interface. ■ Provides more security; configuration information and passwords are not seen on the network. Advantages of Using the CLI ProCurve> Operator Level ProCurve# Manager Level ProCurve(config)# Global Configuration Level ProCurve()# Context Configuration Levels (port, VLAN) Figure 2-2.
PAGE 31
Selecting a Management Interface Advantages of Using the Web Browser Interface Advantages of Using the Web Browser Interface Figure 2-3.
PAGE 32
Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus Advantages of Using ProCurve Manager or ProCurve Manager Plus You can operate ProCurve Manager and 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. Easy to install and use, PCM and PCM+ are the answers to your management challenges. Figure 2-4.
PAGE 33
Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus PCM and PCM+ enable greater control, uptime, and performance in your network: ■ ■ Features and benefits of 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.
PAGE 34
Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus 2-8 • Device Software Updates: This feature automatically obtains new device software images from ProCurve 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 user-specified times.
PAGE 35
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 36
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-8) ■ Rebooting the switch (page 3-11) 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 addressing ne
PAGE 37
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.
PAGE 38
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). 2. 3.
PAGE 39
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.
PAGE 40
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.
PAGE 41
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”.
PAGE 42
Using the Menu Interface Screen Structure and Navigation ■ 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.
PAGE 43
Using the Menu Interface Screen Structure and Navigation Screen title – identifies the location within the menu structure Parameter fields Help describing each of the items in the parameter fields Actions line Help line describing the selected action or selected parameter field Navigation instructions Figure 3-4. Elements of the Screen Structure “Forms” Design. The configuration screens, in particular, operate similarly to a number of PC applications that use forms for data entry.
PAGE 44
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.
PAGE 45
Using the Menu Interface Rebooting the Switch 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.
PAGE 46
Using the Menu Interface Rebooting the Switch (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. (Note that the Reboot Switch option is not available if you log on in Operator mode; that is, if you enter an Operator password instead of a manager password at the password prompt.) Reboot Switch option Figure 3-6.
PAGE 47
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.
PAGE 48
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
PAGE 49
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.
PAGE 50
Using the Menu Interface Where To Go From Here 3-16
PAGE 51
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 52
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.
PAGE 53
Using the Command Line Interface (CLI) Using the CLI When you use the CLI to make a configuration change, the switch writes the change to the Running-Config file in volatile memory. This allows you to test your configuration changes before making them permanent. To make changes permanent, you must use the write memory command to save them to the Startup Config file in non-volatile memory.
PAGE 54
Using the Command Line Interface (CLI) Using the CLI Caution ProCurve strongly recommends that you configure a Manager password. If a Manager 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.
PAGE 55
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 4-2.) A “#” character delimits any Manager prompt. For example: ProCurve#_ ■ 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.
PAGE 56
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.
PAGE 57
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 ProCurve> enable Password:_ After you enter enable, the Password prompt appears.
PAGE 58
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 runningconfig 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.
PAGE 59
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].
PAGE 60
Using the Command Line Interface (CLI) Using the CLI telnet terminal ProCurve(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 extensions. For example: ProCurve(config)# port [Tab] ProCurve(config)# port-security _ Pressing [Tab] after a completed command word lists the further options for that command.
PAGE 61
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 configuring console settings: This example displays the command options for configuring the switch’s console settings. Figure 4-5.
PAGE 62
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.
PAGE 63
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.
PAGE 64
Using the Command Line Interface (CLI) Using the CLI Port or Trunk-Group Context . Includes port- or trunk-specific commands that apply only to the selected port(s) or trunk group, plus the global configuration, Manager, and Operator commands. The prompt for this mode includes the identity of the selected port(s): Command executed at configuration level for ProCurve(config)# interface e trk1 entering port or trk1 static trunk-group context.
PAGE 65
Using the Command Line Interface (CLI) Using the CLI In the port context, the first block of commands in the "?" listing show the context-specific commands that will affect only ports 3-6. The remaining commands in the listing are Manager, Operator, and context commands. Figure 4-9.
PAGE 66
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: ProCurve(config)# vlan 100 Command executed at configuration level to enter VLAN 100 context. ProCurve(vlan-100)# Resulting prompt showing VLAN 100 context.
PAGE 67
Using the Command Line Interface (CLI) CLI Control and Editing CLI Control and Editing 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.
PAGE 68
Using the Command Line Interface (CLI) CLI Control and Editing 4-18
PAGE 69
5 Using the Web Browser Interface Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting a Web Browser Interface Session with the Switch . . . . . . . . . . . . 5-4 Using a Standalone Web Browser in a PC or UNIX Workstation . . . .
PAGE 70
Using the Web Browser Interface Overview Overview The 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).
PAGE 71
Using the 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 status •
PAGE 72
Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch Starting a 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 ProCurve Manager on your network Using a Standalone Web Browser in a PC or UNIX Worksta
PAGE 73
Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) ProCurve Manager and 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 workstation.
PAGE 74
Using the Web Browser Interface Starting a 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.
PAGE 75
Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Tasks for Your First 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 contains a “Fi
PAGE 76
Using the Web Browser Interface Tasks for Your First 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.
PAGE 77
Using the Web Browser Interface Tasks for Your First 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.
PAGE 78
Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Using the Passwords Figure 5-4. Example of the Password Window in the Web Browser Interface The manager and operator passwords are used to control access to all switch interfaces. Once set, you will be prompted to supply the password every time you try to access the switch through any of its interfaces.
PAGE 79
Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Online Help for the Web Browser Interface Online Help is available for the web browser interface. You can use it by clicking on the question mark button in the upper right corner of any of the web browser interface screens. The Help Button Figure 5-5. The Help Button Context-sensitive help is provided for the screen you are on.
PAGE 80
Using the 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.
PAGE 81
Using the 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: www.procurve.com which is the web site for ProCurve’s networking products. Click on the [Support] button on that page and you can get to support information regarding your switch, including white papers, operating system (OS) updates, and more.
PAGE 82
Using the 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 ProCurve web site. Figure 5-7. How To Access Web Browser Interface Online Help Using the PCM Server for Switch Web Help For ProCurve devices that support the “Web Help” feature, you can use the PCM server to host the switch help files for devices that do not have HTTP access to the ProCurve Support Web site. 1.
PAGE 83
Using the Web Browser Interface Support/Mgmt URLs Feature 3. Add an entry, or edit the existing entry in the Discovery portion of the global properties (globalprops.prp) in PCM to redirect the switches to the help files on the PCM server. For example: Global { TempDir=data/temp ... Discovery{ ... ... DeviceHelpUrlRedirect=http://15.29.37.12.8040/rnd/device_help ... } } You will enter the IP address for your PCM server. 8040 is the standard port number to use. 4.
PAGE 84
Using the 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-17) ■ The Alert log (page 5-20) ■ The Status bar (page 5-23) 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.
PAGE 85
Using the Web Browser Interface Status Reporting Features Policy Management and Configuration. ProCurve PCM can perform network-wide policy management and configuration of your switch. The Management Server URL field (page 5-13) shows the URL for the management station performing that function. For more information, refer to the documentation provided with the PCM software.
PAGE 86
Using the Web Browser Interface Status Reporting Features ■ % Error Pkts Rx: All error packets received by the port. (This indicator is a reddish color on many systems.) Although errors received on a port are not propagated to the rest of the network, a consistently high number of errors on a specific port may indicate a problem on the device or network segment connected to the indicated port.
PAGE 87
Using the Web Browser Interface Status Reporting Features Figure 5-11. Display of Numerical Values for the Bar 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: ■ Port Connected – the port is enabled and is properly connected to an active network device.
PAGE 88
Using the 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-21 Figure 5-13.
PAGE 89
Using the Web Browser Interface Status Reporting Features Alert Types and Detailed Views As of August, 2006, 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 Viol
PAGE 90
Using the Web Browser Interface Status Reporting Features Figure 5-14.
PAGE 91
Using the 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. Most Critical Alert Description Status Indicator 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.
PAGE 92
Using the Web Browser Interface Status Reporting Features ■ Most Critical Alert Description. A brief description of the earliest, unacknowledged alert with the current highest severity in the Alert Log, appearing in the right portion of the Status Bar. In instances where multiple critical alerts have the same severity level, only the earliest unacknowledged alert is deployed in the Status bar. ■ Product Name.
PAGE 93
Using the Web Browser Interface Status Reporting Features To provide the most information on network problems in the Alert Log, the recommended sensitivity level for Log Network Problems is High Sensitivity. The Fault Detection settings are: ■ 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.
PAGE 94
Using the Web Browser Interface Status Reporting Features 5-26
PAGE 95
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 96
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 configuration 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 Over
PAGE 97
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.
PAGE 98
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: ProCurve(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.
PAGE 99
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 permanent How To Use the CLI To View the Current Configuration Files. Use show commands to view the configuration for individual features, such as port status or Spanning Tree Protocol.
PAGE 100
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.
PAGE 101
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. ProCurve(config)# interface e 1 disable ProCurve(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.
PAGE 102
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.
PAGE 103
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.
PAGE 104
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.
PAGE 105
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.
PAGE 106
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.
PAGE 107
Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, if a 2510-24 switch is using a software version of Q.11.XX stored in Primary flash, show version produces the following: ProCurve(config)# show version Image stamp: /sw/code/build/bass(ppne_swt) Nov 21 2007 11:44:02 Q.11.XX 1189 Boot Image: Primary Figure 6-7. Example Showing the Identity of the Current Flash Image Determining Whether the Flash Images Are Different Versions.
PAGE 108
Switch Memory and Configuration Using Primary and Secondary Flash Image Options 1. In this example show version indicates the switch has version Q.11.XX in primary flash. ProCurve(config)# show version Image stamp: /sw/code/build/bass(ppne_swt) Dec 17 2007 11:44:02 Q.11.XX 2624 Boot Image: Primary ProCurve(config)# boot system flash secondary Device will be rebooted, do you want to continue [y/n]? 2. After the boot system command, show version indicates that version Q.11.XX is in secondary flash.
PAGE 109
Switch Memory and Configuration Using Primary and Secondary Flash Image Options flash and you can either copy the secondary image into primary or download another image to primary from an external source. See Appendix A, “File Transfers”. 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.
PAGE 110
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Syntax: copy flash flash where: destination flash = primary or secondary: For example, to copy the image in secondary flash to primary flash: 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.
PAGE 111
Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, to erase the software image in primary flash, do the following: 1. First verify that a usable flash image exists in secondary flash. The most reliable way to ensure this is to reboot the switch from the flash image you want to retain.
PAGE 112
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Table 6-2. Comparing the Boot and Reload Commands Actions Included In Boot? Save all configuration changes since the last boot or reload Optional, with prompt Included In Reload Note Yes, automatic Config changes saved to the startup-config file Perform all system self-tests Yes No Reload provides a faster system reboot. Choice of primary or secondary No—Uses the current flash image.
PAGE 113
Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, to reboot the switch from secondary flash when there are no pending configuration changes in the running-config file: Figure 6-14. Example of Boot Command with Primary/Secondary Flash Option In the above example, typing either a y or n at the second prompt initiates the reboot operation.
PAGE 114
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Scheduled Reload. Additional parameters have been added to the reload command to allow for a scheduled reboot of the switch via the CLI. Syntax: [no] reload [after <[dd:]hh:]mm> | at []] Enables a scheduled warm reboot of the switch. The switch boots up with the same startup config file and using the same flash image as before the reload.
PAGE 115
Switch Memory and Configuration Using Primary and Secondary Flash Image Options Operating Notes Default Boot Source. The switch reboots from primary flash by default unless you specify the secondary flash. Boot Attempts from an Empty Flash Location. In this case, the switch aborts the attempt and displays Image does not exist Operation aborted. Interaction of Primary and Secondary Flash Images with the Current Configuration.
PAGE 116
Switch Memory and Configuration Using Primary and Secondary Flash Image Options 6-22
PAGE 117
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 118
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 Web Browser Interface” Why Configure Interface
PAGE 119
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
PAGE 120
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.
PAGE 121
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 local terminal mode page 7-8 Listing the Current Console/Serial Link Configuration. The following command lists the current interface access parameter settings.
PAGE 122
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet To re-enable inbound Telnet access: ProCurve(config)# telnet-server Outbound Telnet to Another Device. This feature operates independently of the telnet-server status and enables you to Telnet to another device that has an IP address. Syntax: telnet < ip-address > For example: ProCurve# telnet 10.28.27.204 Reconfigure Web Browser Access. In the default configuration, web browser access is enabled.
PAGE 123
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Note If you change the Baud Rate or Flow Control settings for the switch, you should make the corresponding changes in your console access device. Otherwise, you may lose connectivity between the switch and your terminal emulator due to differences between the terminal and switch settings for these two parameters.
PAGE 124
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Configure the individual parameters. Save the changes. Boot the switch. Figure 7-4. Example of Executing a Series of Console Commands CLI Local Terminal Mode. To enable temporary and non-disruptive changes to the terminal mode without forcing a change in the switch’s terminal mode configuration, use the console local-terminal command.
PAGE 125
Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet none When invoked in a console session, changes the terminal mode to “raw” (scripting mode) for that console session. (Scripting mode eliminates unwanted control characters that may appear in some scripting languages.) Use this option when the configured terminal mode is either vt100 or ansi, and you want to temporarily use the scripting mode.
PAGE 126
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.
PAGE 127
Interface Access and System Information System Information System Information System Information Features Feature Default Menu CLI Web System Name switch product name page 7-12 page 7-14 page 7-16 System Contact n/a page 7-12 page 7-14 page 7-16 System Location n/a page 7-12 page 7-14 page 7-16 MAC Age Time 300 seconds page 7-12 page 7-15 — Time Sync Method None See Chapter 9, “Time Protocols”.
PAGE 128
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.
PAGE 129
Interface Access and System Information System Information 3. Refer to the online help provided with this screen for further information on configuration options for these features. 4. When you have finished making changes to the above parameters, press [Enter], then press [S] (for Save) and return to the Main Menu.
PAGE 130
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.
PAGE 131
Interface Access and System Information System Information Reconfigure the Age Time for Learned MAC Addresses. This command 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: ProCurve(config)# mac-age-time 420 Configure the Time Zone and Daylight Time Rule.
PAGE 132
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.
PAGE 133
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 . . . . . . . .
PAGE 134
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.
PAGE 135
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.
PAGE 136
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 seconds an outgoing packet should exist in the network. In most cases, the default setting (64 seconds) is adequate.
PAGE 137
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.
PAGE 138
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.
PAGE 139
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.
PAGE 140
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”.
PAGE 141
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.
PAGE 142
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.
PAGE 143
Configuring IP Addressing IP Configuration Configure the Optional Default Gateway. Using the Global configuration level, you can assign one default gateway to the switch. Syntax: ip default-gateway For example: ProCurve(config)# ip default-gateway 10.28.227.115 Configure Time-To-Live (TTL). Use this command at the Global config prompt to set the time that a packet outbound from the switch can exist on the network. The default setting is 64 seconds.
PAGE 144
Configuring IP Addressing IP Configuration 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.
PAGE 145
Configuring IP Addressing IP Configuration 2. Note When a DHCP or Bootp server receives the request, it replies with a previously configured IP address and subnet mask for the switch. The switch also receives an IP Gateway address if the server has been configured to provide one. In the case of Bootp, the server must first be configured with an entry that has the MAC address of the switch. (To determine the switch’s MAC address, see Appendix D, "MAC Address Management".
PAGE 146
Configuring IP Addressing IP Configuration operation, Bootp configurations are always the same for a specific receiving device. That is, the Bootp server replies to a request with a configuration previously stored in the server and designated for the requesting device. Bootp Database Record Entries.
PAGE 147
Configuring IP Addressing IP Configuration Note The above Bootp table entry is a sample that will work for the switch when the appropriate addresses and file names are used. Network Preparations for Configuring DHCP/Bootp In its default configuration, the switch is configured for DHCP/Bootp operation.
PAGE 148
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads IP Preserve enables you to copy a configuration file to multiple switches that use the same operating-system software while retaining the individual IP address and subnet mask on VLAN 1 in each switch, and the Gateway IP address assigned to the switch.
PAGE 149
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads ; J9019B Configuration Editor; Created on release #Q.11.XX hostname "ProCurve Switch" time daylight-time-rule None . . . Entering "ip preserve" in the last line of a configuration password manager file implements IP Preserve when the file is Password operator downloaded to the switch and the switch reboots. ip preserve Figure 8-6.
PAGE 150
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads ; J9019B Configuration Editor; Created on release #Q.11.XX hostname "ProCurve Switch" time daylight-time-rule None interface 11 no lacp interface 12 no lacp exit trunk 11-12 Trk1 Trunk Using figure 8-7, above, switches 1 - 3 ignore these ip default-gateway 10.22.32.
PAGE 151
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads To summarize the IP Preserve effect on IP addressing: ■ If the switch received its most recent VLAN 1 IP addressing from a DHCP/ Bootp server, it ignores the IP Preserve command when it downloads the configuration file, and implements whatever IP addressing instructions are in the configuration file.
PAGE 152
Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads 8-20
PAGE 153
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 154
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).
PAGE 155
Time Protocols Overview: Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation 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 configured SNTP server. (You can configure one server using the menu interface, or up to three servers using the CLI sntp server command.
PAGE 156
Time Protocols SNTP: Viewing, Selecting, and Configuring Disabling Time Synchronization You can use either of the following methods to disable time synchronization without changing the Timep or SNTP configuration: ■ In the System Information screen of the Menu interface, set the Time Synch Method parameter to None, then press [Enter], then [S] (for Save). ■ In the Global config level of the CLI, execute no timesync.
PAGE 157
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.
PAGE 158
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.
PAGE 159
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.
PAGE 160
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.
PAGE 161
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.
PAGE 162
Time Protocols SNTP: Viewing, Selecting, and Configuring For example, suppose: ■ Time synchronization is in the factory-default configuration (TimeP is the currently selected time synchronization method). ■ You want to: 1. View the current time synchronization. 2. Select SNTP as the time synchronization mode. 3. Enable SNTP for Broadcast mode. 4. View the SNTP configuration again to verify the configuration.
PAGE 163
Time Protocols SNTP: Viewing, Selecting, and Configuring Syntax: timesync sntp Selects SNTP as the time synchronization method. sntp unicast Configures the SNTP mode for Unicast operation. sntp server [version] Specifies the SNTP server. The default server version is 3. no sntp server < ip-addr > Deletes the specified SNTP server. Note Deleting an SNTP server when only one is configured disables SNTP unicast operation.
PAGE 164
Time Protocols SNTP: Viewing, Selecting, and Configuring If the SNTP server you specify uses SNTP version 4 or later, use the sntp server command to specify the correct version number. For example, suppose you learned that SNTP version 4 was in use on the server you specified above (IP address 10.28.227.141). You would use the following commands to delete the server IP address and then re-enter it with the correct version number for that server: Deletes unicast SNTP server entry.
PAGE 165
Time Protocols SNTP: Viewing, Selecting, and Configuring If you then viewed the SNTP configuration, you would see the following: 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 parameter), configure the SNTP mode as disabled. Syntax: no sntp Disables SNTP by changing the SNTP mode configuration to Disabled.
PAGE 166
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.
PAGE 167
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.
PAGE 168
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.
PAGE 169
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.
PAGE 170
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.
PAGE 171
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.
PAGE 172
Time Protocols TimeP: Viewing, Selecting, and Configuring 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. (This parameter is separate from the poll interval parameter used for SNTP operation.) Syntax: ip timep dhcp interval < 1 . . 9999 > ip timep manual interval < 1 . .
PAGE 173
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers 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.
PAGE 174
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers 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.
PAGE 175
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers 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. If there are multiple addresses and you delete one of them, the switch re-orders the address priority.
PAGE 176
Time Protocols SNTP Messages in the Event Log SNTP Messages in the Event Log If an SNTP time change of more than three seconds occurs, the switch’s event log records the change. SNTP time changes of less than three seconds do not appear in the Event Log.
PAGE 177
10 Port Status and Basic Configuration Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Viewing Port Status and Configuring Port Parameters . . . . . . . . . . . . . . . 10-2 Menu: Viewing Port Status and Configuring Port Parameters . . . . . 10-4 CLI: Viewing Port Status and Configuring Port Parameters . . . . . . . 10-6 Using the CLI To View Port Status . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 178
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 ■ QoS Pass-Through Mode ■ Configuring Port-Based Priority for Incoming Packets ■ Using Friendly (Optional) Port Names Viewing Port Status and Configuring Port Parameters Port Status and Configuration Features Note On Connect
PAGE 179
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.
PAGE 180
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Status or Parameter Description Flow Control • Disabled (default): The port does not generate flow control packets, and drops any flow control packets it receives. • Enabled: The port uses 802.3x Link Layer Flow Control, generates flow control packets, and processes received flow control packets.
PAGE 181
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters In this example, ports A7 and A8 have previously been configured as a trunk group. Figure 10-1. Example of the Port Status Screen 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 11, “Port Trunking“. 1. From the Main Menu, Select: 2. Switch Configuration... 2.
PAGE 182
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters 2. Press [E] (for Edit). The cursor moves to the Enabled field for the first port. 3. Refer to the online help provided with this screen for further information on configuration options for these features. 4. When you have finished making changes to the above parameters, press [Enter], then press [S] (for Save).
PAGE 183
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Feature Intrusion Alert Mode (Configured) MDIX Mode Show Interfaces Brief Show Interfaces Config Yes No No Yes Operating Configured * There is also the show interfaces [< port-number >] option, which displays port statistics. Refer to “Viewing Port and Trunk Group Statistics and Flow Control Status” on page B-10.
PAGE 184
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters ProCurve# show interface brief Current Operating Mode Status and Counters - Port Status Port ----1 2 3 4 5 6 7 8 9 10 Type --------100/1000T 100/1000T 100/1000T 100/1000T 100/1000T 100/1000T 100/1000T 100/1000T 100/1000T 100/1000T | | + | | | | | | | | | | Intrusion Alert --------No No No No No No No No No No Enabled ------Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Status -----Down Down Down Down Down Down Down Down
PAGE 185
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Figure 10-7 shows sample output from the show tech transceivers command.
PAGE 186
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters • Transceiver type not supported in this software version. • Not a ProCurve Transceiver. Please go to: www.hp.com/rnd/device_help/2_inform for more info. Displaying Spanning Tree Configuration Details To view detailed statistics on spanning tree operation for different ports, use the show spanning-tree command. Syntax: show spanning-tree detail Lists 802.1D and 802.
PAGE 187
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters ProCurve(config)# int e 6 ProCurve(eth-6)# speed-duplex 100-full If port 8 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.
PAGE 188
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Configures a broadcast limit of 90 on ports 1 - 3 in the running configuration. ProCurve(config)# int 1-3 broadcast-limit 90 ProCurve(config)# show running Running configuration: Displays the broadcastlimit in the running-config file. ; J9019B Configuration Editor; Created on release #Q.11.
PAGE 189
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters If you want more information on this subject please refer to the IEEE 802.3ab Standard Reference. For more information on MDI-X, refer to the appendix titled “Switch Ports and Network Cables” in the Installation and Getting Started Guide for your switch.
PAGE 190
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Syntax: show interfaces brief Where a port is linked to another device, this command lists the MDI mode the port is currently using. In the case of ports configured for Auto (auto-mdix), the MDI mode appears as either MDI or MDIX, depending upon which option the port has negotiated with the device on the other end of the link.
PAGE 191
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Note Port Response to Switch Software Updates ■ Switch software updated from xx.xx.xx or earlier 1. Copper ports in auto-negotiation still default to auto-mdix mode. 2. Copper ports in forced speed/duplex default to mdix mode. The default is auto-mdix. If the switch is reset to the factory defaults, these ports are configured as auto-mdix.
PAGE 192
Port Status and Basic Configuration QoS Pass-Through Mode QoS Pass-Through Mode QoS Pass-Through mode is designed to enhance the performance of line-rate traffic transfers through the switches covered in this guide. This feature should only be used in environments where Quality of Service (QoS) is not of major importance, but where lossless data transfers are key.
PAGE 193
Port Status and Basic Configuration QoS Pass-Through Mode Note ■ High priority packets sourced by the switch itself, such as Spanning Tree packets, will be serviced in the "high" priority queue. ■ Any 802.1p tagging on a received packet, or any tag added to a received frame by the switch via its QoS configuration, will be preserved as it is transmitted from the switch.
PAGE 194
Port Status and Basic Configuration QoS Pass-Through Mode How to enable/disable QoS Pass-Through Mode 2510-48: QoS Pass-Through Mode is enabled by default (Optimized). 2510-24: QoS Pass-Through Mode is disabled by default (Typical). To enable or disable QoS Pass-Through Mode: Syntax: [no] qos-passthrough-mode write memory reload The above command sequence enables QoS pass-through mode. The no form of the command sequence disables QoS pass-through mode.
PAGE 195
Port Status and Basic Configuration QoS Pass-Through Mode Configuring Port-Based Priority for Incoming Packets Feature Default Assigning a priority level to traffic on the basis of incoming port Disabled Menu n/a CLI page 10-22 Web n/a When network congestion occurs, it is important to move traffic on the basis of relative importance. However, without prioritization: ■ Traffic from less important sources can consume bandwidth and slow down or halt delivery of more important traffic.
PAGE 196
Port Status and Basic Configuration QoS Pass-Through Mode Outbound Port Queues and Packet Priority Settings Ports on the ProCurve switches have the following outbound port queue structure: Switch Model Outbound Port Queues Switch 6108 4 Series 5300xl Switch 4 Series 4100gl Switch 3 Series 3400cl Switch Series 2600, 2600-PWR Switch 4 Series 2800 Switch 4 Switch 2810 4 Switch 2510 4 Series 2500 Switch 2 Switches 1600M/2400M/2424M/4000M/8000M 2 As shown below, these port queues map to the
PAGE 197
Port Status and Basic Configuration QoS Pass-Through Mode For example, suppose you have configured port 10 to assign a priority level of 1 (low): Note ■ An untagged packet coming into the switch on port 10 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.
PAGE 198
Port Status and Basic Configuration QoS Pass-Through Mode Configuring and Viewing Port-Based Priority This command enables or disables port-based priority on a per-port basis. You can either enter the command on the interface context level or include the interface in the command. Syntax: interface qos priority < 1 .. 7 > Configures a non-default port-based 802.
PAGE 199
Port Status and Basic Configuration QoS Pass-Through Mode For example, suppose you wanted to configure ports 1-3 on the switch to prioritize all untagged, inbound VLAN traffic as “Low” (priority level = 1; refer to table 10-3 on page 10-20). ProCurve(config)# int 1-3 qos priority 1 ProCurve(config)# write mem ProCurve(config)# show config Startup configuration: ; J9019B Configuration Editor; Created on release #Q.11.
PAGE 200
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 25 n/a n/a n/a page 27 n/a This feature enables you to assign alphanumeric port names of your choosing to augment automatically assigned numeric port names.
PAGE 201
Port Status and Basic Configuration Using Friendly (Optional) Port Names ■ In a port listing, not assigned indicates that the port does not have a name assignment other than its fixed port number. ■ 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.
PAGE 202
Port Status and Basic Configuration Using Friendly (Optional) Port Names Configuring the Same Name for Multiple Ports. Suppose that you want to use ports 5 through 8 as a trunked link to a server used by a drafting group. In this case you might configure ports 5 through 8 with the name “DraftServer:Trunk”. Figure 10-14.
PAGE 203
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 runningconfig file.
PAGE 204
Port Status and Basic Configuration Using Friendly (Optional) Port Names Port Without a "Friendly" Name Friendly port names assigned in previous examples. Figure 10-16. 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.
PAGE 205
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 startupconfig file. (show config does not include ports that have only default settings in the startup-config file.
PAGE 206
Port Status and Basic Configuration Using Friendly (Optional) Port Names 10-30
PAGE 207
11 Port Trunking Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Port Status and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Port Connections and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 Link Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 Port Trunk Options and Operation . . . . . . . . . . . . . . . . . .
PAGE 208
Port Trunking Overview Overview This chapter describes creating and modifying port trunk groups. This includes non-protocol trunks and LACP (802.3ad) trunks.
PAGE 209
Port Trunking Port Status and Configuration The multiple physical links in a trunk behave as one logical link Switch 1: Ports c1 - c4 configured as a port trunk group. port c1 port c2 port c3 port c4 port c5 port c6 port c7 port a1 port a2 port a3 port a4 port a5 port a6 port a7 ... ... port n port n Switch 2: Ports a2 and a4 - a6 are configured as a port trunk group Figure 11-1.
PAGE 210
Port Trunking Port Status and Configuration Fault Tolerance: If a link in a port trunk fails, the switch redistributes traffic originally destined for that link to the remaining links in the trunk. The trunk remains operable as long as there is at least one link in operation. If a link is restored, that link is automatically included in the traffic distribution again.
PAGE 211
Port Trunking Port Status and Configuration Static Trunk: The switch uses the links you configure with the Port/Trunk Settings screen in the menu interface or the trunk command in the CLI to create a static port trunk. The switch offers LACP and Trunk static trunks. Table 11-1. Trunk Types Used in Static and Dynamic Trunk Groups Trunking Method LACP Trunk Dynamic Yes No Static Yes Yes Table 11-2. Trunk Configuration Protocols Protocol Trunking Options LACP (802.
PAGE 212
Port Trunking Port Status and Configuration Table 11-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, ProCurve recommends leaving the port Mode setting at Auto or, in networks using Cat 3 cabling, Auto-10.
PAGE 213
Port Trunking Port Status and Configuration Spanning Tree: Spanning Tree operates as a global setting on the switch (one instance of Spanning Tree per switch). However, you can adjust Spanning Tree parameters on a per-port basis. A static trunk of any type appears in the Spanning Tree configuration display, and you can configure Spanning Tree parameters for a static trunk in the same way that you would configure Spanning Tree parameters on a non-trunked port.
PAGE 214
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.
PAGE 215
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 Parameters” on page 10-2. • You can configure the trunk group with one to eight ports.
PAGE 216
Port Trunking Port Status and Configuration 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 Configuring Port Parameters” on page 10-2.) Check the Event Log (“Using Logging To Identify Problem Sources” on page C-23) to verify that the trunked ports are operating properly.
PAGE 217
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-24.
PAGE 218
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 11-5 on page 11-20.) Figure 11-6. Example of a Show LACP Listing Dynamic LACP Standby Links.
PAGE 219
Port Trunking Port Status and Configuration “Up” Links Standby Link Figure 11-7. 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.
PAGE 220
Port Trunking Port Status and Configuration The following examples show how to create different types of trunk groups. Configuring a Static Trunk or Static LACP Trunk Group. For switches covered in this guide: Syntax: trunk < trk1 ... trk24 > < trunk | lacp > The following example uses ports 4 - 6 to create a non-protocol static trunk group with the group name of Trk2. ProCurve(config)# trunk 4-6 trk2 trunk Removing Ports from a Static Trunk Group.
PAGE 221
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).
PAGE 222
Port Trunking Port Status and Configuration Syntax: no interface lacp In this example, port 6 belongs to an operating, dynamic LACP trunk.
PAGE 223
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.
PAGE 224
Port Trunking Port Status and Configuration Table 11-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 1 to 24 depending on how many dynamic and static trunks are currently on the switch.
PAGE 225
Port Trunking Port Status and Configuration Default Port Operation In the default configuration, LACP is off. The port will not try to detect a trunk configuration and will operate as a standard, untrunked port. Note Passive and active LACP ports 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.
PAGE 226
Port Trunking Port Status and Configuration Table 11-5. LACP Port Status Data Status Name Meaning Port Numb Shows the physical port number for each port configured for LACP operation (1, 2, 3 . . .). Unlisted port numbers indicate that the missing ports are assigned to a static Trunk group or are not configured for any trunking. LACP Enabled Active: The port automatically sends LACP protocol packets.
PAGE 227
Port Trunking Port Status and Configuration LACP Notes and Restrictions 802.1X (Port-Based Access Control) Configured on a Port. To maintain 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.
PAGE 228
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.
PAGE 229
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 specifies 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).
PAGE 230
Port Trunking Port Status and Configuration Interface Option Menu Interface Dynamic LACP Trunk Group Static LACP Static Non-Protocol Trunk Group Trunk Group No Yes Yes show trunks No Yes Yes show interfaces No Yes Yes show lacp Yes Yes No show spanning-tree No Yes Yes show igmp No Yes Yes show config No Yes Yes CLI: Outbound Traffic Distribution Across Trunked Links Both trunk group options (LACP and Trunk) use source-destination address pairs (SA/DA) for distributing outboun
PAGE 231
Port Trunking Port Status and Configuration A B C D C1 Switch C 2 C3 W X Y Z Switch Figure 11-10. Example of Port-Trunked Network Table 11-6.
PAGE 232
Port Trunking Port Status and Configuration 11-26
PAGE 233
12 Configuring for Network Management Applications Contents Using SNMP Tools To Manage the Switch . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 SNMP Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4 Configuring for SNMP Access to the Switch . . . . . . . . . . . . . . . . . . . . 12-4 Configuring for SNMP Version 3 Access to the Switch . . . . .
PAGE 234
Configuring for Network Management Applications Contents Configuring LLDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . Configuring Global LLDP Packet Controls . . . . . . . . . . . . . . . . . Configuring SNMP Notification Support . . . . . . . . . . . . . . . . . . . Configuring Per-Port Transmit and Receive Modes . . . . . . . . . Configuring Basic LLDP Per-Port Advertisement Content . . . .
PAGE 235
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 ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+). For more on PCM and PCM+, visit the ProCurve web site at: www.procurve.com Click on ProCurve Products, then click on the Network Management tab.
PAGE 236
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch ■ Security via configuration of SNMP communities (page 12-4) ■ Security via authentication and privacy for SNMP Version 3 access ■ Event reporting via SNMP • Version 1 traps • RMON ■ ProCurve Manager/Plus support ■ Flow sampling using either EASE ■ Standard MIBs, such as the Bridge MIB (RFC 1493), Ethernet MAU MIB (RFC 1515), and others The switch SNMP agent also uses certain variables that are included in a
PAGE 237
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Caution The “public” community exists by default and is used by ProCurve’s network management applications. Deleting the “public” community disables many network management functions (such as auto-discovery, traffic monitoring, SNMP trap generation, and threshold setting). If security for network management is a concern, it is recommended that you change the write access for the “public” community to “Restricted”.
PAGE 238
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Commands SNMP version 3 (SNMPv3) adds new commands to the CLI for configuring SNMPv3 functions. You can: Caution ■ Enable SNMPv3 with the snmpv3 enable command. An initial user entry will be generated with MD5 authentication and DES privacy. ■ Restrict access to only SNMPv3 agents with the snmpv3 only command.
PAGE 239
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 12-1 shows and example of this dialog.
PAGE 240
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.
PAGE 241
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 group group_name user user_name sec-model 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.
PAGE 242
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 12-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 12-3.
PAGE 243
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.
PAGE 244
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Communities SNMP commuities are supported by the switch to allow management application 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 12-11.
PAGE 245
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Figure 12-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 12-4. Assigning a Community to a Group Access Level Table 12-1.
PAGE 246
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Caution Deleting or changing the community named “public” prevents network management 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.
PAGE 247
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 12-6.
PAGE 248
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 [] 12-16 [no] snmp-server 12-17 [community ] 12-17 [host ] [] 12-22 [enable traps 12-23 Listing Community Names and Values.
PAGE 249
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.
PAGE 250
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 1 or version 2c traps, see “Trap Features” on page 12-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.
PAGE 251
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 targetaddress params < params-name> < IP-Addr > 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. Note: You are only allowed up to 103 characters for this value.
PAGE 252
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 12-22 — snmp-server enable (authentication trap) none — page 12-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.
PAGE 253
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 12-12). Syntax: show snmp-server Displays current community and trap receiver data.
PAGE 254
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 assignment.
PAGE 255
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: ProCurve(config)# snmp-server 10.28.227.130 critical Notes trap-receiver red-team 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.
PAGE 256
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 optimizing your network.
PAGE 257
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP (Link-Layer Discovery Protocol) To standardize device discovery on all ProCurve switches, LLDP has been implemented while offering limited read-only support for CDP as documented in this manual. For current information on your switch model, consult the latest Release Notes (available on the ProCurve Networking web site).
PAGE 258
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Also, by using show commands to access the switch’s neighbor database for information collected by an individual switch, system administrators can learn about other devices connected to the switch, including device type (capability) and some configuration information. Terminology Adjacent Device: Refer to “Neighbor or Neighbor Device”. Advertisement: See LLDPDU.
PAGE 259
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) NANP (North American Numbering Plan): A ten-digit telephone number format where the first three digits are an area code and the last seven-digits are a local telephone number. Neighbor: See “LLDP Neighbor”. Non-LLDP Device: A device that is not capable of LLDP operation. PD (Powered Device): This is an IEEE 802.
PAGE 260
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Packet Boundaries in a Network Topology ■ Where multiple LLDP devices are directly connected, an outbound LLDP packet travels only to the next LLDP device. An LLDP-capable device does not forward LLDP packets to any other devices, regardless of whether they are LLDP-enabled. ■ An intervening hub or repeater forwards the LLDP packets it receives in the same manner as any other multicast packets it receives.
PAGE 261
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) ■ Receive only (rxonly): This setting enables a port to receive and read LLDP packets from LLDP neighbors, and to store the packet data in the switch’s MIB. However, the port does not transmit outbound LLDP packets. This prevents LLDP neighbors from learning about the switch through that port. ■ Disable (disable): This setting disables LLDP packet transmissions and reception on a port.
PAGE 262
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Data Type Configuration Options Default Description System Description6 Enable/Disable Enabled Includes switch model name and running software version, and ROM version. Port Description6 Enable/Disable Enabled Uses the physical port identifier. System capabilities supported5, 6 Enable/Disable Enabled Identifies the switch’s primary capabilities (bridge, router).
PAGE 263
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Standards Compatibility The operation covered by this section is compatible with these standards: ■ IEEE P802.1AB ■ RFC 2922 (PTOPO, or Physical Topology MIB) ■ RFC 2737 (Entity MIB) ■ RFC 2863 (Interfaces MIB) LLDP Operating Rules Port Trunking. LLDP manages trunked ports individually. That is, trunked ports are configured individually for LLDP operation, in the same manner as non-trunked ports.
PAGE 264
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Spanning-Tree Blocking. Spanning tree does not prevent LLDP packet transmission or receipt on STP-blocked links. 802.1X Blocking. Ports blocked by 802.1X operation do not allow transmission or receipt of LLDP packets. Configuring LLDP Operation In the default configuration, LLDP is enabled and in both transmit and receive mode on all active ports.
PAGE 265
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) For example, show lldp config produces the following display when the switch is in the default LLDP configuration: Note: This value corresponds to the lldp refresh-interval command (page 12-35). Med Topology Trap Enabled ------------------------False True False False True False False Figure 12-10.
PAGE 266
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying Port Configuration Details. This command displays the portspecific configuration, including. Syntax show lldp config < port-list > Displays the LLDP port-specific configuration for all ports in < port-list >, including which optional TLVs and any non-default IP address that are included in the port’s outbound advertisements.
PAGE 267
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Configuring Global LLDP Packet Controls The commands in this section configure the aspects of LLDP operation that apply the same to all ports in the switch. Enabling or Disabling LLDP Operation on the Switch. Enabling LLDP operation (the default) causes the switch to: ■ Use active, LLDP-enabled ports to transmit LLDP packets describing itself to neighbor devices.
PAGE 268
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Changing the Time-to-Live for Transmitted Advertisements. The Time-to-Live value (in seconds) for all LLDP advertisements transmitted from a switch is controlled by the switch that generates the advertisement, and determines how long an LLDP neighbor retains the advertised data before discarding it. The Time-to-Live value is the result of multiplying the refreshinterval by the holdtime-multiplier described below.
PAGE 269
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax setmib lldpTxDelay.0 -i < 1 - 8192 > Uses setmib to change the minimum time (delay-interval) any LLDP port will delay advertising successive LLDP advertisements due to a change in LLDP MIB content. (Default: 2; Range: 1 - 8192) Note: The LLDP refresh-interval (transmit interval) must be greater than or equal to (4 x delay-interval).
PAGE 270
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) delay interval delays the port’s ability to reinitialize and generate LLDP traffic following an LLDP disable/enable cycle. Syntax setmib lldpReinitDelay.0 -i < 1 - 10 > Uses setmib to change the minimum time (reinitialization delay interval) an LLDP port will wait before reinitializing after receiving an LLDP disable command followed closely by a txonly or tx_rx command.
PAGE 271
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Changing the Minimum Interval for Successive Data Change Notifications for the Same Neighbor. If LLDP trap notification is enabled on a port, a rapid succession of changes in LLDP information received in advertisements from one or more neighbors can generate a high number of traps. To reduce this effect, you can globally change the interval between successive notifications of neighbor data change.
PAGE 272
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Configuring Basic LLDP Per-Port Advertisement Content In the default LLDP configuration, outbound advertisements from each port on the switch include both mandatory and optional data. Mandatory Data. An active LLDP port on the switch always includes the mandatory data in its outbound advertisements.
PAGE 273
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) For example, if port 3 belongs to a subnetted VLAN that includes an IP address of 10.10.10.100 and you wanted port 3 to use this secondary address in LLDP advertisements, you would need to execute the following command: ProCurve(config)# lldp config 3 ipAddrEnable 10.10.10.100 Optional Data. You can configure an individual port or group of ports to exclude one or more of these data types from outbound LLDP advertisements.
PAGE 274
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) system_descr For outbound LLDP advertisements, this TLV includes an alphanumeric string describing the full name and version identification for the system’s hardware type, software version, and networking application. (Default: Enabled) system_cap For outbound advertisements, this TLV includes a bitmask of supported system capabilities (device functions). Also includes information on whether the capabilities are enabled.
PAGE 275
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: [ no ] lldp config < port-list > dot3TlvEnable macphy_config For outbound advertisements, this TLV includes the (local) switch port’s current speed and duplex settings, the range of speed and duplex settings the port supports, and the method required for reconfiguring the speed and duplex settings on the device (auto-negotiation during link initialization, or manual configuration).
PAGE 276
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying Switch Information Available for Outbound Advertisements These commands display the current switch information that will be used to populate outbound LLDP advertisements. Syntax show lldp info local-device [ port-list ] Without the [ port-list ] option, this command displays the global switch information and the per-port information currently available for populating outbound LLDP advertisements.
PAGE 277
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) The Management Address field displays only the LLDP-configurable IP addresses on the switch. (Only manually-configured IP addresses are LLDP-configurable.) If the switch has only an IP address from a DHCP or Bootp server, then the Management Address field is empty (because there are no LLDPconfigurable IP addresses available). For more on this topic, refer to “Remote Management Address” on page 12-30. Figure 12-13.
PAGE 278
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: show interfaces brief < port-list > Includes port speed and duplex configuration in the Mode column of the resulting display. Displaying Advertisements Currently in the Neighbors MIB. These commands display the content of the inbound LLDP advertisements received from other LLDP devices.
PAGE 279
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Figure 12-15.
PAGE 280
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying LLDP Statistics LLDP statistics are available on both a global and a per-port levels. Rebooting the switch resets the LLDP statistics counters to zero. Disabling the transmit and/or receive capability on a port “freezes” the related port counters at their current values.
PAGE 281
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) — Continued — Per-Port LLDP Counters: NumFramesRecvd: Shows the total number of valid, inbound LLDP advertisements received from any neighbor(s) on < portlist >. Where multiple neighbors are connected to a port through a hub, this value is the total number of LLDP advertisements received from all sources. NumFramesSent: Shows the total number of LLDP advertisements sent from [ port-list ].
PAGE 282
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Counters showing frames sent on a port but no frames received on that port indicates an active link with a device that either has LLDP disabled on the link or is not LLDPaware. Figure 12-16. Example of a Global LLDP Statistics Display Figure 12-17.
PAGE 283
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Operating Notes Neighbor Maximum. The neighbors table in the switch supports as many neighbors as there are ports on the switch.
PAGE 284
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP and CDP Data Management This section describes points to note regarding LLDP (Link-Layer Discovery Protocol) and CDP (Cisco Discovery Protocol) data received by the switch from other devices. LLDP operation includes both transmitting LLDP packets to neighbor devices and reading LLDP packets received from neighbor devices. CDP operation is limited to reading incoming CDP packets from neighbor devices.
PAGE 285
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Note Because ProCurve switches do not generate CDP packets, they are not represented in the CDP data collected by any neighbor devices running CDP. A switch with CDP disabled forwards the CDP packets it receives from other devices, but does not store the CDP information from these packets in its own MIB. LLDP data transmission/collection and CDP data collection are both enabled in the switch’s default configuration.
PAGE 286
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) CDP Operation and Commands By default the switches covered by this guide have CDP enabled on each port. This is a read-only capability, meaning that the switch can receive and store information about adjacent CDP devices but does not generate CDP packets.
PAGE 287
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) The following example shows the default CDP configuration. CDP Enable/Disable on the Switch Per-Port CDP Enable/Disable Figure 12-18. Example of Show CDP with the Default CDP Configuration Viewing the Switch’s Current CDP Neighbors Table. Devices are listed by the port on which they were detected.
PAGE 288
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Enabling CDP Operation. Enabling CDP operation (the default) on the switch causes the switch to add entries to its CDP Neighbors table for any CDP packets it receives from other neighboring CDP devices. Disabling CDP Operation. Disabling CDP operation clears the switch’s CDP Neighbors table and causes the switch to drop inbound CDP packets from other devices without entering the data in the CDP Neighbors table.
PAGE 289
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 . . . . . . .
PAGE 290
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.
PAGE 291
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 implement 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.
PAGE 292
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.
PAGE 293
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.
PAGE 294
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 N_10_XX_A_031706.swi from a TFTP server with the IP address of 10.28.
PAGE 295
File Transfers Downloading Switch Software If you need information on primary/secondary flash memory and the boot commands, refer to “Using Primary and Secondary Flash Image Options” on page 6-12. Using Secure Copy and SFTP 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).
PAGE 296
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.
PAGE 297
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.
PAGE 298
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.
PAGE 299
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.
PAGE 300
File Transfers Downloading Switch Software Menu: Xmodem Download to Primary Flash Note that the menu interface accesses only the primary flash. 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.
PAGE 301
File Transfers Downloading Switch Software CLI: Xmodem Download from a PC or Unix Workstation to Primary or Secondary Flash Using Xmodem and a terminal emulator, you can download a switch software file to either primary or secondary flash. Syntax: copy xmodem flash [< 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 G0103.
PAGE 302
File Transfers Downloading Switch Software 4. To confirm that the operating system downloaded correctly, use the show system, show version, or show flash CLI commands. Check the Firmware revision line. It should show the switch software version that you downloaded in the preceding steps. If you need information on primary/secondary flash memory and the boot commands, refer to “Using Primary and Secondary Flash Image Options” on page 6-12.
PAGE 303
File Transfers Downloading Switch Software 7. After the primary flash memory has been updated with the new operating system, you must reboot the switch to implement the newly downloaded software. From the Main Menu, press [6] (for Reboot Switch). You will then see this prompt: Continue reboot of system? : No Press the space bar once to change No to Yes, then press [Enter] to begin the reboot. 8. To confirm that the operating system downloaded correctly: a.
PAGE 304
File Transfers Downloading Switch Software Running Total of Bytes Downloaded Figure A-5. Switch-To-Switch, from Primary in Source to Either Flash in Destination Downloading from Either Flash in the Source Switch to Either Flash in the Destination Switch. This command (executed in the destination switch) gives you the most options for downloading between switches.
PAGE 305
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.
PAGE 306
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.
PAGE 307
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 sw2510 in the configs directory on drive “d” in a remote host having an IP address of 10.28.227.105: ProCurve# copy startup-config tftp 10.28.227.
PAGE 308
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.
PAGE 309
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.
PAGE 310
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.
PAGE 311
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.
PAGE 312
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation A-24
PAGE 313
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 . . . . . . . . . . . . . . . . . .
PAGE 314
Monitoring and Analyzing Switch Operation Contents Port and Static Trunk Monitoring Features . . . . . . . . . . . . . . . . . . . . . . . B-23 Menu: Configuring Port and Static Trunk Monitoring . . . . . . . . . . . B-24 CLI: Configuring Port and Static Trunk Monitoring . . . . . . . . . . . . . B-26 Monitoring Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26 Web: Configuring Port Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28 Locating a Device . .
PAGE 315
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, management 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).
PAGE 316
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.
PAGE 317
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 selecting: 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.
PAGE 318
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.
PAGE 319
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.
PAGE 320
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.
PAGE 321
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.
PAGE 322
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
PAGE 323
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.
PAGE 324
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 command provides traffic details for the port(s) you specify. Syntax: show interfaces [ethernet] < port-list > To Reset the Port Counters for a Specific Port.
PAGE 325
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-13 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-16 — 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
PAGE 326
Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-8. Example of the Address Table To page through the listing, use Next page and Prev page. 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].
PAGE 327
Monitoring and Analyzing Switch Operation Status and Counters Data Port-Level MAC Address Viewing and Searching. This feature displays and searches for MAC addresses on the specified port instead of for all ports on the switch. 1. From the Main Menu, select: 1. Status and Counters 7. Port Address Table Prompt for Selecting the Port To Search Figure B-10. Listing MAC Addresses for a Specific Port 2.
PAGE 328
Monitoring and Analyzing Switch Operation Status and Counters Data CLI Access for MAC Address Views and Searches Syntax: show mac-address [vlan < vlan-id >] [ethernet]< port-list >] [< mac-addr >] To List All Learned MAC Addresses on the Switch, with The Port Number on Which Each MAC Address Was Learned. ProCurve> show mac-address To List All Learned MAC Addresses on one or more ports, with Their Corresponding Port Numbers.
PAGE 329
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.
PAGE 330
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).
PAGE 331
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
PAGE 332
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
PAGE 333
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.
PAGE 334
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 utilization 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.
PAGE 335
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-24 page B-26 page B-28 configure the monitor port(s) ports: none page B-24 page B-27 page B-28 selecting or removing ports page B-24 page B-27 page B-28 none selected You can designate a port for monitoring inbound (ingress) and outbound (egress) traffic of other ports
PAGE 336
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 monitoring 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.
PAGE 337
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 5. Use the Space bar to select the port to use for monitoring. 6. Use the down arrow 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.
PAGE 338
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-27 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.
PAGE 339
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Configuring the Monitor Port. This command assigns or removes a monitoring port, and must be executed from the global configuration level. Removing the monitor port disables port monitoring and resets the monitoring parameters to their factory-default settings.
PAGE 340
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features These two commands show how to disable monitoring at the interface context level for a single port or all ports in an interface context level. These two commands show how to disable monitoring at the global config level for a single port or a group of ports . Figure B-23. Examples of Removing Ports as Monitoring Sources Web: Configuring Port Monitoring To enable port monitoring: 1. Click on the Configuration tab. 2.
PAGE 341
Monitoring and Analyzing Switch Operation Locating a Device Locating a Device If you are trying to locate a particular switch you can enter the chassislocate command. The blue Locator LED will light up on that switch. Syntax: chassislocate [ blink | on | off ] Locate a device by using the blue Locate LED on the front panel. blink <1-1440> Blinks the chassis Locate LED for a selected number of minutes (default is 30 minutes).
PAGE 342
Monitoring and Analyzing Switch Operation Locating a Device Locator LED Figure B-25.
PAGE 343
C Troubleshooting Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Troubleshooting Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Chassis Over-Temperature Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 Browser or Telnet Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7 Unusual Network Activity . . . . . . . . . . . . . . . . . . . . . .
PAGE 344
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 . . . . . . .
PAGE 345
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 and Getting Started Guide you received with the switch.
PAGE 346
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 and Getting Started Guide shipped with the switch for correct cable types and connector pin-outs.
PAGE 347
Troubleshooting Chassis Over-Temperature Detection Chassis Over-Temperature Detection i. If a switch 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 servers). If the switch later returns to its acceptable temperature range, it signals this event with a chassis module Information message to the same destinations.
PAGE 348
Troubleshooting Chassis Over-Temperature Detection ■ C-6 If there are no fan failures, ensure that the ambient temperature in the switch’s operating area is not causing the over-temperature condition. If the condition persists, remove power from the switch until you can find the cause and apply an effective remedy.
PAGE 349
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.
PAGE 350
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.
PAGE 351
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.
PAGE 352
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.
PAGE 353
Troubleshooting Unusual Network Activity IP Multicast Traffic Floods Out All Ports; IGMP Does Not Appear To Filter Traffic. The IGMP feature does not operate if the switch or VLAN does not have an IP address configured manually or obtained through DHCP/ Bootp. To verify whether an IP address is configured for the switch or VLAN, do either of the following: ■ Try Using the Web Browser Interface: If you can access the web browser interface, then an IP address is configured.
PAGE 354
Troubleshooting Unusual Network Activity Port-Based Access Control (802.1X)-Related Problems Note To list the 802.1X port-access Event Log messages stored on the switch, use show log 802. See also “Radius-Related Problems” on page C-15. The switch does not receive a response to RADIUS authentication requests. In this case, the switch will attempt authentication using the secondary method configured for the type of access you are using (console, Telnet, or SSH).
PAGE 355
Troubleshooting Unusual Network Activity The switch appears to be properly configured as a supplicant, but cannot gain access to the intended authenticator port on the switch to which it is connected. If aaa authentication port-access is configured for Local, ensure that you have entered the local login (operator-level) username and password of the authenticator switch into the identity and secret parameters of the supplicant configuration.
PAGE 356
Troubleshooting Unusual Network Activity 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-3. Example of How To List the Global and Server-Specific Radius Encryption Keys Also, ensure that the switch port used to access the RADIUS server is not blocked by an 802.
PAGE 357
Troubleshooting Unusual Network Activity Radius-Related Problems The switch does not receive a response to RADIUS authentication requests. In this case, the switch will attempt authentication using the secondary method configured for the type of access you are using (console, Telnet, or SSH). There can be several reasons for not receiving a response to an authentication request. Do the following: ■ Use ping to ensure that the switch has access to the configured RADIUS server.
PAGE 358
Troubleshooting Unusual Network Activity Spanning-Tree Protocol (STP) and Fast-Uplink Problems Caution If you enable STP, it is recommended that you leave the remainder of the STP parameter settings at their default values until you have had an opportunity to evaluate STP performance in your network. Because incorrect STP settings can adversely affect network performance, you should avoid making changes without having a strong understanding of how STP operates.
PAGE 359
Troubleshooting Unusual Network Activity SSH-Related Problems Switch access refused to a client. Even though you have placed the client’s public key in a text file and copied the file (using the copy tftp pub-keyfile command) into the switch, the switch refuses to allow the client to have access. If the source SSH client is an SSHv2 application, the public key may be in the PEM format, which the switch (SSHv1) does not interpret.
PAGE 360
Troubleshooting Unusual Network Activity The public key file you are trying to download has one of the following problems: ■ A key in the file is too long. The maximum key length is 1024 characters, including spaces. This could also mean that two or more keys are merged together instead of being separated by a . ■ There are more than ten public keys in the key file. ■ One or more keys in the file is corrupted or is not a valid rsa public key.
PAGE 361
Troubleshooting Unusual Network Activity memory to save the authentication configuration to flash, then pressing the Reset button or cycling the power reboots the switch with the boot-up configuration. ■ Disconnect the switch from network access to any TACACS+ servers and then log in to the switch using either Telnet or direct console port access. Because the switch cannot access a TACACS+ server, it will default to local authentication.
PAGE 362
Troubleshooting Unusual Network Activity ■ The access attempt is outside of the time frame allowed for the account. ■ The allowed number of concurrent logins for the account has been exceeded For more help, refer to the documentation provided with your TACACS+ server application. Unknown Users Allowed to Login to the Switch. Your TACACS+ application may be configured to allow access to unknown users by assigning them the privileges included in a default user profile.
PAGE 363
Troubleshooting Unusual Network Activity None of the devices assigned to one or more VLANs on an 802.1Qcompliant switch are being recognized. If multiple VLANs are being used on ports connecting 802.1Q-compliant devices, inconsistent VLAN IDs may have been assigned to one or more VLANs. For a given VLAN, the same VLAN ID must be used on all connected 802.1Q-compliant devices. Link Configured for Multiple VLANs Does Not Support Traffic for One or More VLANs.
PAGE 364
Troubleshooting Unusual Network Activity Note that attempting to create redundant paths through the use of VLANs will cause problems with some switches. One symptom is that a duplicate MAC address appears in the Port Address Table of one port, and then later appears on another port.
PAGE 365
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 chronological 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 10:52:32 System Module ports: Event Message port A1 enabled Figure C-7.
PAGE 366
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.
PAGE 367
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.
PAGE 368
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] [] ProCurve> show logging Lists recorded log messages since last reboot. ProCurve> show logging -a Lists all recorded log messages, including those before the last reboot.
PAGE 369
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 ProCurve(Config)# debug destination session ProCurve(Config)# EVNT I 01/01/06 05:03:45 ports: port 17 is now off-line EVNT I 01/01/06 05:03:45 vlan: VLAN_20 virtual LAN disabled EVNT I 01/01/06
PAGE 370
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 configured debug destination(s). (Default: Disabled) event Configures the switch to send Event Log messages to the configured debug destination(s).
PAGE 371
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.
PAGE 372
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.
PAGE 373
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.
PAGE 374
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.
PAGE 375
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.
PAGE 376
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.
PAGE 377
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.
PAGE 378
Troubleshooting Diagnostic Tools Web: Executing Ping or Link Tests 1. Click here. 2. Click here. 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. 3. Select Ping Test (the default) or Link Test. 6. Click on Start to begin the test. 5. Select the number of tries (packets) and the timeout for each try from the drop-down menus. Figure C-14.
PAGE 379
Troubleshooting Diagnostic Tools 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 repetitions and timeout periods.
PAGE 380
Troubleshooting Diagnostic Tools Link Tests. You can issue single or multiple link tests with varying repetitions 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.
PAGE 381
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”.
PAGE 382
Troubleshooting Diagnostic Tools Listing Switch Configuration and Operation Details for Help in Troubleshooting The show tech command outputs, in a single listing, switch operating and running configuration details from several internal switch sources, including: ■ Image stamp (software version data) ■ Running configuration ■ Event Log listing ■ Boot History ■ Port settings ■ Status and counters — port status ■ IP routes ■ Status and counters — VLAN information ■ GVRP support ■ Load bala
PAGE 383
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: ProCurve# show tech Note a.
PAGE 384
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).
PAGE 385
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. This process momentarily interrupts the switch operation, clears any passwords, clears the console event log, resets the network counters to zero, performs a complete self test, and reboots the switch into its factory default configuration including deleting an IP address.
PAGE 386
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.
PAGE 387
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. b. 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].
PAGE 388
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.
PAGE 389
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 the MAC Addresses of Connected Devices . . . . . . . . . . . . . . . . .
PAGE 390
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.
PAGE 391
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.
PAGE 392
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.
PAGE 393
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.205Base MAC Address (MAC Address for default VLAN; VID = 1) ifPhysAddress.226 & 237MAC Addresses for non-default VLANs. Figure D-2.
PAGE 394
MAC Address Management Viewing the MAC Addresses of Connected Devices Viewing the MAC Addresses of Connected Devices 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). [ mac-addr ] Lists the port on which the switch detects the specified MAC address.
PAGE 395
MAC Address Management Viewing the MAC Addresses of Connected Devices To list the MAC addresses of devices the switch has detected, use the show mac-address command. For example, ProCurve(config)# show mac-address Status and Counters - Port Address Table MAC Address Located on Port ------------- --------------001e6-09620c 1 0001e7-61d4c0 2 0001e7-6025c0 3 Figure D-3.
PAGE 396
MAC Address Management Viewing the MAC Addresses of Connected Devices D-8
PAGE 397
E Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time This information applies to the following ProCurve switches: • • • • • • • • • • • 2510 2512 2524 2626 2650 2626-PWR 2650-PWR 2810 2510 2824 2848 • • • • • • 3400cl 4108gl 4104gl 6108 5304xl 5308xl • • • • • • • 1600M 2400M 2424M 4000M 8000M 212M 224M • ProCurve AdvanceStack Switches • ProCurve AdvanceStack Routers ProCurve switches provide a way to automatically adjust the system clock for Daylight Savings Time (DST) cha
PAGE 398
Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time Canada and Continental US: • Begin DST at 2am on the second Sunday in March. • End DST at 2am on the first Sunday in November. 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. • End DST at 2am the first Sunday on or after March 1st.
PAGE 399
Daylight Savings Time on 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.
PAGE 400
Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time E-4
PAGE 401
Index Symbols => prompt … C-44 Numerics 802.1X LLDP blocked … 12-32 802.1X effect, LLDP … 12-51 A access manager … 12-13 operator … 12-13 Actions line … 3-9, 3-10, 3-11 location on screen … 3-9 address table, port … B-13 address, network manager … 12-4, 12-5 alert log … 5-20 alert types … 5-21 disabling … 5-25 setting the sensitivity level … 5-24 sorting the entries … 5-20 applicable products … 1-ii asterisk … 3-10, 3-13 authentication trap … 12-20, 12-23 See also SNMP.
PAGE 402
configuration … 3-7 Bootp … 8-14 comparing startup to running … 6-5 console … 7-3 copying … A-18 download … A-3 factory default … 6-8, 8-2 IP … 8-3 network monitoring … B-23 permanent … 6-6 permanent change defined … 6-4 port … 10-1, 11-1 port trunk groups … 10-1, 11-1 quick … 3-8 reboot to activate … 3-13 restoring factory defaults … C-43 saving from menu interface … 3-10 serial link … 7-3 SNMP … 12-4, 12-5, 12-12 SNMP communities … 12-14, 12-16 startup … 3-10 system … 7-11 Telnet access configuration … 7-
PAGE 403
E I Emergency Location Identification Number … 12-26 ending a console session … 3-5 event log … 3-7, C-23 navigation … C-25 See also debug logging. severity level … C-23 temperature messages … C-5 use during troubleshooting … C-23 with debug … C-33 IEEE 802.1d … C-16 IEEE 802.3ab … 10-3 IEEE P802.
PAGE 404
K kill command … 7-10 L LACP 802.
PAGE 405
packet dropped … 12-28 packet time-to-live … 12-30 packet-forwarding … 12-28 packets not forwarded … 12-26 per-port counters … 12-49 port description … 12-41 port ID … 12-40 port speed … 12-42 port trunks … 12-31 port type … 12-40 refresh interval … 12-35 reinitialization delay … 12-37 remote management address … 12-30 remote manager address … 12-40 reset counters … 12-48 rxonly … 12-39 setmib, delay interval … 12-36 setmib, reinit delay … 12-38 show advertisement data … 12-43 show commands … 12-32, 12-34 s
PAGE 406
network management functions … 12-5 network manager address … 12-4, 12-5 network monitoring traffic overload … B-23 Network Monitoring Port screen … B-23 network slow … C-9 North American Numbering Plan … 12-27 Not Current One, debug session … C-33 notices … 1-ii O online help … 5-13 online help location … 5-13 operation not allowed, LACP … C-11 operator access … 12-13 operator password … 5-8, 5-10 OS version … A-5, A-12, A-15 OS download failure indication … A-17 switch-to-switch download … A-14 troublesh
PAGE 407
STP … 11-7 STP operation … 11-6 traffic distribution … 11-6 Trk1 … 11-6 trunk (non-protocol) option … 11-5 trunk option described … 11-23 types … 11-5 VLAN … 11-7 VLAN operation … 11-6 web browser access … 11-16 port trunk group interface access … 10-1, 11-1 port, active … 12-26 port-based access control event log … C-12 LACP not allowed … 11-21 troubleshooting … C-12 port-based priority 802.
PAGE 408
show tech … C-40 slow network … C-9 SNMP … 12-3 CLI commands … 12-13 communities … 12-4, 12-5, 12-12, 12-13, 12-14 configure … 12-4, 12-5 IP … 12-3 notification, LLDP SNMP notification … 12-29 public community … 12-5, 12-14 restricted access … 12-14 thresholds … 12-20 traps … 12-4, 12-20 traps, well-known … 12-20 SNMP communities configuring with the CLI … 12-16 configuring with the menu … 12-14 SNMP trap, LLDP … 12-38 SNMPv3 "public" community access caution … 12-6 access … 12-5 assigning users to groups …
PAGE 409
Syslog facility, user … C-34 See debug logging.
PAGE 410
version, OS … A-5, A-12, A-15 view transceiver status … 10-8 VLAN … 8-4, C-22, D-2 address … 12-3 Bootp … 8-14 configuring Bootp … 8-14 device not seen … C-21 event log entries … C-23 link blocked … C-16 management VLAN, SNMP block … 12-3 monitoring … B-3 multinetting … 8-9 multiple … 12-3 multiple IP addresses … 8-9 OS download … A-3 port configuration … C-21 primary … 8-4 reboot required … 3-8 subnet … 8-9 support enable/disable … 3-8 tagging broadcast, multicast, and unicast traffic … C-20 VLAN ID … 4-16
PAGE 411
PAGE 412
Technical information in this document is subject to change without notice. © Copyright 2008 Hewlett-Packard Development Company, L.P. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited except as allowed under the copyright laws.