Diagnostic Troubleshooting - Extreme Networks ExtremeWare Version 7.8 Troubleshooting Manual

Troubleshooting Guidelines

Diagnostic Troubleshooting

For "i" series switches, observe the following troubleshooting guidelines:
• If there are no checksum errors appearing in the system log, but the health check counts for missing
or corrupted packets are increasing, it is probably a transient problem, of low risk (possibly a busy
CPU).
• If the log shows checksum error messages, and the system health check counters for missing or
corrupted packets are increasing:
— Live data is being probably being disrupted.
— The combination of the health check counters in the output of the
and the checksum messages in the log can help isolate the faulty module.
— Compare with CPU health check information from
error might be occurring on the CPU data path and not on the backplane (in which case user
traffic would be largely unaffected, but protocol traffic could be having problems).
— If errors are frequent, user data is probably affected; run the packet memory scan as soon as
possible
• If system health check shows no failures, but the log shows checksum errors:
— If the checksum errors 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 errors occur frequently, user data is probably being affected; run the packet
memory scan as soon as possible.
• In the output from the
indicates that a problem has been detected with FDB memory. FDB scan attempts to map the error
location so that it will not be used. If the location is in use and the entry cannot be safely removed,
FDB scan will mark it as suspect (suspect entries are marked with an "S"). Look at the output of the
command. Address suspect entries by manually removing the entries and
show fdb remap
re-adding them. Consult Extreme Networks TAC if this is not possible.
• In the output from the
incrementing, it might indicate a transceiver problem.
— If there is no associated log message, then the problem is probably a transient problem and
requires no action.
— If there is a log message, then there is most likely an issue that needs to be addressed. Use the log
message and the output of the
106
command, if FDB scan error counters are non-zero, it
show diagnostics
command, if transceiver test error counters are
show diagnostics
show diagnostic
show diagnostics
command; the packet
show diagnostics
command to isolate the problem.
Advanced System Diagnostics and Troubleshooting Guide
command