User Guide

Chapter 3 Getting Started

Managing Alarms

3-14

Cisco AlarmTracker Client User Guide

OL-1501-01

Note An LGArchiver server will not delete the Alarm objects from its Alarms

Database. It will mark the Alarm object as closed and will include the Delete

Event in the database.

By policy, single-state Alarms must be Deleted. They cannot be Cleared. Also by

policy, non single-state Alarms can only be Deleted if they are Down and

Unassigned or if they are closed. Also, only users with Administrator rights (see

User Rights, page 4-15) can Delete non single-state Alarm objects. Users with

Administrator rights or User rights can Delete single-state Alarms.

Exclude Node Feature

Another type of Alarm management is the Exclude Node feature. This feature

indirectly manages a group of Alarm objects related to a node.

The Exclude Node feature can be used to exclude all Alarm objects for a particular

node in the Tree View object hierarchy and all of its children as well. This feature

is used from the Tree View Edit menu, or from the context menu that pops up

when you right click a node in the Tree View.

The Exclude Node feature is equivalent to marking all Alarm objects for the node

and its children as Excluded and it applies to all future Alarm objects for that node

and its children until the node is included by a user. More details on this feature

are included in Exclude/Include a Node, page 7-5.

Note The Exclude Node feature is optional and is not enabled in the Listener server

by default. If you try to Exclde a node and get and error message, contact your

system administrator to enable the feature. Details on how to enable this

feature are provided in the Cisco Remote Monitoring Administration Guide.

Performing User Actions

AlarmTracker Client provides many ways for you to perform a user action on one

or more Alarm objects. Most views (e.g., Alarm Details View, Alarm Bars View,

Object State View, Ticket ID Finder View and the EventsBar) allow you to select

one or more Alarms and perform a user action on them. This is typically done by