Troubleshooting Fip-600 Lpu; Failure To Ping A Directly Connected Device; Symptom; Solution - HP HSR6600 Troubleshooting Manual

Troubleshooting FIP-600 LPU

This section provides troubleshooting information for common FIP-600 LPU problems.

Failure to ping a directly connected device

Symptom

The FIP-600 LPU cannot ping an Ethernet 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.
Contact HP Support for information about why the packets are sent to the CPU.
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 HP Support for 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 HP Support for 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 dpaa slot slot-num bman pool-info command
to view statistics about hardware buffer pools.
Contact HP Support if a buffer pool with a BPID in the range of 0 to 3 meets the following
conditions:
9