Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Configuration Guide
Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on the Cisco ASR 9000 Series Router
Downloads: This chapterpdf (PDF - 435.0KB) The complete bookPDF (PDF - 6.67MB) | Feedback

Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on the Cisco ASR 9000 Series Router

Table Of Contents

Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on the Cisco ASR 9000 Series Router

Contents

Prerequisites for Configuring T3/E3 Controllers

Information About T3/E3 Controllers and Serial Interfaces

Features Supported for Channelized T3 on the Cisco ASR 9000 Series Router

Default Configuration Values for T3 and E3 Controllers

Default Configuration Values for T1 and E1 Controllers

Link Noise Monitoring on T1 or E1 Links

LNM Events

LNM Logging

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

Configuring a Clear Channel E3 Controller

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

Prerequisites

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

Restrictions

Configuring BERT on a DS0 Channel Group

Prerequisites

Configuring Link Noise Monitoring on a T1 or E1 Channel

Prerequisites

Verifying Link Noise Monitoring Configuration and Status

Clearing Link Noise Monitoring States and Statistics

Configuration Examples

Configuring a Clear Channel T3 Controller: Example

Configuring a T3 Controller with Channelized T1 Controllers: Example

Configuring BERT on a T3 Controller: Example

Configuring Link Noise Monitoring on a T1 Controller: Example

QoS on T3 Channels: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance


Configuring Clear Channel T3/E3 Controllers and Channelized T3 Controllers on the Cisco ASR 9000 Series Router


This module describes the configuration of clear channel T3/E3 controllers and channelized T3 controllers on the Cisco ASR 9000 Series Aggregation Services Routers.

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.9.0

This feature was introduced on the Cisco ASR 9000 Series Router for the Cisco 2-Port Channelized OC-12c/DS0 SPA.

Release 4.0.0

Support for the following features was added on the Cisco 2-Port Channelized OC-12c/DS0 SPA:

NxDS0 channelization

Link Noise Monitoring

Support for clear channel T3 controllers on the 1-Port OC-48/STM-16 SPA was introduced.

Release 4.0.1

Support for the following SPAs was added on the Cisco ASR 9000 Series Router:

Cisco 1-Port Channelized OC-3/STM-1 SPA

Cisco 2-Port and 4-Port Clear Channel T3/E3 SPA


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

Configuration Examples

Additional References

Prerequisites for Configuring T3/E3 Controllers

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Before configuring T3/E3 controllers, be sure that you have one of the following supported SPAs installed in the router:

Cisco 2-Port and 4-Port Clear Channel T3/E3 SPA

Cisco 1-Port Channelized OC-3/STM-1 SPA

Cisco 2-Port Channelized OC-12c/DS0 SPA

Cisco 1-Port Channelized OC-48/STM-16 SPA

Before you can configure a clear channel T3 controller on the channelized SPAs, you must configure the SPA for an STS stream channelized for T3. For more information, see the "Configuring Channelized SONET/SDH on Cisco IOS XR Softwarethe Cisco ASR 9000 Series Router" module.

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. 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 28 T1 controllers, for a total controller size of 44210 kbps.

A single T3 controller into 21 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.


This section includes the following additional topics:

Features Supported for Channelized T3 on the Cisco ASR 9000 Series Router

Default Configuration Values for T3 and E3 Controllers

Default Configuration Values for T1 and E1 Controllers

Link Noise Monitoring on T1 or E1 Links

Features Supported for Channelized T3 on the Cisco ASR 9000 Series Router

Channelized T3 SONET on the Cisco ASR 9000 Series Router supports the following features:

DSU modes—Adtran, Digital-link, Cisco, Kentrox, Larscom, Verilink


Note Subrate configuration for the DSU modes is not supported for E3 on the Cisco 1-Port Channelized OC-48/STM-16 SPA.


PPP encapsulation

HDLC encapsulation

T3 channels on MR-APS SONET ports

48 T3 channels per SIP

24 T3 channels per SPA

12 T3 channels per interface

Sending and receiving at full wire rate on all 48 T3 channels

64 byte packets and larger

Equal Cost Multipath (ECMP)

ECMP support for egress paths over T3 or T1 speed channels with either PPP or HDLC encapsulation

ECMP support for paths on multiple controllers, SPAs, and SIPs

Support of intermixed T3 and T1 channels on the same SIP, SPA, or port

IC-SSO for PPP on T3 channels

IC-SSO for T1 when T3 channels are configured on the same system, SIP, SPA or port

Bit Error Rate Tests (BERT) on T3 channels

QoS on T3 channels

Loopback

Local loopback for T3 channels

Local line loopback for ports

Network line loopback for ports

Network line loopback for T3 channels

IP Fast Reroute (IP-FRR) for PPP only

XML support for all T3 related CLI configuration commands

Alarms

AIS

RAI

LOF

Idle

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 the Cisco ASR 9000 Series Router module later in this document.


Default Configuration Values for T3 and E3 Controllers

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


Note Auto-detect framing is not supported on the 2-Port Channelized OC-12c/DS0 SPA on the Cisco ASR 9000 Series Router.


Table 5 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 {auto-detect | 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

(T3 only)

disable

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

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 and E1 Controllers

Table 6 describes the default configuration parameters that are present on the T1 and E1 controllers.

Table 6 T1 and E1 Controller Default Configuration Values

Parameter
Default Value
Configuration File Entry

Frame type for the data line

For T1: extended superframe (esf)For E1: framing with CRC-4 error monitoring capabilities (crc4).

For T1: framing {sf | esf}For E1: framing {crc4 | no-crc4 | unframed

Detection and generation of T1 yellow alarms.

(T1 only)

Yellow alarms are detected and generated on the T1 channel.

yellow {detection | generation} {disable | enable}

Clocking for individual T1 and E1 links

internal

clock source {internal | line}

Cable length

(T1 only)

For cablelength long command: db-gain-value: gain26; db-loss-value: 0db.

For cablelength short command: 533 feet.

To set a cable length of longer than 655 feet: cablelength long db-gain-value db-loss-value

To set a cable length of 655 feet or shorter: cablelength short length

Transmission of ANSI T1.403 or AT&T TR54016 once-per-second performance reports through Facility Data Link (FDL) for a T1 channel

(T1 only)

disable

fdl {ansi | att} {enable | disable}

National reserved bits for an E1 port

(E1 only)

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.


Link Noise Monitoring on T1 or E1 Links

Link Noise Monitoring (LNM) provides the ability to monitor Path Code Violation (PCV) errors on T1 and E1 links on the 2-Port Channelized OC-12c/DS0 SPA on the Cisco ASR 9000 Series Router, and to signal events and alarms on these links when noise continuously meets or exceeds configured thresholds (the set threshold values) for those errors. Events are also signaled when noise falls below configured improved thresholds (the clear threshold values).


Note An LCV is an occurrence of either a Bi-Polar Violation (BPV) or Excessive Zeroes (EXZ) error, and a PCV is an occurrence of a CRC error in a timeslot. However, the LNM feature currently only monitors PCV errors. The LCV values are only used to calculate an expected PCV if the PCV values are not specified. If the PCV values are specified, then the LCV values are ignored.


LNM Events

There are two basic types of monitoring events produced by LNM:

Crossed events—A crossed event signals when PCV threshold values continuously meet or exceed the specified set values for major and minor warnings for a specified period of time (duration). When a crossed event occurs, the major or minor monitoring type for the controller is reported as the alarm state. When the crossed event is no longer present, the monitoring type returns to the stable state.

The following are examples of crossed events:

RP/0/RSP0/CPU0:Router#0/1/CPU0:May 13 9:54:10.980 : g_spa_1[181]: 
%L2-T1E1_LNM-3-MINWARNNOISE : 
Interface T10/1/1/0/1/1/1, noise crossed minor warning threshold
 
   
RP/0/RSP0/CPU0:Router#0/1/CPU0:May 13 9:54:11.980 : g_spa_1[181]: 
%L2-T1E1_LNM-3-MAJWARNNOISE : 
Interface T10/1/1/0/1/1/1, noise crossed major warning threshold
 
   

Cleared events—A cleared event signals when threshold values that were crossed have fallen below the specified clear values for major and minor warnings.

The following are examples of cleared events:

RP/0/RSP0/CPU0:Router#LC/0/1/CPU0:May 13 10:27:25.809 : g_spa_1[181]: 
%L2-T1E1_LNM-3-MAJWARNNOISE : 
Interface T10/1/1/0/1/1/1, noise cleared major warning threshold
 
   
RP/0/RSP0/CPU0:Router#LC/0/1/CPU0:May 13 10:28:14.810 : g_spa_1[181]: 
%L2-T1E1_LNM-3-MINWARNNOISE : 
Interface T10/1/1/0/1/1/1, noise cleared minor warning threshold

LNM Logging

When you enable syslog messages for LNM events using the lnm syslog command, LNM messages will appear in both the system log and in the log events buffer. You can display LNM events in the log events buffer using the show logging events buffer bistate-alarms-set command, and also using the show logging command, which are described in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Command Reference.

LNM supports hierarchical level alarm reporting as defined in the Telcordia (Bellcore) GR-253 standard. Hierarchical alarm reporting means that whenever a higher alarm is asserted, the lower alarm state is suppressed. When the high alarm is cleared, the lower alarm will re-assert if the condition still exists.

For LNM, this means that if a major warning threshold is continuously met or exceeded resulting in a crossed event and alarm state, then a minor warning alarm state is suppressed and returned to stable state. The minor crossed event also is removed from the bistate log. When the major warning is cleared, the minor warning alarm is asserted if the condition still exists.

Only a single crossed event for major warnings will appear in the bistate log for the controller. Therefore, you will see only a single log message for a controller if noise exists above configured threshold values.

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:

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

Configuring Link Noise Monitoring on a T1 or E1 Channel

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.

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.

SUMMARY STEPS

1. configure

2. controller e3 interface-path-id

3. mode serial

4. no shutdown

5. end
or
commit

6. show controllers e3 interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller e3 interface-path-id

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-e3)# end

or

RP/0/RSP0/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 interface-path-id

Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router 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 module.

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 interface-path-id

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 interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller e3 interface-path-id

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-e3)# end

or

RP/0/RSP0/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 interface-path-id

Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router 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

Before you can configure a clear channel T3 controller on a channelized SPA, you must configure the SPA for an STS stream channelized for T3. For more information, see the "Configuring Channelized SONET/SDH on Cisco IOS XR Softwarethe Cisco ASR 9000 Series Router" module.

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.

SUMMARY STEPS

1. configure

2. controller t3 interface-path-id

3. mode serial

4. no shutdown

5. end
or
commit

6. show controllers t3 interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller t3 interface-path-id

Example:

RP/0/RSP0/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/RSP0/CPU0:router(config-t3)# mode serial

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

Step 4 

no shutdown

Example:

RP/0/RSP0/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/RSP0/CPU0:router(config-t3)# end

or

RP/0/RSP0/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 interface-path-id

Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router module.

Configuring a Channelized T3 Controller

The 1-Port Channelized OC-3/STM-1 SPA and 2-Port Channelized OC-12/DS0 SPA 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.

Prerequisites

Before you can configure a channelized T3 controller on the 1-Port Channelized OC-3/STM-1 SPA or 2-Port Channelized OC-12/DS0 SPA, you must configure the SPA for an STS stream channelized for T3. For more information, see the "Configuring Channelized SONET/SDH on Cisco IOS XR Softwarethe Cisco ASR 9000 Series Router" module.


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 interface-path-id

3. mode [t1 | e1]

4. no shutdown

5. end
or
commit

6. show controllers t3 interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller T3 interface-path-id

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-t3)# end

or

RP/0/RSP0/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 interface-path-id

Example:

RP/0/RSP0/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.

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" section.

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" section.

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.

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 interface-path-id

3. clock source {internal | line}

4. cablelength feet

5. framing {auto-detect | c-bit | m23}

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

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

8. no shutdown

9. end
or
commit

10. show controllers t3 interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller T3 interface-path-id

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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 {auto-detect | c-bit | m23}

Example:

RP/0/RSP0/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. Auto-detect is not supported on the 2-Port Channelized OC-12c/DS0 SPA.

Step 6 

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

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-t3)# end

or

RP/0/RSP0/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 interface-path-id

Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router 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" section.

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" section.

Configuring a T1 Controller

This task describes how to configure an individual T1 controller and channelize it into 24 individual DS0 timeslots.

Prerequisites

You must configure the 1-Port Channelized OC-3/STM-1 SPA or 2-Port Channelized OC-12/DS0 SPA for an STS stream channelized for T3. For more information, see the "Configuring Channelized SONET/SDH on Cisco IOS XR Softwarethe Cisco ASR 9000 Series Router" module.

You also must configure the 1-Port Channelized OC-3/STM-1 SPA or 2-Port Channelized OC-12/DS0 SPA as a channelized T3 controller running in T1 mode, as described in the "Configuring a Channelized T3 Controller" section.

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 interface-path-id

2. configure

3. controller t1 interface-path-id

4. framing {sf | esf}

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

6. clock source {internal | line}

7. fdl {ansi | att} {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 interface-path-id

Example:

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

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

Step 2 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 3 

controller t1 interface-path-id

Example:

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

Enters T1 configuration mode.

Step 4 

framing {sf | esf}

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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 | att} {enable | disable}

Example:

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

(Optional) Enables the transmission of ANSI T1.403 or AT&T TR54016 once-per-second performance reports through Facility Data Link (FDL).

Note FDL ansi and att are disabled by default.

Step 8 

no shutdown

Example:

RP/0/RSP0/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/RSP0/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/RSP0/CPU0:router(config-t1-channel_group)# timeslots 7-12

Associates 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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-t1)# exit

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/RSP0/CPU0:router(config-t3)# end

or

RP/0/RSP0/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.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on the Cisco ASR 9000 Series Router module.

Configuring an E1 Controller

This task describes how to configure an individual E1 controller and channelize it into 31 individual DS0 timeslots.

Prerequisites

You must configure the 1-Port Channelized OC-3/STM-1 SPA or 2-Port Channelized OC-12/DS0 SPA for an STS stream channelized for T3. For more information, see the "Configuring Channelized SONET/SDH on Cisco IOS XR Softwarethe Cisco ASR 9000 Series Router" module.

You also must configure the 1-Port Channelized OC-3/STM-1 SPA or 2-Port Channelized OC-12/DS0 SPA as a channelized T3 controller running in E1 mode, as described in the "Configuring a Channelized T3 Controller" section.

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 e1 interface-path-id

2. configure

3. controller e1 interface-path-id

4. clock source {internal | line}

5. framing {crc4 | no-crc4 | 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 interface-path-id

Example:

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

(Optional) Displays information about the E1 controllers.

Step 2 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 3 

controller e1 interface-path-id

Example:

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

Enters E1 configuration mode.

Step 4 

clock source {internal | line}

Example:

RP/0/RSP0/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 {crc4 | no-crc4 | unframed}

Example:

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

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

crc4—Framing with CRC-4 error monitoring capabilities

no-crc4—Framing without CRC-4 error monitoring capabilities

unframed—Unframed E1

Note The default frame type for E1 is crc4.

Step 6 

national bits bits

Example:

RP/0/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/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/RSP0/CPU0:router(config-e3)# end

or

RP/0/RSP0/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 in this module.

Configure the associated serial interface, as described in the Configuring Serial Interfaces on the Cisco ASR 9000 Series Router module later in this document.

Configuring BERT

Depending on your hardware support, 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.

Restrictions

Before configuring BERT on the 1-Port Channelized OC-48/STM-16 SPA, consider the following restrictions on the Cisco ASR 9000 Series Router:

Only two simultaneous BERT tests are possible per STS-12 stream.

The following test patterns are supported:

2^15-1 (O.151)

2^20-1 (O.151) - QRSS

2^23-1 (O.151)

Fixed Patterns (all 0s, all 1s etc.)

Single bit error injection

Data inversion

For other cards, valid patterns for all controllers and channel groups include: 0s, 1s, 2^15, 2^20, 2^20-QRSS, 2^23, and alt-0-1.

Additional valid patterns for T1 and E1 controllers include: 1in8, 3in24, 55Daly, and 55Octet. Additional valid patterns for channel groups include: 2^11, 2^9, ds0-1, ds0-2, ds0-3, and ds0-4.

SUMMARY STEPS

1. configure

2. controller [t3 | e3 | t1 | e1] interface-path-id

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] interface-path-id [channel-group channel-group-number] [error] start

10. bert [t3 | e3 | t1 | e1] interface-path-id [channel-group channel-group-number] stop

11. show controllers [t3 | e3 | t1 | e1] interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller [t3 | e3 | t1 | e1] interface-path-id

Example:

RP/0/RSP0/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/RSP0/CPU0:router(config-t3)# bert pattern 2^15

Enables a specific bit error rate test (BERT) pattern on a controller.

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

Step 4 

bert interval time

Example:

RP/0/RSP0/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/RSP0/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/RSP0/CPU0:router(config-t3)# end

or

RP/0/RSP0/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/RSP0/CPU0:router(config-t3)# exit

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

Step 8 

exit
Example:

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

Exits global configuration mode.

Step 9 

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

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

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

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

Note You can include the optional error keyword to inject errors into the running BERT stream.

Step 10 

bert [t3 | e3 | t1 | e1] interface-path-id 
[channel-group channel-group-number] stop
Example:

RP/0/RSP0/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] 
interface-path-id
Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router module.

Configuring BERT on a DS0 Channel Group

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

Prerequisites

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

SUMMARY STEPS

1. configure

2. controller {t1 | e1} interface-path-id

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] interface-path-id [channel-group channel-group-number][error] start

11. bert [t1 | e1] interface-path-id [channel-group channel-group-number] stop

12. show controllers [t1 | e1] interface-path-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller {t1 | e1} interface-path-id

Example:

RP/0/RSP0/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/RSP0/CPU0:router(config-t1)# channel-group 1

RP/0/RSP0/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/RSP0/CPU0:router(config-t1-channel_group)# bert pattern 2^15

Enables a specific bit error rate test (BERT) pattern on a T1 line. Valid patterns for all controllers and channel groups include: 0s, 1s, 2^15, 2^20, 2^20-QRSS, 2^23, and alt-0-1. Additional valid patterns for T1 and E1 controllers include: 1in8, 3in24, 55Daly, and 55Octet. Additional valid patterns for channel groups include: 2^11, 2^9, ds0-1, ds0-2, ds0-3, and ds0-4.

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

Step 5 

bert interval time

Example:

RP/0/RSP0/CPU0:router(config-t1-channel_group)# bert interval 5

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

Step 6 

end

or

commit

Example:

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

or

RP/0/RSP0/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/RSP0/CPU0:router(config-t1-channel_group)# exit

Exits channel group configuration mode.

Step 8 

exit
Example:

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

Exits T1 or E1 configuration mode.

Step 9 

exit
Example:

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

Exits global configuration mode.

Step 10 

bert [t1 | e1] interface-path-id [channel-group 
channel-group-number] [error] start
Example:

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

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

Starts the configured BERT test on the specified channel group.

Note You can include the optional error keyword to inject errors into the running BERT stream.

Step 11 

bert [t1 | e1] interface-path-id [channel-group 
channel-group-number] stop
Example:

RP/0/RSP0/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 | e1] interface-path-id
Example:

RP/0/RSP0/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 the Cisco ASR 9000 Series Router module later in this document.

Configuring Link Noise Monitoring on a T1 or E1 Channel

This section describes how to configure Link Noise Monitoring (LNM) on a T1 or E1 channel on the Cisco ASR 9000 Series Router.

Prerequisites

Before you configure LNM on the Cisco ASR 9000 Series Router, be sure that the following requirements are met:

A 2-Port Channelized OC-12c/DS0 SPA is installed.

The 2-Port Channelized OC-12/DS0 SPA is configured as a channelized T3 controller running in T1 or E1 mode, as described in the "Configuring a Channelized T3 Controller" section.

The T1 or E1 controller is configured as a single channel supporting the full 24 or 31 DS0 time slots, as described in the "Configuring a T1 Controller" section or "Configuring an E1 Controller" section. LNM is not supported on a fractional T1 or E1 link.

SUMMARY STEPS

1. configure

2. controller {t1 | e1} interface-path-id

3. lnm major-warning [clear | set][line-code-violation lcv-value [path-code-violation pcv-value]][duration seconds]

4. lnm minor-warning [clear | set][line-code-violation lcv-value [path-code-violation pcv-value]][duration seconds]

5. lnm syslog

6. end
or
commit

DETAILED STEPS

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

controller {t1 | e1} interface-path-id

Example:

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

Enters T1 or E1 configuration mode.

Step 3 

lnm major-warning [clear | set][line-code-violation lcv-value [path-code-violation pcv-value]][duration seconds]

Example:

RP/0/RSP0/CPU0:router(config-t1)# lnm major-warning

(Optional) Enables link noise monitoring and specifies thresholds for noise errors on T1/E1 links that are used to signal major warning events and recovery from those events.

The default values for both set and clear thresholds are:

For T1 links—line-code-violation is 1544, path-code-violation is 320, and duration is 10.

For E1 links—line-code-violation is 2048, path-code-violation is 831, and duration is 10.

Step 4 

lnm minor-warning [clear | set][line-code-violation lcv-value [path-code-violation pcv-value]][duration seconds]

Example:

RP/0/RSP0/CPU0:router(config-t1)# lnm minor-warning

(Optional) Enables link noise monitoring and specifies thresholds for noise errors on T1/E1 links that are used to signal minor warning events and recovery from those events.

The default values for both set and clear thresholds are:

For T1 links—line-code-violation is 154, path-code-violation is 145, and duration is 10.

For E1 links—line-code-violation is 205, path-code-violation is 205, and duration is 10.

Step 5 

lnm syslog

Example:

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

(Optional) Enables logging of link noise monitoring major and minor events and alarms.

Note You must use this command for LNM messages to appear in both the system log and in the log events buffer.

Step 6 

end

or

commit

Example:

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

or

RP/0/RSP0/CPU0:router(config-t1)# 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.

Verifying Link Noise Monitoring Configuration and Status

To verify LNM configuration and state information, as well as statistics and events, use the show controllers lnm command as shown in the following example:

RP/0/RSP0/CPU0:Router# show controllers t1 0/1/1/0/1/1 lnm all
Thu May 13 10:28:26.474 PDT
 
   
Controller T1 0/1/1/0/1/1
 
   
Syslog   Monitoring type  State     Thresholds (lcv/pcv/duration)
--------------------------------------------------------------------
enabled   minor-warning   stable    Set(  15/  15/   4) Clear(  15/  15/   4)
          major-warning   stable    Set( 154/ 145/   4) Clear( 154/ 145/   4)
 
   
  Monitoring type            Minor-Warn      Major-Warn
  ---------------            ------------    ------------
  Create                     1               1
  Update                     0               0
  Delete                     0               0
  Clear                      0               0
  Noise Crossed              1               1
  Noise Cleared              1               1
 
   
Last Five Events
--------------------------------------------------------------------
MINWARNCROSS: Noise crossed minor-warn threshold at Thu May 13 09:54:10 2010
MAJWARNCROSS: Noise crossed major-warn threshold at Thu May 13 09:54:11 2010
MAJWARNCLEAR: Noise cleared major-warn threshold at Thu May 13 10:27:25 2010
MINWARNCLEAR: Noise cleared minor-warn threshold at Thu May 13 10:28:14 2010

Clearing Link Noise Monitoring States and Statistics

You can use the clear controller lnm command to reset LNM states or clear statistics and reset them to zero.

There should not normally be any need to clear the LNM controller states. The state option resets the LNM configuration which causes an update of the current LNM states in the system. Therefore, under normal conditions, if the controller is in alarm state, the reset should continue to report the alarm state; alternatively, if the controller is clear of any alarms, the reset will show the stable state. The use of the clear controller lnm state command does not actually clear any alarms, but causes a refresh of their values in the system. Therefore, this command can be used if the reported controller state should happen to be out of synchronization with the actual controller state.

To reset LNM states, use the clear controller lnm command as shown in the following example:

RP/0/RSP0/CPU0:Router# clear controller t1 0/1/0/0/1/1 lnm state
 
   

To clear LNM statistics and reset counters to zero, use the clear controller lnm command as shown in the following example:

RP/0/RSP0/CPU0:Router# clear controller t1 0/1/0/0/1/1 lnm statistics
 
   
RP/0/RSP0/CPU0:Router# show controller T1 0/1/0/1/1/1 lnm statistics   
Thu May 13 11:26:20.991 PDT
 
   
Controller T1 0/1/0/1/1/1
 
   
  Monitoring type            Minor-Warn      Major-Warn
  ---------------            ------------    ------------
  Create                     0               0           
  Update                     0               0           
  Delete                     0               0           
  Clear                      0               0           
  Noise Crossed              0               0           
  Noise Cleared              0               0

Configuration Examples

This section contains the following examples:

Configuring a Clear Channel T3 Controller: Example

Configuring a T3 Controller with Channelized T1 Controllers: Example

Configuring BERT on a T3 Controller: Example

Configuring Link Noise Monitoring on a T1 Controller: Example

QoS on T3 Channels: Example

Configuring a Clear Channel T3 Controller: Example

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

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

Configuring a T3 Controller with Channelized T1 Controllers: Example

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

RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# controller T3 0/3/0/0 
RP/0/RSP0/CPU0:router(config-t3)# mode t1
RP/0/RSP0/CPU0:router(config-t3)# framing m23
RP/0/RSP0/CPU0:router(config-t3)# cablelength 11
RP/0/RSP0/CPU0:router(config-t3)# clock source line
RP/0/RSP0/CPU0:router(config-t3)#commit
RP/0/RSP0/CPU0:router(config-t3)#exit
RP/0/RSP0/CPU0:router(config)# exit
RP/0/RSP0/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/RSP0/CPU0:router#
RP/0/RSP0/CPU0:router(config)#configure
RP/0/RSP0/CPU0:router(config)# controller t1 0/3/0/0/0
RP/0/RSP0/CPU0:router(config-t1)# channel-group 0
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 1-24
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# exit
RP/0/RSP0/CPU0:router(config)# controller t1 0/3/0/0/1
RP/0/RSP0/CPU0:router(config-t1)# channel-group 0
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 1-24
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# exit
RP/0/RSP0/CPU0:router(config)# controller t1 0/3/0/0/2
RP/0/RSP0/CPU0:router(config-t1)# channel-group 0
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 1-12
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# channel-group 1
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 13-24
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# exit
RP/0/RSP0/CPU0:router(config)# controller t1 0/3/0/0/3
RP/0/RSP0/CPU0:router(config-t1)# channel-group 0
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 1-6
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# channel-group 1
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 7-12
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# channel-group 2
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 13-18
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# channel-group 3
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 19-24
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1-channel_group)#commit

Configuring BERT on a T3 Controller: Example

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

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# controller t3 0/3/0/1
RP/0/RSP0/CPU0:router(config-t3)# bert pattern 0s
 
   
Run bert from exec mode for the bert config to take effect
 
   
RP/0/RSP0/CPU0:router(config-t3)#exit
RP/0/RSP0/CPU0:router(config)# exit
 
   
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]
RP/0/RSP0/CPU0:router# bert t3 0/3/0/1 start
 
   
 
   
RP/0/RSP0/CPU0:router# bert t3 0/3/0/1 stop
 
   
 
   
RP/0/RSP0/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

Configuring Link Noise Monitoring on a T1 Controller: Example

The following example shows how to configure a channelized T3 controller for T1 configuration mode using the full 24 DS0 timeslots as a single channel before configuring LNM on the link. In this example, the values shown are actually the system defaults for the set thresholds:

RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# controller T3 0/1/1/0/1
RP/0/RSP0/CPU0:router(config-t3)# mode t1
RP/0/RSP0/CPU0:router(config-t3)# framing m23
RP/0/RSP0/CPU0:router(config-t3)# cablelength 11
RP/0/RSP0/CPU0:router(config-t3)# clock source line
RP/0/RSP0/CPU0:router(config-t3)#commit
RP/0/RSP0/CPU0:router(config-t3)#exit
RP/0/RSP0/CPU0:router(config)# controller t1 0/1/1/0/1/1
RP/0/RSP0/CPU0:router(config-t1)# channel-group 0
RP/0/RSP0/CPU0:router(config-t1-channel_group)# timeslots 1-24
RP/0/RSP0/CPU0:router(config-t1-channel_group)# exit
RP/0/RSP0/CPU0:router(config-t1)# lnm syslog
RP/0/RSP0/CPU0:router(config-t1)# lnm major-warning set line-code-violation 1544 
path-code-violation 320 duration 10
RP/0/RSP0/CPU0:router(config-t1)# lnm minor-warning set line-code-violation 154 
path-code-violation 145 duration 10

QoS on T3 Channels: Example

QoS on the T3 channels is supported for both PPP and HDLC encapsulation. The following example shows a typical QoS configuration for T3 interfaces:

class-map VOIP 
match dscp EF 
end-class-map
class-map OAM 
match dscp AF43 
end-class-map
!
Policy-map T3-no-priority
class OAM
bandwidth percent 30 
!
class class-default
!
end-policy-map
!
Policy-map T3-priority
class VOIP    
priority level 1 
     police rate percent 60
!
class OAM
bandwidth percent 30 
!
class class-default
!
end-policy-map

Additional References

The following sections provide references related to T3 and T1 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


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