Table 17: SONET/SDH Interface Alarm Messages
CLI Message
interface-name so-x/x/x - SONET bit error rate defect
interface-name so-x/x/x - SONET bit error rate fault
interface-name so-x/x/x - SONET line AIS
interface-name so-x/x/x - SONET line remote defect indicator
interface-name so-x/x/x - SONET loss of frame
interface-name so-x/x/x - SONET loss of light
interface-name so-x/x/x - SONET loss of pointer
interface-name so-x/x/x - SONET loss of signal
interface-name so-x/x/x - SONET path AIS
interface-name so-x/x/x - SONET path mismatch
interface-name so-x/x/x - SONET path remote defect indicator
interface-name so-x/x/x - SONET PLL lock
interface-name so-x/x/x - SONET remote error indicator
interface-name so-x/x/x - SONET severely errored frame
interface-name so-x/x/x - SONET unequipped
Juniper Networks Technical Assistance Center
If you need assistance during troubleshooting, you can contact the Juniper Networks
Technical Assistance Center (JTAC) by using the Web or telephone. See
Support"
Troubleshooting the CFEB
If the CFEB fails, the forwarding and routing functions of the router halt immediately
and do not resume until the CFEB failure has been corrected.
To troubleshoot a CFEB, follow these guidelines:
on page xxiv.
Make sure the CFEB is properly seated in the midplane. Use a Phillips screwdriver
to ensure that the screws are securely tightened.
Check the alarm LEDs on the craft interface. A CFEB failure generates either a
red or yellow alarm, depending on the type of failure.
Chapter 12: Troubleshooting Hardware Components
(continued)
Troubleshooting the CFEB
"Requesting
83