Command Reference Guide

88 ● display controller t1 3Com Router 5000 Family and Router 6000 Family
Command Reference
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail
Secs
Total Data (last 2 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations
0 Ais Alarm Secs, 2087 Los Alarm Secs
52 Slip Secs, 2087 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 2087 Unavail
Secs
Table 1 Description on the fields of the display controller t1 command
Field Description
T1 1/0/0 current state
:DOWN
Physical state of the interface: up or down
Description : T1 1/0/0
Interface
Description about the T1 interface
Basic Configuration: Basic configurations for the interface
Work mode Operating mode of the T1 interface, T1 framed in this example
Cable type Cable type of the T1 interface, 100 ohm balanced in this example
Frame-format Frame format configured on the T1 interface: ESF or SF
fdl FDL format: ANSI, ATT, or none
Line code Line code: AMI or B8ZS
Source clock Source clock used by the interface: master or slave
Data-coding Normal or inverted
Idle code 7e or ff
Itf type Type of interframe filling tag: 7e or ff
Itf number Number of interframe filling tags
Loop back Loopback setting on the interface: local, payload, remote, or not set
Alarm State Alarm state
Receiver alarm state is
Loss-of-Signal.
Type of the received alarm: none, LOS, LOF, RAI, or AIS
Transmitter is sending
remote alarm.
Type of the transmitted alarm: RAI, or none
Pulse density violation
detected
The detected pulse density is incompliant with the specification
SendLoopCode History:
inband-llb-up:0 times
inband-llb-down:0 times.
fdl-ansi-llb-up:0 times,
fdl-ansi-llb-down:0 times.
fdl-ansi-plb-up:0 times,
fdl-ansi-plb-down:0 times
History of loopback code sending to the far-end, including the
number of transmissions for each type of code, and the type of the
last sent code. (See the sendloopcode command.)
BERT state:(stopped, not
completed)
BERT state: completed, stopped (not completed), or running.
Test pattern: 2^15, Status:
Not Sync, Sync Detected: 0
Test pattern in use (2^20 or 2^15), 2^15 in this example;
synchronization state, and the number of detected synchronizations
Time: 0 minute(s),
Time past: 0 minute(s)
The duration of the BERT test and the time that has elapsed
Bit Errors (since test started):
0 bits
Number of bit errors received since the start of the BERT test
Bits Received (since test
started)
Number of bits received since the start of the BERT test
Bit Errors (since latest sync) Number of bit errors received since the last synchronization
Bits Received (since latest
sync)
Number of bits received since last synchronization