Extreme Networks ExtremeWare Version 7.8, Troubleshooting Manual

Page: 36 / 122

36 Advanced System Diagnostics and Troubleshooting Guide
Packet Errors and Packet Error Detection
The PBUS checksum type might indicate a problem with the packet memory, but it might also point to
other problem types, indicating failures with other hardware components detected during additional
checking performed under the umbrella of the Extreme diagnostics suite. For example, any other
component in the path between the ingress and egress points could malfunction, resulting in a
corrupted checksum. You should be aware that PBUS checksum messages and conditions can be caused
by a packet memory failure, but that there are other possibilities as well. The packet memory scan
should always be used in conjunction with the extended diagnostics to check the integrity of all the
components.
Possible error conditions for PBUS action messages:
• CARD_HWFAIL_PBUS_CHKSUM_INT_ERROR
• CARD_HWFAIL_PBUS_CHKSUM_EXT_ERROR
• CARD_HWFAIL_PBUS_CHKSUM_EDP_ERROR
• CARD_HWFAIL_PBUS_CHKSUM_CPU_PKT_ERROR
• CARD_HWFAIL_PBUS_CHKSUM_CPU_PKT_DIAG_ERROR
• Backplane link—Indicates that health check packets were lost on one or more backplane
links connecting an MSM module to an I/O module. Either module might be in error; check
the transceiver diagnostics.
• FDB error—Indicates that a discrepancy was detected during the FDB scan of the RAM
memory pool.
error The error condition that summarizes the failure. One of many values that points to a specific
hardware component or software test (for further problem isolation).