
About Alarm Origination Manager
CentreVu CMS R3V8 Alarm Origination Manager
How AOM Works 3
How AOM Works 0
Whenever the AOM receives an error, it writes this error to a log. At a specified
error threshold level, AOM sends an alarm via modem to a remote computer
system, such as INADS. The remote system generates a trouble ticket for the
Lucent Technical Service Center (TSC) personnel.
Errors or conditions that exceed a certain threshold are defined as active alarms
and result in a call to the remote system alarm receiver. The thresholds that cause
a condition to become “alarmable” are link outages, archiver and harchiver
errors, and disk full or disk read/write errors.
Some examples of alarm types are:
ARCH
HARCH
DISK
ACDLINK[i]
ECH_WARNING
ECH_FAILURE
(TEST_ALARM & ES_ALARM)
Receiving and
Resolving Active
Alarms 1
Services personnel are responsible for administering alarm events,
including Expert Systems (ES) and test alarms, on either a local or remote
system. A typical scenario might include the following:
Step Action
1 The AOM receives an error that exceeds the threshold that makes it
“alarmable.”
2 The AOM transmits this active alarm event to a remote alarm
receiver.
3 The AOM automatically creates a TSC trouble ticket, which is
forwarded to Services personnel.
4 Services receives the TSC trouble ticket and enters a call to the active
alarms program, which displays a list of currently active alarms for
the customer site.
5 Services fixes the condition and enters a alarm-resolve command,
causing the alarm to no longer appear on the active list.
Komentarze do niniejszej Instrukcji