Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide - Configuring the 1-Port Channelized OC-3/STM-1 SPA [Cisco 7600 Series Routers]

Table Of Contents

Configuring 1-Port ChOC-3/STM-1 and ChOC-12 / STM-4 SPAs

Configuration Tasks

Required Configuration Tasks

Selection of Physical Port and Controller Configuration

Interface Naming

Selection of Physical Port and controller Configuration—SONET mode

SONET mode Configuration

SDH mode Configuration

Configure Channelized DS3

POS Interface Configuration

DS1 Configuration (Channelized T3 mode)

E1 Configuration (Channelized T3/E3 mode)

BERT Test Configuration

Unchannelized E3 Serial Interface Configuration

Optional Configurations

Configuring Encapsulation

Configuring the CRC Size for T1

Configuring FDL

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

Configuring APS

Verifying the APS Configuration

Configuring MLFR

Invert Data on the T1/E1 Interface

Configuring Multipoint Bridging

Configuring Bridging Control Protocol Support

Changing a Channel Group Configuration

FRF.12 Guidelines

LFI Guidelines

HW MLPPP LFI Guidelines

FRF.12 LFI Guidelines

Configuring QoS Features on Serial SPAs

Saving the Configuration

Verifying the Interface Configuration

Verifying Per-Port Interface Status

Configuration Tasks

Configuring CRTP

Configuring 1-Port ChOC-3/STM-1 and ChOC-12 / STM-4 SPAs

This chapter provides information about configuring the 1-Port Channelized OC-3/STM-1 SPA on Cisco 7600 series routers and 1-Port Channelized OC-12/STM-4 SPA on SIP 400 introduced with IOS release 12.2(33) SRD 1. The new 1-Port Channelized OC-12/STM-4 SPA terminates channelized IP services on the service provider edge and maintains feature parity with 1-Port Channelized OC-12/STM-4 SPA on Cisco 7600 series router SIP-200 line cardand the Channelized OC-12 SPA on the OSM line card.

This chapter 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.2 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 publications.

For more information about the commands used in this chapter, refer to the Cisco IOS Software Releases 12.2SR Command References and to the Cisco IOS Software Releases 12.2SX Command References. Also refer to the related Cisco IOS Release 12.2 software command reference and master index publications. For more information, see the "Related Documentation" section on page li.

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 for the Cisco 7600 series routers and includes information about verifying the configuration.

Up to 12 STS-1 connections can be configured on the 1-Port Channelized OC-12/STM-4 SPA. Each STS-1 connection can be configured as a T3 controller or as a VT controller. STS-1 can be clubbed together to support the concatenated POS interface. A maximum of 2000 interfaces can be configured.

This document shows how to configure the 1-Port Channelized OC-3/STM-1 SPA and 1-Port Channelized OC-12/STM-4 SPAs 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 steps to configure the 1-Port Channelized OC-3/STM-1 SPA and the 1-Port Channelized OC-12/STM-4 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

•Configure Channelized DS3

•POS Interface Configuration

•Verifying Interface Configuration

Note To better understand the address format used to specify the physical location of the Cisco 7600 SIP-200, 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 on the 1-Port Channelized STM-1/OC-3 SPA , 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 7600 SIP-200 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.

To select the physical port and controller configuration on the 1-Port Channelized OC-12/STM-4 SPA, use the following command:

controller sonet slot / bay/ port

Interface Naming

Interface names are automatically generated, and the format will be dependent on the mode each particular line card 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:

Command

Purpose

Step 1

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

Select the controller to configure and enter controller configuration mode.

•slot/subslot/port—Specifies the location of the interface. See the: "Selection of Physical Port and Controller Configuration" section

Note The port number is always zero on the 1-Port Channelized OC-3/STM-1 SPA.

SONET mode Configuration

To configure the SONET controller, complete these steps:

Command

Purpose

Step 1

For SONET controllers:

Router(config-controller)# framing {sonet | sdh}

Selects the framing type.

•sonet—Specifies SONET as the frame type. This is the default.

•sdh—Specifies sdh as the frame type.

Step 2

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

Sets the clock source.

Note The clock source is set to internal if the opposite end of the connection is set to line and the clock source is set to line if the opposite end of the connection is set to internal.

•internal—Specifies that the internal clock source is used.

•line—Specifies that the network clock source is used. This is the default for T1 and E1.

Step 3

Router(config-controller)# [no] loopback {local | network ]

Enables or disables loopback mode on a sonet controller.

•local loopback—loops data from the transmit path to the receive path.

•network loopback—loops data received on the external port to the transmit path and back out the external port.

Default is disabled loopback.

Step 4

In SONET framing:

Router(config-controller)# sts-1 sts1-#

sts-1 #—Specifies the SONET STS level.

Step 5

[no] mode {vt-15 | ct3 | t3 | ct3-e1}

Specifies the mode of operation of a STS-1 path:

•vt-15—A STS-1 is divided into 7 vtg. Each vtg then divided into 4 VT1.5's, each carrying a T1.

•ct3—A STS-1 carry a DS3 signal divided into 28 T1s (PDH)

•t3—STS-1 or AU-4/TUG3 carries a unchannelized (clear channel) T3

•ct3—The channelized T3 is carrying E1 circuits

Step 6

•sts1 carries T1s (sonet - vt):

router(config-controller-sts1)# mode vt-15

or

•sts1 carries T1s (sonet - ds3 down to ds1):

router(config-controller-sts1)# mode ct3

or

•sts1 carries DS3(sonet - ds3):

router(config-controller-sts1)# mode t3

Selects a mode of operation.

Step 7

Router(config-ctrlr-sts1)# vtg?

<1-7> vtg number <1-7>

•vtg—Specifies the vtg number.

Step 8

Router(config-ctrlr-sts1)#vtg 1 ?

T1 T1 line configuration

Router(config-ctrlr-sts1)#vtg 1 t1 1 chan 0 tim 1 - 3

Router(config-ctrlr-sts1)#vtg 2 t1 4 chan 0 tim 1 - 2, 5-6

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

<1-4> t1 line number <1-4>

Configures the T1s on the vtgs. For SONET framing, vtg# range is 1 to 7.

Step 9

Channelized OC-3: vtg <vtg#>...

ct3: no prefix

There is no channelized E3 mode.

The e1# range is from 1 to 3

The t1# range is from 1 to 4.

For PDH mode, where a channelized t3 is mapped into the sts-1, the t1# range is from 1 to 28.

Configures channels. Once TUG-3/STS-1 is configured, then one of the parser modes config-ctrlr-{tug3|au3|sts1} can be set.

SDH mode Configuration

To configure SDH mode, complete the following steps:

Command

Purpose

Step 1

For SDH controllers:

Router(config-controller)# framing {sonet | sdh}

Selects the framing type.

•sonet—Specifies SONET as the frame type. This is the default.

•sdh—Specifies sdh as the frame type.

Step 2

Router(config-controller)# aug mapping {au-3 | au-4}

Configures AUG mapping for SDH only. If the AUG mapping is configured to be au-4, then the following muxing/alignment/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/mapping will be used:

VC-3 <--> AU-3 <--> AUG

This command will be available only when sdh framing is configured.

Default is au-4.

Step 3

If AUG mapping is au-4:

au-4 <au-4#> tug-3 <tug-3#>

If AUG mapping is au-3:

au-3 <au-3#>

Configures TUG-3/AU-3/STS-1. Depending on the framing mode of Sonet or SDH, each STS-1 and each TUG-3/AU-3 of a STM-1 can be configured with this command.

Depending on currently configured AUG mapping setting, this command will further specify TUG-3, AU-3 or STS-1 muxing. As result, the CLI command parser will enter into config-ctrlr-tug3, config-ctrlr-au3 or config-ctrlr-sts1 parser mode, which will make only relevant commands visible.

The au-4# is 1.

The tug-3# range is from 1 to 3.

The au-3# range is from 1 to 3.

The sts-1# is from 1 to 3.

Step 4

In SDH framing in AU-4 mode:

[no] mode {c-12 | t3 | e3}

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.

•c-12—Specifies a AU-4/TUG-3 is divided into 7 tug2. Each tug2 then divided into 3 TU12's, each carrying an E1 (C-12).

•c-11—Specifies a AU-3 is divided into 7 tug2. Each tug2 then divided into 4 TU11's, each carrying a T1 (C-11).

•t3—Specifies a STS-1 or AU-4/TUG3 carries a unchannelized (clear channel) T3

•e3—Specifies a AU-4/TUG3 carries a unchannelized (clear channel) E3

Configure Channelized DS3

To configure channelized DS3 mode, complete the following steps:

Command

Purpose

Step 1

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

Select the controller to configure and enter controller configuration mode.

•slot/subslot/port—Specifies the location of the interface. See the: "Selection of Physical Port and Controller Configuration" section

Step 2

Router(config)#sts-1 sts1-#

The sts-1# is from 1 to y, y being the Sonet STS level, such as in OC-3.

Step 3

Router(config)# t3 framing {c-bit | m23 | auto-detect}

Specifies framing mode.

•c-bit—Specifies C-bit parity framing.

•m23—Specifies M23 framing.

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

Step 4

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

Sets the clock source.

Note The clock source is set to internal if the opposite end of the connection is set to line and the clock source is set to line if the opposite end of the connection is set to internal.

•internal—Specifies that the internal clock source is used.

•line—Specifies that the network clock source is used.

Step 5

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

Enables or disables loopback mode on a SONET controller.

•local loopback—loops data from the transmit path to the receive path.

•network loopback—loops data received on the external port to the transmit path and back out the external port.

•Remote loopback—Applicable only to c-bit framing.

Default is no loopback.

Step 6

[no] t3 mdl string [eic | fic | generator | lic | pfi | port | unit} string

[no] t3 mdl transmit {path | idle-signal | test-signal}

Configures MDL support.

•eic—Specified equipment ID code

•fic— frame ID code

•generator—generator number in MDL test signal

•lic—location ID code

•pfi—facility ID code in MDL path message

•port— port number in MDL idle string message

•unit—unit code

Default is no mdl string and no mdl transmit.

Step 7

t3 equipment {customer | network} loopback

Equipment customer loopback enables the port to honor remote loopback request. Equipment network loopback disables this functionality.

Note Remote loopbacks are only available in c-bit framing mode.

Step 8

t3 bert pattern pattern interval 1-14400

Enables BERT testing.

POS Interface Configuration

To configure the OC-3 or OC 12 POS interfaces, complete the following steps:

Command

Purpose

Step 1

CCAT POS Interface

sts-<num#> <interface range> pos

Example:

Router(config-controller)# sts-1 1 - 3 pos

VCAT POS Interface

mode pos

Example:

Router(config-crtlr-vcg)# mode pos

The first command creates a CCAT POS interface and the alternative command creates a VCAT POS interface

Step 2

[no] encap {hdlc |ppp | fr}

This command configures the encapsulation on the POS interface and sets it to the value hdlc, ppp or fr

Step 3

scramble {enable |disable}

This command enables or disables scrambling on the POS interface

Step 4

CRC {crc16 |crc32}

This command configures the CRC setting to crc16 or crc32 at both connected SPAs

Step 5

invert data

This command configures the Invert Data setting. This should be the same for both connected SPAs

Step 6

control packets

This command sets the configure-controller packets to a hi-priority queue

Use the show interface pos command to verify the POS configuration:

Router# sh int pos 5/1/0.1

Use the interface pos <slot>/<bay>/<port>: sts-<group> command to debug the POS configuration:

Router# interface pos 5/1/0.1:sts-1

Note NSTS-1 is the number of the first STS-1 on the POS interface. N = 1-12

DS1 Configuration (Channelized T3 mode)

To configure DS1 complete the following steps:

Step 1

[no] prefix t1 t1# clock source {internal | line}

Configures the clocking source.

Step 2

[no] prefix t1 t1# fdl ansi

Enables the one-second transmission of the remote performance reports via Facility Data Link (FDL) per ANSI T1.403
Note that without this command, FDL will run in ATT mode. ATT mode is not mutually exclusive or different from ANSI mode, ANSI mode is a super-set of ATT mode.

Step 3

[no] prefix t1 t1# framing {sf | esf}

[no] prefix t1 t1# yellow {detection | generation}

Enables detection and generation of DS1 yellow alarms

Step 4

[no] prefix t1 t1# shutdown

Step 5

[no] prefix t1 t1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64]

Note

Step 6

[no] prefix t1 t1# loopback {local | network line | remote {line fdl {ansi | bellcore} | payload fdl ansi}}

Note Local network payload loopback is not supported due to TEMUX-84/TEMUX-84E limitations.

Note Only 6 E1 berts can be performed concurrently due to TEMUX-84/TEMUX-84E limitations.

E1 Configuration (Channelized T3/E3 mode)

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

Step 1

[no] prefix e1 e1# channel-group channel-group# timeslots list-of-timeslots speed [56 | 64]

Step 2

[no] prefix e1 e1# unframed

Step 3

[no] prefix e1 e1# [unframed | framing] {crc4 | no-crc4}

Step 4

[no] prefix e1 e1# clock source {internal | line}

Configures clock source.

Step 5

[no] prefix e1 e1# national bits pattern

Step 6

[no] prefix e1 e1# loopback [local | network]

Step 7

[no] prefix e1 e1# shutdown

BERT Test Configuration

To configure BERT test, complete the following:

Step 1

[no] [ [e1 | t1] [e1# | t1#] bert pattern {2^11 | 2^15 || 2^20 QRSS } interval time

Send a BERT pattern on a DS1/E1 line.

Unchannelized E3 Serial Interface Configuration

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

Step 1

[no] dsu mode { cisco | digital-link | kentrox }

•cisco—Specifies cisco as the dsu mode.

•digital-link—Specifies Digital link as the dsu mode. Range is from 300-34010.

•kentrox—Specifies kentrox as the dsu mode. Range is 1000-24500, 34010.

Default is cisco.

Step 2

[no] dsu bandwidth number

Specifies the maximum allowed bandwidth in Kpbs.

Step 3

[no] scramble

Default is no scramble.

Step 4

[no] national bit {0 | 1}

Default is 0.

Step 5

[no] crc {16 | 32}

Default is 16 bit (CRC-CITT).

Step 6

[no] loopback {network | local | remote}

Step 7

[no] shutdown

Step 8

[no] bert pattern pattern interval 1-14400

An example of a valid pattern is {2^15 | 2^23 | 0s | 1s }.

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 APS

•Configuring MLFR

•Invert Data on the T1/E1 Interface

•Changing a Channel Group Configuration

•Configuring Multipoint Bridging

•Configuring Bridging Control Protocol Support

•FRF.12 Guidelines

•LFI Guidelines

•HW MLPPP LFI Guidelines

•FRF.12 LFI Guidelines

•Configuring QoS Features on Serial SPAs

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:

Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# interface serial

For addressing information, refer to the "Interface Naming" section.

Selects the interface to configure.

•slot/subslot/port:channel-group—Specifies the location of the interface.

Step 3

Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay}

Set the encapsulation method on the interface.

•hdlc—High-Level Data Link Control (HDLC) protocol for serial interface. This encapsulation method provides the synchronous framing and error detection functions of HDLC without windowing or retransmission. This is the default for synchronous serial interfaces.

•ppp—PPP (for serial interface).

•frame-relay—Frame Relay (for serial interface).

Step 4

Router(config-if)# crc {16 | 32}

Selects the CRC size in bits.

•16—16-bit CRC. This is the default

•32—32-bit CRC.

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:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface serial

For addressing information, refer to the "Interface Naming" section.

Selects the interface to configure.

•slot/subslot/port:channel-group—Specifies the location of the interface.

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.

Command

Purpose

Router# configure terminal

Enters global configuration mode.

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

See the "Interface Naming" section.

Selects the controller to configure.

•slot/subslot/port—Specifies the location of the controller.

Router(config-controller)# sts-1

If the framing format was configured for esf, configures the format used for Facility Data Link (FDL).

•ansi—Select ansi for FDL to use the ANSI T1.403 standard.

Router(config-controller)vtg 1 t1 1 fdl

•vtg—Specifies the vtg number

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 correspond 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:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface multilink group-number

Creates a multilink interface and enter multilink interface mode.

•group-number—The group number for the multilink bundle.

Router(config-if)# ip address address mask

Sets the IP address for the multilink group.

•address—The IP address.

•mask—The IP netmask.

Assign an interface to a Multilink Bundle

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

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface serial

For addressing information, refer to the "Interface Naming" section.

Selects the interface to configure and enters interface configuration mode.

Router(config-if)# encapsulation ppp

Enables PPP encapsulation.

Router(config-if)# multilink-group group-number

Assigns the interface to a multilink bundle.

•group-number—The multilink group number for the T1 or E1 bundle.

Router(config-if)# ppp multilink

Enables multilink PPP on the interface.

Repeat these commands for each interface you want to assign to the multilink bundle.

Configuring fragmentation size on an MLPPP Bundle (optional)

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

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface multilink

For addressing information, refer to the "Interface Naming" section.

Creates a multilink interface and enters multilink interface mode.

•group-number—The group number for the multilink bundle. Range 1-2147483647

Router(config-if)# ppp multilink fragment-delay delay

Sets the fragmentation size satisfying the configured delay on the multilink bundle.

•delay—delay in milliseconds

Disabling the fragmentation on an MLPPP Bundle (optional)

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

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface multilink group-number

Creates a multilink interface and enters multilink interface mode.

•group-number—The group number for the multilink bundle. Range 1-2147483647

Router(config-if)# no ppp multilink fragmentation

Disables the fragmentation on the multilink bundle.

Configuring APS

Automatic protection switching (APS) allows switchover of the channelized OC3/OC12 channels in the event of failure. APS refers to the mechanism of using a protect interface in the network as the backup for a working interface. When the working interface fails, the protect interface quickly assumes its traffic load. Depending on the configuration, the two circuits may be terminated in the same router, or in different routers.

MLPPP MR-APS switchover time on all serial SPAs that support PPP encapsulation and APS on the SIP 400 is enhanced in 12.2(33) SRD2 release. MLPPP APS switchover time on the Cisco 7600 platform is a combination of the time spent executing the software and the time required for LCP, IPCP negotiations by the newly forwarding MLP Bundle. In 12.2(33) SRD2, Cisco 7600 platform software is optimized to help faster MLPPP APS switchover time.

Further, to help reduce the LCP, IPCP negotiation time, the granularity of the ppp timeout retry command is also enhanced in 12.2(33)SRD2, to include millisecond values. The PPP timeout retry determines how long the PPP state machine for LCP waits for a response from the remote peer before transmitting the next configuration request packet. The first configuration request packet from the new active APS router is used by the APS unaware router to bring down the PPP sessions. The second configuration request packet from the new active APS router triggers LCP negotiation.

There is no change in the Default PPP timeout retry value (2secs). In SRD2 release, minimum supported configurable ppp timeout retry value is 255msec.

Note Configuring the PPP retry timeout to be 250ms increases the CPU load on the router but the faster PPP retry timeout speeds up the PPP re-negotiation to help the overall switchover time

The performance enhancement of PPP/MLPPP APS does not impact the original PPP/MLPPP scalability on Cisco 7600.

For more information about APS, refer to A Brief Overview of Packet Over SONET APS at the following URL:

http://www.cisco.com/en/US/tech/tk482/tk607/technologies_tech_note09186a0080093eb5.shtml

To configure the working interface, use the following command in interface configuration mode:

Command

Purpose

Router(config)# interface serial slot/subslot/port:channel-group

Selects the interface to configure and enters interface configuration mode.

slot/subslot/port:channel-group—Specifies the location of the interface.

Router(config-if)# aps working

Configures a channelized OC3/OC12 interface as a working APS interface

To remove the channelized interface as a working interface, use the no form of this command.

To configure the protect channelized interface, use the following command in interface configuration mode:

Command

Purpose

Router(config)# interface serial slot/subslot/port:channel-group

Selects the interface to configure and enters interface configuration mode.

slot/subslot/port:channel-group—Specifies the location of the interface.

Router(config-if)# aps protect

Configures a channelized OC3/OC12 serial interface as a protect APS interface

To revert the protect interfaceconfiguration on the channelized interface, use the no form of this command.

To configure the ppp timeout retry channelized interface, use the following command in interface configuration mode:

Command

Purpose

Router(config)# interface serial slot/subslot/port:channel-group

Selects the interface to configure and enters interface configuration mode.

slot/subslot/port:channel-group—Specifies the location of the interface.

Router(config-if)# ppp timeout retry <0-255> [<0-999>]

Configures the PPP Control Protocol retry timer on the channelized serial interface, in milliseconds

Note The msecs timer increases the load on the router and should not be used except for the APS retry timeout configuration.

Note This command is backward compatible with previous release trains up till12.2(33)SRC for the 1-Port Channelized OC-3/STM-1 SPA and up till 12.2(33)SRD for the 1-Port Channelized OC-12/STM-4 SPA.

To remove thetimeout retry configuration on the interface, use the no form of this command.

Verifying the APS Configuration

To verify the APS configuration or to determine if a switchover has occurred, use the show aps command.

The following is an example of the show aps command anda typical a configuration on the sonet controller for APS on 1-Port Channelized OC-12/STM-4 SPA and 1-Port Channelized OC-3/STM-1 SPA
Router#sh aps
SONET 3/0/0 APS Group 1: working channel 1 (Active)
Protect at 1.0.0.1
PGP timers (from protect): hello time=1; hold time=3
PGP timers (configured): hello time=1; hold time=3
SONET framing
Remote APS configuration: (null)
controller SONET 3/0/0
ais-shut
threshold sf-ber 3
framing sonet
clock source line
aps group 1
aps working 1
aps timers 1 3
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:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface mfr number

Configures a multilink Frame Relay bundle interface.

•number—The number for the Frame Relay bundle.

Router(config-if)# frame-relay multilink bid name

(Optional) Assigns a bundle identification name to a multilink Frame Relay bundle.

•name—The name for the Frame Relay bundle.

Note The bundle identification (BID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Assign an Interface to a Multilink Bundle

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

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface serial

For addressing information, refer to the "Interface Naming" section.

Selects the interface to assign.

Router(config-if)# encapsulation frame-relay mfr number [name]

Creates a multilink Frame Relay bundle link and associates the link with a bundle.

•number—The number for the Frame Relay bundle.

•name—The name for the Frame Relay bundle.

Router(config-if)# frame-relay multilink lid name

(Optional) Assigns a bundle link identification name with a multilink Frame Relay bundle link.

•name—The name for the Frame Relay bundle.

Note The bundle link identification (LID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Router(config-if)# frame-relay multilink hello seconds

(Optional) Configures the interval at which a bundle link will send out hello messages. The default value is 10 seconds.

•seconds—Number of seconds between hello messages sent out over the multilink bundle.

Router(config-if)# frame-relay multilink ack seconds

(Optional) Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message. The default value is 4 seconds.

•seconds—Number of seconds a bundle link will wait for a hello message acknowledgment before resending the hello message.

Router(config-if)# frame-relay multilink retry number

(Optional) Configures the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The default value is 2 tries.

•number—Maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment.

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:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)# interface serial

For addressing information, refer to the "Interface Naming" section.

Selects the serial interface.

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
 multilink-group 1
! 
.
Configuring Multipoint Bridging

Multipoint bridging (MPB) enables the connection of multiple ATM PVCs, Frame Relay PVCs, BCP ports, and WAN Gigabit Ethernet subinterfaces into a single broadcast domain (virtual LAN), together with the LAN ports on that VLAN. This enables service providers to add support for Ethernet-based Layer 2 services to the proven technology of their existing ATM and Frame Relay legacy networks. Customers can then use their current VLAN-based networks over the ATM or Frame Relay cloud. This also allows service providers to gradually update their core networks to the latest Gigabit Ethernet optical technologies, while still supporting their existing customer base.

For MPB configuration guidelines and restrictions and feature compatibility tables, see the "Configuring Multipoint Bridging" section on page 4-25 of Chapter 4, "Configuring the SIPs and SSC."

Configuring Bridging Control Protocol Support

The Bridging Control Protocol (BCP) enables forwarding of Ethernet frames over SONET networks and provides a high-speed extension of enterprise LAN backbone traffic through a metropolitan area. The implementation of BCP on the SPAs includes support for IEEE 802.1D, IEEE 802.1Q Virtual LAN (VLAN), and high-speed switched LANs.

For BCP configuration guidelines and restrictions and feature compatibility tables, see the "Configuring PPP Bridging Control Protocol Support" section on page 4-41 of Chapter 4, "Configuring the SIPs and SSC."

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:

Command

Purpose

Router# configure terminal

Enters global configuration mode.

Router(config)#

For addressing information, refer to the "Interface Naming" section.

Select the controller to configure and enter controller configuration mode.

Router(config-controller)# no channel-group t1 t1-number

Select the channel group you want to remove.

•t1 t1-number— channel-group number.

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.
The supported fragment sizes - 128, 256 and 512 - include the FRF and NLPID headers in addition to the payload.

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.

Configuring QoS Features on Serial SPAs

The SIPs and SPAs support many QoS features using modular QoS CLI (MQC) configuration. For information about the QoS features supported by the serial SPAs, see the "Configuring QoS Features on a SIP" section on page 4-73 of Chapter 4, "Configuring the SIPs and SSC."

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 Configuration Fundamentals Configuration Guide, Release 12.2 and Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 publications.

Verifying the Interface Configuration

Besides using the show running-configuration command to display your Cisco 7600 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 7600 SIP-200 installed in slot 2 of a Cisco 7600 series 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)
Configuration Tasks

This section describes common configurations for the 1-Port Channelized OC-3/STM-1 SPA on a Cisco 7600 series router. It contains procedures for the following configurations:

•Configuring CRTP

Configuring CRTP

For information on configuring cRTP, see Configuring Distributed Compressed Real-Time Protocol at the following URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800b75cd.html