48-port t3/e3 cem interface module configuration guide ... · 48-port t3/e3 cem interface module...

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOSXE Everest 16.6.1 (Cisco NCS 4200 Series)First Published: 2017-07-31

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

C O N T E N T S

Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface Module 1C H A P T E R 1

Information About T3/E3 Interfaces 1

Overview of T3/E3 Interfaces 1

Benefits of T3/E3 Interfaces 1

Restrictions for Configuring T3/E3 Interfaces 1

How to Configure T3/E3 Interfaces 2

Setting the Port 2

Configuring the Controller of Clear Channel T3/E3 Interfaces 2

Verifying Controller Configuration of Clear Channel T3 Interfaces 3

Verifying Controller Configuration of Clear Channel E3 Interfaces 4

Configuring the Controller of Channelized T3/T1 or E3/E1 Interfaces 6

Verifying the Controller Configuration of Channelized T3 or T1 Interfaces 6

Verifying the Controller Configuration of Channelized E3 or E1 Interfaces 8

Configuring SAToP - Clear Channel T3/E3 Interfaces 10

Verifying CEM Configuration of Clear Channel T3 or E3 Interfaces for SAToP 10

Configuring SAToP - Channelized T3/T1 Interfaces 11

Verifying the CEM Configuration of Channelized T3 or T1 Interfaces 11

Configuring SAToP - Channelized E3/E1 Interfaces 12

Verifying the CEM Configuration of Channelized E3/E1 Interfaces 13

Configuring Framed SAToP - Channelized T3/T1 Interfaces 13

Verifying the CEM Configuration of Channelized T3 or T1 Interfaces for Framed SAToP 14

Configuring Framed SAToP - Channelized E3/E1 Interfaces 14

Verifying the CEM Configuration of Channelized E3 or E1 Interfaces for Framed SAToP 15

Configuring MDL for T3 Interfaces 16

Configuring MDL for Path Transmission 16

Configuring MDL for Idle Signal 20

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)iii

Configuring MDL for Test Signal 23

Performance Monitoring 26

Circuit Emulation Service over Packet-Switched Network 33

Restrictions for CESoPSN on T3 or E3 Controller 33

Configuring CESoPSN on T3 or E3 Interfaces 33

Verifying CESoPSN Configurations on E3 Interface 34

Troubleshooting T3/E3 Controllers 37

Running Bit Error Rate Testing for SAToP 37

Configuring BERT for Clear and Channelized T3/E3 Interfaces 38

Bit Error Rate Testing for CESoPSN 39

Restrictions for BERT in CESoPSN 40

Configuring BERT for Clear and Channelized T3/E3 Interfaces for CESoPSN 40

Verifying BERT Configuration for CESoPSN on T3 or E3 Interface 40

Loopback on T3/E3 Interfaces 42

Configuring Loopback for T3/E3 Interfaces 43

Associated Commands 44

Additional References for Configuring 48-Port T3/E3 CEM Interface Module 45

Overview of Circuit Emulation 47C H A P T E R 2

Configuring Pseudowire 47

Information About Pseudowire 47

Overview of Pseudowire 47

How to Configure Pseudowire 48

Structure-Agnostic TDM over Packet 48

Circuit Emulation Service over Packet-Switched Network 51


Additional References for Configuring Pseudowire 56

Alarm History 59C H A P T E R 3

Alarm History Restrictions 59

Configuring Alarm History 60

Verification of Alarm History Configuration 60


Additional References for Alarm History 61

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)iv

Contents

Clock Recovery System for SAToP 63C H A P T E R 4

Finding Feature Information 63

Information About Clock Recovery 63

Adaptive Clock Recovery (ACR) 63

Differential Clock Recovery (DCR) 64

Benefits of Clock Recovery 64

Prerequisites for Clock Recovery 65

Restrictions for Clock Recovery 65

How to Configure ACR and DCR 65

Configuring ACR for T3/E3 65

Configuring Adaptive Clock Recovery of T3/E3 Interfaces for SAToP 65

Configuring DCR for T3/E3 66

Configuring Differential Clock Recovery of T3/E3 Interfaces for SAToP 66

Configuring ACR for Channelized T3/T1 or E3/E1 68

Configuring Adaptive Clock Recovery of Channelized T3/T1 or E3/E1 Interfaces for SAToP68

Configuring DCR for Channelized T3/T1 or E3/E1 69

Configuring Differential Clock Recovery of Channelized T3/T1 or E3/E1 Interfaces for SAToP69


Additional References for Clock Recovery 71

Configuring Synchronous Ethernet ESMC and SSM 73C H A P T E R 5

Understanding Synchronous Ethernet ESMC and SSM 73

Clock Selection Modes 74

QL-Enabled Mode 74

QL-Disabled Mode 74

Managing Clock Selection 74

Restrictions and Usage Guidelines 75

Configuring Synchronous Ethernet ESMC and SSM 75

Managing Clock Source Selection 79

Specifying a Clock Source 79

Selecting a Specific Clock Source 79

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)v

Contents

Forcing a Clock Source Selection 79

Disabling Clock Source Specification Commands 80

Disabling a Clock Source 80

Locking Out a Clock Source 80

Restoring a Clock Source 81

Verifying the Configuration 81

Troubleshooting 81

Configuration Examples 83

Example: Input Synchronous Ethernet Clocking 83

SSM Support on Cisco 48-Port T3/E3 CEM Interface Module 83

Supported Quality Levels 83

Configuring SSM on Cisco 48-Port T3/E3 CEM Interface Module 84

Configuring Clock Source 84

Verification of SSM Configuration 84

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)vi

Contents

C H A P T E R 1Configuring T3 or E3 Interfaces on 48-Port T3 orE3 Interface Module

T3 or E3 interface on the 48-Port T3 or E3 Interface Module supports 48 ports. The channels on the T3 or E3interface can be configured as either clear channel mode or channelized mode.

• Information About T3/E3 Interfaces, on page 1• How to Configure T3/E3 Interfaces, on page 2• Circuit Emulation Service over Packet-Switched Network, on page 33• Troubleshooting T3/E3 Controllers, on page 37• Associated Commands, on page 44• Additional References for Configuring 48-Port T3/E3 CEM Interface Module , on page 45

Information About T3/E3 InterfacesThe following sections provide information about T3/E3 interfaces.

Overview of T3/E3 InterfacesThe T3 or E3 interface supports two modes, clear channel mode and channelized mode. You can enable 28T1or 16E1 only in channelized mode. Each T1 or E1 channel can be configured to use the entire T1 or E1bandwidth for data transmission.

Benefits of T3/E3 InterfacesThe following are the benefits of T3/E3 interfaces:

• Higher bandwidth

• Flexibility by channelization

Restrictions for Configuring T3/E3 Interfaces• You can configure CEM to support serial interface configuration.

• The supported BERT patterns are 2^11, 2^15, 2^20-O153, 2^20-QRSS and 2^23.

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)1

• DS0 level Channelization is not supported.

• The g832 framing mode is not supported.

• Loopback remote is not supported.

How to Configure T3/E3 InterfacesThis section provides the information about how to configure a T3/E3 interface. The T3/E3 interface can beconfigured as clear channel mode or channelized mode.

Setting the PortTo enable the port on the T3/E3 interface module, follow these steps:

enableconfigure terminalcontroller mediatype 0/4/0mode t3exit

Configuring the Controller of Clear Channel T3/E3 Interfaces

Before You Begin

When the clear channel T3/E3 interface is used for the first time, the running configuration does not showthe T3/E3 controller. You can use the show platform command to check whether the chassis recognizes theT3/E3 port and initializes the card correctly. After the port is configured for the slot, the respective controllerappears in the running configuration and you can configure the clear channel T3/E3 interface.

Perform this task to configure clear channel controller as T3.

enableconfigure terminalcontroller t3 0/4/40no channelizedclock source lineno shutexit

By default, the T3 controller is in C-Bit framing mode. To configure CEM, the framing mode must be set tounframed.

Note

Perform this task to configure clear channel controller as E3.

enableconfigure terminalcontroller e3 0/4/40clock source line


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleHow to Configure T3/E3 Interfaces

no shutexit

Verifying Controller Configuration of Clear Channel T3 InterfacesUse the show controllers command to verify the controller configuration of clear channel T3 interface:

Router# show controllers t3 0/4/40T3 0/4/40 is up.Hardware is -48T3E3-CE

Applique type is Clear Channel T3No alarms detected.MDL transmission is disabled

FEAC code received: No code is being receivedFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ftBER thresholds: SF = 10e-10 SD = 10e-10Clock Source is internalEquipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs

Far End0 Errored Secs, 0 Severely Errored Secs0 C-bit Unavailable Secs, 0 Path Failures0 Code Violations, 0 Service Affecting Secs

Data in Interval 1:Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs20 Unavailable Secs, 20 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 Path Failures0 AIS Defect Secs, 20 LOS Defect Secs


Total Data (last 1 15 minute intervals):Near End0 Line Code Violations, 0 P-bit Coding Violations,0 C-bit Coding Violations, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,20 Unavailable Secs, 20 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 path failures0 AIS Defect Secs, 20 LOS Defect Secs


T1 1 is uptimeslots:FDL per AT&T 54016 spec.No alarms detected.


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying Controller Configuration of Clear Channel T3 Interfaces

Framing is ESF, Clock Source is InternalData in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs

Far End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs 0 Path Failures

Data in Interval 1:Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs1 Path Failures, 2 SEF/AIS Secs


Total Data (last 1 15 minute intervals):Near End0 Line Code Violations,0 Path Code Violations,0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs1 Path Failures, 2 SEF/AIS Secs

Far End0 Line Code Violations,0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,3 Errored Secs, 0 Bursty Err Secs, 3 Severely Err Secs0 Unavailable Secs, 0 Path Failures

Verifying Controller Configuration of Clear Channel E3 InterfacesUse the show controllers command to verify the controller configuration of clear channel E3 interface:

Router# show controllers e3 0/4/40E3 0/4/40 is up.Hardware is -48T3E3-CE

Applique type is Clear Channel e3No alarms detected.MDL transmission is disabled

FEAC code received: No code is being receivedFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ftBER thresholds: SF = 10e-10 SD = 10e-10Clock Source is internalEquipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying Controller Configuration of Clear Channel E3 Interfaces

0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs






E1 1 is uptimeslots:FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Clock Source is InternalData in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs




Total Data (last 1 15 minute intervals):Near End


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying Controller Configuration of Clear Channel E3 Interfaces

0 Line Code Violations,0 Path Code Violations,0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs1 Path Failures, 2 SEF/AIS Secs


Configuring the Controller of Channelized T3/T1 or E3/E1 Interfaces

Before You Begin

When the channelized T3/T1 or E3/E1 interface is used for the first time, the running configuration does notshow the T3/E3 controller. You can use the show platform command to check if the chassis recognizes theT3/E3 port and initializes the card properly. After the port is configured for the slot, the respective controllerappears in the running configuration and you can configure the channelized T3/T1 or E3/E1 interface.

Perform this task to configure channelized controller as T3/T1.

enableconfigure terminalcontroller t3 0/4/46channelizedclock source lineno shutexit

The channelized mode is the default mode for T3 interface.Note

Perform this task to configure channelized controller as E3/E1.

enableconfigure terminalcontroller e3 0/4/46channelized mode e1framing g751exit

The clear channel mode is the default mode for E3 interface.Note

Verifying the Controller Configuration of Channelized T3 or T1 InterfacesUse the show controllers command to verify the controller configuration of channelized T3 or T1 interfaces:

Router# show controllers t3 0/4/46

T3 0/4/46 is down.Hardware is -48T3E3-CE


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring the Controller of Channelized T3/T1 or E3/E1 Interfaces

Applique type is Channelized T3No alarms detected.MDL transmission is disabled







T1 1 is uptimeslots:FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Clock Source is InternalData in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs

Far End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the Controller Configuration of Channelized T3 or T1 Interfaces

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs 0 Path Failures





Verifying the Controller Configuration of Channelized E3 or E1 InterfacesUse the show controllers command to verify the controller configuration of channelized E3 or E1 interfaces:

Router# show controllers e3 0/4/46

E3 0/4/46 is down.Hardware is -48T3E3-CEApplique type is Channelized E3No alarms detected.MDL transmission is disabled



Data in Interval 1:Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs20 Unavailable Secs, 20 Line Errored Secs


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the Controller Configuration of Channelized E3 or E1 Interfaces

0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 Path Failures0 AIS Defect Secs, 20 LOS Defect Secs




E1 1 is uptimeslots:FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Clock Source is InternalData in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs







Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the Controller Configuration of Channelized E3 or E1 Interfaces

Configuring SAToP - Clear Channel T3/E3 Interfaces

Before You Begin

Before Structure-Agnostic TDMover Packet (SAToP) is configured, the controller of clear channel T3 interfacemust be configured.

enableconfigure terminalcontroller t3 0/4/40no channelizedcem-group 0 unframedinterface CEM 0/4/40cem 0xconnect 10.10.2.2 204 encapsulation mplsexit

Before You Begin

Before SAToP is configured, the controller of clear channel E3 interface must be configured.

enableconfigure terminalcontroller e3 0/4/40cem-group 0 unframedinterface CEM 0/4/40cem 0xconnect 10.10.2.2 204 encapsulation mplsexit

Verifying CEM Configuration of Clear Channel T3 or E3 Interfaces for SAToPUse the show run interface command to verify the configuration of xconnect:

Router# show run interface cem 0/4/40

Current configuration : 96 bytes!interface CEM 0/4/40no ip addresscem 0xconnect 10.10.2.2 204 encapsulation mpls!end

Use the show cem circuit int cem command to verify the CEM interface configuration of clear channel T3or E3 interface for SAToP:

Router# show cem circuit int cem 0/4/40

CEM 0/4/40, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVEController state: down, T3 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 1024Framing: Unframed


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring SAToP - Clear Channel T3/E3 Interfaces

CEM Defects SetNone

Signalling: No CASRTP: No RTP

Ingress Pkts: 1321577 Dropped: 0Egress Pkts: 1321577 Dropped: 0

CEM Counter DetailsInput Errors: 0 Output Errors: 0Pkts Missing: 0 Pkts Reordered: 0Misorder Drops: 0 JitterBuf Underrun: 0Error Sec: 0 Severly Errored Sec: 0Unavailable Sec: 0 Failure Counts: 0Pkts Malformed: 0 JitterBuf Overrun: 0

Configuring SAToP - Channelized T3/T1 Interfaces

Before You Begin

Before SAToP is configured, the controller of channelized T3/T1 interface must be configured.

enableconfigure terminalcontroller t3 0/4/12channelizedt1 1 cem-group 0 unframedinterface CEM 0/4/12cem 0xconnect 10.10.2.2 204 encapsulation mplsexit

Verifying the CEM Configuration of Channelized T3 or T1 InterfacesUse the show run controller command to verify the CEM configuration of channelized T3 or T1 interface:

Router# show run controller t3 0/4/46

Current configuration : 109 bytes!Controller T3 0/4/46framing c-bitcablelength shortt1 1 cem-group 0 unframedend

Use the show cem circuit int cem command to verify the CEM configuration of channelized T3 or T1interface:


CEM0/4/46, ID: 1, Line: UP, Admin: UP, Ckt: ACTIVEController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring SAToP - Channelized T3/T1 Interfaces

Dejitter: 5 (In use: 0)Payload Size: 192Framing: UnframedCEM Defects SetNone



CEM Counter DetailsInput Errors: 0 Output Errors: 0Pkts Missing: 0 Pkts Reordered: 0Misorder Drops: 0 JitterBuf Underrun: 32Error Sec: 0 Severly Errored Sec: 0Unavailable Sec: 0 Failure Counts: 0Pkts Malformed: 0 JitterBuf Overrun: 0---CEM0/4/46, ID: 28, Line: UP, Admin: UP, Ckt: ACTIVEController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 192Framing: UnframedCEM Defects SetNone




Configuring SAToP - Channelized E3/E1 Interfaces

Before You Begin

Before SAToP is configured, the controller of channelized E3/E1 interfaces must be configured.

enableconfigure terminalcontroller e3 0/4/46channelizede1 1 cem-group 0 unframedinterface CEM 0/4/46cem 0xconnect 10.10.2.2 204 encapsulation mplsexit


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring SAToP - Channelized E3/E1 Interfaces

Verifying the CEM Configuration of Channelized E3/E1 InterfacesUse the show run controller command to verify the CEM configuration of channelized E3 or E1 interface:

Router# show run controller e3 0/4/46

Current configuration : 109 bytes!Controller E3 0/4/46framing c-bitclock source linecablelength shorte1 1 cem-group 0 unframedend

Use the show cem circuit int cem command to verify the CEM configuration of channelized E3 or E1interface:


CEM0/4/46, ID: 1, Line: UP, Admin: UP, Ckt: ACTIVEController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 256Framing: UnframedCEM Defects SetNone




Configuring Framed SAToP - Channelized T3/T1 Interfaces

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

To configure the controller of channelized T3/T1 interface for framed SAToP:

enableconfigure terminalcontroller t3 0/4/46channelized modeframing c-bitt1 1 cem-group 0 framed


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the CEM Configuration of Channelized E3/E1 Interfaces

interface CEM 0/4/46cem 0xconnect 10.10.2.2 204 encapsulation mplsexit

Verifying the CEM Configuration of Channelized T3 or T1 Interfaces for Framed SAToPUse the show run controller command to verify the CEM configuration of channelized T3 or T1 interfacefor Framed SAToP:

Router# show run controller t3 0/4/46

Current configuration : 109 bytes!Controller T3 0/4/46framing c-bitcablelength shortt1 1 cem-group 0 framedend

Use the show cem circuit int cem command to verify the CEM configuration of channelized T3 or T1interface for Framed SAToP:


CEM0/4/46, ID: 1, Line: UP, Admin: UP, Ckt: ACTIVEMode :Channelized-T1, T1: 1, CEM Mode: T1-SAToPController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 192Framing: Framed SAToPCEM Defects SetNone



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

Configuring Framed SAToP - Channelized E3/E1 InterfacesTo configure the controller of channelized E3/E1 interfaces for Framed SAToP:

enable


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the CEM Configuration of Channelized T3 or T1 Interfaces for Framed SAToP

configure terminalcontroller e3 0/4/46channelized mode e1framing g751e1 1 cem-group 0 framedinterface CEM 0/4/46cem 0xconnect 10.10.2.2 204 encapsulation mplsexit

Verifying the CEM Configuration of Channelized E3 or E1 Interfaces for Framed SAToPUse the show run controller command to verify the CEM configuration of channelized E3 or E1 interfacefor Framed SAToP:

Router# show run controller e3 0/4/46

Current configuration : 109 bytes!Controller E3 0/4/46clock source linecablelength shorte1 1 cem-group 0 framedend

Use the show cem circuit int cem command to verify the CEM configuration of channelized E3 or E1interface for Framed SAToP:

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

CEM0/4/46, ID: 1, Line: UP, Admin: UP, Ckt: ACTIVEMode :Channelized-E1, E1: 1, CEM Mode: E1-SAToPController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 192Framing: Framed SAToPCEM Defects SetNone



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


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying the CEM Configuration of Channelized E3 or E1 Interfaces for Framed SAToP

Configuring MDL for T3 InterfacesMaintenance Data Link (MDL) messages are used to communicate identification information between localand remote ports. The MDL message includes:

• Equipment Identification Code (EIC)

• Location Identification Code (LIC)

• Frame Identification Code (FIC)

• Unit

• Path Facility Identification (PFI)

• Port Number

• Generator Identification Number

MDL messages are only supported when the T3 framing is set for C-bit parity.Note

The no mdl command removes the configuration of mdl messages.

MDL configuration is not supported for E3 interfaces.Note

Configuring MDL for Path TransmissionTo configure MDL path transmission messages on T3 controller configuration mode, use the followingcommands:

enableconfigure terminalcontroller t3 0/0/17framing c-bitmdl string eic beicmdl string lic beicmdl string fic bfixmdl string unit bunitmdl string pfi bpfimdl transmit path

Verifying MDL for Path Transmission Configuration

For PE1 Configuration:

Use the show controller command to display the verification of MDL path transmission configuration.


T3 0/0/17 is up.Hardware is -48T3E3-CE

Applique type is Channelized T3


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring MDL for T3 Interfaces

No alarms detected.MDL transmission is disabled








Far End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying MDL for Path Transmission Configuration

0 Unavailable Secs 0 Path FailuresData in Interval 1:Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs1 Path Failures, 2 SEF/AIS Secs





Use the show controller command to display the verification of MDL path transmission configuration.



Applique type is Channelized T3No alarms detected.MDL transmission is enabled

Far-End MDL Information ReceivedEIC: beic, LIC: beic, FIC: bfix, UNIT: bunitIdle Signal PORT_NO: bport

FEAC code received: DS3 Out-Of-FrameFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ftClock Source is internalEquipment customer loopback

Data in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs


Data in Interval 1:Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs



0 P-bit Severely Err Secs, 0 Severely Err Framing Secs20 Unavailable Secs, 20 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 Path Failures0 AIS Defect Secs, 20 LOS Defect Secs












Configuring MDL for Idle SignalTo configure MDL idle signal messages on T3 controller configuration mode, use the following commands:

enableconfigure terminalcontroller T3 0/0/17framing c-bitmdl string eic beicmdl string lic beicmdl string fic bfixmdl string unit bunitmdl string port bportmdl transmit idle-signal

Verifying MDL for Idle Signal Configuration


Use the show controller command to display the verification of MDL for idle signal configuration.








Total Data (last 1 15 minute intervals):


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring MDL for Idle Signal

Near End0 Line Code Violations, 0 P-bit Coding Violations,0 C-bit Coding Violations, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,20 Unavailable Secs, 20 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 path failures0 AIS Defect Secs, 20 LOS Defect Secs









Use the show controller command to display the verification of MDL for idle signal configuration.




Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying MDL for Idle Signal Configuration


Far-End MDL Information ReceivedEIC: beic, LIC: beic, FIC: bfix, UNIT: bunitIdle Signal PORT_NO: bport

FEAC code received: DS3 Out-Of-FrameFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ftClock Source is internalEquipment customer loopback









Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying MDL for Idle Signal Configuration






Configuring MDL for Test SignalTo configure MDL test signal messages on T3 controller configuration mode, use the following commands:

enableconfigure terminalcontroller t3 0/0/17framing c-bitmdl string eic beicmdl string lic beicmdl string fic bfixmdl string unit bunitmdl string generator bgenmdl transmit test-signal

Verifying MDL for Test Signal Configuration


Use the show controller command to display the verification of MDL for test signal configuration.



EIC: beic, LIC: beic, FIC: bfix, UNIT: bunitTest Signal GEN_NO: bgen

FEAC code received: DS3 Out-Of-FrameFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ft


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring MDL for Test Signal

Clock Source is internalEquipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs








Data in Interval 1:Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying MDL for Test Signal Configuration

0 Unavailable Secs, 0 Stuffed Secs1 Path Failures, 2 SEF/AIS Secs





Use the show controller command to display the verification of MDL for test signal configuration.



Far-End MDL Information ReceivedEIC: beic, LIC: beic, FIC: bfix, UNIT: bunitTest Signal GEN_NO: bgen

FEAC code received: DS3 Out-Of-FrameFraming is C-BIT Parity, Line Code is B3ZS, Cablelength Short less than 225ftClock Source is internalEquipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs



Far End0 Errored Secs, 0 Severely Errored Secs0 C-bit Unavailable Secs, 0 Path Failures


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying MDL for Test Signal Configuration

0 Code Violations, 0 Service Affecting SecsTotal Data (last 1 15 minute intervals):Near End0 Line Code Violations, 0 P-bit Coding Violations,0 C-bit Coding Violations, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,20 Unavailable Secs, 20 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 path failures0 AIS Defect Secs, 20 LOS Defect Secs








Performance MonitoringYou can view the statistics or error count generated on the TDM lines for T3 interfaces.enableconfigure terminal


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModulePerformance Monitoring

controller MediaType 0/0/0mode t3controller t3 0/0/0framing c-bitcablelengthlong 224-450 ftshort 0-224 ftcontroller MediaType 0/0/15mode t3controller T3 0/0/15framing c-bitcablelength short

To view the statistics or error count generated on the TDM lines for T3 interfaces, use the show controllercommand:Router# show controller T3 0/0/0T3 0/0/0 is up.Hardware is -48T3E3-CE
















Use Case 1

If your configuration is as follows:

• T3 is up

• No Alarms

• Framing is unframed

• Clock Source is Internal

This performance monitoring result is displayed:T3 is upNo alarms detected.Framing is unframed, Clock Source is Internal






Use Case 2

If your configuration is as follows:

• T1 28 is up or E1 16 is up

• No alarm received

• Framing is unframed

• Clock Source is Internal

This performance monitoring result is displayed:T1 28 is upNo alarms detected.Framing is unframed, Clock Source is InternalData in current interval (240 seconds elapsed):

Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs




Total Data (last 1 15 minute intervals):Near End0 Line Code Violations, 0 P-bit Coding Violations,



0 C-bit Coding Violations, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,20 Unavailable Secs, 20 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored Secs20 Severely Errored Line Secs, 1 path failures0 AIS Defect Secs, 20 LOS Defect Secs








To view the statistics or error count generated on the TDM lines for T3 interfaces, use the show controllercommand is:Router# show controllers t3 0/0/0T3 0/0/0 is down.Hardware is -48T3E3-CE

Applique type is Channelized T3Receiver has loss of signal.Framing is Unknown, Line Code is B3ZS, Cablelength Short less than 225ftClock Source is internal



Equipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs








Data in Interval 1:Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins2 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs



1 Path Failures, 2 SEF/AIS SecsFar End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 2 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins3 Errored Secs, 0 Bursty Err Secs, 3 Severely Err Secs0 Unavailable Secs 0 Path Failures



Circuit Emulation Service over Packet-Switched NetworkCESoPSN is a method for encapsulating structured (NxDS0) TDM signals as pseudowires over packetswitching networks.

Restrictions for CESoPSN on T3 or E3 Controller• The maximum number of CEM interface supported is 1344.

• The change of framing from C-bit to M13 is not supported on the T3 interface, where as the change offraming from g751 to g832 is supported on the E3 interface.

• CT3-E1 and CE3-T1 is not supported and only CT3-T1 and CE3-E1 is supported.

• DS0 loopback is not supported on the T3 interface.

• Alarm forwarding is not supported on the T3 interface.

• Card protection is not supported on the T3 interface.

Configuring CESoPSN on T3 or E3 InterfacesBefore You Begin

Create CEM group for channelized T3 interface, use the following commands:

enableconfigure terminalcontroller MediaType 0/5/1mode t3channelizedcontroller T3 0/5/1framing c-bitcablelength shortt1 1 cem-group 1 timeslots 10exit


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleCircuit Emulation Service over Packet-Switched Network

Create CEM group for channelized E3 interface, use the following commands:

enableconfigure terminalcontroller MediaType 0/5/1mode e3channelized mode e1controller e3 0/14/0channelizedcablelength shorte1 1 cem-group 0 timeslots 10exit

Configure xconnect:

int cem 0/14/0cem 0xconnect 1.1.1.1 9999 encapsulation mpls

Verify the xconnect status:

sh xconnect all | i 9999UP pri ac CE0/14/0:0(CESoPSN Basic) UP mpls 1.1.1.1:9999 UP

Verifying CESoPSN Configurations on E3 InterfaceThis section includes show commands for CESoPSN:Router# show controllers e3 0/14/2E3 0/14/2 is up.Hardware is -48T3E3-CEApplique type is Channelized E3No alarms detected.Framing is E3 G751, Line Code is HDB3, Cablelength Short less than 225ftBER thresholds: SF = 10e-10 SD = 10e-10Clock Source is internal, National Bit 0Equipment customer loopbackData in current interval (240 seconds elapsed):Near End0 Line Code Violations, 0 P-bit Coding Violations0 C-bit Coding Violations, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs0 Severely Errored Line Secs, 0 Path Failures0 AIS Defect Secs, 0 LOS Defect Secs



Far End0 Errored Secs, 0 Severely Errored Secs


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying CESoPSN Configurations on E3 Interface

0 C-bit Unavailable Secs, 0 Path Failures0 Code Violations, 0 Service Affecting Secs



E1 1 is uptimeslots:FDL per AT&T 54016 spec.No alarms detected.Framing is crc4, Clock Source is Internal, National bits are 0x1F.Data in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs






router# sh mpls l2 vc interface cem 0/14/0 0Local intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------CE0/14/0 CESoPSN Basic 0 1.1.1.1 9999 UP



router# sh mpls l2transport vc 9090 detailLocal interface: CE0/14/2 up, line protocol up, CESoPSN Basic 0 upDestination address: 1.1.1.1, VC ID: 9090, VC status: upOutput interface: Te0/12/0, imposed label stack {130}Preferred path: not configuredDefault path: activeNext hop: 123.123.123.1

Create time: 00:18:44, last status change time: 00:18:30Last label FSM state change time: 00:18:30

Signaling protocol: LDP, peer 1.1.1.1:0 upTargeted Hello: 2.2.2.2(LDP Id) -> 1.1.1.1, LDP is UPGraceful restart: not configured and not enabledNon stop routing: configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: No faultLast local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 130, remote 130Group ID: local 207, remote 220MTU: local 0, remote 0Remote interface description:

Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)SSO Descriptor: 1.1.1.1/9090, local label: 130Dataplane:SSM segment/switch IDs: 1237749/557811 (used), PWID: 114

VC statistics:transit packet totals: receive 0, send 0transit byte totals: receive 0, send 0transit packet drops: receive 0, seq error 0, send 0

ASR907# sh cem circuit interface cem 0/14/2 0CEM0/14/2, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVEMode :Channelized-E1, E1: 1, CEM Mode: E1-CESoPController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 160Framing: Framed (DS0 channels: 1-20)CEM Defects SetNoneSignalling: No CASRTP: No RTPIngress Pkts: 24005 Dropped: 0Egress Pkts: 24005 Dropped: 0CEM Counter DetailsInput Errors: 0 Output Errors: 0Pkts Missing: 0 Pkts Reordered: 0Misorder Drops: 0 JitterBuf Underrun: 0Error Sec: 0 Severly Errored Sec: 0Unavailable Sec: 0 Failure Counts: 0Pkts Malformed: 0 JitterBuf Overrun: 0Generated Lbits: 0 Received Lbits: 0Generated Rbits: 0 Received Rbits: 0Generated Mbits: 0 Received Mbits: 0



Troubleshooting T3/E3 ControllersYou can use the following methods to troubleshoot the T3/E3 controllers on the chassis:

Running Bit Error Rate Testing for SAToPBit error rate testing (BERT) is supported on T3/E3 interfaces. You can run 16 BERTs at a time. The test canbe either of the T1/E1 or the T3/E3 interface.

The interface contains on board BERT circuitry. With this, the interface software can send and detect aprogrammable pattern that is compliant with CCITT/ITUO.151, O.152, O.153 pseudo-random, and repetitivetest patterns. BERTs allow you to test cables and signal problems in the field.

BERT is not supported in system direction for framed SAToP. Framing type should be maintained same inall routers end to end.

When running a BERT test, your system must receive the same pattern that it is transmitting. So, ensure thetwo common options are available:

• Use of a loopback somewhere in the link or network

• Configuration of a remote testing equipment to transmit the same BERT test pattern at the same time

Table 1 lists different BERT keywords and their descriptions.

Table 1: BERT Pattern Descriptions

DescriptionKeyword

Repeating pattern of zeros (...000...)0s

Pseudo-random test pattern that is 2,048 bits in length.2^11

Pseudo-random O.151 test pattern that is 32,768 bitsin length.

2^15

Pseudo-random O.153 test pattern that is 1,048,575bits in length.

2^20-O153

Pseudo-random QRSS O.151 test pattern that is1,048,575 bits in length.

2^20-QRSS

Pseudo-random 0.151 test pattern that is 8,388,607bits in length.

2^23

Both the total number of bits and the error bits received are available for analysis. You can select the testingperiod 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


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleTroubleshooting T3/E3 Controllers

When the BERT is configured towards the system direction, it internally loopbacks the TDM side.Note

Configuring BERT for Clear and Channelized T3/E3 Interfaces

Before You Begin

Before you configure BERT for clear channel T3/E3 interfaces, ensure that controller and CEM are configured.

To run a BERT on clear channel T3/E3 interface, perform the following tasks in global configuration mode.

enableconfigure terminalcontroller t3 0/0/1no channelizedbert pattern 0s interval 30 direction lineexit

To run a BERT on channelized T3/T1 interface or channelized E3/E1 interface, perform the following tasksin global configuration mode.

enableconfigure terminalcontroller t3 0/0/1channelizedt1 1 bert pattern 0s interval 30 direction lineexit

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

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

• After you terminate the test using the no bert command

• After the test runs completely

• Anytime during the test (in real time)

Verifying the BERT Configuration for T3/E3 Interfaces

Use the show controller command to verify the BERT configuration for clear channel T3/E3 interfaces:

Router# show controllers t3 0/4/40 | sec BERTBERT test result (running)

Test Pattern : 2^15, Status : Not Sync, Sync Detected : 0DSX3 BERT direction : LineInterval : 5 minute(s), Time Remain : 3 minute(s)Bit Errors (since BERT started): 0 bits,Bits Received (since BERT started): 0 KbitsBit Errors (since last sync): 0 bitsBits Received (since last sync): 0 Kbits


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring BERT for Clear and Channelized T3/E3 Interfaces

Use the show controller command to verify the BERT configuration of channelized T3/T1 interfaces orchannelized E3/E1 interfaces:

Router# sh controller t3 0/3/0 | be T1 1T1 1 is uptimeslots:FDL per AT&T 54016 spec.Receiver is getting AIS.Framing is ESF, Clock Source is InternalBERT test result (running)

Test Pattern : 2^23, Status : Not Sync, Sync Detected : 0Interval : 5 minute(s), Time Remain : 00:01:44Bit Errors (since BERT started): 299 Mbits,Bits Received (since BERT started): 299 MbitsBit Errors (since last sync): 0 bitsBits Received (since last sync): 0 KbitsDirection : Line

Data in current interval (250 seconds elapsed):Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs






Bit Error Rate Testing for CESoPSNBit-Error Rate Testing (BERT) is used for analyzing quality and problem resolution of digital transmissionequipment. BERT tests the quality of an interface by directly comparing a pseudorandom or repetitive test


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleBit Error Rate Testing for CESoPSN

pattern with an identical locally generated test pattern. BERT is supported at the TDM side and pseudowireside. BERT can be used either at NxDS0 or DS1 but not together.

BERT is supported on following controllers:

• T1NxDS0, DS1

• T3NxDS0, DS1 (channelised), clear channel DS3.

• OCXNxDS0, DS1 (channelised),DS3(channelised), clear channel DS3,STS1,STS-nc,VT-1.5,VT1.5 T1

Restrictions for BERT in CESoPSN• The BERT patterns supported are 2^11, 2^15, 2^20-O153, and 2^20-QRSS.

• For the line side BERT to be configured at timeslot level, the first CEM should be configured and itshould be present at the same timeslot level where the BERT is configured.

• The system side BERT is not supported on partial timeslots. For the system side BERT, use full timeslots.

Configuring BERT for Clear and Channelized T3/E3 Interfaces for CESoPSN

Before You Begin

Before you configure BERT for clear channel T3/E3 interfaces, ensure that the controller and CEM areconfigured.

To run a BERT on the T3 interface, use the following commands:

configure terminalcontroller t3 0/5/0t1 1 bert timeslots 1 pattern 2^15 interval 1

To run a BERT on the E3 interface, use the following commands:

config terminalcontroller e3 0/5/0e1 1 bert timeslots 1 pattern 2^15 interval 1

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

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




Verifying BERT Configuration for CESoPSN on T3 or E3 InterfaceUse the following command to verify the BERT configuration for CESoPSN on T3 interfaces:


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleRestrictions for BERT in CESoPSN









T1 1 is downtimeslots: 1-24FDL per AT&T 54016 spec.Receiver has remote alarm.Framing is ESF, Clock Source is Recovered 1BERT running on timeslots 1,BERT test result (running)

Test Pattern : 2^15, Status : Sync, Sync Detected : 0Interval : 0 minute(s), Time Remain : 00:00:37Bit Errors (since BERT started): 0 bits,


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleVerifying BERT Configuration for CESoPSN on T3 or E3 Interface

Bits Received (since BERT started): 137 KbitsBit Errors (since last sync): 0 bitsBits Received (since last sync): 137 KbitsDirection : Line

Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs






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




Loopback on T3/E3 Interfaces

Loopback Description

You can use the following loopback on the clear and channelized T3/T1 or E3/E1 interfaces.

DescriptionLoopback

Loops the transmitting signal back to the receiver.loopback local


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleLoopback on T3/E3 Interfaces

DescriptionLoopback

Loops the incoming signal back to the interface usingthe line loopbackmode of the framer. The framer doesnot reclock or reframe the incoming data. Allincoming data is received by the interface driver.

loopback network line

Configuring Loopback for T3/E3 InterfacesTo set a loopback local on the clear channel T3/E3 interface, perform the following tasks in global configurationmode:

enableconfigure terminalcontroller t3 0/0/1loopback localexit

To set a loopback network on the clear channel T3/E3 interface, perform the following tasks in globalconfiguration mode:

enableconfigure terminalcontroller t3 0/0/1loopback network lineexit

To set a loopback local on the channelized channel T3/T1 or E3/E1 interface, perform the following tasks inglobal configuration mode:

enableconfigure terminalcontroller t3 0/0/1channelizedt1 1 loopback localexit

To set a loopback network on the channelized channel T3/T1 or E3/E1 interface, perform the following tasksin global configuration mode:

enableconfigure terminalcontroller t3 0/0/1channelizedt1 1 loopback network lineexit

To remove a loopback, use the no loopback command.Note


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleConfiguring Loopback for T3/E3 Interfaces

Associated CommandsThe commands used to configure the interfaces.

URLCommands

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

controller mediatype

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

mode t3/e3


controller t1

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-c2.html#wp1921350260

controller t3


controller e3


clock source


channelized


cem


cem-group

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-t2.html#wp8578094790

xconnect

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

t1/e1 cem-group


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleAssociated Commands


































URLCommands

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

payload-size dejitter-buffer

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-a1.html#wp3620978929

bert pattern

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-l2.html#wp2513399572

loopback


t1/e1 loopback

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

show controllers t3

Additional References for Configuring 48-Port T3/E3 CEMInterface Module

Related Documents

Document TitleRelated Topic

Cisco IOS Master Commands List, All ReleasesCisco IOS commands

Standards and RFCs

TitleStandard/RFC

There are no standards and RFCs for this feature.—

MIBs

MIBs LinkMIB

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use CiscoMIB Locator found at the following URL:

http://www.cisco.com/go/mibs

—


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleAdditional References for Configuring 48-Port T3/E3 CEM Interface Module
















http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html


Technical Assistance

LinkDescription

http://www.cisco.com/cisco/web/support/index.htmlThe Cisco Support website provides extensive onlineresources, including documentation and tools fortroubleshooting and resolving technical issues withCisco products and technologies.

To receive security and technical information aboutyour products, you can subscribe to various services,such as the Product Alert Tool (accessed from FieldNotices), the Cisco Technical Services Newsletter, andReally Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support websiterequires a Cisco.com user ID and password.


Configuring T3 or E3 Interfaces on 48-Port T3 or E3 Interface ModuleAdditional References for Configuring 48-Port T3/E3 CEM Interface Module

http://www.cisco.com/cisco/web/support/index.html

C H A P T E R 2Overview of Circuit Emulation

Circuit Emulation (CEM) is a technology that provides a protocol-independent transport over IP/MPLSnetworks. It enables proprietary or legacy applications to be carried transparently to the destination, similarto a leased line.

CEM provides a bridge between a Time-Division Multiplexing (TDM) network and Multiprotocol LabelSwitching (MPLS) network. The chassis encapsulates the TDM data in the MPLS packets and sends the dataover a CEM pseudowire to the remote Provider Edge (PE) chassis. As a result, CEM functions as a physicalcommunication link across the packet network.

The chassis supports the pseudowire type that utilizes CEM transport: Structure-Agnostic TDM over Packet(SAToP).

L2VPN over IP/MPLS is also supported on the interface modules.

The RSP switchover with physical SSO is above 50 ms as follows:

• R0 to R1 is 54 ms

• R1 to R0 is 51 ms

• Configuring Pseudowire, on page 47

Configuring PseudowireCisco Pseudowire Emulation Edge-to-Edge (PWE3) allows you to transport traffic by using traditional servicessuch as T1/E1 over a packet-based backhaul technology such as MPLS or IP. A pseudowire (PW) consistsof a connection between two provider edge (PE) chassis that connects two attachment circuits (ACs), such asT1/E1 or T3 /E3 links.

Information About PseudowireThe following sections describe how to configure pseudowire on the interface module of the chassis.

Overview of PseudowirePseudowires manage encapsulation, timing, order, and other operations in order to make it transparent tousers. The pseudowire tunnel acts as an unshared link or circuit of the emulated service.


How to Configure PseudowireThe following sections describe how to configure pseudowire.

Structure-Agnostic TDM over PacketStructure-Agnostic TDM over Packet (SAToP) encapsulates Time Division Multiplexing (TDM) bit-streamsas pseudowires over public switched networks. It disregards any structure that may be imposed on streams,in particular the structure imposed by the standard TDM framing.

The protocol used for emulation of these services does not depend on the method in which attachment circuitsare delivered to the Provider Edge (PE) chassis. For example, a T1 attachment circuit is treated the same wayfor all delivery methods, including copper, multiplex in a T3 circuit, a virtual tributary of a SONET circuit,or unstructured Circuit Emulation Service (CES).

In SAToPmode, the interface is considered as a continuous framed bit stream. The packetization of the streamis done according to IETF RFC 4553. All signaling is carried out transparently as a part of a bit stream.

Configuring CEM for SAToP

This section provides information about how to configure CEM. CEM provides a bridge between a TimeDivision Multiplexing (TDM) network and a packet network, MPLS. The chassis encapsulates the TDM datain the MPLS packets and sends the data over a CEM pseudowire to the remote Provider Edge (PE) chassis.

The following sections describe how to configure CEM.

Configuring CEM Restriction

• Not all combinations of payload size and dejitter buffer size are supported. If you apply an incompatiblepayload size or dejitter buffer size configuration, the chassis rejects it and reverts to the previousconfiguration.

• The dummy-pattern command is not supported.

CEM interface does not support idle-cas parameter.Note

Configuring CEM Group for SAToP

The following section describes how to configure a CEM group for SAToP.

enableconfigure terminalcontroller t3 0/1/0cem-group 0 unframedend

Configuring CEM Classes

A CEM class allows you to create a single configuration template for multiple CEM pseudowires. Followthese steps to configure a CEM class:


Overview of Circuit EmulationHow to Configure Pseudowire

• The CEM parameters can be configured either by using CEM class or on CEM interface directly.

• The CEMparameters at the local and remote ends of a CEM circuit must match; otherwise, the pseudowirebetween the local and remote PE chassis does not come up.

Note

enableconfigure terminalclass cem mycemclasspayload-size 512dejitter-buffer 12exitinterface cem 0/0/1cem 0cem class mycemclassxconnect 10.10.10.10 200 encapsulation mplsexit

Configuring CEM Parameters

The following sections describe the parameters you can configure for CEM circuits.

Configuring Payload Size

To specify the number of bytes encapsulated into a single IP packet, use the payload-size command. The sizeargument specifies the number of bytes in the payload of each packet.

Default payload sizes for T3/E3 interface are:

• T3/E3 clear channel= 1024 bytes

• T3/E3 channelized = 192 bytes

Default payload sizes for a structured CEM channel depend on the number of time slots that constitute thechannel. Payload size (L in bytes), number of time slots (N), and packetization delay (D in milliseconds) havethe following relationship: L = 8*N*D. The default payload size is selected in such a way that the packetizationdelay is always 1 millisecond.

Both payload-size and dejitter-buffer must be configured simultaneously. When you select a value ofpayload-size, the acceptable range of dejitter-buffer for that payload size is displayed.

Note

Setting the Dejitter Buffer Size

To specify the size of the dejitter-buffer used to compensate for the network filter, use the dejitter-buffercommand. The configured dejitter-buffer size is converted from milliseconds to packets and rounded up tothe next integral number of packets. Use the size argument to specify the size of the buffer, in milliseconds.The range is from 1 to 32; the default is 5.

Shutting Down a CEM Channel

To shut down a CEM channel, use the shutdown command in CEM configuration mode. The shutdowncommand is supported only under CEM mode and not under the CEM class.


Overview of Circuit EmulationConfiguring CEM Parameters

Configuring CEM Parameter on CEM Interface

The CEM parameters can be configured directly on CEM interface. Follow these steps to configure CEMparameters:

enableconfigure terminalclass cem mycemclasspayload-size 1024 dejitter-buffer 10exitinterface cem 0/0/1no ip addresscem 0cem class mycemclassxconnect 10.10.10.10 200 encapsulation mplsexit

Verifying the Interface Configuration

Use the following commands to verify the pseudowire configuration:

• show cem circuit—Displays information about the circuit state, administrative state, the CEM ID of thecircuit, and the interface on which it is configured. If xconnect is configured under the circuit, thecommand output also includes information about the attachment circuit status.

Router# show cem circuit?

<0-504> CEM IDdetail Detailed information of cem ckt(s)interface CEM Interfacesummary 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 --/--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/13/1, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVEController state: down, T3 state: upIdle Pattern: 0x55, Idle CAS: 0x8Dejitter: 10 (In use: 0)Payload Size: 1024Framing: UnframedCEM Defects SetNone




Overview of Circuit EmulationConfiguring CEM Parameter on CEM Interface


• show cem circuit summary—Displays the number of circuits which are up or down for each interface.

Router# show cem circuit summary

CEM Int. Total Active Inactive--------------------------------------CEM0/1/0 1 1 0

• show running configuration—The show running configuration command shows detail on each CEMgroup.

Circuit Emulation Service over Packet-Switched NetworkCESoPSN is a method for encapsulating structured (NxDS0) TDM signals as pseudowires over packetswitching networks.

Restrictions for CESoPSN on T3 Interface

• The maximum sacle is 1344 cem interface.

• Changing framing from C-bit to M13 not supported where as Changing framing from g751 to g832 issupported.

• CT3-E1 and CE3-T1 is not supported (only CT3-T1 and CE3-E1 is supported).

• DS0 loopback is not supported.

• The alarm forwarding is not supported on the T1 interface.

• The card protection is not supported on the T1 interface.

Configuring CEM Group for CESoPSN on T3 Interface

The following section describes how to configure a CEM group for CESoPSN on the T3 interface:

controller MediaType 0/5/1mode t3channelizedcontroller T3 0/5/1framing c-bitcablelength shortt1 1 cem-group 1 timeslots 1-10

Verifying CEM for CESoPSN on T3 Interface

Use the following commands to verify the pseudowire configuration for CESoPSN:


Overview of Circuit EmulationCircuit Emulation Service over Packet-Switched Network

• show cem circuit—Displays information about the circuit state, administrative state, the CEM IDof 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.

• show mpls l2 vc—Displays information about the MPLS VC.

• show mpls l2 vc detail—Displays detailed information about the MPLS VC.

Router# show controllers e3 0/14/2E3 0/14/2 is up.Hardware is -48T3E3-CEApplique type is Channelized E3No alarms detected.Framing is E3 G751, Line Code is HDB3, Cablelength Short less than 225ftBER thresholds: SF = 10e-10 SD = 10e-10Clock Source is internal, National Bit 0Equipment customer loopback







E1 1 is uptimeslots: 1-20No alarms detected.Framing is crc4, Clock Source is Internal, National bits are 0x1F.Data in current interval (250 seconds elapsed):


Overview of Circuit EmulationVerifying CEM for CESoPSN on T3 Interface

Near End0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavailable Secs, 0 Stuffed Secs0 Path Failures, 0 SEF/AIS Secs






router# sh mpls l2 vc interface cem 0/14/0 0

Local intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------CE0/14/0 CESoPSN Basic 0 1.1.1.1 9999 UP

Router# sh mpls l2transport vc 9090 detailLocal interface: CE0/14/2 up, line protocol up, CESoPSN Basic 0 upDestination address: 1.1.1.1, VC ID: 9090, VC status: upOutput interface: Te0/12/0, imposed label stack {130}Preferred path: not configuredDefault path: activeNext hop: 123.123.123.1

Create time: 00:18:44, last status change time: 00:18:30Last label FSM state change time: 00:18:30

Signaling protocol: LDP, peer 1.1.1.1:0 upTargeted Hello: 2.2.2.2(LDP Id) -> 1.1.1.1, LDP is UPGraceful restart: not configured and not enabledNon stop routing: configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No fault


Overview of Circuit EmulationVerifying CEM for CESoPSN on T3 Interface

Last local AC circuit status rcvd: No faultLast local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 130, remote 130Group ID: local 207, remote 220MTU: local 0, remote 0Remote interface description:

Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)SSO Descriptor: 1.1.1.1/9090, local label: 130Dataplane:SSM segment/switch IDs: 1237749/557811 (used), PWID: 114

VC statistics:transit packet totals: receive 0, send 0transit byte totals: receive 0, send 0transit packet drops: receive 0, seq error 0, send 0

Router# sh cem circuit interface cem 0/14/2 0

CEM0/14/2, ID: 0, Line: UP, Admin: UP, Ckt: ACTIVEMode :Channelized-E1, E1: 1, CEM Mode: E1-CESoPController state: up, T1 state: upIdle Pattern: 0xFF, Idle CAS: 0x8Dejitter: 5 (In use: 0)Payload Size: 160Framing: Framed (DS0 channels: 1-20)CEM Defects SetNone



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

Configuring DS1 Local Connect on T3/E3 Interface

The following section describes how to configure the first segment for DS1 local connection:

enableconfigure terminalcontroller MediaType 0/5/7mode e3channelized mode e1controller E3 0/5/7e1 2 cem-group 1 timeslots 1-10

The following section describes how to configure the second segment for DS1 local connection:


Overview of Circuit EmulationConfiguring DS1 Local Connect on T3/E3 Interface

enableconfigure terminalcontroller MediaType 0/5/2mode e3channelized mode e1controller E3 0/5/2e1 2 cem-group 1 timeslots 1-10

The following section describes how to create a DS1 local connection:

enableconfigure terminalconnect ds1_connect CEM0/5/7 1 CEM CEM0/5/2 1

Verifying DS1 Local Connect on T3 Interface

Use the following commands to verify the DS1 local connection:

• show connection name—Displays information about the connection state and segment state.

ASR907# sh xconnect all | i 0/14/7UP pri ac CE0/14/2:2(CESoPSN Basic) UP ac CE0/14/7:2(CESoPSN Basic) UP

ASR907# sh connection all | i 0/14/738 local_t3 CE0/14/2 CESP 2 CE0/14/7 CESP 2 UP

Verifying DS1 Local Connect on T3 Interface

Use the following commands to verify the DS1 local connection:

• show connection name—Displays information about the connection state and segment state.

ASR907# sh xconnect all | i 0/14/7UP pri ac CE0/14/2:2(CESoPSN Basic) UP ac CE0/14/7:2(CESoPSN Basic) UP

ASR907# sh connection all | i 0/14/738 local_t3 CE0/14/2 CESP 2 CE0/14/7 CESP 2 UP

Associated CommandsThe following commands are used to configure pseudowire:

URLCommands


cem-group


payload-size dejitter-buffer


class cem


Overview of Circuit EmulationVerifying DS1 Local Connect on T3 Interface










URLCommands


controller t1


xconnect


show controllers t3

Additional References for Configuring Pseudowire

Related Documents



Standards and RFCs

TitleStandard/RFC

There are no standards and RFCs for this feature.—

MIBs

MIBs LinkMIB



—


Overview of Circuit EmulationAdditional References for Configuring Pseudowire













LinkDescription







C H A P T E R 3Alarm History

Alarm history or the alarm persistence feature enables the maintenance of the history of the port and the pathalarms of 48-Port T3/E3 CEM Interface Module.

The history of the port-level and path-level alarms are saved into a file and is retained for monitoring networkevents.

• Alarm History Restrictions, on page 59• Configuring Alarm History, on page 60• Verification of Alarm History Configuration, on page 60• Associated Commands, on page 61• Additional References for Alarm History, on page 61

Alarm History RestrictionsThe following restrictions apply for the alarm history feature:

• Only port and path level alarm history or alarm persistency is supported.

• Persistence of T1/E1 alarms on a Channelized T3/E3 port is not supported.

• Two new files are created after each reboot.

• The primary and secondary log file are created during feature initialization. The primary log file saves10000 alarms. When the threshold of 10000 alarms in the primary log file is crossed, the subsequent10000 alarms are saved in the secondary log file. After crossing the threshold of 10000 alarms in thesecondary log file, the content of primary log file is cleared and is replaced with the subsequent alarms.

• When a primary file switches to a secondary file and vice versa, the following happens:

• An information level syslog message is displayed.• An informatory message is written in the file where subsequent alarms are stored.

• When RSP switchover happens, the alarm history files are not copied to the new active RSP. Two newfiles are created in the new active RSP.

• When you re-configure alarm history or alarm persistence feature, two new files are created.


Configuring Alarm HistoryThe configuration of alarm history helps in defining the periodicity or the interval at which the alarm entriesare saved in the designated file. To configure alarm history:enableconfigure terminalservice alarm persistency interval <20-600>end

When alarm history is configured, two log files are created in bootflash:tracelogs in the following format:<persistent_alarm[1/2][TIME_STAMP(DD_MMMM_YYYY_HH_MM_SSS)].log>

The syslog message is displayed as the following after configuration:*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_INFO_PROCESS_CREATE: createdmcprp_spa_persistence_logger process:292*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_CHUNK_INFO_CREATED: chunk pool creationfor alarm_info is successful*Jun 15 10:16:51.270: %ALARM_PERSISTENCY-6-ALARM_CHUNK_QUEUE_CREATED: chunk pool foralarm_queue is successful*Jun 15 10:16:51.283: %ALARM_PERSISTENCY-6-ALARM_INFO_FILE_CREATED: Successfully created/bootflash/tracelogs/persistent_alarm_1.15_June_2016_10_16__270.log fileRouter#*Jun 15 10:16:51.295: %ALARM_PERSISTENCY-6-ALARM_INFO_FILE_CREATED: Successfully created/bootflash/tracelogs/persistent_alarm_2.15_June_2016_10_16__270.log file*Jun 15 10:16:52.541: %SYS-5-CONFIG_I: Configured from console by consoleRouter#

Verification of Alarm History ConfigurationUse the show process | include persis command to verify the validity of the process.Router#show process | include persis292 Msi 13F0D4AC 0 49 010328/12000 0 mcprp_spa_persisRouter#

Verify the contents of the persistent alarm log files using the following commands:Router#dir bootflash:tracelogs/*persistent*Directory of bootflash:tracelogs/*persistent*394172 -rw- 1606 Jun 15 2016 07:50:39 +00:00persistent_alarm_1.15_June_2016_07_46__158.log394173 -rw- 6299 Jun 15 2016 07:50:38 +00:00persistent_alarm_2.15_June_2016_07_46__158.log6185086976 bytes total (4867022848 bytes free)Router#

Router#more bootflash:tracelogs/persistent_alarm_1.15_June_2016_07_46__158.logAt:15_June_2016_07_50__916 contents of persistent_alarm_2.15_June_2016_07_46__158.log arefull, so switched to this file*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |6 |4|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |6 |4|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |1|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |1|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |2


Alarm HistoryConfiguring Alarm History

|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |2|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED*07:50:19.360 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |3|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:19.361 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |3|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED*07:50:19.361 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |4|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:19.361 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |2 |1 |7 |4|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_PATH_LOP|RAISED*07:50:23.333 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |1 |1 |1 |1|SONET_SDH_PATH_VT/TU_ALARM|MAJOR|VT_UNEQUIPPED|CLEARED*07:50:27.335 UTC Wed Jun 15 2016|SLOT_0 |BAY_3 |PORT_0 |1 |1 |1 |1|SONET_SDH_PATH_VT/TU_PDH_DS1_ALARM|NA|DS1_AIS|CLEARED

Router#

Associated CommandsThe following commands are used to configure alarm history:

LinksCommands

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-s1.html#wp3501057143

service alarm persistency interval


show process | include persis

Additional References for Alarm HistoryRelated Documents



Standards

TitleStandards

There are no standards for this feature.—


Alarm HistoryAssociated Commands








MIBs

MIBs LinkMIB



—

RFCs

TitleRFCs

There are no RFCs for this feature.—


LinkDescription





Alarm HistoryAdditional References for Alarm History



C H A P T E R 4Clock Recovery System for SAToP

The Clock Recovery System recovers the service clock using Adaptive Clock Recovery (ACR) and DifferentialClock Recovery (DCR).

• Finding Feature Information, on page 63• Information About Clock Recovery, on page 63• Prerequisites for Clock Recovery, on page 65• Restrictions for Clock Recovery, on page 65• How to Configure ACR and DCR, on page 65• Associated Commands, on page 70• Additional References for Clock Recovery, on page 71

Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats andfeature information, see Bug Search Tool and the release notes for your platform and software release. Tofind information about the features documented in this module, and to see a list of the releases in which eachfeature is supported, see the feature information table.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support.To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Information About Clock Recovery

Adaptive Clock Recovery (ACR)Adaptive Clock Recovery (ACR) is an averaging process that negates the effect of random packet delayvariation and captures the average rate of transmission of the original bit stream. ACR recovers the originalclock for a synchronous data stream from the actual payload of the data stream. In other words, a synchronousclock is derived from an asynchronous packet stream. ACR is a technique where the clock from the TDMdomain is mapped through the packet domain, but is most commonly used for Circuit Emulation (CEM).ACR is supported on unframed and framed modes of SAToP.


https://tools.cisco.com/bugsearch/search

http://www.cisco.com/go/cfn


Effective Cisco IOS XE Everest 16.5.1, ACR is supported on the 8-port T1/E1 interface module.

Differential Clock Recovery (DCR)Differential Clock Recovery (DCR) is another technique used for Circuit Emulation (CEM) to recover clocksbased on the difference between PE clocks. TDM clock frequency are tuned to receive differential timingmessages from the sending end to the receiving end. A traceable clock is used at each end, which ensures therecovered clock is not affected by packet transfer. DCR is supported on unframed and framed modes ofSAToP.


Benefits of Clock Recovery• Customer-edge devices (CEs) can have different clock from that of the Provide-edge devices (PEs).


Clock Recovery System for SAToPDifferential Clock Recovery (DCR)

Scaling Information

Pseudowires Supported (Number of Clocks Derived)IM Card

134448-Port T3/E3 CEM Interface Module

Prerequisites for Clock Recovery• The clock of interface modules must be used as service clock.

• CEM must be configured before configuring the global clock recovery.

• RTP must be enabled for DCR in CEM, as the differential clock information is transferred in the RTPheader.

Restrictions for Clock Recovery• The reference clock source is used and locked to a single clock.

• The clock ID should be unique for a particular interface module for ACR or DCR configuration.

• ACR clock configuration under each controller should be performed before configuring CEM group.

How to Configure ACR and DCR

Configuring ACR for T3/E3

Configuring Adaptive Clock Recovery of T3/E3 Interfaces for SAToP

Before You Begin

• The node (router) on which the 48-Port T3/E3 interface module is configured for ACR, must have itsown clock derived from BITS/GPS/Stratum clock.

• The minimum packet size of CEM pseudowires on the network that delivers robust clock recovery is256 bytes.

To configure the clock on T3/E3 interfaces for SAToP in controller mode, use the following commands:

enableconfigure terminalcontroller t3 0/0/1clock source recovered 1cem-group 0 unframedexit

To configure the clock recovery on T3/E3 interfaces in global configurationmode, use the following commands:


Clock Recovery System for SAToPPrerequisites for Clock Recovery

recovered-clock 0 0clock recovered 1 adaptive cem 1 0exit

The clock configuration on controller must be done before configuring the clock recovery on globalconfiguration mode.

Note

Verifying Adaptive Clock Recovery Configuration of T3/E3 Interfaces for SAToP

Use the show recovered-clock command to verify the adaptive clock recovery of T3/E3 interfaces for SAToP:

Router# show recovered-clock

Recovered clock status for subslot 0/4---------------------------------------Clock Type Mode CEM Status Frequency Offset(ppb) Circuit-No

0 DS3 ADAPTIVE 0 ACQUIRED n/a 0 (Port)

Use the show running-config | section command to verify the configuration of adaptive clock of T3/E3interfaces:

Router# show running-config | section 0/0/1controller MediaType 0/0/1mode t3controller T3 0/0/1cem-group 0 unframedclock source recovered 1cablelength 224interface CEM0/0/1no ip addresscem 0

Use the show running-config | section recovered-clock command to verify the recovery of adaptive clockof T3/E3 interfaces:

Router# show running-config | section recovered-clockrecovered-clock 0 0clock recovered 1 adaptive cem 1 0

Configuring DCR for T3/E3

Configuring Differential Clock Recovery of T3/E3 Interfaces for SAToP

Before You Begin

• Before you start configuring DCR, RTP must be enabled on the CEM interface. The RTP is used to carrythe differential time.



Clock Recovery System for SAToPVerifying Adaptive Clock Recovery Configuration of T3/E3 Interfaces for SAToP

To configure differential clock recovery on T3/E3 interface for SAToP in controller mode, use the followingcommands:

enableconfigure terminalcontroller t3 0/0/1clock source recovered 1cem-group 0 unframedexit

To configure RTP header under interface, use the following commands:

interface cem 0/0/1cem 0rtp-present

To configure differential clock recovery of T3/E3 interface in global configuration mode, use the followingcommands:

recovered-clock 0 0clock recovered 1 differential cem 1 0exit


Note

Verifying the Differential Clock Recovery Configuration of T3/E3 Interfaces for SAToP

Use the show recovered-clock command to verify the differential clock recovery of T3/E3 interfaces forSAToP:


Recovered clock status for subslot 0/4----------------------------------------Clock Type Mode CEM Status Frequency Offset(ppb) Circuit-No

0 DS3 DIFFERENTIAL 0 ACQUIRED n/a 0 (Port)

Use the show running-config | section command to verify the configuration of differential clock of T3/E3interfaces for SAToP:

Router# show running-config | section 0/0/1controller MediaType 0/0/1mode t3controller T3 0/0/1cem-group 0 unframedclock source recovered 1cablelength 224interface CEM0/0/1no ip addresscem 0rtp-present


Clock Recovery System for SAToPVerifying the Differential Clock Recovery Configuration of T3/E3 Interfaces for SAToP

Use the show running-config | section recovered-clock command to verify the recovery of differentialclock of T3/E3 interfaces:

Router# show running-config | section recovered-clockrecovered-clock 0 0clock recovered 1 differential cem 1 0

Configuring ACR for Channelized T3/T1 or E3/E1

Configuring Adaptive Clock Recovery of Channelized T3/T1 or E3/E1 Interfaces for SAToP

Before You Begin

• The node (chassis) on which the T3/T1 or E3/E1 is configured for ACR, has to have its own clockderived from BITS/GPS/Stratum clock.


To configure adaptive clock on a channelized T3/T1 or E3/E1 interfaces under controller for SAToP incontroller mode, use the following commands:

enableconfigure terminalcontroller t3 0/0/1t1 1 clock source recovered 1t1 1 cem-group 0 unframedexit

To configure recovery of adaptive clock of channelized T3/T1 or E3/E1 interfaces in global configurationmode, use the following commands:

recovered-clock 0 0clock recovered 1 adaptive cem 1 0exit


Note

To remove the clock configuration in ACR and DCR, you must remove the recovery clock configuration inglobal configuration mode and then remove the controller configuration.

Verifying the Adaptive Clock Recovery Configuration of Channelized T3/T1 or E3/E1 Interfaces for SAToP

Use the show recovered-clock command to verify the adaptive clock recovery of T3/T1 or E3/E1 interfacesfor SAToP:


Recovered clock status for subslot 0/4----------------------------------------


Clock Recovery System for SAToPConfiguring ACR for Channelized T3/T1 or E3/E1

Clock Type Mode CEM Status Frequency Offset(ppb) Circuit-No0 DS3-ds1 ADAPTIVE 0 ACQUIRED n/a 0/1 (Port/t1)

Use the show running-config | section command to verify the configuration of adaptive clock of channelizedT3/T1 or E3/E1 interfaces:

Router# show running-config | section 0/0/1controller MediaType 0/0/1mode t3controller T3 0/0/1framing c-bitcablelength 224t1 1 cem-group 0 unframedt1 1 clock source recovered 1interface CEM0/0/1no ip addresscem 0

Use the show running-config | section recovered-clock command to verify the recovery of adaptive clockof channelized T3/T1 or E3/E1 interfaces:

Router# show running-config | section recovered-clockrecovered-clock 0 0clock recovered 1 adaptive cem 1 0

Configuring DCR for Channelized T3/T1 or E3/E1

Configuring Differential Clock Recovery of Channelized T3/T1 or E3/E1 Interfaces for SAToP

Before You Begin

• Before you start configuring DCR, RTP must be enabled on the CEM interface. The RTP is used to carrythe differential time.


To configure differential clock on a channelized T3/T1 or E3/E1 interfaces under controller in controllermode, use the following commands:

enableconfigure terminalcontroller t30/0/1t1 1 clock source recovered 1t1 1 cem-group 0 unframedexit

To configure RTP header under channelized T3/T1 or E3/E1 interfaces, use the following commands:

interface cem 0/0/1cem 0rtp-present

To configure recovery of differential clock of channelized T3/T1 or E3/E1 interfaces in global configurationmode, use the following commands:


Clock Recovery System for SAToPConfiguring DCR for Channelized T3/T1 or E3/E1

recovered-clock 0 0clock recovered 1 differential cem 1 0exit


Note

Verifying the Differential Clock Recovery Configuration of Channelized T3/T1 or E3/E1 Interfaces for SAToP

Use the show recovered-clock command to verify the differential clock recovery of T3/T1 or E3/E1 interfacesfor SAToP:


Recovered clock status for subslot 0/4----------------------------------------

Clock Type Mode CEM Status Frequency Offset(ppb) Circuit-No

0 DS3-ds1 DIFFERENTIAL 0 ACQUIRED n/a 0/1 (Port/t1)

Use the show running-config | section command to verify the configuration of differential clock of channelizedT3/T1 or E3/E1 interfaces:

Router# show running-config | section 0/0/1controller MediaType 0/0/1mode t3controller T3 0/0/1framing c-bitcablelength 224t1 1 cem-group 0 unframedt1 1 clock source recovered 1interface CEM0/0/1no ip addresscem 0rtp-present

Use the show running-config | section recovered-clock command to verify the recovery of differentialclock of channelized T3/T1 or E3/E1 interfaces:

Router# show running-config | section recovered-clockrecovered-clock 0 0clock recovered 1 differential cem 1 0

Associated CommandsThe commands used to adaptive clock recovery and differential clock recovery on 48-Ports T3/E3 InterfaceModule.


Clock Recovery System for SAToPVerifying the Differential Clock Recovery Configuration of Channelized T3/T1 or E3/E1 Interfaces for SAToP

URLCommands


clock recovered adaptive cem


cem-group

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/command/ir-cr-book/ir-o1.html#wp8262293900

recovered-clock


controller t3/e3


clock-source

Additional References for Clock RecoveryRelated Documents



Standards and RFCs

TitleStandard/RFC

Timing and synchronization aspects in packet networksITU -T G.8261

MIBs

MIBs LinkMIB



—


Clock Recovery System for SAToPAdditional References for Clock Recovery



















LinkDescription





Clock Recovery System for SAToPAdditional References for Clock Recovery


C H A P T E R 5Configuring Synchronous Ethernet ESMC andSSM

Synchronous Ethernet is an extension of Ethernet designed to provide the reliability found in traditionalSONET/SDH and T1/E1 networks to Ethernet packet networks by incorporating clock synchronization featuresthat support the Synchronization Status Message (SSM) and Ethernet Synchronization Message Channel(ESMC) for synchronous Ethernet clock synchronization.

The following sections describe ESMC and SSM support on the Cisco ASR 903 Series Router.

• Understanding Synchronous Ethernet ESMC and SSM, on page 73• Restrictions and Usage Guidelines, on page 75• Configuring Synchronous Ethernet ESMC and SSM, on page 75• Managing Clock Source Selection, on page 79• Verifying the Configuration, on page 81• Troubleshooting, on page 81• Configuration Examples, on page 83• SSM Support on Cisco 48-Port T3/E3 CEM Interface Module, on page 83

Understanding Synchronous Ethernet ESMC and SSMEthernet SynchronizationMessage Channel (ESMC) incorporates the Synchronization StatusMessage (SSM)used in Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) networks.While SONET and SDH transmit the SSM in a fixed location within the frame, ESMC transmits the SSMusing a protocol: the IEEE 802.3 Organization-Specific Slow Protocol (OSSP) standard.

The ESMC carries a Quality Level (QL) value identifying the clock quality of a given synchronous Ethernettiming source. Clock quality values help a synchronous Ethernet node derive timing from the most reliablesource and prevent timing loops.

When configured to use synchronous Ethernet, the Cisco ASR 903 Series Router synchronizes to the bestavailable clock source. If no better clock sources are available, the router remains synchronized to the currentclock source.

The router supports two clock selectionmodes: QL-enabled and QL-disabled. Eachmode uses different criteriato select the best available clock source.


The router can only operate in one clock selection mode at a time.Note

Conversely, PTP clock sources are not supported with synchronous Ethernet. However, you can use hybridclocking to allow the router to obtain frequency using Synchronous Ethernet and phase using PTP.

Note

Clock Selection ModesThe Cisco ASR 903 Series Router supports two clock selection modes, which are described in the followingsections.

QL-Enabled Mode

In QL-enabled mode, the router considers the following parameters when selecting a clock source:

• Clock quality level (QL)• Clock availability• Priority

QL-Disabled Mode

In QL-disabled mode, the router considers the following parameters when selecting a clock source:

• Clock availability• Priority

You can use override the default clock selection using the commands described in theManaging Clock SourceSelection, on page 79.

Note

Managing Clock SelectionYou can manage clock selection by changing the priority of the clock sources; you can also influence clockselection by modifying modify the following clock properties:

• Hold-Off Time: If a clock source goes down, the router waits for a specific hold-off time before removingthe clock source from the clock selection process. By default, the value of hold-off time is 300 ms.

• Wait to Restore: The amount of time that the router waits before including a newly active synchronousEthernet clock source in clock selection. The default value is 300 seconds.

• Force Switch: Forces a switch to a clock source regardless of clock availability or quality.• Manual Switch: Manually selects a clock source, provided the clock source has a equal or higher qualitylevel than the current source.

For more information about how to use these features, see Managing Clock Source Selection, on page 79.


Configuring Synchronous Ethernet ESMC and SSMClock Selection Modes

Restrictions and Usage GuidelinesThe following restrictions apply when configuring synchronous Ethernet SSM and ESMC:

• To use the network-clock synchronization ssm option command, ensure that the router configurationdoes not include the following:

• Input clock source• Network clock quality level• Network clock source quality source (synchronous Ethernet interfaces)

• The network-clock synchronization ssm option commandmust be compatible with the network-clockeec command in the configuration.

• To use the network-clock synchronization ssm option command, ensure that there is not a networkclocking configuration applied to sychronous Ethernet interfaces, BITS interfaces, and timing portinterfaces.

• SSM and ESMC are SSO-coexistent, but not SSO-compliant. The router goes into hold-over mode duringswitchover and restarts clock selection when the switchover is complete.

• It is recommended that you do not configure multiple input sources with the same priority as this impactsthe TSM (Switching message delay).

• You can configure a maximum of 4 clock sources on interfacemodules, with a maximum of 2 per interfacemodule. This limitation applies to both synchronous Ethernet and TDM interfaces.

• Copper SFP is not supported for SyncE Rx and Tx on the uplink interfaces. SyncE Rx and Tx is supportedon the uplink interfaces only for fiber SFP only.

Configuring Synchronous Ethernet ESMC and SSMFollow these steps to configure ESMC and SSM on the Cisco ASR 903 Series Router.

SUMMARY STEPS

1. enable2. configure terminal3. network-clock synchronization automatic4. network-clock eec {1 | 2}5. network-clock synchronization ssm option {1 | 2 {GEN1 | GEN2}}6. network-clock input-source priority {interface interface_name slot/card/port | ptp domain domain_num

| {external {R0 | R1 [ { t1 {sf | esf } linecode {ami | b8zs} line-build-out length} | e1 [crc4 | fas][125ohm | 75ohm] linecode [hdb3 | ami] } | 10m] }}

7. network-clock synchronization mode ql-enabled8. network-clock hold-off {0 | milliseconds} global9. network-clock wait-to-restore seconds global10. network-clock revertive11. esmc process12. network-clock external [r0 / r1 hold-off {0 |milliseconds}13. network-clock quality-level {tx | rx} value {interface interface-name slot/card/port | controller [E1|

BITS] slot/card/port | external [2m | 10m] }


Configuring Synchronous Ethernet ESMC and SSMRestrictions and Usage Guidelines

14. interface type number15. synchronous mode16. esmc mode [ql-disabled | tx | rx] value17. network-clock hold-off {0 | milliseconds}18. network-clock wait-to-restore seconds19. end

DETAILED STEPS

PurposeCommand or Action

Enables privileged EXEC mode.enableStep 1

Example: • Enter your password if prompted.

Router> enable

Enters global configuration mode.configure terminal

Example:

Step 2

Router# configure terminal

Enables the network clock selection algorithm. Thiscommand disables the Cisco-specific network clock

network-clock synchronization automatic

Example:

Step 3

process and turns on the G.781-based automatic clockselection process.

Router(config)# network-clock synchronizationautomatic This command must be configured before any

input source.Note

Specifies the Ethernet Equipment Clock (EEC) type. Validvalues are

network-clock eec {1 | 2}

Example:

Step 4

• 1—ITU-T G.8262 option 1 (2048)Router(config)# network-clock eec 1 • 2—ITU-T G.8262 option 2 and Telcordia GR-1244

(1544)

Configures the G.781 synchronization option used to sendsynchronizationmessages. The following guidelines applyfor this command:

network-clock synchronization ssm option {1 | 2 {GEN1| GEN2}}

Example:

Step 5

• Option 1 refers to G.781 synchronization option 1,which is designed for Europe. This is the defaultvalue.

Router(config)# network-clock synchronization ssmoption 2 GEN2

• Option 2 refers to G.781 synchronization option 2,which is designed for the United States.

• GEN1 specifies option 2 Generation 1synchronization.

• GEN2 specifies option 2 Generation 2synchronization.

Enables you to select an interface as an input clock for therouter. You can select the BITS, Gigabit Ethernet 0/0,

network-clock input-source priority {interfaceinterface_name slot/card/port | ptp domain domain_num

Step 6


Configuring Synchronous Ethernet ESMC and SSMConfiguring Synchronous Ethernet ESMC and SSM


Gigabit Ethernet 0/1 interfaces, or GPS interfaces, or anexternal interface.

| {external {R0 |R1 [ { t1 {sf | esf } linecode {ami | b8zs}line-build-out length} | e1 [crc4 | fas] [125ohm | 75ohm]linecode [hdb3 | ami] } | 10m] }} Before configuring ethernet intreface as clock

source, you should configure synchronousmodeunder interface configuration.

NoteExample:

Router(config)# network-clock input-source 1interface GigabitEthernet 0/0/1

Enables automatic selection of a clock source based onquality level (QL).

network-clock synchronization mode ql-enabled

Example:

Step 7

This command is disabled by default.NoteRouter(config)# network-clock synchronization modeql-enabled

(Optional) Configures a global hold-off timer specifyingthe amount of time that the router waits when a

network-clock hold-off {0 | milliseconds} global

Example:

Step 8

synchronous Ethernet clock source fails before takingaction.

Router(config)# network-clock hold-off 0 global

You can also specify a hold-off value for anindividual interface using the network-clockhold-off command in interface mode.

Note

(Optional) Configures a global wait-to-restore timer forsynchronous Ethernet clock sources. The timer specifies

network-clock wait-to-restore seconds global

Example:

Step 9

how long the router waits before including a restored clocksource in the clock selection process.

Router(config)# network-clock wait-to-restore 70global Valid values are 0 to 86400 seconds. The default value is

300 seconds.

You can also specify a wait-to-restore value foran individual interface using the network-clockwait-to-restore command in interface mode.

Note

(Optional) Sets the router in revertive switching modewhen recovering from a failure. To disable revertive mode,use the no form of this command.

network-clock revertive

Example:

Router(config)# network-clock revertive

Step 10

Enables the ESMC process globally.esmc process

Example:

Step 11

Router(config)# esmc process

Overrides the hold-off timer value for the externalinterface.

network-clock external [r0 / r1 hold-off {0 |milliseconds}

Example:

Step 12

Router(config)# network-clock external r0 hold-off0




Specifies a quality level for a line or external clock source.network-clock quality-level {tx | rx} value {interfaceinterface-name slot/card/port | controller [E1| BITS]slot/card/port | external [2m | 10m] }

Step 13

The available quality values depend on the G.781synchronization settings specified by the network-clocksynchronization ssm option command:Example:

Router(config)# network-clock quality-levelrx qL-pRC external R0 e1 cas crc4

• Option 1—Available values areQL-PRC,QL-SSU-A,QL-SSU-B, QL-SEC, and QL-DNU.

• Option 2, GEN1—Available values are QL-PRS,QL-STU,QL-ST2,QL-SMC,QL-ST4, andQL-DUS.

• Option 2, GEN 2—Available values are QL-PRS,QL-STU, QL-ST2, QL-TNC, QL-ST3, QL-SMC,QL-ST4, and QL-DUS.

Enters interface configuration mode.interface type number

Example:

Step 14

Router(config)# interface GigabitEthernet 0/0/1

Example:

Router(config-if)#

Configures the Ethernet interface to synchronous modeand automatically enables the ESMC and QL process onthe interface.

synchronous mode

Example:

Router(config-if)# synchronous mode

Step 15

Enables the ESMC process at the interface level. The noform of the command disables the ESMC process.

esmc mode [ql-disabled | tx | rx] value

Example:

Step 16

Router(config-if)# esmc mode rx QL-STU

(Optional) Configures an interface-specific hold-off timerspecifying the amount of time that the router waits when

network-clock hold-off {0 | milliseconds}

Example:

Step 17

a synchronous Ethernet clock source fails before takingaction.

Router(config-if)# network-clock hold-off 0

You can configure the hold-off time to either 0 or anyvalue between 50 to 10000 ms. The default value is 300ms.

(Optional) Configures the wait-to-restore timer for anindividual synchronous Ethernet interface.

network-clock wait-to-restore seconds

Example:

Step 18

Router(config-if)# network-clock wait-to-restore70

Exits interface configurationmode and returns to privilegedEXEC mode.

end

Example:

Step 19




Router(config-if)# end

What to do next

You can use the show network-clocks command to verify your configuration.

Managing Clock Source SelectionThe following sections describe how to manage the selection on the Cisco ASR 903 Series Router:

Specifying a Clock SourceThe following sections describe how to specify a synchronous Ethernet clock source during the clock selectionprocess:

Selecting a Specific Clock SourceTo select a specific interface as a synchronous Ethernet clock source, use the network-clock switch manualcommand in global configuration mode.

The new clock source must be of higher quality than the current clock source; otherwise the router does notselect the new clock source.

Note

PurposeCommand

Manually selects a synchronization source,provided the source is available and is withinthe range.

network-clock switch manual external R0 | R1{{E1 {crc4 | cas |fas}} {120ohms | 75ohms |

t0}} }

Router# network-clock switch manual external r0 e1crc4 120ohms t0

Disable a clock source selection.network-clock clear switch {t0 | external slot/card/port [10m| 2m]}

Router# network-clock clear switch t0

Forcing a Clock Source SelectionTo force the router to use a specific synchronous Ethernet clock source, use the network-clock switch forcecommand in global configuration mode.

This command selects the new clock regardless of availability or quality.Note


Configuring Synchronous Ethernet ESMC and SSMManaging Clock Source Selection

Forcing a clock source selection overrides a clock selection using the network-clock switchmanual command.Note

PurposeCommand

Forces the router to use a specific synchronousEthernet clock source, regardless of clockquality or availability.

network-clock switch force external R0 | R1 {{E1 {crc4| cas |fas}} {120ohms {75ohms | t0 }} }

Router# network-clock switch force r0 e1 crc4120ohms t0

Disable a clock source selection.network-clock clear switch {t0 | external slot/card/port[10m | 2m]}


Disabling Clock Source Specification CommandsTo disable a network-clock switch manual or network-clock switch force configuration and revert to thedefault clock source selection process, use the network-clock clear switch command.

PurposeCommand

Disable a clock source selection.network-clock clear switch {t0 | external slot/card/port [10m | 2m]}


Disabling a Clock SourceThe following sections describe how to manage the synchronous Ethernet clock sources that are available forclock selection:

Locking Out a Clock SourceTo prevent the router from selecting a specific synchronous Ethernet clock source, use the network-clock setlockout command in global configuration mode.

PurposeCommand

Prevents the router from selecting aspecific synchronous Ethernet clocksource.

network-clock set lockout {interfaceinterface_name slot/card/port | external {R0 | R1 [ {

t1 {sf | esf } linecode {ami | b8zs}} | e1 [crc4| fas] linecode [hdb3 | ami]}

Router# network-clock set lockout interface GigabitEthernet0/0/0


Configuring Synchronous Ethernet ESMC and SSMDisabling Clock Source Specification Commands

PurposeCommand

Disable a lockout configuration on asynchronous Ethernet clock source.

network-clock clear lockout {interface interface_nameslot/card/port | external {R0 | R1 [ { t1 {sf | esf } linecode {ami |b8zs}} | e1 [crc4 | fas] linecode [hdb3 | ami] }

Router# network-clock clear lockout interfaceGigabitEthernet 0/0/0

Restoring a Clock SourceTo restore a clock in a lockout condition to the pool of available clock sources, use the network-clock clearlockout command in global configuration mode.

PurposeCommand

Forces the router to use a specificsynchronous Ethernet clock source,regardless of clock quality or availability.

network-clock clear lockout {interfaceinterface_name slot/card/port | external external{R0 | R1 [ { t1 {sf | esf } linecode {ami |

b8zs}} | e1 [crc4 | fas] linecode [hdb3 | ami]}

Router# network-clock clear lockout interfaceGigabitEthernet 0/0/0

Verifying the ConfigurationYou can use the following commands to verify your configuration:

• show esmc—Displays the ESMC configuration.• show esmc detail—Displays the details of the ESMC parameters at the global and interface levels.• show network-clock synchronization—Displays the router clock synchronization state.• show network-clock synchronization detail—Displays the details of network clock synchronizationparameters at the global and interface levels.

TroubleshootingTable 2: SyncE Debug Commands , on page 82 list the debug commands that are available for troubleshootingthe SyncE configuration on the Cisco ASR 903 Series Router:

We recommend that you do not use debug commands without TAC supervision.Caution


Configuring Synchronous Ethernet ESMC and SSMRestoring a Clock Source

Table 2: SyncE Debug Commands

PurposeDebug Command

Debugs issues related to the network clock includingactive-standby selection, alarms, and OOR messages.

debug platform network-clock

Debugs issues related to network clock selection.debug network-clock

These commands verify whether the ESMC packets aretransmitted and received with proper quality-level values.

debug esmc error

debug esmc event

debug esmc packet [interface interface-name]

debug esmc packet rx [interface interface-name]

debug esmc packet tx [interface interface-name]

Table 3: Troubleshooting Scenarios , on page 82 provides the information about troubleshooting yourconfiguration

Table 3: Troubleshooting Scenarios

SolutionProblem

• Verify that there are no alarms on the interfaces using the shownetwork-clock synchronization detail command.

• Ensure that the nonrevertive configurations are in place.• Reproduce the issue and collect the logs using the debug network-clockerrors, debug network-clock event, and debug network-clock smcommands. Contact Cisco Technical Support if the issue persists.

Clock selection

• Ensure that there is no framing mismatch with the SSM option.• Reproduce the issue using the debug network-clock errors and debugnetwork-clock event commands.

Incorrect QL values

• Reproduce the issue using the debug platform network-clock commandenabled in the RSP. Alternatively, enable the debug network-clock eventand debug network-clock errors commands.

Alarms

• Verify that there are no alarms on the interfaces using the shownetwork-clock synchronization detail command.

• Use the show network-clock synchronization command to confirm ifthe system is in revertive mode or nonrevertive mode and verify thenon-revertive configurations.

• Reproduce the current issue and collect the logs using the debugnetwork-clock errors, debug network-clock event, and debug network-clocksm RSP commands.

Incorrect clock limit set orqueue limit disabledmode


Configuring Synchronous Ethernet ESMC and SSMTroubleshooting

SolutionProblem

• Use the network clock synchronization SSM (option 1 |option 2)command to confirm that there is no framingmismatch. Use the show runinterface command to validate the framing for a specific interface. Forthe SSM option 1, framing should be SDH or E1, and for SSM option 2,it should be T1.

• Reproduce the issue using the debug network-clock errors and debugnetwork-clock event RSP commands.

Incorrect QL valueswhenyou use the shownetwork-clocksynchronization detailcommand.

Configuration Examples

Example: Input Synchronous Ethernet ClockingThe following example shows how to configure the router to use the BITS interface and two Gigabit Ethernetinterfaces as input synchronous Ethernet timing sources. The configuration enables SSM on the BITS port.

!Interface GigabitEthernet0/0

synchronous modenetwork-clock wait-to-restore 720

!Interface GigabitEthernet0/1

synchronous mode!!network-clock synchronization automaticnetwork-clock input-source 1 External R0 e1 crc4network-clock input-source 1 gigabitethernet 0/0network-clock input-source 2 gigabitethernet 0/1network-clock synchronization mode QL-enabledno network-clock revertive

SSM Support on Cisco 48-Port T3/E3 CEM Interface ModuleSynchronization Status Message (SSM) is transported over T3 links using proprietary method. SSM enablesT3 to select the highest quality timing reference automatically and avoid the timing loops.

SSM is supported on Cisco 48-Port T3/E3 CEM Interface Module.

Effective IOS XE Everest 16.5.1, E3 mode is not supported.Note

Supported Quality LevelsThe quality levels supported on T3 are:

• GEN1—PRS, STU, ST2, ST3, SMC, ST4, and DUS


Configuring Synchronous Ethernet ESMC and SSMConfiguration Examples

• GEN2—PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, and DUS

Configuring SSM on Cisco 48-Port T3/E3 CEM Interface Moduleenableconfigure terminalcontroller media-type controller 0/5/0mode t3controller t3 0/0/0network-clock synchronization automaticnetwork-clock eec 1network-clock synchronization ssm option 2 GEN2network-clock input-source 10 controller t3 0/5/1network-clock synchronization mode ql-enablednetwork-clock hold-off 0network-clock wait-to-restore 70network-clock revertivenetwork-clock quality-level tx ql-prs controller t3 0/0/0network-clock quality-level rx ql-st2 controller t3 0/5/1network-clock hold-off 0network-clock wait-to-restore 70end

Configuring Clock Sourceenableconfigure terminalcontroller media-type controller 0/5/0mode t3controller t3 0/5/0clock source lineend

Verification of SSM ConfigurationUse the show network-clocks synchronization detail command to verify the SSM configuration on Cisco48-Port T3/E3 CEM Interface Module:show network-clock synchronization detailSymbols: En - Enable, Dis - Disable, Adis - Admin DisableNA - Not Applicable* - Synchronization source selected# - Synchronization source force selected& - Synchronization source manually switched

Automatic selection process : EnableEquipment Clock : 1544 (EEC-Option2)Clock State : Frequency LockedClock Mode : QL-EnableESMC : EnabledSSM Option : GEN1T0 : T3 0/0/21Hold-off (global) : 300 msWait-to-restore (global) : 0 secTsm Delay : 180 msRevertive : NoForce Switch: FALSEManual Switch: FALSENumber of synchronization sources: 1


Configuring Synchronous Ethernet ESMC and SSMConfiguring SSM on Cisco 48-Port T3/E3 CEM Interface Module

Squelch Threshold: QL-ST3sm(netsync NETCLK_QL_ENABLE), running yes, state 1ALast transition recorded: (begin)-> 2A (ql_mode_enable)-> 1A (src_added)-> 1A (ql_change)->1A (sf_change)-> 1A (ql_change)-> 1A

Nominated Interfaces

Interface SigType Mode/QL Prio QL_IN ESMC Tx ESMC RxInternal NA NA/Dis 251 QL-ST3 NA NA*T3 0/0/21 NA NA/En 2 QL-PRS NA NA

Interface:---------------------------------------------Local Interface: InternalSignal Type: NAMode: NA(Ql-enabled)SSM Tx: DISABLEDSSM Rx: DISABLEDPriority: 251QL Receive: QL-ST3QL Receive Configured: -QL Receive Overrided: -QL Transmit: -QL Transmit Configured: -Hold-off: 0Wait-to-restore: 0Lock Out: FALSESignal Fail: FALSEAlarms: FALSEActive Alarms: NoneSlot Disabled: FALSESNMP input source index: 1SNMP parent list index: 0Description: None

Local Interface: T3 0/0/21Signal Type: NAMode: NA(Ql-enabled)SSM Tx: ENABLEDSSM Rx: ENABLEDPriority: 2QL Receive: QL-PRSQL Receive Configured: QL-PRSQL Receive Overrided: -QL Transmit: -QL Transmit Configured: -Hold-off: 300Wait-to-restore: 0Lock Out: FALSESignal Fail: FALSEAlarms: FALSEActive Alarms: NoneSlot Disabled: FALSESNMP input source index: 8SNMP parent list index: 0Description: None


Configuring Synchronous Ethernet ESMC and SSMVerification of SSM Configuration


Configuring Synchronous Ethernet ESMC and SSMVerification of SSM Configuration

I N D E X

C

Circuit Emulation Service over Packet-Switched Network(CESoPSN 33, 39, 40, 51

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)IN-1

48-Port T3/E3 CEM Interface Module Configuration Guide, Cisco IOS XE Everest 16.6.1 (Cisco NCS 4200 Series)IN-2

INDEX