Generate alarms
- Last UpdatedJul 29, 2024
- 2 minute read
When failover conditions occur, Application Server reports alarms to subscribed alarm clients like InTouch.
These alarms contain the following information:
-
The name of the AppEngine reporting the alarm.
-
The node name of the AppEngine reporting the alarm.
-
The state of the AppEngine.
-
The node name of the AppEngine’s partner object.
Depending on what caused the failover, the Standby AppEngine can become the Active AppEngine in an Off scan state and alarms might not be generated.
If the Active AppEngine is shutdown off scan, the checkpointer can transfer that state to the Standby. When the Standby becomes the Active, it starts off scan. When the AppEngine is put on scan, alarms then are generated.
Reported alarms include the following:
|
Alarm |
Previous state |
Current state |
Alarm raised when |
Alarm Cleared when |
Alarm reported by |
|---|---|---|---|---|---|
|
Standby Not Ready * |
Active |
Standby Not Ready |
Standby Not Ready |
Entering Stacdby Ready |
Active Engine |
|
Standby Not Available |
Active |
Active Standby Not Available |
Active Standby Not Available |
Entering Active |
Active Engine |
|
Failover Occurred |
Standby becomes Active |
During the next scan of the Active engine |
Active Engine |
||
|
* The Active AppEngine monitors the status of the Standby through the RMC to determine when to raise this alarm. Also, if the Active AppEngine is in Active-Standby not Available state, this alarm is not generated. |
|||||
When a failover occurs, the Standby AppEngine that becomes active carries alarms outstanding from the old Active AppEngine. The state of those old alarms, though, will change to reflect the new partner's status.
Timestamps are preserved for alarms, including when:
-
The alarm was acknowledged
-
The alarm condition went true
-
The alarm condition went false
Finally, the following information is preserved for alarms:
-
An alarm was acknowledged
-
The message input by the operator when the alarm was acknowledged
All alarm state information is collected and sent to the Standby AppEngine at the end of a scan cycle and before being sent to alarm clients.
The sequence of reporting alarms ensures that alarm clients do not report alarms in states that are different from those reported by the Standby AppEngine if the Active AppEngine fails.