Important! As of CA UIM 8.5.1, the ems probe is required to send alarm data to USM, and is installed as part of UIM installation or upgrade.
The Alarm Server (nas) stores and administers alarm messages for the CA UIM Alarm product. The nas package contains two probes: alarm_enrichment and nas.
The alarm_enrichment probe is a preprocessor for the nas probe. Alarm_enrichment attaches to a permanent queue and receives alarm messages distributed by the hub. The messages flow into the alarm_enrichment probe, where messages may be enriched with additional information from external data sources using a Configuration Management Database (cmdb). The alarms are renamed to alarm2 and are sent to the nas probe for further processing.
The nas probe is a service probe that attaches itself to a permanent queue and receives alarm2 messages distributed by the hub. The nas probe stores information about received messages into a database.
The nas responds to a command set reachable by anyone with the correct access. When state changes occur, nas posts messages. Any application can subscribe to nas generated events. The enterprise console and event viewer both subscribe to nas events.
Alarm Flow in CA UIM 8.5 or Earlier (Enrich and then Forward to nas)
The alarm_enrichment and nas probes are packaged, installed, and configured as a single unit. Each probe is displayed in the archive as a separate probe. Configure both probes with the nas probe configuration. The nas configuration is saved in the
Note: Some nas functionality requires the deployment and configuration of additional probes:
The alarm_enrichment probe can be configured to read data from various data sources. Each data source is referred to as a cmdb. Only JDBC compliant SQL database sources are supported.
Each data source is defined by the JDBC connect string, user login, password, and a query to extract the data. Every data source provides a user defined name to reference in the enrichment rules. Each
enrichment_rule can reference one data source. A data source can be used by many enrichment rules.
Once you have defined the cmdb data source, define at least one enrichment rule.
Each enrichment rule defines a matching condition to match alarms to forward to the enrichment rule. The enrichment rule defines what alarm enrichment to perform, and the data source where additional information for the alarm is read.
When an alarm arrives, it is copied to a new event where:
NimIdis modified to ensure it is unique.
subjectare removed from the incoming alarm.
original_is prepended to all fields starting with
hop. For example, the field
original_hop0in the outgoing alarm.
The alarm is matched against the configured alarm enrichment rules. An overwrite rule defines an alarm attribute and a value to which the alarm attribute is set. Once an alarm is processed against the alarm enrichment rules it is sent to the nas probe for further processing.
At a minimum, you need one routing rule to forward your alarms to your Alarm Server (nas). You can create more than one routing rule.
Items to consider:
The nas probe has the following features: