nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

4) USB---------------------------> .
5) CryptoDevice------------------> .
6) NVRAM-------------------------> .
7) RealTimeClock-----------------> .
8) PrimaryBootROM----------------> .
9) SecondaryBootROM--------------> .
10) CompactFlash------------------> .
11) ExternalCompactFlash----------> .
12) PwrMgmtBus--------------------> .
13) SpineControlBus---------------> .
14) SystemMgmtBus-----------------> .
15) StatusBus---------------------> .
16) StandbyFabricLoopback---------> U
Congo#
Referring to the output of Example 6-11, all tests that were run against the module in
question passed diagnostics as denoted with a period. Should a particular test fail, further
investigation might be required. The Cisco Technical Assistance Center (TAC) can use this
information to replace modules that are covered under support agreements.
NX-OS High-Availability Architecture
The high-availability features of NX-OS are managed by several system-level processes:
• System Manager: At the highest level, the System Manager is responsible for the
overall state of the system. The System Manager monitors the health of the system and
the various services that are running based on the configured high-availability
policies. The System Manager manages the starting, stopping, monitoring, and
restarting of services. Along with these high-level tasks, the System Manager also
ensures that state is synchronized between supervisors and coordinates the switchover
of supervisors if necessary. To verify the health of the System Manager process, there
is a hardware watchdog timer located on the supervisor. Periodically, the System
Manager resets the watchdog timer with a keepalive indicator. If the hardware
watchdog timer expires, with no keepalives from the System Manager, a supervisor
switchover occurs.
• Persistent Storage Service (PSS): Where state information for the various services
are stored. PSS provides a database of state and runtime information. Services within
NX-OS dump information to the PSS at various intervals and after restart glean this
information from the PSS to restore the service to prefailure state.
• Message and transaction services (MTS): An interprocess communication (IPC)
broker that handles message routing and queuing between services and hardware
within the system. The function of the MTS ensures that processes can be restarted
independently and that messages from the other processes are received after a restart
has occurred.