HP | PROCURVE 6120 | User's Manual | HP PROCURVE 6120 User's Manual

ProCurve Series 6120 Switches
Management and Configuration Guide
August 2009
© Copyright 2009 Hewlett-Packard Development Company,
L.P. The information contained herein is subject to change without notice. All Rights Reserved.
Warranty
This document contains proprietary information, which is
protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another
language without the prior written consent of HewlettPackard.
A copy of the specific warranty terms applicable to your
Hewlett-Packard products and replacement parts can be
obtained from your HP Sales and Service Office or
authorized dealer.
See the Customer Support/Warranty information at
http://www.hp.com/#Support.
HP Contact Information
Publication Number
For the name of the nearest HP authorized reseller:
5992-5523
August 2009
• See the Contact HP worldwide (in English) webpage
(http://welcome.hp.com/country/us/en/wwcontact.html).
For HP technical support:
Applicable Products
HP ProCurve Switch 6120G/XG
HP ProCurve Switch 6120XG
(498358-B21)
(516733-B21)
Trademark Credits
Microsoft, Windows, and Microsoft Windows NT are US
registered trademarks of Microsoft Corporation. Java™ is a
US trademark of Sun Microsystems, Inc.
• In the United States, for contact options see the Contact
HP United States webpage
(http://welcome.hp.com/country/us/en/contact_us.html).
To contact HP by phone:
• Call 1-800-HP-INVENT (1-800-474-6836). This service is
available 24 hours a day, 7 days a week. For continuous
quality improvement, calls may be recorded or monitored.
• If you have purchased a Care Pack (service upgrade),
call 1-800-633-3600. For more information about Care
Packs, refer to the HP website (http://www.hp.com/hps).
Disclaimer
The information contained in this document is subject to
change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY
OF ANY KIND WITH REGARD TO THIS MATERIAL,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing,
performance, or use of this material.
The only warranties for HP products and services are set
forth in the express warranty statements accompanying
such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions
contained herein.
Hewlett-Packard assumes no responsibility for the use or
reliability of its software on equipment that is not furnished
by Hewlett-Packard.
Hewlett-Packard Company
8000 Foothills Boulevard, m/s 5551
Roseville, California 95747-5551
http://www.procurve.com
• In other locations, see the Contact HP worldwide (in
English) webpage
(http://welcome.hp.com/country/us/en/wwcontact.html).
ii
Contents
Product Documentation
About Your Switch Manual Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Printed Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Electronic Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Software Feature Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
1 Getting Started
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Screen Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Configuration and Operation Examples . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Sources for More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Getting Documentation From the Web . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Need Only a Quick Start? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
To Set Up and Install the Switch in Your Network . . . . . . . . . . . . . . . 1-8
Physical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
2 Selecting a Management Interface
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
iii
Understanding Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Understanding Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Advantages of Using the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Advantages of Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
General Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Information on Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Advantages of Using the Web Browser Interface . . . . . . . . . . . . . . . . 2-6
Advantages of Using ProCurve Manager
or ProCurve Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Custom Login Banners for the Console and
Web Browser Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Banner Operation with Telnet, Serial, or SSHv2 Access . . . . . . . . 2-9
Banner Operation with Web Browser Access . . . . . . . . . . . . . . . . 2-9
Configuring and Displaying a Non-Default Banner . . . . . . . . . . . 2-10
Example of Configuring and Displaying a Banner . . . . . . . . . . . . 2-11
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
3 Using the Menu Interface
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Starting and Ending a Menu Session . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
How To Start a Menu Interface Session . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
How To End a Menu Session and Exit from the Console: . . . . . . . . . . 3-5
Main Menu Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Screen Structure and Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Menu Features List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Where To Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
4 Using the Command Line Interface (CLI)
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
iv
Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Privilege Levels at Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Privilege Level Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Operator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
How To Move Between Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Listing Commands and Command Options . . . . . . . . . . . . . . . . . . . . . . 4-8
Listing Commands Available at Any Privilege Level . . . . . . . . . . . 4-8
Listing Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Displaying CLI “Help” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Configuration Commands and the Context Configuration Modes . . 4-13
CLI Control and Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Executing a Prior Command—Redo . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Repeating Execution of a Command . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Using a Command Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
CLI Shortcut Keystrokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
5 Using the ProCurve Web Browser Interface
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Starting a Web Browser
Interface Session with the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Using a Standalone Web Browser in a PC or UNIX Workstation . . . . 5-4
Using ProCurve Manager (PCM) or
ProCurve Manager Plus (PCM+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Tasks for Your First ProCurve Web Browser Interface Session . . 5-7
Viewing the “First Time Install” Window . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Security: Creating Usernames and Passwords
in the Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Entering a User Name and Password . . . . . . . . . . . . . . . . . . . . . . 5-10
Using a User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
If You Lose the Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
v
Online Help for the Web Browser Interface . . . . . . . . . . . . . . . . . . . . 5-11
Support/Mgmt URLs Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Support URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Help and the Management Server URL . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Using the PCM Server for Switch Web Help . . . . . . . . . . . . . . . . . . . . 5-14
Status Reporting Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
The Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
The Port Utilization and Status Displays . . . . . . . . . . . . . . . . . . . . . . . 5-17
Port Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
The Alert Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Sorting the Alert Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Alert Types and Detailed Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
The Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Setting Fault Detection Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
6 Switch Memory and Configuration
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Using the CLI To Implement Configuration Changes . . . . . . . . . . . . 6-6
Using the Menu and Web Browser Interfaces To Implement
Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Menu: Implementing Configuration Changes . . . . . . . . . . . . . . . . . . . 6-10
Using Save and Cancel in the Menu Interface . . . . . . . . . . . . . . . 6-10
Rebooting from the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . 6-11
Web: Implementing Configuration Changes . . . . . . . . . . . . . . . . . . . . 6-13
Using Primary and Secondary Flash Image Options . . . . . . . . . . . . . 6-14
Displaying the Current Flash Image Data . . . . . . . . . . . . . . . . . . . . . . 6-14
Switch Software Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Local Switch Software Replacement and Removal . . . . . . . . . . . . . . 6-17
Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Operating Notes about Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Boot and Reload Command Comparison . . . . . . . . . . . . . . . . . . . 6-20
vi
Setting the Default Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Booting from the Default Flash (Primary or Secondary) . . . . . . 6-22
Booting from a Specified Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Using Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Multiple Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Transitioning to Multiple Configuration Files . . . . . . . . . . . . . . . . . . . 6-27
Listing and Displaying Startup-Config Files . . . . . . . . . . . . . . . . . . . . . 6-29
Viewing the Startup-Config File Status with Multiple
Configuration Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Displaying the Content of A Specific Startup-Config File . . . . . . 6-30
Changing or Overriding the Reboot Configuration Policy . . . . . . . . . 6-30
Managing Startup-Config Files in the Switch . . . . . . . . . . . . . . . . . . . 6-32
Renaming an Existing Startup-Config File . . . . . . . . . . . . . . . . . . 6-33
Creating a New Startup-Config File . . . . . . . . . . . . . . . . . . . . . . . . 6-33
Erasing a Startup-Config File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Using the Clear + Reset Button Combination To Reset the
Switch to Its Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . 6-37
Transferring Startup-Config Files To or From a Remote Server . . . . 6-37
TFTP: Copying a Configuration File to a Remote Host . . . . . . . . 6-38
TFTP: Copying a Configuration File from a Remote Host . . . . . 6-39
Xmodem: Copying a Configuration File to a Serially
Connected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
Xmodem: Copying a Configuration from a Serially
Connected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
Operating Notes for Multiple Configuration Files . . . . . . . . . . . . 6-41
Automatic Configuration Update with DHCP Option 66 . . . . . . . . 6-41
CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Possible Scenarios for Updating the Configuration File . . . . . . . . . . 6-42
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
7 Interface Access and System Information
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
vii
Interface Access: Console/Serial Link, Web, and Inbound Telnet . 7-3
Menu: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
CLI: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Denying Interface Access by Terminating Remote Management
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Menu: Viewing and Configuring System Information . . . . . . . . . . . . . 7-13
CLI: Viewing and Configuring System Information . . . . . . . . . . . . . . 7-14
Web: Configuring System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
8 Configuring IP Addressing
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Just Want a Quick Start with IP Addressing? . . . . . . . . . . . . . . . . . . . . 8-3
IP Addressing with Multiple VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Menu: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . 8-5
CLI: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . . . 8-6
Web: Configuring IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
How IP Addressing Affects Switch Operation . . . . . . . . . . . . . . . . . . . 8-11
DHCP/Bootp Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Network Preparations for Configuring DHCP/Bootp . . . . . . . . . 8-14
IP Preserve: Retaining VLAN-1 IP
Addressing Across Configuration File Downloads . . . . . . . . . . . . . . 8-16
Operating Rules for IP Preserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Enabling IP Preserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
9 Time Protocols
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
TimeP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
SNTP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Selecting a Time Synchronization Protocol or Turning Off Time
Protocol Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
viii
General Steps for Running a Time Protocol on the Switch: . . . . . . . . 9-3
Disabling Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
SNTP: Viewing, Selecting, and Configuring . . . . . . . . . . . . . . . . . . . . . 9-4
Menu: Viewing and Configuring SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
CLI: Viewing and Configuring SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Viewing the Current SNTP Configuration . . . . . . . . . . . . . . . . . . . . 9-8
Configuring (Enabling or Disabling) the SNTP Mode . . . . . . . . . 9-10
TimeP: Viewing, Selecting, and Configuring . . . . . . . . . . . . . . . . . . . . 9-16
Menu: Viewing and Configuring TimeP . . . . . . . . . . . . . . . . . . . . . . . . 9-17
CLI: Viewing and Configuring TimeP . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Viewing the Current TimeP Configuration . . . . . . . . . . . . . . . . . . 9-19
Configuring (Enabling or Disabling) the TimeP Mode . . . . . . . . 9-20
SNTP Unicast Time Polling with Multiple SNTP Servers . . . . . . . . 9-25
Displaying All SNTP Server Addresses Configured on the Switch . . 9-25
Adding and Deleting SNTP Server Addresses . . . . . . . . . . . . . . . . . . . 9-26
Menu: Operation with Multiple SNTP Server Addresses
Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
SNTP Messages in the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
10 Port Status and Configuration
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Viewing Port Status and Configuring Port Parameters . . . . . . . . . . 10-3
Menu: Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
CLI: Viewing Port Status and Configuring Port Parameters . . . . . . . 10-8
Viewing Port Status and Configuration . . . . . . . . . . . . . . . . . . . . . 10-8
Customizing the Show Interfaces Command . . . . . . . . . . . . . . . . . . . 10-10
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Note on Using Pattern Matching with the “Show Interfaces Custom”
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Viewing Port Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Viewing Transceiver Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Enabling or Disabling Ports and Configuring Port Mode . . . . . . . . . 10-15
Enabling or Disabling Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
ix
Configuring a Broadcast Limit on the Switch . . . . . . . . . . . . . . . . . . 10-18
Configuring ProCurve Auto-MDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Web: Viewing Port Status and Configuring Port Parameters . . . . . 10-22
Using Friendly (Optional) Port Names . . . . . . . . . . . . . . . . . . . . . . . 10-23
Configuring and Operating Rules for Friendly Port Names . . . . . . . 10-23
Configuring Friendly Port Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Displaying Friendly Port Names with Other Port Data . . . . . . . . . . 10-25
Configuring Transceivers and Modules That Haven’t
Been Inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Clearing the Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Uni-Directional Link Detection (UDLD) . . . . . . . . . . . . . . . . . . . . . . 10-31
Configuring UDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Enabling UDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Changing the Keepalive Interval . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Changing the Keepalive Retries . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Configuring UDLD for Tagged Ports . . . . . . . . . . . . . . . . . . . . . . 10-34
Viewing UDLD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Configuration Warnings and Event Log Messages . . . . . . . . . . . . . . 10-37
11 Port Trunking
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Port Trunk Features and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Trunk Configuration Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Menu: Viewing and Configuring a Static Trunk Group . . . . . . . . . . 11-9
CLI: Viewing and Configuring Port Trunk Groups . . . . . . . . . . . . . 11-11
Using the CLI To View Port Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Using the CLI To Configure a Static or Dynamic Trunk Group . . . 11-14
Web: Viewing Existing Port Trunk Groups . . . . . . . . . . . . . . . . . . . . 11-17
Trunk Group Operation Using LACP . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
x
Default Port Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
LACP Notes and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
Trunk Group Operation Using the “Trunk” Option . . . . . . . . . . . . 11-26
How the Switch Lists Trunk Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Outbound Traffic Distribution Across Trunked Links . . . . . . . . . 11-27
12 Port Traffic Controls
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Jumbo Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Operating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Configuring Jumbo Frame Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Viewing the Current Jumbo Configuration . . . . . . . . . . . . . . . . . . 12-5
Enabling or Disabling Jumbo Traffic on a VLAN . . . . . . . . . . . . . 12-7
Configuring a Maximum Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
SNMP Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Displaying the Maximum Frame Size . . . . . . . . . . . . . . . . . . . . . . 12-8
Operating Notes for Maximum Frame Size . . . . . . . . . . . . . . . . . 12-8
Operating Notes for Jumbo Traffic-Handling . . . . . . . . . . . . . . . . . . . 12-9
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
13 Configuring for Network Management Applications
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Using SNMP Tools To Manage the Switch . . . . . . . . . . . . . . . . . . . . . . 13-3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
SNMP Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Configuring for SNMP version 1 and 2c Access to the Switch . . . . . 13-5
Configuring for SNMP Version 3 Access to the Switch . . . . . . . . . . . 13-6
SNMP Version 3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Enabling SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
xi
Group Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
SNMPv3 Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Menu: Viewing and Configuring non-SNMP version 3
Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
CLI: Viewing and Configuring SNMP Community Names . . . . 13-16
SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Supported Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
General Steps for Configuring SNMP Notifications . . . . . . . . . 13-19
SNMPv1 and SNMPv2c Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Configuring an SNMP Trap Receiver . . . . . . . . . . . . . . . . . . . . . . 13-20
Enabling SNMPv2c Informs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Configuring SNMPv3 Notifications . . . . . . . . . . . . . . . . . . . . . . . 13-24
Managing Network Security Notifications . . . . . . . . . . . . . . . . . 13-27
Enabling Link-Change Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Configuring the Source IP Address for SNMP Notifications . . 13-30
Displaying SNMP Notification Configuration . . . . . . . . . . . . . . . 13-32
Configuring Listening Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34
Advanced Management: RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
LLDP (Link-Layer Discovery Protocol) . . . . . . . . . . . . . . . . . . . . . . . 13-36
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
General LLDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
Packet Boundaries in a Network Topology . . . . . . . . . . . . . . . . . . . . 13-39
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Options for Reading LLDP Information Collected by the Switch . . 13-42
LLDP and LLDP-MED Standards Compatibility . . . . . . . . . . . . . . . . 13-42
LLDP Operating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43
Configuring LLDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Viewing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . 13-44
Configuring Global LLDP Packet Controls . . . . . . . . . . . . . . . . . 13-46
Configuring SNMP Notification Support . . . . . . . . . . . . . . . . . . . 13-50
Configuring Per-Port Transmit and Receive Modes . . . . . . . . . 13-51
Configuring Basic LLDP Per-Port Advertisement Content . . . . 13-52
Configuring Support for Port Speed and Duplex
Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
LLDP-MED (Media-Endpoint-Discovery) . . . . . . . . . . . . . . . . . . . . . 13-55
xii
LLDP-MED Topology Change Notification . . . . . . . . . . . . . . . . . 13-58
LLDP-MED Fast Start Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Advertising Device Capability, Network Policy, PoE Status
and Location Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Configuring Location Data for LLDP-MED Devices . . . . . . . . . 13-63
Displaying Advertisement Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
Displaying Switch Information Available for Outbound
Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
Displaying LLDP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
LLDP Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
LLDP and CDP Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
LLDP and CDP Neighbor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
CDP Operation and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 13-79
A File Transfers
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Downloading Switch Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
General Software Download Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Using TFTP To Download Software from a Server . . . . . . . . . . . . . . A-4
Menu: TFTP Download from a Server to Primary Flash . . . . . . . A-5
CLI: TFTP Download from a Server to Flash . . . . . . . . . . . . . . . . A-7
Enabling TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Using Auto-TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Using Secure Copy and SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
The SCP/SFTP Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Disable TFTP and Auto-TFTP for Enhanced Security . . . . . . . A-14
Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
SCP/SFTP Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Troubleshooting SSH, SFTP, and SCP Operations . . . . . . . . . . A-18
Using Xmodem to Download Switch Software From a PC or UNIX
Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19
Menu: Xmodem Download to Primary Flash . . . . . . . . . . . . . . . A-20
xiii
CLI: Xmodem Download from a PC or UNIX Workstation to
Primary or Secondary Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Switch-to-Switch Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Menu: Switch-to-Switch Download to Primary Flash . . . . . . . . A-22
CLI: Switch-To-Switch Downloads . . . . . . . . . . . . . . . . . . . . . . . A-23
Using PCM+ to Update Switch Software . . . . . . . . . . . . . . . . . . . . . . A-24
Copying Software Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25
TFTP: Copying a Software Image to a Remote Host . . . . . . . . . A-25
Xmodem: Copying a Software Image from the Switch to a
USB Serial Console Connected PC or UNIX Workstation . . . . A-25
Transferring Switch Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . A-26
TFTP: Copying a Configuration File to a Remote Host . . . . . . . A-26
TFTP: Copying a Configuration File from a Remote Host . . . . A-27
TFTP: Copying a Customized Command File to a Switch . . . . A-27
Xmodem: Copying a Configuration File to a USB Serial Console
Connected PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . . . . A-28
Xmodem: Copying a Configuration File from a Serially
Connected PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . . . . A-29
Copying Diagnostic Data to a Remote
Host, USB Device, PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . A-30
Copying Command Output to a Destination Device . . . . . . . . . A-31
Copying Event Log Output to a Destination Device . . . . . . . . . A-31
Copying Crash Data Content to a Destination Device . . . . . . . A-32
Copying Crash Log Data Content to a Destination Device . . . . A-33
B Monitoring and Analyzing Switch Operation
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Status and Counters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Menu Access To Status and Counters . . . . . . . . . . . . . . . . . . . . . . . . . B-5
General System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
CLI Access to System Information . . . . . . . . . . . . . . . . . . . . . . . . B-7
Task Monitor—Collecting Processor Data . . . . . . . . . . . . . . . . . . . . . B-8
Switch Management Address Information . . . . . . . . . . . . . . . . . . . . . . B-8
xiv
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
CLI Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Menu: Displaying Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
CLI Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Viewing Port and Trunk Group Statistics and Flow Control Status B-11
Menu Access to Port and Trunk Statistics . . . . . . . . . . . . . . . . . B-12
CLI Access To Port and Trunk Group Statistics . . . . . . . . . . . . B-13
Web Browser Access To View Port and Trunk Group Statistics B-13
Viewing the Switch’s MAC Address Tables . . . . . . . . . . . . . . . . . . . . B-14
Menu Access to the MAC Address Views and Searches . . . . . . B-14
CLI Access for MAC Address Views and Searches . . . . . . . . . . B-17
Spanning Tree Protocol (MSTP) Information . . . . . . . . . . . . . . . . . . B-18
CLI Access to MSTP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Internet Group Management Protocol (IGMP) Status . . . . . . . . . . . B-19
VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20
Web Browser Interface Status Information . . . . . . . . . . . . . . . . . . . . B-22
Traffic Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
Mirroring Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24
Mirrored Traffic Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Local Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Monitored Traffic Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Criteria for Selecting Mirrored Traffic . . . . . . . . . . . . . . . . . . . . . . . . B-26
Mirroring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Endpoint Switches and Intermediate Devices . . . . . . . . . . . . . . B-28
Using the Menu or Web Interface To Configure Local Mirroring . . B-29
Menu and Web Interface Limits . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30
CLI: Configuring Local Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33
Local Mirroring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33
1. Determine the Mirroring Session and Destination . . . . . . . . . . . . B-35
2. Configure a Mirroring Session on the Source Switch . . . . . . . . . . B-35
3. Configure the Monitored Traffic in a Mirror Session . . . . . . . . . . B-35
xv
Traffic Selection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Mirroring-Source Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Selecting All Inbound/Outbound Traffic to Mirror . . . . . . . . . . . . . . B-36
Displaying a Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Displaying the Mirroring Configuration Summary . . . . . . . . . . B-38
Viewing Mirroring in the Current Configuration File . . . . . . . . B-40
Mirroring Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . B-41
Local Mirroring Using Traffic-Direction Criteria . . . . . . . . . . . . B-41
Maximum Supported Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42
Enabling Jumbo Frames To Increase Mirroring Path MTU . . . B-43
Effect of Downstream VLAN Tagging on
Untagged, Mirrored Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45
Troubleshooting Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47
C Troubleshooting
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Troubleshooting Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Browser or Telnet Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Unusual Network Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
802.1Q Prioritization Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
IGMP-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
LACP-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Port-Based Access Control (802.1X)-Related Problems . . . . . . . . . C-11
QoS-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Radius-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Spanning-Tree Protocol (MSTP) and Fast-Uplink Problems . . . . . . C-16
SSH-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
TACACS-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
TimeP, SNTP, or Gateway Problems . . . . . . . . . . . . . . . . . . . . . . . . . C-21
VLAN-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Using the Event Log for Troubleshooting Switch Problems . . . . C-24
xvi
Event Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Menu: Displaying and Navigating in the Event Log . . . . . . . . . . . . . C-31
CLI: Displaying the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32
CLI: Clearing Event Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32
CLI: Turning Event Numbering On . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33
Using Log Throttling to Reduce Duplicate
Event Log and SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33
Log Throttle Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
Example of Log Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
Example of Event Counter Operation . . . . . . . . . . . . . . . . . . . . . C-36
Debug/Syslog Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Destination Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Configuration Commands . . . . . . . . . . . . . . . . . . . . . . C-38
Configuring Debug/Syslog Operation . . . . . . . . . . . . . . . . . . . . . . . . . C-39
Displaying a Debug/Syslog Configuration . . . . . . . . . . . . . . . . . . C-41
Debug Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-45
Debug Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-45
Debug Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-47
Logging Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-48
Configuring a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-49
Adding a Description for a Syslog Server . . . . . . . . . . . . . . . . . . . . . . C-51
Adding a Priority Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-52
Configuring the Severity Level for Event Log Messages
Sent to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-53
Configuring the System Module Used to Select the Event Log
Messages Sent to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . C-54
Operating Notes for Debug and Syslog . . . . . . . . . . . . . . . . . . . . . . . C-54
Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-56
Port Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-57
Ping and Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-57
Web: Executing Ping or Link Tests . . . . . . . . . . . . . . . . . . . . . . . C-58
CLI: Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-59
Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-60
Traceroute Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-61
xvii
Viewing Switch Configuration and Operation . . . . . . . . . . . . . . . . . C-65
CLI: Viewing the Startup or Running Configuration File . . . . . . . . . C-65
Web: Viewing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . C-65
CLI: Viewing a Summary of Switch Operational Data . . . . . . . . . . . C-65
Saving show tech Command Output to a Text File . . . . . . . . . . C-67
Customizing show tech Command Output . . . . . . . . . . . . . . . . . C-68
CLI: Viewing More Information on Switch Operation . . . . . . . . . . . C-71
Pattern Matching When Using the Show Command . . . . . . . . . C-72
CLI: Useful Commands for Troubleshooting Sessions . . . . . . . . . . . C-75
Restoring the Factory-Default Configuration . . . . . . . . . . . . . . . . . C-76
CLI: Resetting to the Factory-Default Configuration . . . . . . . . . . . . C-76
Clear/Reset: Resetting to the Factory-Default Configuration . . . . . C-76
Restoring a Flash Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-77
DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-79
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-79
Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-80
Configuring and Using DNS Resolution with
DNS-Compatible Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-81
Configuring a DNS Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-82
Example Using DNS Names with Ping and Traceroute . . . . . . . . . . C-83
Viewing the Current DNS Configuration . . . . . . . . . . . . . . . . . . . . . . C-85
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-86
Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-87
D MAC Address Management
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Determining MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Menu: Viewing the Switch’s MAC Addresses . . . . . . . . . . . . . . . . . . . . D-4
CLI: Viewing the Port and VLAN MAC Addresses . . . . . . . . . . . . . . . . D-5
Viewing the MAC Addresses of Connected Devices . . . . . . . . . . . . . D-7
E Monitoring Resources
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
xviii
Viewing Information on Resource Usage . . . . . . . . . . . . . . . . . . . . . . . E-2
Policy Enforcement Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
When Insufficient Resources Are Available . . . . . . . . . . . . . . . . . . . . E-3
F Daylight Savings Time on ProCurve Switches
G Network Out-of-Band Management (OOBM)
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5
OOBM and Switch Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-8
OOBM port enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-9
OOBM IPv4 address configuration . . . . . . . . . . . . . . . . . . . . . . . G-10
OOBM IPv4 default gateway configuration . . . . . . . . . . . . . . . . G-10
OOBM Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-11
Show OOBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-11
Show OOBM IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . G-12
Show OOBM ARP information . . . . . . . . . . . . . . . . . . . . . . . . . . . G-12
Application Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-13
Application Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-15
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-16
xix
xx
Product Documentation
About Your Switch Manual Set
Note
For the latest version of switch documentation, please visit any of the following websites:
www.procurve.com/manuals
www.hp.com/go/bladesystem/documentation
h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
Printed Publications
The publication listed below is printed and shipped with your switch. The
latest version is also available in PDF format, as described in the Note at the
top of this page.
■
Quick Installation Card—Explains how to prepare for and perform the
physical installation and connect the switch to your network.
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.
■
Installation and Getting Started Guide—Describes how to install hardware, and get started using the switch.
■
Management and Configuration Guide—Describes how to configure,
manage, and monitor basic switch operation.
■
Advanced Traffic Management Guide—Explains how to configure traffic
management features such as VLANs, MSTP, and QoS.
■
Multicast and Routing Guide—Explains how to configure IGMP features.
■
Access Security Guide—Explains how to configure access security features and user authentication on the switch.
■
IPv6 Configuration Guide—Describes the IPv6 protocol operations that
are supported on the switch.
■
Release Notes—Describe new features, fixes, and enhancements that
become available between revisions of the main product guide.
xxi
Software Feature Index
This feature index indicates which manual to consult for information on a
given software feature.
Note
This Index does not cover IPv6 capable software features. For information on
IPv6 protocol operations and features (such as DHCPv6, DNS for IPv6, and
Ping6), refer to the IPv6 Configuration Guide.
Intelligent Edge Software Features. These features are automatically
included on all switches.
Intelligent Edge Software
Features
Manual
Management
Advanced
and
Traffic
Configuration Management
802.1Q VLAN Tagging
Multicast and
Routing
Access
Security
Guide
X
802.1X Multiple Authenticated Clients Per Port
X
AAA Authentication
X
Authorized IP Managers
X
Authorized Manager List (Web, Telnet, TFTP)
X
Auto MDIX Configuration
X
BOOTP
X
Config File
X
Console Access
X
Copy Command
X
CoS (Class of Service)
X
Debug
X
DHCP Configuration
X
DHCP/Bootp Operation
X
Diagnostic Tools
X
xxii
Intelligent Edge Software
Features
Manual
Management
Advanced
and
Traffic
Configuration Management
Downloading Software
X
Event Log
X
Factory Default Settings
X
Flow Control (802.3x)
X
File Transfers
X
Friendly Port Names
X
GVRP
X
Identity-Driven Management (IDM)
X
IGMP
Access
Security
Guide
X
Interface Access (Telnet, Console/Serial, Web)
X
IP Addressing
X
Jumbo Packets
X
LACP
X
LLDP
X
LLDP-MED
X
Loop Protection
MAC Address Management
Multicast and
Routing
X
X
MAC Lockdown
X
MAC Lockout
X
MAC-based Authentication
X
Monitoring and Analysis
X
Network Management Applications (SNMP)
X
Passwords and Password Clear Protection
X
ProCurve Manager (PCM)
X
Ping
X
Port Configuration
X
xxiii
Intelligent Edge Software
Features
Manual
Management
Advanced
and
Traffic
Configuration Management
Port Monitoring
Multicast and
Routing
Access
Security
Guide
X
Port Security
X
Port Status
X
Port Trunking (LACP)
X
Port-Based Access Control (802.1X)
X
Protocol VLANS
X
Quality of Service (QoS)
X
RADIUS Authentication and Accounting
X
RADIUS-Based Configuration
X
RMON 1,2,3,9
X
Secure Copy
X
SFTP
X
SNMPv3
X
Software Downloads (SCP/SFTP, TFPT, Xmodem)
X
Source-Port Filters
X
Spanning Tree (STP, RSTP, MSTP)
X
SSHv2 (Secure Shell) Encryption
X
SSL (Secure Socket Layer)
X
Syslog
X
System Information
X
TACACS+ Authentication
X
Telnet Access
X
TFTP
X
Time Protocols (TimeP, SNTP)
X
Troubleshooting
X
Uni-Directional Link Detection (UDLD)
X
xxiv
Intelligent Edge Software
Features
Manual
Management
Advanced
and
Traffic
Configuration Management
VLANs
Multicast and
Routing
Access
Security
Guide
X
Web Authentication RADIUS Support
X
Web-based Authentication
X
Web UI
X
xxv
1
Getting Started
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Screen Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Configuration and Operation Examples . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Sources for More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Getting Documentation From the Web . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Need Only a Quick Start? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
To Set Up and Install the Switch in Your Network . . . . . . . . . . . . . . . 1-8
Physical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1-1
Getting Started
Introduction
Introduction
This guide is intended for use with the HP ProCurve 6120G/XG and 6120GX
switches.
It describes how to use the command line interface (CLI), Menu interface, and
web browser to configure, manage, monitor, and troubleshoot switch operation. For an overview of product documentation for the above switches, refer
to “Product Documentation” on page xiii. You can download documentation
from the following web sites:
www.procurve.com/manuals
www.hp.com/go/bladesystem/documentation
h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
Conventions
This guide uses the following conventions for commands and screen displays.
Command Syntax Statements
Syntax: ip < default-gateway < ip-addr >> | routing >

Syntax: show interfaces [port-list ]
■
Vertical bars ( | ) separate alternative, mutually exclusive elements.
■
Square brackets ( [ ] ) indicate optional elements.
■
Braces ( < > ) enclose required elements.
■
Braces within square brackets ( [ < > ] ) indicate a required element within
an optional choice.
■
Boldface indicates use of a CLI command, part of a CLI command syntax,
or other displayed element in general text. For example:
“Use the copy tftp command to download the key from a TFTP server.”
■
Italics indicate variables for which you must supply a value when executing the command. For example, in this command syntax, you must provide
one or more port numbers:
Syntax: aaa port-access authenticator < port-list >
1-2
Getting Started
Conventions
Command Prompts
In the default configuration, your switch displays a CLI prompt similar to the
following examples:
ProCurve 6120G/XG Blade Switch#
ProCurve 6120XG Blade Switch#
To simplify recognition, this guide uses ProCurve to represent command
prompts. For example:
ProCurve#
(You can use the hostname command to change the text in the CLI prompt.)
Screen Simulations
Displayed Text. Figures containing simulated screen text and command
output look like this:
ProCurve> show version
Image stamp:
/sw/code/build/vern
Feb 20 2009 14:56:49
Z.14.XX
427
Boot Image:
Primary
Build Options:
QA
Watchdog:
ENABLED
Figure 1-1. Example of a Figure Showing a Simulated Screen
In some cases, brief command-output sequences appear without figure identification. For example:
ProCurve(config)# clear public-key
ProCurve(config)# show ip client-public-key
show_client_public_key: cannot stat keyfile
Configuration and Operation Examples
Keys
Simulations of actual keys use a bold, sans-serif typeface with square brackets.
For example, the Tab key appears as [Tab] and the “Y” key appears as [Y].
1-3
Getting Started
Sources for More Information
Sources for More Information
For information about switch operation and features not covered in this guide,
consult the following sources:
■
Note
Feature Index—For information on which manual to consult for a given
software feature, refer to the “Software Feature Index” on page xiv.
For the latest version of all HP ProCurve switch documentation referred to
below, including Release Notes covering recently added features, visit any of
the following web sites:
www.procurve.com/manuals
www.hp.com/go/bladesystem/documentation
h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
■
Software Release Notes—Release Notes provide information on new
software updates:
•
•
software management, including downloading software to the switch
•
software fixes addressed in current and previous releases
■
Product Notes and Software Update Information—The printed Quick
Installation Card shipped with your switch provides basic installation
and getting started information.
■
Installation and Getting Started Guide—Use the Installation and Getting Started Guide to prepare for and perform the physical installation.
This guide also steps you through connecting the switch to your network
and assigning IP addressing, as well as describing the LED indications for
correct operation and trouble analysis.
■
Management and Configuration Guide—Use this guide for information
on topics such as:
•
•
•
•
•
•
•
1-4
new features and how to configure and use them
various interfaces available on the switch
memory and configuration operation
interface access
IP addressing
time protocols
port configuration, trunking, and traffic control
SNMP, LLDP, and other network management topics
Getting Started
Sources for More Information
•
■
■
Advanced Traffic Management Guide—Use this guide for information on
topics such as:
•
VLANs: Static port-based and protocol VLANs, and dynamic GVRP
VLANs
•
spanning-Tree: 802.1D (STP), 802.1w (RSTP), and 802.1s (MSTP)
•
Quality-of-Service (QoS)
Multicast and Routing Guide—Use this guide for information on topics
such as:
•
■
■
file transfers, switch monitoring, troubleshooting, and MAC address
management
IGMP
Access Security Guide—Use this guide for information on topics such as:
•
Local username and password security
•
Web-Based and MAC-based authentication
•
RADIUS and TACACS+ authentication
•
SSH (Secure Shell) and SSL (Secure Socket Layer) operation
•
802.1X access control
•
Port security operation with MAC-based control
•
Authorized IP Manager security
IPv6 Configuration Guide—Use this guide for information on topics
such as:
•
Overview of IPv6 operation and features supported
•
Configuring IPv6 addressing
•
Using IPv6 management, security, and troubleshooting features
1-5
Getting Started
Sources for More Information
Getting Documentation From the Web
To obtain the latest versions of documentation and release notes for your
switch, go to any of the following web sites:
www.procurve.com/manuals
www.hp.com/go/bladesystem/documentation
h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
Online Help
Menu Interface
If you need information on specific parameters in the menu interface, refer to
the online help provided in the interface. For example:
Online Help
for Menu
Figure 1-2. Online Help for Menu Interface
1-6
Getting Started
Sources for More Information
Command Line Interface
If you need information on a specific command in the CLI, type the command
name followed by help. For example:
Figure 1-3. Example of CLI Help
Web Browser Interface
If you need information on specific features in the HP ProCurve Web Browser
Interface (hereafter referred to as the “web browser interface”), use the online
Help. You can access the Help by clicking on the question mark button in the
upper right corner of any of the web browser interface screens.
The Help Button
Figure 1-4. Button for Web Browser Interface Online Help
Note
To access the online Help for the Web browser interface, you need either
ProCurve Manager (version 1.5 or greater) installed on your network or an
active connection to the World Wide Web. Otherwise, Online help for the web
browser interface will not be available.
Online help is also accessible by logging into the Onboard Administrator.
1-7
Getting Started
Need Only a Quick Start?
The Help Button
Figure 1-5. Button for Onboard Administrator Interface Online Help
Need Only a Quick Start?
IP Addressing
If you just want to give the switch an IP address so that it can communicate
on your network, or if you are not using VLANs, 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.
Procurve# setup
■
In the Main Menu of the Menu interface, select
8. Run Setup
For more on using the Switch Setup screen, see the Installation and Getting
Started Guide you received with the switch.
To Set Up and Install the Switch in Your
Network
Physical Installation
Use the Installation and Getting Started Guide for the following:
■
1-8
Notes, cautions, and warnings related to installing and using the switch
and its related modules
Getting Started
To Set Up and Install the Switch in Your Network
■
Instructions for physically installing the switch in your network
■
Quickly assigning an IP address and subnet mask, set a Manager password, and (optionally) configure other basic features.
■
Interpreting LED behavior.
For the latest version of the Installation and Getting Started Guide for your
switch, refer to “Getting Documentation From the Web” on page 1-6.
1-9
Selecting a Management Interface
Contents
2
Selecting a Management Interface
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Understanding Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Understanding Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Advantages of Using the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Advantages of Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
General Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Information on Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Advantages of Using the Web Browser Interface . . . . . . . . . . . . . . . . 2-6
Advantages of Using ProCurve Manager
or ProCurve Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Custom Login Banners for the Console and
Web Browser Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Banner Operation with Telnet, Serial, or SSHv2 Access . . . . . . . . 2-9
Banner Operation with Web Browser Access . . . . . . . . . . . . . . . . 2-9
Configuring and Displaying a Non-Default Banner . . . . . . . . . . . 2-10
Example of Configuring and Displaying a Banner . . . . . . . . . . . . 2-11
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2-1
Selecting a Management Interface
Overview
Overview
This chapter describes the following:
■
Physical Interfaces
■
Management interfaces
■
Advantages of using each interface
Understanding Physical Interfaces
Physical interfaces on the switch and the C-class enclosure it is installed in
provide the following options for accessing the management interfaces
described in the next section:
2-2
■
Data ports on the switch console provide networked in-band access
■
Dedicated serial connection to the C-class enclosure through the Onboard
Administrator (OA) provides out-of-band access.
For detailed instructions on how to login to the OA, refer to the Installation and Getting Stated Guide for the switch. See the HP BladeSystem
Onboard Administrator User Guide for details on OA setup. For information on OA command line interface (CLI) commands, see the HP
BladeSystem Onboard Administrator Command Line Interface User
Guide. Both guides are available at
www.hp.com/go/bladesystem/documentation.
■
Another way that the OA provides access is through the switch CLI; telnet
to the OA IP address and connect to the interconnect bay.
■
Mini-USB console port on the switch provides out-of-band access.
For instructions on how to download, install and run the USB driver, refer
to the Installation and Getting Stated Guide for the switch.
■
Dedicated networked management port in the C-class enclosure provides
networked out-of-band access. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on out-of-band
management.
Selecting a Management Interface
Understanding Management Interfaces
Note
The switches covered in this guide allow up to 6 console connections. Console
session 1 always belongs to the serial console, console session 2 always
belongs to the USB serial console, and the remaining 4 can be used via ssh or
telnet from a network connection.
Understanding Management Interfaces
Management interfaces enable you to reconfigure the switch and to monitor
switch status and performance. The switch offers the following interfaces:
■
Menu interface—a menu-driven interface offering a subset of switch
commands through the built-in VT-100/ANSI console—2-4
■
CLI—a command line interface offering the full set of switch commands
through the VT-100/ANSI console built into the switch—2-5
■
Web browser interface --a switch interface offering status information
and a subset of switch commands through a standard web browser (such
as Netscape Navigator or Microsoft Internet Explorer)—2-6
■
ProCurve Manager (PCM)—a windows-based network management
solution included in-box with all manageable ProCurve devices. Features
include automatic device discovery, network status summary, topology
and mapping, and device management.
■
ProCurve Manager Plus (PCM+)—a complete windows-based
network management solution that provides both the basic features
offered with PCM, as well as more advanced management features,
including in-depth traffic analysis, group and policy management, configuration management, device software updates, and advanced 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.
For information on how to access the web browser interface Help, see “Online
Help for the Web Browser Interface” on page 5-11.
To use ProCurve Manager or ProCurve Manager Plus, refer to the Getting
Started Guide and the Administrator’s Guide, which are available electronically with the software for these applications. For more information, visit the
ProCurve Networking web site at www.procurve.com.
2-3
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
VLANs and GVRP
Port Security
Port and Static Trunk Group
Spanning Tree
•
•
•
•
System information
Local passwords
SNMP communities
Time protocols
The menu interface also provides access for:
• Setup screen
• Event Log display
• Switch and port
status displays
2-4
• Switch and port statistic and counter displays
• Reboots
• Software downloads
■
Offers out-of-band access through the RS-232 connection and through
the OA network to the switch, so network bottlenecks, crashes, lack of
configured or correct IP address, and network downtime do not slow or
prevent access
■
Enables Telnet (in-band) access to the menu functionality.
■
Allows faster navigation, avoiding delays that occur with slower
display of graphical objects over a web browser interface.
■
Provides more security; configuration information and passwords are
not seen on the network.
Selecting a Management Interface
Advantages of Using the CLI
Advantages of Using the CLI
ProCurve>
Prompt for Operator Level
ProCurve#
Prompt for Manager Level
ProCurve(config)#
Prompt for Global Configuration
Level
ProCurve(<context>)#
Prompt for Context
Configuration Levels
For example:
ProCurve(eth-1-5)#
ProCurve(vlan-1)#
Figure 2-2. Command Prompt Examples
General Benefits
■
Provides access to the complete set of the switch configuration, performance, and diagnostic features.
■
Offers out-of-band access through the RS-232 connection and through the
through the OA network, or Telnet (in-band) access.
■
Enables quick, detailed system configuration and management access to
system operators and administrators experienced in command prompt
interfaces.
■
Provides help at each level for determining available options and variables.
Information on Using the CLI
■
For information on how to use the CLI, refer to Chapter 4. “Using the
Command Line Interface (CLI)”.
■
To perform specific procedures (such as configuring IP addressing or
VLANs), use the Contents listing at the front of the manual to locate the
information you need.
■
For monitoring and analyzing switch operation, refer to Appendix B.
■
For information on individual CLI commands, refer to the Index or to the
online Help provided in the CLI interface.
2-5
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
2-6
■
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
■
Many features have all their fields in one screen so you can view all
values at once
■
More visual cues, using colors, status bars, device icons, and other
graphical objects instead of relying solely on alphanumeric values
■
Display of acceptable ranges of values available in configuration list
boxes
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
Advantages of Using ProCurve Manager
or ProCurve Manager Plus
You can operate ProCurve Manager and ProCurve Manager Plus (PCM and
PCM+) from a PC on the network to monitor traffic, manage your hubs and
switches, and proactively recommend network changes to increase network
uptime and optimize performance. Easy to install and use, PCM and PCM+ are
the answers to your management challenges.
Figure 2-4. Example of the Home Page for ProCurve Manager Plus
2-7
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
PCM and PCM+ enable greater control, uptime, and performance in your
network:
■
■
2-8
Features and benefits of ProCurve Manager:
•
Network Status Summary: Upon boot-up, a network status screen
displays high-level information on network devices, end nodes,
events, and traffic levels. From here, users can research any one of
these areas to get more details.
•
Alerts and Troubleshooting: An events summary screen displays
alerts to the user and categorizes them by severity, making it easier
to track where bottlenecks and issues exist in the network. Alerts
present detailed information on the problem, even down to the specific port.
•
Automatic Device Discovery: This feature is customized for fast
discovery of all ProCurve manageable network devices. The user can
define which IP subnets to discover.
•
Topology and Mapping: This feature automatically creates a map of
discovered network devices. Maps are color-coded to reflect device
status and can be viewed at multiple levels (physical view, subnet
view, or VLAN view).
•
Device Management: Many device-focused tasks can be performed
directly by the software, or the user can access web-browser and
command-line interfaces with the click of a button to manage individual devices from inside the tool.
Features and benefits of ProCurve Manager Plus:
•
All of the Features of ProCurve Manager: Refer to the above
listing.
•
In-Depth Traffic Analysis: An integrated, low-overhead traffic monitor interface shows detailed information on traffic throughout the
network. Using enhanced traffic analysis protocols such as 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. Configurations can be compared over time or
between two devices, with the differences highlighted for users.
•
Advanced VLAN Management: A new, easy-to-use VLAN management interface allows users to create and assign VLANs across the
entire network, without having to access each network device individually.
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
•
Device Software Updates: This feature automatically obtains new
device software images from ProCurve and updates devices, allowing
users to download the latest version or choose the desired version.
Updates can be scheduled easily across large groups of devices, all at
user-specified times.
•
Investment Protection: The modular software architecture of ProCurve Manager Plus will allow ProCurve to offer network administrators add-on software solutions that complement their needs.
Custom Login Banners for the Console and
Web Browser Interfaces
You can configure the switch to display a login banner of up to 3070 characters
when an operator initiates a management session with the switch through any
of the following methods:
■
Telnet
■
serial connection
■
SSHv2
■
Web browser
The default banner displays product registration information; the copyright
splash is no longer displayed.
If a banner is configured, the banner page is displayed when you access the
Web user interface. The default product registration information is not
displayed as there is already a product registration prompt displayed in the
Web user interface.
Banner Operation with Telnet, Serial, or SSHv2 Access
When a system operator begins a login session, the switch displays the banner
above the local password prompt or, if no password is configured, above the
Press any key to continue prompt. Entering a correct password or, if no password
is configured, pressing any key clears the banner from the CLI and displays
the CLI prompt. (Refer to Figure 2-5 on page 2-11.)
Banner Operation with Web Browser Access
When a system operator uses a Web browser to access the switch, the text of
a non-default banner configured on the switch appears in a dedicated banner
window with a link to the Web agent home page. Clicking on To Home Page
2-9
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
clears the banner window and prompts the user for a password (if configured).
Following entry of the correct username/password information (or if no
username/password is required), the switch then displays either the Registration page or the switch’s home page. Note that if the banner feature is disabled
or if the switch is using the factory-default banner shown in figure 2-5, then
the banner page does not appear in the Web browser when an operator
initiates a login session with the switch.
Configuring and Displaying a Non-Default Banner
You can enable or disable banner operation using either the switch’s CLI or
an SNMP application. The steps include:
1.
Enable non-default banner operation and define the endpoint delimiter
for the banner.
2.
Enter the desired banner text, including any specific line breaks you
want.
3.
Enter the endpoint delimiter.
Use show banner motd to display the current banner status.
Syntax: banner motd < delimiter >
no banner motd
This command defines the single character used to terminate the banner text and enables banner text input. You
can use any character except a blank space as a delimiter.
The no form of the command disables the login banner
feature.
< banner-text-string >
The switch allows up to 3070 banner characters,
including blank spaces and CR-LF ([Enter]). (The tilde “ ~“
and the delimiter defined by banner motd <delimiter> are
not allowed as part of the banner text.) While entering
banner text, you can backspace to edit the current line
(that is, a line that has not been terminated by a CR-LF.)
However, terminating a line in a banner by entering a
CR-LF prevents any further editing of that line. To edit a
line in a banner entry after terminating the line with a
CR-LF requires entering the delimiter described above
and then re-configuring new banner text.
The banner text string must terminate with the character
defined by banner motd < delimiter >.
Note: In redundant management, the banner is not seen
on the standby module, only the active module.
2-10
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
Example of Configuring and Displaying a Banner
Suppose a system operator wanted to configure the following banner message
on her company’s switches:
This is a private system maintained by the
Allied Widget Corporation.
Unauthorized use of this system can result in
civil and criminal penalties!
In this case, the operator will use the [Enter] key to create line breaks, blank
spaces for line centering, and the % symbol to terminate the banner message.
Figure 2-5. Example of Configuring a Login Banner
To view the current banner configuration, use either the show banner motd or
show running command.
ProCurve(config)# show banner motd
Banner Information
Banner status: Enabled
Configured Banner:
This is a private system maintained by the
Allied Widget Corporation.
Unauthorized use of this system can result in
civil and criminal penalties!
Figure 2-6. Example of show banner motd Output
2-11
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
ProCurve (config)# show running
Running configuration:
; 498358-B21
#Z.14.04
Configuration
Editor;
Created
on
release
hostname "ProCurve 6120 Blade Switch"
vlan 1
name "DEFAULT_VLAN"
untagged D1-4,S1-S2,X1-X2,C1
ip address dhcp-bootp
exit
banner motd "This is a private system maintained by the
Allied Widget Corporation.
Unauthorized use of this system can result in
civil and criminal penalties!"
snmp-server community "public" Unrestricted
Shows the current banner
configuration.
Figure 2-7. The Current Banner Appears in the Switch’s Running-Config File
The next time someone logs onto the switch’s management CLI, the following
appears:
The login screen displays the
configured banner.
Entering a correct password
clears the banner and displays
the CLI prompt.
Figure 2-8. Example of CLI Result of the Login Banner Configuration
2-12
Selecting a Management Interface
Advantages of Using ProCurve Manager or ProCurve Manager Plus
If someone uses a Web browser to log in to the switch interface, the following
message appears:
Figure 2-9. Example of Web Browser Interface Result of the Login Banner
Configuration
Operating Notes
■
The default banner appears only when the switch is in the factory
default configuration. Using no banner motd deletes the currently
configured banner text and blocks display of the default banner. The
default banner is restored only if the switch is reset to its factorydefault configuration.
■
The switch supports one banner at any time. Configuring a new
banner replaces any former banner configured on the switch.
■
If the switch is configured with ssh version 1 or ssh version 1-or-2,
configuring the banner sets the SSH configuration to ssh version 2
and displays the following message in the CLI:
Warning: SSH version has been set to v2.
■
If a banner is configured, the switch does not allow configuration with
ssh version 1 or ssh version 1-or-2. Attempting to do so produces the
following error message in the CLI:
Banner has to be disabled first.
■
If a banner is enabled on the switch, the Web browser interface
displays the following link to the banner page:
Notice to all users
2-13
3
Using the Menu Interface
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Starting and Ending a Menu Session . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
How To Start a Menu Interface Session . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
How To End a Menu Session and Exit from the Console: . . . . . . . . . . 3-5
Main Menu Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Screen Structure and Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Menu Features List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Where To Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3-1
Using the Menu Interface
Overview
Overview
This chapter describes the following features:
■
Overview of the Menu Interface (page 3-2)
■
Starting and ending a Menu session (page 3-3)
■
The Main Menu (page 3-7)
■
Screen structure and navigation (page 3-9)
■
Rebooting the switch (page 3-12)
The menu interface operates through the switch console to provide you with
a subset of switch commands in an easy-to-use menu format enabling you to:
■
Perform a “quick configuration” of basic parameters, such as the IP
addressing needed to provide management access through your network
■
Configure these features:
• Manager and Operator
passwords
• A network monitoring port
• System parameters
• IP authorized managers
• IP addressing
• VLANs (Virtual LANs) and GVRP
• SNMP community names
• Time protocol
• Ports
• Trunk groups
■
View status, counters, and Event Log information
■
Update switch software
■
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 recommends 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. An Operator password, if configured, grants access to status and
counter, Event Log, and the Operator level in the CLI. After you configure
passwords on the switch and log off of the interface, access to the menu
interface (and the CLI and web browser interface) will require entry of either
the Manager or Operator password. (If the switch has only a Manager password, then someone without a password can still gain read-only access.)
3-2
Using the Menu Interface
Starting and Ending a Menu Session
Note
If the switch has neither a Manager nor an Operator password, anyone
having access to the console interface can operate the console with full
manager privileges. Also, if you configure only an Operator password,
entering the Operator password enables full manager privileges.
For more information on passwords, refer to the Access Security Guide for
your switch.
Menu Interaction with Other Interfaces.
■
The menu interface displays the current running-config parameter settings. You can use the menu interface to save configuration changes made
in the CLI only if the CLI changes are in the running config when you save
changes made in the menu interface. (For more on how switch memory
manages configuration changes, see Chapter 6, “Switch Memory and
Configuration”.)
■
A configuration change made through any switch interface overwrites
earlier changes made through any other interface.
■
The Menu Interface and the CLI (Command Line Interface) both use the
switch console. To enter the menu from the CLI, use the menu command.
To enter the CLI from the Menu interface, select Command Line (CLI) option.)
Starting and Ending a Menu Session
You can access the menu interface using any of the following:
Note
■
A direct serial connection to the switch’s console port, as described in the
installation and getting started guide you received with the switch
■
A Telnet connection to the switch console from a networked PC or the
switch’s web browser interface. Telnet requires that an IP address and
subnet mask compatible with your network have already been configured
on the switch.
This section assumes that either a terminal device is already configured and
connected to the switch (see the Installation and Getting Started Guide) or
that you have already configured an IP address on the switch (required for
Telnet access).
3-3
Using the Menu Interface
Starting and Ending a Menu Session
How To Start a Menu Interface Session
In its factory default configuration, the switch console starts with the CLI
prompt. To use the menu interface with Manager privileges, go to the Manager
level prompt and enter the menu command.
1.
2.
3.
Use one of these methods to connect to the switch:
•
A PC terminal emulator or terminal
•
Telnet
Do one of the following:
•
If you are using Telnet, go to step 3.
•
If you are using a PC terminal emulator or a terminal, press [Enter] one
or more times until a prompt appears.
When the switch screen appears, do one of the following:
•
If a password has been configured, the password prompt appears.
Password: _
Type the Manager password and press [Enter]. Entering the Manager
password gives you manager-level access to the switch. (Entering the
Operator password gives you operator-level access to the switch.
Refer to the Access Security Guide for your switch.)
•
4.
If no password has been configured, the CLI prompt appears. Go to
the next step.
When the CLI prompt appears, display the Menu interface by entering the
menu command. For example:
ProCurve# menu [Enter]
results in the following display:
3-4
Using the Menu Interface
Starting and Ending a Menu Session
Figure 3-1. Example of the Main Menu with Manager Privileges
For a description of Main Menu features, see “Main Menu Features” on page
3-7.
Note
To configure the switch to start with the menu interface instead of the CLI, go
to the Manager level prompt in the CLI, enter the setup command, and in the
resulting display, change the Logon Default parameter to Menu. For more information, see the Installation and Getting Started Guide you received with the
switch.
How To End a Menu Session and Exit from the Console:
The method for ending a menu session and exiting from the console depends
on whether, during the session, you made any changes to the switch configuration that require a switch reboot to activate. (Most changes via the menu
interface need only a Save, and do not require a switch reboot.) Configuration
changes needing a reboot are marked with an asterisk (*) next to the configured item in the menu and also next to the Switch Configuration item in the
Main Menu.
3-5
Using the Menu Interface
Starting and Ending a Menu Session
Asterisk indicates a
configuration change
that requires a reboot
to activate.
Figure 3-2. Example Indication of a Configuration Change Requiring a Reboot
1.
In the current session, if you have not made configuration changes that
require a switch reboot to activate, return to the Main Menu and press [0]
(zero) to log out. Then just exit from the terminal program, turn off the
terminal, or quit the Telnet session.
2.
If you have made configuration changes that require a switch reboot—
that is, if an asterisk (*) appears next to a configured item or next to Switch
Configuration in the Main Menu:
a.
Return to the Main Menu.
b.
Press [6] to select Reboot Switch and follow the instructions on the
reboot screen.
Rebooting the switch terminates the menu session, and, if you are using
Telnet, disconnects the Telnet session.
(See “Rebooting To Activate Configuration Changes” on page 3-13.)
3.
3-6
Exit from the terminal program, turn off the terminal, or close the Telnet
application program.
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, and port and VLAN address
tables. (Refer to Appendix B, “Monitoring and Analyzing Switch Operation”.)
■
Switch Configuration: Provides access to configuration screens for
displaying and changing the current configuration settings. (See the Contents listing at the front of this manual.) For a listing of features and
parameters configurable through the menu interface, see the “Menu Features List” on page 3-14. For an index of the features covered in the
software manuals for your switch, refer to the “Software Feature Index”
on page -xxii.
■
Console Passwords: Provides access to the screen used to set or change
Manager-level and Operator-level passwords, and to delete Manager and
Operator password protection. (Refer to the chapter on configuring usernames and passwords in the Access Security Guide for your switch.)
■
Event Log: Enables you to read progress and error messages that are
useful for checking and troubleshooting switch operation. (See “Using the
Event Log for Troubleshooting Switch Problems” on page C-24.)
3-7
Using the Menu Interface
Main Menu Features
3-8
■
Command Line (CLI): Selects the Command Line Interface at the same
level (Manager or Operator) that you are accessing in the Menu interface.
(Refer to Chapter 4, “Using the Command Line Interface (CLI)”.)
■
Reboot Switch: Performs a “warm” reboot of the switch, which clears
most temporary error conditions, resets the network activity counters to
zero, and resets the system up-time to zero. A reboot is required to activate
a change in the VLAN Support parameter. (See “Rebooting from the Menu
Interface” on page 6-11.)
■
Download OS: Enables you to download a new switch software version
to the switch. (See Appendix A, “File Transfers”.)
■
Run Setup: Displays the Switch Setup screen for quickly configuring
basic switch parameters such as IP addressing, default gateway, logon
default interface, and others. (Refer to the Installation and Getting
Started Guide for your switch.)
■
Logout: Closes the Menu interface and console session, and disconnects
Telnet access to the switch. (See “How to End a Menu Session and Exit
from the Console” on page 3-5.)
Using the Menu Interface
Screen Structure and Navigation
Screen Structure and Navigation
Menu interface screens include these three elements:
■
Parameter fields and/or read-only information such as statistics
■
Navigation and configuration actions, such as Save, Edit, and Cancel
■
Help line to describe navigation options, individual parameters, and readonly data
For example, in the following System Information screen:
Screen title – identifies
the location within the
menu structure
Parameter fields
Help describing each of the
items in the parameter fields
Actions line
Help line
describing the
selected action
or selected
parameter field
Navigation instructions
Figure 3-4. Elements of the Screen Structure
“Forms” Design. The configuration screens, in particular, operate similarly
to a number of PC applications that use forms for data entry. When you first
enter these screens, you see the current configuration for the item you have
selected. To change the configuration, the basic operation is to:
1.
Press [E] to select the Edit action.
2.
Navigate through the screen making all the necessary configuration
changes. (See Table 3-1 on page 3-10.)
3.
Press [Enter] to return to the Actions line. From there you can save the
configuration changes or cancel the changes. Cancel returns the configuration to the values you saw when you first entered the screen.
3-9
Using the Menu Interface
Screen Structure and Navigation
Table 3-1.
3-10
How To Navigate in the Menu Interface
Task:
Actions:
Execute an action
from the “Actions –>”
list at the bottom of
the screen:
Use either of the following methods:
• Use the arrow keys ([<], or [>]) to highlight the action you want
to execute, then press [Enter].
• Press the key corresponding to the capital letter in the action
name. For example, in a configuration menu, press [E] to select
Edit and begin editing parameter values.
Reconfigure (edit) a
parameter setting or a
field:
1. Select a configuration item, such as System Name. (See figure
3-4.)
2. Press [E] (for Edit on the Actions line).
3. Use [Tab] or the arrow keys ([<], [>], [^], or [v]) to highlight the
item or field.
4. Do one of the following:
– If the parameter has preconfigured values, either use the
Space bar to select a new option or type the first part of your
selection and the rest of the selection appears automatically.
(The help line instructs you to “Select” a value.)
– If there are no preconfigured values, type in a value (the Help
line instructs you to “Enter” a value).
5. If you want to change another parameter value, return to step 3.
6. If you are finished editing parameters in the displayed screen,
press [Enter] to return to the Actions line and do one of the
following:
– To save and activate configuration changes, press [S] (for the
Save action). This saves the changes in the startup
configuration and also implements the change in the
currently running configuration. (See Chapter 6, “Switch
Memory and Configuration”.)
– To exit from the screen without saving any changes that you
have made (or if you have not made changes), press [C] (for
the Cancel action).
Note: In the menu interface, executing Save activates most
parameter changes and saves them in the startup configuration
(or flash) memory, and it is therefore not necessary to reboot the
switch after making these changes. But if an asterisk appears
next to any menu item you reconfigure, the switch will not
activate or save the change for that item until you reboot the
switch. In this case, rebooting should be done after you have
made all desired changes and then returned to the Main Menu.
7. When you finish editing parameters, return to the Main Menu.
8. If necessary, reboot the switch by highlighting Reboot Switch in
the Main Menu and pressing [Enter]. (See the Note, above.)
Exit from a read-only
screen.
Press [B] (for the Back action).
Using the Menu Interface
Screen Structure and Navigation
To get Help on individual parameter descriptions. In most screens
there is a Help option in the Actions line. Whenever any of the items in the
Actions line is highlighted, press [H], and a separate help screen is displayed.
For example:
Pressing [H] or highlighting Help and
pressing [Enter] displays Help for the
parameters listed in the upper part of
the screen
Highlight on any item in
the Actions line
indicates that the
Actions line is active.
The Help line provides
a brief descriptor of
the highlighted Action
item or parameter.
Figure 3-5. Example Showing How To Display Help
To get Help on the actions or data fields in each screen: Use the arrow
keys ([<], [>], [^], or [v]) to select an action or data field. The help line under the
Actions items describes the currently selected action or data field.
For guidance on how to navigate in a screen: See the instructions provided
at the bottom of the screen, or refer to “Screen Structure and Navigation” on
page 3-9.)
3-11
Using the Menu Interface
Rebooting the Switch
Rebooting the Switch
Rebooting the switch from the menu interface
■
Terminates all current sessions and performs a reset of the operating
system
■
Activates any menu interface configuration changes that require a reboot
■
Resets statistical counters to zero
(Note that statistical counters can be reset to zero without rebooting the
switch.)
To Reboot the switch, use the Reboot Switch option in the Main Menu. (Note
that Reboot Switch is not available if you log on in Operator mode; that is, if
you enter an Operator password instead of a manager password at the
password prompt.)
Reboot Switch option
Figure 3-6. The Reboot Switch Option in the Main Menu
3-12
Using the Menu Interface
Rebooting the Switch
Rebooting To Activate Configuration Changes. Configuration changes
for most parameters in the menu interface become effective as soon as you
save them. However, you must reboot the switch in order to implement a
change in the Maximum VLANs to support parameter. (To access this parameter, go
to the Main Menu and select:
2. Switch Configuration
8. VLAN Menu
1. VLAN Support.
If you make configuration changes in the menu interface that require a reboot,
the switch displays an asterisk (*) next to the menu item in which the change
has been made. For example, if you change and save the value for the Maximum
VLANs to support parameter, an asterisk appears next to the VLAN Support entry
in the VLAN Menu screen, and also next to the Switch Configuration entry in
the Main Menu.
Asterisk
indicates a
configuration
change that
requires a
reboot in order
to take effect.
Reminder to
reboot the
switch to
activate
configuration
changes.
Figure 3-7. Indication of a Configuration Change Requiring a Reboot
To activate changes indicated by the asterisk, go to the Main Menu and select
the Reboot Switch option.
Note
Executing the write memory command in the CLI does not affect pending
configuration changes indicated by an asterisk in the menu interface. That is,
only a reboot from the menu interface or a boot or reload command from the
CLI will activate a pending configuration change indicated by an asterisk.
3-13
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
Switch Configuration
•
System Information
•
Port/Trunk Settings
•
Network Monitoring Port
•
IP Configuration
•
SNMP Community Names
•
IP authorized Managers
•
VLAN Menu
Console Passwords
Event Log
Command Line (CLI)
Reboot Switch
Download OS (Download Switch Software)
Run Setup
Logout
3-14
Using the Menu Interface
Where To Go From Here
Where To Go From Here
This chapter provides an overview of the menu interface and how to use it.
The following table indicates where to turn for detailed information on how
to use the individual features available through the menu interface.
Option:
Turn to:
To use the Run Setup option
Refer to the Installation and Getting Started
Guide.
To view and monitor switch status and Appendix B, “Monitoring and Analyzing Switch
counters
Operation”
To learn how to configure and use
Refer to the Access Security Guide for your
passwords and other security features switch.
To learn how to use the Event Log
“Using the Event Log for Troubleshooting Switch
Problems” on page C-24
To learn how the CLI operates
Chapter 4, “Using the Command Line Interface
(CLI)”
To download switch software
Appendix A, “File Transfers”
For a description of how switch
memory handles configuration
changes
Chapter 6, “Switch Memory and Configuration”
For information on other switch
features and how to configure them
Refer to the Feature Index on (page xxii) at the
front of this guide, and to “Sources for More
Information” on page 1-4.
3-15
4
Using the Command Line Interface (CLI)
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Privilege Levels at Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Privilege Level Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Operator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Manager Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
How To Move Between Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Listing Commands and Command Options . . . . . . . . . . . . . . . . . . . . . . 4-8
Listing Commands Available at Any Privilege Level . . . . . . . . . . . 4-8
Listing Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Displaying CLI “Help” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Configuration Commands and the Context Configuration Modes . . 4-13
CLI Control and Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Executing a Prior Command—Redo . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Repeating Execution of a Command . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Using a Command Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
CLI Shortcut Keystrokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4-1
Using the Command Line Interface (CLI)
Overview
Overview
The CLI is a text-based command interface for configuring and monitoring the
switch. The CLI gives you access to the switch’s full set of commands while
providing the same password protection that is used in the web browser
interface and the menu interface.
Accessing the CLI
Like the menu interface, the CLI is accessed through the switch console, and
in the switch’s factory default state, is the default interface when you start a
console session. You can access the console out-of-band by directly connecting a terminal device to the switch, or in-band by using Telnet either from a
terminal device or through the web browser interface.
Also, if you are using the menu interface, you can access the CLI by selecting
the Command Line (CLI) option in the Main Menu.
Using the CLI
The CLI offers these privilege levels to help protect the switch from unauthorized access:
Note
4-2
1.
Operator
2.
Manager
3.
Global Configuration
4.
Context Configuration
CLI commands are not case-sensitive.
Using the Command Line Interface (CLI)
Using the CLI
When you use the CLI to make a configuration change, the switch writes the
change to the Running-Config file in volatile memory. This allows you to test
your configuration changes before making them permanent. To make changes
permanent, you must use the write memory command to save them to the
Startup-Config file in non-volatile memory. If you reboot the switch without
first using write memory, all changes made since the last reboot or write memory
(whichever is later) will be lost. For more on switch memory and saving
configuration changes, see Chapter 6, “Switch Memory and Configuration”.
Privilege Levels at Logon
Privilege levels control the type of access to the CLI. To implement this
control, you must set at least a Manager password. Without a Manager
password configured, anyone having serial port, Telnet, or web browser
access to the switch can reach all CLI levels. (For more on setting passwords,
refer to the chapter on usernames and passwords in the Access Security Guide
for your switch.)
When you use the CLI to log on to the switch, and passwords are set, you will
be prompted to enter a password. For example:
Password Prompt
Figure 4-1. Example of CLI Log-On Screen with Password(s) Set
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# _
4-3
Using the Command Line Interface (CLI)
Using the CLI
Caution
ProCurve strongly recommends that you configure a Manager password. If a
Manager password is not configured, then the Manager level is not passwordprotected, and anyone having in-band or out-of-band access to the switch may
be able to reach the Manager level and compromise switch and network
security. Note that configuring only an Operator password does not prevent
access to the Manager level by intruders who have the Operator password.
Pressing the Clear button on the front of the switch removes password
protection. For this reason, it is recommended that you protect the switch
from physical access by unauthorized persons. If you are concerned about
switch security and operation, you should install the switch in a secure
location, such as a locked wiring closet.
Privilege Level Operation
Operator Privileges
1. Operator Level
Manager Privileges
2. Manager Level
3. Global Configuration
4. Context Configuration Level
Figure 4-2. Access Sequence for Privilege Levels
Operator Privileges
At the Operator level you can examine the current configuration and move
between interfaces without being able to change the configuration. A “>”
character delimits the Operator-level prompt. For example:
ProCurve> _
(Example of the Operator prompt.)
When using enable to move to the Manager level, the switch prompts you for
the Manager password if one has already been configured.
4-4
Using the Command Line Interface (CLI)
Using the CLI
Manager Privileges
Manager privileges give you three additional levels of access: Manager, Global
Configuration, and Context Configuration. A “#” character delimits any Manager prompt. For example:
ProCurve#_
■
Example of the Manager prompt.
Manager level: Provides all Operator level privileges plus the ability to
perform system-level actions that do not require saving changes to the
system configuration file. The prompt for the Manager level contains only
the system name and the “#” delimiter, as shown above. To select this
level, enter the enable command at the Operator prompt and enter the
Manager password, when prompted. For example:
ProCurve> enable
Password:
ProCurve# _
■
Enter enable at the Operator prompt.
CLI prompt for the Manager password.
The Manager prompt appears after the
correct Manager password is entered.
Global Configuration level: Provides all Operator and Manager level
privileges, and enables you to make configuration changes to any of the
switch’s software features. The prompt for the Global Configuration level
includes the system name and “(config)”. To select this level, enter the
config command at the Manager prompt. For example:
ProCurve# config
Enter config at the Manager prompt.
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. The prompt for the Context
Configuration level includes the system name and the selected context.
For example:
ProCurve(eth-1)#
ProCurve(vlan-10)#
The Context level is useful, for example, for executing several commands
directed at the same port or VLAN, or if you want to shorten the command
strings for a specific context area. To select this level, enter the specific
context at the Global Configuration level prompt. For example, to select
the context level for an existing VLAN with the VLAN ID of 10, you would
enter the following command and see the indicated result:
ProCurve(config)# vlan 10
ProCurve(vlan-10)#
4-5
Using the Command Line Interface (CLI)
Using the CLI
Table 4-1.
Privilege Level Hierarchy
Privilege
Level
Example of Prompt and Permitted Operations
Operator Privilege
Operator Level ProCurve>
show < command >
setup
View status and configuration information.
ping < argument >
link-test < argument >
Perform connectivity tests.
enable
Move from the Operator level to the Manager
level.
menu
Move from the CLI interface to the menu interface.
logout
Exit from the CLI interface and terminate the
console session.
exit
Terminate the current session (same as logout).
Manager Privilege
Manager Level ProCurve#
Perform system-level actions such as system
control, monitoring, and diagnostic commands,
plus any of the Operator-level commands. For a list
of available commands, enter ? at the prompt.
Global
Configuration
Level
ProCurve(config)#
Execute configuration commands, plus all
Operator and Manager commands. For a list of
available commands, enter ? at the prompt.
Context
Configuration
Level
ProCurve(eth-5)#
ProCurve(vlan100)#
Execute context-specific configuration
commands, such as a particular VLAN or switch
port. This is useful for shortening the command
strings you type, and for entering a series of
commands for the same context. For a list of
available commands, enter ? at the prompt.
4-6
Using the Command Line Interface (CLI)
Using the CLI
How To Move Between Levels
Change in Levels
Example of Prompt, Command, and Result
Operator level
to
Manager level
ProCurve> enable
Password:_
After you enter enable, the Password
prompt appears. After you enter the
Manager password, the system prompt
appears with the # symbol:
ProCurve#_
Manager level
to
Global configuration
level
ProCurve# config
ProCurve(config)#
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 ProCurve(int-3)# exit
to the preceding level ProCurve(config)# exit
ProCurve# exit
ProCurve>
Move from any level
to the Manager level
ProCurve(int-3)# end
ProCurve#
—or—
ProCurve(config)# end
ProCurve#
Moving Between the CLI and the Menu Interface. When moving
between interfaces, the switch retains the current privilege level (Manager or
Operator). That is, if you are at the Operator level in the menu and select the
Command Line Interface (CLI) option from the Main Menu, the CLI prompt
appears at the Operator level.
Changing Parameter Settings. Regardless of which interface is used (CLI,
menu interface, or web browser interface), the most recently configured
version of a parameter setting overrides any earlier settings for that parameter.
4-7
Using the Command Line Interface (CLI)
Using the CLI
For example, if you use the menu interface to configure an IP address of “X”
for VLAN 1 and later use the CLI to configure a different IP address of “Y” for
VLAN 1, then “Y” replaces “X” as the IP address for VLAN 1 in the runningconfig file. If you subsequently execute write memory in the CLI, then the
switch also stores “Y” as the IP address for VLAN 1 in the startup-config file.
(For more on the startup-config and running config files, see Chapter 6,
“Switch Memory and Configuration”.)
Listing Commands and Command Options
At any privilege level you can:
■
List all of the commands available at that level
■
List the options for a specific command
Listing Commands Available at Any Privilege Level
At a given privilege level you can list and execute the commands that level
offers, plus all of the commands available at preceding levels. For example,
at the Operator level, you can list and execute only the Operator level commands. However, at the Manager level, you can list and execute the commands
available at both the Operator and Manager levels.
Type “?” To List Available Commands. 1.Typing the ? symbol lists the
commands you can execute at the current privilege level. For example,
typing ? at the Operator level produces this listing:
Figure 4-3. Example of the Operator Level Command Listing
4-8
Using the Command Line Interface (CLI)
Using the CLI
Typing ? at the Manager level produces this listing:
When - - MORE - - appears, use the Space
bar or [Return] to list additional commands.
Figure 4-4.Example of the Manager-Level Command Listing
When - - MORE - - appears, there are more commands in the listing. To list the
next screenfull of commands, press the Space bar. To list the remaining
commands one-by-one, repeatedly press [Enter].
Typing ? at the Global Configuration level or the Context Configuration level
produces similar results.
Use [Tab] To Search for or Complete a Command Word. You can use
[Tab] to help you find CLI commands or to quickly complete the current word
in a command. To do so, type one or more consecutive characters in a
command and then press [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]
tacacs-server
telnet-server
time
timesync
trunk
telnet
terminal
traceroute
ProCurve(config)# t
4-9
Using the Command Line Interface (CLI)
Using the CLI
As mentioned above, if you type part of a command word and press [Tab], the
CLI completes the current word (if you have typed enough of the word for the
CLI to distinguish it from other possibilities), including hyphenated extensions. For example:
ProCurve(config)# port-[Tab]
ProCurve(config)# port-security _
Pressing [Tab] after a completed command word lists the further options for
that command.
ProCurve(config)# qos [Tab]
udp-portSet UDP port based priority.
tcp-portSet TCP port based priority.
device-priorityConfigure device-based priority.
dscp-mapDefine mapping between a DSCP
(Differentiated-Services Codepoint)
value and 802.1p priority.
type-of-serviceConfigure the Type-of-Service
method the device uses to
prioritize IP traffic.
Listing Command Options
You can use the CLI to remind you of the options available for a command by
entering command keywords followed by ?. For example, suppose you want
to see the command options for configuring the console settings:
This example displays the command options
for configuring the switch’s console settings.
Figure 4-5. Example of How To List the Options for a Specific Command
4-10
Using the Command Line Interface (CLI)
Using the CLI
Displaying CLI “Help”
CLI Help provides two types of context-sensitive information:
■
Command list with a brief summary of each command’s purpose
■
Detailed information on how to use individual commands
Displaying Command-List Help.
Syntax: help
Displays a listing of command Help summaries for all
commands available at the current privilege level. That is, at
the Operator level, executing help displays the Help summaries
only for Operator-Level commands. At the Manager level,
executing help displays the Help summaries for both the
Operator and Manager levels, and so on.
For example, to list the Operator-Level commands with their purposes:
Figure 4-6. Example of Context-Sensitive Command-List Help
Displaying Help for an Individual Command.
Syntax: < command-string > help
This option displays Help for any command available at the
current context level.
For example, to list the Help for the interface command in the Global Configuration privilege level:
4-11
Using the Command Line Interface (CLI)
Using the CLI
Figure 4-7.Example of How To Display Help for a Specific Command
Note that trying to list the help for an individual command from a privilege
level that does not include that command results in an error message. For
example, trying to list the help for the interface command while at the global
configuration level produces this result:
ProCurve# speed-duplex help
Invalid input: speed-duplex
4-12
Using the Command Line Interface (CLI)
Using the CLI
Configuration Commands and the Context
Configuration Modes
You can execute any configuration command in the global configuration mode
or in selected context modes. However, using a context mode enables you to
execute context-specific commands faster, with shorter command strings.
The switch offers interface (port or trunk group) and VLAN context configuration modes:
Port or Trunk-Group Context. Includes port- or trunk-specific commands
that apply only to the selected port(s) or trunk group, plus the global configuration, Manager, and Operator commands. The prompt for this mode
includes the identity of the selected port(s):
ProCurve(config)# interface c3-c6
ProCurve(eth-C5-C8)#
ProCurve(config)# interface trk1
ProCurve(eth-Trk1)#
Commands executed at configuration level for entering port and
trk1 static trunk-group contexts, and resulting prompts showing
port or static trunk contexts..
ProCurve(eth-C5-C8)#
ProCurve(eth-Trk1)#
ProCurve(eth-C5-C8)# ?
ProCurve(eth-C5-C8)# ?
Lists the commands you can use in the port or static trunk context,
plus the Manager, Operator, and context commands you can execute at this level.
4-13
Using the Command Line Interface (CLI)
Using the CLI
In the port context, the first block of commands in the “?”
listing show the context-specific commands that will affect
only ports C3-C6.
The remaining commands in the listing are Manager,
Operator, and context commands.
Figure 4-8. Context-Specific Commands Affecting Port Context
4-14
Using the Command Line Interface (CLI)
Using the CLI
VLAN Context . Includes VLAN-specific commands that apply only to the
selected VLAN, plus Manager and Operator commands. The prompt for this
mode includes the VLAN ID of the selected VLAN. For example, if you had
already configured a VLAN with an ID of 100 in the switch:
ProCurve(config)# vlan 100
Command executed at configuration level to enter VLAN 100 context.
ProCurve(vlan-100)#
Resulting prompt showing VLAN 100 context.
ProCurve(vlan-100)# ?
Lists commands you can use in the VLAN context, plus Manager,
Operator, and context commands you can execute at this level.
In the VLAN
context, the
first block of
commands in
the “?” listing
show the
commands that
will affect only
vlan-100.
The remaining
commands in
the listing are
Manager,
Operator, and
context
commands.
Figure 4-9. Context-Specific Commands Affecting VLAN Context
4-15
Using the Command Line Interface (CLI)
CLI Control and Editing
CLI Control and Editing
Executing a Prior Command—Redo
The redo command executes a prior command in the history list.
Syntax: redo [number | command-str]
Re-executes a command from history. Executes the last
command by default.
number: The position of the command to execute in the history
list. When number is specified, the nth command starting from
the most recent command in the history is executed.
command-str: When command-str is specified, the most recent
command whose name matches the specified string is
executed.
ProCurve(config)# show history
2
show arp
1
show flash
ProCurve(config)# redo 2
Executes the show arp command again.
IP ARP table
IP Address
--------------15.255.128.1
MAC Address
Type
Port
----------------- ------- ---00000c-07ac00
dynamic A11
Figure 4-10. Example of the redo Command
Repeating Execution of a Command
The repeat command executes a previous command in the history list.
4-16
Using the Command Line Interface (CLI)
CLI Control and Editing
Syntax: repeat [cmdlist] [count] [delay]
Repeats execution of a previous command. Repeats the last
command by default until a key is pressed.
cmdlist: If a number or range of numbers is specified, the
command repeats the nth most recent commands (where “n”
is the position in the history list).
count: Repeats the command for the number of times specified.
delay: The command repeats execution after a delay for the
number of seconds specified.
For example:
ProCurve(config)# repeat 1-4,7-8,10 count 2 delay 3
ProCurve(config)# show history
3
show ver
2
show ip
1
show arp
ProCurve(config)# repeat 1-2
Repeats the show arp and show ip commands.
IP ARP table
IP Address
--------------15.255.128.1
MAC Address
Type
Port
----------------- ------- ---000000-000000
dynamic
Internet (IP) Service
IP Routing : Disabled
Default Gateway
Default TTL
Arp Age
Domain Suffix
DNS server
:
: 64
: 20
:
:
VLAN
| IP Config IP Address
Subnet Mask
Proxy ARP
-------------------- + ---------- --------------- --------------- --------DEFAULT_VLAN
| DHCP/Bootp 15.255.131.90
255.255.248.0
No No
Figure 4-11. Example of repeat Command Using a Range
4-17
Using the Command Line Interface (CLI)
CLI Control and Editing
Using a Command Alias
You can create a simple command alias to use in place of a command name
and its options. Choose an alias name that is not an existing CLI command
already. Existing CLI commands are searched before looking for an alias
command; an alias that is identical to an existing command will not be
executed.
The alias command is executed from the current configuration context (operator, manager, or global). If the command that is aliased has to be executed in
the global configuration context, you must execute the alias for that command
in the global configuration context as well. This prevents bypassing the
security in place for a particular context.
ProCurve recommends that you configure no more than 128 aliases.
Syntax: [no] alias <name> <command>
Creates a shortcut alias name to use in place of a commonly
used command. The alias command is executed from the
current config context.
name: Specifies the new command name to use to simplify
keystrokes and aid memory.
command: Specifies an existing command to be aliased. The
command must be enclosed in quotes.
Use the no form of the command to remove the alias.
For example, if you use the show interface custom command to specify the
output, you can configure an alias for the command to simplify execution. It
is recommended that you use an alias that does not have an existing tab
completion in the CLI. For example, using an alias that starts with “show” or
“int” would complete to “show” and “interface” respectively when you use the
tab completion function.
4-18
Using the Command Line Interface (CLI)
CLI Control and Editing
ProCurve(config)# show int custom 1-4 port name:4 type vlan intrusion speed
enabled mdi
Status and Counters - Custom Port Status
Port
---1
2
3
4
Name
---------Acco
Huma
Deve
Lab1
Type
---------100/1000T
100/1000T
100/1000T
100/1000T
VLAN
----1
1
1
1
Intrusion
Alert
--------No
No
No
No
Speed
------1000FDx
1000FDx
1000FDx
1000FDx
Enabled
------Yes
Yes
Yes
Yes
MDI-mode
-------Auto
Auto
Auto
Auto
ProCurve(config)# alias sic “show int custom 1-4 port name:4 type vlan intrusion
speed enabled mdi”
ProCurve(config)#
ProCurve(config)# sic
Status and Counters - Custom Port Status
Port
---1
2
3
4
Name
---------Acco
Huma
Deve
Lab1
Type
---------100/1000T
100/1000T
100/1000T
100/1000T
VLAN
----1
1
1
1
Intrusion
Alert
--------No
No
No
No
Speed
------1000FDx
1000FDx
1000FDx
1000FDx
Enabled
------Yes
Yes
Yes
Yes
MDI-mode
-------Auto
Auto
Auto
Auto
Figure 4-12. Example of Using the Alias Command with show int custom
Note
Remember to enclose the command being aliased in quotes.
Command parameters for the aliased command can be added at the end of the
alias command string. For example:
ProCurve(config)# alias sc “show config”
ProCurve(config)# sc status
To change the command that is aliased, re-execute the alias name with new
command options. The new options are used when the alias is executed.
To display the alias commands that have been configured, enter the show alias
command.
4-19
Using the Command Line Interface (CLI)
CLI Control and Editing
ProCurve(config)# show alias
Name
-------------------sc
sic
Command
-----------------------------show config
show int custom 1-4 port name:4 type vlan intrusion
speed enabled mdi
Figure 4-13. Example of Alias Commands and Their Configurations
CLI Shortcut Keystrokes
Keystrokes
Function
[Ctrl] [A]
Jumps to the first character of the command line.
[Ctrl] [B] or [<]
Moves the cursor back one character.
[Ctrl] [C]
Terminates a task and displays the command prompt.
[Ctrl] [D]
Deletes the character at the cursor.
[Ctrl] [E]
Jumps to the end of the current command line.
[Ctrl] [F] or [>]
Moves the cursor forward one character.
[Ctrl] [K]
Deletes from the cursor to the end of the command line.
[Ctrl] [L] or [Ctrl] [R]
Repeats current command line on a new line.
[Ctrl] [N] or [v]
Enters the next command line in the history buffer.
[Ctrl] [P] or [^]
Enters the previous command line in the history buffer.
[Ctrl] [U] or [Ctrl] [X] Deletes from the cursor to the beginning of the command line.
4-20
[Ctrl] [W]
Deletes the last word typed.
[Esc] [B]
Moves the cursor backward one word.
[Esc] [D]
Deletes from the cursor to the end of the word.
[Esc] [F]
Moves the cursor forward one word.
[Backspace]
Deletes the first character to the left of the cursor in the command
line.
[Spacebar]
Moves the cursor forward one character.
5
Using the ProCurve Web Browser Interface
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Starting a Web Browser
Interface Session with the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Using a Standalone Web Browser in a PC or UNIX Workstation . . . . 5-4
Using ProCurve Manager (PCM) or
ProCurve Manager Plus (PCM+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Tasks for Your First ProCurve Web Browser Interface Session . . 5-7
Viewing the “First Time Install” Window . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Security: Creating Usernames and Passwords
in the Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Entering a User Name and Password . . . . . . . . . . . . . . . . . . . . . . 5-10
Using a User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
If You Lose the Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Online Help for the Web Browser Interface . . . . . . . . . . . . . . . . . . . . 5-11
Support/Mgmt URLs Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Support URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Help and the Management Server URL . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Using the PCM Server for Switch Web Help . . . . . . . . . . . . . . . . . . . . 5-14
Status Reporting Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
The Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
The Port Utilization and Status Displays . . . . . . . . . . . . . . . . . . . . . . . 5-17
Port Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
The Alert Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Sorting the Alert Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Alert Types and Detailed Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
The Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Setting Fault Detection Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
5-1
Using the ProCurve Web Browser Interface
Overview
Overview
The ProCurve web browser interface built into the switch lets you easily
access the switch from a browser-based PC on your network. This lets you do
the following:
■
Optimize your network uptime by using the Alert Log and other diagnostic
tools
■
Make configuration changes to the switch
■
Maintain security by configuring usernames and passwords
This chapter covers the following:
■
General features (page 5-3).
■
Starting a web browser interface session (page 5-4)
■
Tasks for your first web browser interface session (page 5-7):
■
•
Creating usernames and passwords in the web browser interface
(page 5-8)
•
Selecting the fault detection configuration for the Alert Log operation
(page 5-24)
•
Getting access to online help for the web browser interface (page
5-11)
Description of the web browser interface:
•
Note
Overview window and tabs (page 5-16)
•
Port Utilization and Status displays (page 5-17)
•
Alert Log and Alert types (page 5-20)
•
Setting the Fault Detection Policy (page 5-24)
You can disable access to the web browser interface by either executing no
web-management at the Command Prompt or changing the Web Agent Enabled
parameter setting to No (page 7-4).
For information on operating system, browser, and Java versions for the
switches covered in this guide, go to
www.hp.com/go/bladesystem/documentation.
5-2
Using the ProCurve Web Browser Interface
General Features
General Features
The web browser interface includes these features:
Switch Identity and Status:
• General system data
• Software version
• IP address
• Status Overview
• Port utilization
• Port counters
• Port status
• Alert log
Switch Configuration:
• Device view
• Port configuration
• VLAN configuration
• Fault detection
• Quality of service (QoS)
• Port monitoring (mirroring)
• System information
• IP configuration
• Support and management server URLs
• Device features (Spanning Tree On/Off, VLAN selection, and IGMP)
Switch Security:
• User names and passwords
• Authorized Addresses
• Intrusion Log
• SSL
• RADIUS authentication (Refer to the Access Security Guide.)
Switch Diagnostics:
• Ping/Link Test
• Device reset
• Configuration report
5-3
Using the ProCurve Web Browser Interface
Starting a Web Browser Interface Session with the Switch
Starting a Web Browser
Interface Session with the Switch
You can start a web browser session in the following ways:
■
■
Using a standalone web browser on a network connection from a PC or
UNIX workstation:
•
Directly connected to your network
•
Connected through remote access to your network
Using a network management station running ProCurve Manager on your
network
Using a Standalone Web Browser in a PC or UNIX
Workstation
This procedure assumes that you are using a compatible web browser and that
the switch is configured with an IP address accessible from your PC or
workstation. (For more on assigning an IP address, refer to “IP Configuration”
on page 8-2.)
1.
Ensure that the JavaTM applets are enabled for your browser. For more
information on this topic, refer to your browser’s online Help.
2.
Use the web browser to access the switch. If your network includes a
Domain Name Server (DNS), your switch’s IP address may have a name
associated with it that you can type in the Location or Address field instead
of the IP address. Using DNS names typically improves browser performance. Contact your network administrator 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 [Enter]. (It is not necessary to include http:/
/.)
5-4
switch6120 [Enter]
(example of a DNS-type name)
10.11.12.195 [Enter]
(example of an IP address)
Using the ProCurve Web Browser Interface
Starting a Web Browser Interface Session with the Switch
Using ProCurve Manager (PCM) or
ProCurve Manager Plus (PCM+)
ProCurve Manager and ProCurve Manager Plus are designed for installation
on a network management workstation. For this reason, the system requirements are different from the system requirements for accessing the switch’s
web browser interface from a non-management PC or workstation. For PCM
and PCM+ requirements, refer to the information provided with the software.
This procedure assumes that:
■
You have installed the recommended web browser on a PC or workstation
that serves as your network management station.
■
The networked device you want to access has been assigned an IP address
and (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-2.)
To establish a web browser session with PCM or PCM+ running, do the
following on the network management station:
Note
1.
Make sure the JavaTM applets are enabled for your web browser. If they
are not, refer to the web browser online Help for specific information on
enabling the Java applets.
2.
In the Interconnected Devices listing under Network Manager Home (in the
PCM/PCM+ sidebar), right-click on the model number of the device you
want to access.
3.
The web browser interface automatically starts with the Status Overview
window displayed for the selected device, as shown in Figure 5-1.
If the Registration window appears, click on the Status tab.
5-5
Using the ProCurve Web Browser Interface
Starting a Web Browser Interface Session with the Switch
First time install
alert
Figure 5-1. Example of Status Overview Screen
5-6
Using the ProCurve Web Browser Interface
Tasks for Your First ProCurve Web Browser Interface Session
Tasks for Your First ProCurve Web
Browser Interface Session
The first time you access the web browser interface, there are three tasks you
should perform:
■
Review the “First Time Install” window
■
Set Manager and Operator passwords
■
Set access to the web browser interface online help
Viewing the “First Time Install” Window
When you access the switch’s web browser interface for the first time, the
Alert log contains a “First Time Install” alert, as shown in figure 5-2. This gives
you information about first time installations, and provides an immediate
opportunity to set passwords for security and to specify a Fault Detection
policy, which determines the types of messages that will be displayed in the
Alert Log.
Double click on First Time Install in the Alert log (figure 5-1 on page 5-6). The
web browser interface then displays the “First Time Install” window, below.
Figure 5-2. First-Time Install Window
5-7
Using the ProCurve Web Browser Interface
Tasks for Your First ProCurve Web Browser Interface Session
This window is the launching point for the basic configuration you need to
perform to set web browser interface passwords for maintaining security and
a fault detection policy, which determines the types of messages that the Alert
Log displays.
To set web browser interface passwords, click on secure access to the device
to display the Device Passwords screen, and then go to the next page. (You
can also access the password screen by clicking on the Security tab.)
To set Fault Detection policy, click on select the fault detection configuration in
the second bullet in the window and go to the section, “Setting Fault Detection
Policy” on page 5-24. (You can also access the password screen by clicking on
the Configuration tab, and then the [Fault Detection] key.)
Security: Creating Usernames and Passwords
in the Browser Interface
Note
On the switches covered in this guide you can also configure RADIUS authentication for web browser interface access. For more information, refer to the
chapter titled “RADIUS Authentication and Accounting” in the Access Security Guide for your switch.
You may want to create both a username and a password to create access
security for your switch. There are two levels of access to the interface that
can be controlled by setting user names and passwords:
5-8
■
Operator Setting. An Operator-level user name and password allows
read-only access to most of the web browser interface, but prevents
access to the Security window.
■
Manager Setting. A Manager-level user name and password allows full
read/write access to the web browser interface.
Using the ProCurve Web Browser Interface
Tasks for Your First ProCurve Web Browser Interface Session
Figure 5-3. The Device Passwords Window
To set the passwords:
1.
2.
Access the Device Passwords screen by one of the following methods:
•
If the Alert Log includes a “First Time Install” event entry, double
click on this event, then, in the resulting display, click on the
secure access to the device link.
•
Select the Security tab.
Click in the appropriate box in the Device Passwords window and enter
user names and passwords. You will be required to repeat the password
strings in the confirmation boxes.
Both the user names and passwords can be up to 16 printable ASCII
characters.
3.
Note
Click on [Apply Changes] to activate the user names and passwords.
Passwords you assign in the web browser interface will overwrite previous
passwords assigned in either the web browser interface, the CLI, or the menu
interface. That is, the most recently assigned passwords are the switch’s
passwords, regardless of which interface was used to assign the string.
5-9
Using the ProCurve Web Browser Interface
Tasks for Your First ProCurve Web Browser Interface Session
Entering a User Name and Password
Figure 5-4. Example of the Password Prompt in the Web Browser Interface
The manager and operator passwords are used to control access to all switch
interfaces. Once set, you will be prompted to supply the password every time
you try to access the switch through any of its interfaces. The password you
enter determines the capability you have during that session:
■
Entering the manager password gives you full read/write/troubleshooting
capabilities
■
Entering the operator password gives you read and limited troubleshooting capabilities.
Using a User Name
If you also set user names in the web browser interface screen, you must
supply the correct user name for web browser interface access. If a user name
has not been set, then leave the User Name field in the password window
blank.
Note that the Command Prompt and switch console interfaces use only the
password, and do not prompt you for the User Name.
If You Lose the Password
If you lose the passwords, you can clear them by pressing the Clear button on
the front of the switch. This action deletes all password and user name
protection from all of the switch’s interfaces.
5-10
Using the ProCurve Web Browser Interface
Tasks for Your First ProCurve Web Browser Interface Session
The Clear button is provided for your convenience, but its presence means
that if you are concerned with the security of the switch configuration and
operation, you should make sure the switch is installed in a secure location,
such as a locked wiring closet. (For more information, refer to “Front Panel
Security” in the chapter titled “Configuring Username and Password Security” in the Access Security Guide for your switch.)
Online Help for the Web Browser Interface
Online Help is available for the web browser interface. You can use it by
clicking on the question mark button in the upper right corner of any of the
web browser interface screens.
The Help Button
Figure 5-5. The Help Button
Context-sensitive help is provided for the screen you are on.
Note
To access the online Help for the ProCurve web browser interface, you need
either ProCurve Manager (version 1.5 or greater) installed on your network
or an active connection to the World Wide Web. Otherwise, Online help for the
web browser interface will not be available.
For more on Help access and operation, refer to “Help and the Management
Server URL” on page 5-13.
5-11
Using the ProCurve Web Browser Interface
Support/Mgmt URLs Feature
Support/Mgmt URLs Feature
The Support/Mgmt URLs window enables you to change the World Wide Web
Universal Resource Locator (URL) for two functions:
■
Support URL – A support information site for your switch
■
Management Server URL – The web site for web browser online Help
1. Click Here
2. Click Here
3. Enter one of the following (or use the default setting):
– 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. (The default setting
accesses the switch’s browser-based Help on the ProCurve World Wide
Web site.) Note that if you install PCM in your network, the PCM
management station acts as the web browser Help server and automatically
inserts the necessary URL in this field.)
Figure 5-6.
5-12
The Default Support/Mgmt URLs Window
4. Click on Apply Changes
Using the ProCurve Web Browser Interface
Support/Mgmt URLs Feature
Support URL
For technical support, go to:
www.hp.com/#Support.
Help and the Management Server URL
The Management Server URL field specifies the URL the switch uses to find
online Help for the web browser interface.
■
If you install PCM (ProCurve Manager) in your network, the PCM management station acts as the web browser Help server for the switch and
automatically inserts the necessary URL in this field. For more on the
option, see “Using the PCM Server for Switch Web Help” on page 5-14.)
■
In the default configuration (and if PCM is not running on your network)
this field is set to the URL for accessing online Help from the ProCurve
Networking web site:
www.hp.com/rnd/device_help
Using this option, the Help files are automatically available if your workstation can access the World Wide Web. In this case, if Online Help fails
to operate, ensure that the above URL appears in the Management Server
URL field shown in Figure 5-7:
In the default configuration, the switch uses the URL for
accessing the web browser interface help files on the
Figure 5-7. How To Access Web Browser Interface Online Help
5-13
Using the ProCurve Web Browser Interface
Support/Mgmt URLs Feature
Using the PCM Server for Switch Web Help
For ProCurve devices that support the “Web Help” feature, you can use the
PCM server to host the switch help files for devices that do not have HTTP
access to the ProCurve Support Web site.
1.
Go to the ProCurve Support web site to get the Device Help files:
www.hp.com//rnd/device_help/
2.
Copy the Web help files to the PCM server, under:
C:\\program files\hewlett-packard\pnm\server\webroot\
rnd\sevice_help\help\hpwnd\webhelp
5-14
Using the ProCurve Web Browser Interface
Support/Mgmt URLs Feature
3.
Add an entry, or edit the existing entry in the Discovery portion of the
global properties (globalprops.prp) in PCM to redirect the switches to the
help files on the PCM server. For example:
Global {
TempDir=data/temp
...
Discovery{
...
...
DeviceHelpUrlRedirect=http://15.29.37.12.8040/rnd/device_help
...
}
}
You will enter the IP address for your PCM server. 8040 is the standard port
number to use.
4.
Note
Restart the Discovery process for the change to be applied.
Changing the Discovery’s Global properties file will redirect the Device Help
URL for all devices.
If you just want to change the Device Help URL for a particular device, then
go to the Configuration tab on the Web UI for that device and select the
“Support/Mgmt URL” button. Edit the entry in the “Management Server URL”
field for the device to point to the PCM server; for example:
http://15.29.37.12.8040/rnd/device_help
5-15
Using the ProCurve Web Browser Interface
Status Reporting Features
Status Reporting Features
Browser elements covered in this section include:
■
The Overview window (below)
■
Port utilization and status (page 5-17)
■
The Alert log (page 5-20)
■
The Status bar (page 5-22)
The Overview Window
The Overview Window is the home screen for any entry into the web browser
interface.The following figure identifies the various parts of the screen.
Status Bar
(page 5-22)
Active Button
Tab Bar
Button Bar
Port Utilization Graphs
(page 5-17)
Port Status
Indicators
(page 5-19)
Alert Log
Control Bar
Alert Log
(page 5-20)
Figure 5-8. The Status Overview Window
5-16
Active Tab
Using the ProCurve Web Browser Interface
Status Reporting Features
Policy Management and Configuration. PCM can perform network-wide
policy management and configuration of your switch. The Management Server
URL field (page 5-13) shows the URL for the management station performing
that function. For more information, refer to the documentation provided with
the PCM software.
The Port Utilization and Status Displays
The Port Utilization and Status displays show an overview of the status of the
switch and the amount of network activity on each port. The following figure
shows a sample reading of the Port Utilization and Port Status.
Port Utilization Bar Graphs
Bandwidth Display Control
Port Status Indicators
Legend
Figure 5-9. The Graphs Area
Port Utilization
The Port Utilization bar graphs show the network traffic on the port with a
breakdown of the packet types that have been detected (unicast packets, nonunicast packets, and error packets). The Legend identifies traffic types and
their associated colors on the bar graph:
■
% Unicast Rx & All Tx: This is all unicast traffic received and all
transmitted traffic of any type. This indicator (a blue color on many
systems) can signify either transmitted or received traffic.
■
% Non-Unicast Pkts Rx: All multicast and broadcast traffic received by
the port. This indicator (a gold color on many systems) enables you to
know “at-a-glance” the source of any non-unicast traffic that is causing
high utilization of the switch. For example, if one port is receiving heavy
broadcast or multicast traffic, all ports will become highly utilized. By
color-coding the received broadcast and multicast utilization, the bar
graph quickly and easily identifies the offending port. This makes it faster
and easier to discover the exact source of the heavy traffic because you
don’t have to examine port counter data from several ports.
5-17
Using the ProCurve 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.
■
Maximum Activity Indicator: As the bars in the graph area change
height to reflect the level of network activity on the corresponding port,
they leave an outline to identify the maximum activity level that has been
observed on the port.
Utilization Guideline. A network utilization of 40% is considered the
maximum that a typical Ethernet-type network can experience before encountering performance difficulties. If you observe utilization that is consistently
higher than 40% on any port, click on the Port Counters button to get a detailed
set of counters for the port.
To change the amount of bandwidth the Port Utilization bar graph
shows. Click on the bandwidth display control button in the upper left corner
of the graph. (The button shows the current scale setting, such as 40%.) In the
resulting menu, select the bandwidth scale you want the graph to show (3%,
10%, 25%, 40%, 75%, or 100%), as shown in figure figure 5-10.
Note that when viewing activity on a gigabit port, you may want to select a
lower value (such as 3% or 10%). This is because the bandwidth utilization of
current network applications on gigabit links is typically minimal, and may
not appear on the graph if the scale is set to show high bandwidth utilization.
Figure 5-10. Changing the Graph Area Scale
To display values for each graph bar. Hold the mouse cursor over any of
the bars in the graph, and a pop-up display is activated showing the port
identification and numerical values for each of the sections of the bar, as
shown in figure 5-11 (next).
5-18
Using the ProCurve Web Browser Interface
Status Reporting Features
Figure 5-11. Display of Numerical Values for the Bar
Port Status
Port Status Indicators
Legend
Figure 5-12. The Port Status Indicators and Legend
The Port Status indicators show a symbol for each port that indicates the
general status of the port. There are four possible statuses:
■
Port Connected – the port is enabled and is properly connected to an
active network device.
■
Port Not Connected – the port is enabled but is not connected to an
active network device. A cable may not be connected to the port, or the
device at the other end may be powered off or inoperable, or the cable or
connected device could be faulty.
■
Port Disabled – the port has been configured as disabled through the
web browser interface, the switch console, or SNMP network management.
■
Port Fault-Disabled – a fault condition has occurred on the port that
has caused it to be auto-disabled. Note that the Port Fault-Disabled
symbol will be displayed in the legend only if one or more of the ports is
in that status. See Appendix B, “Monitoring and Analyzing Switch Operation” for more information.
5-19
Using the ProCurve 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. A
full list of alerts is shown in the table on page 5-21.
Figure 5-13. Example of the Alert Log
Each alert has the following fields of information:
■
Status – The level of severity of the event generated. Severity levels can
be Information, Normal, Warning, and Critical. If the alert is new (has not
yet been acknowledged), the New symbol is also in the Status column.
■
Alert – The specific event identification.
■
Date/Time – The date and time the event was received by the web
browser interface. This value is shown in the format: DD-MM-YY
HH:MM:SS AM/PM, for example, 16-Sep-08 7:58:44 AM.
■
Description – A short narrative statement that describes the event. For
example, Excessive CRC/Alignment errors on port: 8.
Sorting the Alert Log Entries
The alerts are sorted, by default, by the Date/Time field with the most recent
alert listed at the top of the list. The second most recent alert is displayed
below the top alert and so on. If alerts occurred at the same time, the
simultaneous alerts are sorted by order in which they appear in the MIB.
Bold characters in a column heading indicate that the alert field alert log
entries. You can sort by any of the other columns by clicking on the column
heading. The Alert and Description columns are sorted alphabetically, while the
Status column is sorted by severity type, with more critical severity indicators
appearing above less critical indicators.
5-20
Using the ProCurve Web Browser Interface
Status Reporting Features
Alert Types and Detailed Views
As of June, 2007, the web browser interface generates the following alert
types:
•
•
•
•
•
•
•
•
•
Note
Auto Partition
Backup Transition
Excessive broadcasts
Excessive CRC/alignment errors
Excessive jabbering
Excessive late collisions
First Time Install
Full-Duplex Mismatch
Half-Duplex Mismatch
•
•
•
•
•
•
•
•
High collision or drop rate
Loss of Link
Mis-Configured SQE
Network Loop
Polarity Reversal
Security Violation
Stuck 10BaseT Port
Too many undersized (runt)/giant
packets
• Transceiver Hot Swap
When troubleshooting the sources of alerts, it may be helpful to check the
switch’s Port Status and Port Counter windows, or use the CLI or menu
interface to view the switch’s Event Log.
When you double click on an Alert Entry, the web browser interface displays
a separate window showing information about the event. This view includes
a description of the problem and a possible solution. It also provides three
management buttons:
■
Acknowledge Event – removes the New symbol from the log entry
■
Delete Event – removes the alert from the Alert Log
■
Cancel – closes the detail view with no change to the status of the alert
and returns you to the Overview screen.
For example, figure 5-14 shows a sample detail view describing an Excessive
CRC/Alignment Error alert.
5-21
Using the ProCurve Web Browser Interface
Status Reporting Features
Figure 5-14. Example of Alert Log Detail View
The Status Bar
The Status Bar appears in the upper left corner of the web browser interface
window. Figure 5-15 shows an expanded view of the status bar.
Status Indicator
Most Critical Alert Description
Product Name
Figure 5-15. Example of the Status Bar
5-22
Using the ProCurve Web Browser Interface
Status Reporting Features
The Status bar includes four objects:
■
Status Indicator. Indicates, by icon, the severity of the most critical alert
in the current display of the Alert Log. This indicator can be one of four
shapes and colors, as shown below.
Table 5-1. Status Indicator Key
Color
Blue
Green
Switch Status
Normal Activity; “First time
installation” information available in
the Alert log.
Normal Activity
Yellow
Warning
Red
Critical
Status Indicator Shape
■
System Name. The name you can configure for the switch by using the
System Info window (under the Configuration tab), the hostname < asciistring > command in the CLI, or the System Name field in the "System
Information" screen in the System Info screen of the menu interface.
■
Most Critical Alert Description. A brief description of the earliest,
unacknowledged alert with the current highest severity in the Alert Log,
appearing in the right portion of the Status Bar. In instances where
multiple critical alerts have the same severity level, only the earliest
unacknowledged alert is deployed in the Status bar.
■
Product Name. The product name of the switch to which you are
connected in the current web browser interface session.
5-23
Using the ProCurve Web Browser Interface
Status Reporting Features
Setting Fault Detection Policy
One of the powerful features in the web browser interface is the Fault
Detection facility. For your switch, this feature controls the types of alerts
reported to the Alert Log based on their level of severity.
Set this policy in the Fault Detection window (figure 5-16).
Figure 5-16. The Fault Detection Window
The Fault Detection screen contains a list box for setting fault detection and
response policy, and enables you to set the sensitivity level at which a network
problem should generate an alert and send it to the Alert Log.
5-24
Using the ProCurve Web Browser Interface
Status Reporting Features
To provide the most information on network problems in the Alert Log, the
recommended sensitivity level for Log Network Problems is High Sensitivity. The
Fault Detection settings are:
■
High Sensitivity. This policy directs the switch to send all alerts to the
Alert Log. This setting is most effective on networks that have none or
few problems.
■
Medium Sensitivity. This policy directs the switch to send alerts related
to network problems to the Alert Log. If you want to be notified of
problems which cause a noticeable slowdown on the network, use this
setting.
■
Low Sensitivity. This policy directs the switch to send only the most
severe alerts to the Alert Log. This policy is most effective on a network
where there are normally a lot of problems and you want to be informed
of only the most severe ones.
■
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:
■
Apply Changes. This button stores the settings you have selected for all
future sessions with the web browser interface until you decide to change
them.
■
Clear Changes. This button removes your settings and returns the
settings for the list box to the level it was at in the last saved detectionsetting session.
■
Reset to Default Settings. This button reverts the policy setting to
Medium Sensitivity for Log Network Problems.
5-25
6
Switch Memory and Configuration
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Using the CLI To Implement Configuration Changes . . . . . . . . . . . . 6-6
Using the Menu and Web Browser Interfaces To Implement
Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Menu: Implementing Configuration Changes . . . . . . . . . . . . . . . . . . . 6-10
Using Save and Cancel in the Menu Interface . . . . . . . . . . . . . . . 6-10
Rebooting from the Menu Interface . . . . . . . . . . . . . . . . . . . . . . . 6-11
Web: Implementing Configuration Changes . . . . . . . . . . . . . . . . . . . . 6-13
Using Primary and Secondary Flash Image Options . . . . . . . . . . . . . 6-14
Displaying the Current Flash Image Data . . . . . . . . . . . . . . . . . . . . . . 6-14
Switch Software Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Local Switch Software Replacement and Removal . . . . . . . . . . . . . . 6-17
Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Operating Notes about Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Boot and Reload Command Comparison . . . . . . . . . . . . . . . . . . . 6-20
Setting the Default Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Booting from the Default Flash (Primary or Secondary) . . . . . . 6-22
Booting from a Specified Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Using Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Multiple Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Transitioning to Multiple Configuration Files . . . . . . . . . . . . . . . . . . . 6-28
Listing and Displaying Startup-Config Files . . . . . . . . . . . . . . . . . . . . . 6-29
Viewing the Startup-Config File Status with Multiple
Configuration Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Displaying the Content of A Specific Startup-Config File . . . . . . 6-30
6-1
Switch Memory and Configuration
Contents
Changing or Overriding the Reboot Configuration Policy . . . . . . . . . 6-30
Managing Startup-Config Files in the Switch . . . . . . . . . . . . . . . . . . . 6-32
Renaming an Existing Startup-Config File . . . . . . . . . . . . . . . . . . 6-33
Creating a New Startup-Config File . . . . . . . . . . . . . . . . . . . . . . . . 6-33
Erasing a Startup-Config File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Using the Clear + Reset Button Combination To Reset the
Switch to Its Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . 6-37
Transferring Startup-Config Files To or From a Remote Server . . . . 6-37
TFTP: Copying a Configuration File to a Remote Host . . . . . . . . 6-38
TFTP: Copying a Configuration File from a Remote Host . . . . . 6-39
Xmodem: Copying a Configuration File to a Serially
Connected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
Xmodem: Copying a Configuration from a Serially
Connected Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
Operating Notes for Multiple Configuration Files . . . . . . . . . . . . 6-41
Automatic Configuration Update with DHCP Option 66 . . . . . . . . 6-41
CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Possible Scenarios for Updating the Configuration File . . . . . . . . . . 6-42
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
6-2
Switch Memory and Configuration
Overview
Overview
This chapter describes:
■
How switch memory manages configuration changes
■
How the CLI implements configuration changes
■
How the menu interface and web browser interface implement configuration changes
■
How the switch provides software options through primary/secondary
flash images
■
How to use the switch’s primary and secondary flash options, including
displaying flash information, booting or restarting the switch, and other
topics
Configuration File Management
The switch maintains two configuration files, the running-config file and the
startup-config file.
Volatile Memory
Running-Config File
(Controls switch operation. When the switch boots, the
contents of this file are erased and replaced by the
contents of the startup-config file.)
Flash (Non-Volatile) Memory
Startup-Config File
(Preserves the most recently saved configuration
through any subsequent reboot.)
Figure 6-1.
■
CLI configuration
changes are written to
this file. To use the CLI to
save the latest version of
this file to the startupconfig file, you must
execute the write
memory command.
Menu interface configuration changes are simultaneously written to both
of these files.
Conceptual Illustration of Switch Memory Operation
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.
6-3
Switch Memory and Configuration
Configuration File Management
■
Startup-config File: Exists in flash (non-volatile) memory and is used
to preserve the most recently-saved configuration as the “permanent”
configuration.
Booting the switch replaces the current running-config file with a new running-config file that is an exact copy of the current startup-config file.
Note
Any of the following actions boots the switch:
•
Executing the boot or the reload command in the CLI
•
Executing the boot command in the menu interface
•
Pressing the Reset button on the front of the switch
•
Removing, then restoring power to the switch
•
Power-cycling or resetting via the OA
For more on reboots and the switch’s dual-flash images, refer to “Using
Primary and Secondary Flash Image Options” on page 6-14.
Options for Saving a New Configuration. Making one or more changes
to the running-config file creates a new operating configuration. Saving a new
configuration means to overwrite (replace) the current startup-config file with
the current running-config file. This means that if the switch subsequently
reboots for any reason, it will resume operation using the new configuration
instead of the configuration previously defined in the startup-config file. There
are three ways to save a new configuration:
■
In the CLI: Use the write memory command. This overwrites the current
startup-config file with the contents of the current running-config file.
■
In the menu interface: Use the Save command. This overwrites both the
running-config file and the startup-config file with the changes you have
specified in the menu interface screen.
■
In the web browser interface: Use the [Apply Changes] button or other
appropriate button. This overwrites both the running-config file and the
startup-config file with the changes you have specified in the web browser
interface window.
Note that using the CLI instead of the menu or web browser interface gives
you the option of changing the running configuration without affecting the
startup configuration. This allows you to test the change without making it
“permanent”. When you are satisfied that the change is satisfactory, you can
make it permanent by executing the write memory command. For example,
suppose you use the following command to disable port 5:
ProCurve(config)# interface ethernet 5 disable
6-4
Switch Memory and Configuration
Configuration File Management
The above command disables port 5 in the running-config file, but not in the
startup-config file. Port 5 remains disabled only until the switch reboots. If
you want port 5 to remain disabled through the next reboot, use write memory
to save the current running-config file to the startup-config file in flash
memory.
ProCurve(config)# write memory
If you use the CLI to make a configuration change and then change from the
CLI to the Menu interface without first using write memory to save the change
to the startup-config file, then the switch prompts you to save the change. For
example, if you use the CLI to create VLAN 20, and then select the menu
interface, VLAN 20 is configured in the running-config file, but not in the
startup-config file. In this case you will see:
ProCurve(config)# vlan 20
ProCurve(config)# menu
Do you want to save current configuration [y/n]?
If you type [Y], the switch overwrites the startup-config file with the runningconfig file, and your configuration change(s) will be preserved across reboots.
If you type [N], your configuration change(s) will remain only in the runningconfig file. In this case, if you do not subsequently save the running-config file,
your unsaved configuration changes will be lost if the switch reboots for any
reason.
Storing and Retrieving Configuration Files. You can store or retrieve a
backup copy of the startup-config file on another device. For more
information, refer to the section on “Transferring Switch Configurations” on
page A-26 in Appendix A on “File Transfers”.
6-5
Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
Using the CLI To Implement
Configuration Changes
The CLI offers these capabilities:
■
Access to the full set of switch configuration features
■
The option of testing configuration changes before making them permanent
How To Use the CLI To View the Current Configuration Files. Use
show commands to view the configuration for individual features, such as port
status or Spanning Tree Protocol. However, to view either the entire startupconfig file or the entire running-config file, use the following commands:
Note
■
show config — Displays a listing of the current startup-config file.
■
show running-config — Displays a listing of the current running-config file.
■
write terminal — Displays a listing of the current running-config file.
■
show config status — Compares the startup-config file to the runningconfig file and lists one of the following results:
•
If the two configurations are the same you will see:
– Running configuration is the same as the startup
configuration.
•
If the two configurations are different, you will see:
– Running configuration has been changed and needs
to be saved.
Show config, show running-config, and write terminal commands display the
configuration settings that differ from the switch’s factory-default configuration.
How To Use the CLI To Reconfigure Switch Features. Use this procedure to permanently change the switch configuration (that is, to enter a change
in the startup-config file).
6-6
1.
Use the appropriate CLI commands to reconfigure the desired switch
parameters. This updates the selected parameters in the running-config
file.
2.
Use the appropriate show commands to verify that you have correctly
made the desired changes.
Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
3.
Observe the switch’s performance with the new parameter settings to
verify the effect of your changes.
4.
When you are satisfied that you have the correct parameter settings, use
the write memory command to copy the changes to the startup-config file.
Syntax:
write memory
Saves the running configuration file to the startup-config.
The saved configuration becomes the boot-up configuration
of the switch on the next boot.
When using redundant management, saves the running
configuration of the switch to flash on the active management
module. The saved configuration becomes the boot-up
configuration of the switch the next time it is booted. The
saved configuration file is sync’d to the standby management
module.
Note: If the active management module and the standby
management module are running on different operating
systems because the boot set-default command was executed
and then the standby module was rebooted, the write memory
command displays this warning: “Warning: The next reboot
or failover is set to boot from a different software image. These
config changes may be incompatible or not used after a reboot
or failover.”
For example, the default port mode setting is auto. Suppose that your network
uses Cat 3 wiring and you want to connect the switch to another autosensing
device capable of 100 Mbps operation. Because 100 Mbps over Cat 3 wiring
can introduce transmission problems, the recommended port mode is auto-10,
which allows the port to negotiate full- or half-duplex, but restricts speed to
10 Mbps. The following command configures port A5 to auto-10 mode in the
running-config file, allowing you to observe performance on the link without
making the mode change permanent.
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
executing the following command:
ProCurve(config)# write memory
The new mode (auto-10) on port A5 is now saved in the startup-config file, and
the startup-config and running-config files are identical. If you subsequently
reboot the switch, the auto-10 mode configuration on port A5 will remain
because it is included in the startup-config file.
6-7
Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
How To Cancel Changes You Have Made to the Running-Config File.
If you use the CLI to change parameter settings in the running-config file, and
then decide that you don’t want those changes to remain, you can use either
of the following methods to remove them:
■
Manually enter the earlier values you had for the changed settings. (This
is recommended if you want to restore a small number of parameter
settings to their previous boot-up values.)
■
Update the running-config file to match the startup-config file by rebooting the switch. (This is recommended if you want to restore a larger
number of parameter settings to their previous boot-up values.)
If you use the CLI to change a parameter setting, and then execute the boot
command without first executing the write memory command to save the
change, the switch prompts you to specify whether to save the changes in the
current running-config file. For example:
Disables port 1 in the running configuration, which causes port 1 to block all traffic.
ProCurve(config)# interface e 1 disable
ProCurve(config)# boot
Device will be rebooted, do you want to continue [y/n]? y
Press [Y] to continue the rebooting process.
You will then see this prompt.
Do you want to save current configuration [y/n]?
Figure 6-2. Boot Prompt for an Unsaved Configuration
The above prompt means that one or more parameter settings in the runningconfig file differ from their counterparts in the startup-config file and you need
to choose which config file to retain and which to discard.
6-8
■
If you want to update the startup-config file to match the running-config
file, press [Y] for “yes”. (This means that the changes you entered in the
running-config file will be saved in the startup-config file.)
■
If you want to discard the changes you made to the running-config file so
that it will match the startup-config file, then press [N] for “no”. (This
means that the switch will discard the changes you entered in the runningconfig file and will update the running-config file to match the startupconfig file.)
Switch Memory and Configuration
Using the CLI To Implement Configuration Changes
Note
If you use the CLI to make a change to the running-config file, you should
either use the write memory command or select the save option allowed during
a reboot (figure 6-6-2, above) to save the change to the startup-config file. That
is, if you use the CLI to change a parameter setting, but then reboot the switch
from either the CLI or the menu interface without first executing the write
memory command in the CLI, the current startup-config file will replace the
running-config file, and any changes in the running-config file will be lost.
Using the Save command in the menu interface does not save a change made
to the running config by the CLI unless you have also made a configuration
change in the menu interface. Also, the menu interface displays the current
running-config values. Thus, where a parameter setting is accessible from both
the CLI and the menu interface, if you change the setting in the CLI, the new
value will appear in the menu interface display for that parameter. However,
as indicated above, unless you also make a configuration change in the
menu interface, only the write memory command in the CLI will actually save
the change to the startup-config file.
How To Reset the startup-config and running-config Files to the
Factory Default Configuration. This command reboots the switch,
replacing the contents of the current startup-config and running-config files
with the factory-default startup configuration.
Syntax:
erase startup-config
For example:
ProCurve(config)# erase startup-config
Configuration will be deleted and device rebooted, continue [y/n]?
Figure 6-3. Example of erase startup-config Command
Press [y] to replace the current configuration with the factory default configuration and reboot the switch. Press [n] to retain the current configuration and
prevent a reboot.
6-9
Switch Memory and Configuration
Using the Menu and Web Browser Interfaces To Implement Configuration Changes
Using the Menu and Web Browser
Interfaces To Implement Configuration
Changes
The menu and web browser interfaces offer these advantages:
■
Quick, easy menu or window access to a subset of switch configuration
features
■
Viewing several related configuration parameters in the same screen, with
their default and current settings
■
Immediately changing both the running-config file and the startup-config
file with a single command
Menu: Implementing Configuration Changes
You can use the menu interface to simultaneously save and implement a subset
of switch configuration changes without having to reboot the switch. That is,
when you save a configuration change in the menu interface, you simultaneously change both the running-config file and the startup-config file.
Note
The only exception to this operation are two VLAN-related parameter changes
that require a reboot—described under “Rebooting To Activate Configuration
Changes” on page 6-12.
Using Save and Cancel in the Menu Interface
For any configuration screen in the menu interface, the Save command:
1.
Implements the changes in the running-config file
2.
Saves your changes to the startup-config file
If you decide not to save and implement the changes in the screen, select
Cancel to discard them and continue switch operation with the current operation. For example, suppose you have made the changes shown below in the
System Information screen:
6-10
Switch Memory and Configuration
Using the Menu and Web Browser Interfaces To Implement Configuration Changes
To save and
implement the
changes for all
parameters in this
screen, press the
[Enter] key, then
press [S] (for Save).
To cancel all
changes, press the
[Enter] key, then
press [C] (for Cancel)
Figure 6-4.
Note
Example of Pending Configuration Changes You Can Save or Cancel
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 (even if you execute a Save operation in the menu
interface). If you then execute a switch boot command in the menu interface,
the switch discards the configuration changes made while using the CLI. To
ensure that changes made while using the CLI are saved, execute write memory
in the CLI before rebooting the switch.
Rebooting from the Menu Interface
■
Terminates the current session and performs a reset of the operating
system
■
Activates any configuration changes that require a reboot
■
Resets statistical counters to zero
(Note that statistical counters can be reset to zero without rebooting the
switch. See “To Display the Port Counter Summary Report” on page 13.)
To Reboot the switch, use the Reboot Switch option in the Main Menu. (Note
that the Reboot Switch option is not available if you log on in Operator mode;
that is, if you enter an Operator password instead of a manager password at
the password prompt.)
6-11
Switch Memory and Configuration
Using the Menu and Web Browser Interfaces To Implement Configuration Changes
Optional Reboot
Switch Command
Figure 6-5.
The Reboot Switch Option in the Main Menu
Rebooting To Activate Configuration Changes. Configuration changes
for most parameters become effective as soon as you save them. However,
you must reboot the switch in order to implement a change in the Maximum
VLANs to support parameter.
(To access these parameters, go to the Main menu and select 2. Switch
Configuration, then 8. VLAN Menu, then 1. VLAN Support.)
If configuration changes requiring a reboot have been made, the switch
displays an asterisk (*) next to the menu item in which the change has been
made. For example, if you change and save parameter values for the Maximum
VLANs to support parameter, an asterisk appears next to the VLAN Support entry in
the VLAN Menu screen, and also next to the Switch Configuration …entry in the
Main menu, as shown in Figure 6-6:
6-12
Switch Memory and Configuration
Using the Menu and Web Browser Interfaces To Implement Configuration Changes
Asterisk indicates
a configuration
change that
requires a reboot
in order to take
effect.
Reminder to
reboot the switch
to activate
configuration
changes.
Figure 6-6.
Indication of a Configuration Change Requiring a Reboot
Web: Implementing Configuration Changes
You can use the web browser interface to simultaneously save and implement
a subset of switch configuration changes without having to reboot the switch.
That is, when you save a configuration change (in most cases, by clicking on
[Apply Changes] or [Apply Settings], you simultaneously change both the runningconfig file and the startup-config file.
Note
If you reconfigure a parameter in the CLI and then go to the browser interface
without executing a write memory command, those changes will be saved to
the startup-config file if you click on [Apply Changes] or [Apply Settings] in the web
browser interface.
6-13
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Using Primary and Secondary Flash
Image Options
The switches covered in this guide feature two flash memory locations for
storing switch software image files:
■
Primary Flash: The default storage for a switch software image.
■
Secondary Flash: The additional storage for either a redundant or an
alternate switch software image.
With the Primary/Secondary flash option you can test a new image in your
system without having to replace a previously existing image. You can also
use the image options for troubleshooting. For example, you can copy a
problem image into Secondary flash for later analysis and place another,
proven image in Primary flash to run your system. The switch can use only
one image at a time.
The following tasks involve primary/secondary flash options:
■
Displaying the current flash image data and determining which switch
software versions are available
■
Switch software downloads
■
Replacing and removing (erasing) a local switch software version
■
System booting
Displaying the Current Flash Image Data
Use the commands in this section to:
■
Determine whether there are flash images in both primary and secondary
flash
■
Determine whether the images in primary and secondary flash are the
same
■
Identify which switch software version is currently running
Viewing the Currently Active Flash Image Version. This command
identifies the software version on which the switch is currently running, and
whether the active version was booted from the primary or secondary flash
image.
Syntax:show version
6-14
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
For example, if the switch is using a software version of K.12.XX stored in
Primary flash, show version produces the following:
ProCurve(config)# show version
Image stamp:
/sw/code/build/vern(t4br)
Jul 27 2009 13:42:40
Z.14.04
1037
Boot Image:
Primary
Build Options:
QA
Watchdog:
ENABLED
Figure 6-7.
Example Showing the Identity of the Current Flash Image
Determining Whether the Flash Images Are Different Versions. If the
flash image sizes in primary and secondary are the same, then in almost every
case, the primary and secondary images are identical. This command provides
a comparison of flash image sizes, plus the boot ROM version and from which
flash image the switch booted. For example, in the following case, the images
are different versions of the switch software, and the switch is running on the
version stored in the secondary flash image:
ProCurve(config)# show flash
Image
Size(Bytes)
Date
-------------- -------Primary Image
: 7173079
07/27/09
Secondary Image : 7173079
07/27/09
Boot Rom Version: Z.14.03
Default Boot
: Primary
Version
------Z.14.04
Z.14.04
Will boot from primary flash
on the next boot.
Figure 6-8.
Example Showing Different Flash Image Versions
Determining Which Flash Image Versions Are Installed. The show version command displays which software version the switch is currently running
and whether that version booted from primary or secondary flash. Thus, if the
switch booted from primary flash, you will see the version number of the
software version stored in primary flash, and if the switch booted from
secondary flash, you will see the version number of the software version
stored in secondary flash. Thus, by using show version, then rebooting the
6-15
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
switch from the opposite flash image and using show version again, you can
determine the version(s) of switch software in both flash sources. For example:
1. In this example show
version indicates the
switch has version Z.14.04
in primary flash.
ProCurve(config)# show version
Image stamp:
Boot Image:
2. After the boot system
command, show version
indicates that version
Z.14.04 is in secondary
flash.
ProCurve(config)# boot system flash secondary
Device will be rebooted, do you want to continue [y/n]? y
ProCurve(config)# show version
Image stamp:
Boot Image:
Figure 6-9.
/sw/code/build/vern(t4br)
Jul 27 2009 13:42:40
Z.14.04
1037
Primary
/sw/code/build/vern(t4br)
Jul 27 2009 13:42:40
Z.14.04
1037
Secondary
Determining the Software Version in Primary and Secondary Flash
Switch Software Downloads
The following table shows the switch’s options for downloading a software
version to flash and booting the switch from flash
Table 6-1.
Primary/Secondary Memory Access
Action
Download to Primary
Download to Secondary
Menu
Yes
No
CLI
Yes
Yes
Web
Browser
Yes
Yes
SNMP
Yes
a
Yes
Boot from Primary
Yes
Yes
Yes
Yes
Boot from Secondary
No
Yes
No
Yes
a.This download simply reloads the image.
The different software download options involve different copy commands,
plus xmodem, usb, and tftp. These topics are covered in Appendix A, “File
Transfers”.
6-16
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Note
xmodem should not be used over the OA serial console. It should only be used
over the USB serial console connection.
Download Interruptions. In most cases, if a power failure or other cause
interrupts a flash image download, the switch reboots with the image previously stored in primary flash. In the unlikely event that the primary image is
corrupted, as a result of an interruption, the switch will reboot from secondary
flash and you can either copy the secondary image into primary or download
another image to primary from an external source. Refer to Appendix A, “File
Transfers”.
Local Switch Software Replacement and Removal
This section describes commands for erasing a software version and copying
an existing software version between primary and secondary flash.
Note
It is not necessary to erase the content of a flash location before downloading
another software file. The process automatically overwrites the previous file
with the new file. 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. To copy a software file between the primary and
secondary flash locations, refer to “Copying a Switch Software Image from
One Flash Location to Another”, below.
The local commands described here are for flash image management within
the switch. To download a software image file from an external source, refer
to Appendix A, “File Transfers”.
Copying a Switch Software Image from One Flash Location to
Another. When you copy the flash image from primary to secondary or the
reverse, the switch overwrites the file in the destination location with a copy
of the file from the source location. This means you do not have to erase the
current image at the destination location before copying in a new image.
Caution
Verify that there is an acceptable software version in the source flash location
from which you are going to copy. Use the show flash command or, if necessary,
the procedure under “Determining Which Flash Image Versions Are Installed”
on page 6-15 to verify an acceptable software version. Attempting to copy from
a source image location that has a corrupted flash image overwrites the image
in the destination flash location. In this case, the switch will not have a valid
flash image in either flash location, but will continue running on a temporary
6-17
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
flash image in RAM. Do not reboot the switch. Instead, immediately download
another valid flash image to primary or secondary flash. Otherwise, if the
switch is rebooted without a software image in either primary or secondary
flash, the temporary flash image in RAM will be cleared and the switch will go
down. To recover, refer to “Restoring a Flash Image” on page C-77 (in the
“Troubleshooting” Appendix).
Syntax:
copy flash flash <destination flash>
where: destination flash = primary or secondary:
For example, to copy the image in secondary flash to primary flash:
1.
Verify that there is a valid flash image in the secondary flash location. The
following figure indicates that a software image is present in secondary
flash. (If you are unsure whether the image is secondary flash is valid, try
booting from it before you proceed, by using boot system flash secondary.)
ProCurve(config)# show flash
Image
Size(Bytes)
Date
-------------- -------Primary Image
: 7184180
07/26/09
Secondary Image : 7173079
07/27/09
Boot Rom Version: Z.14.03
Default Boot
: Primary
Version
------Z.14.03
Z.14.04
The unequal code
size, differing dates,
and differing
version numbers
indicates two
different versions of
the software.
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.
Caution:
No Undo!
6-18
Before using this command in one flash image location (primary or secondary), ensure that you have a valid software file in the other flash image location
(secondary or primary). If the switch has only one flash image loaded (in either
primary or secondary flash) and you erase that image, then the switch does
not have a software image stored in flash. In this case, if you do not reboot or
power cycle the switch, you can recover by using xmodem or tftp to download
another software image.
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Syntax:
erase flash < primary | secondary >
For example, to erase the software image in primary flash, do the following:
1.
First verify that a usable flash image exists in secondary flash. The most
reliable way to ensure this is to reboot the switch from the flash image
you want to retain. For example, if you are planning to erase the primary
image, then first reboot from the secondary image to verify that the
secondary image is present and acceptable for your system:
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.
Figure 6-11. Example of Erase Flash Prompt
3.
Type y at the prompt to complete the flash erase.
4.
Use show flash to verify erasure of the selected software flash image
The “0” here
shows that
primary flash has
been erased.
Figure 6-12. Example of Show Flash Listing After Erasing Primary Flash
Rebooting the Switch
Operating Notes about Booting
Default Boot Source. The switch reboots from primary flash by default
unless you specify the secondary flash by entering either the boot system flash
[primary | secondary] or boot set-default flash [primary | secondary] command.
Both the boot command and the reload command will reboot based on how
these options have been selected.
Boot Attempts from an Empty Flash Location. In this case, the switch
aborts the attempt and displays
6-19
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Image does not exist
Operation aborted.
Interaction of Primary and Secondary Flash Images with the Current
Configuration. The switch has one startup-config file (page 6-3), which it
always uses for reboots, regardless of whether the reboot is from primary or
secondary flash. Also, for rebooting purposes, it is not necessary for the
software image and the startup-config file to support identical software features. For example, suppose you have just downloaded a software upgrade
that includes new features that are not supported in the software you used to
create the current startup-config file. In this case, the software simply assigns
factory-default values to the parameters controlling the new features. Similarly, If you create a startup-config file while using a version “Y” of the switch
software, and then reboot the switch with an earlier software version “X” that
does not include all of the features found in “Y”, the software simply ignores
the parameters for any features that it does not support.
Scheduled Reload. If no parameters are entered after the reload command,
an immediate reboot is executed. The reload at and reload after command
information is not saved across reboots. If the switch is rebooted before a
scheduled reload command is executed, the command is effectively cancelled.
When entering a reload at or reload after command, a prompt will appear to
confirm the command before it can be processed by the switch. For the reload
at command, if mm/dd/yy are left blank, the current day is assumed.
The scheduled reload feature removes the requirement to physically reboot
the switch at inconvenient times (for example, at 1:00 in the morning). Instead,
a reload at 1:00 mm/dd command can be executed (where mm/dd is the date
the switch is scheduled to reboot).
Boot and Reload Command Comparison
The switch offers reboot options through the boot and reload commands, plus
the options inherent in a dual-flash image system. Generally, using boot
provides more comprehensive self-testing; using reload gives you a faster
reboot time.
6-20
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Table 6-2.
Comparing the Boot and Reload Commands
Actions
Included In
Boot?
Included In Reload
Note
Save all
configuration
changes since the
last boot or reload
Optional,
with prompt
Optional with reload
<cr>, when prompt
displays.
Not saved with reload
at/after commands;
No prompt is displayed.
Config changes saved to
the startup-config file if
“y” is selected (reload
command).
Perform all system
self-tests
Yes
No
The reload command
Choice of primary or
secondary flash
image
Yes
No—Uses the current
flash image.
Perform a scheduled
reboot
No
Yes
provides a faster system
reboot.
Use the reload command
with after/at parameters
(see page 6-24 for details).
Setting the Default Flash
You can specify the default flash to boot from on the next boot by entering the
boot set-default flash command.
Syntax:
boot set-default flash [primary |secondary]
Upon booting, set the default flash for the next boot to primary
or secondary.
ProCurve(config)# boot set-default flash secondary
ProCurve(config)# show flash
Image
Size(Bytes)
Date
Version
-------------- -------- ------Primary Image
: 7173079
07/27/09 Z.14.04
Secondary Image : 7173079
07/27/09 Z.14.04
Boot Rom Version: Z.14.03
Default Boot
: Secondary
ProCurve(config)# boot
This management module will now reboot from secondary and will become
the standby module! You will need to use the other management module's
console interface. Do you want to continue [y/n]?
Figure 6-13.Example of boot set-default Command with Default Flash Set to Secondary (with a
Redundant Management Module Present)
6-21
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
Booting from the Default Flash (Primary or Secondary)
The boot command boots the switch from the flash image that you are
currently booted on, or the flash image that was set either by the boot setdefault command or by the last executed boot system flash <primary | secondary>
command. This command also executes the complete set of subsystem selftests. You have the option of specifying a configuration file.
Syntax:
boot [system [flash <primary | secondary>] [config FILENAME]
Reboots the switch from the flash that you are currently booted
on (primary or secondary). You can select which image to
boot from during the boot process itself. When using
redundant management, the switch will failover to the
standby management module.
Note: This is changed from always booting from primary
flash. You are prompted with a message which will indicate
the flash being booted from.
system: Boots the switch. You can specify the flash image to
boot from.
config: You can optionally select a configuration file from
which to boot.
ProCurve(config)# boot
Do you want to save current configuration [y/n]? n
Figure 6-14. Example of Boot Command (Default Primary Flash) with Redundant Management
In the above example, typing either a y or n at the second prompt initiates the
reboot operation. (Entering y saves any configuration changes from the
running-config file to the startup-config file; entering n discards them.)
Booting from a Specified Flash
This version of the boot command gives you the option of specifying whether
to reboot from primary or secondary flash, and is the required command for
rebooting from secondary flash. This option also executes the complete set
of subsystem self-tests.
Syntax: boot system flash < primary | secondary >
For example, to reboot the switch from secondary flash when there are no
pending configuration changes in the running-config file:
6-22
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
ProCurve(config)# boot system flash secondary
System will be rebooted from secondary image. Do you want to continue [y/n]?
Figure 6-15. Example of Boot Command with Secondary Flash Option
In the above example, typing either a y or n at the second prompt initiates the
reboot operation.
Using the Fastboot feature. The fastboot command allows a boot
sequence that skips the internal power-on self-tests, resulting in a faster boot
time. When fastboot is enabled, it is saved to the standby management module
when the config files are synchronized. Fastboot is used during the next
bootup on either management module.
Syntax:
[no] fastboot
Enables the fastboot option
The no option disables the feature.
Syntax:
show fastboot
Shows the status of the fastboot feature, either enabled or
disabled.
The fastboot command is shown below.
ProCurve(config)# fastboot
Using Reload
The Reload command reboots the switch from the flash image that you are
currently booted on (primary or secondary) or the flash image that was set
either by the boot set-default command or by the last executed boot system flash
<primary | secondary> command. Because reload bypasses some subsystem
self-tests, the switch reboots faster than if you use either of the boot command
options.
Syntax: reload
For example, if you change the number of VLANs the switch supports, you
must reboot the switch in order to implement the change. The reload command
prompts you to save or discard the configuration changes.
6-23
Switch Memory and Configuration
Using Primary and Secondary Flash Image Options
ProCurve(config)# max-vlans 12
Command will take effect after saving configuration and reboot.
ProCurve(config)# reload
This command will cause a switchover to the other management module
which may not be running the same software image and configurations.
Do you want to continue [y/n]? y
Figure 6-16. Using Reload with Redundant Management and Pending Configuration Changes
Scheduled Reload. Additional parameters in the reload command allow for
a scheduled reboot of the switch via the CLI.
Syntax: [no] reload [after <[dd:]hh:]mm> | at <hh:mm[:ss]> [<mm/dd[/[yy]yy]>]]
Enables a scheduled warm reboot of the switch. The switch boots
up with the same startup config file and using the same flash
image as before the reload.
Parameters include:
• after: Schedules a warm reboot of the switch after a given amount
of time has passed.
• at: Schedules a warm reboot of the switch at a given time.
The no form of the command removes a pending reboot request.
For more details and examples, see below.
The scheduled reload feature removes the requirement to physically reboot
the switch at inconvenient times (for example, at 1:00 in the morning). Instead,
a reload at 1:00 mm/dd command can be executed (where mm/dd is the date
the switch is scheduled to reboot).
Note
Configuration changes are not saved with reload at or reload after commands.
No prompt to save configuration file changes is displayed. See Table 6-2 on
page 6-21.
Examples of scheduled reload commands:
6-24
■
To schedule a reload in 15 minutes:
ProCurve# reload after 15
■
To schedule a reload in 3 hours:
ProCurve# reload after 03:00
■
To schedule a reload for the same time the following day:
ProCurve# reload after 01:00:00
■
To schedule a reload for the same day at 12:05:
ProCurve# reload at 12:05
■
To schedule a reload on some future date:
ProCurve# reload at 12:05 03/01/2009
Switch Memory and Configuration
Multiple Configuration Files
Multiple Configuration Files
Action
Page
Listing and Displaying Startup-Config Files
6-29
Changing or Overriding the Reboot Configuration Policy
6-30
Managing Startup-Config Files
Renaming Startup-Config Files
6-33
Copying Startup-Config Files
6-33
Erasing Startup-Config Files
6-35
Effect of Using the Clear + Reset Buttons
6-37
Copying Startup-Config Files to or from a Remote Server
6-37
This method of operation means that you cannot preserve different startupconfig files across a reboot without using remote storage.
The switch allows up to three startup-config files with options for selecting
which startup-config file to use for:
■
A fixed reboot policy using a specific startup-config file for a specific boot
path (primary or secondary flash)
■
Overriding the current reboot policy on a per-instance basis
Primary Boot Path
Boot Command
Secondary Boot Path
Startup-Config
Options:
File 1
File 2
File 3
Running-Config
Figure 6-17. Optional Reboot Process
While you can still use remote storage for startup-config files, you can now
maintain multiple startup-config files on the switch and choose which version
to use for a reboot policy or an individual reboot.
This choice of which configuration file to use for the startup-config at reboot
provides the following new options:
■
The switch can reboot with different configuration options without having
to exchange one configuration file for another from a remote storage
location.
6-25
Switch Memory and Configuration
Multiple Configuration Files
■
Transitions from one software release to another can be performed while
maintaining a separate configuration for the different software release
versions.
■
By setting a reboot policy using a known good configuration and then
overriding the policy on a per-instance basis, you can test a new configuration with the provision that if an unattended reboot occurs, the switch
will come up with the known, good configuration instead of repeating a
reboot with a misconfiguration.
General Operation
Multiple Configuration Storage in the Switch. The switch uses three
memory “slots”, with identity (id) numbers of 1, 2, and 3.
Memory Slots
for Different
Startup-Config
Files
A startup-config file stored in a memory slot has a unique, changeable file
name. The switches covered in this guide can use the startup-config in any of
the memory slots (if the software version supports the configured features).
Boot Options. With multiple startup-config files in the switch you can specify a policy for the switch to use upon reboot. The options include:
■
Use the designated startup-config file with either or both reboot paths
(primary or secondary flash)
■
Override the current reboot policy for one reboot instance by specifying
a boot path (primary or secondary flash) and the startup-config file to use.
Changing the Startup-Config File. When the switch reboots, the startupconfig file supplies the configuration for the running-config file the switch uses
to operate. Making changes to the running-config file and then executing a
write-mem command (or, in the Menu interface, the Save command) are
written back to the startup-config file used at the last reboot. For example,
suppose that a system administrator performs the following on a switch that
has two startup-config files (workingConfig and backupConfig):
1.
6-26
Reboot the switch through the Primary boot path using the startup-config
file named backupConfig.
Switch Memory and Configuration
Multiple Configuration Files
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.
Boot Command
Primary Boot Path
Active Startup-Config File:
backupConfig
Idle Startup-Config File:
workingConfig
Generated Running-Config File
Use CLI To Change Running-Config
Execute write mem To Save Changes to
Source Startup-Config File
Figure 6-18. Example of Reboot Process and Making Changes to the StartupConfig File
Creating an Alternate Startup-Config File. There are two methods for
creating a new configuration file:
■
Copy an existing startup-config file to a new filename, then reboot the
switch, make the desired changes to the running-config file, then execute
write memory. (Refer to figure 6-6-18, above.)
■
Erase the active startup-config file. This generates a new, default startupconfig file that always results when the switch automatically reboots after
deletion of the currently active startup-config file. (Refer to “Erasing a
Startup-Config File” on page 6-35.)
Transitioning to Multiple Configuration Files
At the first reboot with a software release supporting multiple configuration,
the switch:
■
Assigns the filename oldConfig to the existing startup-config file (which is
stored in memory slot 1).
6-27
Switch Memory and Configuration
Multiple Configuration Files
■
Saves a copy of the existing startup-config file in memory slot 2 with the
filename workingConfig.
■
Assigns the workingConfig file as the active configuration and the default
configuration for all subsequent reboots using either primary or secondary flash.
Figure 6-19. Switch Memory Assignments After the First Reboot from Software
Supporting Multiple Configuration
In the above state, the switch always:
■
Uses the workingConfig file to reboot
The commands described later in this section enable you to view the current
multiple configuration status, manage multiple startup-config files, configure
reboot policies, and override reboot policies on a per-instance basis.
6-28
Switch Memory and Configuration
Multiple Configuration Files
Listing and Displaying Startup-Config Files
Command
Page
show config files
show config < filename >
Below
6-30
Viewing the Startup-Config File Status with Multiple
Configuration Enabled
Rebooting the switch automatically enables the multiple configuration feature.
Syntax:
show config files
This command displays the available startup-config files on
the switch and the current use of each file.
id: Identifies the memory slot for each startup-config file
available on the switch.
act: An asterisk ( * ) in this column indicates that the
corresponding startup-config file is currently in use.
pri: An asterisk ( * ) in this column indicates that the
corresponding startup-config file is currently assigned to the
primary boot path.
sec: An asterisk ( * ) in this column indicates that the
corresponding startup-config file is currently assigned to the
secondary boot path.
name: Shows the filename for each listed startup-config file in
the switch. Refer to “Renaming an Existing Startup-Config
File” on page 6-33 for the command you can use to change
existing startup-config filenames.
In the default configuration, if the switch was shipped from
the factory with software installed in both the primary and
secondary boot paths, then one startup-config file named
config1 is used for both paths and is stored in memory slot 1.
Memory slots 2 and 3 are empty in this default configuration.
6-29
Switch Memory and Configuration
Multiple Configuration Files
Displaying the Content of A Specific Startup-Config File
With Multiple Configuration enabled, the switch can have up to three startupconfig files. Because the show config command always displays the content of
the currently active startup-config file, the command extension shown below
is needed to allow viewing the contents of any other startup-config files stored
in the switch.
Syntax:
show config < filename >
This command displays the content of the specified startupconfig file in the same way that the show config command
displays the content of the default (currently active) startupconfig file.
Changing or Overriding the Reboot Configuration
Policy
Command
Page
startup-default [ primary | secondary ] config < filename >
Below
boot system flash < primary | secondary > config < filename >
6-32
You can boot the switch using any available startup-config file.
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. For example, when you first download a software version that supports multiple
configuration files and boot from the flash location of this version, the switch
copies the existing startup-config file (named oldConfig) into memory slot 2,
renames this file to workingConfig, and assigns workingConfig as:
■
The active configuration file
■
The configuration file to use when booting from either primary or secondary flash.
In this case, the switch is configured to automatically use the workingConfig
file in memory slot 2 for all reboots.
You can use the following command to change the current policy so that the
switch automatically boots using a different startup-config file.
6-30
Switch Memory and Configuration
Multiple Configuration Files
Syntax:
startup-default [ primary | secondary ] config < filename >
Specifies a boot configuration policy option:
[ primary | secondary ] config < filename >: Designates the
startup-config file to use in a reboot with the software
version stored in a specific flash location. Use this option
to change the reboot policy for either primary or
secondary flash, or both.
config < filename >: Designates the startup-config file to use
for all reboots, regardless of the flash version used. Use
this option when you want to automatically use the same
startup-config file for all reboots, regardless of the flash
source used.
For redundant management systems, this command affects
both the active management module and the standby management module. The config file is copied immediately to the
standby management module and becomes the default on that
module when the next bootup occurs, unless redundancy is
disabled or the standby module has failed selftest.
Note: To override the current reboot configuration policy for
a single reboot instance, use the boot system flash command
with the options described under “Overriding the Default
Reboot Configuration Policy” on page 6-32.
For example, suppose:
■
Software release “A” is stored in primary flash and a later software release
is stored in secondary flash.
■
The system operator is using memory slot 1 for a reliable, minimal
configuration (named minconfig) for the software version in the primary
flash, and slot 2 for a modified startup-config file (named newconfig) that
includes untested changes for improved network operation with the
software version in secondary flash.
The operator wants to ensure that in case of a need to reboot by pressing the
Reset button, or if a power failure occurs, the switch will automatically reboot
with the minimal startup-config file in memory slot 1. Since a reboot due to
pressing the Reset button or to a power cycle always uses the software version
in primary flash, the operator needs to configure the switch to always boot
from primary flash with the startup-config file named minconfig (in memory
slot 1). Also, whenever the switch boots from secondary flash, the operator
also wants the startup-config named newconfig to be used. The following two
commands configure the desired behavior.
6-31
Switch Memory and Configuration
Multiple Configuration Files
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.
Syntax:
boot system flash < primary | secondary > config < filename >
Specifies the name of the startup-config file to apply for the
immediate boot instance only. This command overrides the
current reboot policy.
Using Reload To Reboot From the Current Flash Image and StartupConfig File.
Syntax:
reload
This command boots the switch from the currently active flash
image and startup-config file. Because reload bypasses some
subsystem self-tests, the switch boots faster than if you use a
boot command.
Note: To identify the currently active startup-config file, use
the show config files command.
Managing Startup-Config Files in the Switch
6-32
Command
Page
rename config < current-filename > < newname-str >
6-33
copy config < source-filename > config < dest-filename >
6-33
erase config < filename > | startup-config
6-35
Erase startup-config using the front-panel Clear + Reset Buttons
6-37
Switch Memory and Configuration
Multiple Configuration Files
Renaming an Existing Startup-Config File
Syntax:
rename config < current-filename > < newname-str >
This command changes the name of an existing startupconfig file. A file name can include up to 63, alphanumeric
characters. Blanks are allowed in a file name enclosed in
quotes (“ “ or ‘ ‘). (File names are not case-sensitive.)
For redundant management systems, renaming a config file
affects both the active management module and the standby
management module, unless redundancy is disabled or the
standby module failed selftest.
Creating a New Startup-Config File
The switch allows up to three startup-config files. You can create a new
startup-config file if there is an empty memory slot or if you want to replace
one startup-config file with another.
Syntax:
copy config < source-filename > config < target-filename > [oobm]
6-33
Switch Memory and Configuration
Multiple Configuration Files
This command makes a local copy of an existing startupconfig file by copying the contents of an existing startupconfig file in one memory slot to a new startup-config file in
another, empty memory slot. This enables you to use a separate configuration file to experiment with configuration
changes, while preserving the source file unchanged. It also
simplifies a transition from one software version to another
by enabling you to preserve the startup-config file for the
earlier software version while creating a separate startupconfig file for the later software version. With two such
versions in place, you can easily reboot the switch with the
correct startup-config file for either software version.
• If the destination startup-config file already exists, it is
overwritten by the content of the source startup-config file.
• If the destination startup-config file does not already exist,
it will be created in the first empty configuration memory
slot on the switch.
• If the destination startup-config file does not already exist,
but there are no empty configuration memory slots on the
switch, then a new startup-config file is not created and
instead, the CLI displays the following error message:
Unable to copy configuration to “< target-filename >”.
The oobm parameter specifies that the copy operation will go
out from the out-of-band management interface. If this
parameter is not specified, the copy operation goes out from
the data interface. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on
out-of-band management.
For example, suppose both primary and secondary flash memory contain
software release “A” and use a startup-config file named config1:
Figure 6-20. Example of Using One Startup-Config File for Both Primary and
Secondary Flash
6-34
Switch Memory and Configuration
Multiple Configuration Files
If you wanted to experiment with configuration changes to the software
version in secondary flash, you could create and assign a separate startupconfig file for this purpose.
The first two commands copy the config1
startup-config file to config2, and then
make config2 the default startup-config
file for booting from secondary flash.
Figure 6-21. Example of Creating and Assigning a New Startup-Config File
Note
You can also generate a new startup-config file by booting the switch from a
flash memory location from which you have erased the currently assigned
startup-config file. Refer to “Erasing a Startup-Config File” in the next section.
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, defaultconfiguration file for the affected memory slot.
In a redundant management system, this command erases the config or startup
config file on both the active and the standby management modules as long
as redundancy has not been disabled. If the standby management module is
not in standby mode or has failed selftest, the config or startup config file is
not erased.
Syntax:
erase < config < filename >> | startup-config >
config < filename >: This option erases the specified startupconfig file. If the specified file is not the currently active
startup-config file, then the file is simply deleted from the
memory slot it occupies. If the specified file is the currently
active startup-config file, then the switch creates a new,
default startup-config file with the same name as the erased
file, and boots using this file. (This new startup-config file
contains only the default configuration for the software
version used in the reboot.)
6-35
Switch Memory and Configuration
Multiple Configuration Files
Note: Where a file is assigned to either the primary or the
secondary flash, but is not the currently active startupconfig file, erasing the file does not remove the flash
assignment from the memory slot for that file. Thus, if the
switch boots using a flash location that does not have an
assigned startup-config, then the switch creates a new,
default startup-config file and uses this file in the reboot.
(This new startup-config file contains only the default
configuration for the software version used in the reboot.)
Executing write memory after the reboot causes a switchgenerated filename of configx to appear in the show config
files display for the new file, where x corresponds to the
memory slot number.
startup-config: This option erases the currently active startupconfig file and reboots the switch from the currently active
flash memory location. The erased startup-config file is
replaced with a new startup-config file. The new file has
the same filename as the erased file, but contains only the
default configuration for the software version in the flash
location (primary or secondary) used for the reboot. For
example, suppose the last reboot was from primary flash
using a configuration file named minconfig. Executing
erase startup-config replaces the current content of minconfig
with a default configuration and reboots the switch from
primary flash.
Figure 6-22 illustrates using erase config < filename > to remove a startup-config
file.
Figure 6-22. Example of Erasing a Non-Active Startup-Config File
6-36
Switch Memory and Configuration
Multiple Configuration Files
With the same memory configuration as is shown in the bottom portion of
figure 6-22, executing erase startup-config boots the switch from primary flash,
resulting in a new file named minconfig in the same memory slot. The new file
contains the default configuration for the software version currently in primary flash.
Using the Clear + Reset Button Combination To Reset the
Switch to Its Default Configuration
The Clear + Reset button combination described in the Installation and
Getting Started Guide produces these results. That is, when you press the
Clear + Reset button combination, the switch:
•
Overwrites the content of the startup-config file currently in memory
slot 1 with the default configuration for the software version in
primary flash, and renames this file to config1.
•
Erases any other startup-config files currently in memory.
•
Configures the new file in memory slot 1 as the default for both
primary and secondary flash locations (regardless of the software
version currently in secondary flash).
•
Boots the switch from primary flash using the new startup-config file.
ProCurve# sho config files
Pressing Clear + Reset:
– Replaces all startup-config files with a single
file named config that contains the default
configuration for the software version in
id | act pri sec | name
primary flash.
---+-------------+----------------------------------------– Resets the Active, Primary, and Secondary
1 | *
*
* | config
assignments as shown here.
Configuration files:
2 |
3 |
|
|
Figure 6-23. Example of Clear + Reset Result
Transferring Startup-Config Files To or From a Remote
Server
Command
Page
copy config < src-file > tftp < ip-addr > < remote-file > < pc | unix > [oobm]
below
copy tftp config < dest-file > < ip-addr > < remote-file > < pc | unix > [oobm]
below
6-37
Switch Memory and Configuration
Multiple Configuration Files
copy config < src-file > xmodem < pc | unix > [oobm]
6-40
copy xmodem config < dest-file > < pc | unix > [oobm]
6-40
TFTP: Copying a Configuration File to a Remote Host
Syntax:
copy config < src-file > tftp < ip-addr > < remote-file > < pc | unix > [oobm]
This is an addition to the copy tftp command options. Use
this command to upload a configuration file from the switch
to a TFTP server.
The oobm parameter specifies that the copy operation will go
out from the out-of-band management interface. If this
parameter is not specified, the copy operation goes out from
the data interface. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on
out-of-band management.
For more on using TFTP to copy a file to a remote server, refer
to “TFTP: Copying a Configuration File to a Remote Host” on
page A-26.
For example, the following command copies a startup-config file named test01 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-38
Switch Memory and Configuration
Multiple Configuration Files
TFTP: Copying a Configuration File from a Remote Host
Syntax:
copy tftp config < dest-file > < ip-addr > < remote-file > < pc | unix > [oobm]
This is an addition to the copy tftp command options. Use
this command to download a configuration file from a TFTP
server to the switch.
The oobm parameter specifies that the copy operation will go
out from the out-of-band management interface. If this
parameter is not specified, the copy operation goes out from
the data interface. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on
out-of-band management.
Note: This command requires an empty memory slot in the
switch. If there are no empty memory slots, the CLI displays
the following message:
Unable to copy configuration to "< filename >".
For more on using TFTP to copy a file from a remote host,
refer to “TFTP: Copying a Configuration File from a Remote
Host” on page A-27.
For example, the following command copies a startup-config file named test01.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
6-39
Switch Memory and Configuration
Multiple Configuration Files
Xmodem: Copying a Configuration File to a Serially
Connected Host
Syntax:
copy config < filename > xmodem < pc | unix > [oobm]
This is an addition to the copy < config > xmodem command
options. Use this command to upload a configuration file
from the switch to an Xmodem host.
The oobm parameter specifies that the copy operation will go
out from the out-of-band management interface. If this
parameter is not specified, the copy operation goes out from
the data interface. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on
out-of-band management.
For more on using Xmodem to copy a file to a serially
connected host, refer to “Xmodem: Copying a Configuration
File to a USB Serial Console Connected PC or UNIX Workstation” on page A-28.
Xmodem: Copying a Configuration from a Serially
Connected Host
Syntax:
copy xmodem config < dest-file > < pc | unix > [oobm]
This is an addition to the copy xmodem command options. Use
this command to download a configuration file from an
Xmodem host to the switch.
The oobm parameter specifies that the copy operation will go
out from the out-of-band management interface. If this
parameter is not specified, the copy operation goes out from
the data interface. Refer to Appendix G, “Network Out-ofBand Management” in this guide for more information on
out-of-band management.
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” on
page A-29.
6-40
Switch Memory and Configuration
Automatic Configuration Update with DHCP Option 66
Operating Notes for Multiple Configuration Files
■
SFTP/SCP: The configuration files are available for sftp/scp transfer as
/cfg/< filename >.
Automatic Configuration Update with
DHCP Option 66
ProCurve switches are initially booted up with the factory-shipped configuration file. This feature provides a way to automatically download a different
configuration file from a TFTP server using DHCP Option 66. The prerequisites
for this to function correctly are:
Caution
■
One or more DHCP servers with Option 66 are enabled
■
One or more TFTP servers has the desired configuration file.
This feature must use configuration files generated on the switch to function
correctly. If you use configuration files that were not generated on the switch,
and then enable this feature, the switch may reboot continuously.
CLI Command
The command to enable the configuration update using Option 66 is:
Syntax: [no] dhcp config-file-update
Enables configuration file update using Option 66.
Default: Enabled
ProCurve(config)# dhcp config-file-update
Figure 6-24. Example of Enabling Configuration File Update Using Option 66
6-41
Switch Memory and Configuration
Automatic Configuration Update with DHCP Option 66
Possible Scenarios for Updating the Configuration File
The following table shows various network configurations and how Option 66
is handled.
Scenario
Behavior
Single Server serving Multiple VLANs
• Each DHCP-enabled VLAN interface initiates DHCPDISCOVER
message, receives DHCPOFFER from the server, and send
DHCPREQUEST to obtain the offered parameters.
• If multiple interfaces send DHCPREQUESTs, it’s possible that more
than one DHCPACK is returned with a valid Option 66.
• Evaluating and updating the configuration file occurs only on the
primary VLAN.
• Option 66 is ignored by any interfaces not belonging to the primary
VLAN.
Multiple Servers serving a Single VLAN
• Each DHCP-enabled VLAN interface initiates one DHCPDISCOVER
and receives one or more DHCPOFFER messages.
• Each interface accepts the best offer.
• Option 66 is processed only for the interface belonging to the primary
VLAN.
Multiple Servers serving Multiple VLANs
• Each DHSP-enabled VLAN interface initiates DHCPDISCOVER and
receives one or more DHCPOFFER messages.
• Each interface accepts the best offer.
• Option 66 is processed only for the interface belonging to the primary
VLAN.
Multi-homed Server serving Multiple VLANs
• The switch perceives the multi-homed server as multiple separate
servers.
• Each DHCP-enabled VLAN interface initiates DHCPDISCOVER and
receives one DHCPOFFER message.
• Each interface accepts the offer.
• Option 66 is processed only for the interface belonging to the primary
VLAN.
Operating Notes
Replacing the Existing Configuration File: After the DHCP client downloads the configuration file, the switch compares the contents of that file with
the existing configuration file. If the content is different, the new configuration
file replaces the existing file and the switch reboots.
Option 67 and the Configuration File Name: Option 67 includes the name
of the configuration file. If the DHCPACK contains this option, it overrides the
default name for the configuration file (switch.cfg)
6-42
Switch Memory and Configuration
Automatic Configuration Update with DHCP Option 66
Global DHCP Parameters: Global parameters are processed only if received
on the primary VLAN.
Best Offer: The “Best Offer” is the best DHCP or BootP offer sent by the
DHCP server in response to the DHCPREQUEST sent by the switch. The
criteria for selecting the “Best Offer” are:
•
DHCP is preferred over BootP
•
If two BootP offers are received, the first one is selected
•
For two DHCP offers:
– The offer from an authoritative server is selected
– If there is no authoritative server, the offer with the longest lease
is selected
Log Messages
The file transfer is implemented by the existing TFTP module. The system logs
the following message if an incorrect IP address is received for Option 66:
“Invalid IP address <ip-address> received for DHCP Option 66”
6-43
7
Interface Access and System Information
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Interface Access: Console/Serial Link, Web, and Inbound Telnet . 7-3
Menu: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
CLI: Modifying the Interface Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Denying Interface Access by Terminating Remote Management
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Menu: Viewing and Configuring System Information . . . . . . . . . . . . . 7-13
CLI: Viewing and Configuring System Information . . . . . . . . . . . . . . 7-14
Web: Configuring System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
7-1
Interface Access and System Information
Overview
Overview
This chapter describes how to:
■
View and modify the configuration for switch interface access
■
Use the CLI kill command to terminate a remote session
■
View and modify switch system information
For help on how to actually use the interfaces built into the switch, refer to:
■
Chapter 3, “Using the Menu Interface”
■
Chapter 4, “Using the Command Line Interface (CLI)”
■
Chapter 5, “Using the ProCurve Web Browser Interface”
Why Configure Interface Access and System Information? The interface access features in the switch operate properly by default. However, you
can modify or disable access features to suit your particular needs. Similarly,
you can choose to leave the system information parameters at their default
settings. However, modifying these parameters can help you to more easily
distinguish one device from another in your network.
7-2
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
Interface Access: Console/Serial Link,
Web, and Inbound Telnet
Interface Access Features
Feature
Inactivity Time
Inbound Telnet Access
Outbound Telnet Access
Web Browser Interface Access
Terminal type
Event Log event types to list
(Displayed Events)
Baud Rate
Flow Control
Default
Menu
CLI
Web
0 Minutes
(disabled)
page 7-4
page 7-8
—
Enabled
page 7-4
page 7-5
—
n/a
—
page 7-6
—
Enabled
page 7-4
page 7-7
—
VT-100
—
page 7-8
—
All
—
page 7-8
—
Speed Sense
—
page 7-8
—
XON/XOFF
—
page 7-8
—
In most cases, the default configuration is acceptable for standard operation.
Note
Basic switch security is through passwords. You can gain additional security
by using the security features described in the Access Security Guide for your
switch. You can also simply block unauthorized access via the web browser
interface or Telnet (as described in this section) and installing the switch in a
locked environment.
7-3
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
Menu: Modifying the Interface Access
The menu interface enables you to modify these parameters:
■
Inactivity Timeout
■
Inbound Telnet Enabled
■
Web Agent Enabled
To Access the Interface Access Parameters:
1.
From the Main Menu, Select...
2. Switch Configuration...
1. System Information
Interface Access
Parameters
Figure 7-1. The Default Interface Access Parameters Available in the Menu Interface
2.
Press [E] (for Edit). The cursor moves to the System Name field.
3.
Use the arrow keys ([v], [^], [<], [>]) to move to the parameters you want to
change.
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).
7-4
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
CLI: Modifying the Interface Access
Interface Access Commands Used in This Section
show console
below
[no] telnet-server
below
[no] web-management
page 7-7
console
page 7-8
Listing the Current Console/Serial Link Configuration. This command lists the current interface access parameter settings.
Syntax: show console
This example shows the switch’s default console/serial configuration.
Interface Access
Enable/Disable
Event Log Event
Types To List
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
7-5
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
Outbound Telnet to Another Device. This feature operates independently of the telnet-server status and enables you to Telnet to another device
that has an IP address.
Syntax: telnet <ipv4-addr | ipv6-addr | hostname | switch-num> [oobm]
Initiates an outbound telnet session to another network
device. The destination can be specified as:
•
•
•
•
•
IPv4 address
IPv6 address
Hostname
Stack number of a member switch (1-16) if the
switch is a commander in a stack and stacking is
enabled
The oobm parameter specifies that the Telnet
traffic will go out from the out-of-band management interface. If this parameter is not specified,
the Telnet traffic goes out from the data interface.
Refer to Appendix G, “Network Out-of-Band
Management” in this guide for more information
on out-of-band management.
For example, if the host “Labswitch” is in the domain abc.com, you can enter
the following command and the destination is resolved to “Labswitch.abc.com”.
ProCurve(config)# telnet Labswitch
You can also enter the full domain name in the command:
ProCurve(config)# telnet Labswitch.abc.com
You can use the show telnet command to display the resolved IP address.
7-6
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
ProCurve(config)# show telnet
Telnet Activity
-------------------------------------------------------Session : ** 1
Privilege: Manager
From
: Console
To
:
------------------------------------------------------Session : ** 2
Privilege: Manager
From
: 12.13.14.10
To
: 15.33.66.20
------------------------------------------------------Session : ** 3
Privilege: Operator
From
: 2001:db7:5:0:203:4ff:fe0a:251
To
: 2001:db7:5:0:203:4ff1:fddd:12
Figure 7-3. Example of show telnet Command Displaying Resolved IP Addresses
Reconfigure Web Browser Access. In the default configuration, web
browser access is enabled.
Syntax: [no] web-management [listen <oobm | data | both>]
Use the no version of the command to disable inbound HTTP
access.
The listen parameter is available only on switches that have a
separate out-of-band management port. Values for this
parameter are:
•
•
•
oobm — inbound HTTP access is enabled only on
the out-of-band management port.
data — inbound HTTP access is enabled only on
the data ports.
both — inbound HTTP access is enabled on both
the out-of-band management port and on the data
ports. This is the default value.
Refer to Appendix G, “Network Out-of-Band Management” in
this guide for more information on out-of-band management.
The listen parameter is not available on switches that do not
have a separate out-of-band management port.
7-7
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
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.
Syntax: console
[terminal < vt100 | ansi | none >]
[screen-refresh < 1 | 3 | 5 | 10 | 20 | 30 | 45 | 60 >]
[baud-rate
< speed-sense | 1200 | 2400 | 4800 | 9600 | 19200 |38400 | 57600 |
1155200 >]
[ flow-control < xon/xoff | none >]
[inactivity-timer < 0 | 1 | 5 | 10 | 15 | 20 | 30 | 60 |120 >]
[events <none | all | non-info | critical | debug]
[local-terminal <vt 100 | none | ansi>]
7-8
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
Note
If you change the Baud Rate or Flow Control settings for the switch, you
should make the corresponding changes in your console access device. Otherwise, you may lose connectivity between the switch and your terminal
emulator due to differences between the terminal and switch settings for these
two parameters.
All console parameter changes except events and inactivity-timer require that
you save the configuration with write memory and then execute boot before the
new console configuration will take effect.
For example, to use one command to configure the switch with the following:
■
VT100 operation
■
19,200 baud
■
No flow control
■
10-minute inactivity time
■
Critical log events
you would use the following command sequence:
The switch implements the Event Log change immediately. The switch implements
the other console changes after executing write memory and reload.
Figure 7-4. Example of Executing the Console Command with Multiple Parameters
7-9
Interface Access and System Information
Interface Access: Console/Serial Link, Web, and Inbound Telnet
You can also execute a series of console commands and then save the
configuration and boot the switch. For example:
Configure
the
individual
parameters.
Save the
changes.
Boot the
switch.
Figure 7-5. Example of Executing a Series of Console Commands
7-10
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 five management sessions. You can use show ip ssh
to list the current management sessions, and kill to terminate a currently
running remote session. (Kill does not terminate a Console session on the
serial port, either through a direct connection or via a modem. It does not
affect the console on the standby module.)
Syntax: kill [< session-number >]
For example, if you are using the switch’s serial port for a console session and
want to terminate a currently active Telnet session, you would do the following:
Session 2 is an active
Telnet session.
The kill 2 command
terminates session 2.
Figure 7-6. Example of Using the “Kill” Command To Terminate a Remote Session
7-11
Interface Access and System Information
System Information
System Information
System Information Features
Feature
Default
Menu
CLI
Web
System Name
switch product
name
page
7-13
page
7-15
page
7-19
System Contact
n/a
page
7-13
page
7-15
page
7-19
System Location
n/a
page
7-13
page
7-15
page
7-19
MAC Age Time
300 seconds
page
7-13
page
7-17
—
Time Sync Method
None
See Chapter 9, “Time Protocols”.
Time Zone
0
page
7-13
page
7-18
—
Daylight Time Rule
None
page
7-13
page
7-18
—
Time
January 1, 1990 at
00:00:00 at last
power reset
—
page
7-18
—
Configuring system information is optional, but recommended.
System Name: Using a unique name helps you to identify individual devices
where you are using an SNMP network management 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.
MAC Age Time: The number of seconds a MAC address the switch has
learned remains in the switch’s address table before being aged out (deleted).
Aging out occurs when there has been no traffic from the device belonging to
that MAC address for the configured interval.
Time Sync Method: Selects the method (TimeP or SNTP) the switch will use
for time synchronization. For more on this topic, refer to Chapter 9, “Time
Protocols”.
7-12
Interface Access and System Information
System Information
Time Zone: The number of minutes your time zone location is to the West (+)
or East (-) of Coordinated Universal Time (formerly GMT). The default 0
means no time zone is configured. For example, the time zone for Berlin,
Germany is + 60 (minutes) and the time zone for Vancouver, Canada is - 480
(minutes).
Daylight Time Rule: Specifies the daylight savings time rule to apply for your
location. The default is None. (For more on this topic, refer to Appendix D,
“Daylight Savings Time on ProCurve Switches.)
Time: Used in the CLI to specify the time of day, the date, and other system
parameters.
Menu: Viewing and Configuring System Information
To access the system information parameters:
1.
From the Main Menu, Select...
2. Switch Configuration...
1. System Information
System Information
Figure 7-7. The System Information Configuration Screen (Default Values)
Note
To help simplify administration, it is recommended that you configure
System Name to a character string that is meaningful within your system.
7-13
Interface Access and System Information
System Information
2.
Press [E] (for Edit). The cursor moves to the System Name field.
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
below
show system enclosure
below
hostname
below
snmp-server
[contact] [location]
below
mac-age-time
page 7-17
time
timezone
page 7-18
daylight-time-rule
page 7-18
date
time
page 7-18
Listing the Current System Information. This command lists the current
system information settings.
Syntax: show system information
This example shows the switch’s default console configuration.
ProCurve# show system information
Status and Counters - General System Information
System Name
System Contact
System Location
: ProCurve
:
:
MAC Age Time (sec) : 300
Time Zone
: 0
Daylight Time Rule : None
Figure 7-8. Example of CLI System Information Listing
7-14
Interface Access and System Information
System Information
Listing the System Enclosure Information. This command lists the system enclosure information.
Syntax: show system enclosure
This example shows the switch’s enclosure configuration.
ProCurve# show system enclosure
Rack and Enclosure Information
Rack Name
Rack Unique ID
Enclosure Name
Enclosure Serial Number
:
:
:
:
Donner_Bldg5U
Default RUID
2XX81401UP
2XX81401UP
Figure 7-9. Example of CLI System Enclosure Information Listing
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>]
Each field allows up to 255 characters.
For example, to name the switch “Blue” with “Next-4474” as the system
contact, and “North-Data-Room” as the location:
7-15
Interface Access and System Information
System Information
New hostname, contact,
and location data from
previous commands.
Additional System
Information
Figure 7-10. System Information Listing After Executing the Preceding Commands
The menu interface will only display up to 47 characters although you can
specify a name up to 255 characters in length. A message beginning with “+”
displays if the name exceeds 47 characters. You can use the CLI show running,
show config, or show system information commands to see the complete text.
The menu interface is shown in Figure 7-11.
7-16
Interface Access and System Information
System Information
MENU
ProCurve Switch 6120
24-Oct-2008 12:41:47
===========================- TELNET - MANAGER MODE ===========================
Switch Configuration - System Information
System Name : Blue Switch
System Contact : Bill_Smith
System Location : + characters of the location are missing. It’s too long.
Inactivity Timeout (min) [0] : 0
Inbound Telnet Enabled [Yes] : Yes
Time Sync Method [None] : TIMEP
TimeP Mode [Disabled] : Disabled
MAC Age Time (sec) [300] : 300
Web Agent Enabled [Yes] : Yes
Tftp-enable [Yes] : Yes
Time Zone [0] : 0
Daylight Time Rule [None] : None
Actions->
Cancel
Edit
Save
Help
Cancel changes and return to previous screen.
Use arrow keys to change action selection and <Enter> to execute action.
Figure 7-11. Menu Screen Showing System Information
The Web Browser interface also allows you to enter a maximum of 255
characters. You can view all the characters by using the cursor to scroll
through the field.
Figure 7-12. System Location and System Contact in the Web Browser
Reconfigure the MAC Age Time for Learned MAC Addresses. This
command corresponds to the MAC Age Interval in the menu interface, and is
expressed in seconds.
7-17
Interface Access and System Information
System Information
Syntax: mac-age-time < 10 - 1000000 > (seconds)
Allows you to set the MAC address table’s age-out interval. An
address is aged out if the switch does not receive traffic from that
MAC address for the age-out interval, measured in seconds.
Default: 300 seconds.
For example, to configure the age time to seven minutes:
ProCurve(config)# mac-age-time 420
Configure the Time Zone and Daylight Time Rule. These commands:
■
Set the time zone you want to use
■
Define the daylight time rule for keeping the correct time when daylightsaving-time shifts occur.
Syntax: time timezone < -720 - 840 >
time daylight-time-rule < none | alaska | continental-us-and-canada |
middle-europe-and-portugal | southern-hemisphere | western-europe |
user-defined>
East of the 0 meridian, the sign is “+”. West of the 0 meridian, the sign is “-”.
For example, the time zone setting for Berlin, Germany is +60 (zone +1, or 60
minutes), and the time zone setting for 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 configure both the time of day and the date. Also, executing time without parameters lists the switch’s time of day and date. Note that the CLI uses a 24-hour
clock scheme; that is, hour (hh) values from 1 p.m. to midnight are input as
13 - 24, respectively.
Syntax: time [ hh:mm [ :ss ]] [ mm/dd/ [ yy ] yy ]
For example, to set the switch to 9:45 a.m. on November 17, 2002:
ProCurve(config)# time 9:45 11/17/02
Note
7-18
Executing reload or boot resets the time and date to their default startup values.
Interface Access and System Information
System Information
Web: Configuring System Parameters
In the web browser interface, you can enter the following system information:
■
System Name
■
System Location
■
System Contact
For access to the MAC Age Interval and the Time parameters, use the menu
interface or the CLI.
Configure System Parameters in the Web Browser Interface.
1.
Click on the Configuration tab.
2.
Click on [System Info].
3.
Enter the data you want in the displayed fields.
4.
Implement your new data by clicking on [Apply Changes].
To access the web-based help provided for the switch, click on [?] in the web
browser screen.
7-19
8
Configuring IP Addressing
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Just Want a Quick Start with IP Addressing? . . . . . . . . . . . . . . . . . . . . 8-3
IP Addressing with Multiple VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Menu: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . 8-5
CLI: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . . . 8-6
Web: Configuring IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
How IP Addressing Affects Switch Operation . . . . . . . . . . . . . . . . . . . 8-11
DHCP/Bootp Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Network Preparations for Configuring DHCP/Bootp . . . . . . . . . 8-14
IP Preserve: Retaining VLAN-1 IP
Addressing Across Configuration File Downloads . . . . . . . . . . . . . . 8-16
Operating Rules for IP Preserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Enabling IP Preserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
8-1
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.
■
Assign up to 32 IP addresses to a VLAN (multinetting).
Why Configure IP Addressing? In its factory default configuration, the
switch operates as a multiport learning bridge with network connectivity
provided by the ports on the switch. However, to enable specific management
access and control through your network, you will need IP addressing. Table
8-1 on page 8-11 shows the switch features that depend on IP addressing to
operate.
IP Configuration
IP Configuration Features
Feature
Default
Menu
CLI
Web
DHCP/Bootp
page 8-5
page 8-6
page 8-10
n/a
—
page 8-8
—
Default Gateway Address
none
page 8-5
page 8-6
page 8-10
Packet Time-To-Live (TTL)
64 seconds
page 8-5
page 8-6
—
DHCP
page 8-5
page 8-6
—
IP Address and Subnet Mask
Multiple IP Addresses on a VLAN
Time Server (Timep)
IP Address and Subnet Mask. Configuring the switch with an IP address
expands your ability to manage the switch and use its features. By default, the
switch is configured to automatically receive IP addressing on the default
VLAN from a DHCP/Bootp server that has been configured correctly with
information to support the switch. (Refer to “DHCP/Bootp Operation” on page
8-12 for information on setting up automatic configuration from a server.)
However, if you are not using a DHCP/Bootp server to configure IP addressing,
8-2
Configuring IP Addressing
IP Configuration
use the menu interface or the CLI to manually configure the initial IP values.
After you have network access to a device, you can use the web browser
interface to modify the initial IP configuration if needed.
For information on how IP addressing affects switch operation, refer to “How
IP Addressing Affects Switch Operation” on page 8-11.
Multinetting: Assigning Multiple IP Addresses to a VLAN. For a given
VLAN you can assign up to 32 IP addresses. This allows you to combine two
or more subnets on the same VLAN, which enables devices in the combined
subnets to communicate normally through the network without needing to
reconfigure the IP addressing in any of the combined subnets.
Default Gateway Operation. The default gateway is required when a
router is needed for tasks such as reaching off-subnet destinations or forwarding traffic across multiple VLANs. The gateway value is the IP address of the
next-hop gateway node for the switch, which is used if the requested destination address is not on a local subnet/VLAN. If the switch does not have a
manually-configured default gateway and DHCP/Bootp is configured on the
primary VLAN, then the default gateway value provided by the DHCP or Bootp
server will be used. If the switch has a manually configured default gateway,
then the switch uses this gateway, even if a different gateway is received via
DHCP or Bootp on the primary VLAN. This is also true for manually configured
TimeP, SNTP, and Time-To-Live(TTL). (In the default configuration, VLAN 1 is
the Primary VLAN.) Refer to the information on Primary VLANs in the
Advanced Traffic Management Guide for your switch.
Packet Time-To-Live (TTL) . This parameter specifies the maximum number of routers (hops) through which a packet can pass before being discarded.
Each router decreases a packet’s TTL by 1 before forwarding the packet. If
decreasing the TTL causes the TTL to be 0, the router drops the packet instead
of forwarding it. In most cases, the default setting (64) is adequate.
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.
ProCurve# setup
■
Select 8. Run Setup in the Main Menu of the menu interface.
8-3
Configuring IP Addressing
IP Configuration
For more on using the Switch Setup screen, refer to the Installation and
Getting Started Guide you received with the switch.
IP Addressing with Multiple VLANs
In the factory-default configuration, the switch has one, permanent default
VLAN (named DEFAULT_VLAN) that includes all ports on the switch. Thus,
when only the default VLAN exists in the switch, if you assign an IP address
and subnet mask to the switch, you are actually assigning the IP addressing
to the DEFAULT_VLAN.
Notes
8-4
■
If multiple VLANs are configured, then each VLAN can have its own IP
address. This is because each VLAN operates as a separate broadcast
domain and requires a unique IP address and subnet mask. A default
gateway (IP) address for the switch is optional, but recommended.
■
In the factory-default configuration, the default VLAN (named
DEFAULT_VLAN) is the switch’s primary VLAN. The switch uses the
primary VLAN for learning the default gateway address. The switch can
also learn other settings from a DHCP or Bootp server, such as (packet)
Time-To-Live (TTL), and Timep or SNMP settings. (Other VLANs can also
use DHCP or BootP to acquire IP addressing. However, the switch’s
gateway, TTL, and TimeP or SNTP values, which are applied globally, and
not per-VLAN, will be acquired through the primary VLAN only, unless
manually set by using the CLI, Menu, or web browser interface.(If these
parameters are manually set, they will not be overwritten by alternate
values received from a DHCP or Bootp server.) For more on VLANs, refer
to the chapter titled “Static Virtual LANs” in the Advanced Traffic Management Guide for your switch.
■
The IP addressing used in the switch should be compatible with your
network. That is, the IP address must be unique and the subnet mask must
be appropriate for your IP network.
■
If you change the IP address through either Telnet access or the web
browser interface, the connection to the switch will be lost. You can
reconnect by either restarting Telnet with the new IP address or entering
the new address as the URL in your web browser.
Configuring IP Addressing
IP Configuration
Menu: Configuring IP Address, Gateway, and Time-ToLive (TTL)
Do one of the following:
■
To manually enter an IP address, subnet mask, set the IP Config parameter
to Manual and then manually enter the IP address and subnet mask values
you want for the switch.
■
To use DHCP or Bootp, use the menu interface to ensure that the IP Config
parameter is set to DHCP/Bootp, then refer to “DHCP/Bootp Operation” on
page 8-12.
To Configure IP Addressing.
1.
From the Main Menu, Select.
2. Switch Configuration …
5. IP Configuration
Notes
If multiple VLANs are configured, a screen showing all VLANs appears instead
of the following screen.
The Menu interface displays the IP address for any VLAN. If you use the CLI
to configure the IP address on a VLAN, use the CLI show ip command to list
them. (Refer to “Viewing the Current IP Configuration” on page 8-6.)
For descriptions of these
parameters, see the
online Help for this
screen.
Before using the DHCP/
Bootp option, refer to
“DHCP/Bootp
Operation” on page 8-12.
Figure 8-1. Example of the IP Service Configuration Screen without Multiple
VLANs Configured
2.
Press [E] (for Edit).
8-5
Configuring IP Addressing
IP Configuration
3.
If the switch needs to access a router, for example, to reach off-subnet
destinations, select the Default Gateway field and enter the IP address of
the gateway router.
4.
If you need to change the packet Time-To-Live (TTL) setting, select Default
TTL and type in a value between 2 and 255.
5.
To configure IP addressing, select IP Config and do one of the following:
•
If you want to have the switch retrieve its IP configuration from a
DHCP or Bootp server, at the IP Config field, keep the value as DHCP/
Bootp and go to step 8.
•
If you want to manually configure the IP information, use the Space
bar to select Manual and use the [Tab] key to move to the other IP
configuration fields.
6.
Select the IP Address field and enter the IP address for the switch.
7.
Select the Subnet Mask field and enter the subnet mask for the IP address.
8.
Press [Enter], then [S] (for Save).
CLI: Configuring IP Address, Gateway, and Time-ToLive (TTL)
IP Commands Used in This Section
show ip
Page
8-6
ip address < mask-length >
8-7, 8-8
ip address /< mask-bits >
8-7, 8-8
ip default-gateway
8-10
ip ttl
8-10
Viewing the Current IP Configuration.
Syntax: show ip
This command displays the IP addressing for each VLAN
configured in the switch. If only the DEFAULT_VLAN exists,
then its IP configuration applies to all ports in the switch.
Where multiple VLANs are configured, the IP addressing is
listed per VLAN. The display includes switch-wide packet
time-to-live, and (if configured) the switch’s default gateway
and Timep configuration.
8-6
Configuring IP Addressing
IP Configuration
(You can also use the show management command to display the IP addressing
and time server IP addressing configured on the switch. Refer to figure
9-6 on page 9-10.)
For example, in the factory-default configuration (no IP addressing assigned),
the switch’s IP addressing appears as:
The Default IP
Configuration
Figure 8-2. Example of the Switch’s Default IP Addressing
With multiple VLANs and some other features configured, show ip provides
additional information:
A Switch with IP
Addressing and
VLANs Configured
Figure 8-3. Example of Show IP Listing with Non-Default IP Addressing Configured
Configure an IP Address and Subnet Mask. The following command
includes both the IP address and the subnet mask. You must either include the
ID of the VLAN for which you are configuring IP addressing or go to the
context configuration level for that VLAN. (If you are not using VLANs on the
switch—that is, if the only VLAN is the default VLAN—then the VLAN ID is
always “1”.)
8-7
Configuring IP Addressing
IP Configuration
Note
The default IP address setting for the DEFAULT_VLAN is DHCP/Bootp. On
additional VLANs you create, the default IP address setting is Disabled.
Syntax:
[ no ] vlan < vlan-id > ip address <ip-address/mask-length>
or
[ no ] vlan < vlan-id > ip address < ip-address > < mask-bits >
or
vlan < vlan-id > ip address dhcp-bootp
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.
ProCurve(config)# vlan 1 ip address 10.28.227.103/24
This example deletes an IP address configured in VLAN 1.
ProCurve (config) no vlan 1 ip address 10.28.227.103/24
Configure Multiple IP Addresses on a VLAN (Multinetting). The following is supported:
■
Up to 2000 IP addresses for the switch
■
Up to 32 IP addresses for the same VLAN
■
Up to 512 IP VLANs, that is, VLANs on which you can configure IP
addresses
■
Each IP address on a VLAN must be for a separate subnet, whether on the
same VLAN or different VLANs.
Syntax:
[ no ] vlan < vlan-id > ip address < ip-address/mask-length >
[ no ] vlan < vlan-id > ip address < ip-address > < mask-bits >
For example, if you wanted to multinet VLAN_20 (VID = 20) with the IP
addresses shown below, you would perform steps similar to the following.
(For this example, assume that the first IP address is already configured.)
IP Address
1st address
8-8
VID
20
IP Address
10.25.33.101
Subnet Mask
255.255.240.0
2nd address
20
10.26.33.101
255.255.240.0
3rd address
20
10.27.33.101
255.255.240.0
Configuring IP Addressing
IP Configuration
1. Go to VLAN 20.
2. Configure two additional
IP addresses on VLAN
20.
3. Display IP addressing.
Figure 8-4. Example of Configuring and Displaying a Multinetted VLAN
If you then wanted to multinet the default VLAN, you would do the following:
Figure 8-5. Example of Multinetting on the Default VLAN
Note
The Internet (IP) Service screen in the Menu interface (figure 8-1 on page 8-5)
displays the first IP address for each VLAN. You must use the CLI show ip
command to display the full IP address listing for multinetted VLANs.
8-9
Configuring IP Addressing
IP Configuration
Removing or Replacing IP Addresses in a Multinetted VLAN. To
remove an IP address from a multinetted VLAN, use the no form of the IP
address command shown on page 8-8. Generally, to replace one IP address
with another, you should first remove the address you want to replace, and
then enter the new address.
Configure the Optional Default Gateway. Using the Global configuration level, you can manually assign one default gateway to the switch. (The
switch does not allow IP addressing received from a DHCP or Bootp server
to replace a manually configured default gateway.)
Syntax: ip default-gateway < ip-address >
For example:
ProCurve(config)# ip default-gateway 10.28.227.115
Note
The switch uses the IP default gateway only while operating as a Layer 2
device. While routing is enabled on the switch, the IP default gateway is not
used. Thus, to avoid loss of Telnet access to off-subnet management stations,
you should use the ip route command to configure a static (default) route
before enabling routing. For more information, refer to the chapter titled “IP
Routing Features” in the Multicast and Routing Guide for your switch.
Configure Time-To-Live (TTL). The maximum number of routers (hops)
through which a packet can pass before being discarded. (The default is 64.)
Each router decreases a packet’s TTL by 1 before forwarding the packet. If a
router decreases the TTL to 0, the router drops the packet instead of forwarding it.
Syntax: ip ttl <number-of-hops>
ProCurve(config)# ip ttl 60
In the CLI, you can execute this command only from the global configuration
level. The TTL default is 64, and the range is 2 - 255.
Web: Configuring IP Addressing
You can use the web browser interface to access IP addressing only if the
switch already has an IP address that is reachable through your network.
8-10
1.
Click on the Configuration tab.
2.
Click on [IP Configuration].
Configuring IP Addressing
IP Configuration
3.
If you need further information on using the web browser interface, click
on [?] to access the web-based help available for the switch.
How IP Addressing Affects Switch Operation
Without an IP address and subnet mask compatible with your network, the
switch can be managed only through a direct terminal device connection to
the OA console connection or the USB serial console. You can use directconnect console access to take advantage of features that do not depend on
IP addressing. However, to realize the full capabilities ProCurve proactive
networking offers through the switch, configure the switch with an IP address
and subnet mask compatible with your network. The following table lists the
general features available with and without a network-compatible IP address
configured.
Table 8-1.
Features Available With and Without IP Addressing on the Switch
Features Available Without an IP Address
Additional Features Available with an IP Address and
Subnet Mask
• Direct-connect access to the CLI and the menu
interface.
• DHCP or Bootp support for automatic IP address
configuration, and DHCP support for automatic Timep
server IP address configuration
• Multiple Spanning Tree Protocol
• Port settings and port trunking
• Console-based status and counters information for
monitoring switch operation and diagnosing problems
through the CLI or menu interface.
• VLANs and GVRP
• Serial downloads of software updates and
configuration files (Xmodem)
• Link test
• Port monitoring
• Password authentication
• Quality of Service (QoS)
• Authorized IP manager security
• Web browser interface access, with configuration,
security, and diagnostic tools, plus the Alert Log for
discovering problems detected in the switch along
with suggested solutions
• SNMP network management access such as
ProCurve Manager for network configuration,
monitoring, problem-finding and reporting, analysis,
and recommendations for changes to increase control
and uptime
• TACACS+, RADIUS, SSH, SSL, and 802.1X
authentication
• Multinetting on VLANs
• Telnet access to the CLI or the menu interface
• IGMP
• TimeP and SNTP server configuration
• TFTP download of configurations and software
updates
• Radius
• Ping test
8-11
Configuring IP Addressing
IP Configuration
DHCP/Bootp Operation
Overview. DHCP/Bootp is used to provide configuration data from a DHCP
or Bootp server to the switch. This data can be the IP address, subnet mask,
default gateway, Timep Server address, and TFTP server address. If a TFTP
server address is provided, this allows the switch to TFTP a previously saved
configuration file from the TFTP server to the switch. With either DHCP or
Bootp, the servers must be configured prior to the switch being connected to
the network.
Note
The switches covered in this guide are compatible with both DHCP and Bootp
servers.
The DHCP/Bootp Process. Whenever the IP Config parameter in the switch
or in an individual VLAN in the switch is configured to DHCP/Bootp (the
default), or when the switch is rebooted with this configuration:
Note
1.
DHCP/Bootp requests are automatically broadcast on the local network.
(The switch sends one type of request to which either a DHCP or Bootp
server can respond.)
2.
When a DHCP or Bootp server receives the request, it replies with a
previously configured IP address and subnet mask for the switch. The
switch also receives an IP Gateway address if the server has been configured to provide one. In the case of Bootp, the server must first be
configured with an entry that has the switch’s MAC address. (To determine
the switch’s MAC address, refer to Appendix D, “MAC Address Management”.) The switch properly handles replies from either type of server. If
multiple replies are returned, the switch tries to use the first reply.)
If you manually configure default gateway, TTL, TimeP, and/or SNTP parameters on the switch, it ignores any values received for the same parameters via
DHCP or Bootp.
If the switch is initially configured for DHCP/Bootp operation (the default),
or if it reboots with this configuration, it begins sending request packets on
the network. If the switch does not receive a reply to its DHCP/Bootp requests,
it continues to periodically send request packets, but with decreasing frequency. Thus, if a DHCP or Bootp server is not available or accessible to the
switch when DHCP/Bootp is first configured, the switch may not immediately
receive the desired configuration. After verifying that the server has become
accessible to the switch, reboot the switch to re-start the process immediately.
8-12
Configuring IP Addressing
IP Configuration
DHCP Operation. A significant difference between a DHCP configuration
and a Bootp configuration is that an IP address assignment from a DHCP
server is automatic. Depending on how the DHCP server is configured, the
switch may receive an IP address that is temporarily leased. Periodically the
switch may be required to renew its lease of the IP configuration. Thus, the IP
addressing provided by the server may be different each time the switch
reboots or renews its configuration from the server. However, you can fix the
address assignment for the switch by doing either of the following:
■
Configure the server to issue an “infinite” lease.
■
Using the switch’s MAC address as an identifier, configure the server with
a “Reservation” so that it will always assign the same IP address to the
switch. (For MAC address information, refer to Appendix D, “MAC
Address Management”.)
For more information on either of these procedures, refer to the documentation provided with the DHCP server.
Bootp Operation. When a Bootp server receives a request it searches its
Bootp database for a record entry that matches the MAC address in the Bootp
request from the switch. If a match is found, the configuration data in the
associated database record is returned to the switch. For many Unix systems,
the Bootp database is contained in the /etc/bootptab file. In contrast to DHCP
operation, Bootp configurations are always the same for a specific receiving
device. That is, the Bootp server replies to a request with a configuration
previously stored in the server and designated for the requesting device.
Bootp Database Record Entries. A minimal entry in the Bootp table file
/etc/bootptab to update an IP address and subnet mask to the switch or a VLAN
configured in the switch would be similar to this entry:
6120switch:\
ht=ether:\
ha=0030c1123456:\
ip=10.66.77.88:\
sm=255.255.248.0:\
gw=10.66.77.1:\
hn:\
vm=rfc1048
An entry in the Bootp table file /etc/bootptab to tell the switch or VLAN
where to obtain a configuration file download would be similar to this entry:
6120switch:\
ht=ether:\
ha=0030c1123456:\
ip=10.66.77.88:\
sm=255.255.248.0:\
8-13
Configuring IP Addressing
IP Configuration
gw=10.66.77.1:\
lg=10.22.33.44:\
T144=”switch.cfg”:\
vm=rfc1048
where:
Note
6120switch
is a user-defined symbolic name to help you find the correct section of the
bootptab file. If you have multiple switches that will be using Bootp to get their
IP configuration, you should use a unique symbolic name for each switch.
ht
is the “hardware type”. For the switches covered in this guide, enter ether (for
Ethernet). This tag must precede the ha tag.
ha
is the “hardware address”. Use the switch's (or VLAN's) 12-digit MAC address.
ip
is the IP address to be assigned to the switch (or VLAN).
sm
is the subnet mask of the subnet in which the switch (or VLAN) is installed.
gw
is the IP address of the default gateway.
lg
TFTP server address (source of final configuration file)
T144
is the vendor-specific “tag” identifying the configuration file to download.
vm
is a required entry that specifies the Bootp report format. Use rfc1048 for the
switches covered in this guide.
The above Bootp table entry is a sample that will work for the switch when
the appropriate addresses and file names are used.
Network Preparations for Configuring DHCP/Bootp
In its default configuration, the switch is configured for DHCP/Bootp operation. However, the DHCP/Bootp feature will not acquire IP addressing for the
switch unless the following tasks have already been completed:
■
■
8-14
For Bootp operation:
•
A Bootp database record has already been entered into an appropriate
Bootp server.
•
The necessary network connections are in place
•
The Bootp server is accessible from the switch
For DHCP operation:
•
A DHCP scope has been configured on the appropriate DHCP server.
•
The necessary network connections are in place
•
A DHCP server is accessible from the switch
Configuring IP Addressing
IP Configuration
Note
Designating a primary VLAN other than the default VLAN affects the switch’s
use of information received via DHCP/Bootp. For more on this topic, refer to
the chapter describing VLANs in the Advanced Traffic Management Guide
for your switch.
After you reconfigure or reboot the switch with DHCP/Bootp enabled in a
network providing DHCP/Bootp service, the switch does the following:
■
Receives an IP address and subnet mask and, if configured in the server,
a gateway IP address and the address of a Timep server.
■
If the DHCP/Bootp reply provides information for downloading a configuration file, the switch uses TFTP to download the file from the designated
source, then reboots itself. (This assumes that the switch or VLAN has
connectivity to the TFTP file server specified in the reply, that the configuration file is correctly named, and that the configuration file exists in the
TFTP directory.)
8-15
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
For the switches covered in this guide, IP Preserve enables you to copy a
configuration file to multiple switches while retaining the individual IP
address and subnet mask on VLAN 1 in each switch, and the Gateway IP
address assigned to the switch. This enables you to distribute the same
configuration file to multiple switches without overwriting their individual IP
addresses.
Operating Rules for IP Preserve
When ip preserve is entered as the last line in a configuration file stored on a
TFTP server:
8-16
■
If the switch’s current IP address for VLAN 1 was not configured by DHCP/
Bootp, IP Preserve retains the switch’s current IP address, subnet mask,
and IP gateway address when the switch downloads the file and reboots.
The switch adopts all other configuration parameters in the configuration
file into the startup-config file.
■
If the switch’s current IP addressing for VLAN 1 is from a DHCP server,
IP Preserve is suspended. In this case, whatever IP addressing the configuration file specifies is implemented when the switch downloads the file
and reboots. If the file includes DHCP/Bootp as the IP addressing source
for VLAN 1, the switch will configure itself accordingly and use DHCP/
Bootp. If instead, the file includes a dedicated IP address and subnet mask
for VLAN 1 and a specific gateway IP address, then the switch will
implement these settings in the startup-config file.
■
The ip preserve statement does not appear in show config listings. To verify
IP Preserve in a configuration file, open the file in a text editor and view
the last line. For an example of implementing IP Preserve in a configuration file, see figure 8-6, below.
Configuring IP Addressing
IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads
Enabling IP Preserve
To set up IP Preserve, enter the ip preserve statement at the end of a configuration file. (Note that you do not execute IP Preserve by entering a command
from the CLI).
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 Configuration File
For example, consider Figure 8-7:
DHCP
Server
TFTP
Server
Management
Station
config.
IP
Address
Switch 1
Switch 2
Switch 3
Switch 4
VLAN 1:
10.31.22.101
VLAN 1:
10.31.22.102
VLAN 1:
10.31.22.103
VLAN 1: DHCP
Switches 1 through 3 copy and implement the config.txt file
from the TFTP server (figure 8-8), but retain their current IP
Switch 4 also copies and implements the
config.txt file from the TFTP server (figure 8-8),
but acquires new IP addressing from the DHCP
Figure 8-7. Example of IP Preserve Operation with Multiple Series Switches
If you apply the following configuration file to figure 8-7, switches 1 - 3 will
retain their manually assigned IP addressing and switch 4 will be configured
to acquire its IP addressing from a DHCP server.
8-17
Configuring IP Addressing
IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads
ProCurve(config)# show run
Running configuration:
; 498358-B21 Configuration Editor; Created on release #Z.14.04
hostname "ProCurve"
module 1 type J8702A
module 2 type J8705A
trunk A11-A12 Trk1 Trunk
ip default-gateway 10.10.10.115
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1-A10,A13-A24,B1-B24,Trk1
ip address dhcp-bootp
exit
spanning-tree Trk1 priority 4
password manager
password operator
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
from a DHCP/Bootp server).
Figure 8-8. Configuration File in TFTP Server, with DHCP/Bootp Specified as the IP Addressing Source
If you apply this configuration file to figure 8-7, switches 1 - 3 will still retain
their manually assigned IP addressing. However, switch 4 will be configured
with the IP addressing included in the file.
8-18
Configuring IP Addressing
IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads
ProCurve# show run
Running configuration:
; J8715A Configuration Editor;
hostname "ProCurve"
module 1 type J8702A
module 2 type J8705A
trunk A11-A12 Trk1 Trunk
ip default-gateway 10.10.10.115
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1,A7-A10,A13-A24,B1-B24,Trk1
ip address 10.12.17.175 255.255.255.0
tagged A4-A6
no untagged A2-A3
exit
vlan 2
name "VLAN2"
untagged A2-A3
no ip address
exit
spanning-tree Trk1 priority 4
password manager
password operator
Because switch 4 (figure 8-7) received
its most recent IP addressing from a
DHCP/Bootp server, the switch
ignores the ip preserve command and
implements the IP addressing
included in this file.
Figure 8-9. Configuration File in TFTP Server, with Dedicated IP Addressing Instead of DHCP/Bootp
To summarize the IP Preserve effect on IP addressing:
■
If the switch received its most recent VLAN 1 IP addressing from a DHCP/
Bootp server, it ignores the IP Preserve command when it downloads the
configuration file, and implements whatever IP addressing instructions
are in the configuration file.
■
If the switch did not receive its most recent VLAN 1 IP addressing from a
DHCP/Bootp server, it retains its current IP addressing when it downloads
the configuration file.
■
The content of the downloaded configuration file determines the IP
addresses and subnet masks for other VLANs.
8-19
9
Time Protocols
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
TimeP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
SNTP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Selecting a Time Synchronization Protocol or Turning Off Time
Protocol Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
General Steps for Running a Time Protocol on the Switch: . . . . . . . . 9-3
Disabling Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
SNTP: Viewing, Selecting, and Configuring . . . . . . . . . . . . . . . . . . . . . 9-4
Menu: Viewing and Configuring SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
CLI: Viewing and Configuring SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Viewing the Current SNTP Configuration . . . . . . . . . . . . . . . . . . . . 9-8
Configuring (Enabling or Disabling) the SNTP Mode . . . . . . . . . 9-10
TimeP: Viewing, Selecting, and Configuring . . . . . . . . . . . . . . . . . . . . 9-16
Menu: Viewing and Configuring TimeP . . . . . . . . . . . . . . . . . . . . . . . . 9-17
CLI: Viewing and Configuring TimeP . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Viewing the Current TimeP Configuration . . . . . . . . . . . . . . . . . . 9-19
Configuring (Enabling or Disabling) the TimeP Mode . . . . . . . . 9-20
SNTP Unicast Time Polling with Multiple SNTP Servers . . . . . . . . 9-25
Displaying All SNTP Server Addresses Configured on the Switch . . 9-25
Adding and Deleting SNTP Server Addresses . . . . . . . . . . . . . . . . . . . 9-26
Menu: Operation with Multiple SNTP Server Addresses
Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
SNTP Messages in the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
9-1
Time Protocols
Overview
Overview
This chapter describes:
■
SNTP Time Protocol Operation
■
Timep Time Protocol Operation
Using time synchronization ensures a uniform time among interoperating
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).
Notes
■
Although you can create and save configurations for both time protocols without conflicts, the switch allows only one active time protocol
at any time.
■
In the factory-default configuration, the time synchronization option
is set to TimeP, with the TimeP mode itself set to Disabled.
TimeP Time Synchronization
You can either manually assign the switch to use a TimeP server or use DHCP
to assign the TimeP server. In either case, the switch can get its time synchronization updates from only one, designated Timep server. This option
enhances security by specifying which time server to use.
SNTP Time Synchronization
SNTP provides two operating modes:
■
9-2
Broadcast Mode: The switch acquires time updates by accepting the
time value from the first SNTP time broadcast detected. (In this case,
the SNTP server must be configured to broadcast time updates to the
network broadcast address. Refer to the documentation provided
with your SNTP server application.) Once the switch detects a particular 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.
Time Protocols
Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation
Note
To use Broadcast mode, the switch and the SNTP server must be in the same
subnet.
■
Unicast Mode: The switch requests a time update from the configured SNTP server. (You can configure one server using the menu
interface, or up to three servers using the CLI sntp server command.)
This option provides increased security over the Broadcast mode by
specifying which time server to use instead of using the first one
detected through a broadcast.
Selecting a Time Synchronization
Protocol or Turning Off Time Protocol
Operation
General Steps for Running a Time Protocol on the Switch:
1.
Select the time synchronization protocol: SNTP or TimeP (the default).
2.
Enable the protocol. The choices are:
3.
•
SNTP: Broadcast or Unicast
•
TimeP: DHCP or Manual
Configure the remaining parameters for the time protocol you selected.
The switch retains the parameter settings for both time protocols even if
you change from one protocol to the other. Thus, if you select a time
protocol, the switch uses the parameters you last configured for the
selected protocol.
Note that simply selecting a time synchronization protocol does not enable
that protocol on the switch unless you also enable the protocol itself (step 2,
above). For example, in the factory-default configuration, TimeP is the
selected time synchronization method. However, because TimeP is disabled
in the factory-default configuration, no time synchronization protocol is
running.
Disabling Time Synchronization
You can use either of the following methods to disable time synchronization
without changing the Timep or SNTP configuration:
9-3
Time Protocols
SNTP: Viewing, Selecting, and Configuring
■
In the System Information screen of the Menu interface, set the Time
Synch Method parameter to None, then press [Enter], then [S] (for Save).
■
In the Global config level of the CLI, execute no timesync.
SNTP: Viewing, Selecting, and
Configuring
SNTP Feature
Default
CLI
Web
view the SNTP time synchronization configuration
n/a
page 9-5
page 9-8
—
select SNTP as the time synchronization method
timep
page 9-6
page 9-10 ff.
—
disable time synchronization
timep
page 9-6
page 9-14
—
enable the SNTP mode (Broadcast, Unicast, or Disabled)
disabled
—
broadcast
n/a
page 9-6
page 9-11
—
unicast
n/a
page 9-6
page 9-11
—
none/disabled
n/a
page 9-6
page 9-15
—
page 9-6
page 9-11 ff.
—
configure an SNTP server address (for Unicast mode only) none
9-4
Menu
change the SNTP server version (for Unicast mode only)
3
page 9-7
page 9-13
—
change the SNTP poll interval
720 seconds
page 9-7
page 9-14
—
change the server priority
n/a
page 9-14
—
—
Time Protocols
SNTP: Viewing, Selecting, and Configuring
Table 9-1. SNTP Parameters
SNTP Parameter Operation
Time Sync
Method
Used to select either SNTP, TIMEP, or None as the time synchronization method.
SNTP Mode
Disabled
The Default. SNTP does not operate, even if specified by the Menu interface Time Sync Method
parameter or the CLI timesync command.
Unicast
Directs the switch to poll a specific server for SNTP time synchronization. Requires at least one server
address.
Broadcast
Directs the switch to acquire its time synchronization from data broadcast by any SNTP server to the
network broadcast address. The switch uses the first server detected and ignores any others.
However, if the Poll Interval expires three times without the switch detecting a time update from the
original server, it the switch accepts a broadcast time update from the next server it detects.
Poll Interval
(seconds)
In Unicast Mode: Specifies how often the switch polls the designated SNTP server for a time update.
In Broadcast Mode: Specifies how often the switch polls the network broadcast address for a time
update.
Value between 30-720 seconds.
Server Address
Used only when the SNTP Mode is set to Unicast. Specifies the IP address of the SNTP server that
the switch accesses for time synchronization updates. You can configure up to three servers; one
using the menu or CLI, and two more using the CLI. Refer to “SNTP Unicast Time Polling with Multiple
SNTP Servers” on page 9-25.
Server Version
Default: 3; range: 1 - 7. Specifies the SNTP software version to use, and is assigned on a per-server
basis. The version setting is backwards-compatible. For example, using version 3 means that the
switch accepts versions 1 through 3.
Priority
Specifies the order in which the configured servers are polled for getting the time. Value is between
1 and 3.
Menu: Viewing and Configuring SNTP
To View, Enable, and Modify SNTP Time Protocol:
1.
From the Main Menu, select:
2. Switch Configuration...
1. System Information
9-5
Time Protocols
SNTP: Viewing, Selecting, and Configuring
==========================- CONSOLE - MANAGER MODE -========================
Switch Configuration - System Information
System Name : ProCurve
System Contact :
System Location :
Inactivity Timeout (min) [0] : 0
Inbound Telnet Enabled [Yes] : Yes
Time Sync Method [None] : TIMEP
TimeP Mode [Disabled] : Disabled
Tftp-enable [Yes] : Yes
Time Zone [0] : 0
Daylight Time Rule [None] : None
Actions->
Cancel
Edit
MAC Age Time (sec) [300] : 300
Web Agent Enabled [Yes] : Yes
Server Address :
Jumbo Max Frame Size [9216] : 9216
Jumbo IP MTU [9198] : 9198
Save
Help
Time Protocol Selection Parameter
– TIMEP
– SNTP
– None
Figure 9-1. The System Information Screen (Default Values)
2.
Press [E] (for Edit). The cursor moves to the System Name field.
3.
Use [v] to move the cursor to the Time Sync Method field.
4.
Use the Space bar to select SNTP, then press [v] once to display and move
to the SNTP Mode field.
5.
Do one of the following:
•
Use the Space bar to select the Broadcast mode, then press [v] to
move the cursor to the Poll Interval field, and go to step 6. (For
Broadcast mode details, refer to “SNTP Operating Modes” on
page 9-2.)
Time Sync Method [None] : SNTP
SNTP Mode [Disabled] : Broadcast
Poll Interval (sec) [720] : 720
Tftp-enable [Yes] : Yes
Time Zone [0] : 0
Daylight Time Rule [None] : None
Figure 9-2. Time Configuration Fields for SNTP with Broadcast Mode
•
Use the Space bar to select the Unicast mode, then do the
following:
i.
Press [>] to move the cursor to the Server Address field.
ii. Enter the IP address of the SNTP server you want the switch to
use for time synchronization.
9-6
Time Protocols
SNTP: Viewing, Selecting, and Configuring
Note: This step replaces any previously configured server IP
address. If you will be using backup SNTP servers (requires use
of the CLI), then refer to “SNTP Unicast Time Polling with
Multiple SNTP Servers” on page 9-25.
iii. Press [v] to move the cursor to the Server Version field. Enter the
value that matches the 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 3 and testing SNTP operation to determine
whether any change is necessary.
Note: Using the menu to enter the IP address for an SNTP server
when the switch already has one or more SNTP servers configured causes the switch to delete the primary SNTP server from
the server list and to select a new primary SNTP server from the
IP address(es) in the updated list. For more on this topic, refer to
“SNTP Unicast Time Polling with Multiple SNTP Servers” on page
9-25.
iv. Press [>] to move the cursor to the Poll Interval field, then go to
step 6.
Time Sync Method [None] : SNTP
SNTP Mode [Disabled] : Unicast
Poll Interval (sec) [720] : 720
Tftp-enable [Yes] : Yes
Time Zone [0] : 0
Daylight Time Rule [None] : None
Server Address : 10.28.227.15
Server Version [3] : 3
Note: The Menu interface lists only the highest priority SNTP server, even if others are configured. To view all SNTP servers configured
on the switch, use the CLI show management command. Refer to “SNTP Unicast Time Polling with Multiple SNTP Servers” on page
9-25.
Figure 9-3. SNTP Configuration Fields for SNTP Configured with Unicast Mode
6.
In the Poll Interval field, enter the time in seconds that you want for a Poll
Interval. (For Poll Interval operation, see table 9-1, “SNTP Parameters”,
on page 9-5.)
7.
Press [Enter] to return to the Actions line, then [S] (for Save) to enter the
new time protocol configuration in both the startup-config and runningconfig files.
9-7
Time Protocols
SNTP: Viewing, Selecting, and Configuring
CLI: Viewing and Configuring SNTP
CLI Commands Described in this Section
SNTP Command
show sntp
Page
9-8
[no] timesync
9-10 and ff.,
9-14
sntp broadcast
9-11
sntp unicast
9-11
sntp server
9-11 and ff.
Protocol Version
9-13
Priority
9-14
poll-interval
9-14
no sntp
9-15
This section describes how to use the CLI to view, enable, and configure SNTP
parameters.
Viewing the Current SNTP Configuration
Syntax: show sntp
This command lists both the time synchronization method
(TimeP, SNTP, or None) and the SNTP configuration, even if
SNTP is not the selected time protocol.
For example, if you configured the switch with SNTP as the time
synchronization method, then enabled SNTP in broadcast mode with the
default poll interval, show sntp lists the following:
9-8
Time Protocols
SNTP: Viewing, Selecting, and Configuring
ProCurve(config)# show sntp
SNTP Configuration
Time Sync Mode: Sntp
SNTP Mode : Unicast
Poll Interval (sec) [720] : 719
Priority
-------1
2
3
SNTP Server Address
------------------------------2001:db8::215:60ff:fe79:8980
10.255.5.24
fe80::123%vlan10
OOBM
Protocol Version
------------- ---------------No
7
Yes
3
Yes
3
Figure 9-4. Example of SNTP Configuration When SNTP Is the Selected Time Synchronization Method
In the factory-default configuration (where TimeP is the selected time
synchronization method), show sntp still lists the SNTP configuration even
though it is not currently in use. For example:
ProCurve(config)# show sntp
Even though, in this example, TimeP is the
current time synchronous method, the
switch maintains the SNTP configuration.
SNTP Configuration
Time Sync Mode: Timep
SNTP Mode : Unicast
Poll Interval (sec) [720] : 719
Priority
-------1
2
3
SNTP Server Address
------------------------------2001:db8::215:60ff:fe79:8980
10.255.5.24
fe80::123%vlan10
OOBM
Protocol Version
------------- ---------------No
7
Yes
3
Yes
3
Figure 9-5. Example of SNTP Configuration When SNTP Is Not the Selected Time Synchronization Method
Syntax: show management
This command can help you to easily examine and compare
the IP addressing on the switch. It lists the IP addresses for
all time servers configured on the switch, plus the IP addresses
and default gateway for all VLANs configured on the switch.
9-9
Time Protocols
SNTP: Viewing, Selecting, and Configuring
ProCurve(config)# show management
Status and Counters - Management Address Information
Time Server Address : fe80::215:60ff:fe7a:adc0%vlan10
Priority
-------1
2
3
SNTP Server Address
---------------------------------------------2001:db8::215:60ff:fe79:8980
10.255.5.24
fe80::123%vlan10
Default Gateway
VLAN Name
-----------DEFAULT_VLAN
VLAN10
Protocol Version
---------------7
3
3
: 10.0.9.80
MAC Address
------------------001279-88a100
001279-88a100
|
+
|
|
IP Address
------------------Disabled
10.0.10.17
Figure 9-6. Example of Display Showing IP Addressing for All Configured Time Servers and VLANs
Configuring (Enabling or Disabling) the SNTP Mode
Enabling the SNTP mode means to configure it for either broadcast or unicast
mode. Remember that to run SNTP as the switch’s time synchronization
protocol, you must also select SNTP as the time synchronization method by
using the CLI timesync command (or the Menu interface Time Sync Method
parameter).
Syntax: timesync sntp
Selects SNTP as the time protocol.
sntp < broadcast | unicast >
Enables the SNTP mode (below and page 9-11).
Syntax: sntp server < ip-addr >
Required only for unicast mode page 9-11).
Syntax: sntp server priority <1 - 3 >
Specifies the order in which the configured servers are polled
for getting the time. Value is between 1 and 3.
Syntax: sntp poll-interval < 30 - 720 >
Enabling the SNTP mode also enables the SNTP poll interval
(default: 720 seconds; page 9-14).
9-10
Time Protocols
SNTP: Viewing, Selecting, and Configuring
Enabling SNTP in Broadcast Mode. Because the switch provides an SNTP
polling interval (default: 720 seconds), you need only these two commands
for minimal SNTP broadcast configuration:
Syntax: timesync sntp
Selects SNTP as the time synchronization method.
Syntax: sntp broadcast
Configures broadcast as the SNTP mode.
For example, suppose:
■
Time synchronization is in the factory-default configuration (TimeP
is the currently selected time synchronization method).
■
You want to:
1. View the current time synchronization.
2. Select SNTP as the time synchronization mode.
3. Enable SNTP for Broadcast mode.
4. View the SNTP configuration again to verify the configuration.
The commands and output would appear as follows:
1
show sntp displays the SNTP configuration and also shows that
TimeP is the currently active time synchronization mode.
2
3
4
show sntp again displays the SNTP configuration and shows that
SNTP is now the currently active time synchronization mode and is
configured for broadcast operation.
4
Figure 9-7. Example of Enabling SNTP Operation in Broadcast Mode
Enabling SNTP in Unicast Mode. Like broadcast mode, configuring SNTP
for unicast mode enables SNTP. However, for Unicast operation, you must
also specify the IP address of at least one SNTP server. The switch allows up
to three unicast servers. You can use the Menu interface or the CLI to configure
one server or to replace an existing Unicast server with another. To add a
9-11
Time Protocols
SNTP: Viewing, Selecting, and Configuring
second or third server, you must use the CLI. For more on SNTP operation
with multiple servers, refer to “SNTP Unicast Time Polling with Multiple SNTP
Servers” on page 9-25.
Syntax: timesync sntp
Selects SNTP as the time synchronization method.
Syntax: sntp unicast
Configures the SNTP mode for Unicast operation.
Syntax: sntp server <ip-addr> [version]
Specifies the SNTP server. Server version values are between
1 and 7. The default server version is 3.
Syntax: sntp server priority <1 - 3 >
Specifies the order in which the configured SNTP servers are
polled for getting the time. Value is between 1 and 3.
Syntax: [no] sntp server priority <1-3> <ip-address> [oobm] [version]
Use the no version of the command to disable SNTP.
priority specifies the order in which the configured SNTP serv-
ers are polled for the time; allowable values are 1 through 3.
ip-address is an IPv4 or IPv6 address of an SNTP server.
For switches that have a separate out-of-band management
port, oobm specifies that SNTP traffic goes through that port.
(By default, SNTP traffic goes through the data ports.)
version is the protocol version of the SNTP server. Allowable
values are 1 through 7; default is 3.
Syntax: no sntp server < ip-addr >
Deletes the specified SNTP server.
Note
Deleting an SNTP server when only one is configured disables SNTP unicast
operation.
For example, to select SNTP and configure it with unicast mode and an SNTP
server at 10.28.227.141 with the default server version (3) and default poll
interval (720 seconds):
ProCurve(config)# timesync sntp
Selects SNTP.
9-12
Time Protocols
SNTP: Viewing, Selecting, and Configuring
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).
.
ProCurve(config)# show sntp
SNTP Configuration
Time Sync Mode: Sntp
SNTP Mode : Unicast
Poll Interval (sec) [720] : 720
Priority
-------1
2
3
In this example, the Poll Interval and the Protocol
Version appear at their default settings.
Both IPv4 and IPv6 addresses are displayed.
Note: Protocol Version appears only when there is an
IP address configured for an SNTP server.
SNTP Server Address
------------------------------2001:db8::215:60ff:fe79:8980
10.255.5.24
fe80::123%vlan10
OOBM
Protocol Version
------------- ---------------No
7
Yes
3
Yes
3
Figure 9-8. Example of Configuring SNTP for Unicast Operation
If the SNTP server you specify uses SNTP version 4 or later, use the sntp server
command to specify the correct version number. For example, suppose you
learned that SNTP version 4 was in use on the server you specified above (IP
address 10.28.227.141). You would use the following commands to delete the
server IP address and then re-enter it with the correct version number for that
server:
Deletes unicast SNTP server entry.
Re-enters the unicast server with a nondefault protocol version.
show sntp displays the result.
Figure 9-9. Example of Specifying the SNTP Protocol Version Number
9-13
Time Protocols
SNTP: Viewing, Selecting, and Configuring
Changing the SNTP Poll Interval.
Syntax:
sntp poll-interval < 30..720 >
Specifies how long the switch waits between time polling
intervals. The default is 720 seconds and the range is 30 to
720 seconds. (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
Changing the Priority. You can choose the order in which configured
servers are polled for getting the time by setting the server priority.
Syntax: sntp server priority <1 - 3> <ip-address>
Specifies the order in which the configured servers are polled
for getting the time. Value is between 1 and 3.
Note: Both IPv4 and IPv6 addresses can be entered. For more
information about IPv6 addresses, see the “IPv6 Configuration Guide” for your switch.
For example, to set one server to priority 1 and another to priority 2:
ProCurve(config)# sntp server priority 1 10.28.22.141
ProCurve(config)# sntp server priority 2
2001:db8::215:60ff:fe79:8980
Disabling Time Synchronization Without Changing the SNTP
Configuration. The recommended method for disabling time synchronization is to use the timesync command.
Syntax: no timesync
Halts time synchronization without changing your SNTP
configuration.
For example, suppose SNTP is running as the switch’s time synchronization
protocol, with Broadcast as the SNTP mode and the factory-default polling
interval. You would halt time synchronization with this command:
ProCurve(config)# no timesync
If you then viewed the SNTP configuration, you would see the following:
9-14
Time Protocols
SNTP: Viewing, Selecting, and Configuring
Figure 9-10. Example of SNTP with Time Synchronization Disabled
Disabling the SNTP Mode. If you want to prevent SNTP from being used
even if selected by timesync (or the Menu interface’s Time Sync Method parameter), configure the SNTP mode as disabled.
Syntax: no sntp
Disables SNTP by changing the SNTP mode configuration to
Disabled.
For example, if the switch is running SNTP in Unicast mode with an SNTP
server at 10.28.227.141 and a server version of 3 (the default), no sntp changes
the SNTP configuration as shown below, and disables time synchronization
on the switch.
Even though the Time Sync Mode is set to Sntp,
time synchronization is disabled because no
sntp has disabled the SNTP Mode parameter.
Figure 9-11. Example of Disabling Time Synchronization by Disabling the SNTP Mode
9-15
Time Protocols
TimeP: Viewing, Selecting, and Configuring
TimeP: Viewing, Selecting, and
Configuring
TimeP Feature
Default
Menu
CLI
Web
view the Timep time synchronization configuration
n/a
page 9-17
page 9-19
—
select Timep as the time synchronization method
TIMEP
page 9-15
pages 9-21 ff.
—
disable time synchronization
timep
page 9-17
page 9-23
—
enable the Timep mode
Disabled
—
DHCP
—
page 9-17
page 9-21
—
manual
—
page 9-17
page 9-22
—
none/disabled
—
page 9-17
page 9-24
—
page 9-18
page 9-23
—
change the SNTP poll interval
720 minutes
Table 9-2. Timep Parameters
SNTP Parameter Operation
Time Sync
Method
Used to select either TIMEP (the default), SNTP, or None as the time synchronization method.
Timep Mode
Disabled
The Default. Timep does not operate, even if specified by the Menu interface Time Sync Method
parameter or the CLI timesync command.
DHCP
When Timep is selected as the time synchronization method, the switch attempts to acquire a Timep
server IP address via DHCP. If the switch receives a server address, it polls the server for updates
according to the Timep poll interval. If the switch does not receive a Timep server IP address, it cannot
perform time synchronization updates.
Manual
When Timep is selected as the time synchronization method, the switch attempts to poll the specified
server for updates according to the Timep poll interval. If the switch fails to receive updates from the
server, time synchronization updates do not occur.
Server
Address
9-16
Used only when the TimeP Mode is set to Manual. Specifies the IP address of the TimeP server that
the switch accesses for time synchronization updates. You can configure one server.
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
==========================- CONSOLE - MANAGER MODE -==========================
Switch Configuration - System Information
System Name : ProCurve
System Contact :
System Location :
Inactivity Timeout (min) [0] : 0
Inbound Telnet Enabled [Yes] : Yes
Time Sync Method [None] : TIMEP
TimeP Mode [Disabled] : Disabled
Tftp-enable [Yes] : Yes
Time Zone [0] : 0
Daylight Time Rule [None] : None
Actions->
Cancel
Edit
MAC Age Time (sec) [300] : 300
Web Agent Enabled [Yes] : Yes
Save
Time Protocol Selection Parameter
– TIMEP (the default)
– SNTP
– None
Help
Figure 9-12. The System Information Screen (Default Values)
Press [E] (for Edit). The cursor moves to the System Name field.
2.
Use [v] to move the cursor to the Time Sync Method field.
3.
If TIMEP is not already selected, use the Space bar to select TIMEP, then
press [v] once to display and move to the TimeP Mode field.
4.
Do one of the following:
•
Use the Space bar to select the DHCP mode, then press [v] to move
the cursor to the Poll Interval field, and go to step 6.
•
Use the Space bar to select the Manual mode.
i.
Press [>] to move the cursor to the Server Address field.
9-17
Time Protocols
TimeP: Viewing, Selecting, and Configuring
ii. Enter the IP address of the TimeP server you want the switch to
use for time synchronization.
Note: This step replaces any previously configured TimeP server
IP address.
iii. Press [>] to move the cursor to the Poll Interval field, then go to
step 6.
5.
In the Poll Interval field, enter the time in minutes that you want for a
TimeP Poll Interval.
Press [Enter] to return to the Actions line, then [S] (for Save) to enter the new
time protocol configuration in both the startup-config and running-config
files.
CLI: Viewing and Configuring TimeP
CLI Commands Described in this Section
Command
Page
show timep
9-19
[no] timesync
9-20 ff., 9-23
ip timep
dhcp
9-21
manual
9-22
server <ip-addr>
9-22
interval
9-23
no ip timep
9-24
This section describes how to use the CLI to view, enable, and configure TimeP
parameters.
9-18
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Viewing the Current TimeP Configuration
Using different show commands, you can display either the full TimeP configuration or a combined listing of all TimeP, SNTP, and VLAN IP addresses
configured on the switch.
Syntax: show timep
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. (If the TimeP Mode is
set to Disabled or DHCP, then the Server field does not appear.)
For example, if you configure the switch with TimeP as the time synchronization method, then enable TimeP in DHCP mode with the default poll interval,
show timep lists the following:
ProCurve (config)# show timep
Timep Configuration
Time Sync Mode: Timep
TimeP Mode [Disabled] : Manual
Server Address : 10.10.28.100
Poll Interval (min) [720] : 720
OOBM : Yes
Figure 9-13. Example of TimeP Configuration When TimeP Is the Selected Time
Synchronization Method
If SNTP is the selected time synchronization method, show timep still lists the
TimeP configuration even though it is not currently in use:
ProCurve (config)# show timep
Timep Configuration
Time Sync Mode: Sntp
TimeP Mode [Disabled] : Manual
Server Address : 10.10.28.100
Poll Interval (min) [720] : 720
OOBM : Yes
Even though, in this example, SNTP is the
current time synchronization method, the
switch maintains the TimeP
configuration.
Figure 9-14. Example of TimeP Configuration When TimeP Is Not the Selected
Time Synchronization Method
9-19
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Syntax: show management
This command can help you to easily examine and compare
the IP addressing on the switch. It lists the IP addresses for
all time servers configured on the switch, plus the IP addresses
and default gateway for all VLANs configured on the switch.
ProCurve(config)# show management
Status and Counters - Management Address Information
Time Server Address : 10.10.28.100
Priority
-------1
2
3
SNTP Server Address
---------------------------------------------10.10..28.101
10.255.5.24
fe80::123%vlan10
Default Gateway
VLAN Name
-----------DEFAULT_VLAN
VLAN10
Protocol Version
---------------3
3
3
: 10.0.9.80
MAC Address
------------------001279-88a100
001279-88a100
|
+
|
|
IP Address
------------------10.30.248.184
10.0.10.17
Figure 9-15. Example of Display Showing IP Addressing for All Configured Time Servers and VLANs
Configuring (Enabling or Disabling) the TimeP Mode
Enabling the TimeP mode means to configure it for either broadcast or unicast
mode. Remember that to run TimeP as the switch’s time synchronization
protocol, you must also select TimeP as the time synchronization method by
using the CLI timesync command (or the Menu interface Time Sync Method
parameter).
Syntax: timesync timep
Selects TimeP as the time protocol.
Syntax: ip timep < dhcp | manual >
Enables the selected TimeP mode.
Syntax: no ip timep
Disables the TimeP mode.
Syntax: no timesync
Disables the time protocol.
9-20
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Enabling TimeP in DHCP Mode. Because the switch provides a TimeP
polling interval (default: 720 minutes), you need only these two commands for
a minimal TimeP DHCP configuration:
Syntax: timesync timep
Selects TimeP as the time synchronization method.
Syntax: ip timep dhcp
Configures DHCP as the TimeP mode.
For example, suppose:
■
Time synchronization is configured for SNTP.
■
You want to:
1. View the current time synchronization.
2. Select TimeP as the time synchronization mode.
3. Enable TimeP for DHCP mode.
4. View the TimeP configuration.
The commands and output would appear as follows:
1
show timep displays the TimeP configuration and also shows
that SNTP is the currently active time synchronization mode.
2
3
4
show timep again displays the TimeP configuration and shows that TimeP is
now the currently active time synchronization mode.
Figure 9-16. Example of Enabling TimeP Operation in DHCP Mode
9-21
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Enabling Timep in Manual Mode. Like DHCP mode, configuring TimeP for
Manual mode enables TimeP. However, for manual operation, you must also
specify the IP address of the TimeP server. (The switch allows only one TimeP
server.) To enable the TimeP protocol:
Syntax: timesync timep
Selects Timep.
Syntax: ip timep manual < ip-addr > [oobm]
Activates TimeP in Manual mode with a specified TimeP
server.
For switches that have a separate out-of-band management
port, oobm specifies that TimeP traffic goes through that port.
(By default, TimeP traffic goes through the data ports.)
Syntax: no ip timep
Disables TimeP.
Note
To change from one TimeP server to another, you must (1) use the no ip timep
command to disable TimeP mode, and then reconfigure TimeP in Manual
mode with the new server IP address.
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-22
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Figure 9-17. Example of Configuring Timep for Manual Operation
Changing the TimeP Poll Interval. This command lets you specify how
long the switch waits between time polling intervals. The default is 720
minutes and the range is 1 to 9999 minutes. (This parameter is separate from
the poll interval parameter used for SNTP operation.)
Syntax: ip timep < dhcp | manual > interval < 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 synchronization is to use the timesync command. This halts time synchronization without
changing your TimeP configuration.
Syntax: no timesync
Disables time synchronization by changing the Time Sync
Mode configuration to Disabled.
For example, suppose TimeP is running as the switch’s time synchronization
protocol, with DHCP as the TimeP mode, and the factory-default polling
interval. You would halt time synchronization with this command:
ProCurve(config)# no timesync
If you then viewed the TimeP configuration, you would see the following:
9-23
Time Protocols
TimeP: Viewing, Selecting, and Configuring
Figure 9-18. Example of TimeP with Time Synchronization Disabled
Disabling the TimeP Mode. Disabling the TimeP mode means to configure
it as disabled. (Disabling TimeP prevents the switch from using it as the time
synchronization protocol, even if it is the selected Time Sync Method option.)
Syntax: no ip timep
Disables TimeP by changing the TimeP mode configuration
to Disabled.
For example, if the switch is running TimeP in DHCP mode, no ip timep changes
the TimeP configuration as shown below, and disables time synchronization.
Even though the Time Sync Mode is set to Timep,
time synchronization is disabled because no ip
timep has disabled the TimeP Mode parameter.
Figure 9-19. Example of Disabling Time Synchronization by Disabling the TimeP Mode
Parameter
9-24
Time Protocols
SNTP Unicast Time Polling with Multiple SNTP Servers
SNTP Unicast Time Polling with Multiple
SNTP Servers
When running SNTP unicast time polling as the time synchronization method,
the switch requests a time update from the server you configured with either
the Server Address parameter in the menu interface, or the primary server in
a list of up to three SNTP servers configured using the CLI. If the switch does
not receive a response from the primary server after three consecutive polling
intervals, the switch tries the next server (if any) in the list. If the switch tries
all servers in the list without success, it sends an error message to the Event
Log and reschedules to try the address list again after the configured Poll
Interval time has expired.
Displaying All SNTP Server Addresses Configured on
the Switch
The System Information screen in the menu interface displays only one SNTP
server address, even if the switch is configured for two or three servers. The
CLI show management command displays all configured SNTP servers on the
switch.
ProCurve(config)# show management
Status and Counters - Management Address Information
Time Server Address : fe80::215:60ff:fe7a:adc0%vlan10
Priority
-------1
2
3
SNTP Server Address
---------------------------------------------2001:db8::215:60ff:fe79:8980
10.255.5.24
fe80::123%vlan10
Default Gateway
VLAN Name
-----------DEFAULT_VLAN
VLAN10
Protocol Version
---------------7
3
3
: 10.0.9.80
MAC Address
------------------001279-88a100
001279-88a100
|
+
|
|
IP Address
------------------Disabled
10.0.10.17
Figure 9-20. Example of How To List All SNTP Servers Configured on the Switch
9-25
Time Protocols
SNTP Messages in the Event Log
Adding and Deleting SNTP Server Addresses
Adding Addresses. As mentioned earlier, you can configure one SNTP
server address using either the Menu interface or the CLI. To configure a
second and third address, you must use the CLI. To configure the remaining
two addresses, you would do the following:
ProCurve(config)# sntp server 2001:db8::215:60ff:fe79:8980
ProCurve(config)# sntp server 10.255.5.24
Figure 9-21. Example of Creating Additional SNTP Server Addresses with the CLI
Note
If there are already three SNTP server addresses configured on the switch,
and you want to use the CLI to replace one of the existing addresses with a
new one, you must delete the unwanted address before you configure the new
one.
Deleting Addresses. To delete an address, you must use the CLI. If there are
multiple addresses and you delete one of them, the switch re-orders the
address priority.
Syntax: no sntp server < 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: 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.
SNTP Messages in the Event Log
If an SNTP time change of more than three seconds occurs, the switch’s event
log records the change. SNTP time changes of less than three seconds do not
appear in the Event Log.
9-26
10
Port Status and Configuration
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Viewing Port Status and Configuring Port Parameters . . . . . . . . . . 10-3
Menu: Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
CLI: Viewing Port Status and Configuring Port Parameters . . . . . . . 10-8
Viewing Port Status and Configuration . . . . . . . . . . . . . . . . . . . . . 10-8
Customizing the Show Interfaces Command . . . . . . . . . . . . . . . . . . . 10-10
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Note on Using Pattern Matching with the “Show Interfaces Custom”
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Viewing Port Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Viewing Transceiver Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Enabling or Disabling Ports and Configuring Port Mode . . . . . . . . . 10-15
Enabling or Disabling Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Configuring a Broadcast Limit on the Switch . . . . . . . . . . . . . . . . . . 10-18
Configuring ProCurve Auto-MDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Web: Viewing Port Status and Configuring Port Parameters . . . . . 10-22
Using Friendly (Optional) Port Names . . . . . . . . . . . . . . . . . . . . . . . 10-23
Configuring and Operating Rules for Friendly Port Names . . . . . . . 10-23
Configuring Friendly Port Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Displaying Friendly Port Names with Other Port Data . . . . . . . . . . 10-25
Configuring Transceivers and Modules That Haven’t
Been Inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Clearing the Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Uni-Directional Link Detection (UDLD) . . . . . . . . . . . . . . . . . . . . . . 10-31
10-1
Port Status and Configuration
Contents
Configuring UDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Enabling UDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Changing the Keepalive Interval . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Changing the Keepalive Retries . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Configuring UDLD for Tagged Ports . . . . . . . . . . . . . . . . . . . . . . 10-34
Viewing UDLD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Configuration Warnings and Event Log Messages . . . . . . . . . . . . . . 10-37
10-2
Port Status and 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
■
Friendly Port Names
■
Uni-directional Link Detection (UDLD)
Viewing Port Status and Configuring Port
Parameters
Port Status and Configuration Features
Feature
Default
Menu
CLI
Web
viewing port status
n/a
page 10-6
page 10-8
page 10-22
viewing transceiver status
n/a
n/a
page 10-14
page 10-22
configuring ports
Refer to Table
10-1 on pages
10-4 thru 10-5
page 10-7
page 10-15
page 10-22
configuring ProCurve auto-mdix
Note On Connecting
Transceivers to
Fixed-Configuration
Devices
page 9-11
If the switch either fails to show a link between an installed transceiver and
another device, or demonstrates errors or other unexpected behavior on the
link, check the port configuration on both devices for a speed and/or duplex
(mode) mismatch.
■
To check the mode setting for a port on the switch, use either the Port
Status screen in the menu interface (page 10-6) or show interfaces brief in
the CLI (page 10-8).
To display information about the transceivers installed on a switch, enter the
show tech receivers command in the CLI (page 10-14).
10-3
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Table 10-1. Status and Parameters for Each Port Type
Status or
Parameter
Description
Enabled
Yes (default): The port is ready for a network connection.
No: The port will not operate, even if properly connected in a network. Use this setting, for example, if
the port needs to be shut down for diagnostic purposes or while you are making topology changes.
Status
(read-only)
Up: The port senses a link beat.
Down: The port is not enabled, has no cables connected, or is experiencing a network error. For
troubleshooting information, refer to the Installation and Getting Started Guide you received with the
switch. Refer also to Appendix C, “Troubleshooting” (in this manual).
Mode
The port’s speed and duplex (data transfer operation) setting.
10/100/1000Base-T Ports:
• Auto-MDIX (default): Senses speed and negotiates with the port at the other end of the link for port
operation (MDI-X or MDI).
To see what the switch negotiates for the Auto setting, use the CLI show interfaces brief command
or the “3. Port Status” option under “1. Status and Counters” in the menu interface.
• MDI: Sets the port to connect with a PC using a crossover cable (Manual mode—applies only to
copper port switches using twisted-pair copper Ethernet cables)
• MDIX: Sets the port to connect with a PC using a straight-through cable (Manual mode—applies only
to copper port switches using twisted-pair copper Ethernet cables)
• 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 Auto10 for links between 10/100 auto-sensing ports connected with Cat 3 cabling. (Cat 5 cabling is required
for 100 Mbps links.).
• 10HDx:10 Mbps, Half-Duplex
• 10FDx: 10 Mbps, Full-Duplex
• Auto-100: Uses 100 Mbps and negotiates with the port at the other end of the link for other port
operation features.
• Auto-10-100: Allows the port to establish a link with the port at the other end at either 10 Mbps or 100
Mbps, using the highest mutual speed and duplex mode available. Only these speeds are allowed with
this setting.
• Auto-1000: Uses 1000 Mbps and negotiates with the port at the other end of the link for other port
operation features.
• 100Hdx: Uses 100 Mbps, half-duplex.
• 100Fdx: Uses 100 Mbps, Full-Duplex
— Continued on Next Page —
10-4
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Status or
Parameter
Description
— Continued From Previous Page —
Gigabit Fiber-Optic Ports (Gigabit-SX, Gigabit-LX, and Gigabit-LH):
• 1000FDx: 1000 Mbps (1 Gbps), Full Duplex only
• Auto (default): The port operates at 1000FDx and auto-negotiates flow control with the device
connected to the port.
Gigabit Copper Ports:
• 1000FDx: 1000 Mbps (1 Gbps), Full Duplex only
• Auto (default): The port operates at 1000FDx and auto-negotiates flow control with the device
connected to the port.
10-Gigabit CX4 Copper Ports:
• Auto: The port operates at 10 gigabits FDx and negotiates flow control. Lower speed settings or halfduplex are not allowed.
10-Gigabit SC Fiber-Optic Ports (10-GbE SR, 10-GbE LR, 10-GbE ER):
• Auto: The port operates at 10 gigabits FDx and negotiates flow control. Lower speed settings or halfduplex are not allowed.
Note: Conditioning patch cord cables are not supported on 10-GbE.
Auto-MDIX
The switch supports Auto-MDIX on 10Mb, 100Mb, and 1 Gb T/TX (copper) ports. (Fiber ports and 10gigabit ports do not use this feature.)
• Automdix: Configures the port for automatic detection of the cable type (straight-through or
crossover).
• MDI: Configures the port to connect to a switch, hub, or other MDI-X device with a straight-through
cable.
• MDIX: Configures the port to connect to a PC or other MDI device with a straight-through cable.
Flow Control
• Disabled (default): The port does not generate flow control packets, and drops any flow control
packets it receives.
• Enabled: The port uses 802.3x Link Layer Flow Control, generates flow control packets, and processes
received flow control packets.
With the port mode set to Auto (the default) and Flow Control enabled, the switch negotiates Flow Control
on the indicated port. If the port mode is not set to Auto, or if Flow Control is disabled on the port, then
Flow Control is not used. Note that flow control must be enabled on both ends of a link.
Broadcast
Limit
Specifies the percentage of the theoretical maximum network bandwidth that can be used for broadcast
and multicast traffic. Any broadcast or multicast traffic exceeding that limit will be dropped. Zero (0)
means the feature is disabled.
The broadcast-limit command operates at the port context level to set the broadcast limit for a port on
the switch.
Note: This feature is not appropriate for networks that require high levels of IPX or RIP broadcast traffic.
10-5
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Menu: Port Configuration
From the menu interface, you can view and change the port configuration.
Using the Menu To View Port Configuration. The menu interface displays the configuration for ports and (if configured) any trunk groups.
From the Main Menu, select:
1. Status and Counters
4. Port Status
In this example,
ports A7 and A8
have previously
been configured
as a trunk group.
Figure 10-1. Example of a Switch Port Status Screen
10-6
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Using the Menu To Configure Ports.
You can configure and view the port settings by using the menu.
Note
The menu interface uses the same screen for configuring both individual ports
and port trunk groups. For information on port trunk groups, refer to Chapter
11, “Port Trunking” .
1.
From the Main Menu, Select:
2. Switch Configuration...
2. Port/Trunk Settings
An example of the Menu display is shown below.
===========================- TELNET - MANAGER MODE -=============
Switch Configuration - Port/Trunk Settings
Port
---A1
A2
A3
A4
A5
A6
A7
A8
Type
--------1000T
1000T
1000T
1000T
1000T
1000T
1000T
1000T
Actions->
+
|
|
|
|
|
|
|
|
Cancel
Enabled
------Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Edit
Mode
-----------Auto-10-100
Auto-10-100
Auto
Auto
Auto
Auto
Auto
Auto
Save
Flow Ctrl
--------Disable
Disable
Disable
Disable
Disable
Disable
Disable
Disable
Group
-----
Type
-----
Trk1
Trk2
Trunk
Trunk
Help
Cancel changes and return to previous screen.
Use arrow keys to change action selection and <Enter> to execute action.
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.
4.
When you have finished making changes to the above parameters, press
[Enter], then press [S] (for Save).
10-7
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
CLI: Viewing Port Status and Configuring Port
Parameters
From the CLI, you can configure and view all port parameter settings and view
all port status indicators.
Port Status and Configuration Commands
show interfaces brief
page 10-9
show interfaces config
page 10-9
show interfaces custom
page 10-10
show interfaces port-utilization
page 10-13
show tech transceivers
page 10-14
interface
page 10-15
disable/enable
page 10-15
speed-duplex
page 10-15
flow-control
page 10-17
broadcast-limit
page 10-18
auto-mdix
page 10-19
Viewing Port Status and Configuration
Use the following commands to display port status and configuration data.
Syntax: show interfaces [ brief | config | < port-list >]
brief: Lists the current operating status for all ports on the
switch.
config: Lists a subset of configuration data for all ports on the
switch; that is, for each port, the display shows whether the port
is enabled, the operating mode, and whether it is configured
for flow control.
< port-list >: Shows a summary of network traffic handled by the
specified ports.
An example of the show interfaces brief command is shown below.
10-8
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
ProCurve(config)# show interfaces brief
Status and Counters - Port Status
Port
----B1
B2
B3
B4
B5
B6
Type
--------100/1000T
100/1000T
100/1000T
100/1000T
100/1000T
100/1000T
|
|
+
|
|
|
|
|
|
Intrusion
Alert
--------No
No
No
No
No
No
Enabled
------Yes
Yes
Yes
Yes
Yes
Yes
Status
-----Down
Down
Down
Down
Down
Down
Mode
---------Auto-10-100
1000FDx
1000FDx
1000FDx
1000FDx
1000FDx
MDI
Mode
----Auto
Auto
Auto
Auto
Auto
Auto
Flow
Ctrl
----off
off
off
off
off
off
Bcast
Limit
-----0
0
0
0
0
0
Figure 10-3. Example of Show Interfaces Brief Command Listing
Use the show interfaces config command to view the port settings, as shown
below.
ProCurve(config)# show interfaces config
Port Settings
Port
----B1
B2
B3
B4
B5
B6
Type
--------100/1000T
100/1000T
100/1000T
100/1000T
100/1000T
100/1000T
|
+
|
|
|
|
|
|
Enabled
------Yes
Yes
Yes
Yes
Yes
Yes
Mode
-----------Auto-10-100
Auto
Auto
Auto
Auto
Auto
Flow Ctrl
--------Disable
Disable
Disable
Disable
Disable
Disable
MDI
---Auto
Auto
Auto
Auto
Auto
Auto
Figure 10-4. Example of a Show Interfaces Config Command Listing
The display option can be used to initiate the dynamic update of the show
interfaces command with the output being the same as the show interfaces
command. When using the display option in the CLI, the information stays on
the screen and is updated every 3 seconds, as occurs with the display using
the menu feature. The update is terminated with Cntl-C.
You can use the arrow keys to scroll through the screen when the output does
not fit in one screen.
10-9
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Syntax: show interfaces display
Initiates the dynamic update of a command. The output is the
same as the equivalent “show” command.The information is
updated every 3 seconds.
Note: Select “Back” to exit the display.
For example:
ProCurve# show interfaces display
Dynamically updates
Figure 10-5. Example of show interfaces display Command with Dynamically Updating Output
Customizing the Show Interfaces Command
You can create show commands displaying the information that you want to
see in any order you want by using the custom option.
10-10
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Syntax: show interfaces custom [port-list] column-list
Select the information that you want to display. Parameters
include:
■
port name
■
type
■
vlan
■
intrusion
■
enabled
■
status
■
speed
■
mdi
■
flow
Columns supported are:
Parameter Column
Displays
Examples
port
Port identifier
A2
type
Port type
100/1000T
status
Port status
up or down
speed
Connection speed and duplex
1000FDX
mode
Configured mode
auto, auto-100, 100FDX
mdi
MDI mode
auto, MDIX
flow
Flow control
on or off
name
Friendly port name
vlanid
The vlan id this port belongs to, 4
or “tagged” if it belongs to more tagged
than one vlan
enabled
port is or is not enabled
yes or no
intrusion
intrusion
Intrusion alert status
no
bcast
Broadcast limit
0
10-11
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
ProCurve(config)# show int custom 1-4 port name:4 type vlan intrusion speed
enabled mdi
Status and Counters - Custom Port Status
Port
---1
2
3
4
Name
---------Acco
Huma
Deve
Lab1
Type
---------100/1000T
100/1000T
100/1000T
100/1000T
VLAN
----1
1
1
1
Intrusion
Alert
--------No
No
No
No
Speed
------1000FDx
1000FDx
1000FDx
1000FDx
Enabled
------Yes
Yes
Yes
Yes
MDI-mode
-------Auto
Auto
Auto
Auto
Figure 10-6. Example of the Custom show interfaces Command
You can specify the column width by entering a colon after the column name,
then indicating the number of characters to display. In Figure 10-6 the Name
column only displays the first four characters of the name. All remaining
characters are truncated.
Note
Each field has an fixed minimum width to be displayed. If you specify a field
width smaller than the minimum width, the information is displayed at the
minimum width. For example, if the minimum width for the Name field is 4
characters and you specify Name:2, the Name field displays 4 characters.
Parameters can be entered in any order. There is a limit of 80 characters per
line; if you exceed this limit an error displays.
Error Messages
Error
Error Message
Requesting too many fields (total characters Total length of selected data exceeds one line
exceeds 80)
10-12
Field name is misspelled
Invalid input: <input>
Mistake in specifying the port list
Module not present for port or invalid port:
<input>
The port list is not specified
Incomplete input: custom
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Note on Using Pattern Matching with the “Show Interfaces
Custom” Command
If you have included a pattern matching command to search for a field in the
output of the show int custom command and the show int custom command
produces an error, the error message may not be visible and the output is
empty. For example, if you enter a command that produces an error (vlan is
misspelled) with the pattern matching include option:
ProCurve(config)# show int custom 1-3 name vlun |
include vlan1
the output may be empty. It is advisable to try the show int custom command
first to ensure there is output, and then enter the command again with the
pattern matching option.
Viewing Port Utilization Statistics
Use the show interface port-utilization command to view a real-time rate display
for all ports on the switch. The following shows a sample output from this
command.
ProCurve(config)# show interfaces port-utilization
Status and Counters - Port Utilization
Port
Mode
|
|
--------- -------- +
B1
1000FDx |
B2
1000FDx |
B3
1000FDx |
B4
1000FDx |
B5
1000FDx |
B6
1000FDx |
B7
100FDx
|
Rx
--------------------------Kbits/sec
Pkts/sec Util
---------- ---------- ----0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
624
86
00.62
|
|
+
|
|
|
|
|
|
|
Tx
--------------------------Kbits/sec Pkts/sec
Util
---------- ---------- ----0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
496
0
00.49
Figure 10-7. Example of a Show Interface Port-Utilization Command Listing
10-13
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Operating Notes:
■
For each port on the switch, the command provides a real-time display
of the rate at which data is received (Rx) and transmitted (Tx) in terms
of kilobits per second (KBits/s), number of packets per second (Pkts/
s), and utilization (Util) expressed as a percentage of the total bandwidth available.
■
The show interfaces <port-list> command can be used to display the
current link status and the port rate average over a 5 minute period.
Port rates are shown in bits per second (bps) for ports up to 1 Gigabit;
for 10 Gigabit ports, port rates are shown in kilobits per second
(Kbps).
Viewing Transceiver Status
The show tech transceivers command allows you to:
■
Remotely identify transceiver type and revision number without having
to physically remove an installed transceiver from its slot.
■
Display real-time status information about all installed transceivers,
including non-operational transceivers.
Figure 10-8 shows sample output from the show tech transceivers command.
ProCurve# show tech transceivers
Transceiver Technical Information:
Port # |
Type
| Prod # | Serial #
| Part #
-------+-----------+--------+------------------+---------21
| 1000SX
| J4858B | CN605MP23K
|
22
| 1000LX
| J4859C | H117E7X
| 2157-2345
23
| ??
| ??
| unsupported
|
25
| 10GbE-CX4 | J8440A | US509RU079
|
26
| 10GbE-CX4 | J8440A | US540RU002
|
27
| 10GbE-LR | J8437B | PPA02-2904:0017 | 2157-2345
28
| 10GbE-SR | J8436B | 01591602
| 2158-1000
29
| 10GbE-ER | J8438A | PPA03-2905:0001 |
The following transceivers may not function correctly:
Port #
Message
-------------------------------------------Port 23
Self test failure.
Figure 10-8. Example of Show Tech Transceivers Command
10-14
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Operating Notes:
■
The following information is displayed for each installed transceiver:
•
Port number on which transceiver is installed.
•
Type of transceiver.
•
Product number—Includes revision letter, such as A, B, or C. If no
revision letter follows a product number, this means that no revision
is available for the transceiver.
•
Part number—Allows you to determine the manufacturer for a specified 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 number.
■
The following error messages may be displayed for a non-operational
transceiver:
•
Unsupported Transceiver. (SelfTest Err#060)
Check: www.hp.com/rnd/device_help/2_inform for
more info.
•
This switch only supports revision B and above
transceivers. Check: www.hp.com/rnd/device_help/
2_inform for more info.
•
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.
Enabling or Disabling Ports and Configuring Port Mode
You can configure one or more of the following port parameters. Refer to table
10-1 on pages 10-4 through 10-5.
Syntax: [no] interface < port-list >
[< disable | enable >]
Disables or enables the port for network traffic. Does not
use the no form of the command. (Default: enable.)
speed-duplex < auto-10 |10-full | 10-half | 100-full | 100-half |auto| auto100 | 1000-full >]
10-15
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Specifies the port’s data transfer speed and mode. Does
not use the no form of the command. ([Default: auto.)
Note that in the above syntax you can substitute an “int” for “interface”; that
is: int < port-list >.
The 10/100 auto-negotiation feature allows a port to establish a link with a port
at the other end at either 10 Mbps or 100 Mbps, using the highest mutual speed
and duplex mode available. Only these speeds are allowed with this setting.
For example, to configure port C5 for auto-10-100, enter this command:
ProCurve(config)# int c5 speed-duplex auto-10-100
To configure ports C1 through C3 and port C6 for 100Mbps full-duplex, you
would enter these commands:
ProCurve(config)# int c1-c3,c6 speed-duplex 100-full
Similarly, to configure a single port with the above command settings, 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. For example,
to enter the context level for port C6 and then configure that port for 100FDx:
ProCurve(config)# int e c6
ProCurve(eth-C6)# speed-duplex 100-full
If port C8 was disabled, and you wanted to enable it and configure it for
100FDx with flow-control active, you could do so with either of the following
command sets.
ProCurve(config)# int c8 enable
ProCurve(config)# int c8 speed-duplex 100-full
ProCurve(config)# int c8 flow-control
ProCurve(config)# int c8
ProCurve(eth-C8)# enable
ProCurve(eth-C8)# speed-duplex 100-full
These commands enable and configure
port C8 from the config level:
These commands select the port C8
context level and then apply the
subsequent configuration commands to
port C8:
Figure 10-9. Examples of Two Methods for Changing a Port Configuration
Refer to “Enabling or Disabling Flow Control” on page 10-17 for more on flow
control.
10-16
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Enabling or Disabling Flow Control
Note
Flow control is enabled by default on the downlink ports. You must enable
flow control on the uplink ports in a given link. Otherwise, flow control does
not operate on the link, and appears as Off in the show interfaces brief port
listing, even if flow control is configured as enabled on the port in the switch.
(Refer to Figure 10-3 on page 10-9.) Also, the port (speed-duplex) mode must
be set to Auto (the default).
To disable flow control on some ports, while leaving it enabled on other ports,
just disable it on the individual ports you want to exclude.
Syntax: [ no ]interface < port-list > flow-control
Enables or disables flow control packets on the port. The “no”
form of the command disables flow control on the individual
ports. (Default: Disabled.)
For example, suppose that:
1.
You want to enable flow control on ports A1-A6.
2.
Later, you decide to disable flow control on ports A5 and A6.
3.
As a final step, you want to disable flow control on all ports.
Assuming that flow control is currently disabled on the switch, you would use
these commands:
Enables per-port flow control
for ports A1 - A6.
Figure 10-10. Example of Configuring Flow Control for a Series of Ports
10-17
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Disables per-port flow
control on ports A5 and A6.
Figure 10-11. Example Continued from Figure 10-10
Disables per-port flow
control on ports A1 through
A4. Flow control is now
disabled on the switch.
Ports formerly configured for
flow control.
Figure 10-12. Example Continued from Figure 10-11
Configuring a Broadcast Limit on the Switch
Broadcast-Limit on switches covered in this guide is configured on a per-port
basis. You must be at the port context level for this command to work, for
example:
10-18
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
ProCurve(config)#int B1
ProCurve(int B1)# broadcast-limit 1
Broadcast-Limit.
Syntax: broadcast-limit <0-99>
Enables or disables broadcast limiting for inbound broadcasts
on a selected port on the switch. The value selected is the
percentage of traffic allowed, for example, broadcast-limit 5
allows 5% of the maximum amount of traffic for that port. A
value of zero disables broadcast limiting for that port.
Note: You must switch to port context level before issuing the
broadcast-limit command.
Note: This feature is not appropriate for networks requiring
high levels of IPX or RIP broadcast traffic.
Syntax: show config
Displays the startup-config file. The broadcast limit setting
appears here if enabled and saved to the startup-config file.
Syntax: show running-config
Displays the running-config file. The broadcast limit setting
appears here if enabled. If the setting is not also saved to the
startup-config file, rebooting the switch returns broadcast
limit to the setting currently in the startup-config file.
For example, the following command enables broadcast limiting of 1 percent
of the traffic rate on the selected port on the switch:
ProCurve(int B1)# broadcast-limit 1
For a one Gbps port this results in a broadcast traffic rate of ten Mbps.
Configuring ProCurve Auto-MDIX
Copper ports on the switch can automatically detect the type of cable configuration (MDI or MDI-X) on a connected device and adjust to operate appropriately.
This means you can use a “straight-through” twisted-pair cable or a “crossover” twisted-pair cable for any of the connections—the port makes the
necessary adjustments to accommodate either one for correct operation. The
following port types on your switch support the IEEE 802.3ab standard, which
includes the “Auto MDI/MDI-X” feature:
■
10/100-TX xl module ports
10-19
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
■
100/1000-T xl module ports
■
10/100/1000-T xl module ports
Using the above ports:
■
If you connect a copper port using a straight-through cable on a switch to
a port on another switch or hub that uses MDI-X ports, the switch port
automatically operates as an MDI port.
■
If you connect a copper port using a straight-through cable on a switch to
a port on an end node, such as a server or PC, that uses MDI ports, the
switch port automatically operates as an MDI-X port.
ProCurve Auto-MDIX was developed for auto-negotiating devices, and was
shared with the IEEE for the development of the IEEE 802.3ab standard.
ProCurve Auto-MDIX and the IEEE 802.3ab Auto MDI/MID-X feature are
completely compatible. Additionally, ProCurve Auto-MDIX supports operation in forced speed and duplex modes.
If you want more information on this subject please refer to the IEEE 802.3ab
Standard Reference.
For more information on MDI-X, refer to the appendix titled “Switch Ports and
Network Cables” in the Installation and Getting Started Guide for your
switch.
Manual Override. If you require control over the MDI/MDI-X feature you can
set the switch to either of two non-default modes:
■
Manual MDI
■
Manual MDI-X
Table 10-2 shows the cabling requirements for the MDI/MDI-X settings.
Table 10-2. Cable Types for Auto and Manual MDI/MDI-X Settings
MDI/MDI-X Device Type
Setting
Manual MDI
Manual MDI-X
Auto-MDI-X
(The Default)
10-20
PC or Other MDI Device Type
Switch, Hub, or Other MDI-X Device
Crossover Cable
Straight-Through Cable
Straight-Through Cable
Crossover Cable
Either Crossover or Straight-Through Cable
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
The Auto-MDIX features apply only to copper port switches using twisted-pair
copper Ethernet cables.
Syntax: interface < port-list > mdix-mode < auto-mdix | mdi | mdix >
auto-mdix is the automatic, default setting. This configures the
port for automatic detection of the cable (either straight-through
or crossover).
mdi is the manual mode setting that configures the port for
connecting to either a PC or other MDI device with a crossover
cable, or to a switch, hub, or other MDI-X device with a straightthrough cable.
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 straightthrough cable.
Syntax: show interfaces config
Lists the current per-port Auto/MDI/MDI-X configuration.
Syntax: show interfaces brief
Where a port is linked to another device, this command lists
the MDI mode the port is currently using. In the case of ports
configured for Auto (auto-mdix), the MDI mode appears as
either MDI or MDIX, depending upon which option the port has
negotiated with the device on the other end of the link. In the
case of ports configured for MDI or MDIX, the mode listed in
this display matches the configured setting. If the link to
another device was up, but has gone down, this command
shows the last operating MDI mode the port was using. If a
port on a given switch has not detected a link to another device
since the last reboot, this command lists the MDI mode to
which the port is currently configured.
For example, show interfaces config displays the following data when port A1
is configured for auto-mdix, port A2 is configured for mdi, and port A3 is
configured for mdix.
10-21
Port Status and Configuration
Viewing Port Status and Configuring Port Parameters
Per-Port MDI
Configuration
Figure 10-13. Example of Displaying the Current MDI Configuration
Per-Port MDI
Operating Mode
Figure 10-14. Example of Displaying the Current MDI Operating Mode
Web: Viewing Port Status and Configuring Port
Parameters
In the web browser interface:
1.
Click on the Configuration tab.
2.
Click on [Port Configuration].
3.
Select the ports you want to modify and click on [Modify Selected Ports].
4.
After you make the desired changes, click on [Apply Settings].
Note that the web browser interface displays an existing port trunk group.
However, to configure a port trunk group, you must use the CLI or the menu
interface. For more on this topic, refer to Chapter 11, “Port Trunking” .
10-22
Port Status and Configuration
Using Friendly (Optional) Port Names
Using Friendly (Optional) Port Names
Feature
Configure Friendly Port Names
Display Friendly Port Names
Default
Menu
CLI
Web
Standard Port
Numbering
n/a
page 24
n/a
n/a
n/a
page 25
n/a
This feature enables you to assign alphanumeric port names of your choosing
to augment automatically assigned numeric port names. This means you can
configure meaningful port names to make it easier to identify the source of
information listed by some Show commands. (Note that this feature augments
port numbering, but does not replace it.)
Configuring and Operating Rules for Friendly Port
Names
■
At either the global or context configuration level you can assign a unique
name to a port. You can also assign the same name to multiple ports.
■
The friendly port names you configure appear in the output of the show
name [ port-list ], show config, and show interface < port-number > commands.
They do not appear in the output of other show commands or in Menu
interface screens. (Refer to “Displaying Friendly Port Names with Other
Port Data” on page 10-25.)
■
Friendly port names are not a substitute for port numbers in CLI commands or Menu displays.
■
Trunking ports together does not affect friendly naming for the individual
ports. (If you want the same name for all ports in a trunk, you must
individually assign the name to each port.)
■
A friendly port name can have up to 64 contiguous alphanumeric characters.
■
Blank spaces within friendly port names are not allowed, and if used,
cause an invalid input error. (The switch interprets a blank space as a name
terminator.)
■
In a port listing, not assigned indicates that the port does not have a name
assignment other than its fixed port number.
10-23
Port Status and 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 > name < port-name-string >
Assigns a port name to port-list.
Syntax: no interface < port-list > name
Deletes the port name from port-list.
Configuring a Single Port Name. Suppose that you have connected port
A3 on the switch to Bill Smith’s workstation, and want to assign Bill’s name
and workstation IP address (10.25.101.73) as a port name for port A3:
Figure 10-15. Example of Configuring a Friendly Port Name
10-24
Port Status and Configuration
Using Friendly (Optional) Port Names
Configuring the Same Name for Multiple Ports. Suppose that you want
to use ports A5 through A8 as a trunked link to a server used by a drafting
group. In this case you might configure ports A5 through A8 with the name
“Draft-Server:Trunk”.
Figure 10-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
friendly port names and also quickly shows you which ports do not have
friendly name assignments. (show name data comes from the runningconfig file.)
■
show interface <port-number>: Displays the friendly port name, if any, along
with the traffic statistics for that port. (The friendly port name data comes
from the running-config file.)
■
show config: Includes friendly port names in the per-port data of the
resulting configuration listing. (show config data comes from the startupconfig file.)
To List All Ports or Selected Ports with Their Friendly Port Names.
This command lists names assigned to a specific port.
10-25
Port Status and Configuration
Using Friendly (Optional) Port Names
Syntax: show name [ port-list ]
Lists the friendly port name with its corresponding port
number and port type. The show name command without a port
list shows this data for all ports on the switch.
For example:
Ports Without
“Friendly”
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
examples.
Figure 10-18. Example of Friendly Port Name Data for Specific Ports on the Switch
Including Friendly Port Names in Per-Port Statistics Listings. A
friendly port name configured to a port is automatically included when you
display the port’s statistics output.
10-26
Port Status and Configuration
Using Friendly (Optional) Port Names
Syntax: show interface < port-number >
Includes the friendly port name with the port’s traffic statistics
listing.
For example, if you configure port A1 with the name “O’Connor_10.25.101.43”,
the show interface output for this port appears similar to the following:
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
To Search the Configuration for Ports with Friendly Port Names.
This option tells you which friendly port names have been saved to the startupconfig file. (show config does not include ports that have only default settings
in the startup-config file.)
Syntax: show config
Includes friendly port names in a listing of all interfaces (ports)
configured with non-default settings. Excludes ports that have
neither a friendly port name nor any other non-default
configuration settings.
10-27
Port Status and 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 startupconfig file. The name entered
for port A2 is not saved
because it was executed after
write memory.
; 498358-B21 Configuration Editor; Created on release #Z.14.04
Listing includes friendly
port name for port A1
only.
In this case, show config lists
only port A1. Executing write
mem after entering the name for
port A2, and then executing
show config again would result
in a listing that includes both
ports.
Figure 10-20. Example Listing of the Startup-Config File with a Friendly Port Name Configured (and Saved)
10-28
Port Status and Configuration
Using Friendly (Optional) Port Names
Configuring Transceivers and Modules That Haven’t
Been Inserted
Transceivers
Previously, a port had to be valid and verified for the switch to allow it to be
configured. Transceivers are removable ports and considered invalid when
not present in the switch, so they cannot be configured unless they are already
in the switch. For switches covered in this guide, the verification for allowable
port configurations performed by the CLI is removed and configuration of
transceivers is allowed even if they are not yet inserted in the switch.
Modules
You can create or edit configuration files (as text files) that can be uploaded
to the switch without the modules having been installed yet. Additionally, you
can pre-configure the modules with the CLI “module” command.
Syntax: module <module-num> type <module-type>
Allows you to configure the type of the module.
The same module command used in an uploaded configuration file is used to
define a module that is being pre-configured. The validation performed when
issued through the CLI is still performed just as if the command was executed
on the switch, in other words, as if the module were actually present in the
switch.
Note
You cannot use this method to change the configuration of a module that has
already been configured. The slot must be empty and the configuration file
must not have a configuration associated with it.
Clearing the Module Configuration
Because of the hot-swap capabilities of the modules, when a module is
removed from the chassis, the module configuration remains in the configuration file. This feature allows you to remove the module configuration
information from the configuration file.
10-29
Port Status and Configuration
Using Friendly (Optional) Port Names
Syntax: [no] module <slot>
Allows removal of the module configuration in the configuration file after the module has been removed. Enter an integer
between 1 and 12 for <slot>.
For example:
ProCurve(config)# no module 3
Note
This does not change how hot-swap works.
Operating Notes
The following restrictions apply:
10-30
■
The slot being cleared must be empty
■
There was no module present in the slot since the last boot
■
If there was a module present after the switch was booted, the switch will
have to be rebooted before any module (new or same) can be used in the
slot.
■
This does not clear the configuration of a module still in use by the switch.
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
Uni-Directional Link Detection (UDLD)
Uni-directional Link Detection (UDLD) monitors a link between two ProCurve
switches and blocks the ports on both ends of the link if the link fails at any
point between the two devices. This feature is particularly useful for detecting
failures in fiber links and trunks. Figure 10-21 shows an example.
Scenario 1 (No UDLD): Without UDLD, the switch ports
remain enabled despite the link failure. Traffic continues to
be load-balanced to the ports connected to the failed link.
Scenario 2 (UDLD-enabled): When UDLD is enabled, the
feature blocks the ports connected to the failed link.
Third Party
Switch
Fiber
ProCurve
Switch
ProCurve
Switch
ProCurve
Switch
Link Failure
Third Party
Switch
Trunk
Third Party
Switch
Figure 10-21. UDLD Example
In this example, each ProCurve switch load balances traffic across two ports
in a trunk group. Without the UDLD feature, a link failure on a link that is not
directly attached to one of the ProCurve switches remains undetected. As a
result, each switch continue to send traffic on the ports connected to the failed
link. 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.
Similarly, UDLD is effective for monitoring fiber optic links that use two unidirection fibers to transmit and receive packets. Without UDLD, if a fiber
breaks in one direction, a fiber port may assume the link is still good (because
the other direction is operating normally) and continue to send traffic on the
10-31
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
connected ports. UDLD-enabled ports; however, will prevent traffic from
being sent across a bad link by blocking the ports in the event that either the
individual transmitter or receiver for that connection fails.
Ports enabled for UDLD exchange health-check packets once every five
seconds (the link-keepalive interval). If a port does not receive a health-check
packet from the port at the other end of the link within the keepalive interval,
the port waits for four more intervals. If the port still does not receive a healthcheck packet after waiting for five intervals, the port concludes that the link
has failed and blocks the UDLD-enabled port.
When a port is blocked by UDLD, the event is recorded in the switch log or
via an SNMP trap (if configured); and other port blocking protocols, like
spanning tree or meshing, will not use the bad link to load balance packets.
The port will remain blocked until the link is unplugged, disabled, or fixed.
The port can also be unblocked by disabling UDLD on the port.
Configuring UDLD
When configuring UDLD, keep the following considerations in mind:
Note
■
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.
■
To configure UDLD on a trunk group, you must configure the feature
on each port of the group individually. Configuring UDLD on a trunk
group’s primary port enables the feature on that port only.
■
Dynamic trunking is not supported. If you want to configure a trunk
group that contains ports on which UDLD is enabled, you must
remove the UDLD configuration from the ports. After you create the
trunk group, you can re-add the UDLD configuration.
UDLD interoperates with the following ProCurve switches: 2600, 2800, 3400,
3500, 4200, 5300, 5400, 6200, 6400, 6600, 8212, and 9300. Consult the release
notes and current manuals for required software versions.
The following commands allow you to configure UDLD via the CLI.
Syntax: [no] interface <port-list> link-keepalive
Enables UDLD on a port or range of ports.
To disable the feature, enter the no form of the command.
Default: UDLD disabled
10-32
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
Syntax: link-keepalive interval <interval>
Determines the time interval to send UDLD control packets. The
<interval> parameter specifies how often the ports send a UDLD
packet. You can specify from 10 – 100, in 100 ms increments,
where 10 is 1 second, 11 is 1.1 seconds, and so on.
Default: 50 (5 seconds)
Syntax: link-keepalive retries <num>
Determines the maximum number of retries to send UDLD
control packets. The <num> parameter specifies the maximum
number of times the port will try the health check. You can specify
a value from 3 – 10.
Default: 5
Syntax: [no] interface <port-list> link-keepalive vlan <vid>
Assigns a VLAN ID to a UDLD-enabled port for sending of tagged
UDLD control packets.Under default settings, untagged UDLD
packets can still be transmitted and received on tagged only
ports—however, a warning message will be logged.
The no form of the command disables UDLD on the specified
port(s).
Default: UDLD packets are untagged; tagged only ports will
transmit and receive untagged UDLD control packets
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
Note
When at least one port is UDLD-enabled, the switch will forward out UDLD
packets that arrive on non-UDLD-configured ports out of all other non-UDLDconfigured ports in the same vlan. That is, UDLD control packets will “pass
through” a port that is not configured for UDLD. However, UDLD packets will
be dropped on any blocked ports that are not configured for UDLD.
10-33
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
Changing the Keepalive Interval
By default, ports enabled for UDLD send a link health-check packet once every
5 seconds. You can change the interval to a value from 10 – 100 deciseconds,
where 10 is 1 second, 11 is 1.1 seconds, and so on. For example, to change the
packet interval to seven seconds, enter the following command at the global
configuration level:
ProCurve(config)# link-keepalive interval 70
Changing the Keepalive Retries
By default, a port waits five seconds to receive a health-check reply packet
from the port at the other end of the link. If the port does not receive a reply,
the port tries four more times by sending up to four more health-check
packets. If the port still does not receive a reply after the maximum number
of retries, the port goes down.
You can change the maximum number of keepalive attempts to a value from
3 – 10. For example, to change the maximum number of attempts to 4, enter
the following command at the global configuration level:
ProCurve(config)# link-keepalive retries 4
Configuring UDLD for Tagged Ports
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.
To enable ports to receive and send UDLD control packets tagged with a
specific VLAN ID, enter a command such as the following at the interface
configuration level:
ProCurve(config)#interface l link-keepalive vlan 22
Notes
10-34
■
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
of the port as untagged packets.
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
■
To re-assign a VLAN ID, re-enter the command with the new VLAN ID
number. The new command will overwrite the previous command
setting.
■
When configuring UDLD for tagged ports, you may receive a warning
message if there are any inconsistencies with the port’s VLAN configuration (see page 37 for potential problems).
Viewing UDLD Information
The following show commands allow you to display UDLD configuration and
status via the CLI.
Syntax: show link-keepalive
Displays all the ports that are enabled for link-keepalive.
Syntax: show link-keepalive statistics
Displays detailed statistics for the UDLD-enabled ports on the
switch.
Syntax: clear link-keepalive statistics
Clears UDLD statistics. This command clears the packets sent,
packets received, and transitions counters in the show linkkeepalive statistics display.
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: 3
Keepalive Interval: 1 sec
Port 1 is UDLD-enabled, and
tagged for a specific VLAN.
Port Enabled Physical Keepalive
Adjacent
UDLD
Status
Status
Switch
VLAN
------------------------------------------------------------------1
Yes
up
up
00d9d-f9b700
200
2
Yes
up
up
01560-7b1600
untagged
Port
3 is UDLD-enabled, but
3
Yes
down
off-line
has no physical connection.
4
Yes
up
failure
Port 4 is connected, but is blocked
5
No
down
off-line
due to a link-keepalive failure
Port 5 has been disabled by
the System Administrator.
Figure 10-22. Example of Show Link-Keepalive Command
10-35
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
To display detailed UDLD information for specific ports, enter the show linkkeepalive 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:
Udld Packets Sent:
Udld Packets Received:
Port Blocking:
1
up
1000
1000
no
Neighbor MAC Addr:
Neighbor Port:
State Transitions:
Link-vlan:
0000a1-b1c1d1
5
2
1
Port:
Current State:
Udld Packets Sent:
Udld Packets Received:
Port Blocking:
2
up
500
450
no
Neighbor MAC Addr:
Neighbor Port:
State Transitions:
Link-vlan:
000102-030405
6
3
200
Port:
Current State:
Udld Packets Sent:
Udld Packets Received:
Port Blocking:
3
off line
0
0
no
Neighbor MAC Addr:
Neighbor Port:
State Transitions:
Link-vlan:
n/a
n/a
0 Port 4 is shown as blocked
1 due to a link-keepalive failure
Port:
Current State:
Udld Packets Sent:
Udld Packets Received:
Port Blocking:
4
failure
128
50
yes
Neighbor MAC Addr:
Neighbor Port:
State Transitions:
Link-vlan:
n/a
n/a
8
1
Figure 10-23. Example of Show Link-Keepalive Statistics Command
To clear UDLD statistics, enter the following command:
ProCurve# clear link-keepalive statistics
This command clears the packets sent, packets received, and transitions
counters in the show link keepalive statistics display (see Figure 10-23 for an
example).
10-36
Port Status and 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-3. Warning Messages caused by configuring UDLD for Tagged Ports
CLI Command Example
Warning Message
Possible Problem
link-keepalive 6
Possible configuration
problem detected on port
6. UDLD VLAN configuration
does not match the port's
VLAN configuration.
You have attempted to enable UDLD on a port that is
a tagged only port, but did not specify a configuration
for tagged UDLD control packets. In this example, the
switch will send and receive the UDLD control
packets untagged despite issuing this warning.
link-keepalive 7
vlan 4
Possible configuration
problem detected on port
7. UDLD VLAN configuration
does not match the port's
VLAN configuration.
You have attempted to configure tagged UDLD
packets on a port that does not belong to the specified
VLAN. In this example, if port 7 belongs to VLAN 1 and
22, but the user tries to configure UDLD on port 7 to
send tagged packets in VLAN 4, the configuration will
be accepted. The UDLD control packets will be sent
tagged in VLAN 4, which may result in the port being
blocked by UDLD if the user does not configure VLAN
4 on this port.
no vlan 22 tagged
20
Possible configuration
problem detected on port
18. UDLD VLAN
configuration does not
match the port's VLAN
configuration.
You have attempted to remove a VLAN on port that is
configured for tagged UDLD packets on that VLAN. In
this example, if port 18, 19, and 20 are transmitting and
receiving tagged UDLD packets for Vlan 22, but the
user tries to remove Vlan 22 on port 20, the
configuration will be accepted. In this case, the UDLD
packets will still be sent on Vlan 20, which may result
in the port being blocked by UDLD if the users do not
change the UDLD configuration on this port.
Note: If you are configuring the switch via SNMP with the same problematic VLAN configuration choices, the above
warning messages will also be logged in the switch’s event log.
Event Log Messages. The following table shows the event log messages that
may be generated once UDLD has been enabled on a port.
Table 10-4. UDLD Event Log Messages
Message
Event
I 01/01/06 04:25:05 ports: port 4 is
deactivated due to link failure.
A UDLD-enabled port has been blocked due to part of the link
having failed.
I 01/01/06 06:00:43 ports: port 4 is
up, link status is good.
A failed link has been repaired and the UDLD-enabled port is no
longer blocked.
10-37
11
Port Trunking
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Port Trunk Features and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Trunk Configuration Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Menu: Viewing and Configuring a Static Trunk Group . . . . . . . . . 11-10
CLI: Viewing and Configuring Port Trunk Groups . . . . . . . . . . . . . 11-12
Using the CLI To View Port Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Using the CLI To Configure a Static or Dynamic Trunk Group . . . 11-15
Web: Viewing Existing Port Trunk Groups . . . . . . . . . . . . . . . . . . . . 11-18
Trunk Group Operation Using LACP . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Default Port Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
LACP Notes and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23
Trunk Group Operation Using the “Trunk” Option . . . . . . . . . . . . 11-27
How the Switch Lists Trunk Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Outbound Traffic Distribution Across Trunked Links . . . . . . . . . 11-28
11-1
Port Trunking
Overview
Overview
This chapter describes creating and modifying port trunk groups. This
includes non-protocol trunks and LACP (802.3ad) trunks.
Port Status and Configuration Features
Feature
Default
Menu
CLI
Web
viewing port trunks
n/a
page 11-9
page 11-11
page 11-17
configuring a static trunk
group
none
page 11-9
page 11-15
—
configuring a dynamic LACP
trunk group
disabled
page 11-15
—
—
Port trunking allows you to assign up to eight physical links to one logical link
(trunk) that functions as a single, higher-speed link providing dramatically
increased bandwidth. This capability applies to connections between backbone devices as well as to connections in other network areas where traffic
bottlenecks exist. A trunk group is a set of up to eight ports configured as
members of the same port trunk. Note that the ports in a trunk group do not
have to be consecutive. For example:
The multiple physical links in a trunk behave as one logical link
Switch 1:
Ports c1 - c3,
c5 - c7, and
c9 - c10
configured as a
port trunk group.
port c1
port c2
port c3
port c4
port c5
port c6
port c7
port c8
port c9
port c10
…
port n
port 1
port 2
port 3
port 4
port 5
port 6
port 7
port 8
port 9
port 10
port 11
port 12
Switch 2:
Ports a1, a3 - a4,
a6 - a8, a11, and
a12 configured
as a port trunk
group
…
port n
Figure 11-1. Conceptual Example of Port Trunking
With full-duplex operation in a eight-port trunk group, trunking enables the
following bandwidth capabilities:
11-2
Port Trunking
Overview
Port Connections and Configuration: All port trunk links must be pointto-point connections between a switch and another switch, router, server, or
workstation configured for port trunking. No intervening, non-trunking
devices are allowed. It is important to note that ports on both ends of a port
trunk group must have the same mode (speed and duplex) and flow control
settings.
Note
Link Connections. The switch does not support port trunking through an
intermediate, non-trunking device such as a hub, or using more than one media
type in a port trunk group. Similarly, for proper trunk operation, all links in
the same trunk group must have the same speed, duplex, and flow control.
Port Security Restriction. Port security does not operate on a trunk group.
If you configure port security on one or more ports that are later added to a
trunk group, the switch resets the port security parameters for those ports to
the factory-default configuration.
Caution
To avoid broadcast storms or loops in your network while configuring a
trunk, first disable or disconnect all ports you want to add to or remove from
the trunk. After you finish configuring the trunk, enable or re-connect the
ports.
11-3
Port Trunking
Port Trunk Features and Operation
Port Trunk Features and Operation
The switches covered in this guide offer these options for port trunking:
■
LACP: IEEE 802.3ad—page 11-18
■
Trunk: Non-Protocol—page 11-26
Up to 60 trunk groups are supported on the switches covered in this guide. The
actual maximum depends on the number of ports available on the switch and
the number of links in each trunk. (Using the Link Aggregation Control
Protocol—LACP—option, you can include standby trunked ports in addition
to the maximum of eight actively trunking ports.)
LACP Note
LACP requires full-duplex (FDx) links of the same media type (10/100Base-T,
100FX, etc.) and the same speed, and enforces speed and duplex conformance
across a trunk group. 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 negotiation selects FDx), and 10FDx, 100FDx,
and 1000FDx settings. (The 10-gigabit ports available for some switch models
allow only the Auto setting.)
Fault Tolerance: If a link in a port trunk fails, the switch redistributes
traffic originally destined for that link to the remaining links in the trunk. The
trunk remains operable as long as there is at least one link in operation. If a
link is restored, that link is automatically included in the traffic distribution
again. The LACP option also offers a standby link capability, which enables
you to keep links in reserve for service if one or more of the original active
links fails. Refer to “Trunk Group Operation Using LACP” on page 11-18.)
Trunk Configuration Methods
Dynamic LACP Trunk: The switch automatically negotiates trunked links
between LACP-configured ports on separate devices, and offers one dynamic
trunk option: LACP. To configure the switch to initiate a dynamic LACP trunk
with another device, use the interface command in the CLI to set the default
LACP option to Active on the ports you want to use for the trunk. For example,
the following command sets ports C1-C4 to LACP active:
11-4
Port Trunking
Trunk Configuration Methods
ProCurve(config) int c1-c4 lacp active
Note that the preceding example works if the ports are not already operating
in a trunk. To change the LACP option on ports already operating as a trunk,
you must first remove them from the trunk. For example, if ports C1 - C4 were
LACP-active and operating in a trunk with another device, you would do the
following to change them to LACP-passive:
ProCurve(config)# no int c1-c4 lacp
Removes the ports from the trunk.
ProCurve(config)# int c1-c4 lacp passive
Configures LACP passive.
Static Trunk: The switch uses the links you configure with the Port/Trunk
Settings screen in the menu interface or the trunk command in the CLI to create
a static port trunk. The switch offers two types of static trunks: LACP and
Trunk.
Table 11-1. Trunk Types Used in Static and Dynamic Trunk Groups
Trunking
Method
LACP
Trunk
Dynamic
Yes
No
Static
Yes
Yes
11-5
Port Trunking
Trunk Configuration Methods
Table 11-2. Trunk Configuration Protocols
Protocol
Trunking Options
LACP
(802.3ad)
Provides dynamic and static LACP trunking options.
• Dynamic LACP — Use the switch-negotiated dynamic LACP trunk when:
– The port on the other end of the trunk link is configured for Active or Passive LACP.
– You want fault-tolerance for high-availability applications. If you use an eight-link trunk you can also
configure one or more additional links to operate as standby links that will activate only if another
active link goes down.
• Static LACP — Use the manually configured static LACP trunk when:
– The port on the other end of the trunk link is configured for a static LACP trunk
– You want to configure non-default spanning tree or IGMP parameters on an LACP trunk group.
– You want an LACP trunk group to operate in a VLAN other than the default VLAN and GVRP is disabled.
(Refer to “VLANs and Dynamic LACP” on page 11-23.)
– You want to use a monitor port on the switch to monitor an LACP trunk.
For more information, refer to “Trunk Group Operation Using LACP” on page 11-18.
Trunk
(nonprotocol)
Provides manually configured, static-only trunking to:
• Most ProCurve switches and routing switches not running the 802.3ad LACP 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
– You are unsure which type of trunk to use, or the device to which you want to create a trunk link is
using an unknown trunking protocol.
– You want to use a monitor port on the switch to monitor traffic on a trunk.
Refer to “Trunk Group Operation Using the “Trunk” Option” on page 11-26.
11-6
Port Trunking
Trunk Configuration Methods
Table 11-3. General Operating Rules for Port Trunks
Media: For proper trunk operation, all ports on both ends of a trunk group must have the same media type and mode
(speed and duplex). (For the switches covered in this guide, ProCurve recommends leaving the port Mode setting at Auto
or, in networks using Cat 3 cabling, Auto-10.)
Port Configuration: The default port configuration is Auto, which enables a port to sense speed and negotiate duplex with
an Auto-Enabled port on another device. ProCurve recommends that you use the Auto setting for all ports you plan to use
for trunking. Otherwise, you must manually ensure that the mode setting for each port in a trunk is compatible with the
other ports in the trunk.
Recommended Port Mode Setting for LACP
Figure 11-2. Recommended Port Mode Setting for LACP
All of the following operate on a per-port basis, regardless of trunk membership:
• Enable/Disable
• Flow control (Flow Ctrl)
LACP is a full-duplex protocol. Refer to “Trunk Group Operation Using LACP” on page 11-18.
Trunk Configuration: All ports in the same trunk group must be the same trunk type (LACP or Trunk). All LACP ports in the
same trunk group must be either all static LACP or all dynamic LACP.
A trunk appears as a single port labeled Dyn1 (for an LACP dynamic trunk) or Trk1 (for a static trunk of type: LACP,
Trunk) on various menu and CLI screens. For a listing of which screens show which trunk types, refer to “How the Switch
Lists Trunk Data” on page 11-27.
For spanning-tree or VLAN operation, configuration for all ports in a trunk is done at the trunk level. (You cannot separately
configure individual ports within a trunk for spanning-tree or VLAN operation.)
Traffic Distribution: All of the switch trunk protocols use the SA/DA (Source Address/Destination Address) method of
distributing traffic across the trunked links. Refer to “Outbound Traffic Distribution Across Trunked Links” on page 11-27.
11-7
Port Trunking
Trunk Configuration Methods
Spanning Tree: 802.1D (STP) and 802.1w (RSTP) Spanning Tree operate as a global setting on the switch (with one instance
of Spanning Tree per switch). 802.1s (MSTP) Spanning Tree operates on a per-instance basis (with multiple instances
allowed per switch). For each Spanning Tree instance, 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.
(Note that the switch lists the trunk by name—such as Trk1—and does not list the individual ports in the trunk.) For
example, if ports C1 and C2 are configured as a static trunk named Trk1, they are listed in the Spanning Tree display as
Trk1 and do not appear as individual ports in the Spanning Tree displays.
In this example showing
part of the show spanningtree listing, ports C1 and C2
are members of TRK1 and
do not appear as individual
ports in the port
configuration part of the
listing.
Figure 11-3. Example of a Port Trunk in a Spanning Tree Listing
When Spanning Tree forwards on a trunk, all ports in the trunk will be forwarding. Conversely, when Spanning Tree blocks
a trunk, all ports in the trunk are blocked.
Note: A dynamic LACP trunk operates only with the default Spanning Tree settings. Also, this type of trunk appears in
the CLI show spanning-tree display, but not in the Spanning Tree Operation display of the Menu interface.
If you remove a port from a static trunk, the port retains the same Spanning Tree settings that were configured for the trunk.
IP Multicast Protocol (IGMP): A static trunk of any type appears in the IGMP configuration display, and you can configure
IGMP for a static trunk in the same way that you would configure IGMP on a non-trunked port. (Note that the switch lists
the trunk by name—such as Trk1—and does not list the individual ports in the trunk.) Also, creating a new trunk
automatically places the trunk in IGMP Auto status if IGMP is enabled for the default VLAN. A dynamic LACP trunk
operates only with the default IGMP settings and does not appear in the IGMP configuration display or show ip igmp
listing.
VLANs: Creating a new trunk automatically places the trunk in the DEFAULT_VLAN, regardless of whether the ports in
the trunk were in another VLAN. Similarly, removing a port from a trunk group automatically places the port in the default
VLAN. You can configure a static trunk in the same way that you configure a port for membership in any VLAN.
Note: For a dynamic LACP trunk to operate in a VLAN other than the default VLAN (DEFAULT_VLAN), GVRP must be
enabled. Refer to “Trunk Group Operation Using LACP” on page 11-18.
Port Security: Trunk groups (and their individual ports) cannot be configured for port security, and the switch excludes
trunked ports from the show port-security listing. If you configure non-default port security settings for a port, then
subsequently try to place the port in a trunk, you will see the following message and the command will not be executed:
< port-list > Command cannot operate over a logical port.
Monitor Port:
Note: A trunk cannot be a monitor port. A monitor port can monitor a static trunk but cannot monitor a dynamic LACP trunk.
11-8
Port Trunking
Menu: Viewing and Configuring a Static Trunk Group
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. Refer to
“Enabling or Disabling Ports and Configuring Port Mode” on page 10-15.)
To View and/or Configure Static Port Trunking: This procedure uses
the Port/Trunk Settings screen to configure a static port trunk group on the
switch.
1.
Follow the procedures in the Important note above.
2.
From the Main Menu, Select:
2. Switch Configuration …
2. Port/Trunk Settings
3.
Press [E] (for Edit) and then use the arrow keys to access the port trunk
parameters.
These two columns indicate
static trunk status.
(For dynamic LACP trunk
status, use the CLI show lacp
command—page 11-13.)
Figure 11-4. Example of the Menu Screen for Configuring a Port Trunk Group
4.
In the Group column, move the cursor to the port you want to configure.
5.
Use the Space bar to choose a trunk group assignment (Trk1, Trk2, and so
on) for the selected port.
11-9
Port Trunking
Menu: Viewing and Configuring a Static Trunk Group
•
For proper trunk operation, 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, refer to “Viewing Port
Status and Configuring Port Parameters” on page 10-3.
•
You can configure the trunk group with up to eight ports per trunk. If
multiple VLANs are configured, all ports within a trunk will be
assigned to the same VLAN or set of VLANs. (With the 802.1Q VLAN
capability built into the switch, more than one VLAN can be assigned
to a trunk. Refer to the chapter titled “Static Virtual LANs (VLANs)”
in the Advanced Traffic Management Guide for your switch.)
(To return a port to a non-trunk status, keep pressing the Space bar
until a blank appears in the highlighted Group value for that port.)
Figure 11-5. Example of the Configuration for a Two-Port Trunk Group
6.
Move the cursor to the Type column for the selected port and use the
Space bar to select the trunk type:
– LACP
– Trunk (the default type if you do not specify a type)
All ports in the same trunk group on the same switch must have the same
Type (LACP or Trunk).
7.
When you are finished assigning ports to the trunk group, press [Enter],
then [S] (for Save) and return to the Main Menu. (It is not necessary to
reboot the switch.)
During the Save process, traffic on the ports configured for trunking will
be delayed for several seconds. If the Spanning Tree Protocol is enabled,
the delay may be up to 30 seconds.
11-10
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
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. (Refer to “Viewing Port Status and
Configuring Port Parameters” on page 10-3.)
Check the Event Log (“Using the Event Log for Troubleshooting Switch
Problems” on page C-24) to verify that the trunked ports are operating properly.
CLI: Viewing and Configuring Port Trunk
Groups
Trunk Status and Configuration Commands
show trunks
below
show lacp
page 11-13
trunk
page 11-15
interface < port-list > lacp
page 11-15
Using the CLI To View Port Trunks
You can list the trunk type and group for all ports on the switch or for selected
ports. You can also list LACP-only status information for LACP-configured
ports.
Listing Static Trunk Type and Group for All Ports or for Selected
Ports.
Syntax: show trunks [< port-list >]
Omitting the < port-list > parameter results in a static trunk
data listing for all LAN ports in the switch. For example, in
a switch where ports A4 and A5 belong to Trunk 1 and ports
A7 and A8 belong to Trunk 2, you have the options shown in
figures 11-6 and 11-7 for displaying port data for ports
belonging to static trunks.
11-11
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
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. (Refer to “Using Friendly (Optional) Port Names” on page 10-23.)
Port A6 does not appear in this listing because
it is not assigned to a static trunk.
Figure 11-6. Example Listing Specific Ports Belonging to Static Trunks
The show trunks < port-list > command in the above example includes a port
list, and thus shows trunk group information only for specific ports that have
membership in a static trunk. In figure 11-7, the command does not include a
port list, so the switch lists all ports having static trunk membership.
Figure 11-7. Example of a Show Trunk Listing Without Specifying Ports
11-12
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
Listing Static LACP and Dynamic LACP Trunk Data.
Syntax: show lacp
Lists data for only the LACP-configured ports..
In the following example, ports A1 and A2 have been previously configured
for a static LACP trunk. (For more on the “Active” parameter, see table 11-5
on page 11-21.)
Figure 11-8. Example of a Show LACP Listing
(For a description of each of the above-listed data types, refer to table 11-5,
“LACP Port Status Data” on page 11-21.)
Dynamic LACP Standby Links. Dynamic LACP trunking enables you to
configure standby links for a trunk by including more than eight ports in a
dynamic LACP trunk configuration. When eight ports (trunk links) are up, the
remaining link(s) will be held in standby status. If a trunked link that is “Up”
fails, it will be replaced by a standby link, which maintains your intended
bandwidth for the trunk. (Refer to also the “Standby” entry under “Port Status”
in "Table 11-5. LACP Port Status Data" on page 11-21.) In the next example,
ports A1 through A9 have been configured for the same LACP trunk. Notice
that one of the links shows Standby status, while the remaining eight links are
“Up”.
11-13
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
“Up” Links
Standby Link
Figure 11-9. Example of a Dynamic LACP Trunk with One Standby Link
Using the CLI To Configure a Static or Dynamic Trunk
Group
Important
Configure port trunking before you connect the trunked links between
switches. Otherwise, a broadcast storm could occur. (If you need to connect
the ports before configuring them for trunking, you can temporarily disable
the ports until the trunk is configured. Refer to “Enabling or Disabling Ports
and Configuring Port Mode” on page 10-15.)
The table on page 11-5 describes the maximum number of trunk groups you
can configure on the switch. An individual trunk can have up to eight links,
with additional standby links if you’re using LACP. You can configure trunk
group types as follows:
Trunk Type
Trunk Group Membership
TrkX (Static)
DynX (Dynamic)
LACP
Yes
Yes
Trunk
Yes
No
The following examples show how to create different types of trunk groups.
11-14
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
Configuring a Static Trunk or Static LACP Trunk Group.
Syntax: trunk < port-list > < trk1 ... trk60 > < trunk | lacp >
Configures the specified static trunk type.
This example uses ports C4 - C6 to create a non-protocol static trunk group
with the group name of Trk2.
ProCurve(config)# trunk c4-c6 trk2 trunk
Removing Ports from a Static Trunk Group. This command removes
one or more ports from an existing Trkx trunk group.
Caution
Removing a port from a trunk can create a loop and cause a broadcast storm.
When you remove a port from a trunk where spanning tree is not in use,
ProCurve recommends that you first disable the port or disconnect the link
on that port.
Syntax: no trunk < port-list >
Removes the specified ports from an existing trunk group.
For example, to remove ports C4 and C5 from an existing trunk group.
ProCurve(config)# no trunk c4-c5
Enabling a Dynamic LACP Trunk Group. In the default port configuration, all ports on the switch are set to disabled. To enable the switch to
automatically form a trunk group that is dynamic on both ends of the link, the
ports on one end of a set of links must be LACP Active. The ports on the other
end can be either LACP Active or LACP Passive. The active command enables
the switch to automatically establish a (dynamic) LACP trunk group when the
device on the other end of the link is configured for LACP Passive.
11-15
Port Trunking
CLI: Viewing and Configuring Port Trunk Groups
Switch “A”
with ports set
to LACP
passive.
Switch “B”
with ports set
to LACP
passive.
Dynamic LACP trunk cannot automatically form because both
ends of the links are LACP passive.
(In this case spanning-tree blocking is needed to prevent a loop.
Switch “A”
with ports set
to LACP
active.
Switch “B”
with ports set
to LACP
passive.
Dynamic LACP trunk automatically forms because both
ends of the links are LACP and at least one end is LACP
active. (Spanning tree is not needed, and the clear
advantages are increased bandwidth and fault-tolerance.)
Figure 11-10. Example of Criteria for Automatically Forming a Dynamic LACP Trunk
Syntax: interface < port-list > lacp active
Configures < port-list > as LACP active. If the ports at the other
end of the links on < port-list > are configured as LACP passive,
then this command enables a dynamic LACP trunk group on
< port-list >.
This example uses ports C4 and C5 to enable a dynamic LACP trunk group.
ProCurve(config)# interface c4-c5 lacp active
Removing Ports from an Dynamic LACP Trunk Group. To remove a
port from dynamic LACP trunk operation, you must turn off LACP on the port.
(On a port in an operating, dynamic LACP trunk, you cannot change between
LACP Active and LACP passive without first removing LACP operation from
the port.)
11-16
Port Trunking
Web: Viewing Existing Port Trunk Groups
Caution
Unless spanning tree 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 spanning tree is not in use, ProCurve recommends
that you first disable the port or disconnect the link on that port.
Syntax: no interface < port-list > lacp
Removes < port-list > from any dynamic LACP trunk and
returns the ports in < port-list > to passive LACP.
In this example, port C6 belongs to an operating, dynamic LACP trunk. To
remove port C6 from the dynamic trunk and return it to passive LACP, you
would do the following:
ProCurve(config)# no interface c6 lacp
ProCurve(config)# interface c6 lacp passive
Note that in the above example, if the port on the other end of the link is
configured for active LACP or static LACP, the trunked link will be reestablished almost immediately.
Web: Viewing Existing Port Trunk
Groups
While the web browser interface does not enable you to configure a port trunk
group, it does provide a view of an existing trunk group.
To view any port trunk groups:
Click on the Status tab.
Click on [Port Status].
11-17
Port Trunking
Trunk Group Operation Using LACP
Trunk Group Operation Using LACP
The switch can automatically configure a dynamic LACP trunk group or you
can manually configure a static LACP trunk group.
Note
LACP requires full-duplex (FDx) links of the same media type (10/100Base-T,
100FX, etc.) and the same speed, and enforces speed and duplex conformance
across a trunk group. 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 negotiation selects FDx), and 10FDx, 100FDx,
and 1000FDx settings.
LACP trunk status commands include:
Trunk Display Method
Static LACP Trunk
Dynamic LACP Trunk
CLI show lacp command
Included in listing.
Included in listing.
CLI show trunk command
Included in listing.
Not included.
Port/Trunk Settings screen in menu interface
Included in listing.
Not included
Thus, to display a listing of dynamic LACP trunk ports, you must use the show
lacp command.
In most cases, trunks configured for LACP on the switches covered in this guide
operate as described in table 11-4 on the next page.
11-18
Port Trunking
Trunk Group Operation Using LACP
Table 11-4. LACP Trunk Types
LACP Port Trunk Operation
Configuration
Dynamic LACP
This option automatically establishes an 802.3ad-compliant trunk group, with LACP for the port Type
parameter and DynX for the port Group name, where X is an automatically assigned value from 1 to 60,
depending on how many dynamic and static trunks are currently on the switch. (The switch allows a
maximum of 60 trunk groups in any combination of static and dynamic trunks.)
Note: Dynamic LACP trunks operate only in the default VLAN (unless GVRP is enabled and Forbid is
used to prevent the trunked ports from joining the default VLAN). Thus, if an LACP dynamic port
forms using ports that are not in the default VLAN, the trunk will automatically move to the default
VLAN unless GVRP operation is configured to prevent this from occurring. In some cases, this can
create a traffic loop in your network. For more on this topic, refer to “VLANs and Dynamic LACP” on
page 11-23.
Under the following conditions, the switch automatically establishes a dynamic LACP port trunk group
and assigns a port Group name:
• The ports on both ends of each link have compatible mode settings (speed and duplex).
• The port on one end of each link must be configured for LACP Active and the port on the other end
of the same link must be configured for either LACP Passive or LACP Active. For example:
Switch 1
Switch 2
Port X:
LACP Enable: Active
Port A:
Active-to-Active
Port Y:
LACP Enable: Active
LACP Enable: Active
Port B:
Active-to-Passive
LACP Enable: Passive
Either of the above link configurations allow a dynamic LACP trunk link.
Backup Links: A maximum of eight operating links are allowed in the trunk, but, with dynamic LACP,
you can configure one or more additional (backup) links that the switch automatically activates if a
primary link fails. To configure a link as a standby for an existing eight-port dynamic LACP trunk, ensure
that the ports in the standby link are configured as either active-to-active or active-to-passive between
switches.
Displaying Dynamic LACP Trunk Data: To list the configuration and status for a dynamic LACP trunk,
use the CLI show lacp command.
Note: The dynamic trunk is automatically created by the switch, and is not listed in the static trunk
listings available in the menu interface or in the CLI show trunk listing.
11-19
Port Trunking
Trunk Group Operation Using LACP
LACP Port Trunk Operation
Configuration
Static LACP
11-20
Provides a manually configured, static LACP trunk to accommodate these conditions:
• The port on the other end of the trunk link is configured for a static LACP trunk.
• You want to configure non-default spanning tree or IGMP parameters on an LACP trunk group.
• You want an LACP trunk group to operate in a VLAN other than the default VLAN and GVRP is
disabled. (Refer to “VLANs and Dynamic LACP” on page 11-23.)
• You want to use a monitor port on the switch to monitor an LACP trunk.
The trunk operates if the trunk group on the opposite device is running one of the following trunking
protocols:
• Active LACP
• Passive LACP
• Trunk
This option uses LACP for the port Type parameter and TrkX for the port Group parameter, where X is
an automatically assigned value in a range corresponding to the maximum number of trunks the switch
allows. (The table on page 11-5 lists the maximum number of trunk groups allowed on the switches
covered in this guide.)
Displaying Static LACP Trunk Data: To list the configuration and status for a static LACP trunk, use the
CLI show lacp command. To list a static LACP trunk with its assigned ports, use the CLI show trunk
command or display the menu interface Port/Trunk Settings screen.
Static LACP does not allow standby ports.
Port Trunking
Trunk Group Operation Using LACP
Default Port Operation
In the default configuration, LACP is disabled for all ports. If LACP is not
configured as Active on at least one end of a link, then the port does not try
to detect a trunk configuration and operates as a standard, untrunked port.
Table 11-5 lists the elements of per-port LACP operation. To display this data
for a switch, execute the following command in the CLI:
ProCurve> show lacp
Table 11-5. LACP Port Status Data
Status Name
Meaning
Port Numb
Shows the physical port number for each port configured for LACP operation (C1, C2, C3 …
). Unlisted port
numbers indicate that the missing ports are assigned to a static Trunk group are not configured for any
trunking.
LACP Enabled
Active: The port automatically sends LACP protocol packets.
Passive: The port does not automatically send LACP protocol packets, and responds only if it receives
LACP protocol packets from the opposite device.
A link having either two active LACP ports or one active port and one passive port can perform dynamic
LACP trunking. A link having two passive LACP ports will not perform LACP trunking because both ports
are waiting for an LACP protocol packet from the opposite device.
Note: In the default switch configuration, LACP is disabled for all ports.
Trunk Group
TrkX: This port has been manually configured into a static LACP trunk.
Trunk Group Same as Port Number: The port is configured for LACP, but is not a member of a port trunk.
Port Status
Up: The port has an active LACP link and is not blocked or in Standby mode.
Down: The port is enabled, but an LACP link is not established. This can indicate, for example, a port that
is not connected to the network or a speed mismatch between a pair of linked ports.
Disabled: The port cannot carry traffic.
Blocked: LACP, spanning tree has blocked the port. (The port is not in LACP Standby mode.) This may
be due to a (brief) trunk negotiation or a configuration error such as differing port speeds on the same
link or trying to connect the switch to more trunks than it can support. (See the table on page 11-5.)
Note: Some older devices are limited to four ports in a trunk. When eight LACP-enabled ports are
connected to one of these older devices, four ports connect, but the other four ports are blocked.
Standby: The port is configured for dynamic LACP trunking to another device, but the maximum number
of ports for the Dynamic trunk to that device has already been reached on either the switch or the other
device. This port will remain in reserve, or “standby” unless LACP detects that another, active link in the
trunk has become disabled, blocked, or down. In this case, LACP automatically assigns a Standby port,
if available, to replace the failed port.
LACP Partner
Yes: LACP is enabled on both ends of the link.
No: LACP is enabled on the switch, but either LACP is not enabled or the link has not been detected on
the opposite device.
11-21
Port Trunking
Trunk Group Operation Using LACP
Status Name
Meaning
LACP Status
Success: LACP is enabled on the port, detects and synchronizes with a device on the other end of the
link, and can move traffic across the link.
Failure: LACP is enabled on a port and detects a device on the other end of the link, but is not able to
synchronize with this device, and therefore not able to send LACP packets across the link. This can be
caused, for example, by an intervening device on the link (such as a hub), a bad hardware connection,
or if the LACP operation on the opposite device does not comply with the IEEE 802.3ad standard.
LACP Notes and Restrictions
802.1X (Port-Based Access Control) Configured on a Port. To maintain security, LACP is not allowed on ports configured for 802.1X authenticator
operation. If you configure port security on a port on which LACP (active or
passive) is configured, the switch removes the LACP configuration, displays
a notice that LACP is disabled on the port(s), and enables 802.1X on that port.
ProCurve(config)# aaa port-access authenticator b1
LACP has been disabled on 802.1x port(s).
ProCurve(config)#
The switch will not allow you to configure LACP on a port on which port
access (802.1X) is enabled. For example:
ProCurve(config)# int b1 lacp passive
Error configuring port < port-number >: LACP and 802.1x
cannot be run together.
ProCurve(config)#
To restore LACP to the port, you must first remove the port’s 802.1X configuration and then re-enable LACP active or passive on the port.
Port Security Configured on a Port. To maintain security, LACP is not
allowed on ports configured for port security. If you configure port security
on a port on which LACP (active or passive) is configured, the switch removes
the LACP configuration, displays a notice that LACP is disabled on the port(s),
and enables 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).
ProCurve(config)#
The switch will not allow you to configure LACP on a port on which port
security is enabled. For example:
11-22
Port Trunking
Trunk Group Operation Using LACP
ProCurve(config)# int a17 lacp passive
Error configuring port A17: LACP and port security cannot
be run together.
ProCurve(config)#
To restore LACP to the port, you must remove port security and re-enable
LACP active or passive.
Changing Trunking Methods. To convert a trunk from static to dynamic,
you must first eliminate the static trunk.
Static LACP Trunks. Where a port is configured for LACP (Active or
Passive), but does not belong to an existing trunk group, you can add that port
to a static trunk. Doing so disables dynamic LACP on that port, which means
you must manually configure both ends of the trunk.
Dynamic LACP Trunks. You can configure a port for LACP-active or LACPpassive, but on a dynamic LACP trunk you cannot configure the other options
that you can on static trunks. If you want to manually configure a trunk, use
the trunk command. (Refer to “Using the CLI To Configure a Static or Dynamic
Trunk Group” on page 11-14.)
VLANs and Dynamic LACP. A dynamic LACP trunk operates only in the
default VLAN (unless you have enabled GVRP on the switch and use Forbid to
prevent the ports from joining the default VLAN).
■
If you want to use LACP for a trunk on a non-default VLAN and GVRP is
disabled, configure the trunk as a static trunk.
Blocked Ports with Older Devices. Some older devices are limited to four
ports in a trunk. When eight LACP-enabled ports are connected to one of these
older devices, four ports connect, but the other four ports are blocked. The
LACP status of the blocked ports is shown as “Failure”.
If one of the other ports becomes disabled, a blocked port will replace it (Port
Status becomes “Up”). When the other port becomes active again, the replacement port goes back to blocked (Port Status is “Blocked”). It can take a few
seconds for the switch to discover the current status of the ports.
11-23
Port Trunking
Trunk Group Operation Using LACP
ProCurve(eth-B1-B8)# show lacp
LACP
PORT
NUMB
---B1
B2
B3
B4
B5
B6
B7
B8
LACP
ENABLED
------Active
Active
Active
Active
Active
Active
Active
Active
TRUNK
GROUP
------Dyn1
Dyn1
Dyn1
Dyn1
Dyn1
Dyn1
B7
B8
PORT
STATUS
------Up
Up
Up
Up
Blocked
Blocked
Down
Down
LACP
PARTNER
------Yes
Yes
Yes
Yes
Yes
Yes
No
No
LACP
STATUS
------Success
Success
Success
Success
Failure
Failure
Success
Success
Figure 11-11. Blocked Ports with LACP
■
If there are ports that you do not want on the default VLAN, ensure that
they cannot become dynamic LACP trunk members. Otherwise a traffic
loop can unexpectedly occur. For example:
VLAN-1
(Default
VLAN)
VLAN-1
(Default
VLAN)
VLAN-1
(Default
VLAN)
VLAN-1
(Default
VLAN)
VLAN-2
VLAN-2
VLAN-2
VLAN-2
If the ports in VLAN 2 are configured to allow a dynamic trunk (and GVRP is disabled), adding a
second link in VLAN 2 automatically forms a dynamic LACP trunk and moves the trunk to VLAN-1
(the default VLAN), which creates a traffic loop in VLAN 1 between the two switches and
eliminates the link in VLAN 2 between the two switches.
Figure 11-12. A Dynamic LACP Trunk Forming in a VLAN Can Cause a Traffic Loop
Easy control methods include either disabling LACP on the selected ports or
configuring them to operate in static LACP trunks.
11-24
Port Trunking
Trunk Group Operation Using LACP
Spanning Tree and IGMP. If Spanning Tree 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.
Half-Duplex and/or Different Port Speeds Not Allowed in LACP
Trunks. The ports on both sides of an LACP trunk must be configured for
the same speed and for full-duplex (FDx). The 802.3ad LACP standard specifies a full-duplex (FDx) requirement for LACP trunking. (10-gigabit ports
operate only at FDx.)
A port configured as LACP passive and not assigned to a port trunk can be
configured to half-duplex (HDx). However, in any of the following cases, a
port cannot be reconfigured to an HDx setting:
■
If the port is a 10-gigabit port.
■
If a port is set to LACP Active, you cannot configure it to HDx.
■
If a port is already a member of a static or dynamic LACP trunk, you cannot
configure it to HDx.
■
If a port is already set to HDx, the switch does not allow you to configure
it for a static or dynamic LACP trunk.
Dynamic/Static LACP Interoperation: A port configured for dynamic
LACP can properly interoperate with a port configured for static (TrkX) LACP,
but any ports configured as standby LACP links will be ignored.
11-25
Port Trunking
Trunk Group Operation Using the “Trunk” Option
Trunk Group Operation Using the
“Trunk” Option
This method creates a trunk group that operates independently of specific
trunking protocols and does not use a protocol exchange with the device on
the other end of the trunk. With this choice, the switch simply uses the SA/DA
method of distributing outbound traffic across the trunked ports without
regard for how that traffic is handled by the device at the other end of the
trunked links. Similarly, the switch handles incoming traffic from the trunked
links as if it were from a trunked source.
When a trunk group is configured with the trunk option, the switch automatically sets the trunk to a priority of “4” for spanning-tree operation (even if
spanning-tree is currently disabled. This appears in the running-config file as
spanning-tree Trkn priority 4. Executing write memory after configuring the trunk places the same entry in the startup-config file.
Use the Trunk option to establish a trunk group between a switch covered in
this guide and another device, where the other device’s trunking operation fails
to operate properly with LACP trunking configured on the switches.
11-26
Port Trunking
How the Switch Lists Trunk Data
How the Switch Lists Trunk Data
Static Trunk Group: Appears in the menu interface and the output from the
CLI show trunk and show interfaces commands.
Dynamic LACP Trunk Group: Appears in the output from the CLI show lacp
command.
Interface Option
Dynamic LACP
Trunk Group
Static LACP
Trunk Group
Static Non-Protocol
Menu Interface
No
Yes
Yes
CLI show trunk
No
Yes
Yes
CLI show interfaces
No
Yes
Yes
CLI show lacp
Yes
Yes
No
CLI show spanning-tree
No
Yes
Yes
CLI show igmp
No
Yes
Yes
CLI show config
No
Yes
Yes
Outbound Traffic Distribution Across
Trunked Links
The two trunk group options (LACP and Trunk) use source-destination
address pairs (SA/DA) for distributing outbound traffic over trunked links.
SA/DA (source address/destination address) causes the switch to distribute
outbound traffic to the links within the trunk group on the basis of source/
destination address pairs. That is, the switch sends traffic from the same
source address to the same destination address through the same trunked link,
and may also send traffic from the same source address to a different destination address through the same link or a different link, depending on the
mapping of path assignments among the links in the trunk. Likewise, the
switch distributes traffic for the same destination address but from different
source addresses through links depending on the path assignment.
11-27
Port Trunking
Outbound Traffic Distribution Across Trunked Links
The load-balancing is done on a per communication basis. Otherwise, traffic
is transmitted across the same path as shown in figure 11-13. That is, if Client
A attached to Switch 1 sends five packets of data to Server A attached to
Switch 2, the same link is used to send all five packets. The SA/DA address
pair for the traffic is the same. The packets are not evenly distributed across
any other existing links between the two switches; they all take the same path.
Client A
All five packets go through
the same link
Switch 1
Client B
Switch 2
Figure 11-13. Example of Single Path Traffic through a Trunk
The actual distribution of the traffic through a trunk depends on a calculation
using bits from the Source Address and Destination address. When an IP
address is available, the calculation includes the last five bits of the IP source
address and IP destination address, otherwise the MAC addresses are used.
The result of that process undergoes a mapping that determines which link
the traffic goes through. If you have only two ports in a trunk, it is possible
that all the traffic will be sent through one port even if the SA/DA pairs are
different. The more ports you have in the trunk, the more likely it is that the
traffic will be distributed among the links.
When a new port is added to the trunk, the switch begins sending traffic, either
new traffic or existing traffic, through the new link. As links are added or
deleted, the switch redistributes traffic across the trunk group. For example,
in figure 11-14 showing a three-port trunk, traffic could be assigned as shown
in table 11-6.
A
B
C
D
C1
Switch C 2
C3
Switch
W
X
Y
Z
Figure 11-14. Example of Port-Trunked Network
11-28
Port Trunking
Outbound Traffic Distribution Across Trunked Links
Table 11-6. Example of Link Assignments in a Trunk Group (SA/DA Distribution)
Source:
Destination:
Link:
Node A
Node W
1
Node B
Node X
2
Node C
Node Y
3
Node D
Node Z
1
Node A
Node Y
2
Node B
Node W
3
Because the amount of traffic coming from or going to various nodes in a
network can vary widely, it is possible for one link in a trunk group to be fully
utilized while other links in the same trunk have unused bandwidth capacity
even if the assignments were evenly distributed across the links in a trunk.
11-29
12
Port Traffic Controls
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Jumbo Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Operating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Configuring Jumbo Frame Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Viewing the Current Jumbo Configuration . . . . . . . . . . . . . . . . . . 12-5
Enabling or Disabling Jumbo Traffic on a VLAN . . . . . . . . . . . . . 12-7
Configuring a Maximum Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
SNMP Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Displaying the Maximum Frame Size . . . . . . . . . . . . . . . . . . . . . . 12-8
Operating Notes for Maximum Frame Size . . . . . . . . . . . . . . . . . 12-8
Operating Notes for Jumbo Traffic-Handling . . . . . . . . . . . . . . . . . . . 12-9
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
12-1
Port Traffic Controls
Overview
Overview
Feature
Default
Menu
CLI
Web
Jumbo Packets
Disabled
n/a
12-2
n/a
This chapter includes:
■
Jumbo Frames: Enables ports operating at 1 Gbps or 10 Gbps speeds to
accept inbound frames of up to 9220 bytes when configured for jumbo
traffic.
Jumbo Frames
Feature
display VLAN jumbo status
configure jumbo VLANs
Default
Menu
CLI
Web
n/a
—
12-5
—
Disabled
—
12-7
—
The Maximum Transmission Unit (MTU) is the maximum size IP frame the
switch can receive for Layer 2 frames inbound on a port. The switch drops any
inbound frames larger than the MTU allowed on the port. On ports operating
at 10 Mbps or 100 Mbps, the MTU is fixed at 1522 bytes. However, ports
operating at 1 Gbs or 10 Gbps speeds accept forward frames of up to 9220
bytes (including four bytes for a VLAN tag) when configured for jumbo traffic.
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 Gbs 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.)
Terminology
Jumbo Frame: An IP frame exceeding 1522 bytes in size. The maximum
Jumbo frame size is 9220 bytes. (This size includes 4 bytes for the VLAN
tag.)
12-2
Port Traffic Controls
Jumbo Frames
Jumbo VLAN: A VLAN configured to allow inbound jumbo traffic. All ports
belonging to a jumbo and operating at 1 Gbps or higher can receive jumbo
frames from external devices. If the switch is in a meshed domain, then
all meshed ports (operating at 1 Gbps or higher) on the switch will accept
jumbo traffic from other devices in the mesh.
MTU (Maximum Transmission Unit): This is the maximum-size IP frame
the switch can receive for Layer 2 frames inbound on a port. The switch
allows jumbo frames of up to 9220 bytes. (This size includes 4 bytes for
the VLAN tag.)
Standard MTU: An IP frame of 1522 bytes in size. (This size includes 4 bytes
for the VLAN tag.)
Operating Rules
■
Required Port Speed: This feature allows inbound and outbound jumbo
frames on ports operating at speeds of 1 gigabit or higher. At lower port
speeds, only standard (1522-byte or smaller) frames are allowed, regardless of the jumbo configuration.
■
Switch Meshing: If you enable jumbo traffic on a VLAN, then all meshed
ports on the switch will be enabled to support jumbo traffic. (On a given
meshed switch, every meshed port operating at 1 Gbps or higher becomes
a member of every VLAN configured on the switch.)
■
GVRP Operation: A VLAN enabled for jumbo traffic cannot be used to
create a dynamic VLAN. A port belonging to a statically configured, jumboenabled VLAN cannot join a dynamic VLAN.
■
Port Adds and Moves: If you add a port to a VLAN that is already
configured for jumbo traffic, the switch enables that port to receive jumbo
traffic. If you remove a port from a jumbo-enabled VLAN, the switch
disables jumbo traffic capability on the port only if the port is not currently
a member of another jumbo-enabled VLAN. This same operation applies
to port trunks.
■
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. For a method to allow only some
ports in a VLAN to receive jumbo traffic, refer to “Configuring a Maximum
Frame Size” on page 12-7.
12-3
Port Traffic Controls
Jumbo Frames
Configuring Jumbo Frame Operation
Command
Page
show vlans
12-5
show vlans ports < port-list > 12-6
show vlans < vid >
12-7
jumbo
12-7
jumbo max-frame-size
12-7
Overview
12-4
1.
Determine the VLAN membership of the ports or trunks through which
you want the switch to accept inbound jumbo traffic. For operation with
GVRP enabled, refer to the GVRP topic under “Operating Rules”, above.
2.
Ensure that the ports through which you want the switch to receive jumbo
frames are operating at least at gigabit speed. (Check the Mode field in the
output for the show interfaces brief < port-list > command.)
3.
Use the jumbo command to enable jumbo frames on one or more VLANs
statically configured in the switch. (All ports belonging to a jumboenabled VLAN can receive jumbo frames.
4.
Execute write memory to save your configuration changes to the startupconfig file.
Port Traffic Controls
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. (For more
information refer to “Configuring a Maximum Frame Size”
on page 12-7.) See Figure 12-1, below.
Indicates which static
VLANs are configured to
enable jumbo frames.
Figure 12-1. Example Listing of Static VLANs To Show Jumbo Status Per VLAN
Syntax: show vlans ports < port-list >
Lists the static VLANs to which the specified port(s) belong,
including the Jumbo column to indicate which VLANs are
configured to support jumbo traffic. Entering only one port
in < port-list > results in a list of all VLANs to which that port
belongs. Entering multiple ports in < port-list > results in a
superset list that includes the VLAN memberships of all ports
in the list, even though the individual ports in the list may
belong to different subsets of the complete VLAN listing. For
example, if port 1 belongs to VLAN 1, port 2 belongs to VLAN
10, and port 3 belongs to VLAN 15, then executing this
command with a < port-list > of 1-3 results in a listing of all
three VLANs, even though none of the ports belong to all three
VLANS. (Refer to Figure 12-2.)
12-5
Port Traffic Controls
Jumbo Frames
Indicates which static
VLANs are configured to
enable jumbo frames.
Figure 12-2. Example of Listing the VLAN Memberships for a Range of Ports
Syntax: show vlans < vid >
This command shows port membership and jumbo
configuration for the specified < vid >.
Lists the ports belonging to VLAN
100 and whether the VLAN is
enabled for jumbo frame traffic.
Figure 12-3. Example of Listing the Port Membership and Jumbo Status for a VLAN
12-6
Port Traffic Controls
Jumbo Frames
Enabling or Disabling Jumbo Traffic on a VLAN
Syntax: vlan < vid > jumbo
[ no ] vlan < vid > jumbo
Configures the specified VLAN to allow jumbo frames on all
ports on the switch that belong to that VLAN. If the VLAN is
not already configured on the switch, vlan < vid > jumbo also
creates the VLAN. Note that a port belonging to one jumbo
VLAN can receive jumbo frames through any other VLAN
statically configured on the switch, regardless of whether the
other VLAN is enabled for jumbo frames. The [no] form of the
command disables inbound jumbo traffic on all ports in the
specified VLAN that do not also belong to another VLAN that
is enabled for jumbo traffic. In a VLAN context, the command
forms are jumbo and no jumbo. (Default: Jumbos disabled on
the specified VLAN.)
Configuring a Maximum Frame Size
You can globally set a maximum frame size for Jumbo frames that will support
values from 1518 bytes to 9216 bytes for untagged frames.
Syntax: jumbo max-frame-size <size>
Sets the maximum frame size for Jumbo frames. The range
is from 1518 bytes to 9216 bytes.
Note: The jumbo max-frame-size is set on a GLOBAL level.
Default: 9216 bytes
SNMP Implementation
Jumbo Maximum Frame Size.
The maximum frame size for Jumbos is supported with the following proprietary MIB object:
hpSwitchMaxFrameSize OBJECT-TYPE
This is the value of the global max-frame-size supported by the switch. The
default value is set to 9216 bytes.
12-7
Port Traffic Controls
Jumbo Frames
Jumbo IP MTU.
The IP MTU for Jumbos is supported with the following proprietary MIB
object:
hpSwitchIpMTU OBJECT-TYPE
This is the value of the global Jumbos IP MTU (or L3 MTU) supported by the
switch. The default value is set to 9198 bytes (a value that is 18 bytes less than
the largest possible maximum frame size of 9216 bytes). This object can only
be used in switches which support max-frame-size and ip-mtu configuration.
Displaying the Maximum Frame Size
Use the show jumbos command to display the globally configured untagged
maximum frame size for the switch.
ProCurve(config)# show jumbos
Jumbos Global Values
Configured :
In Use
:
MaxFrameSize : 9216
MaxFrameSize : 9216
Ip-MTU : 9198
Ip-MTU : 9198
Figure 13. Displaying the Maximum Frame Size and IP MTU Values
Operating Notes for Maximum Frame Size
12-8
■
When you set a maximum frame size for Jumbo frames, it must be on
a global level. You cannot use the jumbo max-frame-size command on
a per-port or per-VLAN basis.
■
The original way to configure Jumbo frames remains the same, which
is per-VLAN, but you cannot set a maximum frame size per-VLAN.
■
Jumbo support must be enabled for a VLAN from the CLI or through
SNMP.
■
Setting the maximum frame size does not require a reboot.
■
When you upgrade to a version of software that supports setting the
maximum frame size from a version that did not, the max-frame-size
value is set automatically to 9216 bytes.
■
Configuring a Jumbo maximum frame size on a VLAN allows frames
up to max-frame-size even though other VLANs of which the port is a
member are not enabled for Jumbo support.
Port Traffic Controls
Jumbo Frames
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 performance.
■
You can configure the default, primary, and/or (if configured) the management VLAN to accept jumbo frames on all ports belonging to the VLAN.
■
When the switch applies the default MTU (1522-bytes) to a VLAN, all ports
in the VLAN can receive incoming frames of up to 1522 bytes in length.
When the switch applies the jumbo MTU (9220 bytes) to a VLAN, all ports
in that VLAN can receive incoming frames of up to 9220 bytes in length.
A port receiving frames exceeding the applicable MTU drops such frames,
causing the switch to generate an Event Log message and increment the
“Giant Rx” counter (displayed by show interfaces < port-list >).
■
The switch allows flow control and jumbo frame capability to co-exist on
a port.
■
The default MTU is 1522 bytes (including 4 bytes for the VLAN tag). The
jumbo MTU is 9220 bytes (including 4 bytes for the VLAN tag).
■
When a port is not a member of any jumbo-enabled VLAN, it drops all
jumbo traffic. If the port is receiving “excessive” inbound jumbo traffic,
the port generates an Event Log message to notify you of this condition.
This same condition generates a Fault-Finder message in the Alert log of
the switch’s web browser interface, and also increments the switch’s
“Giant Rx” counter.
■
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. Because a
port belonging to one jumbo-enabled VLAN can receive jumbo frames
through any VLAN to which it belongs, this method enables you to include
both jumbo-enabled and non-jumbo ports within the same VLAN. For
example, suppose you wanted to allow inbound jumbo frames only on
ports 6, 7, 12, and 13. However, these ports are spread across VLAN 100
and VLAN 200, and also share these VLANs with other ports you want
excluded from jumbo traffic. A solution is to create a third VLAN with the
sole purpose of enabling jumbo traffic on the desired ports, while leaving
the other ports on the switch disabled for jumbo traffic. That is:
VLAN 100
VLAN 200
VLAN 300
Ports
6-10
11-15
6, 7, 12, and 13
JumboEnabled?
No
No
Yes
12-9
Port Traffic Controls
Jumbo Frames
If there are security concerns with grouping the ports as shown for VLAN
300, you can either use source-port filtering to block unwanted traffic
paths or create separate jumbo VLANs, one for ports 6 and 7, and another
for ports 12 and 13.
■
Outbound Jumbo Traffic. Any port operating at 1 Gbps or higher can
transmit outbound jumbo frames through any VLAN, regardless of the
jumbo configuration. The VLAN is not required to be jumbo-enabled, and
the port is not required to belong to any other, jumbo enabled VLANs. This
can occur in situations where a non-jumbo VLAN includes some ports that
do not belong to another, jumbo-enabled VLAN and some ports that do
belong to another, jumbo-enabled VLAN. In this case, ports capable of
receiving jumbo frames can forward them to the ports in the VLAN that
do not have jumbo capability.
1
2
3
4
5
6
Jumbo-Enabled VLAN
Non-Jumbo VLAN
VLAN 10
VLAN 20
Port 3 belongs to both VLAN 10 and VLAN 20.
Jumbo frames received inbound on port 3 can be
forwarded out the Non-Jumbo ports 4, 5, and 6.
Figure 12-4. Forwarding Jumbo Frames Through Non-Jumbo Ports
Jumbo frames can also be forwarded out non-jumbo ports when the jumbo
frames received inbound on a jumbo-enabled VLAN are routed to another,
non-jumbo VLAN for outbound transmission on ports that have no memberships in other, jumbo-capable VLANs. Where either of the above
scenarios is a possibility, the downstream device must be configured to
accept the jumbo traffic. Otherwise, this traffic will be dropped by the
downstream device.
12-10
Port Traffic Controls
Jumbo Frames
Troubleshooting
A VLAN is configured to allow jumbo frames, but one or more ports
drops all inbound jumbo frames. The port may not be operating at 1 gigabit or higher. Regardless of a port’s configuration, if it is actually operating at
a speed lower than 1 gigabit, it drops inbound jumbo frames. For example, if
a port is configured for Auto mode (speed-duplex auto), but has negotiated a
100 Mbps speed with the device at the other end of the link, then the port
cannot receive inbound jumbo frames. To determine the actual operating
speed of one or more ports, view the Mode field in the output for the following
command:
show interfaces brief < port-list >
A non-jumbo port is generating “Excessive undersize/giant frames”
messages in the Event Log. The switches can transmit outbound jumbo
traffic on any port, regardless of whether the port belongs to a jumbo VLAN.
In this case, another port in the same VLAN on the switch may be jumboenabled through membership in a different, jumbo-enabled VLAN, and may
be forwarding jumbo frames received on the jumbo VLAN to non-jumbo ports.
Refer to “Outbound Jumbo Traffic” on page 12-10.
12-11
13
Configuring for Network Management
Applications
Contents
Using SNMP Tools To Manage the Switch . . . . . . . . . . . . . . . . . . . . . . 13-3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
SNMP Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Configuring for SNMP version 1 and 2c Access to the Switch . . . . . 13-5
Configuring for SNMP Version 3 Access to the Switch . . . . . . . . . . . 13-6
SNMP Version 3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Enabling SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Group Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
SNMPv3 Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Menu: Viewing and Configuring non-SNMP version 3
Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
CLI: Viewing and Configuring SNMP Community Names . . . . 13-16
SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Supported Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
General Steps for Configuring SNMP Notifications . . . . . . . . . 13-19
SNMPv1 and SNMPv2c Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Configuring an SNMP Trap Receiver . . . . . . . . . . . . . . . . . . . . . . 13-20
Enabling SNMPv2c Informs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Configuring SNMPv3 Notifications . . . . . . . . . . . . . . . . . . . . . . . 13-24
Managing Network Security Notifications . . . . . . . . . . . . . . . . . 13-27
Enabling Link-Change Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Configuring the Source IP Address for SNMP Notifications . . 13-30
Displaying SNMP Notification Configuration . . . . . . . . . . . . . . . 13-32
Configuring Listening Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34
Advanced Management: RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
13-1
Configuring for Network Management Applications
Contents
LLDP (Link-Layer Discovery Protocol) . . . . . . . . . . . . . . . . . . . . . . . 13-36
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
General LLDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
Packet Boundaries in a Network Topology . . . . . . . . . . . . . . . . . . . . 13-39
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Options for Reading LLDP Information Collected by the Switch . . 13-42
LLDP and LLDP-MED Standards Compatibility . . . . . . . . . . . . . . . . 13-42
LLDP Operating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43
Configuring LLDP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Viewing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . 13-44
Configuring Global LLDP Packet Controls . . . . . . . . . . . . . . . . . 13-46
Configuring SNMP Notification Support . . . . . . . . . . . . . . . . . . . 13-50
Configuring Per-Port Transmit and Receive Modes . . . . . . . . . 13-51
Configuring Basic LLDP Per-Port Advertisement Content . . . . 13-52
Configuring Support for Port Speed and Duplex
Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
LLDP-MED (Media-Endpoint-Discovery) . . . . . . . . . . . . . . . . . . . . . 13-55
LLDP-MED Topology Change Notification . . . . . . . . . . . . . . . . . 13-58
LLDP-MED Fast Start Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Advertising Device Capability, Network Policy, PoE Status
and Location Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Configuring Location Data for LLDP-MED Devices . . . . . . . . . 13-63
Displaying Advertisement Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
Displaying Switch Information Available for Outbound
Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
Displaying LLDP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
LLDP Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
LLDP and CDP Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
LLDP and CDP Neighbor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
CDP Operation and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 13-79
13-2
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Using SNMP Tools To Manage the Switch
Overview
You can manage the switch via SNMP from a network management station
running an application such as
ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+). For more on
PCM and PCM+, visit the ProCurve Networking 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.
This section includes:
■
An overview of SNMP management for the switch
■
Configuring the switches for:
■
•
SNMP Communities (page 13-12)
•
Trap Receivers and Authentication Traps (page 13-18)
Information on advanced management through RMON Support (page
13-35)
To implement SNMP management, the switch must have an IP address,
configured either manually or dynamically (using DHCP or Bootp). If multiple
VLANs are configured, each VLAN interface should have its own IP address.
For DHCP use with multiple VLANs, refer to the section titled “The Primary
VLAN” in the “Static Virtual LANs (VLANs)” chapter of the Advanced Traffic
Management Guide for your switch.
Note
If you use the switch’s Authorized IP Managers and Management VLAN
features, ensure that the SNMP management station and/or the choice of
switch port used for SNMP access to the switch are compatible with the access
controls enforced by these features. Otherwise, SNMP access to the switch
will be blocked. For more on Authorized IP Managers, refer to the Access
Security Guide for your switch. (The latest version of this guide is available
on the ProCurve Networking web site.) For information on the Management
13-3
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
VLAN feature, refer to the section titled “The Secure Management VLAN” in
the “Static Virtual LANs (VLANs)” chapter of the Advanced Traffic
Management Guide for your switch.
13-4
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMP Management Features
SNMP management features on the switch include:
■
SNMP version 1, version 2c, or version 3 over IP
■
Security via configuration of SNMP communities (page 13-12)
■
Security via authentication and privacy for SNMP Version 3 access
■
Event reporting via SNMP
•
Version 1 traps
•
RMON: groups 1, 2, 3, and 9
■
ProCurve Manager/Plus support
■
Standard MIBs, such as the Bridge MIB (RFC 1493), Ethernet MAU MIB
(RFC 1515), and others.
The switch SNMP agent also uses certain variables that are included in a
Hewlett-Packard proprietary MIB (Management Information Base) file. If you
are using HP OpenView, you can ensure that it is using the latest version of
the MIB file by downloading the file to the OpenView database. To do so, go
to the HP support web site at:
www.hp.com/# Support
Configuring for SNMP version 1 and 2c Access to the
Switch
SNMP access requires an IP address and subnet mask configured on the
switch. (Refer to “IP Configuration” on page 8-2.) If you are using DHCP/Bootp
to configure the switch, ensure that the DHCP/Bootp process provides the IP
address. (Refer to “DHCP/Bootp Operation” on page 8-12.)
Once an IP address has been configured, the main steps for configuring SNMP
version 1 and version 2c access management features are:
1.
Configure the appropriate SNMP communities. (Refer to “SNMPv3 Communities” on page 13-12.)
2.
Configure the appropriate trap receivers. (Refer to “SNMP Notifications”
on page 13-18.)
3.
Optionally, configure the listening mode if your switch has a separate outof-band management port. (Refer to “Listening Mode” on page 13-34.)
In some networks, authorized IP manager addresses are not used. In this case,
all management stations using the correct community name may access the
switch with the View and Access levels that have been set for that community.
13-5
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
If you want to restrict access to one or more specific nodes, you can use the
switch’s IP Authorized Manager feature. (Refer to the Access Security Guide
for your switch.)
Caution
For ProCurve Manager (PCM) version 1.5 or earlier (or any TopTools version),
deleting the “public” community disables some network management
functions (such as traffic monitoring, SNMP trap generation, and threshold
setting). If network management security is a concern, and you are using the
above software versions, ProCurve recommends that you change the write
access for the “public” community to “Restricted”.
Configuring for SNMP Version 3 Access to the Switch
SNMP version 3 (SNMPv3) access requires an IP address and subnet mask
configured on the switch. (Refer to “IP Configuration” on page 8-2.) If you are
using DHCP/Bootp to configure the switch, ensure that the DHCP/Bootp
process provides the IP address. (See “DHCP/Bootp Operation” on page 8-12.)
Once an IP address has been configured, the main steps for configuring SNMP
version 3 access management features are:
1.
Enable SNMPv3 for operation on the switch (Refer to “SNMP Version 3
Commands” on page 13-7)
2.
Configure the appropriate SNMP users (Refer to “SNMPv3 Users” on page
13-8)
3.
Configure the appropriate SNMP communities. (Refer to “SNMPv3 Communities” on page 13-12.)
4.
Configure the appropriate trap receivers. (Refer to “SNMP Notifications”
on page 13-18.)
In some networks, authorized IP manager addresses are not used. In this case,
all management stations using the correct User and community name may
access the switch with the View and Access levels that have been set for that
community. If you want to restrict access to one or more specific nodes, you
can use the switch’s IP Authorized Manager feature. (Refer to the Access
Security Guide for your switch.)
13-6
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMP Version 3 Commands
SNMP version 3 (SNMPv3) adds some new commands to the CLI for
configuring SNMPv3 functions. To enable SMNPv3 operation on the switch,
use the snmpv3 enable command. An initial user entry will be generated with
MD5 authentication and DES privacy.
You may (optionally) restrict access to only SNMPv3 agents by using the
snmpv3 only command. To restrict write-access to only SNMPv3 agents, use
the snmpv3 restricted-access command.
Caution
Restricting access to only version 3 messages will make the community named
“public” inaccessible to network management applications (such as autodiscovery, traffic monitoring, SNMP trap generation, and threshold setting)
from operating in the switch.
Syntax: [no] snmpv3 enable
Enable and disable the switch for access from SNMPv3
agents. This includes the creation of the initial user record.
[no] snmpv3 only
Enables or disables restrictions to access from only SNMPv3
agents. When enabled, the switch will reject all non-SNMPv3
messages.
[no] snmpv3 restricted-access
Enables or disables restrictions from all non-SNMPv3 agents
to read only access.
show snmpv3 enable
Displays the operating status of SNMPv3.
show snmpv3 only
Displays status of message reception of non-SNMPv3
messages.
show snmpv3 restricted-access
Displays status of write messages of non-SNMPv3 messages.
13-7
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Enabling SNMPv3
The snmpv3 enable command allows the switch to:
■
Receive SNMPv3 messages.
■
Configure initial users.
■
Restrict non-version 3 messages to “read only” (optional).
Figure 13-1 shows an example of how to use the snmpv3 enable command.
Note:
SNMP
Ve r s i o n 3
Initial Users
To create new users, most SNMPv3 management software requires an initial
user record to clone. The initial user record can be downgraded and provided
with fewer features, but not upgraded by adding new features. For this reason
it is recommended that when you enable SNMPv3, you also create a second
user with SHA authentication and DES privacy.
Enable SNMPv3
Create initial user models for SNMPv3
Management Applications
Set restriction on
non-SNMPv3 messages
Figure 13-1. Example of SNMP version 3 Enable Command
SNMPv3 Users
To use SNMPv3 on the switch, you must configure the users that will be
assigned to different groups. To configure SNMP users on the switch:
13-8
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Caution
1.
Configure users in the User Table with the snmpv3 user command. To view
the list of configured users, enter the show snmpv3 user command (see
“Adding Users” on page 13-9).
2.
Assign users to Security Groups based on their security model with the
snmpv3 group command (see “Assigning Users to Groups” on page 13-11).
If you add an SNMPv3 user without authentication and/or privacy to a group
that requires either feature, the user will not be able to access the switch.
Ensure that you add a user with the appropriate security level to an existing
security group.
Adding Users. To configure an SNMPv3 user, you must first add the user
name to the list of known users with the snmpv3 user command.
ProCurve(config)# snmpv3 user NetworkAdmin
Add user Network Admin with
no authentication or privacy.
ProCurve(config)# snmpv3 user NetworkMgr auth md5 authpass priv privpass
Add user Network Mgr with
authentication and privacy.
MD5 authentication is enabled and
the password is set to ”authpass”.
Privacy is enabled and the
password is set to “privpass”.
ProCurve(config)# show snmpv3 user
Status and Counters - SNMP v3 Global Configuration Information
User Name
----------------initial
NetworkAdmin
Auth. Protocol
-------------MD5
MD5
Privacy Protocol
---------------CFB AES-128
CBC-DES
Figure 13-2. Adding SNMPv3 Users and Displaying SNMPv3 Configuration
13-9
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMPv3 User Commands
Syntax: [no] snmpv3 user <user_name>
Adds or deletes a user entry for SNMPv3. Authorization
and privacy are optional, but to use privacy, you must
use authorization. When you delete a user, only the
<user_name> is required.
[auth <md5 | sha> <auth_pass>]
With authorization, you can set either MD5 or SHA
authentication. The authentication password
<auth_pass> must be 6-32 characters in length and is
mandatory when you configure authentication.
Default: None
[priv <des | aes> <priv_pass>]
With privacy, the switch supports DES (56-bit) and
AES (128-bit) encryption. The privacy password
<priv_pass> must be 6-32 characters in length and is
mandatory when you configure privacy.
Default: DES
Note: Only AES 128-bit and DES 56-bit encryption are
supported as privacy protocols. Other non-standard
encryption algorithms, such as AES-172, AES-256, and
3-DES are not supported.
Listing Users. To display the management stations configured to access the
switch with SNMPv3 and view the authentication and privacy protocols that
each station uses, enter the show snmpv3 user command.
Syntax: show snmpv3 user
This example displays information about the management stations configured
on VLAN 1 to access the switch.
ProCurve# configure terminal
ProCurve(config)# vlan 1
ProCurve(vlan-1)# show snmpv3 user
Status and Counters - SNMPv3 Global Configuration Information
User Name
----------initial
NetworkAdmin
13-10
Auth. Protocol
-------------MD5
MD5
Privacy Protocol
----------------CFB AES-128
CBC-DES
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Assigning Users to Groups. Then you must set the group access level for
the user by assigning the user to a group. This is done with the snmpv3 group
command. For more details on the MIBs access for a given group refer to
“Group Access Levels” on page 13-12.
Add NetworkAdmin to
operator noauth group
Add NetworkMgr to managerpriv group
Pre-assigned groups for
access by Version 2c and
version 1 management
applications
Figure 13-3. Example of Assigning Users to Groups
SNMPv3 Group Commands
Syntax: [no] snmpv3 group
This command assigns or removes a user to a security group
for access rights to the switch. To delete an entry, all of the
following three parameters must be included in the
command.
group <group_name>
This parameter identifies the group that has the privileges
that will be assigned to the user. For more details refer to
“Group Access Levels” on page 13-12.
user <user_name>
This parameter identifies the user to be added to the access
group. This must match the user name added with the snmpv3
user command.
sec-model <ver1 | ver2c | ver3>
This defines which security model to use for the added user.
A SNMPv3 access Group should only use the ver3 security
model.
13-11
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.
Group Name
Group Access Type
Group Read View
Group Write View
managerpriv
Ver3 Must have Authentication
and Privacy
ManagerReadView
ManagerWriteView
managerauth
Ver3 Must have Authentication
ManagerReadView
ManagerWriteView
operatorauth
Ver3 Must have Authentication
OperatorReadView
DiscoveryView
operatornoauth
Ver3 No Authentication
OperatorReadView
DiscoveryView
commanagerrw
Ver2c or Ver1
ManagerReadView
ManagerWriteView
commanagerr
Ver2c or Ver1
ManagerReadView
DiscoveryView
comoperatorrw
Ver2c or Ver1
OperatorReadView
OperatorReadView
comoperatorr
Ver2c or Ver1
OperatorReadView
DiscoveryView
Each view allows you to view or modify a different set of MIBs.
Note
■
Manager Read View – access to all managed objects
■
Manager Write View – access to all managed objects except the following: vacmContextTable, vacmAccessTable, vacmViewTreeFamilyTable
■
OperatorReadView – no access to icfSecurityMIB, hpSwitchIpTftpMode, vacmContextTable, vacmAccessTable, vacmViewTreeFamilyTable, usmUserTable, snmpCommunityTable
■
Discovery View – Access limited to samplingProbe MIB.
All access groups and views are predefined on the switch. There is no method
to modify or add groups or views to those that are pre-defined on the switch.
SNMPv3 Communities
SNMP commuities are supported by the switch to allow management
applications that use version 2c or version 1 to access the switch. The
communities are mapped to Group Access Levels that are used for version 2c
or version 1 support. For more information refer to “Group Access Levels” on
page 13-12. This mapping will happen automatically based on the communities
access privileges, but special mappings can be added with the snmpv3
community command.
13-12
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Syntax: [no] snmpv3 community
This command maps or removes a mapping of a
community name to a group access level. To remove a
mapping you, only need to specify the index_name
parameter.
index <index_name>
This is an index number or title for the mapping. The
values of 1-5 are reserved and can not be mapped.
name <community_name>
This is the community name that is being mapped to a
group access level.
sec-name <security_name>
This is the group level to which the community is being
mapped. For more information refer to “Group Access
Levels” on page 13-12.
tag <tag_value>
This is used to specify which target address may have
access by way of this index reference.
Figure 13-4 shows the assigning of the Operator community on MgrStation1
to the CommunityOperatorReadWrite group. Any other Operator only has an
access level of CommunityOperatorReadOnly
Add mapping to allow write access for
Operator community on MgrStation1
Two Operator Access Levels
Figure 13-4. Assigning a Community to a Group Access Level
13-13
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMP Community Features
Feature
Default
show SNMP communities
configure identity information
Menu
CLI
n/a
page
13-14
page
13-16
none
—
page
13-17
public
configure community names
MIB view for a community name
manager
(operator, manager)
write access for default
community name
unrestricted
page
13-14
“
“
“
page
13-17
“
“
“
“
Web
—
—
Use SNMP communities to restrict access to the switch by SNMP management
stations by adding, editing, or deleting SNMP communities. You can configure
up to five SNMP communities, each with either an operator-level or a managerlevel view, and either restricted or unrestricted write access.
Using SNMP requires that the switch have an IP address and subnet mask
compatible with your network.
Caution
For ProCurve Manager (PCM) version 1.5 or earlier (or any TopTools version),
deleting the “public” community disables some network management
functions (such as traffic monitoring, SNMP trap generation, and threshold
setting). If network management security is a concern, and you are using the
above software versions, ProCurve recommends that you change the write
access for the “public” community to “Restricted”.
Menu: Viewing and Configuring non-SNMP version 3
Communities
To View, Edit, or Add SNMP Communities:
1.
From the Main Menu, Select:
2. Switch Configuration...
6. SNMP Community Names
13-14
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Note: This screen gives
an overview of the
SNMP communities
that are currently
configured. All fields in
this screen are readonly.
Add and Edit options are
used to modify the SNMP
options. See Figure 8-2.
Figure 13-5. The SNMP Communities Screen (Default Values)
2.
Press [A] (for Add) to display the following screen:
If you are adding a
community, the
fields in this screen
are blank.
If you are editing an
existing community,
the values for the
currently selected
Community appear
in the fields.
Type the value for this field.
Use the Space bar to select
values for other fields
Figure 13-6. The SNMP Add or Edit Screen
Need Help? If you need information on the options in each field, press
[Enter] to move the cursor to the Actions line, then select the Help option
on the Actions line. When you are finished with Help, press [E] (for Edit)
to return the cursor to the parameter fields.
3.
Enter the name you want in the Community Name field, and use the Space
bar to select the appropriate value in each of the other fields. (Use the
[Tab] key to move from one field to the next.)
4.
Press [Enter], then [S] (for Save).
13-15
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
CLI: Viewing and Configuring SNMP Community Names
Community Name Commands
Page
show snmp-server [<community-string>]
13-16
[no] snmp-server
13-17
[community <community-str>]
13-17
[host <community-str> <ip-addr>]
[<none | debug | all | not-info | critical>]
13-20
[enable traps <authentication>
13-28
[enable traps link-change <port-list>]
13-29
Listing Community Names and Values. This command lists the data for
currently configured SNMP community names (along with trap receivers and
the setting for authentication traps — refer to “SNMP Notifications” 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 “public” community name and another community named "blue-team"
Default
Community and
Settings
Non-Default
Community and
Settings
Trap Receiver
Data (See page
13-18.)
Figure 13-7. Example of the SNMP Community Listing with Two Communities
To list the data for only one community, such as the “public” community, use
the above command with the community name included. For example:
ProCurve# show snmp-server public
13-16
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Configuring Community Names and Values. The snmp-server command
enables you to add SNMP communities with either default or specific access
attributes, and to delete specific communities.
Syntax: [no] snmp-server community < community-name >
Configures a new community name. If you do not also
specify operator or manager, the switch automatically
assigns the community to the operator MIB view. If you
do not specify restricted or unrestricted, the switch
automatically assigns the community to restricted (readonly) access. The no form uses only the < communityname > variable and deletes the named community from
the switch.
[operator | manager]
Optionally assigns an access level. At the operator level
the community can access all MIB objects except the
CONFIG MIB. At the manager level the community can
access all MIB objects.
[restricted | unrestricted]
Optionally assigns MIB access type. Assigning the
restricted type allows the community to read MIB
variables, but not to set them. Assigning the unrestricted
type allows the community to read and set MIB
variables.
For example, to add the following communities:
Community
Access Level
Type of Access
red-team
manager
(Access to all MIB objects.)
unrestricted
(read/write)
blue-team
operator
(Access to all MIB objects
except the CONFIG MIB.)
restricted
(read-only)
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
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMP Notifications
The switches covered in this guide support:
■
SNMP version 1 or SNMP version 2c traps
■
SNMPv2c informs
■
SNMPv3 notification process, including traps
This section describes how to configure a switch to send network security and
link-change notifications to configured trap receivers.
Supported Notifications
By default, the following notifications are enabled on a switch:
■
Manager password changes
■
SNMP authentication failure
■
Link-change traps: when the link on a port changes from up to down
(linkDown) or down to up (linkUp)
■
Port-security (web, MAC, or 802.1X) authentication failure
■
Invalid password entered in a login attempt through a direct serial, Telnet,
or SSH connection
■
Inability to establish a connection with the RADIUS or TACACS+ authentication server
In addition, you can enable the switch to send the following types of
notifications to configured trap receivers. For information on how to
configure each notification, refer to the ProCurve software guide under which
the notification is listed.
■
13-18
Management and Configuration Guide:
•
Configuration changes
•
Instrumentation monitoring
•
Link-Layer Discovery Protocol (LLDP)
•
Ping tests
•
RMON
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
■
■
Advance Traffic Management Guide:
•
Loop protection
•
Spanning Tree (STP, RSTP, MSTP)
Access Security Guide:
•
MAC lockdown
•
MAC lockout
•
Uni-Directional Link Detection (UDLD)
General Steps for Configuring SNMP Notifications
To configure SNMP notifications, follow these general steps:
1.
Determine the versions of SNMP notifications that you want to use in your
network.
If you want to use SNMPv1 and SNMPv2c traps, you must also configure
a trap receiver. Refer to the following sections and follow the required
configuration procedures:
•
“SNMPv1 and SNMPv2c Traps” on page 13-20
•
“Configuring an SNMP Trap Receiver” on page 13-20
•
“Enabling SNMPv2c Informs” on page 13-22
If you want to use SNMPv3 notifications (including traps), you must also
configure an SNMPv3 management station. Follow the required configuration procedure in the following section:
•
2.
To reconfigure any of the SNMP notifications that are enabled by default
to be sent to a management station (trap receiver), refer to the following
section:
•
3.
“Configuring SNMPv3 Notifications” on page 13-24
“Enabling Link-Change Traps” on page 13-29
(Optional) Refer to the following sections to configure optional SNMP
notification features and verify the current configuration:
•
“Configuring the Source IP Address for SNMP Notifications” on page
13-30
•
“Displaying SNMP Notification Configuration” on page 13-32
13-19
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
SNMPv1 and SNMPv2c Traps
The switches covered in this guide support the following functionality from
earlier SNMP versions (SNMPv1 and SNMPv2c):
■
Trap receivers: A trap receiver is a management station to which the
switch sends SNMP traps and (optionally) event log messages sent from
the switch. From the CLI you can configure up to ten SNMP trap receivers
to receive SNMP traps from the switch.
■
Fixed or “Well-Known” Traps: A switch automatically sends fixed traps
(such as “coldStart”, “warmStart”, “linkDown”, and “linkUp”) to trap
receivers using the public community name. These traps cannot be redirected to other communities. If you change or delete the default public
community name, these traps are not sent.
■
Thresholds: A switch automatically sends all messages created when a
system threshold is reached to the network management station that
configured the threshold, regardless of the trap receiver configuration.
Configuring an SNMP Trap Receiver
Use the snmp-server host command to configure a trap receiver that can receive
SNMPv1 and SNMPv2c traps, and (optionally) event log messages. When you
configure a trap receiver, you specify its community membership,
management station IP address, and (optionally) the type of event log
messages to be sent.
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. However, no traps will be sent to that trap receiver until the
community to which it belongs has been configured on the switch.
13-20
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Syntax: snmp-server host <ipv4-addr | ipv6-addr> <community name>
Configures a destination network management station
to receive SNMPv1/v2c traps, and (optionally) event log
messages sent as traps from the switch, using the
specified community name and destination IPv4 or
IPv6 address. You can specify up to ten trap receivers
(network management stations). The default
community name is public.
[<none | all | non-info | critical | debug>]
(Optional) Configures the security level of the event log
messages you want to send as traps to a trap receiver
(see table 13-1, “Security Levels for Event Log Messages
Sent as Traps”).
• The type of event log message that you specify applies
only to event log messages, not to threshold traps.
• For each configured event level, the switch continues
to send threshold traps to all network management
stations that have the appropriate threshold level
configured.
• If you do not specify an event level, the switch uses
the default value (none) and sends no event log
messages as traps.
[<inform>]
(Optional) Configures the switch to send SNMPv2
inform requests when certain events occur. See
“Enabling SNMPv2c Informs” on page 13-22 for more
information.
Table 13-1. Security Levels for Event Log Messages Sent as Traps
Security Level
Action
None (default)
Sends no event log messages.
All
Sends all event log messages.
Non-Info
Sends all event log messages that are not for information only.
Critical
Sends only event log messages for critical error conditions.
Debug
Sends only event log messages needed to troubleshoot network- and
switch-level problems.
13-21
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
For example, to configure a trap receiver in a community named "red-team"
with an IP address of 10.28.227.130 to receive only "critical" event log
messages, you can enter the following command:
ProCurve(config)# snmp-server host 10.28.227.130 red-team
critical
Notes
To replace one community name with another for the same IP address, you
must first enter the no snmp-server host < community-name> <ipv4-address | ipv6address > command to delete the unwanted community name. Otherwise, if
you add a new community name with an IP address that is already used with
a different community name, two valid community name entries are created
for the same management station.
If you do not specify the event level ([<none | all | non-info | critical | debug>]),
the switch does not send event log messages as traps. However, "well-known"
traps and threshold traps (if configured) are still sent.
Enabling SNMPv2c Informs
On a switch enabled for SNMPv2c, you can use the snmp-server host inform
command to send inform requests when certain events occur. When an SNMP
Manager receives an inform request, it can send an SNMP response back to
the sending agent on the switch to let the agent know that the inform request
reached its destination.
If the sending agent on the switch does not receive an SNMP response back
from the SNMP Manager within the timeout period, the inform request may
be resent, based on the retry count value.
When you enable SNMPv2c inform requests to be sent, you must specify the
IP address and community name of the management station that will receive
the inform notification.
Syntax:
[no] snmp-server host <ipv4-addr | ipv6-addr> <community name>
inform [retries <count>] [timeout <interval>]]
Enables (or disables) the inform option for SNMPv2c on the
switch and allows you to configure options for sending
SNMP inform requests.
retries: Maximum number of times to resend an inform
request if no SNMP response is received. Default: 3
timeout: Number of seconds to wait for an acknowledgement
before resending the inform request. Default: 15 seconds
13-22
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Note
The retries and timeout values are not used to send trap requests.
To verify the configuration of SNMPv2c informs, enter the show snmp-server
command:
ProCurve(config)# show snmp-server
SNMP Communities
Community Name
MIB View Write Access
---------------- -------- -----------public
Manager Unrestricted
Trap Receivers
Link-Change Traps Enabled on Ports [All] : All
...
Address
Community
Events Sent Notify Type Retry Timeout
--------------------- --------------- ----------- ----------- ----- -------15.28.333.456
guest
All
inform
3
15
Excluded MIBs
Snmp Response Pdu Source-IP Information
Selection Policy
: Default rfc1517
SNMPv2c Inform
configuration
Trap Pdu Source-IP Information
Selection Policy
: Configured IP
Ip Address
: 10.10.10.10
Figure 13-8. Display of SNMPv2c Inform Configuration
13-23
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Configuring SNMPv3 Notifications
The SNMPv3 notification process allows messages that are passed via SNMP
between the switch and a network management station to be authenticated
and encrypted.
To configure SNMPv3 notifications, follow these steps:
1.
Enable SNMPv3 operation on the switch by entering the snmpv3 enable
command (see “SNMP Version 3 Commands” on page 13-7).
When SNMPv3 is enabled, the switch supports:
•
Reception of SNMPv3 notification messages (traps and informs)
•
Configuration of initial users
•
(Optional) Restriction of non-SNMPv3 messages to “read only”
2.
Configure SNMPv3 users by entering the snmpv3 user command (see
“SNMPv3 Users” on page 13-8). Each SNMPv3 user configuration is
entered in the User Table.
3.
Assign SNMPv3 users to security groups according to their level of access
privilege by entering the snmpv3 group command (see “Assigning Users to
Groups” on page 13-11).
4.
Define the name of an SNMPv3 notification configuration by entering the
snmpv3 notify command.
Syntax: [no] snmpv3 notify <notify_name> tagvalue <tag_name>
Associates the name of an SNMPv3 notification
configuration with a tag name used (internally) in
SNMPv3 commands. To delete a notification-to-tag
mapping, enter no snmpv3 notify <notify_name>.
notify < notify_name >
Specifies the name of an SNMPv3 notification
configuration.
tagvalue < tag_name >
Specifies the name of a tag value used in other SNMPv3
commands, such as snmpv3 targetaddress params taglist
<tag_name> in Step 5.
13-24
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
5.
Configure the target address of the SNMPv3 management station to which
SNMPv3 informs and traps are sent by entering the snmpv3 targetaddress
command.
Syntax: [no] snmpv3 targetaddress < ipv4-addr | ipv6-addr> < name >
Configures the IPv4 or IPv6 address, name, and
configuration filename of the SNMPv3 management
station to which notification messages are sent.
params < parms_name >
Name of the SNMPv3 station’s parameters file. The
parameters filename configured with params
<params_name> must match the params
<params_name> value entered with the snmpv3 params
command in Step 6.
taglist <tag_name> [tag_name] ...
Specifies the SNMPv3 notifications (identified by one
or more <tag_name> values) to be sent to the IP address
of the SNMPv3 management station.
You can enter more than one <tag_name> value. Each
<tag_name> value must be already associated with the
name of an SNMPv3 notification configuration entered
with the snmpv3 notify command in Step 4.
Use a blank space to separate <tag_name> values.
You can enter up to 103 characters in <tag_name>
entries following the taglist keyword.
[filter < none | debug | all | not-info | critical>]
(Optional) Configures the type of messages sent to a
management station. Default: none.
[udp-port < port >]
(Optional) Specifies the UDP port to use. Default: 162.
[port-mask < mask >]
(Optional) Specifies a range of UDP ports. Default: 0.
[addr-mask < mask >]
(Optional) Specifies a range of IP addresses as
destinations for notification messages. Default: 0.
[retries < value >]
(Optional) Number of times a notification is
retransmitted if no response is received. Range: 1-255.
Default: 3.
13-25
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Syntax: [no] snmpv3 targetaddress < ipv4-addr | ipv6-addr> < name >
[timeout < value >]
(Optional) Time (in millisecond increments) allowed
to receive a response from the target before notification
packets are retransmitted. Range: 0-2147483647.
Default: 1500 (15 seconds).
[max-msg-size<size>]
(Optional) Maximum number of bytes supported in a
notification message to the specified target. Default:
1472
Create a configuration record for the target address with the snmpv3
params command.
Syntax [no] snmpv3 params <params_name> user <user_name>
6.
Applies the configuration parameters and IP address
of an SNMPv3 management station (from the params
<params_name> value configured with the snmpv3
targetaddress command in Step 5) to a specified
SNMPv3 user (from the user <user_name> value
configured with the snmpv3 user command in Step 2).
If you enter the snmpv3 params user command, you must
also configure a security model (sec-model) and
message processing algorithm (msg-processing).
< sec-model < ver1 | ver2c | ver3 >
Configures the security model used for SNMPv3
notification messages sent to the management station
configured with the snmpv3 targetaddress command in
Step 5.
If you configure the security model as ver3, you must
also configure the message processing value as ver3.
< msg-processing < ver1 | ver2c | ver3 > [noaut | auth | priv]
Configures the algorithm used to process messages sent
to the SNMPv3 target address.
If you configure the message processing value as ver3
and the security model as ver3, you must also configure
a security services level (noauth, auth, or priv).
13-26
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
An example of how to configure SNMPv3 notification is shown here:
Params _name value in the snmpv3 targetaddress command
matches the params _name value in the snmpv3 params
command.
The tag _name value in snmpv3 notify command matches the
tag _name value in the snmpv3 targetaddress command.
Configuring the security model ver3 requires you to configure
message processing ver3 and a security service level.
Figure 13-9. Example of an SNMPv3 Notification Configuration
Managing Network Security Notifications
By default, a switch is enabled to send the SNMP notifications listed in
“Supported Notifications” on page 13-18 when a network security event (for
example, authentication failure) occurs. However, before security
notifications can be sent, you must first configure one or more trap receivers
or SNMPv3 management stations as described in:
■
“Configuring an SNMP Trap Receiver” on page 13-20
■
“Configuring SNMPv3 Notifications” on page 13-24
You can manage the default configuration of the switch to disable and reenable notifications to be sent for the following types of security events:
■
SNMP authentication failure
■
Port-security (web, MAC, or 802.1X) authentication failure
■
Invalid password entered in a login attempt through a direct serial, Telnet,
or SSH connection
■
Unable to establish a connection with the RADIUS or TACACS+ authentication server
■
Manager password changes
13-27
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
To enable or disable notification/traps for network security failures and other
security events, enter the snmp-server enable traps command.
Syntax: [no] snmp-server enable traps [snmp-auth | password-change-mgr | loginfailure-mgr | port-security | auth-server-fail]
Enables or disables sending one of the following types of
security notification to configured trap receivers:
• snmp-auth sends a trap for a failed authentication attempt via SNMP.
• password-change-mgr sends a trap when a manager password is
reset.
• login-failure-mgr sends a trap for a failed login with a manager
password.
• port-security sends a trap for a failed authentication attempt through
a web, MAC, or 801.X authentication session.
• auth-server-fail sends a trap if the connection with a RADIUS or
TACACS+ authentication server fails.
To determine the specific cause of a security event, check the event log in the
console interface to see why a trap was sent. For more information, refer to
“Using the Event Log for Troubleshooting Switch Problems” on page C-24.
To display the current configuration for network security notifications, enter
the show snmp-server traps command. Note that command output is a subset
of the information displayed with the show snmp-server command in Figure 1312.
13-28
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
ProCurve(config)# show snmp-server traps
Link-change
trap setting
Trap Receivers
Link-Change Traps Enabled on Ports [All] : A1-A24
Trap Category
-----------------------------SNMP Authentication
Password change
Login failures
Port-Security
Authorization Server Contact
ARP Protection
DHCP Snooping
Address
--------------15.255.5.225
Community
---------user1
Current Trap Configuration
-------------------------extended
enabled
Network security
notification settings
enabled
enabled
enabled
enabled
enabled
Events Sent
----------All
Notify Type
----------trap
Retry
----3
Timeout
------15
Excluded MIBs
Figure 13-10. Display of Configured Network Security Notifications
Enabling Link-Change Traps
By default a switch is enabled to send a trap when the link state on a port
changes from up to down (linkDown) or down to up (linkUp). To reconfigure
the switch to send link-change traps to configured trap receivers, enter the
snmp-server enable traps link-change command.
Syntax: [no] snmp-server enable traps link-change<port-list> [all]
Enables or disables the switch to send a link-change trap to
configured trap receivers when the link state on a port goes
from up to down or down to up.
Enter all to enable or disable link-change traps on all ports
on the switch.
13-29
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Configuring the Source IP Address for SNMP Notifications
The switch uses an interface IP address as the source IP address in IP headers
when sending SNMP notifications (traps and informs) or responses to SNMP
requests.
For multi-netted interfaces, the source IP address is the IP address of the
outbound interface of the SNMP reply, which may differ from the destination
IP address in the IP header of the received request. For security reasons, it
may be desirable to send an SNMP reply with the IP address of the destination
interface (or a specified IP address) on which the corresponding SNMP
request was received.
To configure the switch to use the source IP address on which an SNMP
request was received in SNMP notification/traps and replies, enter the snmpserver response-source and snmp-server trap-source commands.
Syntax: [no] snmp-server response-source [dst-ip-of-request | <ipv4-addr | ipv6addr>]
Specifies the source IP address of the SNMP response PDU.
The default SNMP response PDU uses the IP address of the
active interface from which the SNMP response was sent as
the source IP address.
The no form of the command resets the switch to the default
behavior (compliant with rfc-1517).
Default: Interface IP address
dst-ip-of-request: Destination IP address of the SNMP request
PDU that is used as the source IP address in an SNMP
response PDU.
<ipv4-addr | ipv6-addr>: User-defined interface IP address that
is used as the source IP address in an SNMP response PDU.
Both IPv4 and IPv6 addresses are supported.
For example, to use the IP address of the destination interface on which an
SNMP request was received as the source IP address in the IP header of SNMP
traps and replies, enter the following command:
ProCurve(config)# snmp-server response-source
dst-ip-of-request
13-30
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
To configure the switch to use a specified source IP address in generated trap
PDUs, enter the snmp-server trap-source command.
Syntax: [no] snmp-server trap-source [<ipv4-addr >]
Specifies the source IP address to be used for a trap PDU.
The no form of the command resets the switch to the default
behavior (compliant with rfc-1517).
Default: Use the interface IP address in generated trap PDUs.
<ipv4-addr >: User-defined interface IPv4 address that is used
as the source IP address in generated traps. IPv6 addresses
are not supported.
Notes
When you use the snmp-server response-source and snmp-server trap-source
commands, note the following behavior:
■
The snmp-server response-source and snmp-server trap-source commands
configure the source IP address for IPv4 interfaces only.
■
You must manually configure the snmp-server response-source value if you
wish to change the default user-defined interface IP address that is used
as the source IP address in SNMP traps (RFC 1517).
■
The values configured with the snmp-server response-source and snmpserver trap-source commands are applied globally to all interfaces that are
sending SNMP responses or SNMP trap PDUs.
■
Only the source IP address field in the IP header of the SNMP response
PDU can be changed.
■
Only the source IP address field in the IP header and the SNMPv1 Agent
Address field of the SNMP trap PDU can be changed.
To verify the configuration of the interface IP address used as the source IP
address in IP headers for SNMP replies and traps sent from the switch, enter
the show snmp-server command to display the SNMP policy configuration.
13-31
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
ProCurve(config)# show snmp-server
SNMP Communities
Community Name
MIB View Write Access
---------------- -------- -----------public
Manager Unrestricted
Trap Receivers
Link-Change Traps Enabled on Ports [All] : All
...
Excluded MIBs
Snmp Response Pdu Source-IP Information
Selection Policy
: dstIpOfRequest
Trap Pdu Source-IP Information
Selection Policy
: Configured IP
Ip Address
: 10.10.10.10
dstIpOfRequest: The
destination IP address of
the interface on which
an SNMP request is
received i s used as the
source IP address in
SNMP replies.
Figure 13-11. Display of Source IP Address Configuration
Displaying SNMP Notification Configuration
Use the show snmp-server command to display the currently configured:
■
Management stations (trap receivers)
■
Settings for network security notifications and link-change traps
■
SNMP communities
Syntax: show snmp-server
Displays the currently configured notification settings for
versions SNMPv1 and SNMPv2c traps, including SNMP
communities, trap receivers, link-change traps, and network
security notifications.
13-32
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
In the following example, the show snmp-server command output shows that
the switch has been configured to send SNMP traps and notifications to
management stations that belong to the “public”, “red-team”, and “blue-team”
communities.
ProCurve(config)# show snmp-server
SNMP Communities
Community Name
---------------public
blue-team
red-team
MIB View
-------Operator
Manager
Manager
SNMP Community
configuration
Write Access
-----------Restricted
Unrestricted
Unrestricted
Link-change
trap setting
Trap Receivers
Link-Change Traps Enabled on Ports [All] : All
Trap Category
-----------------------------SNMP Authentication
Password change
Login failures
Port-Security
Authorization Server Contact
ARP Protection
DHCP Snooping
Address
--------------10.28.227.200
10.28.227.105
10.28.227.120
...
Community
---------public
red-team
blue-team
Current Trap Configuration
-------------------------extended
enabled
Network security
enabled
notification
enabled
enabled
enabled
enabled
Events Sent
----------All
Critical
Not-INFO
Notify Type
----------trap
trap
trap
Retry
----3
3
3
Timeout
------15
15
15
Figure 13-12. Display of SNMP Notification Configuration
13-33
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Configuring Listening Mode
For switches that have a separate out-of-band management port, you can
specify whether a configured SNMP server listens for SNMP queries over the
out-of-band management interface, the data interface, or both. By default, the
switch listens over both interfaces.
This option is not available for switches that do not have a separate out-ofband management port. Refer to Appendix G, “Network Out-of-Band
Management (OOBM)” in this guide for more information on network out-ofband management.
The listening mode is set with parameters to the snmp-server command:
Syntax: snmp-server [listen <oobm | data | both>]
Enables or disables inbound SNMP access on a switch.
Use the no version of the command to disable inbound SNMP
access.
The listen parameter is available only on switches that have a
separate out-of-band management port. Values for this
parameter are:
•
oobm — inbound SNMP access is enabled only on
•
data — inbound SNMP access is enabled only on
•
both — inbound SNMP access is enabled on both
the out-of-band management port.
the data ports.
the out-of-band management port and on the data
ports. This is the default value.
Refer to Appendix G, “Network Out-of-Band Management” in
this guide for more information on out-of-band management.
The listen parameter is not available on switches that do not
have a separate out-of-band management port.
13-34
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Advanced Management: RMON
The switch supports RMON (Remote Monitoring) on all connected network
segments. This allows for troubleshooting and optimizing your network.
The following RMON groups are supported:
■
■
■
■
Ethernet Statistics (except the numbers of packets of different frame sizes)
Alarm
History (of the supported Ethernet statistics)
Event
The RMON agent automatically runs in the switch. Use the RMON
management station on your network to enable or disable specific RMON
traps and events. Note that you can access the Ethernet statistics, Alarm, and
Event groups from the ProCurve Manager network management software. For
more on ProCurve Manager, visit the ProCurve Networking web site at
www.procurve.com
Click on products index, then look for the ProCurve Manager topic under the
Network Manager bar.
13-35
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
LLDP (Link-Layer Discovery Protocol)
To standardize device discovery on all ProCurve switches, LLDP will be
implemented while offering limited read-only support for CDP as documented
in this manual. For the latest information on your switch model, consult the
Release Notes (available on the ProCurve Networking web site). If LLDP has
not yet been implemented (or if you are running an older version of software),
consult a previous version of the Management and Configuration Guide for
device discovery details.
Table 13-2. LLDP and LLDP-MED Features
Feature
View the switch’s LLDP configuration
Default
n/a
Menu
CLI
Web
—
page 13-44
—
Enable or disable LLDP on the switch
Enabled
—
page 13-40
—
Change the transmit interval (refresh-interval) for
LLDP packets
30 seconds
—
page 13-47
—
Change the holdtime multiplier for LLDP Packets
4 seconds
(holdtime-multiplier x refresh-interval = time-to-live)
—
page 13-40
—
Change the delay interval between advertisements
2 seconds
—
page 13-48
—
Changing the reinitialization delay interval
2 seconds
—
page 13-49
—
Configuring SNMP notification support
Disabled
—
page 13-50
—
Configuring transmit and receive modes
tx_rx
—
page 13-51
—
Configuring basic LLDP per-port advertisement
content
Enabled
—
page 13-52
—
Configuring port speed and duplex advertisements for Enabled
optional LLDP and mandatory LLDP-MED applications
—
page 13-71
—
Configuring topology change notification for LLDPMED
Enable
—
page 13-58
—
Changing the fast-start duration for LLDP-MED
5 sec
—
page 13-60
Configuring LLDP-MED Advertising
Enabled
—
page 13-52
Configuring LLDP-MED device location data
None
—
page 13-69
Displaying Advertisement Data and Statistics
n/a
—
page 13-73
—
LLDP (Link Layer Discovery Protocol): provides a standards-based
method for enabling the switches covered in this guide to advertise themselves
to adjacent devices and to learn about adjacent LLDP devices.
13-36
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
LLDP-MED (LLDP Media Endpoint Discovery): Provides an extension to
LLDP and is designed to support VoIP deployments.
Note
LLDP-MED is an extension for LLDP, and the switch requires that LLDP be
enabled as a prerequisite to LLDP-MED operation.
An SNMP utility can progressively discover LLDP devices in a network by:
1.
Reading a given device’s Neighbors table (in the Management Information
Base, or MIB) to learn about other, neighboring LLDP devices.
2.
Using the information learned in step 1 to find and read the neighbor
devices’ Neighbors tables to learn about additional devices, and so on.
Also, by using show commands to access the switch’s neighbor database for
information collected by an individual switch, system administrators can learn
about other devices connected to the switch, including device type
(capability) and some configuration information. In VoIP deployments using
LLDP-MED on the switches covered in this guide, additional support unique to
VoIP applications is also available. Refer to “LLDP-MED (Media-EndpointDiscovery)” on page 13-55.
Terminology
Adjacent Device: Refer to “Neighbor or Neighbor Device”.
Advertisement: See LLDPDU.
Active Port: A port linked to another active device (regardless of whether
MSTP is blocking the link).
ELIN (Emergency Location Identification Number): A valid telephone
number in the North American Numbering Plan format and assigned to a
multiline telephone system operator by the appropriate authority. This
number calls a public service answering point (PSAP) and relays automatic
location identification data to the PSAP.
LLDP: Link Layer Discovery Protocol:
•
Switches covered in this guide: IEEE 802.1AB
LLDP-Aware: A device that has LLDP in its operating code, regardless of
whether LLDP is enabled or disabled.
LLDP Device: A switch, server, router, or other device running LLDP.
13-37
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
LLDP Neighbor: An LLDP device that is either directly connected to another
LLDP device or connected to that device by another, non-LLDP Layer 2 device
(such as a hub) Note that an 802.1D-compliant switch does not forward LLDP
data packets even if it is not LLDP-aware.
LLDPDU (LLDP Data Unit): LLDP data packet are transmitted on active
links and include multiple TLVs containing global and per-port switch
information. In this guide, LLDPDUs are termed “advertisements” or
“packets”.
LLDP-MED (Link Layer Discover Protocol Media Endpoint
Discovery): The TIA telecommunications standard produced by engineering
subcommittee TR41.4, “VoIP Systems — IP Telephony infrastructure and
Endpoints” to address needs related to deploying VoIP equipment in IEEE 802based environments. This standard will be published as ANSI/TIA-1057.
MIB (Management Information Base): An internal database the switch
maintains for configuration and performance information.
MLTS (Multiline Telephone System): A network-based and/or premisesbased telephone system having a common interface with the public switched
telephone system and having multiple telephone lines, common control units,
multiple telephone sets, and control hardware and software.
NANP (North American Numbering Plan): A ten-digit telephone number
format where the first three digits are an area code and the last seven-digits
are a local telephone number.
Neighbor: See “LLDP Neighbor”.
Non-LLDP Device: A device that is not capable of LLDP operation.
PD (Powered Device): This is an IEEE 802.3af-compliant device that
receives its power through a direct connection to a 10/100Base-TX PoE RJ-45
port in a ProCurve fixed-port or chassis-based switch. Examples of PDs
include Voice-over-IP (VoIP) telephones, wireless access points, and remote
video cameras.
PSAP (Public Safety Answering Point): PSAPs are typically emergency
telephone facilities established as a first point to receive emergency (911) calls
and to dispatch emergency response services such as police, fire and
emergency medical services.
PSE (Power-Sourcing Equipment): A PSE, such as a PoE module installed
in a switch covered in this guide, provides power to IEEE 802.3af-compliant
PDs directly connected to the ports on the module.
13-38
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
TLV (Type-Length-Value): A data unit that includes a data type field, a data
unit length field (in bytes), and a field containing the actual data the unit is
designed to carry (as an alphanumeric string, a bitmap, or a subgroup of
information). Some TLVs include subelements that occur as separate data
points in displays of information maintained by the switch for LLDP
advertisements. (That is, some TLVs include multiple data points or
subelements.)
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 LLDPenabled. (LLDP is a one-way protocol and does not include any
acknowledgement mechanism.) An LLDP-enabled port receiving LLDP
packets inbound from neighbor devices stores the packet data in a Neighbor
database (MIB).
LLDP-MED
This capability is an extension to LLDP and is available on the switches
covered in this guide. Refer to “LLDP-MED (Media-Endpoint-Discovery)” on
page 13-55.
Packet Boundaries in a Network Topology
■
Where multiple LLDP devices are directly connected, an outbound LLDP
packet travels only to the next LLDP device. An LLDP-capable device does
not forward LLDP packets to any other devices, regardless of whether
they are LLDP-enabled.
■
An intervening hub or repeater forwards the LLDP packets it receives in
the same manner as any other multicast packets it receives. Thus, two
LLDP switches joined by a hub or repeater handle LLDP traffic in the same
way that they would if directly connected.
■
Any intervening 802.1D device or Layer-3 device that is either LLDPunaware or has disabled LLDP operation drops the packet.
13-39
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Configuration Options
Enable or Disable LLDP on the Switch. In the default configuration,
LLDP is globally enabled on the switch. To prevent transmission or receipt of
LLDP traffic, you can disable LLDP operation (page 13-40)
Enable or Disable LLDP-MED. In the default configuration for the
switches covered in this guide, LLDP-MED is enabled by default. (Requires that
LLDP is also enabled.) For more information, refer to “LLDP-MED (MediaEndpoint-Discovery)” on page 13-55.
Change the Frequency of LLDP Packet Transmission to Neighbor
Devices. On a global basis, you can increase or decrease the frequency of
outbound LLDP advertisements (page 13-40).
Change the Time-To-Live for LLDP Packets Sent to Neighbors. On a
global basis, you can increase or decrease the time that the information in an
LLDP packet outbound from the switch will be maintained in a neighbor LLDP
device (page 13-40).
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-51). Per-Port
configuration options include four modes:
13-40
■
Transmit and Receive (tx_rx): This is the default setting on all ports. It
enables a given port to both transmit and receive LLDP packets, and to
store the data from received (inbound) LLDP packets in the switch’s MIB.
■
Transmit only (txonly): This setting enables a port to transmit LLDP
packets that can be read by LLDP neighbors. However, the port drops
inbound LLDP packets from LLDP neighbors without reading them. This
prevents the switch from learning about LLDP neighbors on that port.
■
Receive only (rxonly): This setting enables a port to receive and read LLDP
packets from LLDP neighbors, and to store the packet data in the switch’s
MIB. However, the port does not transmit outbound LLDP packets. This
prevents LLDP neighbors from learning about the switch through that
port.
■
Disable (disable): This setting disables LLDP packet transmissions and
reception on a port. In this state, the switch does not use the port for either
learning about LLDP neighbors or informing LLDP neighbors of its presence.
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
SNMP Notification. You can enable the switch to send a notification to any
configured SNMP trap receiver(s) when the switch detects a remote LLDP
data change on an LLDP-enabled port (page 13-50).
Per-Port (Outbound) Data Options. The following table lists the
information the switch can include in the per-port, outbound LLDP packets it
generates. In the default configuration, all outbound LLDP packets include
this information in the TLVs transmitted to neighbor devices. However, you
can configure LLDP advertisements on a per-port basis to omit some of this
information (page 13-52).
Table 13-3. Data Available for Basic LLDP Advertisements
Data Type
Time-to-Live
Chassis Type2, 6
Configuration
Options
Default
Description
See note 1.
120 Seconds
The length of time an LLDP neighbor retains the advertised
data before discarding it.
N/A
Always Enabled
Indicates the type of identifier used for Chassis ID.
6
N/A
Always Enabled
Uses base MAC address of the switch.
3, 6
Port Type
N/A
Always Enabled
Uses “Local”, meaning assigned locally by LLDP.
Port Id6
N/A
Always Enabled
Uses port number of the physical port. In the switches
covered in this guide, this is an internal number reflecting
the reserved slot/port position in the chassis. For more
information on this numbering scheme, refer to figures D-2
and D-3 in Appendix D, “MAC Address Management” of the
Management and Configuration Guide for your switch.
N/A
Always Enabled
Shows the network address type.
Chassis ID
Remote Management
Address
Type4, 6
Address
4
Default or
Configured
System Name6
Uses a default address selection method unless an optional address is
configured. See “Remote Management Address” on page 13-42.
Enable/Disable
Enabled
Uses the switch’s assigned name.
System Description
Enable/Disable
Enabled
Includes switch model name and running software version,
and ROM version.
Port Description6
Enable/Disable
Enabled
Uses the physical port identifier.
System capabilities
supported5, 6
Enable/Disable
Enabled
Identifies the switch’s primary capabilities (bridge, router).
System capabilities
enabled5, 6
Enable/Disable
Enabled
Identifies the primary switch functions that are enabled,
such as routing.
6
13-41
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Data Type
Configuration
Options
Default
Description
1The Packet Time-to-Live value is included in LLDP data packets. (Refer to “Changing the Time-to-Live for Transmitted
Advertisements” on page 13-48.)
Subelement of the Chassis ID TLV.
3
Subelement of the Port ID TLV.
4
Subelement of the Remote-Management-Address TLV.
5
Subelement of the System Capability TLV.
6
Populated with data captured internally by the switch. For more on these data types, refer to the IEEE P802.1AB Standard.
2
Remote Management Address. The switch always includes an IP address
in its LLDP advertisements. This can be either an address selected by a default
process, or an address configured for inclusion in advertisements. Refer to “IP
Address Advertisements” on page 13-43.
Debug Logging. You can enable LLDP debug logging to a configured debug
destination (Syslog server and/or a terminal device) by executing the debug
lldp command. (For more on Debug and Syslog, refer to the “Troubleshooting”
appendix in this guide.) Note that the switch’s Event Log does not record usual
LLDP update messages.
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
collected on adjacent LLDP devices—as well as the local data the
switch is transmitting to adjacent LLDP devices (page 13-44).
■
Using an SNMP application that is designed to query the Neighbors
MIB for LLDP data to use in device discovery and topology mapping.
3400/6400 only?
■
Using the walkmib command to display a listing of the LLDP MIB
objects
LLDP and LLDP-MED Standards Compatibility
The operation covered by this section is compatible with these standards:
13-42
■
IEEE P802.1AB
■
RFC 2922 (PTOPO, or Physical Topology MIB)
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
■
RFC 2737 (Entity MIB)
■
RFC 2863 (Interfaces MIB)
■
ANSI/TIA-1057/D6 (LLDP-MED; refer to “LLDP-MED (Media-EndpointDiscovery)” on page 13-55.)
LLDP Operating Rules
(For additional information specific to LLDP-MED operation, refer to “LLDPMED (Media-Endpoint-Discovery)” on page 13-55.)
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. Similarly, LLDP data received through
trunked ports is stored individually, per-port.
IP Address Advertisements. In the default operation, if a port belongs to
only one static VLAN, then the port advertises the lowest-order IP address
configured on that VLAN. If a port belongs to multiple VLANs, then the port
advertises the lowest-order IP address configured on the VLAN with the
lowest VID. If the qualifying VLAN does not have an IP address, the port
advertises 127.0.0.1 as its IP address. For example, if the port is a member of
the default VLAN (VID = 1), and there is an IP address configured for the
default VLAN, then the port advertises this IP address. In the default operation,
the IP address that LLDP uses can be an address acquired by DHCP or Bootp.
You can override the default operation by configuring the port to advertise
any IP address that is manually configured on the switch, even if the port does
not belong to the VLAN configured with the selected IP address (page 13-52).
(Note that LLDP cannot be configured through the CLI to advertise an
addresses acquired through DHCP or Bootp. However, as mentioned above,
in the default LLDP configuration, if the lowest-order IP address on the VLAN
with the lowest VID for a given port is a DHCP or Bootp address, then the
switch includes this address in its LLDP advertisements unless another
address is configured for advertisements on that port.) Also, although LLDP
allows configuring multiple remote management addresses on a port, only the
lowest-order address configured on the port will be included in outbound
advertisements. Attempting to use the CLI to configure LLDP with an IP
address that is either not configured on a VLAN, or has been acquired by DHCP
or Bootp results in the following error message.
xxx.xxx.xxx.xxx: This IP address is not configured or is
a DHCP address.
13-43
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Spanning-Tree Blocking. Spanning tree does not prevent LLDP packet
transmission or receipt on STP-blocked links.
802.1X Blocking. Ports blocked by 802.1X operation do not allow
transmission or receipt of LLDP packets.
Configuring LLDP Operation
In the default configuration, LLDP is enabled and in both transmit and receive
mode on all active ports. 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.
The commands in this section affect both LLDP and LLDP-MED operation. for
information on operation and configuration unique to LLDP-MED, refer to
“LLDP-MED (Media-Endpoint-Discovery)” on page 13-55.
Command
Page
show lldp config
13-46
[no] lldp run
13-46
lldp refresh-interval
13-47
lldp holdtime-multiplier
13-48
lldpTxDelay
13-48
lldpReinitDelay
13-49
lldp enable-notification
13-50
lldpnotificationinterval
13-51
lldp admin-status < txonly | rxonly | tx_rx | disable >
13-51
lldp config < port-list > IpAddrEnable
13-52
lldp config < port-list > basicTlvEnable
13-53
lldp config < port-list > dot3TlvEnable < macphy_config >
13-55
Viewing the Current Configuration
Displaying the Global LLDP, Port Admin, and SNMP Notification
Status. This command displays the switch’s general LLDP configuration
status, including some per-port information affecting advertisement traffic
and trap notifications.
Syntax show lldp config
13-44
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Displays the LLDP global configuration, LLDP port status, and
SNMP notification status. For information on port admin status,
refer to “Configuring Per-Port Transmit and Receive Modes” on
page 13-51.
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-47).
Med Topology Trap Enabled
------------------------False
True
False
False
True
False
False
Figure 13-13. Example of Viewing the General LLDP Configuration
13-45
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Displaying Port Configuration Details. This command displays the portspecific configuration, including.
Syntax show lldp config < port-list >
Displays the LLDP port-specific configuration for all ports in
< port-list >, including which optional TLVs and any non-default
IP address that are included in the port’s outbound
advertisements. For information on the notification setting,
refer to “Configuring SNMP Notification Support” on page
13-50. For information on the other configurable settings
displayed by this command, refer to “Configuring Per-Port
Transmit and Receive Modes” on page 13-51.
These fields appear when medtlvenable is
enabled on the switch, which is the default
setting.
This field appears when dot3tlvenable is enabled
on the switch, which is the default setting.
The blank IpAddress field indicates that the
default IP address will be advertised from this
port. (Refer to page 13-52: “Configuring a Remote
Management Address for Outbound LLDP
Advertisements”
Figure 13-14. Example of Per-Port Configuration Display
Configuring Global LLDP Packet Controls
The commands in this section configure the aspects of LLDP operation that
apply the same to all ports in the switch.
Enabling or Disabling LLDP Operation on the Switch. Enabling LLDP
operation (the default) causes the switch to:
■
13-46
Use active, LLDP-enabled ports to transmit LLDP packets describing itself
to neighbor devices.
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
■
Add entries to its neighbors table based on data read from incoming LLDP
advertisements.
Syntax [ no ] lldp run
Enables or disables LLDP operation on the switch. The no form
of the command, regardless of individual LLDP port
configurations, prevents the switch from transmitting outbound
LLDP advertisements, and causes the switch to drop all LLDP
advertisements received from other devices. The switch
preserves the current 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
Changing the Packet Transmission Interval. This interval controls how
often active ports retransmit advertisements to their neighbors.
Syntax lldp refresh-interval < 5 - 32768 >
Changes the interval between consecutive transmissions of
LLDP advertisements on any given port. (Default: 30 seconds)
Note: The refresh-interval must be greater than or equal to
(4 x delay-interval). (The default delay-interval is 2). For example,
with the default delay-interval, the lowest refresh-interval you can
use is 8 seconds (4 x 2 = 8). Thus, if you want a refresh-interval of
5 seconds, you must first change the delay interval to 1 (that is,
4 x 1 < 5). If you want to change the delay-interval, use the setmib
command.
13-47
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Changing the Time-to-Live for Transmitted Advertisements. The
Time-to-Live value (in seconds) for all LLDP advertisements transmitted from
a switch is controlled by the switch that generates the advertisement, and
determines how long an LLDP neighbor retains the advertised data before
discarding it. The Time-to-Live value is the result of multiplying the refreshinterval by the holdtime-multiplier described below.
Syntax lldp holdtime-multiplier < 2 - 10 >
Changes the multiplier an LLDP switch uses to calculate the
Time-to-Live for the LLDP advertisements it generates and
transmits to LLDP neighbors. When the Time-to-Live for a given
advertisement expires the advertised data is deleted from the
neighbor switch’s MIB. (Default: 4; Range: 2 - 10)
For example, if the refresh-interval on the switch is 15 seconds and the
holdtime-multiplier is at the default, the 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-toLive of 30 seconds.
ProCurve(config)# lldp holdtime-multiplier 2
Changing the Delay Interval Between Advertisements Generated by
Value or Status Changes to the LLDP MIB. The switch uses a delayinterval 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. The delay-interval can be changed using either an SNMP
network management application or the CLI setmib command.
13-48
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Syntax setmib lldpTxDelay.0 -i < 1 - 8192 >
Uses setmib to change the minimum time (delay-interval) any
LLDP port will delay advertising successive LLDP
advertisements due to a change in LLDP MIB content. (Default:
2; Range: 1 - 8192)
Note: The LLDP refresh-interval (transmit interval) must be
greater than or equal to (4 x delay-interval). The switch does
not allow increasing the delay interval to a value that conflicts
with this relationship. That is, the switch displays Inconsistent
value if (4 x delay-interval) exceeds the current transmit
interval, and the command fails. Depending on the current
refresh-interval setting, it may be necessary to increase the
refresh-interval before using this command to increase the
delay-interval.
For example, to change the delay-interval from 2 seconds to 8 seconds when
the refresh-interval is at the default 30 seconds, you must first set the refreshinterval to a minimum of 32 seconds (32 = 4 x 8).
Attempt to change the transmit-delay
interval shows that the refreshinterval is less than (4 x delay-interval).
Successfully changes the transmitdelay interval to 8.
Changes the refresh-interval to 32; that is:
32 = 4 x (desired transmit-delay interval)
Figure 13-15. Example of Changing the Transmit-Delay Interval
Changing the Reinitialization Delay Interval. In the default
configuration, a port receiving a disable command followed immediately by a
txonly, rxonly, or tx_rx command delays reinitializing for two seconds, during
which time LLDP operation remains disabled. If an active port is subjected to
frequent toggling between the LLDP disabled and enabled states, LLDP
advertisements are more frequently transmitted to the neighbor device. Also,
the neighbor table in the adjacent device will change more frequently, as it
deletes, then replaces LLDP data for the affected port which, in turn, generates
SNMP traps (if trap receivers and SNMP notification are configured). All of
this can unnecessarily increase network traffic. Extending the reinitialization-
13-49
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
delay interval delays the port’s ability to reinitialize and generate LLDP traffic
following an LLDP disable/enable cycle.
Syntax setmib lldpReinitDelay.0 -i < 1 - 10 >
Uses setmib to change the minimum time (reinitialization delay
interval) an LLDP port will wait before reinitializing after
receiving an LLDP disable command followed closely by a
txonly or tx_rx command. The delay interval commences with
execution of the lldp admin-status < port-list > disable command.
(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.
Enabling LLDP Data Change Notification for SNMP Trap Receivers.
Syntax [ no ] lldp enable-notification < port-list >
Enables or disables each port in < port-list > for sending
notification to configured SNMP trap receiver(s) if an LLDP data
change is detected in an advertisement received on the port from
an LLDP neighbor. (Default: Disabled)
For information on configuring trap receivers in the switch, refer
to “SNMP Notifications” on page 13-18.
For example, this command enables SNMP notification on ports 1 - 5:
ProCurve(config)# lldp enable-notification 1-5
13-50
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Changing the Minimum Interval for Successive Data Change
Notifications for the Same Neighbor.
If LLDP trap notification is enabled on a port, a rapid succession of changes
in LLDP information received in advertisements from one or more neighbors
can generate a high number of traps. To reduce this effect, you can globally
change the interval between successive notifications of neighbor data change.
Syntax setmib lldpnotificationinterval.0 -i < 1 - 3600 >
Globally changes the interval between successive traps
generated by the switch. If multiple traps are generated in the
specified interval, only the first trap will be sent. The remaining
traps will be suppressed. (A network management application
can periodically check the switch MIB to detect any missed
change notification traps. Refer to IEEE P802.1AB 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
Configuring Per-Port Transmit and Receive Modes
These commands control 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 configuration,
each port is configured to transmit and receive LLDP packets.
These options enable you to control which ports participate in
LLDP traffic and whether the participating ports allow LLDP
traffic in only one direction or in both directions.
txonly: Configures the specified port(s) to transmit LLDP packets, but block inbound LLDP packets from neighbor devices.
rxonly: Configures the specified port(s) to receive LLDP packets
from neighbors, but block outbound packets to neighbors.
tx_rx: Configures the specified port(s) to both transmit and
receive LLDP packets. (This is the default setting.)
disable: Disables LLDP packet transmit and receive on the
specified port(s).
13-51
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Configuring Basic LLDP Per-Port Advertisement Content
In the default LLDP configuration, outbound advertisements from each port
on the switch include both mandatory and optional data.
Mandatory Data. An active LLDP port on the switch always includes the
mandatory data in its outbound advertisements. LLDP collects the mandatory
data, and, except for the Remote Management Address, you cannot use LLDP
commands to configure the actual data.
■
Chassis Type (TLV subelement)
■
Chassis ID (TLV)
■
Port Type (TLV subelement)
■
Port ID (TLV)
■
Remote Management Address (TLV; actual IP address is a subelement that
can be a default address or a configured address)
Configuring a Remote Management Address for Outbound LLDP
Advertisements. This is an optional command you can use to include a
specific IP address in the outbound LLDP advertisements for specific ports.
Syntax [ no ] lldp config < port-list > ipAddrEnable < ip-address >
Replaces the default IP address for the port with an IP
address you specify. This can be any IP address configured
in a static VLAN on the switch, even if the port does not
belong to the VLAN configured with the selected IP address.
The no form of the command deletes the specified IP
address. If there are no IP addresses configured as
management addresses, then the IP address selection
method returns to the default operation. (Default: The port
advertises the IP address of the lowest-numbered VLAN
(VID) to which it belongs. If there is no IP address configured
on the VLAN(s) to which the port belongs, and the port is
not configured to advertise an IP address from any other
(static) VLAN on the switch, then the port advertises an
address of 127.0.0.1.)
Note: This command does not accept either IP addresses
acquired through DHCP or Bootp, or IP addresses that are
not configured in a static VLAN on the switch
13-52
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
For example, if port 3 belongs to a subnetted VLAN that includes an IP address
of 10.10.10.100 and you wanted port 3 to use this secondary address in LLDP
advertisements, you would need to execute the following command:
ProCurve(config)# lldp config 3 ipAddrEnable 10.10.10.100
Optional Data. You can configure an individual port or group of ports to
exclude one or more of these data types from outbound LLDP advertisements.
Note that optional data types, when enabled, are populated with data internal
to the switch; that is, you cannot use LLDP commands to configure their actual
content.
■
port description (TLV)
■
system name (TLV)
■
system description (TLV)
■
system capabilities (TLV)
■
•
system capabilities Supported (TLV subelement)
•
system capabilities Enabled (TLV subelement)
port speed and duplex (TLV subelement)
Syntax: [ no ] lldp config < port-list > basicTlvEnable < TLV-Type >
port_descr
For outbound LLDP advertisements, this TLV includes an
alphanumeric string describing the port.
(Default: Enabled)
system_name
For outbound LLDP advertisements, this TLV includes an
alphanumeric string showing the system’s assigned name.
(Default: Enabled)
system_descr
For outbound LLDP advertisements, this TLV includes an
alphanumeric string describing the full name and version
identification for the system’s hardware type, software
version, and networking application.
(Default: Enabled)
13-53
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
system_cap
For outbound advertisements, this TLV includes a
bitmask of supported system capabilities (device
functions). Also includes information on whether the
capabilities are enabled.
(Default: Enabled)
For example, if you wanted to exclude the system name TLV from the
outbound LLDP advertisements for all ports on a switch, you would use this
command:
ProCurve(config)# no lldp config 1-24 basicTlvEnable
system_name
If you later decided to reinstate the system name TLV on ports 1-5, you would
use this command:
ProCurve(config)# lldp config 1-5 basicTlvEnable
system_name
Configuring Support for Port Speed and Duplex
Advertisements
This feature is optional for LLDP operation, but is required for LLDP-MED
operation.
Port speed and duplex advertisements are supported on the switches covered
in this guide to inform an LLDP endpoint and the switch port of each other’s
port speed and duplex configuration and capabilities. Configuration
mismatches between a switch port and an LLDP endpoint can result in
excessive collisions and voice quality degradation. LLDP enables discovery of
such mismatches by supporting SNMP access to the switch MIB for comparing
the current switch port and endpoint settings. (Changing a current device
configuration to eliminate a mismatch requires intervention by the system
operator.)
13-54
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Syntax: [ no ] lldp config < port-list > dot3TlvEnable macphy_config
For outbound advertisements, this TLV includes the
(local) switch port’s current speed and duplex settings, the
range of speed and duplex settings the port supports, and
the method required for reconfiguring the speed and
duplex settings on the device (auto-negotiation during
link initialization, or manual configuration).
Using SNMP to compare local and remote information can
help in locating configuration mismatches.
(Default: Enabled)
Note: For LLDP operation, this TLV is optional. For
LLDP-MED operation, this TLV is mandatory.
As mentioned above, an SNMP network management application can be used
to compare the port speed and duplex data configured in the switch and
advertised by the LLDP endpoint. You can also use the CLI to display this
information. For more on using the CLI to display port speed and duplex
information, refer to “Displaying the Current Port Speed and Duplex
Configuration on a Switch Port” on page 13-70.
LLDP-MED (Media-Endpoint-Discovery)
LLDP-MED (ANSI/TIA-1057/D6) extends the LLDP (IEEE 802.1AB) industry
standard to support advanced features on the network edge for Voice Over IP
(VoIP) endpoint devices with specialized capabilities and LLDP-MED
standards-based functionality. LLDP-MED in the switches uses the standard
LLDP commands described earlier in this section, with some extensions, and
also introduces new commands unique to LLDP-MED operation. The show
commands described elsewhere in this section are applicable to both LLDP
and LLDP-MED operation. LLDP-MED benefits include:
■
plug-and-play provisioning for MED-capable, VoIP endpoint devices
■
simplified, vendor-independent management enabling different IP
telephony systems to interoperate on one network
■
automatic deployment of convergence network policies (voice
VLANs, Layer 2/CoS priority, and Layer 3/QoS priority)
■
configurable endpoint location data to support the Emergency Call
Service (ECS) (such as Enhanced 911 service, 999, 112)
■
detailed VoIP endpoint data inventory readable via SNMP from the
switch
13-55
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
■
Power over Ethernet (PoE) status and troubleshooting support via
SNMP
■
support for IP telephony network troubleshooting of call quality
issues via SNMP
This section describes how to configure and use LLDP-MED features in the
switches to support VoIP network edge devices (Media Endpoint Devices)
such as:
■
IP phones
■
voice/media gateways
■
media servers
■
IP communications controllers
■
other VoIP devices or servers
Switches Providing Network
Access to LLDP-MED Endpoints
LLDP-MED Class 1 Generic Endpoints
Such As IP Call Control Devices
IP Network
IP Network
Infrastructure
Infrastructure
(IEEE 802 LAN)
(IEEE 802 LAN)
LLDP-MED Class 2 Media Endpoints Such As
Media Gateways, Conference Bridges, and
other Devices Supporting IP Media Streams
LLDP-MED Class 3 End-User IP Communication
Devices Such As VoIP Telephones
Figure 13-16. Example of LLDP-MED Network Elements
LLDP-MED Endpoint Support. LLDP-MED on the switches covered in this
guide interoperates with directly connected IP telephony (endpoint) clients
having these features and services:
■
13-56
able to autonegotiate speed and duplex configuration with the switch
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
■
Note
able to use the following network policy elements configured on the
client port
•
voice VLAN ID
•
802.1p (Layer 2) QoS
■
• Diffserv codepoint (DSCP) (Layer 3) QoS
discover and advertise device location data learned from the switch
■
support emergency call service (ECS—such as E911, 999, and 112)
■
advertise device information for the device data inventory collected
by the switch, including:
•
hardware revision
•
serial number
•
firmware revision
•
manufacturer name
•
software revision
•
model name
• asset ID
■
provide information on network connectivity capabilities (for
example, a multi-port VoIP phone with Layer 2 switch capability)
■
support the fast start capability
LLDP-MED on the switches covered in this guide is intended for use with VoIP
endpoints, and is not designed to support links between network
infrastructure devices, such as switch-to-switch or switch-to-router links.
LLDP-MED Endpoint Device Classes. LLDP-MED endpoint devices are,
by definition, located at the network edge and communicate using the LLDPMED framework. Any LLDP-MED endpoint device belongs to one of the
following three classes:
■
Class 1 (Generic Endpoint Devices): These devices offer the basic
LLDP discovery services, network policy advertisement (VLAN ID,
Layer 2/802.1p priority, and Layer 3/DSCP priority), and PoE management. This class includes such devices as IP call controllers and
communication-related servers.
■
Class 2 (Media Endpoint Devices): These devices offer all Class 1
features plus media streaming capability, and include such devices as
voice/media gateways, conference bridges, and media servers.
13-57
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
■
Class 3 (Communication Devices): These devices are typically IP
phones or end-user devices that otherwise support IP media and offer
all Class 1 and Class 2 features, plus location identification and
emergency 911 capability, Layer 2 switch support, and device information management.
LLDP-MED Operational Support. The switches covered in this guide offer
two configurable TLVs supporting MED-specific capabilities:
Note
■
medTlvEnable (for per-port enabling or disabling of LLDP-MED operation)
■
medPortLocation (for configuring per-port location or emergency call
data)
LLDP-MED operation also requires the port speed and duplex TLV
(dot3TlvEnable; page 13-55), which is enabled in the default configuration.
LLDP-MED Topology Change Notification
This optional feature provides information an SNMP application can use to
track LLDP-MED connects and disconnects.
13-58
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Syntax: lldp top-change-notify < port-list >
Topology change notification, when enabled on an LLDP port,
causes the switch to send an SNMP trap if it detects LLDPMED endpoint connection or disconnection activity on the
port, or an age-out of the LLDP-MED neighbor on the port. The
trap includes the following information:
■
the port number (internal) on which the activity was
detected (For more in internal port numbers, refer to
“Determining the Switch Port Number Included in
Topology Change Notification Traps” on page 13-76.)
■
the LLDP-MED class of the device detected on the port
(“LLDP-MED Endpoint Device Classes” on page 13-57.)
The show running command shows whether the topology
change notification feature is enabled or disabled. For
example, if ports A1-A10 have topology change notification
enabled, the following entry appears in the show running
output:
lldp top-change-notify A1-A10
(Default: Disabled)
Note: To send traps, this feature requires access to at least
one SNMP server. For information on configuring traps,
refer to “SNMP Notifications” on page 13-18.
Also, if a detected LLDP-MED neighbor begins sending
advertisements without LLDP-MED TLVs, the switch sends
a top-change-notify trap.
Note
Topology change notifications provide one method for monitoring system
activity. However, because SNMP normally employs UDP, which does not
guarantee datagram delivery, topology change notification should not be
relied upon as the sole method for monitoring critical endpoint device
connectivity.
13-59
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
LLDP-MED Fast Start Control
Syntax: lldp fast-start-count < 1 - 10 >
An LLDP-MED device connecting to a switch port may use
the data contained in the MED TLVs from the switch to
configure itself. However, the lldp refresh-interval setting
(default: 30 seconds) for transmitting advertisements can
cause an unacceptable delay in MED device configuration.
To support rapid LLDP-MED device configuration, the lldp
fast-start-count command temporarily overrides the refreshinterval setting for the fast-start-count advertisement interval.
This results in the port initially advertising LLDP-MED at
a faster rate for a limited time. Thus, when the switch detects
a new LLDP-MED device on a port, it transmits one LLDPMED advertisement per second out the port for the duration
of the fast-start-count interval. In most cases, the default
setting should provide an adequate fast-start-count interval.
(Range: 1 - 10 seconds; Default: 5 seconds)
Note: This global command applies only to ports on which a
new LLDP-MED device is detected. It does not override the
refresh-interval setting on ports where non-MED devices are
detected.
Advertising Device Capability, Network Policy, PoE Status
and Location Data
The medTlvEnable option on the switch is enabled in the default configuration
and supports the following LLDP-MED TLVs:
■
LLDP-MED capabilities: This TLV enables the switch to determine:
•
whether a connected endpoint device supports LLDP-MED
•
which specific LLDP-MED TLVs the endpoint supports
•
the device class (1, 2, or 3) for the connected endpoint
This TLV also enables an LLDP-MED endpoint to discover what LLDPMED TLVs the switch port currently supports.
13-60
■
network policy operating on the port to which the endpoint is connected
(VLAN, Layer 2 QoS, Layer 3 QoS)
■
PoE (MED Power-over-Ethernet)
■
physical location data — page 13-63
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Note
LLDP-MED operation requires the macphy_config TLV subelement—enabled
by default—that is optional for IEEE 802.1AB LLDP operation. Refer to the
dot3TlvEnable macphy_config command on page 13-55.
Network Policy Advertisements. Network policy advertisements are
intended for real-time voice and video applications, and include these TLV
subelements:
■
Layer 2 (802.1p) QoS
■
Layer 3 DSCP (diffserv code point) QoS
■
Voice VLAN ID (VID)
VLAN Operating Rules. These rules affect advertisements of VLANs in
network policy TLVs:
■
The VLAN ID TLV subelement applies only to a VLAN configured for voice
operation (vlan < vid > voice).
■
If there are multiple voice VLANs configured on a port, LLDP-MED
advertises the voice VLAN having the lowest VID.
■
The voice VLAN port membership configured on the switch can be tagged
or untagged. However, if the LLDP-MED endpoint expects a tagged membership when the switch port is configured for untagged, or the reverse,
then a configuration mismatch results. (Typically, the endpoint expects
the switch port to have a tagged voice VLAN membership.)
■
If a given port does not belong to a voice VLAN, then the switch does not
advertise the VLAN ID TLV through this port.
Policy Elements. These policy elements may be statically configured on the
switch or dynamically imposed during an authenticated session on the switch
using a RADIUS server and 802.1X or MAC authentication. (Web
authentication does not apply to VoIP telephones and other
telecommunications devices that are not capable of accessing the switch
through a Web browser.) The QoS and voice VLAN policy elements can be
statically configured with the following CLI commands:
vlan < vid > voice
vlan < vid > < tagged | untagged > < port-list >
int < port-list > qos priority < 0 - 7 >
vlan < vid > qos dscp < codepoint >
13-61
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Notes
A codepoint must have an 802.1p priority before you can configure it for use
in prioritizing packets by VLAN-ID. If a codepoint you want to use shows No
Override in the Priority column of the DSCP policy table (display with show qosdscp map, then use qos-dscp map < codepoint > priority < 0 - 7 > to configure a
priority before proceeding. For more on this topic, refer to the chapter titled
“Quality of Service (QoS): Managing Bandwidth More Effectively” in the
Advanced Traffic Management Guide for your switch.
Enabling or Disabling medTlvEnable. In the default LLDP-MED
configuration, the TLVs controlled by medTlvEnable are enabled.
Syntax: [ no ] lldp config < port-list > medTlvEnable < medTlv >
■
Enables or disables advertisement of the following TLVs
on the specified ports:
•
device capability TLV
•
configured network policy TLV
•
configured location data TLV (Refer to “Configuring
Location Data for LLDP-MED Devices” on page
13-63.)
•
current PoE status TLV
(Default: All of the above TLVs are enabled.)
■
Helps to locate configuration mismatches by allowing use
of an SNMP application to compare the LLDP-MED configuration on a port with the LLDP-MED TLVs advertised
by a neighbor connected to that port.
capabilities
This TLV enables the switch to determine:
•
which LLDP-MED TLVs a connected endpoint can
discover
•
the device class (1, 2, or 3) for the connected
endpoint
This TLV also enables an LLDP-MED endpoint to
discover what LLDP-MED TLVs the switch port currently supports.
(Default: enabled)
Note: This TLV cannot be disabled unless the
network_policy, poe, and location_id TLVs are already
disabled.
13-62
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
network-policy
This TLV enables the switch port to advertise its
configured network policies (voice VLAN, Layer 2 QoS,
Layer 3 QoS), and allows LLDP-MED endpoint devices to
auto-configure the voice network policy advertised by the
switch. This also enables the use of SNMP applications to
troubleshoot statically configured endpoint network
policy mismatches.
(Default: Enabled)
Notes: Network policy is only advertised for ports that are
configured as members of the voice VLAN. If the port
belongs to more than one voice VLAN, then the voice
VLAN with the lowest-numbered VID is selected as the
VLAN for voice traffic. Also, this TLV cannot be enabled
unless the capability TLV is already enabled.
For more information, refer to “Network Policy
Advertisements” on page 13-61
location_id
This TLV enables the switch port to advertise its
configured location data (if any). For more on
configuring location data, refer to “Configuring Location
Data for LLDP-MED Devices”.
(Default: Enabled)
Note: When disabled, this TLV cannot be enabled unless
the capability TLV is already enabled.
Configuring Location Data for LLDP-MED Devices
You can configure a switch port to advertise location data for the switch itself,
the physical wall-jack location of the endpoint (recommended), or the
location of a DHCP server supporting the switch and/or endpoint. You also
have the option of configuring these different address types:
■
civic address: physical address data such as city, street number, and
building information
■
ELIN (Emergency Location Identification Number): an emergency
number typically assigned to MLTS (Multiline Telephone System Operators) in North America
■
coordinate-based location: attitude, longitude, and altitude information (Requires configuration via an SNMP application.)
13-63
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Syntax: [ no ] lldp config < port-list > medPortLocation < Address-Type >
Configures location or emergency call data the switch advertises
per port in the location_id TLV. This TLV is for use by LLDPMED endpoints employing location-based applications.
Note: The switch allows one medPortLocation entry per
port (without regard to type). Configuring a new
medPortLocation entry of any type on a port replaces
any previously configured entry on that port.
civic-addr < COUNTRY-STR > < WHAT > < CA-TYPE > < CA-VALUE > . . .
[< CA-TYPE > < CA-VALUE >] . . . [< CA-TYPE > < CA-VALUE >]
This command enables configuration of a physical
address on a switch port, and allows up to 75 characters
of address information.
COUNTRY-STR: A two-character country code, as defined by
ISO 3166. Some examples include FR (France), DE
(Germany), and IN (India). This field is required in a
civic-addr command. (For a complete list of country codes,
visit www.iso.org on the world wide web.)
WHAT: A single-digit number specifying the type of device
to which the location data applies:
0: Location of DHCP server
1: Location of switch
2: Location of LLDP-MED endpoint (recommended
application)
This field is required in a civic-addr command.
—Continued—
13-64
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
— Continued—
Type/Value Pairs (CA-TYPE and CA-VALUE): This is a
series of data pairs, each composed of a location data
“type” specifier and the corresponding location data
for that type. That is, the first value in a pair is
expected to be the civic address “type” number (CATYPE), and the second value in a pair is expected to
be the corresponding civic address data (CA-VALUE).
For example, if the CA-TYPE for “city name” is “3”, then
the type/value pair to define the city of Paris is “3
Paris”. Multiple type/value pairs can be entered in any
order, although it is recommended that multiple
pairs be entered in ascending order of the CATYPE.When an emergency call is placed from a
properly configured class 3 endpoint device to an
appropriate PSAP, the country code, device type, and
type/value pairs configured on the switch port are
included in the transmission. The “type” specifiers
are used by the PSAP to identify and organize the
location data components in an understandable
format for response personnel to interpret. A civicaddr command requires a minimum of one type/
value pair, but typically includes multiple type/value
pairs as needed to configure a complete set of data
describing a given location. CA-TYPE: This is the first
entry in a type/value pair, and is a number defining
the type of data contained in the second entry in the
type/value pair (CA-VALUE). Some examples of CA-TYPE
specifiers include:
• 3 = city
• 6 = street (name)
• 25 = building name
(Range: 0 - 255)
For a sample listing of CA-TYPE specifiers, refer to table
13-4 on page 13-67.
CA-VALUE: This is the second entry in a type/value
pair, and is an alphanumeric string containing
the location information corresponding to the
immediately preceding CA-TYPE entry. Strings
are delimited by either blank spaces, single
quotes (‘ ... ‘), or double quotes (“ ... “). Each string
should represent a specific data type in a set of
unique type/value pairs comprising the
description of a location, and each string must
be preceded by a CA-TYPE number identifying the
type of data in the string.
13-65
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Note: A switch port allows one instance of any given CATYPE. For example, if a type/value pair of 6 Atlantic (to
specify “Atlantic” as a street name) is configured on port
A5 and later another type/value pair of 6 Pacific is
configured on the same port, then Pacific replaces Atlantic
in the civic address location configured for port A5.
elin-addr < emergency-number >
This feature is intended for use in Emergency Call Service
(ECS) applications to support class 3 LLDP-MED VoIP
telephones connected to a switch covered in this guide in
a multiline telephone system (MLTS) infrastructure. An
ELIN (Emergency Location Identification Number) is a
valid North American Numbering Plan (NANP) format
telephone number assigned to MLTS operators in North
America by the appropriate authority. The ELIN is used
to route emergency (E911) calls to a Public Safety
Answering Point (PSAP).
(Range: 1-15 numeric characters)
Configuring Coordinate-Based Locations. Latitude, longitude, and
altitude data can be configured per switch port using an SNMP management
application. For more information, refer to the documentation provided with
the application. A further source of information on this topic is RFC 3825Dynamic Host Configuration Protocol Option for Coordinate-based
Location Configuration Information.
Note
13-66
Endpoint use of data from a medPortLocation TLV sent by the switch is devicedependent. Refer to the documentation provided with the endpoint device.
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Table 13-4. Some Location Codes Used in CA-TYPE Fields*
Location Element
Code
Location Element
Code
national subdivision
1
street number
19
regional subdivision
2
additional location data
22
city or township
3
unit or apartment
26
city subdivision
4
floor
27
street
6
room number
28
street suffix
18
*The code assignments in this table are examples from a work-in-progress (the
internet draft titled “Dynamic Host Configuration Protocol (DHCPv4 and
DHCPv6) Option for Civic Addresses Configuration Information draft-ietfgeopriv-dhcp-civil-06” dated May 30, 2005.) For the actual codes to use,
contact the PSAP or other authority responsible for specifying the civic
addressing data standard for your network.
Example of a Location Configuration. Suppose a system operator
wanted to configure the following information as the civic address for a
telephone connected to her company’s network through port A2 of a switch
at the following location:
Description
CA-Type
CA-VALUE
national subdivision
1
CA
city
3
Widgitville
street
6
Main
street number
19
1433
unit
26
Suite 4-N
floor
27
4
room number
28
N4-3
Figure 13-17 shows the commands for configuring and displaying the above
data.
13-67
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
ProCurve(config)# lldp config d1 medportlocation civic-addr US 2 1 C
A
ProCurve(config)# show lldp config d1
LLDP Port Configuration Detail
Port : D1
AdminStatus [Tx_Rx] : disable
NotificationEnabled [False] : False
Med Topology Trap Enabled [False] : False
Country Name
What
Ca-Type
Ca-Length
Ca-Value
:
:
:
:
:
US
2
1
2
CA
TLVS Advertised:
* port_descr
* system_name
* system_descr
* system_cap
*
*
*
*
capabilities
network_policy
location_id
poe
* macphy_config
IpAddress Advertised:
Figure 13-17. Example of a Civic Address Configuration
Displaying Advertisement Data
Command
show lldp info local-device
Page
below
walkmib lldpXdot3LocPortOperMauType
show lldp info remote-device
13-71
walkmib lldpXdot3RemPortAutoNegAdvertisedCap
show lldp info stats
13-68
13-73
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.
With the [ port-list ] option, this command displays only the
following port-specific information that is currently available for
outbound LLDP advertisements on the specified ports:
• PortType
• PortId
• PortDesc
Note: This command displays the information available on the
switch. Use the lldp config < port-list > command to change the
selection of information that is included in actual outbound
advertisements. In the default LLDP configuration, all
information displayed by this command is transmitted in
outbound advertisements.
For example, in the default configuration, the switch information currently
available for outbound LLDP advertisements appears similar to the display in
Figure 13-18 on page 13-70.
13-69
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
ProCurve# show lldp info local-device
LLDP Local Device Information
Chassis Type : mac-address
Chassis Id
: 00 24 81 b0 09 21
System Name : ProCurve 6120 Blade Switch
System Description : ProCurve 498358-B21 6120 Blade Switch, revision ...
System Capabilities Supported:bridge
System Capabilities Enabled:bridge
Management Address :
Type:ipv4
Address:16.93.40.251
LLDP Port Information
Port
-------D1
D2
D3
D4
D5
D6
.
.
.
|
+
|
|
|
|
|
|
PortType
-------local
local
local
local
local
local
.
.
.
PortId
-------1
2
3
4
5
6
.
.
.
PortDesc
-------D1
D2
D3
D4
D5
D6
.
.
.
The Management Address field displays only
the LLDP-configurable IP addresses on the
switch. (Only manually-configured IP
addresses are LLDP-configurable.) If the
switch has only an IP address from a DHCP or
Bootp server, then the Management Address
field is empty (because there are no LLDPconfigurable IP addresses available). For more
on this topic, refer to “Remote Management
Address” on page 13-42.
Figure 13-18. Example of Displaying the Global and Per-Port Information Available for Outbound
Advertisements
Figure 13-19. Example of the Default Per-Port Information Content for Ports 1 and 2
Displaying the Current Port Speed and Duplex Configuration on a
Switch Port. Port speed and duplex information for a switch port and a
connected LLDP-MED endpoint can be compared for configuration
mismatches by using an SNMP application. You can also use the switch CLI
to display this information, if necessary. The following two commands provide
methods for displaying speed and duplex information for switch ports. For
information on displaying the currently configured port speed and duplex on
13-70
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
an LLDP-MED endpoint, refer to “Displaying the Current Port Speed and
Duplex Configuration on a Switch Port” on page 13-70.
Syntax: show interfaces brief < port-list >
Includes port speed and duplex configuration in the Mode
column of the resulting display.
Displaying Advertisements Currently in the Neighbors MIB. These
commands display the content of the inbound LLDP advertisements received
from other LLDP devices.
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. Discovered devices are listed by the inbound
port on which they were discovered. Multiple devices listed for
a single port indicates that such devices are connected to the
switch through a hub.
Discovering the same device on multiple ports indicates that
the remote device may be connected to the switch in one of the
following ways:
– Through different VLANS using separate links. (This
applies to switches that use the same MAC address for all
configured VLANs.)
– Through different links in the same trunk.
– Through different links using the same VLAN. (In this
case, spanning-tree should be invoked to prevent a network topology loop. Note that LLDP packets travel on links
that spanning-tree blocks for other traffic types.)
With the [ port-list ] option, this command provides a listing of
the LLDP data that the switch has detected in advertisements
received on the specified ports.
For descriptions of the various types of information displayed
by these commands, refer to Table 13-3 on page 13-41.
13-71
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
ProCurve# show lldp info remote-device
LLDP Remote Devices Information
LocalPort
--------1
1
1
1
1
1
1
1
1
1
|
+
|
|
|
|
|
|
|
|
|
|
ChassisId
------------------------HP ProCurve Switch 282...
HP ProCurve Switch 252...
HP ProCurve Switch 282...
Switch
FOX110613GF(casl-ssw31...
HP ProCurve Switch 530...
HP ProCurve Switch 265...
HP ProCurve Switch 252...
HP ProCurve Switch 252...
JAB115102B8(ccswitch2)
PortId PortDescr SysName
------ --------- --------------------1
9
1
Fas...
mgmt0
A13
49
1
1
mgmt0
Figure 13-20. Example of a Global Listing of Discovered Devices
Indicates the policy configured on
the telephone. A configuration
mismatch occurs if the supporting
port is configured differently.
Figure 13-21. Example of an LLLDP-MED Listing of an Advertisement Received From an LLDP-MED (VoIP
Telephone) Source
13-72
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.
Syntax show lldp stats [ port-list ]
The global LLDP statistics command displays an overview of
neighbor detection activity on the switch, plus data on the
number of frames sent, received, and discarded per-port. The
per-port LLDP statistics command enhances the list of per-port
statistics provided by the global statistics command with some
additional per-port LLDP statistics.
Global LLDP Counters:
Neighbor Entries List Last Updated: Shows the elapsed time since
a neighbor was last added or deleted.
New Neighbor Entries Count: Shows the total of new LLDP
neighbors detected since the last switch reboot. Disconnecting,
then reconnecting a neighbor increments this counter.
Neighbor Entries Deleted Count: Shows the number of neighbor
deletions from the MIB for AgeOut Count and forced drops for
all ports. For example, if the admin status for port on a
neighbor device changes from tx_rx or txonly to disabled or
rxonly, then the neighbor device sends a “shutdown” packet out
the port and ceases transmitting LLDP frames out that port.
The device receiving the shutdown packet deletes all
information about the neighbor received on the applicable
inbound port and increments the counter.
Neighbor Entries Dropped Count: Shows the number of valid LLDP
neighbors the switch detected, but could not add. This can
occur, for example, when a new neighbor is detected when the
switch is already supporting the maximum number of
neighbors. Refer to “Neighbor Maximum” on page 13-75.
Neighbor Entries AgeOut Count: Shows the number of LLDP
neighbors dropped on all ports due to Time-to-Live expiring.
— Continued —
13-73
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
— Continued —
Per-Port LLDP Counters:
NumFramesRecvd: Shows the total number of valid, inbound
LLDP advertisements received from any neighbor(s) on < portlist >. Where multiple neighbors are connected to a port through
a hub, this value is the total number of LLDP advertisements
received from all sources.
NumFramesSent: Shows the total number of LLDP
advertisements sent from < port-list >.
NumFramesDiscarded: Shows the total number of inbound LLDP
advertisements discarded by < port-list >. This can occur, for
example, when a new neighbor is detected on the port, but the
switch is already supporting the maximum number of
neighbors. Refer to “Neighbor Maximum” on page 13-75. This
can also be an indication of advertisement formatting
problems in the neighbor device.
Frames Invalid: Shows the total number of invalid LLDP
advertisements received on the port. An invalid advertisement
can be caused by header formatting problems in the neighbor
device.
TLVs Unrecognized: Shows the total number of LLDP TLVs
received on a port with a type value in the reserved range. This
could be caused by a basic management TLV from a later LLDP
version than the one currently running on the switch.
TLVs Discarded: Shows the total number of LLDP TLVs discarded
for any reason. In this case, the advertisement carrying the
TLV may be accepted, but the individual TLV was not usable.
Neighbor Ageouts: Shows the number of LLDP neighbors
dropped on the port due to Time-to-Live expiring.
13-74
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Counters showing frames
sent on a port but no
frames received on that
port indicates an active
link with a device that
either has LLDP disabled
on the link or is not LLDPaware.
Figure 13-22. Example of a Global LLDP Statistics Display
Figure 13-23. Example of a Per-Port LLDP Statistics Display
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.
LLDP Packet Forwarding: An 802.1D-compliant switch does not forward
LLDP packets, regardless of whether LLDP is globally enabled or disabled on
the switch.
13-75
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
One IP Address Advertisement Per-Port: LLDP advertises only one IP
address per-port, even if multiple IP addresses are configured by lldp config
< port-list > ipAddrEnable on a given port.
802.1Q VLAN Information. LLDP packets do not include 802.1Q header
information, and are always handled as untagged packets.
Effect of 802.1X Operation. If 802.1X port security is enabled on a port
and a connected device is not authorized, LLDP packets are not transmitted
or received on that port. Any neighbor data stored in the neighbor MIB for that
port prior to the unauthorized device connection remains in the MIB until it
ages out. If an unauthorized device later becomes authorized, LLDP transmit
and receive operation resumes.
Neighbor Data Can Remain in the Neighbor Database After the
Neighbor Is Disconnected. After disconnecting a neighbor LLDP device
from the switch, the neighbor can continue to appear in the switch’s neighbor
database for an extended period if the neighbor’s holdtime-multiplier is high;
especially if the refresh-interval is large. Refer to “Changing the Time-to-Live
for Transmitted Advertisements” on page 13-48.
Mandatory TLVs. All mandatory TLVs required for LLDP operation are also
mandatory for LLDP-MED operation.
Determining the Switch Port Number Included in Topology Change
Notification Traps. Enabling topology change notification on a switch port
and then connecting or disconnecting an LLDP-MED endpoint on that port
causes the switch to send an SNMP trap to notify the designated management
station(s). The port number included in the trap corresponds to the internal
number the switch maintains for the designated port, and not the port’s
external (slot/number) identity. To match the port’s external slot/number to
the internal port number appearing in an SNMP trap, use the walkmib ifDescr
command, as shown in the following figure:
13-76
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
ProCurve# walkmib ifDescr
ifDescr.1 = D1
ifDescr.2 = D2
ifDescr.3 = D3
.
.
.
ifDescr.23 = X1
ifDescr.24 = X2
ifDescr.25 = C1
ifDescr.75 = DEFAULT_VLAN
.
.
.
Figure 13-24. Matching Internal Port Numbers to External Slot/Port Numbers
LLDP and CDP Data Management
This section describes points to note regarding LLDP (Link-Layer Discovery
Protocol) and CDP (Cisco Discovery Protocol) data received by the switch
from other devices. LLDP operation includes both transmitting LLDP packets
to neighbor devices and reading LLDP packets received from neighbor
devices. CDP operation is limited to reading incoming CDP packets from
neighbor devices. (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. (The switch only stores CDP data
that has a corresponding field in the LLDP neighbor database.) The neighbor
database itself can be read by either LLDP or CDP methods or by using the
show lldp commands. Take note of the following rules and conditions:
■
If the switch receives both LLDP and CDP advertisements on the same
port from the same neighbor the switch stores this information as two
separate entries if the advertisements have differences chassis ID and port
ID information.
■
If the chassis and port ID information are the same, the switch stores this
information as a single entry. That is, LLDP data overwrites the corresponding CDP data in the neighbor database if the chassis and port ID
information in the LLDP and CDP advertisements received from the same
device is the same.
■
Data read from a CDP packet does not support some LLDP fields, such as
“System Descr”, “SystemCapSupported”, and “ChassisType”. For such
fields, LLDP assigns relevant default values. Also:
13-77
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Note
•
The LLDP “System Descr” field maps to CDP’s “Version” and “Platform” fields.
•
The switch assigns “ChassisType” and “PortType” fields as “local” for
both the LLDP and the CDP advertisements it receives.
•
Both LLDP and CDP support the “System Capability” TLV. However,
LLDP differentiates between what a device is capable of supporting
and what it is actually supporting, and separates the two types of
information into subelements of the System Capability TLV. CDP has
only a single field for this data. Thus, when CDP System Capability
data is mapped to LLDP, the same value appears in both LLDP System
Capability fields.
•
System Name and Port Descr are not communicated by CDP, and thus
are not included in the switch’s Neighbors database.
Because ProCurve switches do not generate CDP packets, they are not
represented in the CDP data collected by any neighbor devices running CDP.
A switch with CDP disabled forwards the CDP packets it receives from other
devices, but does not store the CDP information from these packets in its own
MIB.
LLDP data transmission/collection and CDP data collection are both enabled
in the switch’s default configuration. In this state, an SNMP network
management application designed to discover devices running either CDP or
LLDP can retrieve neighbor information from the switch regardless of whether
LLDP or CDP is used to collect the device-specific information.
13-78
Protocol State Packet
Generation
Inbound Data Management Inbound Packet Forwarding
CDP Enabled1
n/a
Store inbound CDP data.
CDP Disabled
n/a
No storage of CDP data from Floods inbound CDP packets
neighbor devices.
from connected devices to
outbound ports.
No forwarding of inbound
CDP packets.
LLDP Enabled1 Generates and Store inbound LLDP data.
transmits
LLDP packets
out all ports on
the switch.
No forwarding of inbound
LLDP packets.
LLDP Disabled No packet
generation.
No forwarding of inbound
LLDP packets.
No storage of LLDP data
from neighbor devices.
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Protocol State Packet
Generation
Inbound Data Management Inbound Packet Forwarding
1Both CDP data collection and LLDP transmit/receive are enabled in the default configuration.
If a switch receives CDP packets and LLDP packets from the same neighbor device on the
same port, it stores and displays the two types of information separately if the chassis and
port ID information in the two types of advertisements is different. In this case, if you want
to use only one type of data from a neighbor sending both types, disable the unwanted
protocol on either the neighbor device or on the switch. However, if the chassis and port ID
information in the two types of advertisements is the same, the LLDP information overwrites
the CDP data for the same neighbor device on the same port.
CDP Operation and Commands
By default the switches covered in 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.
When a CDP-enabled switch receives a CDP packet from another CDP device,
it enters that device’s data in the CDP Neighbors table, along with the port
number where the data was received (and does not forward the packet). The
switch also periodically purges the table of any entries that have expired. (The
hold time for any data entry in the switch’s CDP Neighbors table is configured
in the device transmitting the CDP packet, and cannot be controlled in the
switch receiving the packet.) A switch reviews the list of CDP neighbor entries
every three seconds, and purges any expired entries.
13-79
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Note
Command
Page
show cdp
13-80
show cdp neighbors [< port-list > detail]
[detail < port-list >]
13-81
[no] cdp run
13-81
[no] cdp enable < port-list >
13-82
For details on how to use an SNMP utility to retrieve information from the
switch’s CDP Neighbors table maintained in the switch’s MIB (Management
Information Base), refer to the documentation provided with the particular
SNMP utility.
Viewing the Switch’s Current CDP Configuration. CDP is shown as
enabled/disabled both globally on the switch and on a per-port basis.
Syntax: show cdp
Lists the switch’s global and per-port CDP configuration.
The following example shows the default CDP configuration.
ProCurve# show cdp
Global CDP information
Enable CDP [Yes] : Yes (Receive Only)
Port
---D1
D2
D3
D4
.
.
.
CDP
-------enabled
enabled
enabled
enabled
.
.
.
Figure 13-25. Example of Show CDP with the Default CDP Configuration
13-80
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
Viewing the Switch’s Current CDP Neighbors Table. Devices are listed
by the port on which they were detected.
Syntax: show cdp neighbors
Lists the neighboring CDP devices the switch detects,
with a subset of the information collected from the
device’s CDP packet.
[ [e] port-numb [detail] ]
Lists the CDP device connected to the specified port.
(Allows only one port at a time.) Using detail provides
a longer list of details on the CDP device the switch
detects on the specified port.
[detail [ [e] port-num ] ]
Provides a list of the details for all of the CDP devices
the switch detects. Using port-num produces a list of
details for the selected port.
Figure 13-26 lists CDP devices that the switch has detected by receiving their
CDP packets.
ProCurve# show cdp neighbors
CDP neighbors information
Port
---1
1
1
Device ID
----------------------------HP ProCurve Switch 2824(00...
HP ProCurve Switch 2524(00...
HP ProCurve Switch 2824(00...
| Platform
Capability
+--------------------------- ----------| Revision I.08.58 /sw/code... S
| Revision F.05.17 /sw/code... S
| Revision I.08.58 /sw/code... S
Figure 13-26. Example of CDP Neighbors Table Listing
Enabling CDP Operation. Enabling CDP operation (the default) on the
switch causes the switch to add entries to its CDP Neighbors table for any
CDP packets it receives from other neighboring CDP devices.
Disabling CDP Operation. Disabling CDP operation clears the switch’s
CDP Neighbors table and causes the switch to drop inbound CDP packets
from other devices without entering the data in the CDP Neighbors table.
Syntax: [no] cdp run
Enables or disables CDP read-only operation on the switch.
(Default: Enabled)
13-81
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
For example, to disable CDP read-only on the switch:
ProCurve(config)# no cdp run
When CDP is disabled:
■
show cdp neighbors displays an empty CDP Neighbors table
■
show cdp displays
Global CDP information
Enable CDP [Yes]: No
Enabling or Disabling CDP Operation on Individual Ports. In the
factory-default configuration, the switch has all ports enabled to receive CDP
packets. 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-82
A
File Transfers
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Downloading Switch Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
General Software Download Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Using TFTP To Download Software from a Server . . . . . . . . . . . . . . A-4
Menu: TFTP Download from a Server to Primary Flash . . . . . . . A-4
CLI: TFTP Download from a Server to Flash . . . . . . . . . . . . . . . . A-7
Enabling TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Using Auto-TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Using Secure Copy and SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
The SCP/SFTP Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Disable TFTP and Auto-TFTP for Enhanced Security . . . . . . . A-13
Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
SCP/SFTP Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Troubleshooting SSH, SFTP, and SCP Operations . . . . . . . . . . A-17
Using Xmodem to Download Switch Software From a PC or UNIX
Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19
Menu: Xmodem Download to Primary Flash . . . . . . . . . . . . . . . A-19
CLI: Xmodem Download from a PC or UNIX Workstation to
Primary or Secondary Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-20
Switch-to-Switch Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Menu: Switch-to-Switch Download to Primary Flash . . . . . . . . A-21
CLI: Switch-To-Switch Downloads . . . . . . . . . . . . . . . . . . . . . . . A-22
Using PCM+ to Update Switch Software . . . . . . . . . . . . . . . . . . . . . . A-24
Copying Software Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24
TFTP: Copying a Software Image to a Remote Host . . . . . . . . . A-24
Xmodem: Copying a Software Image from the Switch to a
USB Serial Console Connected PC or UNIX Workstation . . . . A-24
A-1
File Transfers
Contents
Transferring Switch Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . A-25
TFTP: Copying a Configuration File to a Remote Host . . . . . . . A-25
TFTP: Copying a Configuration File from a Remote Host . . . . A-26
TFTP: Copying a Customized Command File to a Switch . . . . A-26
Xmodem: Copying a Configuration File to a USB Serial Console
Connected PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . . . . A-27
Xmodem: Copying a Configuration File from a Serially
Connected PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . . . . A-28
Copying Diagnostic Data to a Remote
Host, USB Device, PC or UNIX Workstation . . . . . . . . . . . . . . . . . . . A-29
Copying Command Output to a Destination Device . . . . . . . . . A-30
Copying Event Log Output to a Destination Device . . . . . . . . . A-30
Copying Crash Data Content to a Destination Device . . . . . . . A-31
Copying Crash Log Data Content to a Destination Device . . . . A-32
A-2
File Transfers
Overview
Overview
The switches covered in this guide support several methods for transferring
files to and from a physically connected device, or via the network, including
TFTP, Xmodem, and USB. This appendix explains how to download new
switch software, and upload or download switch configuration files and
software images. It contains the following information:
■
Downloading switch software (begins on this page)
■
Copying software images (page A-25)
■
Transferring switch configurations (begins on page A-26)
■
Copying diagnostic data (begins on page A-30)
Downloading Switch Software
ProCurve periodically provides switch software updates through the ProCurve Networking web site. For more information, refer to the support and
warranty booklet, or visit www.hp.com/#Support. After you acquire a new
software version, you can use one of the following methods for downloading
software to the switch:
Software Download Feature
Default
Menu
CLI
Web
TFTP
n/a
page A-5
page A-7
—
Xmodem
n/a
page A-20
page A-21
—
USB
n/a
n/a
page A-22
—
n/a
page A-22
page A-23
—
Switch-to-Switch
Software Update Manager in PCM+
Refer to the documentation provided with PCM+.
Note
This manual uses the terms switch software and software image to refer to
the downloadable software files the switch uses to operate its networking
features. Other terms sometimes include Operating System, or OS.
Note
xmodem should not be used over the OA serial console. It should only be used
over the USB serial console connection.
A-3
File Transfers
Downloading Switch Software
General Software Download Rules
Note
■
Switch software that you download via the menu interface always goes
to primary flash.
■
After a software download, you must reboot the switch to implement the
new software. Until a reboot occurs, the switch continues to run on the
software it was using before the download commenced.
Downloading new switch software does not change the current switch configuration. The switch configuration is contained in separate files that can also
be transferred. Refer to “Transferring Switch Configurations” on page A-25.
In most cases, if a power failure or other cause interrupts a flash image
download, the switch reboots with the image previously stored in primary
flash. In the unlikely event that the primary image is corrupted (which may
occur if a download is interrupted by a power failure), the switch goes into
boot ROM mode. In this case, use the boot ROM console to download a new
image to primary flash. Refer to “Restoring a Flash Image” on page C-77.
Using TFTP To Download Software from a Server
This procedure assumes that:
■
A software version for the switch has been stored on a TFTP server
accessible to the switch. (The software file is typically available at
www.hp.com/#Support.)
■
The switch is properly connected to your network and has already been
configured with a compatible IP address and subnet mask.
■
The TFTP server is accessible to the switch via IP.
Before you use the procedure, do the following:
Note
A-4
■
Obtain the IP address of the TFTP server in which the software file has
been stored.
■
If VLANs are configured on the switch, determine the name of the VLAN
in which the TFTP server is operating.
■
Determine the name of the software file stored in the TFTP server for the
switch (for example, E0820.swi).
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 software filenames on the server.
File Transfers
Downloading Switch Software
Menu: TFTP Download from a Server to Primary Flash
Note that the menu interface accesses only the primary flash.
1.
In the console Main Menu, select Download OS to display the screen in
figure A-1. (The term “OS”, or “operating system” refers to the switch
software):
===========================-TELNET - MANAGER MODE -============================
Download OS
Current Software revision : Z.14.04
Method [TFTP] : TFTP
TFTP Server :
Remote File Name :
Actions->
Cancel
Edit
eXecute
Help
Select the file transfer method (TFTP and XMODEM are currently supported).
Use arrow keys to change field selection, <Space> to toggle field choices,
and <Enter> to go to Actions.
Figure A-1.
Example of a Download OS (Software) Screen (Default Values)
2.
Press [E] (for Edit).
3.
Ensure that the Method field is set to TFTP (the default).
4.
In the TFTP Server field, type in the IP address of the TFTP server in which
the software file has been stored.
5.
In the Remote File Name field, type the name of the software file. If you
are using a UNIX system, remember that the filename is case-sensitive.
6.
Press [Enter], then [X] (for eXecute) to begin the software download. The
following screen then appears:
==========================-TELNET - MANAGER MODE -============================
Download OS
Current Software revision : Z.14.04
Method [TFTP] : TFTP
TFTP Server : 10.29.227.105
Remote File Name : Z.15.00.swi
Received 370,000 bytes of OS download.
+--------------------------------------------------------------------+
|********************
|
+--------------------------------------------------------------------+
Figure A-2.
Example of the Download OS (Software) Screen During a Download
A-5
File Transfers
Downloading Switch Software
A “progress” bar indicates the progress of the download. When the entire
software file has been received, all activity on the switch halts and you
will see Validating and writing system software to FLASH...
7.
After the primary flash memory has been updated with the new software,
you must reboot the switch to implement the newly downloaded software.
Return to the Main Menu and press [6] (for Reboot Switch). You will then
see this prompt:
Continue reboot of system?
:
No
Press the space bar once to change No to Yes, then press [Enter] to begin
the reboot.
Note
When you use the menu interface to download a switch software, the new
image is always stored in primary flash. Also, using the Reboot Switch
command in the Main Menu always reboots the switch from primary flash.
Rebooting the switch from the CLI gives you more options. Refer to
“Rebooting the Switch” on page 6-19.
8.
After you reboot the switch, confirm that the software downloaded correctly:
a.
From the Main Menu, select 1. Status and Counters, and from the Status
and Counters menu, select 1. General System Information
b.
Check the Firmware revision line.
Troubleshooting TFTP Download Failures. When using the menu interface, if a TFTP download fails, the Download OS (Operating System, or
software) screen indicates the failure.
===========================-TELNET - MANAGER MODE -============================
Download OS
Current Software revision : Z.14.04
Method [TFTP] : TFTP
TFTP Server : 10.29.227.105
Remote File Name : os
Received 0 bytes of OS download.
+--------------------------------------------------------------------+
|
|
+--------------------------------------------------------------------+
Connection to 10.29.227.105 failed
Press any key to continue
Figure A-3.
A-6
Example of Message for Download Failure
File Transfers
Downloading Switch Software
To find more information on the cause of a download failure, examine the
messages in the switch’s Event Log by executing the show log tftp command
from the CLI. Also:
■
For more on the Event Log, see “Using the Event Log for Troubleshooting
Switch Problems” on page C-24.
■
For descriptions of individual Event Log messages, refer to the latest
version of the Event Log Message Reference Guide for your switch. (See
also “Getting Documentation From the Web” on page 1-6.)
Some of the causes of download failures include:
Note
■
Incorrect or unreachable address specified for the TFTP Server parameter.
This may include network problems.
■
Incorrect VLAN.
■
Incorrect name specified for the Remote File Name parameter, or the
specified file cannot be found on the TFTP server. This can also occur if
the TFTP server is a UNIX machine and the case (upper or lower) for the
filename on the server does not match the case for the filename entered
for the Remote File Name parameter in the Download OS (Operating System,
or software) screen.
■
One or more of the switch’s IP configuration parameters are incorrect.
■
For a UNIX TFTP server, the file permissions for the software file do not
allow the file to be copied.
■
Another console session (through either a direct connection to a terminal
device or through Telnet) was already running when you started the
session in which the download was attempted.
If an error occurs in which normal switch operation cannot be restored, the
switch automatically reboots itself. In this case, an appropriate message is
displayed after the switch reboots.
CLI: TFTP Download from a Server to Flash
Syntax: copy tftp flash <ip-address> <remote-file> [< primary | secondary > ]
[oobm]
A-7
File Transfers
Downloading Switch Software
This command automatically downloads a switch software
file to primary or secondary flash. Note that if you do not
specify the flash destination, the TFTP download defaults to
primary flash.
For switches that have a separate out-of-band management
port, the oobm parameter specifies that the traffic will go
through the out-of-band management interface. If this
parameter is not specified, the traffic goes through the data
interface.
For example, to download a switch software file named k0800.swi from a
TFTP server with the IP address of 10.28.227.103 to primary flash:
1.
Execute copy as shown below:
z
Dynamic counter continually displays the
number of bytes transferred.
Figure A-4.
2.
This message means that the image you
want to upload will replace the image
currently in primary flash.
Example of the Command to Download an OS (Switch Software)
When the switch finishes downloading the software file from the server,
it displays this progress message:
Validating and Writing System Software to FLASH …
3.
When the download finishes, you must reboot the switch to implement
the newly downloaded software image. To do so, use one of the following
commands:
Syntax: boot system flash < primary | secondary >
Boots from the selected flash.
Syntax: reload
Boots from the flash image and startup-config file. A switch
covered in this guide (with multiple configuration files), also
uses the current startup-config file.
(For more on these commands, refer to “Rebooting the Switch” on page
6-19.)
A-8
File Transfers
Downloading Switch Software
4.
To confirm that the software downloaded correctly, execute show system
and check the Firmware revision line.
For information on primary/secondary flash memory and the boot commands,
refer to “Using Primary and Secondary Flash Image Options” on page 6-14.
Note
If you use auto-tftp to download a new image in a redundant management
system, the active management module downloads the new image to both the
active and standby modules. Rebooting after the auto-tftp process completes
reboots the entire system.
Enabling TFTP
TFTP is enabled by default on the switch. If TFTP operation has been disabled,
you can re-enable it by specifying TFTP client or server functionality with the
tftp <client | server> command at the global configuration level.
Syntax: [no] tftp <client | server [listen <oobm|data|both>]>
Disables/re-enables TFTP for client or server functionality so
that the switch can:
• Use TFTP client functionality to access TFTP servers in the
network to receive downloaded files.
• Use TFTP server functionality to upload files to other devices
on the network.
• For switches that have a separate out-of-band management
port, the listen parameter in a server configuration allows you
to specify whether transfers take place through the out-ofband management (oobm) interface, the data interface, or
both. Refer to Appendix G, “Networked Out-of-Band
Management (OOBM)” in this guide for more information
on out-of-band management.
Usage Notes
To disable all TFTP client or server operation on the switch except for the
auto-TFTP feature, enter the no tftp <client | server> command.
When ip ssh file transfer is used to enable SCP and SFTP functionality on the
switch, this will disable TFTP client and server functionality. Once ip ssh file
transfer is enabled, TFTP and auto-TFTP cannot be re-enabled from the CLI.
When TFTP is disabled, instances of TFTP in the CLI copy command and the
Menu interface “Download OS” screen become unavailable.
A-9
File Transfers
Downloading Switch Software
The no tftp <client | server> command does not disable auto-TFTP operation.
To disable an auto-TFTP command configured on the switch, use the no autotftp command described on page A-11 to remove the command entry from the
switch’s configuration.
For information on how to configure TFTP file transfers on an IPv6 network,
refer to the “IPv6 Management Features” chapter in the IPv6 Configuration
Guide for your switch.
A-10
File Transfers
Downloading Switch Software
Using Auto-TFTP
The auto-tftp command allows you to configure the switch to download
software automatically from a TFTP server.
How It Works. At switch startup, the auto-TFTP feature automatically
downloads a specified software image to the switch from a specified TFTP
server, then reboots the switch. To implement the process, you must first
reboot the switch using one of the following methods:
■
enter the boot system flash primary command in the CLI
■
with the default flash boot image set to primary flash (the default), enter
the boot or the reload command, or cycle the power to the switch. (To reset
the boot image to primary flash, use boot set-default flash primary.)
Syntax: auto-tftp <ip-addr > <filename >
By default, auto-TFTP is disabled. This command
configures the switch to automatically download the
specified software file from the TFTP server at the specified
IP address. The file is downloaded into primary flash
memory at switch startup. The switch then automatically
reboots from primary flash.
Notes: To enable auto-TFTP to copy a software image to
primary flash memory, the version number of the downloaded software file (for example, K_14_01.swi) must be
different from the version number currently in the
primary flash image.
The current TFTP client status (enabled or disabled)
does not affect auto-TFTP operation. (Refer to “Enabling
TFTP” on page A-9.)
Completion of the auto-TFTP process may require
several minutes while the switch executes the TFTP
transfer to primary flash, and then reboots again.
The no form of the command disables auto-TFTP operation
by deleting the auto-tftp entry from the startup configuration.
The no auto-tftp command does not affect the current TFTPenabled configuration on the switch. However, entering the
ip ssh filetransfer command automatically disables both autotftp and tftp operation.
A-11
File Transfers
Downloading Switch Software
Using Secure Copy and SFTP
For some situations you may want to use a secure method to issue commands
or copy files to the switch. By opening a secure, encrypted SSH session and
enabling ip ssh file transfer, you can then use a third-party software application
to take advantage of Secure Copy (SCP) and Secure ftp (SFTP). SCP and SFTP
provide a secure alternative to TFTP for transferring information that may be
sensitive (like switch configuration files) to and from the switch. Essentially
you are creating a secure SSH tunnel as a way to transfer files with SFTP and
SCP channels.
To use these commands you must install on the administrator workstation a
third-party application software client that supports the SFTP and/or SCP
functions. Some examples of software that supports SFTP and SCP are
PuTTY, Open SSH, WinSCP, and SSH Secure Shell. Most of these are freeware
and may be downloaded without cost or licensing from the internet. There are
differences in the way these clients work, so be sure you also download the
documentation.
As described earlier in this chapter you can use a TFTP client on the administrator 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. You can also
roll out new software images with automated scripts that make it easier to
upgrade multiple switches simultaneously and securely.
SFTP (secure file transfer protocol) is unrelated to FTP, although there are
some functional similarities. Once you set up an SFTP session through an SSH
tunnel, some of the commands are the same as FTP commands. Certain
commands are not allowed by the SFTP server on the switch, such as those
that create files or folders. If you try to issue commands such as create or
remove using SFTP the switch server returns an error message.
You can use SFTP just as you would TFTP to transfer files to and from the
switch, but with SFTP your file transfers are encrypted and require authentication, so they are more secure than they would be using TFTP. SFTP works
only with SSH version 2 (SSH v2).
Note
A-12
SFTP over SSH version 1 (SSH v1) is not supported. A request from either the
client or the switch (or both) using SSH v1 generates an error message. The
actual text of the error message differs, depending on the client software in
use. Some examples are:
File Transfers
Downloading Switch Software
Protocol major versions differ: 2 vs. 1
Connection closed
Protocol major versions differ: 1 vs. 2
Connection closed
Received disconnect from < ip-addr >: /usr/local/
libexec/sftp-server: command not supported
Connection closed
SCP (secure copy) is an implementation of the BSD rcp (Berkeley UNIX
remote copy) command tunneled through an SSH connection.
SCP is used to copy files to and from the switch when security is required.
SCP works with both SSH v1 and SSH v2. Be aware that the most third-party
software application clients that support SCP use SSHv1.
How It Works
The general process for using SCP and SFTP involves three steps:
1.
Open an SSH tunnel between your computer and the switch if you haven’t
already done so. (This step assumes that you have already set up SSH on
the switch.)
2.
Execute ip ssh filetransfer to enable secure file transfer.
3.
Use a third-party client application for SCP and SFTP commands.
The SCP/SFTP Process
To use SCP and SFTP:
1.
Open an SSH session as you normally would to establish a secure
encrypted tunnel between your computer and the switch. For more
detailed directions on how to open an SSH session refer to the chapter
titled “Configuring Secure Shell (SSH)” in the Access Security Guide for
your switch. Please note that this is a one-time procedure for new
switches or connections. If you have already done it once you should not
need to do it a second time.
2.
To enable secure file transfer on the switch (once you have an SSH session
established between the switch and your computer), open a terminal
window and type in the following command:
ProCurve(config)# ip ssh filetransfer
A-13
File Transfers
Downloading Switch Software
Disable TFTP and Auto-TFTP for Enhanced Security
Using the ip ssh filetransfer command to enable Secure FTP (SFTP) automatically disables TFTP and auto-TFTP (if either or both are enabled).
ProCurve(config)# ip ssh filetransfer
Tftp and auto-tftp have been disabled.
ProCurve(config)# sho run
Enabling SFTP automatically disables TFTP
and auto-tftp and displays this message.
Running configuration:
; 498358-B21 Configuration Editor; Created on release #Z.14.04
hostname "ProCurve"
module 1 type J8702A
module 2 type J702A
vlan 1
name "DEFAULT_VLAN"
untagged A1-A24,B1-B24
ip address 10.28.234.176 255.255.240.0
exit
ip ssh filetransfer
no tftp-enable
password manager
password operator
Figure A-5.
Viewing the configuration shows that SFTP is
enabled and TFTP is disabled.
Example of Switch Configuration with SFTP Enabled
If you enable SFTP, then later disable it, TFTP and auto-TFTP remain disabled
unless they are explicitly re-enabled.
Operating rules are:
■
A-14
The TFTP feature is enabled by default, and can be enabled or disabled
through the CLI, the Menu interface, or an SNMP application. Auto-TFTP
is disabled by default and must be configured through the CLI.
File Transfers
Downloading Switch Software
Enables/Disables TFTP.
Note: If SFTP is enabled, this field will be set to No. You
cannot use this field to enable TFTP if SFTP is enabled.
Attempting to do so produces an Inconsistent value
message in the banner below the Actions line.
Figure A-6.
Using the Menu Interface To Disable TFTP
■
While SFTP is enabled, TFTP and auto-TFTP cannot be enabled from the
CLI. Attempting to enable either non-secure TFTP option while SFTP is
enabled produces one of the following messages in the CLI:
SFTP must be disabled before enabling tftp.
SFTP must be disabled before enabling auto-tftp.
Similarly, while SFTP is enabled, TFTP cannot be enabled using an SNMP
management application. Attempting to do so generates an “inconsistent
value” message. (An SNMP management application cannot be used to
enable or disable auto-TFTP.)
■
To enable SFTP by using an SNMP management application, you must
first disable TFTP and, if configured, auto-TFTP on the switch. You can
use either an SNMP application or the CLI to disable TFTP, but must use
the CLI to disable auto-TFTP. The following two CLI commands disable
TFTP and auto-TFTP on the switch.
Command Options
If you need to enable SSH v2 (which is required for SFTP) enter this command:
ProCurve(config)# ip ssh version 2
A-15
File Transfers
Downloading Switch Software
Note
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 HP ProCurve 2500 switches).
To confirm that SSH is enabled type in the command
ProCurve(config)# show ip ssh
Once you have confirmed that you have enabled an SSH session (with the show
ip ssh command), enter ip ssh filetransfer so that SCP and/or SFTP can run. You
can then open your third-party software client application to begin using the
SCP or SFTP commands to safely transfer files or issue commands to the
switch.
If you need to disable secure file transfer:
ProCurve(config)# no ip ssh filetransfer
Authentication
Switch memory allows up to ten public keys. This means the authentication
and encryption keys you use for your third-party client SCP/SFTP software
can differ from the keys you use for the SSH session, even though both SCP
and SFTP use a secure SSH tunnel.
Note
SSH authentication is mutually exclusive with RADIUS servers.
Some clients such as PSCP (PuTTY SCP) automatically compare switch host
keys for you. Other clients require you to manually copy and paste keys to the
$HOME/.ssh/known_hosts file. Whatever SCP/SFTP software tool you use, after
installing the client software you must verify that the switch host keys are
available to the client.
Because the third-party software utilities you may use for SCP/SFTP vary, you
should refer to the documentation provided with the utility you select before
performing this process.
SCP/SFTP Operating Notes
■
Any attempts to use SCP or SFTP without using ip ssh filetransfer will cause
the SCP or SFTP session to fail. Depending on the client software in use,
you will receive an error message on the originating console, for example:
IP file transfer not enabled on the switch
A-16
File Transfers
Downloading Switch Software
■
When an SFTP client connects, the switch provides a file system displaying all of its available files and folders. No file or directory creation is
permitted by the user. Files may only be uploaded or downloaded, according to the permissions mask. All of the necessary files the switch will need
are already in place on the switch. You do not need to (nor can you create)
new files.
■
The switch supports one SFTP session or one SCP session at a time.
■
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-data-a
|
crash-data-b
|
crash-data-c
|
crash-data-d
|
crash-data-e
|
crash-data-f
|
crash-data-g
|
crash-data-h
|
crash-data-I
|
crash-data-J
|
crash-data-K
|
crash-data-L
|
crash-log
|
crash-log-a
|
crash-log-b
|
crash-log-c
|
crash-log-d
|
crash-log-e
|
crash-log-f
|
crash-log-g
|
crash-log-h
|
crash-log-I
|
crash-log-J
|
crash-log-K
|
crash-log-L
|
event log
+---os
|
primary
|
secondary
\---ssh
+---mgr_keys
A-17
File Transfers
Downloading Switch Software
|
authorized_keys
\---oper_keys
authorized_keys
■
When using SFTP to copy a software image onto the switch, the command
return takes only a few seconds. However, this does not mean that the
transfer is complete, because the switch requires additional time (typically more than one minute) to write the image to flash in the background.
To verify the file transfer has been completed, you can use the show flash
command or look for a confirmation message in the log as in the following
example:
I 01/09/09 16:17:07 00150 update: Primary Image
updated.
Once you have configured your switch to enable secure file transfers with SCP
and SFTP, files can be copied to or from the switch in a secure (encrypted)
environment and TFTP is no longer necessary.
Troubleshooting SSH, SFTP, and SCP Operations
You can verify secure file transfer operations by checking the switch’s event
log, or by viewing the error messages sent by the switch that most SCP and
SFTP clients will print out on their console.
Note
Messages that are sent by the switch to the client depend on the client software
in use to display them on the user console.
Broken SSH Connection. If an ssh connection is broken at the wrong
moment (for instance, the link goes away or spanning tree brings down the
link), a fatal exception would occur on the switch. If this happens, the switch
will gracefully exit the session and produce an event log message indicating
the cause of failure. The following three examples show the error messages
that may appear in the log depending on the type of session that is running
(SSH, SCP, or SFTP).
ssh: read error Bad file number, session aborted I 01/
01/90 00:06:11 00636 ssh: sftp session from
::ffff:10.0.12.35 W 01/01/90 00:06:26 00641 ssh:
sftp read error Bad file number, session aborted I 01/
01/90 00:09:54 00637 ssh: scp session from
::ffff:10.0.12.35 W 01/01/90
ssh: scp read error Bad file number, session aborted
A-18
File Transfers
Downloading Switch Software
Note
The Bad file number is from the system error value and may differ
depending on the cause of the failure. In the third example, the device file to
read was closed as the device read was about to occur.
Attempt to Start a Session During a Flash Write. If you attempt to
start an SCP (or SFTP) session while a flash write is in progress, the switch
will not allow the SCP or SFTP session to start. Depending on the client
software in use, the following error message may appear on the client console:
Received disconnect from 10.0.12.31: 2: Flash access
in progress
lost connection
Failure to Exit from a Previous Session. This next example shows the
error message that may appear on the client console if a new SCP (or SFTP)
session is started from a client before the previous client session has been
closed (the switch requires approximately ten seconds to timeout the previous
session):
Received disconnect from 10.0.12.31: 2: Wait for
previous session to complete
lost connection
Attempt to Start a Second Session. The switch supports only one SFTP
session or one SCP session at a time. If a second session is initiated (for
example, an SFTP session is running and then an SCP session is attempted),
then the following error message may appear on the client console:
Received disconnect from 10.0.12.31: 2: Other SCP/SFTP
session running
lost connection
Using Xmodem to Download Switch Software From a
PC or UNIX Workstation
This procedure assumes that:
■
The switch software is stored on a disk drive in the PC.
■
The terminal emulator you are using includes the Xmodem binary transfer
feature. (For example, in the HyperTerminal application included with
Windows NT, you would use the Send File option in the Transfer dropdown
menu.)
A-19
File Transfers
Downloading Switch Software
Menu: Xmodem Download to Primary Flash
Note that the menu interface accesses only the primary flash.
1.
From the console Main Menu, select
7. Download OS
2.
Press [E] (for Edit).
3.
Use the Space bar to select XMODEM in the Method field.
4.
Press [Enter], then [X] (for eXecute) to begin the software download. The
following message then appears:
Press enter and then initiate Xmodem transfer
from the attached computer.....
5.
Press [Enter] and then execute the terminal emulator command(s) to begin
Xmodem binary transfer. For example, using HyperTerminal:
a.
Click on Transfer, then Send File.
b.
Type the file path and name in the Filename field.
c.
In the Protocol field, select Xmodem.
d.
Click on the [Send] button.
The download will then commence. It can take several minutes, depending on the baud rate set in the switch and in your terminal emulator.
6.
After the primary flash memory has been updated with the new software,
you must reboot the switch to implement the newly downloaded software.
Return to the Main Menu and press [6] (for Reboot Switch). You will then
see the following prompt:
Continue reboot of system? : No
Press the space bar once to change No to Yes, then press [Enter] to begin
the reboot.
7.
To confirm that the software downloaded correctly:
a.
From the Main Menu, select
1. Status and Counters
1. General System Information
b.
A-20
Check the Firmware revision line.
File Transfers
Downloading Switch Software
CLI: Xmodem Download from a PC or UNIX Workstation to
Primary or Secondary Flash
Using Xmodem and a terminal emulator, you can download a software file to
either primary or secondary flash.
Syntax: copy xmodem flash [< primary | secondary >]
Downloads a software file to primary or secondary flash. If
you do not specify the flash destination, the Xmodem
download defaults to primary flash.
For example, to download a switch software file named E0822.swi from a PC
(running a terminal emulator program such as HyperTerminal) to primary
flash:
1.
Execute the following command in the CLI:
2.
Execute the terminal emulator commands to begin the Xmodem transfer.
For example, using HyperTerminal:
a.
Click on Transfer, then Send File.
b.
Type the file path and name in the Filename field.
c.
In the Protocol field, select Xmodem.
d.
Click on the [Send] button.
The download can take several minutes, depending on the baud rate used
in the transfer.
3.
When the download finishes, you must reboot the switch to implement
the newly downloaded software. To do so, use one of the following
commands:
Syntax: boot system flash <primary | secondary>
Reboots from the selected flash.
Syntax: reload
Reboots from the flash image currently in use.
(For more on these commands, see “Rebooting the Switch” on page 6-19.)
A-21
File Transfers
Downloading Switch Software
4.
To confirm that the software downloaded correctly:
ProCurve> show system
Check the Firmware revision line. It should show the software version that
you downloaded in the preceding steps.
If you need information on primary/secondary flash memory and the boot
commands, refer to “Using Primary and Secondary Flash Image Options” on
page 6-14.
Switch-to-Switch Download
You can use TFTP to transfer a software image between two switches of the
same series. The menu interface enables you to transfer primary-to-primary
or secondary-to-primary. The CLI enables all combinations of flash location
options.
Menu: Switch-to-Switch Download to Primary Flash
Using the menu interface, you can download a switch software file from either
the primary or secondary flash of one switch to the primary flash of another
switch of the same series.
1.
From the switch console Main Menu in the switch to receive the download, select 7. Download OS screen.
2.
Ensure that the Method parameter is set to TFTP (the default).
3.
In the TFTP Server field, enter the IP address of the remote switch containing the software file you want to download.
4.
For the Remote File Name, enter one of the following:
•
To download the software in the primary flash of the source switch,
type “flash” in lowercase characters.
•
To download the software in the secondary flash of the source switch,
type
/os/secondary.
5.
Press [Enter], then [X] (for eXecute) to begin the software download.
6.
A “progress” bar indicates the progress of the download. When the entire
switch software download has been received, all activity on the switch
halts and the following messages appear:
Validating and writing system software to FLASH...
A-22
File Transfers
Downloading Switch Software
7.
After the primary flash memory has been updated with the new software,
you must reboot the switch to implement the newly downloaded software.
Return to the Main Menu and press [6] (for Reboot Switch). You will then
see this prompt:
Continue reboot of system? : No
Press the space bar once to change No to Yes, then press [Enter] to begin
the reboot.
8.
To confirm that the software downloaded correctly:
a.
From the Main Menu, select
Status and Counters
General System Information
b.
Check the Firmware revision line.
CLI: Switch-To-Switch Downloads
Where two switches in your network belong to the same series, you can
download a software image between them by initiating a copy tftp command
from the destination switch. The options for this CLI feature include:
■
Copy from primary flash in the source to either primary or secondary in
the destination.
■
Copy from either primary or secondary flash in the source to either
primary or secondary flash in the destination.
Downloading from Primary Only.
Syntax: copy tftp flash < ip-addr > flash [ primary | secondary ]
This command (executed in the destination switch)
downloads the software flash in the source switch’s primary
flash to either the primary or secondary flash in the
destination switch.
If you do not specify either a primary or secondary flash location for the
destination, the download automatically goes to primary flash.
For example, to download a software file from primary flash in a switch with
an IP address of 10.29.227.103 to the primary flash in the destination switch,
you would execute the following command in the destination switch’s CLI:
A-23
File Transfers
Downloading Switch Software
Running Total
of Bytes
Downloaded
Figure A-7. Switch-To-Switch, from Primary in Source to Either Flash in Destination
Downloading from Either Flash in the Source Switch to Either Flash
in the Destination Switch.
Syntax: copy tftp flash < ip-addr > < /os/primary > | < /os/secondary > [ primary |
secondary ]
This command (executed in the destination switch) gives you
the most options for downloading between switches. If you do
not specify either a primary or secondary flash location for
the destination, the download automatically goes to primary
flash.
For example, to download a software file from secondary flash in a switch
with an IP address of 10.28.227.103 to the secondary flash in a destination
switch, you would execute the following command in the destination switch’s
CLI:
Figure A-8. Switch-to-Switch, from Either Flash in Source to Either Flash in
Destination
Using PCM+ to Update Switch Software
ProCurve Manager Plus includes 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.
A-24
File Transfers
Copying Software Images
Copying Software Images
Using the CLI commands described in this section, you can copy software
images from the switch to another device using tftp, xmodem, or usb.
Note
For details on how switch memory operates, including primary and secondary
flash, refer to Chapter 6, “Switch Memory and Configuration”.
TFTP: Copying a Software Image to a Remote Host
Syntax: copy flash tftp < ip-addr > < filename >
This command copies the primary flash image to a TFTP
server.
For example, to copy the primary flash to a TFTP server having an IP address
of 10.28.227.105:
ProCurve# copy flash tftp 10.28.227.105 z0800.swi
where z0800.swi is the filename given to the flash image being copied.
Xmodem: Copying a Software Image from the Switch to a
USB Serial Console Connected PC or UNIX Workstation
To use this method, the switch must be connected via the USB console to a
PC or UNIX workstation.
Syntax: copy flash xmodem < pc | unix >
Uses Xmodem to copy a designated configuration file from the
switch to a PC or Unix workstation.
For example, to copy the primary flash image to a serially connected PC:
1. Execute the following command:
Procurve# copy xmodem flash
Press ‘Enter’ and start XMODEM on your host...
2.
After you see the above prompt, press [Enter].
3.
Execute the terminal emulator commands to begin the file transfer.
A-25
File Transfers
Transferring Switch Configurations
Transferring Switch Configurations
Transfer Features
Feature
Page
Use TFTP to copy from a remote host to a config file
A-27
Use TFTP to copy a config file to a remote host
A-28
Use Xmodem to copy a configuration from a serially connected host to a config file
A-28
Use Xmodem to copy a config file to a serially connected host
A-29
Using the CLI commands described in this section, you can copy switch
configurations to and from a switch.
Note
For greater security, you can perform all TFTP operations using SFTP as
described in the section on Using Secure Copy and SFTP on page A-12.
The include-credentials command can also be used to save passwords, secret
keys, and other security credentials in the running config file. For more
information, see the section on “Saving Security Credentials in a Config File”
in the Access Security Guide for your switch.
TFTP: Copying a Configuration File to a Remote Host
Syntax: copy < startup-config | running-config > tftp < ip-addr > < remote-file >
[ pc | unix ] [oobm]
copy config < filename > tftp < ip-addr > < remote-file > [ pc | unix ] [oobm]
This command can copy a designated config file in the switch
to a TFTP server. For more on multiple configuration files,
refer to “Multiple Configuration Files” on page 6-25.
For switches that have a separate out-of-band management
port, the oobm parameter specifies that the traffic will go
through the out-of-band management interface. If this
parameter is not specified, the traffic goes through the data
interface.
For example, to upload the current startup configuration to a file named
sw8200 in the configs directory on drive “d” in a TFTP server having an IP
address of 10.28.227.105:
ProCurve# copy startup-config tftp 10.28.227.105
d:\configs\sw8200
A-26
File Transfers
Transferring Switch Configurations
TFTP: Copying a Configuration File from a Remote Host
Syntax: copy tftp < startup-config | running-config > < ip-address > < remote-file >
[ pc | unix ]
copy tftp config < filename > < ip-address > < remote-file > [ pc | unix ]
This command can copy a configuration from a remote host
to a designated config file in the switch. For more on
multiple configuration files, refer to “Multiple
Configuration Files” on page 6-25.
(Refer to “Using Primary and Secondary Flash Image
Options” on page 6-14 for more on flash image use.)
For example, to download a configuration file named sw8200 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\sw8200
TFTP: Copying a Customized Command File to a Switch
Using the copy tftp command with the show-tech option provides the ability to
copy a customized command file to the switch. When the show tech custom
command is executed, the commands in the custom file are executed instead
of the hard-coded list of commands. If no custom file is found, the current
hard-coded list is executed. This list contains commands to display data such
as the image stamp, running configuration, boot history, port settings, and so
on.
Syntax: copy tftp show-tech <ipv4 or ipv6 address> <filename>
Copy a customized command file to the switch.
ProCurve(config)# copy tftp show-tech 10.10.10.3 commandfile1
Figure A-9. Example of Using the copy tftp show-tech Command to Upload a
Customized Command File
A-27
File Transfers
Transferring Switch Configurations
Syntax: show tech custom
Executes the commands found in a custom file instead of the
hard-coded list.
Note: Exit the global config mode (if needed) before executing
show tech commands.
You can include show tech commands in the custom file, with the exception
of show tech custom. For example, you can include the command show tech all.
If no custom file is found, a message displays stating “No SHOW-TECH file
found.”
ProCurve# show tech custom
No SHOW-TECH file found.
No custom file was uploaded with the copy tftp showtech command
Figure A-10. Example of the show tech custom Command
Xmodem: Copying a Configuration File to a USB Serial
Console Connected PC or UNIX Workstation
To use this method, the switch must be connected via the USB serial console
to a PC or UNIX workstation. You will need to:
■
Determine a filename to use.
■
Know the directory path you will use to store the configuration file.
Syntax: copy < startup-config | running-config > xmodem < pc | unix >
copy config < filename > xmodem < pc | unix >
Uses Xmodem to copy a designated configuration file from the
switch to a PC or Unix workstation. For more on multiple
configuration files, refer to “Multiple Configuration Files” on
page 6-25.
For example, to copy a configuration file to a PC serially connected to the
switch:
1.
A-28
Determine the file name and directory location on the PC.
File Transfers
Transferring Switch Configurations
2.
Execute the following command:
3.
After you see the above prompt, press [Enter].
4.
Execute the terminal emulator commands to begin the file transfer.
Xmodem: Copying a Configuration File from a Serially
Connected PC or UNIX Workstation
To use this method, the switch must be connected via the serial port to a PC
or UNIX workstation on which is stored the configuration file you want to
copy. To complete the copying, you will need to know the name of the file to
copy and the drive and directory location of the file.
Syntax: copy xmodem startup-config < pc | unix >
copy xmodem config < filename > < pc | unix >
Copies a configuration file from a serially connected PC or
UNIX workstation to a designated configuration file on the
switch. For more on multiple configuration files, refer to
“Multiple Configuration Files” on page 6-25.
For example, to copy a configuration file from a PC serially connected to the
switch:
1.
Execute the following command:
2.
After you see the above prompt, press [Enter].
3.
Execute the terminal emulator commands to begin the file transfer.
4.
When the download finishes, you must reboot the switch to implement
the newly downloaded software. To do so, use one of the following
commands:
A-29
File Transfers
Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation
Syntax: boot system flash [ primary | secondary ]
boot system flash [ config < filename >
Switches boot from the designated configuration file. For more
on multiple configuration files, refer to “Multiple
Configuration Files” on page 6-25.
Syntax: reload
Reboots from the flash image currently in use.
(For more on these commands, refer to “Rebooting the Switch” on page
6-19.)
Copying Diagnostic Data to a Remote
Host, USB Device, PC or UNIX
Workstation
You can use the CLI to copy the following types of switch data to a text file in
a destination device:
■
Command Output: Sends the output of a switch CLI command as a file on
the destination device.
■
Event Log: Copies the switch’s Event Log into a file on the destination
device.
■
Crash Data: software-specific data useful for determining the reason for
a system crash.
■
Crash Log: Processor-Specific operating data useful for determining the
reason for a system crash.
The destination device and copy method options are as follows (CLI key word
is in bold):
A-30
■
Remote Host via TFTP.
■
USB serial console connected PC or UNIX workstation.
File Transfers
Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation
Copying Command Output to a Destination Device
Syntax: copy command-output < “cli-command” > tftp < ip-address > < filepathfilename >
copy command-output < “cli-command” > usb < filename >
copy command-output <“cli-command”> xmodem
These commands direct the displayed output of a CLI
command to a remote host, attached USB device, or to a serially
connected PC or UNIX workstation.
For example, to use Xmodem to copy the output of show config to a serially
connected PC:
At this point, press
[Enter] and start the
Xmodem command
sequence in your
terminal emulator.
Indicates the operation is finished.
Figure A-11. Example of Sending Command Output to a File on an Attached PC
Note
The command you specify must be enclosed in double-quote marks.
Copying Event Log Output to a Destination Device
Syntax: copy event-log tftp < ip-address > < filepath_filename >
copy event-log usb < filename >
copy event-log xmodem <filename>
These commands copy the Event Log content to a remote host,
attached USB device, or to a serially connected PC or UNIX
workstation.
For example, to copy the event log to a PC connected to the switch:
A-31
File Transfers
Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation
At this point, press
[Enter] and start the
Xmodem command
sequence in your
terminal emulator.
Figure A-12. Example of Sending Event Log Content to a File on an Attached PC
Copying Crash Data Content to a Destination Device
This command uses TFTP, USB, or Xmodem to copy the Crash Data content
to a destination device. You can copy individual slot information or the
management module’s switch information. If you do not specify either, the
command defaults to the management function’s data.
Syntax: copy crash-data [master>] tftp <ip-address> <filename>
copy crash-data [mm>] usb <filename>
copy crash-data [mm>] xmodem
where: mm
Retrieves crash log or crash data from the switch’s
chassis processor. When “mm” is specified,
crash files from both management modules are
copied.
These commands copy the crash data content to a remote host,
attached USB device, or to a serially connected PC or UNIX
workstation. You can copy the management module (mm)
switch information. If you do not specify either, the command
defaults to the mm data.
For example, to copy the switch’s crash data to a file in a PC:
At this point, press
[Enter] and start the
Xmodem command
sequence in your
terminal emulator.
Figure A-13. Example of Copying Switch Crash Data Content to a PC
A-32
File Transfers
Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation
Copying Crash Log Data Content to a Destination Device
Syntax: copy crash-log [mm>] tftp <ip-address>
<filepath and filename>
copy crash-log [mm>] usb <filename>
copy crash-log [mm>] xmodem
where: mm
Retrieves the crash log from the switch’s
chassis processor. When mm is specified,
crash files from both management modules are
copied.
These commands copy the Crash Log content to a remote host,
attached USB device, or to a serially connected PC or UNIX
workstation. You can copy the management module (mm)
switch information. If you do not specify either, the command
defaults to the mm data.
For example, to copy the Crash Log for slot C to a file in a PC connected to
the switch:
At this point, press
[Enter] and start the
Xmodem command
sequence in your
terminal emulator.
Figure A-14. Example of sending a Crash Log for Slot C to a File on an Attached PC
Copying Crash Logs with Redundant Management. When you are using
redundant management, the copy crash-log command operates somewhat
differently.
Syntax: copy crash-log [mm] tftp <ip-address> <filename>
Copies both the active and standby management modules’
crash logs to a user-specified file. If no parameter is
specified, files from all modules (management and
interface) are concatenated.
mm: retrieves the crash logs from both management modules
and concatenates them.
A-33
B
Monitoring and Analyzing Switch Operation
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Status and Counters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Menu Access To Status and Counters . . . . . . . . . . . . . . . . . . . . . . . . . B-5
General System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
CLI Access to System Information . . . . . . . . . . . . . . . . . . . . . . . . B-7
Task Monitor—Collecting Processor Data . . . . . . . . . . . . . . . . . . . . . B-8
Switch Management Address Information . . . . . . . . . . . . . . . . . . . . . . B-8
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
CLI Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Menu: Displaying Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
CLI Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Viewing Port and Trunk Group Statistics and Flow Control Status B-11
Menu Access to Port and Trunk Statistics . . . . . . . . . . . . . . . . . B-12
CLI Access To Port and Trunk Group Statistics . . . . . . . . . . . . B-13
Web Browser Access To View Port and Trunk Group Statistics B-13
Viewing the Switch’s MAC Address Tables . . . . . . . . . . . . . . . . . . . . B-14
Menu Access to the MAC Address Views and Searches . . . . . . B-14
CLI Access for MAC Address Views and Searches . . . . . . . . . . B-17
Spanning Tree Protocol (MSTP) Information . . . . . . . . . . . . . . . . . . B-18
CLI Access to MSTP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Internet Group Management Protocol (IGMP) Status . . . . . . . . . . . B-19
VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20
Web Browser Interface Status Information . . . . . . . . . . . . . . . . . . . . B-22
Traffic Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
B-1
Monitoring and Analyzing Switch Operation
Contents
Mirroring Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24
Mirrored Traffic Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Local Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Monitored Traffic Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Criteria for Selecting Mirrored Traffic . . . . . . . . . . . . . . . . . . . . . . . . B-26
Mirroring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Endpoint Switches and Intermediate Devices . . . . . . . . . . . . . . B-28
Using the Menu or Web Interface To Configure Local Mirroring . . B-29
Menu and Web Interface Limits . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30
CLI: Configuring Local Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33
Local Mirroring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33
1. Determine the Mirroring Session and Destination . . . . . . . . . . . . B-35
2. Configure a Mirroring Session on the Source Switch . . . . . . . . . . B-35
3. Configure the Monitored Traffic in a Mirror Session . . . . . . . . . . B-35
Traffic Selection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Mirroring-Source Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Selecting All Inbound/Outbound Traffic to Mirror . . . . . . . . . . . . . . B-36
Displaying a Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Displaying the Mirroring Configuration Summary . . . . . . . . . . B-38
Viewing Mirroring in the Current Configuration File . . . . . . . . B-40
Mirroring Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . B-41
Local Mirroring Using Traffic-Direction Criteria . . . . . . . . . . . . B-41
Maximum Supported Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42
Enabling Jumbo Frames To Increase Mirroring Path MTU . . . B-43
Effect of Downstream VLAN Tagging on
Untagged, Mirrored Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45
Troubleshooting Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47
B-2
Monitoring and Analyzing Switch Operation
Overview
Overview
The switches covered in this guide have several built-in tools for monitoring,
analyzing, and troubleshooting switch and network operation:
Note
■
Status: Includes options for displaying general switch information, management address data, port status, port and trunk group statistics, MAC
addresses detected on each port or VLAN, and STP, IGMP, and VLAN data
(page B-4).
■
Counters: Display details of traffic volume on individual ports (page
B-11).
■
Event Log: Lists switch operating events (“Using the Event Log for
Troubleshooting Switch Problems” on page C-24).
■
Alert Log: Lists network occurrences detected by the switch—in the
Status | Overview screen of the web browser interface (page 5-20).
■
Configurable trap receivers: Uses SNMP to enable management stations on your network to receive SNMP traps from the switch. (Refer to
“SNMPv1 and SNMPv2c Traps” on page 13-20.)
■
Port monitoring (mirroring): Copy all traffic from the specified ports
to a designated monitoring port (page B-23).
Link test and ping test—analysis tools in troubleshooting situations—are
described in Appendix C, “Troubleshooting”. Refer to “Diagnostic Tools” on
page C-56.
B-3
Monitoring and Analyzing Switch Operation
Status and Counters Data
Status and Counters Data
This section describes the status and counters screens available through the
switch console interface and/or the web browser interface.
Note
Status or Counters Type
You can access all console screens from the web browser interface via Telnet
to the console. Telnet access to the switch is available in the Device View
window under the Configuration tab.
Interface
Purpose
Page
Menu Access to Status and Menu
Counters
Access menu interface for status and counter data.
B-5
General System
Information
Menu, CLI
Lists switch-level operating information.
B-6
Management Address
Information
Menu, CLI
Lists the MAC address, IP address, and IPX network number for
each VLAN or, if no VLANs are configured, for the switch.
B-8
Port Status
Menu, CLI,
Web
Displays the operational status of each port.
B-10
Port and Trunk Statistics
and Flow Control Status
Menu, CLI,
Web
Summarizes port activity and lists per-port flow control status.
B-11
VLAN Address Table
Menu, CLI
Lists the MAC addresses of nodes the switch has detected on
specific VLANs, with the corresponding switch port.
B-14
Port Address Table
Menu, CLI
Lists the MAC addresses that the switch has learned from the
selected port.
B-14
STP Information
Menu, CLI
Lists Spanning Tree Protocol data for the switch and for individual
ports. If VLANs are configured, reports on a per-VLAN basis.
B-18
IGMP Status
Menu, CLI
Lists IGMP groups, reports, queries, and port on which querier is
located.
B-19
VLAN Information
Menu, CLI
For each VLAN configured in the switch, lists 802.1Q VLAN ID and
up/down status.
B-20
Port Status Overview and
Port Counters
Web
Shows port utilization and counters, and the Alert Log.
B-22
B-4
Monitoring and Analyzing Switch Operation
Status and Counters Data
Menu Access To Status and Counters
Beginning at the Main Menu, display the Status and Counters menu by selecting:
1. Status and Counters
Figure B-1. The Status and Counters Menu
Each of the above menu items accesses the read-only screens described on
the following pages. Refer to the online help for a description of the entries
displayed in these screens.
B-5
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. Refer to the online Help for details.
B-6
Monitoring and Analyzing Switch Operation
Status and Counters Data
CLI Access to System Information
The show system command displays general system information about the
switch.
Syntax: show system [information | enclosure]
Displays global system information and operational
parameters for the switch.
information
Displays global system information and operational
parameters for the switch.
enclosure
Shows rack and enclosure information.
ProCurve 6120 Blade Switch# show system
Status and Counters - General System Information
System Name
System Contact
System Location
: ProCurve 6120 Blade Switch
:
:
MAC Age Time (sec) : 300
Time Zone
: 0
Daylight Time Rule : None
Software revision
ROM Version
: Z.14.04
: Z.14.03
Base MAC Addr
Serial Number
: 002481-b00921
: TW28080080
Up Time
CPU Util (%)
: 92 mins
: 10
Memory
- Total
Free
: 33,554,432
: 21,563,208
Packet
Buffers
- Total
Free
Lowest
Missed
:
:
:
:
IP Mgmt
- Pkts Rx : 2511
Pkts Tx : 55
3022
2895
2748
0
Figure B-3. Example of Switch System Information
B-7
Monitoring and Analyzing Switch Operation
Status and Counters Data
Task Monitor—Collecting Processor Data
The task monitor feature allows you to enable or disable the collection of
processor utilization data. The task-monitor cpu command is equivalent to the
existing debug mode command “taskusage -d”. (The taskUsageShow command
is available as well.)
When the task-monitor command is enabled, the show cpu command summarizes the processor usage by protocol and system functions.
Syntax: [no] task-monitor cpu
Allows the collection of processor utilization data. Only
manager logins can execute this command. The settings are
not persistent, that is, there are no changes to the configuration.
Default: Disabled
ProCurve(config)# task-monitor cpu
ProCurve(config)# show cpu
2
1
5
1
percent busy, from
sec ave: 9 percent
sec ave: 9 percent
min ave: 1 percent
2865 sec ago
busy
busy
busy
% CPU | Description
-------+-------------------------99 | Idle
Figure B-4. Example of the task-monitor cpu Command and show cpu Output
Switch Management Address Information
Menu Access
From the Main Menu, select:
1 Status and Counters …
2. Switch Management Address Information
B-8
Monitoring and Analyzing Switch Operation
Status and Counters Data
Figure B-5. Example of Management Address Information with VLANs Configured
This screen displays addresses that are important for management of the
switch. If multiple VLANs are not configured, this screen displays a single IP
address for the entire switch. Refer to the online Help for details.
Note
As shown in figure B-5, all VLANs on the switches use the same MAC address.
(This includes both the statically configured VLANs and any dynamic VLANs
existing on the switch as a result of GVRP operation.)
Also, the switches covered in this guide use a multiple forwarding database.
When using multiple VLANs and connecting a switch to a device that uses a
single forwarding database, such as a Switch 4000M, there are cabling and
tagged port VLAN requirements. For more on this topic, refer to the section
titled “Multiple VLAN Considerations” in the “Static Virtual LANs (VLANs)
chapter of the Advanced Traffic Management Guide for your switch.
CLI Access
Syntax: show management
B-9
Monitoring and Analyzing Switch Operation
Status and Counters Data
Port Status
The web browser interface and the console interface show the same port
status data.
Menu: Displaying Port Status
From the Main Menu, select:
1. Status and Counters …
4. Port Status
Figure B-6. Example of Port Status on the Menu Interface
CLI Access
Syntax:
show interfaces brief
Web Access
B-10
1.
Click on the Status tab.
2.
Click on [Port Status].
Monitoring and Analyzing Switch Operation
Status and Counters Data
Viewing Port and Trunk Group Statistics and Flow
Control Status
Feature
Default
Menu
CLI
Web
viewing port and trunk statistics for all
ports, and flow control status
n/a
page B-12
page B-13
page B-13
viewing a detailed summary for a
particular port or trunk
n/a
page B-12
page B-13
page B-13
resetting counters
n/a
page B-12
page B-13
page B-13
These features enable you to determine the traffic patterns for each port since
the last reboot or reset of the switch. You can display:
■
A general report of traffic on all LAN ports and trunk groups in the switch,
along with the per-port flow control status (On or Off).
■
A detailed summary of traffic on a selected port or trunk group.
You can also reset the counters for a specific port.
The menu interface and the web browser interface provide a dynamic display
of counters summarizing the traffic on each port. The CLI lets you see a static
“snapshot” of port or trunk group statistics at a particular moment.
As mentioned above, rebooting or resetting the switch resets the counters to
zero. You can also reset the counters to zero for the current session. This is
useful for troubleshooting. Refer to the “Note On Reset”, below.
Note on Reset
The Reset action resets the counter display to zero for the current session, but
does not affect the cumulative values in the actual hardware counters. (In
compliance with the SNMP standard, the values in the hardware counters are
not reset to zero unless you reboot the switch.) Thus, using the Reset action
resets the displayed counters to zero for the current session only. Exiting from
the console session and starting a new session restores the counter displays
to the accumulated values in the hardware counters.
B-11
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-7. Example of Port Counters on the Menu Interface
To view details about the traffic on a particular port, use the [v] key to highlight
that port number, then select Show Details. For example, selecting port A2
displays a screen similar to figure B-8, below.
Figure B-8. Example of the Display for Show details on a Selected Port
This screen also includes the Reset action for the current session. (Refer to
the “Note on Reset” on page B-11.)
B-12
Monitoring and Analyzing Switch Operation
Status and Counters Data
CLI Access To Port and Trunk Group Statistics
To Display the Port Counter Summary Report.
Syntax: show interfaces
This command provides an overview of port activity for all
ports on the switch.
To Display a Detailed Traffic Summary for Specific Ports.
Syntax: show interfaces < port-list >
This command provides traffic details for the port(s) you
specify
To Reset the Port Counters for a Specific Port.
Syntax: clear statistics < port-list >
This command resets the counters for the specified ports to zero
for the current session. (See the “Note on Reset” on page B-11.)
Web Browser Access To View Port and Trunk Group Statistics
Note
1.
Click on the Status tab.
2.
Click on [Port Counters].
3.
To refresh the counters for a specific port, click anywhere in the row for
that port, then click on [Refresh].
To reset the port counters to zero, you must reboot the switch.
B-13
Monitoring and Analyzing Switch Operation
Status and Counters Data
Viewing the Switch’s MAC Address Tables
Note
The 6120G/XG supports a maximum of 16,000 MAC address entries. The
6120XG supports a maximum of 32,000 MAC address entries.
Feature
Default
Menu
CLI
Web
viewing MAC addresses on all
ports on a specific VLAN
n/a
page B-14
page B-17
—
viewing MAC addresses on a
specific port
n/a
page B-16
page B-17
—
searching for a MAC address
n/a
page B-16
page B-17
—
These features help you to view:
■
The MAC addresses that the switch has learned from network devices
attached to the switch
■
The port on which each MAC address was learned
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 communicate with a specific device on the network. The per-VLAN listing includes:
■
The MAC addresses that the switch has learned from network devices
attached to the switch
■
The port on which each MAC address was learned
1.
From the Main Menu, select:
1. Status and Counters
5. VLAN Address Table
B-14
2.
The switch then prompts you to select a VLAN.
3.
Use the Space bar to select the VLAN you want, then press [Enter]. The
switch then displays the MAC address table for that VLAN:
Monitoring and Analyzing Switch Operation
Status and Counters Data
Figure B-9. Example of the Address Table
To page through the listing, use Next page and Prev page.
Finding the Port Connection for a Specific Device on a VLAN. This
feature uses a device’s MAC address that you enter to identify the port used
by that device.
1.
Proceeding from figure B-9, press [S] (for Search), to display the following
prompt:
Enter MAC address: _
2.
Type the MAC address you want to locate and press [Enter]. The address
and port number are highlighted if found. If the switch does not find the
MAC address on the currently selected VLAN, it leaves the MAC address
listing empty.
Located MAC
Address and
Corresponding
Port Number
Figure B-10. Example of Menu Indicating Located MAC Address
3.
Press [P] (for Prev page) to return to the full address table listing.
B-15
Monitoring and Analyzing Switch Operation
Status and Counters Data
Port-Level MAC Address Viewing and Searching. This feature displays
and searches for MAC addresses on the specified port instead of for all ports
on the switch.
1.
From the Main Menu, select:
1. Status and Counters
7. Port Address Table
Prompt for Selecting
the Port To Search
Figure B-11. Listing MAC Addresses for a Specific Port
2.
Use the Space bar to select the port you want to list or search for MAC
addresses, then press [Enter] to list the MAC addresses detected on that
port.
Determining Whether a Specific Device Is Connected to the Selected
Port. Proceeding from step 2, above:
1.
Press [S] (for Search), to display the following prompt:
Enter MAC address: _
B-16
2.
Type the MAC address you want to locate and press [Enter]. The address
is highlighted if found. If the switch does not find the address, it leaves
the MAC address listing empty.
3.
Press [P] (for Prev page) to return to the previous per-port listing.
Monitoring and Analyzing Switch Operation
Status and Counters Data
CLI Access for MAC Address Views and Searches
Syntax:
show mac-address
[ vlan < vlan-id >]
[< port-list >]
[< mac-addr >]
To List All Learned MAC Addresses on the Switch, with The Port
Number on Which Each MAC Address Was Learned.
ProCurve> show mac-address
To List All Learned MAC Addresses on one or more ports, with Their
Corresponding Port Numbers. For example, to list the learned MAC
address on ports A1 through A4 and port A6:
ProCurve> show mac-address a1-a4,a6
To List All Learned MAC Addresses on a VLAN, with Their Port
Numbers. This command lists the MAC addresses associated with the ports
for a given VLAN. For example:
ProCurve> show mac-address vlan 100
Note
The switches covered in this guide operate with a multiple forwarding database
architecture.
To Find the Port On Which the Switch Learned a Specific MAC
Address. For example, to find the port on which the switch learns a MAC
address of 080009-21ae84:
B-17
Monitoring and Analyzing Switch Operation
Status and Counters Data
Spanning Tree Protocol (MSTP) Information
CLI Access to MSTP Data
This option lists the MSTP configuration, root data, and per-port data (cost,
priority, state, and designated bridge).
Syntax: show spanning-tree
This command displays the switch’s global and regional
spanning-tree status, plus the per-port spanning-tree
operation at the regional level. Note that values for the
following parameters appear only for ports connected to active
devices: Designated Bridge, Hello Time, PtP, and Edge.
Figure B-12. Output from show spanning-tree Command
B-18
Monitoring and Analyzing Switch Operation
Status and Counters Data
Internet Group Management Protocol (IGMP) Status
The switch uses the CLI to display the following IGMP status on a per-VLAN
basis:
Show Command
Output
show ip igmp
Global command listing IGMP status for all VLANs configured
in the switch:
• VLAN ID (VID) and name
• Active group addresses per VLAN
• Number of report and query packets per group
• Querier access port per VLAN
show ip igmp <vlan-id>
Per-VLAN command listing above IGMP status for specified
VLAN (VID)
show ip igmp group <ip-addr> Lists the ports currently participating in the specified group,
with port type, Access type, Age Timer data and Leave Timer
data.
For example, suppose that show ip igmp listed an IGMP group address of
224.0.1.22. You could get additional data on that group by executing the
following:
Figure B-13. Example of IGMP Group Data
B-19
Monitoring and Analyzing Switch Operation
Status and Counters Data
VLAN Information
The switch uses the CLI to display the following VLAN status:
Note
The 6120G/XG supports a maximum of 256 VLANs. The 6120XG supports a
maximum of 1,024 VLANs.
Show Command
Output
show vlan
Lists:
• Maximum number of VLANs to support
• Existing VLANs
• Status (static or dynamic)
• Primary VLAN
show vlan <vlan-id>
For the specified VLAN, lists:
• Name, VID, and status (static/dynamic)
• Per-Port mode (tagged, untagged, forbid, no/auto)
• “Unknown VLAN” setting (Learn, Block, Disable)
• Port status (up/down)
For example, suppose that your switch has the following VLANs:
PortsVLANVID
A1 - A12DEFAULT_VLAN 1
A1, A2VLAN-33 33
A3, A4VLAN-44 44
The next three figures show how you could list data on the above VLANs.
Listing the VLAN ID (VID) and Status for ALL VLANs in the Switch.
B-20
Monitoring and Analyzing Switch Operation
Status and Counters Data
Figure B-14. Example of VLAN Listing for the Entire Switch
Listing the VLAN ID (VID) and Status for Specific Ports.
Because ports A1
and A2 are not
members of VLAN44, it does not appear
in this listing.
Figure B-15. Example of VLAN Listing for Specific Ports
Listing Individual VLAN Status.
Figure B-16. Example of Port Listing for an Individual VLAN
B-21
Monitoring and Analyzing Switch Operation
Status and Counters Data
Web Browser Interface Status Information
The “home” screen for the web browser interface is the Status Overview
screen, as shown below. As the title implies, it provides an overview of the
status of the switch, including summary graphs indicating the network utilization on each of the switch ports, symbolic port status indicators, and the
Alert Log, which informs you of any problems that may have occurred on the
switch.
For more information on this screen, refer to the chapter titled “Using the
ProCurve Web Browser Interface”.
Figure B-17. Example of a Web Browser Interface Status Overview Screen
B-22
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Traffic Mirroring
Mirror Features
Feature
Mirror CLI Quick Reference
Default
n/a
Menu
CLI
n/a
B-34
Configure Mirror Source
disabled
page B-29 page B-35
Configure Mirror Destination at Source
disabled
page B-29 page B-35
n/a
page B-29 page B-38
Display Mirror Configuration
Traffic mirroring (Intelligent Mirroring) allows you to mirror (send a copy of)
network traffic received or transmitted on a switch interface to a local
destination, such as a traffic analyzer or intrusion detection system (IDS).
Traffic mirroring provides the following benefits:
■
Allows you to monitor the traffic flow on specific source interfaces
■
Helps in analyzing and debugging problems in network operation resulting from a misbehaving network or an individual client. The mirroring of
selected traffic to an external device makes it easier to diagnose a network
problem from a centralized location in a topology spread across a campus.
Mirroring destinations. Traffic mirroring supports destination devices
that are connected to the local switch:
■
Configuration
Notes
Traffic can be copied to a destination connected to the same switch as the
mirroring source in a local mirroring session. Up to four local mirroring
destinations are supported on a switch.
Using the CLI, you can make full use of the switch’s local mirroring capabilities. Using the Menu interface, you can configure only local mirroring for a
group of ports and/or static trunks.
Only a single mirror port session is supported.
Mirrored frames exceeding the allowed maximum transmission unit (MTU)
size will be dropped. Also, the switch applies a 54-byte IPv4 header to mirrored
frames. For more information, including the size limitation for jumbo and nonjumbo frames, see “Maximum Supported Frame Size” on page B-42.
Selecting mirrored traffic. You can use any of the following options to
select the traffic to be mirrored on a port or trunk interface in a local session:
B-23
Monitoring and Analyzing Switch Operation
Traffic Mirroring
■
All traffic: Monitors all traffic entering or leaving the switch on one or
more interfaces (inbound and outbound).
Mirroring Terminology
Figure B-18 shows an example of the terms used to describe the configuration
of a sample local mirroring session:
■
In the local session, inbound traffic entering Switch A is monitored on
port C2 and mirrored to a destination (host), traffic analyzer 1, through
exit port A15 on the switch.
A local mirroring session means that the monitored interface (C2) and
exit port (A15) are on the same switch.
Switch A
C1
VLAN 20
Network
C2
A15
Traffic
Analyzer 1
Local mirroring session:
Source Switch: Switch A
Monitored interface: Port C2
Exit port: A15
Destination/Host: Traffic analyzer 1
Figure B-18. Local Session Showing Mirroring Terms
Exit Port: The port to which a traffic analyzer or IDS is connected to receive
mirrored traffic:
- For local mirroring, an exit port can be any port to which a traffic
analyzer or IDS is connected and that is not configured as a monitored
interface. Up to four sessions can be assigned to the same exit port used
for local mirroring. An exit port is configured on the local switch with the
command: mirror eth-port < exit-port >
B-24
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Caution
An exit port should be connected only to a network analyzer, IDS, or other
network edge device that has no connection to other network resources.
Connecting a mirroring exit port to a network can result in serious
network performance problems, and is strongly discouraged by ProCurve
Networking.
Host: Used in this chapter to refer to a traffic analyzer or intrusion detection
system (IDS).
IDS: Intrusion Detection System.
Local Mirroring: The monitored (source) interface and exit port in a mirroring session are on the same switch.
Monitored Interface: The interface (port or trunk) on the source switch on
which the inbound and/or outbound traffic to be mirrored originates,
configured with one of the interface monitor or vlan monitor commands (see
“3. Configure the Monitored Traffic in a Mirror Session” on page B-35).
Source Switch: The source switch on which the inbound and/or outbound
traffic to be mirrored originates. See also Monitored Interface.
B-25
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Mirrored Traffic Destinations
Local Destinations
A local mirrored traffic destination is a port on the same switch as the source
of the traffic being mirrored.
Caution
Configuring a mirroring source switch with the destination and traffic selection criteria for a given mirroring session causes the switch to immediately
begin mirroring traffic to that destination.
Monitored Traffic Sources
You can configure mirroring for traffic entering or leaving the switch on:
■
Ports and static trunks: Provides the flexibility for mirroring on individual ports, groups of ports, and/or static port trunks.
Criteria for Selecting Mirrored Traffic
On the monitored sources listed above, you can configure the following
criteria to select the traffic you want to mirror:
■
Direction of traffic movement (entering or leaving the switch, or both)
■
Source and/or destination MAC addresses in packet headers
Mirroring Sessions
A mirroring session consists of a mirroring source and destination. A mirroring
source can be a port or static-trunk list. For any session, the destination must
be a single (exit) port.
Multiple mirroring sessions can be mapped to the same exit port, which
provides flexibility in distributing hosts such as traffic analyzers or an IDS.
Mirroring sessions can have the same or a different destination. You can
configure an exit port on the local (source) switch as the destination in a
mirroring session. When configuring a mirroring destination, take into
account the following options:
B-26
■
Mirrored traffic belonging to different sessions can be directed to the
same destination or to different destinations.
■
You can reduce the risk of oversubscribing a single exit port by directing
traffic from different session sources to different exit ports.
■
You can segregate traffic by type, direction, or source.
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Mirroring Configuration
Table B-1 shows the different types of mirroring that you can configure using
the CLI, Menu, and SNMP interfaces.
Table B-1.
Mirroring Configuration Options
Monitoring
Interface and
Configuration
Level
Traffic Selection
Criteria
Port(s)
Trunk(s)
All traffic
Switch
(global)
Traffic Direction
CLI Config
Menu and Web SNMP Config
I/F Config1
Inbound only
Outbound only
Both directions
All traffic
(inbound and
outbound
combined)
Inbound only
Outbound only
Both directions
Classifier-based
Inbound only
policy (IPv4 or IPv6
traffic)
Not available
Not available
MAC source/
destination
address
Not available
Inbound only
Outbound only
Both directions
Inbound only
Outbound only
Both directions
1Configures only session 1, and only for local mirroring.
B-27
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Configuration
Notes
Using the CLI, you can configure all mirroring options on a switch.
Using the Menu or Web interface, you can configure session 1 local mirroring
for traffic in both directions on specified interfaces. (If session 1 has been
already configured in the CLI for local mirroring for inbound-only or outbound-only traffic and you use the Menu or Web interface to modify the
session 1 configuration, session 1 is automatically reconfigured to monitor
both inbound and outbound traffic on the assigned interfaces. If session 1 has
been configured in the CLI with a classifier-based mirroring policy, an error
message is displayed if you try to use the Menu or Web interface to configure
the session.)
You can use the CLI to configure sessions 1 to 4 for local mirroring in any
combination, and override a Menu or Web interface-based configuration of
session 1.
You can also use SNMP to configure sessions 1 to 4 for local mirroring in any
combination, and override a Menu or Web interface-based configuration of
session 1, except that SNMP cannot be used to configure a classifier-based
mirroring policy.
Endpoint Switches and Intermediate Devices
The following restrictions apply to endpoint switches and intermediate
devices in a network configured for traffic mirroring:
B-28
■
The exit port for a mirroring destination must be an individual port, and
not a trunk, mesh or VLAN interface.
■
The switch mirrors traffic on static trunks, but not on dynamic LACP
trunks.
■
The switch mirrors traffic at line rate. When mirroring multiple interfaces
in networks with high traffic levels, it is possible to copy more traffic to
a mirroring destination than the link supports. In this case, some mirrored
traffic may not reach the destination. If you are mirroring a high traffic
volume, distribute the load to multiple exit ports if possible.
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Using the Menu or Web Interface To Configure Local
Mirroring
Menu and Web Interface Limits
The Menu and Web interfaces can be used to quickly configure or reconfigure
local mirroring on session 1, and allow the following mirroring source option:
■
any combination of source port(s), and/or trunk(s)
The Menu and Web interfaces also have these limits:
■
Configure and display session 1 as a local mirroring session for traffic in
both directions on the specified interface. (Selecting inbound-only or
outbound-only is not an option.)
■
If session 1 has been configured in the CLI for local mirroring for inboundonly or outbound-only traffic on one or more interfaces, then using the
Menu or Web interface to change the session 1 configuration automatically reconfigures the session to monitor both inbound and outbound
traffic on the designated interface(s).
■
The CLI (and SNMP) can be used to override any Menu or Web interface
configuration of session 1.
B-29
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Configuration Steps
Notes
If mirroring has already been enabled on the switch, the Menu screens will
appear differently than shown in this section.
1.
From the Main Menu, select:
2. Switch Configuration...
3. Network Monitoring Port
Switch Configuration - Network Monitoring Port
Monitoring Enabled [No] : No
Actions->
Cancel
Edit
Enable mirroring by
setting this parameter
to “Yes”.
Save
Help
Select whether to enable traffic monitoring.
Use arrow keys to change field selection, <Space> to toggle field choices,
and <Enter> to go to Actions.
Figure B-19. The Default Network Mirroring Configuration Screen
B-30
2.
In the Actions menu, press [E] (for Edit).
3.
If mirroring is currently disabled for session 1 (the default), then enable
it by pressing the Space bar (or [Y]) to select Yes.
4.
Press the down arrow key to display a screen similar to the following and
move the cursor to the Monitoring Port parameter.
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Switch Configuration - Network Monitoring Port
Move the cursor to the Monitoring Port parameter,
then use the Space bar to select the local exit port.
Monitoring Enabled [No] : Yes
Monitoring Port : D5
Monitor : Ports
Port
---D1
D2
D3
D4
D5
D6
D7
D8
Type
--------1000X
1000X
1000X
1000X
1000X
1000X
1000X
1000X
Actions->
Action
+ ------|
|
|
|
|
|
|
|
Cancel
Edit
|
|
|
|
|
|
|
|
|
|
Port
---D14
D15
D16
1
2
3
4
S1
Type
--------1000X
1000X
1000X
1000T
1000T
1000T
1000T
Save
Help
Action
+ ------|
|
|
|
|
|
|
|
Select the port that will act as the Monitoring Port.
Use arrow keys to change field selection, <Space> to toggle field choices,
and <Enter> to go to Actions.
Figure B-20. How To Select a Local Exit Port
5.
Use the Space bar to select the port to use for sending mirrored traffic to
a locally connected traffic analyzer or IDS. (The selected interface must
be a single port. It cannot be a trunk.) In this example, port D5 is selected
as the local exit port.
6.
Highlight the Monitor field and use the Space bar to select the interfaces
to mirror:
Ports: Use for mirroring ports, or static trunks.
7.
Use the down arrow key to move the cursor to the Action column for the
individual port interfaces and position the cursor at a port, or trunk you
want to mirror.
B-31
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Switch Configuration - Network Monitoring Port
Monitoring Enabled [No] : Yes
Monitoring Port : D5
Monitor : Ports
Port
---D1
D2
D3
D4
D5
D6
D7
D8
Type
--------1000X
1000X
1000X
1000X
1000X
1000X
1000X
1000X
Actions->
Action
+ ------|
|
|
|
|
|
|
|
Cancel
Edit
|
|
|
|
|
|
|
|
|
|
Use the down arrow key to select the interface(s)
whose traffic you want to mirror to the local exit port.
Port
---D14
D15
D16
1
2
3
4
S1
Type
--------1000X
1000X
1000X
1000T
1000T
1000T
1000T
Save
Help
Action
+ ------|
|
|
|
|
|
|
|
Select whether to monitor the selected port.
Use arrow keys to change field selection, <Space> to toggle field choices,
and <Enter> to go to Actions.
8.
Press the Space bar to select Monitor for the port(s) and/or trunk(s) that
you want mirrored. Use the down arrow key to move from one interface
to the next in the Action column. (If any trunks are configured, they will
appear at the end of the port listing.)
9.
When you finish selecting interfaces to mirror, press [Enter], then press [S]
(for Save) to save your changes and exit from the screen.
10. Return to the Main Menu.
B-32
Monitoring and Analyzing Switch Operation
Traffic Mirroring
CLI: Configuring Local Mirroring
Command
Page
Quick Reference
Local Mirroring Commands
B-34
Configuring a Local Mirroring Destination
On the local switch: mirror < session > port < exit-port >
B-35
Configuring Monitored Traffic1
interface < port/trunk >
monitor
B-36
Display Commands
show monitor
B-38
Mirroring Examples
B-41
Maximum Frame Size
B-42
Operating Notes
B-45
Using the CLI, you can configure a mirroring session for a destination device
connected to an exit port on the same switch as the source interface (local
mirroring).
For an overview of the procedures for configuring a local mirroring session,
refer to the following section:
■
“Local Mirroring Overview” on page B-33
For a detailed description of each step in a mirroring configuration, refer to:
“1. Determine the Mirroring Session and Destination” on page B-35
“2. Configure a Mirroring Session on the Source Switch” on page B-35
“3. Configure the Monitored Traffic in a Mirror Session” on page B-35:
•
Caution
“Selecting All Inbound/Outbound Traffic to Mirror” on page B-36
Configuring a switch with the destination and traffic-selection criteria for a
mirroring session causes the switch to immediately begin mirroring traffic to
that destination.
Local Mirroring Overview
To configure a local mirroring session in which the mirroring source and
destination are on the same switch, follow these general steps:
B-33
Monitoring and Analyzing Switch Operation
Traffic Mirroring
1.
Determine the session and local destination port:
•
Session number (1-4) and (optional) alphanumeric name
•
Exit port (any port on the switch except a monitored interface used
to mirror traffic)
2.
Enter the mirror < session-# > [ name < session-name >] port < port-# >
command to configure the session.
3.
Determine the traffic direction and traffic to be selected by any of the
following methods and the appropriate configuration level (port, trunk,
switch):
– Direction: inbound, outbound, or both
– Classifier-based mirroring policy: inbound only for IPv4 or IPv6
traffic
– MAC source and/or destination address: inbound, outbound, or
both
4.
Enter the monitor command to assign one or more source interfaces to the
session.
After you complete step 4, the switch begins mirroring traffic to the configured
exit port. The next two sections provide a quick reference to the configuration
commands for a local mirroring session.
Quick Reference to Local Mirroring Set-Up. The following commands
configure mirroring for a local session in which the mirroring source and
destination are on the same switch. For command syntax details, refer to the
pages listed with each heading.
■
The mirror command identifies the destination in a mirroring session.
■
The interface and vlan commands identify the mirroring source, including
source interface, traffic direction, and traffic-selection criteria for a specified session.
Configure a Local Mirroring Session (Page B-35):
Mirror-Session Number, Local Exit Port, and (Optional) Session Name
[no] mirror < 1 - 4 > port < exit-port-# > [ name < name-str >]
The no mirror <session-#> command removes the mirroring session and any
mirroring source previously assigned to that session by the following commands.
Configure Traffic-Direction Criteria to Select Traffic (Page B-36):
[no] < interface < port/trunk/mesh > | vlan < vid-# >>
monitor all < in | out | both > mirror < session > [< session > ... ] [no-tag-added]
B-34
Monitoring and Analyzing Switch Operation
Traffic Mirroring
1. Determine the Mirroring Session and Destination
For a Local Mirroring Session. Determine the port number for the exit
port (such as A5, B10, etc.), then go to “3. Configure the Monitored Traffic in
a Mirror Session” on page B-35.
2. Configure a Mirroring Session on the Source Switch
To configure local mirroring, only a session number and exit port number are
required. See “Configuring a Source Switch in a Local Mirroring Session”
below for more information.
Configuring a Source Switch in a Local Mirroring Session. For a local
mirroring session, enter the mirror port command on the source switch to
configure an exit port on the same switch. To create the mirroring session,
use the information gathered in “1. Determine the Mirroring Session and
Destination” on page B-35.
Syntax: mirror eth-port
This command assigns the exit port to use for the specified
mirroring session, and must be executed from the global
configuration level.
The no form of the command removes the mirroring session
and any mirroring source previously assigned to that
session. To preserve the session while deleting a mirroring
source assigned to it, refer to the no command descriptions
under “3. Configure the Monitored Traffic in a Mirror
Session” on page B-35.
Caution
Configuring a switch with the traffic selection criteria and destination for a
given mirroring session starts traffic mirroring to that destination.
3. Configure the Monitored Traffic in a Mirror Session
This step configures one or more interfaces on a source switch with the trafficselection criteria to use to select the traffic to mirror in a specified session
configured in Step 3.
B-35
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Traffic Selection Options
To configure traffic mirroring, you must specify the source interface, traffic
direction, and criteria to be used to select the traffic to be mirrored using the
following options:
■
Interface type
•
Port and/or trunk
•
Switch (global configuration level)
Mirroring-Source Restrictions
In a mirroring session, you can configure any of the following sources of
mirrored traffic:
■
Multiple port and trunk interfaces
Selecting All Inbound/Outbound Traffic to Mirror
Use the commands in this section to configure all inbound and/or outbound
traffic on specified port or trunk interfaces for a local mirroring session. For
an example of a mirroring configuration that selects all inbound or outbound
traffic on a monitored interface, see:
■
Note
“Local Mirroring Using Traffic-Direction Criteria” on page B-41
If you have already configured session 1 with a local destination (as described
in “2. Configure a Mirroring Session on the Source Switch” on page B-35), you
can enter the vlan < vid > monitor or interface < port > monitor command without
additional parameters for traffic-selection criteria and session number to
configure mirroring for all inbound and outbound traffic on the specified port
interfaces in session 1 with the preconfigured destination.
Port or Trunk Interface with Traffic Direction as the Selection
Criteria. Use this command when the direction of traffic movement on the
port or trunk interface defines the criteria for mirroring traffic.
Syntax: [no] interface < eth-port-list > monitor all < in | out | both >
B-36
Monitoring and Analyzing Switch Operation
Traffic Mirroring
This command assigns a mirroring source to a previously
configured mirroring session on a source switch. It specifies the
port and/or trunk source(s) to use, the direction of traffic to
mirror, and the session identifier.
The no form of the command removes a mirroring source
assigned to the session, but does not remove the session itself.
This enables you to repurpose a session by removing an
unwanted mirroring source and adding another in its place.
interface < eth-port-list >: Identifies the port(s) or static
trunk(s), on which to mirror traffic. Use a hyphen for a
range of consecutive ports (d5-d8). Use a comma to
separate non-contiguous interfaces (d5,d8).
monitor all < in | out | both >: For the interface specified by
< port-list >, selects traffic to mirror based on whether the
traffic is entering or leaving the switch on the interface.
in: Mirror entering traffic.
out: Mirror exiting traffic.
both: Mirror traffic entering or exiting.
(Using monitor without mirroring criteria or session
number affects session 1. Refer to “Monitor Command” on
page B-46.)
B-37
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Displaying a Mirroring Configuration
Displaying the Mirroring Configuration Summary
Use the show monitor command to display information on the currently configured status, traffic-selection criteria, and number of monitored interfaces
in each mirroring session on a switch.
Local Mirroring Source:
• Session 1 is performing local mirroring using a
classifier-based policy for traffic-selection
criteria.
• Sessions 2, 3, and 4 are not configured.
ProCurve# show monitor
Network Monitoring
Sessions
-------1
2
3
4
Status
----------active
not defined
not defined
not defined
Type
----port
Sources
------1
Policy
----yes
Figure B-21. Example of a Currently Configured Mirroring Summary on a Source Switch
Syntax: show monitor
If a remote mirroring source is configured on the switch, then the
following fields appear. Otherwise, the output displays this
message: Mirroring is currently disabled.
Sessions: Lists the four configurable sessions on the switch.
Status: Displays the current status of each session:
active: The session is configured.
inactive: The session is partially configured. Only the
destination has been configured; the mirroring source is
not configured.
not defined: Mirroring is not configured for this session.
Type: Indicates whether the mirroring session is local (port) or
MAC-based (mac) for local sessions.
Sources: Indicates how many mirroring sources are using each
mirroring session.
B-38
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Syntax: show monitor
Policy: Indicates whether the source is using a classifier-based
mirroring policy to select inbound IPv4 or IPv6 traffic for
mirroring.
B-39
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Viewing Mirroring in the Current Configuration File
Using the show run command, you can view the current mirroring configuration on the switch.
Source mirroring session entries begin with the mirror keyword and the
mirroring sources are listed per-interface. For example:
ProCurve(config)# show run
Running configuration:
; 498358-B21 Configuration Editor; Created on release #Z.14.04
max-vlans 300
ip access-list extended "100"
10 permit icmp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 0
exit
no ip address
Mirroring configured on port B3
exit
. . .
mirror 1 port B3
interface B3
monitor ip access-group "100" In mirror 1
monitor all Both mirror 2
exit
. . .
Selection criteria used to
monitor traffic on port B3
Figure B-22. Example of Using the Configuration File to View Mirroring Configurations
Destination mirroring session entries begin with mirror endpoint. In the following example, two sessions are using the same exit port:
ProCurve(config)# show run
Running configuration:
; 498358-B21 Configuration Editor; Created on release #Z.14.04
module 3 type J8694A
Remote destination and exit port configured for two
source switches using the same UDP port number
. . .
mirror endpoint ip 10.10.20.1 8010 10.10.30.2 port 4
mirror endpoint ip 10.10.51.10 7955 10.10.30.2 port 4
. . .
Figure B-23. Example of Using the Configuration File to View Mirroring Destination
B-40
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Mirroring Configuration Examples
Local Mirroring Using Traffic-Direction Criteria
Example of Local Mirroring Configuration. An administrator wants to
mirror the inbound traffic from workstation “X” on port A5 and workstation
“Y” on port B17 to a traffic analyzer connected to port C24. In this case, the
administrator chooses “1” as the session number. (Any unused session number
from 1 to 4 is valid.) Since the switch provides both the source and destination
for the traffic to monitor, local mirroring can be configured. In this case, the
command sequence is:
1.
Configure the local mirroring session.
2.
Assign a mirroring source to the session.
X
A5
Switch
C24
Traffic
Analyzer
B17
Y
Figure B-24. Example of a Local Mirroring Topology
Configures port C24 as the mirroring
destination (exit port) for session 1.
ProCurve(config)# mirror eth-port
Caution: Please configure destination switch first.
Do you want to continue [y/n]? y
ProCurve(config)# interface a5,b17 monitor all in mirror 1
Reminder to configure mirroring
destination before configuring
source.
Mirrors all inbound and outbound traffic on ports A5
and B17 to the mirroring destination configured for
session 1.
Figure B-25. Example of Configuring Local Mirroring of All Inbound and Outbound Traffic
B-41
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Maximum Supported Frame Size
The IPv4 encapsulation of mirrored traffic adds a 54-byte header to each
mirrored frame. If a resulting frame exceeds the MTU (Maximum Transmission Unit) allowed in the network, the frame is dropped.
Note
Mirroring does not truncate frames, and oversized mirroring frames will be
dropped.
If jumbo frames are enabled on the mirroring source switch, then the mirroring
destination switch and all downstream devices connecting the source switch
to the mirroring destination must be configured to support jumbo frames.
B-42
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Enabling Jumbo Frames To Increase Mirroring Path MTU
On 1 Gbps and 10 Gbps ports in the mirroring path, you can reduce the number
of dropped frames by enabling jumbo frames on all intermediate switches and
routers. (The maximum transmission unit—MTU—on the switches covered
by this manual is 9220 bytes for frames having an 802.1Q VLAN tag, and 9216
bytes for untagged frames.) For information on configuring the switch for
jumbo frames, refer to “Configuring Jumbo Frame Operation” on page 12-4.
Table B-2.
Maximum Frame Sizes for Mirroring
Tagged
Untagged
Frame Type
Configuration
Maximum VLAN Frame Mirrored
Frame
Tag
to Local Port
Size
Data
Non-Jumbo
(default config.)
1518
0
1518
Jumbo1 on All VLANs
9216
0
9216
Jumbo1 On All But
Source VLAN
1518
0
n/a2
Non-Jumbo
1522
4
1522
Jumbo1 on All VLANs
9220
4
9218
Jumbo1 On All But
Source VLAN
1522
4
n/a2
1Jumbo frames are allowed on ports operating at or above 1 Gbps.
2For local mirroring, a non-Jumbo configuration on the source
VLAN dictates an MTU of 1518 bytes for untagged frames, and an
MTU of 1522 for tagged frames, regardless of the Jumbo
configuration on any other VLANs on the switch.
B-43
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Effect of Downstream VLAN Tagging on
Untagged, Mirrored Traffic
In a mirroring application, if mirrored traffic leaves the switch without 802.1Q
VLAN tagging, but is forwarded through a downstream device that adds 802.1Q
VLAN tags, then the MTU for untagged, mirrored frames leaving the source
switch is reduced below the values shown in table B-2. That is, if the MTU on
the path to the destination is 1522 bytes, then untagged, mirrored frames
leaving the source switch cannot exceed 1518 bytes. If the MTU on the path
to the destination is 9220 bytes, then untagged, mirrored frames leaving the
source switch cannot exceed 9216 bytes.
Tagged 10 Gbps VLAN link.
Adds 4 bytes to each frame.
Switch
(Aggregator)
Router in the
Mirror Path
1Gbps
Switch
(Remote
Mirror
Destination)
Untagged 1 Gbps
VLAN Links
Switch
Switch
(Mirror Source)
(Mirror Source)
Traffic
Analyzer
Due to VLAN tagging on the 10 Gbps link,
untagged traffic from the mirror sources must
be at least 4 bytes smaller than the MTU for
the path to the mirror destination.
Figure B-26. Effect of Downstream VLAN Tagging on the MTU for Mirrored Traffic
B-44
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Operating Notes
■
Mirroring Dropped Traffic: Where an interface is configured to mirroring traffic to a destination, it does so regardless of whether the traffic is
dropped while on the interface.
■
Mirroring and Spanning Tree: Mirroring is done regardless of the
spanning-tree (STP) state of a port or trunk. This means, for example, that
inbound traffic on a port blocked by STP can still be monitored for STP
protocol packets during the STP setup phase.
■
Tagged and Untagged Frames: For a frame entering or leaving the
switch on a mirrored port, the mirrored copy retains the tagged or
untagged state the original frame carried when it entered into or exited
from the switch. (The tagged or untagged VLAN membership of ports in
the path leading to the mirroring destination does not affect the tagged or
untagged status of the mirrored copy itself.) Thus, if a tagged frame arrives
on a mirrored port, the mirrored copy will also be tagged, regardless of
the status of ports in the destination path. If a frame exits from the switch
on a mirrored port that is a tagged member of a VLAN, then the mirrored
copy will also be tagged for the same reason.
■
Effect of IGMP on Mirroring: If both inbound and outbound mirroring
is operating when IGMP is enabled on any VLAN, two copies of mirrored
IGMP frames may appear at the mirroring destination.
■
Mirrored Traffic Not Encrypted: Mirrored traffic undergoes IPv4
encapsulation, but mirrored, encapsulated traffic is not encrypted.
■
IPv4 Header Added: The IPv4 encapsulation of mirrored traffic adds a
54-byte header to each mirrored frame. If a resulting frame exceeds the
maximum MTU allowed in the network, it will be dropped. To reduce the
number of dropped frames, enable jumbo frames in the mirroring path,
including all intermediate switches and/or routers. (The maximum transmission unit—MTU—on the switch is 9220 bytes, which includes 4 bytes
for the 802.1Q VLAN tag.) For more information, refer to “Maximum
Supported Frame Size” on page B-42. To configure the switch for jumbo
frames, refer to “Configuring Jumbo Frame Operation” on page 12-4.
■
Intercepted or Injected Traffic: The mirroring feature does not protect
against either mirrored traffic being intercepted or traffic being injected
into a mirrored stream by an intermediate host.
■
Inbound Mirrored IPv4-Encapsulated Frames are Not Mirrored:
The switch does not mirror IPv4-encapsulated mirrored frames that it
receives on an interface. This prevents duplicate mirrored frames in
configurations where the port connecting the switch to the network path
for mirroring to a destination is also a port whose inbound or outbound
traffic is being mirrored. For example, if traffic leaving the switch through
B-45
Monitoring and Analyzing Switch Operation
Traffic Mirroring
ports B5, B6, and B7 is being mirrored through port B7 to a network
analyzer, the mirrored frames from traffic on ports B5 and B6 will not be
mirrored a second time as they pass through port B7.
B-46
■
Switch Operation as Both Destination and Source: A switch configured as remote destination switch can also be configured to mirror traffic
to one of its own ports (local mirroring).
■
Monitor Command Note: If session 1 is already configured with a
destination, you can execute [no] vlan < vid > monitor or [no] interface
< port > monitor without mirroring criteria and a mirror session number. In
this case, the switch automatically configures or removes mirroring for
inbound and outbound traffic from the specified VLAN or port(s) to the
destination configured for session 1.
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Troubleshooting Mirroring
Mirrored traffic does not reach configured remote destination switch or
remote exit port.
Caution
•
For a given mirroring session, the mirror command parameters configured on the source switch for source IP address, source UDP port,
and destination IP address must be identical to their counterparts in
the mirror endpoint command configured on the destination switch.
•
The configured exit port must not be a member of a trunk.
•
If the destination for mirrored traffic is on a different VLAN than the
source, routing must be correctly configured along the path from the
source to the destination.
•
On the destination switch for a given mirroring session, both the port
on which the mirrored traffic enters the switch and the exit port must
be members of the same VLAN.
•
All links on the path from the source switch to the destination switch
must be active.
A mirroring exit port should be connected only to a network analyzer, IDS, or
other network edge device that has no connection to other network resources.
Allowing a mirroring exit port connection to a network can result in serious
network performance problems, and is strongly discouraged by ProCurve
Networking.
B-47
C
Troubleshooting
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Troubleshooting Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Browser or Telnet Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Unusual Network Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
802.1Q Prioritization Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
IGMP-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
LACP-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Port-Based Access Control (802.1X)-Related Problems . . . . . . . . . C-11
QoS-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Radius-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Spanning-Tree Protocol (MSTP) and Fast-Uplink Problems . . . . . . C-16
SSH-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
TACACS-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
TimeP, SNTP, or Gateway Problems . . . . . . . . . . . . . . . . . . . . . . . . . C-21
VLAN-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Using the Event Log for Troubleshooting Switch Problems . . . . C-24
Event Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Menu: Displaying and Navigating in the Event Log . . . . . . . . . . . . . C-31
CLI: Displaying the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32
CLI: Clearing Event Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32
CLI: Turning Event Numbering On . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33
C-1
Troubleshooting
Contents
Using Log Throttling to Reduce Duplicate
Event Log and SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33
Log Throttle Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
Example of Log Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
Example of Event Counter Operation . . . . . . . . . . . . . . . . . . . . . C-36
Debug/Syslog Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Destination Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . C-37
Debug/Syslog Configuration Commands . . . . . . . . . . . . . . . . . . . . . . C-38
Configuring Debug/Syslog Operation . . . . . . . . . . . . . . . . . . . . . . . . . C-39
Displaying a Debug/Syslog Configuration . . . . . . . . . . . . . . . . . . C-41
Debug Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-45
Debug Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-45
Debug Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-47
Logging Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-49
Configuring a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-50
Adding a Description for a Syslog Server . . . . . . . . . . . . . . . . . . . . . . C-52
Adding a Priority Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-53
Configuring the Severity Level for Event Log Messages
Sent to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-54
Configuring the System Module Used to Select the Event Log
Messages Sent to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . C-55
Operating Notes for Debug and Syslog . . . . . . . . . . . . . . . . . . . . . . . C-55
Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-57
Port Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-58
Ping and Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-58
Web: Executing Ping or Link Tests . . . . . . . . . . . . . . . . . . . . . . . C-59
CLI: Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-60
Link Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-61
Traceroute Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-62
Viewing Switch Configuration and Operation . . . . . . . . . . . . . . . . . C-66
CLI: Viewing the Startup or Running Configuration File . . . . . . . . . C-66
Web: Viewing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . C-66
CLI: Viewing a Summary of Switch Operational Data . . . . . . . . . . . C-66
Saving show tech Command Output to a Text File . . . . . . . . . . C-68
C-2
Troubleshooting
Contents
Customizing show tech Command Output . . . . . . . . . . . . . . . . . C-69
CLI: Viewing More Information on Switch Operation . . . . . . . . . . . C-72
Pattern Matching When Using the Show Command . . . . . . . . . C-73
CLI: Useful Commands for Troubleshooting Sessions . . . . . . . . . . . C-76
Restoring the Factory-Default Configuration . . . . . . . . . . . . . . . . . C-77
CLI: Resetting to the Factory-Default Configuration . . . . . . . . . . . . C-77
Clear/Reset: Resetting to the Factory-Default Configuration . . . . . C-77
Restoring a Flash Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-78
DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-80
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-80
Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-81
Configuring and Using DNS Resolution with
DNS-Compatible Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-82
Configuring a DNS Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-83
Example Using DNS Names with Ping and Traceroute . . . . . . . . . . C-84
Viewing the Current DNS Configuration . . . . . . . . . . . . . . . . . . . . . . C-86
Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-87
Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-88
C-3
Troubleshooting
Overview
Overview
This appendix addresses performance-related network problems that can be
caused by topology, switch configuration, and the effects of other devices or
their configurations on switch operation. (For switch-specific information on
hardware problems indicated by LED behavior, cabling requirements, and
other potential hardware-related problems, refer to the Installation and
Getting Started Guide you received with the switch.)
Note
ProCurve periodically places switch software updates on the ProCurve
Networking web site. ProCurve recommends that you check this web site for
software updates that may have fixed a problem you are experiencing.
For information on support and warranty provisions, refer to the Support and
Warranty booklet shipped with the switch.
C-4
Troubleshooting
Troubleshooting Approaches
Troubleshooting Approaches
Use these approaches to diagnose switch problems:
■
Check the HP support web site for software updates that may have solved
your problem: www.hp.com/#support
■
Check the switch LEDs for indications of proper switch operation:
•
Each switch port has a Link LED that should light whenever an active
network device is connected to the port.
•
Problems with the switch hardware and software are indicated by
flashing the Fault and other switch LEDs.
Refer to the Installation and Getting Started Guide for a description
of the LED behavior and information on using the LEDs for troubleshooting.
■
Check the network topology/installation. Refer to the Installation and
Getting Started Guide for topology information.
■
Check cables for damage, correct type, and proper connections. You
should also use a cable tester to check your cables for compliance to the
relevant IEEE 802.3 specification. Refer to the Installation and Getting
Started Guide for correct cable types and connector pin-outs.
■
Use the Port Utilization Graph and Alert Log in the web browser interface
included in the switch to help isolate problems. Refer to Chapter 5, “Using
the ProCurve Web Browser Interface” for operating information. These
tools are available through the web browser interface:
■
•
Port Utilization Graph
•
Alert Log
•
Port Status and Port Counters screens
•
Diagnostic tools (Link test, Ping test, configuration file browser)
For help in isolating problems, use the easy-to-access switch console built
into the switch or Telnet to the switch console. Refer to chapters 3 and 4
for operating information on the Menu and CLI interfaces included in the
console. These tools are available through the switch console
•
Status and Counters screens
•
Event Log
•
Diagnostics tools (Link test, Ping test, configuration file browser, and
advanced user commands)
C-5
Troubleshooting
Troubleshooting Approaches
■
C-6
For the downlink and ISL ports, troubleshooting can be done from the OA
Web interface. These ports are controlled from both the OA and the switch
configuration. A port state is a combination of OA Enable/Disable state
and the switch Enable/Disable state. The port is not Enabled until both
the OA and the switch agree that it is Enabled.
Troubleshooting
Browser or Telnet Access Problems
Browser or Telnet Access Problems
Cannot access the web browser interface:
■
Access may be disabled by the Web Agent Enabled parameter in the switch
console. Check the setting on this parameter by selecting:
2. Switch Configuration …
1. System Information
■
The switch may not have the correct IP address, subnet mask or gateway.
Verify by connecting a console to the switch’s Console port and selecting:
2. Switch Configuration …
5. IP Configuration
Note: If DHCP/Bootp is used to configure the switch, the IP addressing
can be verified by selecting:
1. Status and Counters …
2. Switch Management Address Information
also check the DHCP/Bootp server configuration to verify correct IP
addressing.
■
If you are using DHCP to acquire the IP address for the switch, the IP
address “lease time” may have expired so that the IP address has changed.
For more information on how to “reserve” an IP address, refer to the
documentation for the DHCP application that you are using.
■
If one or more IP-Authorized managers are configured, the switch allows
web browser access only to a device having an authorized IP address. For
more information on IP Authorized managers, refer to the Access Security
Guide for your switch.
■
Java™ applets may not be running on the web browser. They are required
for the switch web browser interface to operate correctly. Refer to the
online Help on your web browser for how to run the Java applets.
C-7
Troubleshooting
Browser or Telnet Access Problems
Cannot Telnet into the switch console from a station on the network:
■
Telnet access may be disabled by the Inbound Telnet Enabled parameter in
the System Information screen of the menu interface:
2. Switch Configuration
1. System Information
■
The switch may not have the correct IP address, subnet mask, or gateway.
Verify by connecting a console to the switch’s Console port and selecting:
2. Switch Configuration
5. IP Configuration
Note: If DHCP/Bootp is used to configure the switch, refer to the Note,
above.
C-8
■
If you are using DHCP to acquire the IP address for the switch, the IP
address “lease time” may have expired so that the IP address has changed.
For more information on how to “reserve” an IP address, refer to the
documentation for the DHCP application that you are using.
■
If one or more IP-Authorized managers are configured, the switch allows
inbound telnet access only to a device having an authorized IP address.
For more information on IP Authorized managers, refer to the Access
Security Guide for your switch.
Troubleshooting
Unusual Network Activity
Unusual Network Activity
Network activity that fails to meet accepted norms may indicate a hardware
problem with one or more of the network components, possibly including the
switch. Such problems can also be caused by a network loop or simply too
much traffic for the network as it is currently designed and implemented.
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 ProCurve Manager. Refer to the Installation and
Getting Started Guide you received with the switch for information on using
LEDs to identify unusual network activity.
A topology loop can also cause excessive network activity. The Event Log
“FFI” messages can be indicative of this type of problem.
General Problems
The network runs slow; processes fail; users cannot access servers or
other devices. Broadcast storms may be occurring in the network. These
may be due to redundant links between nodes.
•
If you are configuring a port trunk, finish configuring the ports in the
trunk before connecting the related cables. Otherwise you may inadvertently create a number of redundant links (i.e. topology loops) that
will cause broadcast storms.
•
Turn on Spanning Tree Protocol to block redundant links (i.e.
topology loops)
•
Check for FFI messages in the Event Log.
Duplicate IP Addresses. This is indicated by this Event Log message:
ip: Invalid ARP source: IP address on IP address
where: both instances of IP address are the same address, indicating the
switch’s IP address has been duplicated somewhere on the network.
Duplicate IP Addresses in a DHCP Network. If you use a DHCP server
to assign IP addresses in your network and you find a device with a valid IP
address that does not appear to communicate properly with the server or other
devices, a duplicate IP address may have been issued by the server. This can
occur if a client has not released a DHCP-assigned IP address after the
intended expiration time and the server “leases” the address to another device.
C-9
Troubleshooting
Unusual Network Activity
This can also happen, for example, if the server is first configured to issue IP
addresses with an unlimited duration, then is subsequently configured to issue
IP addresses that will expire after a limited duration. One solution is to
configure “reservations” in the DHCP server for specific IP addresses to be
assigned to devices having specific MAC addresses. For more information,
refer to the documentation for the DHCP server.
One indication of a duplicate IP address in a DHCP network is this Event Log
message:
ip: Invalid ARP source: < IP-address > on <IP-address >
where: both instances of IP-address are the same address, indicating the
IP address that has been duplicated somewhere on the network.
The Switch Has Been Configured for DHCP/Bootp Operation, But Has
Not Received a DHCP or Bootp Reply. When the switch is first configured for DHCP/Bootp operation, or if it is rebooted with this configuration, it
immediately begins sending request packets on the network. If the switch does
not receive a reply to its DHCP/Bootp requests, it continues to periodically
send request packets, but with decreasing frequency. Thus, if a DHCP or Bootp
server is not available or accessible to the switch when DHCP/Bootp is first
configured, the switch may not immediately receive the desired configuration.
After verifying that the server has become accessible to the switch, reboot the
switch to re-start the process.
802.1Q Prioritization Problems
Ports configured for non-default prioritization (level 1 - 7) are not
performing the specified action. If the ports were placed in a trunk group
after being configured for non-default prioritization, the priority setting was
automatically reset to zero (the default). Ports in a trunk group operate only
at the default priority setting.
IGMP-Related Problems
IP Multicast (IGMP) Traffic That Is Directed By IGMP Does Not Reach
IGMP Hosts or a Multicast Router Connected to a Port. IGMP must
be enabled on the switch and the affected port must be configured for “Auto”
or “Forward” operation.
C-10
Troubleshooting
Unusual Network Activity
IP Multicast Traffic Floods Out All Ports; IGMP Does Not Appear To
Filter Traffic. The IGMP feature does not operate if the switch or VLAN does
not have an IP address configured manually or obtained through DHCP/Bootp.
To verify whether an IP address is configured for the switch or VLAN, do either
of the following:
■
Try Using the Web Browser Interface: If you can access the web
browser interface, then an IP address is configured.
■
Try To Telnet to the Switch Console: If you can Telnet to the switch,
then an IP address is configured.
■
Using the Switch Console Interface: From the Main Menu, check the
Management Address Information screen by clicking on
1. Status and Counters
2. Switch Management Address Information
LACP-Related Problems
Unable to enable LACP on a port with the interface < port-number > lacp
command. In this case, the switch displays the following message:
Operation is not allowed for a trunked port.
You cannot enable LACP on a port while it is configured as static Trunk port.
To enable LACP on static-trunked port, first use the
no trunk < port-number > command to disable the static trunk assignment, then
execute interface < port-number > lacp.
Caution
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.
Port-Based Access Control (802.1X)-Related Problems
Note
To list the 802.1X port-access Event Log messages stored on the switch, use
show log 802.
See also “Radius-Related Problems” on page C-15.
C-11
Troubleshooting
Unusual Network Activity
The switch does not receive a response to RADIUS authentication
requests. In this case, the switch will attempt authentication using the
secondary method configured for the type of access you are using (console,
Telnet, or SSH).
There can be several reasons for not receiving a response to an authentication
request. Do the following:
■
Use ping to ensure that the switch has access to the configured RADIUS
servers.
■
Verify that the switch is using the correct encryption key (RADIUS secret
key) for each server.
■
Verify that the switch has the correct IP address for each RADIUS server.
■
Ensure that the radius-server timeout period is long enough for network
conditions.
The switch does not authenticate a client even though the RADIUS
server is properly configured and providing a response to the
authentication request. If the RADIUS server configuration for authenticating the client includes a VLAN assignment, ensure that the VLAN exists as
a static VLAN on the switch. Refer to “How 802.1X Authentication Affects
VLAN Operation” in the Access Security Guide for your switch.
During RADIUS-authenticated client sessions, access to a VLAN on the
port used for the client sessions is lost. If the affected VLAN is configured as untagged on the port, it may be temporarily blocked on that port during
an 802.1X session. This is because the switch has temporarily assigned another
VLAN as untagged on the port to support the client access, as specified in the
response from the RADIUS server. Refer to “How 802.1X Authentication
Affects VLAN Operation” in the Access Security Guide for your switch.
The switch appears to be properly configured as a supplicant, but
cannot gain access to the intended authenticator port on the switch
to which it is connected. If aaa authentication port-access is configured for
Local, ensure that you have entered the local login (operator-level) username
and password of the authenticator switch into the identity and secret parameters of the supplicant configuration. If instead, you enter the enable (managerlevel) username and password, access will be denied.
C-12
Troubleshooting
Unusual Network Activity
The supplicant statistics listing shows multiple ports with the same
authenticator MAC address. The link to the authenticator may have been
moved from one port to another without the supplicant statistics having been
cleared from the first port. Refer to “Note on Supplicant Statistics” in the
chapter on Port-Based and User-Based Access Control in the Access Security
Guide for your switch.
The show port-access authenticator < port-list > command shows one or more
ports remain open after they have been configured with control
unauthorized. 802.1X is not active on the switch. After you execute aaa portaccess 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). This is
because the port-access
authenticator has not yet been
activated.
Figure C-1. Authenticator Ports Remain “Open” Until Activated
RADIUS server fails to respond to a request for service, even though
the server’s IP address is correctly configured in the switch. Use
show radius to verify that the encryption key (RADIUS secret key) the switch
is using is correct for the server being contacted. If the switch has only a global
key configured, then it either must match the server key or you must configure
a server-specific key. If the switch already has a server-specific key assigned
to the server’s IP address, then it overrides the global key and must match the
server key.
C-13
Troubleshooting
Unusual Network Activity
Global RADIUS Encryption Key
Unique RADIUS Encryption Key
for the RADIUS server at
10.33.18.119
Figure C-2. Displaying 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. For example, show portaccess authenticator < port-list > gives you the status for the specified ports.
Also, ensure that other factors, such as port security or any 802.1X configuration on the RADIUS server are not blocking the link.
The authorized MAC address on a port that is configured for both
802.1X and port security either changes or is re-acquired after
execution of aaa port-access authenticator < port-list > initialize. If the port is
force-authorized with aaa port-access authenticator <port-list> control authorized
command and port security is enabled on the port, then executing initialize
causes the port to clear the learned address and learn a new address from the
first packet it receives after you execute initialize.
A trunked port configured for 802.1X is blocked. If you are using
RADIUS authentication and the RADIUS server specifies a VLAN for the port,
the switch allows authentication, but blocks the port. To eliminate this
problem, either remove the port from the trunk or reconfigure the RADIUS
server to avoid specifying a VLAN.
QoS-Related Problems
Loss of communication when using VLAN-tagged traffic. If you cannot
communicate with a device in a tagged VLAN environment, ensure that the
device either supports VLAN tagged traffic or is connected to a VLAN port that
is configured as Untagged.
C-14
Troubleshooting
Unusual Network Activity
Radius-Related Problems
The switch does not receive a response to RADIUS authentication
requests. In this case, the switch will attempt authentication using the
secondary method configured for the type of access you are using (console,
Telnet, or SSH).
There can be several reasons for not receiving a response to an authentication
request. Do the following:
■
Use ping to ensure that the switch has access to the configured RADIUS
server.
■
Verify that the switch is using the correct encryption key for the designated server.
■
Verify that the switch has the correct IP address for the RADIUS server.
■
Ensure that the radius-server timeout period is long enough for network
conditions.
■
Verify that the switch is using the same UDP port number as the server.
RADIUS server fails to respond to a request for service, even though
the server’s IP address is correctly configured in the switch. Use
show radius to verify that the encryption key the switch is using is correct for
the server being contacted. If the switch has only a global key configured, then
it either must match the server key or you must configure a server-specific
key. If the switch already has a server-specific key assigned to the server’s IP
address, then it overrides the global key and must match the server key.
Global RADIUS Encryption Key
Unique RADIUS Encryption Key
for the RADIUS server at
10.33.18.119
Figure C-3. Examples of Global and Unique Encryption Keys
C-15
Troubleshooting
Unusual Network Activity
Spanning-Tree Protocol (MSTP) and Fast-Uplink
Problems
Caution
If you enable MSTP, it is recommended that you leave the remainder of the
MSTP parameter settings at their default values until you have had an opportunity to evaluate MSTP performance in your network. Because incorrect
MSTP settings can adversely affect network performance, you should avoid
making changes without having a strong understanding of how MSTP operates. To learn the details of MSTP operation, refer to the IEEE 802.1s standard.
Broadcast Storms Appearing in the Network. This can occur when
there are physical loops (redundant links) in the topology.Where this exists,
you should enable MSTP on all bridging devices in the topology in order for
the loop to be detected.
STP Blocks a Link in a VLAN Even Though There Are No Redundant
Links in that VLAN. In 802.1Q-compliant switches MSTP blocks redundant
physical links even if they are in separate VLANs. A solution is to use only one,
multiple-VLAN (tagged) link between the devices. Also, if ports are available,
you can improve the bandwidth in this situation by using a port trunk. Refer
to “Spanning Tree Operation with VLANs” in the chapter titled “Static Virtual
LANs (VLANs)” in the Advanced Traffic Management Guide for your switch.
Fast-Uplink Troubleshooting. Some of the problems that can result from
incorrect usage of Fast-Uplink MSTP include temporary loops and generation
of duplicate packets.
Problem sources can include:
C-16
■
Fast-Uplink is configured on a switch that is the MSTP root device.
■
Either the Hello Time or the Max Age setting (or both) is too long on one or
more switches. Return the Hello Time and Max Age settings to their default
values (2 seconds and 20 seconds, respectively, on a switch).
■
A “downlink” port is connected to a switch that is further away (in hop
count) from the root device than the switch port on which fast-uplink
MSTP is configured.
■
Two edge switches are directly linked to each other with a fast-uplink
(Mode = Uplink) connection.
■
Fast uplink is configured on both ends of a link.
■
A switch serving as a backup MSTP root switch has ports configured for
fast-uplink MSTP and has become the root device due to a failure in the
original root device.
Troubleshooting
Unusual Network Activity
SSH-Related Problems
Switch access refused to a client. Even though you have placed the
client’s public key in a text file and copied the file (using the copy tftp pub-keyfile command) into the switch, the switch refuses to allow the client to have
access. If the source SSH client is an SSHv2 application, the public key may
be in the PEM format, which the switch (SSHv1) does not interpret. Check the
SSH client application for a utility that can convert the PEM-formatted key
into an ASCII-formatted key.
Executing IP SSH does not enable SSH on the switch. The switch
does not have a host key. Verify by executing show ip host-public-key. If you
see the message
ssh cannot be enabled until a host key is configured
(use 'crypto' command).
then you need to generate an SSH key pair for the switch. To do so, execute
crypto key generate.(Refer to “2. Generating the Switch’s Public and Private
Key Pair” in the SSH chapter of the Access Security Guide for your switch.)
C-17
Troubleshooting
Unusual Network Activity
Switch does not detect a client’s public key that does appear in the
switch’s public key file (show ip client-public-key). The client’s public key
entry in the public key file may be preceded by another entry that does not
terminate with a new line (CR). In this case, the switch interprets the next
sequential key entry as simply a comment attached to the preceding key entry.
Where a public key file has more than one entry, ensure that all entries
terminate with a new line (CR). While this is optional for the last entry in the
file, not adding a new line to the last entry creates an error potential if you
either add another key to the file at a later time or change the order of the keys
in the file.
An attempt to copy a client public-key file into the switch has failed
and the switch lists one of the following messages.
Download failed: overlength key in key file.
Download failed: too many keys in key file.
Download failed: one or more keys is not a valid RSA
public key.
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>.
■
There are more than ten public keys in the key file.
■
One or more keys in the file is corrupted or is not a valid rsa public key.
Client ceases to respond (“hangs”) during connection phase. The
switch does not support data compression in an SSH session. Clients will often
have compression turned on by default, but will disable it during the negotiation phase. A client which does not recognize the compression-request
FAILURE response may fail when attempting to connect. Ensure that
compression is turned off before attempting a connection to prevent this
problem.
C-18
Troubleshooting
Unusual Network Activity
TACACS-Related Problems
Event Log. When troubleshooting TACACS+ operation, check the switch’s
Event Log for indications of problem areas.
All Users Are Locked Out of Access to the Switch. If the switch is functioning properly, but no username/password pairs result in console or Telnet
access to the switch, the problem may be due to how the TACACS+ server
and/or the switch are configured. Use one of the following methods to recover:
■
Access the TACACS+ server application and adjust or remove the
configuration parameters controlling access to the switch.
■
If the above method does not work, try eliminating configuration
changes in the switch that have not been saved to flash (boot-up
configuration) by causing the switch to reboot from the boot-up
configuration (which includes only the configuration changes made
prior to the last write memory command.) If you did not use write
memory to save the authentication configuration to flash, then
pressing the Reset button or cycling the power reboots the switch
with the boot-up configuration.
■
Disconnect the switch from network access to any TACACS+ servers
and then log in to the switch using either Telnet or direct console port
access. Because the switch cannot access a TACACS+ server, it will
default to local authentication. You can then use the switch’s local
Operator or Manager username/password pair to log on.
■
As a last resort, use the Clear/Reset button combination to reset the
switch to its factory default boot-up configuration. Taking this step
means you will have to reconfigure the switch to return it to operation
in your network.
No Communication Between the Switch and the TACACS+ Server
Application. If the switch can access the server device (that is, it can ping
the server), then a configuration error may be the problem. Some possibilities
include:
■
The server IP address configured with the switch’s TACACS-server
host command may not be correct. (Use the switch’s show tacacsserver command to list the TACACS+ server IP address.)
C-19
Troubleshooting
Unusual Network Activity
■
The encryption key configured in the server does not match the
encryption key configured in the switch (by using the tacacs-server
key command). Verify the key in the server and compare it to the key
configured in the switch. (Use show tacacs-server to list the global key.
Use show config or show config running to list any server-specific keys.)
■
The accessible TACACS+ servers are not configured to provide
service to the switch.
Access Is Denied Even Though the Username/Password Pair Is
Correct. Some reasons for denial include the following parameters
controlled by your TACACS+ server application:
■
The account has expired.
■
The access attempt is through a port that is not allowed for the
account.
■
The time quota for the account has been exhausted.
■
The time credit for the account has expired.
■
The access attempt is outside of the time frame allowed for the
account.
■
The allowed number of concurrent logins for the account has been
exceeded
For more help, refer to the documentation provided with your TACACS+
server application.
Unknown Users Allowed to Login to the Switch. Your TACACS+ application may be configured to allow access to unknown users by assigning them
the privileges included in a default user profile. Refer to the documentation
provided with your TACACS+ server application.
System Allows Fewer Login Attempts than Specified in the Switch
Configuration. Your TACACS+ server application may be configured to
allow fewer login attempts than you have configured in the switch with the
aaa authentication num-attempts command.
C-20
Troubleshooting
Unusual Network Activity
TimeP, SNTP, or Gateway Problems
The Switch Cannot Find the Time Server or the Configured Gateway .
TimeP, SNTP, and Gateway access are through the primary VLAN, which in
the default configuration is the DEFAULT_VLAN. If the primary VLAN has
been moved to another VLAN, it may be disabled or does not have ports
assigned to it.
VLAN-Related Problems
Monitor Port. When using the monitor port in a multiple VLAN environment, the switch handles broadcast, multicast, and unicast traffic output from
the monitor port as follows:
■
If the monitor port is configured for tagged VLAN operation on the same
VLAN as the traffic from monitored ports, the traffic output from the
monitor port carries the same VLAN tag.
■
If the monitor port is configured for untagged VLAN operation on the same
VLAN as the traffic from the monitored ports, the traffic output from the
monitor port is untagged.
■
If the monitor port is not a member of the same VLAN as the traffic from
the monitored ports, traffic from the monitored ports does not go out the
monitor port.
None of the devices assigned to one or more VLANs on an 802.1Qcompliant switch are being recognized. If multiple VLANs are being used
on ports connecting 802.1Q-compliant devices, inconsistent VLAN IDs may
have been assigned to one or more VLANs. For a given VLAN, the same VLAN
ID must be used on all connected 802.1Q-compliant devices.
Link Configured for Multiple VLANs Does Not Support Traffic for One
or More VLANs. One or more VLANs may not be properly configured as
“Tagged” or “Untagged”. A VLAN assigned to a port connecting two 802.1Qcompliant devices must be configured the same on both ports. For example,
VLAN_1 and VLAN_2 use the same link between switch “X” and switch “Y”.
C-21
Troubleshooting
Unusual Network Activity
Link supporting VLAN_1
and VLAN_2
Switch “X”
Port X-3
Switch “Y”
Port Y- 7
VLAN Port Assignment
VLAN Port Assignment
Port VLAN_1
Port VLAN_1
X-3
VLAN_2
Untagged Tagged
Y-7
VLAN_2
Untagged Tagged
Figure C-4. Example of Correct VLAN Port Assignments on a Link
1.
If VLAN_1 (VID=1) is configured as “Untagged” on port 3 on switch “X”,
then it must also be configured as “Untagged” on port 7 on switch “Y”.
Make sure that the VLAN ID (VID) is the same on both switches.
2.
Similarly, if VLAN_2 (VID=2) is configured as “Tagged on the link port on
switch “A”, then it must also be configured as “Tagged” on the link port
on switch “B”. Make sure that the VLAN ID (VID) is the same on both
switches.
Duplicate MAC Addresses Across VLANs. The switches covered in this
guide operate with multiple forwarding databases. Thus, duplicate MAC
addresses occurring on different VLANs can appear where a device having
one MAC address is a member of more than one 802.1Q VLAN, and the switch
port to which the device is linked is using VLANs (instead of MSTP or trunking)
to establish redundant links to another switch. If the other device sends traffic
over multiple VLANs, its MAC address will consistently appear in multiple
VLANs on the switch port to which it is linked.
Note that attempting to create redundant paths through the use of VLANs will
cause problems with some switches. One symptom is that a duplicate MAC
address appears in the Port Address Table of one port, and then later appears
on another port. While the switches have multiple forwarding databases, and
thus does not have this problem, some switches with a single forwarding
database for all VLANs may produce the impression that a connected device
is moving among ports because packets with the same MAC address but
different VLANs are received on different ports. You can avoid this problem
by creating redundant paths using port trunks or spanning tree.
C-22
Troubleshooting
Unusual Network Activity
Server
MAC Address “A”; VLAN 1
MAC Address “A”; VLAN 2
8212zl Switch
(Multiple
Forwarding
Database)
VLAN 1
VLAN 2
Switch with
Single
Forwarding
Database
Problem: This switch detects
continual moves of MAC
address “A” between ports.
Figure C-5. Example of Duplicate MAC Address
C-23
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
Using the Event Log for Troubleshooting
Switch Problems
The Event Log records operating events in single- or double-line entries and
serves as a tool to isolate and troubleshoot problems.
Starting in software release K.13.xx, the maximum number of entries
supported in the Event Log is increased from 1000 to 2000 entries. Entries are
listed in chronological order, from the oldest to the most recent.
Once the log has received 2000 entries, it discards the oldest message each
time a new message is received. The Event Log window contains 14 log entry
lines. You can scroll through it to view any part of the log.
Note
The Event Log is erased if power to the switch is interrupted or if you enter
the boot system command. The contents of the Event Log are not erased if you:
■
Reboot the switch by choosing the Reboot Switch option from the menu
interface.
■
Enter the reload command from the CLI.
Event Log Entries
As shown in Figure C-1, each Event Log entry is composed of five or six fields,
depending on whether numbering is turned on or not:
Severity
I
Date
08/05/06
Time
Event number
10:52:32 00063
System Module
Event Message
ports: port A1 enabled
Figure C-1. Format of an Event Log Entry
Severity is one of the following codes (from highest to lowest severity):
M (major) indicates that a fatal switch error has occurred.
E
(error) indicates that an error condition occurred on the switch.
W (warning) indicates that a switch service has behaved unexpectedly.
I
C-24
(information) provides information on normal switch operation.
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
D
(debug) is reserved for ProCurve internal diagnostic information.
Date is the date in the format mm/dd/yy when an entry is recorded in the log.
Time is the time in the format hh:mm:ss when an entry is recorded in the log.
Event Number is the number assigned to an event. You can turn event
numbering on and off with the [no] log-number command.
System Module is the internal module (such as “ports:” for port manager) that
generated a log entry. If VLANs are configured, then a VLAN name also appears
for an event that is specific to an individual VLAN. Table C-1 lists the different
system modules with a description of each one.
Event Message is a brief description of the operating event.
Table C-1.
System
Module
Event Log System Modules
Description
Documented in ProCurve Hardware/
Software guide
802.1x
802.1X authentication: Provides access control on a per-client Access Security Guide
or per-port basis:
• Client-level security that allows LAN access to 802.1X
clients (up to 32 per port) with valid user credentials
• Port-level security that allows LAN access only on ports on
which a single 802.1X-capable client (supplicant) has
entered valid RADIUS user credentials
addrmgr
Address Table Manager: Manages MAC addresses that the
switch has learned and are stored in the switch’s address
table.
auth
Authorization: A connected client must receive authorization Access Security Guide
through web, AMC, RADIUS-based, TACACS+-based, or
802.1X authentication before it can send traffic to the switch.
cdp
Cisco Discovery Protocol: Supports reading CDP packets
Management and Configuration Guide
received from neighbor devices, enabling a switch to learn
about adjacent CDP devices. ProCurve switches do not
support the transmission of CDP packets to neighbor devices.
chassis
Hardware operation, including modules and ports, power
Installation Guides
supply, fans, transceivers, CPU interrupt errors, switch
Management and Configuration Guide
temperature, and so on. Chassis messages include events on
Power Over Ethernet (POE) operation.
console
Installation and Getting Started Guide
Console interface used to monitor switch and port status,
reconfigure the switch, read the event log through an in-band
Telnet or out-of-band connection.
Management and Configuration Guide
C-25
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
System
Module
Description
Documented in ProCurve Hardware/
Software guide
cos
Class of Service (CoS): Provides priority handling of packets Advanced Traffic Management Guide
traversing the switch, based on the IEEE 802.1p priority carried
by each packet.
CoS messages also include Quality of Service (QoS) events.
The QoS feature classifies and prioritizes traffic throughout a
network, establishing an end-to-end traffic priority policy to
manage available bandwidth and improve throughput of
important data.
dca
Dynamic Configuration Arbiter (DCA) determines the clientspecific parameters that are assigned in an authentication
session.
Access Security Guide
dhcp
Dynamic Host Configuration Protocol (DHCP) server
configuration: Switch is automatically configured from a
DHCP (Bootp) server, including IP address, subnet mask,
default gateway, Timep Server address, and TFTP server
address.
Management and Configuration Guide
dhcp v6c
DHCP for IPv6 prefix assignment
IPv6 Configuration Guide
download
Download operation for copying a software version or files to Management and Configuration Guide
the switch.
dma
Direct Access Memory (DMA): Transmits and receives
—
packets between the CPU and the switch. Not used for logging
messages in software release K.13.xx.
fault
Fault Detection facility, including response policy and the
Management and Configuration Guide
sensitivity level at which a network problem should generate
an alert.
ffi
Find, Fix, and Inform: Event or alert log messages indicating a Installation and Getting Started Guide
possible topology loop that cause excessive network activity Management and Configuration Guide
and results in the network running slow. FFI messages include
events on transceiver connections with other network
devices.
garp
Generic Attribute Registration Protocol (GARP), defined in the Advanced Traffic Management Guide
IEEE 802.1D-1998 standard.
gvrp
GARP VLAN Registration Protocol (GVRP): Manages dynamic Advanced Traffic Management Guide
802.1Q VLAN operations, in which the switch creates
temporary VLAN membership on a port to provide a link to
another port in the same VLAN on another device.
hpesp
Management module that maintains communication between Installation and Getting Started Guide
switch ports.
idm
Identity-driven Management: Optional management
application used to monitor and control access to switch.
C-26
Advanced Traffic Management Guide
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
System
Module
Description
Documented in ProCurve Hardware/
Software guide
igmp
Internet Group Management Protocol: Reduces unnecessary Multicast and Routing Guide
bandwidth usage for multicast traffic transmitted from
multimedia applications on a per-port basis.
ip
IP addressing: Configures the switch with an IP address and Management and Configuration Guide
Multicast and Routing Guide
subnet mask to communicate on the network and support
remote management access; configures multiple IP
addresses on a VLAN; enables IP routing on the switch.
ipaddrmgr
IP Address Manager: Programs IP routing information in
switch hardware.
ipx
Novell Netware protocol filtering: On the basis of protocol
Access Security Guide
type, the switch can forward or drop traffic to a specific set of
destination ports on the switch.
kms
Key Management System: Configures and maintains security Access Security Guide
information (keys) for all routing protocols, including a timing
mechanism for activating and deactivating an individual
protocol.
lacp
LACP trunks: The switch can either automatically establish an Management and Configuration Guide
802.3ad-compliant trunk group or provide a manually
configured, static LACP trunk.
ldbal
Management and Configuration Guide
Load balancing in LACP port trunks or 802.1s Multiple
Spanning Tree protocol (MSTP) that uses VLANs in a network Advanced Traffic Management Guide
to improve network resource utilization and maintain a loopfree environment.
Load-balancing messages also include switch meshing
events. The Switch Meshing feature provides redundant links,
improved bandwidth use, and support for different port types
and speeds.
lldp
Link-Layer Discovery Protocol: Supports transmitting LLDP
packets to neighbor devices and reading LLDP packets
received from neighbor devices, enabling a switch to
advertise itself to adjacent devices and to learn about
adjacent LLDP devices.
loop_protect
Loop protection: Detects the formation of loops when an
Advanced Traffic Management Guide
unmanaged device on the network drops spanning tree
packets, and provides protection by transmitting loop protocol
packets out ports on which loop protection has been enabled.
macauth
Web and MAC authentication: Port-based security employed Access Security Guide
on the network edge to protect private networks and the
switch itself from unauthorized access using one of the
following interfaces:
• Web page login to authenticate users for access to the
network
• RADIUS server that uses a device’s MAC address for
authentication
Multicast and Routing Guide
Management and Configuration Guide
C-27
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
System
Module
Description
Documented in ProCurve Hardware/
Software guide
maclock
Access Security Guide
MAC lockdown and MAC lockout
• MAC lockdown prevents station movement and MAC
address “hijacking” by requiring a MAC address to be used
only an assigned port on the switch. MAC Lockdown also
restricts the client device to a specific VLAN.
• MAC lockout blocks a specific MAC address so that the
switch drops all traffic to or from the specified address.
mgr
Management and Configuration Guide
ProCurve Manager (PCM) and ProCurve Manager Plus
(PCM+): Windows-based network management solutions for
managing and monitoring performance of ProCurve devices.
PCM messages also include events for configuration
operations.
netinet
Network Internet: Monitors the creation of a route or an
Address Resolution Protocol (ARP) entry and sends a log
message in case of failure.
Advanced Traffic Management Guide
ports
Port status and port configuration features, including mode
(speed and duplex), flow control, broadcast limit, jumbo
packets, and security settings.
Installation and Getting Started Guide
Management and Configuration Guide
Access Security Guide
radius
RADIUS (Remote Authentication Dial-In User Service)
authentication and accounting: A network server is used to
authenticate user-connection requests on the switch and
collect accounting information to track network resource
usage.
Access Security Guide
snmp
Simple Network Management Protocol: Allows you to manage Management and Configuration Guide
the switch from a network management station, including
support for security features, event reporting, flow sampling,
and standard MIBs.
sntp
Simple Network Time Protocol: Synchronizes and ensures a
uniform time among interoperating devices.
ssh
Secure Shell version 2 (SSHv2): Provides remote access to Access Security Guide
management functions on a switch via encrypted paths
between the switch and management station clients capable
of SSH operation.
SSH messages also include events from the Secure File
Transfer Protocol (SFTP) feature. SFTP provides a secure
alternative to TFTP for transferring sensitive information, such
as switch configuration files, to and from the switch in an SSH
session.
ssl
Secure Socket Layer Version 3 (SSLv3), including Transport Access Security Guide
Layer Security (TLSv1) support: Provides remote web access
to a switch via encrypted paths between the switch and
management station clients capable of SSL/TLS operation.
C-28
Management and Configuration Guide
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
System
Module
Description
Documented in ProCurve Hardware/
Software guide
stp
Advanced Traffic Management Guide
Multiple-instance spanning tree protocol/MSTP (802.1s):
Ensures that only one active path exists between any two
nodes in a group of VLANs in the network. MSTP operation is
designed to avoid loops and broadcast storms of duplicate
messages that can bring down the network.
system
Switch management, including system configuration, switch Management and Configuration Guide
bootup, activation of boot ROM image, memory buffers, traffic Access Security Guide
and security filters.
System messages also include events from Management
interfaces (menu, CLI, web browser, ProCurve Manager) used
to reconfigure the switch and monitor switch status and
performance.
tacacs
TACACS+ authentication: A central server is used to control Access Security Guide
access to the switches (and other TACACS-aware devices) in
the network through a switch’s console port (local access) or
Telnet (remote access).
tcp
Transmission Control Protocol: A transport protocol that runs Advanced Traffic Management Guide
on IP and is used to set up connections.
telnet
Session established on the switch from a remote device
through the Telnet virtual terminal protocol.
tftp
Trivial File Transfer Protocol: Supports the download of files to Management and Configuration Guide
the switch from a TFTP network server.
timep
Time Protocol: Synchronizes and ensures a uniform time
among interoperating devices.
Management and Configuration Guide
udld
Uni-directional Link Detection: Monitors a link between two
switches and blocks the ports on both ends of the link if the
link fails at any point between the two devices.
Access Security Guide
update
Updates (TFTP or serial) to ProCurve software and updates to Management and Configuration Guide
running-config and start-up config files
usb
Auxiliary port that allows you to connect external devices to Installation and Getting Started Guide
the switch.
Management and Configuration Guide
C-29
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
System
Module
Description
Documented in ProCurve Hardware/
Software guide
vlan
Static 802.1Q VLAN operations, including port-and protocol- Advanced Traffic Management Guide
based configurations that group users by logical function
instead of physical location
• A port -based VLAN creates a layer-2 broadcast domain
comprised of member ports that bridge IPv4 traffic among
themselves.
• A protocol-based VLAN creates a layer-3 broadcast
domain for traffic of a particular routing protocol, and is
comprised of member ports that bridge traffic of the
specified protocol type among themselves.
VLAN messages include events from Management interfaces
(menu, CLI, web browser, ProCurve Manager) used to
reconfigure the switch and monitor switch status and
performance.
xmodem
Xmodem: Binary transfer feature that supports the download Management and Configuration Guide
of software files from a PC or Unix workstation.
C-30
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
Menu: Displaying and Navigating in the Event Log
To display the Event Log from the Main Menu, select Event Log. Figure C-6
shows a sample event log display.
ProCurve Switch 5406zl
25-Oct-2007 18:02:52
==========================-CONSOLE - MANAGER MODE -============================
M 10/25/07 16:30:02 sys: 'Operator cold reboot from CONSOLE session.'
I 10/25/07 17:42:51 00061 system: --------------------------------------------I 10/25/07 17:42:51 00063 system: System went down: 10/25/07 16:30:02
I 10/25/07 17:42:51 00064 system: Operator cold reboot from CONSOLE session.
W 10/25/07 17:42:51 00374 chassis: WARNING: SSC is out of Date: Load 8.2 or newer
I 10/25/07 17:42:51 00068 chassis: Slot D Inserted
I 10/25/07 17:42:51 00068 chassis: Slot E Inserted
I 10/25/07 17:42:51 00068 chassis: Slot F Inserted
I 10/25/07 17:42:51 00690 udpf: DHCP relay agent feature enabled
I 10/25/07 17:42:51 00433 ssh: Ssh server enabled
I 10/25/07 17:42:52 00400 stack: Stack Protocol disabled
I 10/25/07 17:42:52 00128 tftp: Enable succeeded
I 10/25/07 17:42:52 00417 cdp: CDP enabled
----
Log events stored in memory 1-751.
Actions->
Back
Next page
Log events on screen 690-704.
Prev page
End
Help
Return to previous screen.
Use up/down arrow to scroll one line, left/right arrow keys to
change action selection, and <Enter> to execute action.
Figure C-6. Example of an Event Log Display
The log status line below the recorded entries states the total number of
events stored in the event log and which logged events are currently displayed.
To scroll to other entries in the Event Log, either preceding or following the
currently visible portion, press the keys indicated at the bottom of the display
(Back, Next page, Prev page, or End) or the keys described in Tabletable C-1.
Table C-1.
Event Log Control Keys
Key
Action
[N]
Advances the display by one page (next page).
[P]
Rolls back the display by one page (previous page).
[v]
Advances display by one event (down one line).
C-31
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
Key
Action
[^]
Rolls back display by one event (up one line).
[E]
Advances to the end of the log.
[H]
Displays Help for the Event Log.
CLI: Displaying the Event Log
To display messages recorded in the event log from the CLI, enter the show
logging command. Keyword searches are supported.
Syntax: show logging [-a, -r] [<search-text>]
By default, the show logging command displays the log
messages recorded since the last reboot in chronological
order.
-a displays all recorded log messages, including those
before the last reboot.
-r displays all recorded log messages, with the most recent
entries listed first.
<search-text> displays all Event Log entries that contain the
specified text. Use a <search-text> value with -a or -r to
further filter show logging command output.
Examples. To display all Event Log messages that have “system” in the
message text or module name, enter the following command:
ProCurve# show logging -a system
To display all Event Log messages recorded since the last reboot that have the
word, “system”, in the message text or module name, enter:
ProCurve# show logging system
CLI: Clearing Event Log Entries
Use the clear logging command to hide, but not erase, Event Log entries
displayed in show logging command output. Only new entries generated after
you enter the command will be displayed.
C-32
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
To redisplay all hidden entries, including Event Log entries recorded prior to
the last reboot, enter the show logging -a command.
Syntax: clear logging
Removes all entries from the event log display output.
CLI: Turning Event Numbering On
Syntax: [no] log-numbers
Turns event numbering on and off
Using Log Throttling to Reduce Duplicate
Event Log and SNMP Messages
A recurring event can generate a series of duplicate Event Log messages and
SNMP traps in a relatively short time. As a result, the Event Log and any
configured SNMP trap receivers may be flooded with excessive, exactly
identical messages. To help reduce this problem, the switch uses log throttle
periods to regulate (throttle) duplicate messages for recurring events, and
maintains a counter to record how many times it detects duplicates of a
particular event since the last system reboot.
When the first instance of a particular event or condition generates a message,
the switch initiates a log throttle period that applies to all recurrences of that
event. If the logged event recurs during the log throttle period, the switch
increments the counter initiated by the first instance of the event, but does
not generate a new message.
If the logged event repeats again after the log throttle period expires, the
switch generates a duplicate of the first message, increments the counter, and
starts a new log throttle period during which any additional instances of the
event are counted, but not logged. Thus, for a particular recurring event, the
switch displays only one message in the Event Log for each log throttle period
in which the event reoccurs. Also, each logged instance of the event message
includes counter data showing how many times the event has occurred since
the last reboot. The switch manages messages to SNMP trap receivers in the
same way.
C-33
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
Log Throttle Periods
The length of the log throttle period differs according to an event’s severity
level:
Severity Level
Log Throttle Period
I (Information)
6000 Seconds
W (Warning)
600 Seconds
D (Debug)
60 Seconds
M (Major)
6 Seconds
Example of Log Throttling
For example, suppose that you configure VLAN 100 on the switch to support
PIM operation, but do not configure an IP address. If PIM attempted to use
VLAN 100, the switch would generate the first instance of the following Event
Log message and counter.
W 10/01/06 09:00:33 PIM:No IP address configured on VID 100 (1)
The counter indicates that this is the first instance
of this event since the switch last rebooted.
Figure C-7. Example of the First Instance of an Event Message and Counter
C-34
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
If PIM operation caused the same event to occur six more times during the
initial log throttle period, there would be no further entries in the Event Log.
However, if the event occurred again after the log throttle period expired, the
switch would repeat the message (with an updated counter) and start a new
log throttle period.
This message indicates the original instance
of the event (since the last switch reboot).
W 10/01/06 09:00:33 PIM:No IP address configured on VID 100 (1)
.
.
.
Original Counter from First Log Throttle Period
W 10/01/06 09:28:42 PIM:No IP address configured on VID 100 (8)
The duplicate of the original message is the first
instance of the event since the previous log
throttle period expired, and indicates that a new
log throttle period has begun for this event.
The counter now indicates that this is the
eighth instance of this event since the
switch last rebooted.
Figure C-2. Example of Duplicate Messages Over Multiple Log Throttling Periods
Note that if the same type of event occurs under different circumstances, the
switch handles these as unrelated events for the purpose of Event Log
messages. For example, if PIM operation simultaneously detected that VLANs
100 and 205 were configured without IP addresses, you would see log
messages similar to the following:
These two messages report separate events involving
separate log throttle periods and separate counters.
W 10/01/06 09:00:33 PIM:No IP address configured on VID 100 (1)
W 10/01/06 09:00:33 PIM:No IP address configured on VID 205 (1)
.
.
.
Figure C-3. Example of Log Messages Generated by Unrelated Events of the Same Type
C-35
Troubleshooting
Using the Event Log for Troubleshooting Switch Problems
Example of Event Counter Operation
Suppose the switch detects the following after a reboot:
■
Three duplicate instances of the PIM “Send error” during the first log
throttle period for this event
■
Five more instances of the same Send error during the second log throttle
period for this event
■
Four instances of the same Send error during the third log throttle period
for this event
In this case, the duplicate message would appear three times in the Event Log
(once for each log throttle period for the event being described), and the
Duplicate Message Counter would increment as shown in table C-4. (The same
operation would apply for messages sent to any configured SNMP trap
receivers.)
Table C-4.
How the Duplicate Message Counter Increments
Instances
During 1st Log
Throttle Period
Instances
During 2nd Log
Throttle Period
Instances
During 3rd Log
Throttle Period
3
Duplicate
Message
Counter*
1
5
4
4
9
*This value always comprises the first instance of the duplicate
message in the current log throttle period plus all previous occurrences
of the duplicate message occurring since the switch last rebooted.
C-36
Troubleshooting
Debug/Syslog Operation
Debug/Syslog Operation
While the Event Log records switch-level progress, status, and warning
messages on the switch, the Debug/System Logging (Syslog) feature provides
a way to record Event Log and debug messages on a remote device. For
example, you can send messages about routing misconfigurations and other
network protocol details to an external device, and later use them to debug
network-level problems.
Debug/Syslog Messaging
The Debug/Syslog feature allows you to specify the types of Event Log and
debug messages that you want to send to an external device. As shown in
Figure C-8, you can perform the following operations:
■
■
Use the debug command to configure messaging reports for the following
event types:
•
Dynamic ARP protection events
•
DHCP snooping events
•
Events recorded in the switch’s Event Log
•
IPv4 routing events
•
LLDP events
•
OSPF events
•
SSH events
•
VRRP events
•
Wireless Services events
Use the logging command to select a subset of Event Log messages to send
to an external device for debugging purposes according to:
•
Severity level
•
System module
Debug/Syslog Destination Devices
To use Debug/Syslog messaging, you must configure an external device as the
logging destination by using the logging and debug destination commands. For
more information, see “Debug Destinations” on page C-47 and “Configuring a
Syslog Server” on page C-49.
C-37
Troubleshooting
Debug/Syslog Operation
A Debug/Syslog destination device can be a Syslog server and/or a console
session. You can configure debug and logging messages to be sent to:
■
Up to six Syslog servers
■
A CLI session through a direct RS-232 console connection, or a Telnet or
SSH session
Debug/Syslog Configuration Commands
Event
Notification
Logging
logging
Command
debug
Command
—
<syslog-ip-addr>
Enables Syslog messaging to be sent to the specified IP address.
facility
(Optional) The logging facility command specifies the destination (facility) subsystem
used on a Syslog server for debug reports.
severity
Sends Event Log messages of equal or greater severity than the specified value to
configured debug destinations. (The default setting is to send Event Log messages from
all severity levels.)
system-module
Sends Event Log messages from the specified system module to configured debug
destinations. The severity filter is also applied to the system-module messages you select.
The default setting is to send Event Log messages from all system modules. To restore
the default setting, enter the no logging system-module <system-module> or logging
system-module all-pass commands.
all
Sends debug logging to configured debug destinations for all Event Log, IP-OSPF, and IPRIP options.
destination
logging: Disables or re-enables Syslog logging on one or more Syslog servers configured
with the logging < syslog-ip-addr > command. See “Debug Destinations” on page C-47.
session: Assigns or re-assigns destination status to the terminal device that was most
recently used to request debug output. “Debug Destinations” on page C-47.
buffer: Enables Syslog logging to send the debug message types specified by the debug
< debug-type > command to a buffer in switch memory. See “Debug Destinations” on
page C-47.
event
Sends standard Event Log messages to configured debug destinations. (The same
messages are also sent to the switch’s Event Log, regardless of whether you enable this
option.)
ip
C-38
Automatically sends switch-level event messages to the switch’s Event Log. Debug and
Syslog do not affect this operation, but add the capability of directing Event Log
messaging to an external device.
forwarding: Sends IPv4 forwarding messages to the debug destination(s).
packet: Sends IPv4 packet messages to the debug destination(s).
Troubleshooting
Debug/Syslog Operation
ipv6
dhcpv6-client: Sends DHCPv6 client debug messages to the configured debug
destination.
nd: Sends IPv6 debug messages for IPv6 neighbor discovery to the configured debug
destination(s).
packet: Sends IPv6 packet messages to the debug destination(s).
lldp
Sends LLDP debug logging to the debug destination(s).
ssh
Sends SSH debug messages at the specified level to the debug destination. The levels
are fatal, error, info, verbose, debug, debug2, and debug3.
Figure C-8. Summary of Debug/Syslog Configuration Commands
Using the Debug/Syslog feature, you can perform the following operations:
■
Configure the switch to send Event Log messages to one or more Syslog
servers. In addition, you can configure the messages to be sent to the User
log facility (default) or to another log facility on configured Syslog servers.
■
Configure the switch to send Event Log messages to the current management-access session (serial-connect CLI, Telnet CLI, or SSH).
■
Disable all Syslog debug logging while retaining the Syslog addresses from
the switch configuration. This allows you to configure Syslog messaging
and then disable and re-enable it as needed.
■
Display the current debug configuration. If Syslog logging is currently
active, the list f configured Syslog servers is displayed.
■
Display the current Syslog server list when Syslog logging is disabled.
Configuring Debug/Syslog Operation
1.
To use a Syslog server as the destination device for debug messaging,
follow these steps:
a.
Enter the logging < syslog-ip-addr > command at the global configuration level to configure the Syslog server IP address and enable Syslog
logging. Optionally, you may also specify the destination subsystem
to be used on the Syslog server by entering the logging facility
command.
If no other Syslog server IP addresses are configured, entering the
logging command enables both debug messaging to a Syslog server
and the Event debug message type. As a result, the switch automatically sends Event Log messages to the Syslog server, regardless of
other debug types that may be configured.
C-39
Troubleshooting
Debug/Syslog Operation
b.
2.
3.
Re-enter the logging command in Step “a” to configure additional
Syslog servers. You can configure up to a total of six servers. (When
multiple server IP addresses are configured, the switch sends the
debug message types that you configure in Step 3 to all IP addresses.)
To use a CLI session on a destination device for debug messaging:
a.
Set up a serial, Telnet, or SSH connection to access the switch’s CLI.
b.
Enter the debug destination session command at the manager level.
Enable the types of debug messages to be sent to configured Syslog
servers and/or the current session device by entering the debug < debugtype > command:
ProCurve# debug <all|arp-protect|event|ip
[bgp|forwarding|ospf|packet|rip|routemap]|ipv6|
lldp|vrrp>
Repeat this step if necessary to enable multiple debug message types.
By default, Event Log messages are sent to configured debug destination
devices. To block Event Log messages from being sent, enter the no debug
event command.
4.
If necessary, enable a subset of Event Log messages to be sent to configured Syslog servers by specifying a severity level and/or system module
using the following commands
ProCurve(config)# logging severity < debug | major | error | warning | info >
ProCurve(config)# logging system-module < system-module >
To display a list of valid values for each command, enter logging severity
or logging system-module followed by ? or pressing the Tab key.
The severity levels in order from the highest to lowest severity are: major,
error, warning, info, debug. For a list of valid values for the logging systemmodule <system-module > command, refer to Table C-1 on page C-25.
5.
If you configure system-module and/or severity-level values to filter Event
Log messages, when you finish troubleshooting, you may want to reset
these values to their default settings so that the switch sends all Event Log
messages to configured debug destinations (Syslog servers and/or CLI
session).
To remove a configured setting and restore the default values that send
all Event Log messages, enter one or both of the following commands:
ProCurve(config)# no logging severity < debug | major | error | warning | info>
ProCurve(config)# no logging system-module < system-module >
C-40
Troubleshooting
Debug/Syslog Operation
Caution
If you configure a severity-level, system-module, logging destination, or
logging facility value and save the settings to the startup configuration (for
example, by entering the write memory command), the debug settings are
saved after a system reboot (power cycle or reboot) and re-activated on the
switch. As a result, after switch startup, one of the following situations may
occur:
■
Only a partial set of Event Log messages may be sent to configured debug
destinations.
■
Messages may be sent to a previously configured Syslog server used in an
earlier debugging session.
Displaying a Debug/Syslog Configuration
Use the show debug command to display the currently configured settings for:
■
Debug message types and Event Log message filters (severity level and
system module) sent to debug destinations
■
Debug destinations (Syslog servers or CLI session) and Syslog server
facility to be used
Syntax: show debug
Displays the currently configured debug logging destinations
and message types selected for debugging purposes. (If no
Syslog server address is configured with the logging <syslog-ipaddr> command, no show debug command output is displayed.)
ProCurve(config)# show debug
Debug Logging
Destination:
Logging -10.28.38.164
Facility=kern
Severity=warning
System module=all-pass
Enabled debug types:
event
Figure C-5. Sample Output of show debug Command
Example: In the following example, no Syslog servers are configured on the
switch (default setting). When you configure a Syslog server, debug logging is
enabled to send Event Log messages to the server. To limit the Event Log
C-41
Troubleshooting
Debug/Syslog Operation
messages sent to the Syslog server, specify a set of messages by entering the
logging severity and logging system-module commands.
ProCurve(config)# show debug
Debug Logging
Destination: None
Enabled debug types:
None are enabled
Displays the default debug
configuration. (No Syslog server IP
addresses or debug types are
configured.)
ProCurve(config)# logging 10.28.38.164
When you configure a Syslog IP
ProCurve(config)# write memory
address with the logging
ProCurve(config)# show debug
Debug Logging
Destination:
Logging -10.28.38.164
Facility=user
Severity=debug
System module=all-pass
Enabled debug types:
event
command, by default, the switch
enables debug messaging to the
Syslog address and the user
facility on the Syslog server, and
sends Event Log messages of all
severity levels from all system
modules.
You can enter the logging severity
and logging system-module
commands to specify a subset of
Event Log messages to send to the
Syslog server.
ProCurve(config)# logging severity error
ProCurve(config)# logging system-module iplock
Figure C-2. Syslog Configuration to Receive Event Log Messages From Specified
System Module and Severity Levels
As shown at the top of Figure C-2, if you enter the show debug command when
no Syslog server IP address is configured, the configuration settings for Syslog
server facility, Event Log severity level and system module are not displayed.
However, after you configure a Syslog server address and enable Syslog
logging, all debug and logging settings are displayed with the show debug
command. If you do not want Event Log messages sent to Syslog servers, you
can block the messages from being sent by entering the no debug event
command. (There is no effect on the normal logging of messages in the
switch’s Event Log.)
C-42
Troubleshooting
Debug/Syslog Operation
Example. The next example shows how to configure:
■
Debug logging of IP-OSPF packet messages on a Syslog server at
18.38.64.164 (with user as the default logging facility).
■
Display of these messages in the CLI session of your terminal device’s
management access to the switch.
■
Blocking Event Log messages from being sent from the switch to the
Syslog server and a CLI session.
To configure Syslog operation in these ways with the Debug/Syslog feature
disabled on the switch, you would enter the commands shown in Figure C-6.
C-43
Troubleshooting
Debug/Syslog Operation
ProCurve# config
ProCurve(config)# logging 10.38.64.164
ProCurve(config)# show debug
Debug Logging
Destination:
Logging -10.38.64.164
Facility=user
Severity=debug
System module=all-pass
Enabled debug types:
event
Configure a Syslog server IP address.
(No other Syslog servers are
configured on the switch.) The server
address serves as an active debug
destination for any configured debug
types.)
Display the new debug configuration.
(Default debug settings - facility,
severity, system module, and debug
types- are displayed.)
Remove the unwanted event
message logging to debug
destinations.
Configure the debug messages types
ProCurve(config)#
ProCurve(config)#
ProCurve(config)#
ProCurve(config)#
that you want to send to the Syslog
no debug event
server and CLI session.
debug ip ospf packet
debug destination session
show debug
Debug Logging
Destination:
Logging -10.38.64.164
Facility=user
Severity=debug
System module=all-pass
Session
Enabled debug types:
ip ospf packet
Configure the CLI session as a debug
destination.
Display the final debug and Syslog
server configuration.
Figure C-6. Debug/Syslog Configuration for Multiple Debug Types and Multiple
Destinations
C-44
Troubleshooting
Debug/Syslog Operation
Debug Command
At the manager level, use the debug command to perform two main functions:
■
Specifies the types of event messages to be sent to an external destination.
■
Specifies the destinations to which selected message types are sent.
By default, no debug destination is enabled and only Event Log messages are
enabled to be sent.
Note
To configure a Syslog server, use the logging <syslog-ip-addr> command. For
more information, see “Configuring a Syslog Server” on page C-49.
Debug Messages
Use the debug command to configure the types of debug messages that the
switch can send to configured debug destinations.
Syntax: [no] debug < debug-type >
all
Configures the switch to send all debug message types to
configured debug destination(s). (Default: Disabled - No
debug messages are sent.)
event
Configures the switch to send Event Log messages to configured debug destinations.
Note: This value does not affect the reception of event
notification messages in the Event Log on the switch.
Syntax: [no] debug < debug-type > (Continued)
event
Event Log messages are automatically enabled to be sent to
debug destinations in these conditions:
• If no Syslog server address is configured and you enter
the logging <syslog-ip-addr> command to configure a
destination address.
• If at least one Syslog server address is configured in the
startup configuration and the switch is rebooted or reset.
Event log messages are the default type of debug message
sent to configured debug destinations.
ip
Enables all IP-OSPF messages for configured destinations.
C-45
Troubleshooting
Debug/Syslog Operation
ip [ ospf < adj | event | flood | lsa-generation | packet [ packet-type ] |
retransmission | spf > ]
For the configured debug destination(s):
ospf < adj | event | flood | lsa-generation | packet [ packet-type ] |
retransmission | spf > — Enables the specified IP-OSPF
message type.
adj — Adjacency changes.
event — OSPF events.
flood — Information on flood messages.
lsa-generation — New LSAs added to database.
packet [ packet-type ] — All OSPF packet messages sent and
received on the switch, where packet-type enables only the
specified OSPF packet type. Valid values are:
dd — Database descriptions
hello — Hello messages
lsa — Link-state advertisements
lsr — Link-state requests
lsu — Link-state updates
retransmission — Retransmission timer messages.
spf — Path recalculation messages.
ip [ rip < database | event | trigger > ]
rip < database | event | trigger > > — Enables the specified RIP
message type for the configured destination(s).
database— Display database changes.
event— Display RIP events.
trigger— Display trigger messages.
ipv6
[dhcpv6-client [events | packet ]]
[forwarding | nd | packet]
When no debug options are included, displays debug
messages for all IPv6 debug options.
dhcpv6-client [events | packet]: Displays DHCPv6 client event
and packet data.
[forwarding]: Displays IPv6 forwarding messages.
[nd]: Displays debug messages for IPv6 neighbor discovery.
[packet]: Displays IPv6 packet messages.
lldp
Enables all LLDP message types for the configured destinations.
C-46
Troubleshooting
Debug/Syslog Operation
Debug Destinations
Use the debug destination command to enable (and disable) Syslog messaging
on a Syslog server or to a CLI session for specified types of debug and Event
Log messages.
Syntax: [no] debug destination < logging | session | buffer | debug-console>
logging
Enables Syslog logging to configured Syslog servers so that
the debug message types specified by the debug <debug-type>
command (see “Debug Messages” on page C-45) are sent.
(Default: Logging disabled)
To configure a Syslog server IP address, refer to “Configuring a Syslog Server” on page C-49.
Note: Debug messages from the switches covered in this
guide have a debug severity level. Because the default
configuration of some Syslog servers ignore Syslog
messages with the debug severity level, ensure that the
Syslog servers you want to use to receive debug messages
are configured to accept the debug level. For more information, refer to “Operating Notes for Debug and Syslog” on
page C-54.
session
Enables transmission of event notification messages to the
CLI session that most recently executed this command. The
session can be on any one terminal emulation device with
serial, Telnet, or SSH access to the CLI at the Manager level
prompt (ProCurve#_ ). If more than one terminal device has
a console session with the CLI, you can redirect the destination from the current device to another device. Do so by
executing debug destination session in the CLI on the
terminal device on which you now want to display event
messages.
Event message types received on the selected CLI session are
configured with the debug < debug-type > command. (Refer
to “Debug Messages” on page C-45.)
buffer
Enables Syslog logging to send the debug message types
specified by the debug < debug-type > command to a buffer
in switch memory. To view the debug messages stored in
the switch buffer, enter the show debug buffer command.
C-47
Troubleshooting
Debug/Syslog Operation
Logging Command
At the global configuration level, the logging command allows you to enable
debug logging on specified Syslog servers and select a subset of Event Log
messages to send for debugging purposes according to:
■
Severity level
■
System module
By specifying both a severity level and system module, you can use both
configured settings to filter the Event Log messages you want to use to
troubleshoot switch or network error conditions.
Caution
After you configure a Syslog server and a severity level and/or system module
to filter the Event Log messages that are sent, if you save these settings to the
startup configuration file by entering the write memory command, these debug
and logging settings are automatically re-activated after a switch reboot or
power recycle. The debug settings and destinations configured in your
previous troubleshooting session will then be applied to the current session,
which may not be desirable.
After a reboot, messages remain in the Event Log and are not deleted.
However, after a power recycle, all Event Log messages are deleted.
If you configure a severity level and/or system module to temporarily filter
Event Log messages, be sure to reset the values to their default settings by
entering the no form of the following commands to ensure that Event Log
messages of all severity levels and from all system modules are sent to
configured Syslog servers:
ProCurve(config)# no logging severity < debug | major | error | warning | info>
ProCurve(config)# no logging system-module < system-module >
C-48
Troubleshooting
Debug/Syslog Operation
Configuring a Syslog Server
Syslog is a client-server logging tool that allows a client switch to send event
notification messages to a networked device operating with Syslog server
software. Messages sent to a Syslog server can be stored to a file for later
debugging analysis.
To use the Syslog feature, you must install and configure a Syslog server
application on a networked host accessible to the switch. Refer to the documentation for the Syslog server application for instructions.
To configure a Syslog server, use the logging < syslog-ip-addr > command as
described below.
When you configure a Syslog server, Event Log messages are automatically
enabled to be sent to the server. To reconfigure this setting, use the following
commands:
■
Use debug command to specify additional debug message types (see
“Debug Messages” on page C-45).
■
Use the logging command to configure the system module or severity level
used to filter the Event Log messages sent to configured Syslog servers
(see “Configuring the Severity Level for Event Log Messages Sent to a
Syslog Server” on page C-53 and “Configuring the System Module Used to
Select the Event Log Messages Sent to a Syslog Server” on page C-54).
To display the currently configured Syslog servers as well as the types of debug
messages and the severity-level and system-module filters used to specify the
Event Log messages that are sent, enter the show debug command (see
“Displaying a Debug/Syslog Configuration” on page C-41).
C-49
Troubleshooting
Debug/Syslog Operation
Syntax: [no] logging < syslog-ip-addr > [oobm]
Enables or disables Syslog messaging to the specified IP
address. You can configure up to six addresses. If you
configure an address when none are already configured, this
command enables destination logging (Syslog) and the Event
debug type. Therefore, at a minimum, the switch begins
sending Event Log messages to configured Syslog servers. The
IP-OSPF and/or IP-RIP message types will also be sent to the
Syslog server(s) if they are currently enabled as debug types.
(Refer to “Debug Messages” on page C-45.)
For switches that have a separate out-of-band management
(OOBM) port, specifying the oobm parameter causes logging
traffic to go through the OOBM port. Refer to Appendix G,
“Network Out-of-Band Management” in this guide for more
information on out-of-band management.
no logging removes all currently configured Syslog logging
destinations from the running configuration.
no logging < syslog-ip-address > removes only the specified Syslog
logging destination from the running configuration.
If you use the “no” form of the command to delete the only
remaining Syslog server address, debug destination logging is
disabled on the switch, but the default Event debug type is not
changed.
Also, removing all configured Syslog destinations with the no
logging command (or a specified Syslog server destination with
the no logging < syslog-ip-address > command) does not delete the
Syslog server IP addresses stored in the startup configuration.
To delete Syslog addresses in the startup configuration, you
must enter a no logging command followed by the write memory
command. To verify the deletion of a Syslog server address,
display the startup configuration by entering the show config
command.
To block the messages sent to configured Syslog servers from
the currently configured debug message type, enter the no debug
< debug-type > command. (See “Debug Messages” on page C-45.)
C-50
Troubleshooting
Debug/Syslog Operation
To disable Syslog logging on the switch without deleting configured server addresses, enter the no debug destination logging
command. Note that, unlike the case in which no Syslog servers
are configured, if one or more Syslog servers are already
configured and Syslog messaging is disabled, configuring a
new server address does not re-enable Syslog messaging. To reenable Syslog messaging, you must enter the debug destination
logging command.
Syntax: [no] logging facility < facility-name >
The logging facility specifies the destination subsystem used
in a configured Syslog server. (All configured Syslog servers
must use the same subsystem.) ProCurve recommends the
default (user) subsystem unless your application specifically
requires another subsystem. Options include:
user (default) — Random user-level messages
kern — Kernel messages
mail — Mail system
daemon — System daemons
auth — Security/Authorization messages
syslog — Messages generated internally by Syslog
lpr — Line-Printer subsystem
news — Netnews subsystem
uucp — uucp subsystem
cron — cron/at subsystem
sys9 — cron/at subsystem
sys10 - sys14 — Reserved for system use
local10 - local17 — Reserved for system use
Use the no form of the command to remove the configured
facility and reconfigure the default (user) value.
For a list of supported ProCurve switches, refer to the Note on
page C-39.
Adding a Description for a Syslog Server
You can associate a user-friendly description with each of the IP addresses
(IPv4 only) configured for syslog using the CLI or SNMP.
Note
The HP enterprise MIB hpicfSyslog.mib allows the configuration and monitoring of syslog for SNMP (RFC 3164 supported).
C-51
Troubleshooting
Debug/Syslog Operation
The CLI command is:
Syntax: logging <ip-addr> control-descr <text_string>]
no logging <ip-addr> [control-descr]
An optional user-friendly description that can be associated with
a server IP address. If no description is entered, this is blank. If
<text_string> contains white space, use quotes around the string.
IPv4 addresses only. Use the no form of the command to remove
the description.
Limit: 255 characters
Note: To remove the description using SNMP, set the description
to an empty string.
ProCurve(config)# logging 10.10.10.2 control-descr syslog_one
Figure C-9. Example of the Logging Command with a Control Description
Caution
Entering the no logging command removes ALL the syslog server addresses
without a verification prompt.
Adding a Priority Description
You can add a user-friendly description for the set of syslog filter parameters
using the priority-descr option. The description can be added with the CLI or
SNMP. The CLI command is:
Syntax: logging priority-descr <text_string>
no logging priority-descr
Provides a user-friendly description for the combined filter
values of severity and system module. If no description is
entered, this is blank. If <text_string> contains white space,
use quotes around the string. Use the no form of the command
to remove the description.
Limit: 255 characters
C-52
Troubleshooting
Debug/Syslog Operation
ProCurve(config)# logging priority-descr severe-pri
Figure C-10. Example of the Logging Command with a Priority Description
Note
A notification is sent to the SNMP agent if there are any changes to the syslog
parameters either through the CLI or with SNMP.
Configuring the Severity Level for Event Log Messages
Sent to a Syslog Server
Event Log messages are entered with one of the following severity levels (from
highest to lowest):
Major: A fatal error condition has occurred on the switch.
Error: An error condition has occurred on the switch.
Warning: A switch service has behaved unexpectedly.
Information: Information on a normal switch event.
Debug: Reserved for ProCurve internal diagnostic information.
Using the logging severity command, you can select a set of Event Log
messages according to their severity level and send them to a Syslog server.
Messages of the selected and higher severity will be sent. To configure a Syslog
server, see “Configuring a Syslog Server” on page C-49.
Syntax: [no] logging severity < major | error l warning | info | debug >
Configures the switch to send all Event Log messages with
a severity level equal to or higher than the specified value
to all configured Syslog servers.
Default: debug (Reports messages of all severity levels.)
Use the no form of the command to remove the configured
severity level and reconfigure the default value, which sends
Event Log messages of all severity levels to Syslog servers.
Note: The severity setting does not affect event notification
messages that the switch normally sends to the Event Log.
All messages remain recorded in the Event Log.
C-53
Troubleshooting
Debug/Syslog Operation
Configuring the System Module Used to Select the Event Log
Messages Sent to a Syslog Server
Event Log messages contain the name of the system module that reported the
event. Using the logging system-module command, you can select a set of Event
Log messages according to the originating system module and send them to a
Syslog server. To configure a Syslog server, see “Configuring a Syslog Server”
on page C-49.
Using the logging system-module command, you can select messages from only
one system module to be sent to a Syslog server. You cannot configure
messages from multiple system modules to be sent. If you re-enter the
command with a different system module name, the currently configured
value is replaced with the new one.
Syntax: [no] logging system-module < system-module >
Configures the switch to send all Event Log messages being
logged from the specified system module to configured
Syslog servers.
Refer to Table C-1 on page C-27 for the correct value to enter
for each system module.
Default: all-pass (Reports all Event Log messages.)
Use the no form of the command to remove the configured
system module value and reconfigure the default value,
which sends Event Log messages from all system modules
to Syslog servers.
Note: This setting has no effect on event notification
messages that the switch normally sends to the Event Log.
Operating Notes for Debug and Syslog
■
C-54
Rebooting the Switch or pressing the Reset button resets the
Debug Configuration.
Debug Option
Effect of a Reboot or Reset
logging (debug destination)
If Syslog server IP addresses are stored in the startup-config
file, they are saved across a reboot and the logging
destination option remains enabled. Otherwise, the logging
destination is disabled.
session (debug destination)
Disabled.
Troubleshooting
Debug/Syslog Operation
■
Debug Option
Effect of a Reboot or Reset
All (debug type)
Disabled.
event (debug type)
If a Syslog server IP address is configured in the startupconfig file, the sending of Event Log messages is reset to
enabled, regardless of the last active setting.
If no Syslog server is configured, the sending of Event Log
messages is disabled.
IP (debug type)
Disabled.
Debug commands do not affect normal message output to the
Event Log.
Using the debug event command, you can specify that Event Log messages
are sent to the debug destinations you configure (CLI session and/or
Syslog servers) in addition to the Event Log.
■
Ensure that your Syslog servers accept Debug messages.
All Syslog messages resulting from a debug operation have a “debug”
severity level. If you configure the switch to send debug messages to a
Syslog 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.)
■
Duplicate IP addresses are not stored in the list of syslog servers.
■
If the default severity value is in effect, all messages that have severities
greater than the default value are passed to syslog. For example, if the
default severity is “debug”, all messages that have severities greater than
debug are passed to syslog.
■
There is a limit of six syslog servers. All syslog servers are sent the same
messages using the same filter parameters. An error is generated for an
attempt to add more than six syslog servers.
C-55
Troubleshooting
Diagnostic Tools
Diagnostic Tools
Diagnostic Features
Feature
C-56
Default
Menu
CLI
Web
Port Auto negotiation
n/a
—
—
—
Ping test
n/a
—
page C-59
page C-58
Link test
n/a
—
page C-59
page C-58
Traceroute operation
n/a
—
page C-61
View switch configuration files
n/a
—
page C-65
View switch (show tech)
operation
n/a
—
page C-65
—
View crash information and
command history
n/a
—
page C-71
—
View system information and
software version
n/a
—
page C-71
—
Useful commands in a
troubleshooting session
n/a
—
page C-75
—
Resetting factory-default
configuration
page C-76
(Buttons)
—
page C-76
—
Restoring a flash image
n/a
—
page C-77
—
Port Status
n/a
n/a
page C-65
pages page
pages page pages page
B-10 and page B-10 and page B-10 and page
B-11
B-11
B-11
Troubleshooting
Diagnostic Tools
Port Auto-Negotiation
When a link LED does not light (indicating loss of link between two devices),
the most common reason is a failure of port auto-negotiation between the
connecting ports. If a link LED fails to light when you connect the switch to a
port on another device, do the following:
1.
Ensure that the switch port and the port on the attached end-node are
both set to Auto mode.
2.
If the attached end-node does not have an Auto mode setting, then you
must manually configure the switch port to the same setting as the endnode port. Refer to Chapter 10, “Port Status and Configuration”.
Ping and Link Tests
The Ping test and the Link test are point-to-point tests between your switch
and another IEEE 802.3-compliant device on your network. These tests can
tell you whether the switch is communicating properly with another device.
Note
To respond to a Ping test or a Link test, the device you are trying to reach must
be IEEE 802.3-compliant.
Ping Test. This is a test of the path between the switch and another device
on the same or another IP network that can respond to IP packets (ICMP Echo
Requests). To use the ping (or traceroute) command with host names or fully
qualified domain names, refer to “DNS Resolver” on page C-79.
Link Test. This is a test of the connection between the switch and a designated network device on the same LAN (or VLAN, if configured). During the
link test, IEEE 802.2 test packets are sent to the designated network device
in the same VLAN or broadcast domain. The remote device must be able to
respond with an 802.2 Test Response Packet.
C-57
Troubleshooting
Diagnostic Tools
Web: Executing Ping or Link Tests
1. Click here.
2. Click here.
3. Select Ping Test (the
default) or Link Test
4. For a Ping test, enter
the IP address of the
target device. For a
Link test, enter the
MAC address of the
target device.
6. Click on Start to begin the test.
5. Select the number of tries
(packets) and the timeout for
each try from the drop-down
menus.
Figure C-11. Link and Ping Test Screen on the Web Browser Interface
Successes indicates the number of Ping or Link packets that successfully
completed the most recent test.
Failures indicates the number of Ping or Link packets that were unsuccessful
in the last test. Failures indicate connectivity or network performance problems (such as overloaded links or devices).
Destination IP/MAC Address is the network address of the target, or destination,
device to which you want to test a connection with the switch. An IP address
is in the X.X.X.X format where X is a decimal number between 0 and 255. A
MAC address is made up of 12 hexadecimal digits, for example, 0060b0-080400.
C-58
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.
To reset the screen to its default settings, click on the Defaults button.
CLI: Ping Test
The Ping (Packet InterNet Groper) test uses Internet Control Message
Protocol (ICMP) echo requests and ICMP echo replies to determine if another
device is alive. It also measures the amount of time it takes to receive a reply
from the specified destination. The Ping command has several extended
commands that allow advanced checking of destination availability.
Syntax: ping <ip-address | hostname | switch-num> [repetitions <1-10000>]
[timeout <1-60>] [source <ip-address> | <vlan-id> | oobm] [data-size <0 65471>] [data-fill <0-1024>]
ping6 <ip-address | hostname | switch-num> [repetitions <1-10000>]
[timeout <1-60>] [source <ip-address> | <vlan-id> | oobm] [data-size <0 65471>] [data-fill <0-1024>]
Sends ICMP echo requests to determine if another device is alive.
Note: For information about ping6, see the “IPv6 Configuration
Guide” for your switch.
<ip-address | hostname>
Target IP address or hostname of the destination node being
pinged.
repetitions <1-10000>
Number of ping packets sent to the destination address.
Default: 1
timeout <1-60>
Timeout interval in seconds; the ECHO REPLY must be
received before this time interval expires for the Ping to be
successful.
Default: 5
C-59
Troubleshooting
Diagnostic Tools
source <ip-addr | oobm | vlan-id >
Source IP address, VLAN ID, or oobm. The source IP address
must be owned by the router. If a VLAN is specified, the IP
address associated with the specified VLAN is used. For
switches that have a separate out-of-band management
(OOBM) port, oobm specifies that the traffic originates from
the out-of-band management port.
data-size <0-65471>
Size of packet sent. Default: 0 (zero)
data-fill <0-1024>
The data pattern in the packet. Default: Zero length string
Basic Ping
Operation
Ping with
Repetitions
Ping with
Repetitions
and Timeout
Ping Failure
Figure C-12. Examples of Ping Tests
To halt a ping test before it concludes, press [Ctrl] [C].
Note
To use the ping (or traceroute) command with host names or fully qualified
domain names, refer to “DNS Resolver” on page C-79.
Link Tests
You can issue single or multiple link tests with varying repetitions and timeout
periods. The defaults are:
C-60
■
Repetitions: 1 (1 - 999)
■
Timeout: 5 seconds (1 - 256 seconds)
Troubleshooting
Diagnostic Tools
Syntax: link < mac-address > [repetitions < 1 - 999 >] [timeout < 1 - 256 >]
[vlan < vlan-id >]
Basic Link Test
Link Test with
Repetitions
Link Test with
Repetitions and
Timeout
Link Test Over a
Specific VLAN
Link Test Over a
Specific VLAN;
Test Fail
Figure C-13. Example of Link Tests
Traceroute Command
The traceroute command enables you to trace the route from the switch to a
host address.
This command outputs information for each (router) hop between the switch
and the destination address. Note that every time you execute traceroute, it
uses the same default settings unless you specify otherwise for that instance
of the command.
Syntax: traceroute < ip-address | hostname >
traceroute6 < ip-address | hostname >
C-61
Troubleshooting
Diagnostic Tools
Lists the IP address or hostname of each hop in the route,
plus the time in microseconds for the traceroute packet reply
to the switch for each hop.
To halt an ongoing traceroute search, press the [Ctrl] [C] keys.
Note: For information about traceroute6, see the “IPv6
Configuration Guide” for your switch.
<ip-address | hostname>
The IP address or hostname of the device to which to send the
traceroute.
[minttl < 1-255 >]
For the current instance of traceroute, changes the minimum
number of hops allowed for each probe packet sent along the
route. If minttl is greater than the actual number of hops, then
the output includes only the hops at and above the minttl
threshold. (The hops below the threshold are not listed.) If
minttl matches the actual number of hops, only that hop is
shown in the output. If minttl is less than the actual number
of hops, then all hops are listed. For any instance of
traceroute, if you want a minttl value other than the default,
you must specify that value. (Default: 1)
[maxttl < 1-255 >]
For the current instance of traceroute, changes the maximum
number of hops allowed for each probe packet sent along the
route. If the destination address is further from the switch
than maxttl allows, then traceroute lists the IP addresses for
all hops it detects up to the maxttl limit. For any instance of
traceroute, if you want a maxttl value other than the default,
you must specify that value. (Default: 30)
[timeout < 1-120 >]
For the current instance of traceroute, changes the timeout
period the switch waits for each probe of a hop in the route.
For any instance of traceroute, if you want a timeout value
other than the default, you must specify that value. (Default:
5 seconds)
[probes < 1-5 >]
For the current instance of traceroute, changes the number of
queries the switch sends for each hop in the route. For any
instance of traceroute, if you want a probes value other than
the default, you must specify that value. (Default: 3)
C-62
Troubleshooting
Diagnostic Tools
[source <ip-addr | vlan-id> | oobm]
The source IP address or VLAN. The source IP address must
be owned by the router. If a VLAN is specified, the IP address
associated with the specified VLAN is used. For switches that
have a separate out-of-band management (OOBM) port,
oobm specifies that the traffic originates from the out-ofband management port.
A Low Maxttl Causes Traceroute To Halt Before Reaching the
Destination Address. For example, executing traceroute with its default
values for a destination IP address that is four hops away produces a result
similar to this:
Intermediate router hops
with the time taken for the
switch to receive
acknowledgement of
each probe reaching each
router.
Destination IP Address
Figure C-14. Example of a Completed Traceroute Enquiry
Continuing from the previous example (Figure C-14, above), executing
traceroute with an insufficient maxttl for the actual hop count produces an
output similar to this:
Traceroute does not reach
destination IP address
because of low maxttl
setting.
The asterisk indicates there was a
timeout on the second probe to the third
hop.
Figure C-15. Example of Incomplete Traceroute Due to Low Maxttl Setting
C-63
Troubleshooting
Diagnostic Tools
If A Network Condition Prevents Traceroute from Reaching the
Destination. Common reasons for Traceroute failing to reach a destination
include:
■
Timeouts (indicated by one asterisk per probe, per hop; refer to Figure
C-15, above.)
■
Unreachable hosts
■
Unreachable networks
■
Interference from firewalls
■
Hosts configured to avoid responding
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
but the second probe
reached the router.
All further probes
within the maxttl
timed-out without
finding a router or the
destination IP
address.
An asterisk indicates a timeout
without finding the next hop.
Figure C-16. Example of Traceroute Failing to Reach the Destination Address
C-64
Troubleshooting
Viewing Switch Configuration and Operation
Viewing Switch Configuration and
Operation
In some troubleshooting scenarios, you may need to view the switch configuration to diagnose a problem. The complete switch configuration is contained in a file that you can browse from either the web browser interface or
the CLI using the commands described in this section.
CLI: Viewing the Startup or Running Configuration File
Using the CLI, you can display either the running or the startup configuration.
For more information and examples of how to use these commands, refer to
Chapter 6, “Switch Memory and Configuration”.)
Syntax: write terminal
Displays the running configuration.
show config
Displays the startup configuration.
show running-config
Displays the running-config file.
Web: Viewing the Configuration File
To display the running configuration, through the web browser interface:
1.
Click on the Diagnostics tab.
2.
Click on [Configuration Report]
3.
Use the right-side scroll bar to scroll through the configuration listing.
CLI: Viewing a Summary of Switch Operational Data
Syntax:
show tech
By default, the show tech command displays a single output of switch operating and running-configuration data from several internal switch sources,
including:
C-65
Troubleshooting
Viewing Switch Configuration and Operation
■
Image stamp (software version data)
■
Running configuration
■
Event Log listing
■
Boot History
■
Port settings
■
Status and counters — port status
■
IP routes
■
Status and counters — VLAN information
■
GVRP support
■
Load balancing (trunk and LACP)
Figure C-17 shows sample output from the show tech command.
ProCurve 6120 Blade Switch# show tech
show system
Status and Counters - General System Information
System Name
System Contact
System Location
: ProCurve 6120 Blade Switch
:
:
MAC Age Time (sec) : 300
Time Zone
: 0
Daylight Time Rule : None
Software revision
ROM Version
: Z.14.04
: Z.14.03
Base MAC Addr
Serial Number
: 002481-b00921
: TW28080080
Up Time
CPU Util (%)
: 2 hours
: 23
Memory
- Total
Free
: 33,554,432
: 21,562,672
Packet
Buffers
- Total
Free
Lowest
Missed
:
:
:
:
IP Mgmt
- Pkts Rx : 3980
Pkts Tx : 62
3022
2899
2748
0
Figure C-17. Example of Show Tech Command
To specify the data displayed by the show tech command, use the copy show
tech command as described in “Customizing show tech Command Output” on
page C-68.
C-66
Troubleshooting
Viewing Switch Configuration and Operation
Saving show tech Command Output to a Text File
When you enter the show tech command, a summary of switch operational
data is sent to your terminal emulator. You can use your terminal emulator’s
text capture features to save the show tech data to a text file for viewing,
printing, or sending to an associate to diagnose a problem.
For example, if your terminal emulator is the Hyperterminal application
available with Microsoft® Windows® software, you can copy the show tech
output to a file and then use either Microsoft Word or Notepad to display the
data. (In this case, Microsoft Word provides the data in an easier-to-read
format.)
The following example uses the Microsoft Windows terminal emulator. If you
are using a different terminal emulator application, refer to the documentation
provided with the application.
To save show tech command output from your terminal emulator to a text file,
follow these steps:
1.
In Hyperterminal, click on Transfer | Capture Text...
Figure C-18. Capture Text window of the Hyperterminal Application
2.
In the File field, enter the path and file name in which you want to store
the show tech output.
Figure C-19. Entering a Path and Filename for Saving show tech Output
3.
Click [Start] to create and open the text file.
4.
From the global configuration context, enter the show tech command:
C-67
Troubleshooting
Viewing Switch Configuration and Operation
ProCurve# show tech
The show tech command output is copied into the text file and displayed
on the terminal emulator screen. When the command output stops and
displays -- MORE --, press the Space bar to display and copy more
information. The CLI prompt appears when the command output finishes.
5.
Click on Transfer | Capture Text | Stop in HyperTerminal to stop copying data
and save the text file.
If you do not stop HyperTerminal from copying command output into the
text file, additional unwanted data can be copied from the HyperTerminal
screen.
6.
To access the file, open it in Microsoft Word, Notepad, or a similar text
editor.
Customizing show tech Command Output
Use the copy show tech command to customize the detailed switch information
displayed with the show tech command to suit your troubleshooting needs.
To customize the information displayed with the show tech command:
1.
Determine the information that you want to gather to troubleshoot a
problem in switch operation.
2.
Enter the copy show tech command to specify the data files that contain
the information you want to view.
Syntax: copy <source> show- tech
Specifies the operational and configuration data from one or
more source files to be displayed by the show tech command.
Enter the command once for each data file that you want to
include in the display.
Default: Displays data from all source files, where <source>
can be any one of the following values:
command-output “< command >”
Includes the output of a specified command in show-tech
command output. Enter the command name between
double-quotation marks; for example, copy “show system”
show-tech.
Includes the crash data from all management and interface
modules in show tech command output.
C-68
Troubleshooting
Viewing Switch Configuration and Operation
Syntax: copy <source> show- tech
crash-log [slot-id | master]:
Includes the crash logs from all management and interface
modules in show tech command output.
event-log
Copies the contents of the Event Log to show tech command
output.
running-config
Includes the contents of the running configuration file in
show tech command output.
startup-config
Includes the contents of the startup configuration file in
show tech command output.
tftp config < startup-config | running-config > < ip-addr > < remote-file >
< pc | unix >
Downloads the contents of a configuration file from a
remote host to show tech command output, where:
ip-addr: Specifies the IP address of the remote host device.
remote-file: Specifies the pathname on the remote host for
the configuration file whose contents you want to include
in the command output.
pc | unix: Specifies whether the remote host is a DOS-based
PC or UNIX workstation.
For more information on using copy tftp commands, refer
to the “File Transfers” appendix.
Syntax: copy <source> show- tech
xmodem config < startup-config | config < filename > | command-file
< filename.txt > < pc | unix >
C-69
Troubleshooting
Viewing Switch Configuration and Operation
Syntax: copy <source> show- tech
Copies the contents of a configuration file from a serially
connected PC or UNIX workstation to show tech command
output, where:
startup-config: Specifies the name of the startup
configuration file on the connected device.
config <filename >: Specifies the pathname of a
configuration file on the connected device.
pc | unix: Specifies whether the connected device is a DOSbased PC or UNIX workstation.
For more information on using copy xmodem commands,
refer to the “File Transfers” appendix.
C-70
Troubleshooting
Viewing Switch Configuration and Operation
CLI: Viewing More Information on Switch Operation
Use the following commands to display additional information on switch
operation for troubleshooting purposes.
Syntax: show boot-history
Displays the crash information saved for each management
module on the switch (see “Displaying Saved Crash
Information” in the “Redundancy (Switch 8212zl)” chapter).
See also “Example of Traceroute Failing to Reach the
Destination Address” on page C-64.
show history
Displays the current command history. This command output
is used for reference or when you want to repeat a command
(see “Repeating a Command” in the “Using the Command Line
Interface (CLI)” chapter)
show system-information
Displays globally configured parameters and information on
switch operation (see “CLI: Viewing and Configuring System
Information” in the “Interface Access and System Information”
chapter).
show version
Displays the software version currently running on the switch,
and the flash image from which the switch booted (primary or
secondary). For more information, see “Displaying
Management Information” in the “Redundancy (Switch
8212zl)” chapter.
show interfaces
Displays information on the activity on all switch ports (see
“CLI: Viewing Port Status and Configuring Port Parameters”
in the “Port Status and Configuration” chapter).
show interfaces-display
Displays the same information as the show interfaces command
and dynamically updates the output every three seconds. Press
Ctrl + C to stop the dynamic updates of system information.
Use the Arrow keys to view information that is off the screen.
C-71
Troubleshooting
Viewing Switch Configuration and Operation
Pattern Matching When Using the Show Command
The pattern matching option with the show command provides the ability to
do searches for specific text. Selected portions of the output are displayed
depending on the parameters chosen.
Syntax: show <command option> | <include | exclude | begin > <regular
expression>
Use matching pattern searches to display selected portions of
the output from a show command. There is no limit to the
number of characters that can be matched. Only regular
expressions are permitted; symbols such as the asterisk
cannot be substituted to perform more general matching.
include Only the lines that contain the matching pattern are
displayed in the output.
exclude: Only the lines that contain the matching pattern are
not displayed in the output.
begin: The display of the output begins with the line that
contains the matching pattern.
Note
Pattern matching is case-sensitive.
Below are examples of what portions of the running config file display
depending on the option chosen.
ProCurve(config)# show run | include ipv6
ipv6 enable
ipv6 enable
Displays only lines that contain “ipv6”.
ipv6 access-list "EH-01"
ProCurve(config)#
Figure C-20. Example of Pattern Matching with Include Option
C-72
Troubleshooting
Viewing Switch Configuration and Operation
ProCurve(config)# show run | exclude ipv6
Running configuration:
; J8697A Configuration Editor; Created on release #K.14.06
hostname "ProCurve Switch 5406zl"
module 1 type J8702A
module 2 type J8705A
snmp-server community "notpublic" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1-A24,B1-B20
Displays all lines that don’t contain “ipv6”.
ip address dhcp-bootp
no untagged B21-B24
exit
vlan 20
name "VLAN20"
untagged B21-B24
no ip address
exit
sequence 10 deny tcp 2001:db8:255::/48 2001:db8:125::/48
exit
no autorun
password manager
ProCurve(config)#
Figure C-21. Example of Pattern Matching with Exclude Option
C-73
Troubleshooting
Viewing Switch Configuration and Operation
ProCurve(config)# show run | begin ipv6
ipv6 enable
no untagged B21-B24
Displays the running config beginning at the first line
that contains “ipv6”.
exit
vlan 20
name "VLAN20"
untagged B21-B24
ipv6 enable
no ip address
exit
ipv6 access-list "EH-01"
sequence 10 deny tcp 2001:db8:255::/48 2001:db8:125::/48
exit
no autorun
password manager
ProCurve(config)#
Figure C-22. Example of Pattern Matching with Begin Option
Figure C-23 is an example of the show arp command output, and then the
output displayed when the include option has the IP address of 15.255.128.1 as
the regular expression.
ProCurve(config)# show arp
IP ARP table
IP Address
--------------15.255.128.1
15.255.131.19
15.255.133.150
MAC Address
----------------00000c-07ac00
00a0c9-b1503d
000bcd-3cbeec
Type
------dynamic
dynamic
dynamic
Port
---B1
B1
ProCurve(config)# show arp | include 15.255.128.1
15.255.128.1
00000c-07ac00
dynamic B1
Figure C-23. Example of the Show ARP Command and Pattern Matching with the
Include Option
C-74
Troubleshooting
Viewing Switch Configuration and Operation
CLI: Useful Commands for Troubleshooting Sessions
Use the following commands in a troubleshooting session to more accurately
display the information you need to diagnose a problem. For more information
on other CLI practices, refer to chapter 4, “Using the Command Line Interface
(CLI)”.
Syntax: alias
Creates a shortcut alias name for commonly used commands
and command options.
For more information, see ““Using a Command Alias” ” in the
“Using the Command Line Interface (CLI)” chapter.
kill
Terminates a currently running, remote troubleshooting
session. Use the show ip ssh command to list the current
management sessions.
For more information, see “Denying Interface Access by
Terminating Remote Management Sessions” in the “Interface
Access and System Information” chapter.
[no] page
Toggles the paging mode for show commands between
continuous listing and per-page listing.
repeat
Repeatedly executes one or more commands so that you can see
the results of multiple commands displayed over a period of
time. To halt the command execution, press any key on the
keyboard.
For more information, see “Repeating Execution of a
Command” in the “Using the Command Line Interface (CLI)”
chapter.
setup
Displays the Switch Setup screen from the menu interface.
C-75
Troubleshooting
Restoring the Factory-Default Configuration
Restoring the Factory-Default
Configuration
As part of your troubleshooting process, it may become necessary to return
the switch configuration to the factory default settings. This process momentarily interrupts the switch operation, clears any passwords, clears the console
Event Log, resets the network counters to zero, performs a complete self test,
and reboots the switch into its factory default configuration including deleting
an IP address. There are two methods for resetting to the factory-default
configuration:
Note
■
CLI
■
Clear/Reset button combination
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.
CLI: Resetting to the Factory-Default Configuration
This command operates at any level except the Operator level.
Syntax: erase startup-configuration
Deletes the startup-config file in flash so that the switch will
reboot with its factory-default configuration.
Note
The erase startup-config command does not clear passwords.
Clear/Reset: Resetting to the Factory-Default
Configuration
To execute the factory default reset, perform these steps:
C-76
1.
Using pointed objects, simultaneously press both the Reset and Clear
buttons on the front of the switch.
2.
Continue to press the Clear button while releasing the Reset button.
Troubleshooting
Restoring a Flash Image
3.
When the Self Test LED begins to flash, release the Clear button.
The switch will then complete its self test and begin operating with the
configuration restored to the factory default settings.
Restoring a Flash Image
The switch can lose its operating system if either the primary or secondary
flash image location is empty or contains a corrupted OS file and an operator
uses the erase flash command to erase a good OS image file from the opposite
flash location.
To Recover from an Empty or Corrupted Flash State. Use the switch’s
USB serial console to connect to a workstation or laptop computer that has
the following:
Note
■
A terminal emulator program with Xmodem capability, such as the HyperTerminal program included in Windows PC software.
■
A copy of a good OS image file for the switch.
The following procedure requires the use of Xmodem, and copies an OS image
into primary flash only.
This procedure assumes you are using HyperTerminal as your terminal
emulator. If you use a different terminal emulator, you may need to adapt this
procedure to the operation of your particular emulator.
1.
Start the terminal emulator program.
2.
Ensure that the terminal program is configured as follows:
3.
■
Baud rate: 115200
■
1 stop bit
■
No parity
■
No flow control
■
8 Bits
Use the Reset button to reset the switch. The following prompt should
then appear in the terminal emulator:
Enter h or ? for help.
=>
C-77
Troubleshooting
Restoring a Flash Image
Make sure that the switch automatically boots into ROM first.
4.
Start the Console Download utility by typing do at the => prompt and
pressing [Enter]:
=> do
5.
You will then see this prompt:
6.
At the above prompt:
a.
Type y (for Yes)
b.
Select Transfer | File in HyperTerminal.
c.
Enter the appropriate filename and path for the OS image.
d.
Select the Xmodem protocol (and not the 1k Xmodem protocol).
e.
Click on [Send].
If you are using HyperTerminal, you will see a screen similar to the
following to indicate that the download is in progress:
Figure C-24. Example of Xmodem Download in Progress
7.
C-78
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.
Troubleshooting
DNS Resolver
DNS Resolver
The Domain Name System (DNS) resolver is designed for use in local network
domains where it enables use of a host name or fully qualified domain name
with DNS-compatible switch CLI commands. (At software release K.13.01, the
DNS-compatible commands include ping and traceroute.)
Beginning with software release K.13.01, DNS operation supports both IPv4
and IPv6 DNS resolution and multiple, prioritized DNS servers. (For information on IPv6 DNS resolution, refer to the latest IPv6 Configuration Guide for
your switch.)
Terminology
Domain Suffix — Includes all labels to the right of the unique host name in
a fully qualified domain name assigned to an IP address. For example, in
the fully qualified domain name “device53.evergreen.trees.org”, the
domain suffix is “evergreen.trees.org”, while “device53” is the unique
(host) name assigned to a specific IP address.
Fully Qualified Domain Name — The sequence of labels in a domain name
identifying a specific host (host name) and the domain in which it exists.
For example, if a device with an IP address of 10.10.10.101 has a host name
of device53 and resides in the evergreen.trees.org domain, then the
device’s fully qualified domain name is device53.evergreen.trees.org and
the DNS resolution of this name is 10.10.10.101.
Host Name — The unique, leftmost label in a domain name assigned to a
specific IP address in a DNS server configuration. This enables the server to
distinguish a device using that IP address from other devices in the same
domain. For example, in the evergreen.trees.org domain, if an IPv4 address of
10.10.100.27 is assigned a host name of accounts015 and another IP address
of 10.10.100.33 is assigned a host name of sales021, then the switch configured
with the domain suffix evergreen.trees.org and a DNS server that resolves
addresses in that domain can use the host names to reach the devices with
DNS-compatible commands. For example:
ping accounts015
traceroute accounts015
C-79
Troubleshooting
DNS Resolver
Basic Operation
■
When the switch is configured with only the IP address of a DNS
server available to the switch, then a DNS-compatible command,
executed with a fully qualified domain name, can reach a device found
in any domain accessible through the configured DNS server.
■
When the switch is configured with both of the following:
•
the IP address of a DNS server available to the switch
•
the domain suffix of a domain available to the configured DNS
server
then:
•
A DNS-compatible command that includes the host name of a
device in the same domain as the configured domain suffix can
reach that device.
•
A DNS-compatible command that includes a fully qualified
domain name can reach a device in any domain that is available
to the configured DNS server.
Example. Suppose the switch is configured with the domain suffix
mygroup.procurve.net and the IP address for an accessible DNS server. If an
operator wants to use the switch to ping a target host in this domain by using
the DNS name “leader” (assigned by a DNS server to an IP address used in
that domain), then the operator can use either of the following commands:
ProCurve# ping leader
10.28.229.220 is alive, time = 1 ms
Ping Response
ProCurve# ping leader.mygroup.procurve.net
10.28.229.220 is alive, time = 1 ms
Fully Qualified Domain Name for the
Desired Host
Host Name for the Desired Host
Ping Response
Figure C-25. Example of Using Either a Host Name or a Fully Qualified Domain Name
In the proceeding example, if the DNS server’s IP address is configured on the
switch, but a domain suffix is either not configured or is configured for a
different domain than the target host, then the fully qualified domain name
must be used.
C-80
Troubleshooting
DNS Resolver
Note that if the target host is in a domain other than the domain configured
on the switch, then:
■
The host’s domain must be reachable from the switch. This requires
that the DNS server for the switch must be able to communicate with
the DNS server(s) in the path to the domain in which the target host
operates.
■
The fully qualified domain name must be used, and the domain suffix
must correspond to the domain in which the target host operates,
regardless of the domain suffix configured in the switch.
Example. Suppose the switch is configured with the domain suffix
mygroup.procurve.net and the IP address for an accessible DNS server in this
same domain. This time, the operator wants to use the switch to trace the
route to a host named “remote-01” in a different domain named
common.group.net. Assuming this second domain is accessible to the DNS
server already configured on the switch, a traceroute command using the
target’s fully qualified DNS name should succeed.
Fully Qualified Host Name for
ProCurve# traceroute remote-01.common.group.net
the Target Host
traceroute to 10.22.240.73
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 10.28.229.3
0 ms
0 ms
0 ms
2 10.71.217.1
0 ms
0 ms
0 ms
3 10.0.198.2
1 ms
0 ms
0 ms
IP Address for Target Host
4 10.22.240.73
0 ms
0 ms
0 ms
“remote-01”
Figure C-26. Example Using the Fully Qualified Domain Name for an Accessible Target in Another Domain
Configuring and Using DNS Resolution with
DNS-Compatible Commands
(At software release K.13.01, the DNS-compatible commands include ping and
traceroute.)
1.
Determine the following:
a.
The IP address for a DNS server operating in a domain in your
network
b.
The priority (1 - 2) of the selected server, relative to other DNS servers
in the domain
C-81
Troubleshooting
DNS Resolver
c.
The domain name for an accessible domain in which there are hosts
you want to reach with a DNS-compatible command. (This is the
domain suffix in the fully qualified domain name for a given host
operating in the selected domain. Refer to “Terminology” on page C79.) Note that if a domain suffix is not configured, fully qualified
domain names can be used to resolve DNS-compatible commands.
d. the host names assigned to target IP addresses in the DNS server for
the specified domain
2.
Use the data from steps 1a through 1c to configure the DNS entry on the
switch.
3.
Use a DNS-compatible command with the host name to reach the target
devices.
Configuring a DNS Entry
The switch allows up to three DNS server entries (IP addresses for DNS
servers). One domain suffix can also be configured to support resolution of
DNS names in that domain by using a host name only. Including the domain
suffix enables the use of DNS-compatible commands with a target’s host name
instead of the target’s fully qualified domain name.
.
Syntax: [no] ip dns server-address priority < 1 - 2 > < ip-addr > [oobm]
Configures the access priority and IP address of a DNS server accessible to the
switch. These settings specify:
• the relative priority of the DNS server when multiple servers are configured
• the IP address of the DNS server
• optionally, for switches that have a separate out-of-band-management (OOBM)
port, that DNS access goes through that out-of-band management port
These settings must be configured before a DNS-compatible command can be
executed with host name criteria.
The switch supports three prioritized DNS server entries. Configuring another IP
address for a priority that has already been assigned to an IP address is not allowed.
To replace one IP address at a given priority level with another address having the
same priority, you must first use the no form of the command to remove the
unwanted address. Also, only one instance of a given server address is allowed in
the server list. Attempting to enter a duplicate of an existing entry at a different
priority level is not allowed. To change the priority of an existing server address,
use the no form of the command to remove the entry, then re-enter the address with
the new priority.
The no form of the command replaces the configured IP address with the null setting.
(Default: null)
C-82
Troubleshooting
DNS Resolver
Syntax: [no] ip dns domain-name < domain-name-suffix >
This optional DNS command configures the domain suffix that is automatically
appended to the host name entered with a DNS-compatible command. When the
domain suffix and the IP address for a DNS server that can access that domain are
both configured on the switch, you can execute a DNS-compatible command using
only the host name of the desired target. (For an example, refer to Figure C-25 on
page C-80.) In either of the following two instances, you must manually provide the
domain identification by using a fully qualified DNS name with a DNS-compatible
command:
• If the DNS server IP address is configured on the switch, but the domain suffix
is not configured (null)
• The domain suffix configured on the switch is not the domain in which the target
host exists
The switch supports one domain suffix entry and three DNS server IP address
entries. (Refer to the preceding command description.)
The no form of the command replaces the configured domain suffix with the null
setting. (Default: null)
Example Using DNS Names with Ping and Traceroute
In the network illustrated in Figure C-27, the switch at 10.28.192.1 is configured to use DNS names for DNS-compatible commands in the
pubs.outdoors.com domain. The DNS server has been configured to assign the
host name docservr to the IP address used by the document server
(10.28.229.219).
Switch “A” Configured
with DNS Resolver
10.28.192.1
Router “B”
Document
Server
10.28.192.2
docservr
10.28.229.1
(10.28.229.219)
DNS Server for pubs.outdoors.com
10.28.229.10
Domain: pubs.outdoors.com
Host Name for IP address
10.28.229.219 = “docservr”
Figure C-27. Example Network Domain
C-83
Troubleshooting
DNS Resolver
Configuring switch “A” with the domain name and the IP address of a DNS
server for the domain enables the switch to use host names assigned to IP
addresses in the domain to perform ping and traceroute actions on the devices
in the domain. To summarize:
Entity:
Identity:
DNS Server IP Address
10.28.229.10
Domain Name (and Domain Suffix for Hosts in
the Domain)
pubs.outdoors.com
Host Name Assigned to 10.28.229.219 by the
docservr
DNS Server
Fully Qualified Domain Name for the IP address docservr.pubs.outdoors.com
Used By the Document Server (10.28.229.219)
Switch IP Address
10.28.192.1
Document Server IP Address
10.28.229.219
With the above already configured, the following commands enable a DNScompatible command with the host name docserver to reach the document
server at 10.28.229.219.
ProCurve(config)# ip dns server-address 10.28.229.10
ProCurve(config)# ip dns domain-name pubs.outdoors.com
Figure C-28. Configuring Switch “A” in FigureC-27 To Support DNS Resolution
ProCurve# ping docservr
10.28.229.219 is alive, time = 1 ms
ProCurve# traceroute docservr
First-Hop Router (“B”)
traceroute to 10.28.229.219
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 10.28.192.2
1 ms
0 ms
0 ms
2 10.28.229.219
0 ms
0 ms
0 ms
Traceroute Target
Figure C-29. Example of Ping and Traceroute Execution for the Network in Figure C-27 on Page C-83
C-84
Troubleshooting
DNS Resolver
As mentioned under “Basic Operation” on page C-80, if the DNS entry configured in the switch does not include the domain suffix for the desired target,
then you must use the target host’s fully qualified domain name with DNScompatible commands. For example, using the document server in Figure C27 as a target:
ProCurve# ping docservr.pubs.outdoors.com
10.28.229.219 is alive, time = 1 ms
Target’s Fully Qualified
Domain Name
ProCurve# traceroute docservr.pubs.outdoors.com
traceroute to 10.28.229.219
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 10.28.192.2
1 ms
0 ms
0 ms
2 10.28.229.219
0 ms
0 ms
0 ms
Figure C-30. Example of Ping and Traceroute Execution When Only the DNS Server IP Address Is Configured
Viewing the Current DNS Configuration
The show ip command displays the current domain suffix and the IP address
of the highest priority DNS server configured on the switch, along with other
IP configuration information. If the switch configuration currently includes a
non-default (non-null) DNS entry, it will also appear in the show run command
output.
ProCurve# show ip
Internet (IP) Service
IP Routing : Disabled
Default Gateway
Default TTL
Arp Age
Domain Suffix
DNS server
:
:
:
:
:
10.28.192.2
64
20
pubs.outdoors.com
10.28.229.10
DNS Resolver Configuration in the
show ip command output
VLAN
| IP Config IP Address
Subnet Mask
------------ + ---------- --------------- --------------DEFAULT_VLAN | Manual
10.28.192.1
255.255.255.0
Figure C-31. Example of Viewing the Current DNS Configuration
C-85
Troubleshooting
DNS Resolver
Operating Notes
C-86
■
Configuring another IP address for a priority that has already been
assigned to an IP address is not allowed. To replace one IP address at a
given priority level with another address having the same priority, you
must first use the no form of the command to remove the unwanted
address. Also, only one instance of a given server address is allowed in
the server list. Attempting to enter a duplicate of an existing entry at a
different priority level is not allowed. To change the priority of an existing
server address, use the no form of the command to remove the entry, then
re-enter the address with the new priority.
■
To change the position of an address already configured with priority x,
you must first use no ip dns server-address priority x < ip-addr > to remove
the address from the configuration, then use ip dns server-address priority
< ip-addr > to reconfigure the address with the new priority. Also, if the
priority to which you want to move an address is already used in the
configuration for another address, you must first use the no form of the
command to remove the current address from the target priority.
■
The DNS server(s) and domain configured on the switch must be
accessible to the switch, but it is not necessary for any intermediate
devices between the switch and the DNS server to be configured to
support DNS operation.
■
When multiple DNS servers are configured on the switch, they can
reside in the same domain or different domains.
■
A DNS configuration must include the IP address for a DNS server
that is able to resolve host names for the desired domain. If a DNS
server has limited knowledge of other domains, then its ability to
resolve DNS-compatible command requests is also limited.
■
If the DNS configuration includes a DNS server IP address but does
not also include a domain suffix, then any DNS-compatible
commands should include the target host’s fully qualified domain
name. Refer to Figure C-25 on page C-80.
■
Switch-Initiated DNS packets go out through the VLAN having the
best route to the DNS server, even if a Management VLAN has been
configured.
■
The DNS server address must be manually input. It is not automatically determined via DHCP.
Troubleshooting
DNS Resolver
Event Log Messages
Message
Meaning
DNS server address not configured
The switch does not have an IP address configured for the DNS
server.
DNS server not responding
The DNS server failed to respond or is unreachable. An incorrect
server IP address can produce this result.
Unknown host < host-name >
The host name did not resolve to an IP address. Some reasons for
this occurring include:
• The host name was not found.
• The named domain was not found.
• The domain suffix was expected, but has not been configured. (If
the server’s IP address has been configured in the switch but the
domain name has not been configured, then the host’s fully
qualified domain name must be used.)
C-87
D
MAC Address Management
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Determining MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Menu: Viewing the Switch’s MAC Addresses . . . . . . . . . . . . . . . . . . . . D-4
CLI: Viewing the Port and VLAN MAC Addresses . . . . . . . . . . . . . . . . D-5
Viewing the MAC Addresses of Connected Devices . . . . . . . . . . . . . D-7
D-1
MAC Address Management
Overview
Overview
The switch assigns MAC addresses in these areas:
■
For management functions, one Base MAC address is assigned to the
default VLAN (VID = 1). (All VLANs on the switches covered in this guide
use the same MAC address.)
■
For internal switch operations: One MAC address per port (Refer to “CLI:
Viewing the Port and VLAN MAC Addresses” on page D-5.)
MAC addresses are assigned at the factory. The switch automatically
implements these addresses for VLANs and ports as they are added to the
switch.
Note
D-2
The switch’s base MAC address is also printed on a label affixed to the switch.
MAC Address Management
Determining MAC Addresses
Determining MAC Addresses
MAC Address Viewing Methods
Feature
Menu
CLI
Web
view switch’s base (default vlan) MAC address n/a
and the addressing for any added VLANs
D-4
D-5
—
view port MAC addresses (hexadecimal format) n/a
—
D-5
—
■
Note
Default
Use the menu interface to view the switch’s base MAC address and the
MAC address assigned to any VLAN you have configured on the switch.
(The same MAC address is assigned to VLAN1 and all other VLANs
configured on the switch.)
The switch’s base MAC address is used for the default VLAN (VID = 1) that is
always available on the switch. This is true for dynamic VLANs as well; the
base MAC address is the same across all VLANs.
■
Use the CLI to view the switch’s port MAC addresses in hexadecimal
format.
D-3
MAC Address Management
Determining MAC Addresses
Menu: Viewing the Switch’s MAC Addresses
The Management Address Information screen lists the MAC addresses for:
■
Base switch (default VLAN; VID = 1)
■
Any additional VLANs configured on the switch.
Also, the Base MAC address appears on a label on the back of the switch.
Note
The Base MAC address is used by the first (default) VLAN in the switch. This
is usually the VLAN named “DEFAULT_VLAN” unless the name has been
changed (by using the VLAN Names screen). On the switches covered in this
guide, the VID (VLAN identification number) for the default VLAN is always
“1”, and cannot be changed.
To View the MAC Address (and IP Address) assignments for VLANs
Configured on the Switch:
1.
From the Main Menu, Select
1. Status and Counters
2. Switch Management Address Information
If the switch has only the default VLAN, the following screen appears. If
the switch has multiple static VLANs, each is listed with its address data.
Switch Base (or Default
VLAN) MAC address
Current IP Address
Assigned to the Switch
Figure D-1. Example of the Management Address Information Screen
D-4
MAC Address Management
Determining MAC Addresses
CLI: Viewing the Port and VLAN MAC Addresses
The MAC address assigned to each switch port is used internally by such
features as Flow Control and the spanning-tree protocol. Using the walkmib
command to determine the MAC address assignments for individual ports can
sometimes be useful when diagnosing switch operation.
Switch
MAC Address Allocation
6120G/XG
6120XG
The switch’s base MAC address is assigned to VLAN (VID) 1 and
appears in the walkmib listing after the MAC addresses for the ports.
(All VLANs in the switch have the same MAC address.)
To display the switch’s MAC addresses, use the walkmib command at the
command prompt:
Note
This procedure displays the MAC addresses for all ports and existing VLANs
in the switch, regardless of which VLAN you select.
1.
If the switch is at the CLI Operator level, use the enable command to enter
the Manager level of the CLI.
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, a ProCurve 8212zl switch with the following module configuration shows MAC address assignments similar to those shown in figure D-2:
■
a 4-port module in slot A, a 24-port module in slot C, and no modules in
slots B and D
■
two non-default VLANs configured
D-5
MAC Address Management
Determining MAC Addresses
ProCurve# walkmib ifphysaddress
ifPhysAddress.1 = 00 12 79 88 b1 ff
ifPhysAddress.2 = 00 12 79 88 b1 fe
ifPhysAddress.3 = 00 12 79 88 b1 fd
ifPhysAddress.4 = 00 12 79 88 b1 fc
ifPhysAddress.49 = 00 12 79 88 b1 cf
ifPhysAddress.50 = 00 12 79 88 b1 ce
ifPhysAddress.51 = 00 12 79 88 b1 cd
ifPhysAddress.52 = 00 12 79 88 b1 cc
ifPhysAddress.53 = 00 12 79 88 b1 cb
ifPhysAddress.54 = 00 12 79 88 b1 ca
ifPhysAddress.55 = 00 12 79 88 b1 c9
ifPhysAddress.56 = 00 12 79 88 b1 c8
ifPhysAddress.57 = 00 12 79 88 b1 c7
ifPhysAddress.58 = 00 12 79 88 b1 c6
ifPhysAddress.59 = 00 12 79 88 b1 c5
ifPhysAddress.60 = 00 12 79 88 b1 c4
ifPhysAddress.61 = 00 12 79 88 b1 c3
ifPhysAddress.62 = 00 12 79 88 b1 c2
ifPhysAddress.63 = 00 12 79 88 b1 c1
ifPhysAddress.64 = 00 12 79 88 b1 c0
ifPhysAddress.65 = 00 12 79 88 b1 bf
ifPhysAddress.66 = 00 12 79 88 b1 be
ifPhysAddress.67 = 00 12 79 88 b1 bd
ifPhysAddress.68 = 00 12 79 88 b1 bc
ifPhysAddress.69 = 00 12 79 88 b1 bb
ifPhysAddress.70 = 00 12 79 88 b1 ba
ifPhysAddress.71 = 00 12 79 88 b1 b9
ifPhysAddress.72 = 00 12 79 88 b1 b8
ifPhysAddress.362 = 00 12 79 88 a1 00
ifPhysAddress.461 = 00 12 79 88 a1 00
ifPhysAddress.488 = 00 12 79 88 a1 00
ifPhysAddress.4456 =
ifPhysAddress.1 - 4: Ports A1 - A4 in Slot A
(Addresses 5 - 24 in slot A are unused.)
ifPhysAddress.49 - 72:Ports C1 - C24 in Slot C
(In this example, there is no module in slot B.)
ifPhysAddress.362
ifPhysAddress.461 and
488
Figure D-2. Example of Port MAC Address Assignments on a Switch
D-6
Base MAC Address (MAC
Address for default VLAN;
VID = 1)
Physical addresses for
non-default VLANs configured
on the switch. On the switches
covered by this manual, all
VLANs use the same MAC
address as the Default VLAN.
Refer to "Multiple VLAN Considerations" in the "Static Virtual
LANs (VLANs)" chapter of the
Advanced Traffic Management
Guide for your switch.
MAC Address Management
Viewing the MAC Addresses of Connected Devices
Viewing the MAC Addresses of
Connected Devices
Syntax: show mac-address [ | mac-addr |
Lists the MAC addresses of the devices the switch has detected,
along with the number of the specific port on which each MAC
address was detected.
[ port-list ]
Lists the MAC addresses of the devices the switch has detected, on
the specified port(s).
[ mac-addr ]
Lists the port on which the switch detects the specified MAC
address. Returns the following message if the specified MAC
address is not detected on any port in the switch:
MAC address < mac-addr > not found.
[ vlan < vid > ]
Lists the MAC addresses of the devices the switch has detected on
ports belonging to the specified VLAN, along with the number of
the specific port on which each MAC address was detected.
To list the MAC addresses of devices the switch has detected, use the show
mac-address command.
D-7
E
Monitoring Resources
Contents
Viewing Information on Resource Usage . . . . . . . . . . . . . . . . . . . . . . . E-2
Policy Enforcement Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
When Insufficient Resources Are Available . . . . . . . . . . . . . . . . . . . . E-3
E-1
Monitoring Resources
Viewing Information on Resource Usage
Viewing Information on Resource Usage
The switch allows you to view information about the current usage and
availability of resources in the Policy Enforcement engine, including the
following software features:
■
QoS through RADIUS authentication designated as “IDM”, with or without
the optional identity-driven management (IDM) application
■
Virus throttling (VT) using connection-rate filtering
■
Mirror policies. Other features, including:
•
Management VLAN
•
DHCP snooping
•
Dynamic ARP protection
•
Jumbo IP-MTU
Policy Enforcement Engine
The Policy Enforcement engine is the hardware element in the switch that
manages quality-of-service, as well as other software features, using the rules
that you configure. Resource usage in the Policy Enforcement engine is based
on how these features are configured on the switch.
Resource usage by virus-throttling is determined as follows:
■
A virus-throttling configuration (connection-rate filtering) on the switch
does not affect switch resources unless traffic behavior has triggered
either a throttling or blocking action on the traffic from one or more
clients. When the throttling action ceases or a blocked client is unblocked,
the resources used for that action are released.
Resource usage by the following features (when configured globally or per
VLAN), applies across all port groups (or slots with installed modules):
■
QoS configurations that use the following commands:
QoS device priority (IP Address) through the CLI using the qos
device-priority command
Management VLAN configuration
Jumbo IP-MTU
•
■
■
Resource usage on the following features, which are configured per-port,
applies only to the slot or port group on which the feature is configured:
■
■
E-2
QoS applied per-port or per-user through RADIUS authentication
QoS policies per port through the CLI using service
Monitoring Resources
When Insufficient Resources Are Available
When Insufficient Resources Are
Available
The switch has ample resources for configuring features and supporting:
Note
■
RADIUS-authenticated clients (with or without the optional IDM application)
■
Virus throttling and blocking on individual clients.
Virus throttling does not operate on IPv6 traffic.
If the resources supporting these features become fully subscribed:
Note
■
The current feature configuration, RADIUS-authenticated client sessions,
and virus throttling instances continue to operate normally.
■
The switch generates an event log notice to say that current resources are
fully subscribed.
■
Currently engaged resources must be released before any of the following
actions are supported:
•
Configuration of new entries for QoS, IDM, virus throttling, and other
features (Management VLAN, DHCP snooping, dynamic ARP
protection).
•
Acceptance of new RADIUS-based client authentication requests
(displayed as a new resource entry for IDM).
Failure to authenticate a client that presents valid credentials may indicate that insufficient resources are available for the features configured
for the client in the RADIUS server. To troubleshoot, check the event log.
•
Throttling or blocking of newly detected clients with a high rate of
connection requests (as defined by the current virus-throttling
configuration).
The switch continues to generate event log notifications (and SNMP
trap notification, if configured) for new instances of high connectionrate behavior detected by the virus-throttling feature.
E-3
F
Daylight Savings Time on ProCurve Switches
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” (no time changes), there are five pre-defined settings, named:
■
Alaska
■
Canada and Continental US
■
Middle Europe and Portugal
■
Southern Hemisphere
■
Western Europe
The pre-defined settings follow these rules:
Alaska:
•
Begin DST at 2am on the second Sunday in March.
•
End DST at 2am on the first Sunday in November.
Canada and Continental US:
•
Begin DST at 2am on the second Sunday in March.
•
End DST at 2am on the first Sunday in November.
F-1
Daylight Savings Time on ProCurve Switches
Middle Europe and Portugal:
•
Begin DST at 2am the first Sunday on or after March 25th.
•
End DST at 2am the first Sunday on or after September 24th.
Southern Hemisphere:
•
Begin DST at 2am the first Sunday on or after October 25th.
•
End DST at 2am the first Sunday on or after March 1st.
Western Europe:
•
Begin DST at 2am the first Sunday on or after March 23rd.
•
End DST at 2am the first Sunday on or after October 23rd.
A sixth option named “User defined” allows you to customize the DST configuration by entering the beginning month and date plus the ending month and
date for the time change. The menu interface screen looks like this (all month/
date entries are at their default values):
===========================- TELNET - MANAGER MODE -============================
Switch Configuration - System Information
System Name : ProCurve 6120 Blade Switch
System Contact :
System Location :
Inactivity Timeout (min) [0] : 0
MAC Age Time (sec) [300] : 300
Inbound Telnet Enabled [Yes] : Yes Web Agent Enabled [Yes] : Yes
Time Sync Method [None] : TIMEP
TimeP Mode [Disabled] : Disabled
Tftp-enable [Yes] : Yes
Jumbo Max Frame Size [9216] : 9216
Time Zone [0] : 0
Select User-defined and press [v] to
Daylight Time Rule [None] : User-defined
display the remaining parameters.
Beginning month [April] : April
Beginning day [1] : 1
Ending month [October] : October
Ending day [1] : 1
Actions-> Cancel
Edit
Save
Help
Edit the fields displayed above.
Use arrow keys to change action selection and <Enter> to execute action.
Figure F-1. Menu Interface with “User-Defined” Daylight Time Rule Option
F-2
Daylight Savings Time on ProCurve Switches
Before configuring a “User defined” Daylight Time Rule, it is important to
understand how the switch treats the entries. The switch knows which dates
are Sundays, and uses an algorithm to determine on which date to change the
system clock, given the configured “Beginning day” and “Ending day”:
■
If the configured day is a Sunday, the time changes at 2am on that day.
■
If the configured day is not a Sunday, the time changes at 2am on the first
Sunday after the configured day.
This is true for both the “Beginning day” and the “Ending day”.
With that algorithm, one should use the value “1” to represent “first Sunday of
the month”, and a value equal to “number of days in the month minus 6" to
represent “last Sunday of the month”. This allows a single configuration for
every year, no matter what date is the appropriate Sunday to change the clock.
F-3
G
Network Out-of-Band Management (OOBM)
Contents
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5
OOBM and Switch Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7
OOBM enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-8
OOBM port enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-9
OOBM IPv4 address configuration . . . . . . . . . . . . . . . . . . . . . . . G-10
OOBM IPv4 default gateway configuration . . . . . . . . . . . . . . . . G-10
OOBM Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-11
Show OOBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-11
Show OOBM IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . G-12
Show OOBM ARP information . . . . . . . . . . . . . . . . . . . . . . . . . . . G-12
Application Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-13
Application Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-15
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-16
G-1
Network Out-of-Band Management (OOBM)
Concepts
Concepts
Management communications with a managed switch can be either:
■
in band — through the networked data ports of the switch
or:
■
out of band — through a dedicated management port (or ports) separate
from the data ports
Out-of-band ports have typically been serial console ports using DB-9 or
specially wired 8-pin modular (RJ-style) connectors. The HP ProCurve 6120G/
XG and 6120XG switches have a networked out-of-band management port
available to them through the dedicated networked management port in the
C-class enclosure Onboard Administrator (OA) module. The illustrations
below shows management connections for the two switches and the OA.
Note
For instructions on how to use the OOBM serial interface, see the Installation
and Getting Started Guide.
USB console port
(serial, out of band)
Figure G-1. 6120G/XG Management Ports
USB console port
(serial, out of band)
Figure G-2. 6120XG Management Ports
G-2
Network Out-of-Band Management (OOBM)
Concepts
management port
(networked, out of band)
Figure D-1. C-class enclosure OA Management port
Out-of-band management (OOBM) operates on a “management plane” that is
separate from the “data plane” used by data traffic on the switch and by inband management traffic. That separation means that out-of-band management can continue to function even during periods of traffic congestion,
equipment malfunction, or attacks on the network. In addition, it can provide
improved switch security: a properly configured switch can limit management
access to the management port only, preventing malicious attempts to gain
access via the data ports.
Network OOBM typically occurs on a management network that connects
multiple switches. It has the added advantage that it can be done from a central
location and does not require an individual physical cable from the management station to each switch’s console port.
The table below summarizes the switch management ports.
Table A-1.
Switch Management Ports
In Band
Networked
Out Of Band
Directly connected
Networked
Management interface
command line (CLI), menu, Web command line (CLI), menu
command line (CLI), menu
Communication plane
data plane
management plane
management plane
Connection port
any data port
dedicated serial or USB
console port
dedicated networked
management port
Connector type
usually RJ-45; also CX4, SFP,
SFP+, and XFP
OA C-class DB9 serial
Mini-b USB
G-3
Network Out-of-Band Management (OOBM)
Concepts
In Band
Networked
Out Of Band
Directly connected
Networked
Advantages
allows centralized
management
not affected by events on
data network, shows boot
sequence
not affected by events on
data network; allows
centralized management;
allows improved security
Disadvantages
can be affected by events on
data network; does not show
boot sequence
requires PC to directly
connect to USB connector;
networked terminal server
needs to be attached to OA
serial port
does not show boot
sequence
G-4
Network Out-of-Band Management (OOBM)
Concepts
Example
In a typical data center installation, blade switches in a C-class enclosure
connect servers to the data network, while the management port of the OA
module in the C-class enclosure connects the switches to a physically and
logically separate management network. This allows network administrators
to manage the switches even if operation on the data network is disrupted.
In the illustration below, the switches face the hot aisle of the data center,
allowing easy connection to the network ports on the backs of the servers.
Figure D-2. Network out-of-band management in a data center
For even more control, the serial console ports of the switches could be
connected to the management network through a serial console server (essentially, a networked serial switch), allowing the network administrators to view
the CLI activity of each switch at boot time and to control the switches through
the console ports (as well as through the management ports).
G-5
Network Out-of-Band Management (OOBM)
Concepts
OOBM and Switch Applications
The table below shows the switch applications that are supported on the
OOBM interface as well as on the data interfaces. In this list, some applications
are client-only, some are server-only, and some are both.
Application
Inbound OOBM Outbound OOBM
(server)
(client)
Inbound Data
Plane (server)
Outbound Data
Plane (client)
Telnet
yes
yes
yes
yes
SSH
yes
n/a
yes
n/a
SNMP
yes
yes*
yes
yes
TFTP
yes
yes
yes
yes
HTTP
yes
n/a
yes
n/a
SNTP
n/a
yes
n/a
yes
TIMEP
n/a
yes
n/a
yes
RADIUS
n/a
yes
n/a
yes
TACACS
n/a
yes
n/a
yes
DNS**
n/a
yes
n/a
yes
Syslog
n/a
yes
n/a
yes
Ping
yes***
yes
yes***
yes
Traceroute
yes***
yes
yes***
yes
n/a = not applicable
* = SNMP client refers to SNMP traps as they originate from the switch.
** = DNS has a limit of two servers — primary and secondary. Either can be configured to
use the OOBM interface.
*** = Ping and Traceroute do not have explicit servers. Ping and Traceroute responses are
sent by the host stack.
For applications that have servers, oobm/data/both options have been added to
listen mode. There is now a listen keyword in the CLI commands to allow
selection of those options. Default value is both for all servers. See the Application Server Commands (page G-13) in the “Tasks” section below for details
of the new command syntax.
G-6
Network Out-of-Band Management (OOBM)
Tasks
Tasks
OOBM Configuration
OOBM context
OOBM configuration commands can be issued from the global configuration
context (config) or from a specific OOBM configuration context (oobm). To
enter the OOBM configuration context from the general configuration context, use the oobm command.
Syntax: oobm
Enters the OOBM context from the general configuration
context.
For example:
ProCurve (config)# oobm
ProCurve (oobm)#
G-7
Network Out-of-Band Management (OOBM)
Tasks
OOBM enable/disable
To enable or disable network OOBM, use the enable or disable command.
Network OOBM is enabled by default.
Syntax:
From the OOBM context:
enable
disable
From the general configuration context:
oobm enable
oobm disable
Enables or disables networked out-of-band-management on
the switch.
OOBM is not compatible with either a management VLAN or
stacking. If you attempt to enable OOBM when a management
VLAN is enabled or when stacking is enabled, the command
will be rejected and you will receive an error message.
If an OOBM IP address exists and you disable OOBM, the
OOBM IP address configuration is maintained. If you enable
OOBM and there is a pre-existing OOBM IP address, it will
be reinstated.
Examples:
ProCurve (oobm)# enable
ProCurve (oobm)# disable
ProCurve (config)# oobm enable
ProCurve (config)# oobm disable
G-8
Network Out-of-Band Management (OOBM)
Tasks
OOBM port enable/disable
The OOBM interface command enables or disables the OOBM interface (the
OOBM port, as opposed to the OOBM function).
Syntax:
From the OOBM context:
interface [enable | disable]
From the general configuration context:
oobm interface [enable | disable]
Enables or disables the networked OOBM interface (port).
For example:
ProCurve (oobm)# interface enable
ProCurve (config)# oobm interface disable
G-9
Network Out-of-Band Management (OOBM)
Tasks
OOBM IPv4 address configuration
Configuring an IPv4 address for the OOBM interface is similar to VLAN IP
address configuration, but it is accomplished within the OOBM context.
Syntax:
From the OOBM context:
[no] ip address [dhcp-bootp | ip-address/mask-length]
From the general configuration context:
[no] oobm ip address [dhcp-bootp | ip-address/mask-length]
Configures an IPv4 address for the switch’s OOBM interface.
You can configure an IPv4 address even when global OOBM
is disabled; that address will become effective when OOBM is
enabled.
For example:
ProCurve (oobm)# ip address 10.1.1.17/24
OOBM IPv4 default gateway configuration
Configuring an IPv4 default gateway for the OOBM interface is similar to VLAN
default gateway configuration, but it is accomplished within the OOBM context.
Syntax:
From the OOBM context:
[no] ip default-gateway ip-address
From the general configuration context:
[no] oobm ip default-gateway ip-address
Configures an IPv4 default gateway for the switch’s OOBM
interface.
For example:
ProCurve (oobm)# ip default-gateway 10.1.1.1
G-10
Network Out-of-Band Management (OOBM)
Tasks
OOBM Show Commands
The show commands for OOBM are similar to the analogous commands for
the data plane. Note that you must always include the oobm parameter to see
the information for the OOBM interface, regardless of the context. For
instance, even from the OOBM context the show ip command displays the IP
configuration for the data plane; to see the IP configuration of the OOBM
interface you need to use show oobm ip.
Show OOBM
This command shows the global OOBM and OOBM port configurations.
Syntax: show oobm
Summarizes OOBM configuration information. This command displays the global OOBM configuration (enabled or
disabled), the OOBM interface status (up or down) and the
port status (enabled/disabled, duplex, and speed).
You can issue this command from any context.
For example:
ProCurve# show oobm
Global Configuration
OOBM Enabled
OOBM Port Type
OOBM Interface Status
OOBM Port
OOBM Port Speed
:
:
:
:
:
Yes
10/100TX
Up
Enabled
Auto
G-11
Network Out-of-Band Management (OOBM)
Tasks
Show OOBM IP configuration
Use show oobm ip to see the IP configuration of the OOBM interface.
Syntax: show oobm ip
Summarizes the IP configuration of the OOBM interface. This
command displays the status of IPv4 (enabled/disabled), the
IPv4 default gateway, and the IPv4 address configured for the
interface.
You can issue this command from any context.
For example:
ProCurve# show oobm ip
Show OOBM ARP information
Use show oobm arp to see the ARP table entries for the OOBM interface.
Syntax: show oobm arp
Summarizes the ARP table entries for the OOBM interface.
You can issue this command from any context.
ProCurve# show oobm arp
G-12
Network Out-of-Band Management (OOBM)
Tasks
Application Server Commands
Application servers (as described in OOBM and Server Applications in the
Concepts section above) have added a listen keyword with oobm|data|both
options to specify which interface(s) is(are) active.
Default value is both for all servers.
For example:
Telnet: telnet-server [listen <oobm | data | both>]
Management and Configuration Guide, page 7-6
SSH: ip ssh [listen <oobm | data | both>]
Access Security Guide, page 6-16
SNMP: snmp-server [listen <oobm | data | both>]
Management and Configuration Guide, page 13-34
TFTP: tftp server [listen <oobm | data | both>]
Management and Configuration Guide, page A-9
HTTP: web-management [listen <oobm | data | both>]
Management and Configuration Guide, page 7-7
In all cases, show running-config will display the server configurations.
Use the no form of the command to prevent the server from running on either
interface. For example:
Telnet: no telnet-server
SSH: no ip ssh
SNMP: no snmp-server
TFTP: no tftp server
HTTP: no web-management
G-13
Network Out-of-Band Management (OOBM)
Tasks
The show servers command shows the listen mode of the servers.
ProCurve# show servers
Server listen mode
Server
Listen mode
----------------------------Telnet
|
both
Ssh
|
both
Tftp
|
both
Web-management |
both
Snmp
|
both
G-14
Network Out-of-Band Management (OOBM)
Tasks
Application Client Commands
CLI commands for client applications have added the oobm keyword to allow
you to specify that the outgoing request be issued from the OOBM interface.
If you do not specify the oobm keyword, the request will be issued from the
appropriate in-band data interface. Command syntax is:
Telnet: telnet <ip-address> [oobm]
Management and Configuration Guide, page 7-6
TFTP: copy tftp ... <ip-address> <filename> ... [oobm]
Management and Configuration Guide, page A-7 and following
SNTP: [no] sntp server priority <priority> <ip-address> [oobm] [version]
Management and Configuration Guide, page 9-11
TIMEP: [no] ip timep <dhcp | manual <ip-address> [oobm] > [...]
Management and Configuration Guide, page 9-22
RADIUS: [no] radius-server host <ip-address> [oobm]
Access Security Guide, page 3-17, page 5-14, page 10-25
TACACS+: [no] tacacs-server host <ip-address> [oobm]
Access Security Guide, page 4-18
DNS: [no] ip dns server-address priority <priority> <ip-address> [oobm]
Management and Configuration Guide, page C-82
Syslog: [no] logging <ip-address> [control-descr] | [oobm]]
Management and Configuration Guide, page C-49
Ping: ping [...] [source < ip-address | vlan-id | oobm>]
Management and Configuration Guide, page C-59
Traceroute: traceroute [...] [source <ip-address | vlan-id | oobm>]
Management and Configuration Guide, page C-61
G-15
Network Out-of-Band Management (OOBM)
Tasks
Example
This example shows setup and use of network OOBM using the commands
described above.
Assume that the figure below describes how you want to set up your data
center.
Figure D-3. Example data center
Assume that you are configuring the switch in the left-hand rack to communicate on both the data and management networks. You might do the following:
■
Configure an IP address on the data network.
■
Verify that out-of-band management is enabled. (It is enabled by default.)
■
Configure an IP address on the management network.
■
Verify that the switch can communicate on both networks.
The CLI commands that follow would accomplish those tasks. (The first time
through the process you might easily make the omission shown near the end
of the example.)
G-16
Network Out-of-Band Management (OOBM)
Tasks
Switch
Switch
Switch
Switch
Switch
41# config
41(config)# vlan 1
41(vlan-1)# ip address 10.1.129.7/20
41(vlan-1)# end
41# show oobm
Global Configuration
OOBM Enabled
OOBM Port Type
OOBM Interface Status
OOBM Port
OOBM Port Speed
:
:
:
:
:
Yes
10/100TX
Up
Enabled
Auto
Set up IP address on data network.
Exit back to manager context.
Look at default OOBM configuration.
Defaults look appropriate.
Switch 41# config
Switch 41(config)# oobm
Go to OOBM context and
Switch 41(oobm)# ip address 10.255.255.41/24
add IP address and
Switch 41(oobm)# ip default-gateway 10.255.255.1
default gateway.
Switch 41(oobm)# end
Exit back to manager context.
Switch 41# ping 10.1.131.43
Ping server in this rack (on data network).
10.1.131.44 is alive, time = 19 ms
Switch 41# ping 10.1.131.51
Ping server in adjacent rack.
10.1.131.51 is alive, time = 15 ms
Switch 41# ping 10.255.255.42
Ping switch in adjacent rack.
The destination address is unreachable.
Oops! It’s on the management network.
Switch 41# ping source oobm 10.255.255.42
Go through the management port
10.255.255.42 is alive, time = 2 ms
and it works fine.
Switch 41#
G-17
Index
Symbols
=> prompt … C-77
Numerics
802.1X
effect, LLDP … 13-76
LLDP blocked … 13-44
802.1X access control
authentication failure, SNMP
notification … 13-27
SNMP notification of authentication
failure … 13-27
See also SNMP.
authorized IP managers
SNMP, blocking … 13-3
auto MDI/MDI-X
configuration, display … 10-21
operation … 10-19, 10-21
port mode, display … 10-21
Auto-10 … 11-4, 11-7, 11-18
autonegotiate … 13-56
auto-TFTP … A-11
disable … A-11, A-14
disabled … A-11
download to a redundant management
system … A-9
downloading software images … A-11
A
access
manager … 13-14
operator … 13-14
out-of-band … 2-4
address
network manager … 13-5
address table, port … B-14
address, network manager … 13-6
advertise location … 13-56
AES encryption … 13-10
alert log … 5-20
alert types … 5-21
disabling … 5-25
setting the sensitivity level … 5-24
sorting the entries … 5-20
alias
command … 4-18
use for troubleshooting … C-75
ARP
arp age, default … 8-7
ARP protection
SNMP notification … 13-27
asterisk
meaning in show config … 6-29
meaning in traceroute … C-63
authentication
notification messages … 13-18, 13-27
authentication trap
B
bandwidth
displaying port utilization … 10-13
displaying utilization … 5-17
banner
configuring … 2-11
default … 2-9
non-default … 2-10
operation … 2-9
redundant management … 2-10
Best Offer … 6-43
boot
See also reboot.
boot command … 6-4, 6-20
boot ROM console … A-4
boot ROM mode … C-77
Bootp
Bootp table file … 8-13
Bootptab file … 8-13
effect of no reply … C-9
operation … 8-12, 8-13
server … 8-2
using with Unix systems … 8-13
See also DHCP.
Bootp/DHCP differences … 8-13
Bootp/DHCP, LLDP … 13-52
broadcast limit … 10-5, 10-18
Index – 1
broadcast storm … 11-3, C-16
broadcast traffic
IPX … 10-5, 10-19
RIP … 10-5, 10-19
browser interface
See web browser interface.
C
CDP … 13-77, 13-78, 13-79, 13-80, 13-82
Classifier
mirroring configuration … B-27
Clear + Reset button combination … 6-37
Clear button … 5-10
restoring factory default configuration … C-76
clear logging … C-33
CLI
accessing from menu console … 3-8
context configuration level … 4-5
context level … 10-16
global configuration level … 4-5
Help … 4-11
keystroke shortcuts … 4-20
listing command options … 4-8
moving to or from the menu … 4-7
port or trunk-specific commands … 4-13
privilege levels … 4-3
using … 4-2–4-16, 4-20
VLAN-specific commands … 4-15
command line interface
See CLI.
command syntax conventions … 1-2
communities, SNMP … 13-15
viewing and configuring with the CLI … 13-16
viewing and configuring with the menu … 13-14
config files, SCP/SFTP transfer … 6-41
configuration
Bootp … 8-13
clearing module … 10-29
comparing startup to running … 6-6
console … 7-3
copying … A-26
DHCP Option 66 … 6-41
DHCP, Best Offer … 6-43
factory default … 6-9, 8-2
file update with Option 66 … 6-41
file updating with Option 66 … 6-42
impacts of software download on … A-4
2 – Index
IP … 8-2
Option 67 … 6-42
permanent … 6-7
permanent change defined … 6-4
port … 10-1
port trunk group … 11-1
port, duplex … 10-15
port, speed … 10-15
quick … 3-8
reboot to activate changes … 3-13
restoring factory defaults … C-76
saving from menu interface … 3-10
serial link … 7-3
SNMP … 13-5, 13-6, 13-12
SNMP communities … 13-14, 13-16
startup … 3-10
system … 7-12
Telnet access configuration … 7-3
TFTP server … 6-41
traffic mirroring … B-23
transferring … A-26
updating the file using Option 66 … 6-42
using Menu interface … 3-7
viewing … 6-6
web browser access … 7-3
configuration file
browsing for troubleshooting … C-65
configuration file, multiple
after first reboot … 6-28
applications … 6-25
asterisk … 6-29
backupConfig … 6-26
change policy … 6-30
Clear + Reset button combination … 6-37
copy from tftp host … 6-39
copy to tftp host … 6-38
copy via tftp … A-27
copy via Xmodem … A-28
create new file … 6-27, 6-33, 6-35
current file in use … 6-29
default reboot from primary … 6-31
erasing … 6-35
memory assignments … 6-28
memory slot … 6-26, 6-29, 6-31
minconfig … 6-31, 6-36
newconfig … 6-31
oldConfig … 6-27
override reboot policy … 6-30
policy, override … 6-32
power cycle … 6-31
primary boot path … 6-29
reboot policy options … 6-26
reboot policy, override … 6-30
reboot process … 6-27
reload … 6-32
rename config file … 6-33
reset … 6-31
running-config file … 6-27
running-config file operation … 6-26
secondary boot path … 6-29
show config file content … 6-30
show multiple files … 6-29
startup-config … 6-26
startup-config file … 6-27
transition to multiple files … 6-27
unable to copy … 6-34
workingConfig … 6-26, 6-27
xmodem from host … 6-40
xmodem to host … 6-40
connection-rate filtering
affect on switch resources … E-2
resource usage … E-2
console
Actions line … 3-10, 3-11
configuring … 7-3
ending a session … 3-5
features … 2-4
Help … 3-9, 3-11
inactivity-timer … 7-9
Main Menu interface … 3-7
meaning of asterisk … 3-10, 3-13
measuring network activity … C-9
navigation … 3-9, 3-10
operation … 3-10
starting a session … 3-4
statistics, clear counters … 3-12
status and counters access … 3-7
status and counters menu … B-5
troubleshooting access problems … C-7
context level
global config … 4-5, 8-10
manager level … 4-5
moving between contexts … 4-7
port or trunk-group … 4-13
VLAN-specific … 4-15
copy
command output … A-31
crash data … A-32
crash log … A-33
event log output … A-31
multiple config file, tftp … 6-38
software images … A-25
tftp show-tech … A-27
copy show tech … C-68
copy tftp
show-tech … A-27
CPU utilization … B-6
cpu utilization data … B-8
custom, show tech … A-28
customizing, show command output … 10-10
D
date format, events … C-25
date, configure … 7-18
debug
compared to event log … C-37
destination, logging … C-38
displaying debug configuration … C-41
forwarding IPv4 messages … C-38
lldp messages … C-39
overview
packet messages … C-38
sending event log messages … C-37
standard event log messages … C-38
using CLI session … C-38
debug command
configuring debug/Syslog operation … C-39
destinations … C-38, C-47
event log … C-55
event log as default … C-38
event log messages … C-45
event types supported … C-37
operating notes … C-54
OSPF messages … C-46
RIP messages … C-46
show debug … C-41
support for "debug" severity on Syslog
servers … C-47, C-55
syntax … C-45
using CLI session … C-47
debug logging
LLDP … 13-42
default gateway … 8-3
Index – 3
See also gateway.
default settings
auto-TFTP, disabled … A-11
banner … 2-9, 2-13
baud rate, speed sense … 7-3
boot flash, primary … 6-19
configuration file name, switch.cfg … 6-42
console/serial configuration … 7-5
debug destination, disabled … C-45
default gateway, none … 8-2
DHCP Option 66, enabled … 6-41
factory configuration, restoring … C-76
flow control, XON/XOFF … 7-3
flow-control, disabled … 10-17
inactivity timer, 0 minutes … 7-3
interface access features … 7-3
IP address, DHCP/Bootp … 8-2
IP configuration features … 8-2
jumbo maximum frame size, 9216 bytes … 12-7
jumbo traffic, disabled … 12-7
LLDP advertisements … 13-41
LLDP and CDP, enabled … 13-79
LLDP and LLDP-MED … 13-36
LLDP, enabled … 13-44
logging notifications … C-38
MAC age time, 300 seconds … 7-12
mdix-mode, auto-mdix … 10-21
ping … C-59
port speed, auto … 10-16
show logging … C-32
show tech command … C-65
SNMP community names … 13-14, 13-15
SNMP notifications … 13-18
SNMPv3 management station … 13-25
SNTP … 9-4
sntp poll interval, 720 seconds … 9-10
sntp server version, 3 … 9-12
Support/Mgmnt URL window … 5-12
system information features … 7-12
system name, switch product name … 7-12
task-monitor cpu, disabled … B-8
Telnet access, enabled … 7-3
terminal type, VT-100 … 7-3
TFTP, enabled … A-9
time sync method, none … 7-12
time synchronization protocol, TimeP … 9-3
time zone, 0 … 7-13
Time-to-Live (TTL), 64 … 8-3
4 – Index
traceroute … C-62
traffic mirroring … B-23
UDLD, disabled … 10-32
Web browser access, enabled … 7-3
default trunk type … 11-10
default VLAN … 8-4
DES encryption … 13-10
Device Passwords window … 5-8
DHCP
address problems … C-9
Best Offer … 6-43
Bootp operation … 8-12
effect of no reply … C-9
manual gateway precedence … 8-12
Option 66 … 6-41
DHCP snooping
resource usage … E-2
SNMP notification … 13-27
DHCP/Bootp differences … 8-13
DHCP/Bootp process … 8-12
DHCP/Bootp, LLDP … 13-52
DHCPv6
debug messages … C-39
dhcpv6-client … C-39
diagnostics tools … C-56
browsing the configuration file … C-65
displaying switch operation … C-65, C-68
ping and link tests … C-57
traceroute … C-61
viewing switch operation … C-65
DNS
configuration … C-81, C-84
configuration error … C-87
configuration, viewing … C-85
DNS-compatible commands … C-79, C-81
domain name, fully qualified … C-79, C-80, C-85
domain suffix … C-79
domain-name configuration … C-83
event log messages … C-87
example … C-83
host name … C-79
IPv6 DNS resolution … C-79
name, using in web browser
operating notes … C-86
ping … C-79, C-81, C-84
resolver … C-79
resolver operation … C-80
secure management VLAN … C-86
server address, DHCP not used … C-86
server IP address … C-80, C-86
server-address configuration … C-82
three entries supported … C-82
three server entries supported … C-82
traceroute … C-79, C-81, C-84
VLAN, best route selection … C-86
documentation
feature matrix … -xxii
latest versions … -xxi
printed in-box publication … -xxi
release notes … -xxi
Domain Name Server
See DNS.
download
software … A-22
software using TFTP … A-4
switch-to-switch … A-22
TFTP … A-5
troubleshooting … A-6
Xmodem … A-19
See also switch software.
duplex advertisements … 13-54
duplex information, displaying … 13-70
duplicate MAC address
See MAC address.
Dyn1
See LACP.
dynamic ARP protection
resource usage … E-2
E
Emergency Location Id Number … 13-37, 13-63
event log
clearing entries … C-32
compared to debug/Syslog operation … C-37
console menu … 3-7
debugging by severity level … C-38, C-48
debugging by system module … C-38, C-48
format, date … C-25
generated by system module … C-25
how to read entries … C-24
listing entries … C-32
losing messages … C-24
navigation … C-31
not affected by debug configuration … C-55
security levels … 13-21
sending event log messages as traps … 13-21
severity level … C-24, C-53
system module … C-54
time format … C-25
UDLD warning messages … 10-37
used for debugging … C-38
used for troubleshooting … C-24
excessive frames … 12-11
F
facility
logging … C-38
factory default configuration
restoring … 6-9, C-76
failure, switch software download … A-7
fastboot command … 6-23
fault detection policy … 5-8, 5-24
fault-tolerance … 11-4
fiber optics, monitoring links … 10-31
filter, source-port
jumbo VLANs … 12-10
firmware version … B-6
flash memory … 3-10, 6-3
flow control
constraints … 10-5, 10-17
global … 10-17
global requirement … 10-5
jumbo frames … 12-9
per-port … 10-5, 10-17
status … B-11
terminal … 7-3
friendly port names
See port names, friendly.
G
gateway
configuring … 8-5
default gateway … 8-3
IP address … 8-4, 8-6
manual config priority … 8-12
on primary VLAN … 8-4
precedence of manual gateway over DHCP/
Bootp … 8-12
giant frames … 12-11
global config level … 8-10
Index – 5
H
Help
for CLI … 1-7, 4-11
for menu interface … 1-6, 3-9, 3-11
for web browser interface … 1-7, 5-13
online, inoperable … 5-13
hop, router … 8-10
HP
Auto-MDIX feature … 10-19
web browser interface … 2-6
I
IDM
resource usage … E-2
resources … E-3
IDS … B-25
IEEE 802.1d … C-16
IEEE P802.1AB/D9 … 13-42
IGMP
host not receiving … C-10
not working … C-10
statistics … B-19
inactivity timeout … 7-4
inactivity-timer … 7-9
Inbound Telnet Enabled parameter … C-8
informs
sending to trap receiver … 13-21
SNMP … 13-22
intelligent mirroring
See mirroring.
IP … 8-7
CLI access … 8-6
configuration … 8-2
DHCP/Bootp … 8-2
duplicate address … C-9
duplicate address, DHCP network … C-9
effect when address not used … 8-11
features available with and without … 8-11
gateway … 8-3
gateway (IP) address … 8-4
menu access … 8-5
multiple addresses in VLAN … 8-3, 8-8
subnet … 8-3, 8-8
subnet mask … 8-2, 8-6
time server address … 9-9, 9-20
Time-To-Live … 8-7, 8-10
TTL … 8-7, 8-10
6 – Index
using for web browser interface … 5-4
web access … 8-10
IP address
for SNMP management … 13-3
manually configure … 8-6
multiple in a VLAN … 8-8
quick start … 1-8, 8-3
removing or replacing … 8-10
setup screen … 8-3
show management command … 8-7
IP Preserve
DHCP server … 8-16
overview … 8-16
rules, operating … 8-16
summary of effect … 8-19
IPv6
debug dhcpv6 messages … C-39
IPX
broadcast traffic … 10-5, 10-19
network number … B-9
J
jumbo frames
configuration … 12-4
excessive inbound … 12-9
flow control … 12-9
GVRP operation … 12-3
management VLAN … 12-9
maximum size … 12-2, 12-7
meshing … 12-3
mirroring … B-42
MTU … 12-2, B-42, B-45
port adds and moves … 12-3
port speed … 12-3
security concerns … 12-10
standard MTU … 12-3
through non-jumbo ports … 12-10
traffic sources … 12-3
troubleshooting … 12-11
VLAN tag … 12-2, B-43
voice VLAN … 12-9
K
kill command … 7-11, C-75
L
LACP
802.1X not allowed … 11-22
active … 11-15
blocked ports … 11-23
CLI access … 11-11
default port operation … 11-21
described … 11-6, 11-18
Dyn1 … 11-7
dynamic … 11-19
enabling dynamic trunk … 11-15
full-duplex required … 11-4, 11-18
IGMP … 11-23
mirroring static trunk … B-28
no half-duplex … 11-25
operation not allowed … C-11
overview of port mode settings … 11-4
passive … 11-15
removing port from active trunk … 11-16
restrictions … 11-22
standby link … 11-19
status, terms … 11-21
STP … 11-23
trunk limit … 11-19
VLANs … 11-23
with 802.1X … 11-22
with port security … 11-22
limit, broadcast … 10-18
line rate … B-28
link failures
detecting … 10-31
link speed, port trunk … 11-3
link test … C-57
link, serial … 7-3
link-change traps … 13-18, 13-29
Link-Layer Discovery Protocol
See LLDP.
LLDP
802.1D-compliant switch … 13-75
802.1X blocking … 13-44
802.1X effect … 13-76
active port … 13-37
adjacent device … 13-37
advertisement … 13-37
advertisement content … 13-52
advertisement data … 13-68
advertisement, mandatory data … 13-52
advertisement, optional data … 13-53
advertisements, delay interval … 13-48
CDP neighbor data … 13-77
chassis ID … 13-52
chassis type … 13-52
clear statistics counters … 13-73
comparison with CDP data fields … 13-77
configuration options … 13-40
configuring optional data … 13-53
data options … 13-41
data read options … 13-42
data unit … 13-38
debug logging … 13-42
debug messages … C-39
default configuration … 13-44
DHCP/Bootp operation … 13-43
disable, per-port … 13-51
display neighbor data … 13-71
ELIN … 13-37
enable/disable, global … 13-46
features … 13-36
general operation … 13-39
global counters … 13-73
holdtime multiplier … 13-48
hub, packet-forwarding … 13-39
IEEE P802.1AB/D9 … 13-42
inconsistent value … 13-49
information options … 13-41
invalid frames … 13-74
IP address advertisement … 13-43, 13-76
IP address subelement … 13-52
IP address, DHCP/Bootp … 13-52
IP address, options … 13-52
IP address, version advertised … 13-52
LLDP-aware … 13-37
LLDPDU … 13-38
mandatory TLVs … 13-76
MIB … 13-39, 13-42
neighbor … 13-38
neighbor data remaining … 13-76
neighbor data, displaying … 13-71
neighbor statistics … 13-73
neighbor, maximum … 13-75
operating rules … 13-43
operation … 13-39
optional data, configuring … 13-53
outbound packet options … 13-41
packet boundaries … 13-39
packet dropped … 13-39
Index – 7
packet time-to-live … 13-42
packet-forwarding … 13-39, 13-75
packets not forwarded … 13-38
per-port counters … 13-74
port description … 13-53
port ID … 13-52
port speed … 13-54
port trunks … 13-43
port type … 13-52
refresh interval … 13-47
reinitialization delay … 13-49
remote management address … 13-42
remote manager address … 13-52
reset counters … 13-73
rxonly … 13-51
setmib, delay interval … 13-48
setmib, reinit delay … 13-50
show advertisement data … 13-68
show commands … 13-44, 13-46
show outbound advertisement … 13-69
SNMP notification … 13-41
SNMP traps … 13-41
spanning-tree blocking … 13-44
standards compatibility … 13-42
statistics … 13-73
statistics, displaying … 13-73
system capabilities … 13-53
system description … 13-53
system name … 13-53
terminology … 13-37
time-to-live … 13-40, 13-48
TLV … 13-39
transmission frequency … 13-40
transmission interval, change … 13-47
transmit and receive … 13-40
transmit/receive modes … 13-40
transmit/receive modes, per-port … 13-51
trap notice interval … 13-51
trap notification … 13-50
trap receiver, data change notice … 13-50
TTL … 13-40, 13-42
txonly … 13-51
VLAN, untagged … 13-76
walkmib … 13-42
LLDP-MED
displaying speed … 13-70
ELIN … 13-63
enable or disable … 13-40
8 – Index
endpoint support … 13-56
fast start control … 13-60
location data … 13-63
medTlvenable … 13-62
Neighbors MIB … 13-71
topology change notification … 13-58
Voice over IP … 13-55
load balancing
See port trunk.
logging
facility … C-38
logging command … C-45
syntax … C-38, C-48
logical port … 11-8
loop, network … 11-3
lost password … 5-10
M
MAC address … 8-13, B-6, D-2
displaying detected devices … D-7
duplicate … C-16, C-22
learned … B-14
port … D-2, D-4
same MAC, multiple VLANs … D-6
switch … D-2
traffic selection in mirroring … B-26
VLAN … D-2, D-5
walkmib … D-5
MAC authentication
SNMP notification … 13-27
management
interfaces described … 2-2
server URL … 5-12, 5-13
server URL default … 5-13
Management Information Base
See MIB.
management port … G-2
management VLAN
See VLAN.
management VLAN, DNS … C-86
manager access … 4-5, 4-6, 13-14
manager password … 5-8, 5-10
SNMP notification … 13-18, 13-27
manager privileges … 4-5, 4-6
max frame size, jumbo … 12-7
MD5 authentication … 13-10
MDI/MDI-X
configuration, display … 10-21
operation … 10-19
port mode, display … 10-21
media type, port trunk … 11-3
memory
flash … 3-10, 6-3
startup configuration … 3-10
menu interface
configuration changes, saving … 3-10
moving to or from the CLI … 4-7
See also console.
mesh
mirroring … B-23
MIB
HP proprietary … 13-5
listing … 13-5
standard … 13-5
mini-USB … 2-2
mirroring
802.1Q tag … B-45
caution, configure destination first … B-26, B-33,
B-35
caution, exit port connection … B-25, B-47
classifier-based criteria … B-27, B-39
CLI option … B-23, B-28
command index … B-33
configuration options … B-27
configuration override … B-29
configuration, Menu … B-30
criteria for selecting traffic … B-26
destination, local … B-26, B-33
destination, remote … B-33
directional-based criteria … B-36
display configuration … B-38
distributed traffic … B-28
dropped traffic … B-28
dropped traffic mirrored … B-45
duplicate frames, IGMP … B-45
effect of STP state … B-45
encryption … B-45
endpoint switch … B-28
example configuration … B-24
example, configuration … B-41
exit interface … B-28
exit port, caution … B-25
exit port, local mirroring … B-24, B-34
exit port, oversubscribe … B-26
exit port, VLAN prerequisite … B-26
exit port, VLAN rule … B-47
frame truncation, not allowed … B-42
header … B-23
IDS … B-23, B-25
IGMP, duplicate frames … B-45
in configuration file … B-40
intelligent mirroring … B-23
interface sources … B-26
intermediate switches … B-28
IPv4 encapsulation … B-23, B-35, B-42, B-45
IPv4 frames not mirrored … B-45
jumbo frames … B-23, B-42
local, configuration steps … B-34
local, defined … B-25
MAC-based criteria … B-27, B-38
maximum sources on destination … B-23
Menu interface limit … B-28, B-29
Menu interface, local-only … B-28
Menu option … B-23
mesh source … B-27, B-31
mirror command … B-35
monitor, autoconfig session 1 … B-36, B-37, B-46
monitored interface of source traffic … B-25
MTU … B-42, B-45
operating notes … B-45
overload on destination … B-28
port … B-31
port screen … B-23
port source … B-27
port source, trunk … B-28
quick reference, local … B-34
rate … B-28
restrictions, local sessions … B-23
restrictions, source … B-36
session identity … B-35
session, source … B-35
show commands … B-38, B-40
simultaneous source/destination … B-26
SNMP … B-28, B-29
source switch … B-25
source, configure … B-35
static trunk … B-26
terminology … B-24
traffic overload … B-28
traffic, injected into mirrored stream … B-45
traffic, intercepted … B-45
troubleshooting … B-47
trunk source … B-27, B-31
Index – 9
using MAC addresses … B-26
VLAN … B-31
VLAN rule, exit port … B-47
VLAN tag, frame size … B-43
VLAN tagging … B-45
Web interface … B-28
Web limits … B-29
MLTS … 13-38
module
clearing the config … 10-29
CLI command … 10-29
configuring when not inserted … 10-29
pre-configuring … 10-29
remove configuration command … 10-30
monitoring
links between ports … 10-31
status and counters screens … B-4
monitoring, traffic
See mirroring.
Multiline Telephone system … 13-38
multinetting … 8-3, 8-8
multiple configuration file
See configuration file, multiple.
multiple forwarding database … B-9, B-14, B-17,
B-20
multiple VLAN … 13-3
N
NANP … 13-38
navigation, event log … C-31
network management functions … 13-6, 13-14
network manager address … 13-5, 13-6
network slow … C-9
North American Numbering Plan … 13-38
notifications
authentication messages … 13-18, 13-27
enabling for network security … 13-27
link-change traps … 13-18
network security … 13-27
O
Onboard Administrator (OA) … 2-2
online Help
See Help.
oobm
10 – Index
network … 2-2, 6-38, 6-39, 6-40, 7-6, 7-7, 9-12,
9-22, 13-34, A-7, A-9, C-50, C-59, C-60, C-63,
C-82, G-8, G-9, G-10, G-11, G-12, G-13, G-15,
G-16, G-17
operating system
See switch software.
operation not allowed, LACP … C-11
operator access … 4-4, 4-6, 13-14
operator password … 5-10
setting via web browser … 5-8
operator privileges … 4-4, 4-6
Option 66, DHCP … 6-41
OS
version … A-23
See also switch software.
OSPF
debug command … C-46
out-of-band access … 2-4
P
packet
debug messages … C-38
password … 5-8, 5-10
console … 3-7
creating … 5-8
delete … 5-10
if you lose the password … 5-10
lost … 5-10
manager … 4-4, 5-8
operator … 4-4, 5-8
setting … 5-9
SNMP notification … 13-27
SNMP notification for invalid login … 13-18
using to access browser and console … 5-10
web interface … 5-8
pattern matching, show command output … C-72
PD … 13-38
Physical Interfaces … 2-2
ping … C-79, C-81, C-84
See also DNS, resolver.
See also troubleshooting.
ping test … C-57
PoE
benefit of LLDP-MED … 13-56
status … 13-60
policy enforcement engine
described … E-2
displaying resource usage … E-2
poll interval
See TimeP.
port
address table … B-14
blocked by UDLD … 10-32
broadcast limit … 10-18
CLI access … 10-8
configuration … 10-1
configuring UDLD … 10-32
context level … 10-16
counters … B-11
counters, reset … B-11
duplex, view … 10-8
enabling UDLD … 10-33
fiber-optic … 10-5
MAC address … D-4, D-5
management … G-2
menu access … 10-6
mirroring
See mirroring.
mirroring, static LACP trunk … B-28
monitoring
See mirroring.
speed, view … 10-8
traffic patterns … B-11
transceiver status … 10-14
trunk
See port trunk.
utilization … 5-17, 10-13
CLI … 10-13
web browser interface … 5-17
web browser access … 10-22
port configuration … 11-1
port names, friendly
configuring … 10-24
displaying … 10-25
summary … 10-23
port security
port trunk restriction … 11-3
trunk restriction … 11-8
port trunk … 11-2
bandwidth capacity … 11-2
caution … 11-3, 11-9, 11-17
CLI access … 11-11
default trunk type … 11-10
enabling dynamic LACP … 11-15
enabling UDLD … 10-33
IGMP … 11-8
limit … 11-2
limit, combined … 11-19
link requirements … 11-3
logical port … 11-8
media requirements … 11-7
media type … 11-3
menu access to static trunk … 11-9
mirroring … B-23
monitor port restrictions … 11-8
nonconsecutive ports … 11-2
port security restriction … 11-8
removing port from static trunk … 11-15
requirements … 11-7
SA/DA … 11-27
spanning tree protocol … 11-8
static trunk … 11-7
static trunk, overview … 11-4
static/dynamic limit … 11-19
STP … 11-8
STP operation … 11-7
traffic distribution … 11-7
Trk1 … 11-7
trunk (non-protocol) option … 11-6
trunk option described … 11-26
types … 11-6
UDLD configuration … 10-32
VLAN … 11-8
VLAN operation … 11-7
web browser access … 11-17
See also LACP.
port trunk group
interface access … 11-1
port, active … 13-37
port-access authentication
SNMP notification … 13-27
port-based access control
event log … C-11
LACP not allowed … 11-22
troubleshooting … C-11
port-utilization and status displays … 10-13
power supply
show settings … B-7
Power-Sourcing Equipment … 13-38
privilege levels … 4-3
ProCurve
Auto-MDIX feature … 10-19
switch documentation … -xxi
Index – 11
ProCurve Manager
security concerns when deleting public
community … 13-6
starting web browser … 5-4
updating switch software … A-24
using Java-enabled browser … 5-5
ProCurve, HP, URL … 13-5
prompt, => … C-77
PSAP … 13-38
PSE … 13-38
Public Safety Answering Point … 13-38
public SNMP community … 13-6, 13-14
Q
QoS
See Quality of Service.
quick configuration … 3-8
Quick Installation Card … 1-4
quick start … 1-8
R
RADIUS
web browser access … 5-8
rate display for ports … 10-13
reboot
actions causing … 6-4
faster boot time … 6-23
from secondary flash … 6-22
obtaining faster reboot time … 6-20
scheduling remotely … 6-24
via menu console … 3-8
via menu interface … 3-10, 3-12
See also boot.
redo, command description … 4-16
reload … 6-4
reload command … 6-20
remote intelligent mirroring
See mirroring.
remote session, terminate … 7-11
repeat, command description … 4-16
Reset button … 6-4
restoring factory default configuration … C-76
reset operating system … 3-12
reset port counters … B-11
resetting the switch
factory default reset … C-76
12 – Index
resource monitor
event log … E-3
resource usage
insufficient resources … E-3
restricted write access … 13-14
RFCs
RFC 1493 … 13-5
RFC 1515 … 13-5
RFC 2737 … 13-42, 13-43
RFC 2863 … 13-42, 13-43
RFC 2922 … 13-42
See also MIB.
RIP
broadcast traffic … 10-5, 10-19
debug command … C-46
RMON … 13-5
RMON groups supported … 13-35
router
gateway … 8-6
router, hop … 8-10
routing
OSPF debug messages … C-46
RIP debug messages … C-46
traceroute … C-61
RS-232 … 2-4
running-config
viewing … 6-6
See also configuration.
S
scheduled reboot … 6-24
SCP/SFTP
enabling … A-13
session limit … A-17, A-19
transfer of config files … 6-41
troubleshooting … A-18
secure copy
See SCP/SFTP.
secure FTP
See SCP/SFTP.
secure management VLAN
See VLAN.
secure management VLAN, DNS … C-86
security
Clear button … 5-11
enabling network security notifications … 13-27
privilege levels in CLI … 4-3
username and password … 5-8
web browser access, RADIUS … 5-8
Self Test LED
behavior during factory default reset … C-77
serial number … B-6
setmib, delay interval … 13-48
setmib, reinit delay … 13-50
setup screen … 1-8
severity level
event log … C-24
selecting Event Log messages for
debugging … C-53
SHA authentication … 13-10
show
custom option … 10-10
displaying specific output … C-72
exclude option
show
begin option … C-72
include option … C-72
interfaces brief … 10-8
interfaces config … 10-9
pattern matching with … C-72
tech, custom … A-28
telnet … 7-6
show cpu … B-8
show debug … C-41
show interfaces
dynamic display … 10-9
show interfaces display … C-71
show management … 9-9, 9-20
show tech … C-65
custom … A-28
show-tech … A-27
slow network … C-9
SNMP … 13-3
authentication notification … 13-18, 13-27
CLI commands … 13-14
communities … 13-5, 13-6, 13-14, 13-15
configuring with the CLI … 13-16
configuring with the menu … 13-14
mapping … 13-12
config using trap receivers … 13-20
configure … 13-5, 13-6
configuring security groups … 13-24
configuring SNMPv3 notification … 13-24
configuring SNMPv3 users … 13-24
different versions … 13-18
enabling informs … 13-22
enabling network security traps … 13-28
enabling SNMPv3 … 13-24
fixed traps … 13-20
invalid password in login … 13-18
IP … 13-3
link-change traps … 13-18, 13-29
manager password change … 13-18
mirroring … B-28
network security notification … 13-27
notification, LLDP
SNMP notification … 13-41
public community … 13-6, 13-14
supported notifications … 13-18
system thresholds … 13-20
traps … 10-32, 13-5, 13-18
walkmib … D-5, D-6
well-known traps … 13-20
SNMP trap, LLDP … 13-50
SNMPv3
"public" community access caution … 13-7
access … 13-6
assigning users to groups … 13-8
authentication, configuring … 13-10
communities … 13-12
enable command … 13-8
enabling … 13-7
encryption, configuring … 13-10
group access levels … 13-12
groups … 13-11
network management problems with snmpv3
only … 13-7
restricted-access option … 13-7
set up … 13-6
users … 13-6
SNTP
broadcast mode … 9-2, 9-11
broadcast mode, requirement … 9-3
configuration … 9-4
disabling … 9-12
enabling and disabling … 9-10
event log messages … 9-26
manual config priority … 8-12
menu interface operation … 9-26
operating modes … 9-2
poll interval
See TimeP.
priority … 9-14
Index – 13
selecting … 9-3
server priority … 9-14
show management … 9-9
unicast mode … 9-3, 9-11
unicast time polling … 9-25
unicast, deleting addresses … 9-26
unicast, replacing servers … 9-26
viewing … 9-4, 9-8
software
See switch software.
software image
See switch software.
software version … B-6
sorting alert log entries … 5-20
source port filters
jumbo VLANs … 12-10
spanning tree
fast-uplink, troubleshooting … C-16
mirroring blocked traffic … B-45
problems related to … C-16
show tech, copy output … C-67
using with port trunking … 11-8
SSH
enabling or disabling … A-15
file transfer … A-11
TACACS exclusion … A-16
troubleshooting … A-18, C-17
standard MIB … 13-5
starting a console session … 3-4
startup-config
viewing … 6-6
See also configuration.
statistics … 3-7
statistics, clear counters … 6-11
status and counters
access from console … 3-7
status overview screen … 5-6
subnet … 8-8
subnet mask … 8-4, 8-6
See also IP masks.
support
URL … 5-12
URL Window … 5-12
switch console
See console.
switch setup menu … 3-8
switch software
copy from a USB device … A-22
14 – Index
download using TFTP … A-4
download, failure indication … A-7
download, switch-to-switch … A-22
download, troubleshooting … A-6
download, using TFTP … A-4
software image … A-3
version … A-6, A-20
Syslog
"debug" severity level as default … C-53, C-55
adding priority description … C-52
compared to event log … C-37
config friendly descriptions … C-51
configuring for debugging … C-39
configuring server address … C-38
configuring server IP address … C-45
configuring Syslog servers and debug
destinations … C-38
control-desc … C-52
displaying Syslog configuration … C-41
event log messages sent by default … C-50
logging command … C-45, C-47
operating notes … C-54
overview … C-37
priority-descr … C-52
See also debug command.
sending event log messages … C-37
server configuration … C-49
severity, "debug" … C-47
specifying severity level events for
debugging … C-53
specifying system module events for
debugging … C-54
user facility as default … C-51, C-55
using event log for debugging … C-38, C-48
system configuration screen … 7-12
system information … B-7
fans … B-7
power-supply … B-7
temperature … B-7
system module
selecting event log messages for
debugging … C-54
System Name parameter … 7-13
T
TACACS
SSH exclusion … A-16
task monitor … B-8
taskusage -d … B-8
taskUsageShow … B-8
Telnet
connecting to switch … 3-4
enable/disable … 7-4
outbound … 7-6
terminate session, kill command … 7-11
troubleshooting access … C-8
telnet
domain name address … 7-6
hostname … 7-6
ipv6 address … 7-6
show command … 7-6
switch-num … 7-6
terminal access, lose connectivity … 7-9
terminal type … 7-3
terminate remote session … 7-11
TFTP
auto-TFTP … A-11
auto-TFTP feature … A-11
auto-TFTP, disable … A-11, A-14
copy command output … A-31
copy crash data … A-32
copy crash log … A-33
copy event log output … A-31
copying a configuration file … A-27
copying software image … A-25
disable … A-14
disabled … A-11
download software using CLI … A-7
downloading software using console … A-5
enable client or server … A-9
enabling client functionality … A-9
enabling server functionality … A-9
switch-to-switch transfer … A-22
troubleshooting download failures … A-6
using to download switch software … A-4
threshold setting … 13-6, 13-14
thresholds, SNMP … 13-20
time format, events … C-25
time protocol
selecting … 9-3
time server … 8-2
time zone … 7-13, 7-18
time, configure … 7-18
TimeP … 8-3, 8-5
assignment methods … 9-2
disabling … 9-23
enabling and disabling … 9-20
manual config priority … 8-12
poll interval … 9-23
selecting … 9-3
server address listing … 9-9, 9-20
show management … 9-20
viewing and configuring, menu … 9-17
viewing, CLI … 9-19
timesync, disabling … 9-23
Time-To-Live … 8-3, 8-5, 8-6, 8-10
See also TTL.
time-to-live, LLDP … 13-40
Time-To-Live, on primary VLAN … 8-4
TLV … 13-39
TLVs, mandatory … 13-76
traceroute … C-79, C-81, C-84
asterisk … C-63
blocked route … C-64
fails … C-63
traffic mirroring
See mirroring.
traffic monitoring … 13-6, 13-14
See also mirroring.
traffic, port … B-11
transceiver
error messages … 10-15
view status … 10-14
transceiver, fiber-optic … 10-5
transceivers
configuring when not inserted … 10-29
not inserted … 10-29
trap … 5-25
authentication trap … 13-28
CLI access … 13-20
configuring trap receivers … 13-20
security levels … 13-21
trap notification … 13-50
trap receiver … 13-5, 13-6
configuring … 13-20
sending event log messages … 13-21
sending SNMPv2 informs … 13-21
SNMP … 13-20
up to ten supported … 13-20
traps
enabling network security notifications … 13-27
link-change … 13-29
troubleshooting
Index – 15
approaches … C-5
browsing the configuration file … C-65
configuring debug destinations … C-38
console access problems … C-7
diagnosing unusual network activity … C-9
diagnostics tools … C-56
displaying switch operation … C-65, C-68
DNS
See DNS.
fast-uplink … C-16
ping and link tests … C-57
resource usage … E-2
restoring factory default configuration … C-76
spanning tree … C-16
SSH … C-17
SSH, SFTP, and SCP Operations … A-18
switch software download … A-6
switch won’t reboot, shows => prompt … C-77
traceroute … C-79, C-81
unusual network activity … C-9
using CLI session … C-38
using debug and Syslog messaging
using the event log … C-24
viewing switch operation … C-65
web browser access problems … C-7
trunk
See port trunk.
TTL … 8-3, 8-5, 8-6, 8-7
IP … 8-10
LLDP … 13-40
manual config priority … 8-12
on primary VLAN … 8-4
See also Time-To-Live.
Type-Length-Value … 13-39
types of alert log entries … 5-21
U
UDLD
changing the keepalive interval … 10-34
changing the keepalive retries … 10-34
configuration … 10-32
configuring for tagged ports … 10-34
enabling on a port … 10-33
event log messages … 10-37
operation … 10-32
overview … 10-31
supported switches … 10-32
16 – Index
viewing configuration … 10-35
viewing statistics … 10-36
warning messages … 10-37
unauthorized access … 13-28
undersize frames … 12-11
Uni-directional Link Detection
See UDLD.
Universal Resource Locator
See URL.
Unix, Bootp … 8-13
unrestricted write access … 13-14
unusual network activity … C-9
up time … B-6
URL
browser interface online help location … 5-13
management … 5-13
management server … 5-12, 5-13
ProCurve … 13-5
support … 5-12, 5-13
USB
copy command output … A-31
copy crash data … A-32
copy crash log … A-33
copy event log output … A-31
using to copy switch software … A-22
user name
using for browser or console access … 5-8, 5-10
users, SNMPv3
See SNMPv3.
utilization, port … 5-17, 10-13
V
version, OS … A-23
version, switch software … A-6, A-20
view
duplex … 10-8
port speed … 10-8
transceiver status … 10-14
virus-throttling
See connection-rate filtering.
VLAN
address … 13-3
Bootp … 8-13
configuring Bootp … 8-13
configuring UDLD for tagged ports … 10-34
device not seen … C-21
event log entries … C-25
ID … 4-15
IP addressing with multiple … 8-4
jumbo max frame size … 12-7
link blocked … C-16
MAC address … D-2, D-5
management and jumbo frames … 12-9
management VLAN, resource usage … E-2
management VLAN, SNMP block … 13-3
mirroring … B-3, B-23
multinet … 8-3
multinetting … 8-3, 8-8
multiple … 13-3
multiple IP addresses … 8-3, 8-8
port configuration … C-21
prerequisite, remote mirroring … B-26
primary … 8-3
reboot required … 3-8
same MAC, multiple VLANs … D-6
secure management VLAN, with DNS … C-86
subnet … 8-3, 8-8
support enable/disable … 3-8
switch software download … A-4
tagging broadcast, multicast, and unicast
traffic … C-21
VLAN ID
See VLAN.
VoIP
LLDP-MED support … 13-55
VT-100 terminal … 7-3
W
walkmib … 13-42, D-5, D-6
warranty … -i
web agent
advantages … 2-6
disabling access … 5-2
enable/disable … 7-4
enabled parameter … 5-2
Web authentication
SNMP notification … 13-27
web browser interface
access configuration … 7-3
access parameters … 5-8
access security … 7-3
alert log … 5-20
alert log details … 5-21
bandwidth adjustment … 5-18
bar graph adjustment … 5-18
disable access … 5-2
enabling … 5-4
error packets … 5-17
fault detection policy … 5-8, 5-24
fault detection window … 5-24
features … 2-6
first-time install … 5-7
first-time tasks … 5-7
Java applets, enabling … 5-4
main screen … 5-16
online help … 5-13
online help location specifying … 5-13
online help, inoperable … 5-13
overview … 5-16
Overview window … 5-16
password lost … 5-10
password, setting … 5-9
port status … 5-19
port utilization … 5-17
port utilization and status displays … 5-17
screen elements … 5-16
security … 5-2, 5-8
standalone … 5-4
status bar … 5-22
status indicators … 5-23
status overview screen … 5-6
system requirements … 5-4
troubleshooting access problems … C-7
URL default … 5-13
URL, management server … 5-13
URL, support … 5-13
web site, HP … 13-5
write access … 13-14
write memory
effect on menu interface … 3-13
redundant management … 6-7
X
Xmodem
copy command output … A-31
copy crash data … A-32
copy crash log … A-33
copy event log output … A-31
copying a configuration file … A-28
copying a software image … A-25
download to primary or secondary flash … A-21
using to download switch software … A-19
Index – 17
ProCurve 5400zl Switches
Installation and
Technology for better business outcomes
To learn more, visit
www.hp.com/go/bladesystem/documentation/
© Copyright 2009 Hewlett-Packard Development Company, L.P. The information
contained herein is subject to change without notice. The only warranties for HP products
and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty.
HP will not be liable for technical or editorial errors or omissions contained herein.
August 2009
Manual Part Number
5992-5523
*5992-5523*
Download PDF

advertising