Alcatel-Lucent 9500 MXC User Manual page 690

Chapter 2. 9500 MXC Troubleshooting
Screen Function
Alarms Presents an alarm-tree hierarchy for the
selected module.
• Active alarms are opened out to show the
• Active alarm points have a colored center.
• Viewed alarms which have been active but
A Help for Alarm tab supports
context-sensitive alarm help for a selected
(highlighted) alarm. Provides a description of
the alarm, probable cause, recommended
actions, and where applicable additional
information. The Helpset must first be loaded
on your CT PC. Otherwise, view this alarm
information from within the 9500 MXC
Alarms section of this chapter (for PC-based
access), or from Appendix B
Event Browser View active and cleared alarms in date/time
order. Goes back in time for a maximum
5000 events (first on, first off).
The views provided are particularly helpful
in situations where it is unclear what caused
an alarm; what was the event that first lead to
an alarm being raised. The chronological
ordering and event filtering options allow
easy review of repeated events of the same
type, such as may occur during path fade
situations, or other intermittent fault events.
Each event also captures its event source by
slot location or type.
A Help for Event tab supports
context-sensitive alarm help for a selected
(highlighted) alarm event. Provides a
description of the alarm, probable cause,
recommended actions, and where applicable
additional information. The 9500 MXC
Helpset must first be loaded on your CT PC.
Vol. V-2-34
trunk to tree-end path.
since cleared, will have an up/down arrow
on the right side of their alarm circle.
Tips
• If a hardware alarm is active, this should
be investigated before others. Hardware
alarms occur when communications with
a device fail. Generally hardware status
is only checked during a power-on,
software reload, or in some instances, a
reconfiguration. The exceptions are RTC
and ADC hardware alarms, which are
continuously communicated.
• When multiple alarms are active, most
are likely to be downstream from the real
fault. For instance, with an active
Demodulator Not Locked alarm, the
downstream Rx path warning alarms will
also be active. A Demodulator alarm
may be caused by a loss of path, (path
degradation or a problem with the
remote Tx), or a fault within the
Demodulator, or its upstream hardware
or software. As a rule, follow the
guidance provided within the alarm
description for each alarm.
• Use the filtering options to select only
active alarms, and/or to separately view
all events of the same type.
Alcatel-Lucent