On-Demand Diagnostics; High Availability - Cisco Nexus 7000 Series Configuration Manual

On-Demand Diagnostics

• StandbyFabricLoopback test
The recovery actions feature is disabled by default. With this feature you can configure the system to take
disruptive action as a result of repeated failures on the health-monitoring, or runtime, tests. This feature enables
or disables the corrective, conservative action on all four tests, simultaneously; the corrective action taken
differs for each test. After crossing the maximum consecutive failure count for that test, the system takes
corrective action.
With the recovery actions feature enabled, he corrective action for each test is as follows:
• PortLoopback test—The system moves the port registering faults to an error-disabled state.
• RewriteEngineLookpback test—The system takes different corrective action depending on whether the
• SnakeLoopback test—After the test detects 10 consecutive failures with any port on the module, the
• StandbyFabricLoopback test—The system attempts to reload the standby supervisor three times after it
Finally, the system maintains a history of the recovery actions that includes details of each action, the testing
type, and the severity. You can display these counters.
On-Demand Diagnostics
On-demand tests help localize faults and are usually needed in one of the following situations:
• To respond to an event that has occurred, such as isolating a fault.
• In anticipation of an event that may occur, such as a resource exceeding its utilization limit.
You can run all the health monitoring tests on demand. You can schedule on-demand diagnostics to run
immediately.
You can also modify the default interval for a health monitoring test.

High Availability

A key part of high availability is detecting hardware failures and taking corrective action while the device
runs in a live network. Online diagnostics in high availability detect hardware failures and provide feedback
to high availability software components to make switchover decisions.
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
228
fault is with the supervisor, the fabric, or the port, as follows:
• On a chassis with a standby supervisor, when the system detects a fault with the supervisor, the
system switches over to the standby supervisor. If there is no standby supervisor in the chassis,
the system does not take any action.
• After failures on the fabric, the system will reload the fabric 3 times. If failure persists, the system
powers down the fabric.
• After the failures on a port, the system moves the faulty port to the error-disabled state.
system will move the faulty port to an error-disabled state.
receives errors on this test. If the system cannot reload the standby supervisor, the system powers off
the supervisor.
Configuring Online Diagnostics