KBI 310565 Issue Addressed: Motor Offline System Event Is Regularly Posted On Busy Motors
Argent AT — all versions
Tue, 25 Jun 2013
Customer is running Argent AT in Non-Stop Motor Architecture and is regularly getting System Events indicating Motor is found offline.
System Event is controlled by options under Supervising Engine Manager, it is under
Control Information > Administration > Engine Manager > Supervising Engine
In Argent Defender, it is under
Control Information > Administration > Engine Manager > Argent Defender
There are four check boxes to enable/ disable System Events, as following print screen
Each Motor will give a “Heartbeat” and the record is updated in the “Virtual Server” Table for EACH product, for example Argent for SNMP, the Table name is “ARGSOFT_SN_VIRTUAL_SERVER”
A default “Heartbeat” latency alert threshold is 300 seconds. For a busy Motor, the interval of “Heartbeat” may exceed 300 seconds, therefore System Event is posted.
The default “Heartbeat” latency alerting is controlled by registry key. Non-Stop Motors synchronize their registry key by reading Argent Database.
“CONFIGURATION” Table can be found in the Argent Database for EACH product, for example Argent for SNMP, the Table name is ARGSOFT_SN_CONFIGURATION
The controlling “KEY_NAME” is “ALLOWED_DEAD_MOTOR_LAPSE”, and the value is in unit of second. Desirable value is 300 – 900.
If the “Heartbeat” update latency is way beyond the threshold, please contact Argent Support for investigation.