HP 5500 si series User manual

HP 5500 EI & 5500 SI Switch Series
Troubleshooting Guide
© Copyright 2013 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.
Noth
ing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
Part number: 5998-5152

i
Contents
Introduction··································································································································································· 1
Troubleshooting ACL···················································································································································· 1
ACL application failure with an error message ·············································································································1
Symptom····································································································································································1
Solution······································································································································································1
ACL application failure without an error message········································································································1
Symptom····································································································································································1
Troubleshooting flowchart ·······································································································································2
Solution······································································································································································2
Related commands····························································································································································3
Troubleshooting IRF······················································································································································ 4
IRF fabric establishment failure········································································································································4
Symptom····································································································································································4
Troubleshooting flowchart ·······································································································································4
Solution······································································································································································5
Related commands····························································································································································6
Troubleshooting Ethernet link aggregation················································································································· 7
Link aggregation failure ···················································································································································7
Symptom····································································································································································7
Troubleshooting flowchart ·······································································································································8
Solution······································································································································································8
Related commands····························································································································································9
Troubleshooting ports·················································································································································13
Link up failure on a port ················································································································································ 13
Symptom································································································································································· 13
Troubleshooting flowchart ···································································································································· 14
Solution··································································································································································· 14
Related commands························································································································································· 16
Troubleshooting other problems································································································································17
High CPU usage····························································································································································· 17
Symptom································································································································································· 17
Troubleshooting flowchart ···································································································································· 17
Solution··································································································································································· 17
Related commands ················································································································································ 18
Layer 2 forwarding failure ············································································································································ 18
Symptom································································································································································· 18
Troubleshooting flowchart ···································································································································· 19
Solution··································································································································································· 19
Related commands ················································································································································ 22
Layer 3 forwarding failure ············································································································································ 22
Symptom································································································································································· 22
Troubleshooting flowchart ···································································································································· 23
Solution··································································································································································· 23
Related commands ················································································································································ 23
PoE power supply anomaly ·········································································································································· 24
Symptom································································································································································· 24

ii
Troubleshooting flowchart ···································································································································· 24
Solution··································································································································································· 24
Related commands ················································································································································ 26

1
Introduction
This document provides troubleshooting information for HP 5500 EI and 5500 SI switches. This document
is not specific to any software versions.
Troubleshooting ACL
This section provides troubleshooting information for common problems with ACLs.
ACL application failure with an error message
Symptom
The system fails to apply a packet filter or ACL-based classifiers in a QoS policy to the hardware. It also
displays this message: "Reason: Not enough hardware resource."
Solution
To resolve this problem:
1. Execute the display acl resource command, and then check the Remaining field for ACL resources
insufficiency.
If this field displays 0, the ACL hardware resources are exhausted.
2. To free hardware resources, remove unused packet filters or ACL-based classifiers from QoS
policies.
3. If the problem persists, contact HP Support.
ACL application failure without an error message
Symptom
The system applies a packet filter or a QoS policy that contains ACLs to the hardware. However, the ACL
does not take effect.

2
Troubleshooting flowchart
Figure 1 Troubleshooting an ACL application failure
Solution
Choose a solution depending on the module that uses the ACL.
ACL used in a QoS policy
To resolve the problem when the ACL is used in a QoS policy:
1. Verify that the QoS policy is configured correctly:
a. Use one of the following commands to check the QoS policy for configuration errors,
depending on the policy application destination:
Destination Command
Interface display qos policy interface
VLAN display qos vlan-policy
Global display qos policy global
Control plane display qos policy control-plane slot slot-number
b. If the QoS policy does not contain a class-behavior association, associate the traffic behavior
with the traffic class.
c. If the QoS policy contains a class-behavior association, execute the display traffic classifier
user-defined command and the display traffic behavior user-defined command to check for
traffic class and behavior configuration errors, respectively.
−If they are configured incorrectly, reconfigure them.
−If they are configured correctly, go to Step 2.

3
2. Verify that the ACL is configured correctly:
a. Execute the display acl command.
b. If the ACL is configured incorrectly, reconfigure it.
3. If the problem persists, contact HP Support.
ACL used in a packet filter
To resolve the problem when the ACL is used in a packet filter:
1. Verify that the packet filter is configured correctly:
a. Execute the display packet-filter command.
b. If there are any configuration errors, reconfigure the packet filter.
2. Verify that the ACL is configured correctly:
a. Execute the display acl command.
b. If there are any configuration errors, reconfigure the ACL.
3. If the problem persists, contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting ACLs.
Command Descri
p
tion
display acl resource Displays information about hardware resources for ACL
applications.
display packet-filter Displays whether an ACL has been successfully applied to an
interface for packet filtering.
display qos policy control-plane Displays information about the QoS policies applied to the
specified control plane.
display qos policy global Displays information about global QoS policies.
display qos policy interface Displays information about the QoS policies applied to an
interface or to all interfaces.
display qos vlan-policy Displays information about QoS policies applied to VLANs.
display traffic classifier user-defined Displays traffic class configurations.
display traffic behavior user-defined Displays traffic behavior configurations.

4
Troubleshooting IRF
This section provides troubleshooting information for common problems with IRF.
IRF fabric establishment failure
Symptom
An IRF fabric cannot be established.
Troubleshooting flowchart
Figure 2 Troubleshooting IRF fabric establishment failure
No
Yes
No
Yes
No
Yes
End
IRF setup
failure
No
No
Yes
Yes
Contact HP
Support
No
Yes
Resolved?
No
Yes
Yes
No
Yes No
Yes
You cannot add devices to the
IRF fabric
Yes
No
Member ID unique?
Replace with 10-Gbps, XFP,
SFP+, or CX4 transceiver
modules/cables
Number of members
fewer than the upper limit?
10-Gbps IRF links used? No Resolved?
IRF port bindings
or physical IRF connections
correct?
Modify IRF port bindings or
reconnect physical ports Resolved?
IRF links up? Bring up the IRF links/activate
IRF port configuration Resolved?
Same software version? Upgrade software to the same
version in the fabric Resolved?
Assign a unique member ID to
each member device

5
Solution
To resolve the problem:
1. Verify that the number of member devices does not exceed the upper limit (nine for a 5500-EI IRF
fabric and four for a 5500-SI IRF fabric).
If you are adding a new member device to an existing IRF fabric, use the display irf command to
identify the number of member devices already in the IRF fabric.
2. Verify that the member ID of each member device is unique:
a. Execute the display irf configuration command to view the member ID of each member device.
b. If two member devices use duplicate IDs, assign a unique member ID to each member.
3. Verify that the IRF links are 10 Gbps:
a. Verify that the IRF physical ports are located on the rear 10-GE expansion interface cards. The
following are available 10-GE expansion interface cards:
−Single-port 10G XFP interface card
−2-port 10G XFP interface card
−Short-haul 2-port 10G CX4 interface card
−2-port 10G SFP+ interface card
−2-port 10-GE interface card
b. Verify that the transceiver modules or cables for IRF connection are labeled with 10Gbps, XFP,
SFP+, or CX4.
c. Replace a transceiver module or cable if it is not for 10-Gbps connection.
4. Verify that the IRF port bindings and physical IRF link connections are correct:
IMPORTANT:
W
hen you connect two neighboring IRF members, you must connect the physical ports of IRF-port 1
on one member to the physical ports of IRF-port 2 on the other.
a. Execute the display irf configuration command on each member device, and check the
IRF-Port1 and IRF-Port2 fields for IRF port bindings.
b. Verify the following items:
−The physical ports on the same expansion interface card are bound to the same IRF port.
−When you are facing the rear panel, the physical ports bound to IRF-port 1 are on the left
and the physical ports bound to IRF-port 2 are on the right.
−The physical IRF connections are consistent with the IRF port bindings.
c. If there are binding errors or connection inconsistencies, reconfigure the IRF port bindings or
reconnect the physical IRF ports.
5. Verify that all IRF links are up:
a. Execute the display irf topology command, and then check the Link field.
b. If the Link field for an IRF port displays DOWN, execute the display interface command, and
then check the current state field.
−If all physical ports bound to the IRF port are down, bring them up.
−If the IRF port has at least one physical port in up state, go to step c.

6
c. Save the configuration, and then execute the irf-port-configuration active command in system
view to activate the IRF port configuration.
IMPORTANT:
A
ctivatin
g
IRF port confi
g
uration requires a reboot. To prevent confi
g
uration loss, you must save
the configuration before you execute the irf-port-configuration active command.
6. Verify that all member devices use the same software version:
a. Execute the display version command to identify the software version of each member device.
b. Upgrade the software of all member devices to the same version.
NOTE:
Typically, the irf auto-update enable command can automatically synchronize a member device with
the software version of the master device. However, the synchronization might fail when the gap
between the software versions is too large. For more information, see the release notes.
7. If the problem persists, contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting IRF.
Command Descri
p
tion
display interface
Displays interface information.
Use this command to verify that each IRF port has at least one physical
port in up state.
display irf Displays IRF fabric information, including the member ID, role, priority,
bridge MAC address, and description of each IRF member.
display irf configuration
Displays basic IRF settings, including the current member ID, new
member ID, and physical ports bound to the IRF ports on each IRF
member device. The new member IDs take effect at reboot.
display irf topology Displays the IRF fabric topology, including the member IDs, IRF port state,
and adjacencies of IRF ports.
display version Displays system version information.
irf-port-configuration active Activates IRF configuration on IRF ports.

7
Troubleshooting Ethernet link aggregation
This section provides troubleshooting information for common problems with Ethernet link aggregation.
Link aggregation failure
Symptom
Link aggregation does not operate correctly.

8
Troubleshooting flowchart
Figure 3 Troubleshooting link aggregation failure
Solution
To resolve the problem:
1. Verify that all physical connections are correct.
You can verify the physical connections against your network plan.
2. Verify that all member ports are up:
Are all physical connections correct?
Are all member ports up?
Connect physical links correctly
Bring all member ports up
No
Yes
No
Yes
Attribute configurations/class-two
configurations same as the reference port?
Set attribute configurations/class-two
configurations same as the reference
port
No
Yes
Set no more than 8 member ports
Yes
No
More than 8 member ports?
Attribute configurations/class-two configurations of the
peer ports same as the peer port of the reference port?
Set attribute configurations/class-two
configurations of the peer ports same
as the peer port of the reference port
No
Yes
End
Link aggregation
failed
Link aggregation in dynamic mode?
Yes
No
Resolved?
Resolved?
Resolved?
Resolved?
Resolved?
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Contact HP Support

9
a. Execute the display interface command to display the status of the member ports.
b. If the member ports are down, follow the solution in "Link up failure on a port" to troubleshoot
the problem.
3. Verify that the member ports have the same attribute configurations and class-two configurations
as the reference port:
a. Execute the display current-configuration interface command to display the configurations of
the aggregate interface and the member ports.
b. Configure the member ports to make sure they have the same attribute configurations and
class-two configurations as the reference port.
4. Identify the aggregation mode of the aggregation group.
{If the aggregation mode is static, proceed to step 6.
{If the aggregation mode is dynamic, proceed to step 5.
5. Verify that the peer member ports have the same attribute configurations and class-two
configurations as the peer port of the reference port:
a. Execute the display current-configuration interface command on the peer device to display the
configurations of the peer member ports.
b. Configure the peer member ports to make sure the peer ports have the same attribute
configurations and class-two configurations as the peer port of the reference port.
6. Verify that the number of member ports in the aggregation group does not exceed eight.
a. Execute the display link-aggregation verbose command to verify that the number of member
ports does not exceed eight.
If the number of member ports exceeds eight, the ports with higher port numbers are in
Unselected state.
b. Use the undo port link-aggregation group command to remove undesired member ports from
the aggregation group.
This ensures that all member ports you assign to the aggregation group can become Selected.
7. If the problem persists, contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting Ethernet link aggregation.
Commands Descri
p
tion
display current-configuration interface Displays interface configuration.
display interface Displays Ethernet interface information.
display link-aggregation verbose Displays detailed information about the aggregation groups
that correspond to the Layer 2 or Layer 3 aggregate interfaces.

13
Troubleshooting ports
This section provides troubleshooting information for common problems with ports.
Link up failure on a port
Symptom
A port cannot go up when the port is connected to another port.

14
Troubleshooting flowchart
Figure 4 Troubleshooting link up failure on a port
Solution
To resolve the problem:
1. Verify that the physical connection of the port is correct:

15
a. Unplug and then plug in the network cable of the port.
b. Verify that the port is up.
2. Verify that the port is not shut down:
a. Execute the display interface brief command.
b. Determine whether ADM appears in the second column of the output for the port.
c. If ADM appears, use the undo shutdown command to bring up the port.
3. Verify that the speed and duplex mode of the port match those of the peer port:
a. Execute the display interface brief command.
b. Determine whether the speed and duplex mode of the port match those of the peer port.
c. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
4. Examine the network cable quality or verify that the transceiver module type of the fiber port
matches the wavelength:
a. Replace the network cable with a new one, and verify that the port is up.
b. If the port is a fiber port, verify that the transceiver module type of the fiber port matches the
wavelength.
If the transceiver module information is not on the label, use the display transceiver interface
command to display the transceiver module information.
<Sysname>display transceiver interface ten-gigabitethernet 1/1/1
Ten-GigabitEthernet1/1/1 transceiver information:
Transceiver Type : 10G_BASE_SR_SFP
Connector Type : LC
Wavelength(nm) : 850
Transfer Distance(m) : 80(50um),30(62.5um)
Digital Diagnostic Monitoring : YES
Vendor Name : FINISAR CORP.
Ordering Name : SFP_XGE_SX-MM850
5. If the port is on a subcard, verify that the subcard is operating correctly:
a. Execute the display device command.
b. Determine whether Normal appears in the last column of the output for the subcard.
c. If Normal does not appear in the last column, re-plug in the subcard or replace the subcard
with a subcard of the same model.
[Sysname]display device
Slot 1
SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State
0 52 REV.C NULL 007 607 IVL MAIN Normal
1 2 REV.A NULL NULL NULL IVL 2*10GE Normal
6. Enable internal loopback testing on the port to verify that the physical port is operating correctly.
[Sysname-GigabitEthernet1/0/2]loopback internal
%Apr 26 12:40:25:309 2000 5500 IFNET/4/LINK UPDOWN:
GigabitEthernet1/0/2: link status is UP
%Apr 26 12:40:25:531 2000 5500 IFNET/4/LINK UPDOWN:
GigabitEthernet1/0/2: link status is DOWN
Loop internal succeeded!

16
7. If the problem persists, contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting ports.
Command Descri
p
tion
display device Displays device information.
display interface brief Displays brief interface information.
display transceiver interface Displays key parameters of the transceiver module installed in an
interface.
loopback internal Enables loopback testing on an Ethernet interface.

17
Troubleshooting other problems
High CPU usage
Symptom
The display cpu-usage command shows that the CPU usage is high.
Troubleshooting flowchart
Figure 5 Troubleshooting high CPU usage
Solution
To resolve the problem:
1. Locate the tasks that are using CPU resources.
Use the display cpu-usage task [ slot slot-id ] command in hidden view to display CPU usage
information. Locate the tasks that are using CPU resources.
2. Analyze the tasks that are using CPU resources.
The following are common tasks that use CPU resources:
{bRX1 and bRX2
If these tasks are using CPU resources, the switch might be receiving large amounts of packets
that need to be forwarded to the CPU. Do the following:

18
−Use the display interface command to see whether interfaces have received large amounts
of broadcast packets.
−Identify whether a loop exists on the network. If a loop exists, examine the connections
between the devices.
{MSTP
Use the display stp bpdu-statistics interface command to view the statistics for received and
sent BPDU packets on ports. Examine the counts of TCN/TC packets. If the switch receives a
large quantity of TCN/TC packets generated by STP, the switch has to delete MAC address
entries frequently. This results in high CPU usage.
{AGNT
Examine the network management software. Frequent MIB information browsing might result
in high CPU usage.
{ROUT
Use the display ip routing-table command to examine route changes. Route flapping might
cause high CPU usage.
{L2X0 or L2X1 MAC address synchronization
Examine whether the network topology is stable. If the network topology is not stable, the
device has to use a lot of CPU resources to update its MAC address entries frequently.
3. If the problem persists, contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting high CPU usage.
Command Descri
p
tion
_hidecmd Enters hidden view.
display cpu-usage task [ slot slot-id ]Displays CPU usage information. This command is available in
hidden view.
display interface Displays Ethernet interface information.
display ip routing-table Displays brief information about active routes in the routing
table.
display stp bpdu-statistics interface Displays the BPDU statistics for a port.
Layer 2 forwarding failure
Symptom
Layer 2 packet loss occurs between two devices on the same network segment and in the same VLAN.

19
Troubleshooting flowchart
Figure 6 Troubleshooting Layer 2 packet loss failure
Solution
To resolve the problem:
1. Verify that no error packets have been received on the local port:
a. Execute the display interface command and check for error packets.
<HP>display interface GigabitEthernet1/0/36
GigabitEthernet1/0/36 current state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 000f-e200-002b
……
Last 300 seconds output: 0 packets/sec 10 bytes/sec 0%
Input (total): 57 packets, 7838 bytes
0 unicasts, 50 broadcasts, 2 multicasts, 0 pauses
Input (normal): 52 packets, - bytes

20
0 unicasts, 50 broadcasts, 2 multicasts, 0 pauses
Input: 5 input errors, 0 runts, 0 giants, 0 throttles
5 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
b. If the statistics are not zero, the following failures might occur:
−Interface hardware failure—To test such a failure, connect the cable that is connected to the
local port to a correctly operating port (for example, Port A) that has the same
configurations as the local port. If Port A forwards traffic correctly, you can determine that
the hardware of the local port fails. In this event, you must replace the local port with a
correctly operating port.
−Transceiver module, fiber, or twisted pair failure—To test and solve such a failure, replace
the faulty transceiver module, fiber, or twisted pair with a good one.
−Inconsistent configurations—Verify that the configurations (such as speed and duplex mode)
of the peer are consistent with the local port. If they are inconsistent, modify the
configurations of the local port.
c. If the problem persists, contact HP Support.
2. Verify that packets are not mistakenly filtered out by ACLs:
a. Examine the ACL and QoS policy configuration for packet filtering on the port, on the VLAN of
the port, or globally. If packets are mistakenly filtered out, modify the ACL or QoS policy
configuration.
−To display the ACL configuration on the port for packet filtering, execute the display
packet-filter command.
−To display the QoS policy configuration on the port, execute the display qos policy
command.
−To display the QoS policy configuration on the VLANs of the port, execute the display qos
vlan-policy command.
−To display the global QoS policy configuration, execute the display qos policy global
command.
b. Determine whether packets are filtered out by automatically created ACLs.
The following features automatically create ACLs:
−IP source guard—Configured by using the ip source binding or ip verify source command.
To display source guard binding entries, execute the display ip source binding or display
ipv6 source binding command. If IP source guard is configured but the packets do not match
any entries, further troubleshoot the problem based on the way the binding entries are
created.
−Portal authentication—When portal authentication is configured, the port discards the
packets of unauthenticated users. To display the portal configuration of the port or the
VLANs of the port, execute the display portal interface command. To cancel the portal
configuration on the port, execute the undo portal command in Layer 2 Ethernet interface
view. To cancel the portal configuration on the VLAN of the port, execute the undo portal
server server-name command on the corresponding VLAN interface.
−EAD fast deployment—When EAD fast deployment is enabled, the port discards packets of
unauthenticated users except when the users access only a free IP. To display whether EAD
fast deployment is enabled on the port, execute the display dot1x command.
3. Verify that the port is not blocked: