Each notification has a unique name. A notification’s name consists of the class name and instance name where the event occurred, and the event name. The notification naming convention is:
NOTIFICATION-ClassName_InstanceName_EventName
For example, the notification NOTIFICATION-Router_R1_Down identifies the event Down, which occurred in instance R1 of the Router class.
Unique notification names with this convention are displayed in the InternalEventHandle column. By default, the InternalEventHandle column is not displayed in the Notification Log Console, but you can add it by selecting
Log >
Select Columns. The Class, Name, and Event columns display a more readable form of this information.
Note: A notification created using the
sm_ems
utility allows you to name it freely. However, the notification name must not include the characters
+ ` \ ” ’ or .
, as these may cause issues in the EDAA URL.
The Notification Log Console will not list more than one notification with this name. If the event clears and occurs again before it is archived, the Count field is increased accordingly. “The notification life cycle” on page 116 contains additional information about notification archival.