A New Alarm Arrives, then...

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.

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.

Cleared Existing Alarm

Clearing Service Affecting Existing Alarm Changes Alarm State: This changes the alarm state (higher or lower) of a resource.

Dependencies: 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