- Hewlett-Packard Switch User Manual
Table Of Contents
- HP ProCurve 2520 Switches Management and Configuration Guide
- Front Cover
- Title Page
- Copyright, Notices, & Publication Data
- Contents
- Feature Index
- 1.Getting Started
- 2.Selecting a Management Interface
- 3.Using the Menu Interface
- 4.Using the Command Line Interface (CLI)
- 5.Using the ProCurve Web Browser Interface
- 6.Switch Memory and Configuration
- 7.Interface Access and System Information
- 8.Configuring IP Addressing
- 9.Time Protocols
- 10.Port Status and Configuration
- Contents
- Overview
- Viewing Port Status and Configuring Port Parameters
- Menu: Port Status and Configuration
- CLI: Viewing Port Status and Configuring Port Parameters
- Customizing the Show Interfaces Command
- Viewing Port Utilization Statistics
- Viewing Transceiver Status
- Enabling or Disabling Ports and Configuring Port Mode
- Enabling or Disabling Flow Control
- Configuring a Broadcast Limit on the Switch
- Configuring ProCurve Auto-MDIX
- Web: Viewing Port Status and Configuring Port Parameters
- Using Friendly (Optional) Port Names
- 11.Power Over Ethernet (PoE) Operation
- 12.Port Trunking
- Contents
- Overview
- Port Trunk Features and Operation
- Trunk Configuration Methods
- Menu: Viewing and Configuring a Static Trunk Group
- CLI: Viewing and Configuring Port Trunk Groups
- Web: Viewing Existing Port Trunk Groups
- Trunk Group Operation Using LACP
- Trunk Group Operation Using the “Trunk” Option
- How the Switch Lists Trunk Data
- Outbound Traffic Distribution Across Trunked Links
- 13.Configuring for Network Management Applications
- Contents
- Using SNMP Tools To Manage the Switch
- LLDP (Link-Layer Discovery Protocol)
- Terminology
- General LLDP Operation
- Packet Boundaries in a Network Topology
- Configuration Options
- Options for Reading LLDP Information Collected by the Switch
- LLDP and LLDP-MED Standards Compatibility
- LLDP Operating Rules
- Configuring LLDP Operation
- LLDP-MED (Media-Endpoint-Discovery)
- Displaying Advertisement Data
- LLDP Operating Notes
- LLDP and CDP Data Management
- A.File Transfers
- B.Monitoring and Analyzing Switch Operation
- Contents
- Overview
- Status and Counters Data
- Menu Access To Status and Counters
- General System Information
- Task Monitor—Collecting Processor Data
- Switch Management Address Information
- Port Status
- Viewing Port and Trunk Group Statistics and Flow Control Status
- Viewing the Switch’s MAC Address Tables
- Spanning Tree Protocol (MSTP) Information
- Internet Group Management Protocol (IGMP) Status
- VLAN Information
- Web Browser Interface Status Information
- Interface Monitoring Features
- Locating a Device
- C.Troubleshooting
- Contents
- Overview
- Troubleshooting Approaches
- Browser or Telnet Access Problems
- Unusual Network Activity
- General Problems
- 802.1Q Prioritization Problems
- IGMP-Related Problems
- LACP-Related Problems
- Port-Based Access Control (802.1X)-Related Problems
- QoS-Related Problems
- Radius-Related Problems
- Spanning-Tree Protocol (MSTP) and Fast-Uplink Problems
- SSH-Related Problems
- TACACS-Related Problems
- TimeP, SNTP, or Gateway Problems
- VLAN-Related Problems
- Fan Failure
- Using the Event Log for Troubleshooting Switch Problems
- Debug/Syslog Operation
- Debug/Syslog Messaging
- Debug/Syslog Destination Devices
- Debug/Syslog Configuration Commands
- Configuring Debug/Syslog Operation
- Debug Command
- Logging Command
- Adding a Description for a Syslog Server
- Adding a Priority Description
- Configuring the Severity Level for Event Log Messages Sent to a Syslog Server
- Operating Notes for Debug and Syslog
- Diagnostic Tools
- Viewing Switch Configuration and Operation
- Restoring the Factory-Default Configuration
- Restoring a Flash Image
- DNS Resolver
- D.MAC Address Management
- E.Daylight Savings Time on ProCurve Switches
- F.Power-Saving Features
- Index
- Notices & Publication Data

Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
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.
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-46.
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-75










