Procedure 5-19: Clear
″
FE-LAN CP failed
″
alarm
....................................................................................................................................................................................................................................
Overview
This procedure is used to clear a
FE-LAN CP failed
alarm indicated
by a lighted Critical (
CR
) LED on the SYSCTL faceplate, and
reported as critical in the WaveStar
®
CIT Alarm List.
Before you begin
Prior to performing this procedure:
1.
Refer to
and
in this chapter.
2.
Refer to
and
“Electrostatic discharge” (1-13)
in
Procedure
Complete the following steps to clear a
FE-LAN CP failed
alarm.
............................................................................................................................................................
1
From the WaveStar
®
CIT System View, click the
Alarm List
button
and locate the
FE-LAN CP failed
alarm in the resulting alarm list.
............................................................................................................................................................
2
Refer to the Probable Cause column in the alarm list, determine the
circuit pack affected, and note the corresponding AID.
............................................................................................................................................................
3
CAUTION
Service disruption hazard
Disconnecting cables and/or replacing circuit packs may disrupt
service.
Before taking action, determine the extent of service disruption
caused by disconnecting cables or replacing a circuit pack. Then,
perform the action(s) deemed appropriate in light of the traffic
being carried and the nature of the failure.
Trouble clearing procedures
....................................................................................................................................................................................................................................
5 - 5 8
Lucent Technologies
365-372-333 R2.1
Issue 4, June 2005