Zhone IMACS 8000, User Manual

Page: 110 / 788

5-28 Reference Guide
Model No.
Running Head
Alarms System Configuration and Operation
5.7.4 Alarm Cutoff (ACO)
The ACO (Alarm Cutoff) security feature is used by the system to alert an operator to alarms
that clear themselves while the system is unattended. The ACO option settings are aco-on and
aco-off. If ACO is set to report or log alarms, any alarm set to report or log with a major
modifier brings up an additional alarm message on the screen. You must manually clear this
message, which is the ACO alarm message (depends on whether or not CPU is set for latch or
CUR). The ACO is used with the node port of the Interface card. It can also trigger an external
alarm device, such as a bell or lamp, that must also be manually cleared.
All ACO alarms must be cleared from the Interface card screen. ACO alarms can be cleared
automatically or manually.
5.7.5 Backplane Out of Service (BP_OOS)
The host CPU polls each card periodically for a variety of information and alarm status. The
card responds with a multi-field message to the host with such information as alarm condition
(either active or not and type of alarm), slot number, etc. Alarms are automatically set or
cleared based on the contents of these messages returned by each card. For the BP-OOS alarm,
the slot number reported from a card is corrupted for an OOS type alarm. The CPU reports
BP-OOS when it indexes outside the boundaries of a defined alarm.
Possible causes for this alarm type include:
1. Improper grounding of the system. Floating lines on the backplane can cause the
message between card and host to be corrupted, so proper grounding can have a positive
effect on removing this condition.
2. Improper seating of cards may cause an intermittent error where the CPU receives
incorrect data from the card.
3. Defective serial memory on a card or defective NVRAM on the Interface card can also
cause this condition to occur in the field.
4. In earlier software releases, if an operator erroneously attempted an OOS operation on
an empty slot, a BP-OOS alarm would be generated. Protection for this condition was
added in recent software releases to prevent this alarm from being reported under this
condition.
Once activated, this alarm can only be cleared as follows.
a) For cause type 4 above, contact technical support to clear the alarm that does
not require step b) to be performed.
b) For all conditions other than type 4 above, the system must be zipped
(resetting all the possible alarm codes off).