Troubleshooting guide

Extreme Networks’ Recommendations
Advanced System Diagnostics and Troubleshooting Guide 107
Extreme Networks’ Recommendations
Extreme Networks strongly recommends that you observe the process shown in Figure 11 and outlined
in the steps that follow when dealing with checksum errors.
Figure 11: Diagnostic Troubleshooting Process
1 Is the checksum error a hard error?
The first occurrence of a checksum error doesn’t determine whether the error is a hard error or a soft
error. If the error is persistent (doesn’t disappear after a reboot) and is accompanied by continuous
and consistent checksum error messages in the system log, it might be a temporary hard error.
If any hardware has been changed recently, and this switch is a modular chassis, try reseating the
affected blade.
CG_003
Customer experiences
checksum errors on
Inferno/Triumph
products.
No
No
No No
Yes Yes
Yes
Yes
Call TAC. Next action
will be determined on the
error frequency and
problem details.
Monitor closely.
No action
needed.
Errors will be
mapped out. No further
action needed.
Product
replaced.
Are these
hard errors?
Is
Extremeware
Software version
6.2.2 or higher?
Are
errors detected by
packet memory scan/
extended diags?
Are
errors recoverable?
Run extended diags/
packet memory scan.
Call TAC. Product
needs to be replaced.
TAC creates RMA.
Upgrade to latest EW
and use the packet
memory scan software
to detect and remap
the errors.
Customer
responsibility
TAC
responsibility