The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure the generic online diagnostics (GOLD) feature. It contains the following sections:
Online diagnostics provide verification of hardware components during switch bootup or reset, and they monitor the health of the hardware during normal switch operation.
Cisco Nexus 5000 Series switches support bootup diagnostics and runtime diagnostics. Bootup diagnostics include disruptive tests and nondisruptive tests that run during system bootup and system reset.
Runtime diagnostics (also known as health monitoring diagnostics) include nondisruptive tests that run in the background during normal operation of the switch.
Bootup diagnostics detect faulty hardware before bringing the switch online. Bootup diagnostics also check the data path and control path connectivity between the supervisor and the ASICs. The following table describes the diagnostics that are run only during switch bootup or reset.
Diagnostic |
Description |
---|---|
PCIe |
Tests PCI express (PCIe) access. |
NVRAM |
Verifies the integrity of the NVRAM. |
In band port |
Tests connectivity of the inband port to the supervisor. |
Management port |
Tests the management port. |
Memory |
Verifies the integrity of the DRAM. |
Bootup diagnostics also include a set of tests that are common with health monitoring diagnostics.
Bootup diagnostics log any failures to the onboard failure logging (OBFL) system. Failures also trigger an LED display to indicate diagnostic test states (on, off, pass, or fail).
You can configure Cisco Nexus 5000 Series switches to either bypass the bootup diagnostics, or run the complete set of bootup diagnostics.
Health monitoring diagnostics provide information about the health of the switch. They detect runtime hardware errors, memory errors, software faults, and resource exhaustion.
Health monitoring diagnostics are nondisruptive and run in the background to ensure the health of a switch that is processing live network traffic.
The following table describes the health monitoring diagnostics for the switch.
Diagnostic |
Description |
---|---|
LED |
Monitors port and system status LEDs. |
Power Supply |
Monitors the power supply health state. |
Temperature Sensor |
Monitors temperature sensor readings. |
Test Fan |
Monitors fan speed and fan control. |
The following table describes the health monitoring diagnostics that also run during system boot or system reset.
Diagnostic |
Description |
---|---|
SPROM |
Verifies the integrity of backplane and supervisor SPROMs. |
Fabric engine |
Tests the switch fabric ASICs. |
Fabric port |
Tests the ports on the switch fabric ASIC. |
Forwarding engine |
Tests the forwarding engine ASICs. |
Forwarding engine port |
Tests the ports on the forwarding engine ASICs. |
Front port |
Tests the components (such as PHY and MAC) on the front ports. |
During switch bootup or reset, the bootup diagnostics include tests for the in-service expansion modules in the switch.
When you insert an expansion module into a running switch, a set of diagnostics tests are run. The following table describes the bootup diagnostics for an expansion module. These tests are common with the bootup diagnostics. If the bootup diagnostics fail, the expansion module is not placed into service.
Diagnostic |
Description |
---|---|
SPROM |
Verifies the integrity of backplane and supervisor SPROMs. |
Fabric engine |
Tests the switch fabric ASICs. |
Fabric port |
Tests the ports on the switch fabric ASIC. |
Forwarding engine |
Tests the forwarding engine ASICs. |
Forwarding engine port |
Tests the ports on the forwarding engine ASICs. |
Front port |
Tests the components (such as PHY and MAC) on the front ports. |
Health monitoring diagnostics are run on in-service expansion modules. The following table describes the additional tests that are specific to health monitoring diagnostics for expansion modules.
Diagnostic |
Description |
---|---|
LED |
Monitors port and system status LEDs. |
Temperature Sensor |
Monitors temperature sensor readings. |
You can configure the bootup diagnostics to run the complete set of tests, or you can bypass all bootup diagnostic tests for a faster module boot up time.
Note |
We recommend that you set the bootup online diagnostics level to complete. We do not recommend bypassing the bootup online diagnostics. |
2.
switch(config)# diagnostic bootup level [complete | bypass]
3.
(Optional) switch# show diagnostic bootup level
The following example shows how to configure the bootup diagnostics level to trigger the complete diagnostics:
switch# configure terminal
switch(config)# diagnostic bootup level complete
To display online diagnostics configuration information, perform one of the following tasks:
Command |
Purpose |
---|---|
show diagnostic bootup level | Displays the bootup diagnostics level. |
show diagnostic result module slot | Displays the results of the diagnostics tests. |
The following table lists the default settings for online diagnostics parameters.
Parameters |
Default |
---|---|
Bootup diagnostics level |
complete |