Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide
Configuring the CEoP and Channelized ATM SPAs
Downloads: This chapterpdf (PDF - 1.77MB) The complete bookPDF (PDF - 13.93MB) | Feedback

Table of Contents

Configuring the CEoP and Channelized ATM SPAs

Configuration Tasks

Specifying the Interface Address on a SPA

Configuring Port Usage (Overview)

Configuring the 24-Port Channelized T1/E1 ATM CEoP SPA

Configuring the 2-Port Channelized T3/E3 ATM CEoP SPA

Verifying 2-Port Channelized T3/E3 CEoP SPA configuration

Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT1.5

Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12

Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11

Configuring Circuit Emulation

Configuration Guidelines and Restrictions

Configuring a CEM Group

Configuring a CEM Class (Optional)

Configuring a CEM Pseudowire

Configuring TDM Local Switching

Configuration Example

Verifying

Local Switching Redundancy

Guidelines

Configuration

Configuration Example

Verifying

Configuring ATM

Configuring VC QoS on VP-PW CEoP SPAs

Restriction

Configuring an ATM Pseudowire

Configuring Pseudowire Redundancy (Optional)

Configuring T1

Configuring E1

Configuring T3

T3 Configuration Guidelines

Configuring Port Usage

Configuring the SPA for Clear-Channel ATM

Configuring SONET (OC-3)

SONET Controller Configuration

SDH Configuration for AU-4 C-12

SDH Configuration for AU-3 C-11

Configuring Inverse Multiplexing over ATM

IMA Configuration Guidelines

IMA Link Bundle Configuration Overview

Configuration Example

Configuring an IMA Link Bundle

Configuring IMA Group Parameters

Verifying the IMA Configuration

IMA Auto Restart Examples

Configuring Clocking

BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400

Guidelines

Configuration Tasks

Verifying

Configuring Clock Recovery

Verifying Clock Recovery

Configuring Out-of-Band Clocking

Benefits

Configuration Guidelines

Configuration Overview

Creating and Configuring the Master Clock Interface

Configuring the Slave Clock Interface

Verifying Out-of-Band Clocking

Removing the Out-of-Band Clocking Configuration

Out-of-Band Clocking Configuration Example

Configuring CEM Circuits for Out-of-Band Clocking Example

Configuring CEM Parameters

Configuring Payload Size (Optional)

Setting the Dejitter Buffer Size

Setting the Idle Pattern (Optional)

Enabling Dummy Mode

Setting the Dummy Pattern

Shutting Down a CEM Channel

Configuring Access Circuit Redundancy on CEoP and ATM SPAs

Restrictions and Usage Guidelines

Configuring the ACR Group

Verifying ACR Group

Configuring CEM, ATM, and IMA Interfaces

Verifying CEM Interface

Configure IMA-ACR Interface

Show Commands

Troubleshooting the ACR configuration

Configuring Layer 3 QoS on CEoP SPAs

Restrictions and Guidelines

Supported Interface for CEoP SPA

Configuration

Sample Configuration

Verifying the Configuration

Troubleshooting

Configuring AIS and RAI Alarm Forwarding in CESoPSN Mode on CEoP SPAs

Configuring SONET Mode

Configuring SDH AU-4 Mode

Configuring SDH AU-3 Mode

Configuring T1 Mode

Configuring E1 Mode

Configuration Restrictions

MR-APS Integration with Hot Standby Pseudowire

Failover Operations

Restrictions

Configuring MR-APS Integration with Hot Standby Pseudowire

Configuring MR-APS Integration with Hot Standby Pseudowire on a CEM Interface

Detailed Steps

Example

Configuring MR-APS Integration with Hot Standby Pseudowire on an IMA interface

Detailed Steps

Example

Verification

Troubleshooting Tips

Verifying the Interface Configuration

Configuring Cell Payload Scrambling on CEoP SPAs

Examples

Configuring the CEoP and Channelized ATM SPAs

This chapter provides information about configuring the Circuit Emulation over Packet (CEoP) shared port adapters (SPAs) on the Cisco 7600 series router. It contains the following sections:

For information about managing your system images and configuration files, see the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications for your Cisco IOS software release.

For more information about the commands used in this chapter, refer to the Cisco IOS Software Releases 12.2SR Command Reference s and to the Cisco IOS Software Releases 12.2SX Command References . Also refer to the related Cisco IOS Release 12.2 software command reference and master index publications. For more information, see the “$paratext>” section.

Configuration Tasks

This section describes the most common configurations for the CEoP SPAs on a Cisco 7600 series router. It contains procedures for the following:

Specifying the Interface Address on a SPA

Four CEoP SPAs can be installed in a SPA interface processor (SIP). Ports are numbered from left to right, beginning with 0. Single-port SPAs use only the port number 0. To configure or monitor SPA interfaces, you need to specify the physical location of the SIP, SPA, and interface in the command-line-interface (CLI). The interface address format is slot / subslot / port , where:

  • slot —Specifies the chassis slot number in the Cisco 7600 series router where the SIP is installed
  • subslot —Specifies the secondary slot of the SIP where the SPA is installed
  • port —Specifies the number of the individual interface port on a SPA

The following example shows how to specify the first interface (0) on a SPA installed in subslot 1 of the SIP in chassis slot 3:

Router(config)# interface cem 3/1/0
 

For more information about how to identify slots and subslots, see the “Identifying Slots and Subslots for SIPs, SSCs, and SPAs” section.

Configuring Port Usage (Overview)

The 24-Port Channelized T1/E1 ATM CEoP SPA and 1-Port Channelized OC-3 STM1 ATM CEoP SPA can be configured to run in the following modes:

  • Circuit emulation (CEM)
  • Channelized Asynchronous Transfer Mode (ATM)
  • Inverse Multiplexing over ATM (IMA)

The 2-Port Channelized T3/E3 ATM CEoP SPA, introduced in Cisco IOS Release 12.2(33)SRC, can be configured to run in ATM mode. The SPA does not currently support CEM or IMA mode.

The following tables show the commands to configure each of the SPAs for CEM or ATM. Detailed configuration instructions are provided in the sections that follow.

Configuring the 24-Port Channelized T1/E1 ATM CEoP SPA

To configure the 24-Port Channelized T1/E1 ATM CEoP SPA, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# card type {t1 | e1 } slot subslot

Selects a card type.

Step 2

Router(config)# controller { t1 | e1 } slot/subslot/port

Selects the controller for the SPA port to configure.

Step 3

Router(config-controller)# cem-group group unframed

Creates a SAToP CEM group and configures the port for clear-channel CEM mode.

Router(config-controller)# cem-group group timeslots 1-24

Creates a CESoPSN CEM group and configures the port for channelized CEM mode.

Router(config-controller)# atm

Configures the port for ATM and creates an ATM interface.

Router(config-controller)# ima-group group-number

Configures the interface to run in IMA mode, and assigns the interface to an IMA group.

Configuring the 2-Port Channelized T3/E3 ATM CEoP SPA

To configure the 2-Port Channelized T3/E3 ATM CEoP SPA, complete these steps:

SUMMARY STEPS


Step 1 enable

Step 2 configure terminal

Step 3 card type {t3 | e3 } slot subslot

Step 4 controller { t3 | e3 } slot/subslot/port

Step 5 channelized mode {t1 | e1}

Step 6 cem-group group unframed

or

{t1 } 1-28 cem-group group timeslots 1-24

{e1 } 1-21 cem-group group timeslots 1-31

or

atm

or

{t1 } 1-28 ima-group group-number

{e1 } 1-21 ima-group group-number

Step 7 exit

DETAILED STEPS

 

Command or Action
Purpose

Step 4

Router # enable

Enables privileged EXEC mode.

Step 5

Router# configure terminal

Enters global configuration mode.

Step 6

Router(config)# card type {t3 | e3 } slot subslot

or

Router(config)# [no] card type {t3 | e3 } slot subslot

Selects a card type.

or

Use no command to remove the card type.

Step 7

Router(config)# controller { t3 | e3 } slot/subslot/port

Selects the controller for the SPA port to configure.

Note Effective from Cisco IOS Release 15.1(1)S release, T3 and E3 card types are supported.

Step 8

Router(config-controller)# channelized mode {t1 | e1}

Swaps between the CT3-T1 and CT3-E1 modes. This is applicable only if the card type is T3.

Step 9

Router(config-controller)# cem-group group unframed

or

Router(config-controller)# [no] cem-group group unframed

Creates a SAToP CEM group and configures the port for clear-channel CEM mode.

or

To delete the CEM circuit and release the time slots, use the no cem-group group-number command.

Router(config-controller)# {t1 } 1-28 cem-group group timeslots 1-24

Router(config-controller)# {e1 } 1-21 cem-group group timeslots 1-31

Creates a CESoPSN CEM group and configures the port for channelized CEM mode.

Group number range is from 0 to 671.

Router(config-controller)# atm

or

Router(config-controller)# [no] atm

Configures the port to run in clear-channel ATM mode and creates an ATM interface to represent the port.

or

Use the no form of the command remove the link from the ATM.

Router(config-controller)# {t1 } 1-28 ima-group

group-number

Router(config-controller)# {e1 } 1-21 ima-group group-number

or

Router(config-controller)# [no] {t1 } 1-28 ima-group

group-number

Router(config-controller)# [no] {e1 } 1-21 ima-group group-number

Configures the interface to run in IMA mode, and assigns the interface to an IMA group.

Group number range is from 0 to 41.

or

Use the no form of the command remove the link from the IMA group.

Step 10

Router (config-if)# exit

Exits interface configuration mode and returns to privileged EXEC mode.


NoteSee“Configuring T3” section for information about the features that are not supported on the CEoP SPA in Cisco IOS Release 12.2SRC.


Restrictions and Usage Guidelines

Follow these restrictions and usage guidelines while configuring 2-Port Channelized T3/E3 CEoP SPA:

  • CEoP SPAs does not support Layer 3QoS.
  • Bridging featues such as bridging routed encapsulations (BRE), multipoint bridging(MPB), routed bridge encapsulation(RBE), and multi VLAN are not supported on CEoP.
  • E3 Channelization to E1 is not supported.
  • Maintenance Digital Link (MDL) is supported only for DSX3-C bit framing.
  • CEoP SPAs simultaneously supports multiple interface types.
  • Adaptive clock recovery is supported on 2-Port Channelized T3/E3 CEoP SPA.
  • Out-of-Band(OOB) clock recovery for CEM is not supported.
  • E3 or T3 ATM is not supported.

Sample Configuration for 2-Port Channelized T3/E3 CEoP SPA on Clear channel T3

Configure SPA in a T3 mode

Router(config)# card type T3 5 0
Router(config)# controller T3 5/0/0
 

Create an T3 ATM interface

Router(config-controller)# atm
 

Create CEM group

Router(config-controller)# cem-group 0 unframed

Sample Configuration for 2-Port Channelized T3/E3 CEoP SPA on Clear channel E3 mode

Configure SPA in a E3 mode

Router(config)# card type E3 5 0
Router(config)# controller E3 5/0/0
 

Create an E3 ATM interface

Router(config-controller)# atm
 

Create CEM group

Router(config-controller)# cem-group 0 unframed

Sample Configuration for 2-Port Channelized T3/E3 CEoP SPA on CT3-T1 Channelization mode

Configure SPA in a T3 mode

Router(config)# card type T3 5 0
Router(config)# controller T3 5/0/0
 

Create an T3 ATM interface

Router(config-controller)# t1 1 atm

 

Create a NxDS0 T1 CEM group

router(config-controller)# t1 2 cem-group 0 timeslots 1-12

 

Create two IMA groups (1 with two T1 members)

Router(config-controller)# t1 3 ima-group 5
Router(config-controller)# t1 4 ima-group 5

Sample Configuration for 2-Port Channelized T3/E3 CEoP SPA on CT3-E1 Channelization mode

Configure SPA in a T3 mode

Router(config)# card type T3 5 0
Router(config)# controller T3 5/0/0
 

Changing channelization to E1

Router(config)# controller T3 5/0/0
router(config-controller)# channelized mode e1
 

Create an E1 ATM interface

Router(config-controller)# e1 1 atm
 

Create a NxDS0 E1 CEM group

Router(config-controller)# e1 2 cem-group 0 timeslots 1-12
 

Create two IMA groups (1 with two E1 members)

Router(config-controller)# e1 3 ima-group 5
Router(config-controller)# e1 4 ima-group 5

Verifying 2-Port Channelized T3/E3 CEoP SPA configuration

Router# show controller t3 2/1/0
T3 2/1/0 is up.
Hardware is SPA-2CHT3-CE-ATM
Applique type is Clearchannel T3 ATM
No alarms detected.
Framing is M23, Line Code is B3ZS, Cablelength is 224
Clock Source is internal
Equipment customer loopback
Data in current interval (827 seconds elapsed):
0 Line Code Violations, 7 P-bit Coding Violation
0 C-bit Coding Violation, 2 P-bit Err Secs
0 P-bit Severely Err Secs, 3 Severely Err Framing Secs
17 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
0 Severely Errored Line Secs
0 Far-End Errored Secs, 0 Far-End Severely Errored Secs
0 CP-bit Far-end Unavailable Secs
0 Near-end path failures, 2 Far-end path failures
0 Far-end code violations, 10 FERF Defect Secs
0 AIS Defect Secs, 4 LOS Defect Secs
 
Router# show ip interface br
ATM2/1/0 unassigned YES unset up up
ATM2/1/1/1 unassigned YES unset up up
ATM2/1/ima0 unassigned YES unset up up
 
Router# show interface atm2/1/0
ATM2/1/0 is up, line protocol is up
Hardware is SPA-2CHT3-CE-ATM, address is 000c.862c.4d40 (bia 000c.862c.4d40)
MTU 4470 bytes, sub MTU 4470, BW 44209 Kbit/sec, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Keepalive not supported
Encapsulation(s): AAL5 AAL0
2047 maximum active VCs, 0 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
1 carrier transitions
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
 
Router# show interface ATM2/1/0
ATM2/1/0 is up, line protocol is up
Hardware is SPA-2CHT3-CE-ATM, address is 000c.862c.4d40 (bia 000c.862c.4d40)
MTU 4470 bytes, sub MTU 4470, BW 44209 Kbit/sec, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Keepalive not supported
Encapsulation(s): AAL5 AAL0
2047 maximum active VCs, 0 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
1 carrier transitions
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
 
Router# show atm int atm2/1/0
Interface ATM2/1/0:
AAL enabled: AAL5, AAL0, Maximum VCs: 2047, Current VCCs: 0
 
Max. Datagram Size: 4528
PLIM Type: DS3 - 45000Kbps, Framing is C-bit ADM,
DS3 lbo: short, TX clocking: LINE
Cell-payload scrambling: OFF
0 input, 0 output, 0 IN fast, 0 OUT fast
Avail bw = 44209
Config. is ACTIVE
 
Router# show atm pvc
VCD / Peak Av/Min Burst
Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells St
2/1/0 1 1 33 PVC SNAP UBR 44209 UP
 
Router# show interface atm2/1/ima0
ATM2/1/ima0 is up, line protocol is up
Hardware is ATM IMA, address is 000c.862c.4d40 (bia 000c.862c.4d40)
MTU 4470 bytes, sub MTU 4470, BW 1523 Kbit/sec, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Keepalive not supported
Encapsulation(s): AAL5 AAL0
2047 maximum active VCs, 0 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
7 carrier transitions
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
 
Router# show ima int atm2/1/ima0
ATM2/1/ima0 is up, ACTIVATION COMPLETE
Slot 2 Slot Unit 65 unit 256, CTRL VC 256, Vir -1, VC 4097
IMA Configured BW 1523, Active BW 1523
IMA version 1.1, Frame length 128
Link Test: Disabled
Auto-Restart: Disabled
ImaGroupState: NearEnd = operational, FarEnd = operational
ImaGroupFailureStatus = noFailure
IMA Group Current Configuration:
ImaGroupMinNumTxLinks = 1 ImaGroupMinNumRxLinks = 1
ImaGroupDiffDelayMax = 25 ImaGroupNeTxClkMode = common(ctc)
ImaGroupFrameLength = 128 ImaTestProcStatus = disabled
ImaGroupTestLink = None ImaGroupTestPattern = 0x0
ImaGroupConfLink = 1 ImaGroupActiveLink = 1
IMA Link Information:
ID Link Link State - Ctlr/Chan/Prot Test Status
---- -------------- ------------------------------ ---------------
0 T3 2/1/1 T1 2 Up Up Up Up disabled
 
Router# show cem cir 100
CEM2/2/0, ID: 100, Line: UP, Admin: UP, Ckt: ACTIVE
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8
Dejitter: 8 (In use: 4)
Payload Size: 32
Framing: Framed (DS0 channels: 5)
CEM Defects Set
None
 
Signalling: No CAS
RTP: No RTP
 
Ingress Pkts: 2500 Dropped: 0
Egress Pkts: 2500 Dropped: 0
 
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
 
Router# show cem cir detail | b 100
CEM2/2/0, ID: 100, Line: UP, Admin: UP, Ckt: ACTIVE
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8
Dejitter: 8 (In use: 4)
Payload Size: 32
Framing: Framed (DS0 channels: 5)
CEM Defects Set
None
 
Signalling: No CAS
RTP: No RTP
 
Ingress Pkts: 15000 Dropped: 0
Egress Pkts: 15000 Dropped: 0
 
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
 
Router# show cem circuit interface CEM2/2/0 100
CEM2/2/0, ID: 100, Line: UP, Admin: UP, Ckt: ACTIVE
Controller state: up, T1/E1 state: up
Idle Pattern: 0xFF, Idle CAS: 0x8
Dejitter: 8 (In use: 4)
Payload Size: 32
Framing: Framed (DS0 channels: 5)
CEM Defects Set
None
 
Signalling: No CAS
RTP: No RTP
 
Ingress Pkts: 27500 Dropped: 0
Egress Pkts: 27500 Dropped: 0
 
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 0 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 0
Error Sec: 0 Severly Errored Sec: 0
Unavailable Sec: 0 Failure Counts: 0
Pkts Malformed: 0 JitterBuf Overrun: 0
 
Router# show cem circuit summary
CEM Int. Total Active Inactive
--------------------------------------
CEM2/0/0 13 13 0
CEM2/1/0 7 7 0
CEM2/2/0 576 576 0
 
Router# show cem circuit
CEM Int. ID Ctrlr Admin Circuit AC
--------------------------------------------------------------
CEM2/0/0 0 UP UP Active UP
CEM2/0/0 1 UP UP Active UP
CEM2/0/0 2 UP UP Active UP
CEM2/0/0 3 UP UP Active UP
CEM2/0/0 4 UP UP Active UP
CEM2/0/0 5 UP UP Active UP
CEM2/0/0 6 UP UP Active UP
CEM2/0/0 7 UP UP Active UP
CEM2/0/0 8 UP UP Active UP
CEM2/0/0 9 UP UP Active UP
CEM2/0/0 21 UP UP Active UP
CEM2/0/0 22 UP UP Active UP
CEM2/0/0 23 UP UP Active UP
 
Router# show class cem TDM-class-B
Class: TDM-class-B
Dejitter: 320, Payload Size: 40
 
Router# show class cem all
Class: TDM-class-A
Dejitter: 10, Payload Size: 40
Class: TDM-class-B
Dejitter: 320, Payload Size: 40
 
Router# show class cem detail
*Oct 26 05:43:12.846 IST: %SYS-5-CONFIG_I: Configured from console by console
-Traceback= 4084BB0Cz 40856A84z 41CAF9ACz 41CAF990z
Class: TDM-class-A
Dejitter: 10, Payload Size: 40
Circuits inheriting this Class:
None
Interfaces inheriting this Class:
None
Class: TDM-class-B
Dejitter: 320, Payload Size: 40
Circuits inheriting this Class:
CEM2/2/0: Circuit 100
CEM2/2/0: Circuit 50
Interfaces inheriting this Class:

None


NoteSee the“Configuring T3” section for information about the features that are not supported on the SPA in Cisco IOS Release 12.2SRC.


Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT1.5

To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SONET VT 1.5, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 2

Router(config-controller)# framing sonet

Specifies SONET framing.

Step 3

Router(config-controller)# sts-1 2

Specifies the STS identifier.

Step 4

Router(config-ctrlr-sts1)# mode vt-15

Specifies VT-15 as the STS-1 mode of operation.

Step 5

Router(config-ctrlr-sts1)# vtg 3 t1 2 atm

Creates a T1 (VT1.5) ATM interface.

OR,

Router(config-ctrlr-sts1)# vtg 1 t1 1 ima-group group-number

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

OR,

Router(config-ctrlr-sts1)# vtg 2 t1 1 cem-group 1 unframed

Creates a single SAToP CEM group.

OR,

Router(config-ctrlr-sts1)# vtg 2 t1 4 cem-group 2 timeslots 1-5,14

Creates a CESoPSN CEM group.

Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12

To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-4 C-12, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 2

Router(config-controller)# framing sdh

Specifies SDH as the framing mode.

Step 3

Router(config-controller)# aug mapping au-4

Specifies AUG mapping.

Step 4

Router(config-controller)# au-4 1 tug-3 2

Selects the AU-4, TUG-3 to configure.

Step 5

Router(config-ctrlr-tug3)# mode c-12

Specifies the channelization mode for the TUG-3.

Step 6

Router(config-ctrlr-tug3)# tug-2 7 e1 3 atm

Creates an ATM interface.

Router(config-ctrlr-tug3)# tug-2 1 e1 1 ima-group group-number

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

Router(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 unframed

Creates a SAToP CEM group.

Router(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 timeslots 1-31

Creates a CESoPSN CEM group.

Configuring the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11

To configure the 1-Port Channelized OC-3 STM1 ATM CEoP SPA for SDH AU-3 C-11, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 2

Router(config-controller)# framing sdh

Specifies the framing mode.

Step 3

Router(config-controller)# aug mapping au-3

Specifies AUG mapping.

Step 4

Router(config-controller)# au-3 3

Selects the AU-3 to configure.

Step 5

Router(config-ctrlr-au3)# mode c-11

Specifies the channelization mode for the link.

Step 6

Router(config-ctrlr-au3)# tug-2 7 t1 4 atm

Creates an ATM interface.

Router(config-ctrlr-tug3)# tug-2 1 e1 1 ima-group group-number

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

Router(config-ctrlr-au3)# tug-2 1 t1 2 cem-group 1 unframed

Creates a SAToP CEM group.

Router(config-ctrlr-au3)# tug-2 1 t1 2 cem-group 2015 timeslots 1-12

Creates a CESoPSN CEM group.

Configuring Circuit Emulation

This section provides information about how to configure circuit emulation on a CEoP SPA. Circuit emulation provides a bridge between a time division multiplexed (TDM) network and a packet network (such as Multiprotocol Label Switching [MPLS]). The router encapsulates TDM data in MPLS packets and sends the data over a CEM pseudowire to the remote provider edge (PE) router. Thus, circuit emulation acts like a physical communication link across the packet network.

To configure circuit emulation on a CEoP SPA port, you must do the following:

1. Configure one or more CEM groups on the port. Each CEM group represents a set of time slots from the TDM circuit attached to the port. When you configure a CEM group on the port, the router creates an interface that has the same slot/subslot/port number as the port (for example, cem2/1/0).

2. Configure a pseudowire for each CEM group. The router maps the data from the time slots in each group onto its pseudowire and sends the data over the MPLS network to the remote PE router. Use the xconnect command with encap mpls to create a pseudowire for each CEM group.

Figure 11-1 shows the following sample configuration for a CEoP SPA:

  • A TDM circuit is connected to port 0 on a SPA installed in slot 1, subslot 0 (T1 controller 1/0/0).
  • Two pseudowires (PW10 and PW20) are configured to carry TDM data across the MPLS network.
  • Two CEM groups (2 and 3) are configured for the data in the TDM time slots:

Time slots 1 through 6 are sent over pseudowire 10 to the remote PE router at 10.0.0.0.

Time slots 8 through 13 are sent to PE router 11.0.0.0 over pseudowire 20.

Figure 11-1 TDM Time Slots to Pseudowire Mappings

 

Table 11-1 lists the number of CEM groups you can configure for each CEoP SPA on the SIP 400.

Table 11-1 Number of CEM Groups Supported for Each CEoP SPA

CEoP SPA
Number of Supported CEM Groups

24 T1/E1 Channelized ATM CEoP SPA

191

2-Port Channelized T3/E3 ATM CEoP SPA

576

1-Port Channelized OC-3 STM1 ATM CEoP SPA

576

 

Configuration Guidelines and Restrictions

Not all combinations of payload-size and dejitter-buffer size are supported. Payload size, or dejitter configurations are rejected at the CLI level in CEM circuit mode on the SPA if they are not compatible. Any incompatible parameter modifications will be rejected and the configuration will fall back to the old dejitter and payload parameters if the parameters are being applied through the cem class template.

For relation between the payload size and the dejitter buffer size on CeoPSN and SaToP T1/E1 frames see Table 10-1 , CESoPSN DS0 Lines: Payload and Jitter Limits , Table 10-3 , SAToP T1 Frame: Payload and Jitter Limits and Table 10-4 , SAToP E1 Frame: Payload and Jitter Limits .

Configuring a CEM Group

To configure a CEM group to represent a CEM circuit on a SPA port, use the following procedure.


Note • The first cem-group command under the controller creates a CEM interface that has the same slot/subslot/port information as the controller. The CEM interface is removed when all of the CEM groups under the interface have been deleted.

  • The CEM interface is always up, even if the controller state is down. This allows the CEM pseudowire to carry alarm information to the remote end.


 

 

Command or Action
Purpose

Step 1

Router(config)# controller type slot / subslot / port

Examples

Router(config)# controller t1 3/1/
Router(config)# controller sonet 2/0/1

Selects the controller for the port being configured:

  • type identifies the port type. Depending on the card type, valid values are t1 , e1 , t3 , e3 , or sonet . For additional information, see the sections for configuring those port types.
  • slot / subslot / port identifies the SPA slot, subslot, and port.

Step 2

Router(config-controller)# [ no ] cem-group group-number { unframed | timeslots timeslot }

Examples


Router(config)# controller t1 3/2/0
Router(config-controller)# cem-group 1 unframed
Router(config)# controller t1 3/2/1
Router(config-controller)# cem-group 1 timeslots 1,3,5-11
Router(config-controller)# cem-group 2 timeslots 12-24
Router(config)# controller t3 3/2/0

Router(config-controller)# t1 1 cem-group 1 timeslots 1

Router(config)# controller t3 3/2/1

Router(config-controller)# e1 1 cem-group 1 unframed

Creates a CEM circuit (group) from one or more time slots of the line connected to this port. To delete the CEM circuit and release the time slots, use the no cem-group group-number command.

  • group-number assigns a CEM circuit number:

For 24 T1/E1 Channelized ATM CEoP SPA, you can configure up to 191 CEM groups.

For 2-Port Channelized T3/E3 ATM CEoP SPA, you can configure up to 576 CEM groups.

For 1-Port Channelized OC-3 STM1 ATM CEoP SPA, you can configure up to 576 CEM groups.

  • unframed creates a single CEM circuit from all of the time slots, and uses the framing on the line. Use this keyword for SAToP mode.
  • timeslots timeslot specifies the time slots to include in the CEM circuit. Use this keyword for CESoPSN mode. The list of time slots can include commas and hyphens with no spaces between the numbers, commas, and hyphens.

Note Each time slot operates at 64 kilobits per second (kbps).

Step 3

Router(config-controller)# exit

Exits interface configuration mode.

Configuring a CEM Class (Optional)

To assign CEM parameters to one or more CEM interfaces, you can create a CEM class (template) that defines the parameters and then apply the class to the interfaces.

CEM class parameters can be configured directly on the CEM circuit. The inheritance is as follows:

  • CEM circuit (highest level)
  • Class attached to CEM circuit
  • Class attached to the CEM interface

If the same parameter is configured on the CEM interface and CEM circuit, the value on the CEM circuit takes precedence.

To configure a CEM class, use the following procedure:

 

Command or Action
Purpose

Step 1

Router(config)# class cem name

Creates a CEM class to help in configuring parameters in a template and applying parameters at the CEM interface level.

  • name argument is a string of up to 80 characters that identifies the CEM class. Note that the name is truncated to the first 15 characters.

Step 2

Router(config-cem-class)# command

Configure CEM parameters by issuing the appropriate commands. See the “Configuring CEM Parameters” section for commands.

In the following example, a CEM class (TDM-Class-A) is configured to set the payload-size and dejitter-buffer parameters:

class cem TDM-Class-A
payload-size 512
dejitter-buffer 80
exit
 

In the next example, the CEM parameter settings from TDM-Class-A are applied to CEM interface 2/1/0. Any CEM circuits created under this interface inherit these parameter settings.

int cem 2/1/0
class int TDM-Class-A
cem 6
xconnect 10.10.10.10 2 encap mpls
exit

Configuring a CEM Pseudowire

To configure a pseudowire to transport a CEM circuit across the MPLS network, follow this procedure.

 

Command or Action
Purpose

Step 1

Router(config)# interface cem slot / subslot / port

or

Router(config)# interface cem-acr acr group number

  • Selects the CEM interface where the CEM circuit (group) is located (where slot / subslot is the SPA slot and subslot and port is the SPA port where the interface exists).
  • Selects the ACR CEM interface associated with the ACR group.

Step 2

Router(config-if)# cem group number

Selects the CEM circuit (group) to configure a pseudowire for.

Step 3

Router(config-if-cem)# command

(Optional) Defines the operating characteristics for the CEM circuit. For command details, see the “Configuring CEM Parameters” section.

Step 4

Router(config-if)# xconnect peer-router-id vcid { encapsulation mpls | pseudowire-class name }

Configures a pseudowire to transport TDM data from the CEM circuit across the MPLS network.

  • peer-router-id is the IP address of the remote PE peer router.
  • vcid is a 32-bit identifier to assign to the pseudowire. The same vcid must be used for both ends of the pseudowire.
  • encapsulation mpls sets MPLS for tunneling mode.
  • pseudowire-class name specifies a pseudowire class that includes the encapsulation mpls command.

Note The peer-router-id and vcid combination must be unique on the router.

Step 5

Router(config-if)# exit

Exits interface configuration mode.

To configure a pseudowire to transport a CEM circuit across the UDP/IP network, follow this procedure.

 

Command or Action
Purpose

Step 1

Router(config)# interface loopback interface number

Selects loopback interface.

Step 2

Router(config-if)# ip address ip-address mask [secondary]

Configures loopback IP address.

Step 3

Router(config-if)# mls cemoudp reserve slot slot number

or

Router(config-if)# mls cemoudp reserve acr group number

  • Redirects traffic with destination IP of loopback interface, to a line card in the specified slot number.
  • Redirects traffic with destination IP as loopback interface, to an ACR interface associated with a specific ACR group.

Step 4

Router(config-if)# exit

Returns to global configuration mode.

Step 5

Router(config)# pseudowire-class pseudowire-class-name

Configures a pesudowire class.

Step 6

Router(config-pw-class)# encapsulation udp

Selects UDP/IP as the pseudowire transport mechanism.

Step 7

Router(config-pw-class)# exit

Returns to global configuration mode.

Step 8

Router(config)# interface cem slot/subslot/port

or

Router(config)# interface cem-acr acr group number

  • Selects the CEM interface, if specific CEM interface traffic is to be transported over PSN.
  • Selects the ACR interface, if any one of the CEM interfaces (working or protect) traffic is to be transported over PSN. Only traffic corresponding to active CEM interface is transported over the pseudowire.

Step 9

Router(config-if)# cem group number

Selects the CEM circuit (group) for which to select a pseudowire.

Step 10

Router(config-if-cem)# xconnect peer-router-id vcid {pseudowire-class name}

Configures a pseudowire to transport TDM data from the CEM circuit across the UDP/IP network.

  • peer-router-id is the IP address of the remote PE peer router.
  • vcid is a 32-bit identifier to assign to the pseudowire. The same vcid must be used for both ends of the pseudowire.
  • pseudowire-class name is a pseudowire class that includes the encapsulation udp command.

Note The peer-router-id and vcid combination must be unique on the router.

For more information on CEMoUDP feature, see the Overview of the CEoP and Channelized ATM SPAs section.

Step 11

Router(config-if-cem)# udp port local local_udp_port remote remote_udp_port

Specifies a local and remote UDP port for the connection. Valid port values for CESoPSN pseudowires using UDP are from 49152-57343.

For more information on CEMoUDP feature, see the Overview of the CEoP and Channelized ATM SPAs section.

Step 12

Router(config-if-cem)# exit

Exits the CEM interface.

For troubleshooting CEMoUDP issues, see the Overview of the CEoP and Channelized ATM SPAs section.

For troubleshooting ACR issues, see the Configuring Access Circuit Redundancy on CEoP and ATM SPAs section under Configuring the CEoP and Channelized ATM SPAs.


NoteWhen the T1 controller that carries a particular CEM circuit traffic goes down, a message is sent about a failure between PE and CE routers. This results in pseudowire status as down, but the data plane is kept up for the alarms to be carried over.


The following sample configuration shows a T1 port on which two CEM circuits (groups) are configured. Each CEM circuit carries data from time slots of the TDM circuit attached to the port.

The two xconnect commands create pseudowires to carry the TDM data across the MPLS network. Pseudowire 2 carries the data from time slots 1, 2, 3, 4, 9, and 10 to the remote PE router at 10.10.10.10. Pseudowire 5 carries the data in time slots 5, 6, 7, 8, and 11 to the remote PE router at 10.10.10.11.

 
controller t1 2/1/0
cem-group 6 timeslots 1-4,9,10
cem-group 7 timeslots 5-8,11
framing esf
linecode b8zs
clock source adaptive 6
cablelength long -15db
crc-threshold 512
description T1 line to 3rd floor PBX
loopback network
no shutdown
 
int cem2/1/0
cem 6
xconnect 10.10.10.10 2 encap mpls
cem 7
xconnect 10.10.10.11 5 encap mpls
 
 

The following sample configuration for CEM over UDP, shows one E1 port on which two CEM circuits (groups) are configured. Each CEM circuit carries data from time slots of the TDM circuit attached to the port. Loopback 22 is mapped to the ACR group 1.

The two xconnect commands create pseudowires to carry the TDM data across the IP network. Pseudowire 1 carries data from time slots 1, 2, 3, 4, 5 and 6 to the remote PE router at 12.12.12.12. Pseudowire 2 carries data in time slots 1-31 to the remote PE router at 12.12.12.12.

 
interface Loopback22
description loopback for CEMoUDP
ip address 11.11.11.11 255.255.255.255
mls cemoudp reserve acr 1
end
 
controller SONET 3/0/0
framing sdh
clock source line
aug mapping au-4
!
au-4 1 tug-3 1
mode c-12
!
au-4 1 tug-3 2
mode c-12
!
au-4 1 tug-3 3
mode c-12
aps group acr 1
aps working 1
controller SONET 7/0/0
framing sdh
clock source line
aug mapping au-4
!
au-4 1 tug-3 1
mode c-12
!
au-4 1 tug-3 2
mode c-12
!
au-4 1 tug-3 3
mode c-12
aps group acr 1
aps protect 1 11.11.11.11
!
 
controller SONET-ACR 1
framing sdh
aug mapping au-4
!
au-4 1 tug-3 1
mode c-12
tug-2 1 e1 1 cem-group 1 timeslots 1-6
tug-2 1 e1 2 cem-group 2 timeslots 1-31
 
 
 
interface CEM-ACR1
no ip address
cem 1
xconnect 12.12.12.12 1 pw-class UDP_E1
udp port local 55003 remote 56003
!
cem 2
xconnect 12.12.12.12 2 pw-class UDP_E1
udp port local 55004 remote 56004
end
 
pseudowire-class UDP_E1
encapsulation udp
ip local interface Loopback22
ip tos value 160
ip ttl 100
!

Configuring TDM Local Switching

TDM Local Switching allows switching of Layer 2 data between two CEM interfaces on the same router. The two CEM groups can be on the same physical interface or different physical interfaces; they can be on the same SPA, the same line card, or different line cards.


NoteFor Cisco IOS Release 12.2(33)SRC, this feature is supported on the 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA.


Use the following guidelines for CEoP Phase 2 TDM Local Switching:

  • Autoprovisioning is not supported.
  • Out-of-band signaling is not supported.
  • Port mode local switching is not supported on the CEM interface.
  • Interworking with other interface types is not supported.
  • The same CEM circuit cannot be used for both local switching and xconnect.
  • You can use CEM local switching between two CEM circuits on the same CEM interface.
  • CEM local switching can be across a 24-Port Channelized T1/E1 ATM CEoP SPA and a 1-Port Channelized OC-3 STM1 ATM CEoP SPA.

Use the following procedure to configure CEoPS Phase 2 TDM Local Switching:

 

Command or Action
Purpose

Step 1

Router(config)# interface cem slot / subslot/port

Selects the CEM interface to configure the pseudowire for. This is the interface that the TDM circuit is attached to.

Step 2

Router(config)# [no] connect name cemx/y/z cemckt1 cema/b/c cemckt2

Configures a local switching connection between cemckt1 of the CEM interface x/y/z and cemckt2 of the CEM interface a/b/c.

The no form of this command unconfigures a local switching connection between cemckt1 of the CEM interface x/y/z and cemckt2 of the CEM interface a/b/c.

Configuration Example

The following is an example:

Router(config)# interface CEM4/3/0
Router(config)# connect cem cem2/1/0 1 cem4/2/0 2

Verifying

Use the show connection, show connection all, show connection id conn id, and show connection conn name commands to verify.

Local Switching Redundancy

Local Switching Redundancy provides a backup attachment circuit (AC) when the primary attachment circuit fails. All the ACs must be on same Cisco 7600 series router.


NoteFor Cisco IOS Release 12.2(33)SRC, this feature is supported on the 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA, as well as the 2-Port and 4-Port OC-3c/STM-1 ATM SPA, the 1-Port OC-12c/STM-4 ATM SPA, and the 1-Port OC-48c/STM-16 ATM SPA.


The following combinations of CEM ACs are supported:

  • CEM ACs on the same SPA
  • CEM ACs on different SPAs on the same SIP
  • CEM ACs on different SIPs on the same Cisco 7600 series router

Guidelines

Local Switching Redundancy guidelines are as follows:

  • Autoconfiguration of CEM interfaces is not supported.
  • Only the tail end AC can be backed up, if head end fails, there is no protection.
  • The circuit type of the primary and backup AC must be identical (failover operation will not switch between different types of interfaces or different CEM circuit types).
  • Backs up a local switching connection to cem-ckt3 of CEM interface cem3.Only one backup AC is allowed for each connection.
  • Autoconfiguration of backup CEM circuits is not allowed. Autoconfiguration is allowed for backup ATM Permanent Virtual Circuits (PVCs) or ATM Permanent Virtual Paths (PVPs) .
  • The CEM circuit used as a backup in a local switching connection cannot be used for xconnect configurations.
  • Dynamic modification of parameters in a local switching connection is not supported in the case where the tail-end segment is backed up to a segment using the backup command. If you want to modify the parameters in any of the three segments (head-end, tail-end, or backup segment), you must first unconfigure with the backup command, make the changes in the individual segments, and then reconfigure the backup with the backup command.

Configuration

 

Command or Action
Purpose

Step 1

Router(config)# [no] connect name cema/b/c cemckt1 cemx/y/z cemckt2

Configures a local switching connection between cemckt1 of the CEM interface x/y/z and cemckt2 of the CEM interface a/b/c.

The no form of this command unconfigures a local switching connection between cemckt1 of the CEM interface x/y/z and cemckt2 of the CEM interface a/b/c.

Step 2

Router(config-connection)# backup interface cemx/y/z cemckt

Backs up a locally switched CEM connection.

Configuration Example

The following is a configuration example for Local Switching Redundancy:

Router(config)# connect cem cem2/1/0 1 cem4/2/0 2
Router(config)# backup interface cem 3/0/0 3
 

Verifying

Use the show xconnect all command to check the status of the backup and primary circuits.

Configuring ATM

In addition to CEM mode, CEoP SPAs support ATM. When configured to operate in ATM mode, CEoP SPAs support the ATM features listed in Chapter10, “Overview of the CEoP and Channelized ATM SPAs”

CEoP SPAs also support inverse multiplexing over ATM (IMA), which allows you to combine multiple ATM links into a single high-bandwidth logical link. For more information on IMA, see the “Configuring Inverse Multiplexing over ATM” section.

CEoP SPAs support ATM operation in clear-channel or channelized mode:

  • In clear-channel mode, each SPA port provides a single high-speed ATM connection operating at the line rate of the port.
  • In channelized mode, each port can be divided into multiple logical channels, each providing a separate ATM connection operating at the channelized line rate (for example, T3 channelized to T1).

Note ATM does not support DS0s. ATM can only be channelized down to T1s.


ATM Connections Per SPA

Use the following guidelines:

  • The 24-Port Channelized T1/E1 ATM CEoP SPA provides 24 ATM connections (one for each port) operating at T1 or E1 line rates.
  • The 1-Port Channelized OC-3/STM-1 ATM CEoP SPA cannot be configured for clear-channel (OC-3) ATM. Instead, you must channelize the port to T1s or E1s. The number of ATM connections available depends on the configuration mode:

Channelized T1 mode provides 84 ATM connections (3 T3 x 28 T1 = 84).

Channelized E1 mode provides 63 ATM connections (3 TUG-3/AU-3 x 7 TUG-2 x 3 E1 = 63).

  • In clear-channel mode, each port in the 2-Port Channelized T3/E3 ATM CEoP SPA provides a single ATM connection operating at T3 line rate.

ATM Configuration Overview

To configure a port on a CEoP SPA for ATM operation, you must:

1. Set the port to ATM mode. You can also configure IMA (optional).

2. Configure an ATM permanent virtual circuit (PVC) for the port.

3. Configure a pseudowire for the ATM or IMA interface.

ATM and IMA Interfaces

IMA interfaces may consist of groups of T1s or E1s. IMA is not supported on the 2-Port Channelized T3/E3 ATM CEoP SPA.

The router creates an ATM interface for each T3 or E3 port (or channelized T1 or E1) that is configured for ATM mode. The interface has the format atm slot / subslot / port (where slot / subslot identifies the SPA slot and subslot and / port identifies the port [for example, atm2/1/0]).

If you configure IMA, the router creates an interface to represent each IMA group (link bundle). The interface has the format atm slot / subslot / ima group-id (where slot / subslot identifies the SPA slot and subslot and group-id identifies the IMA group number [for example, atm2/1/ima0]).

Configuring VC QoS on VP-PW CEoP SPAs

The SIPs and SPAs support many QoS features using modular QoS CLI (MQC) configuration. For configuration information on Modular QoS CLI (MQC) policy support and ATM VCI (match atm-vci command), see the “Configuring QoS Features on a SIP” section of Chapter5, “Configuring the SIPs and SSC”

Restriction

VC QoS on VP-PW feature works only with Single Cell Relay and does not work with Packed Cell Relay.

Configuring an ATM Pseudowire

To configure a pseudowire for an ATM connection or an IMA link bundle, perform these steps. The pseudowire is used to carry the ATM data across the MPLS network.

 

Command or Action
Purpose

Step 1

Router(config)# interface atm slot / subslot / port

or

Router(config)# interface atm slot / subslot / ima group-id

Selects the ATM interface to configure the pseudowire for (where slot / subslot is the SPA slot and subslot, and / port is the SPA port where the interface exists).

For IMA, the format is atm slot / subslot / ima group-id (where slot / subslot / identifies the SPA slot and subslot and group-id is the IMA group number).

Step 2

Router(config-if)# pvc vpi / vci

Creates a permanent virtual circuit for the ATM or IMA interface and assigns the PVC a VPI and VCI:

  • vpi specifies the virtual path identifier (0 to 255).
  • vci specifies the virtual channel identifier. Valid values are 32 to 1 less than the value specified by the atm vc-per-vp command.

Note Do not specify 0 for both the VPI and VCI.

Step 3

Router(config-if-atm-vc)# encapsulation { aal0 | aal5 | aal5snap }

Specifies the ATM adaptation layer (AAL) for the PVC:

  • aal0 —Selects ATM adaptation layer 0 (cell mode).
  • aal5 —Selects ATM adaptation layer 5 (packet mode).
  • aal5snap —Supports Inverse Address Resolution Protocol (ARP). Logical link control/Subnetwork Access Protocol (LLC/SNAP) precedes protocol datagram.

Step 4

Router(config-if-atm-vc)# command

Configures the ATM operating characteristics of the PVC. CEoP SPAs support the ATM features in Chapter 10 .

Step 5

Router(config-if-atm-vc)# exit

Returns you to interface configuration mode.

Step 6

Router(config-if)# xconnect peer-router-id vcid { encapsulation mpls | pseudowire-class name }

Configures a pseudowire to transport data from the ATM or IMA interface across the MPLS network.

  • peer-router-id is the IP address of the remote PE peer router.
  • vcid is a 32-bit identifier to assign to the pseudowire. The same vcid must be used for both ends of the pseudowire.
  • encapsulation mpls sets MPLS for tunneling mode.
  • pseudowire-class name specifies a pseudowire class that includes the encapsulation mpls command.

Note The peer-router-id and vcid combination must be unique on the router.

Step 7

Router(config-if)# exit

Exits interface configuration mode.

Configuring Pseudowire Redundancy (Optional)

CEoP SPAs support the L2VPN Pseudowire Redundancy feature, which provides backup service for ATM and circuit emulation (CEM) pseudowires. The L2VPN Pseudowire Redundancy feature enables the network to detect a failure and reroute the Layer 2 (L2) service to another endpoint that can continue to provide service. This feature provides the ability to recover from a failure either of the remote PE router or of the link between the PE and CE routers.

You configure pseudowire redundancy by configuring two pseudowires for an ATM or CEM interface: a primary pseudowire and a backup (standby) pseudowire. If the primary pseudowire goes down, the router uses the backup pseudowire in its place. When the primary pseudowire comes back up, the backup pseudowire is brought down and the router resumes using the primary.

Figure 11-2 shows an example of pseudowire redundancy.

Figure 11-2 Pseudowire Redundancy

 

Following is a summary of the steps to perform to configure pseudowire redundancy on a CEoP SPA. Although an ATM interface is shown, the configuration is the same for CEM.


NoteYou must configure the backup pseudowire to connect to a different router than the primary pseudowire.


1. enable

2. configure terminal

3. interface atm slot / subslot / port

4. xconnect peer-router-id vcid { encapsulation mpls | pw-class pw-class-name }

5. backup peer peer-router-ip-addr vcid [ pw-class pw-class-name ]

6. backup delay enable-delay { disable-delay | never }

The following example shows pseudowire redundancy configured for a CEM circuit (group). In the example, the xconnect command configures a primary pseudowire for CEM group 0. The backup peer command creates a redundant pseudowire for the group.

int cem8/1/1
no ip address
cem 0
xconnect 10.10.10.1 1 encap mpls
backup peer 10.10.10.2 200
exit

Configuring T1

To configure T1 on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure and observe these guidelines:

  • There can be 0 to 23 channels under a T1 controller, one for each T1 time slot.
  • Each channel can be configured as a CEM group.
  • Maximum channels under a CEM group is 24.
  • Each CEM group number under a controller must be unique.
  • A maximum of 191 CEM circuits can be configured.

 

Command or Action
Purpose

Step 1

Router(config)# controller t1 slot / subslot / port

Selects the T1 controller.

Step 2

Router(config-controller)# [ no ] cem-group group-number { unframed | timeslots timeslot }

Creates a CEM interface and assigns it a CEM group number.

Step 3

Router(config-controller)# framing { sf | esf }

Selects the T1 framing type.

Step 4

Router(config-controller)# exit

Exits controller configuration mode and returns you to global configuration mode.

Step 5

Router(config)# interface cem slot / subslot / port

Selects the CEM interface.

Step 6

Router(config-controller)# cem group-number

Selects the specified CEM group.

Step 7

Router(config-controller)# xconnect peer-ip-address encap mpls

Configures a pseudowire for the T1 time slots identified by the CEM group.

Step 8

Router(config-controller)# exit

Exits controller configuration mode.

Configuring E1

To configure E1 on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure:

 

Command or Action
Purpose

Step 1

Router(config)# controller e1 slot / subslot / port

Selects the controller for the E1 port being configured.

Step 2

Router(config-controller)# [ no ] cem-group group-number { unframed | timeslots timeslot }

Creates a CEM interface and assigns a CEM group number.

Step 3

Router(config-controller)# framing { crc4 | no-crc4 }

Selects the framing type.

Step 4

Router(config-controller)# exit

Exits controller configuration mode and returns you to global configuration mode.

Step 5

Router(config)# interface cem slot / subslot / port

Selects the CEM interface.

Step 6

Router(config-controller)# cem group-number

Selects the specified CEM group.

Step 7

Router(config-controller)# xconnect peer-ip-address encap mpls

Configures a pseudowire for the E1 time slots identified by the CEM group.

Step 8

Router(config-controller)# exit

Exits controller configuration mode.

Configuring T3

This section describes how to configure the 2-Port Channelized T3/E3 ATM CEoP SPA. The SPA can be configured to operate in the following modes:

  • T3 (clear-channel)
  • ATM

The router creates a logical interface to represent the mode that the SPA port is configured to run in. An ATM interface is created for each T3 port that is configured for ATM mode. The interface has the format atm slot / subslot / port (where slot / subslot identifies the SPA slot and subslot and / port identifies the port). An example is atm2/1/0.

The following sections provide instructions for configuring the SPA:

T3 Configuration Guidelines

This section lists the guidelines for configuring the 2-Port Channelized T3/E3 ATM CEoP SPA. For information about supported features, see Chapter10, “Overview of the CEoP and Channelized ATM SPAs”


NoteFor a list of features that are not supported in Cisco IOS Release 12.2SRC, see the“Unsupported Features” section.


T3 Mode

In clear-channel T3 mode, each SPA port provides a single high-speed data channel operating at 44210 kilobits per second (kbps).

ATM Mode

For ATM mode up to 4000 point-to-point ATM VCs (per SIP) are supported.

Configuring Port Usage

Perform the following steps to configure a SPA port for T3:


NoteE3 is not supported with Cisco IOS Release 12.2(33)SRC.


 

Command or Action
Purpose

Step 1

Router(config)# controller {t3 } slot / subslot / port

Selects the T3 controller for the port you are configuring (where slot / subslot identifies the SPA slot and subslot and / port identifies the port).

Step 2

Router(config-controller)# [ no ] framing {auto-detect | c-bit | m23}

For the clear-channel ATM mode, configure framing as:

  • auto-detect—Detects the framing type at the device at the end of the line and switches to that framing type. If both devices are set to auto-detect, c-bit framing is used.
  • c-bit—Specifies C-bit parity framing.
  • m23—Specifies M23 framing.

Step 3

Router(config-controller)# clock source {internal | line}

(Optional) Specifies the clock source.

  • internal—Selects the internal clock.
  • line—Selects the network clock.

Step 4

Router(config-controller)# cablelength feet

(Optional) Specifies the length of the cable attached to the port (in feet). Valid values are 0 to 450 ft. The default is 224 ft.

Step 5

Router(config-controller)# [ no ] loopback { local | network | remote { line | payload }}

(Optional) Runs a loopback test, which is useful for troubleshooting problems. The no form of the command stops the test. The default is no loopback.

  • local —Loops the signal from Tx to Rx path. Sends alarm indication signal (AIS) to network.
  • network —Loops the signal from Rx to Tx path.
  • remote { line | payload }—(C-bit framing only) Sends a loopback request to the remote end: line loops back the unframed signal and payload loops back the framed signal.

Step 6

Router(config-controller)# [ no ] bert pattern
[ 2^11 | 2^15 | 2^20 O.153 | 2^20 QRSS | 2^23 | 0s | 1s | alt-0-1 ] interval [ 1 - 1440 ]

(Optional) Configures bit-error-rate (BER) testing.

Step 7

Router(config-controller)# mdl {string {eic | fic | generator | lic | pfi | port | unit } string} | { transmit {idle-signal | path | test-signal}}

Example

Router(config-controller)# mdl string eic ID
Router(config-controller)# mdl string fic Building B
Router(config-controller)# mdl string unit ABC
Router(config-controller)# mdl string pfi Facility Z
Router(config-controller)# mdl string port Port 7

Router(config-controller)# mdl transmit path
Router(config-controller)# mdl transmit idle-signal

(Optional) Configures maintenance data link (MDL) messages, which communicate information between local and remote ports. Valid only with C-bit framing.

  • mdl string specifies the type of identification information to include in MDL messages:

eic string specifies the Equipment Identification Code, up to 10 characters.

fic string specifies the Frame Identification Code, up to 10 characters.

generator string specifies the Generator Number for test-signal messages, up to 38 characters.

lic string is the Location Identification Code, up to 11 characters.

pfi string specifies the Path Facility Identification Code for path messages, up to 38 characters.

port string is the port number for idle-signal messages, up to 38 characters.

unit string —Specifies the Unit Identification Code, up to 6 characters.

  • mdl transmit specifies the type of MDL messages to transmit:

idle-signal—Enables idle-signal messages.

path—Enables path messages.

test-signal—Enables test-signal messages.

Step 8

Router(config-controller)# exit

Returns you to global configuration mode.

Configuring the SPA for Clear-Channel ATM

To configure a T3/E3 SPA port for clear-channel ATM, follow these steps:

Command or Action
Purpose

Step 1

Router(config)# controller {t3 } slot / subslot / port

Selects the T3 controller for the port you are configuring (where slot / subslot identifies the SPA location and / port identifies the port).

Step 2

Router(config-controller)# atm

Configures the port (interface) for clear-channel ATM. The router creates an ATM interface whose format is atm/ slot / subslot / port (where slot / subslot identifies the SPA slot and subslot and / port is the SPA port).

Step 3

Router(config-controller)# exit

Returns you to global configuration mode.

Step 4

Router(config)# interface atm slot / subslot / port

Selects the ATM interface for the SPA port in Step 1 .

Step 5

Router(config-if)# pvc vpi / vci

Configures a PVC for the interface and assigns the PVC a VPI and VCI. Do not specify 0 for both the VPI and VCI. See the “Configuring an ATM Pseudowire” section for details on this command and the next.

Step 6

Router(config-if)# xconnect peer-router-id vcid { encapsulation mpls | pseudowire-class name }

Configures a pseudowire to carry data from the clear-channel ATM interface over the MPLS network.

Step 7

Router(config-if)# end

Exits configuration mode.

Configuring SONET (OC-3)

To configure SONET (OC-3) on the1-Port Channelized OC-3 STM1 ATM CEoP SPA, use the following procedure and observe these guidelines:

  • One OC-3 has three SONET paths, each of which can have a T3. Each T3 has 28 T1s.
  • Each T3 has a submode for T1 configuration.
  • Each T1 can be configured to operate in CEM, ATM, or IMA mode.
  • ATM can be configured on T1s only. These modes cannot be configured on T1s that are channelized to DS0s.
  • CEM groups can be configured on a T1 directly.
  • CEM groups can be channelized to DS0s.
  • A maximum of 2016 DS0s can be configured.
  • A maximum of 576 CEM circuits can be configured.

SONET Controller Configuration

To configure the SONET controller, perform this task:

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet slot / subslot / port

Example

Router(config)# controller sonet 5/1/0

Enters the SONET controller configuration submode.

Step 2

Router(config-controller)# framing sonet

Configures the controller framing for SONET framing (default).

Step 3

Router(config-controller)# sts-1 number

Specifies the STS identifier.

Step 4

Router(config-ctrlr-sts1)# mode vt-15

Specifies VT-15 as the STS-1 mode of operation.

Step 5

Router(config-controller-stsl)# vtg 5 t1 1 cem-group 15 timeslots 1-5 , 20-23

Creates a virtual tributary group carrying a T1.

Step 6

Router(config-controller-stsl)# exit

Exits controller configuration mode.

SDH Configuration for AU-4 C-12

This section describes how to enable an interface under SDH framing with AU-4 mapping after configuring the SONET controller.

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 1

Router(config-controller)# framing sdh

Specifies SDH as the framing mode.

Step 2

Router(config-controller)# aug mapping au-4

Specifies AUG mapping.

Step 3

Router(config-controller)# au-4 1 tug-3 2

Selects the AU-4, TUG-3 to configure.

Step 4

Router(config-ctrlr-tug3)# mode c-12

Specifies the channelization mode for the TUG-3.

Step 5

Router(config-ctrlr-tug3)# tug-2 7 e1 3 atm

Creates an ATM interface.

Step 6

Router(config-ctrlr-tug3)# tug-2 1 e1 1 ima-group group-number

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

Step 7

Router(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 unframed

Creates a SAToP CEM group.

Router(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 timeslots 1-31

Creates a CESoPSN CEM group.

SDH Configuration for AU-3 C-11

This section describes how to enable an interface under SDH framing with AU-3 mapping after configuring the SONET controller.

 

Command or Action
Purpose

Step 1

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 2

Router(config-controller)# framing sdh

Specifies the framing mode.

Step 3

Router(config-controller)# aug mapping au-3

Specifies AUG mapping.

Step 4

Router(config-controller)# au-3 3

Selects the AU-3 to configure.

Step 5

Router(config-ctrlr-au3)# mode c-11

Specifies the channelization mode for the link.

Step 6

Router(config-ctrlr-au3)# tug-2 7 t1 4 atm

Creates an ATM interface.

Step 7

Router(config-ctrlr-au3)# tug-2 1 t1 2 cem-group 1 unframed

Creates a SAToP CEM group.

Router(config-ctrlr-au3)# tug-2 1 t1 2 cem-group 2015 timeslots 1-12

Creates a CESoPSN CEM group.

Configuring Inverse Multiplexing over ATM

Inverse multiplexing over ATM (IMA) allows multiple T1 or E1 links to be bundled together into a high-bandwidth logical link. The rate of the logical IMA link is approximately the sum of the rate of the physical links in the IMA group, although some overhead is required for ATM header and control cells.


NoteIMA is available in Cisco IOS Release 12.2SRC and later releases and is supported on the 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA.


The inverse multiplexing operation is transparent to the ATM layer protocols, and therefore the ATM layer can operate normally, as if only a single physical interface is being used. In the transmit direction, IMA takes cells from the ATM layer and sends them in round-robin manner over the individual T1 or E1 links in the IMA group. At the receiving end, the cells are recombined to form the original cell stream and are passed up the ATM layer. An IMA device always sends a continuous stream. If no ATM layer cells are being sent, an IMA filler cell is transmitted to provide a constant stream at the physical layer.

IMA Control Protocol (ICP) cells are periodically transmitted between IMA interfaces. ICP cells control the inverse multiplexing function, provide sequencing for the ATM cell stream, and define the IMA frame. Using an IMA frame length of 128 cells, one out of every 128 cells on each link is an ICP cell.

Figure 11-3 shows how IMA works. In the figure, IMA performs inverse multiplexing and demultiplexing with four bundled links, providing 5.52 Mbps of bandwidth for T1s for packet traffic, after subtracting the overhead of ATM cell headers and ICP cells. The transmitting side, from which cells are distributed across the links, is referred to as Tx, and the receiving side, where cells are recombined, is called Rx.

Figure 11-3 IMA Operation

 

IMA Configuration Guidelines

Follow these guidelines as you configure the CEoP SPA for inverse multiplexing ATM:

  • IMA is supported on the Cisco 7600 SIP-400 with the following CEoP SPAs:

24-Port Channelized T1/E1 ATM CEoP SPA (24 IMA groups per SPA)

1-Port Channelized OC-3 STM1 ATM CEoP SPA (42 IMA groups per SPA)

2-Port T3/E3 ATM CEoP SPA (42 IMA groups per SPA)

  • When a T1 or E1 interface is configured for IMA mode, the interface no longer operates as an individual ATM link.
  • IMA group numbers (IDs) must be unique on the SPA.
  • You cannot mix T1 and E1 lines in the same IMA group.
  • The T1 or E1 lines in an IMA group must be on the same CEoP SPA. An IMA group cannot contain T1 or E1 lines from different SPAs.
  • Both ends of the T1 or E1 link must be in IMA mode.
  • IMA is compliant with nonstop forwarding with stateful switchover (NSF/SSO). This means that when a switchover occurs, IMA connections remain up and continue to pass traffic, with no interruption in service.
  • IMA Control Protocol (ICP) cells and filler cells are discarded by the receiving end; therefore, any counters displayed in show command output do not include these cells.
  • The Cisco 7600 SIP-400 supports a maximum transmission unit (MTU) size of 4470 bytes.

To ensure that IMA groups synchronize correctly after a restart, observe the following guidelines as you configure IMA links. For information about restarts, see the description of ima autorestart in the “Configuring IMA Group Parameters” section.

  • Each end of an IMA link should have a different IMA group ID. This way, after a restart the router can detect links in loopback mode, which means that a link is communicating with itself instead of the remote end. When both ends of a link have the same group ID, the link is in loopback mode.
  • If both ends of an IMA link have the same group ID, loopbacked links might be the first to respond after a restart, in which case the IMA group could be communicating with itself instead of the far end.
  • Effective from Cisco IOS release 15.1(01)S, the number of IMA groups supported on the different flavours of the CEoP SPA are:

24 T1/E1/J1 port SPA (12 IMA groups per SPA)

2XT3/E3 port SPA (42 IMA groups per SPA)

1xOC3 port SPA (42 IMA groups per SPA)

  • When the atm bandwidth dynamic command is enabled, all of the permanent virtual circuits (PVCs) configured on an IMA group interface are re-created if the total available IMA group bandwidth changes.
  • Maximum of 16 links can be configured on an IMA group.

IMA Link Bundle Configuration Overview

You bundle T1 or E1 links together by assigning the links to the same IMA group and configuring a PVC for the links in the group to use.

To assign a T1 or E1 link to an IMA group, issue the ima group group-number command under the T1 or E1 controller for the port that the link is attached to. Bundle a set of links together by issuing ima group under the controller for each of the links that you want to add to the bundle, and specify the same group number for each.

The router creates an IMA interface to represent the IMA group (link bundle). The interface has the same slot/subslot information as the SPA, followed by the IMA group ID, as shown here (for example, atm2/1/ima0):

interface atm slot / subslot / ima group-id

The IMA interface has all of the characteristics of an ATM interface and supports any currently supported ATM features.

When all of the T1/E1 interfaces are removed from an IMA group, the IMA interface that represents the group is removed.

To configure the IMA group for operation, you must:

Configuration Example

The following steps provide an example of the steps to configure an IMA link bundle on the 24-Port Channelized T1/E1 ATM CEoP SPA. Detailed steps are provided in the section that follows.

1. Bundle T1 or E1 links together by creating an IMA group and adding each link to the group. In this example, the T1 links attached to ports 0, 1, and 2 of the CEoP SPA in chassis slot 2, SPA subslot 1, are assigned to the same IMA link bundle (IMA group 0). Likewise, the E1 links attached to ports 0 and 1 of the SPA in chassis slot 5, SPA subslot 1 are assigned to another bundle (IMA group 1).

controller t1 2/1/0
ima-group 0
exit
controller t1 2/1/1
ima-group 0
exit
controller t1 2/1/2
ima-group 0
exit
 
controller e1 5/1/0
ima-group 1
exit
controller e1 5/1/1
ima-group 1
exit
 

2. Configure a PVC and MPLS pseudowire for the links in the IMA group to use. In the following example, PVC 0/100 is configured for the T1 links in IMA group 0 and PVC 0/101 is configured for the E1 links in IMA group 1:

interface atm2/1/ima0
pvc 0/100 l2transport
xconnect 10.2.0.1 10 encapsulation mpls
exit
interface atm5/1/ima1
pvc 0/101 l2transport
xconnect 10.20.0.4 11 encapsulation mpls
exit
 

3. Configure IMA group parameters to define how the links in the group are to operate. In the following example, IMA group 0 is being configured to operate with a minimum of 2 active links, independent clock mode, and a frame length of 256:

interface atm2/1/ima0
ima active-links-minimum 2
ima clock-mode independent
ima frame-length 256
exit

Configuring an IMA Link Bundle

To configure an IMA link bundle on a 24-Port Channelized T1/E1 ATM CEoP SPA, perform the following steps from global configuration mode:

 

Command or Action
Purpose

Step 1

Router(config)# controller { t1 | e1 } slot / subslot / port

Selects the controller for the link you want to add to an IMA link bundle (an IMA group).

  • slot / subslot / port identifies the chassis slot, SPA subslot, and port being configured.

Step 2

Router(config-controller)# [ no ] ima-group group-number

Creates an IMA group and adds the link to the group. Use the no form of the command remove the link from the IMA group.

  • group-number is a unique ID to assign to the group. Valid values are 0 through 41.

Note The group number must be unique for the SPA. The 24-Port Channelized T1/E1 ATM CEoP SPA supports 24 IMA groups.

Step 3

Router(config-controller)# exit

Returns to global configuration mode.

 


Repeat steps 1 through 3 to add additional links to the IMA link bundle.

Note All links in an IMA group must be located on the same CEoP SPA.

Step 4

Router(config)# interface atm slot / subslot ima group-number

Selects the IMA interface for the link bundle you just created and enters interface configuration mode.

  • atm slot / subslot specifies the location of the interface.
  • ima group-number identifies the IMA group.

Step 5

Router(config-if)# pvc vpi / vci

Configures a PVC for the IMA group and assigns the PVC a VPI and VCI.

  • vpi is the VPI of the PVC. Valid values are 0 to 255.
  • vci is the VCI of the PVC. Valid values are 32 to 1 less than the value set by the atm vc-per-vp command.

Note Do not specify 0 for both the VPI and VCI.

Step 6

Router(config-if)# xconnect peer-router-id vcid { encapsulation mpls | pseudowire-class name }

Configures a pseudowire to carry data from the IMA link bundle over the MPLS network. See the “Configuring an ATM Pseudowire” section for details on the command.

Step 7

Router(config-if)# ima command

Configures parameters for the IMA interface. See Table 11-2 for the configuration commands.

Step 8

Router(config-if)# end

Returns you to privileged EXEC mode.

Configuring IMA Group Parameters

Use the commands in Table 11-2 to configure parameters for an IMA group. Issue the commands in interface configuration mode under the IMA interface of the IMA group being configured. Use the no form of each command to turn off a feature or to revert to its default setting.


NoteIf you modify parameters on an IMA interface, the interface is automatically restarted.


 

Table 11-2 IMA Interface Parameters

Command Name
Description

[ no ] ima version { 1.0 | 1.1 }

Selects which version of IMA to use. The default is version 1.1.

[ no ] ima active-links-minimum number

Specifies the minimum number of IMA links that must be active for the IMA group to be active, where:

  • number is the number of links. Valid values are 1 through 16. The default is 1.

The IMA group is active as long as the specified number of links is active; otherwise, the group is brought down and remains out of service until the minimum number of links becomes active again. To determine an appropriate value, consider your application needs and performance requirements, and the number of links in the group.

[ no ] ima clock-mode { common | independent }

Sets the transmit clock mode for the links in the IMA group. The default is common.

  • common —All links use the same clock (which is derived from the specified port).
  • independent —Each link uses a different clock.

[ no ] ima frame-length { 32 | 64 | 128 | 256 }

Specifies the number of cells in an IMA frame. The default is 128.

Because each IMA frame contains an ICP cell, this parameter also controls how often ICP cells are sent over the links in the IMA group. For example, with a frame length of 64, 1 out of every 64 cells on the link is an ICP cell.

The smaller the IMA frame length, the more often ICP cells are sent, which reduces the amount of link bandwidth that is available for data.

[ no ] ima test [ link link number ] pattern pattern-id

Sends a continuous test pattern over an IMA link to verify that the link is operational. The pattern is looped back at the receiving end, which is useful for troubleshooting the physical link or configuration problems at the remote end. Use the no form of the command to stop the test.

  • link link number identifies the IMA link to test. For link number , specify the link ID that is displayed by the show ima interface interface command. Valid values are 0 through 15.
  • pattern pattern-id specifies the pattern to use. Valid values are 0 through 255 (0 to 0xFF), although 255 is not recommended.

Note If you do not specify a link, the test pattern is sent over the first available link.

[ no ] ima differential-delay-maximum milliseconds

Specifies the maximum allowable differential delay (in milliseconds) among links in the IMA group. If the delay on any link exceeds this value, that link is dropped from the IMA group.

IMA sends cells round-robin over the T1 or E1 links in an IMA group, and every link adds some delay. To enable the router to correctly reconstruct the original data stream, IMA adjusts for differences in link delay. However, if a link’s delay is greater than the specified maximum, the data stream cannot be reconstructed correctly.

Valid values for milliseconds are:

  • 25 to 250 milliseconds (T1)
  • 25 to 190 milliseconds (E1)

A shorter delay allows less adjustment among link delay variations. However, a longer delay can affect overall group performance by adding more latency to traffic or causing retransmission.

[ no ] ima autorestart { near-end-id near-end-group-id [ far-end-id far-end-group-id ]}

Enables the auto restart feature, which controls how IMA groups sync up after a restart. The no form of the command disables auto restart if it is enabled. See “IMA Auto Restart Examples” for examples.

When an IMA group stops operating correctly (for example, due to a failure with the CEoP SPA, an IMA link, or the router), the group must be restarted. When a restart occurs, the local IMA group must sync up with an IMA group at the remote end:

  • If auto restart is disabled (the default), IMA learns the ID of the remote group each time a restart occurs. In this case, the remote IMA group ID might change between restarts.
  • If auto restart is enabled, you can specify which remote IMA group the local group should sync up with. This allows you to keep an IMA group from syncing up with any group ID.

The near-end-id and far-end-id keywords identify the IMA groups. Valid values for near-end-id is 0-41. Valid values for far-end-id are 0-255 .

  • near-end-id near-end-group-id is the local IMA group.
  • far-end-id far-end-group-id is the remote IMA group.

If you specify near-end-id only, the local IMA group learns the ID of the remote group to sync up with (which will be the first remote IMA group to become active). This learned remote group ID remains active until the SPA is reloaded.

If you specify both near-end-id and far-end-id , the local IMA group will only synchronize with this remote IMA group. Both the near-end and far-end IDs must be the same.

ima restart

Manually restarts an IMA group. When an IMA group stops operating correctly (for example, due to a link failure), you can use this command to restart the group after the problem has been corrected.

Verifying the IMA Configuration

To display information about all configured IMA groups, or a specific group, use the show ima interface command in privileged EXEC mode:

show ima interface atm slot / subslot / ima group-number [ detail ]

In the following example, information is displayed for IMA group 1 (on the SPA in slot 5, subslot 0):

Router# show ima interface atm5/0/ima1
ATM5/0/ima1 is up, ACTIVATION COMPLETE
Slot 5 Slot Unit 0 unit 257, CTRL VC 257, Vir 0, VC -1
IMA Configured BW 12186, Active BW 3046
IMA version 1.0, Frame length 128
Link Test: Disabled
Auto-Restart: Disabled
ImaGroupState: NearEnd = operational, FarEnd = operational
ImaGroupFailureStatus = noFailure
IMA Group Current Configuration:
ImaGroupMinNumTxLinks = 1 ImaGroupMinNumRxLinks = 1
ImaGroupDiffDelayMax = 25 ImaGroupNeTxClkMode = common(ctc)
ImaGroupFrameLength = 128 ImaTestProcStatus = disabled
ImaGroupTestLink = None ImaGroupTestPattern = 0x0
ImaGroupConfLink = 8 ImaGroupActiveLink = 2
IMA Link Information:
ID Link Link Status Test Status
---- -------------- ------------------------------ ---------------
0 T1 5/0/0 Up - controller Up disabled
1 T1 5/0/1 Up - controller Up disabled
2 T1 5/0/2 Down - controller Up disabled
3 T1 5/0/3 Down - controller Up disabled
4 T1 5/0/4 Down - controller Up disabled
5 T1 5/0/5 Down - controller Up disabled
6 T1 5/0/6 Down - controller Up disabled
7 T1 5/0/7 Down - controller Up disabled

IMA Auto Restart Examples

IMA auto restart is disabled by default, which means that IMA learns the ID of the remote IMA group each time a restart occurs. To see the current settings for auto restart, issue the show ima interface command and view the Auto-Restart section of the command output.

Following are several examples of different ways to enable auto restart:

  • To enable auto restart so that the local IMA group synchronizes with the first remote IMA group that becomes active, issue the command as follows (where near-end-group-id identifies the local IMA group). The learned remote group ID remains active until the SPA is reloaded.
ima autorestart near-end-id near-end-group-id
  • To specify which remote IMA group the local IMA group should sync up with, issue the command as follows (where near-end-group-id identifies the local IMA group and far-end-group-id identifies the remote IMA group). Both near-end and far-end IDs must be the same.
ima autorestart near-end-id near-end-group-id far-end-id far-end-group-id
  • To disable auto restart and have IMA learn the remote IMA group ID after each restart, issue the command as follows:
no ima autorestart

Configuring Clocking

This section provides information about how to configure clocking on the 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA. It describes the following topics:

BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400

You can use the BITS Clock Support—Receive and Distribute—CEoP SPA on SIP-400 feature to select and configure a clock and distribute it across the chassis to be used as the Transmit reference on all SPA ports.

The BITS Clock support - Receive and Distribute - CEoP SPA on SIP-400 feature is supported on Cisco IOS Release 12.2SRB on the SPA-24CHT1-CE-ATM and the SPA-1CHOC3-CE-ATM, SPA-4XOC3 ATM, SPA-1xOC12/STM4 POS SPAs.

The line card operates in three different modes, dependiing on the configuration and the configured source state.

  • Free-running—A line card that is not participating in network-clocking or a line card that is actively sourcing the clock operates in free-running mode. In this mode, the line card internal oscillator generates the reference clock to the backplane.

Note In a nonpartcipating mode or a disabled mode, the line card distributes a Stratum 3-quality timing signal to an external reference clock. Other interfaces on different line cards receive either the backplane reference clock or the external reference clock depending on their configurations.


  • Normal—In normal mode, the module synchronizes with an externally supplied network timing reference, sourced from one of the chassis BITS inputs or recovered from a network interface. In this mode, the accuracy and stability of the output signal is determined by the accuracy and stability of the input reference.

Note Line card operation is in free-running mode only if the SIP-400 is configured as the active sources; otherwise the line cards operate in normal mode.


  • Holdover—In holdover mode, the network timing module generates a timing signal based on the stored timing reference used when operating in normal mode. Holdover mode is automatically selected when the recovered reference is lost or has drifted excessivley.

Note You cannot configure the drift range; it is set internally on the line card to +/-9.2 phase shifts per minute (ppm) by default.



Note All line cards operate in the free-running mode until network clock is configured.


Guidelines

Use the following guidelines:

  • The SIP-400 operates in free-running mode until network clock is configured.
  • When the network clocking configuration is present in the startup configuration, the clocking configuration is not applied until five minutes after the configuration has been parsed. This prevents clocking instability on the backplane when the interfaces/controllers come up out of order.
  • Network clocking is enabled by default for the SIP-400.
  • Cisco IOS Release 12.2SRB does not support local network clock configurations or synchronization status messaging (SSM).
  • If there is a source flap, there is an interval of 180 seconds before the source becomes valid and active.
  • In the event of an Out-of-Range (OOR) switchover (revertive mode), the source switchover occurs when the clock offset crosses the -9.2 ppm or +9.2 ppm threshold. If this occurs, you must reconfigure the source.

Configuration Tasks

To configure Network Clocking for the Cisco 7600/SIP-400, use the following commands:

 

Command or Action
Purpose

Router# [no] network-clock select priority interface | controller | slot | system interface name [ global ][ local ]

Selects an interface, controller, and configures it as a network clock source at a particular priority.

  • system —Required for platforms that have an internal clock generator. Not applicable for the Cisco 7600 series routers.
  • priority— Configures the priority of network clock source. Values range from 1 to 6.
  • interface name —Configures the network-clock-source to the selected interface.
  • global —Configures the network clock to use a global configuration.
  • local —Configures the network clock to use a local configuration.

Note Configure only one source at a time.

Router# [no] network-clock participate slotnum

Enables a line card to participate in network clocking feature. This is default mode. The no form of this command prevents a line card from participating in network clocking feature. When a slot is disabled, it can neither source nor take the clock from the backplane.

Router# [no] network-clock revertive

Configures revertive behavior on the network clock.

When revertive mode is configured and a previously unavailable higher priority source comes up, then this source becomes the active clock and the previous active source becomes the standby clock. Revertive mode is the default mode and is applicable for all types of interface failures. The alternate source is selected only if there is an interface failure, the alternate source is not selected when a source is supplying the bad clock.

The no form of this command configures nonrevertive mode.

Router(config)# [no] network-clock switchover marginal-source

Prevents an interface from sending an OOR clock. A clock that exceeds the +/-9.2 ppm threshold goes into an OOR state and next alternate source is selected as active. Use the no form of this command to disable it. The default is that switchover occurs on a bad clock.

Router# clock source {line | internal | network}

Enables network clocking and configures clocking on the interface.

  • line Specifies clock recovered from line
  • internal—Specifies SPA internal clock or clock from the host
  • network —Specifies network clock or the host card’s internal oscillator

Router# show network-clocks

Displays details about the configured clocks and the current operational clocks and provides status information.

Router# show platform hardware network-clocks

Shows the mode of operation of the line cards along with relevant SONET clock register settings.

This command is available for line card consoles only.

Router# debug network-clock

This command when enabled helps in debugging network clocking feature operation.

Router# debug network-clock redundancy

Enables high availability (HA) related debugging.

Verifying

Use the show platform hardware network-clocks command to verify.

SIP-400-4# show plat hardware network-clocks
SONET Clock Register = 0x20CA8000
SONET Clock Interrupt Enable Register = 0x0
SONET Clock Interrupt Status Register = 0x0
 
MT90401 Reference : Primary Free Running
Primary : SPA 0
Secondary : SPA 0
Backplane Reference
Primary DISABLED : SPA 0
Secondary DISABLED : SPA 0
Status :
Lock : 0 HoldOver : 0 SecOOR : 1 PriOOR : 1
CLK_2M_OK : 1
Config :
PCCI : 0 FLOCK : 0 ModeSel : 2
SI5321 CAL Signal : 0 SI5321 LOS Signal : 0
SI5321 HoldOver : 0
SIP-400-4#
 
use the show network-clock command to verify output on RP
 
Router# show network-clocks
Active source = SONET 1/3/0
Active source backplane reference line = Primary Backplane Clock
 
 
All Network Clock Configuration
---------------------------------
Priority Clock Source State Reason
1 SONET 1/3/0 Valid
 
Current operating mode is Revertive
 
Current OOR Switchover mode is Switchover
 
There are no slots disabled from participating in network clocking

Configuring Clock Recovery

When configuring clock recovery, consider the following guidelines:

Adaptive Clock Recovery

  • Clock source:

In Cisco IOS Release 12.2(33)SRC and later, both the 1-Port Channelized OC-3 STM1 ATM CEoP SPA and the 24-Port Channelized T1/E1 ATM CEoP SPA can be used as a clock source.

In earlier releases, only the 24-Port Channelized T1/E1 ATM CEoP SPA can be a clock source.

Effective from Cisco IOS Release 15.1(1)S release, 2XT3E3 CE/ATM SPA supports adaptive clock recovery for T3/E3 CEM. Out of Band (OOB) Clocking for T3/E3 CEM is not supported due to lack of hardware support.

  • Number of clock sources allowed:

In Cisco IOS Release 12.2(33)SRC and later, multiple clocks can be sourced for the router: one clock for each SPA.

In earlier releases, only a single clock can be sourced for a router.

  • The clock must be the same as used by the router as the network clock. Any pseudowire in this case can carry the clock.
  • The minimum bundle size of CEM pseudowires on the network that delivers robust clock recovery is 4 DS0s.
  • The minimum packet size of CEM pseudowires on the network that delivers robust clock recovery is 64 bytes.

Differential Clocking

  • The maximum number of differential clocks sourced from a 24-Port Channelized T1/E1 ATM CEoP SPA is 24.
  • The 24-Port Channelized T1/E1 ATM CEoP SPA can recover up to 24 T1/E1 clocks.
  • There are several bundles sent from the same port. The bundle that is used for carryingthe clock of the port is the first created bundle of the port. Only pseudowires that include the first DS0 of a port can carry differential clock.

To configure clock recovery on a 24-Port Channelized T1/E1 ATM CEoP SPA, use the following procedure:

 

Command or Action
Purpose

Step 1

Router(config)# controller { e1 | t1 } slot / subslot / port

Selects the controller.

Step 2

Router(config-controller)# recovered-clock slot / subslot

Specifies the interface for the recovered clock.

Step 3

Router(config-controller)# clock recovered clock-id { adaptive | differential } cem port cem-group

Specifies the recovered clock number and the clock recovery type.

Step 4

Router(config-controller)# clock reference { enhanced | internal }

Specifies the clock reference.

Step 5

Router(config-controller)# clock master

Configures the clock master.

Step 6

Router(config-controller)# clock slave

Configures the clock slave.

To apply the recovered clock to the controller, use the following procedure:

 

Command or Action
Purpose

Step 1

Router(config)# controller { e1 | t1 } slot / subslot / port

Selects the controller.

Step 2

Router(config-controller)# clock source recovered number

Assigns a number to the recovered clock.

Step 3

Router(config-controller)# cem-group number timeslots number

Creates a circuit emulation channel from one or more time slots of a T1 or E1.

Step 4

Router(config-controller)# recovered-clock slot / subslot

Applies the recovered clock to the interface.

Step 5

Router(config-controller)# clock recovered clock-id { adaptive | differential } cem port cem-group

Specifies the recovered clock number and the clock recovery type.

Verifying Clock Recovery

To verify clock recovery, use the show recovered-clock command. In Cisco IOS Release 12.2SRB1 and later, command output has been expanded to include the port number and CEM group number.

Router# show recovered-clock
Recovered clock status for subslot 3/0
----------------------------------------
Clock Mode Port CEM Status Frequency Offset(ppb)
1 ADAPTIVE 0 1 HOLDOVER 0
 
Router# show recovered-clock
Recovered clock status for subslot 3/0
----------------------------------------
Clock Mode Port CEM Status Frequency Offset(ppb)
1 ADAPTIVE 0 1 ACQUIRING -694
 
 

Use the show platform network-clock command to display the contents of network clocking registers.

Router# show platform network-clock
SONET Clock Register = 0x20EB80C8
SONET Clock Interrupt Enable Register = 0x0
SONET Clock Interrupt Status Register = 0x2
 
MT90401 Reference : Primary Reserved
Primary : SPA 0
Secondary : SPA 0
Backplane Reference
Primary ENABLE : SPA 0
Secondary ENABLE : MT90401
Status :
Lock : 0 HoldOver : 1 SecOOR : 1 PriOOR : 1
CLK_2M_OK : 1
Config :
PCCI : 0 FLOCK : 0 ModeSel : 3
SI5321 CAL Signal : 0 SI5321 LOS Signal : 0
SI5321 HoldOver : 0

Configuring Out-of-Band Clocking

A TDM network requires a synchronized clock at each end of the connection (the source and destination). This means that the source and destination clock signals must be synchronized to each other in order to maintain data integrity on the communication link.

On the other hand, a packet-switched network (PSN) does not use a clocking strategy, which means that the PSN does not provide frequency synchronization between source and destination routers. Therefore, to transmit TDM data across a PSN (such as an MPLS network), we need a way to deliver the clocking signal between the source and destination routers.

Out-of-band clocking provides a way to deliver a clock signal between two CEoP SPAs, which allows TDM devices connected to the SPAs to communicate with each other. Dedicated pseudowires (called out-of-band clock channels) carry the timing signal between the sending and receiving SPAs. When a TDM device sends data to a destination TDM device, the receiving SPA uses the out-of-band clock channel to recover the clock signal that was used to send the data.

By keeping the timing packets separate from data packets, out-of-band clocking delivers an extremely accurate timing signal. This timing accuracy is important for mobile wireless applications and other specialized applications that have very low tolerances for such things as packet delay variation (PDV), jitter, and latency in the network. In-band clocking (where timing information is derived from the data stream) does not provide a clock that is accurate enough for these applications.

To set up out-of-band clock channels, you must configure a master clock interface and a slave clock interface on the SPAs and configure pseudowires to connect the master and slave clocks. Instructions for performing these steps are provided later in this section.

Benefits

Out-of-band clocking provides the following benefits:

  • Enables mobile wireless providers to migrate from TDM networks to PSNs in order to save on costs and improve scalability.
  • CEoP equipment can ignore the contents of the timing packets that are sent over the out-of-band clock channel because the packets do not contain data.
  • Allows the CEoP SPA to be used for applications that use something other than constant bit rate (CBR) data. For example, out-of-band clocking allows the SPA to be used for 3G (data) wireless applications, which use AAL2 in variable bit rate (VBR) mode. In addition, out-of-band clocking allows the SPA to be used for 2G (voice) applications.
  • Provides recovered clock accuracy that complies with ITU-T specifications G.823 and G.824, which enables the CEoP SPA to be used in mobile and wireless applications (including voice) that require extreme synchronization accuracy.
  • Provides an alternative clock-recovery mechanism when adaptive clocking cannot be deployed.
  • Enables the CEoP SPA to be the master clock in a PSN.
  • Makes it possible to have two master clocks. Previously, only one master clock was possible.

Configuration Guidelines

The following guidelines apply to out-of-band clocking on CEoP SPAs:

  • The default packet size for out-of-band clock channels (CEM circuits) is 910 bytes.
  • Out-of-band clocking can co-exist with Stateful SwitchOver (SSO), but it is not SSO compliant. Therefore, if a switchover occurs, the out-of-band clocking functionality is not available for a brief period of time while the feature is brought back online.
  • A CEoP SPA cannot be configured as both a master and slave clock. To reconfigure a SPA’s clock type, you must first remove the existing clock configuration (master or slave).
  • Pseudowires for out-of-band clocking are configured under the virtual CEM interface that represents the recovered clock interface. This process differs from normal CEM pseudowires, which are configured under the port (controller interface).
    When no network clock is available, the virtual CEM interface goes down and the pseudowire is disabled. This process is reversed when a valid network clock becomes available again. Normal CEM interfaces never go down, even if the associated physical link is down.
  • The master clock pseudowire and slave clock pseudowire should be on different CEoP SPAs.

Router Sending Clock (Master Clock)

  • You must select the common telecom 19.44MHz clock as the recovered clock to use for the master clock.
  • A maximum of 64 out-of-band clock channels can be configured from the CEoP SPA that provides the master clock signal.
  • The out-of-band clock channel (pseudowire) is configured under the virtual CEM interface that represents the SPA from which the master clock is recovered. The xconnect command used to create the clock channel must specify the destination for the clock signal.
  • The out-of-band clock stream is sent in SAToP (unframed) format.

Router Recovering Clock (Slave Clock)

  • The out-of-band clock signal is always recovered in adaptive mode. The clock signal can then be used to drive all of the ports on the CEoP SPA.
  • Two CEM circuits (a primary and a secondary out-of-band channel) can be configured under a slave clock interface, one for each of two master clock signals. This way, the SPA can receive a master clock signal from two separate sources (that is, two master clocks).
  • Under the slave clock interface, the xconnect command (used to create the out-of-band clock channel) must specify the router from which the master clock is recovered.

Configuration Overview

The following steps provide a high-level overview of the procedure for configuring out-of-band clocking between two CEoP SPAs. Detailed steps are provided in the sections that follow.

Before you begin, determine which CEoP SPAs have TDM devices connected to them. You must configure an out-of-band clock channel to deliver the clock signal from each SPA that sends TDM data to every destination SPA that receives the data.

1. Use the recovered clock command to identify the CEoP SPA that is to send TDM data across the MPLS network. This SPA’s clock is used as the master clock for out-of-band clocking.

2. Configure master and slave clock interfaces to represent the source (clock master) and destination (clock slave) for the out-of-band clock signal. The master and slave clock interfaces (and pseudowires) should be configured on different SPAs.

a. The master clock interface represents the master clock, which is distributed to all destination CEoP SPAs that receive data from the source TDM device connected to this SPA. (See the “Creating and Configuring the Master Clock Interface” section for instructions.)

b. Configure a slave clock interface on each of the SPAs connected to TDM devices that can receive data from the source TDM device. (See the “Configuring the Slave Clock Interface” section for detailed instructions.)


Note When you configure a master or slave clock interface, the router creates a virtual CEM interface to represent this out-of-band clock. The virtual CEM interface has the same slot and subslot information as the CEoP SPA from which the master clock is recovered. The port number is always 24. For example, if the clock signal is recovered from the SPA in slot 8, subslot 1 (recovered-clock 8 1), the virtual CEM interface is virtual-cem8/1/24.


3. Under both the master and slave clock interfaces, use the cem circuit-id command to configure CEM circuits to represent the out-of-band channels that will distribute the clock signal over the MPLS network. Each CEM circuit represents a separate out-of-band channel for delivering the clock signal from the source (master clock) to a destination TDM device (slave clock). The out-of-band clock channel is created when you issue the xconnect command in the next step.

Under the master clock interface, you can configure up to 64 CEM circuits, one for each of the destination TDM devices that will use this clock signal as its master clock.

Under the slave clock interface (on the destination TDM device), you can configure one or two CEM circuits. Two CEM circuits are allowed because the clock slave can receive a clock signal from two master clocks.


Note Each out-of-band clock channel requires two CEM circuits (one on the master clock interface and one on the slave clock interface). Each CEM circuit represents the CEM attachment circuit at one end of the out-of-band clock channel.


4. Create the out-of-band channel for the clock signal by using the xconnect command to configure two pseudowires between the CEM circuit on the master clock interface and the CEM circuit on the slave clock interface. The master clock pseudowire and slave clock pseudowire should be on different SPAs; however, you should use the same VCID for both pseudowires.

a. Under the master clock interface, configure a pseudowire to the destination device (slave clock).

b. Under the slave clock interface (on the SPA that connects to the destination TDM device), configure a pseudowire to the router that contains the master clock interface.

Creating and Configuring the Master Clock Interface

To create the master clock interface for out-of-band clocking, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# recovered-clock slot / subslot

Specifies the slot and subslot of the CEoP SPA to recover the master clock signal from. This is the SPA from which the TDM data will be sent.

Note You must specify the 19.44MHz clock as the recovered clock to use as the clock master.

Step 2

Router(config)# clock master

Specifies that the recovered clock is to be used as the master clock signal for out-of-band clocking.

The router creates a virtual CEM interface for the master clock. Go to the following steps to configure an out-of-band channel to use for the master clock.

To configure the out-of-band channel to use for the master clock signal, perform the following steps:

 

Command or Action
Purpose

Step 1

Router(config)# int virtual-cem slot / subslot / port

Selects the virtual CEM interface for the master clock and enters interface configuration mode. The interface has the same slot and subslot as the SPA from which the master clock was recovered (Step 1 in the preceding task), and the port number is always 24.

Step 2

Router(config-if)# cem circuit-id

Creates a CEM attachment circuit for the master clock signal. Valid values for circuit-id are 0 to 63.

Note You can configure up to 64 CEM circuits under the master clock interface.

Step 3

Router(config-if-cem)# xconnect peer-router-id vcid encapsulation mpls

Configures an out-of-band channel (pseudowire) to carry the master clock signal.

  • peer-router-id is the IP address of the router that is connected to the destination TDM device.
  • vcid is a 32-bit identifier for the pseudowire.
  • encapsulation mpls sets MPLS for the tunneling mode.

Note Use the same vcid for the master and slave clock pseudowires; otherwise, the clock channel does not come up.

Step 4

Router(config-if-cem-xconn)# end

Exits CEM interface configuration mode and returns you to privileged EXEC mode.


NoteA CEoP SPA cannot be configured as both master and slave at the same time. To reconfigure a SPA’s clock type, you must first remove the existing clock configuration.


Configuring the Slave Clock Interface

To configure the slave clock interface and out-of-band channel to use for out-of-band clocking, perform the following steps. Configure a slave clock interface on every CEoP SPA that receives TDM data from the SPA configured as the master clock in the preceding section.

 

Command or Action
Purpose

Step 1

Router(config)# recovered-clock slot / subslot

Specifies the slot and subslot of the CEoP SPA from which the master clock is recovered.

Step 2

Router(config)# clock slave

Creates a virtual CEM interface to represent the clock slave for out-of-band clocking.

Step 3

Router(config)# int virtual-cem slot / subslot / port

Enters configuration mode for the virtual CEM interface that represents the clock slave.

  • slot / subslot is the slot and subslot of the SPA from which the master clock was recovered (Step 1 above).
  • port is always 24.

Step 4

Router(config-if)# cem circuit-id

Creates a CEM attachment circuit for the clock slave. The circuit-id value can be:

  • 0—The primary clock source.
  • 1—The secondary clock source.

Note You can configure up to two CEM circuits, one for each of two master clock signals.

Step 5

Router(config-if-cem)# xconnect peer-router-id vcid encapsulation mpls

Configures an out-of-band channel (pseudowire) to carry the clock signal.

  • peer-router-id is the IP address of the router that is connected to the source TDM device.
  • vcid is a 32-bit identifier for the pseudowire.
  • encapsulation mpls sets MPLS for the tunneling mode.

Note Use the same VCID for the master and slave clock pseudowires; otherwise, the clock channel does not come up.

Step 6

Router(config-if-cem-xconn)# end

Exits CEM interface configuration mode and returns you to privileged EXEC mode.

Verifying Out-of-Band Clocking

This section lists the show commands that you can use to verify the out-of-band clocking configuration.

  • Use the show ip interface brief command to display the virtual CEM interfaces that the router created to represent master and slave clock interfaces. The output in the following example shows only the virtual CEM interface. Information for all other interfaces is omitted from the display.
Router# show ip int brief
. . .
Virtual-cem8/1/24 unassigned YES unset up up
. . .
 
  • Use the show cem circuit command to display a list of CEM circuits configured on the SPA. The command displays both normal and out-of-band clocking CEM circuits.
Router# show cem circuit
CEM Int. ID Line Admin Circuit AC
--------------------------------------------------------------
CEM8/1/1 1 DOWN DOWN Active --/--
Virtual-cem8/1/1 DOWN UP Active UP
 
  • Use the show cem interface virtual-cem slot / subslot / port command to display information about a particular virtual CEM interface:
Router# show cem interface virtual-cem 8/1/24
(Virtual-cem8/1/24) State: CONFIG COMPLETE
Virtual CEM Slave Clock Interface
Slot 8, Slot Unit 88, VC -1
Total cem circuits: 1
Cem circuits up : 1
Cem circuits down : 0
 
  • Use the show run interface virtual-cem slot / subslot / port command to dislay the current running configuration for the specified interface:
Router# show run int virtual-cem 8/1/24
Building configuration...
 
Current configuration : 117 bytes
!
interface Virtual-cem8/1/24
no ip address
cem 1
rtp-present
xconnect 20.0.0.1 300 encapsulation mpls
!
end
 
  • Use the show run | begin recovered command to display the recovered clock being used for out-of-band clocking:
Router# show run | begin recovered
recovered-clock 8 1
clock master
 
  • On the clock slave, you can use the show recovered-clock command to display the status of the out-of-band clock:
Router# show recovered-clock
Recovered clock status for subslot 3/0
----------------------------------------
Clock Mode Port CEM Status Frequency Offset(ppb)
ENHANCED PRIMARY 0 HOLDOVER 0

Removing the Out-of-Band Clocking Configuration

Use the following commands to delete the various components used for out-of-band clocking:

  • To remove a CEM circuit, use the no cem circuit-id command (where circuit-id is the number assigned to the circuit). Issue the command under the virtual CEM interface where the circuit exists.
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int virtual-cem 8/1/24
Router(config-if)# no cem 1
Router(config-if)# end
 
  • To remove a virtual CEM interface, use the no clock master or no clock slave command in recovered-clock configuration mode, as shown in the following examples. Note that the virtual CEM interface is not deleted when you remove the last CEM circuit under the interface.
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# recovered-clock 8 1
Router(config-clock)# no clock master
Router(config-clock)# end
Router#
 

In the following example, the no clock slave command deletes the slave clock interface for the recovered clock (which is 8/1):

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# recovered-clock 8 1
Router(config-clock)# no clock slave
Router(config-clock)# end
Router#

Out-of-Band Clocking Configuration Example

This section provides an example of how to configure out-of-band clocking between two CEoP SPAs. It is divided into several different configuration sections.

Configuring the Master Clock Interface

The following example shows how to configure a CEoP SPA as a master clock and verify the configuration:

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router (config)# recovered-clock ?
<0-14> Slot number
 
Router (config)# recovered-clock 8 1
Router(config-clock)# clock ?
master Configure clock master on the card
recovered Configure recovered clock on the card
reference Configure reference clock on the card
slave Configure clock slave on the card
Router(config-clock)# clock master
Router(config-clock)# end
 
Router# show run | begin recovered
recovered-clock 8 1
clock master

Configuring the Slave Clock Interface

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# recovered-clock 8 1
Router(config-clock)# clock slave
Router(config-clock)# end
Router#
Router# show run | begin recovered-clock
recovered-clock 8 1
clock slave

Verifying the Virtual CEM Interface Configuration

The router creates a virtual CEM interface when you configure either the master or slave clock interface. You can view the interface using the show ip interface brief command:

Router# show ip int br
Virtual-cem8/1/24 unassigned YES unset up up
 
Router# sh run int Virtual-cem 8/1/24
Building configuration...
 
Current configuration : 50 bytes
!
interface Virtual-cem8/1/24
no ip address
end

Configuring CEM Circuits for Out-of-Band Clocking Example

This section provides an example of how to configure CEM circuits and pseudowires for out-of-band clocking. The sample configuration shows the circuits and pseudowires configured on a CEoP SPA in PE1, which sends TDM data to another CEoP SPA in PE2.

You configure CEM circuits for the master and slave clocks under the virtual CEM interface that represents the recovered clock that is being used for out-of-band clocking. This differs from normal CEM circuits, which are configured under the SPA controller through the cem-group command.

Issuing the xconnect command under the master and slave CEM circuits configures an out-of-band clock channel to use to send the clock signal from the sending SPA to the receiving SPA. Note that normal CEM pseudowires are configured under the SPA controller interface.

Out-of-Band Clocking (PE1)

PE1# conf t
PE1(config)# int virtual-cem 8/1/24
PE1(config-if)# cem 1
PE1(config-if-cem)# xconnect 20.0.0.1 200 encap mpls
PE1(cfg-if-cem-xconn)# end
 
PE1# show run int Virtual-CEM 8/1/24
Building configuration...
 
Current configuration : 117 bytes
!
interface Virtual-cem8/1/24
no ip address
cem 1
rtp-present
xconnect 20.0.0.1 200 encapsulation mpls
!
end

Out-of-Band Clocking (PE2)

PE2# conf t
PE2(config)# int virtual-cem 8/1/24
PE2(config-if)# cem 1
PE2(config-if-cem)# xconnect 10.0.0.1 200 encap mpls
PE2(cfg-if-cem-xconn)# end
 
PE2# show run int Virtual-CEM 8/1/24
Building configuration...
 
Current configuration : 117 bytes
!
interface Virtual-cem8/1/24
no ip address
cem 1
rtp-present
xconnect 10.0.0.1 200 encapsulation mpls
!
end

Configuring CEM Parameters

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


NoteThe CEM parameters at the local and remote ends of a CEM circuit must match; otherwise, the pseudowire between the local and remote PE routers will not come up.


Configuring Payload Size (Optional)

To specify the number of bytes encapsulated into a single IP packet, use the pay-load size command. The size argument specifies the number of bytes in the payload of each packet. The range is from 32 to 1313 bytes.

Default payload sizes for an unstructured CEM channel are as follows:

  • E1 = 56 bytes
  • T1 = 192 bytes
  • T3/E3 = 1024 bytes

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

The payload size must be an integer of the multiple of the number of time slots for structured CEM channels.

Effective with Cisco IOS release 12.2 SRB for Cisco 7600 and later releases, configuring the payload size for virtual cem interfaces is possible only at interface level and not allowed on the cem circuit mode. On normal cem interfaces, the payload size can be configured on the cem circuit mode.

If you try to configure payload size in cem circuit mode for a virtual cem interface, the router shows a warning message as given in the following example:

Router# conf t
Router(config)# interface virtual-cem 3/1/24
Router(config-if)# cem 0
Router(config-if-cem)# payload-size 333
Use interface wide payload size command to configure
Router(config-if-cem)# exit
 

Instead of that, you can configure payload size at the interface level for the virtual cem interface as shown in the following example.

Router# conf t
Router(config)# interface virtual-cem 3/1/24
Router(config-if)# payload-size 320
Router(config-if)# exit

Setting the Dejitter Buffer Size

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

Setting the Idle Pattern (Optional)

To specify the idle pattern, use the [ no ] idle-pattern pattern1 command. The payload of each lost CESoPSN data packet must be replaced with the equivalent amount of the replacement data. The range for pattern is from 0x0 to 0xFF; the default idle pattern is 0xFF.

Enabling Dummy Mode

Dummy mode enables a bit pattern for filling in for lost or corrupted frames. To enable dummy mode, use the dummy-mode [ last-frame | user-defined ] command. The default is last-frame. The following is an example:

Router(config-cem)# dummy-mode last-frame

Setting the Dummy Pattern

If dummy mode is set to user defined, you must use the dummy-pattern pattern command to configure the dummy pattern. The range for pattern is from 0x0 to 0xFF. The default dummy pattern is 0xFF. The following is an example:

Router(config-cem)# dummy-pattern 0x55

Shutting Down a CEM Channel

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

Configuring Access Circuit Redundancy on CEoP and ATM SPAs

Access Circuit Redundancy (ACR) is supported on CEoP and ATM SPAs. The support enables local switching for ATM, IMA and CEM interfaces. Similar to the virtual ACR interface for ATM SPAs, the virtual CEM-ACR, IMA-ACR and ATM-ACR interfaces are created depending on the configuration.

For configuring ACR and virtual ACR interface for ATM SPAs, see Configuring Access Circuit Redundancy on SIP-400 ATM SPA s.

Restrictions and Usage Guidelines

Follow these restrictions and usage guidelines while configuring ACR on CEoP and ATM SPAs:

  • ACR support for CEoP SPAs is applicable for ATM, IMA, and CEM interfaces on the same router. The support is not extended for multi level routers.
  • Configure the frame manually under the virtual controller and two physical member controllers. This is consistent across the interfaces.
  • You can configure a maximum of 256 controllers on the ACR groups on a single router. But the Cisco 7600 router can hold a maximum of 44 CEoP SPAs, which restricts the maximum number of ACR controllers to 22.
  • You cannot configure ACRs within the physical ATM, CEM, or IMA interfaces that are part of the ACR group, but allowed on the ATM-ACR, CEM-ACR, IMA-ACR interfaces.

Configuring the ACR Group

This section provides the configuration for ACR in ATM, IMA, and CEM interfaces.

SUMMARY STEPS


Step 1 enable

Step 2 configure terminal

Step 3 controller sonet slot/subslot/port

Step 4 aps group acr acr no

Step 5 aps working circuit number

Step 6 exit

Step 7 controller sonet slot/subslot/port

Step 8 aps group acr acr no

Step 9 aps protect circuit number ip-address

Step 10 aps revert minutes

Step 11 exit

DETAILED STEPS

Command or Action
Purpose

Step 1

Router # enable

Enables privileged EXEC mode..

Step 2

Router# configure terminal

Enters global configuration mode.

Step 3

Router (config)# controller sonet slot/subslot/port

Select the controller to configure and enter controller configuration mode.

Step 4

Router(config-controller)# aps group acr acr no

This command configures the APS group for the controller.

acr- This command configures the ACR group on top of APS.

acr no—This specifies a group number between 0 and 255. An ACR virtual controller is created.

Step 5

Router (config-controller)# aps working circuit number

Identifies the interface as the Working interface.

circuit-number—Identification number for this particular channel in the APS pair. Since the interface only supports 1 + 1 redundancy, the valid values are 0 or 1, and the default value for working interface is 1.

Step 6

Router (config-controller)# exit

Exits interface configuration mode and returns to privileged EXEC mode.

Step 7

Router (config)# controller sonet slot/subslot/port

Select the controller to configure and enter controller configuration mode.

Step 8

Router(config-controller)# aps group acr acr no

Enables the use of the APS Protect Group Protocol for the working interface.

Step 9

Router(config-controller)#aps protect circuit number ip-address

aps protect- Identifies this interface as the Protect interface:

  • circuit-number —Identification number for this particular channel in the APS pair. Because only 1+1 redundancy is supported, the only valid values are 0 or 1, and the Protect interface defaults to 0.
  • ip-address —IP address for the loopback interface. The Protect interface uses this IP address to communicate with the working interface.

The APS group can be active or inactive.
Active-The interface that is currently sending and receiving data.
Inactive-The interface which is currently standing by to take over when the active fails.

Step 10

Router(config-controller)#aps revert minutes

aps revert- This command configures the ACR interface as revert. The value of the minutes argument specifies the time, in minutes, after which the revert process begins.

Note Use the revert command only under the protect member of the ACR group.

To create an ACR interface without any members attached, use the interface acr acr no command.

Step 11

Router (config-controller)# exit

Exits interface configuration mode and returns to privileged EXEC mode.

Example 11-1 Configuring ACR Interface

This is an example for configuring ACR interface:

ACR-PE2# Configure terminal
ACR-PE2(config)# Controller sonet 4/1/0
ACR-PE2(config-controller)# aps group acr 1
ACR-PE2(config-controller)# aps working 1
ACR-PE2(config-controller)# exit

 

ACR-PE2(config)# controller sonet 3/1/0
ACR-PE2(config-controller)# aps group acr 1
ACR-PE2(config-controller)# aps protect 1 4.1.1.1
ACR-PE2(config-controller)# do show ip interface br | incl Loop
 
Loopback0 4.1.1.1 YES NVRAM up up
 
ACR-PE2(config-controller)#end

Verifying ACR Group

ACR-PE2# show acr group
 
ACR Group Working I/f Protect I/f Currently Active Status
 
--------------------------------------------------------------------------
 
1 SONET 4/1/0 SONET 3/1/0 SONET 4/1/0

Configuring CEM, ATM, and IMA Interfaces

This section provides the configuration for CEM, ATM, and IMA interfaces:

SUMMARY STEPS


Step 1 enable

Step 2 configure terminal

Step 3 controller sonet 5/1/0

Step 4 sts-1 2

Step 5 vtg 3 t1 2 atm

or

vtg 1 t1 1 ima-group group-number

or

vtg 2 t1 1 cem-group 1 unframed

or

vtg 2 t1 4 cem-group 2 timeslots 1-5,14

Step 6 exit

DETAILED STEPS:

Command or Action
Purpose

Step 1

Router # enable

Enables privileged EXEC mode..

Step 2

Router# configure terminal

Enters global configuration mode.

Step 3

Router(config)# controller sonet 5/1/0

Selects the controller to configure.

Step 4

Router(config-controller)# sts-1 2

Specifies the STS identifier.

Step 5

Router(config-ctrlr-sts1)# vtg 3 t1 2 atm

Creates a T1 (VT1.5) ATM interface.

OR,

Router(config-ctrlr-sts1)# vtg 1 t1 1 ima-group group-number

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

OR,

Router(config-ctrlr-sts1)# vtg 2 t1 1 cem-group 1 unframed

Creates a single SAToP CEM group.

OR,

Router(config-ctrlr-sts1)# vtg 2 t1 4 cem-group 2 timeslots 1-5,14

Creates a CESoPSN CEM group.

Step 6

Router (config-controller)# exit

Exits interface configuration mode and returns to privileged EXEC mode.

Example 11-2 Configuring CEM Interface

ACR-PE2# Configure terminal
ACR-PE2(config)# controller sonet-acr 1
ACR-PE2(config-ctrlr-sts1)# sts-1 1
ACR-PE2(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 1 timeslots 1-10
ACR-PE2(config-ctrlr-sts1)# sts-1 2
ACR-PE2(config-ctrlr-sts1)# vtg 1 t1 2 atm
ACR-PE2(config-ctrlr-sts1)# vtg 1 t1 2 ima 10
ACR-PE2(config-ctrlr-sts1)# end

 

ACR-PE2# show run | sec SONET-ACR 1
controller SONET-ACR 1
framing sonet
!
sts-1 1
mode vt-15
vtg 1 t1 1 cem-group 1 timeslots 1-10 >>>> CEM configs
vtg 1 t1 2 ima-group 10 >>>>>>>>>>>>>>>>> IMA configs
!
sts-1 2
mode vt-15
vtg 1 t1 2 atm >>>>>>>>>>>>>>>>>>>>>>>> ATM configs
!
sts-1 3
mode vt-15

 

ACR-PE2# show ip int br | incl ACR
 
CEM-ACR1 unassigned YES unset up up
 
ATM-ACR1.2/1/2 unassigned YES unset down down
 
IMA-ACR1/ima10 unassigned YES unset up up

Verifying CEM Interface

ACR-PE2# show cem circuit
CEM Int. ID Ctrlr Admin Circuit AC
--------------------------------------------------------------
CEM-ACR1 1 UP UP Active --/--

 

Configure IMA-ACR Interface

ACR-PE2# configure terminal
ACR-PE2(config)# int IMA-ACR1/ima10
ACR-PE2(config-controller)# pvc 89/90 l2trans
ACR-PE2(cfg-if-atm-l2trans-pvc)# end

Show Commands

This section includes show commands for ACR:

ACR-PE2# show acr group 1 detail cem
ACR Group Working I/f Protect I/f Currently Active Status
--------------------------------------------------------------------------
CE1 CEM4/1/0 CEM3/1/0 CEM4/1/0
CEM CKT Details
Cktid State on Working State on Protect
1 Provision Success Provision Success

 

ACR-PE2# show acr group 1 detail atm
ACR Group Working I/f Protect I/f Currently Active Status
--------------------------------------------------------------------------
AT1.2/1/2 ATM4/1/0.2/1/2 ATM3/1/0.2/1/2 ATM4/1/0.2/1/2
ATM PVC Detail
VPI VCI State on Working State on Protect
23 34 Unknown Unknown

 

ACR-PE2# show acr group 1 detail ima
ACR Group Working I/f Protect I/f Currently Active Status
--------------------------------------------------------------------------
IM1/ima10 ATM4/1/ima10 ATM3/1/ima10 ATM4/1/ima10
ATM PVC Detail
VPI VCI State on Working State on Protect
89 90 Provision Success Provision Success

Troubleshooting the ACR configuration

This section provides the supported debug commands to troubleshoot the ACR configuration:

  • debug acr events : Provides details on all events occurring on the ACR interface.
  • debug acr errors : Provides debugging information on errors.
  • debug acr state : Provides debugging information on state change – when there is a switchover.
  • debug cem events : Debugging informationto create and delete CEM circuits.
  • debug cem errors : Debugging information about possible errors while creating and deleting of CEM circuits.
  • debug cem states : Debugs to show the state changes of CEM circuits.

Configuring Layer 3 QoS on CEoP SPAs

The SIPs and SPAs support many QoS features using modular QoS CLI (MQC) configuration. For more information about the QoS features supported by the CEoP SPAs, see the Configuring QoS Features on a SIP of Chapter5, “Configuring the SIPs and SSC”

Restrictions and Guidelines

Follow these restrictions and guidelines for the 24-Port Channelized T1/E1 ATM CEoP SPA, the 2-Port Channelised T3/E3 ATM CEoP SPA, and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA:

  • In the ingress direction, all QoS features are supported by the Cisco 7600 SIP-400.
  • The VC QoS on VP-PW feature works only with the single cell relay function and not with packed cell relay.
  • In the egress direction:

All queueing-based features such as class-based weighted fair queueing (CBWFQ), ATM per-VC weighted fair queueing (WFQ), Weighted Random Early Detection (WRED), and shaping are implemented on the SIP-400 unlike the ATM SPA.

Policing, classification, and marking are also implemented on the SIP-400.

Class based shaping is supported.

For more support information, see QoS Congestion Management and Avoidance Feature Compatibility by SIP and SPA Combination .

Supported Interface for CEoP SPA

The following interfaces are supported:

  • P2P and Multipoint permanent virtual circuit (PVC) under the main interface
  • P2P and Multipoint PVC under the sub-interface
  • P2P and Multipoint L2 PVC under the main interface – AAL5 and AAL0 (sustainable cell rate (SCR) and peak cell rate (PCR))
  • P2P and Multipoint L2PVC under the sub-interface – AAL5 and AAL0 (SCR and PCR)
  • Any transport over MPLS (AToM) Interworking
  • Inverse multiplexing (IMA)

Configuration

To configure the QoS features on the CEoP SPA, complete these steps:

SUMMARY STEPS


Step 1 enable

Step 2 configure terminal

Step 3 interface atm slot / subslot / port subinterface point-to-point

Step 4 ip address address mask

Step 5 pvc vpi/vci

Step 6 service-policy in policy-map-name

Step 7 service-policy out policy-map-name

Step 8 end

DETAILED STEPS

 

Command or Action
Purpose

Step 1

enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2

configure terminal

Enters global configuration mode.

Step 3

interface atm slot / subslot / port subinterface point-to-point

Specifies or creates a subinterface, and enters subinterface configuration mode. These are the parameters:

  • slot —Specifies the chassis slot number where the SIP is installed.
  • subslot —Specifies the secondary slot number on a SIP where a SPA is installed.
  • port —Specifies the number of the interface port on the SPA.
  • subinterface —Specifies the number of the subinterface on the interface port.
  • point-to-point —Specifies a point-to-point subinterface.

Step 4

ip address address mask [ secondary ]

(Optional) Assigns the specified IP address and subnet mask to the interface. Repeat the command with the optional secondary keyword to assign additional, secondary IP addresses to the port.

Step 5

pvc vpi/vci

Assigns a virtual path identifier (VPI) and a virtual circuit identifier (VCI).

Step 6

service-policy in policy-map-name

Attaches ingress QoS to the configuration.

Step 7

service-policy out policy-map-name

Attaches egress QoS to the configuration.

Step 8

end

Exits interface configuration mode and returns to privileged EXEC mode.

Sample Configuration

This is an example for configuring layer 3 QOS on CEoP SPAs.

Router# configure terminal
Router(config)# interface ATM3/0/0.1/1/1 point-to-point
Router(config-if)# ip address 24.0.0.1 255.255.255.0
Router(config-if)# pvc 1/40
Router(config-if-atm-vc)# service-policy in omni_flat_ingress10
Router(config-if-atm-vc)# service-policy out flat_brr10
Router(config-if-atm-vc)# end

Verifying the Configuration

This section provides the commands to verify the configuration.

Router# show run interface ATM3/0/0.1/1/1.1
interface ATM3/0/0.1/1/1.1 point-to-point
ip address 24.0.0.1 255.255.255.0
no atm enable-ilmi-trap
bfd interval 50 min_rx 100 multiplier 3
pvc 10/100
protocol ip 24.0.0.2
oam-pvc manage
service-policy in omni_flat_ingress11
service-policy out omni_flat11 !
end
 
Router# show policy-map interface ATM3/0/0.1/1/1
ATM3/0/0.1/1/1: VC 1/40 -
Service-policy input: omni_flat_ingress10
Counters last updated 00:00:03 ago
Class-map: prec4 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 4
police:
cir 52500 bps, bc 4470 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0000 bps, exceeded 0000 bps
 
Class-map: prec5 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 5
police:
cir 54000 bps, bc 4470 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0000 bps, exceeded 0000 bps
 
Class-map: prec6 (match-all)
391 packets, 29584 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 6
police:
cir 56000 bps, bc 4470 bytes
conformed 391 packets, 29584 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0000 bps, exceeded 0000 bps
 
Class-map: class-default (match-any)
255775 packets, 194214265 bytes
30 second offered rate 1325000 bps, drop rate 1275000 bps
Match: any
police:
cir 51000 bps, bc 4470 bytes
conformed 30423 packets, 7439395 bytes; actions:
transmit
exceeded 225352 packets, 186774870 bytes; actions:
drop
conformed 51000 bps, exceeded 1275000 bps
 
Service-policy output: omni_flat10
Counters last updated 00:00:03 ago
queue stats for all priority classes:
Queueing
priority level 1
queue limit 12 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 43602/7460616
 
queue stats for all priority classes:
Queueing
priority level 2
queue limit 14 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
 
Class-map: prec4 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 4
Queueing
queue limit 13 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 52 kbps
 
Class-map: prec5 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 5
Queueing
queue limit 13 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 54 kbps
 
Class-map: prec6 (match-all)
393 packets, 29724 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: precedence 6
police:
cir 56000 bps, bc 4470 bytes
conformed 393 packets, 29724 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0000 bps, exceeded 0000 bps
Priority: Strict, b/w exceed drops: 0
 
Priority Level: 2
 
Class-map: class-default (match-any)
1055920 packets, 803961420 bytes
30 second offered rate 5452000 bps, drop rate 5401000 bps
Match: any
police:
cir 51000 bps, bc 4470 bytes
conformed 43617 packets, 7433658 bytes; actions:
transmit
exceeded 1012303 packets, 796527762 bytes; actions:
drop
conformed 51000 bps, exceeded 5401000 bps
Priority: Strict, b/w exceed drops: 0
Priority Level: 1

Troubleshooting

For specific troubleshooting information, contact Cisco Technical Assistance Center (TAC) at this location:

Configuring AIS and RAI Alarm Forwarding in CESoPSN Mode on CEoP SPAs

Cisco IOS Release 12.2(33)SRD3 introduces the ability to configure on a per-T1/E1 basis the forwarding of AIS and RAI alarms towards peer CE devices via the TDM attachment circuit.

This feature allows grooming of traffic from several different cell-site fractional T1/E1s via CEM, through an MPLS cloud, onto a single aggregate T1/E1 going to the BSC.

This feature provides the following functionality:

  • By default, AIS and RAI alarms are not forwarded on T1/E1s having CESoPSN mode configured on the 1-Port Channelized OC-3 STM1 ATM CEoP SPA and 24-Port Channelized T1/E1 ATM CEoP SPA, SIP-400 line cards, even if one or all CESoPSN groups terminating on the T1/E1 are receiving AIS or RAI from the corresponding remote CESoPSN peers across the PSN.
  • AIS forwarding can be enabled on a per-T1/E1 basis on the 1-Port Channelized OC-3 STM1 ATM CEoP SPA and 24-Port Channelized T1/E1 ATM CEoP SPA. This ensures that the PE transmits AIS on the T1/E1 whenever one or more CESoPSN groups configured on it are receiving AIS notification from remote CESoPSN peers across the PSN.
  • RAI forwarding can be enabled on a per-T1/E1 basis on the 1-Port Channelized OC-3 STM1 ATM CEoP SPA and 24-Port Channelized T1/E1 ATM CEoP SPA. This ensures that the PE will transmit RAI on the T1/E1 whenever one or more CESoPSN groups configured on it are receiving RAI notification from remote CESoPSN peers across the PSN.

Configuring SONET Mode

Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SONET mode:

Command or Action
Purpose

R1(config)#controller sonet slot/bay/port

R1(config-controller)#sts-1 id

Router(config-controller-sts)#vtg identifier t1 identifier forward-alarm ais/rai

Example:

R1(config)#controller sonet 2/2/0

R1(config-controller)#sts-1 1

R1(config-ctrlr-sts1)#vtg 1 t1 1 forward-alarm ais

Enables AIS/RAI alarm forwarding on the selected interface for SONET mode.

Configuring SDH AU-4 Mode

Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SDH AU-4 Mode:

Command or Action
Purpose

R1(config-controller)#au-4 id tug-3 id

R1(config-ctrlr-tug3)#tug-2 id e1 id forward-alarm ais/rai

Example:

R1(config-controller)#au-4 1 tug-3 1

R1(config-ctrlr-tug3)#tug-2 1 e1 1 forward-alarm rai

Enables AIS/RAI alarm forwarding on the selected SDH mode for AU-4 mode.

Configuring SDH AU-3 Mode

Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for SDH AU-3 Mode:

Command or Action
Purpose

R1(config-controller)#au-3 id

R1(config-ctrlr-tug3)#tug-2 id t1 id forward-alarm ais/rai

Example:

R1(config-controller)#au-3 1

R1(config-ctrlr-au3)#tug-2 1 t1 1 forward-alarm ais

R1(config-ctrlr-au3)#tug-2 1 t1 1 forward-alarm rai

Enables AIS/RAI alarm forwarding on the selected SDH mode for AU-3 mode.

Configuring T1 Mode

Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for T1 mode:

Command or Action
Purpose

R1(config)#controller t1 slot/bay/port

R1(config-controller)#forward-alarm ais/rai

Example:

R1(config)#controller t1 2/0/0

R1(config-controller)#forward-alarm rai

Enables AIS/RAI alarm forwarding on the selected T1 controller interface for the 24-Port Channelized T1/E1 ATM CEoP SPA

Configuring E1 Mode

Use the following commands to enable AIS/RAI forwarding on the CEoP SPAs on the SIP-400 line card interface for E1 mode:

Command or Action
Purpose

R1(config)#controller e1 slot/bay/port

R1(config-controller)#forward-alarm ais/rai

Example:

R1(config)#controller e1 2/0/0

R1(config-controller)#forward-alarm ais

Enables AIS/RAI alarm forwarding on the selected E1 controller interface for the 24-Port Channelized T1/E1 ATM CEoP SPA


NoteThese commands are available only for T1s that support CEM group configuration on them.


Configuration Restrictions

The following restrictions apply while configuring AIS/alarm RAI forwarding:

  • Alarms cannot be suppressed in unframed CEM mode (SAToP). Alarms received from the remote SAToP peer across the PSN will always be propagated over the attachment circuit.
  • Forward-alarm -ais/rai- is a hidden command and is not available in the option list. You must type the full command.
  • Starting Cisco IOS Release 12.233)SRD3 changing modes of the T1 or E1 from CEoPSN to ATM or IMA is not allowed

MR-APS Integration with Hot Standby Pseudowire

The multi router automatic protection switching (MR-APS) enables interface connections to switch from one circuit to another if a circuit fails. Interfaces can be switched in response to a router failure, degradation or loss of channel signal, or manual intervention. In a multi router environment, the MR-APS allows the protected SONET interface to reside in a different router from the working SONET interface.

Service providers are migrating to ethernet networks from their existing SONET or SDH equipment to reduce cost. Any transport over MPLS (AToM) pseudowires (PWs) help service providers to maintain their investment in asynchronous transfer mode (ATM) or time division multiplexing (TDM) network and change only the core from SONET or SDH to ethernet. When the service providers move from SONET or SDH to ethernet, network availability is always a concern. Therefor to enhance the network availability, service providers use PWs.

The hot-standby PW support for ATM and TDM access circuits (ACs) allow the backup PW to be in a hot- standby state, so that it can immediately take over if the primary PW fails. The present hot-standby PW solution does not support access circuits (ACs) as part of the APS group. The PWs which are configured over the protected interface, remains in the down state. This increases the PW switchover time in case of an APS switchover. MR-APS integration with a hot standby PW is an integration of APS with ATM or TDM hot standby PWs created over the SIP 400 line card for the Cisco 7600 platform and improves the switchover time.

Figure 11-4 explains MR-APS integration with hot standby PW feature implementation.

Figure 11-4 MR-APS Integration with Hot Standby Pseudowire Implementation

In this example routers P1 and PE1 are in the same APS group G1, and routers P2 and PE2 are in the same APS group G2. In group G1, P1 is the working router and PE1 is the protected router. Similarly in group G2, P2 is the working router and PE2 is the protected router.

The MR-APS integration with hot standby PW deployment involves cell sites connected to the provider network using bundled T1/E1 connections. These T1/E1 connections are aggregated into the optical carrier 3 (OC3) or optical carrier 12 (OC12) links using the add-drop multiplexers (ADMs).

For more information on APS, see the Automatic Protection Switching section in the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide at the following link:

http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfstm1.html#wp1216498

Failover Operations

MR-APS integration with hot standby PW feature handles the following failures.

  • Failure 1, where the link between ADM and P1 goes down, or the connecting ports at ADM or P1 go down.
  • Failure 2, where the router P1 fails.
  • Failure 3, where the router P1 is isolated from the core.

Figure 11-5 explains the failure points in the network.

Figure 11-5 Failure Points in the Network

 

In case of failure 1, where either port at the ADM goes down, or the port at the router goes down or the link between ADM and router fails, the APS switchover triggers the pseudowires at the protect interface to become active. The same applies to failure 2 as well where the complete router fails over.

In case of failure 3, where all the links carrying primary and backup traffic lose the connection, a new client is added to the inter chassis redundancy manager (ICRM) infrastructure to handle the core isolation. The client listens to the events from the ICRM. Upon receiving the core isolation event from the ICRM, the client either initiates the APS switchover, or initiates the alarm based on the peer core isolation state. If APS switchover occurs, it changes the APS inactive interface to active and hence activates the PWs at the interface. Similarly, when core connectivity goes up based upon the peer core isolation state, it clears the alarms or triggers the APS switchover. ICRM monitors the directly connected interfaces only. Hence only those failures in the directly connected interfaces can cause a core isolation event.

Restrictions

Following restrictions apply to the MR-APS integration with hot standby PW feature:

  • MR-APS integration with hot standby PW is supported only on the SIP 400 line cards.
  • For ATM pseudowires only ATM asynchronous mode is supported.
  • Revertive APS mode should not be configured on the interfaces.
  • MR-APS integration with hot standby PW is supported only on 1-port channelized OC-3 STM1 ATM CEoP SPA and 2-port and 4-port OC-3c/STM-1 ATM SPA.
  • APS group number should be greater than zero.
  • Do not configure the backup delay value command if the MR-APS integration with hot standby PW feature is configured.
  • Unconfiguring mpls ip command on the core interface is not supported.
  • The hspw force switch command is not supported.

Configuring MR-APS Integration with Hot Standby Pseudowire

MR-APS integration with hot standby PW can be configured on a CEM interface or IMA interface on the 1-port channelized OC-3 STM1 ATM CEoP SPA. Perform the steps in the corresponding section to configure the MR-APS integration with hot standby PW feature on a CEM or IMA interface.

Configuring MR-APS Integration with Hot Standby Pseudowire on a CEM Interface

Complete these steps to configure MR-APS integration with hot standby PW on a CEM interface. The configuration involves configuring the working routers and protect routers that are part of the APS group.

SUMMARY STEPS

1. enable

2. configure terminal

3. pseudowire-class pw-class-name

4. encapsulation mpls

5. status peer topology dual-homed

6. exit

7. redundancy

8. interchassis group group-id pw-class-name

9. member ip ip-address

10. backbone interface interface

11. backbone interface interface

12. exit

13. controller sonet slot/bay/port

14. framing [sonet|sdh]

15. clock source line

16. sts-1 sts1-number

17. mode vt-15

18. vtg vtg_number t1 t1_line_number cem-group channel-number timeslots list-of-timeslots

19. exit

20. aps group group_id

21. aps [ working | protect ] aps-group-number [ ip-address ]

22. aps hspw-icrm-group icrm-group-number

23. exit

24. interface cem slot/subslot/port

25. cem cem-group

26. xconnect peer-ip-address vc-id pw-class pw-class-name

27. backup peer ip-address vc-id pw-class pw-class-name

28. end

Detailed Steps

Command
Purpose

Step 1

enable

 
Router> enable

Enables the privileged EXEC mode. If prompted, enter your password.

Step 2

configure terminal

 

Router# configure terminal

Enters the global configuration mode.

Step 3

pseudowire-class pw-class-name

 

 

Router(config)# pseudowire-class hw_aps

Specifies the name of a PW class and enters PW class configuration mode.

Step 4

encapsulation mpls

 

 

Router(config-pw-class)# encapsulation mpls

Specifies that MPLS is used as the data encapsulation method for tunneling Layer 2 traffic over the pseudowire.

Step 5

status peer topology dual-homed

 

 

Router(config-pw-class)# status peer topology dual-homed

Enables the reflection of the attachment circuit status on both the primary and secondary pseudowires. This configuration is necessary if the peer PEs are connected to a dual-homed device.

Step 6

exit

 

Router(config-pw-class)# exit

Exits PW class configuration mode.

Step 7

redundancy

 

Router(config)# redundancy

Enters the redundancy configuration mode.

Step 8

interchassis group group-id

 

Router(config-red)# interchassis group 50

Configures an interchassis group within the redundancy configuration mode and enters the interchassis redundancy mode.

Step 9

member ip ip-address

 

 

Router(config-r-ic)# member ip 60.60.60.2

Configures the IP address of the peer member group.

Step 10

backbone interface interface

 

Router(config-r-ic)# backbone interface GigabitEthernet 2/3

Specifies the backbone interface.

Step 11

exit

 

Router(config-r-ic)# exit

 

Exits the redundancy mode.

Step 12

controller SONET slot/bay/port

 

Router(config)# controller SONET 1/1/0

Selects and configures a SONET controller and enters controller configuration mode.

slot/subslot/port —Specifies the location of the interface.

Step 13

framing [SDH|SONET]

 

Router(config-controller)# framing SONET

Configures the controller with framing type. SONET framing is the default option.

Step 14

clock source line

 

Router(config-controller)# clock source line

Sets the clocking for individual T1 or E1 links.

Step 15

sts-1 sts1-number

 

Router(config-controller)# sts-1 1

Specifies the STS identifier.

Step 16

mode vt-15

 

Router(config-ctrlr-sts1)# mode vt-15

Specifies the STS-1 mode of operation.

Step 17

vtg vtg_number t1 t1_line_number cem-group channel-number timeslots list-of-timesolts

 

Router(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 0 timeslots 1-24

Creates a Circuit Emulation Services over Packet Switched Network circuit emulation (CESoPSN) CEM group.

Step 18

exit

 

Working-Router(config-ctrlr-sts1)# exit

 

Exits from the STS configuration mode.

Step 19

aps group group_id

 

 

Router(config-controller)# aps group 1

Configures the APS group for CEM

Step 20

aps [working | protect] aps-group-number

 

Router(config-controller)# aps working 1

Configures the APS group as working or protect interface.

Step 21

aps hspw-icrm-grp group-number

 

 

Router(config-controller)# aps hspw-icrm-group 1

 

Associates the APS group to an ICRM group number.

Step 22

exit

 

Router(config-ctrlr)# end

Ends the controller session and returns to the configuration mode.

Step 23

interface cem slot/subslot/port

 

Router(config-if)# interface cem 1/1/0

Configures a serial interface and enter the interface configuration mode.

Step 24

cem group-number

 

Router(config-if)# cem 0

Selects the CEM circuit (group) to configure a PW for.

Step 25

xconnect peer-ip-address vcid pw-class pw-class-name

 

 

 

Router(config-if-srv)# xconnect 3.3.3.3 1 pw-class hspw_aps

Specifies the IP address of the peer PE router and the 32-bit virtual circuit identifier shared between the PEs at each end of the control channel.

pw-class-name —The PW class configuration from which the data encapsulation type is taken.

Note The peer router IP address and virtual circuit ID must be a unique combination on the router.

Step 26

backup peer peer-id vc-id pseudowire-class pw-classname

 

Router(config-if-srv)# backup peer 4.3.3.3 90 pseudowire-class vpws

 

Specifies a redundant peer for a PW virtual circuit.

Step 27

end

 

Router(config-controller)#end

Ends the configuration session and returns to the EXEC mode.

Example

This example shows how to configure the MR-APS integration with hot standby PW on a CEM interface on the working router with framing mode as SONET on router P1.

RouterP1> enable
RouterP1# configure terminal
RouterP1(config)# pseudowire-class hspw_aps
RouterP1(config-pw-class)# encapsulation mpls
RouterP1(config-pw-class)# status peer topology dual-homed
RouterP1(config-pw-class)# exit
RouterP1(config)# redundancy
RouterP1(config-red)# interchassis group 1
RouterP1(config-r-ic)# member ip 14.2.0.2
RouterP1(config-r-ic)# backbone interface GigabitEthernet 1/0/0
RouterP1(config-r-ic)# backbone interface GigabitEthernet 1/0/1
RouterP1(config-r-ic)# exit
RouterP1(config)# controller SONET 1/1/0
RouterP1(config-controller)# framing sonet
RouterP1(config-controller)# clock source line
RouterP1(config-controller)# sts-1 1
RouterP1(config-ctrlr-sts1)# mode vt-15
RouterP1(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 0 timeslots 1-24
RouterP1(config-ctrlr-sts1)# exit
RouterP1(config-controller)# aps group 3
RouterP1(config-controller)# aps working 1
RouterP1(config-controller)# aps hspw-icrm-grp 1
RouterP1(config-controller)# exit
RouterP1(config)# interface cem 1/1/0
RouterP1(config-if)# cem 0
RouterP1(config-if)# xconnect 3.3.3.3 1 encapsulation mpls pw-class hspw_aps
RouterP1(config-if)# backup peer 4.4.4.4 2 pw-class hspw_aps
RouterP1(config-if)# exit
RouterP1(config)# end
 

This example shows how to configure the MR-APS integration with hot standby PW on a CEM interface on the protect router with framing mode as SONET on router PE1.

RouterPE1> enable
RouterPE1# configure terminal
RouterPE1(config)# pseudowire-class hspw_aps
RouterPE1(config-pw-class)# encapsulation mpls
RouterPE1(config-pw-class)# status peer topology dual-homed
RouterPE1(config-pw-class)# exit
RouterPE1(config)# redundancy
RouterPE1(config-red)# interchassis group 1
RouterPE1(config-r-ic)# member ip 14.2.0.1
RouterPE1(config-r-ic)# backbone interface GigabitEthernet 1/0/0
RouterPE1(config-r-ic)# backbone interface GigabitEthern
RouterPE1(config-r-ic)# exit
RouterPE1(config)# controller SONET 3/0/0
RouterPE1(config-controller)# framing sonet
RouterPE1(config-controller)# clock source line
RouterPE1(config-controller)# sts-1 1
RouterPE1(config-ctrlr-sts1)# mode vt-15
RouterPE1(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 0 timeslots 1-24
RouterPE1(config-ctrlr-sts1)# exit
RouterPE1(config-controller)# aps group 3
RouterPE1(config-controller)# aps protect 1 14.2.0.2
RouterPE1(config-controller)# aps hspw-icrm-grp 1
RouterPE1(config-controller)# exit
RouterPE1(config)# interface cem 3/0/0
RouterPE1(config-if)# cem 0
RouterPE1(config-if)# xconnect 3.3.3.3 3 pw-class hspw_aps
RouterPE1(config-if)# backup peer 4.4.4.4 4 pw-class hspw_aps
RouterPE1(config-if)# exit
RouterPE1(config)# end

 

This example shows how to configure the MR-APS integration with hot standby PW on a CEM interface on the working router with framing mode as SONET on router P2.

RouterP2> enable
RouterP2# configure terminal
RouterP2(config)# pseudowire-class hspw_aps
RouterP2(config-pw-class)# encapsulation mpls
RouterP2(config-pw-class)# status peer topology dual-homed
RouterP2(config-pw-class)# exit
RouterP2(config)# redundancy
RouterP2(config-red)# interchassis group 1
RouterP2(config-r-ic)# member ip 14.6.0.2
RouterP2(config-r-ic)# backbone interface GigabitEthernet 2/0/3
RouterP2(config-r-ic)# backbone interface GigabitEthernet 2/0/4
RouterP2(config-r-ic)# exit
RouterP2(config)# controller SONET 1/1/0
RouterP2(config-controller)# framing sonet
RouterP2(config-controller)# clock source line
RouterP2(config-controller)# sts-1 1
RouterP2(config-ctrlr-sts1)# mode vt-15
RouterP2(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 0 timeslots 1-24
RouterP2(config-ctrlr-sts1)# exit
RouterP2(config-controller)# aps group 3
RouterP2(config-controller)# aps working 1
RouterP2(config-controller)# aps hspw-icrm-grp 1
RouterP2(config-controller)# exit
RouterP2(config)# interface cem 1/1/0
RouterP2(config-if)# cem 0
RouterP2(config-if)# xconnect 1.1.1.1 1 encapsulation mpls pw-class hspw_aps
RouterP2(config-if)# backup peer 2.2.2.2 3 pw-class hspw_aps
RouterP2(config-if)# exit
RouterP2(config)# end

 

This exampleshows how to configure the MR-APS Integration with hot standby PW on a CEM interface on the protect router PE2 with framing mode as SONET.

RouterPE2> enable
RouterPE2# configure terminal
RouterPE2(config)# pseudowire-class hspw_aps
RouterPE2(config-pw-class)# encapsulation mpls
RouterPE2(config-pw-class)# status peer topology dual-homed
RouterPE2(config-pw-class)# exit
RouterPE2(config)# redundancy
RouterPE2(config-red)# interchassis group 1
RouterPE2(config-r-ic)# member ip 14.6.0.1
RouterPE2(config-r-ic)# backbone interface GigabitEthernet 1/0/0
RouterPE2(config-r-ic)# backbone interface GigabitEthern
RouterPE2(config-r-ic)# exit
RouterPE2(config)# controller SONET 3/2/0
RouterPE2(config-controller)# framing sonet
RouterPE2(config-controller)# clock source line
RouterPE2(config-controller)# sts-1 1
RouterPE2(config-ctrlr-sts1)# mode vt-15
RouterPE2(config-ctrlr-sts1)# vtg 1 t1 1 cem-group 0 timeslots 1-24
RouterPE2(config-ctrlr-sts1)# exit
RouterPE2(config-controller)# aps group 2
RouterPE2(config-controller)# aps protect 1 14.6.0.2
RouterPE2(config-controller)# aps hspw-icrm-grp 1
RouterPE2(config-controller)# exit
RouterPE2(config)# interface cem 3/2/0
RouterPE2(config-if)# cem 0
RouterPE2(config-if)# xconnect 1.1.1.1 2 pw-class hspw_aps
RouterPE2(config-if)# backup peer 2.2.2.2 4 pw-class hspw_aps
RouterPE2(config-if)# exit
RouterPE2(config)# end
 

Configuring MR-APS Integration with Hot Standby Pseudowire on an IMA interface

Perform these steps to configure MR-APS integration with hot standby PW on an IMA interface. The configuration includes configuring the working routers and protect routers that are part of the APS group.

SUMMARY STEPS

1. enable

2. configure terminal

3. pseudowire-class pw-class-name

4. encapsulation mpls

5. status peer topology dual-homed

6. exit

7. redundancy

8. interchassis group group-id pw-class-name

9. member ip ip-address

10. backbone interface interface slot/bay/port

11. backbone interface interface slot/bay/port

12. exit

13. controller sonet slot/bay/port

14. framing sonet | sdh

15. clock source line

16. sts-1 sts1-number

17. mode vt-15

18. vtg vtg_number t1 t1_line_number ima-group group-number

19. exit

20. aps group group_id

21. aps [ working | protect ] aps-group-number [ ip-address ]

22. aps hspw-icrm -grp group-number

23. interface atm slot / subslot / ima group-id

24. atm asynchronous

25. pvc vpi/vci l2transport

26. xconnect peer-ip-address vc-id pw-class pw-class-name

27. backup peer ip-address vc-id pw-class pw-class-name

28. end

Detailed Steps

Command
Purpose

Step 1

enable

 
Router> enable

Enables the privileged EXEC mode. If prompted, enter your password.

Step 2

configure terminal

 

Router# configure terminal

Enters the global configuration mode.

Step 3

pseudowire-class pw-class-name

 

 

Router(config)# pseudowire-class hw_aps

Specifies the name of a PW class and enters PW class configuration mode.

Step 4

encapsulation mpls

 

 

Router(config-pw-class)# encapsulation mpls

Specifies that MPLS is used as the data encapsulation method for tunneling layer 2 traffic over the pseudowire.

Step 5

status peer topology dual-homed

 

 

Router(config-pw-class)# status peer topology dual-homed

Enables the reflection of the attachment circuit status on both the primary and secondary pseudowires. This configuration is necessary if the peer PEs are connected to a dual-homed device.

Step 6

exit

 

Router(config-pw-class)# exit

Exits PW class configuration mode.

Step 7

redundancy

 

Router(config)# redundancy

Enters the redundancy configuration mode.

Step 8

interchassis group group-id

 

Router(config-red)# interchassis group 50

Configures an interchassis group within the redundancy configuration mode and enters the interchassis redundancy mode.

Step 9

member ip ip-address

 

 

Router(config-r-ic)# member ip 60.60.60.2

Configures the IP address of peer member.

Step 10

backbone interface interface

 

Router(config-r-ic)# backbone interface GigabitEthernet 2/3

Specifies the backbone interface.

Step 11

exit

 

Router(config-r-ic)# exit

 

Exits the redundancy mode.

Step 12

controller sonet slot/subslot/port

 

Router(config)# controller sonet 1/1/0

Selects and configures a SONET controller and enters controller configuration mode.

slot/subslot/port—Specifies the location of the interface.

Step 13

framing [sonet|sdh]

 

Router(config-controller)# framing sonet

Configures the controller for SONET framing. SONET framing is the default option.

Step 14

clock source line

 

Router(config-controller)# clock source line

Sets the clocking for individual T1 or E1 links.

Step 15

sts-1 sts1-number

 

Router(config-controller)# sts-1 1

Specifies the STS identifier.

Step 16

mode vt-15

 

Router(config-ctrlr-sts1)# mode vt-15

Specifies the STS-1 mode of operation.

Step 17

vtg vtg_number t1 t1_line_number ima-group ima-group-number

 

Router(config-ctrlr-sts1)# vtg 1 t1 1 ima-group 0

Configures the interface to run in IMA mode and assigns the interface to an IMA group.

Step 18

exit

 

Router(config-ctrlr-sts1)# exit

 

Exits from the interface configuration mode.

Step 19

aps group group_id

 

 

Router(config-controller)#aps group 1

Configures the APS group for IMA interface.

Step 20

aps [working | protect] aps-group-number

 

Router(config-controller)# aps working 1

Configures the APS group as working or protect interface.

Step 21

aps hspw-icrm-grp group-number

 

 

Router(config-controller)# aps hspw-icrm-grp 1

 

Associates the APS group to an hot standby PW ICRM group number.

Step 22

exit

 

Router(config-ctrlr)#end

Ends the controller session and returns to the configuration mode.

Step 23

interface atm slot/subslot/ ima group-number

 

Router(config-if)# interface atm 1/1/ima0

Specifies the IMA interface and enters interface configuration mode.

Step 24

no ip address

 

Router(config-if)# no ip address

 

Removes the configured IP address from the interface.

Step 25

atm asynchronous
 

Router(config-if)# atm asynchronous

This command enables or disables the asynchronous functionality on the ATM interface.

Step 26

pvc vpi/vci l2transport

 

Router(config-if)# pvc 1/100 l2transport

Assigns a VPI and VCI and enters PVC l2transport configuration mode.

  • vpi —ATM network virtual path identifier (VPI) of the VC to multiplex on the permanent virtual path. The range is from 0 to 255.
  • vci — VCI specifies the virtual channel identifier.

Note The l2transport keyword indicates that the PVC is a switched PVC instead of a terminated PVC.

Step 27

xconnect peer-ip-address vcid pw-class pw-class-name

 

 

Router(config-if-srv)# xconnect 3.3.3.3 1 pw-class hspw_aps

 

Specifies the IP address of the peer PE router and the 32-bit virtual circuit identifier shared between the PEs at each end of the control channel.

pw-class-name —The PW class configuration from which the data encapsulation type is taken.

Note The peer router ID (IP address) and virtual circuit ID must be a unique combination on the router.

Step 28

backup peer peer-id vc-id pseudowire-class pw-classname

 

Router(config-if-srv)# backup peer 4.3.3.3 90 pseudowire-class vpws

 

Specifies a redundant peer for a PW virtual circuit.

Step 29

end

 

Working-Router(config-controller)# end

Ends the configuration session and returns to the EXEC mode.

Example

This example shows how to configure the MR-APS integration with hot standby PW on an IMA interface on the working router P1.

RouterP1> enable
RouterP1# configure terminal
RouterP1(config)# pseudowire-class hspw_aps
RouterP1(config-pw-class)# encapsulation mpls
RouterP1(config-pw-class)# status peer topology dual-homed
RouterP1(config-pw-class)# exit
RouterP1(config)# redundancy
RouterP1(config-red)# interchassis group 1
RouterP1(config-r-ic)# member ip 14.2.0.2
RouterP1(config-r-ic)# backbone interface GigabitEthernet 1/0/0
RouterP1(config-r-ic)# backbone interface GigabitEthernet 1/0/1
RouterP1(config-r-ic)# exit
RouterP1(config)# controller sonet 1/1/0
RouterP1(config-controller)# framing sonet
RouterP1(config-controller)# clock source line
RouterP1(config-controller)# sts-1 1
RouterP1(config-ctrlr-sts1)# mode vt-15
RouterP1(config-ctrlr-sts1)# vtg 1 t1 1 ima-group 0
RouterP1(config-ctrlr-sts1)# exit
RouterP1(config-controller)# aps group 3
RouterP1(config-controller)# aps working 1
RouterP1(config-controller)# aps hspw-icrm-grp 1
RouterP1(config-controller)# exit
RouterP1(config)# interface atm 1/1/ima0
RouterP1(config-if)# atm asynchronous
RouterP1(config-if)# pvc 1/100 l2transport
RouterP1(config-if)# xconnect 3.3.3.3 1 encapsulation mpls pw-class hspw_aps
RouterP1(config-if)# backup peer 4.4.4.4 2 pw-class hspw_aps
RouterP1(config-if)# exit
RouterP1(config)# end
 

This example shows how to configure the MR-APS integration with hot standby PW on an IMA interface on the protect router PE1.

RouterPE1> enable
RouterPE1# configure terminal
RouterPE1(config)# pseudowire-class hspw_aps
RouterPE1(config-pw-class)# encapsulation mpls
RouterPE1(config-pw-class)# status peer topology dual-homed
RouterPE1(config-pw-class)# exit
RouterPE1(config)# redundancy
RouterPE1(config-red)# interchassis group 1
RouterPE1(config-r-ic)# member ip 14.2.0.2
RouterPE1(config-r-ic)# backbone interface GigabitEthernet 1/0/0
RouterPE1(config-r-ic)# backbone interface GigabitEthernet 1/0/1
RouterPE1(config)# controller sonet 1/1/0
RouterPE1(config-controller)# framing sonet
RouterPE1(config-controller)# clock source line
RouterPE1(config-controller)# sts-1 1
RouterPE1(config-ctrlr-sts1)# mode vt-15
RouterPE1(config-ctrlr-sts1)# vtg 1 t1 1 ima-group 0
RouterPE1(config-ctrlr-sts1)# exit
RouterPE1(config-controller)# aps group 3
RouterPE1(config-controller)# aps protect 1 14.2.0.1
RouterPE1(config-controller)# aps hspw-icrm-grp 1
RouterPE1(config-controller)# exit
RouterPE1(config)# interface atm 1/1/ima0
RouterPE1(config-if)# atm asynchronous
RouterPE1(config-if)# pvc 1/100 l2transport
RouterPE1(config-if)# xconnect 3.3.3.3 1 encapsulation mpls pw-class hspw_aps
RouterPE1(config-if)# backup peer 4.4.4.4 2 pw-class hspw_aps

RouterPE1(config-if)# exit

RouterPE1(config)# end

This example shows how to configure the MR-APS integration with hot standby PW on an IMA interface on the working router P2.
 
RouterP2> enable
RouterP2# configure terminal
RouterP2(config)# pseudowire-class hspw_aps
RouterP2(config-pw-class)# encapsulation mpls
RouterP2(config-pw-class)# status peer topology dual-homed
RouterP2(config-pw-class)# exit
RouterP2(config)# redundancy
RouterP2(config-red)# interchassis group 1
RouterP2(config-r-ic)# member ip 14.6.0.2
RouterP2(config-r-ic)# backbone interface GigabitEthernet 2/0/3
RouterP2(config-r-ic)# backbone interface GigabitEthernet 2/0/4
RouterP2(config-r-ic)# exit
RouterP2(config)# controller sonet 1/1/0
RouterP2(config-controller)# framing sonet
RouterP2(config-controller)# clock source line
RouterP2(config-controller)# sts-1 1
RouterP2(config-ctrlr-sts1)# mode vt-15
RouterP2(config-ctrlr-sts1)# vtg 1 t1 1 ima-group 0
RouterP2(config-ctrlr-sts1)# exit
RouterP2(config-controller)# aps group 2
RouterP2(config-controller)# aps working 1
RouterP2(config-controller)# aps hspw-icrm-grp 1
RouterP2(config-controller)# exit
RouterP2(config)# interface atm 1/1/ima0
RouterP2(config-if)# atm asynchronous
RouterP2(config-if)# pvc 1/100 l2transport
RouterP2(config-if)# xconnect 1.1.1.1 1 encapsulation mpls pw-class hspw_aps
RouterP2(config-if)# backup peer 2.2.2.2 3 pw-class hspw_aps
RouterP2(config-if)# exit
RouterP2(config)# end
 
This example shows how to configure the MR-APS integration with hot standby PW on an IMA interface on the working router PE2.
 
RouterPE2> enable
RouterPE2# configure terminal
RouterPE2(config)# pseudowire-class hspw_aps
RouterPE2(config-pw-class)# encapsulation mpls
RouterPE2(config-pw-class)# status peer topology dual-homed
RouterPE2(config-pw-class)# exit
RouterPE2(config)# redundancy
RouterPE2(config-red)# interchassis group 1
RouterPE2(config-r-ic)# member ip 14.6.0.1
RouterPE2(config-r-ic)# backbone interface GigabitEthernet 3/0/1
RouterPE2(config-r-ic)# backbone interface GigabitEthernet 3/0/2
RouterPE2(config-r-ic)# exit
RouterPE2(config)# controller sonet 1/1/0
RouterPE2(config-controller)# framing sonet
RouterPE2(config-controller)# clock source line
RouterPE2(config-controller)# sts-1 1
RouterPE2(config-ctrlr-sts1)# mode vt-15
RouterPE2(config-ctrlr-sts1)# vtg 1 t1 1 ima-group 0
RouterPE2(config-ctrlr-sts1)# exit
RouterPE2(config-controller)# aps group 3
RouterPE2(config-controller)# aps protect 1 14.6.0.2
RouterPE2(config-controller)# aps hspw-icrm-grp 1
RouterPE2(config-controller)# exit
RouterPE2(config)# interface atm 3/2/ima0
RouterPE2(config-if)# atm asynchronous
RouterPE2(config-if)# pvc 1/100 l2transport
RouterPE2(config-if)# xconnect 1.1.1 1 2 encapsulation mpls pw-class hspw_aps
RouterPE2(config-if)# backup peer 2.2.2.2 4 pw-class hspw_aps
RouterPE2(config-if)# exit
RouterPE2(config)# end

 

Verification

Use these commands to verify the MR-APS integration with hot standby PW configuration.

Table 11-3 Verification

Command
Purpose

show mpls l2transport vc

Displays information about Any Transport over MPLS (AToM) virtual circuits (VCs) that have been enabled to route layer 2 packets on a router.

show hspw-aps-icrm group group-id

Displays information about a specified hot standby PW APS group.

show hspw-aps-icrm all

Displays information about all hot standby PW APS and ICRM groups.

show redundancy interchassis

Displays information about interchassis redundancy group configuration.

show xconnect all

Displays information about all xconnect attachment circuits and pseudowires.

Troubleshooting Tips

Table 11-4 Troubleshooting Tips

Command
Purpose

debug hspw-aps errors

Displays information about hot standby PW APS group errors.

debug hspw-aps events

Displays information about events related to hot standby PW APS group configuration.

 

Verifying the Interface Configuration

The show cem circuit command shows information about the circuit state, administrative state, the CEM ID of the circuit, and the interface on which it is configured. If xconnect is configured under the circuit, the command output also includes information about the attached circuit.

Router# show cem circuit ?
<0-504> CEM ID
detail Detailed information of cem ckt(s)
interface CEM Interface
summary Display summary of CEM ckts
| Output modifiers
 
 
Router# show cem circuit
CEM Int. ID Line Admin Circuit AC
--------------------------------------------------------------
CEM1/1/0 1 UP UP ACTIVE --/--
CEM1/1/0 2 UP UP ACTIVE --/--
CEM1/1/0 3 UP UP ACTIVE --/--
CEM1/1/0 4 UP UP ACTIVE --/--
CEM1/1/0 5 UP UP ACTIVE --/--
 
 

The show cem circuit 0-504 command displays the detailed information about that particular circuit.

Router# show cem circuit 1
CEM1/1/0, ID: 1, Line State: UP, Admin State: UP, Ckt State: ACTIVE
Idle Pattern: 0xFF, Idle cas: 0x8, Dummy Pattern: 0xFF
Dejitter: 5, Payload Size: 40
Framing: Framed, (DS0 channels: 1-5)
Channel speed: 56
CEM Defects Set
Excessive Pkt Loss RatePacket Loss
 
Signalling: No CAS
RTP: No RTP
Ingress Pkts: 25929 Dropped: 0
Egress Pkts: 0 Dropped: 0
CEM Counter Details
Input Errors: 0 Output Errors: 0
Pkts Missing: 25927 Pkts Reordered: 0
Misorder Drops: 0 JitterBuf Underrun: 1
Error Sec: 26 Severly Errored Sec: 26
Unavailable Sec: 5 Failure Counts: 1
Pkts Malformed: 0
 
 

The show cem circuit summary command displays the number of circuits which are up or down per interface basis.

Router# show cem circuit summary
CEM Int. Total Active Inactive
--------------------------------------
CEM1/1/0 5 5 0
 
 

The show running module command shows detail on each CEM group:

Router# show running module 1
Building configuration...
 
Current configuration : 1542 bytes
card type t1 1 1
!
Controller T1 1/1/0
framing esf
linecode b8zs
cem-group 1 timeslots 1-5 speed 56
cem-group 2 timeslots 6-10 speed 56
cem-group 3 timeslots 11-15 speed 56
cem-group 4 timeslots 16-20 speed 56
cem-group 5 timeslots 21-24 speed 56
!
Controller T1 1/1/1
framing esf
linecode b8zs
!
Controller T1 1/1/2
framing esf
linecode b8zs
!
Controller T1 1/1/3
framing esf
!
Controller T1 1/1/4
framing esf
linecode b8zs
!
Controller T1 1/1/5
framing esf
fdl both
linecode b8zs
!
Controller T1 1/1/6
framing esf
linecode b8zs
!
Controller T1 1/1/7
framing esf
linecode b8zs
!
Controller T1 1/1/8
framing esf
linecode b8zs
!
Controller T1 1/1/9
framing esf
clock source internal
linecode b8zs
!
Controller T1 1/1/10
framing esf
linecode b8zs
!
Controller T1 1/1/11
framing esf
linecode b8zs
!
Controller T1 1/1/12
framing esf
linecode b8zs
!
Controller T1 1/1/13
framing esf
linecode b8zs
!
Controller T1 1/1/14
framing esf
linecode b8zs
!
Controller T1 1/1/15
framing esf
linecode b8zs
!
Controller T1 1/1/16
framing esf
linecode b8zs
!
Controller T1 1/1/17
framing esf
linecode b8zs
!
Controller T1 1/1/18
framing esf
linecode b8zs
!
Controller T1 1/1/19
framing esf
linecode b8zs
!
Controller T1 1/1/20
framing esf
linecode b8zs
!
Controller T1 1/1/21
framing esf
linecode b8zs
!
Controller T1 1/1/22
framing esf
linecode b8zs
!
Controller T1 1/1/23
framing esf
linecode b8zs
!
interface CEM1/1/0
no ip address
cem 1
!
cem 2
!
cem 3
!
cem 4
!
cem 5
!
end
 
Router# show int cem 2/1/3
CEM2/1/3 is up, line protocol is up
Hardware is Circuit Emulation Interface
MTU 1500 bytes, BW 10000000 Kbit, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation CEM, loopback not set
Keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
 
Router# show class cem class1
Class: class1
Idle Pattern: 0x9, Idle cas: 0xF
Dejitter: 5, Payload Size: 100
RTP: No RTP
 
Router# show class cem all
Class: abcdefghijklmn
Idle Pattern: 0xF, Idle cas: 0x8
Dejitter: 200, Payload Size: 200
RTP: Configured, RTP-HDR Compression: Disabled
 
Class: class1
Idle Pattern: 0x9, Idle cas: 0xF
Dejitter: 5, Payload Size: 100
RTP: No RTP
 
Class: 1234
Idle Pattern: 0xF, Idle cas: 0x8
Dejitter: 5, Payload Size: 32
RTP: No RTP
Router# show class cem detail
Class: abcdefghijklmn
Idle Pattern: 0xF, Idle cas: 0x8
Dejitter: 200, Payload Size: 200
RTP: Configured, RTP-HDR Compression: Disabled
 
Circuits inheriting this Class:
None
 
Interfaces inheriting this Class:
None
 
Class: class1
Idle Pattern: 0x9, Idle cas: 0xF
Dejitter: 5, Payload Size: 100
RTP: No RTP
 
Circuits inheriting this Class:
None
 
Interfaces inheriting this Class:
None
 
Class: 1234
Idle Pattern: 0xF, Idle cas: 0x8
Dejitter: 5, Payload Size: 32
RTP: No RTP
 
Circuits inheriting this Class:
None
 
Router# show class cem class1
Class: class1
Idle Pattern: 0x9, Idle cas: 0xF
Dejitter: 5, Payload Size: 100
RTP: No RTP
 

Configuring Cell Payload Scrambling on CEoP SPAs

Cell payload scrambling is a technique using an ATM switch to maintain framing on some medium-speed edge and trunk interfaces. Scrambling is designed to randomize the pattern of 1s and 0s carried in ATM cells or in the physical layer frame. Randomizing the digital bits can prevent continuous, non-variable bit patterns like long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking. This section provides information on how to configure cell payload scrambling on CEoP SPAs for the Cisco 7600 router.

For T3/T1modes the default behavior is cell-payload scrambling off while for E3/E1 modes the default behavior is cell-payload scrambling on.

Examples

This example configures cell payload scrambling on T3 mode for 2-Port channelized T3/E3 ATM CEoP SPA.

Router(config)# controller t3 1/0/0
Router(config-controller)# atm
Router(config-controller)# scrambling cell-payload

Router(config-controller)# exit

This example configures cell payload scrambling on T3/T1 mode for 2-Port channelized T3/E3 ATM CEoP SPA.

Router(config)# controller t3 1/0/0
Router(config-controller)# t1 1 atm
Router(config-controller)# t1 1 scrambling cell-payload

Router(config-controller)# exit

This example configures cell payload scrambling on E3 mode for 2-Port Channelized T3/E3 ATM CEoP SPA.

Router(config)# controller e3
Router(config-controller)# atm
Router(config-controller)# no scrambling cell-payload

Router(config-controller)# exit

This example configures cell payload scrambling on T1 mode for 24-Port Channelized T1/E1 ATM CEoP SPA.

Router(config)# controller t1
Router(config-controller)# atm
Router(config-controller)# scrambling cell-payload

Router(config-controller)# exit

This example configures scrambling cell payload on E1 mode 24-Port Channelized T1/E1 ATM CEoP SPA.

Router(config)# controller e1
Router(config-controller)# atm
Router(config-controller)# no scrambling cell-payload
Router(config-controller)# exit

 

This example configures cell payload scrambling on STS mode for OC-3 STM1 ATM CEoP SPA.

Router(config)# controller sonet 1/1/0
Router(config-controller)# framing sonet
Router(config-controller)# clock source line
Router(config-controller)# sts-1 1
Router(config-ctrlr-sts1)# mode vt-15
Router(config-ctrlr-sts1)# vtg 1 t1 1 atm
Router(config-ctrlr-sts1)# vtg 1 t1 1 scrambling cell-payload
Router(config-ctrlr-sts1)# exit
 

This example configures cell payload scrambling on SDH-AUG mapping au-4 and tug mode E1 for OC-3 STM1 ATM CEoP SPA.

Router(config)# controller sonet 1/1/0
Router(config-controller)# framing sdh
Router(config-controller)# aug mapping au-4
Router(config-controller)# au-4 1 tug 1
Router(config-ctrlr-tug1)# tug 1 e1 1 atm
Router(config-ctrlr-tug1)# no tug 1 e1 1 scrambling cell-payload
Router(config-ctrlr-tug1)# exit
 
This example configures cell payload scrambling with SDH-AUG mapping au-4 and tug mode T1 for OC-3 STM1 ATM CEoP SPA.
 
Router(config)# controller sonet 1/1/0
Router(config-controller)# framing sdh
Router(config-controller)# aug mapping au-3
Router(config-controller)# au-3 1 tug 1
Router(config-ctrlr-tug1)# tug 1 t1 1 atm
Router(config-ctrlr-tug1)# tug 1 t1 1 scrambling cell-payload
Router(config-ctrlr-tug1)# exit