Users Guide

Alarms | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 291
Here are a few things you need to know about alarm correlation state:
• Alarm Processing Effects
An alarm’s correlation state does not affect alarm processing behavior. So if a clearing event
enters OpenManage Network Manager, the open alarm clears regardless of its correlation
state. Event counts also continue to increase as duplicate events arrive.
• Default Filtering
By default, all alarm filters exclude child alarms. A filter criteria (
Include child alarms ) can
include child alarms, so you can always see all alarms regardless of their correlation state by
selecting the
Include child alarms attribute within the expanded alarms portlet and setting
the search criteria to
Is true .
• Additional Alarm Attributes
The following attributes reflect the correlation state for an alarm. When another alarm
conceals the child alarm (or blocks it), it sets the following too.
• Correlated By: User who created the correlation
• Correlation Date: Date the correlation was created
• Correlation State: CausedBy or BlockedBy
• Parent Alarm
• Has Children: Whether the alarm has children
Alarm Email
The e-mail sent by right-clicking an alarm has the subject specified when you send it, and contains
the information within the alarm. For example:
Alarm: monitorIntervalSkip
Alarm Attributes:
===============================
Device IP =
Message =
Alarm State = Open
Severity = 5 - Major
Count = 1
Date Opened = Tue Dec 14 22:01:30 PST 2010
Update Date/Time = Tue Dec 14 22:01:36 PST 2010
Entity Name =
Entity Type =
Entity Description =
Equipment =
Region = SUPDEMOPartition
Location =
Assigned By = OWSystem
Date Assigned = Thu Dec 16 10:40:24 PST 2010
Assigned User = qatester
Acknowledged = false
Ack By =