Troubleshooting Basics - Alcatel-Lucent 9500 MXC User Manual

Chapter 2. 9500 MXC Troubleshooting

Troubleshooting Basics

Vol. V-2-4
• Toolkit.
• Key(s) for access to the site.
This section provides general guidance on 9500 MXC troubleshooting:
• Check front-panel LED indications. These provide summary alarm
indications, which can help narrow down the location and type of failure. Refer
to 9500 MXC LEDs on page 2-10.
• Where a Status LED on a plug-in is off (unlit), but power to the INU/INUe
is confirmed by LEDs on other plug-ins, check the seating of the affected
plug-in.
• Check System Summary screen. When logging into 9500 MXC with CT, the
opening screen is System Summary. Use the information provided to check the
alarm location, its severity, and problem type:
• Mouse-over problem icons for a description of the problem type.
• Double clicking a module takes you to the relevant CT Alarms screen. Refer
to CT Alarms on page 2-16. Use these alarms with the information provided
on probable cause and recommended actions, to help determine the real
cause of a failure and the action to take.
• Check the basics first.
• For example, if multiple alarms are present, and these include power supply
voltage or hardware alarms, always check their cause before looking at
resultant down-stream path failure or path warning alarms.
• Similarly, if a path-related failure is indicated (no hardware or software
alarms), investigate the path. Go to the CT History screen (15 minute view),
and the Events screen to check supporting data, such as low RSL and
incidence of intermittent pre-failure BER alarms, which if present are
evidence of a path-related failure. Refer to Troubleshooting Path Problems
on page 2-6 for more information.
• Check if symptoms match the alarm. Alarms reflect the alarm state, but in
exceptional circumstances an alarm may be raised because of a failure to
communicate correctly with the alarm source, or a failure in alarm management
processing. Always check to see if symptoms match the alarm, using LED
indications and CT Diagnostics.
• Check if recent work may be a cause. Recent work at the site may be a cause
or contributing factor. Check for a configuration change, software upgrade,
power recycling (reboot), or other site work:
Alcatel-Lucent