Result:
A warning appears asking you to confirm executing
this command.
............................................................................................................................................................
11
Click
Yes
to execute the command.
Important! You will be logged off the system when the system
resets.
Result:
You are logged off the system.
............................................................................................................................................................
12
From the System View, click the
Alarm List
button and click
Refresh
.
............................................................................................................................................................
13
Is the
inc. VCG failed
alarm still present?
If...
Then...
Yes
Continue with
No
STOP! End of Procedure.
............................................................................................................................................................
14
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.
Disengage the affected Ethernet circuit pack completely from the
shelf.
1.
Release the circuit pack faceplate latch.
2.
Extract the circuit pack from the shelf, fully disconnecting it
from the backplane, and therefore removing power.
The
ACTIVE
and
FAULT
LED on the pack extinguish.
3.
Re-seat the circuit pack in the shelf.
Procedure 5-32: Clear
″
inc. VCG failed
″
alarm
Trouble clearing procedures
....................................................................................................................................................................................................................................
5 - 1 0 2
Lucent Technologies
365-372-333 R2.1
Issue 4, June 2005