Configuring the PA-MC-2T3+

To continue your PA-MC-2T3+ installation, you must configure the PA-MC-2T3+ interface. The instructions that follow apply to all supported platforms. Minor differences between the platforms are noted. This chapter contains the following sections:

Using the EXEC Command Interpreter

You modify the configuration of your router through the software command interpreter called the EXEC (also called enable mode). You must enter the privileged level of the EXEC command interpreter with the enable command before you can use the configure command to configure a new interface or change the existing configuration of an interface. The system prompts you for a password if one has been set.

The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>). At the console terminal, use the following procedure to enter the privileged level:

Step 1 At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a privileged-level password as follows:

Router> enable

Password:

Step 2 Enter the password (the password is case-sensitive). For security purposes, the password is not displayed.

Step 3 When you enter the correct password, the system displays the privileged-level system prompt (#):

Router#

Proceed to the "Configuring the T3 Link" section to configure the new interfaces.

Configuring the T3 Link

If you installed a new PA-MC-2T3+ or if you want to change the configuration of an existing PA-MC-2T3+ link, you must enter the privileged level of the EXEC command interpreter and then use the configure command. If you replace a PA-MC-2T3+ that was previously configured, the system recognizes the new PA-MC-2T3+ link and brings it up in its existing configuration.

After you verify that the new PA-MC-2T3+ is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interface. Be prepared with the information you need, such as the following:

Protocols you plan to route on each new interface
IP addresses, if you plan to configure the interfaces for IP routing

The configure command requires privileged-level access to the EXEC command interpreter, which usually requires a password. Contact your system administrator if necessary to obtain EXEC-level access.

Identifying Interface Numbers and Addresses

This section describes how to identify interface processor (or chassis) slot numbers, port adapter slot numbers, T1 line, and T1 logical channel group numbers.

Note The Cisco IOS software recognizes a configured logical channel group as a serial interface; therefore, you can use all configuration commands that are available for serial interfaces with configured logical channel groups. You can configure a logical channel group to carry data traffic using the following encapsulation methods: PPP, HDLC, SMDS, and Frame Relay. Set the encapsulation method you want using the serial interface configuration commands. For configured logical channel groups, you can use all command switches that are applicable to a serial interface.

Depending on the system in which the PA-MC-2T3+ is installed, these numbers are combined to form the port address that consists of a 4- or 5-part number in one of the following two formats:

5-part address for VIP2 installations:
interface processor slot/port-adapter/interface port/t1-line-number:channel-group-number
- The first number identifies the interface processor slot in which the VIP2 is installed; the number depends on the Cisco 7000 series or Cisco 7500 series router in which you plan to install the VIP2.
- The second number identifies the port adapter slot (or bay) on the VIP2, which is either 0 or 1.
- The third number identifies the interface port on the PA-MC-2T3+, which is either 0 or 1.
- The fourth number identifies the T1 line number on the PA-MC-2T3+, which is a number from 1 through 28.
- The fifth number identifies the logical channel group on the T1 line, which is a number from 0 through 23.
4-part address for all other installations:
chassis slot/interface port/t1-line-number:channel-group-number
- The first number identifies the chassis slot (or bay), and is numbered according to the number of chassis slots that are available in the system in which the PA-MC-2T3+ is installed.
- The second number identifies the interface port on the PA-MC-2T3+, which is either 0 or 1.
- The third number identifies the T1 line number on the PA-MC-2T3+ and is a number from 1 through 28.
- The fourth number identifies the logical channel group on the T1 line, which is a number from 0 through 23.

: Interface ports on a specific port adapter maintain the same port address regardless of whether other port adapters are installed or removed; however, when you move a port adapter to a different location in a system, the first number in the port address changes to reflect the new location.
: You can also identify interface ports by physically checking the port-adapter/interface port location on the back of the router or by using show commands to display information about a specific interface or all interfaces in the router.

Note Throughout this chapter, examples using the command syntax for all systems in which the PA-MC-2T3+ can be used are shown. Exceptions are clearly noted.

Configuring the T3 Controller

This section provides procedures and examples for configuring the T3 controller on the PA-MC-2T3+, and includes information on the following topics:

Selecting a T3 Controller

You must enter the following controller command, before any other configuration commands, to select the T3 controller you want to configure:

controller T3 slot/port-adapter/port.

Examples of selecting the T3 controller follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)#

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)#

Setting the Framing Type for the T3 Controller

At the prompt, specify the framing type using the controller command:

framing [c-bit | m23 | auto-detect]

You can set c-bit framing format as follows:

Router(config-controller)# framing c-bit

You can set m23 framing format as follows:

Router(config-controller)# framing m23

You can request the PA-MC-2T3+ to detect the framing type it is to receive from the far end and transmit that same framing type as follows:

Router(config-controller)# framing auto-detect

Specifying the Cable Length

At the prompt, specify the cable length using the controller command:

cablelength feet

where:

feet is a numeral from 0 to 450.
The default value is 49 feet.

An example follows:

Router(config-controller)# cablelength 40

Note For the cablelength feet command, user-specified T3 cable lengths are structured into ranges as follows: 0-49 and 50-450. If you enter a cable length value that falls into one of these ranges, the range within which that value applies is used.

In the preceding example, a cable length of 40 is specified, which means that the 0-49 range is used. If you change the cable length to 45, then the 0-49 range still applies. Further, if you specify a cable length of 100 and then change it to 200, the 50-450 range applies in each case; therefore, these changes have no effect. Only moving from one range (0-49) to the other range (50-450) has an effect. The actual cable-length number you enter is stored in the configuration file.

Setting the Clock Source for the T3 Controller

At the prompt, set the internal or line clock source for the selected T3 controller with the controller command:

clock source {internal | line}

The default is clock source internal.

Examples follow:

Instruct the PA-MC-2T3+ to use a line clock source.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# clock source line

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# clock source line

Instruct the PA-MC-2T3+ to use an internal clock source.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# clock source internal

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# clock source internal

Configuring MDL Messages

You can configure Maintenance Data Link (MDL) messages (which are defined in the ANSI T1.107a-1990 specification) on the PA-MC-2T3+.

Note MDL messages are only supported when the T3 framing is set for c-bit parity. (See the "Setting the Framing Type for the T3 Controller" section.)

To configure MDL messages, use the controller commands:

mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}

no mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}

where:

eic is the equipment identification code (up to 10 characters).
lic is the location identification code (up to 11 characters).
fic is the frame identification code (up to 10 characters).
unit is the unit identification code (up to 6 characters).
pfi is the facility identification code to send in the MDL path message (up to 38 characters).
port is the equipment port, which initiates the idle signal, to send in the MDL idle signal message (up to 38 characters).
generator is the generator number to send in the MDL test signal message (up to 38 characters).

Use the no form of this command to remove MDL messages. The default is that no MDL message is configured.

Examples of MDL Message Configuration

Examples of configuring MDL messages follow:

Enter controller configuration mode first.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure t
Enter configuration commands, one per line. End with CNTL/Z. 
Router(config)# controller T3 1/0/0
Router(config-controller)#

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure t
Enter configuration commands, one per line. End with CNTL/Z. 
Router(config)# controller T3 1/0
Router(config-controller)#

Enable the MDL path message transmission as follows:

Router(config-controller)# mdl transmit path

Enable the MDL idle signal message transmission as follows:

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

Enable the MDL test signal message transmission as follows:

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

Enter the equipment identification code as follows:

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

Enter the location identification code as follows:

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

Enter the frame identification code as follows:

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

Enter the unit identification code as follows:

Router(config-controller)# mdl string unit abc

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

Router(config-controller)# mdl string pfi string

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

Router(config-controller)# mdl string port string

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

Router(config-controller)# mdl string generator string

Configuring Idle Patterns

You can set a specific pattern to be transmitted for unused timeslots on all T1 lines. (Unused timeslots are timeslots that have not been assigned to any logical channel group on channelized T1 lines.)

To set an idle pattern, use the controller command:

idle pattern patterns

where:

patterns is a hexadecimal number in the range of 0x0 to 0xFF (hexadecimal) or 0 to 255 (decimal); you can enter this value in either hexadecimal or decimal.
The default idle pattern is 0x7F (or 127).

Examples follow:

Set a hexadecimal idle pattern.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# idle pattern 0x10

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# idle pattern 0x10

Set a decimal idle pattern.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# idle pattern 23

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# idle pattern 23

Configuring the Loopback Mode for the T3 Controller

You can configure the T3 controller for loopback modes using the controller command:

loopback [local | network | remote]

The default is no loopback.

To return the T3 controller to its default condition, use the no form of the command.

Examples follow:

Configure the T3 controller for local loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# loopback local

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# loopback local

: Local loopback simultaneously loops all channels toward the router and transmits a T3 AIS to the network. You can use local loopback to diagnose problems with the port adapter when isolated from the network cables.

Configure the T3 controller for network loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# loopback network

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# loopback network

: Network loopback loops the T3 line back towards the network and can be used to diagnose problems with cables from the central switching office to the port adapter.

Configure the T3 controller for remote loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# loopback remote

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# loopback remote

: Remote loopback sends a command to loop the T3 line at the far end (central office). It can be used to diagnose problems with cables from the port adapter to the switching office.

Configure the T3 controller for remote T3 loopback.

Equipment customer loopback enables the port adapter to respond to remote T3 loopback commands from the remote T3 equipment while equipment network loopback causes the PA to ignore remote T3 loopback commands.

equipment [customer | network] loopback

Note

Shutting Down the T3 Controller

You can shut down the T3 controller on the PA-MC-2T3+ with the controller command:

shutdown

This command sends a DS3 Idle signal toward the network. You can bring the T3 controller back up with the no shutdown controller command.

Examples follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# shutdown

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# shutdown

Configuring T1 Lines

This section provides procedures and examples for configuring T1 lines on the T3 link of the PA-MC-2T3+, and includes information on the following topics:

Note For consistency throughout the following configuration examples and whenever possible, the port addresses 1/0/0 and 1/0/0/1:1 are used.

Your PA-MC-2T3+ port addressing might be different depending on the interface processor slot in which your VIP2 is installed and the VIP2 port adapter slot in which your PA-MC-2T3+ is installed.

Creating a Logical Channel Group on a T1 Line

You can create a logical channel group on a T1 line using one of the following two controller commands as appropriate for your channelized configuration:

t1 t1-line-number channel-group channel-group-number timeslots list-of-timeslots
[speed {56 | 64}]

where:

t1-line-number is 1-28 (all 28 T1 lines can have more than one logical channel group).
channel-group defines a logical channel group to be a channelized T1 line (T1 lines 1-28 can be channelized).
channel-group-number is 0-23.
timeslots list-of-timeslots can be 1-24 or a combination of subranges within 1-24 (each subrange is a list of timeslots that makes up the T1 line).
speed{56 | 64} is an optional argument that specifies the speed of a time slot to be either 56 kbps or 64 kbps.

Configure logical channel group 20 on T1 line 1 and assign channelized timeslots 1 to 5 and 20 to 23.

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 channel-group 20 timeslots 1-5, 20-23

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 1 channel-group 20 timeslots 1-5, 20-23

Removing a Logical Channel Group from a T1 Line

You can remove a logical channel group from a T1 line (or a T1 line) with the controller command appropriate to your channelized configuration as follows:

no t1 t1-line-number channel-group channel-group-number

where:

t1-line-number is 1-28.
channel-group-number is 0-23.

Remove logical channel group 10 from channelized T1 line 1.

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# no t1 1 channel-group 10

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# no t1 1 channel-group 10

Setting the Framing Format on a T1 Line

You can specify the T1 framing format using the controller command:

t1 t1-line-number framing {esf | sf}

where:

The default framing format is extended super frame (ESF).
t1-line-number is 1-28.

Examples follow:

Set super frame (SF) framing format for T1 line 6.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 6 framing sf

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 6 framing sf

Other options for setting super frame (SF):

mc2t3-uut(config-controller)#t1 6 framing ?
    esf  Extended Superframe Framing format
    sf   Superframe Framing Format
 
  mc2t3-uut(config-controller)#t1 6 framing sf ?
    hdlc-idle  Specify the HDLC idle pattern on a T1
    <cr>
 
  mc2t3-uut(config-controller)#t1 6 framing sf hdlc-idle ?
    0x7E  Use 0x7E as HDLC idle pattern
    0xFF  Use 0xFF as HDLC idle pattern
 
  mc2t3-uut(config-controller)#t1 6 framing sf hdlc-idle 0x7e ?

Note You can use the [no] t1 t1-line-number yellow {detection | generation} command (where t1-line-number is 1-28) to turn the detection or generation of a yellow alarm on and off. When you select SF framing, you should consider using the no t1-line-number yellow detection command to turn off yellow alarm detection, because the yellow alarm can be incorrectly detected with SF framing.

Set ESF framing format for T1 line 16 as follows:

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 16 framing esf

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 16 framing esf

Setting the Clock Source on a T1 Line

You can set the internal or line (network) clock source for a T1 line with the controller command:

t1 t1-line-number clock source {internal | line}

where:

t1-line-number is 1-28.
The default clock source is internal.

Note You can set the clock source to use internal clocking for testing purposes. One end of a T1 circuit must provide the clock source.

Examples follow:

Instruct T1 line 1 to use an internal clock source.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 clock source internal

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 1 clock source internal

Instruct T1 line 16 to use a line clock source.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 16 clock source line

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 16 clock source line

Note After a T1 line is configured, it appears to the Cisco IOS software as a serial interface; therefore, all the configuration commands for a serial interface are available. However, not all commands are applicable to the T1 line. All the encapsulation formats, such as PPP, HDLC, SMDS, and Frame Relay are applicable to the configured T1 line. Encapsulation can be set using the serial interface configuration commands. All the switching types that are applicable to a serial interface are also applicable to the configured T1 line.

Configuring a BER Test on a T1 Line

Bit error rate test (BERT) circuitry is built into the PA-MC-2T3+. With BER tests, you can test cables and signal problems in the field. You can configure individual T1 lines to run an independent BER test; only one BER test circuit exists for all 28 T1 lines.

There are two categories of test patterns that can be generated by the onboard BER test circuitry: pseudorandom and repetitive. The former test patterns are exponential numbers and conform to the CCITT/ITU O.151 and O.153 specifications; the latter test patterns are zeros or ones, or alternating zeros and ones.

A description of each type of test pattern follows:

Pseudorandom test patterns:
- 2^11 (per CCITT/ITU O.151)
- 2^15 (per CCITT/ITU O.151)
- 2^20 (per CCITT/ITU O.153)
- 2^20 QRSS (per CCITT/ITU O.151)
- 2^23 (per CCITT/ITU O.151)
Repetitive test patterns:
- All zeros (0s)
- All ones (1s)
- Alternating zeros (0s) and ones (1s)

Both the total number of error bits received and the total number of bits received are available for analysis. You can set the testing period from 1 minute to 14,400 minutes (240 hours), and you can also retrieve the error statistics anytime during the BER test.

Note BER testing for the T3 link is not supported.

When running a BER test, your system expects to receive the same pattern that it is transmitting. To help ensure this, two common options are available:

Use a loopback somewhere in the link or network.
Configure remote testing equipment to transmit the same BER test pattern at the same time.

Sending a BER Test Pattern on a T1 Line

You can send a BERT pattern on a T1 line with the controller command. The unframed option causes the BERT pattern to use the entire T1 bandwidth including the T1 framing as well as payload bits. If "unframed" is omitted then the T1 will be either SF or ESF framed as configured by the "T1 n framing" command and the BERT pattern will occupy only the T1 payload bits.

t1 t1-line-number bert pattern pattern interval time [unframed]

where:

t1-line-number is 1-28.
time is 1-14400 minutes.
pattern is:
- 0s, repetitive test pattern of all zeros (as 00000...)
- 1s, repetitive test pattern of all ones (as 11111...)
- 2^11, pseudorandom test pattern (2,048 bits long)
- 2^15, pseudorandom O.151 test pattern (32,768 bits long).
- 2^20-O153, pseudorandom O.153 test pattern (1,048,575 bits long)
- 2^20-QRSS, pseudorandom QRSS O.151 test pattern (1,048,575 bits long)
- 2^23, pseudorandom O.151 test pattern (8,388,607 bits long)
- alt-0-1, repetitive alternating test pattern of zeros (0s) and ones (1s), as 01010101

Examples follow:

Send a BERT pseudorandom pattern of 2^20 through T1 line 10 for 5 minutes.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 10 bert pattern 2^20 interval 5 unframed

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 10 bert pattern 2^20 interval 5 unframed

Send a repetitive pattern of all ones through T1 line 10 for 14400 minutes (240 hours).

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# t1 10 bert pattern 1s interval 14400 unframed

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# t1 10 bert pattern 1s interval 14400 unframed

Note You can terminate a BER test during the specified test period with the no t1 bert command.

Viewing the Results of a BER Test

You can view the results of a BER test using the controller command:

show controllers T3 slot/port-adapter/port/t1-line-number

where: t1-line-number is 1-28.

You can view the results of a BER test at the following times:

After you terminate the test using the no t1 bert command
After the test runs completely
Anytime during the test (in real time)

You can view information about a BER test using the controller command:

show controllers T3 slot/port-adapter/port/t1-line-number

where: t1-line-number is 1-28.

Examples follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# show cont T3 1/0/0/1
T3 1/0/0 is up.
C2T3 H/W Version : 3, C2T3 ROM Version : 0.79, C2T3 F/W Version : 0.29.0
T3 1/0/0 T1 1
No alarms detected.
Clock Source is internal.
BERT test result (running)
   Test Pattern : 2^11, Status : Sync, Sync Detected : 1
   Interval : 5 minute(s), Time Remain : 5 minute(s)
   Bit Errors(Since BERT Started): 6 bits, 
   Bits Received(Since BERT start): 8113 Kbits
   Bit Errors(Since last sync): 6 bits
   Bits Received(Since last sync): 8113 Kbits

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router:

Router# show cont T3 1/0/1
T3 1/0 is up.
C2T3 H/W Version : 3, C2T3 ROM Version : 0.79, C2T3 F/W Version : 0.29.0
T3 1/0 T1 1
No alarms detected.
Clock Source is internal.
BERT test result (running)
   Test Pattern : 2^11, Status : Sync, Sync Detected : 1
   Interval : 5 minute(s), Time Remain : 5 minute(s)
   Bit Errors(Since BERT Started): 6 bits, 
   Bits Received(Since BERT start): 8113 Kbits
   Bit Errors(Since last sync): 6 bits

Bits Received(Since last sync): 8113 Kbits

The following explains the output of the preceding command, line by line:

Output Display Line Explanation

BERT test result (running)

This line indicates the current state of the test. In this case, "running" indicates that the BER test is still in process. After a test is completed, "done" is displayed.

Test Pattern : 2^11, Status : Sync, Sync Detected : 1

This line indicates the test pattern you selected for the test (2^11), the current synchronization state (sync), and the number of times synchronization has been detected during this test (1).

Interval : 5 minute(s), Time Remain : 5 minute(s)

This line indicates the time the test takes to run and the time remaining for the test to run.

Interval : 5 minute(s), Time Remain : 2 minute(s) (unable to complete)

For a BER test that you terminate, this line indicates the time the test would have taken to run and the time remaining for the test to run had you not terminated it; "unable to complete" signifies that you interrupted the test.

Bit Errors(Since BERT Started): 6 bits,

Bits Received(Since BERT start): 8113 Kbits

Bit Errors(Since last sync): 6 bits

Bits Received(Since last sync): 8113 Kbits

These four lines show the bit errors that have been detected versus the total number of test bits that have been received since the test started and since the last synchronization was detected.

Output Display Line	Explanation
`BERT test result (running)`	This line indicates the current state of the test. In this case, "running" indicates that the BER test is still in process. After a test is completed, "done" is displayed.
`Test Pattern : 2^11, Status : Sync, Sync Detected : 1`	This line indicates the test pattern you selected for the test (2^11), the current synchronization state (sync), and the number of times synchronization has been detected during this test (1).
`Interval : 5 minute(s), Time Remain : 5 minute(s)`	This line indicates the time the test takes to run and the time remaining for the test to run.
`Interval : 5 minute(s), Time Remain : 2 minute(s) (unable to complete)`	For a BER test that you terminate, this line indicates the time the test would have taken to run and the time remaining for the test to run had you not terminated it; "unable to complete" signifies that you interrupted the test.
`Bit Errors(Since BERT Started): 6 bits,` `Bits Received(Since BERT start): 8113 Kbits` `Bit Errors(Since last sync): 6 bits` `Bits Received(Since last sync): 8113 Kbits`	These four lines show the bit errors that have been detected versus the total number of test bits that have been received since the test started and since the last synchronization was detected.

Note Unless unframed is selected, the BER test runs over the currently configured framing option for the specified T1 line (ESF or SF). Before running a BER test, you should configure the framing option that is appropriate to your application. (Refer to the "Setting the Framing Format on a T1 Line" section.)

Terminating a BER Test

You can terminate a BER test with the controller command:

no t1 t1-line-number bert

where: t1-line-number is 1-28.

Examples follow:

Terminate the BER test running on T1 line 10.

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router(config)# controller T3 1/0/0
Router(config-controller)# no t1 10 bert

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# controller T3 1/0
Router(config-controller)# no t1 10 bert

This completes the procedures for configuring and testing T1 lines.

To check your configurations using show commands, proceed to the "Checking the Configuration" section; otherwise, proceed to the following sections to perform a basic interface configuration and T3 controller configurations:

Basic Interface Configuration

This section provides the procedure for performing a basic interface configuration. Press Return after each step unless otherwise noted.

At any time you can exit the privileged level and return to the user level by entering disable at the prompt as follows:

Router# disable
Router>

Following is an example of a basic interface configuration procedure:

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

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

Step 2 At the prompt, specify the first channel group you want to configure by entering the subcommand interface, followed by the type (serial), and slot/port-adapter/interface port/t1-line-number:channel-group-number. (This step assumes you have already configured the logical channel group. For channelized T1 lines, channel-group-number can be 0-23.)

The example that follows is for logical channel group 1 on T1 line 1 of the T3 link on the first PA-MC-2T3+ on a VIP2 in interface processor slot 1:

Router(config)# interface serial1/0/0/1:1

The example that follows is for logical channel group 1 on T1 line 1 of the T3 link on a PA-MC-2T3+ in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router(config)# interface serial1/0/1:1

Step 3 If IP routing is enabled on the system, you can 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.1.10 255.255.255.252

Step 4 Add any additional configuration subcommands required to enable routing protocols and set the T1 line characteristics. (For additional configuration options, see the "Configuring the T3 Controller" section and the "Configuring the T3 Controller" section.)

Step 5 Change the shutdown state to up and enable the interface as follows:

Router(config-if)# no shutdown

Step 6 Repeat Step 2 through Step 5 to configure additional T1 lines as required.

Step 7 When you have entered all of the configuration subcommands to complete the configuration, press Ctrl-Z to exit configuration mode.

Step 8 Write the new configuration to nonvolatile memory as follows:

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

Checking the Configuration

After installing the PA-MC-2T3+ and configuring the T1 lines and T3 controller, use show commands to display the status of the new T1 lines, T3 controller, and the system, and use the ping command to verify network connectivity. This section includes information on the following topics:

Using show Commands to Display System Information

The following show commands display information you can use to verify that the system, new interfaces, and new port adapters are operating correctly:

Display the system hardware configuration with the show version command. Ensure that the list includes the new interfaces.
Display all the current interface processors and their interfaces with the show controllers command. Verify that the new T3-equipped VIP2 appears in the correct slot.
Specify one of the new interfaces with the show interfaces serial command, and verify that the display specifies the interface with the correct slot number. Also verify that the interface and line protocol are in the correct state: up or down.
Display the protocols configured for the entire system and specific interfaces with the show protocols command. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.
Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM using the show startup-config command. Verify that the configuration is accurate for the system and each interface.

If an 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 up the interface, contact a service representative for assistance.

Using show Commands to Verify Interface and Controller Status

Use additional show commands, which display interface and controller information, to verify the success of your PA-MC-2T3+ installation and configuration.

You can display information about a specific serial interface on a PA-MC-2T3+ with the following command:

show interfaces serial slot/port-adapter/port/t1-line-number:channel-group-number

where: channel-group-number is 0-23.

Examples follow:

In the example that follows, a VIP2 is in interface processor slot 1, and the PA-MC-2T3+ is in port adapter slot 0.

Router# show interfaces serial 1/0/0/1:0
Serial1/0/0/1:0 is up, line protocol is up
  Hardware is cyBus T3
  Internet address is 1.1.1.1/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 19:04:01, output 12:49:52, output hang never
  Last clearing of "show interface" counters 13:09:09
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     18722 packets input, 2134308 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     82 input errors, 0 CRC, 0 frame, 82 overrun, 0 ignored, 0 abort
     18722 packets output, 2134308 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffers copied, 0 interrupts, 0 failures
     8 carrier transitions no alarm present
  Timeslot(s) Used: 1-24, Transmitter delay is 0 flags, transmit queue length 5
  non-inverted data

In the example that follows, the port adapter is in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# show interfaces serial 1/0/1:0
Serial1/0/1:0 is up, line protocol is up
  Hardware is cyBus T3
  Internet address is 1.1.1.1/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 19:04:01, output 12:49:52, output hang never
  Last clearing of "show interface" counters 13:09:09
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     18722 packets input, 2134308 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     82 input errors, 0 CRC, 0 frame, 82 overrun, 0 ignored, 0 abort
     18722 packets output, 2134308 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffers copied, 0 interrupts, 0 failures
     8 carrier transitions no alarm present
  Timeslot(s) Used: 1-24, Transmitter delay is 0 flags, transmit queue length 5
  non-inverted data

You can display information for all T1 lines within a PA-MC-2T3+ with the command:

show controllers T3 slot/port-adapter/port [brief | tabular | remote performance]

where:

brief displays a list of configurations only.
tabular displays a list of configurations and MIB data in a tabular format.
remote performance displays a list of performance data from the remote end of a T1 connection.

Note If you use the show controllers T3 slot/port-adapter/port command without either of the three optional arguments (brief, tabular, or remote performance), all information is displayed for the T3 controller you specified; therefore, the resulting display output can be extensive.

The following examples show command output display information for a PA-MC-2T3+ in port adapter slot 0 on a VIP2 installed in interface processor slot 1.

Note You can use these three show controllers T3 commands for all other systems in which the PA-MC-2T3+ is supported. The syntax is as follows:

--- show controllers T3 chassis-slot/port brief

--- show controllers T3 chassis-slot/port tabular

--- show controllers T3 chassis-slot/port remote performance

Examples of these show controllers T3 commands using this different syntax are not shown.

show controllers T3 0/1/0/1 tabular

T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.1, CT3 ROM Version: 0.95, CT3 F/W Version: 0.15.3
  FREEDM version: 1, reset 0
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received: No code is being received
  Framing is M23, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
  INTERVAL      LCV   PCV   CCV   PES  PSES  SEFS   UAS   LES   CES  CSES
  13:32-13:38     0     0     0     0     0     0     0     0     0     0
  13:17-13:32     0     0     0     0     0     0     0     0     0     0
  13:02-13:17     0     0     0     0     0     0     0     0     0     0
  12:47-13:02     0     0     0     0     0     0     0     0     0     0
  12:32-12:47     0     0     0     0     0     0     0     0     0     0
  12:17-12:32     0     0     0     0     0     0     0     0     0     0
  12:02-12:17     0     0     0     0     0     0     0     0     0     0
  11:47-12:02     0     0     0     0     0     0     0     0     0     0
  11:32-11:47     0     0     0     0     0     0     0     0     0     0
  11:17-11:32     0     0     0     0     0     0     0     0     0     0
  11:02-11:17     0     0     0     0     0     0     0     0     0     0
  10:47-11:02     0     0     0     0     0     0     0     0     0     0
  10:32-10:47     0     0     0     0     0     0     0     0     0     0
  10:17-10:32     0     0     0     0     0     0     0     0     0     0
  10:02-10:17     0     0     0     0     0     0     0     0     0     0
  09:47-10:02     0     0     0     0     0     0     0     0     0     0
  09:32-09:47     0     0     0     0     0     0     0     0     0     0
  09:17-09:32     0     0     0     0     0     0     0     0     0     0
  09:02-09:17     0     0     0     0     0     0     0     0     0     0
  08:47-09:02     0     0     0     0     0     0     0     0     0     0
  08:32-08:47     0     0     0     0     0     0     0     0     0     0
  08:17-08:32     0     0     0     0     0     0     0     0     0     0
  08:02-08:17     0     0     0     0     0     0     0     0     0     0
  07:47-08:02     0     0     0     0     0     0     0     0     0     0
  07:32-07:47     0     0     0     0     0     0     0     0     0     0
  07:17-07:32     0     0     0     0     0     0     0     0     0     0
  07:02-07:17     0     0     0     0     0     0     0     0     0     0
  06:47-07:02     0     0     0     0     0     0     0     0     0     0
  06:32-06:47     0     0     0     0     0     0     0     0     0     0
  06:17-06:32     0     0     0     0     0     0     0     0     0     0
  06:02-06:17     0     0     0     0     0     0     0     0     0     0
  05:47-06:02     0     0     0     0     0     0     0     0     0     0
  05:32-05:47     0     0     0     0     0     0     0     0     0     0
  05:17-05:32     0     0     0     0     0     0     0     0     0     0
  05:02-05:17     0     0     0     0     0     0     0     0     0     0
  04:47-05:02     0     0     0     0     0     0     0     0     0     0
  04:32-04:47     0     0     0     0     0     0     0     0     0     0
  04:17-04:32     0     0     0     0     0     0     0     0     0     0
  04:02-04:17     0     0     0     0     0     0     0     0     0     0
  03:47-04:02     0     0     0     0     0     0     0     0     0     0
  03:32-03:47     0     0     0     0     0     0     0     0     0     0
  03:17-03:32     0     0     0     0     0     0     0     0     0     0
  03:02-03:17     0     0     0     0     0     0     0     0     0     0
  02:47-03:02     0     0     0     0     0     0     0     0     0     0
  02:32-02:47     0     0     0     0     0     0     0     0     0     0
  02:17-02:32     0     0     0     0     0     0     0     0     0     0
  02:02-02:17     0     0     0     0     0     0     0     0     0     0
  01:47-02:02     0     0     0     0     0     0     0     0     0     0
  01:32-01:47     0     0     0     0     0     0     0     0     0     0
  01:17-01:32     0     0     0     0     0     0     0     0     0     0
  01:02-01:17     0     0     0     0     0     0     0     0     0     0
  00:47-01:02     0     0     0     0     0     0     0     0     0     0
  00:32-00:47     0     0     0     0     0     0     0     0     0     0
	Total           0     0     0     0     0     0     0     0     0     0
 
  T1 1 is down
  timeslots: 1-24
  FDL per ANSI T1.403 and AT&T 54016 spec.
  Transmitter is sending LOF Indication.
  Receiver is getting AIS.
  Framing is ESF, Clock Source is Internal
  INTERVAL      LCV   PCV   CSS  SELS   LES    DM    ES   BES   SES   UAS    SS
  13:32-13:39     0     0     0     0     0     0     0     0     0   396     0
  13:17-13:32     0     0     0     0     0     0     0     0     0   900     0
  13:02-13:17     0     0     0     0     0     0     0     0     0   900     0
  12:47-13:02     0     0     0     0     0     0     0     0     0   900     0
  12:32-12:47     0     0     0     0     0     0     0     0     0   900     0
  12:17-12:32     0     0     0     0     0     0     0     0     0   900     0
  12:02-12:17     0     0     0     0     0     0     0     0     0   900     0
  11:47-12:02     0     0     0     0     0     0     0     0     0   900     0
  11:32-11:47     0     0     0     0     0     0     0     0     0   900     0
  11:17-11:32     0     0     0     0     0     0     0     0     0   900     0
  11:02-11:17     0     0     0     0     0     0     0     0     0   900     0
  10:47-11:02     0     0     0     0     0     0     0     0     0   900     0
  10:32-10:47     0     0     0     0     0     0     0     0     0   900     0
  10:17-10:32     0     0     0     0     0     0     0     0     0   900     0
  10:02-10:17     0     0     0     0     0     0     0     0     0   900     0
  09:47-10:02     0     0     0     0     0     0     0     0     0   900     0
  09:32-09:47     0     0     0     0     0     0     0     0     0   900     0
  09:17-09:32     0     0     0     0     0     0     0     0     0   900     0
  09:02-09:17     0     0     0     0     0     0     0     0     0   900     0
  08:47-09:02     0     0     0     0     0     0     0     0     0   900     0
  08:32-08:47     0     0     0     0     0     0     0     0     0   900     0
  08:17-08:32     0     0     0     0     0     0     0     0     0   900     0
  08:02-08:17     0     0     0     0     0     0     0     0     0   900     0
  07:47-08:02     0     0     0     0     0     0     0     0     0   900     0
  07:32-07:47     0     0     0     0     0     0     0     0     0   900     0
  07:17-07:32     0     0     0     0     0     0     0     0     0   900     0
  07:02-07:17     0     0     0     0     0     0     0     0     0   900     0
  06:47-07:02     0     0     0     0     0     0     0     0     0   900     0
  06:32-06:47     0     0     0     0     0     0     0     0     0   900     0
  06:17-06:32     0     0     0     0     0     0     0     0     0   900     0
  06:02-06:17     0     0     0     0     0     0     0     0     0   900     0
  05:47-06:02     0     0     0     0     0     0     0     0     0   900     0
  05:32-05:47     0     0     0     0     0     0     0     0     0   900     0
  05:17-05:32     0     0     0     0     0     0     0     0     0   900     0
  05:02-05:17     0     0     0     0     0     0     0     0     0   900     0
  04:47-05:02     0     0     0     0     0     0     0     0     0   900     0
  04:32-04:47     0     0     0     0     0     0     0     0     0   900     0
  04:17-04:32     0     0     0     0     0     0     0     0     0   900     0
  04:02-04:17     0     0     0     0     0     0     0     0     0   900     0
  03:47-04:02     0     0     0     0     0     0     0     0     0   900     0
  03:32-03:47     0     0     0     0     0     0     0     0     0   900     0
  03:17-03:32     0     0     0     0     0     0     0     0     0   900     0
  03:02-03:17     0     0     0     0     0     0     0     0     0   900     0
  02:47-03:02     0     0     0     0     0     0     0     0     0   900     0
  02:32-02:47     0     0     0     0     0     0     0     0     0   900     0
  02:17-02:32     0     0     0     0     0     0     0     0     0   900     0
  02:02-02:17     0     0     0     0     0     0     0     0     0   900     0
  01:47-02:02     0     0     0     0     0     0     0     0     0   900     0
  01:32-01:47     0     0     0     0     0     0     0     0     0   900     0
  01:17-01:32     0     0     0     0     0     0     0     0     0   900     0
  01:02-01:17     0     0     0     0     0     0     0     0     0   900     0
  00:47-01:02     0     0     0     0     0     0     0     0     0   900     0
  00:32-00:47     0     0     0     0     0     0     0     0     0   900     0
  00:17-00:32     0     0     0     0     0     0     0     0     0   900     0
  Total           0     0     0     0     0     0     0     0     0 47700     0
 
  T1 2 is up
  timeslots: 1-24
  FDL per ANSI T1.403 and AT&T 54016 spec.
  No alarms detected.
  Framing is ESF, Clock Source is Internal
  INTERVAL      LCV   PCV   CSS  SELS   LES    DM    ES   BES   SES   UAS    SS
  13:32-13:39     0     0     0     0     0     0     0     0     0     0     0
  13:17-13:32     0     0     0     0     0     0     0     0     0     0     0
  13:02-13:17     0     0     0     0     0     0     0     0     0     0     0
  12:47-13:02     0     0     0     0     0     0     0     0     0     0     0
  12:32-12:47     0     0     0     0     0     0     0     0     0     0     0
  12:17-12:32     0     0     0     0     0     0     0     0     0     0     0
  12:02-12:17     0     0     0     0     0     0     0     0     0     0     0
(additional displayed text not shown)

show controllers t3 4/0/0/1

router # show controllers t3 4/0/0/1
T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.0, CT3 ROM Version: 0.95, CT3 F/W Version: 0.3.9
  FREEDM version: 1, reset 0
 
  T1 1 is up
  timeslots: 1-24
  FDL per AT&T 54016 spec.
  Transmitter is sending LOF Indication.
  Receiver is getting AIS.
  Framing is ESF, Clock Source is Internal
.
.
.
(additional displayed text not shown)

show controllers t3 4/0/0/1 remote performance

router # show controllers t3 4/0/0/1 remote performance
T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.0, CT3 ROM Version: 0.95, CT3 F/W Version: 0.3.9
  FREEDM version: 1, reset 0
 
  T1 1 - Remote Performance Data (Not available)
.
.
.
(additional displayed text not shown)

Note In the preceding example, remote performance data is unavailable.

show controllers t3 4/0/0/1 brief

T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.1, CT3 ROM Version: 0.95, CT3 F/W Version: 0.15.3
  FREEDM version: 1, reset 0
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received: No code is being received
  Framing is M23, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
 
  T1 1 is down
  timeslots: 1-24
  FDL per ANSI T1.403 and AT&T 54016 spec.
  Transmitter is sending LOF Indication.
  Receiver is getting AIS.
  Framing is ESF, Clock Source is Internal
 
  T1 2 is up
  timeslots: 1-24
  FDL per ANSI T1.403 and AT&T 54016 spec.
  No alarms detected.
  Framing is ESF, Clock Source is Internal
 
  T1 3 is up
  timeslots: 1-24
  FDL per ANSI T1.403 and AT&T 54016 spec.
  No alarms detected.
  Framing is ESF, Clock Source is Internal
(additional displayed text not shown)

If you use the show controllers T3 command without specifying a port address (slot/port-adapter/port/t1-line-number), all information is displayed for all 28 T1 lines within every T3 port adapter in the router; therefore, the resulting display output can be extensive.

You can also display brief configuration information or tabular configuration and MIB information about a specific T1 line within a PA-MC-2T3+ with the command:

show controllers T3 slot/port-adapter/port/t1-line-number [brief | tabular | remote performance]

where:

t1-line-number is 1-28.
brief displays a list of configurations only.
tabular displays a list of configurations and MIB data in a tabular format.

The following examples show command output display information for a PA-MC-2T3+ in port adapter slot 0 on a VIP2 installed in interface processor slot 1, using the following commands.

Note You can use these show controllers T3 commands in all other systems in which the PA-MC-2T3+ is supported. The syntax is as follows:

--- show controllers T3 chassis-slot/port/t1-line-number brief

--- show controllers T3 chassis-slot/port/t1-line-number tabular

Examples of these show controllers T3 commands, using this different syntax, are not shown.

show controllers T3 1/0/0/1 brief

Router# show controllers T3 4/0/0 brief
 
T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.1, CT3 ROM Version: 0.95, CT3 F/W Version: 0.15.3
  FREEDM version: 1, reset 0
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received: No code is being received
  Framing is M23, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
 
(additional displayed text not shown)

show controllers T3 1/0/0/1 tabular

Router# show controllers t3 4/0/0 tabular
 
T3 4/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version: 0.1.1, CT3 ROM Version: 0.95, CT3 F/W Version: 0.15.3
  FREEDM version: 1, reset 0
  Applique type is Channelized T3
  No alarms detected.
  FEAC code received: No code is being received
  Framing is M23, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
  INTERVAL      LCV   PCV   CCV   PES  PSES  SEFS   UAS   LES   CES  CSES
  13:32-13:38     0     0     0     0     0     0     0     0     0     0
  13:17-13:32     0     0     0     0     0     0     0     0     0     0
  13:02-13:17     0     0     0     0     0     0     0     0     0     0
  12:47-13:02     0     0     0     0     0     0     0     0     0     0
  12:32-12:47     0     0     0     0     0     0     0     0     0     0
  12:17-12:32     0     0     0     0     0     0     0     0     0     0
  12:02-12:17     0     0     0     0     0     0     0     0     0     0
  11:47-12:02     0     0     0     0     0     0     0     0     0     0
  11:32-11:47     0     0     0     0     0     0     0     0     0     0
 
(additional displayed text not shown)

Note To enable and display remote performance reports, see the "Enabling Performance Reports" section, and the "Displaying Remote Performance Reports" section.

You can also display information about a specific T1 line within a PA-MC-2T3+ with the following command:

show controllers T3 slot/port-adapter/port/t1-line-number

where: t1-line-number is 1-28.

Using show Commands to Verify System Status

You can display the configuration of system hardware (the number of each interface type installed), the Cisco IOS software version, the names and sources of configuration files, and the boot images with the show version command.

Examples follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# show version
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(5.6)S2 [soma-v120_6
_s_throttle.build2 108]
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Tue 17-Aug-99 23:39 by biff
Image text-base: 0x60010908, data-base: 0x61030000
 
ROM: System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
BOOTFLASH: RSP Software (RSP-BOOT-M), Version 12.0(19990624:041614)
 [sju-mc2t3h 293]
 
7513_1 uptime is 4 days, 6 hours, 11 minutes
System returned to ROM by reload
 
cisco RSP2 (R4700) processor with 131072K/2072K bytes of memory.
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Last reset from power-on
G.703/E1 software, Version 1.0.
G.703/JT2 software, Version 1.0.
Channelized E1, Version 1.0.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Bridging software.
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Chassis Interface.
1 EIP controller (4 Ethernet).
1 HIP controller (1 HSSI).
1 FSIP controller (8 Serial).
1 AIP controller (1 ATM).
1 TRIP controller (4 Token Ring).
1 FIP controller (1 FDDI).
2 VIP2 R5K controllers (2 E1)(2 Channelized T3).
4 Ethernet/IEEE 802.3 interface(s)
4 Token Ring/IEEE 802.5 interface(s)
66 Serial network interface(s)
1 HSSI network interface(s)
1 FDDI network interface(s)
1 ATM network interface(s)
2 Channelized T3 port(s)
123K bytes of non-volatile configuration memory.
 
16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
16384K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
No slave installed in slot 7.
Configuration register is 0x0

You can determine which type of port adapter is installed on a VIP2 in your system with the show diag slot command. Specific port adapter information is displayed.

Examples follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 3:

Router# show diag 3
Slot 3:
        Physical slot 3, ~physical slot 0xC, logical slot 3, CBus 0
        Microcode Status 0x4
        Master Enable, LED, WCS Loaded
        Board is analyzed
        Pending I/O Status: None
        EEPROM format version 1
        VIP2 R5K controller, HW rev 2.01, board revision B0
        Serial number: 06747787  Part number: 73-2167-03
        Test history: 0x00        RMA number: 00-00-00
        Flags: cisco 7000 board; 7500 compatible
 
        EEPROM contents (hex):
          0x20: 01 1E 02 01 00 66 F6 8B 49 08 77 03 00 00 00 00
          0x30: 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 
        Slot database information:
        Flags: 0x4      Insertion time: 0x1B50 (19:07:47 ago)
 
        Controller Memory Size: 64 MBytes DRAM, 8192 KBytes SRAM
 
PA Bay 0 Information:
                2CT3 single wide PA, 2 ports
                EEPROM format version 1
                HW rev 0.00, Board revision UNKNOWN
                Serial number:01740340  Part number:00-0000-00 
 
The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:
Router# show diag 1
 
PA Bay 0 Information:
                2CT3 single wide PA, 2 ports
                EEPROM format version 1
                HW rev 0.00, Board revision UNKNOWN
                Serial number:01740340  Part number:00-0000-00

For additional command descriptions and examples for serial interfaces, see the publications listed in the "Related Documentation" section of Preface .

Enabling Performance Reports

To enable and disable 1-second transmissions of performance reports through the facility data link (per ANSI T1.403 specification), you must use the following command on both ends of the connection:

t1 t1-line-number fdl ansi

where: t1-line-number is 1-28.

Note You can use this command only when the T1 framing is ESF. Use the no form of the command to disable remote performance reports.

Displaying Remote Performance Reports

To display remote (far-end) performance data, use the following command:

show controllers T3 0/1/0 remote performance.

Examples follow:

The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# show controlers T3 0/1/0 remote performance 
T3 1/0/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version : 1.0.0, CT3 ROM Version: 1.1, CT3 F/W Version: 0.23.0
  FREEDM version: 1
 
  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:
     0 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
     0 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
.
.
.
(additional displayed text not shown)

Note If you do not first enable remote performance data with the t1 t1-line-number fdl ansi command, the following is displayed:

T1 1 - Remote Performance Data (Not available)

The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# show controllers T3 1/0 remote performance 
T3 1/0 is up.  Hardware is 2CT3 single wide port adapter
  CT3 H/W Version :1.0.1, CT3 ROM Version :1.1, CT3 F/W Version :2.0.1
  FREEDM version:1, reset 0
 
  T1 1 - Remote Performance Data
  Data in current interval (640 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
 
  T1 2 - Remote Performance Data
  Data in current interval (640 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
  T1 3 - Remote Performance Data
  Data in current interval (7 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
 
  T1 4 - Remote Performance Data (Not available)
 
  T1 5 - Remote Performance Data (Not available)
 
  T1 6 - Remote Performance Data (Not available)
.
.
.
(additional displayed text not shown)

Note If you do not first enable remote performance data with the t1 t1-line-number fdl ansi command, the following is displayed:

T1 1 - Remote Performance Data (Not available)

Note The PA-MC-2T3+ does not support controlled slip seconds.

Using loopback Commands

If you have difficulty with the PA-MC-2T3+ configuration or installation, you can troubleshoot the port adapter using the loopback command. Specify loopback for a T1 line using the following command:

t1 t1-line-number loopback [local | network | remote]

where: t1-line-number is 1-28.

Note This command requires that you are in T3 controller mode.

Note Fdl loopback commands are available only for T1 lines configured for ESF framing.

Explanations of specific loopback modes follow:

local

(Optional.) Loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network.

network {line | payload}

(Optional). Loops the data back toward the network before the T1 framer and automatically sets a local loopback at the HDLC controllers (line), or loops the payload data back toward the network at the T1 framer and automatically sets a local loopback at the HDLC controllers (payload).

remote line fdl {ansi | bellcore}

(Optional.) Sends a repeating, 16-bit ESF data link code word (00001110 11111111 for ANSI; 00010010 11111111 for Bellcore) to the remote end, requesting that it enter into a network line loopback.

Specify the ansi keyword to enable the remote line facility data link (FDL) ANSI bit loopback on the T1 channel, per the ANSI T1.403 specification.

Specify the bellcore keyword to enable the remote SmartJack loopback on the T1 channel, per the TR-TSY-000312 specification.

remote line inband

(Optional.) Sends a repeating, 5-bit inband pattern (00001) to the remote end, requesting that it enter into a network line loopback.

remote payload [fdl] [ansi]

(Optional.) 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. Enables the remote payload Facility Data Link (FDL) ANSI bit loopback on the T1 channel.

You can optionally specify fdl and ansi, but it is not necessary.

Examples of the loopback commands follow:

Set the first T1 line into local loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loopback local

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loopback local

: In the preceding examples, local loopback loops the router output data back toward the router at the T1 framer and sends an AIS out toward the network.

Set the first T1 line into network line loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loopback network line

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loopback network line

: In the preceding examples, network line loopback loops the data back toward the network (before the T1 framer).

Set the first T1 line into network payload loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loopback network payload

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loopback network payload

: In the preceding examples, network payload loopback loops just the payload data back toward the network at the T1 framer.

Examples of the loopback remote command follow, where the command syntax is:

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

Set the first T1 line into remote line inband loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loop remote line inband

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loop remote line inband

: In the preceding examples, remote line inband loopback sends a repeating five-bit in-band pattern (of 00001) to the remote end, requesting that it enter into a network line loopback.

Set the first T1 line into remote line FDL ANSI bit loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loop remote line fdl ansi

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loop remote line fdl ansi

: In the preceding examples, remote line FDL ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 00001110 11111111) to the remote end, requesting that it enter into a network line loopback.

Set the first T1 line into remote payload FDL ANSI bit loopback.

: The example that follows is for a port adapter on a VIP2 in interface processor slot 1:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0/0
Router(config-controller)# t1 1 loop remote payload fdl ansi

: The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7246:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# controller T3 1/0
Router(config-controller)# t1 1 loop remote payload fdl ansi

: In the preceding examples, remote payload ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 00010100 11111111) to the remote end, requesting that it enter into a network payload loopback.

Using the ping Command to Verify Network Connectivity

This section provides brief descriptions of the ping command, with which you can verify that an interface port is functioning properly and to check the path between a specific port and connected devices at various locations on the network. After you verify that the system and VIP2 have booted successfully and are operational, you can use this command to verify the status of interface ports. (For additional information on the ping command, refer to the publications listed in the "Related Documentation" section of the preface "About This Manual.")

The ping command sends an echo request out to a remote device at an IP address that you specify. After sending a series of signals, the command waits a specified time for the remote device to echo the signals. Each returned signal is displayed as an exclamation point (!) on the console terminal; each signal that is not returned before the specified timeout is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate that the connection failed.

Following is an example of a successful ping command to a remote server with the IP address 1.1.1.10. (Press Return after entering the ping command and IP address.)

Router# ping 1.1.1.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 1.1.1.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms
Router#

If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.

local	(Optional.) Loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network.
network {line \| payload}	(Optional). Loops the data back toward the network before the T1 framer and automatically sets a local loopback at the HDLC controllers (line), or loops the payload data back toward the network at the T1 framer and automatically sets a local loopback at the HDLC controllers (payload).
remote line fdl {ansi \| bellcore}	(Optional.) Sends a repeating, 16-bit ESF data link code word (00001110 11111111 for ANSI; 00010010 11111111 for Bellcore) to the remote end, requesting that it enter into a network line loopback. Specify the ansi keyword to enable the remote line facility data link (FDL) ANSI bit loopback on the T1 channel, per the ANSI T1.403 specification. Specify the bellcore keyword to enable the remote SmartJack loopback on the T1 channel, per the TR-TSY-000312 specification.
remote line inband	(Optional.) Sends a repeating, 5-bit inband pattern (00001) to the remote end, requesting that it enter into a network line loopback.
remote payload [fdl] [ansi]	(Optional.) 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. Enables the remote payload Facility Data Link (FDL) ANSI bit loopback on the T1 channel. You can optionally specify fdl and ansi, but it is not necessary.

Table of Contents

Configuring the PA-MC-2T3+

Configuring a BER Test on a T1 Line