|
|
Product Numbers: PA-5EFL and PA-5EFL(=)
This configuration note describes the installation and configuration of the Ethernet 10BaseFL port adapter (PA-5EFL[=]). 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 adapters 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.
This configuration note is organized into the following sections:
The 5EFL 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 5EFL 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 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 for preventing ESD damage:
 | Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms. |
The term Ethernet is commonly used for all carrier sense multiple access/collision detection (CSMA/CD) LANs that conform to Ethernet specifications, including IEEE 802.3. Ethernet Version 2 and IEEE 802.3 were based on, and developed shortly after, Ethernet Version 1. The slight differences between Ethernet and IEEE 802.3 are implemented in hardware, and both are supported automatically by the 5EFL without any hardware configuration changes. Together, Ethernet and IEEE 802.3 are the most widely used LAN protocols. They are well suited to applications where a local communication medium must carry sporadic, occasionally heavy traffic at high peak data rates.
The term 10BaseFL is an abbreviation for 10 Mbps transmission, Baseband medium, F for fiber, and L for link, as defined in the 10BaseFL specification. The Ethernet specifications call the 5EFL device a transceiver, and it is connected to the station with a transceiver cable. The 5EFL port adapter is not an end station. The IEEE 802.3 specifications refer to the same type of device as a media attachment unit (MAU). Stations on a CSMA/CD LAN can access the network at any time. Before sending data, the station listens to the network to see if it is already in use. If it is, the station waits until the network is not in use, and then transmits. A collision occurs when two stations listen for network traffic, hear none, and transmit simultaneously. When this happens, both transmissions are damaged, and the stations must retransmit. The stations detect the collision and use backoff algorithms to determine when they should retransmit.
Both Ethernet and IEEE 802.3 are broadcast networks, which means that all stations see all transmissions. Each station must examine received frames to determine whether it is the intended destination and, if it is, pass the frame to a higher protocol layer for processing. IEEE 802.3 specifies several different physical layers, and Ethernet defines only one. Each IEEE 802.3 physical layer protocol has a name that summarizes its characteristics in the format speed/signaling method/segment length where speed is the LAN speed in Mbps, signaling method is the signaling method used (either Baseband or Broadband), and segment length is the maximum length between stations in hundreds of meters. The maximum distances for Ethernet network segments and connections depend on the type of transmission cable used; for example, fiber-optic cable (10BaseFL).
Table 1 summarizes the characteristics of IEEE 802.3 Ethernet and Ethernet 10BaseFL.
| Parameter | IEEE 802.3 Ethernet | 10BaseFL Ethernet |
|---|---|---|
Data Rate (Mbps) | 10 | 10 |
Signaling method | Baseband | Baseband |
Media | 50-ohm coax (thick) | Multimode optical fiber |
Topology | Bus | Star |
Table 2 lists the distance limitations for 10-Mbps transmission over fiber-optic cables.
| Parameter | ST Connections |
|---|---|
Cable specification | Multimode fiber-optic cable1 |
Maximum segment lengths | 400 m (1312 ft.) for any repeater-to-DTE2 fiber segment |
| 1Cisco does not supply fiber-optic cables; these cables are available commercially. 2DTE = data terminal equipment |
Table 3 lists multimode fiber-optic parameters.
| Parameter | Multimode |
|---|---|
Size | 62.5/125 micrometer (nominal diameter) optical fiber1 |
Attenuation | 3.75 dB/km, at 850 nanometers (nm) |
Insertion loss | < 12.5 dB, at 850 nm |
Bandwidth | > 160MHzkm, at 850 nm |
Propagation delay | 5 microseconds/km |
| 1Specified in IEC Publication 793-2[14]. |
The 5EFL port adapter provides up to five IEEE 802.3 Ethernet 10BaseFL interfaces. (See Figure 1.) Each Ethernet 10BaseFL interface allows a maximum bandwidth of 10 Mbps, for a maximum aggregate bandwidth of 50 Mbps, half-duplex. Each 10BaseFL interface uses two multimode (ST) receptacles for receive (RX) and transmit (TX). All five ports run at wire speed. Figure 1 shows a 5EFL port adapter.
You can install the 5EFL port adapter in either port adapter slot 0 or port adapter slot 1. Figure 2 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 5EFL port adapter contains the enabled (EN) LED, standard on all port adapters, and one status LED for each port, called the link LED. After system initialization, the enabled LED goes on to indicate that the 5EFL port adapter has been enabled for operation. (The LEDs are shown in Figure 3.) The following conditions must be met before the enabled LED goes on:
If any of these conditions is not met, or if the initialization fails for other reasons, the enabled LED does not go on. When a 10BaseFL port is active, its link LED is on when the 5EFL port adapter receives a carrier signal from the network.
The interface connectors on the 5EFL port adapter are five pairs of (ST) receptacles, designated as RX and TX. You can use all five connection pairs simultaneously or any combination of each pair individually. Each connection pair supports IEEE 802.3 and Ethernet 10BaseFL interfaces compliant with appropriate standards. Figure 4 shows the ST fiber-optic cable plug used for RX and TX connections.
The following sections describe how to install the 5EFL port adapter.
| Caution To prevent system problems, do not remove port adapters from the RSM/VIP2 or attempt to install other port adapters in the Catalyst VIP2 while the RSM/VIP2 is installed in the switch. To install or replace port adapters, first remove the RSM/VIP2 from its switch slot. |
Each port adapter circuit board is mounted to a metal carrier and is sensitive to ESD damage. We strongly recommend that the following procedures be performed by a Cisco-certified service provider; however, this is not a requirement. While the RSM/VIP2 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 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, 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 5). 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 6).
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 6).
| 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 6. |
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 6. 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 6. |
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 5 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.
On a single 5EFL port adapter, you can use up to five pairs of ST fiber-optic connections. The 5EFL port adapter is an end station device and not a repeater. You must connect the 5EFL port adapter to a 10BaseFL repeater or hub. ST-type fiber-optic cables are not available from Cisco; they are available from outside commercial cable vendors.
Connect ST fiber-optic cables to the 5EFL port adapter as follows:
Step 1 Attach the RX multimode fiber-optic cable directly to the RX port on the 5EFL port adapter. (See Figure 9.)
Step 2 Attach the TX multimode fiber-optic cable directly to the TX port on the 5EFL port adapter. (See Figure 9.)
Step 3 Connect a 5EFL RX port to the appropriate TX port of the repeater, hub, DTE, or other external 10BaseFL equipment.
Step 4 Connect a 5EFL TX port to the appropriate RX port of the repeater, hub, DTE, or other external 10BaseFL equipment.
Step 5 Repeat Steps 1 and 4 for each additional 5EFL interface connection you require.
This completes cable connection to the 5EFL port adapter.
After you verify that the new 5EFL 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 5EFL interfaces on the RSM VIP, see the "Related Documentation" section.
The configure command requires privileged-level access to the EXEC command interpreter, which usually requires a password. Contact your system administrator, if necessary, to obtain EXEC-level access.
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, on an Catalyst VIP2 equipped with two 5EFL port adapters, the addresses of the first 5EFL port adapter are 0/0 through 0/4 (port adapter slot 0 and interface ports 0-4), and the addresses of the second 5EFL port adapter are 1/0 through 1/4 (port adapter slot 1 and interface ports 0-4).
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.
The following steps describe a basic 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>
The following example shows how to perform a basic configuration procedure:
Step 1 At the privileged-level prompt, enter configuration mode and specify that the console terminal will be 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 At the prompt, specify the first interface to configure by entering the subcommand interface, followed by the interface type/port adapter slot/interface port number. The example that follows is for the first interface of the port adapter in slot 0:
Router(config)# interface e 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 in the following example:
Router(config-int)# ip address 1.1.1.10 255.255.255.0
Step 4 Add any additional configuration subcommands required to enable routing protocols and set the interface characteristics.
Step 5 Change the shutdown state to up and enable the interface as follows:
Router(config-int)# no shutdown
Step 6 Configure additional interfaces as required.
Step 7 To complete the configuration, press CNTL/Z to exit configuration mode.
Step 8 Write the new configuration to nonvolatile memory as follows:
Router# copy running-config startup-config [OK] Router#
To check the interface configuration using show commands, proceed to the "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.
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 slot/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 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 and port address in the format show interfaces interface type/port adapter slot/interface port number.
Router# sh int e 0/0 Ethernet0/1 is administratively down, line protocol is down Hardware is cxBus Ethernet, 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 e 0/1 Ethernet0/2 is administratively down, line protocol is down Hardware is cxBus Ethernet, address is 0000.0ca5.2301 (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 e 0/2 Ethernet0/3 is administratively down, line protocol is down Hardware is cxBus Ethernet, address is 0000.0ca5.2302 (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 e 0/3 Ethernet0/3 is administratively down, line protocol is down Hardware is cxBus Ethernet, address is 0000.0ca5.2303 (bia 0000.0ca5.238c) 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 e 0/4 Ethernet0/4 is administratively down, line protocol is down Hardware is cxBus Ethernet, address is 0000.0ca5.2304 (bia 0000.0ca5.238d) 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# 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 C5IP controller (15 Vlan). 1 VIP2 controllers (5 Ethernet)(4 Serial). 5 Ethernet/IEEE 802.3 interfaces. 4 Serial network interfaces. 15 Virtual Ethernet/IEEE 802.3 interface(s) 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 the Catalyst VIP2 in your system, use the show diag command. Specific port adapter information is displayed, as shown in the following example of a 5EFL port adapter:
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:
Ethernet PA, 5 ports
EEPROM format version 1
HW rev 1.0, Board revision 6
Serial number: 03522225 Part number: 73-1679-01
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.
Refer to the following configuration and command reference publications, as appropriate for your configuration:
For your Catalyst VIP2 port adapters, 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.
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.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Mon Jul 26 09:47:22 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.