Filter
Top Products
MPCMM0001 Chassis Management Module Software Technical Product Specification 45
Process Monitoring and Integrity
ProcessSeverity=3
Note: The recovery action and escalation action should not be set to "no action" for the xinetd process.
This process is involved in data synchronization between the CMMs.
Note: When a user tries to change the recovery action for cmd_hand or BPM to values other than allowed
via the CLI API, the error string displayed is:
"Recovery action not allowed for this target."
6.7 Failure Scenarios and Eventing
This section describes the process fault scenarios that are detected and handled by the PMS. It also
describes the eventing that is associated with the detection and recovery mechanisms. Each
scenario contains a brief textual description and a table that further describes the scenario.
In the table, the Description column outlines the current action. The Event Type String defines the
text for the event that is written to the SEL. The text in this field describes the portion of the event
containing event-specific string (the remainder of the event text is standard for all events).
However, for PMS the target name (sensor name) will be PmsProc<#> instead of the name of the
sensor (where # is the unique identifier of the given process).
The UID indicates the unique identifier for the process causing the event. An ID of 1 indicates the
monitoring service itself (global) and an ID of # indicates an application process.
The Assert column indicates if the event is asserted or de-asserted. For items that are just written to
the SEL for informational purposes, the assertion state is not applicable. However, it is required by
the interface and therefore it will be set to de-assert.
The Severity column will define the severity of the event. A severity of Configure indicates that the
severity is configurable. The configurable severities are available in the Configuration Database.
The remaining columns (SNMP traps, health events, LEDs, and telecommunication alarms) define
what indicator will be triggered by the event.
6.7.1 No Action Recovery
In this scenario PMS detects a process fault. The PMS is configured to take no action and therefore
disables monitoring of the process.