|
|
Product Number: PA-4R-FDX(=)
This configuration note describes the installation and configuration of the full-duplex Token Ring port adapter (PA-4R-FDX). 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 Catalyst VIP2-15 and VIP2-40.
For complete descriptions of interface subcommands and the configuration options available for interfaces that support 4R-FDX 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. The effective use of many of these features is easier if you have more information at hand. For additional information on configuring the Catalyst VIP2 port adapter interfaces, refer to the following documentation:
The 4R-FDX 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-FDX port adapter. Note that there is a Catalyst VIP2-40 available (2-MB SRAM and 32-MB DRAM).
The PA-4R-FDX port adapter supports full-duplex operation. (The PA-4R port adapter does not support full-duplex operation.)
To determine if a Token Ring interface installed in your system supports full-duplex operation, use the show interfaces tokenring command. If the interface does not support full-duplex, the following message is displayed, and no changes are made to the interface:
%TokenRing0/0 interface does not support full-duplex.
If you do not have the appropriate Cisco IOS software release and 4R-FDX port adapter installed in your system, you cannot configure full-duplex operation. For specific full-duplex configuration requirements, refer to the "Configuring Full-Duplex Operation" section on page 21.
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.
The term 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 resembles, 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) for half duplex or a Token Ring switch for full duplex. IEEE 802.5 does not specify any topology, although most implementations use a star configuration with end stations attached to a device called a media access unit (MAU) for half duplex or a Token Ring switch for full duplex. Also, IBM Token Ring specifies twisted-pair (STP) cabling, whereas IEEE 802.5 does not specify media type. Most Token Ring networks use shielded twisted-pair 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-FDX port adapter interfaces support both 4- and 16-Mbps, half-duplex and full-duplex operation and early token release. The default for all ports is for half-duplex 4-Mbps operation with 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. To enable full-duplex operation, specify the interface type/port adapter slot/interface port number and use configuration command full-duplex. To return to half-duplex operation, use the no full-duplex or half-duplex command. For complete descriptions and examples of software commands, refer to the related software configuration documentation.
In the typical half-duplex Token Ring network, lobe cables connect each Token Ring station (4R-FDX port adapter interface) to the MSAU (or MAU), and patch cables connect adjacent MSAUs (or MAUs) to form one large ring. (See Figure 1.)
In the typical full-duplex Token Ring network, lobe cables connect each Token Ring station (4R-FDX port adapter interface) to the Token Ring switch, and patch cables connect adjacent Token Ring switches to form one large ring. (Refer to Figure 2.)
To provide the interface between the 4R-FDX port adapter Token Ring interface and the external ring, you need an IEEE 802.5 MAU, MSAU, or a Token Ring switch. You also need a Token Ring lobe cable between each 4R-FDX port adapter interface and the MAU, MSAU, or the Token Ring switch. Lobe cables connect each Token Ring station (4R-FDX port adapter interface) to the MAU, MSAU, or Token Ring switch. Patch cables can connect adjacent MSAUs or Token Ring switches to form one large ring.
4R-FDX port adapter interfaces operate at either 4 or 16 Mbps. The default speed for all 4R-FDX port adapter interfaces is 4 Mbps, which you can change to 16 Mbps on any port by 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 you risk bringing down the ring.
| Caution Each 4R-FDX 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 causes the ring to beacon, which effectively brings the ring down. |
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, network length and repeater spacing must be planned accordingly.
Before you install the 4R-FDX 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 connects; 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. |
The 4R-FDX port adapter shown in Figure 3 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, half-duplex or full-duplex operation. All Token Ring ports run at wire speed.
You can install the 4R-FDX port adapter in either port adapter slot 0 or port adapter slot 1. Figure 4 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-FDX port adapter has several LEDs that indicate status of the port adapter and its interfaces. The 4R-FDX port adapter's enabled LED (shown in Figure 5) goes on to indicate the following status of the 4R-FDX 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 5) indicate the following for each port:
A network interface cable provides the connection between the 4R-FDX port adapter 9-pin Token Ring receptacles and a MAU or Token Ring switch. The 9-pin connector at the 4R-FDX port adapter end and the MAU or Token Ring switch connector at the network end are described in the "Token Ring Connection Equipment" section on page 8.
The Token Ring ports on the 4R-FDX 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 6.) The 4R-FDX 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 7.) The 4R-FDX 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-FDX port adapter.
| Pin | Signal |
|---|---|
1 | Ring-In B |
5 | Ring-Out A |
6 | Ring-In A |
9 | Ring-Out B |
10 and 11 | Ground |
This section describes how to install the 4R-FDX port adapter.
| Caution To prevent system problems, do not remove port adapters from the Catalyst VIP2 or attempt to install other port adapters in the Catalyst VIP2 while the system operates. To install or replace port adapters, first remove the RSM/VIP2 combination from its switch slot. |
Each port adapter circuit board is mounted 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 combination from the chassis, and then install or replace port adapters as required. If a blank port adapter is installed on 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 in 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 8). 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 9).
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 10).
| 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 10. |
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 11. 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 11. |
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 8 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.
You need one Token Ring interface cable for each 4R-FDX port adapter interface you want to use. Token Ring interface cables are not available from Cisco but are commercially available from outside cable vendors.
Use this procedure for attaching Token Ring cables to the 4R-FDX port adapter:
Step 1 Determine which 4R-FDX 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 12).
| Caution Each 4R-FDX port adapter interface must be configured for the same ring speed as the ring to which it connects; either 4 or 16 Mbps. If the 4R-FDX port adapter interface is set for a different speed, it will cause the ring to beacon, which effectively brings the ring down. |
Step 3 Attach the network end of the Token Ring interface cable to the appropriate Token Ring equipment at your site: a MAU, MSAU, or Token Ring switch.
This completes the procedure for attaching a 4R-FDX interface cable.
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#
If you installed a new 4R-FDX-equipped Catalyst VIP2 or if you want to change the configuration of an existing interface, you must use the privileged-level configure command. If you replaced a previously configured 4R-FDX port adapter, the system recognizes the new 4R-FDX port adapter interfaces and brings them up in their existing configurations.
After you verify that the new 4R-FDX port adapter is installed correctly (the enabled LED goes on), use the configure command to configure the new interfaces. Be prepared with the information you need, such as the following:
For complete descriptions of interface subcommands and the configuration options available for Catalyst VIP2-related interfaces, refer to the 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 addresses for the 4R-FDX interface ports on the first port adapter in a Catalyst VIP2 are 0/0 through 0/3 (port adapter slot 0 and interface ports 0 through 3). If the 4R-FDX port adapter was installed in port adapter slot 1, the interface addresses would be 1/0 through 1/3.
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.
Before you replace an interface cable, replace port adapters, or remove an interface, use the shutdown command to disable the interfaces. Doing so prevents anomalies from occurring when you reinstall the new or reconfigured Catalyst VIP2. You can shut down individual interfaces by specifying the port adapter number and interface port number. When you shut down an interface, it is designated administratively down in the show interface command display.
Follow these steps to shut down an interface:
Step 1 Enter the privileged level of the EXEC command interpreter. (Refer to 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:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 3 Specify the port address of the controller that you want shut down by entering the subcommand controller, followed by the type (tokenring) and port adapter number/interface port number. This example is for a 4R-FDX port adapter in port adapter slot 1:
Router(config)# controller tokenring 1/0
Step 4 Enter the shutdown command as follows:
Router(config-cont)# shutdown
Step 5 Write the new configuration to memory as follows:
Router# copy running-config startup-config [OK] Router#
The system displays an OK message when the configuration is stored.
Step 6 To verify that new interfaces are now in the correct state (shutdown), use the show interface tokenring port adapter number/interface port number command to display the specific interface.
Router# show int tokenring 1/0 TokenRing1/0 is down, line protocol is down Hardware is cxBus Token Ring, address is 0000.0000.0000 (bia 0000.0000.0000) [display text omitted]
Step 7 To reenable the interfaces, repeat the previous steps, but use the no shutdown command in Step 4; then write the new configuration to memory, as follows:
Router(config)# int tokenring 1/0 Router(config-int)# no shutdown CNTL/Z Router# Router# copy running-config startup-config [OK] Router# show int tokenring 1/0 TokenRing1/0 is up, line protocol is up Hardware is cxBus Token Ring, address is 0000.0000.0000 (bia 0000.0000.0000) [display text omitted]
For complete descriptions of software configuration commands, refer to the publications listed in the "If You Need More Information" section on page 2.
The following instructions are 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 and the protocols you plan to route on the interface. For complete descriptions of configuration subcommands and the configuration options available, refer to the publications listed in the "If You Need More Information" section on page 2.
Press the Return key after each step unless otherwise noted. You can exit the privileged level at any time and return to the user level by entering disable at the prompt as follows:
Router# disable Router>
The following example shows how to perform a basic configuration procedure:
Step 1 At the privileged-mode prompt, enter Configuration mode and specify that the console terminal is the source of the configuration subcommands, as follows:
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 2 At the prompt, specify the first Token Ring interface to configure by entering the subcommand interface followed by tokenring, and port adapter number/interface port number. The following example is for the 4R-FDX in port adapter slot 0 and interface port 0:
Router(config)# interface tokenring 0/0
Step 3 If IP routing is enabled on the 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 1.1.1.10 255.255.255.0
| 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 to up and enable the interface, as follows:
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 to enable routing protocols and set the interface characteristics.
Step 7 Repeat Step 2 through Step 6 for each new interface.
Step 8 When all new interfaces are configured, press CNTL/Z (hold the Control key down and press the Z key) to exit Configuration mode.
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 completed configuring the Token Ring interfaces. To check the configuration, proceed to the "Checking the Configuration" section.
Full-duplex operation requires a 4R-FDX port adapter and a host router running a specific level of Cisco IOS software. (Refer to the "Software and Hardware Requirements" section on page 3.)
Full-duplex operation is not the default configuration and must be turned on using the full-duplex command. To turn off full-duplex operation and reset the interface, use the no full-duplex or half-duplex command.
An example of configuring a 4R-FDX interface for full-duplex operation using the full-duplex command follows:
Router# conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# int tokenring 0/0 Router(config-if)# full-duplex CNTL/Z Router#
The output of the show interfaces tokenring port adapter number/interface port number command displays the state of the Token Ring port adapter interface and the state of full-duplex operation. Following is a partial sample output of this command from a 4R-FDX interface with full-duplex operation enabled:
Router# show int tokenring 0/0 TokenRing0/0 is up, line protocol is up Hardware is cxBus Token Ring, address is 0000.0000.0000 (bia 0000.0000.0000) Internet address is 14.0.0.2/8 MTU 4464 bytes, BW 1600 Kbit, DLY 630 usec, rely 255/255, load 1/255 Encapsulation SNAP, loopback not set, keepalive not set ARP type: SNAP, ARP Timeout 04:00:00 Ring speed: 16 Mbps, operating in full-duplex [display text omitted]
operating in half-duplex.
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.
The following steps use show commands to verify that the new interfaces are configured and operating correctly.
Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new interfaces.
Step 2 Display all interfaces with the show controllers cbus command.
Step 3 Specify one of the new interfaces with the show interfaces interface type/port adapter number/interface port number command and verify that the interface and line protocol are in the correct state: up or down.
Step 4 Display the protocols configured for the entire system and specific interfaces with the show protocols command. If necessary, return to Configuration mode to add or remove protocol routing on the system or specific interfaces.
Step 5 Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM by using the show startup-config command. Verify that the configuration is accurate for the system and each interface.
If the interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a service representative for assistance.
To display information about a specific interface, use the show interfaces command with the interface type, port adapter, and interface port address in the format show interfaces interface type/port adapter number/interface port number. To display information about all interfaces installed in the system, use the show interfaces command without arguments.
The following example of the show interfaces tokenring port adapter number/interface port number command displays information specific to the first 4R-FDX interface port (port 0) in port adapter slot 0:
Router# sh int tokenring 0/0 TokenRing0/0 is up, line protocol is up Hardware is cxBus Token Ring, address is 0000.0000.0000 (bia 0000.0000.0000) Internet address is 14.0.0.2/8 MTU 4464 bytes, BW 1600 Kbit, DLY 630 usec, rely 255/255, load 1/255 Encapsulation SNAP, loopback not set, keepalive not set ARP type: SNAP, ARP Timeout 04:00:00 Ring speed: 16 Mbps, operating in full-duplex [display text omitted]
Router# show version Cisco Internetwork Operating System Software IOS (tm) C5RSM Software (C5RSM-JSV-M), Version 11.2(9)P Copyright (c) 1986-1997 by cisco Systems, Inc. Compiled Tue 24-Jun-97 17:09 by shj Image text-base: 0x600108E0, data-base: 0x6095E000 ROM: System Bootstrap, Version 11.2(15707) BOOTFLASH: C5RSM Software (C5RSM-JSV-M), Version 11.2 yosemite_3 uptime is 17 hours, 17 minutes System restarted by reload System image file is "dirt/yosemite/c5rsm-jsv-mz.7P", booted via tftp from 223.2 55.254.254 cisco RSP2 (R4700) processor with 32768K bytes of memory. R4700 processor, Implementation 33, Revision 1.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. 1 EIP controller (6 Ethernet). 1 TRIP controller (4 Token Ring). 2 MIP controllers (4 E1). 1 VIP2 controller (2 E1)(4 Token Ring). 6 Ethernet/IEEE 802.3 interfaces. 8 Token Ring/IEEE 802.5 interfaces. 3 Serial network interfaces. 6 Channelized E1/PRI ports. 123K bytes of non-volatile configuration memory. 16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x100 Router#
To determine which type of port adapter is installed on a Catalyst VIP2 in your system, use the show diag command. Specific port adapter information is displayed, as shown in the following example of two 4R-FDX 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 and loopback commands allow 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 the system has booted successfully and is operational. Refer to the publications listed in the "If You Need More Information" section on page 2 for detailed command descriptions and examples.
The ping command sends echo request packets to a remote device at an IP address that you specify. After sending an echo request, the command 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 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 destination and that the device is active (powered on), and repeat the ping command.
The loopback test allows you to detect and isolate equipment malfunctions by testing the connection between the 4R-FDX port adapter interface and a remote device such as a MAU, MSAU, or Token Ring switch. The loopback subcommand places an interface in loopback mode, which enables test packets that are generated from the ping command to loop through a remote device or interface cable. If the packets complete the loop, the connection is good. If not, you can isolate a fault to the remote device or interface cable in the path of the loopback test.
When no interface cable is attached to a 4R-FDX port adapter interface, issuing the loopback controller command tests the path between the Catalyst VIP2 and the interface port only (without leaving the Catalyst VIP2 and port adapter).
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:45:17 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.