User Guide

Chapter 3 Getting Started
Managing Alarms
3-12
Cisco AlarmTracker Client User Guide
OL-1501-01
More information on using the Alarm Details View can be found in Alarm Details
View, page 8-4.
Managing Alarms
User Actions
Alarm objects are managed by the different user actions that can be applied to
them. The following user actions are allowed on Alarm objects:
• Assign - a user can assign an Alarm object which acknowledges that someone
at the support center is aware of the condition. As part of assigning the Alarm,
you can assign the Alarm to someone else or to a queue, enter some notes
about the Alarm, and enter a Ticket ID to cross reference the Alarm with an
external trouble ticket reporting system.
• Unassign - this is the inverse operation of an Assign. Unassigning an object
moves the object back to the unassigned state. Note that this option is not
available if the Alarm is Excluded.
• Exclude - a user can exclude an Alarm object which generally means that
someone at the support center is aware of the condition, but it is a condition
that can be essentially ignored. As part of excluding the Alarm, you can
assign the Alarm to someone else or to a queue, enter some notes about the
Alarm, enter a Ticket ID to cross reference the Alarm with an external trouble
ticket reporting system.
• Include - this is the inverse operation of an Exclude. Including an object
moves the object back to the unassigned state. Note that this option is not
available if the Alarm is Assigned
• Clear - you can Clear an Alarm which effectively overrides a clear Event
from the customer site. A user clear operation is sometimes needed if, for
some reason, the up or clear Event was not sent by the relevant device at the
customer site. Note that a user Clear can only be done to an unassigned
object, and cannot be done to single-state Alarm objects.