cc/td/doc/product/cable/cab_rout/cfig_nts
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring the PA-T3

Configuring the PA-T3

To continue your PA-T3 port adapter installation, you must configure the serial interfaces. The instructions that follow apply to all supported platforms. Minor differences between the platforms---with Cisco IOS software commands---are noted.

If you installed a new PA-T3 port adapter or if you want to change the configuration of an existing interface, you must enter configuration mode using the configure command. If you replaced a PA-T3 port adapter that was previously configured, the system recognizes the new PA-T3 port adapter interfaces and brings each of them up in their existing configuration.

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

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

Configuration commands are executed from the privileged level of the EXEC command interpreter, which usually requires password access. Contact your system administrator, if necessary, to obtain access. (See the "Using the EXEC Command Interpreter" section for an explanation of the privileged level of the EXEC.)

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 is 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#


Proceed to the following sections to configure the new interfaces.

Shutting Down an Interface

Before you remove an interface that you will not replace, replace a compact serial cable, 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 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 Crtl-Z.
Router(config)#
 

Step 3 Specify the slot/port address of the first interface that you want shut down by entering the subcommand interface as described in .


Table 4-1: Interface Subcommand Syntax
Platform Command Example

Cisco 7200 series or Cisco uBR7200

interface, followed by the type (serial) and slot/port (port adapter slot number/0)

Router(config)# interface serial 1/0

VIP2 or VIP4

interface, followed by the type (serial) and slot/port (interface processor slot number/0)

Router(config)# interface serial 1/1/0

Catalyst RSM/VIP2

interface, followed by the type (serial) and port adapter slot number/interface port number (port adapter slot number/0)

Router(config)# interface serial 0/0

Cisco 7120

interface, followed by the type (serial) and port adapter number/interface port number

Router(config)# interface serial 3/0

Cisco 7140

interface, followed by the type (serial) and port adapter number/interface port number

Router(config)# interface serial 4/0

Step 4 Enter the shutdown command as follows:

Router(config-if)# shutdown
 

Step 5 To shut down additional interfaces, enter the slot/port address (or slot/port address/interface port for a VIP) of each additional interface followed by the shutdown command. When you have entered all the interfaces to be shut down, press Ctrl-Z (hold down the Control key while you press Z) or enter end to exit configuration mode and return to the EXEC command interpreter prompt.

The example that follows is for the Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series routers:

Router(config-if)# interface serial 1/0
Router(config-if)# shutdown
Router(config-if)# interface serial 1/1
Router(config-if)# shutdown
Ctrl-Z
Router#
 

The example that follows is for a VIP:

Router(config-if)# interface serial 1/1/0
Router(config-if)# shutdown
Router(config-if)# interface serial 1/1/1
Router(config-if)# shutdown
Ctrl-Z
Router#
 

The example that follows is for a Catalyst RSM/VIP2:

Router(config-if)# interface serial 1/0
Router(config-if)# shutdown
Router(config-if)# interface serial 1/1
Router(config-if)# shutdown
Ctrl-Z
Router#
 

Step 6 Write the new configuration to memory as follows:

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

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

Step 7 Verify that new interfaces are now in the correct state (shutdown). To do so on the Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series routers, use the show interfaces serial slot/port command to display the specific interface, or use the show interfaces command, without variables, to display the status of all interfaces in the system.

The example that follows is for Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series routers:

Router# show interfaces serial 1/0
 
Serial 1/0 is administratively down, line protocol is down
  Hardware is M1T-T3 pa
  [display text omitted]
 

To verify that new interfaces are now in the correct state (shutdown) on a VIP, use the show interfaces serial slot/port adapter/interface command to display the specific interface, or use the show interfaces command, without variables, to display the status of all interfaces in the system.

The example that follows is for a VIP:

Router# show interfaces serial 1/1/0
 
Serial 1/1/0 is administratively down, line protocol is down
  Hardware is cyBus PODS3 Serial
  [display text omitted]
 

To verify that new interfaces are now in the correct state (shutdown) on a Catalyst RSM/VIP2, use the show interfaces serial port adapter/interface command to display the specific interface, or use the show interfaces command, without variables, to display the status of all interfaces in the system.

The example that follows is for a Catalyst RSM/VIP2:

Router# show interfaces serial 1/0
 
Serial 1/0 is administratively down, line protocol is down
  Hardware is cyBus PODS3 Serial
  [display text omitted]
 

Step 8 Reenable the interfaces. To do so, repeat the previous steps, but use the no shutdown command in Step 4, and then write the new configuration to memory as follows.

The example that follows is for the Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series routers:

Router(config)# interface serial 1/0
Router(config-if)# no shutdown
Ctrl-Z
Router#
 
Router# copy running-config startup-config
[OK]
Router# show interfaces serial 1/0
Serial 1/0 is up, line protocol is up
  Hardware is M1T-T3 pa
[display text omitted]
 

The example that follows is for a VIP:

Router(config)# interface serial 1/1/0
Router(config-if)# no shutdown
Ctrl-Z
Router#
 
Router# copy running-config startup-config
[OK]
Router# show interfaces serial 1/1/0
 
Serial 1/1/0 is up, line protocol is up
  Hardware is M1T-T3 pa
  [display text omitted]
 

The example that follows is for a Catalyst RSM/VIP2:

Router(config)# interface serial 1/0
Router(config-if)# no shutdown
Ctrl-Z
Router#
 
Router# copy running-config startup-config
[OK]
Router# show interfaces serial 1/0
 
Serial 1/0 is up, line protocol is up
  Hardware is M1T-T3 pa
  [display text omitted]

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

Performing a Basic Configuration

The following steps make up a basic interface configuration for the PA-T3 serial port adapter. 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:

router# disable
 
router> 
 

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

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

Step 2 Specify the interface to configure:

    router(config)# interface serial 3/0
    

    router(config)# interface serial 1/0/0
     
    
    router(config)# interface serial 0/0
    

Step 3 If IP routing is enabled on the system, change to interface configuration mode and use the ip address configuration subcommand to assign an IP address and subnet mask to the interface, as in the following example:

router(config-if)# ip address 10.0.0.0 10.255.255.255 
 

Step 4 In interface configuration mode, choose the internal clock source by entering the clock source configuration subcommand, as in the following example:

router(config-if)# clock source internal
 

Use the no form of this command to restore the default clock source, which is line.

Step 5 In interface configuration mode, change the shutdown state to up and enable the interface as follows:

router(config-if)# no shutdown
 

Step 6 Configure additional interfaces as required.

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

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

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

To check the interface configuration using show commands, proceed to the section "Using show Commands to Display Interface and System Information" section .

Configuration Example

The following example shows a typical configuration for the PA-T3 serial port adapter on a Cisco 7500 series router:

router> enable
router# configure terminal
router(config)# interface serial
router(config)# interface serial 1/0/0
router(config)# ip address 10.0.0.0 10.255.255.255
router(config-if)# clock source internal
router(config-if)# no shutdown
router(config-if)# ^Z
 

Customizing the PA-T3 Serial Port Adapter

You can customize the PA-T3 serial port adapter. The features you can customize have default values that probably suit your environment and do not require change. However, you might need to enter configuration commands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. Perform the tasks in the following sections if you need to customize the PA-T3 serial port adapter.

Setting the Bandwidth

In interface configuration mode, reduce effective bandwidth (range of 22 to 44210 kbps) by entering the dsu bandwidth configuration subcommand, as in the following example:

router(config-if)# dsu bandwidth 16000
 

Use the no form of this command to return to the default, which is 44210.


Note The local port configuration must match the remote port configuration. For example, if you reduce the effective bandwidth to 16000 on the local port, you must do the same on the remote port.

Defining the DSU Mode

In interface configuration mode, define the DSU interoperability mode by entering the dsu mode [0 | 1 | 2] 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, which is 0.


Note The local port configuration must match the remote port configuration. For example, if you define the DSU interoperability mode as 1 on the local port, you must do the same on the remote port. You need to know what type of DSU is at the remote port to find out if it interoperates with the PA-T3 port adapter. For T3 serial interfaces, specify mode 0 for connection from a T3 serial port adapter to another PA-T3 serial port adapter or a Digital Link DSU (DL3100). Specify mode 1 for connection from a PA-T3 serial port adapter to a Kentrox DSU. Specify mode 2 for connection from a PA-T3 serial port adapter to a Larscom DSU.

See the "Interoperability Guidelines for PA-T3 Serial Port Adapter DSUs" section for information regarding DSU feature compatibilities.

Enabling T3 Scrambling

In interface configuration mode, enable T3 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, which is disabled.


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

See the "Interoperability Guidelines for PA-T3 Serial Port Adapter DSUs" section for information regarding DSU feature compatibilities.

Specifying T3 Framing

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

router(config-if)# framing c-bit
 

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


Note If you use the bypass option, scrambling must be set to the default, disabled; the DSU mode must be set to the default, 0; and the DSU bandwidth must be set to the default, 44210.

Setting the Cable Length

In interface configuration mode, set the cable length (range of 0 to 450 feet), as in the following example:

router(config-if)# cablelength 250
 

Use the no form of this command to return to the default, which is 10 feet.

Configuring Cyclic Redundancy Checks

The PA-T3 serial port adapter uses a 16-bit CRC by default; it also supports a 32-bit CRC.

CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The sender of a data frame divides the bits in the frame message by a predetermined number to calculate a remainder or frame check sequence (FCS). Before sending the frame, the sender appends the FCS value to the message so that the frame contents are exactly divisible by the predetermined number. The receiver divides the frame contents by the same predetermined number that the sender used to calculate the FCS. If the result is not 0, the receiver assumes that a transmission error occurred and sends a request to the sender to resend the frame.


Note To enable 32-bit CRC on an interface, follow Steps 1 and 2 of the preceding procedure (enter configuration mode and specify the slot and port address [and the interface port number for a VIP] of the PA-T3 serial port adapter), and then enter the command crc 32. Enter Ctrl-Z to exit from configuration mode.

For a Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series router, use the following example:

router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#
router(config)# interface serial 3/0
router(config-int)# crc 32 
Ctrl-z
 

For a VIP, use the following example:

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

For a Catalyst RSM/VIP2, use the following example:

router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#
router(config)# interface serial 0/0
router(config-if)# crc 32 
Ctrl-z
 

To disable CRC-32 and return to the default CRC-16 setting, specify the slot and port address (and the interface port number for a VIP) and use the no crc 32 command. For complete command descriptions and instructions, refer to the related software documentation.


Note When enabling a 32-bit CRC on an interface, ensure that the remote device is also configured for a 32-bit CRC. Both the sender and the receiver must use the same CRC setting.

To check the interface configuration using show commands, proceed to the following section, "Checking the Configuration ."

Checking the Configuration

After configuring the new interface, use the show commands to display the status of the new interface or all interfaces, the ping command to check connectivity, and the loopback command to troubleshoot the physical interface.

Using show Commands to Verify Status

Use the show commands to verify that the new interfaces are configured and operating correctly:


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

Step 2 Display all the current port adapters and their interfaces with the show controllers command. Verify that the new PA-T3 serial port adapter appears in the correct slot.

Step 3 Specify one of the new interfaces:

Step 4 Specify the new serial interface:

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

Step 6 Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM using the show startup-config command. Verify that the configuration is accurate for the system and each interface.


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

Using show Commands to Display Interface and System Information

For a Cisco 7100 series, Cisco 7200 series, or Cisco uBR7200 series router, to display information about a specific interface, use the show interfaces command with the interface type and port address in the format show interfaces [type slot/port].

The following example of the show interfaces type slot/port command shows all of the information specific to the serial PA-T3 port (interface port 0) in port adapter slot 2:

router# show interfaces serial 2/0
 
Serial2/0 is up, line protocol is up 
  Hardware is M1T-T3 pa
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 00:00:01, output 00:00:03, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0 (size/max/drops); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/64/0 (size/threshold/drops) 
     Conversations  0/1 (active/max active)
     Reserved Conversations 0/0 (allocated/max allocated)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     18958 packets input, 4172738 bytes, 0 no buffer
     Received 5073 broadcasts, 0 runts, 0 giants
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     18294 packets output, 4552579 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
   rxLOS inactive, rxLOF inactive, rxAIS inactive
   txAIS inactive, rxRAI inactive, txRAI inactive
 
router#
 

For a VIP, the show interfaces type slot/port-adapter/port command displays status information (including the physical slot and port address) for the interfaces you specify. In this example, a one-port PA-T3 serial port adapter-configured VIP is in chassis slot 10, in port adapter slot 0.

router# show interfaces serial 10/0/0
Serial10/0/0 is up, line protocol is up 
  Hardware is cyBus PODS3 Serial
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 00:00:00, output 00:00:00, 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
     14771 packets input, 3032919 bytes, 0 no buffer
     Received 2664 broadcasts, 0 runts, 0 giants
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     15775 packets output, 2808513 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
   rxLOS inactive, rxLOF inactive, rxAIS inactive
   txAIS inactive, rxRAI inactive, txRAI inactive
router#
 

For a Catalyst RSM/VIP2, the show interfaces port-adapter/port command displays status information for the interfaces you specify. In this example, a one-port PA-T3 serial port adapter-configured Catalyst RSM/VIP2 is in port adapter slot 0.

router# show interfaces serial 0/0
Serial0/0 is up, line protocol is up 
  Hardware is cyBus PODS3 Serial
  MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load 1/255
  Encapsulation HDLC, loopback not set, keepalive not set
  Last input 00:00:00, output 00:00:00, 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
     14771 packets input, 3032919 bytes, 0 no buffer
     Received 2664 broadcasts, 0 runts, 0 giants
              0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     15775 packets output, 2808513 bytes, 0 underruns
     0 output errors, 0 applique, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
   rxLOS inactive, rxLOF inactive, rxAIS inactive
   txAIS inactive, rxRAI inactive, txRAI inactive
router#
 

For Cisco 7100 series, Cisco 7200 series, and Cisco uBR7200 series routers, use the show controllers command to display all the current interface processors and their interfaces. Following is an example of the show controllers command that shows serial port 2/0 on a one-port PA-T3 serial port adapter installed in chassis slot 2 for a Cisco 7200 series router:

router# show controllers 2/0
 
M1T-Serial: show controller:
PAS unit 0, subunit 0, f/w version 1-23, rev ID 0x1, version 2
idb = 0x608PA-T3340, ds = 0x608E50C0, ssb=0x608E5A84
Clock mux=0x35, ucmd_ctrl=0x8, port_status=0x25
maxdgram=4474, bufpool=64Kb, 128 particles
     TM=down  CA=up  LC=down
line state: up
Serial DTE cable
          
(Additional display text omitted from this example.)
 

For Cisco 7100 series, Cisco 7200 series, Cisco uBR7200 series routers, use the show controllers serial command, using arguments such as the slot and port number (slot/port), to display information that is specific to the serial interface hardware. Following is an example of the show controllers serial slot/port command that shows the serial port adapter installed on a Cisco 7200 series router in chassis slot 3:

router# show controllers serial 3/0
 
M1T-T3 pa: show controller:
PAS unit 0, subunit 0, f/w version 2-55, rev ID 0x2800001, version 2
idb = 0x60C03278, ds = 0x60C07704, ssb=0x60C05298
Clock mux=0x30, ucmd_ctrl=0x0, port_status=0x0
Serial config=0x8, line config=0x1B0202
maxdgram=4480, bufpool=128Kb, 256 particles
 
   rxLOS active, rxLOF inactive, rxAIS inactive
   txAIS active, rxRAI inactive, txRAI active
 
line state: down
PA-T3 DTE cable, received clockrate 1582
 
base0 registers=0x3F000000, base1 registers=0x3F002000
mxt_ds=0x60CD2308, rx ring entries=128, tx ring entries=256
rxring=0x4B0AB940, rxr shadow=0x60CB06E4, rx_head=95
txring=0x4B0ABE20, txr shadow=0x60CB12C0, tx_head=0, tx_tail=0,
tx_count=0
throttled=0, enabled=0, disabled=0, halted=0
rx_no_eop_err=3231, rx_no_stp_err=0, rx_no_eop_stp_err=0
rx_no_buf=0, rx_soft_overrun_err=0, dump_err= 3465869
tx_underrun_err=1, tx_soft_underrun_err=0, tx_limited=1
tx_fullring=0, tx_started=121324
   Framing is c-bit, Clock Source is Line, Bandwidth limit is 44210.,
DSU mode 0 Cable length is 50
   Data in current interval (407 seconds elapsed):
     406 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
     408 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely
Errored Secs
   Total Data (last 24 hours)
     86400 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,
     86400 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely
Errored Secs
 
   Transmitter is sending remote alarm.
 
   Receiver has loss of signal.
  Last FEAC code received: LOS
  FEBE since last read:  0
  F-bit errors since last read:  24
  M-bit errors since last read:  2
          
PIO A: 738, PIO B: 60B, Gapper register: 1094
Framer register information:
reg 0: C0       reg 1: C5       reg 2: 0        reg 3: 27
reg 4: 5        reg 5: 8E       reg 6: 8E       reg 7: CB
reg 8: 80       reg 9: 0        reg A: 0        reg B: 0
reg C: E        reg D: 0        reg E: B8       reg F: E
reg 10: CB      reg 11: 0       reg 12: 0       reg 13: 0
reg 14: 0
router#
 

For a VIP, use the show controllers serial command, using arguments such as those that specify the slot, port adapter, and port number (slot/port-adapter/port), to display information that is specific to the serial interface hardware. Following is an example of the show controllers serial type slot/port adapter/interface command that shows serial port 10/0/0 on a one-port PA-T3 serial port adapter installed on a VIP in chassis slot 0:

router# show controllers serial 10/0/0
Serial10/0/0 - 
   Mx PA-T3(1) HW Revision 0x2, FW Revision 2.55
   Framing is c-bit, Clock Source is Line, Bandwidth limit is 44210., 
DSU mode 0 Cable length is 50
   Data in current interval (325 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
   Total Data (last 24 hours)
     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
 
   No alarms detected.
router#
 

For a Catalyst RSM/VIP2, use the show controllers serial command, using arguments such as those that specify the port adapter and port number (port-adapter/port), to display information that is specific to the serial interface hardware. Following is an example of the show controllers serial port adapter/interface command that shows serial port 0/0 on a one-port PA-T3 serial port adapter installed on a Catalyst RSM/VIP2:

router# show controllers serial 0/0
Serial0/0 - 
   Mx PA-T3(1) HW Revision 0x2, FW Revision 2.55
   Framing is c-bit, Clock Source is Line, Bandwidth limit is 44210., 
DSU mode 0 Cable length is 50
   Data in current interval (325 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
   Total Data (last 24 hours)
     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
 
   No alarms detected.
router#
 

The show version (or show hardware) command displays the configuration of the system hardware (the number of each port adapter type installed), the software version, the names and sources of configuration files, and the boot images. Following is an example of the output from the show version command on a Cisco 7200 series router:

router# show version
 
Cisco Internetwork Operating System Software 
IOS (tm) GS Software (RSP-JV-M), Version 11.1(16)CA 
Synced to mainline version: 11.1(13.5)
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Sat 06-Sep-97 02:12 by paking
Image text-base: 0x60010900, data-base: 0x60A42000
 
ROM: System Bootstrap, Version 11.1(5) [mkamson 5], RELEASE SOFTWARE (fc1)
ROM: 7200 Software (C7200-BOOT-M), Version 11.1(6), RELEASE SOFTWARE (fc1)
 
byron uptime is 22 minutes
System restarted by reload
System image file is "c7200-p-mz", booted via tftp from 10.0.0.0
 
cisco 7206 (NPE150) processor with 12288K/4096K bytes of memory.
R4700 processor, Implementation 33, Revision 1.0 (512KB Level 2 Cache)
Last reset from power-on
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
4 Ethernet/IEEE 802.3 interfaces.
1 Serial network interface.
1 FDDI network interface.
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 0x2
 

Following is an example of the show version command used with a Cisco 7500 series router:

router# show version
 
Cisco Internetwork Operating System Software 
IOS (tm) GS Software (RSP-JV-M), Version 11.1(16)CA 
Synced to mainline version: 11.1(13.5)
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Sat 06-Sep-97 02:12 by paking
Image text-base: 0x60010900, data-base: 0x60A42000
 
ROM: System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM SOFTWARE
ROM: GS Software, Version 11.1(8)CA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) 
 
keats uptime is 22 minutes
System restarted by reload
System image file booted via tftp from 10.0.0.0
 
Last reset from power-on
G.703/E1 software, Version 1.0.
G.703/JT2 software, Version 1.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc).
Chassis Interface.
3 VIP2 controllers (1 FastEthernet)(4 Ethernet)(1 Fddi)(2 PA-T3).
4 Ethernet/IEEE 802.3 interfaces.
1 FastEthernet/IEEE 802.3 interface.
2 Serial network interfaces.
1 FDDI network interface.
125K bytes of non-volatile configuration memory.
 
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2
 

To determine which type of port adapter is installed in your system, use the show diag slot command. Specific port adapter information is displayed, as shown in the following example of a one-port PA-T3 serial port adapter in chassis slot 3 on a Cisco 7200 series router:

router# show diag 3
 
Slot 3:
        PA-T3 PA port adapter, 1 port
        Port adapter is analyzed 
        Port adapter insertion time 3d19h ago
        Hardware revision 0.1           Board revision UNKNOWN
        Serial number     4526750       Part number    73-2616-01
        Test history      0x0           RMA number     00-00-00
        EEPROM format version 0
        EEPROM contents (hex):
          0x20: 00 70 00 01 00 45 12 9E 49 0A 38 01 00 00 00 00
          0x30: 00 00 00 00 97 05 01 00 FF FF FF FF FF FF FF FF
 

The following example shows a one-port PA-T3 serial port adapter in chassis slot 10 on a VIP:

router# show diag 10
 
Slot 10:
        Physical slot 10, ~physical slot 0x5, logical slot 10, CBus 0
        Microcode Status 0x4
        Master Enable, LED, WCS Loaded
        Board is analyzed 
        Pending I/O Status: None
        EEPROM format version 1
        VIP2 controller, HW rev 2.4, board revision D0
        Serial number: 04481599  Part number: 73-1684-03
        Test history: 0x00        RMA number: 00-00-00
        Flags: cisco 7000 board; 7500 compatible
 
        EEPROM contents (hex):
          0x20: 01 15 02 04 00 44 62 3F 49 06 94 03 00 00 00 00
          0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 
        Slot database information:
        Flags: 0x4      Insertion time: 0x14AC (3d19h ago)
 
        Controller Memory Size: 32 MBytes DRAM, 2048 KBytes SRAM
 
        PA Bay 0 Information:
                PA-T3 Serial PA, 1 ports
                EEPROM format version 0
                HW rev 0.1, Board revision UNKNOWN
                Serial number: 04526751  Part number: 73-2616-01 
 
        PA Bay 1 Information:
                PA-T3 Serial PA, 1 ports
                EEPROM format version 0
                HW rev 0.1, Board revision UNKNOWN
                Serial number: 04526749  Part number: 73-2616-01 
 

The following example shows a one-port PA-T3 serial port adapter on a Catalyst RSM/VIP2:

router# show diag 0
 
Slot 0:
        Physical slot 0, ~physical slot 0x5, logical slot 0, CBus 0
        Microcode Status 0x4
        Master Enable, LED, WCS Loaded
        Board is analyzed 
        Pending I/O Status: None
        EEPROM format version 1
        VIP2 controller, HW rev 2.4, board revision D0
        Serial number: 04481599  Part number: 73-1684-03
        Test history: 0x00        RMA number: 00-00-00
        Flags: cisco 7000 board; 7500 compatible
 
        EEPROM contents (hex):
          0x20: 01 15 02 04 00 44 62 3F 49 06 94 03 00 00 00 00
          0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 
        Slot database information:
        Flags: 0x4      Insertion time: 0x14AC (3d19h ago)

Note The slot values displayed by some commands (such as show diag and show controllers cbus) are not relevant to any physical connection; you should disregard these slot values for the Catalyst RSM/VIP2.

For a VIP, use the show controllers cbus command to display all of the current interface processors and their interfaces. Following is an example of the show controllers cbus command that shows serial port 1/0/0 on a one-port PA-T3 serial port adapter installed on a VIP in chassis slot 1:

router# show controllers cbus 1/0/0
 
MEMD at 40000000, 2097152 bytes (unused 4288, recarves 1, lost 0)
  RawQ 48000100, ReturnQ 48000108, EventQ 48000110
  BufhdrQ 48000138 (2810 items), LovltrQ 48000150 (20 items, 2016 bytes)
  IpcbufQ 48000160 (32 items, 4096 bytes)
  IpcbufQ_classic 48000158 (8 items, 4096 bytes)
  3570 buffer headers (48002000 - 4800FF10)
  pool0: 9 buffers, 256 bytes, queue 48000140
  pool1: 458 buffers, 1536 bytes, queue 48000148
  pool2: 229 buffers, 4512 bytes, queue 48000168
  pool3: 4 buffers, 4544 bytes, queue 48000170
  slot0: VIP2, hw 2.4, sw 21.40, ccb 5800FF20, cmdq 48000080, vps 8192
    software loaded from system 
    IOS (tm) VIP Software (SVIP-DW-M), Version 11.1(16)CA
    ROM Monitor version 17.0
    Ethernet0/0/0, addr 00e0.f7d7.cb00 (bia 00e0.f7d7.cb00)
      gfreeq 48000148, lfreeq 48000178 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 2, maxrxcurr 4
      txq 48001A00, txacc 48001A02 (value 152), txlimit 152
    Ethernet0/0/1, addr 00e0.f7d7.cb01 (bia 00e0.f7d7.cb01)
      gfreeq 48000148, lfreeq 48000180 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A08, txacc 48001A0A (value 0), txlimit 152
    Ethernet0/0/2, addr 00e0.f7d7.cb02 (bia 00e0.f7d7.cb02)
      gfreeq 48000148, lfreeq 48000188 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A10, txacc 48001A12 (value 0), txlimit 152
    Ethernet0/0/3, addr 00e0.f7d7.cb03 (bia 00e0.f7d7.cb03)
      gfreeq 48000148, lfreeq 48000190 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A18, txacc 48001A1A (value 0), txlimit 152
 
(Additional displayed text omitted from this example.)
 

For a Catalyst RSM/VIP2, use the show controllers cbus command to display all of the interfaces. Following is an example of the show controllers cbus command that shows serial port 0/0 on a one-port PA-T3 serial port adapter installed on a Catalyst RSM/VIP2:

router# show controllers cbus 0/0
 
MEMD at 40000000, 2097152 bytes (unused 4288, recarves 1, lost 0)
  RawQ 48000100, ReturnQ 48000108, EventQ 48000110
  BufhdrQ 48000138 (2810 items), LovltrQ 48000150 (20 items, 2016 bytes)
  IpcbufQ 48000160 (32 items, 4096 bytes)
  IpcbufQ_classic 48000158 (8 items, 4096 bytes)
  3570 buffer headers (48002000 - 4800FF10)
  pool0: 9 buffers, 256 bytes, queue 48000140
  pool1: 458 buffers, 1536 bytes, queue 48000148
  pool2: 229 buffers, 4512 bytes, queue 48000168
  pool3: 4 buffers, 4544 bytes, queue 48000170
  slot0: VIP2, hw 2.4, sw 21.40, ccb 5800FF20, cmdq 48000080, vps 8192
    software loaded from system 
    IOS (tm) VIP Software (SVIP-DW-M), Version 11.1(16)CA
    ROM Monitor version 17.0
    Ethernet0/0, addr 00e0.f7d7.cb00 (bia 00e0.f7d7.cb00)
      gfreeq 48000148, lfreeq 48000178 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 2, maxrxcurr 4
      txq 48001A00, txacc 48001A02 (value 152), txlimit 152
    Ethernet0/1, addr 00e0.f7d7.cb01 (bia 00e0.f7d7.cb01)
      gfreeq 48000148, lfreeq 48000180 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A08, txacc 48001A0A (value 0), txlimit 152
    Ethernet0/2, addr 00e0.f7d7.cb02 (bia 00e0.f7d7.cb02)
      gfreeq 48000148, lfreeq 48000188 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A10, txacc 48001A12 (value 0), txlimit 152
    Ethernet0/3, addr 00e0.f7d7.cb03 (bia 00e0.f7d7.cb03)
      gfreeq 48000148, lfreeq 48000190 (1536 bytes), throttled 0
      rxlo 4, rxhi 273, rxcurr 0, maxrxcurr 0
      txq 48001A18, txacc 48001A1A (value 0), txlimit 152
 
(Additional displayed text omitted from this example.)
 

Note The slot values displayed by some commands (such as show diag and show controllers cbus) are not relevant to any physical connection; you should disregard these slot values for the Catalyst RSM/VIP2.

For complete command descriptions and examples for the Cisco 7100 series routers, Cisco 7200 series routers, Cisco uBR7200 series routers, VIP and Catalyst RSM/VIP2, refer to the publications listed in the "Related Documentation" section.

Using the ping Command to Verify Network Connection

The ping command allows you to verify that an interface port is functioning properly and to check the path between a specific port and connected devices at various locations on the network. After you verify that the system has booted successfully and is operational, you can use the ping command to verify the status of interface ports. Refer to the publications listed in the "Related Documentation" section for detailed command descriptions and examples.

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

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

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

If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command. Refer to the publications listed in the "Related Documentation" section for complete descriptions of interface subcommands and the available configuration options.

Using the loopback Command to Verify the Physical Interface

Use the loopback {dte | local | network {line | payload} | remote} command to troubleshoot the PA-T3 serial port adapter at the physical interface level. The command loops all packets from the PA-T3 interface either back to the interface or from the network back out toward the network. Use the no form of the command to remove the loop.

The following examples of the loopback {dte | local | network {line | payload} | remote} command configure loopback modes on serial port 0 of a one-port PA-T3 serial port adapter installed in chassis slot 6 of a Cisco 7200 series router:

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

Loopback DTE loops the router output data back toward the router (after the line interface unit [LIU]).

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

Local loopback loops the router output data back toward the router at the framer.

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

Network line loopback loops the data back toward the network (before the framer).

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

Network payload loopback loops just the payload data back toward the network at the PA-T3 framer.

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

Remote loopback loops the data back toward the network (before the framer at the remote
T3 device).


Note Remote loopback mode works with C-bit framing only. The other loopback modes listed above work with C-bit, M13, and bypass framing. See the "Specifying T3 Framing" section for information on configuring C-bit framing.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Jul 21 07:30:13 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.