Juniper JUNOSE 11.2.X MULTICAST ROUTING, Configuration Manual

Page: 53 / 256

•
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
•
Number of valid intervals—Number of 15-minute intervals since the line module was
last powered on or reset
•
Time elapse in current interval—Reported in 15-second intervals
•
P-bit errored seconds—Number of errored seconds encountered by a T3 in the current
interval
•
P-bit severely errored seconds—Number of severely errored seconds encountered
by a T3 in the current interval
•
Severely errored frame seconds—Number of severely errored framing seconds
encountered by a T3 in the current interval
•
Unavailable seconds—Number of unavailable seconds encountered by a T3 in the
current interval
•
Line code violations—Number of line code violations encountered by a T3 in the
current interval
•
P-bit coding violations—Number of coding violations encountered by a T3 in the
current interval
•
Line errored seconds—Number of line errored seconds encountered by a T3 in the
current interval
•
C-bit coding violations—Number of C-bit coding violations encountered by a T3 in
the current interval
•
C-bit errored seconds—Number of C-bit errored seconds encountered by a T3 in the
current interval
•
C-bit severely errored seconds—Number of C-bit severely errored seconds
encountered by a T3 in the current interval
•
Example 1—In this example, a T3 interface is specified.
host1# show controllers t3 2/0
DS3 2/0
Description: toronto ct3 interface
ifAdminStatus = ifAdminDown
snmp trap link-status = enabled
No alarms detected
31 Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring Channelized T3 Interfaces