Extreme 3804 Supplementary Manual
100
Advanced System Diagnostics and Troubleshooting Guide
Troubleshooting Guidelines
2
Did the problem go away?
If it did, monitor the operation of the switch, but no immediate action is required.
If it did not disappear, it is probably a permanent hard error, is service-affecting, and must be dealt
with immediately by running the ExtremeWare extended diagnostics (including the packet memory
scan).
with immediately by running the ExtremeWare extended diagnostics (including the packet memory
scan).
3
Because the extended diagnostics require down time, schedule an appropriate maintenance window
to minimize the impact on the rest of the network.
to minimize the impact on the rest of the network.
4
If the switch is not currently running the latest version of ExtremeWare 6.2.2 software (Version
6.2.2b134 or higher), the switch software should be upgraded to gain availability to the latest
ExtremeWare diagnostics.
6.2.2b134 or higher), the switch software should be upgraded to gain availability to the latest
ExtremeWare diagnostics.
5
Isolate the target switches, either physically or logically, from the network while the diagnostics are
being run because of the high CPU utilization of the diagnostics. Isolating the core switches ensures
that various network features converge properly.
being run because of the high CPU utilization of the diagnostics. Isolating the core switches ensures
that various network features converge properly.
6
Run the extended diagnostics in manual mode (which automatically invokes the packet memory
scan).
scan).
In addition to the extended diagnostics, you should also run the transceiver diagnostics and FDB
scan diagnostics within this same maintenance window, because run together these tests can detect
not only problems with the packet memory, but also any other problems within the system.
scan diagnostics within this same maintenance window, because run together these tests can detect
not only problems with the packet memory, but also any other problems within the system.
If possible, perform memory scanning while actual fabric checksums are being reported in the log.
Although this is not an absolute requirement (and is—in fact—not a factor in the actual memory
scan), by executing manual memory scanning while there are checksum errors occurring provides
the best correlation between this diagnostic and the actual event.
Although this is not an absolute requirement (and is—in fact—not a factor in the actual memory
scan), by executing manual memory scanning while there are checksum errors occurring provides
the best correlation between this diagnostic and the actual event.
NOTE
For fully-redundant systems (for example, when ESRP has been enabled), the system health
checker can be run in automatic (auto-recovery) mode.
checker can be run in automatic (auto-recovery) mode.
Did the extended diagnostics (plus the packet memory scan) detect errors?
•
If no errors were detected, you should call the Extreme Networks TAC. The next action will be
determined by the frequency with which the error occurs and other problem details.
determined by the frequency with which the error occurs and other problem details.
•
If errors were detected, were the errors recoverable (mapped out of use)?
—
If they were, no further action is required.
—
If they were not mapped out of use, call the Extreme Networks TAC. The product must be
replaced. TAC will initiate the RMA process.
replaced. TAC will initiate the RMA process.