Corrective Behavior Messages - Extreme Networks ExtremeWare Version 7.8 Troubleshooting Manual

These messages appear in the log when EDP packets received are corrupted:
•
<Crit:SYST> Sys-health-check [EDP] checksum error (slow-path) on M-BRD, port 0x03
701026-00-03 0003Y-00052
•
<Crit:SYST> Sys-health-check [EDP] checksum error (slow-path) on BPLNE, port 0x03
701026-00-03 0003Y-00052
•
<Crit:SYST> Sys-health-check [EDP] checksum error (slow-path) on MSM-A, port 0x03
701026-00-03 0003Y-00052
These messages appear in the log when the hardware detects checksum errors in the fast path and
updates the corresponding registers:
•
<Crit:KERN> Sys-health-check [EXT] checksum error (fast-path) on slot 4 prev=0
cur=100 701033-00-02 0047B-00008
•
<Crit:KERN> Sys-health-check [INT] checksum error (fast-path) on slot 5 prev=0
cur=100 701033-00-02 0087E-00009

Corrective Behavior Messages

These error messages are inserted into the system log when the decision parameters (described earlier
in "Responding to Reported Failures" on page
exceeded. These messages indicate that the system health check has taken the configured response
action (log, send traps, card down, system down, or auto recovery) upon detecting a systematic error
and take the general format:
date time < level : from > Sys-health-check [ACTION] problem-type error
Example:
<CRIT:SYST> Sys-health-check [ACTION] (PBUS checksum)
(CARD_HWFAIL_PBUS_CHKSUM_CPU_PKT_ERROR) slot 2
where:
problem-type
Advanced System Diagnostics and Troubleshooting Guide
— (Summit)
— (Alpine)
— (BlackDiamond)
The type of problem detected, based on the health check diagnostic component that triggered
the action, from among the following:
• CPU diag packet—Action was taken because an excessive number of CPU health check
packets were missed. Examine the CPU health check diagnostics. Errors on more than one
slot probably indicate MSM management bus transceiver issues. Errors on single slots
probably indicate that the specified slot is in error.
• Backplane diag packet—Action was taken because an excessive number of backplane health
check packets were missed.
• Hardware failure—Indicates a card diagnostic failure during:
- System boot
- Card initialization
- Manual diagnostics
- Transceiver test
• PBUS checksum—Fabric checksum error detected for:
- Data traffic, [INT] or [EXT]
- CPU-bound traffic [CPU}
- EDP packets [EDP]
31) used by the interpreting and reporting subsystem are
Health Check Messages
35