To display information about the T3 links and hardware and software drivers for the T3 controller, use the show controllers t3 command in EXEC mode .
show controllers t3 interface-path-id [all | bert | brief | internal-state | tabular]
Syntax Description
interface-path-id
|
Physical interface or virtual interface.
Note
|
Use the show
interfaces command to see a list of all interfaces
currently configured on the router.
|
For more information about the syntax for the router, use the question mark
(? ) online help function.
|
all
|
Displays all information for the controllers.
|
bert
|
Displays internal T3 bit error rate test results.
|
brief
|
Displays summary information for the controller.
|
internal-state
|
Displays internal T3 state information.
|
tabular
|
Displays T3 controller information in tabular format.
|
Command Default
No default behavior or values
Command History
Release
|
Modification
|
Release 3.5.0
|
This command was introduced.
|
Usage Guidelines
For the interface-path-id argument, use the
following guidelines:
- When specifying a T3 controller, the naming notation is
rack/slot/module/port/T3num. The slash between
values is required as part of the notation. An explanation of each component of the
naming notation is as follows:
-
rack —Chassis number of the rack.
-
slot —Physical slot number of the line card or
SIP.
-
module —Module number or subslot (for a SPA). A
physical layer interface module (PLIM) is always 0.
-
port —Physical port number of the interface.
-
T3num —T3 controller number.
- If specifying a virtual interface, the number range varies, depending on interface
type.
Task ID
Task ID
|
Operations
|
interface
|
read
|
Examples
The following example shows sample output from the show
controllers t3 command using the brief
keyword for a single T3 port:
RP/0/RP0/CPU0:router# show controllers t3 0/4/2/0/1 brief
T3 0/4/2/0 is up
No alarms detected.
mode: serial
MDL transmission is disabled
EIC: , LIC: , FIC: , UNIT:
Path FI:
Idle Signal PORT_NO:
Test Signal GEN_NO:
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
Alarm Soaking Interval:
Alarm Declaring= 2500 msec
Alarm clearing = 10000 msec
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 3. show controllers t3 brief Field Descriptions
Field
|
Description
|
T3 0/4/2/0/1 is up
|
T3 channel is operating. The channel state can be up, down, or
administratively down. Loopback conditions are shown by (Locally Looped)
or (Remotely Looped).
|
No alarms detected
|
Any alarms detected by the 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.
|
mode
|
Mode of the T3 controller, which can be
ATM, serial, or T1serial or T1
.
|
MDL transmission
|
Status of the Maintenance Data Link (either enabled or disabled) and the
values of the MDL message fields.
|
EIC
|
Equipment Identification Code.
|
LIC
|
Location Identification Code.
|
FIC
|
Frame Identification Code.
|
UNIT
|
Unit Identification Code.
|
Path FI
|
Path facility identifier.
|
Idle Signal PORT_NO
|
Identifies the port that initiates the idle signal message.
|
Test Signal GEN_NO
|
Generator number to send in test signal messages.
|
FEAC code received
|
Whether or not a far-end alarm code request is being received. Possible
values are as follows:
- DS3 Eqpt. Failure (SA)
- DS3 LOS/HBER
- DS3 Out-of-Frame
- DS3 AIS Received
- DS3 IDLE Received
- DS3 Eqpt. Failure (NSA)
- Common Eqpt. Failure (NSA)
- Multiple DS1 LOS/HBER
- DS1 Eqpt. Failure
- Single DS1 LOS/HBER
- DS1 Eqpt. Failure (NSA)
- No code is being received
|
Framing
|
Framing type on the channelized controller. Values are auto-detect, M23,
and C-Bit.
|
Line Code
|
Line coding format on the channelized controller. Values are AMI and
B8ZS.
|
Clock Source
|
Clock source on the channelized controller. 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 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 t3 command using the tabular
keyword, for a single T3 port:
RP/0/RP0/CPU0:router# show controllers 0/4/2/0/1 tabular
T3 0/4/2/0/1 is up
INTERVAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES
09:00-09:02 0 0 0 0 0 0 0 0 0 0
08:45-09:00 0 0 0 0 0 0 0 0 0 0
08:30-08:45 0 0 0 0 0 0 0 0 0 0
08:15-08:30 0 0 0 0 0 0 0 0 0 0
08:00-08:15 0 0 0 0 0 0 0 0 0 0
07:45-08:00 0 0 0 0 0 0 0 0 0 0
07:30-07:45 0 0 0 0 0 0 0 0 0 0
.
.
.
The following example shows sample output from the show
controllers t3 command for a single T3 port:
RP/0/RP0/CPU0:router# show controllers t3 0/4/2/0/1
T3 0/4/2/0/1 is up
No alarms detected.
mode: serial
MDL transmission is disabled
EIC: , LIC: , FIC: , UNIT:
Path FI:
Idle Signal PORT_NO:
Test Signal GEN_NO:
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
Data in current interval (695 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
0 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Data in Interval 1:
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
0 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Data in Interval 2:
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
0 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Data in Interval 3:
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
0 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
.
.
.
Table 4. show controllers t3 and show controllers t3 tabular Field Descriptions
Field
|
Description
|
T3 0/4/2/0/1 is up
|
T3 channel is operating. The channel state can be up, down, or
administratively down. Loopback conditions are shown by (Locally Looped)
or (Remotely Looped).
|
No alarms detected
|
Any alarms detected by the 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.
|
mode
|
Mode of the T3 controller, which can be
ATM, serial, T1, or E1
serial or T1
ATM or serial
.
|
MDL transmission
|
Status of the Maintenance Data Link (either enabled or disabled) and the
values of the MDL message fields.
|
EIC
|
Equipment Identification code.
|
LIC
|
Location Identification code.
|
FIC
|
Frame Identification code.
|
UNIT
|
Unit Identification code.
|
Path FI
|
Path facility identifier.
|
Idle Signal PORT_NO
|
Identifies the port that initiates the idle signal message.
|
Test Signal GEN_NO
|
Generator number to send in test signal messages.
|
FEAC code received
|
Whether or not a far-end alarm code request is being received. Possible
values are as follows:
- DS3 Eqpt. Failure (SA)
- DS3 LOS/HBER
- DS3 Out-of-Frame
- DS3 AIS Received
- DS3 IDLE Received
- DS3 Eqpt. Failure (NSA)
- Common Eqpt. Failure (NSA)
- Multiple DS1 LOS/HBER
- DS1 Eqpt. Failure
- Single DS1 LOS/HBER
- DS1 Eqpt. Failure (NSA)
- No code is being received
|
Framing
|
Framing type on the channelized controller. Values are M23 and C-Bit.
|
Line Code
|
Line coding format on the channelized controller. Values are AMI and
B8ZS.
|
Clock Source
|
Clock source on the channelized controller. 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.
|
P-bit Coding Violation
|
For all DS3 applications, a P-bit coding violation (PCV) error event is a
P-bit parity error event. A P-bit parity error event is the occurrence of
a received P-bit code on the DS3 M-frame that is not identical to the
corresponding locally calculated code.
|
C-bit Coding Violation
|
For C-bit parity and SYNTRAN DS3 applications, the C-bit coding violation
(CCV) is the count of coding violations reported by the C-bits. For C-bit
parity, it is the count of CP-bit parity errors that occur during the
accumulation interval. For SYNTRAN, it is a count of CRC-9 errors that
occur during the accumulation interval.
|
P-bit Err Secs
|
P-bit errored seconds (PES) is a second with one or more PCVs, one or
more out-of-frame defects, or a detected incoming AIS. This gauge does
not increment when unavailable seconds are counted.
|
P-bit Severely Err Secs
|
P-bit severely errored seconds (PSES) is a second with 44 or more PCVs,
one or more out-of-frame defects, or a detected incoming AIS. This gauge
does not increment when unavailable seconds are counted.
|
Severely Err Framing Secs
|
Severely errored framing seconds (SEFS) is a second with one or more
out-of-frame defects or a detected incoming AIS.
|
Unavailable Secs
|
The number of unavailable seconds (UAS) is calculated by counting the
number of seconds for which the interface is unavailable. For more
information, see RFC 1407, DS3 MIB Variables.
|
Line Errored Secs
|
Line errored seconds (LES) is a second in which one or more code
violations or one or more LOS defects occurred.
|
C-bit Errored Secs
|
C-bit errored seconds (CES) is a second with one or more C-bit code
violations (CCV), one or more out-of-frame defects, or a detected
incoming AIS. This gauge is not incremented when UASs are counted.
|
C-bit Severely Errored Secs
|
C-bit severely errored seconds (CSES) is a second with 44 or more CCVs,
one or more out-of-frame defects, or a detected incoming AIS. This gauge
is not incremented when UASs are counted.
|