Event Configuration

This section provides a brief overview of conceptual information about Events and Alarms.
CA Spectrum Event and Alarm Concepts
This section provides a brief overview of conceptual information about Events and Alarms.
About Alarms and Events
 is a services and infrastructure management system that notifies you of faults on managed elements within the network infrastructure. 
 receives alerts from problem areas within the managed infrastructure. 
 converts alerts into events and alarms, which are displayed in OneClick event and alarm views. Alerts, events, and alarms let 
 notify you about significant occurrences in your IT infrastructure.
 is an unsolicited message from a managed element on a network. A more specific definition of an alert depends on the management protocol that is used to report the alert. In general, 
 uses SNMP as the management protocol to communicate with devices on a network. Alerts that an SNMP-compliant device generates are named 
You can configure managed elements that have enabled the SNMP traps to direct their traps to the host that is running 
. The host receives a trap 
 and identifies the model in the 
 database that is associated with the managed element, using the source IP address. Next, 
 maps the trap to a 
 event. The event is then generated and processed.
 applies special handling to traps that are not mapped to specific 
 events. Traps that occur on managed elements that are not modeled at the time the trap is received are also handled differently. For more information, see .
You map the traps from a managed element to specific
events using the MIB Tools application in OneClick. Perform these mappings before you can create and modify the events and associated alarms using Event Configuration. For more information, see .
is a 
 object that indicates that something significant has occurred within 
 itself or within the managed environment. Events always occur in relation to a model. When 
 receives an alert from a managed element on the network, in response, it generates a 
 event for the corresponding model if the received trap is mapped to an event.
 also generates some events automatically. For example, 
 generates an event when models are created or destroyed or when 
 connects or disconnects from a device application. 
 also generates an event when contact with a managed element is established or lost.
 uses the configuration of the underlying event to process an event instance. For example, the Archive Manager in the Distributed Data Manager (DDM) database can log an event instance. Or an event instance can clear an alarm or can generate another event using an event rule.
Network operators can view the list of current events in a landscape on the OneClick Events tab. For a specific event, you can also view information such as a description of the event and the time it was created.
To map the traps from a device to specific 
 events, use the MIB Tools application in OneClick. Then complete event customization using Event Configuration. In Event Configuration, define event processing rules, create the event message to display to users, and set other parameters.
Event Codes
Every event has a unique event code. The event code is a 4-byte integer that is expressed in hexadecimal format.
An event code has two parts:
  • The first 2 bytes contain the developer ID of the developer who created the event
  • The last 2 bytes identify the event with a unique number relative to all other event codes for that developer
 assigns event codes to all events created using MIB Tools or Event Configuration. The next available event code is always used as the default code. In Event Configuration, you have the option of overriding the default code and specifying a different one.
The event code 0x10000 represents a null event. This event cannot be generated. However, the null event can be used in an event rule that requires an event code as a parameter.
 is a 
 object that indicates that a user-actionable, abnormal condition exists in a model. 
 generates an alarm when a 
 event -- typically generated as a result of a received trap -- specifies an alarm creation. 
 can generate an alarm that is based on the results of a watch. 
 can also send an event in response to an abnormal situation that did not send an event. (For example, a model loses the connection to its managed element).
Network operators are alerted to alarms in multiple ways that depend on OneClick configuration. For example, the icon representing the model of the managed element (or a container model for the managed element model) can change color. Or an audio message can announce the new alarm.
Operators can view the current list of alarms in a landscape on the OneClick Alarms tab. For a specific alarm, you can also view detailed information. For example, you can see whether a user has acknowledged the alarm, its symptoms, probable causes, and the recommended corrective actions.
When the abnormal condition that caused the alarm ends, another event automatically clears the corresponding alarm. You can clear the alarm manually and also send any Alarm notifications to external third-party or internal 
 applications as appropriate.
You can specify whether an event generates an alarm (and alarm severity) in MIB Tools when you map a trap to an event. However, you use Event Configuration to set more alarm parameters and to change the alarm severity.
The following figure illustrates the flow of alerts, events, and alarms within 
This section contains information about the following topics: