Administrator Guide

13
Debugging and Diagnostics
This chapter describes debugging and diagnostics for the MXL switch.
Oine Diagnostics
The oine diagnostics test suite is useful for isolating faults and debugging hardware.
The diagnostics tests are grouped into three levels:
• Level 0 — Level 0 diagnostics check for the presence of various components and perform essential path verications. In
addition, Level 0 diagnostics verify the identication registers of the components on the board.
• Level 1 — A smaller set of diagnostic tests. Level 1 diagnostics perform status, self-test, access, and read-write tests for all the
components on the board and test their registers for appropriate values. In addition, Level 1 diagnostics perform extensive tests
on memory devices (for example, SDRAM, ash, NVRAM, EEPROM) wherever possible.
• Level 2 — The full set of diagnostic tests. Level 2 diagnostics are used primarily for on-board MAC level, Physical level, external
Loopback tests, and more extensive component diagnostics. Various components on the board are put into Loopback mode and
test packets are transmitted through those components. These diagnostics also perform snake tests using virtual local area
network (VLAN) congurations.
NOTE: Diagnostic is not allowed in Stacking mode, including member stacking. Avoid stacking before executing the
diagnostic tests in the chassis.
Important Points to Remember
• You can only perform oine diagnostics on an oine standalone unit. You cannot perform diagnostics if the ports are congured
in a stacking group. Remove the port(s) from the stacking group before executing the diagnostic test.
• Diagnostics only test connectivity, not the entire data path.
• Diagnostic results are stored on the ash of the unit on which you performed the diagnostics.
• When oine diagnostics are complete, the unit or stack member reboots automatically.
Running Oine Diagnostics
To run oine diagnostics, use the following commands.
For more information, refer to the examples following the steps.
1. Place the unit in the oine state.
EXEC Privilege mode
offline stack-unit <id>
You cannot enter this command on a MASTER or Standby stack unit.
NOTE: The system reboots when the oine diagnostics complete. This is an automatic process. The following
warning message appears when you implement the offline stack-unit <id> command: Warning -
Diagnostic execution will cause stack-unit to reboot after completion of diags.
Proceed with Offline-Diags [confirm yes/no]:y
Dell#offline stack-unit 0
Warning - offline of unit will bring down all the protocols and
252
Debugging and Diagnostics