H3C S5560S-EI Series User manual

Troubleshooting Guide
H3C S5560S-EI & S5560S-SI Switch Series
H3C S5500V3-SI Switch Series
H3C S5130S-HI & S5130S-EI & S5130S-SI & S5130S-LI Switch Series
H3C S5120V2-SI & S5120V2-LI Switch Series
H3C S5110V2 & S5110V2-SI Switch Series
H3C S5000V3-EI & S5000E-X Switch Series
H3C S3100V3-EI & S3100V3-SI Switch Series
H3C E128C & E152C & E500C & E500D Switch Series
H3C MS4520V2 & MS4320V2 & MS4300V2 & MS4200 Switch Series
H3C WS5850-WiNet & WS5820-WiNet & WS5810-WiNet Switch Series
H3C WAS6000 Switch Series
Document version: 6W103-2020315
Copyright © 2020 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 ·························································································1
Collecting common log messages···························································································2
Collecting diagnostic log messages·························································································3
Collecting operating statistics·································································································3
Contacting technical support ········································································································4
Troubleshooting hardware··································································4
Unexpected switch reboot············································································································5
Symptom···························································································································5
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 ··························································································································7
Symptom···························································································································7
Solution·····························································································································7
USB device anomaly ··················································································································8
Symptom···························································································································8
Solution·····························································································································8
Interface card anomaly················································································································8
Symptom···························································································································8
Solution·····························································································································8
Related commands ····················································································································9
Troubleshooting ACL ······································································10
ACL application failure with an error message················································································10
Symptom·························································································································10
Solution···························································································································10
ACL application failure without an error message············································································10
Symptom·························································································································10
Troubleshooting flowchart ···································································································11
Solution···························································································································11
Related commands ··················································································································12
Troubleshooting IRF ·······································································13
IRF fabric establishment failure···································································································13
Symptom·························································································································13
Troubleshooting flowchart ···································································································14
Solution···························································································································14
Related commands ··················································································································16
Troubleshooting Ethernet link aggregation···········································18
Link aggregation failure·············································································································18
Symptom·························································································································18
Troubleshooting flowchart ···································································································19
Solution···························································································································19
Related commands ··················································································································20
Troubleshooting ports ·····································································21
A fiber port fails to come up········································································································21
Symptom·························································································································21

ii
Troubleshooting flowchart ···································································································21
Solution···························································································································22
A copper port fails to come up ····································································································23
Symptom·························································································································23
Troubleshooting flowchart ···································································································23
Solution···························································································································23
Related commands ··················································································································24
Troubleshooting other issues····························································25
Layer 2 forwarding failure ··········································································································25
Symptom·························································································································25
Troubleshooting flowchart ···································································································25
Solution···························································································································26
Related commands············································································································28
Layer 3 forwarding failure ··········································································································28
Symptom·························································································································28
Troubleshooting flowchart ···································································································29
Solution···························································································································29
Related commands············································································································30
Protocol flapping······················································································································30
Symptom·························································································································30
Troubleshooting flowchart ···································································································30
Solution···························································································································30
PoE power supply anomaly········································································································31
Symptom·························································································································31
Troubleshooting flowchart ···································································································32
Solution···························································································································32
Related commands············································································································34

1
Introduction
This document provides information about troubleshooting common software and hardware issues
with the switches.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a failure from causing loss of configuration, save the configuration each time you finish
configuring a feature. For configuration recovery, regularly back up the configuration to a remote
server.
When you troubleshoot the switch, follow these general guidelines:
•To help identify the failure cause, collect system and configuration information, including:
{Symptom, time of failure, and configuration.
{Network topology information, including the network diagram, port connections, and points
of failure.
{Log messages and diagnostic information. For more information about collecting this
information, see "Collecting log and operating information."
{Physical evidence of failure:
−Photos of hardware.
−Status of the LEDs.
{Measures you have taken, such as reconfiguration, cable swapping, and reboot.
{Output from the commands executed during the troubleshooting process.
•To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware
component.
•If hardware replacement is required, use the release notes to verify the hardware and software
compatibility.
Collecting log and operating information
IMPORTANT:
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 to the log file. 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.
Table 1 shows the types of files that the system uses to store operating log and status information.
You can export these files by using FTP, TFTP, or USB.
In an IRF system, the common log and diagnostic log files are stored in the flash:/logfile and
flash:/diagfile directories of the master device, respectively. 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 locate log information, save the files to a separate folder for each member device, and
include their member IDs in the folder names.
Table 1 Log and operating information
Category File name format Content
Common log logfile.log Log messages about command executions, event
occurrences, state changes, and so on.
Diagnostic log diagfile.log
Diagnostic log messages about device operation,
including the following items:
•Parameter settings used when an error occurs.
•Information about a card startup error.
•Handshaking information between member
devices when a communication error occurs.
Operating statistics file-basename.tar.gz
IMPORTANT:
Current operating statistics for feature modules,
including the following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
Collecting common log messages
1. Save the common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the flash memory on each member
device.
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each member device:
# Display the log file on the master device.
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw- 21863 Jul 11 2015 16:00:37 logfile.log
251904 KB total (147468 KB free)
# Display the log file on each subordinate device (subordinate device 2 for example):
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2015 16:00:37 logfile.log
251904 KB total (147468 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 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 2015 16:16:00 diagfile.log
251904 KB total (147468 KB free)
# Display the diagnostic log file on each subordinate device (subordinate device 2 for example):
<Sysname> dir slot2#flash:/diagfile/
Directory of slot2#flash:/diagfile
0 -rw- 161321 Jul 11 2015 16:16:00 diagfile.log
251904 KB total (147468 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.
•As a best practice to ensure information completeness, save the statistics to a file.
NOTE:
The amount of time to collect statistics increases along with the number of IRF member devices.
To collect operating statistics:
1. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
2. At the prompt, choose to save or display operating statistics:
# To save operating statistics, enter yat the prompt and then specify the destination file path.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :y
Please input the file name(*.tar.gz)
[flash:/diag_Sysname_20160101-000704.tar.gz] :flash:/diag.tar.gz
Diagnostic information is outputting to flash:/diag.tar.gz.
Please wait...
Save successfully.

4
<Sysname> dir flash:/
Directory of flash:
…
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz
251904 KB total (147468 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
=================================================
---- More ----
3. Display operating statistics in the file.
# Decompress the file.
<Sysname> tar extract archive-file diag.tar.gz
Extracting archive flash:/diag.tar.gz Done.
<Sysname> gunzip diag.gz
Decompressing file flash:/diag.gz.... Done.
# Display the statistics in the file.
<Sysname> more diag
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
---- 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 [e-mail].
Troubleshooting hardware
This section provides troubleshooting information for common hardware issues.

5
NOTE:
•This section describes how to troubleshoot unexpected switch reboot, removable power modules, and fixed
fan trays. To troubleshoot transceiver modules and ports, see "Troubleshooting ports."
•Hardware varies by device model. For example, a switch might use fixed power modules or removable
power modules.
Unexpected switch reboot
Symptom
The switch reboots unexpectedly when it is operating.
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
Solution
To resolve the issue:
1. Verify that you can access the CLI.
{If you can access the CLI, execute the display diagnostic-information command to
collect operating statistics.
{If you cannot access the CLI, go to step 2.

6
2. Verify that the system software image on the switch is correct.
Log in to the switch through the console port and restart the switch. If the system reports that a
CRC error has occurred or that no system software image is available during the BootWare
loading process, reload the system software image on the BootWare menu and configure it as
the current system software image.
3. If the issue persists, contact H3C Support.
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 display power module information.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal DC -- -- --
2 Fault AC -- -- --
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. If the power module is in Absent state, perform the following tasks:
a. Remove and reinstall the power module to make sure the power module is installed
correctly. Then, execute the display power command to verify that the power module has
changed to Normal state.
b. If the power module remains in Absent state, remove and reinstall the power module in an
empty power module slot. Then, execute the display power command to verify that the
power module has changed to Normal state.
c. If the power module remains in Absent state, replace the power module.
3. If the power module is in Fault state, perform the following tasks:
a. Verify that the power module has not been disconnected from the power source. If it has
been disconnected from the power source, connect the power source to it.
b. Verify that the power module surface is clean. If there is dust accumulated on the power
module, remove the dust. Then remove and reinstall the power module. Execute the
display power command to verify that the power module has changed to Normal state. If
the power module remains in Fault state, go to step c.
c. Install the power module into an empty power module slot. Then execute the display power
command to verify that the power module has changed to Normal state in the new slot. If
the power module remains in Fault state, replace the power module.
4. If the issue persists, contact H3C Support.

7
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.
<Sysname> display power
Slot 1:
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Normal DC -- -- 0
2 Fault AC -- -- 0
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. When the power module is in Absent state, perform the following tasks:
a. Remove and reinstall the power module to make sure the power module is installed
securely. Then execute the display power command to verify that the power module has
changed to Normal state. If the power module remains in Absent state, go to step b.
b. Remove and install the power module into an empty power module slot. Then execute the
display power command to verify that the power module has changed to Normal state in
the new slot. If the power module remains in Absent state, go to step 4.
3. Remove and install the power module into an idle power module slot. Then execute the display
power command to verify that the power module has changed to Normal state in the new slot.
If the power module remains in Fault state, go to step 4.
4. If the issue persists, contact H3C Support.
Fan tray failure
Symptom
A fan tray is not operating correctly. The display fan command displays that the fan tray is in Fault
state.
<Sysname> display fan
Slot 1:
Fan 1:
State : Normal
Fan 2:
State : Fault
Solution
Contact H3C Support to resolve the issue.

8
USB device anomaly
Symptom
The USB device connected to the USB port is in abnormal state.
Solution
To resolve the issue:
1. Display information about the USB device.
<Sysname> display device usb
slot 1:
Device Name : usba
State : Absent
If the USB device state is Absent, it has failed to be identified by the USB port. Go to 2.
2. Verify that the USB device is operating correctly.
Connect another USB device to the USB port. If this USB device cannot be identified, go to 3.
3. If the issue persists, contact H3C Support.
Interface card anomaly
Symptom
An interface card is in abnormal state.
Solution
To resolve the issue:
1. View the message displayed for the interface card.
%Jan 1 20:57:42:169 2013 H3C DRVPLAT/4/DrvDebug:
Subslot 1 can not support this card.
If the device outputs this message repeatedly, determine whether the device supports this
interface card. If the device does not support this interface card, replace the interface card with
one compatible with the device. If the issue persists, go to 4.
2. View interface card information on the device.
<sysname> display device manuinfo slot 1
Subslot 1:
DEVICE_NAME : LSWM2SP2PB
DEVICE_SERIAL_NUMBER : 210231A9UFM186A0000R
MANUFACTURING_DATE : 2018-06-19
VENDOR_NAME : H3C
…
If no information about the interface card is displayed, go to 3.
3. Verify that the interface card is installed securely.
Remove and reinstall the interface card and then view interface card information. If information
about the interface card is still not available, go to 4.

9
4. If the issue persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting hardware.
Command Description
display device manuifo Displays information about the device.
display device usb Displays operating information about USB devices.
display fan Displays operating information about fan trays.

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

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

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

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

14
Troubleshooting flowchart
Figure 3 Troubleshooting IRF fabric establishment failure
Solution
To resolve the issue:
1. Verify that the switch models can form an IRF fabric:
a. Verify that the member switches are from the same switch series.
b. Use the virtual technologies configuration guide for the switch series to verify whether the
switches in the switch series are grouped for IRF compatibility. If they are grouped, make
sure the IRF member switches are from the same IRF compatibility group.
No
Yes
No
Yes
No
Yes
IRF setup failure
No
No
Yes
Yes
No
Yes
No
Yes
Yes
No
Yes No
Yes
Use models in the same
switch series or same
group
Yes
No
Is the number of members
fewer than the upper limit?
Assign a unique member
ID to each member device
Can models join the
same IRF fabric?
Is the member ID of
each member unique? No Resolved?
Are physical IRF connections
correct? Reconnect IRF physical
interfaces Resolved?
Do IRF physical
interfaces meet binding and
connection requirements? Resolved?
Are IRF links up? Resolved?
You cannot add any device
to the IRF fabric or
complete IRF merge
Bring up the IRF
links/activate IRF port
configuration
Use IRF physical
interfaces that meet the
binding and connection
requirements
Same software version? Upgrade software to the
same version
Contact H3C
Support
No Resolved?
End
Yes
No
Resolved?
Yes

15
2. Verify that the number of member devices does not exceed the upper limit (varies by software
version and device model).
To obtain the upper limit for your device, contain H3C Support.
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.
3. 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.
4. Verify that the physical IRF connections are correct:
a. Execute the display irf configuration command on each member device, and check the
IRF-Port1 and IRF-Port2 fields for physical interfaces bound to IRF ports.
b. Verify that the physical interfaces of IRF-port 1 on one member are connected to the
physical interfaces of IRF-port 2 on the other member.
5. Verify that the IRF physical interfaces meet the binding and connection requirements:
a. Verify that the physical interfaces bound to IRF ports can be used as IRF physical
interfaces.
IMPORTANT:
Make sure all the member devices use ports of the same type as IRF physical interfaces.
Software
version Hardware platforms Candidate IRF physical interfaces
Release 63xx All
10-GE ports operating at 10 Gbps
5-GE ports operating at 5 Gbps
2.5-GE ports operating at 2.5 Gbps
1-GE ports operating at 1 Gbps
Release 612x
S5130S-28MP-EI
S5130S-28MP-HPWR-EI
S5130S-52MP-EI
5-GE ports operating at 5 Gbps
1-GE ports operating at 1 Gbps
S5000E-X switch series 10-GE ports operating at 10 Gbps
1-GE ports operating at 1 Gbps
Switch models not listed
above
Switches with 10 GE ports: 10-GE ports
operating at 10 Gbps
Switches without 10 GE ports: 1-GE ports
operating at 1 Gbps
b. Verify that the cables and transceiver modules match the IRF physical interfaces.
If you use transceiver modules and fibers for IRF connections, make sure the transceiver
modules at the two ends of the link are the same type.
c. Verify that the IRF port bindings meet the grouping restrictions if you use ports in a group for
IRF links. When you use the ports in a group for IRF links, follow these restrictions and
guidelines:
−If you use one port in a group as an IRF physical interface, the remaining ports in the
group can only act as IRF physical interfaces. You cannot use them for any other

16
purposes. To use a port in a group for any purpose other than IRF physical interfaces, do
not bind any of the ports in the group to an IRF port.
−The ports in a group can be bound to different IRF ports.
−You must shut down all ports in a group before you can assign or remove any of the
ports to or from an IRF port. To bring up the ports after the assignment or removal is
complete, execute the undo shutdown command.
To identify ports in a port group, use the debug port mapping command in probe view.
Ports that have the same unit value belong to the same group.
IMPORTANT:
The following information varies by device model:
•Candidate IRF physical interfaces.
•Port binding restrictions.
•Applicable transceiver modules or cables.
For more information, see configuration and installation guides for the device.
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 in use 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 interfaces.
−If the field displays UP for a minimum of 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. As a best practice,
upgrade the earlier versions to the most recent 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.

17
Command Description
display irf Displays IRF fabric information, including the member ID, role, priority,
bridge MAC address, and description of each IRF member.
display irf link Displays IRF link information, including the member ID, IRF port,
interfaces bound to each IRF port, and status of each IRF link.
display irf configuration Displays basic IRF settings, including the current member ID, new member ID, and physical interfaces 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.