Dell PowerEdge XL 5133-4 MXL 10/40GbE Switch IO Module FTOS Command Reference - Page 264
Offline Diagnostics, Important Points to Remember
View all Dell PowerEdge XL 5133-4 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 264 highlights
www.dell.com | support.dell.com Offline Diagnostics The offline 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 verifications. In addition, they verify the identification 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, they perform extensive tests on memory devices (for example, SDRAM, flash, 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, and 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) configurations. 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 offline diagnostics on an offline standalone unit. You cannot perform diagnostics if the ports are configured 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 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, follow these steps: 1. Place the unit in the offline state using the offline stack-unit command from EXEC Privilege mode (Figure 22-3). The system reboots when the off-line diagnostics complete. This is an automatic process. A 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 250 | Debugging and Diagnostics