H3C S6800 Series User manual

H3C S6800 Switch Series Troubleshooting
Guide
Document version: 6W100-20171220
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
Contacting technical support ········································································································4
Troubleshooting hardware··································································1
Unexpected switch reboot············································································································1
Symptom···························································································································1
Troubleshooting flowchart ·····································································································1
Solution·····························································································································2
Operating power module failure ····································································································2
Symptom···························································································································2
Troubleshooting flowchart ·····································································································2
Solution·····························································································································3
Newly installed power module failure······························································································3
Symptom···························································································································3
Troubleshooting flowchart ·····································································································4
Solution·····························································································································4
Fan tray failure ··························································································································5
Symptom···························································································································5
Troubleshooting flowchart ·····································································································5
Solution·····························································································································5
Related commands ····················································································································6
Troubleshooting ACL ········································································7
ACL application failure with an error message··················································································7
Symptom···························································································································7
Solution·····························································································································7
ACL application failure without an error message··············································································7
Symptom···························································································································7
Troubleshooting flowchart ·····································································································8
Solution·····························································································································8
Related commands ····················································································································9
Troubleshooting IRF ·······································································11
IRF fabric setup failure··············································································································11
Symptom·························································································································11
Troubleshooting flowchart ···································································································12
Solution···························································································································13
Related commands ··················································································································15
Troubleshooting Ethernet link aggregation···········································17
Link aggregation failure·············································································································17
Symptom·························································································································17
Troubleshooting flowchart ···································································································18
Solution···························································································································18
Related commands ··················································································································19
Troubleshooting ports ·····································································20
A 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up ·····································20
Symptom·························································································································20
Troubleshooting flowchart ···································································································20
Solution···························································································································20
A 10/100/1000Base-T GE copper port or 1/10GBase-T 10-GE copper port fails to come up·····················22

ii
Symptom·························································································································22
Troubleshooting flowchart ···································································································22
Solution···························································································································22
Non-H3C transceiver module error message ·················································································23
Symptom·························································································································23
Troubleshooting flowchart ···································································································23
Solution···························································································································23
Transceiver module does not support digital diagnosis·····································································24
Symptom·························································································································24
Troubleshooting flowchart ···································································································24
Solution···························································································································24
Error frames (for example, CRC errors) on a port············································································25
Symptom·························································································································25
Troubleshooting flowchart ···································································································25
Solution···························································································································26
Failure to receive packets··········································································································27
Symptom·························································································································27
Troubleshooting flowchart ···································································································27
Solution···························································································································27
Failure to send packets ·············································································································28
Symptom·························································································································28
Troubleshooting flowchart ···································································································29
Solution···························································································································29
Related commands ··················································································································30
Troubleshooting EVPN····································································31
EBGP or IBGP neighbor relationship setup failure···········································································31
Symptom·························································································································31
Troubleshooting flowchart ···································································································31
Solution···························································································································31
ECMP forwarding failure············································································································32
Symptom·························································································································32
Troubleshooting flowchart ···································································································33
Solution···························································································································33
VXLAN tunnel establishment failure·····························································································34
Symptom·························································································································34
Troubleshooting flowchart ···································································································35
Solution···························································································································35
VXLAN tunnel forwarding failure··································································································35
Symptom·························································································································35
Troubleshooting flowchart ···································································································36
Solution···························································································································36
Related commands ··················································································································37
Troubleshooting system management ················································38
High CPU utilization··················································································································38
Symptom·························································································································38
Troubleshooting flowchart ···································································································38
Solution···························································································································38
High memory utilization·············································································································40
Symptom·························································································································40
Troubleshooting flowchart ···································································································40
Solution···························································································································40
Related commands ··················································································································41
Troubleshooting other problems························································42
Layer 2 forwarding failure ··········································································································42
Symptom·························································································································42
Troubleshooting flowchart ···································································································42
Solution···························································································································42
Related commands············································································································45
Layer 3 forwarding failure ··········································································································45

iii
Symptom·························································································································45
Troubleshooting flowchart ···································································································46
Solution···························································································································46
Related commands············································································································47
Protocol flapping······················································································································47
Symptom·························································································································47
Troubleshooting flowchart ···································································································47
Solution···························································································································47

1
Introduction
This document provides information about troubleshooting common software and hardware
problems with the S6800 switch series.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a problem 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 cause of the problem, 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 the hardware.
−Status of the LEDs.
{Steps 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, TFTP, or USB.
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 Command execution and operational log messages.
Diagnostic log diagfile.log
Diagnostic log messages about device operation, including the
following items:
•Parameter settings in effect when an error occurs.
•Information about a card startup error.
•Handshaking information between member devices when a
communication error occurs.
Operating
statistics file-basename.gz
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 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 (134600 KB free)
# Display the log file on each subordinate device:
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
524288 KB total (134600 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)
Collecting diagnostic log messages
1. Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.
By default, the diagnostic log file is saved in the diagfile directory of the Flash memory on each
member device.
<Sysname> diagnostic-logfile save

3
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 (134600 KB free))
# Display the diagnostic log file on each subordinate device:
<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 (134600 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (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 or management port instead of the console port, if
possible. Network and management ports are faster than the console port.
•Do not execute commands while operating statistics are being collected.
•As a best practice, save operating statistics to a file to retain the information.
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] :
Diagnostic information is outputting to flash:/diag_Sysname_20160101-000704.tar.gz.
Please wait...
Save successfully.
<Sysname> dir flash:/
Directory of flash:
…
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz
524288 KB total (134600 KB free)

4
# 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===============
23:49:53 UTC Tue 01/01/2016
=================================================
……
3. View diagnostic information:
a. Extract the file that contains diagnostic information.
<Sysname> tar extract archive-file diag_Sysname_20160101-000704.tar.gz
Extracting archive flash:/diag_Sysname_20160101-000704.tar.gz Done.
<Sysname> gunzip diag_Sysname_20160101-000704.gz
Decompressing file flash:/diag_Sysname_20160101-000704.gz.... Done.
b. View diagnostic information in the file.
<Sysname> more diag_Sysname_20160101-000704
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
---- More ----
Contacting technical support
If you cannot resolve a problem after using the troubleshooting procedures in this document, contact
H3C Support. When you contact an authorized H3C support representative, be prepared to provide
the following information:
•Information described in "General guidelines."
•Product serial numbers.
This information will help the support engineer assist you as quickly as possible.
The following is the contact information for H3C Support:
•Telephone number—400-810-0504.
•E-mail—[e-mail].

1
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
This section describes how to troubleshoot unexpected switch reboot, power module failure, and fan
tray failure. To troubleshoot ports, see "Troubleshooting ports."
Unexpected switch reboot
Symptom
The switch reboots unexpectedly when it is operating.
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot

2
Solution
To resolve the problem:
1. Verify that you can access the CLI after the switch reboots.
{If you can access the CLI, execute the display diagnostic-information command to
collect operating information.
{If you cannot access the CLI, go to step 2.
2. Verify that the system software image on the switch is correct.
Connect to the switch through the console port and restart the switch. If BootWare reports that
a CRC error has occurred or that no system software image is available, perform the following
steps:
a. Use the BootWare menu to reload the system software image.
b. Configure it as the current system software image.
3. If the problem persists, contact H3C Support.
Operating power module failure
Symptom
A trap or log is generated indicating that an operating power module is faulty.
Troubleshooting flowchart
Figure 2 Troubleshooting operating power module failure

3
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<Sysname> display power
Slot 1
Input Power: 266(W)
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Absent -- -- -- --
2 Normal 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 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, replace the power module.
3. When the power module is in Fault state, do the following:
a. Verify that the power module is connected to the power source securely. If it has been
disconnected from the power source, connect the power source to it.
b. Determine whether the power module is in high temperature. If dust accumulation on the
power module causes the high temperature, 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.
Newly installed power module failure
Symptom
A trap or log is generated indicating that a newly installed power module is faulty.

4
Troubleshooting flowchart
Figure 3 Newly installed power module failure
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<Sysname> display power
Slot 1
Input Power: 266(W)
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Absent -- -- -- --
2 Normal 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. When the power module is in Absent state, do the following:
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.

5
Fan tray failure
Symptom
A trap or log indicates that a fan tray is faulty, or the display fan command shows that a fan tray is
not in Normal state.
Troubleshooting flowchart
Figure 4 Troubleshooting fan tray failure
Solution
To resolve the problem:
1. Execute the display fan command to display the operating states of the fan tray.
<Sysname> display fan
Slot 1:
Fan 1:
State : FanDirectionFault
Airflow Direction: Port-to-power
Prefer Airflow Direction: Power-to-port
Fan 2:
State : FanDirectionFault
Airflow Direction: Port-to-power
Prefer Airflow Direction: Power-to-port
{If the fan tray is in FanDirectionFault state, the airflow direction of the fan tray is not as
configured. Replace the fan tray with a fan tray that has the same airflow direction as the

6
equipment room, or use the fan prefer-direction command to change the preferred airflow
direction.
{If the fan tray is in Absent state, go to step 2.
{If the fan tray is in Fault state, go to step 3.
2. Remove and reinstall the fan tray to make sure the fan tray is installed securely. Then execute
the display fan command to verify that the fan tray has changed to Normal state. If the fan tray
remains in Absent state, replace the fan tray.
3. Execute the display environment command to display temperature information. If the
temperature continues to rise, put your hand at the air outlet to feel if air is being expelled out of
the air outlet. If no air is being expelled out of the air outlet, remove and reinstall the fan tray.
Then execute the display fan command to verify that the fan tray has changed to Normal state.
If the fan tray remains in Fault state, replace the fan tray.
You must make sure the switch operating temperature is below 60°C (140°F) while you replace
the fan tray. If a new fan tray is not readily available, power off the switch to avoid damage
caused by high temperature.
4. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting the hardware.
Command Description
dir Displays information about files and directories.
display boot-loader Displays current configuration files and system software images.
display environment Displays temperature information.
display fan Displays the operating states of the fan tray.
display logbuffer Displays the state of the log buffer and the log information in the
log buffer.
display power Displays power module information.
fan prefer-direction slot slot-number
{ power-to-port |port-to-power }Specifies the preferred airflow direction.

7
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, delete unnecessary 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.

8
Troubleshooting flowchart
Figure 5 Troubleshooting 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
Ethernet service instance display qos policy l2vpn-ac (This command is available in Release
24xx and Release 26xx.)
Interface display qos [ accounting |remarking ]
policy interface (The
accounting and remarking keywords are available in Release 26xx.)
VLAN display qos vlan-policy
Global display qos policy global
Control plane display qos policy control-plane slot slot-number
User profile display qos policy user-profile
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.

9
−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, 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 acl Displays configuration and match statistics for ACLs.
display diagnostic-information Displays operating statistics for multiple feature modules
in the system.
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 l2vpn-ac (This command is
available in Release 24xx and Release 26xx.) Displays information about the QoS policies applied to Ethernet service instances.
display qos policy diagnosis l2vpn-ac Displays diagnostic information about the QoS policies
applied to Ethernet service instances.
display qos policy control-plane Displays information about the QoS policies applied to
control planes.
display qos policy diagnosis control-plane Displays diagnostic information about the QoS policies
applied to control planes.
display qos policy global Displays information about global QoS policies.
display qos policy diagnosis global Displays diagnostic information about global QoS
policies.
display qos [ accounting |remarking ] policy
interface (The accounting and remarking
keywords are available in Release 26xx.)
Displays information about the QoS policies applied to an
interface or to all interfaces.

10
Command Description
display qos [ accounting |remarking ] policy
diagnosis interface (The accounting and
remarking keywords are available in Release
26xx.)
Displays diagnostic information about the QoS policies
applied to interfaces.
display qos policy user-defined Displays user-defined QoS policies.
display qos vlan-policy Displays information about QoS policies applied to
VLANs.
display qos vlan-policy diagnosis Displays diagnostic 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.
display qos policy user-profile Displays information about QoS policies applied to user
profiles.
display qos policy diagnosis user-profile Displays diagnostic information about QoS policies
applied to user profiles.
The commands for displaying diagnostic information about QoS policies are available in Release
26xx.

11
Troubleshooting IRF
This section provides troubleshooting information for common problems with IRF.
IRF fabric setup failure
Symptom
An IRF fabric cannot be set up.

12
Troubleshooting flowchart
Figure 6 Troubleshooting IRF fabric setup failure
Does the number
of members exceed the upper
limit?
Is member ID unique
for each member?
You cannot add devices
to the IRF fabric or
complete IRF merge
Assign a unique
member ID to each
member device
Do member devices
use the same software
version?
Upgrade software to
the same version
Contact the support
IRF setup failure
Yes
No
Resolved?
No Yes
Yes No
Resolved?
No
Yes No
Yes
End
Are IRF port
bindings or physical IRF
connections correct?
Modify IRF port
bindings or reconnect
IRF physical interfaces Resolved?
No Yes
Yes No
Bring up the IRF links
or activate IRF port
configuration Resolved?
Yes
No
No
Yes
Are IRF links up?
Do physical IRF
links meet the rate
requirements?
Replace with correct
transceiver modules or
cables Resolved?
No Yes
Yes No
Are specific settings
same across member
devices?
Modify the settings to
be the same Resolved?
No
Yes
No
Can member
devices join the same IRF
fabric?
Replace with devices
that can join the same
IRF fabric
No
Yes
Resolved?
No
Yes
Yes