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
4
command.
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.
