H3C S6300 Series User manual

H3C S6300 Switch Series
Troubleshooting Guide
Copyright © 2021 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.
Except for the trademarks of NewH3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are
the property of their respective owners.
The information in this document is subject to change without notice

i
Contents
Introduction····································································································1
Troubleshooting hardware·············································································1
Unexpected switch reboot··································································································································1
Symptom····················································································································································1
Troubleshooting flowchart··························································································································2
Solution······················································································································································2
Operating power supply failure ··························································································································3
Symptom····················································································································································3
Solution······················································································································································3
Newly-installed power supply failure··················································································································3
Symptom····················································································································································3
Solution······················································································································································3
Fan tray failure···················································································································································4
Symptom····················································································································································4
Solution······················································································································································4
Related commands············································································································································5
Troubleshooting ACL·····················································································6
ACL application failure with an error message···································································································6
Symptom····················································································································································6
Solution······················································································································································6
ACL application failure without an error message······························································································6
Symptom····················································································································································6
Troubleshooting flowchart··························································································································7
Solution······················································································································································7
Related commands············································································································································8
Troubleshooting IRF······················································································9
IRF fabric establishment failure··························································································································9
Symptom····················································································································································9
Troubleshooting flowchart························································································································10
Solution····················································································································································10
Related commands··········································································································································12
Troubleshooting Ethernet link aggregation···················································13
Link aggregation failure····································································································································13
Symptom··················································································································································13
Troubleshooting flowchart························································································································14
Solution····················································································································································14
Related commands··········································································································································15
Troubleshooting ports··················································································16
A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber port fails to go up·································································16
Symptom··················································································································································16
Troubleshooting flowchart························································································································16
Solution····················································································································································16
A 1/10GBASE-T copper port fails to go up ······································································································18
Symptom··················································································································································18
Troubleshooting flowchart························································································································18
Solution····················································································································································18
Related commands··········································································································································19
Troubleshooting other issues·······································································20
Layer 2 forwarding failure·································································································································20
Symptom··················································································································································20
Troubleshooting flowchart························································································································20

ii
Solution····················································································································································21
Related commands··································································································································24
Layer 3 forwarding failure·································································································································24
Symptom··················································································································································24
Troubleshooting flowchart························································································································25
Solution····················································································································································25
Related commands··································································································································26
Protocol flapping ··············································································································································26
Symptom··················································································································································26
Troubleshooting flowchart························································································································26
Solution····················································································································································26
Fan failure························································································································································27
Symptom··················································································································································27
Troubleshooting flowchart························································································································28
Solution····················································································································································28
Related commands··································································································································29

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

2
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
Solution
To resolve the issue:
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 log messages.
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, reload the system
software image. The system software image is automatically set to the current system software
image during the Boot ROM image running process.
3. If the issue persists, contact H3C Support.
The switch reboots unexpectedly
Can the CLI be
accessed?
Collect log messages Reload the system
software image
Yes
No
Is the fault
rectified?
End
Contact H3C Support
Yes No
Yes
No
Is the system software
image correct?

3
Operating power supply failure
Symptom
A trap or log is generated indicating that an operating power supply is faulty.
Solution
To resolve the issue:
1. Execute the display power command to display power supply information.
<H3C> display power
Slot 1:
Input Power: 78(W)
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal AC -- -- --
2 Absent -- -- -- --
If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to
step 3.
2. Remove and reinstall the power supply to make sure the power supply is installed correctly.
Then, execute the display power command to verify that the power supply has changed to
Normal state. If the power supply remains in Absent state, replace the power supply.
3. When the power supply is in Fault state, do the following:
a. Verify that the power supply has not been disconnected from the power source. If it has
been disconnected from the power source (The switch is being powered up with another
power supply.), connect the power source to it.
b. Verify that the power supply surface is clean. If there is dust accumulated on the power
supply, remove the dust. Then remove and reinstall the power supply. Execute the
display power command to verify that the power supply has changed to Normal state. If
the power supply remains in Fault state, go to step c.
c. Install the power supply into an empty power supply slot. Then execute the display
power command to verify that the power supply has changed to Normal state in the new
slot. If the power supply remains in Fault state, replace the power supply.
4. If the issue persists, contact H3C Support.
Newly-installed power supply failure
Symptom
A trap or log is generated indicating that a newly-installed power supply is faulty.
Solution
To resolve the issue:
1. Execute the display power command to display power supply information.
<H3C> display power
Slot 1:
Input Power: 78(W)

4
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal AC -- -- --
2 Absent -- -- -- --
If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to
step 3.
2. When the power supply is in Absent state, do the following:
a. Remove and reinstall the power supply to make sure the power supply is installed securely.
Then execute the display power command to verify that the power supply has changed
to Normal state. If the power supply remains in Absent state, go to step b.
b. Remove and install the power supply into an empty power supply slot. Then execute the
display power command to verify that the power supply has changed to Normal state in
the new slot. If the power supply remains in Absent state, go to step 4.
3. Remove and install the power supply into an idle power supply slot. Then execute the display
power command to verify that the power supply has changed to Normal state in the new slot. If
the power supply remains in Fault state, go to step 4.
4. If the issue persists, contact H3C Support.
Fan tray failure
Symptom
A trap or log is generated indicating that an operating fan tray or a newly-installed fan tray is faulty.
Solution
To resolve the issue:
1. Execute the display fan command to display the operating state of the fan tray.
<H3C> display fan
Slot 1:
Fan 1:
State : Normal
Airflow Direction: Port-to-power
Prefer Airflow Direction: Port-to-power
Fan 2:
State : Normal
Airflow Direction: Port-to-power
Prefer Airflow Direction: Port-to-power
If the Airflow Direction value is different from the Prefer Airflow Direction value, replace
the fan tray with one that has an airflow direction as the preferred airflow direction, or
execute the fan prefer-direction command to configure the preferred airflow
direction as that of the fan tray.
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 securely installed. 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 vents to verify that air is being

5
exhausted from the air outlet vents. If there is no air being exhausted from the air outlet vents,
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.
If there is no new fan tray, power off the switch to avoid damage caused by high
temperatures.
If there are cooling measures to maintain the switch operating temperature below 60°C
(140°F), the switch can be used temporarily.
4. If the issue 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 supply information.

6
Troubleshooting ACL
This section provides troubleshooting information for common issues 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 issue:
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 issue 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.

7
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 issue 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.
QoS policy/packet filter
configured correctly?
ACL rule
configured correctly?
Reconfigure QoS
policy/packet filter Problem resolved?
Failure to apply an ACL
No
No
Yes
Contact H3C Support
Problem resolved?
End
Reconfigure ACL rule Yes
No
Yes
No
Yes

8
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 issue persists, contact H3C Support.
ACL used in a packet filter
To resolve the issue 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 issue 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.

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

10
Troubleshooting flowchart
Figure 3 Troubleshooting IRF fabric establishment failure
Solution
To resolve the issue:
1. Verify that the number of member devices does not exceed the upper limit.
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 or 40-Gbps IRF links used? Replace with 10-Gbps or 40-
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

11
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:
W
hen you connect two neighboring IRF members, you must connect the physical ports of
IRF-port 1 on one member to the physical ports of IRF-port 2 on the other.
a. Execute the display irf configuration command on each member device, and
check the IRF-Port1 and IRF-Port2 fields for IRF port bindings.
b. Verify that all or none of the physical ports in a port group are used for IRF connection.
The following are physical port grouping rules:
−The 10GBASE-T ports or SFP+ ports are grouped by port number in order, starting from
1. Each port group contains four ports.
−The 10-GE interfaces split from a QSFP+ port belong to the same port group.
c. Verify that the physical IRF connections are consistent with the IRF port bindings.
d. If there are binding errors or connection inconsistencies, reconfigure the IRF port bindings
or reconnect the physical IRF ports.
4. Verify that the IRF links are 10 Gbps or 40 Gbps:
a. Verify that the transceiver modules or cables for IRF connection are labeled with 10Gbps,
SFP+, 40Gbps, or QSFP+.
b. Replace a transceiver module or cable if it is not for 10-Gbps or 40-Gbps connection.
5. (Optional.) Verify that transceiver modules at the two ends of an IRF link are the same type.
If the transceiver modules are not the same type, replace them to be the same type.
Skip this step if you are using SFP+ or QSFP+ cables to connect IRF member devices.
6. 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 7.
−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 at least 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.

12
7. Verify that all member devices use the same software version:
a. Execute the display version command to identify the software version of each member
device.
b. Upgrade the software of all member devices to the same version.
NOTE:
Typically
, the irf auto-update enable
command can automatically synchronize a member
device
with the software version of the master device. However, the synchronization might fail
when the gap between the software versions is
too
large. For more information, see the release
notes.
8. If the issue 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 verifythat each IRF port hasat 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.
undo shutdown
Brings up an Ethernet interface or subinterface.

13
Troubleshooting Ethernet link
aggregation
This section provides troubleshooting information for common issues 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.

14
Troubleshooting flowchart
Figure 4 Troubleshooting link aggregation failure
Solution
To resolve the issue:
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.
Are all physical connections correct?
Are all member ports up?
Connect physical links correctly
Bring all member ports up
No
Yes
No
Yes
Operational key/attribute configurations same
as the reference port?
Set operational key/attribute
configurations same as the reference
port
No
Yes
Set the number of member ports less
than or equal to allowed max. number of
Selected ports
Yes
No
More member ports than allowed max. number
of Selected ports?
Operational key/attribute configurations of the peer ports
same as the peer port of the reference port?
Set operational key/attribute
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

15
b. If the member ports are down, follow the solution in "Troubleshooting ports" to troubleshoot
the issue.
3. Verify that the member ports have the same operational key and attribute configurations as the
reference port:
a. Execute the display link-aggregation verbose command to display the Selected
state of the member ports.
b. Execute the display current-configuration interface command to display the
configurations of the aggregate interface and the Unselected ports.
c. Configure the Unselected ports to make sure they have the same operational key and
attribute 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 operational key and attribute 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 operational
key and attribute configurations as the peer port of the reference port.
6. Verify that the number of member ports in the aggregation group does not exceed the
configured maximum number of Selected ports.
a. Execute the link-aggregation selected-port maximum command to set the
maximum number of Selected ports allowed in the aggregation group. The value range is 1
to 16.
b. Execute the display link-aggregation verbose command to verify that the number
of member ports does not exceed the configured maximum number of Selected ports.
If the number of member ports exceeds the maximum number of Selected ports, the ports
with higher port numbers are in Unselected state.
c. 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 ports.
7. If the issue persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting Ethernet link aggregation.
Commands
Description
display current-configuration interface
Displays interface configuration.
display interface
Displays Ethernet interface information.
display link-aggregation verbose D
isplay detailed information about the
aggregation groups that correspond to the
existing aggregate interfaces.
link-aggregation selected-port maximum
Configure the maximum number of Selected
ports allowed in an aggregation group.

16
Troubleshooting ports
This section provides troubleshooting information for common port issues.
A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber
port fails to go up
Symptom
A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber port fails to go up.
Troubleshooting flowchart
Figure 5 Troubleshooting link up failure on a copper port
Solution
To resolve the issue:
Speed/duplex
match at both ends?
Speed/duplex match on port
and transceiver module?
Configure matching
speed/duplex Resolved?
Configure matching
speed/duplex
A fiber port failed to go up
No
Yes No
Yes
Resolved?
No Yes
Yes No
Transceiver module
and cable correct?
Replace matching
transceiver module and
cable Resolved?
No Yes
Yes No
Fiber correct? Replace fiber Resolved?
No Yes
Yes No
Contact H3C Support Resolved
Ports on both ends
operating correctly? Replace the local and
peer ports Resolved?
No Yes
Yes No

17
1. Verify that the speed and duplex mode of the local port match the speed and duplex mode of
the peer port:
a. Execute the display interface brief command to examine whether the speed and
duplex mode of the port match the speed and duplex mode of the peer port.
b. If they do not match, use the speed command and the duplex command to set the rate
and duplex mode for the port.
2. Verify that the speed and duplex mode of the local port match the speed and duplex mode of
the transceiver module:
a. Execute the display interface brief command to examine whether the speed and
duplex mode of the port match the speed and duplex mode of the transceiver module.
b. If they do not match, use the speed command and the duplex command to set the rate
and duplex mode for the port.
3. Verify that the ports at both ends are operating correctly:
a. For a 10-GE SFP+ fiber port, use an SFP+ cable (used for short-haul connection) to directly
connect it to another 10-GE SFP+ fiber port on the local end. For a 40-GE QSFP+ port, use
a QSFP+ cable (used for short-haul connection) to directly connect it to another 40-GE
QSFP+ port on the local end.
b. Identify whether the port can go up:
−If the port can go up, you can determine that the peer port fails. Replace the peer port
with a new port operating correctly.
−If the port cannot go up, you can determine that the local port fails. Replace the local port
with a new port operating correctly.
4. Verify that the transceiver module and cable are operating correctly:
a. Use the display transceiver alarm interface command to display the alarms
present on the transceiver module:
−The device displays None if no error occurs.
−The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver
module are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength
and transmission distance of the local transceiver module are consistent with the
wavelength and transmission distance of the peer transceiver module.
d. If the transceiver module is not operating correctly, replace it with a H3C transceiver module
that matches the fiber port.
For more information about transceiver modules and cables, see the installation guide.
NOTE:
When you use a QSFP+ to SFP+ cable to connect a 40
-GE QSFP+ fiber port, you
must use an
optical attenuator because the Tx optical power of the QSFP+ transceiver module exceeds the
upper Rx optical power limit of the SFP+ transceiver module.
5. Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with
a new one that matches the transceiver module.
For more information about fibers, see the installation guide.
6. If the issue persists, contact H3C Support, and provide the following information:
<H3C> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y