Page 1 Management and Configuration Guide 2610 2610-PWR ProCurve Switches R.11.XX www.procurve.com...
Page 3 ProCurve Switch 2610 Series Switch 2610-PWR Series December 2007 Management and Configuration Guide...
Page 4 Applicable Products The only warranties for HP products and services are set forth in the express warranty statements accompanying ProCurve Switch 2610-24 (J9085A) such products and services. Nothing herein should be ProCurve Switch 2610-48 (J9088A) construed as constituting an additional warranty.
Page 5: Table Of Contents
Advantages of Using the Web Browser Interface ..... 2-5 Advantages of Using ProCurve Manager or ProCurve Manager Plus ..2-6 3 Using the Menu Interface Contents .
Page 6 Starting a Web Browser Interface Session with the Switch ... . 5-4 Using a Standalone Web Browser in a PC or UNIX Workstation ..5-4 Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) 5-5...
Page 7 Tasks for Your First Web Browser Interface Session ....5-7 Viewing the “First Time Install” Window ......5-7 Creating Usernames and Passwords in the Browser Interface .
Page 8 Rebooting the Switch ........6-18 Operating Notes .
Page 9 8 Configuring IP Addressing Contents ............8-1 Overview .
Page 10 CLI: Viewing and Configuring TimeP ......9-16 Viewing the Current TimeP Configuration ....9-17 Configuring (Enabling or Disabling) the TimeP Mode .
Page 11 Configuring Port-Based Priority for Incoming Packets ....10-28 The Role of 802.1Q VLAN Tagging ......10-28 Outbound Port Queues and Packet Priority Settings .
Page 12 Displaying the PoE Status on Specific Ports ....11-12 Planning and Implementing a PoE Configuration ....11-13 Assigning PoE Ports to VLANs .
Page 13 SNMP Version 3 Commands ....... . . 13-6 SNMPv3 Enable ........13-7 SNMP Version 3 Users .
Page 14 CLI: Switch-To-Switch Downloads ..... . . A-15 Using ProCurve Manager Plus to Update Switch Software ..A-16 Troubleshooting TFTP Downloads .
Page 15 B Monitoring and Analyzing Switch Operation Contents ............B-1 Overview .
Page 16 C Troubleshooting Contents ............C-1 Overview .
Page 17 Viewing the MAC Addresses of Connected Devices ....D-6 E Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time ....... E-1...
Page 18 xvi...
Page 19: Product Documentation
Electronic Publications The latest version of each of the publications listed below is available in PDF format on the ProCurve Web site, as described in the Note at the top of this page. Management and Configuration Guide—Describes how to configure, ■...
Page 20: Software Feature Index
Product Documentation Software Feature Index For the software 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...
Page 21 Product Documentation Feature Management and Advanced Traffic Access Security Configuration Management Guide File Transfers Friendly Port Names GVRP IGMP Interface Access (Telnet, Console/Serial, Web) Jumbo Packets IP Addressing IP Routing LACP Link LLDP LLDP-MED MAC Address Management MAC Lockdown MAC Lockout MAC-based Authentication Monitoring and Analysis Multicast Filtering...
Page 22 Product Documentation Feature Management and Advanced Traffic Access Security Configuration Management Guide Port-Based Access Control Port-Based Priority (802.1Q) Power over Ethernet (PoE) Quality of Service (QoS) RADIUS ACLs RADIUS Authentication and Accounting Routing Secure Copy sFlow SFTP SNMP Software Downloads (SCP/SFTP, TFTP, Xmodem) Source-Port Filters Spanning Tree (STP, RSTP, MSTP) SSH (Secure Shell) Encryption...
Page 23 Product Documentation Feature Management and Advanced Traffic Access Security Configuration Management Guide VLANs Web-based Authentication Xmodem...
Page 24 Product Documentation xxii...
Page 25 Getting Started Contents Introduction ........... 1-2 Conventions .
Page 26: Getting Started
For an overview of other product documentation for the above switches, refer to “Product Documentation” on page xvii. You can download a copy from the ProCurve website, www.procurve.com. Conventions This guide uses the following conventions for command syntax and displayed information.
Page 27: Command Prompts
Command Prompts In the default configuration, your switch displays the following CLI prompt: ProCurve Switch 2610# To simplify recognition, this guide uses ProCurve to represent command prompts for all models. For example: ProCurve# (You can use the hostname command to change the text in the CLI prompt.)
Page 28: Port Identity Examples
Port Identity Examples This guide describes software applicable to both chassis-based and stackable ProCurve switches. Where port identities are needed in an example, this guide uses the chassis-based port identity system, such as “A1”, “B3 - B5”, “C7”, etc. However, unless otherwise noted, such examples apply equally to the stackable switches, which for port identities typically use only numbers, such as “1”, “3-5”, “15”, etc.
Page 29 For information on specific features in the Web browser interface, ■ use the online help. For information on Help options, see “Online Help for the Web Browser Interface” on page 5-1. For further information on ProCurve Networking switch technology, ■ visit the ProCurve website at: www.procurve.com...
Page 30: Need Only A Quick Start
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.
Page 31 Advantages of Using the Web Browser Interface ..... 2-5 Advantages of Using ProCurve Manager or ProCurve Manager Plus ..2-6...
Page 32: Selecting A Management Interface
VLAN management. (ProCurve includes a copy of PCM+ in-box for a free 30-day trial.) This manual describes how to use the menu interface (chapter 3), the CLI (chapter 4), the web browser interface (chapter 5), and how to use these interfaces to configure and monitor the switch.
Page 33: Advantages Of Using The Menu Interface
Selecting a Management Interface Advantages of Using the Menu Interface Advantages of Using the Menu Interface Figure 2-1. Example of the Console Interface Display Provides quick, easy management access to a menu-driven subset of ■ switch configuration and performance features: • IP addressing •...
Page 34: Advantages Of Using The Cli
■ Provides more security; configuration information and passwords are not seen on the network. Advantages of Using the CLI Operator Level ProCurve> Manager Level ProCurve# Global Configuration Level ProCurve(config)# Context Configuration Levels (port, VLAN) ProCurve(<context>)#...
Page 35: Advantages Of Using The Web Browser Interface
Selecting a Management Interface Advantages of Using the Web Browser Interface Advantages of Using the Web Browser Interface Figure 2-3. Example of the Web Browser Interface Easy access to the switch from anywhere on the network ■ ■ Familiar browser interface--locations of window objects consistent with commonly used browsers, uses mouse clicking for navigation, no terminal setup ■...
Page 36: 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.
Page 37 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus Extended RMON and sFlow, users can monitor overall traffic levels, segments with the highest traffic, or even the top users within a network segment. • Group and Policy Management: Changes in configuration are tracked and logged, and archived configurations can be applied to one or many devices.
Page 38 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus...
Page 39 Using the Menu Interface Contents Overview ............3-2 Starting and Ending a Menu Session .
Page 40: Using The Menu Interface
Reboot the switch For a detailed list of menu features, see the “Menu Features List” on page 3-14). Privilege Levels and Password Security. ProCurve strongly recom mends that you configure a Manager password to help prevent unauthorized access to your network. A Manager password grants full read-write access to the switch.
Page 41: Starting And Ending A Menu Session
Using the Menu Interface Starting and Ending a Menu Session N o t e 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.
Page 42: How To Start A Menu Interface Session
Access Security Guide for your switch.) • If no password has been configured, the CLI prompt appears. Go to the next step. 4. When the CLI prompt appears, display the Menu interface by entering the menu command. For example: Enter ProCurve# menu results in:...
Page 43: How To End A Menu Session And Exit From The Console
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). N o t e 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 44 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 (zero) to log out.
Page 45: Main Menu Features
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.
Page 46 Using the Menu Interface Main Menu Features 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)”.) ■...
Page 47: Screen Structure And Navigation
Using the Menu Interface Screen Structure and Navigation Screen Structure and Navigation Menu interface screens include these three elements: ■ Parameter fields and/or read-only information such as statistics Navigation and configuration actions, such as Save, Edit, and Cancel ■ ■ Help line to describe navigation options, individual parameters, and read- only data For example, in the following System Information screen:...
Page 48 Using the Menu Interface Screen Structure and Navigation Table 3-1. How To Navigate in the Menu Interface Task: Actions: Execute an action Use either of the following methods: from the “Actions –>” • Use the arrow keys ([<] or [>]) to highlight the action you want to list at the bottom of execute, then press [Enter].
Page 49 Using the Menu Interface Screen Structure and Navigation To get Help on individual parameter descriptions. In most screens there is a Help option in the Actions line. Whenever any of the items in the Actions line is highlighted, press , and a separate help screen is displayed. For example: Pressing [H] or highlighting Help and pressing [Enter] displays Help for the...
Page 50: Rebooting The Switch
Using the Menu Interface Rebooting the Switch Rebooting the Switch Rebooting the switch from the menu interface ■ Terminates all current sessions and performs a reset of the operating system Activates any menu interface configuration changes that require a reboot ■...
Page 51 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 .
Page 52: Menu Features List
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 •...
Page 53: Where To Go From Here
To use the Run Setup option Refer to the Installation and Getting Started Guide shipped with the switch. To use the ProCurve Stack Manager See the chapter on stack management in the Advanced Traffic Management Guide. To view and monitor switch status and Appendix B, “Monitoring and Analyzing Switch counters Operation”...
Page 54 Using the Menu Interface Where To Go From Here 3-16...
Page 55: Using The Command Line Interface (Cli)
Using the Command Line Interface (CLI) Contents Overview ............4-2 Accessing the CLI .
Page 56: Overview
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.
Page 57: Privilege Levels At Logon
In the above case, you will enter the CLI at the level corresponding to the password you provide (operator or manager). If no passwords are set when you log onto the CLI, you will enter at the Manager level. For example: ProCurve# _...
Page 58: Privilege Level Operation
Using the CLI C a u t i o n ProCurve strongly recommends that you configure a Manager password. If a Manager password is not configured, then the Manager level is not password- protected, 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.
Page 59: Manager Privileges
Manager prompt. For example: Enter config at the Manager prompt. ProCurve# _ ProCurve(config)#_The Global Config prompt.) ■ Context Configuration level: Provides all Operator and Manager privileges, and enables you to make configuration changes in a specific context, such as one or more ports or a VLAN.
Page 60 ProCurve(eth-5)# Execute context-specific configuration commands, such as a particular VLAN or switch port. This is useful for shortening the Configuration ProCurve(vlan-100)# command strings you type, and for entering a series of commands Level for the same context. For a list of available commands, enter ? at...
Page 61: How To Move Between Levels
Global configuration ProCurve(config)# vlan 10 level ProCurve(vlan-10)# to a Context configuration level Context configuration ProCurve(vlan-10)# interface e 3 level ProCurve(int-3)# to another The CLI accepts "e" as the abbreviated Context configuration form of "ethernet". level Move from any level...
Page 62: Listing Commands And Command Options
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”...
Page 63 [Tab] (with no spaces allowed). For example, at the Global Configuration level, if you press [Tab] immediately after typing "t", the CLI displays the available command options that begin with "t". For example: ProCurve(config)# t [Tab] telnet-server time trunk...
Page 64: Command Option Displays
CLI completes the current word (if you have typed enough of the word for the CLI to distinguish it from other possibilities), including hyphenated exten sions. For example: ProCurve(config)# port [Tab] ProCurve(config)# port-security _ Pressing after a completed command word lists the further options for [Tab] that command.
Page 65: Displaying Cli "Help
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 . For example, suppose you want to see the command options for config uring port C5: This example displays the command options for configuring the switch’s console settings.
Page 66 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.
Page 67: Configuration Commands And The Context Configuration Modes
Manager, and Operator commands. The prompt for this mode includes the identity of the selected port(s): ProCurve(config)# interface e c3-c6 Command executed at configuration level for ProCurve(config)# interface e trk1 entering port or trk1 static trunk-group context. Resulting prompt showing ProCurve(eth-C5-C8)#...
Page 68 Using the Command Line Interface (CLI) Using the CLI Lists the commands you ProCurve(eth-C5-C8)#? can use in the port or static trunk context, plus the ProCurve(eth-C5-C8)#? Manager, Operator, and context commands you can execute at this level. In the port context, the first block of commands in the "?"...
Page 69 VLAN ID of the selected VLAN. For example, if you had already configured a VLAN with an ID of 100 in the switch: Command executed at configura ProCurve(config)# vlan 100 tion level to enter VLAN 100 context.
Page 70: Cli Control And Editing
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. or [<] Moves the cursor back one character. [Ctrl] [B] [Ctrl] [C] Terminates a task and displays the command prompt. [Ctrl] [D] Deletes the character at the cursor.
Page 71: Using The Web Browser Interface
Using a Standalone Web Browser in a PC or UNIX Workstation ..5-4 Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) 5-5 Tasks for Your First Web Browser Interface Session ....5-7 Viewing the “First Time Install”...
Page 72: Overview
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 ■...
Page 73: General Features
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 •...
Page 74: Starting A Web Browser Interface Session With The Switch
Location or Address field instead of the IP address. Using DNS names typically improves browser performance. Contact your network adminis trator to enquire about DNS names associated with your ProCurve switch. Type the IP address (or DNS name) of the switch in the browser Location or Address (URL) field and press .
Page 75: Using Procurve Manager (Pcm) Or Procurve Manager Plus (Pcm+)
(optionally) a DNS name, and has been discovered by PCM or PCM+. (For more on assigning an IP address, refer to “IP Configuration” on page 8-3.) To establish a web browser session with ProCurve PCM or PCM+ running, do the following on the network management station: 1. Make sure the Java applets are enabled for your web browser.
Page 76 Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch Alert First-Time Install Alert Figure 5-1. Example of Status Overview Screen N o t e The above screen appears somewhat different if the switch is configured as a stack Commander.
Page 77: Tasks For Your First Web Browser Interface Session
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 ■...
Page 78: Creating Usernames And Passwords In The Browser Interface
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.
Page 79 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. 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.
Page 80: Using The Passwords
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.
Page 81: Online Help For The Web Browser Interface
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.
Page 82: Support/Mgmt Urls Feature
– The URL for the support information source you want the switch to access when you click on the web browser interface Support tab. The default is the URL for the ProCurve Networking home page. – The URL of a PCM (ProCurve Network Manager) workstation or other server for the online Help files for this web browser interface.
Page 83: 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 informa...
Page 84: Status Reporting Features
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-15) ■ The Alert log (page 5-18) The Status bar (page 5-20) ■...
Page 85: The Port Utilization And Status Displays
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. For more information, refer to the documentation provided with the PCM software. The Port Utilization and Status Displays The Port Utilization and Status displays show an overview of the status of the switch and the amount of network activity on each port.
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: Port Status
Using the Web Browser Interface Status Reporting Features Figure 5-10. Display of Numerical Values for the Bar Port Status Port Status Indicators Legend Figure 5-11. The Port Status Indicators and Legend The Port Status indicators show a symbol for each port that indicates the general status of the port.
Page 88: The Alert Log
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.
Page 89: Alert Types And Detailed Views
Using the Web Browser Interface Status Reporting Features Alert Types and Detailed Views The web browser interface generates the following alert types: • Auto Partition • High collision or drop rate • Backup Transition • Loss of Link • Excessive broadcasts •...
Page 90: The Status Bar
Using the Web Browser Interface Status Reporting Features Figure 5-13.Example of Alert Log Detail View The Status Bar The Status Bar is displayed in the upper left corner of the web browser interface screen. Figure 5-14 shows an expanded view of the status bar. Status Indicator Most Critical Alert Description Product Name...
Page 91: Setting Fault Detection Policy
Using the Web Browser Interface Status Reporting Features Table 5-1.Status Indicator Key Color Switch Status Status Indicator Shape Blue Normal Activity; "First time installation" information available in the Alert log. Green Normal Activity Yellow Warning Critical System Name. The name you have configured for the switch by using ■...
Page 92 Using the Web Browser Interface Status Reporting Features Figure 5-15. The Fault Detection Window The Fault Detection screen contains a list box for setting fault detection and response policy. You set the sensitivity level at which a network problem should generate an alert and send it to the Alert Log. To provide the most information on network problems in the Alert Log, the recommended sensitivity level for Log Network Problems is High Sensitivity.
Page 93 Never. Disables the Alert Log and transmission of alerts (traps) to the ■ management server (in cases where a network management tool such as ProCurve Manager is in use). Use this option when you don’t want to use the Alert Log. The Fault Detection Window also contains three Change Control Buttons: ■...
Page 94 Using the Web Browser Interface Status Reporting Features 5-24...
Page 95: Switch Memory And Configuration
Switch Memory and Configuration Contents Overview ............6-3 Overview of Configuration File Management .
Page 96 Switch Memory and Configuration Contents Transferring Startup-Config Files To or From a Remote Server ..6-35 TFTP: Copying a Configuration File to a Remote Host ..6-35 TFTP: Copying a Configuration File from a Remote Host ..6-36 Xmodem: Copying a Configuration File to a Serially Connected Host .
Page 97: Overview
Switch Memory and Configuration Overview Overview This chapter describes: ■ How switch memory manages configuration changes How the CLI implements configuration changes ■ ■ How the menu interface and web browser interface implement configu ration changes ■ How the switch provides software options through primary/secondary flash image options How to use the switch’s primary and secondary flash options, including ■...
Page 98 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.
Page 99 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.
Page 100: Using The Cli To Implement Configuration Changes
Switch Memory and Configuration Using the CLI To Implement Configuration Changes Using the CLI To Implement Configuration Changes The CLI offers these capabilities: Access to the full set of switch configuration features ■ ■ The option of testing configuration changes before making them perma nent How To Use the CLI To View the Current Configuration Files.
Page 101 ProCurve(config)# interface e a5 speed-duplex auto-10 After you are satisfied that the link is operating properly, you can save the change to the switch’s permanent configuration (the startup-config file) by...
Page 102 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 to continue the rebooting process.
Page 103: Using The Menu And Web Browser Interfaces To Implement Configuration Changes
Syntax: erase startup-config For example: ProCurve(config)# erase startup-config Configuration will be deleted and device rebooted, continue [y/n]? Figure 6-3.Resetting to the Factory-Default Configuration Press to replace the current configuration with the factory default config...
Page 104 Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes N o t e 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-12. Using in the Menu Interface Save...
Page 105: Rebooting From The Menu Interface
Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes N o t e 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.
Page 106: Configuration Changes Using The Web Browser Interface
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.
Page 107: Using Primary And Secondary Flash Image Options
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. ■...
Page 108 Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, if the switch is using a software version of R.01.01 stored in Primary flash, show version produces the following: ProCurve(config)# show version Image stamp: /sw/code/build/info (s03) Nov 01 2007 10:50:26 R.01.01...
Page 109: Switch Software Downloads
Boot Image: Primary switch has version R.11.XX in primary flash. Procurve(config)# boot system flash secondary Device will be rebooted, do you want to continue [y/n]? y After the boot system command, show version indicates that version ProCurve> show version R.11.XX is in secondary...
Page 110: Local Switch Software Replacement And Removal
If you want to remove an unwanted software version from flash, ProCurve recommends that you do so by overwriting it with the same software version that you are using to operate the switch, or with another acceptable software version.
Page 111 Figure 6-10. Example Indicating Two Different Software Versions in Primary and Secondary Flash Execute the copy command as follows: ProCurve(config)# copy flash flash primary Erasing the Contents of Primary or Secondary Flash. This command deletes the software image file from the specified flash location.
Page 112: Rebooting The Switch
ProCurve# boot system flash secondary 2. Then erase the software image in the selected flash (in this case, primary): The prompt shows which flash location will be erased.
Page 113 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Table 6-2. Comparing the Boot and Reload Commands Actions Included In Included In Reload Note Boot? Save all Optional, Optional with reload Config changes saved to configuration with prompt <cr>, when prompt the startup-config file if changes since the...
Page 114 For example, to reboot the switch from secondary flash when there are no pending configuration changes in the running-config file: ProCurve(config)# boot system flash secondary Device will be rebooted, do you want to continue [y/n]? y Do you want to save current configuration [y/n]? n Figure 6-14.
Page 115 ■ ProCurve# reload at 12:05 ■ To schedule a reload on some future date: ProCurve# reload at 12:05 01/01/2008 ProCurve(config)# reload after 04:14:00 Reload scheduled in 4 days, 14 hours, 0 minutes Figure 6-16. An Example of the reload Command...
Page 116: Operating Notes
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.
Page 117: Multiple Configuration Files
Switch Memory and Configuration Multiple Configuration Files Multiple Configuration Files Action Page Listing and Displaying Startup-Config Files 6-26 Changing or Overriding the Reboot Configuration Policy 6-27 Managing Startup-Config Files Renaming Startup-Config Files 6-30 Copying Startup-Config Files 6-30 Erasing Startup-Config Files 6-33 Effect of Using the Clear + Reset Buttons 6-34...
Page 118: General Operation
General Operation Multiple Configuration Storage in the Switch. The switch uses three memory “slots”, with identity (id) numbers of 1, 2, and 3. ProCurve(config)# show config files Configuration files: id | act pri sec | name ---+-------------+---------------------...
Page 119 Switch Memory and Configuration Multiple Configuration Files 1. Reboot the switch through the Primary boot path using the startup-config file named backupConfig. 2. Use the CLI to make configuration changes in the running-config file, and then execute write mem. The result is that the startup-config file used to reboot the switch is modified by the actions in step 2.
Page 120: Listing And Displaying Startup-Config Files
Switch Memory and Configuration Multiple Configuration Files Listing and Displaying Startup-Config Files Command Page show config files Below show config < filename > 6-27 Viewing the Startup-Config File Status with Multiple Configuration Enabled Syntax: show config files This command displays the available startup-config files on the switch and the current use of each file.
Page 121: Displaying The Content Of A Specific Startup-Config File
Switch Memory and Configuration Multiple Configuration Files ProCurve(config)# show config files Configuration files: id | act pri sec | name ---+-------------+--------------------- | oldconfig | workingConfig As this example shows, you must reconfigure either the primary or the secondary boot path if you want to boot the switch using the startup-config file in another memory slot.
Page 122 Switch Memory and Configuration Multiple Configuration Files Changing the Reboot Configuration Policy. For a given reboot, the switch automatically reboots from the startup-config file assigned to the flash location (primary or secondary) being used for the current reboot. The switch copies the existing startup-config file (named oldConfig) into memory slot 2, renames this file to workingConfig, and assigns workingConfig as: ■...
Page 123 The following two commands configure the desired behavior. ProCurve(config)# startup-default pri config minconfig ProCurve(config) # startup-default sec config newconfig. Overriding the Default Reboot Configuration Policy. This command provides a method for manually rebooting with a specific startup-config file other than the file specified in the default reboot configuration policy.
Page 124: Managing Startup-Config Files In The Switch
Switch Memory and Configuration Multiple Configuration Files Managing Startup-Config Files in the Switch Command Page rename config < current-filename > < newname-str > 6-30 copy config < source-filename > config < dest-filename > 6-30 erase config < filename > | startup-config 6-33 Erase startup-config using the front-panel Clear + Reset Buttons 6-34...
Page 125 Unable to copy configuration to “< target-filename >”. For example, suppose both primary and secondary flash memory contain software releaseR.11.01 and use a startup-config file named config1: ProCurve(config)# show config files Configuration files: id | act pri sec | name...
Page 126 If you wanted to experiment with configuration changes to the software version in secondary flash, you could create and assign a separate startup config file for this purpose. ProCurve(config)# copy config config1 config config2 ProCurve(config)# startup-default secondary config config2 ProCurve(config)# show config files...
Page 127: Erasing A Startup-Config File
Switch Memory and Configuration Multiple Configuration Files Erasing a Startup-Config File You can erase any of the startup-config files in the switch’s memory slots. In some cases, erasing a file causes the switch to generate a new, default- configuration file for the affected memory slot. Syntax: erase <...
Page 128: Using The Clear + Reset Button Combination To Reset The Switch To Its Default Configuration
Switch Memory and Configuration Multiple Configuration Files Figure 6-22 illustrates using erase config < filename > to remove a startup-config file. ProCurve(config)# show config files Configuration files: id | act pri sec | name ---+-------------+--------------------- | minconfig | config2 | config3...
Page 129: Transferring Startup-Config Files To Or From A Remote Server
“TFTP: Copying a Configuration File to a Remote Host” on page A-19. For example, the following command copies a startup-config file named test 01 from the switch to a (UNIX) TFTP server at IP address 10.10.28.14: ProCurve(config)# copy config test-01 tftp 10.10.28.14 test-01.txt unix 6-35...
Page 130: Tftp: Copying A Configuration File From A Remote Host
For example, the following command copies a startup-config file named test 01.txt from a (UNIX) TFTP server at IP address 10.10.28.14 to the first empty memory slot in the switch: ProCurve(config)# copy tftp config test-01 10.10.28.14 test-01.txt unix Xmodem: Copying a Configuration File to a...
Page 131: Xmodem: Copying A Configuration From A Serially Connected Host
Switch Memory and Configuration Multiple Configuration Files Xmodem: Copying a Configuration from a Serially Connected Host Syntax: copy xmodem config < dest-file > < pc | unix > Use this command to download a configuration file from an Xmodem host to the switch. For more on using Xmodem to copy a file from a serially connected host, refer to “Xmodem: Copying a Configuration File from a Serially Connected PC or Unix Workstation”...
Page 132 Switch Memory and Configuration Multiple Configuration Files 6-38...
Page 133: Interface Access And System Information
Interface Access and System Information Contents Overview ............7-2 Interface Access: Console/Serial Link, Web, and Telnet .
Page 134: Overview
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: ■...
Page 135: Interface Access: Console/Serial Link, Web, And Telnet
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 Default Menu Inactivity Time 0 Minutes page 7-4 page 7-6 — (disabled) Inbound Telnet Access Enabled page 7-4 page 7-5 —...
Page 136: Menu: Modifying The Interface Access
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: From the Main Menu, Select...
Page 137: Cli: Modifying The Interface Access
Console Control Options Figure 7-2. Listing of Show Console Command Reconfigure Inbound Telnet Access. In the default configuration, inbound Telnet access is enabled. Syntax: [no] telnet-server To disable inbound Telnet access: ProCurve(config)# no telnet-server To re-enable inbound Telnet access: ProCurve(config)# telnet-server...
Page 138 Reconfigure Web Browser Access. In the default configuration, web browser access is enabled. Syntax: [no] web-management To disable web browser access: ProCurve(config)# no web-management To re-enable web browser access: ProCurve(config)# web-management Reconfigure the Console/Serial Link Settings. You can reconfigure one or more console parameters with one console command.
Page 139 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet For example, to use one command to configure the switch with the following: ■ VT100 operation ■ 19,200 baud No flow control ■ ■ 10-minute inactivity time ■ Critical log events you would use the following command sequence: The switch implements the Event Log change immediately.
Page 140 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet 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. This command dynamically changes only the console session from which it is executed.
Page 141: Denying Interface Access By Terminating Remote Management Sessions
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.
Page 142: System Information
System Name: Using a unique name helps you to identify individual devices in stacking environments and where you are using an SNMP network manage ment tool such as ProCurve Manager. System Contact and Location: This information is helpful for identifying the person administratively responsible for the switch and for identifying the locations of individual switches.
Page 143: Menu: Viewing And Configuring System Information
Daylight Time Rule: Specifies the daylight savings time rule to apply for your location. The default is None. (For more on this topic, see Appendix E, “Daylight Savings Time on ProCurve Switches.) Time: Used in the CLI to specify the time of day, the date, and other system parameters.
Page 144: Cli: Viewing And Configuring System Information
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. CLI: Viewing and Configuring System Information System Information Commands Used in This Section show system-information...
Page 145 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 <name-string> snmp-server [contact <system contact>] [location <system location>] Both fields allow up to 255 characters.
Page 146 Vancouver, Canada is -480 (zone -8, or -480 minutes). To configure the time zone and daylight time rule for Vancouver, Canada: ProCurve(config)# time timezone -480 daylight-time-rule continental-us-and-canada Configure the Time and Date. The switch uses the time command to con...
Page 147: Web: Configuring System Parameters
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.
Page 148 Interface Access and System Information System Information 7-16...
Page 149 Configuring IP Addressing Contents Overview ............8-2 IP Configuration .
Page 150: Configuring Ip Addressing
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 151: Ip Configuration
Configuring IP Addressing IP Configuration IP Configuration IP Configuration Features Feature Default Menu IP Address and Subnet Mask DHCP/Bootp page 8-5 page 8-7 page 8-11 Multiple IP Addresses on a VLAN page 8-9 Default Gateway Address none page 8-5 page 8-7 page 8-11 Packet Time-To-Live (TTL) 64 seconds...
Page 152: Just Want A Quick Start With Ip Addressing
If you just want to give the switch an IP address so that it can communicate on your network, or if you are not using VLANs, 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 153: Ip Addressing In A Stacking Environment
URL in your web browser. IP Addressing in a Stacking Environment If you are installing the switch into an ProCurve stack management environ ment, entering an IP address may not be required. See the chapter on stack management in the Advanced Traffic Management Guide.
Page 154 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. E xample of the IP Service Configuration Screen without Multiple VLANs Configured 2. Press (for Edit).
Page 155: Cli: Configuring Ip Address, Gateway, And Time-To-Live (Ttl)
Configuring IP Addressing IP Configuration CLI: Configuring IP Address, Gateway, and Time-To- Live (TTL) IP Commands Used in This Section show ip page 8-7 vlan <vlan-id> ip page 8-8 address 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.
Page 156 This example configures IP addressing on the default VLAN with the subnet mask specified in mask bits. ProCurve(config)# vlan 1 ip address 10.28.227.103/255.255.255.0 This example configures the same IP addressing as the preceding example, but specifies the subnet mask by mask length.
Page 157 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.
Page 158 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 N o t e 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 159: Web: Configuring Ip Addressing
Console RS-232 port. You can use direct-connect console access to take advantage of features that do not depend on IP addressing. However, to realize the full performance capabilities ProCurve proactive networking offers 8-11...
Page 160: Dhcp/Bootp Operation
• DHCP or Bootp support for automatic IP address suggested solutions configuration, and DHCP support for automatic Timep • SNMP network management access such as ProCurve server IP address configuration Manager network configuration, monitoring, problem- • Spanning Tree Protocol finding and reporting, analysis, and recommendations for • Port settings and port trunking...
Page 161 Configuring IP Addressing IP Configuration The DHCP/Bootp Process. Whenever the IP Config parameter in the switch or in an individual VLAN in the switch is configured to DHCP/Bootp (the default), or when the switch is rebooted with this configuration: 1. DHCP/Bootp requests are automatically broadcast on the local network. (The switch sends one type of request to which either a DHCP or Bootp server can respond.) 2. When a DHCP or Bootp server receives the request, it replies with a...
Page 162 Configuring IP Addressing IP Configuration Bootp Operation. When a Bootp server receives a request it searches its Bootp database for a record entry that matches the MAC address in the Bootp request from the switch. If a match is found, the configuration data in the associated database record is returned to the switch.
Page 163: Network Preparations For Configuring Dhcp/Bootp
Configuring IP Addressing IP Configuration TFTP server address (source of final configuration file) T144 is the vendor-specific “tag” identifying the configuration file to download. is a required entry that specifies the Bootp report format. For the switches described in this guide, set this parameter to rfc1048. N o t e The above Bootp table entry is a sample that will work for the switch when the appropriate addresses and file names are used.
Page 164: Ip Preserve: Retaining Vlan-1 Ip Addressing Across Configuration
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 165 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Entering "ip preserve" in the last line of a configuration file implements IP Preserve when the file is downloaded to the switch and the switch reboots. Figure 8-6. Example of Implementing IP Preserve in a Switch Configuration File For example, consider Figure 8-7: DHCP TFTP...
Page 166 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Using figure 8-7, above, switches 1 - 3 ignore these entries because the file implements IP Preserve and their current IP addressing was not acquired through DHCP/Bootp. Switch 4 ignores IP Preserve and implements the DHCP/Bootp addressing and IP Gateway specified in this file (because its last IP addressing was acquired...
Page 167 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads Because switch 4 (figure 8-7) received its most recent IP addressing from a DHCP/Bootp server, the switch ignores the ip preserve command and implements the IP addressing included in this file.
Page 168 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads 8-20...
Page 169 Time Protocols Contents Overview ............9-2 TimeP Time Synchronization .
Page 170: Time Protocols
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 171: Overview: Selecting A Time Synchronization Protocol Or Turning Off Time Protocol Operation
Time Protocols Overview: Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation ular server, it ignores time broadcasts from other SNTP servers unless the configurable Poll Interval expires three consecutive times without an update received from the first-detected server. Note To use Broadcast mode, the switch and the SNTP server must be in the same subnet.
Page 172: Disabling Time Synchronization
Time Protocols SNTP: Viewing, Selecting, and Configuring Note that simply selecting a time synchronization protocol does not enable that protocol on the switch unless you also enable the protocol itself (step 2, above). For example, in the factory-default configuration, TimeP is the selected time synchronization method.
Page 173: Menu: Viewing And Configuring Sntp
Time Protocols SNTP: Viewing, Selecting, and Configuring Table 9-1.SNTP Parameters SNTP Parameter Operation Time Sync Used to select either SNTP, TIMEP, or None as the time synchronization method. 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.
Page 174 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 (for ). The cursor moves to the field. Edit System Name 3. Use [v] to move the cursor to the Time Sync Method field.
Page 175 SNTP server version running on the device you specified in the preceding step (step ii). If you are unsure which version to use, ProCurve recommends leaving this value at the default setting of and testing SNTP operation to determine whether any change is necessary.
Page 176: Cli: Viewing And Configuring Sntp
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 177: Configuring (Enabling Or Disabling) The Sntp Mode
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 178 Time Protocols SNTP: Viewing, Selecting, and Configuring 2. Select SNTP as the time synchronization mode. 3. Enable SNTP for Broadcast mode. 4. View the SNTP configuration again to verify the configuration. The commands and output would appear as follows: show sntp displays the SNTP configuration and also shows that TimeP is the currently active time synchronization mode.
Page 179 ProCurve(config)# timesync sntp Selects SNTP. ProCurve(config)# sntp unicast Activates SNTP in Unicast mode. ProCurve(config)# sntp server 10.28.227.141 Specifies the SNTP server and accepts the current SNTP server version (default: 3). In this example, the Poll Interval and the Protocol Version appear at their default settings.
Page 180 720 seconds. (This parameter is separate from the poll interval parameter used for Timep operation.) For example, to change the poll interval to 300 seconds: ProCurve(config)# sntp poll-interval 300 Disabling Time Synchronization Without Changing the SNTP Configuration. The recommended method for disabling time synchroniza...
Page 181 Time Protocols SNTP: Viewing, Selecting, and Configuring Figure 9-7. Example of SNTP with Time Sychronization Disabled Disabling the SNTP Mode. If you want to prevent SNTP from being used even if selected by (or the Menu interface’s param timesync Time Sync Method eter), configure the SNTP mode as disabled.
Page 182: Timep: Viewing, Selecting, And Configuring
Time Protocols TimeP: Viewing, Selecting, and Configuring TimeP: Viewing, Selecting, and Configuring TimeP Feature Default Menu view the Timep time synchronization page 9-15 page 9-17 — configuration select Timep as the time synchronization TIMEP page 9-13 pages 9-18 — method disable time synchronization timep page 9-15...
Page 183: Menu: Viewing And Configuring Timep
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) –...
Page 184: Cli: Viewing And Configuring Timep
Time Protocols TimeP: Viewing, Selecting, and Configuring • Use the Space bar to select the mode. Manual i. Press [>] to move the cursor to the field. Server Address ii. Enter the IP address of the TimeP server you want the switch to use for time synchronization.
Page 185: Viewing The Current Timep Configuration
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 186: Configuring (Enabling Or Disabling) The Timep Mode
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).
Page 187 For example, to select TimeP and configure it for manual operation using a TimeP server address of 10.28.227.141 and the default poll interval (720 minutes, assuming the TimeP poll interval is already set to the default): ProCurve(config)# timesync timep Selects TimeP. ProCurve(config)# ip timep manual 10.28.227.141 Activates TimeP in Manual mode. 9-19...
Page 188 < 1 . . 9999 > For example, to change the poll interval to 60 minutes: ProCurve(config)# ip timep interval 60 Disabling Time Synchronization Without Changing the TimeP Configuration. The recommended method for disabling time synchroniza...
Page 189: Sntp Unicast Time Polling With Multiple Sntp Servers
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 option.) Time Sync Method Syntax:...
Page 190: Adding And Deleting Sntp Server Addresses
Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers accordingly, with the lowest decimal value assigned as the primary address, the second-lowest decimal value assigned as the next address, and the third- lowest decimal value as the last address. If the first octet is the same between two of the addresses, the second octet is compared, and so on.
Page 191: Menu Interface Operation With Multiple Sntp Server Addresses
<ip-addr> For example, to delete the primary address in the above example (and automatically convert the secondary address to primary): ProCurve(config)# no sntp server 10.28.227.141 Menu Interface Operation with Multiple SNTP Server Addresses Configured When you use the Menu interface to configure an SNTP server IP address, the new address writes over the current primary address, if one is configured.
Page 192 Time Protocols SNTP Messages in the Event Log 9-24...
Page 193: Port Status And Basic Configuration
Port Status and Basic Configuration Contents Overview ........... . . 10-3 Viewing Port Status and Configuring Port Parameters .
Page 194 Port Status and Basic Configuration Contents Configuring and Viewing Port-Based Priority ....10-31 Messages Related to Prioritization ......10-32 Troubleshooting Prioritization .
Page 195: Overview
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 ■...
Page 196 • Auto-10: Allows the port to negotiate between half-duplex (HDx) and full-duplex (FDx) while keeping speed at 10 Mbps. Also negotiates flow control (enabled or disabled). ProCurve recommends Auto-10 for links between 10/100 autosensing ports connected with Cat 3 cabling. (Cat 5 cabling is required for 100 Mbps links.).
Page 197 (Continued) • Auto-10: Allows the port to negotiate between half-duplex (HDx) and full-duplex (FDx) while keeping speed at 10 Mbps. Also negotiates flow control (enabled or disabled). ProCurve recommends Auto-10 for links between 10/100 autosensing ports connected with Cat 3 cabling. (Cat 5 cabling is required for 100 Mbps links.).
Page 198: Menu: Viewing Port Status And Configuring Port Parameters
LACP trunk, if any, to which a port belongs. Trunk Group Note: An LACP trunk requires a full-duplex link. In most cases, ProCurve recommends that you leave (CLI) the port Mode setting at Auto (the default). Refer to “Trunk Group Operation Using LACP” on page 12-15.
Page 199 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters ProCurve Switch 11-Sept-2007 8:46:35 ==========================- CONSOLE - MANAGER MODE -============================ Status and Counters - Port Status Intrusion Flow Bcast Port Type Alert Enabled Status Mode Mode Ctrl Limit...
Page 200: Cli: Viewing Port Status And Configuring Port Parameters
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Figure 10-2. Example of Port/Trunk Settings with a Trunk Group Configured 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.
Page 201 Refer to “Viewing Port and Trunk Group Statistics and Flow Control Status” on page B-10. The figure 10-3 shows an example of the output of the show interface brief command. ProCurve(config)# show interfaces brief Current Operating Mode Status and Counters - Port Status | Intrusion...
Page 202: Displaying Spanning Tree Configuration Details
For example, to configure ports C1 through C3 and port C6 for 100 Mbps full- duplex, you would enter these commands: ProCurve(config)# int e c1-c3,c6 speed-duplex 100-full Similarly, to configure a single port with the settings in the above command, you could either enter the same command with only the one port identified, or go to the context level for that port and then enter the command.
Page 203: Using The Cli To Configure A Broadcast Limit
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters These commands enable and configure port C8 from the config level: ■ ProCurve(config)# int e c8 enable ProCurve(config)# int e c8 speed-duplex 100-full ProCurve(config)# int e c8 flow-control ■...
Page 204: Configuring Auto-Mdix
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Displays the startup-config file. The broadcast limit setting appears here if configured and saved to the startup-config file by a write memory command. You must reboot the switch to implement the new setting.
Page 205: Manual Auto-Mdix Override
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Auto-MDIX was developed for auto-negotiating devices, and was shared with the IEEE for the development of the IEEE 802.3ab standard. Auto-MDIX and the IEEE 802.3ab Auto MDI/MID-X feature are completely compatible. Addi tionally, Auto-MDIX supports operation in forced speed and duplex modes.
Page 206 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters mdix is the manual mode setting that configures the port for connecting to either a switch, hub, or other MDI-X device with a crossover cable, or to a PC or other MDI device with a straight- through cable.
Page 207: Viewing Transceiver Status
Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Per-Port MDI Operating Mode Figure 10-7. Example of Displaying the Current MDI Operating Mode N o t e Port Response to Switch Software Updates 1. Copper ports in auto-negotiation still default to auto-mdix mode. 2. Copper ports in forced speed/duplex default to mdix mode.
Page 208 • Part number—Allows you to determine the manufacturer for a spec ified transceiver and revision number. For a non-ProCurve installed transceiver (see line 23 Figure 10-8), no ■ transceiver type, product number, or part information is displayed. In the Serial Number field, non-operational is displayed instead of a serial num...
Page 209: Web: Viewing Port Status And Configuring Port Parameters
• Self test failure. • Transceiver type not supported in this port. • 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. Web: Viewing Port Status and Configuring Port Parameters In the web browser interface: 1. Click on the Configuration tab.
Page 210: Terminology
Port Status and Basic Configuration Jumbo Frames You can enable inbound jumbo frames on a per-VLAN basis. That is, on a VLAN configured for jumbo traffic, all ports belonging to that VLAN and operating at 1 Gbps or 10 Gbps allow inbound jumbo frames of up to 9220 bytes. (Regardless of the mode configured on a given jumbo-enabled port, if the port is operating at only 10 Mbps or 100 Mbps, only frames that do not exceed 1522 bytes are allowed inbound on that port.)
Page 211: Configuring Jumbo Frame Operation
Port Status and Basic Configuration Jumbo Frames Jumbo Traffic Sources: A port belonging to a jumbo-enabled VLAN can ■ receive inbound jumbo frames through any VLAN to which it belongs, including non-jumbo VLANs. For example, if VLAN 10 (without jumbos enabled) and VLAN 20 (with jumbos enabled) are both configured on a switch, and port 1 belongs to both VLANs, then port 1 can receive jumbo traffic from devices on either VLAN.
Page 212: Viewing The Current Jumbo Configuration
Port Status and Basic Configuration Jumbo Frames Viewing the Current Jumbo Configuration Syntax: show vlans Lists the static VLANs configured on the switch and includes a Jumbo column to indicate which VLANs are configured to support inbound jumbo traffic. All ports belonging to a jumbo-enabled VLAN can receive jumbo traffic.
Page 213 Port Status and Basic Configuration Jumbo Frames Indicates which static VLANs are configured to enable jumbo packets. Figure 10-10. Example of Listing the VLAN Memberships for a Range of Ports Syntax: show vlans < vid > This command shows port membership and jumbo configuration for the specified <...
Page 214: Enabling Or Disabling Jumbo Traffic On A Vlan
Operating Notes for Jumbo Traffic-Handling ■ ProCurve does not recommend configuring a voice VLAN to accept jumbo frames. Voice VLAN frames are typically small, and allowing a voice VLAN to accept jumbo frame traffic can degrade the voice transmission perfor...
Page 215 Port Status and Basic Configuration Jumbo Frames This same condition generates a Fault-Finder message in the Alert log of the switch’s web browser interface, and also increments the switch’s “Giant Rx” counter. ■ If you do not want all ports in a given VLAN to accept jumbo frames, you can consider creating one or more jumbo VLANs with a membership comprised of only the ports you want to receive jumbo traffic.
Page 216: Troubleshooting
Port Status and Basic Configuration Jumbo Frames Non-Jumbo VLAN Jumbo-Enabled VLAN VLAN 20 VLAN 10 Port 3 belongs to both VLAN 10 and VLAN 20. Jumbo packets received inbound on port 3 can be forwarded out the Non-Jumbo ports 4, 5, and 6. Figure 10-12.
Page 217: Qos Passthrough Mode
Port Status and Basic Configuration QoS Passthrough Mode QoS Passthrough Mode QoS Passthrough mode is designed to enhance the performance of line-rate traffic transfers through the switch. 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 218: Priority Mapping With And Without Qos Passthrough Mode
Port Status and Basic Configuration QoS Passthrough Mode Note As stated earlier, use of this QoS-Passthrough-Mode feature generally assumes that QoS tagged frames are not being sent through the switch. The receipt of priority 6 or 7 packets may in fact suffer packet drops depending on the traffic load of non-priority 6 or 7 packets.
Page 219 (with QoS Passthrough Mode enabled) as follows: ProCurve(config)# show config Startup configuration: ; J9085A Configuration Editor; Created on release #R.11.XX hostname "ProCurve Switch 2610-24" snmp-server contact "George" Indicates QoS ip default-gateway 15.255.152.1 Passthrough mode qos-passthrough-mode snmp-server community "public"...
Page 220: Configuring Port-Based Priority For Incoming Packets
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets Configuring Port-Based Priority for Incoming Packets Feature Default Menu Assigning a priority level to traffic on the basis Disabled page 10-31 of incoming port When network congestion occurs, it is important to move traffic on the basis of relative importance.
Page 221: Outbound Port Queues And Packet Priority Settings
VLAN, then the tag is stripped from the packet, which then exits from the switch without a priority setting. Outbound Port Queues and Packet Priority Settings Ports on the ProCurve switches have the following outbound port queue structure: Switch Model...
Page 222: Operating Rules For Port-Based Priority
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets For example, suppose you have configured port A10 to assign a priority level of 1 (low): ■ An untagged packet coming into the switch on port A10 and leaving the switch through any other port configured as a tagged VLAN member would leave the switch as a tagged packet with a priority level of 1.
Page 223: Configuring And Viewing Port-Based Priority
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets On a given port, an inbound, tagged packet received on the port with a ■ preset priority of 1 - 7 in its tag keeps that priority and is assigned an outbound queue on the basis of that priority (regardless of the port-based priority configured on the port).
Page 224: Messages Related To Prioritization
Port Status and Basic Configuration Configuring Port-Based Priority for Incoming Packets For example, suppose you wanted to configure ports A10 -A12 on the switch to prioritize all untagged, inbound VLAN traffic as “Low” (priority level = 1; refer to table 10-3 on page 10-29). Configures port-based priority on ports A9 -A12 to "1"...
Page 225: Using Friendly (Optional) Port Names
Port Status and Basic Configuration Using Friendly (Optional) Port Names Using Friendly (Optional) Port Names Feature Default Menu Configure Friendly Port Names Standard Port page 34 Numbering Display Friendly Port Names page 35 This feature enables you to assign alphanumeric port names of your choosing to augment automatically assigned numeric port names.
Page 226: Configuring Friendly Port Names
Port Status and Basic Configuration Using Friendly (Optional) Port Names To retain friendly port names across reboots, you must save the current ■ running-configuration to the startup-config file after entering the friendly port names. (In the CLI, use the write memory command.) Configuring Friendly Port Names Syntax: interface <port-list>...
Page 227: Displaying Friendly Port Names With Other Port Data
Port Status and Basic Configuration Using Friendly (Optional) Port Names Figure 10-16. Example of Configuring One Friendly Port Name on Multiple Ports 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 ■...
Page 228 Port Status and Basic Configuration Using Friendly (Optional) Port Names For example: Ports Without "Friendly" Name Friendly port names assigned in previous examples. Figure 10-17. Example of Friendly Port Name Data for All Ports on the Switch Port Without a "Friendly" Name Friendly port names assigned in previous...
Page 229 Port Status and Basic Configuration Using Friendly (Optional) Port Names Friendly Port Name Figure 10-19. Example of a Friendly Port Name in a Per-Port Statistics Listing 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...
Page 230 Port Status and Basic Configuration Using Friendly (Optional) Port Names For example, if you configure port A1 with a friendly port name: This command sequence saves the friendly port name for port A1 in the startup config file, but does not do so for the name entered for port Listing includes friendly port name for port A1...
Page 231: Uni-Directional Link Detection (Udld)
When UDLD is enabled on the trunk ports on each ProCurve switch, the switches detect the failed link, block the ports connected to the failed link, and use the remaining ports in the trunk group to forward the traffic.
Page 232: Configuring Udld
When configuring UDLD, keep the following considerations in mind: ■ UDLD is configured on a per-port basis and must be enabled at both ends of the link. See the note below for a list of ProCurve switches that support UDLD. ■...
Page 233: Enabling Udld
Enabling UDLD UDLD is enabled on a per port basis. For example, to enable UDLD on port a1, enter: ProCurve(config)#interface al link-keepalive To enable the feature on a trunk group, enter the appropriate port range. For example: ProCurve(config)#interface al-a4 link-keepalive...
Page 234: Changing The Keepalive Interval
The default implementation of UDLD sends the UDLD control packets untagged, even across tagged ports. If an untagged UDLD packet is received by a non-ProCurve switch, that switch may reject the packet. To avoid such an occurrence, you can configure ports to send out UDLD control packets that are tagged with a specified VLAN.
Page 235: Viewing Udld Information
Port Status and Basic Configuration Uni-Directional Link Detection (UDLD) N o t e s You must configure the same VLANs that will be used for UDLD on ■ all devices across the network; otherwise, the UDLD link cannot be maintained. If a VLAN ID is not specified, then UDLD control packets are sent out ■...
Page 236 Port Status and Basic Configuration Uni-Directional Link Detection (UDLD) To display summary information on all UDLD-enabled ports, enter the show link-keepalive command. For example: ProCurve(config)# show link-keepalive Total link-keepalive enabled ports: 4 Keepalive Retries: Keepalive Interval: 1 sec Port 1 is UDLD-enabled, and tagged for a specific VLAN.
Page 237 To display detailed UDLD information for specific ports, enter the show link keepalive statistics command. For example: Ports 1 and 2 are UDLD-enabled and show the number of health check packets sent and received on each port. ProCurve(config)# show link-keepalive statistics Port: Current State: Neighbor MAC Addr: 0000a1-b1c1d1...
Page 238: Configuration Warnings And Event Log Messages
Port Status and Basic Configuration Uni-Directional Link Detection (UDLD) Configuration Warnings and Event Log Messages Warning Messages. The following table shows the warning messages that may be issued and their possible causes, when UDLD is configured for tagged ports. Table 10-1. Warning Messages caused by configuring UDLD for Tagged Ports CLI Command Example Warning Message Possible Problem...
Page 239: Power Over Ethernet (Poe) Operation
Power Over Ethernet (PoE) Operation Contents Overview ........... . . 11-2 Configuration Options .
Page 240: Overview
(PD) to a PoE-enabled port without reconfiguring the port. Configuration Options In the default configuration, all 10/100Base-TX ports on the ProCurve switches 2610-24-PWR and 2610-48-PWR support PoE operation. The ProCurve Switch 2610-24/12-PWR supports PoE operation on 12 ports. Using the commands described in this chapter, you can: ■...
Page 241: Related Publications
PoE provisioning on the switch becomes oversubscribed. External Power Supply; for example, a ProCurve 600 RPS/EPS or a ProCurve 610 EPS. An EPS device provides power to provision PoE ports on a switch. See also “RPS” below.
Page 242: Power Availability And Provisioning
Power Over Ethernet (PoE) Operation Power Availability and Provisioning Power Availability and Provisioning Powered Device (PD) Support The switch must have a minimum of 15.4 watts of unused PoE power available when you connect an 802.3af-compliant PD, regardless of how much power the PD actually uses.
Page 243: Power Priority
PoE-capable switches, refer to the PoE Planning and Implementation Guide. Table 11-1 provides examples of how PoE priority settings impact operation. Table 11-1. Example of PoE Priority Operation on the ProCurve 2510-48-PWR Port Priority...
Page 244 9, until all available power is in use. For this example, the CLI command to set ports to “High” is: ProCurve(config)# interface e 9-12 power high 1 - 8 This priority class receives power only if all PDs on ports with High and Critical priority settings are receiving power.
Page 245: Configuring Poe Operation
Power Over Ethernet (PoE) Operation Configuring PoE Operation Configuring PoE Operation By default, PoE support is enabled on the switch’s 10/100Base-TX ports, with the power priority set to Low and the power threshold set to 80 (%). The following commands allow you to adjust these settings. Syntax: power threshold <...
Page 246: Cycling Power On A Port
To cycle the power on a PD receiving power from a PoE port on the switch, disable, then re-enable the power to that port. For example, to cycle the power on a PoE device connected to port 1 on a switch covered in this guide: ProCurve(config)# no interface 1 power ProCurve(config)# interface 1 power 11-8...
Page 247: Poe For Pre-802.3Af-Standard Pds
IEEE specification. This allows non-compliant devices to be powered. For a current listing of PDs supported by this feature, visit the ProCurve Networking website at www.procurve.com. Click on Technical support, and then on FAQs, and then select the switch model.
Page 248 Power Over Ethernet (PoE) Operation Configuring PoE Operation For information on the meaning of other power status parameters, refer to “Viewing PoE Configuration and Status” on page 11-11. 11-10...
Page 249: Viewing Poe Configuration And Status
For example, in the default PoE configuration, when the switch is running with several ports supporting PD loads, show power-management displays data similar to the following: ProCurve(config)# show power-management Status and Counters - System Power Status Pre-standard Detect : Off...
Page 250: Displaying An Overview Of Poe Status On All Ports
Power Over Ethernet (PoE) Operation Viewing PoE Configuration and Status Displaying an Overview of PoE Status on All Ports Syntax: show power-management brief Displays the following port power status: • Port: Lists all PoE-capable ports on the switch. • Power Enable: Shows Yes for ports on which PoE is enabled (the default) and No for ports on which PoE is disabled.
Page 251: Displaying The Poe Status On Specific Ports
Power Over Ethernet (PoE) Operation Viewing PoE Configuration and Status Displaying the PoE Status on Specific Ports Syntax: show power-management <port-list> Displays the following PoE status and statistics (since the last reboot) for each port in < port-list >: • Power Enable: Shows Yes for ports enabled to support PoE (the default) and No for ports on which PoE is disabled.
Page 252: Planning And Implementing A Poe Configuration
Planning and Implementing a PoE Configuration This section provides an overview of some considerations for planning a PoE application. For additional information, refer to the ProCurve PoE Planning and Implementation Guide. Assigning PoE Ports to VLANs If your network includes VLANs, you may want to assign various PoE...
Page 253: Poe Event Log Messages
Power Over Ethernet (PoE) Operation PoE Event Log Messages MAC Address Security: Using Port Security, you can configure each ■ switch port with a unique list of up to eight MAC addresses for devices that are authorized to access the network through that port. For more information, refer to the chapter titled “Configuring and Monitoring Port Security”...
Page 254 • Fan fault: A fan in an external power supply has failed. • Temperature fault: The operating temperature in an external power supply has exceeded the normal operating range. • 50V fault: The ProCurve 600 RPS/EPS or ProCurve 610 EPS reported a fault condition. Contact your ProCurve support representative.
Page 255 Power Over Ethernet (PoE) Operation PoE Event Log Messages POE usage has exceeded threshold of < 1 - 99 > % < slot-# > POE usage has exceeded threshold of < 1 - 99 > % Indicates that POE usage in the switch or indicated slot (if the switch includes module slots) has exceeded the configured threshold for the switch, as specified by the last execution of the power threshold <...
Page 256 Power Over Ethernet (PoE) Operation PoE Event Log Messages 11-18...
Page 257 Port Trunking Contents Overview ........... . . 12-2 Port Status and Configuration .
Page 258: Port Trunking
This capability applies to connections between backbone devices as well as to connections in other network areas where traffic bottlenecks exist. Port Trunking Support ProCurve Switch ProCurve Switch 2610-24 2610-48 Ports per trunk (maximum) Trunks per switch (maximum) A trunk group is a set of ports configured as members of the same port trunk.
Page 259: Port Connections And Configuration
LACP (IEEE 802.3ad—page 12-15) Trunk (non-protocol—page 12-21) ■ The ProCurve 2610-24 switch supports twelve trunk groups of up to eight ports each. The ProCurve 2610-48 supports twenty-four trunk groups of up to eight ports each. (Using the Link Aggregation Control Protocol—LACP—option, you can include standby trunked ports in addition to the maximum of four actively trunking ports.)
Page 260: Trunk Configuration Methods
L A C P N o t e LACP operation requires full-duplex (FDx) links. For most installations, ProCurve recommends that you leave the port Mode settings at Auto (the default). LACP also operates with Auto-10, Auto-100, and Auto-1000 (if negotia...
Page 261 See “Trunk Group Operation Using LACP” on page 12-15. Trunk Provides manually configured, static-only trunking to: (non- • Most ProCurve switches and routing switches not running the 802.3ad LACP protocol. protocol) • Windows NT and HP-UX workstations and servers Use the Trunk option when: – The device to which you want to create a trunk link is using a non-802.3ad trunking protocol...
Page 262 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...
Page 263 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 264: Menu: Viewing And Configuring A Static Trunk Group
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.
Page 265 Port Trunking Port Status and Configuration • All ports in a trunk must have the same media type and mode (such as 10/100TX set to 100FDx, or 100FX set to 100FDx). The flow control settings must also be the same for all ports in a given trunk. To verify these settings, see “Viewing Port Status and Configuring Port Param...
Page 266: Cli: Viewing And Configuring A Static Or Dynamic Port Trunk Group
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 Configur ing Port Parameters”...
Page 267 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.
Page 268: Using The Cli To Configure A Static Or Dynamic Trunk Group
Port Trunking Port Status and Configuration Listing Static LACP and Dynamic LACP Trunk Data. This command lists data for only the LACP-configured ports. Syntax: show lacp In the following example, ports A1 and A2 have been previously configured for a static LACP trunk. (For more on “Active”, see table 12-5 on page 12-18.) Figure 12-6.
Page 269 Removing a port from a trunk can result in a loop and cause a broadcast storm. When you remove a port from a trunk where STP is not in use, ProCurve recommends that you first disable the port or disconnect the link on that port.
Page 270 < port-list > lacp active This example uses ports C4 and C5 to enable a dynamic LACP trunk group. ProCurve(config)# interface c4-c5 lacp active Removing Ports from a Dynamic LACP Trunk Group. To remove a port from dynamic LACP trunk operation, you must turn off LACP on the port. (On...
Page 271: Web: Viewing Existing Port Trunk Groups
Unless STP is running on your network, removing a port from a trunk can result in a loop. To help prevent a broadcast storm when you remove a port from a trunk where STP is not in use, ProCurve recommends that you first disable the port or disconnect the link on that port.
Page 272 Port Trunking Port Status and Configuration LACP trunk status commands include: Trunk Display Method Static LACP Trunk Dynamic LACP Trunk show lacp command Included in listing. Included in listing. show trunk command Included in listing. Not included. Port/Trunk Settings screen in menu interface Included in listing.
Page 273 (ProCurve 2610-24) or 1-24 (ProCurve 2610-48), depending on how many dynamic and static trunks are currently on the switch. (The ProCurve Switch 2610-24 allow a maximum of twelve trunk groups in any combination of static and dynamic trunks; the ProCurve switch 2610-48 allows a maximum of twenty- four trunk groups in any combination of static and dynamic trunks.)
Page 274: Default Port Operation
The following table describes the elements of per-port LACP operation. To display this data for a particular switch, execute the following command in the CLI: ProCurve> show lacp Table 12-5. LACP Port Status Data Status Name Meaning Port Numb Shows the physical port number for each port configured for LACP operation (C1, C2, C3 .
Page 275: Lacp Notes And Restrictions
LACP configuration, displays a notice that LACP is disabled on the port(s), and enables port security on that port. For example: ProCurve(config)# port-security a17 learn-mode static address-limit 2 LACP has been disabled on secured port(s). The switch will not allow you to configure LACP on a port on which port security is enabled.
Page 276 Port Trunking Port Status and Configuration ProCurve(config)# int a17 lacp passive Error configuring port A17: LACP and port security cannot be run together. To restore LACP to the port, you must remove port security and re-enable LACP active or passive.
Page 277: Trunk Group Operation Using The "Trunk" Option
Port Trunking Port Status and Configuration Easy control methods include either disabling LACP on the selected ports or configuring them to operate in static LACP trunks. STP and IGMP. If spanning tree (STP) and/or IGMP is enabled in the switch, a dynamic LACP trunk operates only with the default settings for these features and does not appear in the port listings for these features.
Page 278: Outbound Traffic Distribution Across Trunked Links
In actual networking environments, this is rarely a problem. However, if it becomes a problem, you can use the ProCurve Man ager Plus network management software to quickly and easily identify the sources of heavy traffic (top talkers) and make adjustments to improve performance.
Page 279 Port Trunking Port Status and Configuration Broadcasts, multicasts, and floods from different source addresses are dis tributed evenly across the links. As links are added or deleted, the switch redistributes traffic across the trunk group. For example, in figure 12-9 show ing a three-port trunk, traffic could be assigned as shown in table 12-6.
Page 280 Port Trunking Port Status and Configuration 12-24...
Page 281: Configuring For Network Management Applications
Configuring for Network Management Applications Contents Overview ........... . . 12-2 Port Status and Configuration .
Page 282 Configuring for Network Management Applications Contents LLDP Configuration Options ....... . 13-31 Options for Reading LLDP Information Collected by the Switch .
Page 283: 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 products index in the sidebar, then click on the appropriate link appearing under the Network Management heading.
Page 284: Snmp Management Features
The switch SNMP agent also uses certain variables that are included in a Hewlett-Packard proprietary MIB (Management Information Base) file. To ensure that you have the latest version in the database of your SNMP network management tool, you can copy the MIB file from the ProCurve Networking web site at: www.procurve.com Click on software, then MIBs.
Page 285: Configuring For Snmp Version 3 Access To The Switch
IP Authorized Manager feature. (Refer to the Access Security Guide for your switch.) C a u t i o n 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).
Page 286: Snmp Version 3 Commands
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: Enable SNMPv3 with the snmpv3 enable command. An initial user entry ■...
Page 287: Snmpv3 Enable
(given fewer features), but not upgraded with new features added. For this I n i t i a l U s e r s reason ProCurve recommends that you create a second user with SHA and DES at when you enable SNMPv3...
Page 288: Snmp Version 3 Users
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: Add the users to the User table.
Page 289 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 group group_name user user_name sec-model <ver1| ver2c | ver3> (— Continued —) user user_name This is the user to be added to the access group. This must match the user name added with the snmpv3 user command...
Page 290 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”...
Page 291: Group Access Levels
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 292: Snmp Communities
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.
Page 293 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Figure 13-4 shows the assigning of the Operator community on MgrStation1 to the CommunityOperatorReadWrite group. Any other Operator only has an access level of CommunityOperatorReadOnly. Add mapping to allow write access for Operator community on MgrStation1 Two Operator Access Levels Figure 13-4.
Page 294: Menu: Viewing And Configuring Non-Snmp Version 3 Communities
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch C a u t i o n 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”...
Page 295 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, Type the value for this field. the values for the currently selected Use the Space bar to select Community appear...
Page 296: Cli: Viewing And Configuring Snmp Community Names
— see “SNMP Notification and Traps” on page 13-18). Syntax: show snmp-server [<community-string>] This example lists the data for all communities in a switch; that is, both the default ProCurve "public" community name and another community named "blue-team". Default Community and Settings...
Page 297 (Access to all MIB objects (read-only) except the CONFIG MIB.) ProCurve(config)# snmp-server community red-team manager unrestricted ProCurve(config)# snmp-server community blue-team operator restricted To eliminate a previously configured community named "gold-team": ProCurve(config) # no snmp-server community gold-team 13-17...
Page 298: Snmp Notification And Traps
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 13-20. The SNMPv3 notification process allows for the messages passed to be authenticated and encrypted if you choose.
Page 299 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 targetaddress < addr-name > params < parms-name> < IP-Addr > ( — Continued — ) max-msg-size<size> The maximum number of bytes of length a message to this target can be.
Page 300: Trap Features
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Trap Features Feature Default Menu snmp-server host (trap receiver) public — page — 13-21 snmp-server enable (authentication trap) none — page — 13-25 A trap receiver is a management station designated by the switch to receive SNMP traps sent from the switch.
Page 301: Configuring Trap Receivers
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”...
Page 302: Enabling And Configuring Snmp Inform
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch N o t e 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 303 You must specify an IP address that will receive the notifications and the community name. N o t e The retries and timeout options are not used when using trap requests. ProCurve Switch# show snmp-server SNMP Communities Community Name MIB View Write Access...
Page 304: Sending Event Log Messages As Traps
Send the log messages that are not information-only. Critical Send critical-level log messages. Debug Reserved for ProCurve-internal use. 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 trap-receiver red-team 10.28.227.130 critical...
Page 305: Advanced Management: Rmon
For example: ProCurve(config)# snmp-server enable traps authentication Check the Event Log in the console interface to help determine why the authentication trap was sent. (Refer to “Using Logging To Identify Problem Sources”...
Page 306: Configuring Sflow
Configuring for Network Management Applications Using SNMP Tools To Manage the Switch sFlow agent — A software process that runs as part of the network manage ment software within a device. The agent packages data into datagrams that are forwarded to a central data collector. sFlow destination —...
Page 307: Viewing Sflow Configuration And Status
Agent Address 10.0.10.228 Figure 13-11. Example of Viewing sFlow Agent Information The show sflow <instance> destination command includes information about the management-station’s destination address, receiver port, and owner. ProCurve# show sflow 2 destination Destination Instance sflow Enabled Datagrams Sent Destination Address 10.0.10.41...
Page 308 You can specify a list or range of ports for which to view sampling information. ProCurve# show sflow 2 sampling-polling A1-A4 Number denotes the sampling/polling instance to which the receiver is coupled.
Page 309: Lldp (Link-Layer Discovery Protocol)
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 310: Lldp Terminology
Active Port: A port linked to another active device (regardless of whether STP is blocking the link). LLDP: Link Layer Discovery Protocol. ProCurve switches are compatible with IEEE 802.1AB-2005. LLDP-Aware: A device that has LLDP in its operating code, regardless of whether LLDP is enabled or disabled.
Page 311: General Lldp Operation
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) General LLDP Operation An LLDP packet contains data about the transmitting switch and port. The switch advertises itself to adjacent (neighbor) devices by transmitting LLDP data packets out all ports on which outbound LLDP is enabled, and reading LLDP advertisements from neighbor devices on ports that are inbound LLDP- enabled.
Page 312 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Transmit and Receive Mode. With LLDP enabled, the switch periodically transmits an LLDP advertisement (packet) out each active port enabled for outbound LLDP transmissions, and receives LLDP advertisements on each active port enabled to receive LLDP traffic (page 13-43). Per-Port configuration options include four modes: ■...
Page 313 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Data Type Configuration Default Description Options Remote Management Address 4, 6 Type Always Enabled Shows the network address type. Address Default or Uses a default address selection method unless an optional address is Configured configured.
Page 314: Options For Reading Lldp Information Collected By The Switch
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Options for Reading LLDP Information Collected by the Switch You can extract LLDP information from the switch to identify adjacent LLDP devices. Options include: Using the switch’s show lldp info command options to display data ■...
Page 315: Lldp Operating Rules
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) 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. Also, LLDP sends separate advertisements on each port in a trunk, and not on a per-trunk basis.
Page 316: Lldp Operation And Commands
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Operation and Commands In the default configuration, LLDP is enabled and in both transmit and receive mode on all active ports. The LLDP configuration includes global settings that apply to all active ports on the switch, and per-port settings that affect only the operation of the specified ports.
Page 317 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 13-39). Figure 13-15. Example of Viewing the General LLDP Configuration Displaying Port Configuration Details.
Page 318: Configuring Global Lldp Packet Controls
LLDP configuration when LLDP is disabled. After LLDP is disabled, the information in the LLDP neighbors database remains until it times-out. (Default: Enabled) For example, to disable LLDP on the switch: ProCurve(config)# no lldp run 13-38...
Page 319 Time-to-Live for advertisements transmitted from the switch is 60 seconds (4 x 15). To reduce the Time-to-Live, you could lower the holdtime-interval to 2, which would result in a Time-to- Live of 30 seconds. ProCurve(config)# lldp holdtime-multiplier 2 13-39...
Page 320 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Changing the Delay Interval Between Advertisements Generated by Value or Status Changes to the LLDP MIB. The switch uses a delay- interval setting to delay transmitting successive advertisements resulting from these LLDP MIB changes. If a switch is subject to frequent changes to its LLDP MIB, lengthening this interval can reduce the frequency of successive advertisements.
Page 321: Configuring Snmp Notification Support
(Default: 2 seconds; Range: 1 - 10 seconds) For example, the following command changes the reinitialization delay interval to five seconds: ProCurve(config)# setmib lldpreinitdelay.0 -i 5 Configuring SNMP Notification Support You can enable SNMP trap notification of LLDP data changes detected on advertisements received from neighbor devices, and control the interval between successive notifications of data changes on the same neighbor.
Page 322 Refer to IEEE 802.1AB-2005 or later for more information.) (Default: 5 seconds) For example, the following command limits change notification traps from a particular switch to one per minute. ProCurve(config)# setmib lldpnotificationinterval.0 -i 60 lldpNotificationInterval.0 = 60 13-42...
Page 323: Configuring Per-Port Lldp Transmit And Receive Modes
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Configuring Per-Port LLDP Transmit and Receive Modes These commands control LLDP advertisement traffic inbound and outbound on active ports. Syntax lldp admin-status < port-list > < txonly | rxonly | tx_rx | disable > With LLDP enabled on the switch in the default LLDP configuration, each port is configured to transmit and receive LLDP packets.
Page 324 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 325: Displaying Advertisement Data
For example, if you wanted to exclude the system name from the outbound LLDP advertisements for all ports on a 2626 switch, you would use this command: ProCurve(config)# no lldp config 1-26 basicTlvEnable system_name If you later decided to reinstate the system name on ports 1-5, you would use...
Page 326: Displaying Switch Information Available For Outbound Advertisements
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 327 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 LLDP...
Page 328 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax show lldp info remote-device [ port-list ] Without the [ port-list ] option, this command provides a global list of the individual devices it has detected by reading LLDP advertisements (and also CDP advertisements). Discovered devices are listed by the inbound port on which they were discovered.
Page 329 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) The data shown for port 3 was translated from a CDP advertisement from a 5300xl switch with LLDP disabled. (Not all fields expected by the LLDP device are populated with the CDP data.) Figure 13-20.
Page 330: Displaying Lldp Statistics
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 331 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) — Continued from the preceding page. — Per-Port LLDP Counters: NumFramesRecvd: Shows the total number of valid, inbound LLDP advertisements received from any neighbor(s) on < port- list >. Where multiple neighbors are connected to a port through a hub, this value is the total number of LLDP advertisements received from all sources.
Page 332 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 LLDP- aware.
Page 333: Lldp Operating Notes
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. The switch can support multiple neighbors connected through a hub on a given port, but if the switch neighbor maximum is reached, advertisements from additional neighbors on the same or other ports will not be stored in the neighbors table unless some existing neighbors time-out or are removed.
Page 334: Lldp And Cdp Data Management
LLDP packets received from neighbor devices. CDP operation is limited to reading incoming CDP packets from neighbor devices. (ProCurve switches do not generate CDP packets.) LLDP and CDP Neighbor Data With both LLDP and (read-only) CDP enabled on a switch port, the port can read both LLDP and CDP advertisements, and stores the data from both types of advertisements in its neighbor database.
Page 335 LLDP (Link-Layer Discovery Protocol) N o t e 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.
Page 336: Cdp Operation And Commands
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 337 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 13-24. 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 338 Disabling CDP on a port causes it to drop inbound CDP packets without recording their data in the CDP Neighbors table. Syntax: [no] cdp enable < [e] port-list > For example, to disable CDP on port A1: ProCurve(config)# no cdp enable a1 13-58...
Page 339 CLI: Switch-To-Switch Downloads ..... . . A-15 Using ProCurve Manager Plus to Update Switch Software ..A-16 Troubleshooting TFTP Downloads .
Page 340: Overview
Downloading Switch Software ProCurve Networking periodically provides switch software updates through the ProCurve website (www.procurve.com). For more information, see the support and warranty booklet shipped with the switch. After you acquire a new switch software file, you can use one of the following methods for...
Page 341: General Switch Software Download Rules
An switch software file for the switch has been stored on a TFTP server ■ accessible to the switch. (The switch software file is typically available from the ProCurve website at www.procurve.com.) The switch is properly connected to your network and has already been ■...
Page 342: Menu: Tftp Download From A Server To Primary Flash
File Transfers Downloading Switch Software N o t e 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.
Page 343 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...
Page 344: Cli: Tftp Download From A Server To Primary Or Secondary Flash
You will need to reboot to activate. At this point, use the boot command to reboot the switch and activate the software you just downloaded: ProCurve # boot (For more on these commands, refer to “Rebooting the Switch” on page 6-18.) 4. To confirm that the switch software downloaded correctly, execute show...
Page 345: Using Secure Copy And Sftp
As described earlier in this chapter you can use a TFTP client on the admin istrator workstation to update software images. This is a plain text mechanism and it connects to a standalone TFTP server or another ProCurve switch acting as a TFTP server to obtain the software image file(s). Using SCP and SFTP allows you to maintain your switches with greater security.
Page 346: How It Works
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.
Page 347: The Scp/Sftp Process
As a matter of policy, administrators should not enable the SSHv1-only or the SSHv1-or-v2 advertisement modes. SSHv1 is supported on only some legacy switches (such as the ProCurve Series 2500 switches). To confirm that SSH is enabled type in the command ProCurve(config)# show ip ssh 3. Once you have confirmed that you have enabled an SSH session (with the...
Page 348: Authentication
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.
Page 349: Using Xmodem To Download Switch Software From A Pc Or Unix Workstation
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. The switch displays the following files: +---cfg running-config startup-config +---log crash-data crash-log event log +---os primary secondary...
Page 350: Cli: Xmodem Download From A Pc Or Unix Workstation To Primary Or Secondary Flash
File Transfers Downloading Switch Software 7. Download OS (for Edit). 2. Press 3. Use the Space bar to select XMODEM in the Method field. 4. Press , then (for eXecute) to begin the switch software download. [Enter] The following message then appears: Press enter and then initiate Xmodem transfer from the attached computer..
Page 351 File Transfers Downloading Switch Software Note that if you do not specify the flash destination, the Xmodem download defaults to primary flash. For example, to download a switch software file named G0103.swi from a PC (running a terminal emulator program such as HyperTerminal) to primary flash: 1. Execute the following command in the CLI: Figure A-4. Example of the Command to Download Switch Software Using...
Page 352: Switch-To-Switch Download
File Transfers Downloading Switch Software Switch-to-Switch Download You can use TFTP to transfer a switch software file between two ProCurve switches that use the same software code base. The menu interface enables you to transfer primary-to-primary or secondary-to-primary. The CLI enables all combinations of flash location options.
Page 353: Cli: Switch-To-Switch Downloads
File Transfers Downloading Switch Software General System Information b. Check the Firmware revision line. CLI: Switch-To-Switch Downloads You can download a switch software file between two switches that use the same code base and which are connected on your LAN. To do so, use a copy tftp command from the destination switch.The options for this CLI feature include: Copy from primary flash in the source to either primary or secondary in...
Page 354: Using Procurve Manager Plus To Update Switch Software
Destination Using ProCurve Manager Plus to Update Switch Software ProCurve Manager Plus include a software update utility for updating on ProCurve switch products. For further information, refer to the Getting Started Guide and the Administrator’s Guide, provided electronically with the application.
Page 355: Troubleshooting Tftp Downloads
To find more information on the cause of a download failure, examine the messages in the switch’s Event Log by executing this CLI command: ProCurve# show log tftp (For more on the Event Log, see “Using Logging To Identify Problem Sources”...
Page 356: Transferring Switch Configurations
(Refer to Chapter 6, “Switch Memory and Configuration” for information on the startup-config file.) For example, to download a configuration file named sw2610 in the configs directory on drive "d" in a remote host having an IP address of 10.28.227.105: ProCurve# copy tftp startup-config 10.28.227.105 d:\configs\sw2610 A-18...
Page 357 For example, to upload the current startup configuration to a file named sw2610 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.105 d:\configs\sw2610 Xmodem: Copying a Configuration File from the Switch to a Serially Connected PC or Unix Workstation.
Page 358 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.
Page 359: Copying Diagnostic Data To A Remote Host, Pc, Or Unix Workstation
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: ■...
Page 360: Copying Event Log Output To A Destination Device
File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Event Log Output to a Destination Device This command uses TFTP or Xmodem to copy the Event Log content to a PC or UNIX workstation on the network. Syntax: copy event-log tftp <...
Page 361: Copying Crash Log Data Content To A Destination Device
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.
Page 362 File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation A-24...
Page 363 Monitoring and Analyzing Switch Operation Contents Overview ........... . . B-3 Status and Counters Data .
Page 364 Monitoring and Analyzing Switch Operation Contents Menu: Configuring Port and Static Trunk Monitoring ... B-24 CLI: Configuring Port and Static Trunk Monitoring ... . . B-26 Web: Configuring Port Monitoring .
Page 365: Overview
Monitoring and Analyzing Switch Operation Overview Overview The switch has several built-in tools for monitoring, analyzing, and trouble shooting switch and network operation: ■ Status: Includes options for displaying general switch information, man agement address data, port status, port and trunk group statistics, MAC addresses detected on each port or VLAN, and STP, IGMP, and VLAN data (page B-4).
Page 366: Status And Counters Data
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. N o t e You can access all console screens from the web browser interface via Telnet to the console.
Page 367: Menu Access To Status And Counters
Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access To Status and Counters Beginning at the Main Menu, display the Status and Counters menu by select ing: 1. Status and Counters Figure B-1. The Status and Counters Menu Each of the above menu items accesses the read-only screens described on the following pages.
Page 368: General System Information
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.
Page 369: Switch Management Address Information
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.
Page 370: Module Information
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.
Page 371: Port Status
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.
Page 372: Viewing Port And Trunk Group Statistics And Flow Control Status
Monitoring and Analyzing Switch Operation Status and Counters Data Viewing Port and Trunk Group Statistics and Flow Control Status Feature Default Menu viewing port and trunk statistics for all page B-11 page B-12 page B-12 ports, and flow control status viewing a detailed summary for a page B-11 page B-12...
Page 373: Menu Access To Port And Trunk Statistics
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.
Page 374: Cli Access To Port And Trunk Group Statistics
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.
Page 375: Menu Access To The Mac Address Views And Searches
Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access to the MAC Address Views and Searches Per-VLAN MAC-Address Viewing and Searching. This feature lets you determine which switch port on a selected VLAN is being used to communi cate with a specific device on the network.
Page 376 Monitoring and Analyzing Switch Operation Status and Counters Data Finding the Port Connection for a Specific Device on a VLAN. This feature uses a device’s MAC address that you enter to identify the port used by that device. 1. Proceeding from figure B-8, press (for Search), to display the following prompt: Enter MAC address: _...
Page 377: Cli Access For Mac Address Views And Searches
[< 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 B-15...
Page 378 To List All Learned MAC Addresses on a VLAN, with Their Port Numbers. This command lists the MAC addresses associated with the ports for a given VLAN. For example: ProCurve> show mac-address vlan 100 N o t e The switch operates with a multiple forwarding database architecture. For more on this topic, refer to “Duplicate MAC Addresses Across VLANs”...
Page 379: Spanning Tree Protocol (Stp) Information
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.
Page 380: Cli Access To Stp Data
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). Syntax: show spanning-tree ProCurve> show spanning-tree B-18...
Page 381: Internet Group Management Protocol (Igmp) Status
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: •...
Page 382: Vlan Information
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) •...
Page 383 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 VLAN...
Page 384: Web Browser Interface Status Information
Monitoring and Analyzing Switch Operation Status and Counters Data Web Browser Interface Status Information The “home” screen for the web browser interface is the Status Overview screen, as shown below. As the title implies, it provides an overview of the status of the switch, including summary graphs indicating the network utili...
Page 385: Port And Static Trunk Monitoring Features
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Port and Static Trunk Monitoring Features Port Monitoring Features Feature Default Menu display monitoring disabled page B-24 page B-26 page B-28 configuration configure the monitor port(s) ports: none page B-24 page B-26 page B-28 selecting or removing ports none selected page B-24 page B-27 page B-28 You can designate a port for monitoring inbound (ingress) and outbound...
Page 386: Menu: Configuring Port And Static Trunk Monitoring
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Menu: Configuring Port and Static Trunk Monitoring This procedure describes configuring the switch for monitoring when moni toring is disabled. (If monitoring has already been enabled, the screens will appear differently than shown in this procedure.) 1. From the Console Main Menu, Select: 2.
Page 387 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.
Page 388: Cli: Configuring Port And Static Trunk Monitoring
Remov ing the monitor port disables port monitoring and resets the monitoring parameters to their factory-default settings. Syntax: [no] mirror-port [< port-num >] For example, to assign port A6 as the monitoring port: ProCurve(config)# mirror-port a6 B-26...
Page 389 Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features To turn off monitoring: ProCurve(config)# no mirror-port Selecting or Removing Ports and Static Trunks As Monitoring Sources. After you configure a monitor port you can use either the global configuration level or the interface context level to select ports and static trunks as monitoring sources.
Page 390: Web: Configuring Port Monitoring
Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Web: Configuring Port Monitoring To enable port monitoring: Click on the Configuration tab. Click on Monitor Port. To monitor one or more ports. Click on the radio button for Monitor Selected Ports. b.
Page 391 Troubleshooting Contents Overview ........... . . C-3 Troubleshooting Approaches .
Page 392 Troubleshooting Contents Displaying the Configuration File ......C-37 CLI: Viewing the Configuration File ..... . C-37 Web: Viewing the Configuration File .
Page 393: Overview
For information on support and warranty provisions, see the Support and Warranty booklet shipped with the switch. Troubleshooting Approaches Use these approaches to diagnose switch problems: Check the ProCurve web site – the web site may have software updates ■ or other information to help solve your problem: www.procurve.com ■...
Page 394 Status and Counters screens – Event Log – Diagnostics tools (Link test, Ping test, configuration file browser, and advanced user commands) • ProCurve Manager / ProCurve Manager + – Use ProCurve Man ager to help isolate problems and recommend solutions.
Page 395: Browser Or Telnet Access Problems
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.
Page 396 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.
Page 397: Unusual Network Activity
Unusual network activity is usually indicated by the LEDs on the front of the switch or measured with the switch console interface or with a network management tool such as the ProCurve Manager. Refer to the Installation Guide you received with the switch for information on using LEDs to identify unusual network activity.
Page 398: Prioritization Problems
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”...
Page 399: Lacp-Related Problems
Removing a port from a trunk without first disabling the port can create a traffic loop that can slow down or halt your network. Before removing a port from a trunk, ProCurve recommends that you either disable the port or disconnect it from the LAN.
Page 400 Troubleshooting Unusual Network Activity 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 ■ servers. Verify that the switch is using the correct encryption key (RADIUS secret ■...
Page 401 Troubleshooting Unusual Network Activity unauthorized. 802.1X is not active on the switch. After you execute aaa port- access authenticator active, all ports configured with control unauthorized should be listed as Closed. Port A9 shows an “Open” status even though Access Control is set to Unauthorized (Force Auth).
Page 402 Troubleshooting Unusual Network Activity Global RADIUS Encryption Key Unique RADIUS Encryption Key for the RADIUS server at 10.33.18.119 Figure C-2. 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.1X configuration on that port.
Page 403: Radius-Related Problems
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.
Page 404: Spanning-Tree Protocol (Stp) And Fast-Uplink Problems
Troubleshooting Unusual Network Activity Spanning-Tree Protocol (STP) and Fast-Uplink Problems C a u t i o n 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.
Page 405: Ssh-Related Problems
Troubleshooting Unusual Network Activity SSH-Related Problems Switch access refused to a client. Even though you have placed the cli ent’s public key in a text file and copied the file (using the copy tftp pub-key file command) into the switch, the switch refuses to allow the client to have access.
Page 406: Stacking-Related Problems
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 <CR><LF>.
Page 407 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.
Page 408: Timep, Sntp, Or Gateway Problems
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.
Page 409 Troubleshooting Unusual Network Activity None of the devices assigned to one or more VLANs on an 802.1Q compliant 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.
Page 410 You can avoid this problem by creating redundant paths using port trunks or spanning tree. MAC Address “A”; VLAN 1 Server VLAN 1 Switch with ProCurve Single Switches Covered MAC Address “A”; VLAN 2 Forwarding by this Guide...
Page 411: Using Logging To Identify Problem Sources
Troubleshooting Using Logging To Identify Problem Sources Using Logging To Identify Problem Sources Event Log Operation The Event Log records operating events as single-line entries listed in chrono logical order, and serves as a tool for isolating problems. Each Event Log entry is composed of five fields: Severity Date...
Page 412 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.Event Log System Modules Module Event Description Module Event Description addrMgr Address table Console management chassis switch hardware ports Change in port status;...
Page 413: Menu: Entering And Navigating In The Event Log
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-7. 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 414: Cli
Lists recorded log messages since last reboot. ProCurve> show logging -a Lists all recorded log messages, including those before the last reboot. ProCurve> show logging -a system Lists log messages with “system” in the text or module name. ProCurve> show logging system Lists all log messages since the last reboot that have “system”...
Page 415: Debug And Syslog Operation
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 •...
Page 416: Debug Types
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 > Configures the switch to send all debug types to the config ured debug destination(s).
Page 417: Configuring The Switch To Send Debug Messages To One Or More Syslogd Servers
< facility-name > Specifies the destination subsystem the SyslogD server(s) must use. (All SyslogD servers must use the same subsystem.) ProCurve recommends the default (user) subsystem unless your application specifically requires another subsystem. Options include: user (the default) - Various user-level messages...
Page 418 Syslog debug ; J9085A Configuration Editor; Created on release #R.11.XX logging. (In this case, Syslog is automatically enabled because debug hostname "ProCurve Switch 2610-24" The configured Syslog server destination logging has ip default-gateway 10.0.8.1 IP addresses appear in the not been previously logging 18.20.38.155...
Page 419 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 with out removing the servers from the switch configuration.
Page 420 < config | running > Lists the current startup-config or running-config file, with any currently configured IP addresses for SyslogD servers. ProCurve(config)# show config Startup configuration: ; J9085A Configuration Editor; Created on release #R.11.XX The configured Syslog server IP hostname “ProCurve switch”...
Page 421 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.
Page 422: Diagnostic Tools
Troubleshooting Diagnostic Tools 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.) ■ A reboot temporarily suspends Syslog logging. After a reboot, the switch suspends configured Syslog logging for 30 seconds.
Page 423: Ping And Link Tests
Troubleshooting Diagnostic Tools 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. N o t e To respond to a Ping test or a Link test, the device you are trying to reach must be IEEE 802.3-compliant.
Page 424: Web: Executing Ping Or Link Tests
Troubleshooting Diagnostic Tools Web: Executing Ping or Link Tests 1. Click here. 2. Click here. 3. Select Ping Test (the default) or Link Test 5. Select the number of tries (packets) and the timeout 4. For a Ping test, enter for each try from the drop-down menus.
Page 425: Cli: Ping Or Link Tests
Troubleshooting Diagnostic Tools Number of Packets to Send is the number of times you want the switch to attempt to test a connection. Timeout in Seconds is the number of seconds to allow per attempt to test a connection before determining that the current attempt has failed. To halt a Link or Ping test before it concludes, click on the Stop button.
Page 426 Troubleshooting Diagnostic Tools Link Tests. You can issue single or multiple link tests with varying repeti tions and timeout periods. The defaults are: ■ Repetitions: 1 (1 - 999) Timeout: 5 seconds (1 - 256 seconds) ■ Syntax: link < mac-address > [repetitions < 1 - 999 >] [timeout < 1 - 256 >] [vlan <...
Page 427: Displaying The Configuration File
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.
Page 428: Listing Switch Configuration And Operation Details For Help In Troubleshooting
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 ■...
Page 429 [Start] 4. Execute show tech ProCurve# show tech a. Each time the resulting listing halts and displays -- MORE --, press the Space bar to resume the listing. b. When the CLI prompt appears, the show tech listing is complete. At...
Page 430: Cli Administrative And Troubleshooting Commands
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. N o t e For more on the CLI, refer to “Using the Command Line Interface (CLI)” on page 4-1.
Page 431 Troubleshooting Diagnostic Tools Syntax: traceroute < ip-address > Lists the IP address of each hop in the route, plus the time in microseconds traceroute for the packet reply to the switch for each hop. To halt an ongoing traceroute search, press the [Ctrl] [C] keys. [minttl <...
Page 432 Troubleshooting Diagnostic Tools Intermediate router hops with the time taken for the switch to receive acknowledgement of each probe reaching each router. Destination IP Address Figure C-18. Example of a Completed Traceroute Enquiry Continuing from the previous example (figure C-18, above), executing traceroute with an insufficient maxttl for the actual hop count produces an output similar to this: Traceroute does not reach...
Page 433 Troubleshooting Diagnostic Tools Executing traceroute where the route becomes blocked or otherwise fails results in an output marked by timeouts for all probes beyond the last detected hop. For example with a maximum hop count of 7 (maxttl = 7), where the route becomes blocked or otherwise fails, the output appears similar to this: At hop 3, the first and third probes timed out...
Page 434: Restoring The Factory-Default Configuration
■ Clear/Reset button combination N o t e ProCurve recommends that you save your configuration to a TFTP server before resetting the switch to its factory-default configuration. You can also save your configuration via Xmodem, to a directly connected PC.
Page 435: Restoring A Flash Image
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.
Page 436 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: Change the switch baud rate to 115,200 Bps. =>...
Page 437 Troubleshooting Restoring a Flash Image Figure C-21. Example of Xmodem Download in Progress 8. 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. C-47...
Page 438 Troubleshooting Restoring a Flash Image C-48...
Page 439: Mac Address Management
MAC Address Management Contents Overview ........... . . D-2 Determining MAC Addresses in the Switch .
Page 440: Overview
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 ■...
Page 441: Menu: Viewing The Switch's Mac Addresses
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) ■...
Page 442: Cli: Viewing The Port And Vlan Mac Addresses
2. Type the following command to display the MAC address for each port on the switch: ProCurve# walkmib ifPhysAddress (The above command is not case-sensitive.) For example, with a six-port module in slot 1, a three-port module in slot 3,...
Page 443 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;...
Page 444: Viewing The Mac Addresses Of Connected Devices
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.
Page 445 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# show mac-address Status and Counters - Port Address Table MAC Address Located on Port...
Page 446 MAC Address Management Viewing the MAC Addresses of Connected Devices D-8...
Page 447: E Daylight Savings Time On Procurve Switches
• 5400zl • 8200zl ProCurve switches provide a way to automatically adjust the system clock for Daylight Savings Time (DST) changes. To use this feature you define the month and date to begin and to end the change from standard time. In addition to the value "none"...
Page 448 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: •...
Page 449 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"...
Page 450 Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time E-4...
Page 451 Index Symbols effect on configuration … 3-13 See also reboot. => prompt … C-45 boot ROM console … A-3 boot ROM mode … C-45 Numerics Bootp Bootp table file … 8-14 802.1x Bootptab file … 8-14 LLDP blocked … 13-35 effect of no reply …...
Page 452 comparing startup to running … 6-6 reboot policy, override … 6-27 console … 7-3 reboot process … 6-25 copying … A-18 reload … 6-29 download … A-3 rename config file … 6-30 factory default … 6-9, 8-2 reset … 6-28 IP …...
Page 453 Syslog logging disabled … C-27 excessive packets … 10-24 Syslog server, view configuration … C-30 Syslog, number of servers … C-25 Telnet session … C-25 factory default configuration debug logging, LLDP … 13-33 restoring … 6-9, C-44 default gateway … 8-3 failure, OS download …...
Page 454 statistics … B-19 port adds and moves … 10-18 inactivity timeout … 7-4 port speed … 10-18 Inbound Telnet Enabled parameter … C-6 security concerns … 10-23 Inconsistent value … 13-40 standard MTU … 10-18 inform requests … 13-22 through non-jumbo ports … 10-24 invalid input …...
Page 455 LLDP neighbor data, displaying … 13-47 802.1D-compliant switch … 13-53 neighbor statistics … 13-50 802.1x blocking … 13-35 neighbor, maximum … 13-53 802.1X effect … 13-53 operating rules … 13-35 active port … 13-30 optional data, configuring … 13-45 advertisement … 13-30 packet boundaries …...
Page 456 load balancing See port trunk. navigation, console interface … 3-9, 3-10 logical port … 12-7 navigation, event log … C-23 loop, network … 12-3 network management functions … 13-5 lost password … 5-10 network manager address … 13-4, 13-5 network monitoring traffic overload …...
Page 457 … 11-14 IGMP … 12-7 operation on ProCurve switches … 11-2 LACP … 10-6 planning and implementation … 11-13 LACP, full duplex required … 12-4 port priority … 11-5 link requirements … 12-3 power supplies … 11-3 logical port …...
Page 458 See also configuration. See PoE. pre-standard detect … 11-10 ProCurve Networking SCP/SFTP support URL … 5-13 session limit … A-10 prompt, => … C-45 secure copy public SNMP community … 13-5 See SCP/SFTP. publication data … 1-ii secure FTP See SCP/SFTP.
Page 459 snmp-server using with port trunking … 12-7 inform … 13-22 viewing port operating statistics … 10-10 SNMPv3 SSH "public" community access caution … 13-6 debug logging … C-25 access … 13-5 TACACS exclusion … A-10 assigning users to groups … 13-8 troubleshooting …...
Page 460 … 13-20, 13-21 browser interface online help location … 5-13 troubleshooting management … 5-13 approaches … C-3 management server … 5-12, 5-13 browsing the configuration file … C-37 ProCurve Networking … 5-13 console access problems … C-5 10 – Index...
Page 461 support … 5-12, 5-13 web browser interface user name, using for browser or console access parameters … 5-8 access … 5-8, 5-10 alert log … 5-6, 5-18 users, SNMPv3 alert log details … 5-19 See SNMPv3. bandwidth adjustment … 5-16 using the passwords …...
Page 462 12 – Index...

This manual is also suitable for:

2610-pwr series 2610-24 2610-48 2610-24-pwr 2610-48-pwr 2610-24/12-pwr

ProCurve 2610 Series Management And Configuration Manual

1 Getting Started

4 Using the Command Line Interface (CLI)

5 Using the Web Browser Interface

6 Switch Memory and Configuration

7 Interface Access and System Information

8 Configuring IP Addressing

9 Time Protocols

10 Port Status and Basic Configuration

11 Power over Ethernet (Poe) Operation

12 Port Trunking

13 Configuring for Network Management Applications

Quick Links

Troubleshooting

Related Manuals for ProCurve 2610 Series

Summary of Contents for ProCurve 2610 Series