How Stuff Works > Alert Generation

Alert Generation

Tags:  

Alarm Generation

Alarms are of different types. They are:
  • Status poll alarms (if any device/interface/port/service goes down)
  • Threshold alarms
  • Alarms from SNMP traps
  • Windows eventlog alarms
Alarms have various status levels which indicate the severity of the failure. The various status levels are  Attention, Trouble, Critical, Down & Clear.



If any device is down for the first ping check, then an alarm with severity Attention is created. If it is still down for the second ping check, then the same alarm with the same severity is maintained. If the same situation continues for the third ping check, then the status is changed to Trouble. If is down for the fourth ping check, then the severity is kept unchanged. If the same situation continues for the fifth ping check, then the status is changed to Critical. The same procedure is followed when the interfaces/ports go down during the polls. But, if a service goes down, then a Service Down alarm alarm is raised. Even if the service is down for the subsequent polls, the same status (Down) is maintained.



However, for alarms that are raised by threshold violations, the alarms generation process is slightly different. The threshold alarms are raised with the severity what you have selected while configuring the threshold settings.

If any notification profile is associated to the devices, then a notification is sent for when the first alarm with severity Attention is sent. In the case of threshold alerts a notification is sent when the first alarm with the configured severity. In the case of services, a notification with severity Down is sent. But for all the cases, no notification will be sent if the alarm changes it severity. If the device/interface/service is up again or the the threshold is satisfied, then the severity of the alarm changes to Clear. Now a notification will be sent indicating that the alarm has been cleared.





 RSS of this page

rtttrrb