H3C S6520X-HI Series User manual

H3C S6520X-HI[EI][SI] & S6520-SI &
S5560X-HI & S5000-EI & MS4600
Switch Series
Troubleshooting Guide
Document version: 6W101-20191128
Copyright © 2019 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 New H3C 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 ·························································································2
Collecting common log messages···························································································2
Collecting diagnostic log messages·························································································3
Collecting operating statistics·································································································3
Contacting technical support ········································································································5
Troubleshooting hardware··································································5
Unexpected switch reboot············································································································5
Symptom···························································································································5
Troubleshooting flowchart ·····································································································6
Solution·····························································································································6
Operating power module failure ····································································································7
Symptom···························································································································7
Troubleshooting flowchart ·····································································································7
Solution·····························································································································7
Newly installed power module failure······························································································8
Symptom···························································································································8
Troubleshooting flowchart ·····································································································8
Solution·····························································································································8
Fan tray failure ··························································································································9
Symptom···························································································································9
Troubleshooting flowchart ·····································································································9
Solution·····························································································································9
Related commands ··················································································································10
Troubleshooting ACL ······································································10
ACL application failure with an error message················································································10
Symptom·························································································································10
Troubleshooting flowchart ···································································································11
Solution···························································································································11
ACL application failure without an error message············································································11
Symptom·························································································································11
Troubleshooting flowchart ···································································································12
Solution···························································································································12
Packet loss or forwarding failure··································································································13
Symptom·························································································································13
Troubleshooting flowchart ···································································································13
Solution···························································································································14
Related commands ··················································································································15
Troubleshooting IRF ·······································································15
IRF fabric establishment failure···································································································16
Symptom·························································································································16
Troubleshooting flowchart ···································································································16
Solution···························································································································17
Related commands ··················································································································18
Troubleshooting Ethernet link aggregation···········································19
Link aggregation failure·············································································································19
Symptom·························································································································19
Troubleshooting flowchart ···································································································20
Solution···························································································································20
Related commands ··················································································································21

ii
Troubleshooting ports ·····································································22
Fiber port remains in down state ·································································································22
Symptom·························································································································22
Troubleshooting flowchart ···································································································22
Solution···························································································································23
Copper port remains in down state ······························································································24
Symptom·························································································································24
Troubleshooting flowchart ···································································································24
Solution···························································································································24
Non-H3C transceiver module······································································································25
Symptom·························································································································25
Troubleshooting flowchart ···································································································25
Solution···························································································································25
Transceiver module does not support digital diagnosis·····································································26
Symptom·························································································································26
Troubleshooting flowchart ···································································································27
Solution···························································································································27
Error frames (for example, CRC errors) on a port············································································28
Symptom·························································································································28
Troubleshooting flowchart ···································································································28
Solution···························································································································28
Failure to receive packets··········································································································30
Symptom·························································································································30
Troubleshooting flowchart ···································································································30
Solution···························································································································30
Failure to send packets ·············································································································32
Symptom·························································································································32
Troubleshooting flowchart ···································································································32
Solution···························································································································32
Related commands ··················································································································33
Troubleshooting system management ················································34
High CPU utilization··················································································································34
Symptom·························································································································34
Troubleshooting flowchart ···································································································35
Solution···························································································································35
High memory utilization·············································································································37
Symptom·························································································································37
Troubleshooting flowchart ···································································································37
Solution···························································································································37
Related commands ··················································································································38
Troubleshooting other issues····························································39
Layer 2 forwarding failure ··········································································································39
Symptom·························································································································39
Troubleshooting flowchart ···································································································39
Solution···························································································································40
Related commands············································································································42
Layer 3 forwarding failure ··········································································································43
Symptom·························································································································43
Troubleshooting flowchart ···································································································44
Solution···························································································································44
Related commands············································································································45
Protocol flapping······················································································································45
Symptom·························································································································45
Troubleshooting flowchart ···································································································45
Solution···························································································································45
VXLAN configuration failure ·······································································································46
Symptom·························································································································46
Troubleshooting flowchart ···································································································47
Solution···························································································································47

1
Introduction
This document provides information about troubleshooting common software and hardware issues
with the following switches:
•H3C S6520X-HI switch series.
•H3C S6520X-EI switch series.
•H3C S6520X-SI switch series.
•H3C S6520-SI switch series.
•H3C S5560X-HI switch series.
•H3C S5000-EI switch series.
•H3C MS4600 switch series.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a failure from causing loss of configuration, save the configuration each time you finish
configuring a feature. For configuration recovery, regularly back up the configuration to a remote
server.
When you troubleshoot xxx, follow these general guidelines:
•To help identify the failure cause, collect system and configuration information, including:
{Symptom, time of failure, and configuration.
{Network topology information, including the network diagram, port connections, and points
of failure.
{Log messages and diagnostic information. For more information about collecting this
information, see "Collecting log and operating information."
{Physical evidence of failure:
−Photos of hardware.
−Status of the LEDs.
{Measures you have taken, such as reconfiguration, cable swapping, and reboot.
{Output from the commands executed during the troubleshooting process.
•To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware
component.
•If hardware replacement is required, use the release notes to verify the hardware and software
compatibility.

2
Collecting log and operating information
IMPORTANT:
To quickly locate faults, verify that the following features are enabled:
•Information center—Enabled by default. To enable the information center, use the info-center
enable command.
•Log file—Enabled by default. To enable the log file feature, use the info-center logfile enable
command.
•Saving diagnostic log messages to the diagnostic log file—Enabled by default. To enable this feature,
use the info-center diagnostic-logfile enable command.
Table 1 shows the types of files that the system uses to store operating log and status information.
Common log files are stored in the flash:/logfile directory and diagnostic log files are stored in the
flash:/diagfile directory. You can export these files by using FTP, TFTP, or USB.
In an IRF system, these files are stored on the master device. If master/subordinate switchovers
have occurred, master devices before and after the switchovers have log files. You must collect log
files from all these devices. To more easily locate log information, save log files to a separate folder
for each member device and include their IRF member IDs in the folder names.
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 used when an error occurs.
•Information about a card startup error.
•Handshaking information between member devices
when a communication error occurs.
Operating
statistics file-basename.tar.gz
IMPORTANT:
Current operation statistics for feature modules, including the
following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
Collecting common log messages
1. Save the common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the Flash memory on each member
device.
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each member device:
# Display the log file on the master device.

3
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
1038336 KB total (963860 KB free)
# Display the log file on a subordinate device:
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
1038336 KB total (963860 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 the 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
1038336 KB total (963860 KB free)
# Display the diagnostic log file on a subordinate device:
<Sysname> dir slot2#flash:/diagfile/
Directory of slot2#flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log
1038336 KB total (963860 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 port or management port (if any) instead of the console
port as long as possible. Network and management ports are faster than the console port.
•Do not execute commands during operating statistics collection.
•To ensure information completeness, save the statistics to a file as a best practice.

4
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_20171116-165524.tar.gz] :flash:/diag.tar.gz
Diagnostic information is outputting to flash:/diag.tar.gz.
Please wait...
Save successfully.
<Sysname> dir flash:/
Directory of flash:
…
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz
1038336 KB total (963860 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
=================================================
===============display version===============
H3C Comware Software, Version 7.1.070, ESS 1108
Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved.
H3C S6520X-30QC-EI uptime is 0 weeks, 0 days, 5 hours, 57 minutes
Last reboot reason : Cold reboot
Boot image: flash:/s6520x-cmw710-boot-e1108.bin
Boot image version: 7.1.070, ESS 1108
Compiled Jul 18 2017 16:00:00
System image: flash:/s6520x-cmw710-system-e1108.bin
System image version: 7.1.070, ESS 1108
Compiled Jul 18 2017 16:00:00
……
3. Display the content of the operating statistics file:
# Extract and decompress the operating statistics file.
<Sysname> tar extract archive-file diag_Sysname_20171116-165524.tar.gz
Extracting archive flash:/diag_Sysname_20171116-165524.tar.gz Done.
<Sysname> gunzip diag_Sysname_20171116-165524.gz
Decompressing file flash:/diag_Sysname_20171116-165524.gz.... Done.
# Display the content of the operating statistics file.

5
<Sysname> more diag_Sysname_20171116-165524
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
===============display version===============
H3C Comware Software, Version 7.1.070, ESS 1108
Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved.
H3C S6520X-30QC-EI uptime is 0 weeks, 0 days, 5 hours, 57 minutes
Last reboot reason : Cold reboot
Boot image: flash:/s6520x-cmw710-boot-e1108.bin
Boot image version: 7.1.070, ESS 1108
Compiled Jul 18 2017 16:00:00
System image: flash:/s6520x-cmw710-system-e1108.bin
System image version: 7.1.070, ESS 1108
Compiled Jul 18 2017 16:00:00
---- More ----
Contacting technical support
If an issue persists after you perform 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.
You can contact H3C Support at servic[email protected].
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 while it is operating.

6
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
Solution
To resolve the issue:
1. Check whether 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:
Log in to the switch through the console port and restart the switch. If the system reports that a
CRC error has occurred orthat no system software image is available, use the BootWare menu
to download the system software image and reboot the switch. The switch loads the system
software image.
3. If the issue persists, contact H3C Support.

7
Operating power module failure
Symptom
An operating power module has failed.
Troubleshooting flowchart
Figure 2 Troubleshooting operating power module failure
Solution
To resolve the issue:
1. Identify the operating state of the power module.
<Sysname> display power
Slot 2:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal AC -- -- --
2 Absent -- -- -- --
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, perform the following tasks:
a. Verify that the power module is connected to the power source securely and is powered on.
If it has been disconnected from the power source (The switch is being powered up with
another power module.), connect the power source to it.

8
b. Verify that the power module is in an acceptable temperature range. Dust buildup might
cause high temperature. If dust is accumulated on the power module, remove the dust.
Then remove and reinstall the power module. Execute the display power command to
verify that the power module has changed to Normal state. If the power module remains in
Fault state, go to step c.
c. Install the power module into an empty power module slot. Then execute the display
power command to verify that the power module has changed to Normal state in the new
slot. If the power module remains in Fault state, replace the power module.
4. If the issue persists, contact H3C Support.
Newly installed power module failure
Symptom
A newly installed power module has failed.
Troubleshooting flowchart
Figure 3 Troubleshooting newly installed power module failure
Solution
To resolve the issue:
1. Identify the operating state of the power module.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal AC -- -- --
2 Absent -- -- -- --
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.

9
2. When the power module is in Absent state, perform the follow tasks:
a. Remove and reinstall the power module to make sure the power module is installed
securely. Then execute the display power command to verify that the power module has
changed to Normal state. If the power module remains in Absent state, go to step b.
b. Remove and install the power module into an empty power module slot. Then execute the
display power command to verify that the power module has changed to Normal state
in the new slot. If the power module remains in Absent state, go to step 4.
3. Remove and install the power module into an idle power module slot. Then execute the
display power command to verify that the power module has changed to Normal state in the
new slot. If the power module remains in Fault state, go to step 4.
4. If the issue persists, contact H3C Support.
Fan tray failure
Symptom
An operating fan tray or a newly installed fan tray has failed.
Troubleshooting flowchart
Figure 4 Troubleshooting fan tray failure
Solution
To resolve the issue:
1. Display fan tray information.
<Sysname> display fan
Slot 1:
Fan 1:
State : Normal
Airflow Direction: Port-to-power
Prefer Airflow Direction: Port-to-power

10
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 required, or execute the fan
prefer-direction command to configure the preferred airflow direction as required.
{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. If the fan tray is in Fault state, 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 vents to feel if air is being
expelled out of the air outlet.
b. If no air is being expelled out of 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.
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 issue persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting the hardware.
Command Description
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.
Troubleshooting ACL
This section provides troubleshooting information for common issues withACLs.
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.

11
Troubleshooting flowchart
Figure 5 Troubleshooting an ACL application failure
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, delete unnecessary 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.

12
Troubleshooting flowchart
Figure 6 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 theACL 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
b. If the QoS policy contains a class-behavior association, execute the display traffic
classifier user-defined command and the display traffic behavior
user-defined command to check for traffic class and behavior configuration errors,
respectively.
−If they are configured incorrectly, reconfigure them.
−If they are configured correctly, go to step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
{If the ACL is configured incorrectly, reconfigure it.

13
{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 theACL 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.
Packet loss or forwarding failure
Symptom
The network experiences packet loss or packet forwarding failure. You can use ACLs to count traffic
statistics to determine the location of the fault.
Troubleshooting flowchart
Figure 7 Troubleshooting a forwarding failure

14
Solution
To resolve the issue:
1. Identify the characteristics of the packets that are not forwarded correctly.
Use a packet capture tool to identify the characteristics of the traffic, such as the IP address,
MAC address, or VLAN. Make sure the characteristics are unique among traffic to be
forwarded.
2. Configure a QoS policy and apply it to interfaces:
Figure 8 Traffic path
a. Configure a QoS policy according to the traffic characteristics. This example uses
destination IP address 2.2.2.2.
<Sysname> system-view
System View: return to User View with Ctrl+Z.
[Sysname] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013
[Sysname] acl number 3000 name geliACL
[Sysname-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range
t1
[Sysname-acl-adv-3000-geliACL] quit
[Sysname] traffic classifier count
[Sysname-classifier-count] if-match acl 3000
[Sysname-classifier-count] quit
[Sysname] traffic behavior count
[Sysname-behavior-count] accounting packet
[Sysname-behavior-count] quit
[Sysname] qos policy count
[Sysname-qospolicy-count] classifier count behavior count
b. Apply the QoS policy to interfaces on devices along the forwarding path. In this example,
apply the QoS policy to the incoming traffic on Ten-GigabitEthernet 1/0/1 on Device B and
Ten-GigabitEthernet 2/0/1 on Device C.
The following shows the application on Device B:
[Sysname-qospolicy-count] quit
[Sysname] interface ten-gigabitethernet 1/0/1
[Sysname-Ten-GigabitEthernet1/0/1] qos apply policy count inbound
3. After the time range, execute the display qos policy interface command to display
traffic statistics on the interfaces:
{On Ten-GigabitEthernet 1/0/1 of Device B:
<Sysname> display qos policy interface ten-gigabitethernet 1/0/1
Interface:ten-gigabitethernet1/0/1
Direction: Inbound
Policy: count
Classifier: count
Operator: AND
Rule(s) : If-match ACL 3000
Behavior: count

15
Accounting Enable:
251 (Packets)
The output shows that a total of 251 packets match ACL 3000.
{On Ten-GigabitEthernet 2/0/1 of Device C:
<Sysname> display qos policy interface ten-gigabitethernet 2/0/1
Interface:ten-gigabitethernet2/0/1
Direction: Inbound
Policy: count
Classifier: count
Operator: AND
Rule(s) : If-match ACL 3000
Behavior: count
Accounting Enable:
50 (Packets)
The output shows that a total of 50 packets match ACL 3000.
4. Compare the traffic statistics on the two interfaces. Packet loss or forwarding fault exists
between Device B and Device C.
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 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 policy user-defined Displays user-defined QoS policies.
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.
Troubleshooting IRF
This section provides troubleshooting information for common issues with IRF.

16
IRF fabric establishment failure
Symptom
An IRF fabric cannot be established.
Troubleshooting flowchart
Figure 9 Troubleshooting IRF fabric establishment 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
No
Yes
Resolved?
No Yes
Yes No
All IRF links meet the
requirements? Resolved?
No Yes
Yes No
Upgrade software to the
same version in the fabric Resolved?
Yes
No
No
Yes
Same software version?
IRF links up? Resolved?
No Yes
Yes
No
Replace with correct
cables or transceiver
modules
Bring up the IRF
links/activate IRF port
configuration
IRF setup failure
Number of members fewer
than the upper limit? No You cannot add the
device to the IRF fabric or
complete IRF merge
Yes
Resolved? Yes
No
Contact the support End

17
Solution
To resolve the issue:
1. Verify that the number of member devices does not exceed 9.
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. Assign a unique member ID to each member.
−If you are adding a new member device to an existing IRF fabric, assign the member
device a member ID that is not being used in the IRF fabric.
−If you are merging IRF fabrics, make sure each member device in these IRF fabrics has
a unique member ID.
3. Verify that the IRF port bindings and physical IRF link connections are correct:
IMPORTANT:
When you connect two neighboring IRF members, you must connect the physical ports of
IRF-port 1 on one member to the physical ports of IRF-port 2 on the other.
a. Execute the display irf configuration command on each
b. member device, and check the IRF-Port1 and IRF-Port2 fields for IRF port bindings.
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 meet the requirements.
For information about the interfaces that can be used as IRF physical interfaces, see the switch
installation guide or the IRF configuration in the virtual technologies configuration guide for your
switches. In addition, follow these restrictions and guidelines:
{Typically, a port must operate at its highest rate when it is used as an IRF physical interface.
However, if you connect a 10G rate autosensing Ethernet port to a 5G rate autosensing
Ethernet ports, the 10G rate autosensing Ethernet port will operate at 5 Gbps.
{The breakout interfaces of a QSFP+ or OSFP28 port cannot be used as IRF physical
interfaces.
{Ports on the LSPM4G4T6P module cannot be used as IRF physical interfaces.
When you select transceiver modules or cables, follow these restrictions and guidelines:
{Ethernet ports that operate at different rates have different requirements for cables or
transceiver modules. For more information, see the switch installation guide.
{The cable or transceiver module for an IRF physical interface must match the rate of the
interface.
{If transceiver modules and fibers are used, the transceiver modules at the two ends of an
IRF link must be the same type.
5. Verify that all IRF links are up:
a. Execute the display irf topology command, and then check the Link field.
−If the Link field for each IRF port does not display DOWN, go to step 6.
−If
the Link field for an IRF port displays DOWN, go to step b.
b. Execute the display irf link command, and then check the Status field of the physical
ports bound to the IRF port.