Cisco ONS 15310-CL, Руководство по устранению неисправностей

Страница: 100 / 332

1-66
Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.0
78-17235-01
Chapter 1 General Troubleshooting
1.10.10 Blinking STAT LED after Installing a Card
1.10.10 Blinking STAT LED after Installing a Card
Symptom
After installing a card, the STAT LED blinks continuously for more than 60 seconds.
Table 1-29 describes the potential cause of the symptom and the solution.
1.11 Fiber and Cabling
This section explains problems typically caused by cabling connectivity errors. It also includes
instructions for crimping CAT-5 cable and lists the optical fiber connectivity levels.
1.11.1 Bit Errors Appear for a Traffic Card
Symptom A traffic card has multiple bit errors.
Table 1-30 describes the potential cause of the symptom and the solution.
Table 1-29 Blinking STAT LED on Installed Card
Possible Problem Solution
The card cannot boot
because it failed the
Power On Shelf Test
(POST) diagnostics. The blinking STAT LED indicates that POST diagnostics are being
performed. If the LED continues to blink more than 60 seconds, the card has
failed the POST diagnostics test and has failed to boot.
If the card has truly failed, an EQPT-BOOT alarm is raised against the slot
number with an “Equipment Fails To Boot” description. Check the alarm tab
for this alarm to appear for the slot where the card is installed.
To attempt recovery, remove and reinstall the card and observe the card boot
process. If the card fails to boot, replace the card.
Table 1-30 Bit Errors Appear for a Line Card
Possible Problem Solution
Faulty cabling or low
optical-line levels. Troubleshoot cabling problems using the “1.1 Network Troubleshooting
Tests” section on page 1-2 . Troubleshoot low optical levels using procedures
in the “1.11.2 Faulty Fiber-Optic Connections” section on page 1-67 .
Note
Bit errors on line (traffic) ports usually originate from cabling
problems or low optical-line levels. The errors can be caused by
synchronization problems, especially if pointer justification (PJ)
errors are reported. Use a test set whenever possible because the
cause of the errors could be external cabling, fiber, or external
equipment connecting to the node.