|
|
Product Numbers: PA-4R and PA-4R=
This configuration note describes the installation and configuration of the PA-4R(=) Token Ring port adapter. The port adapter is used in the Catalyst VIP2-15 and VIP2-40 modules attached to the Route Switch Module (RSM) and used in the Catalyst 5000 series switches. The port adapter can also be used in the following:
Use this configuration note with the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your VIP2-15 and VIP2-40.
For complete descriptions of interface subcommands and the configuration options available for interfaces that support 4R port adapter functionality, refer to the publications listed in the "If You Need More Information" section.
This configuration note is organized into the following sections:
The Cisco IOS software that runs your router contains extensive features and functionality. For additional information on configuring the Catalyst VIP2 port adapter interfaces, refer to the following documentation:
The 4R port adapter requires that the host RSM runs Cisco IOS Release 11.2(9)P or later and that the supervisor engine runs Catalyst 5000 series supervisor engine software release 2.3(1) or later.
A Catalyst VIP2-15 (1-MB SRAM and 16-MB DRAM) is recommended for the 4R port adapter. Note that there is a Catalyst VIP2-40 available (2-MB SRAM and 32-MB DRAM).
Follow the safety guidelines in this section when working with any equipment that connects to electrical power or telephone wiring.
Follow these basic guidelines when working with any electrical equipment:
ESD damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. Port adapters and the Catalyst VIP2 comprise printed circuit boards that are fixed in metal carriers. Electromagnetic interference (EMI) shielding and connectors are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use a preventive antistatic strap during handling.
Follow these guidelines to prevent ESD damage:
![]() | Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms. |
The following sections describe Token Ring specifications, physical connections, connection equipment, and cables and connectors.
Token Ring refers to both IBM's Token Ring Network, which IBM developed in the 1970s, and to IEEE 802.5 networks. The IEEE 802.5 specification was modeled after, and still closely shadows, IBM's network. The two types are compatible, although the specifications differ slightly.
Token Ring and IEEE 802.5 are token passing networks, which move a small frame, called a token, around the network. Possession of the token grants the right to transmit; a station with information to transmit must wait until it detects a free token passing by.
The IBM Token Ring specifies a star topology, with all end stations connected through a device called a multistation access unit (MSAU). IEEE 802.5 does not specify any topology, although most implementations are based on a star configuration with end stations attached to a device called a media access unit (MAU). Also, IBM Token Ring specifies twisted-pair cabling, whereas IEEE 802.5 does not specify media type. Most Token Ring networks use shielded twisted-pair (STP) cabling; however, some networks that operate at 4 Mbps use unshielded twisted-pair (UTP) cable.
Table 1 shows a comparison of the two types.
| Network Type | Data Rates | Stations/ Segment | Topology | Media | Signaling | Access Method | Encoding |
|---|---|---|---|---|---|---|---|
IBM Token Ring network | 4, 16 Mbps | 260 STP | Star | Twisted-pair | Baseband | Token passing | Differential Manchester |
IEEE 802.5 network | 4, 16 Mbps | 250 | Not | Not | Baseband | Token passing | Differential Manchester |
All 4R port adapter interfaces support both 4- and 16-Mbps, half-duplex operation and early token release. The default for all ports is for 4-Mbps operation and early token release disabled. Both states are enabled with configuration commands in Configuration mode.
To enable 16 Mbps, specify the interface type/port adapter slot/interface port number and use the configuration command ring-speed 16; to return to 4-Mbps operation, use the command ring-speed 4. To enable and disable early token release, specify the interface type/port adapter slot/interface port number and use the configuration command [no] early token release. For complete descriptions and examples of software commands, refer to the related software configuration documentation.
In the typical Token Ring network shown in Figure 1, lobe cables connect each Token Ring station (4R port adapter interface) to the MSAU (or MAU), and patch cables connect adjacent MSAUs (or MAUs) to form one large ring.

You will need an IEEE 802.5 MAU or an MSAU to provide the interface between the 4R port adapter Token Ring interfaces and the external ring, and a Token Ring lobe cable between each 4R port adapter interface and the MAU or MSAU. Lobe cables connect each Token Ring station (4R port adapter interface) to the MAU or MSAU, and patch cables can connect adjacent MSAUs to form one large ring.
4R port adapter interfaces operate at either 4 or 16 Mbps. The default speed for all 4R port adapter interfaces is 4 Mbps, which you can change to 16 Mbps on any port using the ring-speed n configuration command, where n is the speed (4 or 16) in Mbps. The speed of each Token Ring port must match the speed of the ring to which it is connected. Before you enable the Token Ring interfaces, ensure that each is set for the correct speed, or it can bring down the ring.
![]() | Caution Each 4R port adapter interface must be configured for the same ring speed as the ring to which it is connected, either 4 or 16 Mbps. If the port is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable. |
The maximum transmission distance is not defined for IEEE 802.5 (Token Ring) networks. STP cabling is most commonly used for rates of 4 and 16 Mbps. Twisted-pair cabling is more susceptible to interference than other types of cabling; therefore, you should plan accordingly for your network length and repeater spacing.
Before you install the 4R port adapter, determine the ring speed (4 or 16 Mbps) of each ring to be connected to the server. There is no factory default for the interface speed; you must set the speed of each interface (within the setup command facility or with the ring-speed command) before you bring the interface up and insert it into the ring with the no shutdown command.
![]() | Caution Each Token Ring port must be configured for the same ring speed as the ring to which it is connected; either 4 or 16 Mbps. If the port is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable. |
The 4R port adapter provides up to four IBM Token Ring or IEEE 802.5 Token Ring interfaces. Each Token Ring interface can be set for 4 or 16 Mbps. All Token Ring ports are half duplex (only) and run at wire speed.
The following sections discuss the 4R port adapter, which is shown in Figure 2.

Figure 3 shows a Catalyst VIP2 with one installed port adapter and one port adapter blank. Port adapters have handles that allow for easy installation and removal. The left port adapter is in port adapter slot 0, and the port adapter blank is in port adapter slot 1.

The 4R port adapter has several LEDs that indicate status of the port adapter and its interfaces. The 4R port adapter's enabled LED (shown in Figure 4) goes on to indicate the following status of the 4R port adapter:
If any of these conditions is not met, or if the initialization fails for other reasons, the port adapter's enabled LED does not go on.

When a Token Ring interface is configured by using software commands, the In Ring and 4/16-Mbps LEDs (shown in Figure 4) indicate the following for each port:
A network interface cable provides the connection between the 9-pin Token Ring receptacles on the 4R port adapter and an MAU. The 9-pin connector at the 4R port adapter end and the MAU connector at the network end are described in the "Token Ring Connection Equipment" section on page 7.
The Token Ring ports on the 4R port adapter are DB-9 (PC type) receptacles that require Type 1 or Type 3 lobe cables. Token Ring interface cables are not available from Cisco, but are commercially available through outside cable vendors.
Type 1 lobe cables use STP cable and terminate at the network end with a large MAU plug. (See Figure 5.) The 4R port adapter end of the cable is a DB-9 plug.

Type 3 lobe cables use either STP or UTP cable and terminate at the network end with an RJ-11 plug. (See Figure 6.) The 4R port adapter end of the cable is a DB-9 plug.

Table 2 lists the pinouts for the DB-9 receptacle used on the 4R port adapter.
| Pin | Signal |
|---|---|
1 | Ring-In B |
5 | Ring-Out A |
6 | Ring-In A |
9 | Ring-Out B |
10 and 11 | Ground |
The following sections describe how to install the 4E port adapter.
The 4R port adapter is used on the Catalyst VIP2, and can be installed in either port adapter slot 0 or port adapter slot 1.
![]() | Caution To prevent system problems, do not remove port adapters from the RSM/VIP2 combination or attempt to install other port adapters in the Catalyst VIP2 while the RSM/VIP2 combination is installed in the switch. To install or replace port adapters, first remove the RSM/VIP2 combination from its switch slot. |
Each port adapter circuit board mounts to a metal carrier and is sensitive to ESD damage. The following procedures should be performed by a Cisco-certified service provider only. While the RSM/VIP2 combination supports online insertion and removal (OIR), individual port adapters do not. To replace port adapters, you must first remove the RSM/VIP2 from the chassis, and then install or replace port adapters as required. If a blank port adapter is installed in the Catalyst VIP2 in which you want to install a new port adapter, you must first remove the RSM/VIP2 combination from the chassis, and then remove the blank port adapter.
When only one port adapter is installed in a Catalyst VIP2, a blank port adapter must fill the empty slot to allow the Catalyst VIP2 and switch chassis to conform to EMI emissions requirements, and to permit proper airflow through the chassis. If you plan to install a new port adapter, you must first remove the blank port adapter.
Follow this procedure to remove and replace any type of port adapter on the Catalyst VIP2:
Step 1 Attach an ESD-preventive wrist strap between you and an unfinished chassis surface or to the ESD connector on the switch.
Step 2 For a new port adapter installation or a port adapter replacement, first disconnect any interface cables from the ports on the front of the port adapter.
Step 3 To remove the RSM/VIP2 combination from the chassis, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
Step 4 Place the removed RSM/VIP2 on an antistatic mat.
Step 5 Locate the screw at the rear of the port adapter (or blank port adapter) to be replaced (see Figure 7). This screw secures the port adapter (or blank port adapter) to its slot.

Step 6 Remove the screw that secures the port adapter (or blank port adapter).
Step 7 With the screw removed, grasp the handle on the front of the port adapter (or blank port adapter) and carefully pull it out of its slot, away from the edge connector at the rear of the slot (see Figure 8).

Step 8 If you removed a port adapter, place it in an antistatic container for safe storage or shipment back to the factory. If you removed a blank port adapter, no special handling is required; store the blank port adapter for potential future use.
Step 9 Remove the new port adapter from its antistatic container and position it at the opening of the slot (see Figure 9).
![]() | Caution To prevent jamming the carrier between the upper and lower edges of the port adapter slot, and to ensure that the edge connector at the rear of the port adapter mates with the connector at the rear of the port adapter slot, make certain that the leading edges of the carrier are between the upper and lower slot edges, as shown in Figure 9. |

Step 10 Before you insert the new port adapter in its slot, verify that the port adapter carrier is between the upper and lower slot edges, as shown in Figure 10. Do not jam the carrier between the slot edges.
![]() | Caution To ensure a positive ground attachment between the port adapter carrier and the Catalyst VIP2 port adapter slot, and to ensure that the connectors at the rear of the port adapter slot mate properly, make certain the carrier is between the upper and lower slot edges, as shown in Figure 10. |
Step 11 Carefully slide the new port adapter into the port adapter slot until the connector on the port adapter completely mates with the connector on the motherboard.

Step 12 Install the screw in the rear of the port adapter slot (see Figure 7 for its location). Do not overtighten this screw.
Step 13 To replace the RSM/VIP2 combination in the chassis, follow the steps in the "RSM and Catalyst VIP2 Installation" section in the Route Switch Module Catalyst VIP2-15 and VIP2-40 Installation and Configuration Note (Document Number 78-4780-01), which shipped with your Catalyst VIP2.
Step 14 Reconnect the interface cables to the port adapter ports.
This completes the procedure for installing a new port adapter or replacing a port adapter in a Catalyst VIP2.
The Token Ring ports on the 4R port adapter run at either 4 or 16 Mbps. You need one Token Ring interface cable for each 4R port adapter interface you want to use. Token Ring interface cables are not available from Cisco, but are commercially available through outside cable vendors. Port adapters have a handle attached (see Figure 9), but this handle is not shown in Figure 11 to allow a full view of detail on the 4R port adapter's faceplate.
Follow this procedure for attaching Token Ring cables to the 4R port adapter:
Step 1 Determine which 4R port adapter ports you want to use.
Step 2 Attach the port adapter end of a Token Ring interface cable, or other connection equipment, to the interface port. (See Figure 11).

![]() | Caution Each 4R port adapter interface must be configured for the same ring speed as the ring to which it is connected; either 4 or 16 Mbps. If the 4R port adapter interface is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable. |
Step 3 Attach the network end of the Token Ring interface cable to the appropriate Token Ring equipment at your site: a MAU or MSAU.
This completes the procedure for attaching interface cables to the 4R port adapter.
After you verify that the new 4R port adapter is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. You need the following information:
For a summary of the configuration options available and instructions for configuring the 4R interfaces on the Catalyst VIP2, refer to the appropriate configuration publications listed in the "If You Need More Information" section on page 2.
In the RSM, physical port addresses specify the actual physical location of each interface port on the Catalyst VIP2. This physical location is identified by interface type/port adapter slot/interface port number.
On the Catalyst VIP2, the first port adapter slot number is always 0. The second port adapter slot number is always 1. The individual interface port numbers always begin with 0. The number of additional ports depends on the number of ports on a port adapter.
For example, the four 4R interface ports on a 4R port adapter in port adapter slot 0 appear as follows: TokenRing0/0, TokenRing0/1, TokenRing0/2, and TokenRing0/3. If the 4E port adapter was in port adapter slot 1, these same interface ports would be numbered TokenRing1/0 through TokenRing1/3. Port adapters can occupy either port adapter slot. There are no restrictions.
You can identify interface ports by physically checking the port adapter interface port location on the Catalyst VIP2 or by using the show interface command to display information about a specific interface or all interfaces in the router.
You can modify the configuration of your router through the EXEC software command interpreter. 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 to 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:
Router> enable
Password:
Step 2 Enter the password (the password is case-sensitive). For security purposes, the password is not displayed.
Step 3 When you enter the correct password, the system displays the privileged-mode system prompt (#):
Router#
To configure Token Ring interfaces using the setup EXEC command facility, follow the instructions in the "Using the Setup Command Facility" section. To configure the Token Ring interfaces by using the configure EXEC command, follow the instructions in the "Configuring Interfaces Using the Configure Command" section.
The setup command facility identifies all interfaces (including the Token Ring interfaces for the ports on the 4R port adapter) that are installed and prompts you for configuration information for each installed interface. When you finish configuring one interface, the setup command prompts you for the next, continuing until each interface has been configured.
When you enter the setup command after first-time startup, you must run through the entire dialog until you come to the interface you want to change. Note that when you use the setup command after first-time startup, the default values indicated within the brackets in the System Configuration Dialog are the values last set using the setup command or left as defaults.
After you choose to continue with the setup command (by answering yes to the system configuration dialog prompt), the remainder of the script is the actual configuration process. The dialog prompts you first for global system parameters, and then for configuration information for each interface. The existing configuration is displayed as the default, in brackets ([ ]), at the end of each prompt. Press Return to accept the default settings.
Follow this procedure for using the setup facility to configure the 4R Token Ring interfaces:
Step 1 After you access the privileged level of the EXEC, as described in the "Using the EXEC Command Interpreter" section on page 17, enter the setup command to begin the setup facility:
Router# setup
Step 2 The following script is displayed on the screen, with the name of your router as the default in the brackets.
-System Configuration Dialog-
At any point you may enter a question mark `?' for help.
Refer to the `Getting Started' Guide for additional help.
Default settings are in square brackets `[]'.
Continue with configuration dialog? [yes]: (Use Ctrl-c to abort configuration at any prompt)
Configuring global parameters:
Enter host name [Router]: sandbox
Step 3 To accept the default and keep the router name, press Return. (If you do want to change the name of the router, enter the new name before pressing Return.)
Step 4 Proceed through the remainder of the global parameter prompts, using the Return key to accept the defaults.
After the global parameters are configured, the system prompts you for interface configuration information, one interface at a time. Following is a partial display of the script for a previously configured interface:
Configuring interface parameters:
Configuring interface Token Ring0:
Is this interface in use [yes]:
Tokenring ring speed (4 or 16) [16]
Configure IP on this interface? [yes]:
IP address for this interface: 1.1.1.30
(remainder of display text omitted)
![]() | Caution Each 4R port adapter interface must be configured for the same ring speed as the ring to which it is connected; either 4 or 16 Mbps. If the 4R port adapter interface is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable. |
Step 5 To accept the default at each prompt and retain the existing configuration information, press the Return key. When you reach the scripts for configuring new interfaces, enter the new configuration information at each prompt.
When all interfaces are configured, the system displays the entire configuration script followed by a prompt for which there is no default (you must enter yes or no):
Use this configuration [yes/no]:
Step 6 To use the configuration you created, enter yes. To discard the configuration file and begin the configuration process again, enter no.
If you entered yes at the prompt, the following message is displayed:
Press RETURN to get started!
The configuration process is complete. Proceed to the section "Checking the Configuration" on page 20. It provides show commands you can use to display and verify the configuration information.
Follow the instructions in this section for a basic configuration using the configure command: enabling an interface, setting interface ring speed, and specifying IP routing. You might also need to enter other configuration subcommands depending upon the requirements for your system configuration. 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>
Use this example of a basic configuration procedure:
Step 1 After you access the privileged level of the EXEC as described in the "Using the EXEC Command Interpreter" section on page 17, enter the configure terminal command:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z.
Step 2 Specify the first Token Ring interface to configure by entering the subcommand interface interface type/port adapter slot/interface port number. For example, if you are configuring Token Ring interface 0 for a 4R port adapter installed in port adapter slot 0, enter the following command:
Router(config)# interface tokenring 0/0
Step 3 If IP routing is enabled on your system, you can assign an IP address and subnet mask to the interface with the ip address configuration subcommand as follows:
Router(config-int)# ip address ip address subnet mask
![]() | Caution Each Token Ring port must be configured for the same ring speed as the ring to which it is connected; either 4 or 16 Mbps. If the port is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down and makes it inoperable. |
Step 4 Change the default shutdown state and enable the interface:
Router(config-int)# no shutdown
When you enable the interface by using the no shutdown command, the LED for 4 or 16 Mbps is turned on after approximately 5 seconds. The In Ring LED for that interface is turned on approximately 5 to 18 seconds later, when the port is initialized and connected to the ring.
Step 5 Either accept the default ring speed of 4 Mbps, or enable the Token Ring interface speed for 16-Mbps operations as follows:
Router(config-int)# ring-speed 16
Step 6 Enter any additional configuration subcommands required.
Step 7 Repeat Steps 2 through 6 for each new interface.
Step 8 When all new interfaces are configured, press CNTL/Z.
Step 9 Write the new configuration to nonvolatile memory by entering the following:
Router# copy running-config startup-config [OK] Router#
Step 10 Enter quit to exit Configuration mode:
Router# quit
You have now completed configuring the Token Ring interfaces. Check the configuration as described in the "Checking the Configuration" section.
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces and the ping command to check connectivity. Refer to the publications listed in the "If You Need More Information" section on page 2 for detailed command descriptions and examples.
After configuring the new interface(s) using either the setup command or the configure command, use the EXEC show commands to display status information.
Step 1 To display the current system configuration file, enter the show configuration command:
Router# show configuration
The configuration file for the router is displayed. Check the Token Ring configuration information in the display.
Step 2 To display and check all interfaces, enter the following command:
Router# show interfaces
To display information about a specific interface, use the show interfaces command with the interface type and port address in the format show interfaces interface type/port adapter slot/interface port number.
Verify that each new Token Ring interface appears. Each interface is listed along with its assigned IP address. The first line of display specifies the port adapter slot and interface port number. It indicates whether the hardware is functional and if the line protocol is up or down. If the line protocol is down (and you did not administratively shut it down), or if the hardware is not functioning properly, ensure that the network interface is properly connected and terminated.
Router# sh int tokenring 0/0 TokenRing0/0 is administratively down, line protocol is down Hardware is cyBus TokenRing, address is 0000.0ca5.2300 (bia 0000.0ca5.2389) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) Router# sh int tokenring 0/1 TokenRing0/1 is administratively down, line protocol is down Hardware is cyBus TokenRing, address is 0000.0ca5.2300 (bia 0000.0ca5.238a) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) Router# sh int tokenring 0/2 TokenRing0/2 is administratively down, line protocol is down Hardware is cyBus TokenRing, address is 0000.0ca5.2300 (bia 0000.0ca5.238b) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) Router# sh int tokenring 0/3 TokenRing0/3 is administratively down, line protocol is down Hardware is cyBus TokenRing, address is 0000.0ca5.2300 (bia 0000.0ca5.238b) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec)
Step 3 Detailed port adapter information is displayed using the show diag command, as shown in the following example of two 4R port adapters:
Router# show diag
Slot 0:
Physical slot 0, ~physical slot 0xF, logical slot 0, CBus 1
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: Console I/O, Debug I/O
EEPROM format version 1
C5IP controler, HW rev 1.0, board revision A0
Serial number: 00000001 Part number: 00-0000-01
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 1C 01 00 00 00 00 01 00 00 00 01 00 00 00 00
0x30: 50 00 00 00 00 00 00 00 00 00 00 78 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0xFAC (17:24:40 ago)
Slot 7:
EEPROM format version 1
Route/Switch Processor 2, HW rev 1.0, board revision A0
Serial number: 00000001 Part number: 00-0000-01
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 1C 01 00 00 00 00 01 00 00 00 01 00 00 00 00
0x30: 50 00 00 00 00 00 00 00 00 00 00 78 00 00 00 00
.
.
.
PA Bay 0 Information:
Token Ring PA, 4 ports
EEPROM format version 1
HW rev 1.1, Board revision 0
Serial number: 02827613 Part number: 73-1390-04
PA Bay 1 Information:
Token Ring PA, 4 ports
EEPROM format version 1
HW rev 1.1, Board revision 88
Serial number: 02023786 Part number: 73-1390-04
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 and Catalyst VIP2 have booted successfully and are operational, you can use this command to verify the status of interface ports.
The ping command sends an echo request 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 messages (timed out) or (failed) indicate that the connection failed.
Following is an example of a successful ping command to a remote server with the address 1.1.1.10:
Router# ping 1.1.1.10 <Return> Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 1.1.1.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms Router# If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.
For complete descriptions of interface subcommands and the configuration options available for Catalyst VIP2-related interfaces that support Catalyst VIP2 functionality, refer to the publications listed in the "If You Need More Information" section on page 2.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Jul 26 09:43:04 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.