Juniper J-Series Administration Manual page 192

J-series Services Router Administration Guide
Table 89: Interface Alarm Conditions (continued)
Interface Alarm Condition
T3 (DS3) Alarm indication signal
Excessive number of zeros
Far-end receive failure
Idle alarm
Line code violation
Loss of frame
Loss of signal
Phase-locked loop out of lock
Yellow alarm
Chassis Alarm Conditions and Corrective Actions
Table 90 on page 171 lists chassis components with preset alarms, the conditions
that can trigger an alarm, the alarm severity, and the action you take to correct the
condition.
170
Alarm Overview
Description
The normal T3 traffic signal contained a defect
condition and has been replaced by the AIS. A
transmission interruption occurred at the remote
endpoint or upstream of the remote endpoint. This
all-ones signal is transmitted to prevent
consequential downstream failures or alarms.
The bit stream received from the upstream host has
more consecutive zeros than are allowed in a T3
frame.
The remote endpoint of the connection has failed.
A FERF differs from a yellow alarm, because the
failure can be any failure, not just an out-of-frame
(OOF) or loss-of-signal (LOS) failure.
The Idle signal is being received from the remote
endpoint.
Either the line encoding along the T3 link is
corrupted, or a mismatch between the encoding at
the local and remote endpoints of a T3 connection
occurred.
An out-of-frame (OOF) or loss-of-signal (LOS)
condition has existed for 10 seconds. The
loss-of-frame (LOF) failure is cleared when no OOF
or LOS defects have occurred for 20 seconds. A LOF
failure is also called a red failure.
No remote T3 signal is being received at the T3
interface.
The clocking signals for the local and remote
endpoints no longer operate in lock-step.
The remote endpoint is in red alarm failure. This
condition is also known as a far end alarm failure.
Configuration
Option
ais
exz
ferf
idle
lcv
lof
los
pll
ylw