Users Guide

Understanding Alarm Propagation to Services and Customers | Alarms, Events, and Automation
350 OMNM 6.5.3 User Guide
Understanding Alarm Propagation to Services and
Customers
The following describes the use cases where Alarm Propagation services and customers occurs. This
describes the sequence of events/alarms. See also
Variable Binding Definition Editor on page 348
for ways to augment propagation possibilities.
Alarm state must propagate to associated entities for each step and might take some time to reach
all of them, so matching mentioned may not be instantaneous, depending on the complexity of the
associations. This propagation to services and customers occurs through a background process,
running on regular intervals.
A resource can have several levels of services that depend on it, and then customers can depend on
them, and so on. Potentially, several levels of dependency and a large database full of services and
customers to propagate alarm states can exist, so propagation processing occurs in the background.
By default, this process runs every 30 seconds, but you can configure this interval by setting the
com.dorado.assure.propagation.AlarmPropagationInterval property. This value is in milliseconds.
For example, the to set the interval to 60 seconds, set this property as follows:
com.dorado.assure.propagation.AlarmPropagationInterval=60000
To prevent any OpenManage Network Manager upgrades from overwriting this setting, it is best to
put it into the following file:
\owareapps\installprops\lib\installed.properties
After changing this property, make sure that you restart the application server for the change to
take effect.
NOTE:
Only services associated with the alarmed subcomponents are affected by alarms on the subcomponent,
not services connected to the rest of the device. You can also override default service affecting alarm
behavior with an Event Processing Rule. See Automation and Event Processing Rules on page 297 for
more details about this editor.
The remainder of this section describes what happens when a new alarm arrives , an existing alarm
clears
, or user actions execute .
A New Alarm Arrives
When a new alarm arrives, here is what happens:
What Happens Description
Service Affecting Alarm
Changes Source Alarm State:
The new alarm changes the alarm state (higher or lower) of the resource
that is its source.
Dependencies: If this resource has services or customers that depend on it,
the alarm state matches for all such deployed, dependent services and their
associated customers. Without such dependencies, no alarm state changes,
besides that of the source.
Parent Resources: The alarm changes the alarm state of a child of the source and the alarm's
Resource Propagation value is Impacts Subcomponents.
Dependencies: Child equipment matches the top level’s alarm state. All
deployed services and their related customers depending on this particular
resource component match the resource component’s alarm state.