Cisco 10000 Series Router Line Card Configuration Guide - 8-Port Unchannelized E3/T3 Line Card Configuration [Cisco 10000 Series Routers]

Table Of Contents

8-Port Unchannelized E3/T3 Line Card Configuration

Software Support

Checking Hardware and Software Compatibility

Default Values

Naming Convention

Interface Syntax

Configuration Task Overview

Configuration Examples

Configuring an E3 Interface

Configuring a T3 Interface

Controller Configuration Commands

Cablelength Command

Clock Source Command

Controller Description Command

Controller dsx3mode Command

Shutdown Command

Interface Configuration Commands

Running a BER Test

Interface Description Command

Specifying DSU Mode

Specifying DSU Bandwidth

Creating a Subrate E3 or T3 Interface

Encapsulation Command

Equipment Loopback Command

Fallback-Clocking Command

Setting the Framing Type

Specifying the Idle-Character

Performing Loopback Tests

Entering MDL Messages

Setting the National Bit

Enabling Scrambling

8-Port Unchannelized E3/T3 Line Card Configuration

This chapter describes procedures for configuring the Cisco 10000 series 8-Port Unchannelized E3/T3 line card, hereafter known as the 8-Port Unchannelized E3/T3 line card.

The 8-Port Unchannelized E3/T3 line card provides Cisco 10000 series routers with eight E3 or T3 high-density unchannelized interface ports.

This chapter contains the following sections:

•Software Support

•Default Values

•Configuration Task Overview

•Controller Configuration Commands

•Interface Configuration Commands

Software Support

Table 15-1 shows the minimum Cisco IOS release on each release train that supports the 8-Port Unchannelized E3/T3 line card.

Table 15-1 8-Port Unchannelized E3/T3 Line Card Software Support

Required PRE

Minimum Cisco IOS Releases

PRE1

Cisco IOS Release 12.0(22)S and later releases of Cisco IOS 12.0S

PRE2

Cisco IOS Release 12.0(22)S and later releases of Cisco IOS 12.0S
Cisco IOS Release 12.0(20)ST and later releases of Cisco IOS Release 12.0ST
Cisco IOS Release 12.3(7)XI and later releases of Cisco IOS 12.3XI
Cisco IOS Release 12.2(28)SB and later releases of Cisco IOS 12.2SB

Checking Hardware and Software Compatibility

The PRE installed in the Cisco 10000 series router chassis must support the Cisco IOS software running on the router. Use the show version command to check the PRE version installed.

To see if a feature is supported by a Cisco IOS release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/pcgi-bin/Support/CompNav/Index.pl

This tool does not verify whether line cards within a system are compatible, but does provide the minimum Cisco IOS requirements for individual hardware line cards, modules, or options.

You must be a registered user on Cisco.com to access this tool.

Default Values

Table 15-2 lists default configuration values for the 8-Port Unchannelized E3/T3 line card. This table also includes default values and indicates whether or not you must invoke a corresponding value at the remote side Channel Service Unit/Data Service Unit (CSU/DSU).
Table 15-2 8-Port Unchannelized E3/T3 Line Card Parameters
Command Name

Default Value

Command Syntax

Remote CSU/DSU Setting

Common Controller Configuration Mode
cable length

450
cablelength feet
—
clock source

internal
clock source [line | internal]
At least one side set to internal
description

—
description string
—
dsx3mode

t3
[no] dxs3mode [e3 | t3]
Same
shutdown

no shutdown
[no] shutdown
—
T3 Interface Configuration Mode
bert

no bert
[no] bert pattern pattern interval time 
[unframed]
No
description

—
description string
—
dsu bandwidth

44,210
dsu bandwidth bandwidth
[no] bandwidth
Same
dsu mode

cisco
dsu mode [adtran | cisco | digilink | 
kentrox | larscom | verilink low-bit | 
verilink high-bit]
Same
encapsulation

hdlc
encapsulation [hdlc | ppp |frame-relay]
Same
equipment

customer
equipment [customer | network]loopback
Same
framing

auto-detect
framing [auto-detect | c-bit | m13]
Same
idle character

flags (0x7e)
idle character [flags | marks]
Same
loopback

no loopback
[no] loopback network [line | payload]
[no] loopback [local | remote]
No
mdl

no mdl
[no] mdl {transmit {idle-signal | path | 
test-signal} | string {eic | fic | 
generator | lic | pfi | port | unit} 
<string>}
Same
scramble

no scramble
[no] scramble
Same
shutdown

no shutdown
shutdown
—
E3 Interface Configuration Mode
bert

no bert
[no] bert pattern pattern interval time 
[unframed]
Same
description

—
description string
—
encapsulation

hdlc
encapsulation [hdlc | ppp |frame-relay]
Same
dsu bandwidth

34,368 kbps
[no] dsu bandwidth bandwidth
Same
dsu mode

cisco
[no] dsu mode [cisco | kentrox] 
Same
fallback-clocking

off
fallback-clocking on | off
Same
idle character

flags (0x7e)
idle character [flags | marks]
Same
loopback

no loopback local network line
[no] loopback network [line | payload]
[no] loopback [local | remote]
No
scramble

no scrambling
[no] scramble
Same
shutdown

no shutdown
shutdown
—
Naming Convention

The Cisco 10000 series router line cards use the extended slot naming convention to identify the line card slot, subslot, and port in commands. This convention uses the following format:
slot/subslot/port
Where:

•slot is the slot number of the installed the line card

•subslot is the subslot number of the line card (the subslot number for all full-height line cards is always 0)

•port is the number of the line card port

Interface Syntax

The following tables contain the line card syntax to configure 8-Port Unchannelized E3/T3 line card interfaces for the Cisco 10008 router and Cisco 10005 router chassis.

Note The dsx3 controller designation is a generic term that refers to both E3 and T3 type interfaces. A dsx3 interface controls the configuration and management of DS3 channels and characteristics.

Table 15-3 specifies the 8-Port Unchannelized E3/T3 line card interface syntax for the Cisco 10008 router 8-slot chassis.

Table 15-3 8-Port Unchannelized E3/T3 Line Card Interface Syntax for the Cisco 10008 Chassis

Configuration

Command

Slot

Subslot

Port Number

Controller

controller dsx3 slot/0/port

1 to 8/

0/

0 to 7

Interface T3 (DS3)

serialslot/0/port

1 to 8/

0/

0 to 7

Interface E3

serialslot/0/port

1 to 8/

0/

0 to 7

Table 15-4 specifies the 8-Port Unchannelized E3/T3 line card interface syntax for the Cisco 10005 router 5-slot chassis.

Table 15-4 8-Port Unchannelized E3/T3 Line Card Interface Syntax for the Cisco 10005 Chassis

Configuration

Command

Slot

Subslot

Port Number

Controller

controller dsx3 slot/0/port

1 to 5/

0/

0 to 7

Interface T3 (DS3)

serialslot/0/port

1 to 5/

0/

0 to 7

Interface E3

serialslot/0/port

1 to 5/

0/

0 to 7

Configuration Task Overview

You can configure each port of the 8-Port Unchannelized E3/T3 line card as a full-rate or subrate unchannelized E3 or T3 interface.

Note Subrate unchannelized interfaces use specific vendor DSU proprietary formats that limit interface bit rates to less than full-rate on an E3 or T3 serial interface line.

To configure an 8-Port Unchannelized E3/T3 line card interface:

1. Designate a port as a controller.

2. Configure the controller parameters and save the configuration to NVRAM.

3. Create a serial interface.

4. Specify the interface parameters for the interface and save the configuration to NVRAM.

Note Each time you change a port mode (from T3 to E3, or E3 to T3), the running configuration of the controller and interface of the changed port mode is erased. If you want to keep a configuration, you must save it before you change its mode.

Configuration Examples

This section contains examples to configure both full-rate and subrate E3 or T3 interfaces on the line card. You must be in privileged EXEC mode to designate, create, and configure an E3 or T3 controller and interface.

Tip To view available command parameters, type ? at the command line.

Configuring an E3 Interface

The following sample procedure describes how to create and configure an E3 interface on port 6 of the line card in slot 4.

Step 1 Enter global configuration mode and designate the port as a controller.
Router# configure terminal
Router(config)# controller dsx3 4/0/6
Step 2 Configure the port as a dsx3 e3 controller and save the configuration to NVRAM.
Router(config-controller)# dsx3mode e3
Router(config-controller)# end
Router# write
Step 3 Enter configuration interface mode and designate port 6 as the serial interface.
Router# configure terminal
Router(config)# interface serial 4/0/6
Step 4 Configure the E3 interface DSU parameters for the port as a full-rate or subrate interface:

a. Full-rate (default 34,368):
Router (config-if)# dsu mode cisco
Router (config-if)# 
b. Subrate (any value below 34,368):
Router (config-if)# dsu mode cisco
Router (config-if)# dsu bandwidth 16000
Step 5 Save the configuration to NVRAM.
Router(config-if)# end
Router# write
Configuring a T3 Interface

The following sample procedure describes how to create and configure a T3 interface on port 6 of the line card in slot 4.

Step 1 Enter global configuration mode and designate the port as a controller.
Router# configure terminal
Router(config)# controller dsx3 4/0/6
Step 2 Configure the port as a dsx3 t3 controller and save the configuration to NVRAM.
Router(config-controller)# dsx3mode t3
Router(config-controller)# end
Router# write
Step 3 Enter configuration interface mode and designate port 6 as the serial interface.
Router# configure terminal
Router(config)# interface serial 4/0/6
Step 4 Configure the T3 interface DSU parameters for the port as a full-rate or subrate interface:

a. Full-rate (default of 44,210):
Router (config-if)# dsu mode cisco
b. Subrate (any value below 44,210):
Router (config-if)# dsu mode cisco
Router (config-if)# dsu bandwidth 16000
Step 5 Save the configuration to NVRAM.
Router(config-if)# end
Router# write
Controller Configuration Commands

This section describes the 8-Port Unchannelized E3/T3 line card commands to modify and test an E3 or T3 controller. You must be in configuration-controller mode to modify an E3 or T3 controller.

Note Each time you change a port (from T3 to E3, or E3 to T3), the running configuration of the controller and interface of the changed port is erased. If you want to keep a configuration, you must save it before you change its port mode.

•Cablelength Command

•Clock Source Command

•Controller Description Command

•Controller dsx3mode Command

•Shutdown Command

Cablelength Command

The cablelength command improves signal strength for losses associated with lengthy cables. To specify the physical length of the interface cable between the near and far-end CSU/DSU devices, use the cablelength command in the following format:
[no] cablelength feet
Where feet is a number from 0 to 450.

The default value is 450 feet.

Use the no form of this command to restore the default cable length.

In the following example, the cable length is set to 120 feet:
Router(config)# controller dsx3 4/0/6
Router(config-controller)# cablelength 120
The following cable length distances take into consideration line buildout for E3 and T3 controllers:

Interface

Cable Length (feet)

Buildout

E3

0 to 224

no line buildout

E3

225 to 450

line buildout

T3

0 to 299

no line buildout

T3

300 to 450

line buildout

Clock Source Command

Use the clock source command to choose whether or not the transmitted clock is derived from the received clock or is generated by an internal clock source. In some cases a network configuration may require you to derive network synchronization from a remote master clock.

The clock source command is set in controller configuration mode using the following format:
clock source [internal | line]
Where:

•internal specifies that the internal clock source is used

•line specifies that the network clock source is used

The default is clock source internal.

In this example, the controller is instructed to use a line clock source.
Router(config)# controller dsx3 4/0/6
Router(config-controller)# clock source line
Caution Never configure both sides of an E3 or T3 link to the clock source line.

Controller Description Command

Use the description command to identify particulars about the controller. You can enter up 80 characters in your controller description string using the following format:
description string
In the following example, port 6 is labeled with a description to help identify it:
Router(config)# controller dsx3 4/0/6
Router(config-controller)# description "Company ABC; IP = 240.21.3.8"
Note The description command can also be used in interface mode (see "Interface Description Command" section).

Controller dsx3mode Command

Use the dsx3mode command to define the controller type as an E3 or T3 controller using the following format:
[no] dxs3mode [e3 | t3]
The default controller type is t3.

Use the no form of this command to remove the controller.
The following example shows how to define a T3 type controller:
Router(config)# controller dsx3 2/0/0
Router(config-controller)# dsx3mode t3
Shutdown Command

Use the shutdown command to shut down the controller and interface using the following format:
[no] shutdown
Use the no form of this command to restore the previously configured controller and interface.

•It takes 10 seconds for alarms to clear after issuing a no shut command on a T3 port. Shutting down a controller causes a T3 port to transmit:

–AIS (alarm indication signal, for m13 framing)

–An idle signal (for c-bit framing)

•There is no delay for alarms to clear after issuing a no shut command on an E3 port.

–Shutting down a controller causes an E3 port to transmit AIS.

Note The AIS (alarm indication signal), also called a blue alarm, is sent downstream to notify the downstream device that an upstream line failure has occurred.

In the following example, the controller on port 0 is shut down:
Router(config)# controller dsx3 1/0/0
Router(config-controller)# shutdown
Interface Configuration Commands

This section describes the following command procedures to modify and test E3 and T3 interfaces on the line card:

•Running a BER Test

•Interface Description Command

•Specifying DSU Mode

•Specifying DSU Bandwidth

•Encapsulation Command

•Equipment Loopback Command

•Fallback-Clocking Command

•Setting the Framing Type

•Specifying the Idle-Character

•Performing Loopback Tests

•Entering MDL Messages

•Setting the National Bit

•Enabling Scrambling

You must be in configuration interface mode to modify an E3 or T3 configuration, for example:
Router# configure terminal
Router(config)# interface serial 1/0/0
Router(config-if)#
Running a BER Test

You can configure an interface to run a BER test (bit error-rate test). The BER test checks network cables and isolates apparent signal problems in the field.

Before you begin a BER test, you need to set up a remote loopback from the far-end (remote) DSU/CSU. See "Performing Loopback Tests" section for additional information about configuring the loopbacks.

The following loopback commands cause the remote CSU/DSU to perform a full-bandwidth loopback through its CSU:

•loopback network line causes a loopback toward the network before going through the CSU/DSU framer.

•loopback network payload causes a loopback toward the network after going through the CSU/DSU framer.

To run a BER test pattern on an interface, use the following interface configuration command:
bert [errors number | pattern pattern] interval time
[no] bert
Where:

•errors number is 1 to 255

•pattern pattern is:

–0s—repetitive test pattern of all zeros (00000º)

–1s—repetitive test pattern of all ones (11111º)

–2^15—pseudo-random O.151 test pattern (32,768 bits in length)

–2^20-O153—pseudorandom O.153 test pattern (1,048,575 bits in length)

–2^23—test pattern

–alt-0-1—alternating 0s and 1s test pattern

–QRSS-2^20—pseudorandom QRSS O.151 test pattern (1,048,575 bits in length)

The default is no bert pattern test. Use the no form of this command to terminate a BER test.

For more information about BER testing, refer to the Cisco IOS Interface and Hardware Component Configuration Guide and the online Cisco 10000 Series Internet Router Troubleshooting Guide.

Example:

•Send a BERT pseudorandom pattern of 2^20 through T3 interface 1/0/0 for 5 minutes.
Router(config)# interface serial 1/0/0
Router(config-if)# bert pattern 2^20 interval 5
Interface Description Command

Use the description command to identify particulars about the interface. You can enter up 80 characters in your controller description string using the following format:
description string
In the following example, port 6 is labeled with a description to help identify it:
Router(config)# interface 4/0/6
Router(config-if)# description "Company ABC; IP = 240.21.3.8"
Note The description command can also be used in controller mode (see the "Controller Description Command" section).

Specifying DSU Mode

The dsu mode command configures the line card to emulate a manufacturer's proprietary multiplexing scheme. Be sure that the remote DSU connection at the far end is connected and set up as an identical E3 or T3 interface.

Note Only Cisco, Digital-Link, and Kentrox are supported on E3 interfaces.

Use the dsu mode command to specify a Data Service Unit (DSU) mode for a selected interface using the following format:
dsu mode [Adtran | cisco | digital-link | kentrox | larscom | verilink-highbit | 
verilink-lowbit]
[no] dsu mode 
The default DSU mode is cisco. Use the no form of the command to return the DSU mode to the default mode.

In the following example, the DSU mode is set to cisco:
Router(config)# interface serial 1/0/0
Router(config-if)# dsu mode cisco
Specifying DSU Bandwidth

Use the dsu bandwidth command to specify the full-rate or subrate bandwidth for an E3 or T3 interface using the following format:
dsu bandwidth bandwidth
[no] bandwidth
Where:

•bandwidth = 0 to 44210 kbps for a T3 interface

–The default value for a T3 interface is 44210 (full-rate)

•bandwidth = 0 to 34368 kbps for an E3 interface

–The default value for an E3 interface is 34368 (full-rate)

Use the no form of this command to return to the full-rate default values.

In the following example, the full-rate bandwidth for an E3 interface is set to 34368:
Router(config)# interface serial 2/0/0
Router(config-if)# dsu bandwidth 34368
Creating a Subrate E3 or T3 Interface

You can create a subrate E3 or T3 controller interface by specifying a bandwidth value that is less than full-rate for the near end DSU.

In the following example, the subrate dsu bandwidth for a T3 interface is set to 16000:
Router(config)# interface serial 4/0/6
Router(config-if)# dsu mode cisco
Router(config-if)# dsu bandwidth 16000 
Note When you specify a bandwidth, the software sets that bandwidth to the closest acceptable bandwidth value based on the time-slot size for the current DSU mode. See the Chapter 17, "Provisioning a Subrate E3 or T3 Interface" for information about bandwidth.

Encapsulation Command

Use the encapsulation command to specify the type of encapsulation for the interface using the following format:
encapsulation encapsulation-type
Where encapsulation-type is:

•frame-relay

•hdlc (serial HDLC synchronous)

•ppp (Point-to-Point Protocol)

The default encapsulation is hldc.

The following example sets the encapsulation type as ppp:
Router(config)# interface serial 4/0/6
Router(config-if)# encapsulation ppp
Equipment Loopback Command

Use the equipment loopback command to specify whether or not a T3 port for the near-end device will accept remote loopback requests from the far-end device.

Note Because remote loopback requests are available only when c-bit framing is invoked, the equipment loopback command is useful only when framing is set to c-bit or auto-frame-detect.
[no] equipment [customer | network] loopback
The default mode is customer.

Use the no form of this command to disable the equipment selection and revert back to auto-detect as the framing value (see Setting the Framing Type).

The following examples show how to the equipment loopback command:

Equipment Customer Loopback Command

When you invoke the equipment customer loopback command, the near-end T3 port accepts far-end loopback requests.
Router(config)# interface dsx3 1/0/0
Router(config-if)# equipment customer loopback
Note Specify equipment customer loopback as the equipment type, unless you want to block the far end from setting near-end loopbacks.

Equipment Network Loopback Command

When you invoke the equipment network loopback command, the near-end T3 port ignores far-end loopback requests.
Router(controller)# interface dsx3 1/0/0
Router(config-if)# equipment network loopback
Fallback-Clocking Command

Use the fallback-clocking command to force the setting on the master clock to internal on receipt of an AIS message. This command is used only for E3 serial interfaces.

Note We recommend that you use the fallback clock command only in countries in which regulations require it.

Use the fallback-clocking command using the following format:
[no] fallback-clocking [on | off]
The default is off.

Use the no form of this command to restore the E3 interface default, which causes the controller to revert back to programmed E3 clocking.

In the following example, the fallback-clocking is set to on.
Router(config-if)# interface dsx3 1/0/0
Router(config-if)# fallback-clocking on
Setting the Framing Type

Use the framing command to specify the framing type for the T3 interface using the following format:

[no] framing [auto-detect | c-bit | m13]

Where:

•auto-detect detects whether or not the far-end T3 line is currently using m13 or c-bit framing and automatically configures itself to match.

Note If the port detects that framing rapidly toggles between m13 and c-bit framing, the port forces m13 framing.

•c-bit specifies c-bit framing.

•m13 specifies m13 framing. m13 is a Cisco framing method that functions the same as m23 framing.

The default is no framing.

Use the no form of this command to restore the default auto-detect framing type.

In the following example, framing is set to m13:
Router(config)# interface serial 1/0/0 
Router(config-if)# framing m13
Specifying the Idle-Character

Use the idle-character command to set a specific character on the interface for transmission between HDLC packets using the following format:

[no] idle-character [flags | marks]

Where:

•flags sets an idle character of 0x7e

•marks sets an idle character of all 0xff

The default idle character is 0x7e.

Use the no form of this command to return the idle character to its default value.

In the following example, the idle character is set to flags (0x7e):
Router(config)# interface serial 1/0/0 
Router(config-if)# idle-character flags
Note Some systems interpret marks (0xff), as an abort signal. Therefore, the flags (0x7e) setting is preferred.

Performing Loopback Tests

Use the loopback command to assign an E3 or T3 interface into loopback test using the following format:
[no] loopback network [line | payload]
[no] loopback [local | remote]
Where:

•network line loops the data back to the network

•network payload loops the payload portion back to the network

•local loops the line card output data back toward the line card and sends an AIS message

•remote sends a far end alarm control (FEAC) request to the far-end (remote) device, requesting that it enter a network line loopback

Note A remote loopback test is possible only when the line is configured for c-bit framing.

The default is no loopback.

To cancel a loopback test, use the no form of the command.

In the following example, the loopback network is set to line:
Router(config)# dsx3 1/0/0 
Router(config-if)# network loopback line
See the Cisco IOS Interface and Hardware Component Configuration Guide, and the Cisco 10000 Series Internet Router Troubleshooting Guide for details about loopback testing.

Entering MDL Messages

Use the maintenance data link (MDL) message strings and codes to send messages in response to far-end inquiries.

Note MDL messages are supported only when the T3 framing is set to c-bit (see the "Setting the Framing Type" section.)

You can configure MDL messages (as defined in the ANSI T1.107a-1990 specification) on a T3 interface using the mdl command in the following format:
[no] mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | 
port | generator} id_string}
Where:

•transmit enables one of the following transmissions:

–path enables transmission of the MDL path message

–idle-signal enables transmission of the MDL idle-signal message

–test-signal enables transmission of the MDL test-signal message

•string enables one of the following identification codes:

–eic is the equipment identification code (up to 10 characters).

–lic is the location identification code (up to 11 characters).

–fic is the frame identification code (up to 10 characters).

–unit is the unit identification code (up to 6 characters).

–pfi is the facility identification code to include in the MDL path message
(up to 38 characters).

–port is the equipment port (which initiates the idle signal) to include in the MDL idle signal message (up to 38 characters).

–generator is the generator number to include in the MDL test signal message (up to 38 characters).

The default is no mdl message.

Use the no form of the command to remove an MDL message.

Examples of configuring MDL messages are:

•Enable the MDL path message transmission.
Router(config-controller)# mdl transmit path
•Enable the MDL idle signal message transmission.
Router(config-controller)# mdl transmit idle-signal
•Enable the MDL test signal message transmission.
Router(config-controller)# mdl transmit test-signal
•Enter the equipment identification code.
Router(config-controller)# mdl string eic router A
•Enter the location identification code.
Router(config-controller)# mdl string lic test network
•Enter the frame identification code.
Router(config-controller)# mdl string fic building b
•Enter the unit identification code.
Router(config-controller)# mdl string unit abc
•Enter the facility identification code.
Router(config-controller)# mdl string pfi string
•Enter the port number to send in the MDL idle signal message.
Router(config-controller)# mdl string port string
•Enter the generator number to send in the MDL test signal message.
Router(config-controller)# mdl string generator string
Setting the National Bit

Use the national bit command to set bit 12 in the E3 frame, using the following format:
[no] national bit [0 | 1]
The default is 0.

Use the no form of this command to return to the default bit.

In the following example, the national bit is set to 1 on an E3 interface:
Router(config)# interface serial 1/0/0
Router(config-if)# national bit 1
Enabling Scrambling

Scrambling can prevent some bit patterns from being mistakenly interpreted as alarms by switches placed between the DSUs. Use the scramble command to assist clock recovery on the receiving end using the following format:
[no] scramble
The default is no scramble.

In the following example, scrambling is enabled:
Router(config)# interface serial 1/0/0
Router(config-if)# scramble