Channelized T3 Interface Processor

This chapter provides information about the Channelized T3 Interface Processor (CT3IP-40 and CT3IP-50), which for convenience are referred to in this chapter as CT3IP, with specific differences clearly noted.

The CT3IP, shown in Figure 4-1 and Figure 4-2, is a fixed-configuration interface processor that operates in the Cisco 7000 series and Cisco 7500 series routers.

The CT3IP provides four T1 connections via DB-15 connectors and one DS3 connection via two 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 (using a DB-15 connector) that can be configured individually.

Packet memory for the CT3IP-40 is 1 to 2 megabytes (MB) of static random-access memory (SRAM) provided on one dual-inline memory module (DIMM). (See Figure 4-2.) CT3IP microcode is loaded into and operates from dynamic random-access memory (DRAM). The DRAM configuration for CT3IP-40 is 16 to 32 MB, and is provided on two single-inline memory modules (SIMMs). (See Figure 4-2.) The CT3IP-40 supports RFC 1406 (T1 MIB) and RFC 1407 (T3 MIB).

Packet memory for the CT3IP-50 is 4 to 8 megabytes (MB) of static random-access memory (SRAM) provided on a proprietary SRAM daughter card. (See Figure 4-2.) CT3IP microcode is loaded into and operates from synchronous dynamic random-access memory (SDRAM). The SDRAM configuration for CT3IP-50 is 64 to 128  MB, and is provided on one dual-inline memory module (DIMM). (See Figure 4-2.) The CT3IP-50 supports RFC 1406 (T1 MIB) and RFC 1407 (T3 MIB).

CT3IP Hardware Prerequisites

For the CT3IP to operate properly in the Cisco 7000 series routers, the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) must be installed. The show version command displays the current hardware configuration of the router, including the system processor type. The show controller cbus command lists all interfaces and includes the currently loaded and running microcode version for each.

Router> show version
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Tue 09-Jul-96 09:58 by biff
Image text-base: 0x600108A0, data-base: 0x606C6000
ROM: System Bootstrap, Version 5.3.2(3.2) [biff 3.2], RELEASED SOFTWARE
ROM: GS Software (RSP-P-M), Version 11.1(10)CA, RELEASED SOFTWARE
(additional text omitted from example)

Router# show controller cbus
slot3: VIP2, hw 2.4, sw 21.40, ccb 5800FF40, cmdq 48000090, vps 8192
    software loaded from system 
    IOS (tm) VIP Software (SVIP-DW-M), Version 11.1(9)CA [biff 120]
    ROM Monitor version 17.0
    CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.7.0
    Mxt H/W version: 2, Mxt ucode ver: 1.24
    T3 2/0/0, applique is Channelized T3
      gfreeq 48000138, lfreeq 48000168 (1536 bytes), throttled 0
      rxlo 4, rxhi 258, rxcurr 4, maxrxcurr 130
(additional text omitted from example)

CT3IP Interface Types

The CT3IP has four T1 connections via DB-15 connectors and one DS3 connection via BNC connectors. (See Figure 4-4.) The CT3IP ships under the following product numbers: CT3IP-20(=) and CT3IP-40(=).

CT3IP Agency Compliance and Interface Specifications for T3 and T1

The T3 line interface unit (LIU) is designed to meet the following specifications: ANSI T1.102 - 1987 and BELLCORE TR-TSY-000499.

The T1 LIU is designed to meet the following specifications (see also Table 4-1): ANSI 62411 and BELLCORE TR499.

The T1 LIU is designed to meet the preceding specifications for input jitter tolerance, pulse shape/amplitude (DSX-1), and line termination and jitter. The LIU has a relatively flat transfer function so jitter introduced by the LIU is minimal.

The CT3IP T1 ports are designed to receive and transmit at the DSX-1 level while driving and receiving from a 100-ohm twisted-pair cable. The CT3IP T1 ports connect directly to any equipment with DSX-1 level input/output. The T1 front end is designed to meet the following specifications:

• Line rate: 1.544 Mbps (± 32ppm)

• Line code: AMI/B8ZS (bipolar with eight-zero substitution) on only the four external ports

• Impedance: 100 ohms

• Pulse shape: ANSI T1.102, pulse amplitude is between 2.4 and 3.6V peak.

• Input signal: DSX-3 (3db to -13.6 db)

• Output signal: DSX-1 able to drive 655 feet (199.6 meters) of 75-ohm twisted-pair cable and to meet DSX-1 pulse shape template at the line side.

Table 4-1 lists T1 channel data rates.

CT3IP Interface Cables

This section provides information on CT3IP interface cables and pinouts, and instructions for attaching interface cables to the CT3IP. For T1, two standard serial cables, null-modem and straight-through, are available from Cisco Systems and other vendors for use with the CT3IP. The CT3IP T1 interface cables are used to connect your router to external CSUs or a MultiChannel Interface Processor (MIP). The CT3IP T1 interface cables have two male 15-pin DB connectors at each end to connect the CT3IP's T1 interfaces. Figure 4-5 shows the CT3IP T1 interface cable, connectors, and pins. Table 4-2 lists the pinout for the straight-through cable. Table 4-3 lists the pinout for the null-modem cable.

Figure 4-6 shows typical 75-ohm coaxial cables with BNC connectors.

Attaching Network Interface Cables to the CT3IP

Attach the CT3IP network interface cables between the CT3IP interface ports and the CSU. This includes up to four T1 cables and two 75-ohm, DS1 BNC cables. (See Figure 4-7.)

Using LEDs to Check CT3IP Status

The CT3IP has several status LEDs on its faceplate. (See Figure 4-8.)

(For additional functions of the status and alarm LEDs, refer to the section "Using Status and Alarm LED Indications" on page 4-43.)

The individual 1, 2, 3, and test LEDs next to each T1 port indicate the following: each green LED will go on when its respective port is enabled. When a port is not enabled, its LED is off.

The remaining five LEDs, between the TEST and T3 ports, indicate the following:

• OOF--This yellow out-of-frame LED goes on when there is an out-of-frame condition.

• FERF --This yellow far-end-receive-failure LED goes on when the receive DS3 stream indicates the presence of a far-end-receive failure.

• AIS--This yellow alarm-indication-signal LED goes on when the receive DS3 stream indicates the presence of AIS.

• LOS--This yellow loss-of-signal LED pulses or stays on when 175 successive zeros are detected on the DS3 input stream. Indicates a loss of signal, a loss of frame, or unavailability due to excessive errors.

• T3EN-- This green LED is on when the T3 is enabled via software and means that the internal relay is on, thereby connecting the T3 to the BNC connector.

After you connect cables to the CT3IP, observe the LED states and the console displays the router initializes. When the system has reinitialized all interfaces, the enabled LED on the CT3IP should go on. The console screen will also display a message as the system discovers each interface during its reinitialization. After system initialization, the enabled LED goes on to indicate that the CT3IP is enabled for operation.

The following conditions must be met before the CT3IP is enabled:

• The CT3IP is correctly connected to the backplane and receiving power.

• The system bus recognizes the CT3IP.

• A valid version of CT3IP microcode is loaded and running.

If any one of these conditions is not met, or if the initialization fails, the enabled LED does not go on.

Verify that the CT3IP is connected correctly as follows:

Step 2 When the reinitialization is complete, verify that the enabled LED on the CT3IP is on and remains on. If the LED does stay on, proceed to Step 5. If the enabled LED does not stay on, proceed to the next step.

Step 3 If the enabled LED on the CT3IP fails to go on, suspect the that the CT3IP board connector is not fully seated in the backplane. Loosen the captive installation screws, then firmly push the top ejector down while pushing the bottom ejector up until both are parallel to the CT3IP faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the CT3IP should go on. If the enabled LED goes on, proceed to Step 5. If the enabled LED does not go on, proceed to the next step.

Step 4 If the enabled LED still fails to go on, remove the CT3IP and try installing it in another available interface processor slot.

• If the enabled LED goes on when the CT3IP is installed in the new slot, suspect a failed backplane port in the original interface processor slot.

• If the enabled LED still fails to go on, but other LEDs on the CT3IP go on to indicate activity, proceed to Step 5 to resume the installation checkout and suspect that the enabled LED on the CT3IP has failed.

• If no LEDs on the CT3IP go on, suspect that the CT3IP is faulty.

• If the enabled LED still does not go on, do not proceed with the installation. Contact a service representative to report the faulty equipment and obtain further instructions.

Step 5 Use the show interfaces or show controllers cbus command to verify the status of the CT3IP's interfaces. (If the interfaces are not configured, you must configure them using the procedures in the section "Configuring the CT3IP.")

If an error message displays on the console terminal, refer to the appropriate reference publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.

Configuring the CT3IP

If you installed a new CT3IP or if you want to change the configuration of an existing controller, you must enter configuration mode. If you replaced the CT3IP that was previously configured, the system will recognize the new CT3IP and bring it up in the existing configuration.

After you verify that the new CT3IP is installed correctly, use the privileged-level configure command to configure the new CT3IP controller. Be prepared with the information you will need, such as the following:

Configuring the CT3IP first requires privileged-level access to the EXEC command interpreter. (Refer to the section "Using the EXEC Command Interpreter" in the chapter "Using Interface Processors.") Also, privileged-level access usually requires a password. (Contact your system administrator, if necessary, to obtain privileged-level access.)

For a complete summary of the configuration options available and more detailed instructions for configuring the CT3IP controller, refer to the appropriate software configuration and command reference publications in the section "If You Need More Information" in the chapter "Using Interface Processors."

Interface Port Numbering for CT3IP T1 and T3 Interfaces

The interface numbering scheme for the CT3IP's T1 interfaces is in the form of slot/port-adapter/port:t1 channel: where slot refers to the chassis slot in which the CT3IP is installed, port-adapter is always 0 (because the CT3IP has only one dual-width port adapter); port refers to the physical port on the CT3IP and is always 0; and t1 channel is a number between 1 and 28. (For more specific interface configuration information, refer to the section "Configuring the CT3IP," on page 4-16.)

Designate and turn on an external T1 port (one of the three DB-15 connectors labeled 1 through 3) using the t1 external channel command, where t1 channel is a number between 1 and 3.

Designate and turn on the T1 test port (the DB-15 connector labeled TEST) using the t1 test channel command, where t1 channel is a number between 1 and 28.

Port Numbering Examples and Sample Displays

This section provides examples of CT3IP interface port numbering and sample displays:

• For T1 channel 5 on a CT3IP in chassis slot 2: 2/0/0:5

• For the T3 port on a CT3IP in chassis slot 4: 4/0/0

The following sample display shows the events logged by the system as the CT3IP is removed from interface processor slot 3; the system then reinitializes the remaining interface processors and marks as down the CT3IP when it is installed in interface processor slot 4. When the CT3IP is reinserted, the system marks the interfaces as down again because the CT3IP interfaces were not shut down before the CT3IP was removed.

Router#
%OIR-6-REMCARD: Card removed from slot 3, interfaces disabled
%LINK-5-CHANGED: Interfaces T3 4/0/0, changed to administratively down

When a new CT3IP is inserted, or when a CT3IP whose interfaces are shut down is moved to a new slot, the system recognizes the CT3IP controller, but leaves its interfaces in a shutdown state until you configure them and change the state to up with the configure command. If you move a CT3IP to a new slot and its interfaces are not shut down, the system recognizes them as not shut down when the CT3IP is installed in the new slot.

The following example display shows the events logged by the system as a new CT3IP is inserted in interface processor slot 0:

Router#
%OIR-6-INSCARD: Card inserted in slot 0, interfaces administratively shut down
%LINK-5-CHANGED: Interfaces T3 0/0/0, changed to administratively down
Router#

Configuring the T3 and T1 Interfaces

This section describes basic configuration guidelines and provides configuration command examples for the T3 and then T1 interfaces. Before you perform any configuration steps, you must first enter the privileged level of the EXEC command interpreter. (Refer to the section "Using the EXEC Command Interpreter" in the chapter "Using Interface Processors.") Press the Return key after each step.

Configuring the T3 Interface

Use the following procedure to configure the T3 interface:

Step 1 At the privileged-mode prompt, enter configuration mode and specify that the console terminal will be the source of the configuration subcommands as follows:

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

Step 2 Specify the controller to configure by entering the subcommand controller, followed by t1 or t3, and slot/port (interface processor slot number/interface port number). The example that follows is for the CT3IP in interface processor slot 3 for T3 channel 0:

Router(config)# cont t3 3/0/0

Step 3 At the prompt, specify the framing type using the framing [c-bit | m23 | auto-detect] command: set C-BIT framing format, as follows:

To shut down the T3 controller, use the shutdown command at the controller prompt. This command sends a DS3 Idle signal toward the network. You can bring the T3 controller back up with the no shutdown controller command. (For details on using the shutdown command, refer to the section "Shutting Down an Interface" in the chapter "Using Interface Processors.")

Configuring MDL Messages

Maintenance Data Link (MDL) messages (which are defined in the ANSI T1.107a-1990 specification) can be configured on the CT3IP.

To configure MDL messages, use the following controller configuration commands:

Examples of MDL Message Configuration

Following are examples of MDL messages, configured in controller configuration mode:

Router# conf t
Router(config)# cont t3 3/0/0
Router(config-controll)# 

• Enter the equipment identification code, as follows:

Router(config-controll)# mdl string eic router A

• Enter the location identification code, as follows:

Router(config-controll)# mdl string lic test network

• Enter the frame identification code, as follows:

Router(config-controll)# mdl string fic building b

• Enter the unit identification code, as follows:

Router(config-controll)# mdl string unit abc

• Enter the facility identification code, to send in the MDL path message, as follows:

Router(config-controll)# mdl string pfi string

• Enter the port number to send in the MDL idle signal message, as follows:

Router(config-controll)# mdl string port string

• Enter the generator number to send in the MDL test signal message, as follows:

Router(config-controll)# mdl string generator string

• Enable the MDL path message transmission, as follows:

Router(config-controll)# mdl transmit path

• Enable the MDL idle signal message transmission, as follows:

Router(config-controll)# mdl transmit idle-signal

• Enable the MDL test signal message transmission, as follows:

Router(config-controll)# mdl transmit test-signal

Configuring the Logical T1 Interfaces

Use the following procedure to configure the logical T1 interfaces using controller configuration commands. Examples follow:

Step 1 Specify the channel and timeslots to be mapped using the t1 t1 channel timeslots range [speed {56 | 64}] command.

where t1 channel is a number in the range 1-28, range supports contiguous timeslots as well as arbitrary timeslots, and a speed of 56 kbps is only valid for T1 21-28 (the default is 64 kbps).

Examples follow:

Configure T1 0 for full T1 bandwidth, as follows:

Router(config-controll)# t1 0 timeslots 1-24 speed 64

Configure the T1 20 to use timeslots 1 through 5 and timeslots 20 through 23 as follows:

Router(config-controll)# t1 20 timeslots 1-5,20-23

Configure the T1 21 for 24 x 56 kbps, as follows:

Router(config-controll)# t1 21 timeslot 1-24 speed 56

Step 2 Specify the T1 framing format using the t1 t1 channel framing [esf | sf] command. The default is the extended super frame (ESF) framing format, and t1 channel is a number in the range 1-28. Examples follow:

Set super frame (SF) framing format for T1 6 as follows:

Router(config-controll)# t1 6 framing sf

You can use the [no] t1 t1 channel yellow [detection | generation] command (where t1 channel is a number in the range 1-28) to turn the detection/generation of a yellow alarm on/off. Before selecting SF framing, consider using the no form of this command to turn off yellow alarm detection because the yellow alarm can be incorrectly detected with SF framing.

Set ESF framing format for T1 18, as follows:

Router(config-controll)# t1 18 framing esf

Step 3 Specify the remote T1 line code using the t1 t1 channel linecode [ami | b8zs] command. The default is b8zs, and the t1 channel is a number in the range 1-28.

An example follows:

Router(config-controller)# t1 0 linecode ami
Router(config-controller)# int s2/0/0:0
Router(config-if)# invert data

Step 4 Specify the T1 clock source using the t1 t1 channel clock source [internal | line] command, where the t1 channel is a number in the range 1-28, and the default is network (line) clocking.

Router(config-controll)# no t1 20 timeslots 1-24

To shut down a T1 controller, use the shutdown command at the controller prompt. This command sends a DS3 Idle signal toward the network. You can bring the T3 controller back up with the no shutdown controller command. (For details on using the shutdown command, refer to the section "Shutting Down an Interface" in the chapter "Using Interface Processors.")

Configuring the External T1 Ports on a CT3IP

The following controller configuration commands are valid only to the first three T1 channels (T1 0 through 2) when they are broken out to the external T1 port. (Use the show controller t3 command to first check the status of the external ports; refer to the example of this command on page 4-29 of the section "Using show Commands to Check Interface Status.")

Configure a T1 interface as an external port using the t1 external t1 channel [linecode {b8zs | ami}] [cablelength feet] command, where external t1 channel is a number in the range 1-3, and the cable length range is 0-655 feet. The default values are as follows: line code is B8ZS; cable length is 133 feet.

An example follows. Configure T1 1 to be an external port, as follows:

Router(config-controll)# t1 external 1 linecode ami cablelength 300

To remove a T1 interface from an external port, use the no t1 external t1 channel command, where external t1 channel is a number in the range 1-3.

For example, remove T1 channel 1 from the external port, as follows:

Router(config-controll)# no t1 external 1

Configuring the T1 Test Port on a CT3IP

The following controller configuration commands are valid only to the T1 test port. (Use the show controller t3 command to first check the status of the test port; refer to the example of this command on page 4-29 of the section "Using show Commands to Check Interface Status.")

Configure the T1 test port using the t1 test t1 test channel [linecode {b8zs | ami}] [cablelength feet] command, where t1 test channel is a number in the range 1-28, and the cable length range is 0-655 feet. The default values are as follows: line code is B8ZS; cable length is 133 feet.

An example follows, bring T1 20 to the test port, as follows:

Router(config-controll)# t1 test 20 linecode ami cablelength 300

To remove a T1 port from the test port, use the no t1 test t1 test channel command, where t1 test channel is a number in the range 1-28.

For example, remove T1 channel 20 from the test port, as follows:

Router(config-controll)# no t1 test 20

Additional Steps to Complete the CT3IP Configuration

The following additional steps are required to complete the CT3IP configuration:

Step 1 Assign an IP address and subnet mask to the interface with the ip address configuration subcommand as in the following example:

Router(config-if)# ip address 1.1.15.1 255.255.255.0
Router(config-if)#

Step 2 Add any additional interface subcommands required to enable routing protocols and adjust the interface characteristics.

Step 3 After including all of the interface subcommands to complete the configuration, press Ctrl-Z (hold down the Control key while you press Z) to exit configuration mode.

Step 4 Write the new configuration to memory as follows:

Router# copy running-config startup-config
[OK]
Router#

The system displays an OK message when the configuration is stored.

Step 5 Exit the privileged level and return to the user level by entering disable at the prompt as follows:

Router# disable
Router>

Proceed to the following section to use show commands to check the interface status, then to the section "Using Show Commands to Check the Configuration," on page 4-30.

Using show Commands to Check Interface Status

You can use show commands to display the status of the new interface or all interfaces. This section provides descriptions and examples of various show commands you can use to check interface status.

Router# show controller t3 0/0/0

Router# show controller t3 0/0/0:5

Router# show controller t3 0/0/0 brief

• The show controller t3 command (entered with no additional arguments) displays the status of the four T1 ports (external 1, external 2, external 3, and the test port, respectively), as follows:

Router# show cont t3
(additional displayed text omitted from this example)
  Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OK 

Using Show Commands to Check the Configuration

The following procedure summarizes how to use the show commands to verify that a new CT3IP interface is configured correctly:

Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new CT3IP network interface.

Step 2 Display all of the current CxBus interface processors and their interfaces with the show controllers cbus command. Verify that the new CT3IP appears in the correct slot.

Step 3 Display the T1 alarm condition with the show controllers T3 command.

Step 4 Specify the new interface with the show interfaces command and verify that the first line of the display specifies the serial interface with the correct slot, port adapter, and port. Also, verify that the interface and line protocol are in the correct state: up or down.

Step 5 Display the protocols configured for the entire system and specific interfaces with the command show protocols. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.

Step 6 Display the entire system configuration file with the show running-config and show startup-config commands. Verify that the configuration is accurate for the system and each interface.

If the interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a customer service representative for assistance.

Following are descriptions and examples of the show commands you can use to check the configuration. Descriptions are limited to fields that are relevant for verifying the CT3IP configuration.

• The show version command displays the configuration of the system hardware (the channel of each interface processor type installed), the software version, the names and sources of configuration files, and the boot images.

Following is an example from a Cisco 7505 router:

Router# show version
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Sat 10-May-97 06:02 by mpo
Image text-base: 0x600108A0, data-base: 0x606C6000
ROM: System Bootstrap, Version 5.3.2(3.2) [mpo 3.2], RELEASED SOFTWARE
ROM: GS Software (RSP-P-M), Version 11.1(9)CA, RELEASED SOFTWARE
Router uptime is 19 hours, 15 minutes
System restarted by reload
System image file is "rsp-pv-mz", booted via tftp from 1.1.1.254
cisco RSP1 (R4600) processor with 16384K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0 
Last reset from power-on
G.703/E1 software, Version 1.0.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
Chassis Interface.
1 VIP2 controller.
1 Channelized T3 port.
125K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0

• The show controllers cbus command displays the internal status of each interface processor, including the interface processor slot location, the card hardware version, and the currently running microcode version. It also lists each interface (port) on each interface processor including the logical interface number, interface type, physical (slot/port) address, and hardware (station address) of each interface. The following example shows the CT3IP installed in interface processor slot 0:

Router# show cont cbus
slot0: VIP2, hw 2.4, sw 21.40, ccb 5800FF40, cmdq 48000090, vps 8192
    software loaded from system 
    IOS (tm) VIP Software (SVIP-DW-M), Version 11.1(9)CA [biff 120]
    ROM Monitor version 17.0
    CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 0.7.0
    Mxt H/W version : 2, Mxt ucode ver : 1.24
    T3 2/0/0, applique is Channelized T3
      gfreeq 48000138, lfreeq 48000168 (1536 bytes), throttled 0
      rxlo 4, rxhi 258, rxcurr 4, maxrxcurr 130
Router#

• The show controller type slot/port-adapter/port command displays the status of the default T1 and T3 (which is specified in RFC 1406). The command show controller t1 slot/port-adapter/port command displays the verbose information for a particular T1 including the T3 alarms and all 28 T1 alarms. (The port adapter and port arguments must always be 0.)

Router# show cont t3 0/0/0
T3 0/0/0 is up.
  Applique type is Channelized T3
  No alarms detected.
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line.
  Data in current interval (120 seconds elapsed):
     1 Line Code Violations, 2 P-bit Coding Violation
     3 C-bit Coding Violation
     4 P-bit Err Secs, 5 P-bit Severely Err Secs
     6 Severely Err Framing Secs, 7 Unavailable Secs
     8 Line Errored Secs, 9 C-bit Errored Secs, 10 C-bit Severely Errored Secs
  Data in Interval 1:
     10 Line Code Violations, 12 P-bit Coding Violation
     0 C-bit Coding Violation
     14 P-bit Err Secs, 15 P-bit Severely Err Secs
     16 Severely Err Framing Secs, 17 Unavailable Secs
     18 Line Errored Secs, 19 C-bit Errored Secs, 20 C-bit Severely Errored Secs
  Data in Interval 2:
     10 Line Code Violations, 12 P-bit Coding Violation
     0 C-bit Coding Violation
     14 P-bit Err Secs, 15 P-bit Severely Err Secs
     16 Severely Err Framing Secs, 17 Unavailable Secs
     18 Line Errored Secs, 19 C-bit Errored Secs, 20 C-bit Severely Errored Secs
  Data in Interval 3:
     10 Line Code Violations, 12 P-bit Coding Violation
     0 C-bit Coding Violation
     14 P-bit Err Secs, 15 P-bit Severely Err Secs
     16 Severely Err Framing Secs, 17 Unavailable Secs
     18 Line Errored Secs, 19 C-bit Errored Secs, 20 C-bit Severely Errored Secs
  T1 0, speed: 1536 kbs
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is AMI, Clock Source is Line.
  Data in current interval (180 seconds elapsed):
     2 Line Code Violations, 1 Path Code Violations
     7 Slip Secs, 5 Fr Loss Secs, 8 Line Err Secs, 10 Degraded Mins
     3 Errored Secs, 9 Bursty Err Secs, 4 Severely Err Secs, 6 Unavail Secs
  Data in Interval 1:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs
  Data in Interval 2:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs
  Data in Interval 3:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs
  T1 1, speed: 1536 kbs
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is AMI, Clock Source is Line.
  Data in current interval (250 seconds elapsed):
     2 Line Code Violations, 1 Path Code Violations
     7 Slip Secs, 5 Fr Loss Secs, 8 Line Err Secs, 10 Degraded Mins
     3 Errored Secs, 9 Bursty Err Secs, 4 Severely Err Secs, 6 Unavail Secs
  Data in Interval 1:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs
  Data in Interval 2:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs
  Data in Interval 3:
     12 Line Code Violations, 11 Path Code Violations
     17 Slip Secs, 15 Fr Loss Secs, 18 Line Err Secs, 20 Degraded Mins
     13 Errored Secs, 19 Bursty Err Secs, 14 Severely Err Secs, 16 Unavail Secs 
Router#

• The show controller type slot/port-adapter/port brief command displays less verbose information about a T3 and all configured T1s.

An example follows:

Router# show controller t3 0/0/0 brief
T3 0/0/0 is up.
  CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 0.7.0
  Mxt H/W version : 2, Mxt ucode ver : 1.24
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received : No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.
  T1 0 is up, speed: 1536 kbs, non-inverted data
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
  T1 1 is up, speed: 1536 kbs, non-inverted data
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
  T1 2 is up, speed: 1536 kbs, non-inverted data
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is B8ZS, Clock Source is Internal.

• Another permutation of the preceding show controller type slot/port-adapter/port command shows the T3 and an individual T1 that you specify by adding :t1 channel, where t1 channel is a number in the range 1-28.

An example follows:

Router# sh cont t3 0/0/0:1 brief
T3 0/0/0 is up.
  CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 0.7.0
  Mxt H/W version : 2, Mxt ucode ver : 1.24
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received : No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.
  T1 1 is up, speed: 1536 kbs, non-inverted data
  timeslots: 1-24
  No alarms detected.
  Framing is ESF, LineCode is B8ZS, Clock Source is Internal.

• The show startup-config command displays the contents of the system configuration file stored in NVRAM. This file should reflect all new configuration changes you made and wrote to memory with the copy running-config startup-config command. (The show running-config command displays the contents of a configuration file before it is written to NVRAM.)

Router# show startup-config
controller T3 0/0/0
 cablelength 224
 t1 0 timeslots 1-24
 t1 1 timeslots 1-24
 t1 2 timeslots 1-24
!
interface Serial0/0/0:0
 ip address 30.30.30.2 255.255.255.0
 no ip route-cache optimum
 no keepalive
 no fair-queue
!
interface Serial0/0/0:1
 ip address 1.1.1.2 255.255.255.0
 no ip route-cache optimum
 no keepalive
 no fair-queue
!
interface Serial0/0/0:2
 ip address 2.2.2.2 255.255.255.0
 no ip route-cache optimum
 no keepalive
 no fair-queue
!
(additional display text omitted from this example)

• The show protocols command displays the global (system-wide) and interface-specific status of any configured Level 3 protocol.

Router# show protocols
Serial0/0/0:0 is up, line protocol is up
  Internet address is 30.30.30.2/24
Serial0/0/0:1 is up, line protocol is up
  Internet address is 1.1.1.2/24

• The show interfaces type slot/port-adapter/port:t1 channel command displays information about a T1 interface you specify. Following is an example:

Router# sh int serial 0/0/0:0
Serial0/0/0:0 is up, line protocol is up 
  Hardware is cxBus T3
  Internet address is 30.30.30.2/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 10:05:52, output 10:05:52, output hang never
  Last clearing of "show interface" counters 17:53:35
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 26 drops
  5 minute input rate 1426000 bits/sec, 1700 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     102606572 packets input, 2285893928 bytes, 1 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     298 input errors, 0 CRC, 0 frame, 298 overrun, 0 ignored, 0 abort
     5 packets output, 530 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions no alarm present
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 7   non-inverted data

Testing and Troubleshooting the CT3IP

This section describes suggested guidelines for troubleshooting the CT3IP using the loopback command, status and alarm LED indications, a bit error test (BERT), facilities data link (FDL) performance reports, and for displaying remote performance reports.

Using loopback Commands

This section provides suggested guidelines for using loopback commands.

If you have difficulty with the CT3IP configuration or installation, you can troubleshoot the CT3IP using the loopback interface configuration command. Specify loopback for a T1 channel where the T1 channel is 1-28. Specify the loopback format using the following command format:

loopback [local | network {line | payload} | remote {line {fdl {ansi | bellcore} | inband} 
payload [fdl] [ansi]}]

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface serial 2/0/0:1
Router(config)# loopback local	

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface serial 2/0/0:1
Router(config)# loopback network line

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface serial 2/0/0:1
Router(config)# loopback network payload

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int serial 2/0/0:1
Router(config-if)# loop remote line fdl ansi

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int serial 2/0/0:1
Router(config-if)# loop remote line fdl bellcore

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int serial 2/0/0:1
Router(config-if)# loop remote line inband

Router# config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int serial 2/0/0:1
Router(config-if)# loop remote payload fdl ansi

Router# show controllers t3 2/0/0:2
 T3 2/0/0 is up.
   CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9
   Mx H/W version: 2, Mx ucode ver: 1.34
 
   T1 2 is down, speed: 1536 kbs, non-inverted data
   timeslots: 1-24
   FDL per AT&T 54016 spec.
   Transmitter is sending LOF Indication.
   Receiver is getting AIS.

Router(config)# controllers t3 2/0/0
Router(config-controll)# no t1 2 yellow generation
Router(config-controll)# ^D

Router# show cont t3 2/0/0:2
 T3 0/0/0 is up.
   CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9
   Mx H/W version: 2, Mx ucode ver: 1.34 
   T1 2 is down, speed: 1536 kbs, non-inverted data
   timeslots: 1-24
   FDL per AT&T 54016 spec.
   Receiver is getting AIS.
   Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
   Yellow Alarm Generation is disabled

Using Status and Alarm LED Indications

This section describes various system states and functions that are indicated by the front-panel alarm and status LEDs on the CT3IP during the CPU boot process and microcode download.

Checking Bit Errors Using a BERT

To check bit errors using a bit error test (BERT), use the following command:

t1 t1 channel bert pattern {2^15 | 2^20 | 2^23 | 0s | 1s} interval minutes

where t1 channel is a number in the range 1-28, 2^15 is an exponential number that represents a pseudo-random repeating pattern that is 32767 bits long, 2^20 is a pseudo-random repeating pattern that is 1048575 bits long, 2^23 is a pseudo-random repeating pattern that is 8388607 bits long, 0s is a pattern of all zeroes (00000000...), 1s is a pattern of all 1s (111111...), and minutes is a number in the range 1-14400, which designates the time the BERT will run. To stop the BERT, use the optional no form of the command.

Router# t1 1 bert pattern 2^20 interval 60

Router# sh cont t3 number 
Router# sh cont t3 number brief

Enabling Performance Reports

To enable and disable one-second transmissions of performance reports via the FDL (per ANSI T1.403), use the [no] t1 t1 channel fdl ansi command, where the T1 channel is 1-28.

Displaying Remote Performance Reports

To display remote (far-end) performance data, use the show controller t3 3/0/0 remote performance command, as follows:

Router# sh cont t3 3/0/0 remote performance 
T3 3/0/0 is up.
  CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 20.2.0
  Mx H/W version : 2, Mx ucode ver : 1.25
  T1 1 - Remote Performance Data
  Data in current interval (356 seconds elapsed):
     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 Secs
     0 Unavail Secs
  Data in Interval 1:
     1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
     0 Unavail Secs
  Data in Interval 2:
     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 Secs
     0 Unavail Secs
  Total Data (last 2 15 minute intervals):
     1 Path Code Violations
     1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
     0 Unavail Secs
  T1 2 - Remote Performance Data
  Data in current interval (425 seconds elapsed):
     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 Secs
     0 Unavail Secs
  Data in Interval 1:
     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 Secs
     0 Unavail Secs
  Data in Interval 2:
     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 Secs
     0 Unavail Secs
  Total Data (last 2 15 minute intervals):
     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 Secs
     0 Unavail Secs