- 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
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 oppor-
tunity 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 oper-
ates. 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:
■ 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.
C-15