Examples
The following example shows sample output from the show
controllers t1 command with the brief
keyword for a single T1 channel:
RP/0/0/CPU0:router# show controllers t1 0/4/2/0/1 brief
T1 0/4/2/0/1 is up
mode: ATM
timeslots: 1-24
FDL per AT&T 54016 spec.
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Clock Source is internal
Alarm Soaking Interval:
Alarm Declaring= 2500 msec
Alarm clearing = 10000 msec
Bert Test on controller port : T1 0/4/2/0/1
BERT test result (not running)
Test Pattern : Not Configured, Status : not running, Sync Detected : 0
Interval : 1 minute(s), Time Remain : 0 (ms)
Bit Errors (since BERT started): 0 bits,
Bits Received (since BERT started): 0 Kbits
Bit Errors (since last sync): 0 bits
Bits Received (since last sync): 0 Kbits
Table 4 show controllers t1 brief Field Descriptions
Field
|
Description
|
T1 0/4/2/0/1 is up
|
T1 channel is operating. The channel state can be up, down, or
administratively down. Loopback conditions are shown by (Locally Looped)
or (Remotely Looped).
|
mode
|
Mode of the T1 controller, which can be ATM.
|
timeslots
|
DS0 time slots assigned to the T1 channel.
|
FDL per spec-name spec.
|
Performance monitoring is through Facility Data Link based on ANSI T1.403
specification or AT&T standard specification number 54016.
|
Receiver has no alarms.
|
Any alarms detected by the T1 controller are displayed here. Possible
alarms are as follows:
- Transmitter is sending remote alarm.
- Transmitter is sending AIS.
- Receiver has loss of signal.
- Receiver is getting AIS.
- Receiver has loss of frame.
- Receiver has remote alarm.
- Receiver has no alarms.
|
Framing
|
Framing type on the channelized controller. Values are ESF and SF.
|
Line Code
|
Line coding format on the channelized controller. Values are AMI or B8ZS.
|
Clock Source
|
Clock source on the T1 channel. Values are internal and line.
|
Alarm Soaking Interval
|
Values of the following alarm soaking intervals:
- Alarm declarings: amount of time, in milliseconds, after which an
alarm is declared.
- Alarm clearing: amount of time, in milliseconds, after which an alarm
is cleared.
|
Bert Test on controller port
|
Indicates controller port on which BERT test can be run.
|
BERT test result
|
Indicates the current state of the test. Can be one of the following:
- running— BER test is still in progress.
- done—BER test is complete.
- not running—BER test is not running on the controller.
|
Test Pattern
|
Indicates the test pattern you selected for the test.
|
Status
|
Indicates the current synchronization state (sync).
|
Sync Detected
|
Indicates the number of times synchronization has been detected during
this test.
|
Interval
|
Indicates the length of the test.
|
Time Remain
|
Indicates the time remaining for the test to run.
Note
|
If you terminate a BER test, you receive a message similar to the
following: Time Remain : 2 minute(s) (unable to complete) "(Unable to
complete)" signifies that you interrupted the test.
|
|
Bit Errors (since BERT started)
|
Bit errors that have been detected since the test started.
|
Bits Received (since BERT started)
|
Total number of test bits that have been received since the test started.
|
Bit Errors (since last sync)
|
Bit errors that have been detected since the synchronization started.
|
Bits Received (since last sync)
|
Total number of test bits that have been received since the
synchronization started.
|
The following example shows sample output from the show
controllers t1 command for a single T1 channel:
RP/0/0/CPU0:router# show controllers t1 0/4/2/0/1
T1 0/4/2/0/1 is up
mode: ATM
timeslots: 1-24
FDL per AT&T 54016 spec.
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Clock Source is internal
Data in current interval (38 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Data in Interval 1:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
.
.
.
The following example shows sample output from the show
controllers t1 command with the tabular
keyword for a single T1 channel:
RP/0/0/CPU0:router# show controllers t1 0/4/2/0/1 tabular
T1 0/4/2/0/1 is up
mode: ATM
timeslots: 1-24
FDL per AT&T 54016 spec.
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Clock Source is internal
INTERVAL LCV PCV CSS SEFS LES DM ES BES SES UAS SSS
08:30-08:35 0 0 0 0 0 0 0 0 0 0 0
08:15-08:30 0 0 0 0 0 0 0 0 0 0 0
08:00-08:15 0 0 0 0 0 0 0 0 0 0 0
07:45-08:00 0 0 0 0 0 0 0 0 0 0 0
07:30-07:45 0 0 0 0 0 0 0 0 0 0 0
07:15-07:30 0 0 0 0 0 0 0 0 0 0 0
07:00-07:15 0 0 0 0 0 0 0 0 0 0 0
06:45-07:00 0 0 0 0 0 0 0 0 0 0 0
06:30-06:45 0 0 0 0 0 0 0 0 0 0 0
06:15-06:30 0 0 0 0 0 0 0 0 0 0 0
06:00-06:15 0 0 0 0 0 0 0 0 0 0 0
05:45-06:00 0 0 0 0 0 0 0 0 0 0 0
05:30-05:45 0 0 0 0 0 0 0 0 0 0 0
05:15-05:30 0 0 0 0 0 0 0 0 0 0 0
.
.
.
Table 5 show controllers t1 and show controllers t1 tabular Field Descriptions
Field
|
Description
|
T1 0/4/2/0/1 is up
|
T1 channel is operating. The channel state can be up, down, or
administratively down. Loopback conditions are shown by (Locally Looped)
or (Remotely Looped).
|
mode
|
Mode of the T1 controller, which can be ATM.
|
timeslots
|
DS0 time slots assigned to the T1 channel.
|
FDL per spec-name spec.
|
Performance monitoring is through Facility Data Link based on ANSI T1.403
specification or AT&T standard specification number 54016.
|
Receiver has no alarms.
|
Any alarms detected by the T1 controller are displayed here. Possible
alarms are as follows:
- Transmitter is sending remote alarm.
- Transmitter is sending AIS.
- Receiver has loss of signal.
- Receiver is getting AIS.
- Receiver has loss of frame.
- Receiver has remote alarm.
- Receiver has no alarms.
|
Framing
|
Framing type on the channelized controller. Values are ESF and SF.
|
Line Code
|
Line coding format on the channelized controller. Values are AMI or B8ZS.
|
Clock Source
|
Clock source on the T1 channel. Values are internal and line.
|
Data in current interval (seconds elapsed)
|
Shows the current accumulation period, which rolls into the 24-hour
accumulation every 15 minutes. The accumulation period is from 1 to
900 seconds. The oldest 15-minute period falls off the back of the
24-hour accumulation buffer.
|
Line Code Violations
|
Line Code Violations (LCVs) is a count of both Bipolar Violations (BPVs)
and Excessive Zeros (EXZs) that occur over the accumulation period. An
EXZ increments the LCV by one regardless of the length of the zero
string.
|
Slip Secs
|
Controlled slip second (CSS) is a 1-second interval that contains one or
more controlled slips.
|
Fr Loss Secs
|
Frame loss seconds (SELS) is the number of seconds for which an
out-of-frame error is detected.
|
Line Err Secs
|
Line errored seconds (LES) is a second in which one or more line code
violation errors are detected.
|
Degraded Mins
|
Degraded minute (DM) is a minute in which the estimated error rate
exceeds 1E-6 but does not exceed 1E-3. For more information, see RFC
1406, Definitions of Managed Objects for DS1 and E1 Interface
Types.
|
Errored Secs
|
Errored seconds (ES) is a second with one or more path coding violations,
one or more out-of-frame defects, or one or more controlled slip events
or a detected AIS defect.
|
Bursty Err Secs
|
Bursty errored seconds (BES) is a second with fewer than 320 and more
than one path coding violation error events, no severely errored frame
defects, and no detected incoming AIS defects. Controlled slips are not
included in this parameter.
|
Severely Err Secs
|
Severely errored seconds (SES) is a second with 320 or more path code
violation errors events, one or more out-of-frame defects, or a detected
AIS defect.
|
Unavailable Secs
|
Number of seconds during which the interface was not available in this
interval, referred to as UAS.
|
Stuffed Secs
|
Stuffed seconds (SSS) is a second in which one more bit stuffings take
place. This happens when the Pulse Density Enforcer detects a potential
violation in the output stream and inserts a 1 to prevent it. Such bit
stuffings corrupt user data and indicate that the network is configured
incorrectly. This counter can be used to help diagnose this
situation.
|
Near-end path failures
|
Total number of near-end path failures.
|
Far-end path failures
|
Total number of far-end path failures.
|
SEF/AIS Secs
|
Total number or Severely Errored Framing (SEF) and Alarm Indication
Signal (AIS) errors.
|