Juniper JUNOSE 10.0.X PHYSICAL LAYER, Configuration Manual

Page: 182 / 262

■
alarms used for operational status calculation—Types of defects that the
router uses to determine the operational status of the interface at the section
and line layers
■
defect trigger soaking delay—Time that the router waits to set an alarm
when the router records a defect at the section or line layer
■
Operational Status—Physical state of the interface:
■
up—Interface is operational
■
down, failure alarm—Interface is not operational; type of defect that
caused failure is specified
■
time since last status change—Time since the line module was rebooted
■
Loopback State—Type of loopback configured at this layer in the interface,
or none
■
Last Remote Loopback Request Sent
■
BERT test—Number of current test and total number of tests
■
Test interval—Length of the BERT test
■
status—Sync (controller is synchronized with remote device) or NoSync
(controller is not synchronized with remote device
■
Sync count—Number of times the pattern detector synchronized with
the incoming data pattern
■
Received bit count—Number of bits received
■
Error bit count—Number of bits with errors
■
Mode—Type of interface: SONET or SDH
■
Timing source—Type of clock source configured for the channel:
■
internal module—Internal clock is from the line module itself
■
chassis—Internal clock is from the configured router clock
■
Current section alarms—Number of suspect bit patterns found in several
consecutive frames in section layer, or none
■
Current line alarms—Number of suspect bit patterns found in several
consecutive frames in line layer
■
Channel configuration—Parameters for specific controllers; the actual
parameters depend on the controller.
■
ifAdminStatus—State of the controller in the software configuration: up or
down
■
ifOperStatus—Physical state of the controller: up or down
■
Time since last status change—Time the controller has been up or down
156 ■
Monitoring Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide