Users Guide
Event Definitions | Alarms, Events, and Automation
332 OMNM 6.5.3 User Guide
Event Definitions
You can define how the OpenManage Network Manager application treats notifications (events)
coming into the system. Administrators define event behavior deciding whether it is suppressed,
rejected, or generates an Alarm. Manage the definitions of events from this portlet.
By default, this portlet is accessed by selecting Settings > Alarm Definitions from the navigation
bar.
From this portlet, you can configure events that, when correlated as described in
Automation and
Event Processing Rules
on page 297, trigger actions.
Columns include the
MIB Name, Event Name, Notification OID, Severity
for associated alarms
,
and
Default Behavior.
Alter these settings from the
Event Definition Editor
. Right-click a selected
event definition for the following menu items:
Edit
—Open the selected event definition in the
Event Definition Editor
.
Set Behavior
—This lets you select from the following options
:
• Reject–Every received message is rejected.
• Suppress–The message is tracked in Event History and then ignored.
• Alarm–The message is tracked in Event History and then processed through the alarm
life cycle, which might create a new alarm, increment an existing alarm, or clear an
existing alarm.
Set Severity
—Set the alarm severity for the selected event, or select the Cleard option.
MIB
—This lets you upload a new MIB to your event definitions.
Import/Export—
Export the selected config file to disk, or import it from disk. You can also import/
export a selected configuration file.
Provides the following actions when available for the selected image:
• Import retrieves a file containing XML compliance descriptions. Some imports can
come from a URL.
• Export Selection exports the selected description to an XML file.
• Export All exports all descriptions to an XML file.
Click Download Export File to specify where to save the file.
The Import/Export option is useful as a backup or to share descriptors with other projects.
You must import data into the correct portlet. For example, you cannot import event data
into the Actions portlet.
If one type of data depends on another, you must import the other data before importing the
data that depends on it.