Alarm Propagation to Services and Customers: What Happens

The following describes the use cases where you Alarm Propagation to services and customers occurs. This describes the sequence of events / alarms.

Alarm state must propagate to associated entities for each step and might take some time to reach all of them, so matching mentioned below 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. The following...

com.dorado.assure.propagation.AlarmPropagationInterval=60000

sets the interval at 60 seconds. Best practice is to put this property in \owareapps\installprops\lib\installed.properties, so upgrading your Open Manage Network Manager package does not overwrite any change you make. After changing this property, you must restart the application server for the change to take effect.

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 Event Processing Rules for more about them.