Extreme Networks ExtremeWare Version 7.8 Troubleshooting Manual page 81

• CPU health check failures might indicate a faulty transceiver on one of the MSMs, but might also
indicate other I/O control bus failures. Always use log messages in conjunction with the output of
the
show diagnostics
• If a health check checksum error message appears in the log, and the output of the
show diagnostics
use those two sources of information to determine the location of the problem.
• If backplane health check counts for missing or corrupted packets are increasing, but the log shows
no checksum error messages, the problem is probably a low-risk, transient problem—possibly a busy
CPU.
• If the log shows checksum error messages and the backplane health check counts for missing or
corrupted packets are increasing:
— Live data is probably being disrupted.
— The combination of the health check counters in the output of the
and the checksum message information in the log can help isolate the faulty module.
— Examine which modules are reporting CPU health check counters in the output of the
show diagnostics
only one module is reporting errors, the I/O module is probably faulty.
• If the backplane health check shows no failures, but the log shows checksum error messages:
— If the checksum error messages occur infrequently, it might indicate a packet memory problem
that is being triggered sporadically; it might be a low-risk situation, but—if possible—you should
run the packet memory scan.
— If the checksum error messages occur frequently, user data is probably being affected; run the
packet memory scan as soon as possible.
Advanced System Diagnostics and Troubleshooting Guide
command.
command shows excessive backplane health check error counts, you can usually
command. If many modules are reporting errors, the MSM might be faulty; if
System (CPU and Backplane) Health Check
command
show diagnostics
81