Users Guide

Automation and Event Processing Rules | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 319
For example, you can retrieve the following attributes:
{RedCell.Config.EquipmentManager_Custom1}
{RedCell.Config.EquipmentManager_Custom2}
{RedCell.Config.EquipmentManager_LastBackup}
{RedCell.Config.EquipmentManager_LastConfigChange} and
{RedCell.Config.EquipmentManager_HealthStatus}
NOTE:
If the entity does not contain/return these values, then the message [No data for <attribute name>]
appears in the email instead.
Best practice is to clarify such attributes by combining them with others that spell out their source.
Basic Variables
Here is a description of the basic variables:
Managed Equipment Variables
Here is a description of the managed equipment variables. These variables may have a performance
impact
Attribute Description Email Action Variable
Name The event/alarm name {Name}
Message Description from the event {Message}
Entity Name The entity (interface, card...) name {EntityName}
Equipment Manager
Name
The name of the equipment, parent or
chassis.
{EquipMgrName}
Device IP address the IP of the device in alarm {DeviceIP}
Entity Type Type of entity (Router, and so on) {EntityType}
Instance ID An identifier for the event {InstanceID}
Protocol Type Of originating alarm (SNMP, syslog,
etc.)
{ProtocolType}
Protocol Sub Type Inform, Trap, [blank] (for internal
events)
{ProtocolSubType}
Receive Time {RecvTime}
Region The mediation server partition name. {Region}
Severity 0 - cleared, through 6 - critical, from
Alarm Definition
{Severity}
Source IP address The IP of the component sending the
alarm
{SourceIP}
Attribute Description Email Action Variable
Custom 1 Note that although you can re-name
any Custom attribute, you must use
the variable’s original name. For
example here, that is
{RedCell.Config.EquipmentManager
_Custom1}
{RedCell.Config.EquipmentManager
_Custom1}