Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Support

Configuring the PA-F Port Adapter

Downloads

Table Of Contents

Configuring the PA-F

Using the EXEC Command Interpreter

Configuring the Interfaces

Shutting Down an Interface

Performing a Basic 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 ping Command to Verify Network Connectivity


Configuring the PA-F

To continue your PA-F-MM or PA-F-SM installation, you must configure the FDDI interfaces. The instructions that follow apply to all supported platforms. Minor differences between the platforms—for example, with Cisco IOS software commands—are noted.

This chapter contains the following sections:

•Using the EXEC Command Interpreter

•Configuring the Interfaces

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

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

Configuring the Interfaces

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

•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

If you installed a new PA-F 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-F 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-F, refer to the appropriate configuration publications listed in the "Related Documentation" section on page vi.

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

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

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

Table 5-1 Syntax of the shutdown Command 

Platform
Command
Example

Catalyst RSM/VIP2 in
Catalyst 5000 family switches

interface, followed by the type (fddi) and slot/port (port-adapter-slot-number/
interface-port-number)

The example is for interface 0 and interface 1 on a port adapter in port adapter slot 1. 

Router(config-if)# interface fddi 1/0

Router(config-if)# shutdown

Router(config-if)# interface fddi 1/1

Router(config-if)# shutdown

Ctrl-Z

Router#

Cisco 7200 series routers

interface, followed by the type (fddi) and slot/port (port-adapter-slot-number/
interface-port-number)

The example is for interface 0 and interface 1 on a port adapter in port adapter slot 6. 

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

Router(config-if)# shutdown

Router(config-if)# interface fddi 6/1

Router(config-if)# shutdown

Ctrl-Z

Router#

VIP in Cisco 7000 series or
Cisco 7500 series routers

interface, followed by the type (fddi) and slot/port adapter/port (interface-processor-slot-number/
port-adapter-slot-number/
interface-port-number)

The example is for interface 1 and interface 0 on a port adapter in port adapter slot 1 of a VIP installed
in interface processor slot 1. 

Router(config-if)# interface fddi 1/1/1

Router(config-if)# shutdown

Router(config-if)# interface fddi 1/1/0

Router(config-if)# shutdown

Ctrl-Z

Router#

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

Step 4 Write the new configuration to NVRAM as follows: 

Router# copy running-config startup-config

[OK]

Router#

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

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

Table 5-2 Examples of the show interfaces Command 

Platform
Command
Example

Catalyst RSM/VIP2 in Catalyst 5000 family switches

show interfaces fddi, followed by slot/port (port-adapter-slot-number/
interface-port-number)

The example is for interface 0 on a port adapter in port adapter slot 1. 

Router# show interfaces fddi 1/0


fddi 1/0 is administratively down, line 
protocol is down


[Additional display text omitted from 
this example]

Cisco 7200 series and
Cisco 7200 VXR routers

show interfaces fddi, followed by slot/port (port-adapter-slot-number/
interface-port-number)

The example is for interface 0 on a port adapter in port adapter slot 6. 

Router# show interfaces fddi 6/0


fddi 6/0 is administratively down, line 
protocol is down


[Additional display text omitted from 
this example]

VIP in Cisco 7000 series or
Cisco 7500 series routers

show interfaces fddi, followed by slot/port adapter/port (interface-processor-slot-number/
port-adapter-slot-number/
interface-port-number)

The example is for interface 0 on a port adapter in port adapter slot 1 of a VIP in interface processor slot 1. 

Router# show interfaces fddi 1/1/0


fddi 1/1/0 is administratively down, 
line protocol is down


[Additional display text omitted from 
this example]

Step 6 Reenable interfaces by doing the following:

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

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

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

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

Performing a Basic 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 FDDI 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# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#

Step 2 Specify the first interface to configure by entering the interface fddi subcommand, followed by the interface address of the interface you plan to configure. Table 5-3 provides examples.

Table 5-3 Examples of the interface fddi Subcommand 

Platform
Command
Example

Catalyst RSM/VIP2 in Catalyst 5000 family switches

interface fddi, followed by slot/port (port-adapter-slot-number/
interface-port-number)

The example is for the first interface of a port adapter in port adapter slot 0. 

Router(config)# interface fddi 0/0

Router(config-if)#

Cisco 7200 series and
Cisco 7200 VXR routers

interface fddi, followed by slot/port (port-adapter-slot-number/
interface-port-number)

The example is for the first interface of a
port adapter in port adapter slot 6. 

Router(config)# interface fddi 6/0

Router(config-if)#

VIP in Cisco 7000 series or
Cisco 7500 series routers

interface fddi, followed by slot/port adapter/port (interface-processor-slot-number/
port-adapter-slot-number/
interface-port-number)

The example is for the first interface of a
port adapter in port adapter slot 1 of a VIP in interface processor slot 1. 

Router(config)# interface fddi 1/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 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: 

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 show Commands to Verify the New Interface Status

Table 5-4 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the PA-F 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 vi.

Note The ouputs 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 5-4 Using show Commands 

Command
Function
Example

show version or
show hardware

Displays system hardware configuration, the number of each interface type installed, Cisco IOS software version, names and sources of configuration files, and boot images 

Router# show version

show controllers

Displays all the current interface processors and their interfaces 

Router# show controllers

show diag slot

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

Displays types of port adapters installed in your system and information about a specific port adapter slot, interface processor slot, or chassis slot 

Router# show diag 2

show interfaces type 0 or 1/
interface-port-number

Displays status information about a specific type of interface (for example, fddi) on a Catalyst RSM/VIP2 

Router# show interfaces fddi 1/0

show interfaces type port-adapter-slot-number/
interface-port-number

Displays status information about a specific type of interface (for example, fddi) in a Cisco 7200 series router 

Router# show interfaces fddi 1/0

show interfaces type interface-processor-
slot-number/port-adapter-slot-number/
interface-port-number

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

Router# show interfaces fddi 
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 displays indicate 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

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 ouputs 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 RSM/VIP2 in Catalyst 5000 Family Switches

Following is an example of the show version command from a Catalyst 5000 family switch with the PA-F: 

Router# show version

Cisco Internetwork Operating System Software 

IOS (tm) GS Software (RSP-JV-M), Released Version 11.1(6)CA [biff 101]

Copyright (c) 1986-1996 by cisco Systems, Inc.

Compiled Fri 10-May-96 16:20 by biff

Image text-base: 0x600108A0, data-base: 0x608DC000

ROM: System Bootstrap, Version 5.3(18168) [biff 61], RELEASED SOFTWARE

ROM: GS Software (RSP-BOOT-M), Released Version 11.1(6) [biff 103]

Router uptime is 20 hours, 34 minutes

System restarted by power-on

System image file is "slot0:zippy/biff/rsp-jv-mz.111.472", booted via slot0

cisco RSP2 (R4600) processor with 16384K bytes of memory.

R4600 processor, Implementation 32, Revision 2.0 

Last reset from power-on

G.703/E1 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).

Primary Rate ISDN software, Version 1.0.

Chassis Interface.

2 VIP2 controllers (8 Ethernet)(2 Fddi).

8 Ethernet/IEEE 802.3 interfaces.

2 FDDI network interfaces.

125K bytes of non-volatile configuration memory.

8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).

8192K bytes of Flash internal SIMM (Sector size 256K).

No slave installed in slot 6.

Configuration register is 0x0

Cisco 7200 Series Router

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

Router# show version


Cisco Internetwork Operating System Software

IOS (tm) 7200 Software (C7200-J-M), Version 11.1(6)CA [biff 105]

Copyright (c) 1986-1996 by cisco Systems, Inc.

Compiled Sun 21-Apr-95 12:22 by

Image text-base: 0x600088A0, data-base: 0x605A4000


ROM: System Bootstrap, Version 11.1(6) RELEASED SOFTWARE


Router uptime is 8 hours, 22 minutes

System restarted by reload

System image file is "slot0:c7200-j-mz.960421", booted via slot0


cisco 7200 (R4700) processor with 22528K/10240K bytes of memory.

R4700 processor, Implementation 33, Revision 1.0 (Level 2 Cache)

Last reset from power-on

Bridging software.

X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.

Chassis Interface.

4 Ethernet/IEEE 802.3 interfaces.

4 FDDI network interfaces.

125K bytes of non-volatile configuration 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 0x2

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

Router# show version

Cisco Internetwork Operating System Software 

IOS (tm) GS Software (RSP-JV-M), Released Version 11.1(6)CA [biff 101]

Copyright (c) 1986-1996 by cisco Systems, Inc.

Compiled Fri 10-May-96 16:20 by biff

Image text-base: 0x600108A0, data-base: 0x608DC000

ROM: System Bootstrap, Version 5.3(18168) [biff 61], RELEASED SOFTWARE

ROM: GS Software (RSP-BOOT-M), Released Version 11.1(6) [biff 103]

Router uptime is 20 hours, 34 minutes

System restarted by power-on

System image file is "slot0:zippy/biff/rsp-jv-mz.111.472", booted via slot0

cisco RSP2 (R4600) processor with 16384K bytes of memory.

R4600 processor, Implementation 32, Revision 2.0 

Last reset from power-on

G.703/E1 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).

Primary Rate ISDN software, Version 1.0.

Chassis Interface.

2 VIP2 controllers (8 Ethernet)(2 Fddi).

8 Ethernet/IEEE 802.3 interfaces.

2 FDDI network interfaces.

125K bytes of non-volatile configuration memory.

8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).

8192K bytes of Flash internal SIMM (Sector size 256K).

No slave installed in slot 6.

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 7200 series, and Cisco 7200 VXR series router and the interface processor slot in a Cisco 7000 series or Cisco 7500 series router with a VIP.

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

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

Catalyst RSM/VIP2 in Catalyst 5000 Family Switches

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

Router# show diag 0

Slot 0:

        Physical slot 0, ~physical slot 0xC, logical slot 0, CBus 0

        Microcode Status 0xC

        Master Enable, LED, WCS Loaded

        Board is analyzed 

        Pending I/O Status: Console I/O

        EEPROM format version 1

        VIP2 controller, HW rev 2.2, board revision UNKNOWN

        Serial number: 03507946  Part number: 73-1684-02

        Test history: 0x00        RMA number: 00-00-00

        Flags: cisco 7000 board; 7500 compatible

        EEPROM contents (hex):

          0x20: 01 15 02 02 00 35 86 EA 49 06 94 02 00 00 00 00

          0x30: 12 2B 00 2A 1A 00 00 00 00 00 00 00 00 00 00 00

        Slot database information:

        Flags: 0x4      Insertion time: 0x1988 (20:32:53 ago)

Cisco 7200 Series and Cisco 7200 VXR Routers

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

Router# show diag 4


Slot 4:

FDDI DAS (Multimode) port adapter, 1 port

Port adapter is analyzed

Port adapter insertion time 1d19h ago

Hardware revision 1.0           Board revision UNKNOWN

Serial number     1329897       Part number    73-1558-01

Test history      0x0           RMA number     00-00-00

EEPROM format version 1

EEPROM contents (hex):

	0x20: 01 0A 01 00 00 14 4A E9 49 06 16 01 00 00 00 00

	0x30: 07 1C 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-F in port adapter
slot 0 on a VIP in interface processor slot 3: 

Router# show diag 3

Slot 3:

        Physical slot 3, ~physical slot 0xC, logical slot 3, CBus 0

        Microcode Status 0xC

        Master Enable, LED, WCS Loaded

        Board is analyzed 

        Pending I/O Status: Console I/O

        EEPROM format version 1

        VIP2 controller, HW rev 2.2, board revision UNKNOWN

        Serial number: 03507946  Part number: 73-1684-02

        Test history: 0x00        RMA number: 00-00-00

        Flags: cisco 7000 board; 7500 compatible

        EEPROM contents (hex):

          0x20: 01 15 02 02 00 35 86 EA 49 06 94 02 00 00 00 00

          0x30: 12 2B 00 2A 1A 00 00 00 00 00 00 00 00 00 00 00

        Slot database information:

        Flags: 0x4      Insertion time: 0x1988 (20:32:53 ago)

        Controller Memory Size: 8 MBytes


        PA Bay 0 Information:

                FDDI PA, 1 ports

                EEPROM format version 1

                HW rev 1.0, Board revision 21

                Serial number: 03524551  Part number: 73-1630-01

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 FDDI interfaces.

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

Note The ouputs 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 RSM/VIP2 in Catalyst 5000 Family Switches

Following is an example of how the show interfaces [port adapter/port] command displays status information for the interfaces you specify. In these examples, most of the status information for each interface is omitted. In the following example, the show interfaces fddi port adapter/port command shows all of the information specific to the first FDDI port (interface port 0) in port adapter slot 0: 

Router# show interfaces fddi 0/0

Fddi0/0 is up, line protocol is up 

  Hardware is cxBus FDDI, address is 0000.0c0c.4444 (bia 0060.3e47.4360)

  Internet address is 14.0.0.2/8

  MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 10/255

  Encapsulation SNAP, loopback not set, keepalive not set

  ARP type: SNAP, ARP Timeout 04:00:00

  Phy-A state is connect, neighbor is Unknown, status QLS 

  Phy-B state is active, neighbor is A, status SILS

  ECM is in, CFM is c_wrap_b, RMT is ring_op,

  Requested token rotation 5000 usec, negotiated 0 usec

  Configured tvx is 2500 usec

  LER for PortA = 09, LER for PortB = 0C ring operational 11:36:23

  Upstream neighbor 0000.0c0c.8888, downstream neighbor 0000.0c0c.8888

  Last input 00:02:22, output 00:00:06, output hang never

  Last clearing of "show interface" counters 14:57:58

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 3922000 bits/sec, 147 packets/sec

  5 minute output rate 3962000 bits/sec, 148 packets/sec

     7523044 packets input, 631964210 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     7523554 packets output, 625092443 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

     0 transitions, 0 traces, 0 claims, 0 beacon

Cisco 7200 Series and Cisco 7200 VXR Routers

Following is an example of the show interfaces command for Cisco 7200 series and Cisco 7200 VXR routers. In this example, the eight serial interfaces (0 to 7) 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.) 

Router# show interfaces fddi 4/0

Fddi4/0 is up, line protocol is up 

  Hardware is MIF68840_MM, address is 1.1.1.10 (bia 0000.0000.0000)

  Internet address is 1.1.1.10

  MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 10/255

  Encapsulation SNAP, loopback not set, keepalive not set

  ARP type: SNAP, ARP Timeout 04:00:00

  Phy-A state is connect, neighbor is Unknown, status Q

  Phy-B state is active, neighbor is A, status H

  ECM is in, CFM is c_wrap_b, RMT is ring_op,

  Requested token rotation 5000 usec, negotiated 0 usec

  Configured tvx is 2500 usec

  LER for PortA = 09, LER for PortB = 0C ring operational 11:36:23

  Upstream neighbor 0000.0c0c.8888, downstream neighbor 0000.0c0c.8888

  Last input 00:02:22, output 00:00:06, output hang never

  Last clearing of "show interface" counters 14:57:58

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 3922000 bits/sec, 147 packets/sec

  5 minute output rate 3962000 bits/sec, 148 packets/sec

     7523044 packets input, 631964210 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     7523554 packets output, 625092443 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

     0 transitions, 0 traces,  0 claims, 0 beacon

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 eight serial interfaces (0 to 7) 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.) 

Router# show interfaces fddi 3/0/0

Fddi3/0/0 is up, line protocol is up 

  Hardware is cxBus FDDI, address is 0000.0c0c.4444 (bia 0060.3e47.4360)

  Internet address is 14.0.0.2/8

  MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 10/255

  Encapsulation SNAP, loopback not set, keepalive not set

  ARP type: SNAP, ARP Timeout 04:00:00

  Phy-A state is connect, neighbor is Unknown, status QLS 

  Phy-B state is active, neighbor is A, status SILS

  ECM is in, CFM is c_wrap_b, RMT is ring_op,

  Requested token rotation 5000 usec, negotiated 0 usec

  Configured tvx is 2500 usec

  LER for PortA = 09, LER for PortB = 0C ring operational 11:36:23

  Upstream neighbor 0000.0c0c.8888, downstream neighbor 0000.0c0c.8888

  Last input 00:02:22, output 00:00:06, output hang never

  Last clearing of "show interface" counters 14:57:58

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 3922000 bits/sec, 147 packets/sec

  5 minute output rate 3962000 bits/sec, 148 packets/sec

     7523044 packets input, 631964210 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     7523554 packets output, 625092443 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

     0 transitions, 0 traces, 0 claims, 0 beacon

Proceed to the next section, "Using the ping Command to Verify Network Connectivity," to check network connectivity of the PA-F 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 on page vi 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.