Cisco 12000 Series Router SIP and SPA Software Configuration Guide, 12.0(33)S

Configuring the 1-Port Channelized OC-3/STM-1 SPA

This chapter provides information about configuring the 1-Port Channelized OC-3/STM-1 SPA on Cisco 12000 Series Routers. It includes the following sections:

•Configuration Tasks

•Verifying the Interface Configuration

For information about managing your system images and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.0 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.0 publications.

Also refer to the related Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the "Related Documentation" section in the Preface.

Configuration Tasks

This section describes how to configure the 1-Port Channelized OC-3/STM-1 SPA for the Cisco 12000 Series Routers and includes information about verifying the configuration. This document shows how to configure the 1-Port Channelized OC-3/STM-1 SPA in either SONET or SDH framing modes.

It includes the following topics:

•Required Configuration Tasks

•Selection of Physical Port and Controller configuration

•Optional Configurations

•Saving the Configuration

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. If the default value is correct for your network, then you do not need to configure the command.

•Selection of Physical Port and Controller configuration

•Interface Naming

•SONET mode Configuration

•SDH mode Configuration

•Verifying Interface Configuration

Note To better understand the address format used to specify the physical location of the Cisco 12000 SIP-401, SPA, and interfaces, see the: "Selection of Physical Port and Controller configuration" section.

Selection of Physical Port and Controller configuration

To select the physical port and controller configuration, use the following command:

controller sonet slot / subslot / port

If the 1-Port Channelized OC-3/STM-1 SPA sits in subslot 0 of a Cisco 12000 SIP-401 in slot3, the 1-Port Channelized OC-3/STM-1 SPA port would be identified as controller SONET 3/0/0. Since there is only 1 port on a 1-Port Channelized OC-3/STM-1 SPA, the port number is always 0.

Interface Naming

Interface names are automatically generated, and the format will be dependent on the mode each particular linecard is operating on. The name format of the serial interface created are listed below.

SONET mode

•If framing is SONET and mode is vt-15:

interface serial [slot / subslot / port].[sts1/ ds1 / t1]:[channel-group]

•If framing is SONET and mode is CT3

interface serial [slot / subslot / port].[sts1 / ds1 / ds1]:[channel-group]

•If framing is SONET and mode is CT3-E1:

interface serial [slot / subslot / port].[sts1 / ds1 / e1]:[channel-group]

•If framing is SONET and mode is T3:

interface serial [slot / subslot / port.sts1]

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 / 0.1 / <tug-3>]

•If SDH-AUG mapping is au-3:

interface serial [slot / subslot / port / au-3 / <tug-2> / t1]:[channel-group]

•If framing is SDH with ct-12 mode:

interface serial [slot/ subslot / 0.1 / <tug-3> / <tug-2> / e1]:[channel-group]

•If framing is SDH with c-11 mode:

interface serial [slot / subslot / 0.<au-3> / <tug-2> / t1]: [channel-group]

For channelized T3 mode

•If framing is SONET or SDH with au-3:

interface serial [slot | subslot | port] [ds3| DS1]:[channel-group]

Selection of Physical Port and controller Configuration—SONET mode

To create the interface for the 1-Port Channelized OC-3/STM-1 SPA, complete these steps:

SONET mode Configuration

To configure the SONET controller, complete these steps:

SDH mode Configuration

To configure SDH mode, complete the following steps:

Configure Channelized DS3

To configure channelized DS3 mode, complete the following steps:

DS1 Configuration (Channelized T3 mode)

To configure DS1 complete the following steps:

E1 Configuration (Channelized T3/E3 mode)

E1 configuration must be done in channelized DS3 mode. To configure E1, complete the following steps:

BERT Test Configuration

To configure BERT test, complete the following:

Unchannelized E3 Serial Interface Configuration

To configure an unchannelized E3 serial interface, complete the following:

Use the show controllers command to verify the controller configuration:

Router(config)# show controllers t1

T1 6/0/1 is up.

  Applique type is Channelized T1

  Cablelength is long gain36 0db

  No alarms detected.

blarm-trigger is not set

  Framing is ESF, Line Code is B8ZS, Clock Source is Line.

  Data in current interval (395 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 24 hours)

     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

Verifying Interface Configuration

Use the show interface serial command to verify the interface configuration:

Router(config)# show interface serial

Serial2/0/0.1/2 unassigned YES TFTP administratively down down  
Serial2/1/0.1/1/1:0 unassigned YES unset down down  
Serial2/1/0.1/2/4:0 unassigned YES unset down down  
Serial2/1/0.1/2/4:1 unassigned YES unset down down  
Serial2/1/0.2/1:0 unassigned YES unset down down  
Serial2/1/0.2/2:0 unassigned YES unset down down  
Serial2/1/0.2/3:0 unassigned YES unset down down  
Serial2/1/0.3 unassigned YES unset down down  
UUT#sh int Serial2/1/0.1/1/1:0 
Serial2/1/0.1/1/1:0 is down, line protocol is down  
Hardware is Channelized-T3 
MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec, rely 255/255, load 1/255 
Encapsulation HDLC, crc 16, loopback not set 
Keepalive set (10 sec) 
Last input never, output never, output hang never 
Last clearing of "show interface" counters never 
Queueing strategy: fifo 
Output queue 0/40, 0 drops; input queue 0/75, 0 drops 
Available Bandwidth 192 kilobits/sec 
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 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 
0 carrier transitions alarm present 
VC 2: timeslot(s): 1-3, Transmitter delay 0, non-inverted data 
UUT#sh run | beg 2/1/0 
controller SONET 2/1/0 
ais-shut 
framing sonet 
clock source line 
overhead j0 1 
! 
sts-1 1 
mode vt-15 
vtg 1 t1 1 channel-group 0 timeslots 1-3 
vtg 2 t1 4 channel-group 0 timeslots 1-2,5-6 
vtg 2 t1 4 channel-group 1 timeslots 3,7,9 
! 
sts-1 2 
mode ct3 
t1 1 channel-group 0 timeslots 1-24 
t1 2 channel-group 0 timeslots 1-12 
t1 3 channel-group 0 timeslots 1 
! 
sts-1 3 
mode t3 
! 
controller T3 3/1/0 
shutdown 
cablelength 224 
! 
controller T3 3/1/1 
shutdown 
cablelength 224 
! 
! 
interface Loopback0 
ip address 172.10.11.1 255.255.255.255

.

.

Optional Configurations

There are several standard, but optional, configurations that might be necessary to complete the configuration of your serial SPA.

•Configuring Encapsulation

•Configuring the CRC Size for T1

•Configuring FDL

•Configuring Multilink Point-to-Point Protocol (Hardware-based)

•Configuring MLFR

•Invert Data on the T1/E1 Interface

•Changing a Channel Group Configuration

•FRF.12 Guidelines

•LFI Guidelines

•HW MLPPP LFI Guidelines

•FRF.12 LFI Guidelines

Configuring Encapsulation

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:

Configuring the CRC Size for T1

The 1-Port Channelized OC-3/STM-1 SPA interface uses a 16-bit cyclic redundancy check (CRC) by default, but also support a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. 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.

CRC-16, the most widely used CRC throughout the United States and Europe, is used extensively with WANs. CRC-32 is specified by IEEE 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.

To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:

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.

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 Multilink Point-to-Point Protocol (Hardware-based)

Multilink Point to Point Protocol (MLPPP) allows you to combine interfaces which correspind to an entire T1 or E1 multilink bundle. You choose the number of bundles and the number of T1 or E1 lines in each bundle.

MLPPP Configuration Guidelines

The required conditions are:

•Only T1 or E1 links in a bundle

•All links on the same SPA

•Maximum of 12 links in a bundle.

Note Some notes about hardware-based MLPPP:

Only 3 fragmentation sizes are possible 128, 256 and 512 bytes

Fragmentation is enabled by default, default size is 512 bytes

Fragmentation size is configured using the ppp multilink fragment-delay command after using the interface multilink command. The least of the fragmentation sizes (among the 3 sizes possible) satisfying the delay criteria is configured. (e.g., a 192 byte packet causes a delay of 1 millisecond on a T1 link, so the nearest fragmentation size is 128 bytes.

The show ppp multilink command will indicate the MLPPP type and the fragmentation size:

Router# show ppp multilink
Multilink1, bundle name is Patriot2
Bundle up for 00:00:13
Bundle is Distributed
0 lost fragments, 0 reordered, 0 unassigned
0 discarded, 0 lost received, 206/255 load
0x0 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 rcvd
Se4/2/0/2:0, since 00:00:10, no frags rcvd
Distributed fragmentation on. Fragment size 512. Multilink in Hardware.

Fragmentation is disabled explicitly by using the no ppp multilink fragmentation command after using the interface multilink command.

Create a Multilink Bundle

To create a multilink bundle, use the following commands:

Assign an interface to a Multilink Bundle

To assign an interface to a multilink bundle, use the following commands:

Configuring fragmentation size on an MLPPP Bundle (optional)

To configure the fragmentation size on a multilink ppp bundle, use the following commands:

Disabling the fragmentation on an MLPPP Bundle (optional)

To assign an interface to a multilink bundle, use the following commands:

Configuring MLFR

Multilink Frame Relay (MLFR) allows you to combine T1/E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of T1/E1 lines in each bundle. This allows you to increase the bandwidth of your network links beyond that of a single T1/E1 line.

MLFR Configuration Guidelines

MLFR will function in hardware if all of the following conditions are met:

•Only T1 or E1 member links

•All links are on the same SPA

•Maximum of 12 links in a bundle

Create a Multilink Bundle

To create a multilink bundle, use the following commands:

Assign an Interface to a Multilink Bundle

To assign an interface to a multilink bundle, use the following commands:

Verifying Multilink Frame Relay

Use the show frame-relay multilink detailed command to verify the Frame Relay multilinks:

router# show frame-relay multilink detailed

Bundle: MFR49, State = down, class = A, fragmentation disabled

 BID = MFR49

 No. of bundle links = 1, Peer's bundle-id = 

 Bundle links:

  Serial6/0/0:0, HW state = up, link state = Add_sent, LID = test

    Cause code = none, Ack timer = 4, Hello timer = 10,

    Max retry count = 2, Current count = 0,

    Peer LID = , RTT = 0 ms

    Statistics:

    Add_link sent = 21, Add_link rcv'd = 0,

    Add_link ack sent = 0, Add_link ack rcv'd = 0,

    Add_link rej sent = 0, Add_link rej rcv'd = 0,

    Remove_link sent = 0, Remove_link rcv'd = 0,

    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

    Hello sent = 0, Hello rcv'd = 0,

    Hello_ack sent = 0, Hello_ack rcv'd = 0,

    outgoing pak dropped = 0, incoming pak dropped = 0

Invert Data on the T1/E1 Interface

If the interface on the 1-Port Channelized OC-3/STM-1 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:

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

 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:

FRF.12 Guidelines

FRF.12 functions in hardware. Note the following:

•The fragmentation is configured at the main interface

•Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.

LFI Guidelines

LFI can function two ways - using FRF.12 or MLPPP. MLPPP LFI can be done in both hardware and software while FRF.12 LFI is done only in hardware.

HW MLPPP LFI Guidelines

LFI using MLPPP will function only in hardware if there is just one member link in the MLPPP bundle. The link can be a fractional T1 or full T1. Note the following:

•The ppp multilink interleave command needs to be configured to enable interleaving.

•Only three fragmentation sizes are supported - 128 bytes, 256 bytes, and 512 bytes.

•Fragmentation is enabled by default, the default size being 512 bytes.

•A policy-map having a priority class needs to applied to main interface.

FRF.12 LFI Guidelines

LFI using FRF.12 is always done is hardware. Note the following:

•The fragmentation is configured at the main interface

•Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.

•A policy-map having a priority class needs to applied to main interface.

Saving the Configuration

To save your running configuration to nonvolatile random-access memory (NVRAM), use the following command in privileged EXEC configuration mode:

For more information about managing configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.0 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.0 publications.

Verifying the Interface Configuration

Besides using the show running-configuration command to display your Cisco 12000 Series Router configuration settings, you can use the show interface serial and the show controllers serial commands to get detailed information on a per-port basis for your1-Port Channelized OC-3/STM-1 SPA.

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the 1-Port Channelized OC-3/STM-1 SPA use the show interface serial command.

The following example provides sample output for interface port 0 on the SPA located in the first subslot of the Cisco 12000 SIP-401 installed in slot 2 of a Cisco 12000 router:

Router# show interface serial 2/1/0.2/1:0

Serial2/1/0.2/1:0 is down, line protocol is down  
Hardware is Channelized-T3 
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 1/255 
Encapsulation HDLC, crc 16, loopback not set 
Keepalive set (10 sec) 
Last input never, output never, output hang never 
Last clearing of "show interface" counters never 
Queueing strategy: fifo 
Output queue 0/40, 0 drops; input queue 0/75, 0 drops 
Available Bandwidth 1536 kilobits/sec 
5 minute output rate 0 bits/sec, 0 packets/sec 
0 packets input, 0 bytes, 0 no buffer 
Received 0 broadcasts, 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 
0 carrier transitions alarm present 
VC 5: timeslot(s): 1-24, Transmitter delay 0, non-inverted data 
UUT#sh int Serial2/1/0.3  
Serial2/1/0.3 is down, line protocol is down  
Hardware is CHOCx SPA 
MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load 1/255 
Encapsulation HDLC, crc 16, loopback not set 
Keepalive set (10 sec) 
Last input never, output never, output hang never 
Last clearing of "show interface" counters never 
Queueing strategy: fifo 
Output queue 0/40, 0 drops; input queue 0/75, 0 drops 
Available Bandwidth 44210 kilobits/sec 
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 runts, 0 giants, 0 throttles 
0 parity 

(Remaining output omitted)