Table of Contents

Using the EXEC Command Interpreter
Configuring the Interfaces

Configuring T1 Lines

T1 Line Configuration Commands
Configuring a BER Test on a T1 Line
Sending a BERT Pattern on a T1 Line
Viewing the Results of a BERT
Terminating a BERT

Shutting Down an Interface
Performing a Basic Configuration
Configuring the T3 Controller

T3 Controller Configuration Commands
Configuring MDL Messages
Examples of MDL Message Configuration
Configuring Idle Patterns
Configuring the Loopback Mode for the T3 Controller
Configure the T3 Controller for Remote T3 Loopback
Shutting Down the T3 Controller

Checking the Configuration

Using show Commands to Display New Interface Status

Using the show version or show hardware Commands
Using the show diag Command
Using the show interfaces Command
Cisco 7200 Series and Cisco uBR7200 Series Routers

Enabling Performance Reports
Displaying Remote Performance Reports
Using the ping Command to Verify Network Connectivity
Using loopback Commands

Configuring the PA-MC-T3

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

• Using the EXEC Command Interpreter

• Configuring the Interfaces

• Configuring the T3 Controller

• Checking the Configuration

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:

Router> enable

Password:

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

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

Router#
 

To configure the new interfaces, proceed to the "Configuring the Interfaces" section.

Configuring the Interfaces

After you verify that the new PA-MC-T3 is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. Have the following information available:

For a summary of the configuration operations available and instructions for configuring interfaces on a PA-MC-T3, refer to the appropriate configuration publications listed in the "Related Documentation" section.

You execute configuration commands from the privileged-level access of the EXEC command interpreter, which usually requires password access. Contact your system administrator, if necessary, to obtain password access. (See the "Using the EXEC Command Interpreter" section for and explanation of the privileged level of the EXEC.)

This section contains the following subsections:

• Configuring T1 Lines

• Shutting Down an Interface

• Performing a Basic Configuration

• Configuring the T3 Controller

Configuring T1 Lines

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

• T1 Line Configuration Commands

• Configuring a BER Test on a T1 Line

• Sending a BERT Pattern on a T1 Line

• Viewing the Results of a BERT

• Terminating a BERT

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. The PA-MC-T3 port addressing might be different depending on the interface processor slot in which the VIP is installed and the VIP port adapter slot in which the PA-MC-T3 is installed.

T1 Line Configuration Commands

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 to 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 to 28 can be channelized).

• channel-group-number is 0 to 23.

• timeslots list-of-timeslots can be 1 to 24 or a combination of subranges within 1 to 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.

Table 4-1 shows the configuration of logical channel group 20 on T1 line 1 assigning channelized timeslots 1 to 5 and 20 to 23.

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 to 28.

• channel-group-number is 0 to 23.

Table 4-1 shows how to remove logical channel group 10 from channelized T1 line 1.

Table 4-1: T1 Line Configuration Commands

Purpose	Command	Example	Additional Information
Create a Logical Channel group on a T1 line	t1 t1-line-number channel-group channel-group-number	The example is for interface 0 on a port adapter in slot 1 Router(config)# controller t3 1/0 Router(config-controller)# t1 1 channel-group 20 timeslots 1-5, 20-23
Remove a Channel Group from a T1 Line	no t1 t1-line-number channel-group channel-group-number	The example is for interface 0 on a port adapter in port adapter slot 1. Router(config)# controller t3 1/0 Router(config-controller)# no t1 1 channel-group 10
Configure a T1 line as a PRI ISDN group	t1 t1-line-number pri-group timeslots range	The example configures T1 channel 1 for fulle T1 bandwidth, and as a PRI ISDN group. Router(config)# t1 1 pri-group timeslots 1-24	t1-line-number is 1 to 28 rante is 1 to 24, excluding timeslot 16 (supports contiguous time slots and arbitrary time slots.) Default ranges for timeslots are 1 to 15 and 17 to 24; timeslot 16 is always excluded as a data channel.
		The example is configures T1 channel 2 to use timeslots 1 to 5 and 20 to 23 and as a PRI ISDN group. Router(config-controll)# t1 2 pri-group timeslots 1-5, 20-23
Remove a PRI ISDN group from a T1 line	no t1 t1-line-number pri-group	The examle removes PRI ISDN group 1. Router(config-controll)# no pri-group t1 1
Set the framing format on a T1 Line	t1 t1-line-number framing {esf | sf}	The example sets super frame (SF) framing for T1 line 6. Router(config)# controller t3 1/0 Router(config-controller)# t1 6 framing sf	Default framing format is Extended Superframe (ESF).
Turn detection or generation of a yellow alarm on and off.	[no] t1 t1-line-number yellow {detection | generation}	The example turns the detection of a yellow alarm off on a T1 line number 6. Router (config-controller)# no t1 6 yellow detection	When you select SF framing, you should consider turning off yellow alarm detection, because the yellow alarm can be incorrectly detected with SF framing.
Set ESF framing format for T1 line 16	t1 16 framing esf	The example sets ESF framing format for T1 line 16. Router(config)# controller t3 1/0 Router(config-controller)# t1 16 framing esf
Set internal clock source on a T1 line	t1 t1-line-number clock source {internal | line}	The example configures T1 line 1 to use an internal clock source on a VIP in interface processor slot 1. Router(config)# controller t3 1/0/0 Router(config-controller) # t1 1 clock source internal	t1-line-number is 1 to 28. The default clock source is internal. You can set the clock source to use internal clocking for testing purposes. One end of a T1 circuit must provide the clock source.
Set line clock source on a T1 line.	t1 t1-line-number clock source {internal | line}	Example configures T1 line 16 using a line clock source on a VIP in interface processor slot 1 Router(config)# controller t3 1/0/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 apply 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, including optimum switching, 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 MC-T3 port adapter. Using BERT you can test cables and signal problems in the field. You can configure individual T1 lines to run an independent BERT; each T1 line has its own BERT circuitry.

Two categories of test patterns can be generated by the onboard BERT 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,440 minutes (240 hours), and you can also retrieve the error statistics anytime during the BERT.

Note BER testing for the T3 link is not supported.

When running a BERT, your system expects to receive the same pattern that it is transmitting. To help ensure this, you can use one of two common options:

• Use a loopback somewhere in the link or network.

• Configure remote testing equipment to transmit the same BERT pattern at the same time.

Sending a BERT Pattern on a T1 Line

You can send a BERT pattern on a T1 line with the controller command:

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

where:

• t1-line-number is 1 to 28.

• time is 1 to 14440 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... .

---

Note Use unframed T1 to run BERTs. If you do not specify unframed, the port adapter uses the currently configured T1 framing option to run a BERT.

---

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 VIP 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 on a Catalyst RSM/VIP2 in slot 1:

Router(config)# controller t3 1/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 uBR7200 series:

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 14440 minutes (240 hours).

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

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

The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1:

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

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

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

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

Viewing the Results of a BERT

You can view the results of a BERT using the controller command:

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

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

You can view the results of a BERT 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 to 28.

Examples follow:

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

Router# show controllers t3 1/0/0/1
T3 1/0/0 is up.
CT3 H/W Version : 3, CT3 ROM Version : 0.79, CT3 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 on a VIP4 in interface processor slot 1:

vip4_tb1_uut2#show controllers
T3 8/0/0 is down.  Hardware is CT3 single wide port adapter
  CT3 H/W Version:1.0.1, CT3 ROM Version:1.1, CT3 F/W Version:2.3.0
  FREEDM version:1, reset 0
  Applique type is Channelized T3
  Transmitter is sending remote alarm.
  Receiver has loss of signal.
  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
  Data in current interval (96 seconds elapsed):
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     106 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
 
  T1 1
    Not configured.
 
  T1 2
    Not configured.
 
  T1 3
    Not configured.
 
  T1 4
    Not configured.
 
  T1 5
    Not configured.
 
  T1 6
    Not configured.
 
  T1 7
    Not configured.
 
  T1 8
    Not configured.
 
  T1 9
    Not configured.
 
  T1 10
    Not configured.
 
  T1 11
    Not configured.
 
  T1 12
    Not configured.
 
  T1 13
    Not configured.
 
  T1 14
    Not configured.
 
  T1 15
    Not configured.
 
  T1 16
    Not configured.
 
  T1 17
    Not configured.
 
  T1 18
    Not configured.
 
  T1 19
    Not configured.
 
  T1 20
    Not configured.
 
  T1 21
    Not configured.
 
  T1 22
    Not configured.
 
  T1 23
    Not configured.
 
  T1 24
    Not configured.
 
  T1 25
    Not configured.
 
  T1 26
    Not configured.
 
  T1 27
    Not configured.
 
  T1 28
    Not configured.
 

• The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1:

Router# show controllers t3 1/0/1
T3 1/0 is up.
CT3 H/W Version : 3, CT3 ROM Version : 0.79, CT3 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 example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series:

Router# show controllers t3 1/0/1
T3 1/0 is up.
CT3 H/W Version : 3, CT3 ROM Version : 0.79, CT3 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 BERT 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 BERT 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 The BERT runs over the currently configured framing option for the specified T1 line (ESF or SF). Before running a BERT, you should configure the framing option that is appropriate to your application. You can run the BERT unframed by specifying unframed.

Terminating a BERT

You can terminate a BERT with the controller command:

no t1 t1-line-number bert

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

Examples follow:

Terminate the BERT running on T1 line 10.

• The example that follows is for a port adapter on a VIP 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 on a Catalyst RSM/VIP2 in slot 1:

Router(config)# controller t3 1/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 uBR7200 series:

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:

• Shutting Down an Interface

• Performing a Basic Configuration

• Configuring the T3 Controller

Shutting Down an Interface

Before you remove an interface that you will not replace or replace port adapters, use the shutdown command to shut down (disable) the interfaces to prevent anomalies when you reinstall the new or reconfigured interface processor. When you shut down an interface, it is designated administratively down in the show command displays.

Follow these steps to shut down an interface:

Step 2 At the privileged-level prompt, enter configuration mode and specify that the console terminal is the source of the configuration subcommands, as follows"

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

Step 3 Shut down interfaces by entering the interfaces serial subcommand (followed by the interface address of the interface), and then enter the shutdown command. shows the command syntax.

This step assumes you have already configured the logical channel group. For channelized T1 lines, channel-group-number can be 0 to 23.

When you have finished, press Cntl-Z---hold down the Control key while you press Z--- or enter end or exit to exit configuration mode and return to the EXEC command interpreter.

Table 4-2: Syntax of the shutdown Command

Platform	Command	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	interface, followed by the type (serial) slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-nuimber	The example is for logical channel group 1 on T1 line1 of the T3 link on a port adapter on interface 0 in port adapter slot 1. Router(config)# interface serial 1/0/1:1 Router(config-if)# shutdown Ctrl-Z Router#
Cisco 7200 series and Cisco uBR7200 series routers	interface, followed by the type (serial) slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-nuimber	The example is for logical channel group 1 on T1 line 1 of the T3 link on interface 0 of a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0/1:1 Router(config-if)# shutdown Ctrl-Z Router#
VIP in Cisco 7000 series or Cisco 7500 series routers	interface serial, followed by the type and slot/port-adapter/port (interface-processor-slot-number/ port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-number	The example is for logical channel group1 on T1 line 1 of the T3 link on interface 0 on a port adapter in port adapter slot 1 of a VIP installed in interface processor slot 1. Router(config-if)# interface serial 1/1/0/1:1 Router(config-if)# shutdown Ctrl-Z Router#

Note If you need to shut down additional interfaces, enter the interface serial command (followed by the address of the interface) for each of the interfaces on your port adapter. Use the no shutdown command to enable the interface.

Step 4 Write the new configuration to NVRAM as follows:

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

The system displays an OK message when the configuration has been stored in NVRAM.

Step 5 Verify that new interfaces are now in the correct state (shut down) using the show interfaces command (followed by the interface type and interface address of the interface) to display the specific interface.

Table 4-3: Examples of the show interfaces Command

Platform	Command	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	show interfaces serial, followed by slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-number	The example is for T1 line 1, channel group number 0 and interface 0 on a port adapter in port adapter slot 1. Router# show interfaces serial 1/0/1:0 Serial 1/0/1:0 is administratively down, line protocol is down [Additional display text omitted from this example]
Cisco 7200 series and Cisco uBR7200 series routers	show interfaces serial, followed by slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-number	The example is for T1 line 1, channel group number 0, interface 0 on a port adapter in port adapter slot 1. Router# show interfaces serial 1/0/1:0 Serial 1/0/1:0 is administratively down, line protocol is down [Additional display text omitted from this example]
VIP in Cisco 7000 series or Cisco 7500 series routers	show interfaces serial, followed by slot/port adapter/port (interface-processor-slot-number/ port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-number	The example is forT1 line 1, channel group  0, interface 0 on a port adapter in port adapter slot 0 of a VIP in interface processor slot 1. Router# show interfaces serial 1/0/0/1:0 Serial 1/0/0/1:0 is administratively down, line protocol is down   [Additional display text omitted from this example]

Step 6 Reenable the interfaces by doing the following:

a. Repeat Step 3 to reenable an interface. Substitute the no shutdown command for the shutdown command.

b. Repeat Step 4 to write the new configuration to memory. Use the copy running-config startup-config command

c. Repeat Step 5 to verify that the interfaces are in the correct state. Use the show interfaces command followed by the interface type and interface address of the interface.

For complete descriptions of software configuration commands, refer to the publications listed in the "Related Documentation" section.

Performing a Basic Configuration

Following are instructions for a basic configuration: enabling an interface, specifying IP routing, and configuring the T3 controller. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. For complete descriptions of configuration subcommands and the configuration options available for serial interfaces, refer to the appropriate software documentation.

In the following procedure, press the Return key 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>

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

Step 2 Specify the first interface to configure by entering the interface serial subcommand, followed by the interface address of the interface you plan to configure.

Table 4-4: Examples of the interface serial Subcommand

Platform	Command	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	interface, followed by the type (serial) slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-nuimber	The example is for logical channel group 1 on T1 line1 of the T3 link on a port adapter on interface 0 in port adapter slot 1. Router(config)# interface serial 1/0/1:1 Router(config-if)#
Cisco 7200 series and Cisco uBR7200 series routers	interface, followed by the type (serial) slot/port (port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-nuimber	The example is for logical channel group 1 on T1 line 1 of the T3 link on interface 0 of a port adapter in port adapter slot 1. Router(config-if)# interface serial 1/0/1:1 Router(config-if)#
VIP in Cisco 7000 series or Cisco 7500 series routers	interface, followed by the type (serial) and slot/port adapter/port (interface-processor-slot-number/ port-adapter-slot-number/ interface-port-number)/t1-line-number:channel-group-number	The example is for logical channel group1 on T1 line 1 of the T3 link on interface 0 on a port adapter in port adapter slot 1 of a VIP installed in interface processor slot 1. Router(config-if)# interface serial 1/1/0/1:1 Router(config-if)# s

Step 3 Assign an IP address and subnet mask to the interface (if IP routing is enabled on the system) by using the ip address subcommand, as in the following example:

Router(config-if)# ip address 10.0.0.0 10.255.255.255
 

Step 4 Add any additional configuration cubcommands required to enable routing protocols and set the interface characteristics.

Step 5 Reenable the interfaces using the no shutdown command. (See the "Shutting Down an Interface" section.)

Step 6 Configure all additional port adapter interfaces as required.

Step 7 After including all of the configuration subcommands to complete your configuration, press Ctrl-Z-hold down the Control key while you press Z---or enter end or exit to exit configuration mode and return to the EXEC command interfpreter prompt.

Step 8 Write the new configuration to NVRAM as follows:

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

This completes the procedure for creating a basic configuration.

Configuring the T3 Controller

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

• T3 Controller Configuration Commands

• Configuring MDL Messages

• Examples of MDL Message Configuration

• Configuring Idle Patterns

• Configuring the Loopback Mode for the T3 Controller

• Configure the T3 Controller for Remote T3 Loopback

• Shutting Down the T3 Controller

T3 Controller Configuration Commands

Table 4-5 provides examples of T3 controller configuration commands

Table 4-5: T3 Controller Configuration Commands

Purpose	Command	Example	Additional Information
Select a T3 controller	controller t3 slot/port-adapter/port	The example shows a port adapter on a Cisco 7200 series router in port adapter slot 1. Router# controller t3 1/0	You must enter this command before any other T3 configuration commands.
Set the Framing Type for a T3 controller	framing [c-bit | m23 | auto-detect]	The example sets c-bit framing. Router(config-controller)# framing c-bit The example sets m23 framing. Router(config-controller)# framing m23	You can request the PA-MC-T3 to detect the framing type it is to receive from the far end as follows: router(config-controller)# framing auto-detect
Specify the cable length1	cablelength feet	Router(config-controller)# cablelength 402	feet is a numberal from 0 to 450. The default value is 49 feet.
Set the clock source for the T3 Controller	clock source {internal | line}	The example instructs a PA-MC-T3 on a VIP in interface processor slot 1 to use a line clock source. Router(config)# controller t3 1/0/0 Router(config-controller)# clock source line The example instructs a PA-MC-T3 on a Cisco 7200 series router to use an internal clock source. Router(config)# controller t3 1/0 Router(config-controller)# clock source line

1User-specified T3 cable lengths are structured into ranter 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 vaule applies is used. 2Sinc a cable length of 40 is specified, the 0--49 range is used. If you change the cable length to 45, 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 rante (0-49) to the other ranter (50-450) has an effect. The actual cable-length number you enter is store in the configuration file.

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

Note MDL messages are only supported when the T3 framing is set for c-bit parity. (See Table 4-5 for T3 controller configuration commands.)

To configure MDL messages, use the controller commands:

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 VIP 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 on a Catalyst RSM/VIP2 in slot 1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
Router(config)# controller t3 1/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 uBR7200 series:

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

Table 4-6: MDL Message Configurations

Purpose	Command	Example
Enable the MDL path message transmission	mdl transmit path	Router(config-controller)#mdl transmit path
Enable the MDL idle signal message transmission	mdl transmit idle-signal	Router(config-controller)# mdl transmit idle-signal
Enable the MDL test signal message transmission	mdl transmit test-signal	Router(config-controller)# mdl transmit test-signal
Enter the equipment identification code	mdl string eic router A	Router(config-controller)# mdl string eic router A
Enter the location identification code	mdl string eic router A	Router(config-controller)# mdl string lic test network
Enter the frame identification code	mdl string fic building b	Router(config-controller)# mdl string fic building b
Enter the unit identification code	mdl string unit abc	Router(config-controller)# mdl string unit abc
Enter the facility identification code to send in the MDL path message	mdl string pfi string	Router(config-controller)# mdl string pfi string
Enter the port number to send in the MDL idle signal message	mdl string port string	Router(config-controller)# mdl string port string
Enter the generator number to send in the MDL test signal message	mdl string generator string	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).

Table 4-6 summarizes the idle pattern controller command.

Table 4-7: Idle Pattern Command Examples

Platform	Purpose	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	Set a hexadecimal idle pattern	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# idle pattern 0x10
Cisco 7200 series and Cisco uBR7200 series routers	Set a hexadecimal idle pattern	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# idle pattern 0x10
VIP in Cisco 7000 series or Cisco 7500 series routers	Sets a hexadecimal idle pattern	The example is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/0 Router(config-controller)# idle pattern 0x10
Catalyst RSM/VIP2 in Catalyst 5000 family switches	Sets a decimal idle pattern	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# idle pattern 23
Cisco 7200 series and Cisco uBR7200 series routers	Sets a decimal idle pattern	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# idle pattern 23
VIP in Cisco 7000 series or Cisco 7500 series routers	Sets a decimal idle pattern	The example that follows is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/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.

Table 4-8 summarizes the loopback mode controller commands.

Table 4-8: Configuring the Loopback Mode for the T3 Controller

Platform	Purpose	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	Configure the T3 controller for local loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# loopback local
Cisco 7200 series and Cisco uBR7200 series routers	Configure the T3 controller for local loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# loopback local
VIP in Cisco 7000 series or Cisco 7500 series routers	Configure the T3 controller for local loopback	The example that follows is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/0 Router(config-controller)# loopback local
Catalyst RSM/VIP2 in Catalyst 5000 family switches	Configure the T3 controller for network loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# loopback network
Cisco 7200 series and Cisco uBR7200 series routers	Configure the T3 controller for network loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# loopback network
VIP in Cisco 7000 series or Cisco 7500 series routers	Configure the T3 controller for network loopback	The example that follows is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/0 Router(config-controller)# loopback network
Catalyst RSM/VIP2 in Catalyst 5000 family switches	Configure the T3 controller for remote loopback1	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# loopback remote
Cisco 7200 series and Cisco uBR7200 series routers	Configure the T3 controller for remote loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# loopback remote
VIP in Cisco 7000 series or Cisco 7500 series routers	Configure the T3 controller for remote loopback	The example that follows is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/0 Router(config-controller)# loopback remote

1Remote loopbacks are only available when you use c-bit parity framing.

Local loopback simultaneously loops all channels toward the router and loops the T3 link back toward the network. You can use local loopback to diagnose problems with cables between the T3 controller and the central switching office at the T3 link level.

Configure the T3 Controller for Remote T3 Loopback

equipment [customer | network] loopback

This command 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.

Shutting Down the T3 Controller

You can shut down the T3 controller on the PA-MC-T3 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.

Table 4-9: T3 shutdown command

Platform	Command	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	controller t3, followed by the slot/port (port-adapter-slot-number/interface-port-number)	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: Router(config)# controller t3 1/0 Router(config-controller)# shutdown
Cisco 7200 series and Cisco uBR7200 series routers	controller t3, followed by the slot/port (port-adapter-slot-number/interface- port-number)	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: Router(config)# controller t3 1/0 Router(config-controller)# shutdown
VIP in Cisco 7000 series or Cisco 7500 series routers	controller t3, followed by the slot/port adapter/port (interface-processor-slot-number/ port-adapter-slot-number/interface- port-number)	The example that follows is for a port adapter on a VIP in interface processor slot 1: Router(config)# controller t3 1/0/0 Router(config-controller)# shutdown

Checking the Configuration

After configuring the T1 lines and T3 controller, use the show commands to display the status of the new T1 lines, T3 controller, and the new interface or all interfaces, and use the ping and loopback commands to verify network connectivity. This section includes information on the following subsections:

• Using show Commands to Display New Interface Status

• Enabling Performance Reports

• Displaying Remote Performance Reports

• Using the ping Command to Verify Network Connectivity

• Using loopback Commands

Using show Commands to Display New Interface Status

Table 4-10 demonstrates how you can use show commands to verify that the new interfaces are configured and operating correctly and that the PA-MC-T3 appears in them correctly. Sample displays of the output of selected show commands appear in the sections that follow. For complete command descriptions and examples, refer to the publications listed in the "Related Documentation" section.

Table 4-10: Using show Commands

Command	Function	Example
show version or show hardware	Displays system hardware configuration, the number of each interface type installed, Cisco IOS software version, names and sources of configuration files, and boot images	Router# show version
show controllers	Displays all the current interface processors and their interfaces	Router# show controllers
show diag slot Note The slot argument is not required with Catalyst 5000 family switches.	Displays types of port adapters installed in your system and information about a specific port adapter slot, interface processor slot, or chassis slot	Router# show diag 2
show interfaces serial 0 interface-port-number/t1-line-number:channel- group-number	Displays status information about a specific type of interface (for example, serial) on a Catalyst RSM/VIP2	Router# show interfaces serial 1/0/1:0
show interfaces serial 0 /interface-port-numbert1-line-number:channel- group-number	Displays status information about a specific type of interface (for example, serial) in a Cisco uBR7200 series router	Router# show interfaces serial 1/0/1:0
show interfaces serial interface-processor- slot-number/port-adapter-slot-number/ interface-port-number/t1 line number:channel-group-number	Displays status information about a serial interface on a VIP in a Cisco 7000 series or Cisco 7500 series router	Router# show interfaces serial 1/0/0/1:0
show controllers t3	Displays information for all 28 T1 lines within each T3 port adapter in the router	Router# show controllers t3
show controllers t3 slot/port-adapter/port	Displays all information for the specified T3 line.	Router# show controllers t3
show controllers t3 slot/port-adapter/port brief	Displays a list of configurations for all T1 lines within a PA-MC-T3	The example is for a PA-MC-T3 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t3 1/0/0 brief
show controllers t3 slot/port-adapter/port tabular	Displays a list of configurations and MID data in a tabular format for all T1 lines within a PA-MC-T3	The example is for a PA-MC-T3 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t3 1/0/0 tabular
show controllers t3 slot/port-adapter/port remote performance	Displays a list of performance data from the remote end of a T1 connection	The example is for a PA-MC-T3 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t3 1/0/0 remote performance
show controllers t3 slot/port-adapter/port/t1-line-number brief	Displays a list of configurations for a specific T1 line within a PA-MC-T3	The example is for T1 line 1 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t3 1/0/0/1 brief
show controllers t3 slot/port-adapter/port/t1-line-number tabular	Displays a list of configurations and MID data in a tabular format for all T1 lines within a PA-MC-T3	The example is for T1 line 1 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t2 1/0/0/1 tabular
show controllers t3 slot/port-adapter/port/t1 line number remote performance	Displays a list of performance data from the remote end of a T1 connection	The example is for T1 line 1 in port adapter slot 0 on a VIP installed in interface processor slot 1: Router# show controllers t2 1/0/0/1 remote performance
show protocols	Displays protocols configured for the entire system and for specific interfaces	Router# show protocols
show running-config	Displays the running configuration file	Router# show running-config
show startup-config	Displays the configuration stored in NVRAM	Router# show startup-config

• Using the show version or show hardware Commands

• Using the show diag Command

• Using the show interfaces Command

Using the show version or show hardware Commands

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 (or show hardware) command.

Using the show diag Command

Display the types of port adapters installed in your system (and specific information about each) using the show diag slot command, where slot is the port adapter slot in a Cisco 7200 series or Cisco uBR7200 series router and the interface processor slot in a Cisco 7500 series router with a VIP.

Note The slot argument is not required for the Catalyst 5000 family switches.

Catalyst RSM/VIP2 in Catalyst 5000 Family Switches

Following is an example of the show diag command that shows a PA-MC-T3 on a Catalyst RSM/VIP2:

Router# show diag
Slot 1:
        Physical slot 1, ~physical slot 0xC, logical slot 1, CBus 0
        Microcode Status 0x4
        Master Enable, LED, WCS Loaded
        Board is analyzed
        Pending I/O Status: None
        EEPROM format version 1
        C5IP 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)

Cisco 7200 Series and Cisco uBR7200 Series Routers

Following is an example of the show diag slot command that shows a PA-MC-T3 on a Cisco 7200 or Cisco uBR7200 series router:

Router# show diag 1
Slot 1:
        CT3 single wide port adapter, 1 port
        Port adapter is analyzed 
        Port adapter insertion time 00:03:24 ago
        Hardware revision 1.0           Board revision A0
        Serial number     8526482       Part number    73-3037-01
        Test history      0x0           RMA number     00-00-00
        EEPROM format version 1
        EEPROM contents (hex):
          0x20: 01 A0 01 00 00 82 1A 92 49 0B DD 01 00 00 00 00
          0x30: 05 00 00 00 98 04 27 00 00 00 00 00 00 00 00 00
 

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

VIP2 in Cisco 7000 and Cisco 7500 Series Routers

Following is an example of the show diag slot command that shows a PA-MC-T3 on a VIP2:

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:
                CT3 single wide PA, 1 port
                EEPROM format version 1
                HW rev 1.00, Board revision UNKNOWN
                Serial number: 07503345  Part number: 73-3037-01
 
        PA Bay 1 Information:
                CT3 single wide PA, 1 port
                EEPROM format version 1
                HW rev 1.00, Board revision UNKNOWN
                Serial number: 07503343  Part number: 73-3037-01 

VIP4 in Cisco 7000 and Cisco 7500 Series Routers

Following is an example of the show diag slot command that shows a PA-MC-T3 on a VIP4:

router# show diag 8
Slot 8:
        Physical slot 8, ~physical slot 0x7, logical slot 8, CBus 0
        Microcode Status 0x4
        Master Enable, LED, WCS Loaded
        Board is analyzed 
        Pending I/O Status:None
        EEPROM format version 2
        VIP4 RM7000 controller, HW rev 2.01, board revision UNKNOWN
        Serial number:11500489  Part number:211-18700-71
        Test history:0x02        RMA number:00-00-00
        Flags: unknown flags 0x7F; 7500 compatible
 
        EEPROM contents (hex):
          0x20:02 22 02 01 00 AF 7B C9 D3 49 0C 47 02 00 00 00
          0x30:02 3A 0C FF FF FF FF FF FF FF FF FF FF FF FF FF
 
        Slot database information:
        Flags:0x4      Insertion time:0x3E6C96C (00:01:19 ago)
 
        Controller Memory Size:64 MBytes DRAM, 65536 KBytes SRAM
 
        PA Bay 0 Information:
                CT3 single wide PA, 1 port
                EEPROM format version 1
                HW rev 1.00, Board revision A0
                Serial number:13345087  Part number:73-3037-01 
 
        PA Bay 1 Information:
                T3+ Serial PA, 1 ports
                EEPROM format version 1
                HW rev 1.00, Board revision B0
                Serial number:12374558  Part number:

Using the show interfaces Command

The show interfaces command displays status information (including the physical slot and interface address) for the interfaces you specify. All of the examples that follow specify serial interfaces.

For complete descriptions of interface subcommands and the configuration options available for Catalyst RSM/VIP2, Cisco 7200 series, Cisco uBR7200 series and VIP2 interfaces, refer to the publications listed in the "Related Documentation" section.

VIP2 in Cisco 7000 Series or Cisco 7500 Series Routers

Following is an example of the show interfaces command used with VIP2 in interface processor slot 1, and the PA-MC-T3 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
 

Catalyst RSM/VIP2 in Catalys 5000 Family Switches

Following is an example of the show interfaces command used with a Catalyst RSM/VIP2 with the PA-MC-T3 in port adapter slot 1.

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
 

Cisco 7200 Series and Cisco uBR7200 Series Routers

Following is an example of the show interfaces command used with a Cisco 7200 series or Cisco uBR7200 series router with the PA-MC-T3 in slot 1:

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

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 to 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 1/0/0/1 remote performance.

Examples follow:

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

Router# show controllers t3 1/0/0/1 remote performance 
T3 1/0/0 is up.  Hardware is CT3 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:
     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
.
.
.
(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 on a Catalyst RSM/VIP2 in slot 1:

Router# show controllers t3 1/0/1 remote performance 
T3 1/0 is up.  Hardware is CT3 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:
     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
.
.
.
(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 uBR7200 series:

Router# show controllers t3 1/0 remote performance 
T3 1/0 is up.  Hardware is CT3 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)

Using the ping Command to Verify Network Connectivity

Using the ping command, you can verify that an interface port is functioning properly. This section provides a brief description of this command. Refer to the publications listed in the "Related Documentation" section for detailed command descriptions and examples.

The ping command sends echo requests out to a remote device at an IP address that you specify. After sending an echo request, the system waits a specified time for the remote device to reply. Each echo reply is displayed as an exclamation point(!) on the console terminal; each request 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 a bad connection.

Following is an example of a successful ping command to a remote server with the IP address 10.0.0.10.

Router# ping 10.0.0.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 destination and that the device is active (powered on), and repeat the ping command.

Proceed to the next section, "Using loopback Commands," to finish checking network connctivity.

Using loopback Commands

With the loopback test, you can detect and isolate equipment malfunctions by testing the connection between the PA-MC-T3 interface and a remote device such as a modem or a CSU/DSU. The loopback subcommand places an interface in loopback mode, which enables test packets that are generated from the ping command to loop through a remote device or compact serial cable. If the packets complete the loop, the connection is good. If not, you can isolate a fault to the remote device or compact serial cable in the path of the loopback test.

Note You must configure a clock rate on the port before performing a loopback test. However, if no cable is attached to the port, the port is administratively up, and the port is in loopback mode; you do not have to configure a clock rate on the port before performing a loopback test.

Specify loopback for a T1 line using the following command:

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

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

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

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.

Table 4-11 provides examples of the loopback commands.

The loopback remote command syntax is:

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

Table 4-11: loopback Command Examples

Platform	Command	Purpose	Example
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loopback local	Sets the first T1 line into local loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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
Cisco 7200 series or Cisco uBR7200 series routers	loopback local	Sets the first T1 line into local loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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
VIP in Cisco 7000 series or Cisco 7500 series routers	loopback local1	Sets the first T1 line into local loopback	The example that follows is for a port adapter on a VIP 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
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loopback network line2	Set the first T1 line into network line loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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
Cisco 7200 series or Cisco uBR7200 series routers	loopback network line	Set the first T1 line into network line loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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
VIP in Cisco 7000 series or Cisco 7500 series routers	loopback network line	Set the first T1 line into network line loopback	The example that follows is for a port adapter on a VIP 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
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loopback network payload3	Set the first T1 line into network payload loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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
Cisco 7200 series or Cisco uBR7200 series routers	loopback network payload	Set the first T1 line into network payload loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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
VIP in Cisco 7000 series or Cisco 7500 series routers	loopback network payload	Set the first T1 line into network payload loopback	The example that follows is for a port adapter on a VIP 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
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loopback remote line inband4	Set the first T1 line into remote line inband loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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 remote line inband
Cisco 7200 series or Cisco uBR7200 series routers	loopback remote line inband	Set the first T1 line into remote line inband loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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 remote line inband
VIP in Cisco 7000 series or Cisco 7500 series routers	loopback remote line inband	Set the first T1 line into remote line inband loopback	The example that follows is for a port adapter on a VIP 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 remote line inband
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loop remote line fdl ansi5	Set the first T1 line into remote line FDL ANSI bit loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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 remote line fdl ansi
Cicso 7200 series or Cisco uBR7200 series routers	loop remote line fdl ansi	Set the first T1 line into remote line FDL ANSI bit loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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 remote line fdl ansi
VIP in Cisco 7000 series or Cisco 7500 series routers	loop remote line fdl ansi	Set the first T1 line into remote line FDL ANSI bit loopback	The example that follows is for a port adapter on a VIP 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 remote line fdl ansi
Catalyst RSM/VIP2 in Catalyst 5000 family switches	loopback remote payload fdl ansi6	Set the first T1 line into remote payload FDL ANSI bit loopback	The example that follows is for a port adapter on a Catalyst RSM/VIP2 in slot 1: 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 remote payload fdl ansi
Cicso 7200 series or Cisco uBR7200 series routers	loopback remote payload fdl ansi	Set the first T1 line into remote payload FDL ANSI bit loopback	The example that follows is for a port adapter in slot 1 of the Cisco 7200 series router or the Cisco uBR7200 series: 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 remote payload fdl ansi
VIP in Cisco 7000 series or Cisco 7500 series routers	loopback remote payload fdl ansi	Set the first T1 line into remote payload FDL ANSI bit loopback	The example that follows is for a port adapter on a VIP 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 remote payload fdl ansi

1Local loopback loops the router output data back toward the router at the T1 framer and send an AIS out toward the network. 2Network line loopback loops the data back toward the network (before the T1 framer). 3Network payload loopback loops just the payload data back toward the network at the T1 framer. 4Remote line inband loopback sends a repeating 5-bit inband pattern (of 00001) to the remote end, requesting that it enter into a network line loopback. 5Remote line FDL ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 0000111011111111) to the remote end, requesting that it enter into a network line loopback. 6Remot payload ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 0001010011111111) to the remote end, requesting that it enter into a newtwork payload loopback.

Posted: Fri Apr 28 10:10:37 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.