H3C S5150-EI Series User manual

H3C S5150-EI Switch Series
Troubleshooting Guide
Document version: 6W101-20171222
Copyright © 2017 New 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 New H3C Technologies Co., Ltd.
The information in this document is subject to change without notice.

i
Contents
Introduction·····················································································1
General guidelines ·····················································································································1
Collecting log and operating information ·························································································1
Collecting common log messages···························································································2
Collecting diagnostic log messages·························································································2
Collecting operating statistics·································································································3
Troubleshooting hardware··································································5
Unexpected switch reboot············································································································5
Symptom···························································································································5
Troubleshooting flowchart ·····································································································5
Solution·····························································································································5
Operating power module failure (for switch models that support removable power modules)······················6
Symptom···························································································································6
Solution·····························································································································6
Newly-installed power module failure (for switch models that support removable power modules)···············7
Symptom···························································································································7
Solution·····························································································································7
Fan tray failure ··························································································································7
Symptom···························································································································7
Solution·····························································································································7
Related commands ····················································································································8
Troubleshooting ACL ········································································9
ACL application failure with an error message··················································································9
Symptom···························································································································9
Solution·····························································································································9
ACL application failure without an error message··············································································9
Symptom···························································································································9
Troubleshooting flowchart ···································································································10
Solution···························································································································10
Related commands ··················································································································11
Troubleshooting IRF ·······································································12
IRF fabric establishment failure···································································································12
Symptom·························································································································12
Troubleshooting flowchart ···································································································13
Solution···························································································································13
Related commands ··················································································································15
Troubleshooting Ethernet link aggregation···········································16
Link aggregation failure·············································································································16
Symptom·························································································································16
Troubleshooting flowchart ···································································································17
Solution···························································································································17
Related commands ··················································································································18
Troubleshooting ports ·····································································19
A fiber port fails to come up········································································································19
Symptom·························································································································19
Troubleshooting flowchart ···································································································19
Solution···························································································································19
A copper port fails to come up ····································································································20
Symptom·························································································································20
Troubleshooting flowchart ···································································································21
Solution···························································································································21
Related commands ··················································································································22

ii
Troubleshooting other problems························································23
Layer 2 forwarding failure ··········································································································23
Symptom·························································································································23
Troubleshooting flowchart ···································································································23
Solution···························································································································24
Related commands············································································································27
Layer 3 forwarding failure ··········································································································28
Symptom·························································································································28
Troubleshooting flowchart ···································································································28
Solution···························································································································29
Related commands············································································································29
Protocol flapping······················································································································29
Symptom·························································································································29
Troubleshooting flowchart ···································································································30
Solution···························································································································30
PoE power supply anomaly········································································································31
Symptom·························································································································31
Troubleshooting flowchart ···································································································31
Solution···························································································································31
Related commands············································································································33

1
Introduction
This document provides information about troubleshooting common software and hardware
problems with H3C S5150-EI Switch Series.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a failure from causing loss of configuration, save the configuration each time you finish
configuring a feature. For configuration recovery, regularly back up the configuration to a remote
server.
When you troubleshoot the switch, follow these general guidelines:
•To help identify the failure cause, collect system and configuration information, including:
{Symptom, time of failure, and configuration.
{Network topology information, including the network diagram, port connections, and points
of failure.
{Log messages and diagnostic information. For more information about collecting this
information, see "Collecting log and operating information."
{Physical evidence of failure:
−Photos of hardware.
−Status of the LEDs.
{Measures you have taken, such as reconfiguration, cable swapping, and reboot.
{Output from the commands executed during the troubleshooting process.
•To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware
component.
•If hardware replacement is required, use the release notes to verify the hardware and software
compatibility.
Collecting log and operating information
IMPORTANT:
By default, the information center is enabled. If the feature is disabled, you must use the info-cente
r
enable command to enable the feature for collecting log messages.
Table 1 shows the types of files that the system uses to store operating log and status information.
You can export these files by using FTP or TFTP.
In an IRF system, these files are stored on the master device. Multiple devices will have log files if
master/subordinate switchovers have occurred. You must collect log files from all these devices. To
more easily locate log information, use a consistent rule to categorize and name files. For example,
save log files to a separate folder for each member device, and include their slot numbers in the
folder names.

2
Table 1 Log and operating information
Category File name format Content
Common log logfile.log Log messages about command executions, event occurrences,
state changes, and so on.
Diagnostic log diagfile.log
Diagnostic log messages about device operation, including the
following items:
•Parameter settings used when an error occurs.
•Information about a card startup error.
•Handshaking information between member devices when
a communication error occurs.
Operating
statistics file-basename.tar.gz
IMPORTANT:
Current operating statistics for feature modules, including the
following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
Collecting common log messages
1. Save the common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the flash memory on each member
device.
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each member device:
# Display the log file on the master device.
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
524288 KB total (107944 KB free)
# Display the log file on each subordinate device (subordinate device 2 for example):
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
524288 KB total (107944 KB free)
3. Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)
Collecting diagnostic log messages
1. Save the diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.

3
By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each
member device.
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
2. Identify the diagnostic log file on each member device:
# Display the diagnostic log file on the master device.
<Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log
524288 KB total (107944 KB free)
# Display the diagnostic log file on each subordinate device (subordinate device 2 for example):
<Sysname> dir slot2#flash:/diagfile/
<Sysname> dir slot2#flash:/diagfile/
Directory of slot2#flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log
524288 KB total (107944 KB free)
3. Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)
Collecting operating statistics
You can collect operating statistics by saving the statistics to a file or displaying the statistics on the
screen.
When you collect operating statistics, follow these guidelines:
•Log in to the device through a network port or management port (if any) instead of the console
port as long as possible. Network and management ports are faster than the console port.
•Do not execute commands during operating statistics collection.
•To ensure information completeness, H3C recommends that you save the statistics to a file.
NOTE:
The amount of time to collect statistics increases along with the number of IRF member devices.
To collect operating statistics:
1. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
2. At the prompt, choose to save or display operating statistics:
# To save operating statistics, enter yat the prompt and then specify the destination file path.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :y
Please input the file name(*.tar.gz)
[flash:/diag_Sysname_20160101-000704.tar.gz] :flash:/diag.tar.gz
Diagnostic information is outputting to flash:/diag.tar.gz.
Please wait...
Save successfully.

4
<Sysname> dir flash:/
Directory of flash:
…
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz
524288 KB total (107944 KB free)
# To display operating statistics on the monitor terminal, enter nat the prompt. (The output from
this command varies by software version.)
Save or display diagnostic information (Y=save, N=display)? [Y/N] :N
===============================================
===============display clock===============
09:36:03 UTC Fri 01/01/2016
=================================================
---- More ----

5
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
This section describes how to troubleshoot unexpected switch reboot, removable power modules,
and fixed fan trays. To troubleshoot transceiver modules and ports, see "Troubleshooting ports."
Unexpected switch reboot
Symptom
The switch reboots unexpectedly when it is operating.
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
Solution
To resolve the problem:
1. Verify that you can access the CLI.

6
{If you can access the CLI, execute the display diagnostic-information command to
collect operating statistics.
{If you cannot access the CLI, go to step 2.
2. Verify that the system software image on the switch is correct.
Log in to the switch through the console port and restart the switch. If the system reports that a
CRC error has occurred or that no system software image is available during the BootWare
loading process, reload the system software image on the BootWare menu and configure it as
the current system software image.
3. If the problem persists, contact H3C Support.
Operating power module failure (for switch
models that support removable power modules)
Symptom
A trap or log is generated indicating that an operating power module is faulty.
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal DC -- -- --
2 Fault AC -- -- --
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. Remove and reinstall the power module to make sure the power module is installed correctly.
Then, execute the display power command to verify that the power module has changed to
Normal state. If the power module remains in Absent state, replace the power module.
3. When the power module is in Fault state, perform the following tasks:
a. Verify that the power module has not been disconnected from the power source. If it has
been disconnected from the power source, connect the power source to it.
b. Verify that the power module surface is clean. If there is dust accumulated on the power
module, remove the dust. Then remove and reinstall the power module. Execute the
display power command to verify that the power module has changed to Normal state. If
the power module remains in Fault state, go to step c.
c. Install the power module into an empty power module slot. Then execute the display power
command to verify that the power module has changed to Normal state in the new slot. If
the power module remains in Fault state, replace the power module.
4. If the problem persists, contact H3C Support.

7
Newly-installed power module failure (for switch
models that support removable power modules)
Symptom
A trap or log is generated indicating that a newly-installed power module is faulty.
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal DC -- -- 0
2 Fault AC -- -- 0
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. When the power module is in Absent state, perform the following tasks:
a. Remove and reinstall the power module to make sure the power module is installed
securely. Then execute the display power command to verify that the power module has
changed to Normal state. If the power module remains in Absent state, go to step b.
b. Remove and install the power module into an empty power module slot. Then execute the
display power command to verify that the power module has changed to Normal state in
the new slot. If the power module remains in Absent state, go to step 4.
3. Remove and install the power module into an idle power module slot. Then execute the display
power command to verify that the power module has changed to Normal state in the new slot.
If the power module remains in Fault state, go to step 4.
4. If the problem persists, contact H3C Support.
Fan tray failure
Symptom
A fan tray is not operating correctly. The display fan command displays that the fan tray is in Fault
state.
<Sysname> display fan
Slot 1:
Fan 1:
State : Normal
Fan 2:
State : Fault
Solution
Contact H3C Support to resolve the problem.

8
Related commands
This section lists the commands that you might use for troubleshooting fan trays.
Command Description
display fan Displays fan tray operating status information.

9
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 an ACL-based QoS policy to the hardware. It also displays
the "Reason: Not enough hardware resource" message.
Solution
To resolve the problem:
1. Execute the display qos-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 for packet filtering or QoS classification, remove unused ACLs.
3. If the problem persists, contact H3C Support.
ACL application failure without an error message
Symptom
The system applies a packet filter or an ACL-based QoS policy to the hardware. However, the ACL
does not take effect.

10
Troubleshooting flowchart
Figure 2 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.
2. Verify that the ACL is configured correctly.

11
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, go to step 3.
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 is configured correctly.
Execute the display packet-filter command to check whether the packet filter is configured
correctly.
{If there are any configuration errors, reconfigure the packet filter.
{If there is no configuration error, 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, go to step 3.
3. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting ACLs.
Command Description
display packet-filter Displays whether an ACL has been successfully applied to
an interface for packet filtering.
display qos-acl resource Displays QoS and ACL resource usage.
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 configuration.
display traffic behavior user-defined Displays traffic behavior configuration.

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

13
Troubleshooting flowchart
Figure 3 Troubleshooting IRF fabric establishment failure
Solution
To resolve the problem:
1. Verify that the number of member devices does not exceed the upper limit (varies by software
version).
If you are adding a new member device to an existing IRF fabric or merging IRF fabrics, use the
display irf command to identify the number of member devices in the IRF fabrics. If the total
number of member devices exceeds the upper limit, the IRF setup will fail.
No
Yes
No
Yes
No
Yes
IRF setup
failure
No
No
Yes
Yes
No
Yes
Resolved?
No
Yes
Yes
No
Yes No
Yes
You cannot add devices to the
IRF fabric
Yes
No
Member ID unique?
Modify IRF port bindings or
reconnect physical ports
Number of members
fewer than the upper limit?
IRF port bindings
or physical IRF connections
correct?
No Resolved?
10-Gbps IRF links used? Replace with 10-Gbps
transceiver modules/cables Resolved?
(Optional.)
Transceiver modules at link ends are
the same type?
Replace the transceiver
modules to be the same type Resolved?
IRF links up? Bring up the IRF links/activate
IRF port configuration Resolved?
Assign a unique member ID to
each member device
Contact H3C
Support End
Same software version? Upgrade software to the same
version in the fabric Resolved?
No
Yes
No
Yes

14
2. Verify that the member ID of each member device is unique:
a. Execute the display irf command to view the member ID of each member device.
b. Assign a unique member ID to each member.
−If you are adding a new member device to an existing IRF fabric, assign the member
device a member ID that is not being used in the IRF fabric.
−If you are merging IRF fabrics, make sure each member device in these IRF fabrics has
a unique member ID.
3. Verify that the IRF port bindings and physical IRF link connections are correct:
IMPORTANT:
When 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 that 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.
4. Verify that the IRF physical interfaces are 10GBase-T Ethernet ports or SFP+ ports.
{If the IRF physical interfaces are 10GBase-T Ethernet ports, verify that category 6A or
above twisted pair cables are used for IRF connections.
{If the IRF physical interfaces are SFP+ ports, verify that the transceiver modules or cables
for IRF connections are labeled with 10Gbps or SFP+. If you use transceiver modules and
fibers for IRF connections, make sure the transceivermodules at the two ends of the link are
the same type.
5. Verify that all IRF links are up:
a. Execute the display irf topology command, and then check the Link field.
−If the Link field for each IRF port does not display DOWN, go to step 6.
−If
the Link field for an IRF port displays DOWN, go to step b.
b. Execute the display irf link command, and then check the Status field of the physical ports
bound to the IRF port.
−If the field displays DOWN or ADM (administratively down) for all the physical ports,
remove the link failures or use the undo shutdown command to bring up the
administratively down ports.
−If the field displays UP for a minimum of one of the physical ports, go to step c.
c. Save the configuration, and then execute the irf-port-configuration active command in
system view to activate the IRF port configuration.
IMPORTANT:
Activating IRF port configuration requires a reboot. To prevent configuration 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. As a best practice,
upgrade the earlier versions to the most recent version.

15
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 H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting IRF.
Command Description
display interface Displays interface information.
Use this command to verify that each IRF port has a minimum of 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.
undo shutdown Brings up an Ethernet interface or subinterface.

16
Troubleshooting Ethernet link
aggregation
This section provides troubleshooting information for common problems with Ethernet link
aggregation.
Link aggregation failure
Symptom
Some member ports fail to be placed in Selected state, and link aggregation does not operate
correctly.

17
Troubleshooting flowchart
Figure 4 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:
a. Execute the display interface command to display the status of the member ports.