1 port OC-48/STM-16 or 4 port OC-12/OC-3 / STM-1/STM-4 + 12 port T1/E1 + 4 port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (ASR 920 Series Routers)

Information About T1 Interfaces

The following sections provide information about T1 interfaces.

Overview of T1 Interfaces

The 12-port T1 interface module on CEM line card supports generic single or dual-port T1 trunk interfaces for voice, data, and integrated voice or data applications.

Configuring the Controller

To configure T1 interface, use the following commands:

enable
configure terminal
controller mediatype 0/4/0
mode t1
exit
controller t1 0/4/0
clock source internal
framing esf
cablelength short 110
linecode b8zs
no shutdown
exit

Verifying Controller Configuration

Use show controllers command to verify the controller configuration:

#show controller t1 0/4/0
T1 0/4/0 is up
  Applique type is  
  Cablelength is short 110                                                      
  No alarms detected.                                                           
  alarm-trigger is not set                                                      
  Soaking time: 3, Clearance time: 10                                           
  AIS State:Clear  LOS State:Clear  LOF State:Clear                             
  Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.         
  BER thresholds:  SF = 10e-3  SD = 10e-6                                       
  Data in current interval (230 seconds elapsed):                               
   Near End                                                                     
     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 Unavailable Secs 
     0 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     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 Unavailable Secs 
     0 Path Failures                                                            
  Data in Interval 1:                                                           
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins             
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End Data                                                                 
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins              
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures                                                            
  Total Data (last 1 15 minute intervals):                                      
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins,            
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,             
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures

Performance Monitoring

The performance monitoring result displays the statistics or error count generated on the TDM lines for DS1.

To view the performance monitoring error details, use the show controller t1 command:

PE2#show controller t1 0/4/0
T1 0/4/0 is up
  Applique type is  
  Cablelength is short 110                                                      
  No alarms detected.                                                           
  alarm-trigger is not set                                                      
  Soaking time: 3, Clearance time: 10                                           
  AIS State:Clear  LOS State:Clear  LOF State:Clear                             
  Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.         
  BER thresholds:  SF = 10e-3  SD = 10e-6                                       
  Data in current interval (230 seconds elapsed):                               
   Near End                                                                     
     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 Unavailable Secs 
     0 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     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 Unavailable Secs 
     0 Path Failures                                                            
  Data in Interval 1:                                                           
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins             
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End Data                                                                 
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins              
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures                                                            
  Total Data (last 1 15 minute intervals):                                      
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins,            
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,             
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures

Table 1. Feature History
Feature Name	Release Information	Description
GR-820-CORE specific Performance Monitoring	Cisco IOS XE Bengaluru 17.5.1	The show controller tabular enables you to view the performance monitoring details in tabular form as per GR-820-Core standards.

To view the performance monitoring details on T1 interface, use the show controller t1 tabular command:

Router#show controllers t1 0/7/0 tabular
T1 0/7/0 is down
  Applique type is 
  Receiver has loss of signal.
  alarm-trigger is not set
  Soaking time: 3, Clearance time: 10
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  BER thresholds:  SF = 10e-3  SD = 10e-6
  Near End Data
  INTERVAL     CV-L   ES-L   CV-P   ES-P  SES-P  CSS-P  SAS-P  UAS-P   FC-P
  10:48-10:57     0    530      0      0      0      0      0    530      1
  Far End Data
  INTERVAL     ES-LFE  ES-PFE  SES-PFE  SEFS-PFE  CSS-PFE  UAS-PFE  FC-PFE
  10:48-10:57       0       0        0         0        0        0       0
PE2#

Configuring Structure-Agnostic TDM over Packet - T1 Interfaces

To configure Structure-Agnostic TDM over Packet (SAToP):

enable
configure terminal
controller t1 0/4/0
cem-group 0 unframed
exit
interface cem 0/4/0
cem 0
xconnect 10.2.2.2 10000 encapsulation mpls
exit

Verifying CEM Configuration for SAToP

Use the following command to verify the CEM configuration for T1 interfaces:

#show cem ci interface cem 0/4/0

CEM 0/4/0, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Mode :T1, CEM Mode: T1-SAToP
Controller state: up, T1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8
Dejitter: 6 (In use: 0)
Payload Size: 192
Framing: Unframed
CEM Defects Set
None

Signalling: No CAS
RTP: No RTP

Ingress Pkts:    6463477              Dropped:             0
Egress Pkts:     5132190              Dropped:             0

CEM Counter Details
Input Errors:    0                    Output Errors:       0
Pkts Missing:    0                    Pkts Reordered:      0
Misorder Drops:  0                    JitterBuf Underrun:  0
Error Sec:       0                    Severly Errored Sec: 0
Unavailable Sec: 0                    Failure Counts:      0
Pkts Malformed:  0                    JitterBuf Overrun:   0
Generated Lbits: 0                    Received Lbits:      0
Generated Rbits: 0                    Received Rbits:      0

Framed Structure-Agnostic TDM over Packet (SAToP)

Framed Structure-Agnostic TDM over Packet (SAToP) is required to detect an incoming AIS alarm in the DS1 SAToP mode. An AIS alarm indicates a problem with the line that is upstream from the DS1 network element connected to the interface. Framed SAToP further helps in the detection of a packet drop.

In case of unframed mode of SAToP, data received from the Customer Edge (CE) device is transported ove the pseudowire. If the Provider Edge (PE) device receives a Loss of Frame (LOF) signal or Remote Alarm Indication (RAI) signal from a CE, the PE can only transmit the signal that is detected by the CE device. With the introduction of Framed SAToP, when the PE device receives the LOF or RAI signal, the PE device can detect the alarm for SAToP. Thus, the alarm can be detected earlier in the network. This helps in enhanced performance.

Note

Framing type should be maintained same in all routers end to end.

Difference between Framed and Unframed SAToP:

For unframed SAToP, the incoming signal is transmitted to the far end. This signal is not analyzed by the PE device. Hence, no alarm is reported.
For framed SAToP, the incoming signal is analyzed but is not terminated. If a LOF or RAI signal is detected, the remote PE detects the signals and transmits towards the remote CE.

Difference between Framed SAToP and CESoP:

Table 2. Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on LOF Alarm
Modes	Alarm Detected at PE	Controller Status at PE	Alarm Detected at CE (Remote)	Framing Bits Generationat PE (Remote)	Framing Bits Terminated at PE (Remote)
Unframed SAToP	None	Up	LOF	No	No
Framed SAToP	LOF	Down (Data path remians up)	AIS¹ ²	Yes	No
CESOP	LOF	Down (Data path remians up)	AIS	Yes	Yes

¹ AIS—Cisco IOS XE Amsterdam 17.3.1 to later releases

² LOF—Support until Cisco IOS XE Amsterdam 17.2.1

Table 3. Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on RDI Alarm
Modes	Alarm Detected at PE	Controller Status at PE	Alarm Detected at CE (Remote)	Framing Bits Generation at PE (Remote)	Framing Bits Terminated at PE (Remote)
Unframed SAToP	None	Up	RDI	No	No
Framed SAToP	RDI	Down (data path remains up)	RDI	No	No
CESOP	RDI	Down (data path remains up)	RDI	M-bit is set into control word	Yes

Table 4. Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on AIS alarm
Modes	Alarm Detected at PE	Controller Status at PE	Alarm Detected at CE (Remote)	Framing Bits Generation at PE (Remote)	Framing Bits Terminated at PE (Remote)
Unframed SAToP	AIS	Down (data path remains up)	AIS	No	No
Framed SAToP	AIS	Down (data path remains up)	AIS	No	No
CESOP	AIS	Down (data path remains up)	AIS	L-bit is set into control word	Yes

Remote Loopback from CE to PE Detection:

Framed SAToP does not detect any loopback.


	Loopback Detected at PE	Controller Status at PE (Remote)	Controller Status at CE (Remote)
Unframed SAToP	No	Not in Loopback	Loopback
Framed SAToP	No	Not in Loopback	Loopback
CESOP	Yes	Loopback	Not in loopback

Configuring Framed SAToP

Note

Framing type should be maintained same in all routers end to end.

To configure Framed Structure-Agnostic TDM over Packet (SAToP):

enable
configure terminal
controller t1 0/4/0
framing esf
cem-group 0 framed
exit
interface cem 0/4/0
cem 0
xconnect 10.2.2.2 10000 encapsulation mpls
exit

Verifying CEM Configuration for Framed SAToP

Use show cem ci interface to verify CEM configuration for Framed SAToP:

#show cem ci interface cem 0/4/0

CEM 0/4/0, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE
Mode :T1, CEM Mode: T1-SAToP
Controller state: up, T1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8
Dejitter: 6 (In use: 0)
Payload Size: 192
Framing: Framed SAToP
CEM Defects Set
None

Signalling: No CAS
RTP: No RTP

Ingress Pkts:    6463477              Dropped:             0
Egress Pkts:     6463477              Dropped:             0

CEM Counter Details
Input Errors:    0                    Output Errors:       0
Pkts Missing:    0                    Pkts Reordered:      0
Misorder Drops:  0                    JitterBuf Underrun:  0
Error Sec:       0                    Severly Errored Sec: 0
Unavailable Sec: 0                    Failure Counts:      0
Pkts Malformed:  0                    JitterBuf Overrun:   0
Generated Lbits: 0                    Received Lbits:      0
Generated Rbits: 0                    Received Rbits:      0

Troubleshooting T1 Controllers

You can use the following methods to troubleshoot the T1 controllers:

Running Bit Error Rate Testing

Bit error rate testing (BERT) is supported on T1 interfaces.

The interface module contains onboard BERT circuitry. With this, the interface module software can send and detect a programmable pattern that is compliant with CCITT/ITU O.151, O.152, O.153 pseudo-random and repetitive test patterns. BERT allows you to test cables and signal problems in the field.

When running a BERT test, your system expects to receive the same pattern that it is transmitting. To help ensure this, two common options are available:

Use a loopback somewhere in the link or network
Configure remote testing equipment to transmit the same BERT test pattern at the same time

The total number of error bits received, and the total number of bits received are available for analysis. You can select the testing period from 1 minute to 24 hours, and you can also retrieve the error statistics anytime during the BERT test.

BERT is supported in two directions:

Line - supports BERT in TDM direction
System - supports BERT in PSN direction

Note

Before starting system side BERT, you must configure CEM. When the BERT is configured towards system direction, it internally loopbacks the TDM side. BERT in system direction is not supported for framed SAToP.

BERT Patterns on T1 or E1 Interface Module

Bit error rate testing (BERT) is supported on T1 or E1 interfaces. You can run BERT tests on 16 controllers out of 48T1 or E1 controllers at a time.

Table 5. Feature History
Feature Name	Release Information	Description
Support for all 0s and 1s BERT Patterns	Cisco IOS XE Bengaluru 17.4.1	Support for all 0s and 1s BERT patterns on T1 or E1 interfaces.

The BERT patterns on the 48-port T1 or E1 interface module are :

Table 6. BERT Pattern Descriptions
Keyword	Description
All 1s ³	Pseudo-random binary test pattern consisting of all 1’s that is used to test alternating line volt and repeaters.
All 0s	Pseudo-random binary test pattern consisting of all 0’s that is used for test line coding.
2^15-1 O.151	Pseudo-random O.151 test pattern consisting of a maximum of 14 consecutive zeros and 15 consecutive ones. The length of this pattern is 32,768 bits.
2^20-O.151	Pseudo-random O.151 test pattern consisting of a maximum of 19 consecutive zeros and 20 consecutive ones. The length of this pattern is 1,048,575 bits.
2^20-O.153	Pseudo-random O.153 test pattern consisting of a maximum of 19 consecutive zeros and 20 consecutive ones. The length of this pattern is 1,048,575 bits.
2^23-1 O.151	Pseudo-random 0.151 test pattern consisting of a maximum of 22 consecutive zeros and 23 consecutive ones. The length of this pattern is 8,388,607 bits.
2^9 ⁴	Pseudo-random binary test pattern consisting of a maximum of eight consecutive zeros and nine consecutive ones. The length of this pattern is 511 bits.
2^11 ⁵	Pseudo-random binary test pattern consisting of a maximum of ten consecutive zeros and eleven consecutive ones. The length of this pattern is 2048 bits.

³ Starting with Cisco IOS XE Bengaluru 17.4.1, All Is are supported.

⁴ Starting with Cisco IOS XE Gibraltar 16.12.1, 2^9 is supported on the T1 mode.

⁵ Starting with Cisco IOS XE Fuji 16.9.5, 2^11 is supported on the T1 mode.

Note

If All 1's BERT pattern is tested on the system side, then ensure that you need to start all 1's pattern from both sides of the end points.

Configuring BERT on one side and loopback on other side of the end points is not supported. The router treats all 1's pattern as AIS alarm and BERT will not come in sync with the other side configuration of the end point.

Configuring BERT

Before you run BERT test, you must configure card type and controller.

To run a BERT on T1 interface, perform the following tasks in global configuration mode.

enable
configure terminal
controller t1 0/4/0
bert pattern 2^11 interval 5 direction [line | system]
exit

Verifying BERT Configuration for SAToP

Use the following command to verify the BERT configuration for T1 interfaces:

Router# show controllers t1 0/4/0
T1 0/4/0 is up.
Applique type is  
Cablelength is short 110
DSX1 BERT pattern : 2^11
DSX1 BERT direction : Line
DSX1 BERT sync : no sync
DSX1 BERT sync count : 0
DSX1 BERT interval : 5
DSX1 BERT time remain : 2
DSX1 BERT total errs : 0
DSX1 BERT total k bits: 0
DSX1 BERT errors (last): 0
DSX1 BERT k bits (last): 0
Last clearing of BERT counters never
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is unframed, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (230 seconds elapsed):                               
   Near End                                                                     
     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 Unavailable Secs 
     0 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     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 Unavailable Secs 
     0 Path Failures                                                            
  Data in Interval 1:                                                           
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins             
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End Data                                                                 
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins              
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures                                                            
  Total Data (last 1 15 minute intervals):                                      
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins,            
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,             
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures

Loopback on T1 Interfaces

Loopback is supported on both unframed and framed modes. You can use the following loopback on the T1 interfaces.

Loopback

Description

loopback diag

Loops the outgoing transmit signal back to the receive signal. This is done using the diagnostic loopback feature in the interface module’s framer. The interface transmits AIS in this mode. Set the clock source command to internal for this loopback mode.

loopback local

Loops the incoming receive signal back out to the transmitter. You can specify whether to use the line or payload.

loopback local line

The incoming signal is looped back in the interface using the framer’s line loopback mode. The framer does not reclock or reframe the incoming data. All incoming data is received by the interface driver.

loopback local payload

Loops the incoming signal back in the interface using the payload loopback mode of the framer. The framer reclocks and reframes the incoming data before sending it back out to the network.

Note

Loopback Local Payload support is available only when framing is ESF.

loopback network line

Loops the incoming signal back in the interface module using the line loopback mode of the framer. The framer does not reclock or reframe the incoming data. All incoming data is received by the interface module driver.

Configuring Loopback

Before you configure loopback, you must configure the controller and the CEM.

To set a loopback local on the T1 interface, perform the following tasks in global configuration mode:

 
enable
configure terminal
controller t1 0/4/0
loopback local line
exit

To set a loopback diag on the T1 interface, perform the following tasks in global configuration mode:

 
enable
configure terminal
controller t1 0/4/0
loopbackdiag
exit

Note

To remove a loopback, use the no loopback command.

Note

Network payload configuration is not supported on SAToP. To configure loopback network payload when SAToP is configured, you need to remove the CEM configuration and then configure the loopback.

Loopback Remote on T1 Interfaces

The remote loopback configuration attempts to put the far-end T1 into a loopback.

The remote loopback setting loops back the far-end at line or payload, using IBOC (in-band bit-orientated CDE) or the ESF loopback codes to communicate the request to the far-end.

For releases later than Cisco IOS XE Fuji 16.8.x, we recommend that you use ESF loopback codes with ESF framing and IBOC loopback codes with SF framing.

Restrictions for Loopback Remote

E1 loopback remote is not supported until Cisco IOS XE 16.9.4 Fuji Release. Starting from Cisco IOS XE Fuji 16.9.5 release, E1 loopback remote is supported.
Loopback remote is not supported when cem-group is configured under T1 until Cisco IOS XE 16.9.4 Fuji Release.
IBOC loopcode configuration is not supported when CESoP or SATOP (framed or unframed) is configured.
ESF loopcode configuration is not supported when SAToP is configured.

Configuring Loopback Remote on a T1 Interface Module

To set T1 loopback remote iboc fac1/fac2/csu for DS1, perform the following tasks in global configuration mode:

enable
configure terminal
controller t1 0/1/1
loopback remote iboc {fac1 | fac2 | csu}
exit

To set T1 loopback remote esf line csu/payload on the DS1 interface, perform the following tasks in global configuration mode:

enable
configure terminal
controller t1 0/1/1
loopback remote esf {line csu | payload}
exit

Note

loopback remote esf line niu is not supported.

Verifying the Loopback Remote Configuration

Use the following command to check the loopback remote configuration:

router# show running-config | sec 0/1/1
controller T1 0/1/10
 threshold sd-ber 6
 threshold sf-ber 3
 framing sf
 linecode b8zs
 cablelength short 110
 loopback remote iboc fac1

Use the following command to verify the loopback remote configuration:

router# show controller t1 0/1/1
T1 0/1/1 is up (NIU FAC1 Line Loopback with IBOC)
  Currently in Inband Remotely Line Looped
  Applique type is 
  Cablelength is short 110
  Receiver has no alarms.
  alarm-trigger is not set
Soaking time: 3, Clearance time: 10                                           
  AIS State:Clear  LOS State:Clear  LOF State:Clear                             
  Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.         
  BER thresholds:  SF = 10e-3  SD = 10e-6                                       
  Data in current interval (230 seconds elapsed):                               
   Near End                                                                     
     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 Unavailable Secs 
     0 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     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 Unavailable Secs 
     0 Path Failures                                                            
  Data in Interval 1:                                                           
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins             
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End Data                                                                 
     0 Line Code Violations, 0 Path Code Violations                             
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins              
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures                                                            
  Total Data (last 1 15 minute intervals):                                      
   Near End                                                                     
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 0 Fr Loss Secs, 14 Line Err Secs, 0 Degraded Mins,            
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 15 Unavailable Secs
     1 Path Failures, 0 SEF/AIS Secs                                            
   Far End                                                                      
     0 Line Code Violations, 0 Path Code Violations,                            
     0 Slip Secs, 4 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,             
     4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 
     0 Path Failures

Associated Commands

The commands used to configure the Interfaces.


Commands	URL
cem-group	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c1.html#wp2440628600
payload-size dejitter-buffer	https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-o1.html#wp3946673156
class cem	https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c1.html#wp2169323859
controller t1/e1	https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c2.html#wp1472647421
xconnect	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-t2.html#wp8578094790
linecode	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-l1.html#wp2312535965
framing	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-f1.html#wp2853515177
clock source	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c2.html#wp6081785140
cable length	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c1.html#wp2492964151
bert pattern	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-a1.html#wp3620978929
channelized	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c1.html#wp7026926390
loopback	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-l1.html#wp1033903426
show controller t1	http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-s3.html#wp2149471094

Bias-Free Language

Book Title

1 port OC-48/STM-16 or 4 port OC-12/OC-3 / STM-1/STM-4 + 12 port T1/E1 + 4 port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (ASR 920 Series Routers)

Chapter Title

Configuring T1 Interfaces

Results

Chapter: Configuring T1 Interfaces

Configuring T1 Interfaces

Information About T1 Interfaces

Overview of T1 Interfaces

Configuring the Controller

Verifying Controller Configuration

Performance Monitoring

Configuring Structure-Agnostic TDM over Packet - T1 Interfaces

Verifying CEM Configuration for SAToP

Framed Structure-Agnostic TDM over Packet (SAToP)

Configuring Framed SAToP

Verifying CEM Configuration for Framed SAToP

Troubleshooting T1 Controllers

Running Bit Error Rate Testing

BERT Patterns on T1 or E1 Interface Module

Configuring BERT

Verifying BERT Configuration for SAToP

Loopback on T1 Interfaces

Configuring Loopback

Loopback Remote on T1 Interfaces

Restrictions for Loopback Remote

Configuring Loopback Remote on a T1 Interface Module

Verifying the Loopback Remote Configuration

Associated Commands

Was this Document Helpful?

Contact Cisco