Filter
Top Products
50 MPCMM0001 Chassis Management Module Software Technical Product Specification
Process Monitoring and Integrity
6.7.7 Excessive Restarts, Escalate No Action
In this scenario PMS detects a process fault. The configured recovery action is: restart the process.
However, the PMS also detects that the process has exceeded the threshold for excessive process
restarts. Therefore, the PMS will execute the escalation action. The escalation action is configured
for no action.
Table 11. Failed Failover/Reboot Recovery, Critical
Description Event String UID Assert Severity
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.
Process existence fault;
attempting recovery or
Thread watchdog fault; attempting
recovery or
Process integrity fault; attempting
recovery
# Assert Configure
The recovery action specified is
"failover & reboot"
Attempting failover & reboot
recovery action
# N/A Configure
PMS executes a failover.
The existing code generates the
events for failover. They are
separate from process monitoring
events and are not described
here.
-N/A N/A
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.
Monitoring initialized # De-assert OK
Table 12. Existence Fault, Excessive Restarts, Escalate No Action (Sheet 1 of 2)
Description Event String UID Assert Severity
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.
Process existence fault;
attempting recovery or
Thread watchdog fault; attempting
recovery or
Process integrity fault; attempting
recovery
# Assert Configure
The recovery action specified is
"process restart"
Attempting process restart
recovery action
# N/A Configure