H3C s5800 series User manual

H3C S5820X & S5800 Switch Series
Troubleshooting Guide
Copyright © 2014 Hangzhou H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means
without prior written consent of Hangzhou H3C Technologies Co., Ltd.
The information in this document is subject to change without notice.

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 ·······································································································································5
Solution······································································································································································6
Related commands····························································································································································7
Troubleshooting Ethernet link aggregation················································································································· 8
Link aggregation failure ···················································································································································8
Symptom····································································································································································8
Troubleshooting flowchart ·······································································································································9
Solution······································································································································································9
Related commands························································································································································· 10
Troubleshooting ports·················································································································································13
Link up failure on a port ················································································································································ 13
Symptom································································································································································· 13
Troubleshooting flowchart ···································································································································· 13
Solution··································································································································································· 13
Related commands························································································································································· 15
Troubleshooting other problems································································································································16
Layer 2 forwarding failure ············································································································································ 16
Symptom································································································································································· 16
Troubleshooting flowchart ···································································································································· 16
Solution··································································································································································· 17
Related commands ················································································································································ 19
Layer 3 forwarding failure ············································································································································ 20
Symptom································································································································································· 20
Troubleshooting flowchart ···································································································································· 20
Solution··································································································································································· 20
Related commands ················································································································································ 21
SFP+ port not coming up··············································································································································· 21
Symptom································································································································································· 21
Troubleshooting flowchart ···································································································································· 22
Solution··································································································································································· 22
Related commands ················································································································································ 22
PoE power supply anomaly ·········································································································································· 23
Symptom································································································································································· 23

ii
Troubleshooting flowchart ···································································································································· 23
Solution··································································································································································· 23
Related commands ················································································································································ 25

1
Introduction
This document is not specific to any software version or device model.
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 the "Reason: Not enough hardware resource" message.
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 H3C 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.
End
Failure to apply an ACL
Contact H3C Support
No
Yes
Resolved?
No
Yes
Reconfigure QoS
policy/packet filter
Yes
No
ACL rule
configured correctly?
QoS policy/packet filter
configured correctly?
Reconfigure ACL rule
Resolved?
No
Yes

3
−If they are configured incorrectly, reconfigure them.
−If they are configured correctly, go to Step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
{If the ACL is configured incorrectly, reconfigure it.
{If the ACL is configured correctly but the problem persists, contact H3C Support.
3. If the problem persists, contact H3C 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 configuration is correct:
a. Execute the display packet-filter command.
b. If there are any configuration errors, reconfigure the packet filter.
2. Verify that the ACL configuration is correct:
a. Execute the display acl command.
b. If there are any configuration errors, reconfigure the ACL.
3. If the problem persists, contact H3C 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 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 qos policy global Displays information about global QoS policies.
display qos policy control-plane Displays information about the QoS policies applied to the
specified control plane.
display traffic classifier user-defined Displays traffic class configurations.
display traffic behavior user-defined Displays traffic behavior configurations.
display packet-filter Displays whether an ACL has been successfully applied to an
interface for packet filtering.

4
Troubleshooting IRF
This section provides troubleshooting information for common problems with IRF.
IRF fabric establishment failure
Symptom
An IRF fabric cannot be established.

5
Troubleshooting flowchart
Figure 2 Troubleshooting IRF fabric establishment failure
No
Yes
No
Yes
No
Yes
End
IRF fabric setup failed
No
No
Yes
Yes
Contact H3C Support
No
Yes
Resolved?
No
Yes
Yes
No
Yes No
Yes
Remove excess
member chassis
Yes
No
All member IDs are unique?
Modify bindings or
reconnect physical ports
IRF fabric size allowed?
Physical IRF
connections consistent with
IRF port bindings?
No Resolved?
IRF links up? Bring up physical
ports/activate IRF port
configuration Resolved?
All chassis use same
software version? Upgrade software version to be the same Resolved?
Software versions
compatible? Upgrade software Resolved?
Change member IDs
Resolved?
No
Yes
10-Gbps IRF links used?
Yes No
Yes
Replace with 10 Gbps
or SFP+ transceiver
modules/cables
No Resolved?

6
Solution
To resolve the problem:
1. Verify that the number of member chassis does not exceed the upper limit (nine).
If you are adding new chassis to an existing IRF fabric, use the display irf command to identify the
number of member chassis already in the chassis.
2. Verify that the member ID of each member chassis is unique:
a. Execute the display irf configuration command to view the member ID of each chassis.
b. If two member chassis use duplicate IDs, assign a unique member ID to each member.
3. Verify that the physical IRF links are connected correctly:
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 chassis, and check the
IRF-Port1 and IRF-Port2 fields for IRF port bindings.
b. Verify that the physical IRF connections are consistent with the IRF port bindings.
c. If there are inconsistencies, reconfigure the IRF port bindings or reconnect the physical IRF
ports.
4. Verify that IRF links are 10 Gbps:
a. Verify that the transceiver modules or cables for IRF connection are labeled with 10Gbps or
SFP+.
b. Replace a transceiver module or cable if it is not for 10 Gbps connection.
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, proceed to the next step.
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 chassis 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 chassis to the same version.

7
NOTE:
Typically the irf auto-update enable command can automatically synchronize a member chassis with
the software version of the master chassis. However, the synchronization might fail when the gap
between the software versions is large.
7. If the problem persists, contact H3C 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.

8
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.

9
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 H3C Support

10
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 makes sure all member ports you assign to the aggregation group can become Selected.
7. If the problem persists, contact H3C 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
Display 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.
Troubleshooting flowchart
Figure 4 Troubleshooting link up failure on a port
Solution
To resolve the problem:
Physically connected?
Shut down?
Check the port
connection
undo shutdown
No
Yes
Yes
No
Cable is correct or transceiver
module matches wavelength? Replace the cable
or fiber
No
Yes
Subcard is operating correctly
if the interface is on a subcard?
Install the subcard
again or replace a
subcard
No
Yes
A port failed to go
up
End
Yes
Yes
Yes
Yes
Resolved?
Resolved?
Resolved?
No
No
No
No
Enable internal loopback
testing to examine the physical
port
Contact H3C Support
Resolved?

14
1. Verify that the physical connection of the port is correct:
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. Check 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. Check 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. Check 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-GigabitEthernet1/0/2]display device
Slot 1
SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State
0 52 Ver.B NULL 003 003 018 IVL MAIN Normal
1 4 Ver.A NULL 002 NULL IVL LSW1SP4P0 Normal
2 16 Ver.A NULL 001 NULL IVL LSW1GP16P0 Normal
3 1 Ver.A NULL 000 NULL IVL LSWM1IPS10 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 60CPWR IFNET/4/LINK UPDOWN:
GigabitEthernet1/0/2: link status is UP

15
%Apr 26 12:40:25:531 2000 60CPWR IFNET/4/LINK UPDOWN:
GigabitEthernet1/0/2: link status is DOWN
Loop internal succeeded!
7. If the problem persists, contact H3C 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.

16
Troubleshooting other problems
Layer 2 forwarding failure
Symptom
Layer 2 packet loss occurs between two devices on the same network segment and in the same VLAN.
Troubleshooting flowchart
Figure 5 Troubleshooting Layer 2 packet loss failure
Incoming error packets?
No
Yes
Yes Locate the
reasons of the
failure
End
No
Yes
Layer 2 packet loss
Packets filtered by
ACLs or QoS policies?
Locate the
reasons and solve
the failure
Port blocked?
No
Yes
Port misconfigurations?
No
Locate and modify
misconfigurations
Yes
Port congestion?
No
Locate and solve
congestion
Yes
Resolved?
No
No
No
No
No
Yes
Yes
Yes
Yes
Resolved?
Resolved?
Resolved?
Resolved?
Contact H3C Support
Locate the
reasons and solve
the failure

17
Solution
To solve 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.
<H3C>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
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) with 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 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 H3C 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. Examine 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

18
ipv6 source binding command. If IP source guard is configured but the packets match no
entry, 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 only access a free IP. To display whether EAD
fast deployment is enabled on the port, execute the display dot1x command.
−MFF—To display the MFF configuration information of the VLAN to which the port belongs,
execute the display mac-forced-forwarding vlan command. If the output does not contain
the gateway information, examine whether the ARP snooping or DHCP snooping
configuration is correct.
3. Verify that the port is not blocked:
{Execute the display stp brief command to determine whether STP sets the state of the port to
discarding. When the port is in discarding state, it cannot forward traffic. H3C recommends
disabling STP on the port, or configuring the port as an edge port if the port is connected to a
terminal device.
{If the port belongs to an aggregation group, execute the display link-aggregation verbose
command to identify the port status. When the port is an Unselected port, it cannot forward
traffic. Locate the reasons why the port is in Unselected state. For example, the attribute
configurations of the port are different from the configurations of the reference port.
{Execute the display rrpp verbose command to determine whether the port is down or RRPP sets
the state of the port to blocked. When the port is in down or blocked state, it cannot forward
traffic.
−If the port is in down state, examine whether the port is physically or administratively shut
down.
−If the port is in blocked state, find the reasons. For example, the roles of the primary and
secondary port on the master node are reversed, or the broadcast storm suppression
mechanism blocks the port because SRPT failure occurs in a multi-homed subring.
{Execute the display smart-link group command to determine whether Smart Link sets the state
of the port to standby or down. When the port is in standby or down state, it cannot forward
traffic.
If the port is in standby state, set the port as the primary port.
If the port is in down state, the follow reasons might apply, and further troubleshooting is
required:
−The uplink device is configured with Monitor link, and its uplink is down.
−The link between the local port and its peer fails.
−The local port is administratively shut down.
4. Examine the following configurations that might cause packet loss:
{VLAN configuration—Execute the display this command in Ethernet interface view to display
whether the port is in the VLAN of the packets. If not, add the port to the VLAN.
{Blackhole MAC address entries—Execute the display mac-address blackhole command to
display blackhole MAC address entries. If the packets are discarded because they match a

19
blackhole MAC address entry, delete the entry. To delete the blackhole MAC address entry,
execute the undo mac-address blackhole mac-address vlan vlan-id command.
{Rate limit—Execute the display qos lr interface command to display the rate limit configuration
on the port. If rate limit is configured on the port, make sure the committed information rate (CIR)
and the committed burst size (CBS) are appropriate. To adjust the CIR and CBS values, execute
the qos lr { inbound | outbound } cir committed-information-rate [ cbs committed-burst-size ]
command.
{Storm suppression—Execute the display this command in Ethernet interface view to display the
configuration of storm suppression. Storm suppression includes broadcast suppression,
multicast suppression, and unknown unicast suppression. To adjust the suppression thresholds,
execute the broadcast-suppression, multicast-suppression, and unicast-suppression
commands, respectively.
5. Verify that no congestion occurs by using the display qos queue-statistics interface command.
If congestion occurs, locate and solve the problem by referencing related congestion management
documents.
6. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting Layer 2 packet loss failure.
Command Descri
p
tion
display interface Displays Ethernet interface information.
display packet-filter Displays whether an ACL has been successfully
applied to an interface for packet filtering.
display qos policy Displays user-defined QoS policy configuration
information.
display qos policy interface Displays information about the QoS policies applied
to an interface or all interfaces.
display qos vlan-policy Displays information about QoS policies applied to
VLANs.
display qos policy global Displays information about global QoS policies.
display this Displays the running configuration in the current
view.
display ip source binding/display ipv6 source binding
Displays source guard binding entries.
display portal interface Displays the portal configuration of an interface.
display dot1x Displays information about 802.1X.
display mac-forced-forwarding vlan Displays the MFF configuration information of a
VLAN.
display link-aggregation verbose Displays detailed information about the aggregation
groups that correspond to the aggregate interfaces.
display rrpp verbose Displays detailed RRPP information.
display smart-link group Displays information about the specified or all smart
link groups.