- Preface
- Using Cisco IOS XE Software
- SIP and SPA Product Overview
- Overview of the SIP
- Configuring the SIP
- Troubleshooting the SIP
- Overview of the ATM SPAs
- Configuring the ATM SPAs
- Troubleshooting the ATM SPAs
- Overview of the Ethernet SPAs
- Configuring the Ethernet SPAs
- Troubleshooting the Gigabit Ethernet SPAs
- Overview of the POS SPAs
- Configuring the POS SPAs
- Overview of the Serial SPAs
- Configuring the 8-Port Channelized T1/E1 Serial SPA
- Configuring the 2-Port and 4-Port Channelized T3 SPAs
- Configuring the 2-Port and 4-Port T3/E3 Serial SPA
- Configuring the 4-Port Serial Interface SPA
- Configuring the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA
- Troubleshooting the Serial SPAs
- Overview of the Cisco WebEx Node for the Cisco ASR 1000 Series Routers
- Configuring the Cisco WebEx Node for the ASR 1000 Series Aggregation Services Routers
- Troubleshooting the Cisco WebEx Node for the ASR 1000 Series Aggregation Services Routers
- Overview of the Cisco DSP SPA for the ASR 1000 Series Aggregation Services Routers
- Configuring the Cisco DSP SPA for the ASR 1000 Series Aggregation Services Routers
- Upgrading Field-Programmable Devices
- Classifying and Scheduling Packets for the ASR 1000 Series Aggregation Services Routers
- Overview of the Circuit Emulation over Packet Shared Port Adapter
- Configuring the Circuit Emulation over Packet Shared Port Adapter
- Index
- Restrictions for Configuring the 1-Port Channelized OC-12/STM-4 SPA
- Configuration Tasks
- Specifying the Physical Address for Controller and Interface Configuration
- Required Configuration Tasks
- Configuring the Controller for the SONET Mode and the SDH Mode
- Configuring the SONET Mode
- Configuring the SDH Mode
- Configuring the Channelized DS3 Mode
- Configuring DS1 (Channelized T3 mode)
- Configuring E1 (Channelized T3/E3 mode)
- Configuring the Unchannelized E3 Serial Interface
- Verifying the Interface Configuration
- Optional Configurations
- Saving the Configuration
Configuring the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA
This chapter provides information about configuring the 1-Port Channelized OC-3/STM-1 SPA and the 1-Port Channelized OC-12/STM-4 SPA on the Cisco ASR 1000 Series Aggregation Services Routers.
- Restrictions for Configuring the 1-Port Channelized OC-12/STM-4 SPA
- Configuration Tasks
- Verifying Interface Configuration
- Configuration Examples
Restrictions for Configuring the 1-Port Channelized OC-12/STM-4 SPA
This chapter contains information for configuring two models of the channelized SPAs on the Cisco ASR 1000 Series Aggregation Services Routers, but some features are not yet supported on both models.
Consider the following restrictions when configuring the 1-Port Channelized OC-12/STM-4 SPA on the Cisco ASR 1000 Series Aggregation Services Routers in Cisco IOS XE Release 2.6:
- Multilink Frame Relay (MLFR) is not supported.
- A maximum of 2000 NxDS0 channels are supported.
![]() Note | APS is not supported on Channelized OC-x SPA. |
Configuration Tasks
This section describes how to configure the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA on the Cisco ASR 1000 Series Router, including required and optional configurations. It includes information about configuring the SPAs in either synchronous optical network (SONET) or synchronous digital hierarchy (SDH) framing modes. For information about managing your system images and configuration files, refer to the following:
- Specifying the Physical Address for Controller and Interface Configuration
- Required Configuration Tasks
- Optional Configurations
- Saving the Configuration
Specifying the Physical Address for Controller and Interface Configuration
This section describes how to specify the physical location of the SIP, SPAs, and interfaces on the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA.
To specify the physical address for controller or interface configuration, use the interface and controller sonet commands, where:
- slot —Specifies the chassis slot number in the Cisco ASR 1000 Series Routers where the SIP is installed.
- subslot —Specifies the slot of the SIP where the SPA is installed.
- port —Specifies the SONET port number. There is only one port on a 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA, therefore the port number is always 0.
For example, if the 1-Port Channelized OC-3/STM-1 SPA or 1-Port Channelized OC-12/STM-4 SPA is installed in subslot 0 of a Cisco ASR 1000 SIP in slot 3 of the chassis, the controller configuration address is specified as controller sonet 3/0/0.
For channelized SPA configuration, the interface address format is: slot/subslot/port:channel-group , where:
- channel-group —Specifies the logical channel group assigned to the time slots within the T1 link.
For more information about identifying slots and subslots, see the Required Configuration Tasks.
Naming the Interface
Interface names are automatically generated, and the format will be dependent on the mode each particular linecard is operating on. The name formats of the serial interface created are listed below.
Channelized T3 mode
If framing is SONET or SDH with au-3:
interface serial [slot/subslot/port ][ds3 |ds1 ]:[channel-group ]
SONET Mode
- If framing is SONET and mode is vt-15:
interface serial [slot/subslot/port ].[sts1/vtg/t1 ]:[channel-group ]
- If framing is SONET and mode is CT3
interface serial [slot/subslot/port ].[ds3/t1 ]:[channel-group ]
- If framing is SONET and mode is T3:
interface serial [slot/subslot/port ].[ds3 ]
SDH Mode
If the aug mapping is au-4, the au-4 value is always 1; if the aug mapping is au-3, then the only supported mode is c-11 (carrying a T1).
- If SDH-AUG mapping is au-4 and if the tug-3 is mode t3/e3:
interface serial [slot/subslot/port ].[au-4/tug-3/tug-2/e1 ]:[channel-group ]
- If SDH-AUG mapping is au-3:
interface serial [slot/subslot/port/au-3/tug-2/t1 ]:[channel-group ]
POS on the 1-Port Channelized OC-12/STM-4 SPA
If framing is SONET and n is from 1-12:
interface pos slot/subslot/port:nsts-1
Required Configuration Tasks
This section lists the required configuration steps to configure the 1-Port Channelized OC-3/STM-1 SPA. Some of the required configuration commands implement default values that might be appropriate for your network.
This section includes the following topics:
- Configuring the Controller for the SONET Mode and the SDH Mode
- Configuring the SONET Mode
- Configuring the SDH Mode
- Configuring the Channelized DS3 Mode
- Configuring DS1 (Channelized T3 mode)
- Configuring E1 (Channelized T3/E3 mode)
- Configuring the Unchannelized E3 Serial Interface
- Verifying the Interface Configuration
Configuring the Controller for the SONET Mode and the SDH Mode
Controller configuration is required for both SONET and SDH framing modes. To configure the controller on the 1-Port Channelized OC-3/STM-1 SPA or 1-Port Channelized OC-12/STM-4 SPA, complete the following step:
Command |
Purpose |
||
---|---|---|---|
Router(config)# controller sonet slot/subslot/port |
Selects the controller to configure and enters controller configuration mode, where:
|
Configuring the SONET Mode
To configure the SONET mode, complete the following steps:
1. Router(config-controller)# framing sonet
2. Router(config-controller)# clock source {internal | line}
3. Router(config-controller)# loopback {local | network}
4. Router(config-controller)# sts-1 {1- 12 | 1 - 3 | 4 - 6 | 7 - 9 | 10 - 12} pos
5. Router(config-controller)# sts-1 sts1-#
6. Router(config-ctrlr-sts1)# mode {ct3 | ct3-e1 | t3 | vt-15}
7. Router(config-ctrlr-sts1)# vtg vtg#
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router(config-controller)# framing sonet |
Specifies SONET as the frame type. This is the default. |
Step 2 | Router(config-controller)# clock source {internal | line} |
Sets the clock source, where:
|
Step 3 | Router(config-controller)# loopback {local | network} |
Enables or disables loopback mode on a SONET controller, where:
The default is disabled loopback. |
Step 4 | Router(config-controller)# sts-1 {1- 12 | 1 - 3 | 4 - 6 | 7 - 9 | 10 - 12} pos |
Configures the CHOC12 SONET controller for the OC12 POS mode and the OC3 POS mode by specifying that the STS-1s be bundled together for POS. |
Step 5 | Router(config-controller)# sts-1 sts1-# |
Specifies the SONET Synchronous Transport Signal (STS) level and enters STS1 configuration mode, where:
|
Step 6 | Router(config-ctrlr-sts1)# mode {ct3 | ct3-e1 | t3 | vt-15} |
Specifies the mode of operation of an STS-1 path, where:
|
Step 7 | Router(config-ctrlr-sts1)# vtg vtg# |
Configures the T1 on the VTG, where:
|
Configuring the SDH Mode
![]() Note | The SDH mode is supported on 1-Port Channelized OC-12/STM-4 SPA from Cisco IOS XE Release 3.1.1S onwards. |
To configure the SDH mode, complete the following steps:
- Router(config-controller)# au-4 au-4# tug-3 tug-3#
- Router(config-controller)# au-3 au-3#
1. Router(config-controller)# framing sdh
2. Router(config-controller)# aug mapping {au-3 | au-4}
3. Router(config-controller)# clock source {internal | line}
4.
Do one of the following:
5. In SDH framing in AU-4 mode:
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router(config-controller)# framing sdh |
Specifies SDH as the frame type. |
Step 2 | Router(config-controller)# aug mapping {au-3 | au-4} |
Configures AUG mapping for SDH framing. If the AUG mapping is configured to be AU-4, then the following muxing, alignment, and mapping will be used: TUG-3 <--> VC-4 <--> AU-4 <--> AUG If the mapping is configured to be AU-3, then the following muxing, alignment, and mapping will be used: VC-3 <--> AU-3 <--> AUG Default is au-4. |
Step 3 | Router(config-controller)# clock source {internal | line} |
Sets the clock source, where:
|
Step 4 | Do one of the following:
|
Configures AU-3, AU-4, and tributary unit groups, type 3 (TUG-3) for AU-4 and enters specific configuration mode. Depending on the framing mode of SONET or SDH, each STS-1, AU-3, TUG-3, and AU-4 of a 1-Port Channelized OC-3/STM-1 SPA can be configured with one of these commands. Depending on currently configured AUG mapping setting, this command further specifies TUG-3, AU-3, AU-4 or STS-1 muxing. The CLI command parser enters into config-ctrlr-tug3 (SDH mode), config-ctrlr-au3 (SDH mode), or config-ctrlr-sts1 parser mode (SONET mode), which makes only relevant commands visible.
|
Step 5 |
In SDH framing in AU-4 mode: Example: Router(config-ctrlr-tug3)# mode {c-11 | c-12 | t3 | e3} Example: In SDH framing AU-3 mode: Example: Router(config-ctrlr-au3)# mode {c-11 | c-12 | t3 | e3 | ct3 | ct3-e1} Example: |
Configures mode of operation for AU-3 or AU-4 mode, where: C-11 and C-12 are container level-n (SDH) channelized T3s. They are types of T3 channels that are subdivided into 28 T1 channels.
|
Configuring the Channelized DS3 Mode
To configure channelized DS3 mode, complete the following steps:
1. Router(config)# controller sonet slot/subslot/port
2. Router(config-controller)# sts-1 sts1-#
3. Router(config-ctrlr-sts1)# t3 framing {c-bit | m23 | auto-detect}
4. Router(config-ctrlr-sts1)# t3 clock source {internal | line}
5. Router(config-ctrlr-sts1)# t3 loopback {local | network [line | payload] | remote [line | payload]}
6. Router(config-ctrlr-sts1)# t3 mdl string {eic | fic | generator | lic | pfi | port | unit} string
7. Router(config-ctrlr-sts1)# t3 mdl transmit {path | idle-signal | test-signal}
8. Router(config-ctrlr-sts1)# t3 equipment {customer | network} loopback
9. Router(config-ctrlr-sts1)# t3 bert pattern pattern interval 1-14400
DETAILED STEPS
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
Router(config)# controller sonet slot/subslot/port
Example: |
Selects the controller to configure and enters controller configuration mode, where: | ||
Step 2 | Router(config-controller)# sts-1 sts1-# |
Selects STS mode and enters sts1 configuration mode.
| ||
Step 3 |
Router(config-ctrlr-sts1)# t3 framing {c-bit | m23 | auto-detect} Example: Example: |
Specifies the framing mode, where:
| ||
Step 4 |
Router(config-ctrlr-sts1)# t3 clock source {internal | line} Example: |
Sets the clock source, where:
| ||
Step 5 | Router(config-ctrlr-sts1)# t3 loopback {local | network [line | payload] | remote [line | payload]} |
Enables or disables loopback mode on a SONET controller, where:
The default is no loopback. | ||
Step 6 |
Router(config-ctrlr-sts1)# t3 mdl string {eic | fic | generator | lic | pfi | port | unit} string Example: Example: |
Configures maintenance data link (MDL) support parameters, where:
The default is no mdl string. | ||
Step 7 | Router(config-ctrlr-sts1)# t3 mdl transmit {path | idle-signal | test-signal} |
Configures MDL transmit parameters, where:
The default is no mdl transmit. | ||
Step 8 |
Router(config-ctrlr-sts1)# t3 equipment {customer | network} loopback Example: |
Enables the port to honor remote loopback request. Equipment network loopback disables this functionality.
| ||
Step 9 | Router(config-ctrlr-sts1)# t3 bert pattern pattern interval 1-14400 |
Enables Bit Error Rate Testing (BERT), where:
|
Configuring DS1 (Channelized T3 mode)
To configure DS1, complete the following steps:
1. Router(config)# controller sonet slot/subslot/port
2. Router(config-controller)# sts-1 sts-1#
3. Router(config-ctrlr-sts1)# mode {ct3 | vt-15}
4. Router(config-ctrlr-sts1)# t1 t1# clock source {internal | line}
5. Router(config-ctrlr-sts1)# t1 t1# fdl ansi
6. Router(config-ctrlr-sts1)# t1 t1# framing {sf | esf}
7. Router(config-ctrlr-sts1)# t1 t1# yellow {detection | generation}
8. Router(config-ctrlr-sts1)# t1 t1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64]
9. Router(config-ctrlr-sts1)# t1 t1# loopback [local | network {line | payload} | remote {line {fdl {ansi | bellcore} | inband} | payload [fdl] [ansi]}]
10. Router(config-ctrlr-sts1)# t1 t1# shutdown
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 |
Router(config)# controller sonet slot/subslot/port
Example: |
Selects the controller to configure and enters controller configuration mode, where: |
Step 2 | Router(config-controller)# sts-1 sts-1# |
Specifies the SONET Synchronous Transport Signal (STS) level and enters STS configuration mode, where:
|
Step 3 | Router(config-ctrlr-sts1)# mode {ct3 | vt-15} |
Specifies the mode of operation of an STS-1 path, where:
|
Step 4 |
Router(config-ctrlr-sts1)# t1 t1# clock source {internal | line} Example: |
Configures the clocking source, where:
|
Step 5 | Router(config-ctrlr-sts1)# t1 t1# fdl ansi |
Enables the one-second transmission of the remote performance reports using Facility Data Link (FDL), where:
Without this command, FDL runs in ATT, the default mode. ATT is the AT&T TR54016 standard. |
Step 6 | Router(config-ctrlr-sts1)# t1 t1# framing {sf | esf} |
Specifies the type of framing, where:
|
Step 7 | Router(config-ctrlr-sts1)# t1 t1# yellow {detection | generation} |
Enables detection and generation of DS1 yellow alarms, where:
|
Step 8 | Router(config-ctrlr-sts1)# t1 t1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64] |
Configures a T1 or E1 interface, where:
|
Step 9 |
Router(config-ctrlr-sts1)# t1 t1# loopback [local | network {line | payload} | remote {line {fdl {ansi | bellcore} | inband} | payload [fdl] [ansi]}] Example: Example: |
Enables specific t1 channels to loopback, where:
|
Step 10 | Router(config-ctrlr-sts1)# t1 t1# shutdown |
Shuts down the specified T1 channel, where:
|
Configuring E1 (Channelized T3/E3 mode)
![]() Note | From Cisco IOS XE Release 3.1.1S onwards, E1/E3 channelization modes are supported on the 1-Port Channelized OC-12/STM-4 SPA. |
E1 configuration must be done in channelized DS3 mode. To configure E1, complete the following steps:
1. Router(config-controller)# e1 e1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64]
2. Router(config-controller)# e1 e1# unframed
3. Router(config-controller)# e1 e1# [unframed | framing] {crc4 | no-crc4}
4. Router(config-controller)# e1 e1# clock source {internal | line}
5. Router(config-controller)# e1 e1# national bits pattern
6. Router(config-controller)# e1 e1# loopback [local | network]
7. Router(config-controller)# e1 e1# shutdown
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 |
Router(config-controller)# e1 e1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64] Example: |
Creates a logical channel group on an E1 line, where:
|
Step 2 | Router(config-controller)# e1 e1# unframed |
Creates an E1 unframed (clear channel) logical channel group on an E1 line, where:
|
Step 3 | Router(config-controller)# e1 e1# [unframed | framing] {crc4 | no-crc4} |
Sets the type of framing (including unframed) used by an E1 line, where:
|
Step 4 | Router(config-controller)# e1 e1# clock source {internal | line} |
Sets the clock source on an E1 line, where:
|
Step 5 | Router(config-controller)# e1 e1# national bits pattern |
Sets the national reserved bits on an E1 line, where:
|
Step 6 |
Router(config-controller)# e1 e1# loopback [local | network] Example: |
Specifies a loopback on an E1 line, where:
|
Step 7 |
Router(config-controller)# e1 e1# shutdown Example: |
Shuts down an individual E1 line, where:
|
Configuring the Unchannelized E3 Serial Interface
![]() Note | From Cisco IOS XE Release 3.1.1S onwards, E1/E3 channelization modes are supported on the 1-Port Channelized OC-12/STM-4 SPA. |
To configure an unchannelized E3 serial interface, complete the following:
1. Router(config-controller)# dsu mode {cisco | digital-link | kentrox}
2. Router(config-controller)# dsu bandwidth number
3. Router(config-controller)# scramble
4. Router(config-controller)# national bit {0 | 1}
5. Router(config-controller)# framing {bypass | g751 | g832}
6. Router(config-controller)# crc {16 | 32}
7. Router(config-controller)# loopback {network | local | remote}
8. Router(config-controller)# shutdown
9. Router(config-controller)# bert pattern pattern interval 1-14400
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router(config-controller)# dsu mode {cisco | digital-link | kentrox} |
Specifies the interoperability mode used by a T3 or E3 controller, where:
The default is cisco. |
Step 2 | Router(config-controller)# dsu bandwidth number |
Specifies the maximum allowed bandwidth in kbps, where:
|
Step 3 | Router(config-controller)# scramble |
Enables scrambling for the E3 physical layer interface. The default is no scramble. |
Step 4 | Router(config-controller)# national bit {0 | 1} |
Sets the national reserved bits on an E3 line. The default is 0. |
Step 5 | Router(config-controller)# framing {bypass | g751 | g832} |
Sets the framing on the interface, where:
|
Step 6 | Router(config-controller)# crc {16 | 32} |
Selects the CRC size in bits, where:
|
Step 7 | Router(config-controller)# loopback {network | local | remote} |
Specifies loopback is enabled for the unchannelized E3 serial interface, where:
|
Step 8 | Router(config-controller)# shutdown |
Shuts down the E3 interface. |
Step 9 | Router(config-controller)# bert pattern pattern interval 1-14400 |
Sends a BERT pattern on an E3 line, where:
|
Verifying the Interface Configuration
Use the show interface serial command to verify the interface configuration:
Router# show interface serial 1/0/0.1/1:0 Serial1/0/0.1/1:0 is up, line protocol is up Hardware is SPA-1XCHSTM1/OC3 Internet address is 10.1.1.1/16 MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, crc 16, loopback not set Keepalive not set 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, 2 interface resets 0 output buffer failures, 0 output buffers swapped out 1 carrier transitions no alarm present VC 0: timeslot(s): 1, Transmitter delay 0, non-inverted data
Optional Configurations
There are several standard, but optional, configurations that might be necessary to complete the configuration of your serial SPA.
- Configuring the Encapsulation Method
- Configuring the CRC Size for T1
- Configuring FDL
- Configuring FRF.12
- Configuring Multilink Point-to-Point Protocol (Hardware-Based on the QFP)
- Configuring LFI
- Inverting Data on the T1/E1 Interface
- Changing a Channel Group Configuration
- Configuring BERT
Configuring the Encapsulation Method
When traffic crosses a WAN link, the connection needs a Layer 2 protocol to encapsulate traffic. To set the encapsulation method, use the following commands:
1. Router# configure terminal
2. Router(config)# interface serial slot/subslot/port:channel-group
3. Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay}
4. Router(config-if)# crc {16 | 32}
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 |
Router(config)# interface serial slot/subslot/port:channel-group
Example: |
Selects the interface to configure and enters interface configuration mode.
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration. and Naming the Interface. |
Step 3 | Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay} |
Sets the encapsulation method on the interface, where:
|
Step 4 | Router(config-if)# crc {16 | 32} |
Selects the CRC size in bits, where:
|
Configuring the CRC Size for T1
CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA uses a 16-bit cyclic redundancy check (CRC) by default, but also supports a 32-bit CRC. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead. Both the sender and receiver must use the same setting.
To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:
1. Router# configure terminal
2. Router(config)# interface serial slot/subslot/port:channel-group
3. Router(config-if)# crc {16 | 32}
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 |
Router(config)# interface serial slot/subslot/port:channel-group
Example: |
Selects the interface to configure and enters interface configuration mode.
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration and Naming the Interface. |
Step 3 | Router(config-if)# crc {16 | 32} |
Selects the CRC size in bits, where:
|
Configuring FDL
Facility Data Link (FDL) is a 4-kbps channel provided by the Extended Super Frame (ESF) T1 framing format. The FDL performs outside the payload capacity and allows you to check error statistics on terminating equipment without intrusion. To configure FDL, use the following commands:
1. Router# configure terminal
2. Router(config)# controller sonet slot/subslot/port
3. Router(config)# sts-1 sts-#
4. Router(config-ctrlr-sts1)# mode {ct3 | ct3-e1 | t3 | vt-15}
5. If vt-15 mode was selected:
6. Router(config-ctrlr-sts1)# t1 t1# framing {sf | esf}
7. Router(config-ctrlr-sts1)# t1 t1# fdl ansi
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 |
Router(config)# controller sonet slot/subslot/port
Example: |
Selects the controller to configure and enters controller configuration mode.
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration. |
Step 3 | Router(config)# sts-1 sts-# |
Specifies the SONET Synchronous Transport Signal (STS) level and enters STS1 configuration mode, where: sts-1#—STS values are 1 to 3. |
Step 4 | Router(config-ctrlr-sts1)# mode {ct3 | ct3-e1 | t3 | vt-15} |
Specifies the mode of operation of an STS-1 path, where:
|
Step 5 |
If vt-15 mode was selected: Example: Router(config-ctrlr-sts1)# vtg vtg# |
Configures the T1 on the VTG, where:
|
Step 6 |
Router(config-ctrlr-sts1)# t1 t1# framing {sf | esf} Example: |
Specifies the type of framing, where:
|
Step 7 |
Router(config-ctrlr-sts1)# t1 t1# fdl ansi Example: Example: |
Configures the format used for Facility Data Link (FDL) if the framing format was configured for esf, where:
|
Verifying FDL
Use the show controllers t1 command to verify the FDL setting:
Router# show controllers t1 T1 6/0/1 is up. Applique type is Channelized T1 Cablelength is long gain36 0db No alarms detected. alarm-trigger is not set Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line. Data in current interval (742 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 Total Data (last 73 15 minute intervals): 1278491 Line Code Violations, 3 Path Code Violations, 0 Slip Secs, 1 Fr Loss Secs, 177 Line Err Secs, 0 Degraded Mins, 3 Errored Secs, 0 Bursty Err Secs, 1 Severely Err Secs, 227 Unavail Secs
Configuring FRF.12
The 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA support FRF.12 end-to-end fragmentation for Frame Relay. For information about how to configure Frame Relay fragmentation support, see the “Frame Relay Queueing and Fragmentation at the Interface” chapter of the Cisco IOS XE Wide-Area Networking Configuration Guide , Release 2 at:
Configuring Multilink Point-to-Point Protocol (Hardware-Based on the QFP)
Multilink Point-to-Point Protocol (MLPPP) allows you to combine interfaces which correspond to an entire T1 or E1 multilink bundle. You can choose the number of bundles and the number of T1 or E1 lines in each bundle in any combination of E1, T1, and NxDS0 member links interfaces.
On the Cisco ASR 1000 Series Router, MLPPP functionality is implemented on the Quantum Flow Processor (QFP)—not the SPA. On other platforms that implement SPA-based MLPPP, the MLPPP member links must reside on the same SPA—this is not a restriction on the Cisco ASR 1000 Series Aggregation Services Routers. QFP-based MLPPP supports member links in the MLPPP bundle across different SPAs and SIPs on the Cisco ASR 1000 Series Aggregation Services Routers.
For more information about configuring MLPPP in Cisco IOS XE software, see the “Configuring Media-Independent PPP and Multilink PPP” chapter of the Cisco IOS XE Wide-Area Networking Configuration Guide, Release 2 .
This section includes the following topics:
- MLPPP Configuration Guidelines
- Creating a Multilink Bundle
- Assigning an Interface to a Multilink Bundle
- Configuring Fragmentation Size and Delay on an MLPPP Bundle
- Disabling Fragmentation on an MLPPP Bundle
MLPPP Configuration Guidelines
When configuring MLPPP, consider the following guidelines:
- Only T1, E1, or NxDS0 links are supported in a bundle. The configuration will not prohibit higher bandwidth links from being added to the bundle, but they are not supported.
- Links of differing bandwidths are supported in the same bundle.
- PPP encapsulation must be enabled before configuring multilink-related commands.
Creating a Multilink Bundle
To create a multilink bundle, use the following commands:
1. Router# configure terminal
2. Router(config)# interface multilink group-number
3. Router(config-if)# ip address address mask
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 | Router(config)# interface multilink group-number |
Creates a multilink interface and enters multilink interface mode, where:
|
Step 3 | Router(config-if)# ip address address mask |
Sets the IP address for the multilink group, where:
|
Assigning an Interface to a Multilink Bundle
To assign an interface to a multilink bundle, use the following commands:
1. Router# configure terminal
2. Router(config)# interface serial slot/subslot/port
3. Router(config-if)# encapsulation ppp
4. Router(config-if)# ppp multilink group group-number
5. Router(config-if)# ppp multilink
6. Repeat these commands for each interface you want to assign to the multilink bundle.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 | Router(config)# interface serial slot/subslot/port |
Selects the interface to configure and enters interface configuration mode, where:
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration. |
Step 3 | Router(config-if)# encapsulation ppp |
Enables PPP encapsulation. |
Step 4 | Router(config-if)# ppp multilink group group-number |
Assigns the interface to a multilink bundle, where:
|
Step 5 | Router(config-if)# ppp multilink |
Enables multilink PPP on the interface. |
Step 6 | Repeat these commands for each interface you want to assign to the multilink bundle. |
Configuring Fragmentation Size and Delay on an MLPPP Bundle
To configure the fragmentation size on a multilink PPP bundle, use the following commands:
1. Router# configure terminal
2. Router(config)# interface multilink group-number
3. Router(config-if)# multilink fragment size fragment-size
4. Router(config-if)# ppp multilink fragment-delay delay
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 | Router(config)# interface multilink group-number |
Creates a multilink interface and enters multilink interface mode, where:
|
Step 3 | Router(config-if)# multilink fragment size fragment-size |
Sets the fragmentation size in bytes. Fragmentation is disabled by default. |
Step 4 | Router(config-if)# ppp multilink fragment-delay delay |
Sets the configured delay on the multilink bundle that satisfies the fragmentation size, where:
|
The following example of the show ppp multilink command shows the MLPPP type and the fragmentation size:
Router# show ppp multilink Multilink1, bundle name is test2Bundle up for 00:00:13Bundle is Distributed0 lost fragments, 0 reordered, 0 unassigned0 discarded, 0 lost received, 206/255 load0x0 received sequence, 0x0 sent sequence Member links: 2 active, 0 inactive (max not set, min not set)Se4/2/0/1:0, since 00:00:13, no frags rcvdSe4/2/0/2:0, since 00:00:10, no frags rcvdDistributed fragmentation on. Fragment size 512. Multilink in Hardware. .
Disabling Fragmentation on an MLPPP Bundle
By default, PPP multilink fragmentation is enabled. To disable fragmentation on a multilink bundle, use the following commands:
1. Router# configure terminal
2. Router(config)# interface multilink group-number
3. Router(config-if)# ppp multilink fragment disable
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 | Router(config)# interface multilink group-number |
Specifies the multilink interface and enters multilink interface mode, where:
|
Step 3 | Router(config-if)# ppp multilink fragment disable |
Disables PPP multilink fragmentation. |
Configuring LFI
Link Fragmentation and Interleaving (LFI) is implemented on the QFP on the Cisco ASR 1000 Series Aggregation Services Routers. QFP-based LFI supports LFI on a bundle with any number of links—from one link, up to the maximum number supported by the router. When using LFI on MLPPP, the QFP load balances the priority packets across all links in the bundle to minimize the latency on the priority interleaved traffic.
LFI Configuration Guidelines
When you configure LFI, consider the following guidelines:
- Configure LFI using the ppp multilink interleave command. For MLPPP, this is on the multilink interface.
- Configure and apply an output QoS service-policy that classifies the priority and non-priority traffic. For MLPPP, you can apply the output policy on the multilink interface.
![]() Note | When you configure LFI, note the following restrictions:
To configure LFI on a multilink interface, use the following commands: |
1. Router# configure terminal
2. Router(config)# interface multilink group-number
3. Router(config-if) ppp multilink
4. Router(config-if)# ppp multilink interleave
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 | Router(config)# interface multilink group-number |
Creates or specifies a multilink interface and enters multilink interface mode, where:
|
Step 3 | Router(config-if) ppp multilink |
Enables Multilink PPP. |
Step 4 | Router(config-if)# ppp multilink interleave |
Enables interleaving of packets among the fragments of larger packets on an MLP bundle.
|
Inverting Data on the T1/E1 Interface
If the interface on the channelized SPA is used to drive a dedicated T1 line that does not have B8ZS encoding, you must invert the data stream on the connecting CSU/DSU or on the interface. Be careful not to invert data on both the CSU/DSU and the interface, as two data inversions will cancel each other out.
To invert data on a T1/E1 interface, use the following commands:
1. Router# configure terminal
2. Router(config)# interface serial slot/subslot/port
3. Router(config-if)# invert data
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 |
Router(config)# interface serial slot/subslot/port
Example: |
Selects the serial interface and enters interface configuration mode, where:
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration. |
Step 3 | Router(config-if)# invert data |
Inverts the data stream. |
Use the show running configuration command to verify that invert data has been set:
router# show running configuration interface Serial6/0/0:0 no ip address encapsulation ppp logging event link-status load-interval 30 invert data no cdp enable ppp chap hostname group1 ppp multilink ppp multilink group 1
Changing a Channel Group Configuration
To alter the configuration of an existing channel group, the channel group needs to be removed first using the no form of the channel-group command. To remove an existing channel group, use the following commands:
1. Router# configure terminal
2. Router(config)# interface serial slot/subslot/port
3. Router(config-controller)# no channel-group t1 t1-number
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 | Router# configure terminal |
Enters global configuration mode. |
Step 2 |
Router(config)# interface serial slot/subslot/port
Example: |
Select the controller to configure and enters controller configuration mode, where:
For addressing information, refer to the Specifying the Physical Address for Controller and Interface Configuration. |
Step 3 | Router(config-controller)# no channel-group t1 t1-number |
Selects the channel group you want to remove, where:
|
Configuring BERT
BERT (Bit-Error Rate Testing) is used for analyzing quality and for problem resolution of digital transmission equipments. BERT tests the quality of an interface by directly comparing a pseudorandom or repetitive test pattern with an identical locally generated test pattern.
The BERT operation is data-intensive. Regular data cannot flow on the path while the test is in progress. The path is reported to be in alarm state when BERT is in progress and restored to a normal state after BERT has been terminated.
BERT Test Configuration Guidelines
When configuring BERT on the 1-Port Channelized OC-3/STM-1 SPA or 1-Port Channelized OC-12/STM-4 SPA, consider the following guidelines:
- Only DS1/T1 and DS3/T3 paths are supported on the 1-Port Channelized OC-12/STM-4 SPA.
- A maximum of 27 concurrent tests across all paths on the SPA is supported.
BERT Pattern Descriptions
The following tables describe the supported BERT patterns on the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPA.
Pattern |
Description |
---|---|
0s |
All 0’s in the test pattern (...000...). |
1-in-8 |
8-bit test pattern where 1 out of 8 bits is set to 1. |
1s |
All 1’s in the test pattern (...111...). |
2^11 |
Pseudorandom 1 test pattern that is 2,048 bits in length. |
2^15 |
Pseudorandom 1 O.151 test pattern that is 32,768 bits in length. |
2^15-inverted |
Pseudorandom 1 inverted O.151 test pattern that is 32,768 bits in length. |
2^20-O153 |
Pseudorandom 1 O.153 test pattern that is 1,048,575 bits in length. |
2^20-QRSS |
Pseudorandom 1 quasi-random signal sequence (QRSS) 0.153 test pattern that is 1,048,575 bits in length. |
2^23 |
Pseudorandom 1 O.151 test pattern that is 8,388,607 bits in length. |
2^23-inverted |
Pseudorandom 1 inverted O.151 test pattern that is 8,388,607 bits in length. |
2^9 |
Pseudorandom 1 O.150 test pattern that is 511 bits in length. |
3-in-24 |
24-bit test pattern where 3 out of 24 bits is set to 1. |
alt-0-1 |
Repeating test pattern of alternating 0’s and 1’s (...01010...). |
Pattern |
Description |
---|---|
0s |
All 0’s in the test pattern (...000...). |
1s |
All 1’s in the test pattern (...111...). |
2^15 |
Pseudorandom 1 O.151 test pattern that is 32,768 bits in length. |
2^20 |
Pseudorandom 1 O.153 test pattern that is 1,048,575 bits in length. |
2^23 |
Pseudorandom 1 O.151 test pattern that is 8,388,607 bits in length. |
alt-0-1 |
Repeating test pattern of alternating 0’s and 1’s (...01010...). |
To configure a BERT pattern for DS1/T1/E1, use one of the following commands:
Command |
Purpose |
---|---|
Router(config-controller)# t1 channel-number bert pattern pattern interval time or Router(config-ctrlr-sts1)# e1 e1-number bert pattern pattern interval time |
Sends a BERT pattern on a line, where:
|
To configure a BERT pattern for DS3/T3/E3, use the following command in controller configuration mode:
Command |
Purpose |
||
---|---|---|---|
Router(config-controller)# bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1} interval time or Router(config-ctrlr-sts1)# bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1} interval time |
Sends a BERT pattern on the DS3 channel, where:
|
The SIPs and SPAs support many QoS features using modular QoS CLI (MQC) configuration. Since there are no serial SPA-specific QoS features, refer to your network processor documentation for QoS configuration information.
Saving the Configuration
To save your running configuration to nonvolatile random-access memory (NVRAM), use the following command in privileged EXEC configuration mode:
Command |
Purpose |
---|---|
Router# copy running-config startup-config |
Writes the new configuration to NVRAM. |
For more information about managing configuration files, refer to the Cisco IOS XE Configuration Fundamentals Configuration Guide, Release 2 and Cisco IOS Configuration Fundamentals Command Reference publications.
Verifying Interface Configuration
Besides using the show running-configuration command to display your Cisco ASR 1000 Series Router configuration settings, you can use the show interface serial and the show controllers sonet commands to get detailed information on a per-port basis for your channelized SPA.
Verifying Per-Port Interface Status
To find detailed interface information on a per-port basis for the channelized SPAs, use the show interface serial and show controllers sonet commands.
See the Verifying the Interface Configuration for an example of the show interface serial command.
The following example provides sample output for interface port 0 on the SPA located in subslot 0 of the Cisco ASR 1000 SIP installed in slot 1of a Cisco ASR 1000 Series Router:
Router# show controllers sonet 1/0/0 SONET 1/0/0 is up. Hardware is SPA-1XCHSTM1/OC3 IO FPGA version: 1.7, HDLC Framer version: 0 T3/T1 Framer(1) version: 1 Sonet/SDH Framer version: 0 SUBRATE FPGA version: 1.4 HDLC controller available FIFO buffers 3760 Applique type is Channelized Sonet/SDH Clock Source is Line Medium info: Type: Sonet, Line Coding: NRZ, SECTION: LOS = 0 LOF = 0 BIP(B1) = 85 SONET/SDH Section Tables INTERVAL CV ES SES SEFS 23:15-23:20 0 0 0 0 23:00-23:15 0 0 0 0 22:45-23:00 85 1 1 0 Total of Data in Current and Previous Intervals 22:45-23:20 85 1 1 0 LINE: AIS = 0 RDI = 1 REI = 65 BIP(B2) = 207 Active Defects: None Active Alarms: None Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 SONET/SDH Line Tables INTERVAL CV ES SES UAS 23:15-23:20 0 0 0 0 23:00-23:15 0 0 0 0 22:45-23:00 272 1 0 5 Total of Data in Current and Previous Intervals 22:45-23:20 272 1 0 5 . . . SONET/SDH Path Tables INTERVAL CV ES SES UAS 23:15-23:20 0 0 0 0 23:00-23:15 0 0 0 0 22:45-23:00 187382 2 0 0 Total of Data in Current and Previous Intervals 22:45-23:20 187382 2 0 0 . . . T3 1/0/0 Path 1 is up. Hardware is SPA-1XCHSTM1/OC3 IO FPGA version: 1.7, HDLC Framer version: 0 T3/T1 Framer(1) version: 1 Sonet/SDH Framer version: 0 SUBRATE FPGA version: 1.4 HDLC controller available FIFO buffers 3760 Applique type is T3 No alarms detected. MDL transmission is enabled FEAC code received: No code is being received Framing is C-BIT Parity, Cablelength is 224 Clock Source is Line Equipment customer loopback Data in current interval (346 seconds elapsed): 0 Line Code Violations, 0 P-bit Coding Violation 0 C-bit Coding Violation, 0 P-bit Err Secs 0 P-bit Severely Err Secs, 0 Severely Err Framing Secs 0 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, 0 Far-end path failures 0 Far-end code violations, 0 FERF Defect Secs 0 AIS Defect Secs, 0 LOS Defect Secs . . . CT3 1/0/0.2 is up. Hardware is SPA-1XCHSTM1/OC3 IO FPGA version: 1.7, HDLC Framer version: 0 T3/T1 Framer(1) version: 1 Sonet/SDH Framer version: 0 SUBRATE FPGA version: 1.4 HDLC controller available FIFO buffers 3760 Applique type is Channelized T3 to T1 No alarms detected. Framing is M23, Cablelength is 224 Clock Source is Internal Equipment customer loopback Data in current interval (356 seconds elapsed): 0 Line Code Violations, 0 P-bit Coding Violation 0 C-bit Coding Violation, 0 P-bit Err Secs 0 P-bit Severely Err Secs, 0 Severely Err Framing Secs 0 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, 0 Far-end path failures 0 Far-end code violations, 0 FERF Defect Secs 0 AIS Defect Secs, 0 LOS Defect Secs (Remaining output omitted)
Configuration Examples
This section includes the following configuration examples:
- Example of T3 Framing Configuration
- Example of Cyclic Redundancy Check Configuration
- Example of Facility Data Link Configuration
- Example of Invert Data on T1/E1 Interface
Example of T3 Framing Configuration
The following example configures framing on a T3 interface:
! Specify the interface to configure and enter interface configuration mode. ! Router(config)# controller sonet 3/0/0 ! ! Select the STS mode. ! Router(config-controller)# sts-1 2 ! !Select the framing mode. ! Router(config-controller)# t3 framing m23
Example of Cyclic Redundancy Check Configuration
The following example configures CRC on a T1 interface:
! Specify the interface to configure and enter interface configuration mode. ! Router(config)# interface serial 2/0/0.1 ! ! Specify the CRC type. ! Router(config-if)# crc 32
Example of Facility Data Link Configuration
The following example configures FDL on a T1 interface:
! Specify the interface to configure and enter interface configuration mode. ! Router(config)# interface serial 1/0/0.2 ! ! Specify the T1 number and select fdl. ! Router(config-controller)#t1 2 fdl ansi
Example of Invert Data on T1/E1 Interface
The following example inverts the data on the serial interface:
! Specify the interface to configure and enter interface configuration mode. ! Router(config)# interface serial 3/0/0.1/2/1:0 ! ! Configure invert data. ! Router(config-if)#