PA-MC-2T3+ Multichannel T3 Port Adapter Installation and Configuration
Configuring Unchannelized Mode for the PA-MC-2T3+ Multi-Channel T3 Port Adapter
Downloads: This chapterpdf (PDF - 464.0KB) The complete bookPDF (PDF - 2.94MB) | Feedback

Table Of Contents

Configuring Unchannelized mode for the Cisco PA-MC-2T3+

Using the EXEC Command Interpreter

Replacing an Existing Port Adapter

Shutting Down the T3 Controller

Configuring an Unchannelized T3 Link

Configuring the T3 Controller

Selecting a T3 Controller

Setting Unchannelized Mode for the T3 Controller

Setting the Framing Type for the Serial Interface

Specifying the Cable Length for the Serial Interface

Setting the Clock Source for the Serial Interface

Configuring MDL Messages for the Serial Interface

Examples of MDL Message Configuration

Setting the DSU Mode for the Serial Interface

Setting the Bandwidth for the Serial Interface

Setting Scrambling for the Serial Interface

Configuring Loopback Mode for the Serial Interface

Configuring the T3 controller to Enable Loopbacks

Shutting Down the T3 Controller

Configuring a BER Test on the T3 Controller

Sending a BER Test Pattern on the T3 Line

Viewing the Results of a BER Test

Terminating a BER Test

Performing a Basic Serial Interface Configuration

Checking the Configuration

Using show Commands to Verify the New Interface Status

Using the show version or show hardware Commands

Using the show diag Command

Using the show interfaces Command

Using the show controllers Command

Using the ping Command to Verify Network Connectivity

Using loopback Commands to Troubleshoot Network Problems


Configuring Unchannelized mode for the Cisco PA-MC-2T3+


To continue your Cisco PA-MC-2T3+ port adapter installation, you must configure the PA-MC-2T3+ 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

Replacing an Existing Port Adapter

Configuring an Unchannelized T3 Link

Configuring the T3 Controller

Performing a Basic Serial Interface Configuration

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:


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.

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

Router#

Replacing an Existing Port Adapter

Before you remove or replace a port adapter, use the shutdown command to disable the port adapter to prevent anomalies when you remove and reinstall the port adapter. 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 1 Enter the privileged level of the EXEC command interpreter (also called enable mode). (See the "Using the EXEC Command Interpreter" section for instructions.)

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

Shutting Down the T3 Controller

Step 3 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 VIP in interface processor slot 1 of the Cisco 7500 series router:

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

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

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

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

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


Note Both T3 ports of the PA-MC-2T3+ should be shut down before removing the port adapter.


Step 4 Verify that the two T3 ports are now shut down using the
show controller T3
command shown in the following examples:

The following example is for a PA-MC-2T3+ in port adapter slot 6 of a Cisco 7200 series router.

Router(config-controller)# end
Router# show controller T3 6/0
T3 6/0 is administratively down. 

Router# show controller T3 6/1
T3 6/1 is administratively down.

The following example is for a PA-MC-2T3+ in port adapter slot 1 of a VIP in a Cisco 7500 series router.

Router(config-controller)# end
Router# show controller T3 1/1/0
T3 1/1/0 is administratively down. 

Router# show controller T3 1/1/1
T3 1/1/1 is administratively down.

Step 5 Save the shutdown configuration to nonvolatile memory.

Router# copy running-config startup-config

Step 6 Replace the port adapter in the slot. See the "Port Adapter Removal and Installation" section on page 3-4 for more information.

Step 7 Re enable the port adapter by doing the following:

a. Repeat Step 3 to renewable an interface but substitute the no shutdown command for the shutdown command.

b. Repeat Step 4 to verify that the interfaces are in the correct state and no longer shut down. Use the
show controller T3 command.

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


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

Configuring an Unchannelized 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.

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

Setting Unchannelized Mode for the T3 Controller

Setting the Framing Type for the Serial Interface

Specifying the Cable Length for the Serial Interface

Setting the Clock Source for the Serial Interface

Configuring MDL Messages for the Serial Interface

Examples of MDL Message Configuration

Configuring Loopback Mode for the Serial Interface

Configuring the T3 controller to Enable Loopbacks

Shutting Down the T3 Controller

Configuring a BER Test on the T3 Controller

Sending a BER Test Pattern on the T3 Line

Viewing the Results of a BER Test

Terminating a BER Test

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 interface-processor-slot/port-adapter-slot/T3-port for Cisco 7500 series router

controller T3 chassis-slot/T3-port for Cisco 7200 series router

controller T3 chassis-slot/T3-port for Cisco 7301 series router

controller T3 chassis-slot/T3-port for Cisco 7401ASR router

Examples of selecting the T3 controller follow:

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 in slot 1 of the Cisco 7200 series routers:

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

Setting Unchannelized Mode for the T3 Controller

To configure the T3 for unchannelized mode, use the no channelized command. After the full-rate T3 interface is configured, use the dsu bandwidth command to create a subrate T3 interface. The following example configures a subrate T3 interface on a PA-MC-2T3+ in port adapter slot 1 of a Cisco 7200 series router.

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller t3 1/0
Router (config)# no channelized
Router (config-controller)# exit
Router (config)# interface serial 1/0
Router (config-if)# dsu bandwidth 16000
Router (config-if)# encapsulation frame-relay
Router (config-if)# ip address 10.10.10.10 255.255.255.255
Router (config-if)# no shutdown

The following example is for a PA-MC-2T3+ in port adapter slot 1 of a VIP in a Cisco 7500 series router.

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller T3 1/1/0
Router (config)# no channelized
Change to subrate mode will cause cbus complex reset. Proceed? [yes/no]: Y
Router(config)# interface serial 1/1/0
Router(config-if)# encapsulation ppp
Router(config-if)# ip address 10.10.10.10.10 255.255.255.255
Router(config)# no shutdown

When the PA-MC-2T3+ is configured for unchannelized T3 mode, its default MTU size is set to 4470 for compatibility with other T3 equipment and port adapters.


Caution The change in MTU sizes will cause a memory recarve and cbus complex to occur, disrupting all traffic on the router for several minutes. (This occurs only on Cisco 7500 series routers.)

The following message will be displayed when switching from channelized to unchannelized mode on Cisco 7500 series routers:

Change to subrate mode will cause cbus complex reset. Proceed? [yes/no]: Y

Type Y for `yes' at the end of the warning. At the prompt, type ^Z to exit. This will allow you to exit configuration mode and enter unchannelized mode.

Setting the T3 port to unchannelized mode creates a serial interface which the following commands may be used to configure. Use the interface serial command to select the serial interface.


router# configure terminal
router# interface serial 1/0/1
router(config-if)#

Setting the Framing Type for the Serial Interface

In interface configuration mode, specify T3 framing by entering the {c-bit | m13} configuration subcommand, as in the following example:

router(config-if)# framing {c-bit | m13}

where:

c-bit—C-bit parity DS3 framing

m13—M13 Multiplex DS3 framing

Use the no form of this command to return to the default, C-bit framing.

Specifying the Cable Length for the Serial Interface

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

cablelength feet

where:

feet is a numeral from 0 to 450.

The default value is 10 feet.

An example follows:

Router(config-if)# cablelength 40

Note For the cablelength feet command, user-specified T3 cable lengths are structured into ranges as follows: 0-49 and 50-450 to represent short and long cables.

If the numerical value entered by the user falls within the lower range, then the PA-MC-2T3+ T3 port is set for short cable output levels. If the value falls into higher range, the long cable output levels will be 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 or 200, the 50-450 range applies in both cases. 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. It is recommended that the actual cable length be entered to ensure future compatibility.


Setting the Clock Source for the Serial Interface

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

clock source {line | internal}

Where:

line—selects a network clock source

internal—selects an internal clock source

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 VIP in interface processor slot 1:

Router(config)# interface serial 1/0/0
Router(config-if)# clock source line

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

Router(config)# interface serial 1/0
Router(config-if)# 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 VIP in interface processor slot 1:

Router(config)# interface serial 1/0/0
Router(config-if)# clock source internal

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

Router(config)# interface serial 1/0
Router(config-if)# clock source internal

Configuring MDL Messages for the Serial Interface

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 Serial Interface" section.)


To configure MDL messages, use the interface 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 interface 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)# interface serial 1/0/0
Router(config-if)# 

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

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

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-if)# mdl transmit idle-signal

Enable the MDL test signal message transmission as follows:

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

Enter the equipment identification code as follows:

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

Enter the location identification code as follows:

Router(config-if)# mdl string lic tst network

Enter the frame identification code as follows:

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

Enter the unit identification code as follows:

Router(config-if)# mdl string unit abc

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

Router(config-if)# mdl string pfi string

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

Router(config-if)# mdl string port string

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

Router(config-if)# mdl string generator string

Setting the DSU Mode for the Serial Interface

In interface configuration mode, define the DSU interoperability mode by entering the dsu mode [0 | 1 | 2 | 3 | 4] configuration subcommand, as in the following example:

router(config-if)# dsu mode 1

Use the no form of this command to return to the default, 0.

The local DSU mode must match the remote DSU or T3 port configuration. For example, if an ADC Kentrox DSU is at the remote end of the T3 link, then the local T3 port must be configured for mode 1.

You need to know what type of DSU is at the remote T3 end to find out if it interoperates with the PA-MC-2T3+. Specify mode 0 for connection from a PA-MC-2T3+ to another PA-MC-2T3+ or a Digital Link DSU (DL3100). Specify mode 1 for connection from a PA-MC-2T3+ to a Kentrox DSU. Specify mode 2 for connection from a PA-MC-2T3+ to a Larscom DSU. See Table 4-1 for a list of DSUs and their corresponding bandwidth range.

Also see the "T3 Specifications" section on page 1-3 for information regarding DSU feature compatibilities.

Table 4-1

Mode
DSU
Bandwidth Range

0

PA-MC-2T3+, PA-2T3+

Other Cisco subrate T3 equipment

22-44210 kbps

0

Digital Link 3100

300-44210 kbps

1

ADC Kentrox T3/E3 IDSU

1500-35000, 44210 kbps

2

Larscom Access T45

3100-44210 kbps

3

Adtran T3SU 300

75-44210 kbps

4

Verilink HDM 2182

1500-44210 kbps


DSU Mode Bandwidth Ranges


Note If the far end DSU has more than one DTE (HSSI) port, connect to and configure only DTE#1. See Caution below for Verilink DSUs.



Caution Always connect to and configure HSSI port B on the Verilink HDM2182. Port A is not supported by the PA-MC-2T3+.


Caution The PA-MC-2T3+ does not support the Kentrox DSU bandwidth setting of 1.0 mbps. The Kentrox DSU speed must be set to 1.5 mbps or greater.


Caution For all DSU modes, the DSU must be configured for the same transmit and receive speeds. Asymmetrical transmit and receive speeds are not supported.

Setting the Bandwidth for the Serial Interface

In interface configuration mode, set the bandwidth to be used by the serial interface on the T3 link by entering the dsu bandwidth bandwidth configuration subcommand, as in the following example:

Router(config-if)# dsu bandwidth 16000

The allowable bandwidth range is 1 to 44210 kbps. Use the no form of this command to return to the default, 44210.

The local DSU bandwidth value must match the remote DSU or T3 port bandwidth exactly. For example, if you set the DSU bandwidth to 16000 on the local port, you must do the same on the remote DSU or T3 port.

Setting Scrambling for the Serial Interface

In interface configuration mode, enable serial interface scrambling by entering the scramble configuration subcommand, as in the following example:

router(config-if)# scramble

Use the no form of this command to restore the default value, disabled.

The local port configuration must match the remote DSU or T3 port configuration. For example, if you enable scrambling on the local port, you must do the same on the remote DSU or T3 port.

Configuring Loopback Mode for the Serial Interface

With loopbacks, you can detect and isolate equipment malfunctions by testing the connection between the PA-MC-2T3+ interface and a remote device such as a CSU/DSU. Remote loopback sends a command to loop the T3 line at the far end. It can be used to diagnose problems with cables from the port adapter to the switching office. Network loopback loops the PA-MC-2T3+ T3 port back to the network, allowing the remote end to test the connection to the PA-MC-2T3+.

Local loopback loops the PA-MC-2T3+ T3 port back to itself allowing it to be tested in isolation from the T3 cables and remote T3 equipment.

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 and cables. If the packets complete the loop, the connection is good.

Table 4-2 provides examples of the loopback {local | network {line | payload} | remote {line | payload}2 command. You can configure the serial interface for loopback modes using the interface command:

loopback [local | network | remote]

The default is no loopback.

To return the serial interface to its default unlooped condition, use the no form of the command.

Table 4-2 Using loopback Commands

loopback local

Sets the interface into local loopback mode. Local loopback loops the router output data back toward the router at the framer.

Router(config)# interface serial 
10/0/0
router(config-if)# loopback local	

loopback network line

Sets the interface into network line loopback mode. Network line loopback loops the data back toward the network (before the framer).

Router(config)# interface serial 
10/0/0
router(config-if)# loopback network 
line

loopback network payload

Sets the interface into network payload loopback mode. Network payload loopback loops just the payload data back toward the network at the T3 framer.

Router(config)# interface serial 
10/0/0
router(config-if)# loopback network 
payload

loopback remote1

Sends a command to the remote T3 device instructing it to loop itself back toward the network (before the framer at the remote T3 device).

Router(config)# interface serial 
10/0/0
router(config-if)# loopback remote

loopback remote line2

Sends a command to the remote Kentrox to loop itself back toward the network before the framer.

Router(config)# interface serial 
10/0/0
router(config-if)# loopback remote 
line

loopback remote payload2

Sends a command to the remote Kentrox DSU to loop only the payload after the framer back toward the network.

Router(config)# interface serial 
10/0/0
router(config-if)# loopback remote 
payload

1 Remote loopback mode works with C-bit framing only. The other loopback modes listed above work with C-bit and M13 framing. Refer to the "Setting the Framing Type for the Serial Interface" section for information on configuring C-bit framing.

2 These loopback commands are only available when the DSU mode is set to 1, Kentrox mode.


Configuring the T3 controller to Enable Loopbacks

The PA-MC-2T3+ can be configured to respond to or to ignore remote T3 loopback requests sent to it from the far end T3 equipment. 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

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

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


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 VIP 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 routers:

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

Configuring a BER Test on the T3 Controller

Bit error rate test (BERT) circuitry is built into the PA-MC-2T3+. With BER tests, you can test cable and signal problems in the field.

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 polynomial based 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 list of the available test patterns follows:

Pseudorandom test patterns:

2^15 (per CCITT/ITU O.151)

2^20 (per CCITT/ITU O.151 non-QRSS)

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.

When running a BER test, your system expects to receive the same pattern that it is transmitting. To accomplish 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 the T3 Line

You can send a BERT pattern on the T3 line with the bert command in controller configuration mode.

bert pattern pattern interval time

where:

pattern is:

0s, repetitive test pattern of all zeros (as 00000...)

1s, repetitive test pattern of all ones (as 11111...)

2^15, pseudorandom O.151 test pattern (32,768 bits long)

2^20, pseudorandom O.151 non-QRSS 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)

time is 1-14400 minutes.

Examples follow:

Send a BERT pseudorandom pattern of 2^23 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)# bert pattern 2^23 interval 5

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

Router(config)# controller T3 1/0
Router(config-controller)# bert pattern 2^23 interval 5

Send a repetitive pattern of all ones for 14400 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)# bert pattern 1s interval 14400

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

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

Note You can terminate a BER test during the specified test period with the no 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/t3-port for Cisco 7500 series routers

show controllers T3 slot/t3-port for Cisco 7200 series routers

show controllers T3 slot/t3-port for Cisco 7401ASR routers

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

After you terminate the test using the no bert command

After the test runs completely

Anytime during the test (in real time)

Examples follow:

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

Router# show controller T3 1/0/0

T3 1/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: 1.4.4
  FREEDM version: 1, reset 0
  Applique type is Subrate T3
  No alarms detected.
  MDL transmission is disabled
    
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
  Data in current interval (9 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
     9 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 1:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 2:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 3:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 4:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 5:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 6:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 7:
     1 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 1 Severely Err Framing Secs
     0 Unavailable Secs, 1 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Total Data (last 7 15 minute intervals):
     1 Line Code Violations, 0 P-bit Coding Violation,
     0 C-bit Coding Violation, 0 P-bit Err Secs,
     0 P-bit Severely Err Secs, 1 Severely Err Framing Secs,
     0 Unavailable Secs, 1 Line Errored Secs,
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
BERT test result (done)
     Test Pattern : All 1's, Status : Not Sync, Sync Detected : 0
     Interval : 14400 minute(s), Time Remain : 14400 minute(s)
     Bit Errors (since BERT started): 0 bits, 
     Bits Received (since BERT started): 0 Kbits
     Bit Errors (since last sync): 0 bits
     Bits Received (since last sync): 0 Kbits

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

Router# show controllers T3 5/0

T3 5/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 : 1.4.4
  FREEDM version: 1, reset 0
  Applique type is Subrate T3
  No alarms detected.
  MDL transmission is disabled
    
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
  Rx throttle total 0, equipment customer loopback
  Data in current interval (63 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
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 1:
     4905 Line Code Violations, 4562 P-bit Coding Violation
     5167 C-bit Coding Violation, 2 P-bit Err Secs
     1 P-bit Severely Err Secs, 3 Severely Err Framing Secs
     58 Unavailable Secs, 1 Line Errored Secs
     3 C-bit Errored Secs, 3 C-bit Severely Errored Secs
  Data in Interval 2:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
(additional display text ommitted)
BERT test result (running)
     Test Pattern : All 1's, Status : Sync, Sync Detected : 1
     Interval : 14400 minute(s), Time Remain : 14400 minute(s)
     Bit Errors (since BERT started): 0 bits, 
     Bits Received (since BERT started): 92 Mbits
     Bit Errors (since last sync): 0 bits
     Bits Received (since last sync): 92 Mbits

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^15, Status : Sync, Sync Detected : 1

This line indicates the test pattern you selected for the test (2^15), 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. Bits and errors are only counted when the test status is "sync".


Terminating a BER Test

You can terminate a BER test with the controller command:

no bert

Examples follow:

Terminate the BER test running on T3 0.

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 bert

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

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

To check your configurations using show commands, proceed to the "Checking the Configuration" section; otherwise, proceed to the following section to perform a basic interface configuration.

Performing a Basic Serial Interface Configuration

Following are instructions for a basic configuration: enabling an interface and specifying IP routing. 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> 


Step 1 Enter configuration mode and specify that the console terminal is the source of the configuration subcommands, as follows:

Router# configuration 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. See "Port Adapter Slot Locations on the Supported Platforms" section on page 1-5 and "Identifying Interface Addresses" section on page 1-11.

This example is for the serial interface of T3 port 0 in port adapter slot 6.

Router(config)# interface serial 6/0
Router(config-if)#

This example is for the serial interface of T3 port 0 of a port adapter in port adapter slot 1 of a VIP in interface processor slot 2.

Router(config)# interface serial 2/1/0
Router(config-if)#

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 subcommands required to enable routing protocols and set the interface characteristics.

Step 5 Re enable the interfaces using the no shutdown command. (See the "Replacing an Existing Port Adapter" 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 interpreter 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.

Checking the Configuration

After configuring the new interface, use the show commands to display the status of the new interface or all interfaces, and use the ping and loopback commands to check connectivity. This section includes the following subsections:

Using show Commands to Verify the New Interface Status

Using the ping Command to Verify Network Connectivity

Using loopback Commands to Troubleshoot Network Problems

Using show Commands to Verify the New Interface Status

Table 4-3 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the PA-MC-2T3+ 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 on page viii.


Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.


Table 4-3 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

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

For Cisco 7200 series routers:
show interfaces serial port-adapter/t3-port

Displays status information about a specific type of interface

Router# show interfaces serial 3/1/

For a Cisco 7304 PCI Port Adapter Carrier Card in a Cisco 7304 router:
show interfaces serial port-adapter/t3-port

Displays status information about a specific type of interface

Router# show interfaces serial 3/1

For Cisco 7301 routers:
show interfaces serial port-adapter/t3-port

Displays status information about a specific type of interface

Router# show interfaces serial 3/1

For Cisco 7401ASR routers:
show interfaces serial port-adapter/t3-port

Displays status information about a specific type of interface

Router# show interfaces serial 3/1

For Cisco 7500 series routers:
show interfaces serial slot/port-adapter/t3-port

Displays status information about a specific type of interface (for example, serial) on a VIP in a Cisco 7000 series or Cisco 7500 series router

Router# show interfaces serial 3/1/0

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

If an interface is shut down and you configured it as up, or if the display indicates that the hardware is not functioning properly, ensure that the interface is properly connected and terminated. If you still have problems bringing up the interface, contact a service representative for assistance. This section includes the following subsections:

Using the show version or show hardware Commands

Using the show diag Command

Using the show interfaces Command

Using the show controllers Command

Choose the subsection appropriate for your system. Proceed to the "Using the ping Command to Verify Network Connectivity" section when you have finished using the show commands.

Using the show version or show hardware Commands

Display the configuration of the 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, using the show version (or show hardware) command. Following are examples for some of the platforms.


Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.


Cisco 7200 Series Routers

Following is an example of the show version command from a Cisco 7200 series router with the PA-MC-2T3+:

Router# show version
Cisco Internetwork Operating System Software 
IOS (tm) 7200 Software (C7200-JS-M), Released Version 12.0
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Fri 02-Jun-00 04:19 by biff
Image text-base: 0x600088F8, data-base: 0x61274000

ROM: System Bootstrap, Version 11.1(10) [dschwart 10], RELEASE SOFTWARE (fc1)
BOOTFLASH: 7200 Software (C7200-BOOT-M), Version 11.1(25.1)CC, EARLY DEPLOYMENT 

ranger uptime is 5 weeks, 14 hours, 32 minutes
System returned to ROM by reload

cisco 7206 (NPE150) processor with 90112K/8192K bytes of memory.
R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache
6 slot midplane, Version 1.3

Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
4 Ethernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
1 FDDI network interface(s)
2 Channelized T3 port(s)
125K bytes of non-volatile configuration memory.
1024K bytes of packet SRAM memory.

4096K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0

Cisco 7301 Routers

Router# show version
Cisco Internetwork Operating System Software 
IOS (tm) 7301 Software (C7300-JS-M), Experimental Version 12.2(20020904:004736) [biff 107]
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 09-Sep-02 18:02 by biff
Image text-base:0x600088F8, data-base:0x61A94000

ROM:System Bootstrap, Version 12.2(20020730:200705) [biff-TAZ2_QA_RELEASE_16B 101], 
DEVELOPMENT SOFTWARE
BOOTLDR:7301 Software (C7301-BOOT-M), Experimental Version 12.2(20020813:014224) 
[biff-TAZ2_QA_RELEASE_17B 101]

7301p2b uptime is 0 minutes
System returned to ROM by reload at 00:01:51 UTC Sat Jan 1 2000
System image file is "tftp://10.1.8.11/tazii/images/c7301-js-mz"

cisco 7301 (NPE-G1) processor (revision A) with 491520K/32768K bytes of memory.
Processor board ID 0
BCM1250 CPU at 700Mhz, Implementation 1, Rev 0.2, 512KB L2 Cache
1 slot midplane, Version 2.0

Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
3 Gigabit Ethernet/IEEE 802.3 interface(s)
509K bytes of non-volatile configuration memory.
          
62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
32768K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x102

Cisco 7401ASR Routers

Following is an example of the show version command from a Cisco 7401ASR router with the PA-MC-2T3+:

Router# show version
Cisco Internetwork Operating System Software 
IOS (tm) 7401ASR Software (C7401ASR)0
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Fri 02-Jun-00 04:19 by biff
Image text-base: 0x600088F8, data-base: 0x61274000

ROM: System Bootstrap, Version 11.1(10) [dschwart 10], RELEASE SOFTWARE (fc1)
BOOTFLASH: 7401ASR Software (C7401ASR-BOOT-M)

ranger uptime is 5 weeks, 14 hours, 32 minutes
System returned to ROM by reload

cisco 7401ASR processor with 90112K/8192K bytes of memory.
R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache
6 slot midplane, Version 1.3

Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
4 Ethernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
1 FDDI network interface(s)
2 Channelized T3 port(s)
125K bytes of non-volatile configuration memory.
1024K bytes of packet SRAM memory.

4096K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0

VIP in Cisco 7000 Series and Cisco 7500 Series Routers

Following is an example of the show version command from a Cisco 7500 series router with the PA-MC-2T3+:

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)
 [biff-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

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 7100 series router, Cisco 7200 series router, Cisco 7301 router, and Cisco 7401ASR router and the interface processor slot in a Cisco 7000 series router or Cisco 7500 series router with a VIP. In the Cisco 7304 PCI Port Adapter Carrier Card in a Cisco 7304 router, slot is the router module-slot-number. The following examples show output for some of the supported platforms.


Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.


Cisco 7200 Series Routers

Following is an example of the show diag slot command that shows a PA-MC-2T3+ in port adapter slot 5 of a Cisco 7200 series router:

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

Router# show diag 5

Slot 5:
        2CT3+ single wide Port adapter, 2 ports
        Port adapter is analyzed 
        Port adapter insertion time 16:03:05 ago
        EEPROM contents at hardware discovery:
        Hardware revision 1.00          Board revision A0
        Serial number     14338549      Part number    73-3388-03
        Test history      0x0           RMA number     00-00-00
        EEPROM format version 1
        EEPROM contents (hex):
          0x20: 01 B7 00 00 00 DA C9 F5 00 00 00 00 00 00 00 00
          0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Cisco 7301 Routers


Note Input/output data for the console port, auxiliary port, Gigabit Ethernet ports, and CompactFlash Disk are listed in the output of the show c7300 command, rather than in the output of the show diag command. Use the show diag command for port adapter information.


Router# sh diag 

Slot 1:
        POS Single Width, Multi Mode Port adapter, 1 port 
        Port adapter is analyzed 
        Port adapter insertion time 01:38:29 ago 
        EEPROM contents at hardware discovery:
        Hardware revision 2.2           Board revision A0 
        Serial number     28672741      Part number    73-3192-06 
        FRU Part Number:PA-POS-OC3MM= 

        Test history      0x0           RMA number     00-00-00 
        EEPROM format version 1 
        EEPROM contents (hex):
          0x20:01 96 02 02 01 B5 82 E5 49 0C 78 06 00 00 00 00 
          0x30:50 00 00 00 02 08 19 00 00 00 FF FF FF FF FF FF 

Cisco 7401ASR Routers

Following is an example of the show diag slot command that shows a PA-MC-2T3+ in port adapter slot 5 of a Cisco 7401ASR router:

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

Router# show diag 5

Slot 1:
        2CT3+ single wide Port adapter, 2 ports
        Port adapter is analyzed 
        Port adapter insertion time 16:03:05 ago
        EEPROM contents at hardware discovery:
        Hardware revision 1.00          Board revision A0
        Serial number     14338549      Part number    73-3388-03
        Test history      0x0           RMA number     00-00-00
        EEPROM format version 1
        EEPROM contents (hex):
          0x20: 01 B7 00 00 00 DA C9 F5 00 00 00 00 00 00 00 00
          0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

VIP in Cisco 7000 Series and Cisco 7500 Series Routers

Following is an example of the show diag slot command that shows a PA-MC-2T3+ in port adapter
slot 0 on a VIP in interface processor slot 1:


Router# show diag 1
Slot 1:
        Physical slot 1, ~physical slot 0xE, 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
        VIP2 R5K controller, HW rev 2.02, board revision C0
        Serial number: 12720200  Part number: 73-2167-05
        Test history: 0x00        RMA number: 00-00-00
        Flags: cisco 7000 board; 7500 compatible

        EEPROM contents (hex):
          0x20: 01 1E 02 02 00 C2 18 48 49 08 77 05 00 00 00 00
          0x30: 60 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00

        Slot database information:
        Flags: 0x4      Insertion time: 0x165C (16:04:59 ago)

        Controller Memory Size: 32 MBytes DRAM, 4096 KBytes SRAM

        PA Bay 0 Information:
                2CT3+ single wide PA, 2 ports
                EEPROM format version 1
                HW rev 1.00, Board revision A0
                Serial number: 14062933  Part number: 73-3388-03 

        PA Bay 1 Information:
                Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
                EEPROM format version 1
                HW rev 1.00, Board revision A0
                Serial number: 06641389  Part number: 73-1688-04 

        --Boot log begin--

Cisco Internetwork Operating System Software 
IOS (tm) VIP Software (SVIP-DW-M), Experimental Version 12.1(20000630:023314) []
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Tue 11-Jul-00 13:15 by biff
Image text-base: 0x60010910, data-base: 0x60320000


        --Boot log end--

Using the show interfaces Command

The show interfaces serial command displays status information (including the physical slot and interface address) for the interfaces you specify. Following are examples for some of the supported platforms; the examples specify serial interfaces.

For complete descriptions of interface subcommands and the configuration options available for Cisco 7200, Cisco 7401ASR and VIP interfaces, refer to the publications listed in the "Related Documentation" section on page viii.


Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.


Cisco 7200 Series Routers

Following is an example of the show interfaces serial command for Cisco 7200 series routers. In this example, the port adapter is in slot 5 of the Cisco 7200 series router:

Router# show interfaces serial 5/0

Serial5/0 is up, line protocol is down 
  Hardware is PA-MC-2T3+
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, 
     reliability 128/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5823 packets output, 140669 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
 DSU mode 0, bandwidth 44210, scramble 0

Cisco 7301 Router

Following is an example of the show interfaces command for Cisco 7301 routers. Most of the status information for each interface is omitted. (Interfaces are administratively shut down until you enable them.)

outer# show interfaces
GigabitEthernet0/0 is up, line protocol is up 
  Hardware is BCM1250 Internal MAC, address is 0005.dd2c.7c1b (bia 0005.dd2c.7c1b)
  Internet address is 10.1.3.153/16
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 100Mb/s, media type is RJ45
  output flow-control is off, input flow-control is off
  ARP type:ARPA, ARP Timeout 04:00:00
  Last input 00:00:01, output 00:00:07, output hang never
  Last clearing of "show interface" counters 19:00:50
  Input queue:0/75/63658/0 (size/max/drops/flushes); Total output drops:0

(display text omitted)

GigabitEthernet0/1 is up, line protocol is up 
  Hardware is BCM1250 Internal MAC, address is 0005.dd2c.7c1a (bia 0005.dd2c.7c1a)
  Internet address is 192.18.1.1/24
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 5/255, rxload 6/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, link type is autonegotiation, media type is SX
  output flow-control is off, input flow-control is off
  ARP type:ARPA, ARP Timeout 04:00:00
  Last input 18:56:46, output 00:00:09, output hang never
  Last clearing of "show interface" counters 19:00:52
  Input queue:0/75/16176489/0 (size/max/drops/flushes); Total output drops:0

(display text omitted)

GigabitEthernet0/2 is up, line protocol is up 
  Hardware is BCM1250 Internal MAC, address is 0005.dd2c.7c19 (bia 0005.dd2c.7c19)
  Internet address is 1.1.1.1/24
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 5/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, link type is autonegotiation, media type is SX
  output flow-control is off, input flow-control is off
  ARP type:ARPA, ARP Timeout 04:00:00
  Last input 00:04:42, output 00:00:01, output hang never
  Last clearing of "show interface" counters 19:00:54
  Input queue:0/75/22087/0 (size/max/drops/flushes); Total output drops:0

(display text omitted)

Cisco 7401ASR Routers

Following is an example of the show interfaces serial command for Cisco 7401ASR routers. In this example, the port adapter is in slot 1 of the Cisco 7401ASR router:

Router# show interfaces serial 1/0

Serial1/0 is up, line protocol is down 
  Hardware is PA-MC-2T3+
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, 
     reliability 128/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5823 packets output, 140669 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
 DSU mode 0, bandwidth 44210, scramble 0

VIP in Cisco 7000 Series or Cisco 7500 Series Routers

Following is an example of the show interfaces serial command used with a VIP in interface processor slot 1 and a PA-MC-2T3+ in port adapter slot 0.

Router# show interfaces serial 1/0/0

Serial1/0/0 is up, line protocol is up 
  Hardware is cyBus 2CT3+ Serial
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input 00:00:09, output 00:00:07, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 4 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
     4 packets input, 402 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 1 abort
     5 packets output, 1008 bytes, 0 underruns
     0 output errors, 0 applique, 1 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions
 DSU mode 0, bandwidth 44210, scramble 0

Using the show controllers Command

You can display information for the T3 controller within a PA-MC-2T3+ in Cisco 7200 series, Cisco 7301 routers, and Cisco 7401ASR routers with the command:

show controllers t3 port-adapter/t3-port [brief | tabular]

where:

brief displays a list of configurations only.

tabular displays a list of configurations and MIB data in a tabular format.


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



Note You can use these show controllers t3 commands for Cisco 7500 series routers in which the PA-MC-2T3+ is supported. The syntax is as follows:

— show controllers t3 slot/port-adapter/t3-port brief

— show controllers t3 slot/port-adapter/t3-port tabular


The following examples show command output display information for a PA-MC-2T3+ in port adapter slot 0 on a VIP installed in interface processor slot 1. Examples for Cisco 7200 series and Cisco 7401ASR routers are not shown.

show controllers t3 1/0/0 brief

router# show controllers t3 1/0/0 brief
T3 1/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: 1.4.4
  FREEDM version: 1, reset 0
  Applique type is Subrate T3
  No alarms detected.
  MDL transmission is disabled
    
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line
  Rx throttle total 0, equipment customer loopback

show controllers t3 1/0/0 tabular

router# show controllers t3 1/0/0 tabular
T3 1/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: 1.4.4
  FREEDM version: 1, reset 0
  Applique type is Subrate T3
  No alarms detected.
  MDL transmission is disabled
    
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line
  Rx throttle total 0, equipment customer loopback
  INTERVAL      LCV   PCV   CCV   PES  PSES  SEFS   UAS   LES   CES  CSES
  08:23-08:26     1     0     0     0     0     1     0     1     0     0
  08:08-08:23     0     0     0     0     0     0     0     0     0     0
  07:53-08:08     0     0     0     0     0     0     0     0     0     0
  07:38-07:53     0     0     0     0     0     0     0     0     0     0
  07:23-07:38     0     0     0     0     0     0     0     0     0     0
  07:08-07:23     0     0     0     0     0     0     0     0     0     0
  06:53-07:08     0     0     0     0     0     0     0     0     0     0
  06:38-06:53     0     0     0     0     0     0     0     0     0     0
  06:23-06:38     0     0     0     0     0     0     0     0     0     0
  06:08-06:23     0     0     0     0     0     0     0     0     0     0
  05:53-06:08     0     0     0     0     0     0     0     0     0     0
  05:38-05:53     0     0     0     0     0     0     0     0     0     0
  05:23-05:38     0     0     0     0     0     0     0     0     0     0
  05:08-05:23     0     0     0     0     0     0     0     0     0     0
  04:53-05:08     0     0     0     0     0     0     0     0     0     0
  04:38-04:53     0     0     0     0     0     0     0     0     0     0
  04:23-04:38     0     0     0     0     0     0     0     0     0     0
  04:08-04:23     0     0     0     0     0     0     0     0     0     0
  03:53-04:08     0     0     0     0     0     0     0     0     0     0
  03:38-03:53     0     0     0     0     0     0     0     0     0     0
  03:23-03:38     0     0     0     0     0     0     0     0     0     0
  03:08-03:23     0     0     0     0     0     0     0     0     0     0
  02:53-03:08     0     0     0     0     0     0     0     0     0     0
  02:38-02:53     0     0     0     0     0     0     0     0     0     0
  02:23-02:38     0     0     0     0     0     0     0     0     0     0
  02:08-02:23     0     0     0     0     0     0     0     0     0     0
  01:53-02:08     0     0     0     0     0     0     0     0     0     0
  01:38-01:53     0     0     0     0     0     0     0     0     0     0
  01:23-01:38     0     0     0     0     0     0     0     0     0     0
  01:08-01:23     0     0     0     0     0     0     0     0     0     0
  00:53-01:08     0     0     0     0     0     0     0     0     0     0
  00:38-00:53     0     0     0     0     0     0     0     0     0     0
  00:23-00:38     0     0     0     0     0     0     0     0     0     0
  00:08-00:23     0     0     0     0     0     0     0     0     0     0
  23:53-00:08     0     0     0     0     0     0     0     0     0     0
  23:38-23:53     0     0     0     0     0     0     0     0     0     0
  23:23-23:38     0     0     0     0     0     0     0     0     0     0
  23:08-23:23     0     0     0     0     0     0     0     0     0     0
  22:53-23:08     0     0     0     0     0     0     0     0     0     0
  22:38-22:53     0     0     0     0     0     0     0     0     0     0
  22:23-22:38     0     0     0     0     0     0     0     0     0     0
  22:08-22:23     0     0     0     0     0     0     0     0     0     0
  21:53-22:08     0     0     0     0     0     0     0     0     0     0
  21:38-21:53     0     0     0     0     0     0     0     0     0     0
  21:23-21:38     0     0     0     0     0     0     0     0     0     0
  21:08-21:23     0     0     0     0     0     0     0     0     0     0
  20:53-21:08     0     0     0     0     0     0     0     0     0     0
  20:38-20:53     0     0     0     0     0     0     0     0     0     0
  20:23-20:38     0     0     0     0     0     0     0     0     0     0
  20:08-20:23     0     0     0     0     0     0     0     0     0     0
  19:53-20:08     0     0     0     0     0     0     0     0     0     0
  19:38-19:53     0     0     0     0     0     0     0     0     0     0
  19:23-19:38     0     0     0     0     0     0     0     0     0     0
  19:08-19:23     0     0     0     0     0     0     0     0     0     0
  18:53-19:08     0     0     0     0     0     0     0     0     0     0
  18:38-18:53     0     0     0     0     0     0     0     0     0     0
  18:23-18:38     0     0     0     0     0     0     0     0     0     0
  18:08-18:23     0     0     0     0     0     0     0     0     0     0
  17:53-18:08     0     0     0     0     0     0     0     0     0     0
  17:38-17:53     0     0     0     0     0     0     0     0     0     0
  17:23-17:38     0     0     0     0     0     0     0     0     0     0
  17:08-17:23     0     0     0     0     0     0     0     0     0     0
  16:53-17:08     0     0     0     0     0     0     0     0     0     0
  16:38-16:53     0     0     0     0     0     0     0     0     0     0
  16:23-16:38     0     0     0     0     0     0     0     0     0     0
  16:08-16:23     1     0     0     0     0     1     0     1     0     0
  Total           2     0     0     0     0     2     0     2     0     0

show controllers t3 1/0/0

router # show controllers t3 1/0/0

T3 1/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: 1.4.4
  FREEDM version: 1, reset 0
  Applique type is Subrate T3
  No alarms detected.
  MDL transmission is disabled
    
  FEAC code received: No code is being received
  Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line
  Rx throttle total 0, equipment customer loopback
  Data in current interval (364 seconds elapsed):
     1 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 1 Severely Err Framing Secs
     0 Unavailable Secs, 1 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 1:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 2:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 3:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Data in Interval 4:
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
(additional displayed text not shown)

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

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 on page viii for detailed command descriptions and examples.

The ping command sends echo request packets 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 a bad connection.

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

Router# ping 10.0.0.10 <Return>
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 10.0.0.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 Troubleshoot Network Problems," to finish checking network connectivity.

Using loopback Commands to Troubleshoot Network Problems

If you have difficulty with the PA-MC-2T3+ configuration or installation, you can troubleshoot the port adapter using the loopback command. Refer to the "Configuring Loopback Mode for the Serial Interface" section for instructions on setting loopbacks.

If the ping command to the remote IP address failed, then use loopbacks to troubleshoot the T3 connection using the following steps:


Step 1 Use the show controller T3 and show interface serial commands to confirm that the T3 controller, serial interface, and line protocol are up.

Step 2 Place the serial interface of the PA-MC-2T3+ in local loopback using the loop local command.

Step 3 Repeat the ping command using the IP address of the local serial interface. Using the previous example where the remote server's IP address was 10.0.0.10, if the local IP address is 10.0.0.5, then use the command:

ping 10.0.0.5

If the ping is successful, proceed to Step 4. A failure indicates a configuration problem or a hardware problem with the PA-MC-2T3+.

Step 4 Remove the local loop with the no loopback command and place the remote server or DSU in network loopback with the loopback remote command.


Note The loopback remote command is only available when the framing is set to c-bit parity. If the framing is not set to c-bit parity, the remote server will have to be placed into network loopback by someone at the remote site.


Step 5 Repeat Step 3. If the ping is successful then the PA-MC-2T3+ and the T3 link to the remote site is functioning correctly. The problem is probably in the remote DSU or server configuration or hardware. If the ping fails then either the T3 link to the remote site or the remote server or DSU configuration or hardware has a problem.