Process Administrative Action; Excessive Restarts, Failed Escalate Failover/Reboot, Critical; Administrative Action - Intel NetStructure MPCMM0001 Software Instructions

recovery action is unsuccessful (standby is not available, etc.). The process being monitored is of
critical severity and therefore the reboot of the CMM will still be executed even though the CMM
is still active.
Table 15. Excessive Restarts, Failed Escalate Failover/Reboot, Critical
PMS detects a faulty process. The
mechanism (existence, thread
watchdog, or integrity) used to detect
the fault will determine which of the
event type strings will be used.
The recovery action specified is
"restart process"
PMS detects that the process has
been restarted excessively.
The escalated recovery action
specified is "failover and reboot"
PMS executes a failover.
PMS detects that it is still running on
the active CMM. The process is
critical and therefore the reboot
operation is performed.
Upon initialization of PMS after the
reboot. The monitor will de-assert the
event.
6.7.11

Process Administrative Action

In this scenario, PMS has detected a fault in a process, but has not been able to recover the process
(recovery is configured for no action, etc.). This causes PMS to operationally disable monitoring of
the process. To re-enable monitoring of the process, an operator must administratively lock the
process, take the necessary actions to fix the process, and administratively unlock the process.
Table 16. Administrative Action
Operator administratively locks
monitoring of the process
Operator takes actions to fix the
problem
Operator administratively unlocks
monitoring of the process causing
monitoring to restart
MPCMM0001 Chassis Management Module Software Technical Product Specification
Download from Www.Somanuals.com. All Manuals Search And Download.
Description
Process existence fault;
attempting recovery or
Thread watchdog fault; attempting
recovery or
Process integrity fault; attempting
recovery
Attempting process restart
recovery action
Recovery failure due to excessive
restarts
Attempting failover & reboot
escalated recovery action
The existing code generates the
events for failover. They are
separate from process monitoring
events and are not described
here.
Monitoring initialized
Description
None
N/A
Monitoring initialized
Process Monitoring and Integrity
Event String UID
#
#
#
#
-
#
Event String UID
-
-
#
Assert Severity
Assert Configure
N/A Configure
N/A Configure
N/A Configure
N/A N/A
De-assert OK
Assert Severity
N/A N/A
N/A N/A
De-assert OK
53