User Guide

1-7
Cisco AlarmTracker Client User Guide
OL-1501-01
Chapter 1 AlarmTracker Client Introduction
Overview
Single-State Alarms
Single-state Alarms are Alarms that do not have an associated clear Event
associated with them. Thus, the Alarm must be deleted by an AlarmTracker user.
This is the only way to clear a single-state Alarm. In fact, by policy, all
single-state Alarms must actually be deleted by AlarmTracker users. When an
Alarm is deleted, the Listener Base Record object is also deleted as well.
Application Errors
Application Errors are a type of single-state Alarm object, but they are considered
of lower priority than other Alarm objects. Application Errors are typically
indicative of configuration problems, but are not related to system faults.
Examples of Application Errors in the ICM system are unmapped dialed numbers.
Application Errors are also displayed differently in AlarmTracker and their
visibility can be easily toggled on and off. They are also maintained and tracked
differently in the Alarms Database.
Simple Events
Another class of Alarm objects are not really Alarm objects at all. They are called
Simple Events and are maintained and tracked separately from other Alarm
objects. Simple Events (or Simples) are stateless Alarms that are maintained by
Listener and can be displayed by AlarmTracker in the Event Details View (see
Event Details View, page 8-20) and in the Events Bar (see EventsBar, page 4-13).
These are considered lower priority Events and their display can be easily toggled
on and off in the Event Details View. In addition, because they are stateless, they
are maintained in a separate table in the Alarms Database and tracked differently.
Also, Simples cannot be assigned, excluded or deleted.
A Listener setting defines how long Simples are held and tracked. After this
period has elapsed, Listener will purge the Simples from its in-memory state and
inform client applications (like LGMapper) to do the same. LGMapper servers
will purge these Events from its database when instructed to do so by the Listener.
LGArchiver servers, on the other hand, will ignore any requests to delete Simple
Events. They are purged when the Event's CreationTime is greater than the
LGArchiver time history window.