T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series)

Unknown

PDF - Complete Book (2.08 MB)

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) - Overview of the T1 or E1 Interface Module [Cisco Network Convergence System 4200 Series] - Cisco

• Google Docs
• Google Drive
• Download [pdf]
• Document:
  • References

File Info : application/pdf, 50 Pages, 2.08MB

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series)
First Published: 2021-03-26 Last Modified: 2022-04-11
Americas Headquarters
Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000
800 553-NETS (6387) Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on standards documentation, or language that is used by a referenced third-party product.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
© 2022 Cisco Systems, Inc. All rights reserved.

CONTENTS

CHAPTER 1 CHAPTER 2 CHAPTER 3
CHAPTER 4

Preface 1 Document Organization 1 Related Documentation 2
Feature History 3
Overview of the T1 or E1 Interface Module 5 Restrictions for Configuring T1 or E1 Interfaces 6 Circuit Emulation 7 Overview of CEM Pseudowire 7 Configuring Pseudowire 7 Framed Structure-Agnostic TDM over Packet (SAToP) 7 Circuit Emulation Service over Packet-Switched Network 9 Restrictions for CESoPSN on T1 Interface 9
Configuring T1 or E1 Interfaces 11 Setting the Card Type 11 Configuring the Controller 11 Verifying the Controller Configuration 13 Configuring Structure-Agnostic TDM over Packet - T1/E1 Interfaces 13 Verifying CEM Configuration for SAToP 14 Configuring Framed SAToP 14 Verifying Framed SAToP Configuration 15 Verifying CEM Statistics for Framed SAToP 15 Verifying CEM Statistics for SAToP 16 Configuring CEM Group for SAToP for T1 Interfaces 17

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) iii

Contents

CHAPTER 5 CHAPTER 6
CHAPTER 7

Configuring CEM Group for CESoPSN on T1 Interface 18 Verifying CEM for CESoPSN on T1 Interface 18
Configuring DS1 Local Connet 19 Verifying DS1 Local Connect 20
Monitoring the T1 or E1 Interface Module 21 Performance Monitoring 21
Troubleshooting the T1 or E1 Interface Module 25 Overview of BERT 25 BERT Restrictions 26 BERT for SAToP 26 Configuring BERT for SAToP 26 Verifying BERT Configuration for SAToP 27 BERT for CESoPSN 28 Configuring BERT for CESoPSN 28 Verifying BERT Configuration for CESoPSN 28 Loopback on T1 or E1 Interfaces 30 Configuring Loopback 30 Loopback Remote on T1 Interfaces 31 Restrictions for Loopback Remote 31 Configuring Loopback Remote on a T1 Interface Module 32 Verifying the Loopback Remote Configuration 32
Card Protection for T1 or E1 35 Card Protection 35 Y Cable 36 Card Protection Switchover 36 Alarm Based Switchover 37 Restrictions 37 Supported Features on Interface Module 38 How to Configure Card Protection for T1 or E1 38 Configuring T1/E1 Card Protection 38 Configuring Revertive Mode 39

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) iv

CHAPTER 8

Verification of T1/E1 Card Protection Configuration 40 Configuring Maintenance Commands 40
Priority Table 40 Associated Commands 41
Additional References 43 Linecode Configuration and Supported Patterns 43

Contents

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) v

Contents
T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) vi

1 C H A P T E R

Preface

This guide provides an overview and explains how to configure the various features for the T1 or E1 CEM Interface Module. This document is applicable for the following interface modules:
Table 1: Supported Interface Module

Interface Module 48-port T1/E1 Interface module

Part Number · NCS4200-48T1E1-CE

Mode T1/E1

1-port OC48/ STM-16 or 4-port OC-12/OC-3 / STM-1/STM-4 + 12-Port T1/E1 + 4-Port T3/E3 CEM Interface Module

· NCS4200-3GMS

Circuit Emulation (CEM) is a technology that provides a protocol-independent transport over IP/MPLS networks. It enables proprietary or legacy applications to be carried transparently to the destination, similar to a leased line.
· Document Organization, on page 1 · Related Documentation, on page 2

Document Organization
Chapter Overview of the T1/E1 Interface Module
Configuring the T1/E1 Interface Module Monitoring the Interface Module

Description
Provides a high-level overview of the interface module. Also provides additional information such as restrictions, benefits etc..
Provides information about how to configure the interface module.
Provides information on monitoring features for the interface module.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 1

Related Documentation

Preface

Chapter Troubleshooting the Interface Module
Additional References

Description
Describes features that you can use to troubleshoot the operation of interface module.
Provides information on additonal features, technical details.

Related Documentation
· Alarm Configuring and Monitoring Guide · CEM Generic Guide · T3 or E3 CEM Interface Module Configuration Guide

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 2

2 C H A P T E R

Feature History

The following table lists the new features supported in the 48-Port T1/E1 CEM Interface Module Configuration Guide in Cisco IOS XE 17 releases., on Cisco NCS 4201 and Cisco NCS 4202 routers.

Feature

Description

Cisco IOS XE Cupertino 17.8.1

NCS4200-48T1E1-CE The router supports the following features for the 48-Port T1/E1 Circuit Emulation support in NCS4202 (CEM) interface module:
· Basic mode, and T1 or E1 controller required configurations
· CEM clocking, ACR, and DCR
· CEM pseudowires such as Structure-Agnostic TDM over Packet (SATOP) and Circuit Emulation over Packet-Switched Network (CESoPSN)
· BERT, loopback, and alarms
· Performance monitoring

The support for the interface module provides cost-effective delivery of CEM over a packet-based network (MPLS).

Cisco IOS XE Bengaluru 17.5.1

GR-820-CORE Performance Monitoring

The show controller tabular command enables you to view the performance monitoring details in tabular form as per GR-820-Core standards.

Cisco IOS XE Bengaluru 17.4.1

Support for all 0s and 1s BERT Patterns

Support for all 0s and 1s BERT patterns on T1 or E1 interfaces.

The following table lists the new and modified features supported in the 48-Port T1/E1 CEM Interface Module Configuration Guide in Cisco IOS XE 17 releases., on Cisco NCS 4206 and Cisco NCS 4216 routers.

Feature

Description

Cisco IOS XE Bengaluru 17.5.1

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 3

Feature History

Feature
GR-820-CORE Performance Monitoring

Description
The show controller tabular command enables you to view the performance monitoring details in tabular form as per GR-820-Core standards.

Cisco IOS XE Bengaluru 17.4.1

Support for all 0s and 1s BERT Patterns

Support for all 0s and 1s BERT patterns on T1 or E1 interfaces.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 4

3 C H A P T E R

Overview of the T1 or E1 Interface Module

Table 2: Feature History

Feature Name

Release Information

NCS4200-48T1E1-CE support in Cisco IOS XE Cupertino 17.8.1 NCS4202

Description
The router supports the following features for the 48-Port T1/E1 Circuit Emulation (CEM) interface module:
· Basic mode, and T1 or E1 controller required configurations
· CEM clocking, ACR, and DCR
· CEM pseudowires such as Structure-Agnostic TDM over Packet (SATOP) and Circuit Emulation over Packet-Switched Network (CESoPSN)
· BERT, loopback, and alarms
· Performance monitoring

The support for the interface module provides cost-effective delivery of CEM over a packet-based network (MPLS).

The T1 or E1 interface module delivers T1 or E1 connectivity on the router with the RSP3 module. The module can be software configured as either T1 mode or E1 mode per interface module The module provides physical connectivity using a single high-density connector and requires a breakout cable and patch panel for individual port connections.
The T1 or E1 interface module supports the following modes:
· T1

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 5

Restrictions for Configuring T1 or E1 Interfaces

Overview of the T1 or E1 Interface Module

· E1

Note Mixing T1 and E1 ports on the same interface module is not supported.

CEM configurations are supported on different modes on the interface module. The troubleshooting, monitoring, and redundancy features are supported on the module. The module can be clocked from a line or from an internal clock source. The table describes the configurations and features for the modes that are supported on the T1 or E1 interface module.
Table 3: Configurations on T1 or E1 Interface Module

Required Configurations

T1

E1

Mode

Yes

Yes

Internal/Line Clock Source

Yes

Yes

ACR/DCR Clock

Yes

Yes

CEM Configurations

Structure-Agnostic TDM over Packet (SATOP) Yes

Yes

(Framed/Unframed)

Circuit Emulation over Packet-Switched Network Yes

Yes

(CESoPSN)

Troubleshooting Features

Bit Error Rate Testing (BERT)

Yes

Yes

Loopback

Yes

Yes

Monitoring Features

Performance Monitoring

Yes

Yes

· Restrictions for Configuring T1 or E1 Interfaces, on page 6 · Circuit Emulation, on page 7 · Overview of CEM Pseudowire, on page 7 · Framed Structure-Agnostic TDM over Packet (SAToP), on page 7 · Circuit Emulation Service over Packet-Switched Network, on page 9

Restrictions for Configuring T1 or E1 Interfaces
· You can configure CEM to support serial interface configuration.
· The card can be configured either in the T1 or E1 mode. A combination of T1 and E1 ports is not supported.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 6

Overview of the T1 or E1 Interface Module

Circuit Emulation

Circuit Emulation
Circuit Emulation (CEM) is a technology that provides a protocol-independent transport over IP/MPLS networks. It enables proprietary or legacy applications to be carried transparently to the destination, similar to a leased line. CEM provides a bridge between a Time-Division Multiplexing (TDM) network and Multiprotocol Label Switching (MPLS) network. The router encapsulates the TDM data in the MPLS packets and sends the data over a CEM pseudowire to the remote Provider Edge (PE) router. As a result, CEM functions as a physical communication link across the packet network. The router supports the pseudowire type that utilizes CEM transport: Structure-Agnostic TDM over Packet (SAToP) and Circuit Emulation Service over Packet-Switched Network (CESoPSN). L2VPN over IP/MPLS is supported on the interface modules.
Note We recommend that you configure the controller in the administratively up mode. Configuration under the administratively down mode is not recommended and it might cause configuration errors.
Overview of CEM Pseudowire
Pseudowires manage encapsulation, timing, order, and other operations in order to make it transparent to users. The pseudowire tunnel acts as an unshared link or circuit of the emulated service. CEM is a way to carry TDM circuits over packet switched network. CEM embeds the TDM circuits into packets, encapsulates them into an appropriate header, and then sends that through Packet Switched Network. The receiver side of CEM restores the TDM circuits from packets.
Configuring Pseudowire
Cisco Pseudowire Emulation Edge-to-Edge (PWE3) allows you to transport traffic by using traditional services such as T1/E1 over a packet-based backhaul technology such as MPLS or IP. A pseudowire (PW) consists of a connection between two provider edge (PE) chassis that connects two attachment circuits (ACs), such as T1/E1 or T3 /E3 links.
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.
T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 7

Framed Structure-Agnostic TDM over Packet (SAToP)

Overview of the T1 or E1 Interface Module

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

Difference between Framed and Unframed SAToP:
1. 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.
2. 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 4: Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on LOF Alarm

Modes

Alarm Detected Controller Status Alarm Detected Framing Bits Framing Bits

at PE

at PE

at CE (Remote) Generationat PE Terminated at PE

(Remote)

(Remote)

Unframed

None

Up

LOF

No

No

SAToP

Framed SAToP LOF

Down (Data path AIS12

Yes

No

remians up)

CESOP

LOF

Down (Data path AIS

Yes

Yes

remians up)

1 AIS--Cisco IOS XE Amsterdam 17.3.1 to later releases 2 LOF--Support until Cisco IOS XE Amsterdam 17.2.1

Table 5: Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on RDI Alarm

Modes

Alarm Detected Controller Status Alarm Detected Framing Bits Framing Bits

at PE

at PE

at CE (Remote) Generation at PE Terminated at PE

(Remote)

(Remote)

Unframed

None

Up

RDI

No

No

SAToP

Framed SAToP RDI

Down (data path RDI

No

No

remains up)

CESOP

RDI

Down (data path RDI remains up)

M-bit is set into Yes control word

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 8

Overview of the T1 or E1 Interface Module

Circuit Emulation Service over Packet-Switched Network

Table 6: Behaviour Difference between Unframed SAToP, Framed SAToP, and CESoP on AIS alarm

Modes

Alarm Detected Controller Status Alarm Detected Framing Bits Framing Bits

at PE

at PE

at CE (Remote) Generation at PE Terminated at PE

(Remote)

(Remote)

Unframed

AIS

Down (data path AIS

No

No

SAToP

remains up)

Framed SAToP AIS

Down (data path AIS

No

No

remains up)

CESOP

AIS

Down (data path AIS remains up)

L-bit is set into Yes control word

Remote Loopback from CE to PE Detection: Framed SAToP does not detect any loopback.

Loopback Detected at PE Controller Status at PE (Remote)

Unframed SAToP

No

Not in Loopback

Framed SAToP

No

Not in Loopback

CESOP

Yes

Loopback

Controller Status at CE (Remote) Loopback
Loopback
Not in loopback

Circuit Emulation Service over Packet-Switched Network
CESoPSN is a method for encapsulating structured (NxDS0) TDM signals as pseudowires over packet switching networks.
Restrictions for CESoPSN on T1 Interface
· The maximum number of CEM interface supported is 192. · DS0 loopback is not supported on the T1 interface. · Alarm forwarding is not supported on the T1 interface. · Card protection is not supported on the T1 interface.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 9

Restrictions for CESoPSN on T1 Interface

Overview of the T1 or E1 Interface Module

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 10

4 C H A P T E R
Configuring T1 or E1 Interfaces
This chapter provides the information about how to configure a T1 or E1 interface. · Setting the Card Type, on page 11 · Configuring the Controller, on page 11 · Configuring Structure-Agnostic TDM over Packet - T1/E1 Interfaces, on page 13 · Configuring CEM Group for CESoPSN on T1 Interface, on page 18 · Configuring DS1 Local Connet, on page 19
Setting the Card Type
To set the card type for the T1/E1 interfaces, complete these steps:
enable configure terminal card type t1 0 1 exit
Configuring the Controller
To configure T1 interface, use the following commands:
enable configure terminal controller t1 0/1/0 clock source internal framing esf cablelength short 110 linecode b8zs no shut exit
Note For T1 interface, the default frame mode is Extended Super Frame (ESF).
To configure E1 interface, use the following commands:
T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 11

Configuring the Controller

Configuring T1 or E1 Interfaces

enable configure terminal controller e1 0/1/0 clock source internal framing crc4 linecode hdb3 no shut exit

Note For E1 interface, the default frame mode is Cyclic Redundancy Check 4 (CRC4).

Staring with Cisco IOS XE Cupertino 17.7.1, the cable length short values are modified for the following interface modules:
· NCS4200-48T1E1-CE ·
Table 7: Cable Length Short Values

Cable Length Short (in ft) 110 220 330 440 550

Range (in ft) 0­133 134­266 267­399 400-533 534­655

For the following interface modules, the cable length short values remain the same:
Table 8: IM Port Support - Cable Length Short

Port Supported T1 Port

IM NCS4200-8E1T1-CE

Table 9: Cable Length Short Values - IMs
Cable Length Short (in ft) 110 220 330 440 550

Range (in ft) 0­110 111­220 221­330 331­440 441­550

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 12

Configuring T1 or E1 Interfaces

Verifying the Controller Configuration

Verifying the Controller Configuration
Use the show controllers command to verify the controller configuration:
Router# show controller e1 0/2/0
E1 0/2/0 is up. Applique type is ASR903-48T1E1-CE
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
Use the show platform command to verify the router information:
Configuring Structure-Agnostic TDM over Packet - T1/E1 Interfaces
To configure Structure-Agnostic TDM over Packet (SAToP), use the following commands:
enable

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 13

Verifying CEM Configuration for SAToP

Configuring T1 or E1 Interfaces

configure terminal controller t10/1/0 cem-group 0 unframed exit

Note To configure SAToP, the framing mode for the port is set to unframed.

Verifying CEM Configuration for SAToP
Use the following command to verify the CEM configuration for T1/E1 interfaces:

Router# show cem circuit interface CEM 0/1/0

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

Signalling: No CAS RTP: No RTP

Ingress Pkts: Egress Pkts:

475471 475471

Dropped:

0

Dropped:

0

CEM Counter Details

Input Errors: 0

Pkts Missing: 0

Misorder Drops: 0

Error Sec:

0

Unavailable Sec: 0

Pkts Malformed: 0

Output Errors:

0

Pkts Reordered:

0

JitterBuf Underrun: 0

Severly Errored Sec: 0

Failure Counts:

0

JitterBuf Overrun: 0

Configuring Framed SAToP

Note Framing type should be maintained same in all routers end to end.
To configure framed SAToP:
enable configure terminal controller t1 0/1/0 framing esf cem-group 0 framed exit

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 14

Configuring T1 or E1 Interfaces

Verifying Framed SAToP Configuration

Verifying Framed SAToP Configuration
Use the following command to verify the CEM configuration for T1/E1 interfaces:

Router# show cem circuit interface cem 0/1/0
CEM0/1/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: 5 (In use: 0) Payload Size: 192 Framing: Framed SAToP CEM Defects Set None
Signalling: No CAS RTP: No RTP
Ingress Pkts: 7836 Dropped: 0 Egress Pkts: 7836 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
Verifying CEM Statistics for Framed SAToP
Use the following commands to verify the pseudowire configuration for SAToP:
· show cem circuit--Displays information about the circuit state, administrative state, the CEM ID of the circuit, and the interface on which it is configured. If cross connect is configured under the circuit, the command output also includes information about the attachment circuit status.

Router# show cem circuit

<0-4294967295> CEM ID

detail

Detailed information of cem ckt(s)

interface CEM Interface

summary Display summary of CEM ckts

|

Output modifiers

Router# show cem circuit

CEM Int. ID Ctrlr Admin Circuit AC -------------------------------------------------------------CEM0/1/0 1 UP UP Active UP CEM0/1/1 2 UP UP Active UP CEM0/1/2 3 UP UP Active UP CEM0/1/3 4 UP UP Active UP CEM0/1/4 5 UP UP Active UP
· show cem circuit cem-id -- Displays the detailed information about that particular circuit.

Router# show cem circuit 0 CEM0/1/2, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 15

Verifying CEM Statistics for SAToP

Configuring T1 or E1 Interfaces

Mode :T1, CEM Mode: T1-SAToP Controller state: up, T1 state: up Idle Pattern: 0xFF, Idle CAS: 0x8 Dejitter: 5 (In use: 0) Payload Size: 192 Framing: Framed SAToP CEM Defects Set None
Signalling: No CAS RTP: No RTP
Ingress Pkts: 167027103 Dropped: 0 Egress Pkts: 167027102 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

· show cem circuit summary -- Displays the number of circuits which are up or down per interface basis.

Router# show cem circuit summary

CEM Int. Total Active Inactive

--------------------------------------

CEM0/1/0 1

1

0

CEM0/1/1 1

1

0

CEM0/1/2 1

1

0

CEM0/1/3 1

1

0

CEM0/1/4 1

1

0

Verifying CEM Statistics for SAToP
Use the following commands to verify the pseudowire configuration for SAToP:
· show cem circuit--Displays information about the circuit state, administrative state, the CEM ID of the circuit, and the interface on which it is configured. If cross connect is configured under the circuit, the command output also includes information about the attachment circuit status.

Router# show cem circuit

<0-32000> CEM ID

detail

Detailed information of cem ckt(s)

interface CEM Interface

summary Display summary of CEM ckts

|

Output modifiers

Router# show cem circuit

CEM Int.

ID Line

Admin

Circuit

AC

--------------------------------------------------------------

CEM0/1/0

1 UP

UP

ACTIVE

--/--

CEM0/1/0

2 UP

UP

ACTIVE

--/--

CEM0/1/0

3 UP

UP

ACTIVE

--/--

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 16

Configuring T1 or E1 Interfaces

Configuring CEM Group for SAToP for T1 Interfaces

CEM0/1/0

4 UP

UP

ACTIVE

CEM0/1/0

5 UP

UP

ACTIVE

--/---/--

· show cem circuit cem-id -- Displays the detailed information about that particular circuit.

Router# show cem circuit 0

CEM0/1/2, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVE Controller state: up, T1 state: up Idle Pattern: 0xFF, Idle CAS: 0x8 Dejitter: 5 (In use: 0) Payload Size: 192 Framing: Unframed CEM Defects Set None

Signalling: No CAS RTP: No RTP

Ingress Pkts: Egress Pkts:

11060 11061

Dropped:

0

Dropped:

0

CEM Counter Details

Input Errors: 0

Pkts Missing: 0

Misorder Drops: 0

Error Sec:

0

Unavailable Sec: 0

Pkts Malformed: 0

Output Errors:

0

Pkts Reordered:

0

JitterBuf Underrun: 0

Severly Errored Sec: 0

Failure Counts:

0

JitterBuf Overrun: 0

· show cem circuit summary -- Displays the number of circuits which are up or down per interface basis.

Router# show cem circuit summary

CEM Int.

Total Active Inactive

--------------------------------------

CEM0/1/0

1

1

0

Configuring CEM Group for SAToP for T1 Interfaces
To configure a CEM group for SAToP.

enable configure terminal controller t1 0/1/0 cem-group 0 unframed end

Note You need metroaggrservice license to configure CEM group on the Interface Module. By deafult, metroaggressive license is enabled for NCS 4200 Series Routers.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 17

Configuring CEM Group for CESoPSN on T1 Interface

Configuring T1 or E1 Interfaces

Configuring CEM Group for CESoPSN on T1 Interface
The following section describes how to configure a CEM group for CESoPSN.
To configure xconnect over MPLS, use the following commands:
enable configure terminal controller t1 0/1/32 cem-group 0 timeslots 1-10
Configure cross-connect:
enable configure terminal interface cem 0/1/32 cem 0 xconnect 2.2.2.2 10 encapsulation mpls
Perform a similar configuration on the other end of the pseudowire.
show running-config | sec 0/1/16 controller t1 0/1/16
framing esf linecode b8zs cablelength short 110
cem-group 0 timeslots 1-10 interface CEM0/1/16
no ip address cem 0
xconnect 2.2.2.2 10 encapsulation mpls
Check for cross-connect configuration using the following command:

Router#show xconnect all | i 0/1/32

UP pri ac CE0/1/32:0(CESoPSN Basic) UP mpls 2.2.2.2:10

UP

Router#sh controllers t1 0/1/32 T1 0/1/32 is up
Applique type is NCS4200-48T1E1-CE 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, Line Code is B8ZS, Clock Source is Line.

Verifying CEM for CESoPSN on T1 Interface
Use the following commands to verify the pseudowire configuration for CESoPSN:
· show cem circuit--Displays information about the circuit state, administrative state, the CEM ID of the circuit, and the interface on which it is configured. If cross connect is configured under the circuit, the command output also includes information about the attachment circuit status.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 18

Configuring T1 or E1 Interfaces

Configuring DS1 Local Connet

· show mpls l2 vc--Displays information about the MPLS VC. · show mpls l2 vc detail--Displays detailed information about the MPLS VC.

PE1#show mpls l2 vc 10

Local intf

Local circuit

Dest address VC ID

Status

------------- -------------------------- --------------- ---------- ----------

CE0/1/32

CESoPSN Basic 0

2.2.2.2

10

UP

PE1#sh mpls l2 vc 10 detail

Local interface: CE0/1/32 up, line protocol up, CESoPSN Basic 0 up

Destination address: 2.2.2.2, VC ID: 10, VC status: up

Output interface: Te0/0/0, imposed label stack {650}

Preferred path: not configured

Default path: active

Next hop: 123.123.123.2

Create time: 00:21:25, last status change time: 00:21:25

Last label FSM state change time: 00:21:25

Signaling protocol: LDP, peer 2.2.2.2:0 up

Targeted Hello: 1.1.1.1(LDP Id) -> 2.2.2.2, LDP is UP

Graceful restart: configured and not enabled

Non stop routing: not configured and not enabled

Status TLV support (local/remote) : enabled/supported

LDP route watch

: enabled

Label/status state machine

: established, LruRru

Last local dataplane status rcvd: No fault

Last BFD dataplane

status rcvd: Not sent

Last BFD peer monitor status rcvd: No fault

Last local AC circuit status rcvd: No fault

Last local AC circuit status sent: No fault

Last local PW i/f circ status rcvd: No fault

Last local LDP TLV

status sent: No fault

Last remote LDP TLV status rcvd: No fault

Last remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 577, remote 650

Group ID: local 238, remote 276

MTU: local 0, remote 0

Remote interface description:

Sequencing: receive disabled, send disabled

Control Word: On (configured: autosense)

SSO Descriptor: 2.2.2.2/10, local label: 577

Dataplane:

SSM segment/switch IDs: 6893171/4140658 (used), PWID: 674

VC statistics:

transit packet totals: receive 0, send 0

transit byte totals: receive 0, send 0

transit packet drops: receive 0, seq error 0, send 0

Configuring DS1 Local Connet
The following section describes how to configure first segment for DS1 local connection:
enable configure terminal controller T1 0/1/0 framing unframed clock source internal linecode b8zs

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 19

Verifying DS1 Local Connect

Configuring T1 or E1 Interfaces

cablelength short 110 cem-group 0 unframed description TO_CE1_0/1/0
The following section describes how to configure second segment for DS1 local connection:
enable configure terminal controller T1 0/1/3 framing unframed clock source recovered 0 linecode b8zs cablelength short 110 cem-group 0 unframed description TO_CE1_0/1/1
The following section describes how to create a DS1 local connection:
enable configure terminal connect ds1_connect CEM0/1/0 0 CEM0/1/3 0
Verifying DS1 Local Connect
Use the following commands to verify the DS1 local connection: · show connection name--Displays information about the connection state and segment state.
Router#show connection name ds1_connect
Connection: 673 ­ ds1_connect Current State: UP Segment 1: CEM0/1/0 SATOP T1 0 up Segment 2: CEM0/1/3 SATOP T1 0 up

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 20

5 C H A P T E R
Monitoring the T1 or E1 Interface Module
This chapter provides information on monitoring the T1 or E1 interface module. Some of monitoring tools available are:
· Perfomance Monitoring
· Performance Monitoring, on page 21
Performance Monitoring
The performance monitoring result displays the statistics or error count generated on the TDM lines for DS1. To view the performance monitoring details, use the show controller command:
Router# show controllers t1 0/1/1
T1 0/1/1 is down. Applique type is ASR900-48T1E1-CE 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
T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 21

Performance Monitoring

Monitoring the T1 or E1 Interface Module

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
Router# show controllers e1 0/1/1
E1 0/1/1 is down. Applique type is ASR900-48T1E1-CE 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
The performance monitoring result displays the statistics TDM lines for DS1.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 22

Monitoring the T1 or E1 Interface Module

Performance Monitoring

Table 10: Feature History Table

Feature Name

Release Information

Description

GR-820-CORE Performance Cisco IOS XE Bengaluru

Monitoring

17.5.1

The show controller tabular command 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 controller, use the show controller t1 tabular command:
Router#show controllers t1 0/1/0 tabular

T1 0/1/0 is up

Applique type is ASR900-48T1E1-CE

Cablelength is short 110

No alarms detected.

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

09:49-10:01

0

0

0

0

0

0

0

0

0

Far End Data

INTERVAL

ES-LFE ES-PFE SES-PFE SEFS-PFE CSS-PFE UAS-PFE FC-PFE

09:49-10:01

0

0

0

0

0

0

0

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 23

Performance Monitoring

Monitoring the T1 or E1 Interface Module

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 24

6 C H A P T E R
Troubleshooting the T1 or E1 Interface Module
You can use the following methods to troubleshoot the T1 or E1 interface modules: · Bit Error Rate Testing (BERT) · Loopback
· Overview of BERT, on page 25 · Loopback on T1 or E1 Interfaces, on page 30
Overview of BERT
Bit Error Rate Testing (BERT) is used to test the integrity of the physical line. The interface contains on board BERT circuitry. With this circuitry, the interface 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. BERTs allow you to test cables and signal problems in the field. The bit error rate (BER) is determined by comparing the erroneous bits received with the total number of bits received. You can display and analyze the total number of error bits transmitted and the total number of bits received on the link. You can retrieve error statistics anytime during the BERT. Both the total number of bits and the error 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. Running a BERT Test When running a BERT test, the system expects to receive the same pattern that it transmits. 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 BERT runtime engine can be kept running until the interval completes or can be stopped by unconfiguring it anytime. Types of BERT BERT is supported in two directions:
· Line - supports BERT in TDM direction
T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 25

BERT Restrictions

Troubleshooting the T1 or E1 Interface Module

· System - supports BERT in PSN direction
BERT engines uses different BERT patterns for transmission for each mode. The supported BERT patterns on each card is described.
BERT Restrictions
· BERT is not supported on the following modes: · T3--Framing M-13, non-channelized · E3--Framing G832, channelized
· When the BERT is initiated with pattern 0s and 1s from the local end and the loopback local is applied from the far end, then the BERT syncing does not happen. Since the BERT process is asserted as LOS alarms for all 0s and AIS alarms for all 1s BERT patterns. Whereas the BERT syncing behaves properly when the BERT is initiated from both the local and the far end. For all 1s on T3 or E3, the BERT behaviour is not asserted as AIS and the BERT syncing happens as usual.
· In the unframed mode, BERT sync is not stable and may generate alarms until Cisco IOS XE Fuji 16.9.4.
Note Framing type should be similar in all routers end to end.
BERT Restrictions for Cisco IOS XE Bengaluru 17.4.1 release · When the BERT is initiated from the local end and the loopback local is applied from the far end, then BERT syncing does not happen. Since the BERT process is asserted as LOS alarms for all 0s and AIS alarms for all 1s BERT patterns. Whereas the BERT syncing behaves properly when the BERT is initiated from both the local and the far end.
BERT for SAToP
BERT is supported for both unframed and framed modes.
Configuring BERT for SAToP
Before You Begin Before you run BERT test, you must configure card type and controller. To run a BERT on T1/E1 interface, perform the following tasks in global configuration mode.
enable configure terminal controller t10/1/1 bert pattern 2^11 interval 5 direction line/system exit

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 26

Troubleshooting the T1 or E1 Interface Module

Verifying BERT Configuration for SAToP

Note To terminate a BERT test during the specified test period, use the no bert command.

Verifying BERT Configuration for SAToP
Use the following command to verify the BERT configuration for T1/E1 interfaces:

Router# show controllers t1 0/1/1

T1 0/1/1 is up.

Applique type is ASR903-48T1E1-CE

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 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,

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 27

BERT for CESoPSN

Troubleshooting the T1 or E1 Interface Module

4 Errored Secs, 0 Bursty Err Secs, 4 Severely Err Secs, 0 Unavailable Secs 0 Path Failures
You can view the results of a BERT test at the following times: · After you terminate the test using the no bert command · After the test runs completely · Anytime during the test (in real time)
BERT for CESoPSN
BERT is supported at the TDM side and pseudowire side. BERT can be used either at NxDS0 or DS1 but not together. BERT is supported on following controllers:
· T1--NxDS0, DS1 · T3--NxDS0, DS1 (channelised), clear channel DS3. · OCX--NxDS0, DS1 (channelised),DS3(channelised), clear channel DS3,STS1,STS-nc,VT-1.5,VT1.5
T1
Configuring BERT for CESoPSN
Before You Begin Before you run BERT test, you must configure card type and controller. To run a BERT on T1/E1 interface for CESoPSN, perform the following tasks in global configuration mode.
enable configure terminal controller t10/1/1 bert pattern 2^11 interval 5 direction line/system timeslots value speed exit

Note To terminate a BERT test during the specified test period, use the no bert command.

Verifying BERT Configuration for CESoPSN
Use the following command to verify the BERT configuration for CESoPSN on T1 interfaces:

Router# show controllers t1 0/1/32

T1 0/1/32 is up

Applique type is NCS4200-48T1E1-CE

Cablelength is short 110

DS0 Bert enabled on the following timeslots : 1-2

Speed : 64 kpbs

DSX1 BERT test result: (running)

DSX1 BERT pattern

: 2^15

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 28

Troubleshooting the T1 or E1 Interface Module

Verifying BERT Configuration for CESoPSN

DSX1 BERT direction : Line

DSX1 BERT sync

: sync

DSX1 BERT sync count : 1

DSX1 BERT interval : 1

DSX1 BERT time remain : 00:00:55

DSX1 BERT total errs : 0

DSX1 BERT total k bits: 512

DSX1 BERT errors (last): 0

DSX1 BERT k bits (last): 512

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 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

You can view the results of a BERT test at the following times:

· After you terminate the test using the no bert command

· After the test runs completely

· Anytime during the test (in real time)

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 29

Loopback on T1 or E1 Interfaces

Troubleshooting the T1 or E1 Interface Module

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

Restrictions · Framing type should be maintained same in all routers end to end .
· AIS alarm is not transmitted to the connected peer port with loopback local line configuration until Cisco IOS XE 16.9.4 Fuji Release.

Loopback loopback local line
loopback network line

Description
Loops the outgoing transmit signal back to the receive signal. This is done using the diagnostic loopback feature in the interface module's framer. Set the clock source command to internal for this loopback mode.
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.
Loopback network line is supported on E1 interface.

Note Starting Cisco IOS Release 16.8.1, the following loopback commands are not supported. · loopback diag · loopback local · loopback local payload
Configuring Loopback
Before You Begin 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/1/1 loopback local line exit

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 30

Troubleshooting the T1 or E1 Interface Module

Loopback Remote on T1 Interfaces

To set a loopback diag on the T1 interface, perform the following tasks in global configuration mode:
enable configure terminal controller t1 0/1/1 loopbackdiag exit
To set a loopback local on the E1 interface, perform the following tasks in global configuration mode:
enable configure terminal controller e1 0/1/1 loopback local exit
To set a loopback network on the E1 interface, perform the following tasks in global configuration mode:
enable configure terminal controller e1 0/1/1 loopback network line exit
Note To remove a loopback, use the no loopback command.
Note Network payload configuration is not supported on the port configured with 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.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 31

Configuring Loopback Remote on a T1 Interface Module

Troubleshooting the T1 or E1 Interface Module

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 ASR900-48T1E1-CE 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

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 32

Troubleshooting the T1 or E1 Interface Module

Verifying the Loopback Remote Configuration

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

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 33

Verifying the Loopback Remote Configuration

Troubleshooting the T1 or E1 Interface Module

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 34

7 C H A P T E R

Card Protection for T1 or E1

The card protection feature is supported on the following interface module:
Table 11: Supported Interface Module

Interface Module 48-port T1/E1 Interface module

Part Number · NCS4200-48T1E1-CE

In this feature, the interface module bay is protected by another interface module of the same type.
· Card Protection, on page 35 · Restrictions, on page 37 · Supported Features on Interface Module, on page 38 · How to Configure Card Protection for T1 or E1 , on page 38 · Associated Commands, on page 41

Card Protection
The Card Protection feature is required to protect traffic flow either when an interface module is out of service, when the software fails or a hardware component has issues. Because card protection is supported only on redundant interface modules, traffic is switched to the protect interface module when the active interface module does not respond, and vice-versa.

Note This feature does not require any change in the patch panel of the interface modules.
In card protection, a Y Cable is used to multiplex the signal from the patch panel to both the ports of active and protect interface modules. Both ports receive the signal, but only the active interface module transmits the signal from its port.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 35

Y Cable

Figure 1: Y Cable

Card Protection for T1 or E1

To support the Card Protection feature, the configuration on the active and protect interface module must be same. To achieve this, a virtual interface module is created with the same interface module type as the active interface module. A virtual controller is also created, which broadcasts the configuration to both the interface modules. The configuration on the physical controllers is then blocked and you can make configuration changes only on the virtual controller. The user configuration can only be performed on the virtual controller.
The virtual controller supports CEM level configuration and all other configurations. These configurations are blocked on physical controllers.
Figure 2: Card Protection Topology

Note DS3 (T3) channelized into T1 and E3 channelized into E1s are supported in card protection. For more information on configuration, see the Configuring the Controller of Channelized T3/T1 Interfaces section.

Y Cable

In card protection, a Y cable is used to multiplex the signal from the patch panel to both the ports of active and standby interface modules. Both the active and protect ports receive the signal, but only the active port transmits the signal from its port. Protect port transmitter is disabled.

Card Protection Switchover

The following table shows the card protection switchover trigger and time to complete the switchover between the working and protect interface module.

Trigger

Time

Interface Module Reload with CLI OIR

Less than 50 millisecond

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 36

Card Protection for T1 or E1

Alarm Based Switchover

Trigger

Time

Non-responsive Interface Module Process (interface 100 millisecond to 200 millisecond module reloads on its own, the reload is initiated due to software error)

Interface Module shuts down due to high temperature Less than 50 millisecond

Interface Module shuts down using CLI

Less than 50 millisecond

Interface Module stops using CLI

Less than 50 millisecond

Card Physical Jackout

100 millisecond to 200 millisecond

Serializer/Deserializer (SerDes) Failures

250 millisecond to 1 second

Alarm Based Switchover

Based on Hold Over Time or Soak Time

Card Protection Commands

20 millisecond to 30 millisecond

Non-responsive Interface Module Process (interface 200 millisecond to 1 second module reloads on its own, the reload is initiated due to software error)

Card Physical Jackout

200 millisecond to 1 second

Alarm Based Switchover
Alarm based switchover is only applicable for Loss Of Signal (LOS) alarm. Switchover happens only when the number of ports with LOS alarm in working interface module is greater than that on the protect interface module.
Each card protection group maintains a weight for each working and protect interface module. This weight is updated when the LOS alarms are asserted or cleared. The switchover happens only if the weight of working interface module and protect interface module stays same for a certain amount of time called soak time.
When there is any issue with the Patch Panel, both working interface module and protect interface module have the same number of LOS alarms (weights are same). Hence, switchover does not happen.

Restrictions
· Card physical jack out convergence time for card protection switchover is more than 50 milliseconds. · The time taken to restart the interface module due to any software error is more than 50 milliseconds. · Alarm toggle on active or backup card causes at least one card protection switch. · When BERT is started from the virtual controllers, the syslog displays the physical controllers instead
of the virtual controller port.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 37

Supported Features on Interface Module

Card Protection for T1 or E1

Supported Features on Interface Module
The supported features are: · Switching Mode · Non-revertive mode · Revertive mode
· Alarm Based Switchover · SerDes Based Switchover · Adaptive Clock Recovery (ACR) on virtual CEM · Differential Clock Recovery (DCR) on virtual CEM · Maintenance Commands
· Lockout · Force · Manual
Note All controller configurations are performed on the virtual controller.
You can create card protection with one slot (either primary or backup) and the remaining slots can be added later.
How to Configure Card Protection for T1 or E1
Configuring T1/E1 Card Protection
Configuring Card Protection Group:
enable configure terminal card type t1 0 2 card type t1 0 1 card-protection [1-16] primary slot 0 bay 1 backup slot 0 bay 2 end
Note The card protection number 1 to 16 refers to CPGN.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 38

Card Protection for T1 or E1

Configuring Revertive Mode

Configuring Virtual Card and Virtual Controller: When card protection group is configured, it creates virtual card for card protection object, denoted by 8/x/port. Slot 8 is a fixed slot number for all card protection created virtual card. Bay number `x' for virtual card is x =CPGN -1 = 15. Virtual controllers can be configured from 8/15/0 to 8/15/47. Physical Card Configuration:
· No configuration is required for traffic.
Virtual Card Configuration: · Configures CEM on virtual controller (8/x/port).
· Configures xconnect and local connect on CEM interface.
enable configure terminal controller t1 8/15/0 cem 0 unframed interface cem 8/15/0 cem 0 xconnect 11.1.1.1 212 encasulation mpls end
enable configure terminal controller t1 8/15/11 cem 0 unframed interface cem 8/15/11 cem 0 connect testLC cem 8/15/0 0 cem 8/15/11 0 end
Note To un-configure a CEM group under a virtual controller, first perform shutdown of the virtual controller and then un-configure the CEM group.
Configuring Revertive Mode
To configure revertive mode:
enable configure terminal card-protection 4 primary slot 0 bay 0 backup slot 0 bay 5 end card-protection 4 revertive time [30-720] end
Note The revertive time ranges from 30 to 720 seconds.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 39

Verification of T1/E1 Card Protection Configuration

Card Protection for T1 or E1

Verification of T1/E1 Card Protection Configuration

Use show card-protection command to verify card protection group configuration.
#show card-protection 2 detail Working(0/1:A900-IMA48T-C NCS4200-48T1E1-CE):
Number of LOS Alarms:7 ok,Active 1:1, Revertive

Protect(0/2:A900-IMA48T-C NCS4200-48T1E1-CE): Number of LOS Alarms:7 ok,Inactive 1:1, Revertive

Revert Timer : (Not Started) Last switchover reason :None

Use show xconnect all command to verify xconnect configuration.

#show xconnect all | I CE8/15/ UP pri ac CE8/15/0:0(SATOP T1) #

UP mpls 11.1.1.1:212

#show xconnect all | i CE8/15/

72

testLC

CE8/15/11 SAT1 0

#

CE8/15/12 SAT1 0

UP UP

Configuring Maintenance Commands
To configure maintenance commands:
enable configure terminal card-protection 4 primary slot 0 bay 0 backup slot 0 bay 5 end card-protection 4 card-protection [manual {backup|primary} | force {backup|primary} | lockout] end

Note Maintenance commands are not synced in the standby environment. After Redundancy Force Switchover (SSO), maintenance commands must be executed again on the new active environment.

Priority Table

The following table shows the priority of the actions:

Priority

Configurations

1

Lockout

2

Force

3

Alarm or Card Failure

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 40

Card Protection for T1 or E1

Associated Commands

Priority 4 5

Configurations Manual Switch Revert

Associated Commands

The following table shows the commands for the IM configuration:

Command

Link

Card Protection Creation Commands: card-protection CPGN card-protection {primary | backup}

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-c1.html#wp1208639895

card-protection revertive time

Card Protection Maintenance Commands:

card-protection CPGN [manual {primary | backup} | force {primary | backup} | lockout ]

show card-protection CPGN detail

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ interface/command/ir-cr-book/ ir-s2.html#wp1628614402

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 41

Associated Commands

Card Protection for T1 or E1

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 42

8 C H A P T E R

Additional References

This appendix describes additional CEM features that are used on the router. This appendix describes the following topics:
· Linecode Configuration and Supported Patterns, on page 43

Linecode Configuration and Supported Patterns

The following pattern for linecode configuration is supported for T1 or E1.
Table 12: Linecode Configuration and Pattern Supported on T1 or E1 Controllers

Part Number XRT83VSH316 LIU

Linecode Configuration T1 or E1

B8ZS/AMI

T1

HDB3/AMI

E1

Random Pattern QRSS PRBS15

Configuration Using AMI Linecodes at Both Ends (UUT (AMI) and TESTER (AMI))
When both sides are configured as AMI, the linecodes match and the T1 or E1 controller is always UP with a smooth traffic flow.
Configuration Using Different Linecodes at Both Ends (UUT (AMI) and TESTER (B8ZS or HDB3))
· The line codes do not match when one side is configured with AMI and other side is configured with non-AMI codes such as B8ZS or HDB3. Based on the pattern that is inserted, there is change in the behavior.
· For 511 QRSS pattern, although the line codes do not match, the controller is UP. The controllers go DOWN for other patterns.
· Each pattern is unique and contains a combination of ones and zeros. Only the pattern 511 QRSS is supported. If patterns other than 511 QRSS are used, then LOS is generated, and controller goes to the DOWN state.

The following table details the configuration using same and different linecodes at both ends and the pattern that is supported on T1 (UUT mode) controller:

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 43

Linecode Configuration and Supported Patterns

Additional References

Table 13: Configuration Using Linecodes for T1 Controllers

Pattern Mode (ANSI) 511 QRSS QRSS 2047 QRSS

Pattern with UUT (AMI) and TESTER (B8zS) Controller is UP. Linecodes do not match. UUT controller is DOWN.
UUT controller is DOWN.

UUT(AMI) and TESTER (AMI)
T1 controller is UP on UUT. Linecodes match. T1 controller is UP on UUT. Linecodes match. T1 controller is UP on UUT. Linecodes match.

The following table details configuration using same and different linecodes at both ends and the pattern that is supported on E1 (UUT mode) controller:
Table 14: Configuration Using Linecodes for E1 Controllers

Pattern Mode (ANSI) 2^15- 1 2^15- 1 INV

Pattern with UUT (AMI) and TESTER (B8zS) Controller is DOWN.
Controller is DOWN.

UUT(AMI) and TESTER (AMI)
E1 controller is UP on UUT. Linecodes match. E1 controller is UP on UUT. Linecodes match.

T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) 44



References

• Cisco Trademarks - Cisco
• Cisco IOS Interface and Hardware Component Command Reference - cable bundle through clock mode [Cisco IOS XE 16] - Cisco
• Cisco IOS Interface and Hardware Component Command Reference - service-module t1 linecode through show controllers satellite [Cisco IOS XE 16] - Cisco
• 48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE 3S (Cisco ASR 900 Series) - Configuring T3 Interfaces on 48-Port T3/E3 Interface Module [Cisco IOS XE 3S] - Cisco
• T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) - Overview of the T1 or E1 Interface Module [Cisco Network Convergence System 4200 Series] - Cisco
• T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) - Monitoring the T1 or E1 Interface Module [Cisco Network Convergence System 4200 Series] - Cisco
• T1 or E1 CEM Interface Module Configuration Guide, Cisco IOS XE 17 (Cisco NCS 4200 Series) - Troubleshooting the T1 or E1 Interface Module [Cisco Network Convergence System 4200 Series] - Cisco