Users Guide

Understanding Alarm Propagation to Services and Customers | Alarms, Events, and Automation
OMNM 6.5.3 User Guide 351
Existing Alarm Clears
When an existing alarm clears, here is what happens:
User Actions Execute
When user actions execute, here is what happens:
Child Resources: The alarm changes the alarm state of parent of the source and the alarm's
Resource Propagation value is Impacts Top Level.
Dependencies: Parent equipment matches the child entities alarm state.
All deployed services and associated customers depending on only this
resource’s alarmed component have their alarm state match the resource’s
component.
No Change to Alarm State: The new alarm does not change the alarm state of its source, so no services
or customers have their alarm state changed
Alarm not Service Affecting: The new alarm is not service affecting. The result is that no change occurs
to services’ or customers’ alarm state.
What Happens Description
Clearing Service Affecting
Existing Alarm Changes
Alarm State:
This changes the alarm state (higher or lower) of a resource.
Dependancies: All deployed services and associated customers depending
on this resource have their alarm state match the resource.
No Dependencies: No services or customers change their alarm state
Clearing Non-Service
Affecting Existing Alarm:
No services or customers have their alarm state changed
What Happens Description
Resync the resource’s alarm
state:
• If the resource’s displayed alarm state was incorrect, perhaps because it
is a parent or child of a resource whose alarm state has changed, then
this corrects it.
• If this action changes the alarm state and this resource’s most severe
alarm is service affecting, then resync makes alarm states propagate to
any associated services and customers. If the deployed services have the
incorrect alarm state, then resync corrects that inaccuracy.
Viewing alarms associated
with a service:
• If the service is deployed, and the target resource has open service
affecting alarms, all open service affecting alarms for the target resource
appear.
• If the service is deployed, but the target resource has only cleared or
non-service affecting alarms against it, no alarms appear.
• If the service is deployed, and the target resource does not have open
service affecting alarms, but at least one descendent entity of this
resource has open service affecting alarms against it, those alarms
propagate up to the resource. All open service affecting alarms that
propagate up (Resource Propagation is Impacts top level) for the target
resource’s descendants appear
• If the target resource does not have service affecting alarms, and neither
do any service affecting alarms exist for its descendent entities, no
alarms appear.
• If the service is undeployed, no alarms appear.
What Happens Description