Users Guide

• Perform offline diagnostics on one stack member at a time.
• Diagnostics only test connectivity, not the entire data path.
• Diagnostic results are stored on the flash of the unit on which you performed the diagnostics.
• When offline diagnostics are complete, the unit or stack member reboots automatically.
Running Offline Diagnostics
To run offline diagnostics, use the following commands.
For more information, refer to the examples following the steps.
1 Place the unit in the offline state.
EXEC Privilege mode
offline stack-unit
You cannot enter this command on a MASTER or Standby stack unit.
NOTE: The system reboots when the offline diagnostics complete. This is an automatic process. The
following warning message appears when you implement the offline stack-unit command:
Warning - Diagnostic execution will cause stack-unit to reboot after
completion of diags. Proceed with Offline-Diags [confirm yes/no]:y
After the system goes offline, you must reload or execute the online stack-unit <id> command for the
normal operation.
2 Confirm the offline status.
EXEC Privilege mode
show system brief
3 Start diagnostics on the unit.
diag
When the tests are complete, the system displays the following message and automatically reboots the
unit.
Diagnostic results are printed to a file in the flash using the filename format TestReport-SU-<stack-unit-
id>.txt.
Log messages differ somewhat when diagnostics are done on a standalone unit and on a stack member.
4 View the results of the diagnostic tests.
EXEC Privilege mode
show file flash://
Examples of the Diagnostics Commands
The following is an example of taking a stack unit offline.
Dell#offline stack-unit 2
Warning - offline of stack unit will bring down all the protocols and
the unit will be operationally down, except for running Diagnostics.
S5000 Debugging and Diagnostics 1232