Cisco IOS XR Interface and Hardware Component Configuration Guide, Release 3.6
Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on Cisco IOS XR Software
Downloads: This chapterpdf (PDF - 619.0KB) The complete bookPDF (PDF - 4.93MB) | Feedback

Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on Cisco IOS XR Software

Table Of Contents

Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on Cisco IOS XR Software

Contents

Prerequisites for Configuring T3/E3 Controllers

Information About T3/E3 Controllers and Serial Interfaces

Default Configuration Values for T3 and E3 Controllers

Default Configuration Values for T1 Controllers

Default Configuration Values for E1 Controllers

How to Configure Clear Channel T3/E3 Controllers and Channelized T1/E1 Controllers

Setting the Card Type for the Clear Channel SPAs

Prerequisites

Restrictions

Configuring a Clear Channel E3 Controller

Prerequisites

Restrictions

What to Do Next

Modifying the Default E3 Controller Configuration

Prerequisites

What to Do Next

Configuring a Clear Channel T3 Controller

Prerequisites

Restrictions

What to Do Next

Configuring a Channelized T3 Controller

What to Do Next

Modifying the Default T3 Controller Configuration

Prerequisites

What to Do Next

Configuring a T1 Controller

Prerequisites

Restrictions

What to Do Next

Configuring an E1 Controller

Prerequisites

Restrictions

What to Do Next

Configuring BERT

Configuring BERT on T3/E3 and T1/E1 Controllers

Prerequisites

Configuring BERT on a DS0 Channel Group

Prerequisites

Examples

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance


Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on Cisco IOS XR Software


This module describes the configuration of clear channel T3/E3 controllers and channelized T3 controllers on routers supporting Cisco IOS XR software. You must configure the T3/E3 controller before you can configure an associated serial interface.

Feature History for Configuring T3/E3 Controller Interfaces

Release
Modification

Release 3.3.0

This feature was introduced on the Cisco XR 12000 Series Router.

Support was added on the Cisco XR 12000 Series Router for the following SIPS:

Cisco XR 12000 SIP-401

Cisco XR 12000 SIP-501

Cisco XR 12000 SIP-601

Support was added on the Cisco XR 12000 Series Router for the following SPAs:

2-Port and 4-Port Channelized T3 SPA

2-Port Clear Channel T3/E3 SPA

Release 3.4.0

No modifications.

Release 3.4.1

This feature was introduced on the Cisco CRS-1 for the 4-Port Clear Channel T3/E3 SPA.

Release 3.5.0

This feature was introduced on the Cisco XR 12000 Series Router for the Cisco 1-Port Channelized OC-12/DS0 shared port adapter.

Release 3.6.0

No modifications.


Contents

Prerequisites for Configuring T3/E3 Controllers

Information About T3/E3 Controllers and Serial Interfaces

How to Configure Clear Channel T3/E3 Controllers and Channelized T1/E1 Controllers

Examples

Additional References

Prerequisites for Configuring T3/E3 Controllers

Before configuring T3/E3 controllers, be sure that the following tasks and conditions are met:

You must be in a user group associated with a task group that includes the proper task IDs for T3/E3 commands. Task IDs for commands are listed in Cisco IOS XR Interface and Hardware Component Command Reference.

If you are configuring a channelized T3 controller, you must be in a user group associated with a task group that includes the proper task IDs for T1/E1 commands. Task IDs for commands are listed in Cisco IOS XR Interface and Hardware Component Command Reference.

Your hardware must support T3/E3 controllers and serial interfaces. The following hardware supports T3/E3 controllers and serial interfaces in Cisco IOS XR Software Release 3.3:

2-Port and 4-Port Clear Channel T3/E3 SPAs

2-Port and 4-Port Channelized T3 SPAs


Note The 2-Port and 4-Port Channelized T3 SPAs can run in clear channel mode, or they can be channelized into 28 T1 or 21 E1 controllers.


Information About T3/E3 Controllers and Serial Interfaces

The 2-Port and 4-Port Clear Channel T3/E3 SPAs support clear channel services over serial lines only. The 2-Port and 4-Port Channelized T3 SPAs supports clear channel services and channelized serial lines.

If a controller is not channelized, then it is a clear channel controller, and the full bandwidth of its associated serial line is dedicated to a single channel that carries serial services.


Note In this release, only T3-to-T1/E1 channelization is supported.


When a T3 controller is channelized, it is logically divided into smaller bandwidth T1 or E1 controllers, depending on which mode of channelization you select. The sum of the bandwidth of the serial interfaces on the T1 or E1 controllers cannot exceed the bandwidth of the T3 controller that contains those channelized T1 or E1 controllers.

When you channelize a T3 controller, each individual T1 or E1 controller is automatically further channelized into DS0 time slots. A single T1 controller carries 24 DS0 time slots, and a single E1 controller carries 31 DS0 time slots. Users can divide these DS0 time slots up into individual channel groups. Each channel group can support a single serial interface.

When a controller is channelized, and channel groups have been created, services are provisioned on the associated serial interfaces.

The channelization feature in this release allows the following types of channelization:

a single T3 controller into 21 E1 controllers, for a total controller size of 44210 kbps.

a single E3 controller into 16 E1 controllers, for a total controller size of 34010 kbps.

a single T1 controller supports up to 1.536 MB.

a single E1 controller supports up to 2.048 MB.


Note A single shared port adapter (SPA) can support up to 448 channel groups.


Configuring a channelized T3 controller and its associated serial interfaces is a 4-step process:


Step 1 Configure the T3 controller, and set the mode for that controller to T1 or E1.

Step 2 Configure the T1 or E1 controller.

Step 3 Create channel groups and assign DS0 time slots to these channel groups as desired.

Step 4 Configure the serial interfaces that are associated with the individual channel groups, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.


Default Configuration Values for T3 and E3 Controllers

Table 1 describes the default configuration parameters that are present on the T3 and E3 controllers.

Table 1 T3 and E3 Controller Default Configuration Values

Parameter
Default Value
Configuration File Entry

Frame type for the data line

For T3: C-bit framing

For E3: G.751

framing {c-bit | m23}

Clocking for individual T3/E3 links

internal

clock source {internal | line}

Cable length

224 feet

cablelength feet

Maintenance data link (MDL) messages

(T1 only)

disable

mdl transmit {idle-signal | path | test-signal} {enable | disable}

National reserved bits for an E3 port

(E3 only)

enable, and the bit pattern value is 1.

national bits {disable | enable}



Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.


Default Configuration Values for T1 Controllers

Table 2 describes the default configuration parameters that are present on the T1 controllers.

This line prevents blank table in PDF.

Table 2 T1 Controller Default Configuration Values

Parameter
Default Value
Configuration File Entry

Frame type for the data line

Extended superframe (esf)

framing {sf | esf}

Detection and generation of T1 yellow alarms.

Yellow alarms are detected and generated on the T1 channel.

yellow {detection | generation} {disable | enable}

Clocking for individual T1 links

internal

clock source {internal | line}

Transmission of ANSI T1.403 once-per-second remote performance reports through Facility Data Link (FDL) for a T1 channel

enable

fdl ansi {enable | disable}



Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.


Default Configuration Values for E1 Controllers

Table 3 describes the default configuration parameters that are present on the E1 controllers.

Table 3 E1 Controller Default Configuration Values

Parameter
Default Value
Configuration File Entry

Frame type for the data line

Framing with CRC-4 error monitoring capabilities (crc).

framing {crc | no-crc | unframed

Clocking for individual T1 links

internal

clock source {internal | line}

National reserved bits for an E1 port

0 (which corresponds to 0x1f in hexadecimal format)

national bits bits



Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.


How to Configure Clear Channel T3/E3 Controllers and Channelized T1/E1 Controllers

The T3/E3 controllers are configured in the physical layer control element of the Cisco IOS XR software configuration space. This configuration is described in the following tasks:

Setting the Card Type for the Clear Channel SPAs

Configuring a Clear Channel E3 Controller

Modifying the Default E3 Controller Configuration

Configuring a Clear Channel T3 Controller

Configuring a Channelized T3 Controller

Modifying the Default T3 Controller Configuration

Configuring a T1 Controller

Configuring an E1 Controller

Configuring BERT

Setting the Card Type for the Clear Channel SPAs

By default, the 2-Port and 4-Port Clear Channel T3/E3 SPAs boot in T3 mode. If you want to use the card in E3 mode you must set the card type to be E3, as described in this procedure that follows.


Note The hw-module subslot card type command configures all ports on the SPA to be the same type.



Caution The SPA is automatically reset when the hw-module subslot card type command is committed.


Note You must set the card type on the 2-Port and 4-Port Clear Channel T3/E3 SPA only; the 2-Port and 4-Port Channelized T3 SPA runs in T3 mode only.


Prerequisites

If you have previously configured the interfaces on the 2-Port or 4-Port Clear Channel T3/E3 SPA, and now you want to change the card type, you must delete any previously defined T3/E3 controller and serial interface configurations. Use the no controller [t3|e3] and no interface serial commands to revert the controller and interface configurations to their defaults.

Restrictions

This task is applicable to 2-Port and 4-Port Clear Channel T3/E3 SPAs only.

SUMMARY STEPS

1. configure

2. hw-module subslot subslot-id cardtype {t3 | e3}

3. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

hw-module subslot subslot-id cardtype {t3 | e3}

Example:

RP/0/0/CPU0:router(config)# hw-module subslot 0/1/0 cardtype e3

Sets the serial mode for the SPA.

t3—Specifies T3 connectivity of 44,210 kbps through the network, using B3ZS coding. This is the default setting.

e3—Specifies a wide-area digital transmission scheme used predominantly in Europe that carries data at a rate of 34,010 kbps.

Step 3 

end

or

commit

Example:

RP/0/0/CPU0:router(config)# end

or

RP/0/0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring a Clear Channel E3 Controller

When an E3 controller is in clear channel mode, it carries a single serial interface.

The E3 controllers are configured using the E3 configuration mode.

Prerequisites

You must first use the hw-module subslot cardtype command to set the card to support E3.

Restrictions

If you configure an option that is not valid for your controller type, you receive an error when you commit the configuration.

A single SPA cannot support a mixture of T3 and E3 interfaces.

This task is applicable to 2-Port and 4-Port Clear Channel T3/E3 SPAs only.

SUMMARY STEPS

1. configure

2. controller e3 instance

3. mode serial

4. no shutdown

5. end
or
commit

6. show controllers e3 instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller e3 instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the E3 controller name in the notation rack/slot/module/port and enters E3 configuration mode.

Step 3 

mode serial

Example:

RP/0/0/CPU0:router(config-e3)# mode serial

Configures the mode of the port to be clear channel serial.

Note This step is required for the 2-Port and 4-Port Channelized T3 SPA only. The 2-Port and 4-Port Clear Channel T3/E3 SPA run in serial mode by default.

Step 4 

no shutdown

Example:

RP/0/0/CPU0:router(config-e3)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 5 

end

or

commit

Example:

RP/0/0/CPU0:router(config-e3)# end

or

RP/0/0/CPU0:router(config-e3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 6 

show controllers e3 instance

Example:

RP/0/0/CPU0:router# show controllers e3 0/1/0/0

(Optional) Displays information about the E3 controllers.

What to Do Next

Modify the default configuration that is running on the E3 controller you just configured, as described in the Modifying the Default E3 Controller Configuration section later in this module.

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Modifying the Default E3 Controller Configuration

This task explains how to modify the default E3 controller configuration, which is described in the Default Configuration Values for T3 and E3 Controllers section earlier in this chapter.

Prerequisites

You must configure a clear channel E3 controller, as described in the Configuring a Clear Channel E3 Controller section earlier in this module.

SUMMARY STEPS

1. configure

2. controller e3 instance

3. clock source {internal | line}

4. cablelength feet

5. framing {g751 | g832}

6. national bits {disable | enable}

7. no shutdown

8. end
or
commit

9. show controllers e3 instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller e3 instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the E3 controller name in the notation rack/slot/module/port and enters E3 configuration mode.

Step 3 

clock source {internal | line}

Example:

RP/0/0/CPU0:router(config-e3)# clock source internal

(Optional) Sets the clocking for individual E3 links.

Note The default clock source is internal.

Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.

Step 4 

cablelength feet

Example:

RP/0/0/CPU0:router(config-e3)# cablelength 250

(Optional) Specifies the distance of the cable from the router to the network equipment.

Note The default cable length is 224 feet.

Step 5 

framing {g751 | g832}

Example:

RP/0/0/CPU0:router(config-e3)# framing g832

(Optional) Selects the frame type for the E3 port. Possible E3 frame types are G.751 and G.832.

Note The default framing for E3 is G.751.

Step 6 

national bits {disable | enable}

Example:

RP/0/0/CPU0:router(config-e3)# national bits enable

(Optional) Enables or disables the 0x1F national reserved bit pattern on the E3 port.

Note The E3 national bit is enabled by default, and the bit pattern value is 1.

Step 7 

no shutdown

Example:

RP/0/0/CPU0:router(config-e3)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 8 

end

or

commit

Example:

RP/0/0/CPU0:router(config-e3)# end

or

RP/0/0/CPU0:router(config-e3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 9 

show controllers e3 instance

Example:

RP/0/0/CPU0:router# show controllers e3 0/1/0/0

(Optional) Displays information about the E3 controllers.

What to Do Next

Modify the default configuration that is running on the T3 controller you just configured, as described in the Modifying the Default T3 Controller Configuration section later in this module.

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Configuring a Clear Channel T3 Controller

When a T3 controller is in clear channel mode, it carries a single serial interface.

The T3 controllers are configured in the T3 configuration mode.

Prerequisites

You must use the hw-module subslot cardtype command to set the card to support T3, as described in the Setting the Card Type for the Clear Channel SPAs section on earlier in this module.

Restrictions

This task is applicable to 2-Port and 4-Port Clear Channel T3/E3 SPAs only.

If you configure an option that is not valid for your controller type, you receive an error when you commit the configuration.

A single SPA cannot support a mixture of T3 and E3 interfaces.

SUMMARY STEPS

1. configure

2. controller t3 instance

3. mode serial

4. no shutdown

5. end
or
commit

6. show controllers t3 instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller t3 instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the T3 controller name in the rack/slot/module/port notation and enters T3 configuration mode.

Step 3 

mode serial

Example:

RP/0/0/CPU0:router(config-t3)# mode serial

Configures the mode of the port to be clear channel serial.

Note This step is required for the 2-Port and 4-Port Channelized T3 SPA only. The 2-Port and 4-Port Clear Channel T3/E3 SPA run in serial mode by default.

Step 4 

no shutdown

Example:

RP/0/0/CPU0:router(config-t3)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 5 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t3)# end

or

RP/0/0/CPU0:router(config-t3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 6 

show controllers t3 instance

Example:

RP/0/0/CPU0:router# show controllers t3 0/1/0/0

(Optional) Displays information about the T3 controllers.

What to Do Next

Modify the default configuration that is running on the T3 controller you just configured, as described in the Modifying the Default T3 Controller Configuration section later in this module.

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Configuring a Channelized T3 Controller

The 2-Port and 4-Port Channelized T3 SPAs support channelization to T1, E1, and DS0. The steps in this section describe how to channelize a single T3 controller into 28 T1 controllers or 21 E1 controllers. Once you have created T1 or E1 controllers, you can further channelize those controllers into DS0 time slots, as described in the following sections:

Configuring a T1 Controller

Configuring an E1 Controller

Each individual T1 controller supports a total of 24 DS0 time slots, and each individual E1 controller supports a total of 31 DS0 time slots.


Note If you configure an option that is not valid for your controller type, you receive an error when you commit the configuration.


SUMMARY STEPS

1. configure

2. controller t3 instance

3. mode [t1 | e1]

4. no shutdown

5. end
or
commit

6. show controllers t3 instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller T3 instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the T3 controller name in the notation rack/slot/module/port and enters T3 configuration mode.

Step 3 

mode t1

Example:

RP/0/0/CPU0:router(config-t3)# mode t1

Sets the mode of the channelized controllers to be T1, and creates 28 T1 controllers.

Step 4 

no shutdown

Example:

RP/0/0/CPU0:router(config-t3)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 5 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t3)# end

or

RP/0/0/CPU0:router(config-t3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 6 

show controllers t3 instance

Example:

RP/0/0/CPU0:router# show controllers t3 0/1/0/0

(Optional) Displays information about the T3 controllers.

What to Do Next

Modify the default configuration that is running on the T3 controller you just configured, as described in the Modifying the Default T3 Controller Configuration section later in this module.

If you channelized your T3 controller into 28 T1 controllers, configure the T1 controllers and assign DS0 time slots to them, as described in the Configuring a T1 Controller module later in this document.

If you channelized your T3 controller into 21 E1 controllers, configure the E1 controllers and assign DS0 time slots to them, as described in the Configuring an E1 Controller module later in this document.

Modifying the Default T3 Controller Configuration

This task explains how to modify the default T3 controller configuration, which is described in the Default Configuration Values for T3 and E3 Controllers section earlier in this chapter.

Prerequisites

You must configure a clear channel or channelized T3 controller, as described in one of the following sections:

Configuring a Clear Channel T3 Controller

Configuring a Channelized T3 Controller

SUMMARY STEPS

1. configure

2. controller t3 instance

3. clock source {internal | line}

4. cablelength feet

5. framing {c-bit | m23}

6. mdl transmit {idle-signal | path | test-signal} {enable | disable}

7. mdl string {eic | fi | fic | gen-number | lic | port-number | unit} string

8. no shutdown

9. end
or
commit

10. show controllers t3 instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller T3 instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the T3 controller name in the notation rack/slot/module/port and enters T3 configuration mode.

Step 3 

clock source {internal | line}

Example:

RP/0/0/CPU0:router(config-t3)# clock source internal

(Optional) Sets the clocking for the T3 port.

Note The default clock source is internal.

Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.

Step 4 

cablelength feet

Example:

RP/0/0/CPU0:router(config-t3)# cablelength 250

(Optional) Specifies the distance of the cable from the router to the network equipment.

Note The default cable length is 224 feet.

Step 5 

framing {c-bit | m23}

Example:

RP/0/0/CPU0:router(config-t3)# framing c-bit

(Optional) Selects the frame type for the T3 port.

Note The default frame type for T3 is C-bit.

Step 6 

mdl transmit {idle-signal | path | test-signal} {enable | disable}

Example:

RP/0/0/CPU0:router(config-t3)# mdl transmit path enable

(Optional) Enables Maintenance Data Link (MDL) messages on the T3 port.

Note MDL messages are supported only when the T3 framing is C-bit parity.

Note MDL message are disabled by default.

Step 7 

mdl string {eic | fi | fic | gen-number | lic | port-number | unit} string

Example:

RP/0/0/CPU0:router(config-t3)# mdl fi facility identification code

(Optional) Specifies the values of the strings sent in the MDL messages.

Step 8 

no shutdown

Example:

RP/0/0/CPU0:router(config-t3)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 9 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t3)# end

or

RP/0/0/CPU0:router(config-t3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 10 

show controllers t3 instance

Example:

RP/0/0/CPU0:router# show controllers t3 0/1/0/0

(Optional) Displays information about the T3 controllers.

What to Do Next

If you configured a clear channel T3 controller, perform the following tasks:

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

If you channelized your T3 controller into 28 T1 controllers, configure the T1 controllers and assign DS0 time slots to them, as described in the Configuring a T1 Controller module later in this document.

If you channelized your T3 controller into 21 E1 controllers, configure the E1 controllers and assign DS0 time slots to them, as described in the Configuring an E1 Controller module later in this document.

Configuring a T1 Controller

A single T3 controller can be channelized into 28 T1 controllers, and each T1 controller can be further channelized into up to 24 DS0 time slots. This task describes how to configure an individual T1 controller and channelize it into individual DS0 timeslots. Perform this task after you channelize a T3 controller into 28 individual T1 controllers.

Prerequisites

You must have a 2-Port or 4-Port Channelized T3 SPA installed in your router.

You must configure a channelized T3 controller to run in T1 mode, as described in Configuring a Channelized T3 Controller section earlier in this module.

Restrictions

If you configure an option that is not valid for your controller type, you receive an error when you commit the configuration.

SUMMARY STEPS

1. show controllers t1 instance

2. configure

3. controller t1 instance

4. framing {sf | esf}

5. yellow {detection | generation} {disable | enable}

6. clock source {internal | line}

7. fdl ansi {enable | disable}

8. no shutdown

9. channel-group channel-group-number

10. timeslots range

11. speed kbps

12. exit

13. Repeat Step 9 through Step 12 to assign time slots to a channel group. Each controller can contain up to 24 time slots.

14. exit

15. Repeat Step 2 through Step 14 to assign more channel groups to a controller.

16. end
or
commit

DETAILED STEPS

Step 1 

show controllers t1 instance

Example:

RP/0/0/CPU0:router# show controllers t3 0/1/0/0

(Optional) Displays information about the T1controllers you created in Step 3.

Step 2 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 3 

controller t1 instance

Example:

RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/0

Enters T1 configuration mode.

Step 4 

framing {sf | esf}

Example:

RP/0/0/CPU0:router(config-t1)# framing esf

(Optional) Selects the frame type for the T1 data line:

sf—Superframe

esf—Extended super frame

Note The default frame type for T1 is Extended superframe (esf).

Step 5 

yellow {detection | generation} {disable | enable}

Example:

RP/0/0/CPU0:router(config-t1e1)# yellow detection enable

(Optional) Enables or disables the detection and generation of T1 yellow alarms.

Note Yellow alarms are detected and generated on the T1 channel by default.

Step 6 

clock source {internal | line}

Example:

RP/0/0/CPU0:router(config-t1e1)# clock source internal

(Optional) Sets the clocking for individual T1 links.

Note The default clock source is internal.

Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.

Step 7 

fdl ansi {enable | disable}

Example:

RP/0/0/CPU0:router(config-t1e1)# fdl ansi enable

(Optional) Enables the transmission of ANSI T1.403 once-per-second remote performance reports through Facility Data Link (FDL).

Note FDL ansi is enabled by default.

Step 8 

no shutdown

Example:

RP/0/0/CPU0:router(config-t1e1)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 9 

channel-group channel-group-number

Example:

RP/0/0/CPU0:router(config-t1)# channel-group 0

Creates a T1 channel group and enters channel group configuration mode for that channel group.

Step 10 

timeslots range

Example:

RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 7-12

Associates one or more DS0 time slots to a channel group and creates an associated serial subinterface on that channel group.

Range is from 1 to 24 time slots.

You can assign all 24 time slots to a single channel group, or you can divide the time slots among several channel groups.

Note Each individual T1 controller supports a total of 24 DS0 time slots.

Step 11 

speed kbps

Example:

RP/0/0/CPU0:router(config-t1e1-channel_group)# speed 64

(Optional) Specifies the speed of the DS0s in kilobits per second. Valid values are 56 and 64.

Note The default speed is 64 kbps.

Step 12 

exit

Example:

RP/0/0/CPU0:router(config-t1-channel_group)# exit

Exits channel group configuration mode.

Step 13 

Repeat Step 9 through Step 12 to assign time slots to a channel group. Each controller can contain up to 24 time slots.

Step 14 

exit

Example:

RP/0/0/CPU0:router(config-t1)#

Exits T1 configuration mode and enters global configuration mode.

Step 15 

Repeat Step 2 through Step 14 to assign more 
channel groups to a controller as desired.

Step 16 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t3)# end

or

RP/0/0/CPU0:router(config-t3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

What to Do Next

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Configuring an E1 Controller

The 2-Port and 4-Port Channelized T3 SPAs support channelization to E1 controllers. A single T3 controller can be channelized into 21 E1 controllers, and each E1 controller can be further channelized into up to 31 DS0 timeslots.

Prerequisites

You must configure a channelized T3 controller to run in E1 mode, as described in Configuring a Channelized T3 Controller section earlier in this module.

Restrictions

If you configure an option that is not valid for your controller type, you receive an error when you commit the configuration.

SUMMARY STEPS

1. show controllers t1 instance

2. configure

3. controller e1 instance

4. clock source {internal | line}

5. framing {crc | no-crc | unframed}

6. national bits bits

7. no shutdown

8. channel-group channel-group-number

9. timeslots range

10. speed kbps

11. exit

12. Repeat Step 8 through Step 11 to assign time slots to a channel group. Each controller can contain up to 24 time slots.

13. exit

14. Repeat Step 2 through Step 13 to assign more channel groups to a controller as desired.

15. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show controllers e1 instance

Example:

RP/0/0/CPU0:router# show controllers e1 0/1/0/0

(Optional) Displays information about the E1controllers.

Step 2 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 3 

controller e1 instance

Example:

RP/0/0/CPU0:router(config)# controller e1 0/3/0/0/0

Enters E1 configuration mode.

Step 4 

clock source {internal | line}

Example:

RP/0/0/CPU0:router(config-e1)# clock source internal

(Optional) Sets the clocking for individual E1 links.

Note The default clock source is internal.

Note When configuring clocking on a serial link, you must configure one end to be internal, and the other end to be line. If you configure internal clocking on both ends of a connection, framing slips occur. If you configure line clocking on both ends of a connection, the line does not come up.

Step 5 

framing {crc | no-crc | unframed}

Example:

RP/0/0/CPU0:router(config-e1)# framing unframed

(Optional) Selects the frame type for the E1 data line. The following frame types are valid for E1:

crc—framing with CRC-4 error monitoring capabilities

no-crc—framing without CRC

unframed—unframed E1

Note The default frame type for E1 is crc.

Step 6 

national bits bits

Example:

RP/0/0/CPU0:router(config-e1)# national bits 10

(Optional) Specifies the national reserved bits for an E1 port. Range is from 0 to 31.

Note The default bit pattern is 0, which corresponds to the hexadecimal value 0x1f.

Step 7 

no shutdown

Example:

RP/0/0/CPU0:router(config-e1)# no shutdown

Removes the shutdown configuration.

The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or a down state.

Step 8 

channel-group channel-group-number

Example:

RP/0/0/CPU0:router(config-e1)# channel-group 0

Creates an E1 channel group and enters channel group configuration mode for that channel group.

Step 9 

timeslots range

Example:

RP/0/0/CPU0:router(config-e1-channel_group)# timeslots 1-16

Associates one or more time slots to a channel group and creates an associated serial subinterface on that channel group.

Range is from 1 to 31 time slots.

You can assign all 31 time slots to a single channel group, or you can divide the time slots among several channel groups.

Note Each E1 controller supports a total of 31 DS0 time slots.

Step 10 

speed kbps

Example:

RP/0/0/CPU0:router(config-e1-channel_group)# speed 100

(Optional) Specifies the speed of the DS0s in kilobits per second. Valid values are 56 and 64.

Note The default speed is 64 kbps.

Step 11 

exit

Example:

RP/0/0/CPU0:router(config-e1-channel_group)# exit

Exits channel group configuration mode

Step 12 

Repeat Step 8 through Step 11 to assign time slots to a channel group.

Step 13 

exit

Example:

RP/0/0/CPU0:router(config-e1)# exit

Exits E1 configuration mode

Step 14 

Repeat Step 2 through Step 13 to assign more channel groups to a controller as desired.

Step 15 

end

or

commit

Example:

RP/0/0/CPU0:router(config-e3)# end

or

RP/0/0/CPU0:router(config-e3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

What to Do Next

Configure a bit error rate test (BERT) on the controller to test its integrity, as described in the Configuring BERT section later in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Configuring BERT

Bit error rate testing (BERT) is supported on each of the T3/E3 or T1/E1 controllers, and on the DS0 channel groups. It is done only over an unframed T3/E3 or T1/E1 signal and is run on only one port at a time. It is also supported on individual channel groups.

To view the BERT results, use the show controllers t1 or show controllers t3 command in EXEC mode. The BERT results include the following information:

Type of test pattern selected

Status of the test

Interval selected

Time remaining on the BER test

Total bit errors

Total bits received

BERT is data intrusive. Regular data cannot flow on a line while the test is in progress. The line is put in an alarm state when BERT is in progress and restored to a normal state after BERT has been terminated.

Configuring BERT on T3/E3 and T1/E1 Controllers

This task explains how to enable a bit error rate test (BERT) pattern on a T3/E3 or T1/E1 line or an individual channel group.

Prerequisites

You must have configured a clear channel T3/E3 controller, or a channelized T3-to-T1/E1 controller.

SUMMARY STEPS

1. configure

2. controller [t3 | e3 | t1 | e1] instance

3. bert pattern pattern

4. bert interval time

5. bert error [number]

6. end
or
commit

7. exit

8. exit

9. bert [t3 | e3 | t1 | e1] instance [channel-group channel-group-number] [error] start

10. bert [t3 | e3 | t1 | e1] instance [channel-group channel-group-number] stop

11. show controllers [t3 | e3 | t1 | e1] instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller [t3 | e3 | t1 | e1] instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the controller name and instance in the notation rack/slot/module/port, and enters T3, E3, T1, or E1 controller configuration mode.

Step 3 

bert pattern pattern

Example:

RP/0/0/CPU0:router(config-t3)# bert pattern 2^15

Enables a specific bit error rate test (BERT) pattern on a controller. Valid patterns include: 0s, 1s, 2^15 2^20, 2^20-QRSS, 2^23, alt-0-1. and none.

Note You must use the bert command in EXEC mode to start the BER test.

Step 4 

bert interval time

Example:

RP/0/0/CPU0:router(config-t3)# bert pattern 2^15

(Optional) Specifies the duration of a bit error rate test (BERT) pattern on a T3/E3 or T1/E1 line. The interval can be a value from 1 to 14400.

Step 5 

bert error [number]
Example:

RP/0/0/CPU0:router(config-t3)# bert error 10

Specifies the number of BERT errors to introduce into the bit stream. Range is from 1 to 255.

Step 6 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t3)# end

or

RP/0/0/CPU0:router(config-t3)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 7 

exit
Example:

RP/0/0/CPU0:router(config-t3)# exit

Exits T3/E3 or T1/E1 controller configuration mode.

Step 8 

exit
Example:

RP/0/0/CPU0:router(config)# exit

Exits global configuration mode.

Step 9 

bert [t3 | e3 | t1 | e1] instance 
[channel-group channel-group-number] [error] 
start
Example:

RP/0/0/CPU0:router# bert t3 0/3/0/0 error start

Starts the configured BERT test on the specified T3/E3 or T1/E1 controller.

Note For T3/E3 controllers, you can include the optional error keyword to inject errors into the running BERT stream. The error keyword is not available on T1/E1 interfaces.

Step 10 

bert [t3 | e3 | t1 | e1] instance 
[channel-group channel-group-number] stop
Example:

RP/0/0/CPU0:router# bert t3 0/3/0/0 stop

Stops the configured BERT test on the specified T3/E3 or T1/E1 controller.

Step 11 

show controllers [t3 | e3 | t1 | e1] instance
Example:

RP/0/0/CPU0:router# show controllers t3 0/3/0/0

Displays the results of the configured BERT.

What to Do Next

Configure the serial interfaces that are associate with the controllers you tested, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Configuring BERT on a DS0 Channel Group

This task explains how to enable a bit error rate test (BERT) pattern on a an individual DS0 channel group.

Prerequisites

You must have configured a clear channel T3/E3 controller, or a channelized T3-to-T1/E1 controller.

SUMMARY STEPS

1. configure

2. controller [t1| e1] instance

3. channel-group channel-group-number

4. bert pattern pattern

5. bert interval time

6. end
or
commit

7. exit

8. exit

9. exit

10. bert [t1| e1] instance start

11. bert [t1| e1] instance stop

12. show controllers [t1| e1] instance

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller [t1 | e1] instance

Example:

RP/0/0/CPU0:router(config)# controller t3 0/1/0/0

Specifies the controller name and instance in the notation rack/slot/module/port, and enters T1 or E1 controller configuration mode.

Step 3 

channel-group channel-group-number
Example:

RP/0/0/CPU0:router(config-t1)# channel-group 1

RP/0/0/CPU0:router(config-t1-channel_group)#

Enters channel group configuration mode for a specific channel group. Replace channel-group-number with the number that identifies the channel group on which you want to configure a BERT.

Step 4 

bert pattern pattern

Example:

RP/0/0/CPU0:router(config-t1-channel_group)# bert pattern 2^15

Enables a specific bit error rate test (BERT) pattern on a T3 line. Valid patterns include: 0s, 1s, 2^15 2^20, 2^20-QRSS, 2^23, alt-0-1. and none.

Note You must use the bert command in EXEC mode to start the BER test.

Step 5 

bert interval time

Example:

RP/0/0/CPU0:router(config-t1-channel_group)# bert pattern 2^15

(Optional) Specifies the duration of a bit error rate test (BERT) pattern on a T3/E3 or T1/E1 line. The interval can be a value from 1 to 14400.

Step 6 

end

or

commit

Example:

RP/0/0/CPU0:router(config-t1-channel_group)# end

or

RP/0/0/CPU0:router(config-t1-channel_group)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 7 

exit
Example:

RP/0/0/CPU0:router(config-t1-channel_group)# exit

Exits channel group configuration mode.

Step 8 

exit
Example:

RP/0/0/CPU0:router(config-t1)# exit

Exits T1 or E1 configuration mode.

Step 9 

exit
Example:

RP/0/0/CPU0:router(config)# exit

Exits global configuration mode.

Step 10 

bert [t1 | e1] instance channel-group 
channel-group-number start
Example:

RP/0/0/CPU0:router# bert t1 0/3/0/0/0 error start

Starts the configured BERT test on the specified channel group.

Step 11 

bert [t1 | e1] instance channel-group 
channel-group-number stop
Example:

RP/0/0/CPU0:router# bert t1 0/3/0/0/0 stop

Stops the configured BERT test on the specified channel group.

Step 12 

show controllers [t1 | e3] instance
Example:

RP/0/0/CPU0:router# show controllers t3 0/3/0/0

Displays the results of the configured BERT.

What to Do Next

Configure the serial interfaces that are associate with the controllers you tested, as described in the Configuring Serial Interfaces on Cisco IOS XR Software module later in this document.

Examples

The following example shows configuration for a clear channel T3 controller:

RP/0/0/CPU0:router# configure
RP/0/0/CPU0:router(config)#controller T3 0/3/2/0
RP/0/0/CPU0:router(config-t3)#clock source internal
RP/0/0/CPU0:router(config-t3)#mode serial
RP/0/0/CPU0:router(config-t3)#cablelength 4
RP/0/0/CPU0:router(config-t3)#framing c-bit
RP/0/0/CPU0:router(config-t3)#commit
RP/0/0/CPU0:router(config-t3)#
 
   

The following example shows how to configure a T3 controller that has been channelized 28 T1 controllers:

RP/0/0/CPU0:router# configure
RP/0/0/CPU0:router(config)# controller T3 0/3/0/0
RP/0/0/CPU0:router(config-t3)# mode t1
RP/0/0/CPU0:router(config-t3)# framing m23
RP/0/0/CPU0:router(config-t3)# cablelength 11
RP/0/0/CPU0:router(config-t3)# clock source line
RP/0/0/CPU0:router(config-t3)#commit
RP/0/0/CPU0:router(config-t3)#exit
RP/0/0/CPU0:router(config)# exit
RP/0/0/CPU0:router#show controllers T1 ?
 
   
  0/3/0/0/0   T1 Interface Instance
  0/3/0/0/1   T1 Interface Instance
  0/3/0/0/10  T1 Interface Instance
  0/3/0/0/11  T1 Interface Instance
  0/3/0/0/12  T1 Interface Instance
  0/3/0/0/13  T1 Interface Instance
  0/3/0/0/14  T1 Interface Instance
  0/3/0/0/15  T1 Interface Instance
  0/3/0/0/16  T1 Interface Instance
  0/3/0/0/17  T1 Interface Instance
  0/3/0/0/18  T1 Interface Instance
  0/3/0/0/19  T1 Interface Instance
  0/3/0/0/2   T1 Interface Instance
  0/3/0/0/20  T1 Interface Instance
  0/3/0/0/21  T1 Interface Instance
  0/3/0/0/22  T1 Interface Instance
  0/3/0/0/23  T1 Interface Instance
  0/3/0/0/24  T1 Interface Instance
  0/3/0/0/25  T1 Interface Instance
  0/3/0/0/26  T1 Interface Instance
  0/3/0/0/27  T1 Interface Instance
  0/3/0/0/3   T1 Interface Instance
  0/3/0/0/4   T1 Interface Instance
  0/3/0/0/5   T1 Interface Instance
 --More--
RP/0/0/CPU0:router(config)#
RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/0
RP/0/0/CPU0:router(config-t1)# channel-group 0
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 1-24
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# exit
RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/1
RP/0/0/CPU0:router(config-t1)# channel-group 0
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 1-24
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# exit
RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/2
RP/0/0/CPU0:router(config-t1)# channel-group 0
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 1-12
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# channel-group 1
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 13-24
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# exit
RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/3
RP/0/0/CPU0:router(config-t1)# channel-group 0
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 1-6
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# channel-group 1
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 7-12
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# channel-group 2
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 13-18
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1)# channel-group 3
RP/0/0/CPU0:router(config-t1-channel_group)# timeslots 19-24
RP/0/0/CPU0:router(config-t1-channel_group)# exit
RP/0/0/CPU0:router(config-t1-channel_group)#commit
 
   

The following example shows how to configure a BERT on a T3 controller, and then display the results of the BERT:

RP/0/0/CPU0:router# config
RP/0/0/CPU0:router(config)# controller t3 0/3/0/1
RP/0/0/CPU0:router(config-t3)# bert pattern 0s
 
   
Run bert from exec mode for the bert config to take effect
 
   
RP/0/0/CPU0:router(config-t3)#exit
RP/0/0/CPU0:router(config)# exit
 
   
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]
RP/0/0/CPU0:router#bert t3 0/3/0/1 start
 
   
 
   
RP/0/0/CPU0:router# bert t3 0/3/0/1 stop
 
   
 
   
RP/0/0/CPU0:router# show controllers t3 0/3/0/1
 
   
  T30/3/0/1 is up
  No alarms detected.
  MDL transmission is disabled
    EIC: , LIC: , FIC: , UNIT:
     Path FI:
     Idle Signal PORT_NO:
     Test Signal GEN_NO:
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
  Data in current interval (108 seconds elapsed):
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 1:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 2:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 3:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

The following example shows how to configure a BERT on a T1 controller, and then display the results of the BERT:

RP/0/0/CPU0:router# config
RP/0/0/CPU0:router(config)# controller t1 0/3/0/1
RP/0/6/CPU0:router(config-t1)#bert pattern ?
  0s         All 0's test pattern
  1in8       1 in 8 test pattern
  1s         All 1's test pattern
  2e15       2^15-1 O.151 test pattern
  2e20       2^20-1 O.153 test pattern
  2e20-QRSS  2^20-1 QRSS O.151 test pattern
  2e23       2^23-1 O.151 test pattern
  3in24      3 in 24 test pattern
  55Daly     55 Daly test pattern
  55Octet    55 Octect test pattern
  alt-0-1    Alternating 0's and 1's test pattern
  none       no pattern assigned
 
   

Controller output:

Bert Test on controller port : T10_13_2_0_1 
  BERT test result (running)
     Test Pattern : 2^23-1 O.151 test pattern, Status : Sync, Sync Detected : 1
     Interval : 15 minute(s), Time Remain : 900000 (ms)
     Bit Errors (since BERT started): 0 bits, 
     Bits Received (since BERT started): 1 Mbits
     Bit Errors (since last sync): 0 bits
     Bits Received (since last sync): 1 Mbits
 
   

The following example shows how to configure a channelized T1 controller:

RP/0/0/CPU0:router(config)#
RP/0/0/CPU0:router(config)# controller t1 0/3/0/0/0
RP/0/0/CPU0:router(config-t1)# channel-group 0
RP/0/6/CPU0:router(config-t1-channel_group)#bert pattern ?
  0s         All 0's test pattern
  1s         All 1's test pattern
  2e11       2^11-1(2047) O.151 test pattern
  2e15       2^15-1 O.151 test pattern
  2e20       2^20-1 O.153 test pattern
  2e20-QRSS  2^20-1 QRSS O.151 test pattern
  2e23       2^23-1 O.151 test pattern
  2e9        2^9-1(511) O.151 test pattern
  alt-0-1    Alternating 0's and 1's test pattern
  ds0-1      DS0 1 test pattern
  ds0-2      DS0 2 test pattern
  ds0-3      DS0 3 test pattern
  ds0-4      DS0 4 test pattern
 
   

Controller output:

 
  Bert Test on controller port : T10_13_2_0_1 
  BERT test result (stopped)
     Test Pattern : 2^23-1 O.151 test pattern, Status : stopped, Sync Detected : 1
     Interval : 15 minute(s), Time Remain : 0 (ms)
     Bit Errors (since BERT started): 0 bits, 
     Bits Received (since BERT started): 163 Mbits
     Bit Errors (since last sync): 0 bits
     Bits Received (since last sync): 163 Mbits
 
  Bert Test on channel group : 0, timeslots : 1-10
  BERT test result (running)
     Test Pattern : 2^09-1 test pattern/511, Status : Sync, Sync Detected : 1
     Interval : 15 minute(s), Time Remain : 900000 (ms)
     Bit Errors (since BERT started): 0 bits, 
     Bits Received (since BERT started): 18 Mbits
     Bit Errors (since last sync): 0 bits
     Bits Received (since last sync): 18 Mbits

Additional References

The following sections provide references related to T3/E3 and T1/E1 controllers.

Related Documents

Related Topic
Document Title

Cisco IOS XR master command reference

Cisco IOS XR Master Commands List

Cisco IOS XR interface configuration commands

Cisco IOS XR Interface and Hardware Component Command Reference

Initial system bootup and configuration information for a router using Cisco IOS XR software

Cisco IOS XR Getting Started Guide

Cisco IOS XR AAA services configuration information

Cisco IOS XR System Security Configuration Guide and
Cisco IOS XR System Security Command Reference

Information about configuring interfaces and other components on the Cisco CRS-1 from a remote Craft Works Interface (CWI) client management application

Cisco CRS-1 Series Carrier Routing System Craft Works Interface Configuration Guide


Standards

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.


MIBs

MIBs
MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature

To locate and download MIBs for selected platforms using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL:

http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


RFCs

RFCs
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.


Technical Assistance

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport