Table of Contents

Using the EXEC Command Interpreter
Configuring the Interfaces

Shutting Down an Interface
Performing a Basic Configuration
Configuring Timing (Clock) Signals

Setting the Clock Rate
Inverting the Clock Signal
Inverting the Data Signal

Configuring NRZI Format
Configuring Cyclic Redundancy Checks

Configuring Half-Duplex and Binary Synchronous Communications in Cisco 7200 Series Routers

Setting the Bandwidth
Defining the DSU Mode
Enabling T3+ Scrambling
Specifying T3+ Framing
Setting the Cable Length

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 ping Command to Verify Network Connectivity
Using loopback Commands

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.

This chapter contains the following sections:

• Using the EXEC Command Interpreter
  
  
• Configuring the Interfaces
  
  
• Configuring Half-Duplex and Binary Synchronous Communications in Cisco 7200 Series Routers
  
  
• 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:

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 (#):

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

Configuring the Interfaces

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

• T3+ information such as clock source and framing type
  
  
• Protocols you plan to route on each new interface
  
  
• IP addresses, if you plan to configure the interfaces for IP routing
  
  
• Bridging protocols you plan to use
  
  
• Timing source for each new interface and clock speeds for external timing
  
  

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

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

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

This section contains the following subsections:

• Shutting Down an Interface
  
  
• Performing a Basic Configuration
  
  
• Configuring Timing (Clock) Signals
  
  
• Configuring NRZI Format
  
  
• Configuring Cyclic Redundancy Checks
  
  
• Setting the Bandwidth
  
  
• Defining the DSU Mode
  
  
• Enabling T3+ Scrambling
  
  
• Specifying T3+ Framing
  
  
• Setting the Cable Length
  
  

Shutting Down an Interface

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

Follow these steps to shut down an interface:

Step 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:

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

When you have finished, 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.

Step 4   Write the new configuration to NVRAM as follows:

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

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

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

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

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

Performing a Basic Configuration

Following are instructions for a basic configuration: enabling an interface, specifying IP routing, and setting up external timing on a DCE interface. 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:

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

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. (The command for your port adapter may be different, for example, interface atm.) Table 4-3 provides examples.

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

Step 6   Configure all additional port adapter interfaces as required.

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

Step 8   Write the new configuration to NVRAM as follows:

This completes the procedure for creating a basic configuration.

Configuring Timing (Clock) Signals

All EIA/TIA-232 interfaces support both DTE and DCE mode, depending on the mode of the compact serial cable attached to the port. To use a port as a DTE interface, you need only connect a DTE compact serial cable to the port. When the system detects the DTE mode cable, it automatically uses the external timing signal. To use a port in DCE mode, you must connect a DCE compact serial cable and set the clock speed with the clock rate configuration command. You must also set the clock rate to perform a loopback test. This section describes how to set the clock rate on a DCE port and, if necessary, how to invert the clock to correct a phase shift between the data and clock signals. Table 4-4 summarizes some of the commands used to configure the clock rate. See the specific sections that follow for further details.

Setting the Clock Rate

The default operation on a PA-T3+ DCE interface is for the DCE device to generate its own clock signal (TxC) and send it to the remote DTE. The remote DTE device returns the clock signal to the DCE (the PA-T3+). Set the clock rate of an interface using the clock rate subcommand, which specifies the clock rate as a bits-per-second value. This subcommand functions in the same way on all supported platforms.

Before you can assign a clock rate, you must use the interface serial command (followed by the interface address of the interface) to select the interface to which you want to assign the clock rate value.

In the following example, the clock rate is specified as 72 kbps:

The preceding command example applies to all systems in which the PA-T3+ is supported. Use the no clock rate command to remove the clock rate.

Following are the standard clock rates:

1200, 2400, 4800, 9600, 19200 38400 , 56000 , 64000 ,
72000 , 125000 148000 , 250000, 500000, 800000, 1000000,
1300000, 2000000, 4000000, 8000000

When you have finished, 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. Then write the new configuration to NVRAM using the copy running-config startup-config command.

Note   Cisco IOS Release 11.2(7a)P or a later release of 11.2 P, or Release 11.1(10)CA or a later release of 11.1 CA loaded on your Cisco 7200 router or on your Cisco 7000 series or Cisco 7500 series router with a VIP2-40(=) supports nonstandard clock rates (any value from 1200 to 8000000) on PA-T3+ interfaces. Cisco IOS Release 12.0(3)T or a later release of 12.0 T, or Release 12.0(1)XE or a later release of 12.0 XE supports nonstandard clock rates on PA-T3+ interfaces installed in Cisco 7204VXR and Cisco 7206VXR routers. Cisco IOS Release 11.3(7)NA or a later release of 11.3 NA, or Release 12.0(3)T or a later release of 12.0 T loaded on your Cisco uBR7200 series router supports nonstandard clock rates (any value from 1200 to 8000000) on PA-T3+ interfaces. Nonstandard clock rates are rounded (if necessary) to the nearest clock rate that the hardware can support.

Set a nonstandard clock rate for an interface using the clock rate subcommand. Before you can assign a nonstandard clock rate, you must use the interface serial command (followed by the interface address of the interface) to select the interface to which you want to assign the nonstandard clock rate value.

In the following example, a nonstandard clock rate of 1234567 bps is specified:

The preceding command example applies to all systems in which the PA-T3+ is supported.
Use the no clock rate command to remove the clock rate.

When you have finished, 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. Then write the new configuration to NVRAM using the copy running-config startup-config command.

The following example shows how to use the show running-config command to determine the exact clock rate to which the nonstandard clock rate was rounded:

In the preceding example, only the relevant output from the show running-config command is shown; other information is omitted.

Inverting the Clock Signal

Systems that use long cables or cables that are not transmitting the TxC (clock) signal might experience high error rates when operating at higher transmission speeds. If a PA-T3+ DCE port is reporting a high number of error packets, a phase shift might be the problem: inverting the clock might correct this phase shift.

When the EIA/TIA-232 interface is a DTE, the invert-txc command inverts the TxC signal the DTE receives from the remote DCE. When the EIA/TIA-232 interface is a DCE, the invert-txc command inverts the clock signal to the remote DTE port. Use the no invert-txc command to change the clock signal back to its original phase.

Inverting the Data Signal

If you use an EIA/TIA-232 interface on the PA-T3+ port adapter to drive a dedicated T1 line that does not have B8ZS encoding—a method to avoid 15 zeros—you must invert the data stream
(both TXD and RXD) either in the connecting CSU/DSU or on the interface. To invert the data stream coming out of the PA-T3+, use the invert data command. By inverting the HDLC data stream, the HDLC zero insertion algorithm becomes a ones insertion algorithm that satisfies the T1 requirements.

Note   Invert data only on the PA-T3+ interface or on the CSU/DSU; inverting both cancels out both data inversions.

Configuring NRZI Format

Table 4-5 summarizes NRZI format commands. For more information, see the remainder of this section.

For complete command descriptions and instructions, refer to the Configuration Fundamentals Configuration Guide publication. For more information, see the "Obtaining Documentation" section and the "Obtaining Technical Assistance" section.

Configuring Cyclic Redundancy Checks

Table 4-6 summarizes cyclic redundancy check (CRC) commands. For more information, see the remainder of this section.

For command descriptions, refer to the Configuration Fundamentals Configuration Guide publication. For more information, see the "Obtaining Documentation" section and the."Obtaining Technical Assistance" section.

Note   If you are configuring a PA-T3+ in a Cisco 7200 router and you want to configure the interface for half-duplex or Bisync operation, proceed to the next section, "Setting the Bandwidth"; otherwise, proceed to the "Setting the Bandwidth" section.

Configuring Half-Duplex and Binary Synchronous Communications in Cisco 7200 Series Routers

This section explains how to configure EIA/TIA-232 interfaces for half-duplex and Bisync operation in Cisco 7200 routers.

Note   Cisco IOS Release 11.2(7a)P or a later release of 11.2 P supports half-duplex and Bisync operation on the PA-T3+ in Cisco 7200 routers. Cisco IOS Release 11.1(19)CC1 or a later release of 11.1 CC, or Release 11.3(4)AA or a later release of 11.3 AA supports half-duplex and Bisync operation on the PA-T3+ installed in Cisco 7202 routers. Cisco IOS Release 12.0(3)T or a later release of 12.0 T, or Release 12.0(2)XE or a later release of 12.0 XE supports half-duplex and Bisync operation on the PA-T3+ in Cisco 7204VXR and Cisco 7206VXR routers. The Catalyst RSM/VIP2, Cisco 7100 series routers, Cisco uBR7200 series routers, and the VIP do not support half-duplex and Bisync operation on the PA-T3+.

Use the half-duplex command to configure EIA/TIA-232 interfaces for half-duplex mode; full-duplex mode is the default for low-speed serial interfaces. Serial DCE interfaces in half-duplex mode can be configured for controlled-carrier mode or constant-carrier mode; constant-carrier mode is the default. Controlled-carrier mode sets the EIA/TIA-232 interface to deactivate Data Carrier Detect (DCD) until a transmission is sent to the interface. After a transmission is received, DCD is activated and the interface waits a user-configured amount of time and then transmits the data. After the transmission, the interface waits a user-configured amount of time and then deactivates DCD. Constant-carrier mode activates DCD at all times.

Use the half-duplex controlled-carrier command to configure an EIA/TIA-232 interface for controlled-carrier mode. Use the no half-duplex controlled-carrier command to return the interface to constant-carrier mode.

Follow these steps to configure controlled-carrier mode on an EIA/TIA-232 interface:

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

Step 2   Specify the interface to configure for controlled-carrier mode using the interface serial subcommand (followed by the interface address of the interface) and then enter the
half-duplex controlled-carrier subcommand.

The following example is for the first interface of the port adapter in port adapter slot 1:

Step 3   Specify the length of the timer delay the interface uses when it is configured for controlled-carrier mode by using the following command:

half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}

where value is the length of the timer delay in milliseconds.

The following example specifies a Data Carrier Detect (DCD) drop delay of 100 milliseconds on the first interface of a port adapter in port adapter slot 1:

Table 4-7 lists the default delay settings and the value argument for each timer you can use with the half-duplex timer command.

This completes the procedure for configuring controlled-carrier mode on an EIA/TIA-232 interface. For additional information on configuring half-duplex operation on low-speed serial interfaces, refer to the chapter "Configuring Interfaces" of the Configuration Fundamentals Configuration Guide publication. For more information, see the "Obtaining Documentation" section and the "Obtaining Technical Assistance" section.

Note   To configure EIA/TIA-232 interfaces for Binary Synchronous (Bisync) operation in Cisco 7200 routers, refer to the "Block Serial Tunneling (BSTUN)" section of the "Configuring Serial Tunnel (STUN) and Block Serial Tunnel (BSTUN)" chapter of the Bridging and IBM Networking Configuration Guide.

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:

Use the no form of this command to return to the default, 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:

Use the no form of this command to return to the default, 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+. For T3+ serial interfaces, specify mode 0 for connection from a PA-T3+ to another PA-T3+ or a Digital Link DSU (DL3100). Specify mode 1 for connection from a PA-T3+ to a Kentrox DSU. Specify mode 2 for connection from a PA-T3+ to a Larscom DSU.

Also see the "Interoperability Guidelines for PA-T3+ 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:

Use the no form of this command to restore the default value, 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.

Also see the "Interoperability Guidelines for PA-T3+ 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:

Use the no form of this command to return to the default, 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 (0 to 450 feet), as in the following example:

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

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
  
  

Using show Commands to Verify the New Interface Status

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

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.

• Using the show version or show hardware Commands
  
  
• Using the show diag Command
  
  
• Using the show interfaces 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.

---

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.

---

Catalyst 6000 Family FlexWAN Module in Catalyst 6000 Family Switches

Following is an example of the show version command from a Catalyst 6000 family switch with the PA-T3+:

Router# show version Cisco Internetwork Operating System Software IOS (tm) MSFC Software (C6MSFC-JSV-M), Experimental Version 12.1(20000209:134547) [amcrae-cosmos_e_nightly 163] Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Wed 09-Feb-00 07:10 by Image text-base: 0x60008900, data-base: 0x6140E000 ROM: System Bootstrap, Version 12.0(3)XE, RELEASE SOFTWARE const-uut uptime is 5 minutes System returned to ROM by reload System image file is "bootflash:c6msfc-jsv-mz.Feb9" cisco Cat6k-MSFC (R5000) processor with 122880K/8192K bytes of memory. Processor board ID SAD03457061 R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache Last reset from power-on Channelized E1, Version 1.0. Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. Primary Rate ISDN software, Version 1.1. 6 FlexWAN controllers (13 Serial)(8 E1)(8 T1)(2 HSSI)(2 ATM)(1 Channelized T3)(1 Channelized E3)(2 POS). 1 Virtual Ethernet/IEEE 802.3 interface(s) 17 Serial network interface(s) 2 HSSI network interface(s) 2 ATM network interface(s) 2 Packet over SONET network interface(s) 1 Channelized T3 port(s) 1 Channelized E3 port(s) 123K bytes of non-volatile configuration memory. 4096K bytes of packet SRAM memory. 16384K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x1

Cisco 7200 Series Routers

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

Router# show version Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-J-M), Released Version 11.1(24)CC FIB_branch Synced to mainline version:11.1(21.2)CA Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled Tue 03-Nov-98 16:44 by Image text-base:0x600088E0, data-base:0x60882000 ROM:System Bootstrap, Version 11.1(13)CA, RELEASE SOFTWARE router uptime is 2 days, 14 hours, 48 minutes System restarted by reload System image file is "slot0:c7200-j-mz.111CC", booted via console cisco 7206 (NPE200) processor with 122880K/8192K bytes of memory. R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache) Last reset from power-on Bridging software. SuperLAT software (copyright 1990 by Meridian Technology Corp). X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software (copyright 1994 by TGV Inc). 4 Ethernet/IEEE 802.3 interfaces. 3 FastEthernet/IEEE 802.3 interfaces. 3 Serial network interfaces. 125K bytes of non-volatile configuration memory. 4096K bytes of packet SRAM memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 4096K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x0

Cisco 7401ASR Routers

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

Router# show version Cisco Internetwork Operating System Software IOS (tm) 7401ASR Software (C7401ASR-J-M), Released Version 11.1(24)CC FIB_branch Synced to mainline version:11.1(21.2)CA Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled Tue 03-Nov-98 16:44 by Image text-base:0x600088E0, data-base:0x60882000 ROM:System Bootstrap, Version 11.1(13)CA, RELEASE SOFTWARE router uptime is 2 days, 14 hours, 48 minutes System restarted by reload System image file is "slot0:c7200-j-mz.111CC", booted via console cisco 7401ASR processor with 122880K/8192K bytes of memory. R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache) Last reset from power-on Bridging software. SuperLAT software (copyright 1990 by Meridian Technology Corp). X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software (copyright 1994 by TGV Inc). 4 Ethernet/IEEE 802.3 interfaces. 3 FastEthernet/IEEE 802.3 interfaces. 3 Serial network interfaces. 125K bytes of non-volatile configuration memory. 4096K bytes of packet SRAM memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 4096K bytes of Flash internal SIMM (Sector size 256K).

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-T3+:

Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-PV-M), Released Version 11.1(24)CC FIB_branch Synced to mainline version:11.1(21.2)CA Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled Tue 03-Nov-98 17:20 by Image text-base:0x60010910, data-base:0x6081E000 ROM:System Bootstrap, Version 11.1(8)CA1, RELEASE SOFTWARE router uptime is 2 days, 14 hours, 52 minutes System restarted by reload System image file is "rsp-pv-mz.111CC", booted via console cisco RSP4 (R5000) processor with 65536K/2072K bytes of memory. R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache) Last reset from power-on G.703/E1 software, Version 1.0. G.703/JT2 software, Version 1.0. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. Chassis Interface. 1 EIP controller (6 Ethernet). 1 VIP2 controller (4 Serial). 2 VIP2 R5K controllers (2 Serial)(2 HSSI). 6 Ethernet/IEEE 802.3 interfaces. 6 Serial network interfaces. 2 HSSI network interfaces. 123K bytes of non-volatile configuration memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x100

Using the show diag Command

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

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.

Catalyst 6000 FlexWAN Module in Catalyst 6000 Family Switches

Following is an example of the show diag command that shows a PA-T3+ in chassis slot 9 on a Catalyst 6000 family FlexWAN module:

Cisco 7200 Series Routers

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

Cisco 7401ASR Routers

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

VIP in Cisco 7000 Series and Cisco 7500 Series Routers

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

Using the show interfaces Command

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

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

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.

Catalyst 6000 Family FlexWAN Module in Catalyst 6000 Family Switches

Following is an example of the show interfaces command used with the FlexWAN module. In this example, the two serial interfaces (0 to 1) are on a port adapter in bay 0 of a FlexWAN module in module slot 9; also, most of the status information for each interface is omitted. (Interfaces are administratively shut down until you enable them.)

Cisco 7200 Series Routers

Following is an example of the show interfaces command for Cisco 7200 series routers. In this example, the serial two interfaces (0 to 1) are on a port adapter in port adapter slot 1; also, most of the status information for each interface is omitted. (Interfaces are administratively shut down until you enable them.)

Cisco 7401ASR Routers

Following is an example of the show interfaces command for Cisco 7401ASR routers. In this example, the serial two interfaces (0 to 1) are on a port adapter in port adapter slot 1; also, most of the status information for each interface is omitted. (Interfaces are administratively shut down until you enable them.)

VIP in Cisco 7000 Series or Cisco 7500 Series Routers

Following is an example of the show interfaces command used with the VIP. In this example, the two serial interfaces (0 to 1) are on a port adapter in port adapter slot 1 of a VIP in interface processor slot 3; also, most of the status information for each interface is omitted. (Interfaces are administratively shut down until you enable them.)

Proceed to the next section, "Using the ping Command to Verify Network Connectivity," to check network connectivity of the PA-T3+ and switch or router.

Using the ping Command to Verify Network Connectivity

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

The ping command sends echo 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:

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

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

Using loopback Commands

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

Depending on the mode of the port, issuing the loopback command checks the following path:

• When no compact serial cable is attached to the PA-T3+ interface port, or if a DCE cable is attached to a port that is configured as line protocol up, the loopback command tests the path between the network processing engine and the interface port only (without leaving the network processing engine and port adapter).
  
  
• When a DTE cable is attached to the port, the loopback command tests the path between the network processing engine and the near (network processing engine) side of the DSU or modem to test the PA-T3+ interface and compact serial cable.
  
  

Table 4-9 provides examples of the loopback {dte | local | network {line | payload} | remote} command. The examples given are for interface 0 of a one-port PA-T3+ in port adapter slot 0 of a VIP in chassis slot 10 of a Cisco 7500 series router:

Posted: Tue Nov 12 15:13:56 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.