H3C SR6600 Series User manual

i
H3C SR6600&SR6600-X Routers
Troubleshooting Guide
SR6600 Router Series
SR6600-X Router Series
Software version: R7606
Document version: 6W101-20181015
Copyright © 2018 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.

ii
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······························································································································5
Troubleshooting CPOS interfaces··································································6
CPOS interface and serial interface down·········································································································6
Symptom····················································································································································6
Solution······················································································································································6
Data link layer protocol flapping or traffic forwarding failure on serial interface·················································7
Symptom····················································································································································7
Solution······················································································································································7
Related commands············································································································································7
Troubleshooting FIP-600 modules·································································9
Failure to ping a directly connected device········································································································9
Symptom····················································································································································9
Solution······················································································································································9
Failure to forward traffic ···································································································································10
Symptom··················································································································································10
Solution····················································································································································10
Packet loss·······················································································································································11
Symptom··················································································································································11
Solution····················································································································································11
Related commands··········································································································································11
Troubleshooting POS interfaces··································································13
Interface physically down·································································································································13
Symptom··················································································································································13
Solution····················································································································································13
Data link layer down·········································································································································13
Symptom··················································································································································13
Solution····················································································································································13
Related commands··········································································································································14
Troubleshooting SAP modules ····································································15
Failure of an interface to come up····················································································································15
Symptom··················································································································································15
Solution····················································································································································15
Failure to forward traffic ···································································································································15
Symptom··················································································································································15
Solution····················································································································································15
Packet loss in data forwarding·························································································································16
Symptom··················································································································································16
Solution····················································································································································16
Related commands··········································································································································16
Troubleshooting WAN-IRF···········································································17
IRF fabric setup failure·····································································································································17
Symptom··················································································································································17
Solution····················································································································································17
Cross-chassis traffic forwarding failure············································································································18
Symptom··················································································································································18
Solution····················································································································································18

iii
Cross-chassis packet loss problem ·················································································································19
Symptom··················································································································································19
Solution····················································································································································19
IRF split····························································································································································19
Symptom··················································································································································19
Solution····················································································································································19
Related commands··········································································································································20
Troubleshooting cards·················································································22
MPU or SR6602-X device startup failure·········································································································22
Symptom··················································································································································22
Solution····················································································································································22
LPU startup failure ···········································································································································26
Symptom··················································································································································26
Solution····················································································································································26
Related commands··········································································································································28
Troubleshooting transceiver modules··························································28
Interface down··················································································································································28
Symptom··················································································································································28
Solution····················································································································································28
Transceiver module type not recognized·········································································································29
Symptom··················································································································································29
Solution····················································································································································29
Interface or transceiver module alarm ·············································································································29
Symptom··················································································································································29
Solution····················································································································································29
Related commands··········································································································································29
Troubleshooting ports··················································································30
Failure to ping the directly connected device···································································································30
Symptom··················································································································································30
Solution····················································································································································30
Failure to forward packets································································································································31
Symptom··················································································································································31
Solution····················································································································································31
Packet dropping···············································································································································32
Symptom··················································································································································32
Solution····················································································································································32
Related commands··········································································································································32
Troubleshooting active/standby MPU switchover·········································33
Exceptional standby MPU reboot·····················································································································33
Symptom··················································································································································33
Solution····················································································································································33
Exceptional active/standby MPU switchover····································································································34
Symptom··················································································································································34
Solution····················································································································································34
Related commands··········································································································································34
Troubleshooting interface modules······························································34
Interface information not displayed··················································································································35
Symptom··················································································································································35
Solution····················································································································································35
Interface module information not displayed ·····································································································35
Symptom··················································································································································35
Solution····················································································································································35
Related commands··········································································································································36

1
Introduction
This document provides information about troubleshooting common software and hardware
problems with H3C SR6600/SR6600-X routers.
General guidelines
IMPORTANT:
To prevent a
problem from causing loss of configuration, save the configuration each time you finish
configuring a feature. For configuration recovery, regularly back up the configuration to a remote
server.
When you troubleshoot the router, follow these general guidelines:
•
To help identify the cause of the problem, collect system and configuration information,
including:
Symptom, time of failure, and configuration.
Network topology information, including the network diagram, port connections, and points
of failure.
Log messages and diagnostic information. For more information about collecting this
information, see "Collecting log and operating information."
Physical evidence of failure:
−Photos of the hardware.
−Status of the card, power, and fan status 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
IMPO
RTANT:
By default, the information center is enabled. If the feature is disabled,
you must use the info-
center
enable command to enable the feature for collecting log messages.
Table 1 shows the types of files that the system uses to store operating log and status information.
You can export these files by using FTP, TFTP, or USB.
These files are stored on the active MPU (in standalone mode) or global active MPU (in IRF mode).
Multiple MPUs will have log files if active/standby or master/subordinate switchovers have occurred.
You must collect log files from all these MPUs. To more easily locate log information, use a consistent
rule to categorize and name files. For example, save log information files to a separate folder for
each MPU, and include their chassis and slot numbers in the folder names.

2
Table 1 Log and operating information
Category
File name format
Content
Common log
logfile
X
.log
Command execution and operational log messages.
Diagnostic log diagfileX.log
Diagnostic log messages about device operation, including the
following items:
•Parameter settings in effect when an error occurs.
•Information about a card startup error.
•Handshaking information between the MPU and LPU
when a communication error occurs.
Operating
statistics file-basename.gz
Current operating
statistics for feature modules, including the
following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
NOTE:
For common and diagnostic log files, the system automatically compresses them into .gz files when
they are full.
Collecting common log messages
1. Save common log messages from the log buffer to a log file.
By default, log files are saved in the logfile directory of the CF card on the active MPU (in
standalone mode) or global active MPU (in IRF mode).
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
cfa0:/logfile/logfile8.log
2. Identify the log files on each MPU:
# Display the log files on the active MPU (in standalone mode) or global active MPU (in IRF
mode).
<Sysname> dir cfa0:/logfile/
Directory of cfa0:/logfile
0 -rw-21863 Jul 11 2013 16:00:37 logfile8.log
1021104 KB total (421552 KB free)
# Display the log files on each standby MPU:
In standalone mode, display the log files on the standby MPU.
<Sysname> dir slot1#cfa0:/logfile/
Directory of slot1#cfa0:/logfile
0 -rw-21863 Jul 11 2013 16:00:37 logfile8.log
1021104 KB total (421552 KB free)
In IRF mode, display the log files on each standby MPU.
<Sysname> dir chassis2#slot0#cfa0:/logfile/
Directory of chassis2#slot0#cfa0:/logfile

3
0 -rw-21863 Jul 11 2013 16:00:37 logfile8.log
1021104 KB total (421552 KB free)
NOTE:
If a subordinate chassis has two MPUs, make sure you identify and export the log files on both
MPUs.
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)
Collecting diagnostic log messages
1. Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.
By default, diagnostic log files are saved in the diagfile directory of the CF card on each MPU.
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
cfa0:/diagfile/diagfile18.log
2. Identify the diagnostic log files on each MPU:
# Display the diagnostic log files on the active MPU (in standalone mode) or global active MPU
(in IRF mode).
<Sysname> dir cfa0:/diagfile/
Directory of cfa0:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile18.log
1021104 KB total (421416 KB free)
# Display the diagnostic log files on each standby MPU:
In standalone mode, display the diagnostic log files on the standby MPU.
<Sysname> dir slot1#cfa0:/diagfile/
Directory of slot1#cfa0:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile18.log
1021104 KB total (421416 KB free)
In IRF mode, display the diagnostic log files on each standby MPU.
<Sysname> dir chassis2#slot0#cfa0:/diagfile/
Directory of chassis2#slot0#cfa0:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile18.log
1021104 KB total (421416 KB free)
NOTE:
If a subordinate chassis has two MPUs, make sure you identify and export the
diagnostic log
files on both MPUs.
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.

4
When you collect operating statistics, follow these guidelines:
•
Log in to the device through a network port 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.
•
H3C recommends saving operating statistics to a file to retain the information.
To collect operating statistics:
1. Disable pausing between screens of output if you want to display operating statistics on the
screen. Skip this step if you are saving statistics to a file.
<Sysname> screen-length disable
2. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
3. 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.tar.gz] :cfa0:/diag.tar.gz
Diagnostic information is outputting to cfa0:/diag.tar.gz.
Please wait...
Save successfully.
<Sysname> dir cfa0:/
Directory of cfa0:
…
6 -rw-898180 Jun 26 2013 09:23:51 diag.tar.gz
1021808 KB total (259072 KB free)
# To display operating statistics on the monitor terminal, enter nat the prompt.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :N
===========================================================
===============display alarm===============
No alarm information.
=========================================================
===============display boot-loader===============
Software images on slot 0:
Current software images:
cfa0:/SR6600-X-CMW710-BOOT-R7328_mrpnc.bin
cfa0:/SR6600-X-CMW710-SYSTEM-R7328_mrpnc.bin
Main startup software images:
cfa0:/SR6600-X-CMW710-BOOT-R7328_mrpnc.bin
cfa0:/SR6600-X-CMW710-SYSTEM-R7328_mrpnc.bin
Backup startup software images:
None
=========================================================
===============display counters inbound interface===============
Interface Total (pkts) Broadcast (pkts) Multicast (pkts) Err (pkts)
BAGG1 0 0 0 0
GE4/0/1 0 0 0 0
GE4/0/2 2 2 0 0
GE4/0/3 0 0 0 0

5
GE4/0/4 0 0 0 0
GE4/0/5 0 0 0 0
GE4/0/6 0 0 0 0
GE4/0/7 0 0 0 0
GE4/0/8 0 0 0 0
GE4/0/9 0 0 0 0
GE4/0/10 0 0 0 0
……
Contacting technical support
If you cannot resolve a problem after using the troubleshooting procedures in this document, contact
H3C Support. When you contact an authorized H3C support representative, be prepared to provide
the following information:
•
Information described in "General guidelines."
•
Product serial numbers.
This information will help the support engineer assist you as quickly as possible.
The following is the contact information for H3C Support:
•
Telephone number—400-810-0504.
•
E-mail—[e-mail]

6
Troubleshooting CPOS interfaces
This section provides troubleshooting information for common CPOS interface problems.
CPOS interface and serial interface down
Symptom
A CPOS interface directly connected to another device is physically down. The serial interface
created through channelization on the CPOS interface is physically down, and the data link layer
protocol state of the serial interface is down.
Solution
To resolve the problem:
1. Execute the display controller cpos interface-name command to view the status information
of the CPOS interface.
2. If the CPOS interface is down and an LOS or LOF error has been generated, verify the following
items:
The optical fiber is connected correctly.
The two ends use different clock mode settings (master at one end and slave at the other
end).
3. If the CPOS interface is up but the serial interface is physically down, execute the display
controller cpos interface-name command. Determine whether the channel to which the serial
interface belongs has alarms generated.
If the channel to which the serial interface belongs has no alarms generated, the shutdown
command might have been executed for the serial interface. Execute the display interface
serial interface-number command to view the status of the serial interface. If the serial interface
status is DOWN (Administratively), execute the undo shutdown command to bring up the
serial interface.
4. If the serial interface is physically up but the data link layer protocol state is down, execute the
display interface serial interface-number command. Verify that the HDLC chip of the CPOS
interface collects packet statistics correctly.
5. If the problem persists, collect the following statistics and contact H3C Support:
Execute the debugging physical packet command to enable packet debugging on both
devices to verify that they can correctly send and receive packets. Collect packet sending
and receiving statistics.
Execute the display hardware internal module cpos interface-number statistics
command in probe view to collect statistics of the CPOS interface.
Execute the display hardware internal module cpos interface-number reg 0command in
probe view to collect the CPLD information of the CPOS interface.
Execute the display hardware internal module cpos interface-number reg 1command in
probe view to collect the FPGA information of the CPOS interface.
Collect the chip register information of the CPOS interface by executing the following
commands in probe view:
−display hardware internal module cpos interface-number reg 2.
−display hardware internal module cpos interface-number reg 3.
−display hardware internal module cpos interface-number reg 4.

7
Execute the display hardware internal module serial interface-number statistics
command in probe view to collect statistics of the serial interface, including the CPU
statistics.
Execute the display hardware internal module cpos interface-number statistics
command in probe view to collect the FPGA information of the interface module.
Data link layer protocol flapping or traffic
forwarding failure on serial interface
Symptom
The data link layer protocol state flaps or the traffic forwarding fails on the serial interface.
Solution
To resolve the problem:
1. If the serial interface is physically down, follow the steps described in "CPOS interface and
serial interface down" to resolve the problem.
2. If the problem persists, collect the following statistics and contact H3C Support:
Execute the display hardware internal module interface-number command in probe view
to determine whether the serial interface has received or sent error packets and collect
packet statistics.
Use the debugging physical packet command to enable packet debugging on both
devices to verify that they can correctly send and receive packets. Collect packet sending
and receiving statistics.
Execute the display hardware internal module cpos interface-number statistics
command in probe view to collect statistics of the CPOS interface.
Execute the display hardware internal module cpos interface-number reg 0command in
probe view to collect the CPLD information of the CPOS interface.
Execute the display hardware internal module cpos interface-number reg 1command in
probe view to collect the FPGA information of the CPOS interface.
Collect the chip register information of the CPOS interface by executing the following
commands in probe view:
−display hardware internal module cpos interface-number reg 2.
−display hardware internal module cpos interface-number reg 3.
−display hardware internal module cpos interface-number reg 4.
Execute the display hardware internal module serial interface-number statistics
command in probe view to collect statistics of the serial interface, including the CPU
statistics.
Execute the display hardware internal module cpos interface-number statistics
command in probe view to collect the FPGA information of the interface module.
Related commands
This section lists the commands that you might use for troubleshooting CPOS interfaces.

8
Command
Description
clock master
Sets the clock mode of the CPOS interface to
master.
debugging physical packet Enables packet debugging on the device.
display controller cpos interface-name
Displays status information for CPOS interfaces,
including alarms and errors that occurred to the
regenerator section, multiplex section, and
higher-order path.
display hardware internal module interface-name
interface-number reg { 0| 1| 2|3| 4}
Displays hardware register information about
CPOS interfaces.
display hardware internal module interface-name
interface-number
statistics
Displays mainte
nance information about CPOS
interfaces.
display interface serial interface-number Displays information about serial interfaces.
undo shutdown Brings up the CPOS interface.

9
Troubleshooting FIP-600 modules
This section provides troubleshooting information for common FIP-600 module problems.
Failure to ping a directly connected device
Symptom
A FIP-600 module fails to ping a directly connected device.
Solution
To resolve the problem:
1. Use the display interface command to view information about the output interface of the ping
packets and verify the following items:
The interface is up.
The interface counters are collecting packet statistics correctly. For example, if packet error
statistics are correctly collected, cable and interface problems can be ruled out.
2. Use the display arp all command to verify that the router has an ARP entry for the directly
connected interface.
If no such ARP entry exists, execute the debugging arp packet command on both devices to
determine whether they can correctly receive and send ARP packets.
3. In probe view, use the debugging hardware internal fdp cdat slot slot-num debug { ingress
| egress } command to view debugging information of packets sent and received by the CPU
data channel interface.
The first 32 bytes represent the header fields, followed by 32 bytes of payload. You can filter the
packets to be displayed based on criteria such as interface or packet length.
To learn the reason why the packets are sent to the CPU, contact H3C Support.
4. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics
command to view the packet statistics of the CPU data channel. To view detailed statistics such
as vCPU-based statistics, execute the display hardware internal fdp cdat slot slot-num
statistics 4command.
5. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 8
command to view the packet drop statistics of the CPU and the logic module. Contact H3C
Support to learn the causes for the packet drop.
6. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 80
command to view statistics of the logic module. Contact H3C Support to learn the causes if
packet drop exists.
7. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 100
command to view statistics about the CPU data channel interface.
8. In probe view, execute the display hardware internal fdp flow slot slot-num statistic
command to view statistics about the Layer 3 packets sent to the CPU. If packet error or loss
occurs, contact H3C Support to learn the causes.
9. In probe view, execute the display hardware internal fdp cdat slot slot-num status 80
command to view statistics of the logic module. If the FIFO status is not empty when there is no
traffic, the FIFO queue is congested. Contact H3C Support to diagnose the problem.

10
10. If the logic module and the CPU can correctly send and receive packets, use the software
forwarding diagnostic techniques to diagnose the problem. For example, verity that the correct
routing entry exists in the routing table.
11. Execute the display hardware internal nae slot slot-num freein command in probe view to
collect hardware information and contact H3C Support to locate the problem.
Failure to forward traffic
Symptom
A router installed with FIP-600 modules fails to forward traffic as an intermediate device.
Solution
To resolve the problem:
1. Ping a directly connected device. If the ping operation fails, follow the procedure described in
"Failure to ping a directly connected device" to resolve the problem.
2. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics
command to view the packet statistics of the CPU data channel. The following conditions might
exist:
If the packet output rate of the CPU decreases significantly, the packets are dropped or
transparently sent to the MPU.
If the packet output rate and input rate are approximately the same, the packets are sent to
the CPU for normal forwarding.
If the packet input rate is significantly lower than the packet output rate, the packets are not
sent to the CPU.
3. If the packets are sent to the CPU, execute the following command in probe view to view the
debugging information of packets sent and received by the CPU data channel interface:
debugging hardware internal fdp cdat slot slot-num debug { ingress | egress }
The first 32 bytes represent the header fields, followed by 32 bytes of payload. You can filter the
packets to be displayed based on criteria such as interface or packet length.
To learn the causes why the packets are sent to the CPU, contact H3C Support.
4. If the packets are dropped, perform the following tasks:
Execute the display hardware internal fdp cdat slot slot-num statistics 8 command in
probe view to view the packet loss statistics. Contact H3C Support to learn the causes for
the packet loss.
Execute the display hardware internal fdp flow slot slot-num statistic command to view
statistics about the Layer 3 packets sent to the CPU. If packet error or drop exists, contact
H3C Support to diagnose the problem.
5. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 8
command to view the packet loss statistics of the CPU and the logic module. Contact H3C
Support to learn the causes for the packet loss.
6. In probe view, execute the debugging hardware internal fdp cdat slot slot-num bypass
interface command to enable bypass logic on the interface where the packets to be forwarded
are received. If traffic can be forwarded correctly after the feature is enabled, an error has
occurred to the logic module. Contact H3C Support to diagnose the problem.
7. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 80
command to view statistics of the logic module. If packet drops exist, contact H3C Support to
learn the causes.

11
8. In probe view, execute the display hardware internal fdp cdat slot slot-num status 80
command to view statistics of the logic module. If the FIFO status is not empty when there is no
traffic, the FIFO queue is congested. Contact H3C Support to diagnose the problem.
9. If the logic module and the CPU can correctly send and receive packets, use the software
forwarding diagnostic techniques to diagnose the problem. For example, verity that the correct
routing entry exists in the routing table.
10. If the problem persists, contact H3C Support.
Packet loss
Symptom
A large number of packets are dropped by a FIP-600 module during the forwarding process.
Solution
To resolve the problem:
1. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics
command to view the packet statistics of the CPU data channel. The following conditions might
exist:
If the packet output rate and input rate are approximately the same, the packets are
forwarded by the logic module to the CPU for normal forwarding.
If the packet input rate is significantly lower than the output rate, the packets are not sent to
the CPU.
2. If the packets are sent to the CPU, execute the following command in probe view to view the
debugging information of packets sent and received by the CPU data channel interface:
debugging hardware internal fdp cdat slot slot-num debug { ingress | egress }
The first 32 bytes represent the header fields, followed by 32 bytes of payload. You can filter the
packets to be displayed based on criteria such as interface or packet length.
To learn the causes why the packets are sent to the CPU, contact H3C Support.
3. If the packets are dropped by the logic module before being sent to the CPU, execute the
display hardware internal fdp cdat slot slot-num statistics 8 command in probe view to view
the packet loss statistics of the logic module. Contact H3C Support to learn the causes for the
packet loss.
4. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 80
command to view statistics of the logic module. If packet drops exist, contact H3C Support to
learn the causes for the packet drops.
5. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting FIP-600 modules.
Command
Description
debugging hardware internal fdp cdat slot
slot-num bypass Enables the bypass logic feature.
debugging hardware internal fdp cdat slot
slot-num debug
Enables packet debugging for the CPU data
channel.

12
Command
Description
display hardware internal fdp cdat slot slot-num
statistics Displays the CPU data channel statistics.
display hardware internal fdp cdat slot slot-num
status Displays the CPU data channel status information.
display hardware internal fdp flow slot slot-num
statistic Displays statistics about received Layer 3 packets.
display hardware internal nae slot slot-num freein Displays information about
the CPU hardware
buffer pools.
reset hardware internal fdp cdat slot slot-num
statistics Clears the CPU data channel statistics.
reset hardware internal fdp flow slot slot-num
statistic Clears statistics about received Layer 3 packets.

13
Troubleshooting POS interfaces
This section provides troubleshooting information for common POS interface problems.
Interface physically down
Symptom
The physical state of the POS interface is down.
Solution
To resolve the problem:
1. Verify that the two ends use different clock mode settings (master at one end and slave at the
other end).
2. Verify that the POS interface and its optical module have matching transmission rate.
3. Verify that the two ends use the same framing format.
4. Use the display interface pos interface-number command to view the alarms generated on
the interface.
If an AIS alarm was generated, verify that the interface has correct overhead bytes settings.
If an LOS or LOF error was generated, verify that the optical module on the two ends and
the optical fiber are working correctly.
5. If the problem persists, contact H3C Support.
Data link layer down
Symptom
The physical state of the POS interface is up, but the data link layer state is down.
Solution
This symptom might occur due to negotiation failures caused by packet loss.
To resolve the problem:
1. Execute the debugging physical packet all interface pos command on both devices to
identify the faulty device.
2. On the faulty device, perform the following tasks:
a. Execute the reset counters interface pos interface-number command to clear statistics
for the POS interface.
b. In probe view, execute the display hardware internal module pos interface-number
statistics command to view packet statistics.
c. Perform the following tasks:
−Use the display hardware internal module pos interface-number reg 3 command in
probe view to verify that the physical layer configuration is correct.

14
−Use the display hardware internal module pos interface-number reg 1command in
probe view to verify that the FPGA configuration is correct.
3. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting POS interfaces.
Command
Description
debugging physical packet Enables packet debugging on the device.
display hardware internal module interface-name
interface-number reg 1 Displays FPGA information about POS interfaces.
display hardware internal module interface-name
interface-number reg 3 Displays physical layer information abo
ut POS
interfaces.
display hardware internal module interface-name
interface-number statistics
Displays maintenance information about POS
interfaces.
reset counters interface pos
interface-number
Clears POS interface statistics.

15
Troubleshooting SAP modules
This section provides troubleshooting information for common SAP module problems.
Failure of an interface to come up
Symptom
An interface on a SAP module fails to come up.
Solution
To resolve the problem:
1. Verify that the SAP module has started up correctly.
2. Verify that the interface is not shut down manually. If it is shut down manually, execute the undo
shutdown command to bring up the interface.
3. Check the transceiver module and fiber for damages and connection faults. Adjust the fiber
connector or reconnect the fiber connector to the transceiver module.
4. Verify that the transceiver module and the fiber are compatible.
5. If the problem persists, contact H3C Support.
Failure to forward traffic
Symptom
A SAP module fails to forward traffic.
Solution
To resolve the problem:
1. Verify that the device where the SAP module resides is operating correctly.
2. Verify that the traffic forwarding configuration on the SAP module is correct.
3. Verify that both the inbound and outbound interfaces are up. If an interface is not up, see
"Failure of an interface to come up."
4. Execute the display interface command in system view to determine whether the interfaces
are sending and receiving packets correctly.
If the interface is receiving packets correctly, verify that the directly connected device is
operating correctly. If the peer device is not operating correctly, troubleshoot the peer
device.
If the interface fails to send packets or packet loss occurs in data transmitting, execute the
debugging physical packet command to display information about packets sent to the
CPU.
−If the command displays packet information, the packets are sent to the CPU correctly.
−If the command does not display packet information, packets are not sent to the CPU.
Enter probe view and execute the bcm slot chip show/counter command to display
statistics about packet loss and contact H3C Support.

16
5. If the packets are discarded after being sent to the CPU, contact H3C Support.
6. Execute the bcm slot chip l3/defip/show command in probe view to determine whether the
routing entries are correct and whether the packets match the routing entries. If not, contact
H3C Support
7. If the problem persists, contact H3C Support.
Packet loss in data forwarding
Symptom
Packet loss occurs in data forwarding.
Solution
To resolve the problem, see "Failure to forward traffic."
Related commands
This section lists the commands that you might use for troubleshooting SAP modules.
Command
Description
bcm slot chip l3/defip/show Displays information about routing entries.
bcm slot chip l3/l3table/show Displays ARP entries.
bcm slot chip show/counter Displays
traffic statistics and data rate for an
interface.
debugging physical packet [all | input | output ]
interface interface-number Displays information about the packets sent to the
CPU.
display counters { inbound | outbound } interface Displays traffic statistics on an interface.
display interface interface-number Displays information about an interface.
reset counters interface Clears traffic statistics on an interface.

17
Troubleshooting WAN-IRF
This section provides troubleshooting information for common WAN-IRF problems. In this section,
WAN-IRF is referred to as IRF.
IRF fabric setup failure
Symptom
Two routers cannot form an IRF fabric.
Solution
To resolve the problem:
1. Execute the display device command on each device to verify that the devices are operating in
IRF mode and have unique IRF member IDs:
If the Chassis field is not available for a device, use the chassis convert mode irf
command to enable IRF mode for the device.
If the Chassis field is available, check the value for this field. Make sure each device has a
unique value for this field and the value must be 1 or 2. You can use the irf member
renumber command to configure the value (IRF member ID). The value takes effect after a
reboot.
2. Execute the display irf configuration command to verify that IRF physical interfaces have
been bound to IRF-port 1 on one device and to IRF-port 2 on the other device.
Make sure the IRF port bindings meet the binding requirements in the virtual technologies
configuration guide for the router.
3. Verify that the IRF physical interfaces are connected correctly:
IMPORTANT:
When you connect two neighboring IRF members,
connect the physical interfaces of IRF-
port 1
on one member to the physical interfaces of IRF-port 2 on the other.
a. Verify that no intermediate devices are deployed between the member devices.
b. Verify that the recommended connection media are used to connect IRF physical
interfaces:
−Use straight-through or crossover copper Ethernet cables to connect copper Ethernet
ports for a short-distance connection.
−Use transceiver modules and fibers to connect fiber Ethernet ports for a long-distance
connection.
−Make sure the transceiver modules at the two ends of an IRF link are the same type. For
more information about transceiver modules, see the device installation guide.
c. Verify that the physical IRF connections are consistent with the IRF port bindings. If there
are inconsistencies, reconfigure the IRF port bindings or reconnect the IRF physical
interfaces.
4. Execute the display irf link command to verify that a minimum of one IRF link is up for the
devices.
5. In probe view, execute the display hardware internal wanirf ipc pkt-info chassis
chassis-number slot slot-number interface-type interface-number command for each IRF