HP NonStop G-Series - Manual (Page 121)

Appendix L: EMS Burst Suppression 121
Reset
This is used to define when the burst should be considered as expired. Once a burst has been detected,
no more EMS messages will be processed until after the amount of time defined in this field. The start of
the burst will be defined as the EMS generation time of the first EMS message that is part of the burst
criteria. So if the burst is defined as 5 messages in 5 minutes, the reset time is defined as 30 minutes,
and the very first EMS message is generated at 12:00, 2 more at 12:02 and 2 more at 12:03 (5
total), the reset time will be at 12:30 – 30 minutes after the first message that was part of the burst
criteria. Using the same burst criteria, if a message was consumed at 12:00, 12:01, 12:02, 12:04,
12:06, 12:08, 12:09; 12:10: 12:10, then the first message that is part of the burst will be at 12:06,
the burst detected message would be generated at 12:10 (the second 12:10) and the burst will be
‘over’ at 12:36.
Generate start/end EMS burst notification messages
If this check box is checked, then both ACC ($OVOCC) and EMON ($OVEMN) will generate EMS
messages when they detect a new burst and when the burst expires. If this box is not checked, then
these messages will not be generated by OVNM.
4. OVNM Level Burst Suppression
If neither of the Collector and EMS distributor level EMS burst suppression methods work in your
environment, you have the option of suppressing duplicate events within OVNM. OVNM has two processes
that consume events. The $OVOCC process consumes events for EMS thresholds and to generate Emails
and perform automated recovery actions. EMON consumes events to send them to HPOM. You have the
option of configuring EMS burst suppression for both sides of OVNM independently. The burst suppression
can be identical for both sides, or unique for each side based on your requirements. For more information
about this feature, review the SAMPSUPR (Sample Suppression Configuration file) on HP NonStop.