Table Of Contents
Clear Channel T3/E3 with Integrated CSU/DSU
Prerequisites for Clear Channel T3/E3 with Integrated CSU/DSU
Information About Clear Channel T3/E3 with Integrated CSU/DSU
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for a T3 Interface
Configuring the Card Type and Controller for a T3 Interface
Configuring DSU Mode and Bandwidth for T3
Configuring the T3 Maintenance Data Link
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for an E3 Interface
Configuring the Card Type and Controller for an E3 Interface
Configuring DSU Mode and Bandwidth for E3
Configuring National Bit for E3
Verifying the T3 or E3 Configuration
Configuration Example for the Clear Channel T3/E3 with Integrated CSU/DSU Feature
Clear Channel T3/E3 with Integrated CSU/DSU
The Clear Channel T3/E3 NM-1 Network Module with Integrated CSU/DSU feature provides a software configurable T3/E3 product. This flexible network module allows you to switch between T3 and E3 applications with a single Cisco IOS command.
The T3/E3 NM-1 network module supports a single-port T3 or E3 with an integrated channel service unit (CSU) and a data service unit (DSU). It supports High-Level Data Link Control (HDLC), PPP, and Frame Relay. It includes the following features:
•
Single port—universal T3/E3 version
•
Clear and subrate support on both T3 and E3 modes
•
Online insertion and removal (OIR) support on Cisco 3660 series and Cisco 3745 routers
•
Onboard processing of Cisco Message Definition Language (MDL) and performance monitoring
•
Support for scrambling and subrate can be independently or simultaneously enabled in each DSU mode
•
Support for full T3 and E3 line rates
T3/E3 Applications and Positioning
The T3/E3 NM-1 network module provides high-speed performance for advanced, fully converged networks supporting a wide array of applications and services such as security and advanced QoS for voice and video. T3/E3 and subrate T3/E3 connectivity optimizes WAN bandwidth for deploying the new applications and service delivery. All the supported platforms, except the Cisco 2650XM or Cisco 2651XM routers, are capable of supporting line rate performance but impose varying levels of CPU overhead and therefore affect the overall platform performance. See Table 1 for recommended branch office positioning.
Table 1 T3/E3 NM-1 Branch Office Positioning and Support Comparison
Supported Platforms Recommended Type of Service Recommended Branch Office Sizes Maximum T3/E3 Modes SupportedCisco 2650/2651XM
Subrate T3/E3
Small to medium offices
1 1
Cisco 2691
Subrate T3/E3
Small to medium offices
1
Cisco 3660 series
Subrate and full-rate T3/E3
Large and regional offices
1
Cisco 3725
Subrate and full-rate T3/E3
Medium and large offices
1
Cisco 3745
Subrate and full-rate T3/E3
Medium, large, and regional offices
2
1 For Cisco 2650XM and Cisco 2651XM platforms only, we recommend that you configure the NM-1 T3/E3 in subrate mode with a DSU setting of 15000 (15 mbps). All other platforms can operate with full DSU bandwidth.
Feature Specifications for the Clear Channel T3/E3 with Integrated CSU/DSU Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for Clear Channel T3/E3 with Integrated CSU/DSU
•
Information About Clear Channel T3/E3 with Integrated CSU/DSU
•
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for a T3 Interface
•
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for an E3 Interface
•
Configuration Example for the Clear Channel T3/E3 with Integrated CSU/DSU Feature
Prerequisites for Clear Channel T3/E3 with Integrated CSU/DSU
•
Implementation of this feature requires Cisco IOS Release 12.2(11)YT or a later release.
•
See Table 2 for the minimum platform memory recommended.
Information About Clear Channel T3/E3 with Integrated CSU/DSU
Configuration of the Clear Channel T3/E3 with Integrated CSU/DSU feature can be set up for a T3 interface and for an E3 interface:
•
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for a T3 Interface
•
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for an E3 Interface
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for a T3 Interface
This section describes the tasks used to configure the Clear Channel T3/E3 with Integrated CSU/DSU feature for a T3 interface:
•
Configuring the Card Type and Controller for a T3 Interface (required)
•
Configuring DSU Mode and Bandwidth for T3 (required)
•
Configuring Scrambling for T3 (optional)
•
Configuring the BERT for T3 (optional)
•
Configuring Loopback for T3 (optional)
•
Configuring the T3 Maintenance Data Link (optional)
Configuring the Card Type and Controller for a T3 Interface
When the Clear Channel T3/E3 network module is used for the first time, the running configuration does not show the T3/E3 controller and its associated serial interface. You can use the show version command to learn if the router recognized the T3/E3 card and was able to initialize the card properly. After the card type is configured for the slot, the respective controller and serial interface appear in the running configuration. See the "Use the show version Command" section.
After the network module has ascertained that the card has been initialized properly, use the card type command to configure the card. If the command is accepted successfully, Cisco IOS software creates a controller and a serial interface for the card.
Perform this task to select and configure a card type and controller as T3.
Note
The autoconfig/setup utility does not support configuring the card type for the T3/E3 network module.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
card type t3 slot
4.
controller t3 slot/port
5.
framing {c-bit | m23}
6.
cablelength feet
7.
clock source {internal | line}
8.
exit
DETAILED STEPS
Configuring DSU Mode and Bandwidth for T3
Perform this task to specify the interoperability mode and maximum allowable bandwidth used by a T3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port
4.
dsu mode {0 | 1 | 2 | 3 | 4}
5.
dsu bandwidth kbps
6.
exit
DETAILED STEPS
Command PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface serial slot/port
Example:Router(config)# interface serial 1/1
Specifies the serial interface created on the controller.
Step 4
dsu mode {0 | 1 | 2 | 3 | 4}
Example:Router(config-if)# dsu mode 0
Specifies the interoperability mode used by a T3 controller.
•
0—Connects a T3 controller to another T3 controller or to a Digital Link DSU (DL3100). Bandwidth range is from 300 to 44210 kbps. This is the default.
•
1—Connects a T3 controller to a Kentrox DSU. Bandwidth range is from 1500 to 35000/44210 kbps.
Note
If the bandwidth is set to greater than 35000 kbps, it defaults to 44210 kbps.
•
2—Connects a T3 controller to a Larscom DSU. Bandwidth range is from 3100 to 44210 kbps.
•
3—Connects a T3 controller to an Adtran T3SU 300. Bandwidth range is from 75 to 44210 kbps.
•
4—Connects a T3 controller to a Verilink HDM 2182. Bandwidth range is from 1500 to 44210 kbps.
Step 5
dsu bandwidth kbps
Example:Router(config-if)# dsu bandwidth 44210
Specifies the maximum allowable bandwidth in the range from 1 to 44210 kbps.
•
The real (actual) vendor-supported bandwidth is in the range from 75 to 44210 kbps. See Table 2.
Note
For the Cisco 2650XM and Cisco 2651XM platforms only, we recommend that you set the DSU bandwidth to 15000 in any subrate mode.
Step 6
exitExample:Router(config-if)# exit
Exits interface configuration mode and returns to privileged EXEC mode.
Configuring Scrambling for T3
Perform this task to enable encryption of the payload on the T3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port
4.
scramble
5.
exit
DETAILED STEPS
Configuring the BERT for T3
Perform this task to configure a bit error rate (BER) test pattern on a T3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller t3 slot/port
4.
bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time
5.
no bert
6.
exit
DETAILED STEPS
Configuring Loopback for T3
Perform this task to loop an entire T3 line toward the line and back toward the router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller t3 slot/port
4.
loopback {local | network {line | payload} | remote}
5.
no loopback
6.
exit
DETAILED STEPS
Configuring the T3 Maintenance Data Link
Perform this task to configure the MDL message.
Note
This configuration information is applicable only to C-bit parity T3.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller t3 slot/port
4.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
5.
exit
DETAILED STEPS
How to Configure the Clear Channel T3/E3 with Integrated CSU/DSU Feature for an E3 Interface
The section describes the commands used to configure the Clear Channel T3/E3 with Integrated CSU/DSU feature for an E3 interface:
•
Configuring the Card Type and Controller for an E3 Interface (required)
•
Configuring Scrambling for E3 (required)
•
Configuring the BERT for E3 (optional)
•
Configuring Loopback for E3 (optional)
•
Configuring National Bit for E3 (optional)
Configuring the Card Type and Controller for an E3 Interface
Perform this task to configure the card type and controller for a E3 interface.
Note
The autoconfig/setup utility does not support configuring the card type for the T3/E3 network module.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
card type e3 slot
4.
controller e3 slot/port
5.
framing {bypass | g751}
6.
clock source {internal | line}
7.
exit
DETAILED STEPS
Configuring DSU Mode and Bandwidth for E3
Perform this task to specify the interoperability mode used by an E3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port
4.
dsu mode {0 | 1}
5.
dsu bandwidth kbps
6.
exit
DETAILED STEPS
Command PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface serial slot/port
Example:Router(config)# interface serial 1/1
Enters interface configuration mode and specifies the serial interface created on the controller.
Step 4
dsu mode {0 | 1}
Example:Router(config-if)# dsu mode 0
Specifies the interoperability mode used by an E3 controller.
•
0—Sets the interoperability mode to 0. This is the default. Specify mode 0 to connect an E3 controller to another E3 controller or to a Digital Link DSU (DL3100). Bandwidth range is from 358 to 24500/34010 kbps.
Note
If the bandwidth is set to greater than 24500 kbps, it defaults to 34010 kbps.
•
1—Sets the interoperability mode to 1. Specify mode 1 to connect an E3 controller to a Kentrox DSU. Bandwidth range is from 500 to 34010 kbps.
Step 5
dsu bandwidth kbps
Example:Router(config-if)# dsu bandwidth 44210
Specifies the maximum allowable bandwidth in the range from 22 to 34010 kbps.
•
The real (actual) vendor-supported bandwidth is in the range from 358 to 34010 kbps. See Table 2.
Note
For the Cisco 2650XM and Cisco 2651XM platforms only, we recommend that you set the DSU bandwidth to 15000 in any subrate mode.
Step 6
exitExample:Router(config-if)# exit
Exits interface configuration mode and returns to privileged EXEC mode.
Configuring Scrambling for E3
Perform this task to enable encryption of the payload on the E3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port
4.
scramble
5.
exit
DETAILED STEPS
Configuring the BERT for E3
Perform this task to configure a BER test pattern on an E3 controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller t3 slot/port
4.
bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1}
5.
no bert
6.
exit
DETAILED STEPS
Configuring Loopback for E3
Perform this task to loop an entire E3 line toward the line and back toward the router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller e3 slot/port
4.
loopback {local | network {line | payload}}
5.
no loopback
6.
exit
DETAILED STEPS
Configuring National Bit for E3
Perform this task to set the E3 national bit in the G.751 frame used by the E3 controller. This configuration is used to set the bit when the E3 line crosses national boundaries.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller e3 slot/port
4.
national bit {1 | 0}
5.
exit
DETAILED STEPS
Verifying the T3 or E3 Configuration
Perform this task to verify that the T3 or E3 controller is configured correctly. Enter the show running-config, show controllers, or show interfaces serial privileged EXEC command to display the command settings for the router.
Troubleshooting Tips
You can use the methods described in this section to troubleshoot the T3/E3 network module using Cisco IOS software.
Set Loopbacks
The T3/E3 local loopback can be used to ensure that the router and the T3/E3 network module are working properly. The controller clock source should be configured to "internal."
Use T3/E3 network loopback and remote loopback to diagnose problems with cables between the T3/E3 controller and the central switching office at the link level. For this diagnostic setup to work, if the network module is looped toward the network, the network module must be configured with the clock source as "line."
Run Bit Error Rate Test
The network module contains onboard BERT circuitry. With this circuitry present, the software can send and detect a programmable pattern that is compliant with CCITT/ITU pseudorandom and repetitive test patterns. BERT allows you to test cables and signal problems in the field.
When a BERT is running, your system expects to receive the same pattern that it is sending. To help ensure this, two common options are available.
•
Use a loopback somewhere in the link or network.
•
Configure remote testing equipment to send the same BERT pattern at the same time.
Please refer to the bert pattern (t3/e3) command in the "Command Reference" section for instructions on how to run BERT and check the results.
Use the show version Command
Use the show version command to learn if the router recognized the T3/E3 card and was able to initialize the card properly. The show version command lists the hardware interfaces and controllers present in the router. You should find "1 Subrate T3/E3 port(s)" as shown in the following example.
Router# show version...Router uptime is 2 hours, 6 minutesSystem returned to ROM by power-onSystem image file is "flash:c3725-i-mz"cisco 3725 (R7000) processor (revision 0.4) with 111616K/19456K bytes of memory.Processor board ID 12345678901R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 CacheBridging software.X.25 software, Version 3.0.0Primary Rate ISDN software, Version 1.12 FastEthernet/IEEE 802.3 interface(s)1 Serial network interface(s)2 Channelized T1/PRI port(s)1 Subrate T3/E3 port(s)DRAM configuration is 64 bits wide with parity disabled.55K bytes of non-volatile configuration memory.15680K bytes of ATA System CompactFlas (Read/Write)Configuration register is 0x0Configuration Example for the Clear Channel T3/E3 with Integrated CSU/DSU Feature
The following is sample output from the show running-config command for an E3 controller:
Router# show running-configBuilding configuration...%AIM slot 0 doesn't existCurrent configuration :1509 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Router1!card type e3 1no logging console!ip subnet-zerono ip routing!!!!!voice call carrier capacity active!!!!!!!!!mta receive maximum-recipients 0!!controller E3 1/0clock source internal!!!!interface Loopback0no ip addressno ip route-cacheshutdownno keepalive!interface FastEthernet0/0ip address 10.0.145.34 255.255.255.0no ip route-cacheno ip mroute-cacheduplex autospeed autono cdp enable!interface Serial0/0no ip addressencapsulation pppno ip route-cacheno ip mroute-cacheshutdownclockrate 2000000no fair-queue!interface FastEthernet0/1no ip addressno ip route-cacheno ip mroute-cacheshutdownduplex autospeed autono keepaliveno cdp enable!interface Serial0/1no ip addressencapsulation pppno ip route-cacheno ip mroute-cacheshutdownclockrate 2000000!interface Serial0/2:0ip address 172.27.27.2 255.255.255.0no ip route-cacheno keepalive!interface Serial1/0no ip addressno ip route-cacheno keepalivedsu bandwidth 34010!ip classlessno ip http server!ip pim bidir-enable!!!!!call rsvp-sync!!mgcp profile default!!!dial-peer cor custom!!!!line con 0exec-timeout 0 0line aux 0line vty 0 4login!endAdditional References
The following sections provide additional references related to the Clear Channel T3/E3 with Integrated CSU/DSU feature:
•
MIBs
•
RFCs
Related Documents
Standards
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
Technical Assistance
Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 T command reference publications.
bert pattern (t3/e3)
To enable a bit error rate (BER) test pattern on a T3 or E3 controller, use the bert pattern command in controller configuration mode. To disable a BER test pattern, use the no form of this command.
bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time
no bert
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
BER testing is supported on T3/E3 links and is done only over framed T3 or E3 signal, unless E3 framing is in bypass mode.
To display the BER test results, use the show controllers (t3/e3) EXEC command. The BER test 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
When the T3 or E3 line has a BER test running, the line state is DOWN and the status field shows the current or last result of the test.
The bert pattern command is not written to NVRAM. This command is used only to test the T3 or E3 line for a short predefined interval and to avoid accidentally saving the command, which could cause the interface not to come up the next time the router reboots.
Examples
In the following example, a BER test pattern of all zeros is run for 30 minutes on the T3 controller in slot 1:
controller t3 1/0bert pattern 0s interval 30Related Commands
]
cablelength (t3)
To specify the distance of the cable from the routers to the network equipment, use the cablelength command in controller configuration mode. To restore the default cable length, use the no form of this command.
cablelength feet
no cablelength
Syntax Description
Defaults
224 feet
Command Modes
Controller configuration
Command History
Usage Guidelines
The default cable length of 224 feet is used by the clear T3.
Examples
The following example shows the cable length for the router set to 300 feet:
controller t3 1/0cablelength 300card type (t3/e3)
To configure the card type on the T3 or E3 controller, use the card type command in global configuration mode. To restore the default value, use the no form of this command.
card type {t3 | e3} slot
no card type {t3 | e3} slot
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Once a card type is issued, the user can enter the no card type command and then another card type command to configure a new card type. The user must save the configuration to the NVRAM and reboot the router in order for the new configuration to take effect.
When the router comes up, the software comes up with the new card type. Note that the software will reject the configuration associated with the old controller and old interface. The user will now have to configure the new controller and serial interface and save it.
Examples
The following example shows T3 data transmission configured in slot 1:
card type t3 1clock source (t3/e3)
To specify where the clock source is obtained for use by a T3 or E3 controller, use the clock source command in controller configuration mode. To restore the default clock source, use the no form of this command.
clock source {internal | line}
no clock source
Syntax Description
internal
Specifies that the internal clock source is used. This is the default for T3.
line
Specifies that the network clock source is used. This is the default for E3.
Defaults
The internal clock source is used for T3 controllers. The line clock source is used for E3 controllers.
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the clock source command, the default clock source is used.
Configure clock source line if your telephone company or the remote data service unit provides the master clock of the T3 or E3 connection.
Configure clock source internal if your router provides the master clock of the T3 or E3 connection.
Note
For a back-to-back connection between two T3 or E3 network modules, one controller must be configured for clock source internal while the other must be configured for clock source line.
Examples
The following example shows the clock source set to line:
controller t3 1/0clock source linecontroller e3
To select the E3 controller, use the controller e3 command in global configuration mode.
controller e3 slot/port
Syntax Description
slot/port
Number of the slot and port being configured. Refer to the appropriate hardware manual for slot and port information. The slash mark is required.
Defaults
No default values or behaviors
Command Modes
Global configuration
Command History
Examples
The following example shows the E3 controller configured in slot 0, port 0:
controller e3 0/0Related Commands
Command Descriptioncontroller t3
Selects a T3 controller.
show controllers (t3/e3)
Displays information about the T3 or E3 controllers.
dsu bandwidth (e3)
To specify the maximum allowable bandwidth used by an E3 controller, use the dsu bandwidth command in interface configuration mode. To return to the default bandwidth, use the no form of this command.
dsu bandwidth kbps
no dsu bandwidth kbps
Syntax Description
Defaults
The default value is 34010 kbps.
Command Modes
Interface configuration
Command History
Usage Guidelines
The local interface configuration must match the remote interface configuration. For example, if you reduce the maximum bandwidth to 16000 kbps on the local port, you must also do the same on the remote port.
The dsu bandwidth command reduces the bandwidth by padding the E3 frame.
To verify the data service unit (DSU) bandwidth configured on the interface, use the show interface serial EXEC command.
When G.751 framing is used, DSU bandwidth can be used to select a payload subrate from 34010 kbps down to 22 kbps.
Before framing bypass can be used, DSU bandwidth of 34010 kbps must be configured.
Even though software allows the user to configure a continuous range of bandwidths in subrate modes, vendors support bandwidths only in quantums (for example, in an E3 digital link, bandwidth must be in multiples of 358 kbps). Therefore, the software sets the user-configured bandwidth to the closest vendor-supported bandwidth. Use the show interfaces serial slot/port command to display the actual bandwidth that is configured.
The user-configured subrate mode, subrate bandwidth, actual subrate bandwidth configured, and scramble configuration are displayed near the end of the show interfaces serial command output. See the "Examples" section for more information.
Mode DSU Bandwidth Range Bandwidth Multiples0
Digital Link or Cisco
358-34010 kbps
358 kbps
1
Kentrox
1000-24500/34010 kbps
500 kbps
The following table shows DSU Mode and Bandwidth for NM-1.
Note
If the bandwidth is set to greater than 24500 kbps, it will default to 34010 kbps.
Note
For the Cisco 2650XM and Cisco 2651XM platforms only, we recommend that you override the default DSU bandwidth of 34010 kbps and set the DSU bandwidth to 15000 kbps in any subrate mode.
Examples
The following example shows the DSU bandwidth set to 16,000 kbps on serial interface 1/0:
interface serial 1/0dsu bandwidth 16000The following example shows the user-configured subrate bandwidth and actual-configured subrate bandwidth displayed in the show interfaces serial command output.
Serial1/0 is up, line protocol is upHardware is DSXPNM SerialMTU 1500 bytes, BW 44210 Kbit, DLY 20000 usec,reliability 253/255, txload 1/255, rxload 1/255Encapsulation HDLC, crc 16, loopback not setKeepalive not setDTR is pulsed for 0 seconds on reset, Restart-Delay is 1637167 secsLast input 04:59:04, output 04:59:04, output hang neverLast clearing of "show interface" counters 00:00:02Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDSU mode 0, bandwidth 34010, real bandwidth 34010, scramble 0Related Commands
Command Descriptionshow interfaces serial
Displays information that is specific to the interface hardware.
dsu bandwidth (t3)
To specify the maximum allowable bandwidth used by a T3 controller, use the dsu bandwidth command in interface configuration mode. To return to the default bandwidth, use the no form of this command.
dsu bandwidth kbps
no dsu bandwidth kbps
Syntax Description
Defaults
The default value is 44210 kbps.
Command Modes
Interface configuration
Command History
Usage Guidelines
The local interface configuration must match the remote interface configuration. For example, if you reduce the maximum bandwidth to 16000 kbps on the local port, you must also do the same on the remote port.
The dsu bandwidth command reduces the bandwidth by padding the T3 frame.
Even though software allows the user to configure a continuous range of bandwidths in subrate modes, vendors support bandwidths only in quantums (for example, in T3 digital link the bandwidth must be in multiples of 300 kbps). Therefore, the software sets the user-configured bandwidth to the closest vendor-supported bandwidth. Use the show interfaces serial slot/port command to display the real (actual) bandwidth that is configured.
The user-configured subrate mode, subrate bandwidth, actual subrate bandwidth configured, and scramble configuration are displayed near the end of the show interfaces serial command output. See the "Examples" section for more information.
The following table shows DSU Modes and Bandwidths for NM-1
Note
For the Cisco 2650XM and Cisco 2651XM platforms only, we recommend that you override the default DSU bandwidth of 44210 kbps and set the DSU bandwidth to 15000 kbps in any subrate mode.
Examples
The following example shows the data service unit bandwidth set to 16000 kbps on serial interface 1/0:
interface serial 1/0dsu bandwidth 16000The following example shows the user-configured subrate bandwidth and the actual configured subrate bandwidth displayed in the show interfaces serial command output:
Serial1/0 is up, line protocol is upHardware is DSXPNM SerialMTU 1500 bytes, BW 44210 Kbit, DLY 20000 usec,reliability 253/255, txload 1/255, rxload 1/255Encapsulation HDLC, crc 16, loopback not setKeepalive not setDTR is pulsed for 0 seconds on reset, Restart-Delay is 1637167 secsLast input 04:59:04, output 04:59:04, output hang neverLast clearing of "show interface" counters 00:00:02Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDSU mode 0, bandwidth 34010, real bandwidth 34010, scramble 0Related Commands
Command Descriptionshow interfaces serial
Displays information that is specific to the interface hardware.
dsu mode (e3)
To specify the interoperability mode used by an E3 controller, use the dsu mode command in interface configuration mode. To return to the default mode, use the no form of this command.
dsu mode {0 | 1}
no dsu mode
Syntax Description
Defaults
The default value is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
The local interface configuration must match the remote interface configuration. For example, if you define the DSU interoperability mode as 1 on the local port, you must also do the same on the remote port.
You must know what type of DSU is connected to the remote port to determine if it interoperates with a T3 or E3 controller.
To verify the DSU mode configured on the interface, use the show interfaces serial EXEC command.
Examples
The following example shows the DSU mode set to 1 on serial interface 1/0:
interface serial 1/0dsu mode 1Related Commands
Command Descriptionshow controllers serial
Displays information that is specific to the serial controllers.
show interfaces serial
Displays information that is specific to the interface hardware.
dsu mode (t3)
To specify the interoperability mode used by a T3 controller, use the dsu mode command in interface configuration mode. To return to the default mode, use the no form of this command.
dsu mode {0 | 1 | 2 | 3 | 4}
no dsu mode
Syntax Description
Defaults
The default value is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
The local interface configuration must match the remote interface configuration. For example, if you define the data service unit (DSU) interoperability mode as 1 on the local port, you must also do the same on the remote port.
You must know what type of DSU is connected to the remote port to determine if it interoperates with a T3 or E3 controller.
To verify the DSU mode configured on the interface, use the show interfaces serial EXEC command.
Examples
The following example shows the DSU mode set to 1 on serial interface 1/0:
interface serial 1/0dsu mode 1Related Commands
Command Descriptionshow interfaces serial
Displays information that is specific to the interface hardware.
framing (e3)
To specify the type of framing used by the E3 controller, use the framing command in controller configuration mode. To restore the default framing type, use the no form of this command.
framing {bypass | g751}
no framing
Syntax Description
bypass
Specifies that the G.751 framing be bypassed.
g751
Specifies G.751 framing as the E3 framing type. This is the default.
Defaults
The default is G.751.
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the framing command, the default, g751, is used by the E3 controller to automatically determine the framing type received from the far-end equipment.
Configure framing as G.751 when the E3 connection terminates remotely on a Digital Link or Kentrox data service unit, or when needing a subrate on an E3 connection between two T3 or E3 network modules.
Note
The local interface configuration must match the remote interface, or DSU, configuration.
When framing G.751 is used, DSU bandwidth can be used to select a payload subrate from 34010 kbps down to 22 kbps.
When framing bypass is used, DSU bandwidth of 34010 kbps must be configured.
When framing G.751 is used, configuring the scrambling command can prevent some payload data from being mistakenly interpreted as G.751 framing bits by switches placed between the DSUs. By default, the no scrambling command is configured.
When framing bypass is used, the no scrambling command must be configured.
When framing G.751 is used, bit 11 of the G.751 frame is reserved for national use and is set to 1 by default.
Configure national bit 1 only when required for interoperability with your telephone company.
Examples
The following example shows the framing for the E3 controller set to bypass:
controller e3 1/0framing bypassframing (t3)
To specify the type of framing used by the T3 controller, use the framing command in controller configuration mode. To restore the default framing type, use the no form of this command.
framing {c-bit | m23}
no framing
Syntax Description
c-bit
Specifies C-bit framing as the T3 framing type. This is the default.
m23
Specifies M23 framing as the T3 framing type.
Defaults
The default is C-bit.
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the framing command, the default, c-bit, is used by the T3 controller to automatically determine the framing type received from the far-end equipment.
Examples
The following example shows the framing for the T3 controller set to C-bit:
controller t3 1/0framing c-bitloopback (e3)
To loop an entire E3 line toward the line and back toward the router, use the loopback command in controller configuration mode. To remove the loop, use the no form of this command.
loopback {local | network {line | payload}}
no loopback
Syntax Description
Defaults
The default is local.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command for troubleshooting purposes. To verify that a loopback is configured on the interface, use the show controllers (t3/e3) EXEC command. Note that line loopback is available only in C-bit parity mode.
Examples
The following example configures the controller located in slot 1, port 0 for a local loopback:
controller e3 1/0loopback localRelated Commands
loopback (t3)
To loop an entire T3 line toward the line and back toward the router, use the loopback command in controller configuration mode. To remove the loop, use the no form of this command.
loopback {local | network {line | payload} | remote}
no loopback
Syntax Description
Defaults
The default is local.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command for troubleshooting purposes. To verify that a loopback is configured on the interface, use the show controllers (t3/e3) EXEC command. Note that remote loopback is available only in C-bit parity mode.
Examples
The following example configures the controller located in slot 1, port 0 for a local loopback:
controller t3 1/0loopback localRelated Commands
mdl (t3)
To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification, use the mdl command in interface configuration mode. To remove the message, use the no form of this command.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
no mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
Syntax Description
Defaults
No MDL message is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the show controllers command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.
Note
MDL is supported only when framing is set to C-bit parity.
Examples
The following example shows the mdl commands configured on a T3 controller in slot 1, port 0:
!controller T3 1/0clock source linemdl string eic IDmdl string lic LocationIDmdl string fic FrameIDmdl string unit Unitmdl string pfi Facilitymdl string port PortNumbermdl string generator factoryAmdl transmit pathmdl transmit idle-signalmdl transmit test-signalRelated Commands
national bit (e3)
To set the E3 national bit in the G.751 frame used by the E3 controller, use the national bit command in controller configuration mode. To return to the default national bit, use the no form of this command.
national bit {0 | 1}
no national bit
Syntax Description
Defaults
The default value is 1.
Command Modes
Controller configuration
Command History
Usage Guidelines
The national bit command sets bit 12 in the E3 frame.
When framing G.751 is used, bit 11 of the G.751 frame is reserved for national use and is set to 1 by default.
Configure national bit 1 only when required for interoperability with your telephone company.
Examples
The following example sets the national bit to 1:
controller t3 1/0national bit 1scramble (t3/e3)
To enable scrambling (encryption) of the payload on the T3 or E3 controller, use the scramble command in interface configuration mode. To disable scrambling, use the no form of this command.
scramble
no scramble
Syntax Description
This command has no arguments or keywords.
Defaults
Scrambling is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
T3 or E3 scrambling is used to assist clock recovery on the receiving end. Scrambling is designed to randomize the pattern of 1s and 0s carried in the physical layer frame. Randomizing the digital bits can prevent continuous, nonvariable bit patterns—in other words, long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.
Scrambling prevents some bit patterns from being mistakenly interpreted as alarms by switches placed between the data service units.
The local interface configuration must match the remote interface configuration. For example, if you enable scrambling on the local port, you must also do the same for the remote port.
To verify that scrambling is configured on the interface, use the show interfaces serial EXEC command.
For T3 controllers, all the DSU modes support scrambling except the Clear mode.
For E3 controllers, only Kentrox mode supports scrambling.
Examples
The following example enables scrambling on the controller in slot 1, port 0:
interface serial 1/0scrambleRelated Commands
Command Descriptionshow interfaces serial
Displays information that is specific to the interface hardware.
show controllers (t3/e3)
To display information about a T3 or E3 controller, use the show controllers command in EXEC mode.
show controllers {t3 | e3} slot/port [brief | tabular]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Examples
The following are samples of output from the show controllers command:
Router# show controllers e3 2/0E3 2/0 is down.Applique type is Subrate E3Transmitter is sending remote alarm.Receiver has loss of signal.Framing is G751, Clock Source is Internal.Data in current interval (450 seconds elapsed):0 C-bit Coding Violation0 P-bit Err Secs, 0 P-bit Severely Err Secs0 Severely Err Framing Secs, 450 Unavailable Secs0 Line Errored Secs, 0-C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 1:0 C-bit Coding Violation0 P-bit Err Secs, 0 P-bit Severely Err Secs0 Severely Err Framing Secs, 900 Unavailable Secs0 Line Errored Secs, 0-C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 1 15 minute intervals):0 C-bit Coding Violation0 P-bit Err Secs, 0 P-bit Severely Err Secs0 Severely Err Framing Secs, 900 Unavailable Secs0 Line Errored Secs, 0-C-bit Errored Secs, 0 C-bit Severely Errored SecsRouter# show controllers e3 2/0 briefE3 2/0 is down.Applique type is Subrate E3Transmitter is sending remote alarm.Receiver has loss of signal.Framing is G571, Clock Source is Internal.Router# show controllers e3 2/0 tabularE3 2/0 is down.Applique type is Subrate E3Transmitter is sending remote alarm.Receiver has loss of signal.Framing is G571, Clock Source is Internal.INTERNAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES18:10-18:21 0 0 0 0 0 0 680 0 0 017:55-18:10 0 0 0 0 0 0 900 0 0 0Total 0 0 0 0 0 0 900 0 0 0The following table describes the significant fields shown in this display and includes other fields that might occur in different configurations.
Glossary
backplane—The physical connection between an interface processor or card and the data buses and the power distribution buses inside a chassis.
BER—bit error rate. Ratio of received bits that contain errors.
CSU—channel service unit. Digital interface device that connects end-user equipment to the local digital telephone loop. Often referred to together with DSU as CSU/DSU.
DS-3—digital signal level 3. Framing specification used for sending digital signals at 44.736 Mbps on a T3 facility.
DSU—data service unit. Device used in digital transmission that adapts the physical interface on a DTE device to a transmission facility, such as T1 or E1. The DSU also is responsible for such functions as signal timing. Often referred to together with CSU as CSU/DSU.
E3—Wide-area digital transmission scheme used predominantly in Europe that carries data at a rate of 34.368 Mbps. E3 lines can be leased for private use from common carriers.
FEAC—far-end alarm code.
Frame Relay— industry-standard, switched data link layer protocol that handles multiple virtual circuits using HDLC encapsulation between connected devices. Frame Relay is more efficient than X.25, the protocol for which it generally is considered a replacement.
HDLC—High-Level Data Link Control. Bit-oriented synchronous data link layer protocol developed by ISO. Derived from SDLC, HDLC specifies a data encapsulation method on synchronous serial links using frame characters and checksums.
MDL—Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification. Also, the Cisco Message Definition Language—a high-level language used to specify protocols and protocol conversion operations on the VSC.
OIR—online insertion and removal. Feature that permits the addition, the replacement, or the removal of cards without interrupting the system power, entering console commands, or causing other software or interfaces to shut down.
PPP—Point-to-Point Protocol. Successor to SLIP that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. Whereas SLIP was designed to work with IP, PPP was designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.
Subrate—Less than the standard rate of transmission, which is defined at the voice-grade rate of 64 kbps.
T3—Digital WAN carrier facility. T3 sends DS3-formatted data at 44.736 Mbps through the telephone switching network.
TDM—time-division multiplexing. Technique in which information from multiple channels can be allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to send.

