Users Guide

Understanding Alarm Propagation to Services and Customers | Alarms, Events, and Automation
352 OMNM 6.5.3 User Guide
Viewing alarms associated
with a given customer:
• If at least one service associated with the customer has open, service
affecting alarms, all open service affecting alarms for all services
associated with this customer appear.
• If none of the services associated with this customer have open, service
affecting alarms, so alarms appear
User views the services
impacted by a particular
alarm:
• If the alarmed resource has at least one deployed service that depends
on it, all deployed services depending on the alarmed resource appear.
• If the alarmed resource does not have any deployed services that depend
on it, no services appear.
Deploying a service whose
target resource has service
affecting alarms:
• Before deploying, no alarms appear for the service. After deploying, all
open, service affecting alarms for the target resource appear.
Undeploying a service whose
target resource has service
affecting alarms:
• Before undeploying, all open, service affecting alarms for the target
resource should appear. After undeploying, no alarms appear.
Editing a deployed service to
change the target from one
resource to another:
• If the original resource has service affecting alarms but the new one does
not, all open service affecting alarms for the original target resource
should appear before the edit. After the edit, no alarms appear.
• If the original resource does not have service affecting alarms but the
new one does, before editing, no alarms appear. After editing, all open
service affecting alarms for the new target resource appear.
What Happens Description