Recovery Actions For Specified Health-Monitoring Diagnostics - Cisco Nexus 7000 Series Configuration Manual

Configuring Online Diagnostics
Test Name
SpineControlBus
SystemMgmtBus
StatusBus
StandbyFabricLoopback
PCIeBus

Recovery Actions for Specified Health-Monitoring Diagnostics

Before Cisco NX-OS Release 6.2(8), runtime tests did not take corrective recovery actions when they detected
a hardware failure. The default action through EEM included generating alerts (callhome, syslog) and logging
(OBFL, exception logs). These actions are informative, but they did not remove faulty devices from the
network, which can lead to network disruption, traffic black holing, and so forth. Before Cisco NX-OS Release
6.2(8), you must manually shut the devices to recover the network.
In Cisco NX-OS Release 6.2(8) and later releases, you can configure the system to take disruptive action if
the system detects failure on one of the following runtime, or health-monitoring, tests:
• PortLoopback test
• RewriteEngineLoopback test
• SnakeLoopback test
Description Default Interval
Verifies the 30 sec
availability of the
standby spine
module control
bus.
Verifies the 30 sec
availability of the
standby system
management bus.
Verifies the status 30 sec
transmitted by the
status bus for the
supervisor,
modules, and
fabric cards.
Verifies the 30 sec
connectivity of the
standby supervisor
to the crossbars on
the spine card.
Verifies PCIe 30 sec
connectivity from
the supervisor to
the crossbar
ASICs on the
fabric cards.
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
Recovery Actions for Specified Health-Monitoring Diagnostics
Supported Supervisors
Sup1 and Sup2
Sup1, Sup2, and Sup2E
Sup1, Sup2, and Sup2E
Sup1, Sup2, and Sup2E
Sup2 and Sup2E
Unsupported
Supervisors
Sup2E
—
—
—
—
227