H3C S6805 Series User manual

H3C
S6805 & S6825 & S6850 & S9850
Switch Series
Troubleshooting Guide
Document version: 6W101-20220818
Copyright © 2019-2022 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
General guidelines·············································································································································1
Collecting log and operating information············································································································1
Collecting common log messages ·············································································································2
Collecting diagnostic log messages···········································································································3
Collecting operating statistics·····················································································································3
Troubleshooting hardware·············································································4
Unexpected switch reboot··································································································································4
Symptom····················································································································································4
Troubleshooting flowchart··························································································································5
Solution······················································································································································5
Operating power module failure·························································································································6
Symptom····················································································································································6
Solution······················································································································································6
Newly installed power module failure·················································································································7
Symptom····················································································································································7
Solution······················································································································································7
Fan tray failure···················································································································································8
Symptom····················································································································································8
Solution······················································································································································8
Related commands············································································································································9
Troubleshooting ACL···················································································10
Insufficient hardware resource for ACLs··········································································································10
Symptom··················································································································································10
Troubleshooting flowchart························································································································10
Solution····················································································································································10
Applied ACLs fail to take effect························································································································11
Symptom··················································································································································11
Troubleshooting flowchart························································································································12
Solution····················································································································································12
Troubleshooting IRF····················································································14
IRF fabric setup failure·····································································································································14
Symptom··················································································································································14
Troubleshooting flowchart························································································································15
Solution····················································································································································16
Related commands··········································································································································17
Troubleshooting Ethernet link aggregation···················································19
Link aggregation failure····································································································································19
Symptom··················································································································································19
Troubleshooting flowchart························································································································20
Solution····················································································································································20
Related commands··········································································································································21
Troubleshooting ports··················································································22
A GE SFP, 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up······························22
Symptom··················································································································································22
Troubleshooting flowchart························································································································22
Solution····················································································································································23
A 25-GE SFP28 fiber port fails to come up······································································································24
Symptom··················································································································································24
Troubleshooting flowchart························································································································24
Solution····················································································································································25
A 1/10GBase-T 10-GE copper port fails to come up························································································27

ii
Symptom··················································································································································27
Troubleshooting flowchart························································································································27
Solution····················································································································································27
Non-H3C transceiver module error message···································································································28
Symptom··················································································································································28
Troubleshooting flowchart························································································································28
Solution····················································································································································28
Transceiver module does not support digital diagnosis···················································································29
Symptom··················································································································································29
Troubleshooting flowchart························································································································29
Solution····················································································································································29
Error frames (for example, CRC errors) on a port····························································································30
Symptom··················································································································································30
Troubleshooting flowchart························································································································31
Solution····················································································································································31
Failure to receive packets································································································································32
Symptom··················································································································································32
Troubleshooting flowchart························································································································33
Solution····················································································································································33
Failure to send packets····································································································································34
Symptom··················································································································································34
Troubleshooting flowchart························································································································34
Solution····················································································································································35
Related commands··········································································································································35
Troubleshooting EVPN················································································37
EBGP or IBGP neighbor relationship setup failure ··························································································37
Symptom··················································································································································37
Troubleshooting flowchart························································································································37
Solution····················································································································································37
ECMP forwarding failure··································································································································38
Symptom··················································································································································38
Troubleshooting flowchart························································································································39
Solution····················································································································································39
Related commands··········································································································································40
Troubleshooting system management·························································41
High CPU utilization·········································································································································41
Symptom··················································································································································41
Troubleshooting flowchart························································································································41
Solution····················································································································································41
High memory utilization····································································································································43
Symptom··················································································································································43
Troubleshooting flowchart························································································································43
Solution····················································································································································43
Related commands··········································································································································44
Troubleshooting other issues·······································································45
Layer 2 forwarding failure·································································································································45
Symptom··················································································································································45
Troubleshooting flowchart························································································································45
Solution····················································································································································46
Related commands··································································································································51
Layer 3 forwarding failure·································································································································51
Symptom··················································································································································51
Troubleshooting flowchart························································································································52
Solution····················································································································································52
Related commands··································································································································53
Protocol flapping ··············································································································································53
Symptom··················································································································································53
Troubleshooting flowchart························································································································54
Solution····················································································································································54

1
Introduction
This document provides information about troubleshooting common software and hardware issues
with the S6805, S6825, S6850, and S9850 switch series.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a
n issue 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 issue, 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.
Common log messages and diagnostic log 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:
To facilitate quick troubleshooting, execute
the following commands:
•
info-center enable—Enables the information center. By default, the information center is enabled.
•
info-center logfile enable—
Enables the log file feature so the system outputs logs tolog files. By default,
the log file feature is enabled.
•
info-center diagnostic-logfile enable—Enables saving diagnostic logs to the diagnostic log file. By
default, saving diagnostic logs to the diagnostic log file is enabled.
During operation, the device generates common log messages and diagnostic log messages to
record information about routine operations and operating status. Table 1 shows the types of files
that the system uses to store the log messages. You can export these files by using FTP, TFTP, or
USB.
In an IRF system, log 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 member devices.

2
To more easily identify log files from different member devices, use two directories to save the log
files from each member device and include member IDs in the directory names.
Table 1 Log and operating information
Category
File name format
Log file directory
Content
Common log logfile.log flash:/logfile Command execution, events, and status
changes log messages.
Diagnostic
log diagfile.log flash:/diagfile
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.tar.gz N/A
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 common log file on each member device:
# Display the common 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
1048576 KB total (38812 KB free)
# Display the common 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
1048576 KB total (38812 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

3
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
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
1048576 KB total (38812 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
1048576 KB total (38812 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.
•
Hewlett Packard Enterprise recommends saving 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 name.
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.

4
Please wait...
Save successfully.
<Sysname> dir flash:/
Directory of flash:
...
6 -rw-898180 Jun 26 2013 09:23:51 diag.tar.gz
1048576 KB total (38812 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===============
23:49:53 UTC Tue 01/01/2016
=================================================
...
3. Extract and decompress the operating statistics file.
<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.
4. Display the content of the operating statistics file.
<Sysname> more diag_Sysname_20160101-000704
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
---- More ----
Troubleshooting hardware
This section provides troubleshooting information for common hardware issues.
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.

5
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 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 issue persists, contact H3C Support.
Unexpected switch reboot
Can you
access the CLI?
Collect operating
information Reload the system
software image
Yes
No
Resolved?
End
Contact the support
Yes No
Yes
No
Is the system software
image correct?

6
Operating power module failure
Symptom
A trap or log is generated indicating that an operating power module is faulty.
Solution
To resolve the issue:
1. Execute the display power command to check whether the power module is in faulty or absent
state.
<H3C> display power
Slot 1:
Input Power: 60(W)
PowerID State Mode Current(A) Voltage(V) Power(W) FanDirction
1 Normal AC 5.08 11.84 60 PowerToPort
2 Absent -- -- -- -- --
2. Observe the status LED on the power module.
The power module status LED has the following indications:
Steady green: The power module is operating correctly.
Flashing green: The power module has power input but is not installed on the device.
Steady red: The power module is faulty or in self-protection mode.
Flashing green/red alternatively: An alarm is present on the power module and the power
module is not in self-protection mode. The possible alarms include output overcurrent,
output overpower, and overtemperature.
Flashing red
−The power module does not have power input, and the other power module installed on
the same device has power input.
−The power module is in input undervoltage protection mode.
Off: The power module does not have power input.
3. If the power module is in Absent state, no power module is in the slot or the power module is
not installed securely in the slot.
If the power module is in the slot but its status is Absent, and the status LED on the power
module is flashing green (connected to power) or off (not connected to power), remove and
reinstall the power module to make sure the power module is installed securely. Then check
whether the power module has changed to Normal state and whether its status LED is steady
green. If the issue persists, replace the power module.
4. If the power module is in Fault state, do the following:
a. If no power is present on the power module (the status LED flashing red), connect power to
the power module.
b. If the power module is in high temperature (the status LED steady red or flashing red/green
alternatively) because of dust accumulation, remove the dust and then remove and reinstall
the power module. Execute the display power command to check whether 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 check whether the power module has changed to Normal state in the new slot.
If the power module remains in Fault state, replace the power module.

7
5. If the issue 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.
Solution
To resolve the issue:
1. Execute the display power command to display power module information.
<H3C>display power
Slot 1:
Input Power: 60(W)
PowerID State Mode Current(A) Voltage(V) Power(W) FanDirction
1 Normal AC 5.08 11.84 60 PowerToPort
2 Absent -- -- -- -- --
2. Observe the status LED on the power module.
The power module status LED has the following indications:
Steady green: The power module is operating correctly.
Flashing green: The power module has power input but is not installed on the device.
Steady red: The power module is faulty or in self-protection mode.
Flashing green/red alternatively: An alarm is present on the power module and the power
module is not in self-protection mode. The possible alarms include output overcurrent,
output overpower, and overtemperature.
Flashing red
−The power module does not have power input, and the other power module installed on
the same device has power input.
−The power module is in input undervoltage protection mode.
Off: The power module does not have power input.
3. If the power module is in Absent state, and the status LED on the power module is flashing
green (connected to power) or off (not connected to power), the power module is not installed
securely.
a. Remove and reinstall the power module to make sure the power module is installed
securely. Then check whether the power module has changed to Normal state and whether
its status LED is steady green. If the issue persists, go to step b.
b. Remove and install the power module into an empty power module slot. Then check
whether the power module has changed to Normal state and whether its status LED is
steady green. If the issue persists, go to step 5.
4. If the power module is in Fault state, perform the following tasks:
a. If no power is present on the power module (the status LED flashing red), connect power to
the power module.
b. If the status LED on the power module is steady red or flashing red/green alternatively, the
power module is faulty, an alarm is present on the power module, or the power module has
entered into self-protection mode. Remove and install the power module into an empty
power module slot. Then check whether the power module has changed to Normal state
and whether its status LED is steady green. If the issue persists, go to step 5

8
5. If the issue persists, contact H3C Support.
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.
Solution
To resolve the issue:
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
equipment room, or use the fan prefer-direction command to change the preferred airflow
direction.
2. If the fan tray is in the slot but it is in Absent state, 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. Observe the alarm LED on the fan tray.
If the alarm LED is on, the fan tray is operating incorrectly.
If the alarm LED is off, the fan tray is operating correctly.
4. If the fan tray is in Fault state and its alarm LED is on, the fan tray is faulty. Perform the
following tasks:
a. 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 and observe whether its alarm LED is off.
b. If the issue persists, replace the fan tray.
If no new fan tray is available, power off the switch to avoid damage caused by high
temperature. If you can use cooling measures to ensure that the device operates in an
temperature below 60°C (140°F), you can continue to use the device but prepare a new fan
tray to replace the failed fan tray as soon as possible.
5. If the issue persists, contact H3C Support.

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

10
Troubleshooting ACL
This section provides troubleshooting information for common issues with ACLs.
Insufficient hardware resource for ACLs
Symptom
ACL application fails and the system displays a message "Reason: Not enough hardware resource."
Troubleshooting flowchart
Figure 2 Troubleshooting insufficient hardware resource for ACLs
Solution
To resolve the issue:
1. Execute display qos-acl resource command to view ACL resource usage information.
<Sysname> display qos-acl resource
Interfaces: WGE1/0/1 to WGE1/0/24, HGE1/0/25 to HGE1/0/28 (slot 1)
---------------------------------------------------------------------
Type Total Reserved Configured Remaining Usage
---------------------------------------------------------------------
VFP ACL 1024 257 1 766 25%
IFP ACL 18432 9220 2 9210 50%
IFP Meter 3072 97 1 2974 3%
Delete unnecessary ACLs
Issue resolved?
ACL application
failure
No
Yes
Contact the support
End
Insufficient hardware
resources reported

11
IFP Counter 9216 4610 1 4605 50%
EFP ACL 2048 0 0 2048 0%
EFP Meter 1024 0 0 1024 0%
EFP Counter 1024 0 0 1024 0%
Interfaces: HGE1/0/29 to HGE1/0/32, WGE1/0/33 to WGE1/0/56
GE1/0/57 to GE1/0/58 (slot 1)
---------------------------------------------------------------------
Type Total Reserved Configured Remaining Usage
---------------------------------------------------------------------
VFP ACL 1024 257 1 766 25%
IFP ACL 18432 9220 2 9210 50%
IFP Meter 3072 106 1 2965 3%
IFP Counter 9216 4610 1 4605 50%
EFP ACL 2048 0 0 2048 0%
EFP Meter 1024 0 0 1024 0%
EFP Counter 1024 0 0 1024 0%
IFP indicates ACL resources for the inbound traffic.
EFP indicates ACL resources for the outbound traffic.
2. If the resources required for applying the ACLs exceed the remaining resources, the system
reports hardware resources insufficiency. Delete unnecessary ACLs to release resources.
3. If the resources are sufficient, the ACLs might conflict with an ASIC chip algorithm. Contact
H3C Support to resolve the issue.
4. If the issue persists, contact H3C Support.
Applied ACLs fail to take effect
Symptom
Applied ACLs fail to take effect.

12
Troubleshooting flowchart
Figure 3 Troubleshooting ACL failure to take effect
Solution
1. Verify that the ACL rules are defined correctly.
Execute the display acl command to view the ACL settings, including the rules and the match
order of the rules. Determine whether rules are configured correctly for packet match and
whether packets are not matched because of the incorrect match order of the rules.
For example, if you configure the following ACL rules:
ACL number 3100
rule 0 permit ip source 2.2.2.2 0.0.255.255
rule 1 deny ip destination 3.3.3.3 0.0.255.255
Packets with source IP 2.2.2.2 and destination IP 3.3.3.3 will match only rule 0 and do not
match rule 1.
For information about the rule match order, see ACL configuration in the ACL and QoS
configuration guide for the switch.
2. Check the applied ACLs for overlapping rules:
a. Use the following commands to display applied ACLs:
−display packet-filter
−display qos policy user-defined
ACL rules overlap?
ACLs fail to take
effect
Yes
No
No
Yes
Contact the support End
Actions of overlapping
ACL rules conflict? Remove the conflicts Resolved
Yes
No
ACL rules defined
correctly?
Yes
Revise ACL
rules Resolved
No Yes
No

13
−display traffic classifier user-defined
−display ip policy-based-route
b. Execute the display acl command to check for overlapping rules in the ACLs.
In the following example, rule 0 in ACL 3100 and rule 0 in ACL 3009 can both match traffic
sourced from 2.2.2.2.
ACL number 3100
rule 0 permit ip source 2.2.2.2 0.0.255.255
ACL number 3009
rule 0 permit ip source 2.2.2.2 0.0.0.255
3. Remove the action conflict between overlapping rules.
If two ACLs has overlapping rules, only actions in the ACL with higher priority take effect.
4. Collect related information and contact H3C Support.

14
Troubleshooting IRF
This section provides troubleshooting information for common issues with IRF.
IRF fabric setup failure
Symptom
An IRF fabric cannot be set up.
NOTE:
•
S6850 switches can establish an IRF fabric with switches in the S6850 switch series and S9850 switch
series.
•
S9850 switches can establish an IRF fabric with switches in the S9850 switch series and S6850 switch
series.
•
S6805 switches can establish an IRF fabric only with switches in the S6805 switch series.
•S6825 switches can establish an IRF fabric only with switches in the S6825 switch series.

15
Troubleshooting flowchart
Figure 4 Troubleshooting IRF fabric setup failure
Member ID unique?
IRF port bindings
or physical IRF connections
correct?
Assign a unique member
ID to each member
device
Modify IRF port bindings
or reconnect physical
interfaces
Same software version? Upgrade software to the
same version in the fabric
No
Yes
Resolved?
No Yes
Yes No
Resolved?
No
Yes No
Yes
Correct
transceiver modules or cables
used? Resolved?
No Yes
Yes No
Bring up the IRF links or
activate IRF port
configuration Resolved?
Yes
No
No
Yes
IRF links up?
Are two ends of an IRF link
operating at the same rate? Resolved?
No Yes
Yes
No
Replace with correct
cables or transceiver
modules
Replace the transceiver
modules or ports
IRF setup failure
Number of members fewer
than the upper limit? No You cannot add
additional devices to the
IRF fabric or complete
IRF merge
Yes
Resolved? Yes
No
Contact the support
Are specific settings same
across member devices? Modify the settings to be
the same
No Resolved?
No
Yes
Yes
End

16
Solution
To resolve the issue:
1. Verify that the number of member devices does not exceed the upper limit (10).
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.
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. Use the irf member renumber command to 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:
a. Execute the display irf configuration command, and check the IRF-Port1 and IRF-Port2
fields for IRF port bindings.
b. Verify that the physical interfaces bound to IRF ports are IRF capable. You can use QSFP+
or QSFP28 ports for IRF links. If there are binding errors, reconfigure the IRF port bindings.
IMPORTANT:
QSFP28 ports on the LSWM18CQMSEC module cannot be used as IRF physical interfaces.
c. Verify that the IRF physical interfaces are correct connected. When you connect two
neighboring IRF members, you must connect the physical interfaces of IRF-port 1 on one
member to the physical interfaces of IRF-port 2 on the other.
4. Verify that the correct transceiver modules and cables are used:
To connect QSFP+ ports in a long distance, use QSFP+ transceiver modules and fibers.
To connect QSFP+ ports in a short distance, use QSFP+ DAC or AOC cables.
To connect QSFP28 ports in a long distance, use QSFP28 or QSFP+ transceiver modules
and fibers.
To connect QSFP28 ports in a short distance, use QSFP28 or QSFP+ DAC or AOC cables.
IMPORTANT:
Except the above listed transceiver modules and fibers or cables, do not use any other
transceiver modules and fiber
s or cables to connect IRF physical interfaces on the switch
series.
When you use QSFP+ DAC cables to connect IRF physical interfaces for S6850 switch series
and S9850 switch series, follow these restrictions and guidelines:
The two ends of a physical IRF link must both use fixed ports as IRF physical interfaces or
both use ports on interface modules as IRF physical interfaces. Do not connect a fixed port
to a port on an interface module for IRF connection. However, you can bind fixed ports and
ports on an interface module to the same IRF port.
If you use ports on interface modules as IRF physical interfaces, make sure the interface
modules at the two ends of a physical IRF link are the same type.
To use a fixed QSFP28 port on the rear panel of an S6850-2C member as an IRF physical
interface, you must make sure its IRF neighbor is also an S6850-2C switch. In addition, you
can connect that port only to a fixed QSFP28 port on the rear panel of the neighboring
S6850-2C switch.

17
5. Verify that the two ends of an IRF link are operating at the same rate.
If you are using transceiver modules and fibers, verify that the 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.
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
interfaces bound to the IRF port.
−If the field displays DOWN or ADM (administratively down) for all the physical interfaces,
remove the link failures or use the undo shutdown command to bring up the
administratively down physical interfaces.
−If the field displays UP for at least one of the physical interfaces, 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.
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. Execute display commands to verify that all member devices use the same settings for the
following features:
System operating mode (set by using the system-working-mode command).
Hardware resource mode for the MAC address table, ARP and ND tables, and routing
tables (set by using the hardware-resource switch-mode command).
Enhanced ECMP mode (set by using the ecmp mode enhanced command).
Support for the IPv6 routes with prefixes longer than 64 bits (set by using the
hardware-resource routing-mode ipv6-128 command).
Enabling status of packet loss prevention for OpenFlow forwarding (set by using the
openflow lossless enable command).
VXLAN hardware resource allocation mode (set by using the hardware-resource vxlan
command).
9. If the issue persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting IRF.