Table Of Contents
Channelized T3 Interface Processor and Port Adapter
Configure External T1 Channels
Troubleshoot the T3 and T1 Channels
Monitor and Maintain the CT3IP
CT3IP Configuration with Default Values Accepted
CT3IP External Ports Configuration
Channelized T3 Interface Processor and Port Adapter
Description
The Channelized T3 Interface Processor (CT3IP) is available on Cisco 7500 series routers and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). The Channelized T3 dual-wide port adapter (PA-CT3/4T1) can be used in Cisco 7200 series routers.
Note
Throughout this document are references to the CT3IP. However, the term CT3IP also applies to the PA-CT3/4T1. Wherever you see a description of a feature of the CT3IP, the feature is also available in the PA-CT3/4T1.
The CT3IP is a fixed-configuration interface processor based on the second-generation Versatile Interface Processor (VIP2). The CT3 channelized port adapter (PA-CT3/4T1) is a dual-wide module. The CT3IP or PA-CT3/4T1 has four T1 connections via DB-15 connectors and one DS3 connection via BNC connectors. Each DS3 interface can provide up to 28 T1 channels (a single T3 group). Each channel is presented to the system as a serial interface that can be configured individually. The CT3IP or PA-CT3/4T1 can transmit and receive data bidirectionally at the T1 rate of 1.536 Mbps. The four T1 connections use 100-ohm twisted-pair serial cables to external channel service units (CSUs) or to a MultiChannel Interface Processor (MIP) on the same router or on another router. For wide-area networking, the CT3IP or PA-CT3/4T1 can function as a concentrator for a remote site.
As mentioned above, the CT3IP or PA-CT3/4T1 provides 28 T1 channels for serial transmission of data. Each T1 channel can be configured to use a portion of the T1 bandwidth or the entire T1 bandwidth for data transmission. Bandwidth for each T1 channel can be configured for n x 56 kbps or n x 64 kbps (where n is 1 to 24). The unused portion of the T1 bandwidth, when not running at full T1 speeds, is filled with idle channel data. The CT3IP or PA-CT3/4T1 does not support the aggregation of multiple T1 channels (called inverse muxing or bonding) for higher bandwidth data rates.
The first three T1 channels of the CT3IP or PA-CT3/4T1 can be broken out to the three DSUP-15 connectors on the CPT3IP or PA-CT3/4T1 so the T1 can be further demultiplexed by the MIP on the same router or on another router or by other multiplexing equipment. When connecting to the MIP, you configure a channelized T1 as described in the "Configure External T1 Channels" section later in this chapter. This is referred to as an external T1 channel.
The CT3IP or PA-CT3/4T1 supports the following WAN protocols:
•
Frame Relay
•
HDLC
•
PPP
•
SMDS Data Exchange Interface (DXI)
The CT3IP or PA-CT3/4T1 meets ANSI T1.102-1987 and BELCORE TR-TSY-000499 specifications for T3 and meets ANSI 62411 and BELCORE TR499 specifications for T1. The CT3IP or PA-CT3/4T1 provides internal channel service unit (CSU) functionality and includes reporting performance data statistics, transmit and receive statistics, and error statistics. The CT3IPor PA-CT3/4T1 supports RFC 1406 (T1 MIB) and RFC 1407 (T3 MIB).
External T1 channels do not provide CSU functionality and must connect to an external CSU.
Platforms
This feature is supported on these platforms:
•
Cisco 7500 series routers
•
Cisco 7200 series routers
•
Cisco 7000 series routers with the RSP7000 and RSP7000CI
Configuration Tasks
Perform the tasks in the following sections to configure the CT3IP (all tasks are optional except for the second task):
•
Configure External T1 Channels
•
Troubleshoot the T3 and T1 Channels
•
Monitor and Maintain the CT3IP
After you configure the T1 channels on the CT3IP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 channel. For more information, refer to the "Configure a Synchronous Serial Interface" section in the "Configuring Interfaces" chapter of the Configuration Fundamentals Configuration Guide.
For CT3IP configuration examples, see the "Configuration Examples" section later in this chapter.
For information on other commands that can be used by the CT3IP interface, refer to the Cisco IOS Release 11.2 configuration guides.
Configure the T3 Controller
If you do not modify the configuration of the CT3IP, the configuration defaults shown in are used.
Table 37 CT3IP Controller Defaults
Attribute Default ValueFraming
auto-detect
Cable length
224 feet
Clock source
internal
If you need to change any of the default configuration attributes, complete the first task in global configuration mode followed by any of the optional tasks in controller configuration mode:
Note
The port adapter and port numbers for the CT3IP are 0.
Note
Although you can specify a cable length from 0 to 450 feet, the hardware only recognizes two ranges: 0 to 224 and 225 to 450. For example, entering 150 feet uses the 0 to 224 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 0 to 224 range. However, if you change the cable length to 250, the 225 to 450 range is used. The actual number you enter is stored in the configuration file.
Configure Each T1 Channel
You must configure the timeslots used by each T1 channel on the CT3IP. Optionally you can specify the speed, framing format, and clock source used by each T1 channel. If you do not specify the speed, framing format, and clock source used by each T1 channel, the configuration defaults shown in are used.
Table 38 CT3IP T1 Channel Defaults
Attribute Default ValueSpeed
64 kbps
Framing
esf
Clock source
internal
Linecode
b8zs
T1 yellow alarm
detection and generation
To specify the timeslots used by each T1 channel, complete the following tasks beginning in global configuration mode:
Note
The 56-kbps speed is valid only for T1 channels 21 through 28.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
If you need to change any of the default configuration attributes, complete the first task in global configuration mode followed by any of the optional tasks in controller configuration mode:
Note
If you select ami line coding, you must also invert the data on the T1 channel by using the invert data interface command. To do so, first use the interface serial global configuration command to select the T1 channel and enter interface configuration mode.
Note
If you select sf framing, you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with sf framing.
After you configure the T1 channels on the CT3IP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 channel. For more information, refer to the "Configure a Synchronous Serial Interface" section in the "Configuring Interfaces" chapter of the Configuration Fundamentals Configuration Guide.
To enter interface configuration mode and configure the serial interface that corresponds to a T1 channel, perform the following task in global configuration mode:
Note
The port adapter and port numbers for the CT3IP are 0.
In addition to the commands in the "Configure a Synchronous Serial Interface" chapter, the invert data interface command can be used to configure the T1 channels on the CT3IP. If the T1 channel on the CT3IP is using AMI line coding, you must invert the data. For information on the invert data interface command, refer to the "Synchronous Serial Port Adapters" chapter later in this document. For more information, see the t1 linecode controller command.
Configure External T1 Channels
The first three T1 channels (1, 2, and 3) of the CT3IP can be broken out to the DSUP-15 connectors on the CPT3IP. This way, the T1 channel can be further demultiplexed by the MIP on the same router, another router, or other multiplexing equipment.
Note
If a T1 channel that was previously configured as a serial interface is broken out to the external T1 port, that interface and its associated configuration remain intact while the channel is broken out to the external T1 port. The serial interface is not usable during the time the T1 channel is broken out to the external T1 port; however, the configuration remains to facilitate the return of the T1 channel to a serial interface with the no t1 external command.
To configure a T1 channel as an external port, complete the following tasks beginning in EXEC mode:
Note
Only T1 channels 1 through 3 can be configured as an external T1.
Note
Although you can specify a cable length from 0 to 655 feet, the hardware only recognizes the following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example, entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 134 to 266 range. However, if you change the cable length to 399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.
After you configure the external T1 channel, you can continue configuring it as a channelized T1 from the MIP. All channelized T1 commands might not be applicable to the T1 interface. To define the T1 controller and enter controller configuration mode, perform the following task in global configuration mode:
After you configure the channelized T1 on the MIP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 interface. To enter interface configuration mode and configure the serial interface that corresponds to a T1 channel group, perform the following task beginning in global configuration mode:
Task CommandDefine the serial interface for a T1 channel on the MIP (values are 1 to 28) and enter interface configuration mode.
interface serial slot/port:t1-channel
For more information, refer to the "Configure Channelized T1" section and the "Configure a Synchronous Serial Interface" section in the "Configuring Interfaces" chapter of the Configuration Fundamentals Configuration Guide. For an example of configuring an external T1 channel, see the "Configuration Examples" section later in this chapter.
Troubleshoot the T3 and T1 Channels
You can use the following methods to troubleshoot the CT3IP using Cisco IOS software:
•
Test the T1 by using the t1 test controller configuration command and the test port
•
Loop the T1 by using loopback interface configuration commands
•
Loop the T3 by using loopback controller configuration commands
Enable Test Port
You can use the T1 test port available on the CT3IP to break out any of the 28 T1 channels for testing (for example, 24-hour BERT testing as is commonly done by telephone companies before a line is brought into service).
The T1 test port is also available as an external port. For more information on configuring an external port, see the previous section, "Configure External T1 Channels."
Note
If a T1 channel that was previously configured as a serial interface is broken out to the T1 test port, that interface and its associated configuration remain intact while the channel is broken out to the T1 test port. The serial interface is not usable during the time the T1 channel is broken out to the T1 test port; however, the configuration remains to facilitate the return of the T1 channel to a serial interface with the no t1 test command.
To enable a T1 channel as a test port, complete the following tasks beginning in global configuration mode:
To disable a T1 channel as a test port, complete the following tasks beginning in global configuration mode:
Note
Although you can specify a cable length from 0 to 655 feet, the hardware only recognizes the following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example, entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 134 to 266 range. However, if you change the cable length to 399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.
Loopback T1 Channels
You can perform the following types of loopbacks on a T1 channel:
•
Local—Loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network (see ).
•
Network line—Loops the data back toward the network before the T1 framer and automatically sets a local loopback (see ).
•
Network payload—Loops just the payload data back toward the network at the T1 framer and automatically sets a local loopback (see ).
•
Remote line inband—Sends a repeating 5-bit inband pattern (00001) to the remote end requesting that it enter into a network line loopback (see ).
•
Remote payload FDL ANSI—Sends a repeating, 16-bit ESF data link code word (00010100 11111111) to the remote end requesting that it enter into a network payload loopback.
•
Remote line FDL ANSI—Sends a repeating, 16-bit ESF data link code word (00001110 11111111) to the remote CSU end requesting that it enter into a network line loopback.
•
Remote line FDL Bellcore—Sends a repeating, 16-bit ESF data link code word (00001110 11111111) to the remote SmartJack end requesting that it enter into a network line loopback.
To enable loopbacks on a T1 channel, complete the first task beginning in global configuration mode followed by any one of the following tasks:
Note
The port adapter and port numbers for the CT3IP are 0.
shows an example of a local loopback in which the loopback occurs in the T1 framer.
Figure 6 CT3IP Local Loopback
shows an example of a network line loopback in which just the data is looped back toward the network (before the T1 framer).
Figure 7 CT3IP Network Line Loopback
shows an example of a network payload loopback in which just the payload data is looped back toward the network at the T1 framer.
Figure 8 CT3IP Network Payload Loopback
shows an example of a remote inband loopback in which the network line enters a line loopback.
Figure 9 CT3IP Remote Loopback
Loopback T3
You can put the entire T3 line into loopback mode (that is, all T1 channels are looped) by using the following types of loopbacks:
•
Local—Loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network.
•
Network—Loops the data back toward the network (before the T1 framer).
•
Remote —Sends a FEAC (far-end alarm control) request to the remote end requesting that it enter into a network line loopback. FEAC requests (and therefore remote loopbacks) are only possible when the T3 is configured for C-bit framing. The type of framing used is determined by the equipment you are connecting to. (For more information, see the framing controller command.)
To enable loopbacks on the T3 (and all T1 channels), complete the first task beginning in global configuration mode followed by any one of the following tasks:
Note
The port adapter and port numbers for the CT3IP are 0.
Monitor and Maintain the CT3IP
After configuring the new interface, you can monitor the status and maintain the CT3IP in the Cisco 7000 series routers with an RSP7000 or in the Cisco 7500 series routers by using the show commands. To display the status of any interface, complete one of the following tasks in EXEC mode:
Configuration Examples
The examples in this section show how to configure the Channelized T3 Interface Processor (CT3IP). The first example shows how to configure two of the T1 channels of the channelized T3 controller. The second example shows how to configure one of the T1 channels of the channelized T3 controller as an external port for further channelization on the Multichannel Interface Processor (MIP).
For more information, refer to the "Configure the T3 Controller" and "Configure External T1 Channels" sections earlier in this chapter.
CT3IP Configuration with Default Values Accepted
In the following example, timeslots 1 through 24 (the entire T1 bandwidth) are assigned to T1 channel 16 and timeslots 1 through 5 and 20 through 23 (fractional T1 bandwidth) are assigned to T1 channel 10 for the CT3IP in slot 9. The default framing, cable length, and clock source are accepted for the T3, and the default speed, framing, clock source, and line code are accepted for each T1 channel. Each T1 channel is assigned an IP address. Other interface configuration commands can be assigned to the T1 channel at this time.
router(config)# controller t3 9/0/0router(config-controll)# t1 16 timeslot 1-24router(config-controll)# t1 10 timeslot 1-5,20-23router(config-controll)# exitrouter(config)# interface serial 9/0/0:16router(config-if)# ip address 10.20.20.1 255.255.255.0router(config-if)# exitrouter(config)# interface serial 9/0/0:10router(config-if)# ip address 10.20.20.3 255.255.255.0router(config-if)# exitrouter(config)#CT3IP External Ports Configuration
In the following example, T1 channel 1 on the CT3IP in slot 9 is broken out as an external port so that it can be further channelized on the MIP in slot 3. The cable length is 300 feet, and the default line coding format on the T1 channel is used. Because the default line coding format on the T1 channel is B8ZS and the default line coding on the MIP is AMI, the line coding on the MIP is changed to B8ZS.
router(config)# controller t3 9/0/0router(config-controll)# t1 external 1 cablelength 300router(config-controll)# exitrouter(config)# controller t1 3/0router(config-controll)# linecode b8zsrouter(config-controll)# channel-group 1 timeslots 1router(config)# interface serial 3/0:1router(config-if)# ip address 10.20.20.5 255.255.255.0router(config-if)# exitrouter(config)#Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references.
cablelength
To specify the distance of the cable from the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers to the network equipment, use the cablelength controller configuration command. Use the no form of this command to restore the default cable length.
cablelength feet
no cablelengthSyntax Description
Default
224 feet
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the cablelength command, the default cable length of 224 feet is used by the CT3IP.
Note
Although you can specify a cable length from 0 to 450 feet, the hardware only recognizes two ranges: 0 to 224 and 225 to 450. For example, entering 150 feet uses the 0 to 224 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 0 to 224 range. However, if you change the cable length to 250, the 225 to 450 range is used. The actual number you enter is stored in the configuration file.
Example
In the following example, the cable length for the CT3IP is set to 300:
controller t3 9/0/0cablelength 300clear interface
To reset the hardware logic on an interface, use the clear interface EXEC command.
clear interface type number
clear interface type slot/port (Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series with
a Packet OC-3 Interface Processor)
clear interface [type slot/port-adapter/port] (ports on VIP2s in the Cisco 7000 series and
Cisco 7500 series)
clear interface [type slot/port] (ports on VIP2s in the Cisco 7200 series)
clear interface type slot/port [:channel-group] (Cisco 7000 series MIP T1 interface)
clear interface type slot/port-adapter/port [:t1-channel] (CT3IP in Cisco 7000 series routers
with RSP7000 and Cisco 7500 series)
clear interface type slot/port [:t1-channel] (PA-CT3/4T1 in Cisco 7200 series routers)Syntax Description
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.0.
This command was modified in Cisco IOS Release 11.1 CA to include command syntax for the CT3IP.
Under normal circumstances, you do not need to clear the hardware logic on interfaces.
lists the type keywords available for the clear interface command.
Examples
The following example resets the interface logic on HSSI interface 1:
clear interface hssi 1The following example resets the interface logic on Packet OC-3 interface 0 on the POSIP in slot 1:
clear interface pos 1/0The following example resets the interface logic on T1 0 on the CT3IP in slot 9:
clear interface serial 9/0/0:0clock source
To specify where the clock source is obtained for use by the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the clock source controller configuration command. Use the no form of this command to restore the default clock source.
clock source {internal | line}
no clock sourceSyntax Description
internal
Specifies that the internal clock source is used. This is the default.
line
Specifies that the network clock source is used.
Default
internal
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the clock source command, the default clock source of internal is used by the CT3IP.
Select line clocking when the CT3IP is connected to a device known to provide a good DS3 clock signal.
Note
When performing a coaxial loop between the transmit and receive ports, you must select internal clocking because there is no external equipment connected that can provide a clock signal.
You can also set the clock source for each T1 channel by using the t1 clock source controller configuration command.
Example
In the following example, the clock source for the CT3IP is set to line:
controller t3 9/0/0clock source lineRelated Command
controller t3
To configure the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers or to configure the PA-CT3/4T1 in Cisco 7200 series routers, use the controller t3 global configuration command.
controller t3 slot/port-adapter/port (Cisco 7500 series and Cisco 7000 series routers with the
RSP7000 and RSP7000CI)
controller t3 slot/port (Cisco 7200 series)Syntax Description
slot
Backplane slot number.The value varies depending on the platform.
port-adapter
Port adapter and port numbers for the CT3IP are 0.
port
Port adapter and port numbers for the CT3IP are 0.
Default
No T3 controller is configured.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
This command is used to configure the CT3IP and the 28 T1 channels. After the T1 channels are configured, continue to configure each T1 channel as a serial interface by using the interface serial global configuration command.
Example
In the following example, the CT3IP in slot 3 is configured:
controller t3 3/0/0Related Command
interface serial
description (controller)
To add a description to an E1 or T1 controller or the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the description controller configuration command. Use the no form of this command to remove the description.
description string
no descriptionSyntax Description
string
Comment or a description to help you remember what is attached to the interface. Up to 80 characters.
Default
No description is added.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command was modified in Cisco IOS Release 11.1 CA to include the CT3IP controller.
The description command is meant solely as a comment to be put in the configuration to help you remember what certain controllers are used for. The description affects the CT3IP and MIP interfaces only and appears in the output of the show controller t3, show controller e1, show controller t1, and show running-config EXEC commands.
Example
The following example describes a 3174 controller:
controller t1description 3174 Controller for test labRelated Commands
show controller e1
show controller t1
show controller t3
show running-configframing (T3)
To specify the type of framing used by the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the framing controller configuration command. Use the no form of this command to restore the default framing type.
framing {c-bit | m23 | auto-detect}
no framingSyntax Description
Default
auto-detect
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the framing command, the default auto-detect is used by the CT3IP to automatically determine the framing type received from the far-end equipment.
Because the CT3IP supports the Application Identification Channel (AIC) signal, the setting for the framing might be overridden by the CT3IP firmware.
You can also set the framing for each T1 channel by using the t1 framing controller configuration command.
Example
In the following example, the framing for the CT3IP is set to C-bit:
controller t3 9/0/0framing c-bitRelated Command
loopback (T1)
To loop individual T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the loopback interface configuration command. Use the no form of this command to remove the loopback.
loopback [local | network {line | payload} | remote {line {fdl {ansi | bellcore} | inband} |
payload [fdl] [ansi]}]
no loopbackSyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
Use this command for troubleshooting purposes.
To better diagnose T1 provisioning problems, you can place the the remote CSU or remote SmartJack into loopback. The loopback remote line fdl interface configuration command allows you to place either the CSU or the SmartJack into loopback:
•
ansi—Places the CSU into loopback, per the ANSI T1.403 Specification
•
bellcore—Places the SmartJack into loopback, per the TR-TSY-000312 Specification
When both are configured, transmission of LOF indication (yellow alarm) takes priority over transmission of some FDL messages.
If the remote loopback appears not to be working, use the show controllers t3 command to determine if the given T1 is currently attempting to transmit a LOF indication (yellow alarm):
Router# show controllers t3 0/0/0:2T3 0/0/0 is up.CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9Mx H/W version: 2, Mx ucode ver: 1.34T1 2 is down, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per AT&T 54016 spec.Transmitter is sending LOF Indication.Receiver is getting AIS.If the transmitter is sending a LOF indication, as in the previous example, stop the transmission of the LOF indication (yellow alarm) with the no t1 yellow generation configuration command as shown in the following example:
Router(config)# controllers t3 0/0/0Router(config-controll)# no t1 2 yellow generationRouter(config-controll)# ^DTo verify that the transmission of the LOF indication (yellow alarm) has stopped, use the show controllers t3 command:
Router# show controllers t3 0/0/0:2T3 0/0/0 is up.CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9Mx H/W version: 2, Mx ucode ver: 1.34T1 2 is down, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per AT&T 54016 spec.Receiver is getting AIS.Framing is ESF, Line Code is B8ZS, Clock Source is Internal.Yellow Alarm Generation is disabledNow retry the remote loopback command. When diagnosis is complete, remember to re-enable the LOF indication (yellow alarm). You can also loopback all the T1 channels by using the loopback (CT3IP) interface configuration command.
For more information, refer to the "Troubleshoot the T3 and T1 Channels" section earlier in this chapter.
Example
The following example configures T1 channel 5 for a local loopback:
interface serial 3/0/0:5loopback localRelated Command
loopback (T3)
To loop the entire T3 (all 28 T1 channels) on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the loopback controller configuration command. Use the no form of this command to remove the loopback.
loopback [local | network | remote]
no loopbackSyntax Description
Default
Disabled
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
Use this command for troubleshooting purposes.
You can also loopback each T1 channel by using the loopback interface configuration command.
For more information, refer to the "Troubleshoot the T3 and T1 Channels" section earlier in this chapter.
Example
The following example configures the CT3IP for a local loopback:
controller t3 3/0/0loopback localRelated Command
show controller t3
To display information about the Channelized T3 Interface Processor (CT3IP) on Cisco 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers or to display information about the PA-CT3/4T1 in Cisco 7200 series routers, use the show controller t3 privileged EXEC command.
show controller t3 [slot/port-adapter/port [:t1-channel]] [remote performance [brief |
tabular]] (Cisco 7500 series and Cisco 7000 series routers with the RSP7000
and RSP7000CI)
show controller t3 [slot/port [:t1-channel]] [remote performance [brief |tabular]]
(Cisco 7200 series)Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Sample Displays
The following is partial sample output from the show controller t3 command:
Router# show controller t3 3/0/0T3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0Mx H/W version: 2, Mx ucode ver: 1.24Applique type is Channelized T3No alarms detected.FEAC code received: No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is Internal.Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OKData in current interval (39 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation0 P-bit Err Secs, 0 P-bit Severely Err Secs0 Severely Err Framing Secs, 0 Unavailable Secs0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 1 15 minute intervals):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 SecsT1 1 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24No alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal.Data in current interval (50 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs, 0 Stuffed SecsTotal Data (last 1 15 minute intervals):0 Line Code Violations, 0 Path Code Violations,0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs, 0 Stuffed Secs...T1 15 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24No alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal.Data in current interval (69 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs, 0 Stuffed SecsTotal Data (last 1 15 minute intervals):0 Line Code Violations, 0 Path Code Violations,0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs, 0 Stuffed SecsThe following is partial sample output from the show controller t3 brief command:
router# show controller t3 3/0/0 briefT3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0Mxt H/W version: 2, Mxt ucode ver: 1.24Applique type is Channelized T3No alarms detected.FEAC code received: No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is Internal.Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OKT1 1 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24No alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal....T1 28 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24No alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal.The following is partial sample output from the show controllers t3 tabular command:
router# show controllers t3 3/0/0 tabularT3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 1.2, CT3 F/W Version: 2.1.0Mx H/W version: 2, Mx ucode ver: 1.25Applique type is Channelized T3No alarms detected.MDL transmission is disabledFEAC code received: No code is being receivedFraming is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.Ext1: AIS, Ext2: LOS, Ext3: LOS, Test: LOSINTERVAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES08:56-09:11 0 0 0 0 0 0 0 0 0 008:41-08:56 0 0 0 0 0 0 0 0 0 008:26-08:41 0 0 0 0 0 0 0 0 0 0Total 0 0 0 0 0 0 0 0 0 0T1 2 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Line Code is B8ZS, Clock Source is Internal.INTERVAL LCV PCV CSS SELS LES DM ES BES SES UAS SS08:56-09:11 0 0 0 0 0 0 0 0 0 0 008:41-08:56 0 0 0 0 0 0 0 0 0 0 008:26-08:41 0 0 0 0 0 0 0 0 0 0 0Total 0 0 0 0 0 0 0 0 0 0 0describes the show controller t3 display fields.
show interfaces serial
To display information about a serial interface, use the show interfaces serial privileged EXEC command.
show interfaces serial [number] [accounting]
show interfaces serial [number [:channel-group] [accounting] (Cisco 4000 series)
show interfaces serial [slot/port [:channel-group]] [accounting] (Cisco 7000 series)
show interfaces serial [slot/port-adapter/port] [serial] (ports on VIPs in the
Cisco 7000 and Cisco 7500 series)
show interfaces serial [slot/port] [serial] (ports on VIPs in the Cisco 7200 series)
show interfaces serial [slot/port-adapter/port] [:t1-channel] [accounting | crb] (CT3IP in
Cisco 7000 series routers with RSP7000 and Cisco 7500 series)
show interfaces serial [slot/port] [:t1-channel] [accounting | crb] (PA-CT3/4T1 in
Cisco 7200 series)Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.0 for the Cisco 4000 series.
This command first appeared in Cisco IOS Release 11.0 for the Cisco 7000 series.This command was modified in Cisco IOS Release 11.1 CA to include the CT3IP.
Sample Displays
The following is sample output from the show interfaces command for a synchronous serial interface:
Router# show interfaces serialSerial 0 is up, line protocol is upHardware is MCI SerialInternet address is 150.136.190.203, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)Last input 0:00:07, output 0:00:00, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec16263 packets input, 1347238 bytes, 0 no bufferReceived 13983 broadcasts, 0 runts, 0 giants2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort1 carrier transitions22146 packets output, 2383680 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restartsdescribes significant fields shown in the display.
The following is sample output of the show interfaces serial command for the CT3IP serial interface:
Router# show interfaces serial 3/0/0:25Serial3/0/0:25 is up, line protocol is upHardware is cyBus T3Internet address is 25.25.25.2/24MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 12/255Encapsulation HDLC, loopback not set, keepalive not setLast input 00:19:01, output 00:11:49, output hang neverLast clearing of "show interface" counters 00:19:39Input queue: 0/75/0 (size/max/drops); Total output drops: 0Queueing strategy: weighted fairOutput queue: 0/64/0 (size/threshold/drops)Conversations 0/1 (active/max active)Reserved Conversations 0/0 (allocated/max allocated)5 minute input rate 69000 bits/sec, 90 packets/sec5 minute output rate 71000 bits/sec, 90 packets/sec762350 packets input, 79284400 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants150 input errors, 0 CRC, 0 frame, 150 overrun, 0 ignored, 0 abort763213 packets output, 80900472 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitions no alarm presentTimeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 5non-inverted dataMost fields are described in . Fields relevant to the CT3IP are described in .
The following is sample output of the show interfaces serial command for the HDLC synchronous serial interface on a Cisco 7000:
Router# show interfaces serial 1/0Serial1/0 is up, line protocol is upHardware is cxBus SerialInternet address is 150.136.190.203, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)Last input 0:00:07, output 0:00:00, output hang neverLast clearing of "show interface" counters 2w4dOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec16263 packets input, 1347238 bytes, 0 no bufferReceived 13983 broadcasts, 0 runts, 0 giants2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort22146 packets output, 2383680 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restarts1 carrier transitionsThe following is sample output of the show interfaces serial command for a G.703 interface on which framing is enabled:
Router# show interfaces serial 2/3Serial2/3 is up, line protocol is upHardware is cxBus SerialInternet address is 5.4.4.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive not setLast input 0:00:21, output 0:00:21, output hang neverLast clearing of "show interface" counters neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec53 packets input, 7810 bytes, 0 no bufferReceived 53 broadcasts, 0 runts, 0 giants2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort56 packets output, 8218 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restarts1 carrier transitions2 alarm indications, 333 remote alarms, 332 rx LOF, 0 rx LOSRTS up, CTS up, DTR up, DCD up, DSR upBER inactive, NELR inactive, FELR inactivedescribes significant fields shown in the display.
Sample Display with Frame Relay Encapsulation
When using the Frame Relay encapsulation, use the show interfaces command to display information on the multicast DLCI, the DLCI of the interface, and the LMI DLCI used for the local management interface.
The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and the frame-relay local-dlci configuration commands, or provided through the local management interface. The status information is taken from the LMI, when active.
The following is sample output from the show interfaces serial command when using Frame Relay encapsulation:
Router# show interfaces serialSerial 2 is up, line protocol is upHardware type is MCI SerialInternet address is 131.108.122.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)multicast DLCI 1022, status defined, activesource DLCI 20, status defined, activeLMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2Last input 7:21:29, output 0:00:37, output hang neverOutput queue 0/100, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec47 packets input, 2656 bytes, 0 no bufferReceived 5 broadcasts, 0 runts, 0 giants5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 57 abort518 packets output, 391205 bytes0 output errors, 0 collisions, 0 interface resets, 0 restarts1 carrier transitionsIn this display, the multicast DLCI has been changed to 1022 with the frame-relay multicast-dlci interface configuration command.
The display shows the statistics for the LMI are the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). See the Frame Relay Interface specification for additional explanations of this output.
Sample Display with ANSI LMI
For a serial interface with the ANSI LMI enabled, use the show interfaces command to determine the LMI type implemented.
The following is a sample display from the show interfaces output for a serial interface with the ANSI LMI enabled:
Router# show interfaces serialSerial 1 is up, line protocol is upHardware is MCI SerialInternet address is 131.108.121.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive setLMI DLCI 0, LMI sent 10, LMI stat recvd 10LMI type is ANSI Annex DLast input 0:00:00, output 0:00:00, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 1 packets/secFive minute output rate 1000 bits/sec, 1 packets/sec261 packets input, 13212 bytes, 0 no bufferReceived 33 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort238 packets output, 14751 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restartsNotice that the show interfaces output for a serial interface with ANSI LMI shown in this display is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. describes the few differences that exist.
Sample Display with LAPB Encapsulation
Use the show interfaces command to display operation statistics for an interface using LAPB encapsulation.
The following is sample output from the show interfaces command for a serial interface using LAPB encapsulation:
Router# show interfacesLAPB state is DISCONNECT, T1 3000, N1 12000, N2 20, K7, TH 3000Window is closedIFRAMEs 12/28 RNRs 0/1 REJs 13/1 SABMs 1/13 FRMRs 3/0 DISCs 0/11shows the fields relevant to all LAPB connections.
show the fields relevant to PPP connections.
Sample Display with SDLC Connections
Use the show interfaces command to display the SDLC information for a given SDLC interface. The following is sample output from the show interfaces command for an SDLC primary interface supporting the SDLLC function:
Router# show interfacesSerial 0 is up, line protocol is upHardware is MCI SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation SDLC-PRIMARY, loopback not setTimers (msec): poll pause 100 fair poll 500. Poll limit 1[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: noneSDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10largest token ring frame 2052]SDLC addr C1 state is CONNECTVS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0Poll: clear, Poll count: 0, chain: p: C1 n: C1SDLLC [largest SDLC frame: 265, XID: disabled]Last input 00:00:02, output 00:00:01, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 517 bits/sec, 30 packets/secFive minute output rate 672 bits/sec, 20 packets/sec357 packets input, 28382 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort926 packets output, 77274 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restarts2 carrier transitionsshows the fields relevant to all SDLC connections.
shows other data given for each SDLC secondary configured to be attached to this interface.
Sample Display with SDLLC
Use the show interfaces serial command to display the SDLLC statistics for SDLLC configured interfaces.
The following is sample output from the show interfaces serial command for an a serial interface configured for SDLLC:
Router# show interfaces serialSerial 0 is up, line protocol is upHardware is MCI SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation SDLC-PRIMARY, loopback not setTimers (msec): poll pause 100 fair poll 500. Poll limit 1[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: noneSDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10largest token ring frame 2052]SDLC addr C1 state is CONNECTVS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0Poll: clear, Poll count: 0, chain: p: C1 n: C1SDLLC [largest SDLC frame: 265, XID: disabled]Last input 00:00:02, output 00:00:01, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 517 bits/sec, 30 packets/secFive minute output rate 672 bits/sec, 20 packets/sec357 packets input, 28382 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort926 packets output, 77274 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restarts6608 Last polled device: noneSDLLC [ma: 0000.0C01.14--, ring: 7 brid2 carrier transitionsMost of the output shown in the display is generic to all SDLC encapsulated interfaces and is described in the "LLC2 and SDLC Commands" chapter in the Bridging and IBM Networking Command Reference. shows the parameters specific to SDLLC.
Sample Display with Accounting Option
The following example illustrates the show interfaces serial command with the accounting option on a Cisco 7000 series router:
Router# show interfaces serial 1/0 accountingSerial1/0Protocol Pkts In Chars In Pkts Out Chars OutIP 7344 4787842 1803 1535774Appletalk 33345 4797459 12781 1089695DEC MOP 0 0 127 9779ARP 7 420 39 2340shutdown (controller)
To disable the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the shutdown controller configuration command. To restart a disabled CT3IP, use the no form of this command.
shutdown
no shutdownSyntax Description
This command has no arguments or keywords.
Default
Enabled
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
Shutting down the CT3IP disables all functions on the interface and sends a blue alarm to the network. This command marks the interface as unavailable. To check if the CT3IP is disabled, use the show controller t3 command.
Example
In the following example, the CT3IP is shutdown:
controller t3 9/0/0shutdownRelated Command
t1 clock source
To specify where the clock source is obtained for use by each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the t1 clock source controller configuration command.
t1 channel clock source {internal | line}
Syntax Description
channel
Number between 1 and 28 that indicates the T1 channel.
internal
Specifies that the internal clock source is used. This is the default.
line
Specifies that the network clock source is used.
Default
Internal
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the t1 clock source command, the default clock source of internal is used by all the T1s on the CT3IP.
You can also set the clock source for the CT3IP by using the clock source controller configuration command.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Example
In the following example, the clock source for T1 6 and T1 8 on the CT3IP are set to line:
controller t3 9/0/0t1 6 clock source linet1 8 clock source lineRelated Command
clock source
t1 external
To specify that a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers is used as an external port so the T1 channel can be further multiplexed on the Multichannel Interface Processor (MIP) or other multiplexing equipment, use the t1 external controller configuration command. Use the no form of this command to remove a T1 as an external port.
t1 external channel [cablelength feet] [linecode ami | b8zs]
no t1 external channelSyntax Description
Default
No external T1 is specified.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
The first three T1 channels (1, 2, and 3) of the CT3IP can be broken out to the DSUP-15 connectors on the CPT3IP so the T1 channel can be further demultiplexed by the MIP on the same router or on another router.
After you configure the external T1 channel, you can continue configuring it as a channelized T1 (also referred to as fractional T1) from the MIP. All channelized T1 commands might not be applicable to the T1 interface. After you configure the channelized T1 on the MIP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 interface.
The line coding on the T1 channel and the MIP must be the same. Because the default line coding format on the T1 channel is B8ZS and the default line coding on the MIP is AMI, you must change the line coding on the MIP or on the T1 so that they match.
To determine if the external device connected to the external T1 port is configured and cabled correctly before configuring an external port, use the show controller t3 command and locate the line Ext1... in the display output. The line status can be one of the following:
•
LOS—Loss of signal indicates that the port is not receiving a valid signal. This is the expected state if nothing is connected to the port.
•
AIS—Alarm indication signal indicates that the port is receiving an all-ones signal.
•
OK—A valid signal is being received and the signal is not an all-ones signal.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Note
Although you can specify a cable length from 0 to 655 feet, the hardware only recognizes the following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example, entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 134 to 266 range. However, if you change the cable length to 399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.
Example
In the following example, the T1 1 on the CT3IP is configured as an external port using AMI line coding and a cable length of 300 feet:
controller t3 9/0/0t1 external 1 cablelength 300 linecode amiRelated Command
t1 framing
To specify the type of framing used by the T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the t1 framing controller configuration command.
t1 channel framing {esf | sf}
Syntax Description
Default
Extended super frame (ESF)
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the t1 framing command, the default ESF is used.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Example
In the following example, the framing for the T1 6 and T1 8 on the CT3IP are set to sf:
controller t3 9/0/0t1 6 framing sft1 8 framing sft1 linecode
To specify the type of line coding used by the T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the t1 linecode controller configuration command.
t1 channel linecode {ami | b8zs}
Syntax Description
Default
B8ZS
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If you do not specify the t1 linecode command, the default B8ZS is used.
If you select ami line coding for the T1 channel, you must also invert the data on the T1 channel by using the invert data interface command. This is required because the T1 channel is bundled into the T3 signal, so there are no local T1 line drivers and receivers associated with it. Therefore, the t1 channel linecode ami command does not modify local line driver settings. Rather, it advises the CT3IP what line code the remote T1 is using. The CT3IP uses this information solely for the purpose of determining whether or not to enable the pulse density enforcer for that T1 channel.
When you select b8zs line coding, the pulse density enforcer is disabled. When you select ami line coding, the pulse density enforcer is enabled. To avoid having the pulse density enforcer corrupt data, the T1 channel should be configured for inverted data.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Example
In the following example, the line coding for T1 channel 16 on the CT3IP is set to AMI:
controller t3 9/0/0t1 16 linecode amiexitinterface serial 9/0/0:16invert dataRelated Command
t1 test
To break out a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers to the test port for testing, use the t1 test controller configuration command. Use the no form of this command to remove the T1 channel from the test port.
t1 test channel [cablelength feet] [linecode {ami | b8zs}]
no t1 test channelSyntax Description
Default
No test port is configured
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
You can use the T1 test port available on the CT3IP to break out any of the 28 T1 channels for testing (for example, 24-hour BERT testing as is commonly done by telephone companies before a line is brought into service).
The T1 test port is also available as an external port. For more information on configuring an external port, see the t1 external controller configuration command.
To determine if the external device connected to the T1 test port is configured and cabled correctly before configuring a test port, use the show controller t3 command and locate the line Ext1... in the display output. The line status can be one of the following:
•
LOS—loss of signal indicates that the port is not receiving a valid signal. This is the expected state if nothing is connected to the port.
•
AIS—alarm indication signal indicates that the port is receiving an all-ones signal.
•
OK—a valid signal is being received and the signal is not an all-ones signal.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Note
Although you can specify a cable length from 0 to 655 feet, the hardware only recognizes the following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example, entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there is no change because 200 is within the 134 to 266 range. However, if you change the cable length to 399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.
Example
In the following example, T1 6 on the CT3IP is configured as a test port using the default cable length and line coding:
controller t3 9/0/0t1 test 6Related Commands
t1 timeslot
To specify the timeslots and data rate used on each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the t1 timeslot controller configuration command. Use the no form of this command to remove the configured T1 channel.
t1 channel timeslot range [speed {56 | 64}]
no t1 channel timeslotSyntax Description
Default
No timeslots are specified for the T1 channel.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
You must specify the timeslots used by each T1 channel.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Examples
In the following example, timeslots 1 through 24 are assigned to T1 1 for full T1 bandwidth usage:
controller t3 9/0/0t1 1 timeslots 1-24In the following example, timeslots 1 to 5 and 20 to 23 are assigned to T1 6 for fractional T1 bandwidth usage:
controller t3 9/0/0t1 6 timeslots 1-5,20-23In the following example, T1 8 is configured for n x 56 (where n is 24) bandwidth usage:
controller t3 9/0/0t1 8 timeslots 1-24 speed 56t1 yellow
To enable detection and generation of yellow alarms for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with RSP7000 and Cisco 7500 series routers, use the t1 yellow controller configuration command. Use the no form of this command to disable the detection and generation of yellow alarms.
t1 channel yellow {detection | generation}
no channel yellow {detection | generation}Syntax Description
channel
Number between 1 and 28 that indicates the T1 channel.
detection
Detect yellow alarms.
generation
Generate yellow alarms.
Default
Yellow alarms are detected and generated on the T1 channel.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 CA.
If the T1 framing type is superframe (SF), you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with SF framing.
Note
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This is to ensure consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Example
In the following example, the yellow alarm detection is disabled on T1 channel 6 on the CT3IP:
controller t3 9/0/0t1 6 framing sfno t1 6 yellow detectionSupported MIBs
The CT3IP supports RFC 1406 (T1 MIB) and RFC 1407 (T3 MIB).
What to Do Next
For more information on the CT3IP, refer to the Channelized T3 Interface Processor (CT3IP) Installation and Configuration publication. For more information on the PA-CT3/4T1, refer to the Channelized T3 Dual-Wide Port Adapter Installation and Configuration publication.




