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 must 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 ASR 1000 Series Router in which the SIP is installed
• subslot —Specifies the secondary slot of the SIP in which 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 that is installed in subslot 1 of the SIP in chassis slot 0:

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

The SPA-1CHOC3-CE-ATM can be configured to run only in the CEM mode. The 2-Port Channelized T3/E3 ATM CEoP SPA, introduced in Cisco IOS XE Release 3.4.0S, can be configured to run only in the ATM mode. Effective from Cisco IOS XE Release 3.6.0S, the 2-Port Channelized T3/E3 ATM CEoP SPA supports the CEM mode, but does not support the IMA mode. Effective from Cisco IOS XE Release 3.10.0S, The 24-port channelized T1E1 SPA supported ATM mode on the SPA-24CHT1-CE-ATM.

The following sections show how to configure each of the SPAs for the CEM mode.

From Cisco IOS XE Release 3.4S, ATM support for the SPA-2CHT3-CE-ATM is introduced. When configured to operate in the ATM mode, CEoP SPAs support the ATM features.

The SPA-2CHT3-CE-ATM CEoP supports ATM operation only in the clear-channel mode. In this mode, each SPA port provides a single high-speed ATM connection operating at the line rate of the port.

In Cisco IOS XE Release 3.10S, ATM support for the SPA-24CHT1-CE-ATM is introduced. When configured to operate in the ATM mode, CEoP SPAs support the ATM feature.

The SPA-24CHT1-CE-ATM CEoP is supported only in the clear-channel mode. In the clear-channel mode, each SPA port provides a single high-speed ATM connection operating at the line rate of the port.

To configure a pseudowire for an ATM connection, perform the procedure described in the following sections. The pseudowire carries ATM data across the MPLS network.

1.    Router(config)# controller t3 slot/subslot/port

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

3.    Router(config-controller)# cablelength feet

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

5.    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]

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

7.    Router(config-controller)# exit

To configure a SPA port for the E3 mode, perform the following steps:

Note	The E3 mode is not supported in Cisco IOS XE Release 3.4.0S. Effective from Cisco IOS XE Release 3.5.0S, support for ATM on the clear-channel E3 mode has been introduced. Mixed configuration of both the T3 mode and the E3 mode simultaneously is not supported on the SPA-2CHT3-CE-ATM.

1.    Router(config)# controller e3 slot/subslot/port

2.    Router(config-controller)# [no] framing g751

3.    Router(config-controller)# cablelength feet

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

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

6.    Router(config-controller)# exit

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

2.    Router(config-controller)# atm

3.    Router(config-controller)# exit

4.    Router(config)# interface atm 0/1/2.10 point-to-point

5.    Router(config-if)# pvc vpi /vci

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

7.    Router(config-if)# end

To configure the Scrambling Payload feature on a T3/E3 SPA port, perform the following steps:

Note	The scrambling command is supported on SPA-2CHT3-CE-ATM from Cisco IOS XE Release 3.16.4S and Cisco IOS XE Everest 16.4.1 onwards.

1.    Router(config)# controller t3 slot/subslot/port

2.    Router(config-controller)# atm

3.    Router(config-controller)# scrambling cell-payload

4.    Router(config-controller)# exit

Prior to configuring CEM on the SPA-1CHOC3-CE-ATM port, SPA-2CHT3-CE-ATM port, and SPA-24CHT1-CE-ATM port, perform the following steps:

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, cem 0/1/0).

2. Configure a pseudowire for each CEM group. The router maps the data from the time slots in each group to 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.

The following figure shows the following sample configurations for the SPA-1CHOC3-CE-ATM, SPA-2CHT3-CE-ATM, and SPA-24CHT1-CE-ATM:

• 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 the PE router 11.0.0.0 over pseudowire 20.

Figure 2. TDM Time Slots-to-Pseudowire Mappings

The following table lists the number of CEM groups you can configure for each CEM SPA.

To configure a CEM group to represent a CEM circuit on a SPA port, perform the following steps:

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

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

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

3.    Router(config-controller)# exit

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

Router(config)# controller t1 3/2/0Router(config-controller)# cem-group 1 unframedRouter(config)# controller t1 3/2/1Router(config-controller)# cem-group 1 timeslots 1,3,5-11Router(config-controller)# cem-group 2 timeslots 12-24Router(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

1.    Router# configure terminal

2.    Router(config)# class cem name

3.    Router(config-cem-class)# command

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 following example, the CEM parameter settings from TDM-Class-A are applied to CEM interface 0/1/0. Any CEM circuits created under this interface inherit these parameter settings.

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

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

2.    Router(config-if)# cem group-number

3.    Router(config-if-cem)# command

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

5.    Router(config-if)# exit

Example

The following sample configuration shows a T1 port on which two CEM circuits (groups) are configured. Each CEM circuit carries data from the 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 from time slots 5, 6, 7, 8, and 11 to the remote PE router at 10.10.10.11.

controller SONET 0/1/0
 description This is SONET controller
 framing sonet
 clock source internal
 loopback network
 !
 sts-1 1
  mode vt-15
  vtg 1 t1 1 description T1 line to 3rd floor PBX
  vtg 1 t1 1 clock source Recovered 6
  vtg 1 t1 1 cem-group 6 timeslots 1-4,9,10
  vtg 1 t1 1 cem-group 7 timeslots 5-8,11
 !
 sts-1 2
  mode vt-15
 !
 sts-1 3
  mode vt-15
int cem0/1/0
  cem 6
    xconnect 10.10.10.10 2 encap mpls
  cem 7
    xconnect 10.10.10.11 5 encap mpls

1.    Router# configure terminal

2.    Router(config)# [no] connect name cem x/y/z circuit-id cem a/b/c circuit-id

Router(config)# connect cem cem 0/1/0 cemckt1 cem 0/2/0 cemckt2

Router(config)# no connect cem cem 0/1/0 cemckt1 cem 0/2/0 cemckt2

Local Switching Redundancy provides a backup attachment circuit (AC) when the primary attachment circuit fails. All the ACs must be on the same Cisco ASR 1000 Series Aggregation Services Router.

The following combinations of CEM ACs are supported:

• CEM ACs on different SPAs on the same SIP
• CEM ACs on different SIPs on the same Cisco ASR 1000 Series Aggregation Services Router

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

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

The following example shows how to verify the configuration of the 24-Port channelized T1/E1 CEoP SPA:

Router# show controllers T1 1/1/14
T1 1/1/14 is up.
  Applique type is SPA-24CHT1-CE-ATM
  Cablelength is short 133
  No alarms detected.
  alarm-trigger is not set
  Soaking time: 3, Clearance time: 10
  AIS State:Clear  LOS State:Clear  LOF State:Clear 
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  Data in current interval (87 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
  Data in Interval 1:
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
  Data in Interval 2:
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
  Data in Interval 3:
     0 Line Code Violations, 3 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
  Total Data (last 3 15 minute intervals):
     0 Line Code Violations, 3 Path Code Violations,
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Router# show ip int brief | inc ATM1/1
ATM1/1/6               unassigned      YES unset  up                    up      
ATM1/1/14              unassigned      YES unset  up                    up      
ATM1/1/14.10           unassigned      YES unset  up                    up 
Router# show interfaces ATM1/1/14
ATM1/1/14 is up, line protocol is up 
  Hardware is SPA-24CHT1-CE-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 4470, BW 1536 Kbit/sec, DLY 100 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, 1 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/375/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 interfaces ATM1/1/14.10
ATM1/1/14.10 is up, line protocol is up 
  Hardware is SPA-24CHT1-CE-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, BW 1536 Kbit/sec, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ATM
  Keepalive not supported 
     0 packets input, 0 bytes
     0 packets output, 0 bytes 
     0 OAM cells input, 0 OAM cells output
  AAL5 CRC errors : 0
  AAL5 SAR Timeouts : 0
  AAL5 Oversized SDUs : 0
  AAL5 length violation : 0
  Last clearing of "show interface" counters never
Router#show interfaces ATM1/1/14.10
ATM1/1/14.10 is up, line protocol is up 
  Hardware is SPA-24CHT1-CE-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, BW 1536 Kbit/sec, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ATM
  Keepalive not supported 
     0 packets input, 0 bytes
     0 packets output, 0 bytes 
     0 OAM cells input, 0 OAM cells output
  AAL5 CRC errors : 0
  AAL5 SAR Timeouts : 0
  AAL5 Oversized SDUs : 0
  AAL5 length violation : 0
  Last clearing of "show interface" counters never
Router# show atm interface ATM1/1/14
Interface ATM1/1/14:
AAL enabled:  AAL5, AAL0, Maximum VCs: 2047, Current VCCs: 1
Max. Datagram Size: 4528
PLIM Type: DS1, TX clocking: LINE
Cell-payload scrambling: OFF
0 input, 0 output, 0 IN fast, 0 OUT fast
 Avail bw = 1536 
Config. is ACTIVE
Router#
Router#show atm interface ATM1/1/14.10
Interface ATM1/1/14.10:
AAL enabled:  AAL5, AAL0, Maximum VCs: 2047, Current VCCs: 1
Max. Datagram Size: 4528
PLIM Type: DS1, TX clocking: LINE
Cell-payload scrambling: OFF
0 input, 0 output, 0 IN fast, 0 OUT fast
 Avail bw = 1536 
Config. is ACTIVE

The following example displays the output of the show commands in the E1 mode:

Router# show controllers e1 1/1/14
E1 1/1/14 is up.
  Applique type is SPA-24CHT1-CE-ATM
  Cablelength is Unknown
  No alarms detected.
  alarm-trigger is not set
  Framing is crc4, Line Code is HDB3, Clock Source is Line.
  International Bit: 1, National Bits: 11111
  Data in current interval (599 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
     0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Router# show interfaces ATM1/1/14
ATM1/1/14 is up, line protocol is up 
  Hardware is SPA-24CHT1-CE-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, sub MTU 4470, BW 1920 Kbit/sec, DLY 100 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/375/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 interfaces ATM1/1/14
*May 24 00:41:57.886: %SYS-5-CONFIG_I: Configured from console by console.10
ATM1/1/14.10 is up, line protocol is up 
  Hardware is SPA-24CHT1-CE-ATM, address is 0000.0000.0000 (bia 0000.0000.0000)
  MTU 4470 bytes, BW 1920 Kbit/sec, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ATM
  Keepalive not supported 
     0 packets input, 0 bytes
     0 packets output, 0 bytes 
     0 OAM cells input, 0 OAM cells output
  AAL5 CRC errors : 0
  AAL5 SAR Timeouts : 0
  AAL5 Oversized SDUs : 0
  AAL5 length violation : 0
  Last clearing of "show interface" counters never
Router# show atm interface ATM1/1/14
Interface ATM1/1/14:
AAL enabled:  AAL5, AAL0, Maximum VCs: 2047, Current VCCs: 1
Max. Datagram Size: 4528
PLIM Type: E1, TX clocking: LINE
Cell-payload scrambling: OFF
0 input, 0 output, 0 IN fast, 0 OUT fast
 Avail bw = 1920 
Config. is ACTIVE
Router#show atm interface ATM1/1/14.10
Interface ATM1/1/14.10:
AAL enabled:  AAL5, AAL0, Maximum VCs: 2047, Current VCCs: 1
Max. Datagram Size: 4528
PLIM Type: E1, TX clocking: LINE
Cell-payload scrambling: OFF
0 input, 0 output, 0 IN fast, 0 OUT fast
 Avail bw = 1920 
Config. is ACTIVE
Router# show atm pvc 
           VCD /                                            Peak Av/Min Burst
Interface  Name         VPI   VCI Type    Encaps     SC     Kbps   Kbps Cells St
1/1/14.10  1             10    11 PVC     SNAP       UBR    1920              UP

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

2.    Router(config-controller)# framing sonet

3.    Router(config-controller)# sts-1 2

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

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

6.    Router(config-controller-sts1)# exit

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

2.    Router(config-controller)# framing sdh

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

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

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

6.    Router(config-ctrlr-tug3)# tug-2 1 e1 1 cem-group 1 unframedor

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

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

2.    Router(config-controller)# framing sdh

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

4.    Router(config-controller)# au-3 3

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

6.    Router(config-ctrlr-au3)# tug-2 1 t1 2 cem-group 1 unframedor

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

You can use the BITS Clock Support—Receive and Distribute—CEM SPA 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 line card operates in three different modes, depending 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 the free-running mode. In this mode, the internal oscillator of the line card generates the reference clock to the backplane.

• Normal—In the 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.

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

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

1.    Router(config)# recovered-clock slot subslot

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

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

4.    Router(config-clock)# clock master

5.    Router(config-clock)# clock slave

To verify clock recovery, use the show recovered-clock command.

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

A TDM network requires a synchronized clock at each end of the connection (source and destination). This means that the source and destination clock signals must be synchronized with 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 the source and the 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 the destination routers.

Out-of-band clocking provides a way to deliver a clock signal between two SPAs. This 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 the 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.

Note	The SPA-2CHT3-CE-ATM does not support Out-of-Band (OOB) clocking in the CEM mode due to lack of hardware support.

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 = 248 bytes
• T1 = 192 bytes
• DS0 = 32 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.

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.

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.

The 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 

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 

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.

The following restriction exists when configuring a Layer 3 QoS on the CEoP SPA:

• The VC QoS on VP-PW feature works only with the single-cell relay function and not with the packed-cell relay function.

The following interfaces are supported for the :

• P2P and multipoint permanent virtual circuit (PVC) under the main interface.
• P2P and multipoint PVC under the subinterface.
• 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 subinterface—AAL5 and AAL0 (SCR and PCR).

1.    Router> enable

2.    Router# configure terminal

3.    Router(config)# interface atm slot /subslot /port.subinterface point-to-point

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


5.    Router(config-if)# pvc vpi/vci

6.    Router(config-if-atm-vc)# service-policy in policy-map-name

7.    Router(config-if-atm-vc)# service-policy out policy-map-name

8.    Router(config-if-atm-vc)# end

The following example shows how to configure a Layer 3 QOS on the CEoP SPA:

Router# configure terminal
Router(config)# interface atm 3/0/0.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

The following example shows how to verify the configuration:

Router# show policy-map interface cem3/0/0.1/1/1
CEM3/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

The following restrictions are applicable while configuring AIS and RAI alarm forwarding:

• Alarms cannot be suppressed in the unframed CEM mode (SAToP). Alarms received from the remote SAToP peer across the PSN always pass over the attachment circuit.
• The forward-alarm -ais/rai- command is a hidden command and is not available in the option list. You must type the full command.

1.    Router> enable

2.    Router# configure terminal

3.    Do one of the following:

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

4.    Do one of the following:

• Router(config-controller)# forward-alarm ais/rai
• Router(config-controller)# t1 1-28 forward-alarm ais/rai

1.    Router> enable

2.    Router# configure terminal

3.    Do one of the following:

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

4.    Do one of the following:

• Router(config-controller)# forward-alarm ais/rai
• Router(config-controller)# e1 1-21 forward-alarm ais/rai

1.    Router(config)# controller sonet slot/bay/port

2.    Router(config-controller)# sts-1 id

3.    Router(config-controller-sts)# vtg identifier t1 identifier forward-alarm {ais|rai}

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

Router(config-controller)# sts-1 1

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

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

2.    Router(config-controller)# framing sdh

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

4.    Router(config-controller)# au-4 id tug-3 id

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

6.    tug-2 id e1 id forward-alarm ais | rai

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

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

2.    Router(config-controller)# framing sdh

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

4.    Router(config-controller)# au-3 3

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

6.    Router(config-ctrlr-au3)# tug-2 tug-2 number t1 t1-line-number forward-alarm {ais | rai}

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

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

The following restrictions apply while configuring AIS or RAI alarm 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.
• The forward-alarm {ais/rai} is a hidden command and is not available in the option list. You must type the full command.