|
|
This chapter provides information about the Fiber Distributed Data Interface (FDDI) Interface Processor (FIP). (See Figure 7-1.)
Each FIP provides a single network interface for both multimode and single-mode FDDI networks, and provides the interface for connection to a Class A dual attachment station (DAS) with primary and secondary rings, or to a Class B single attachment station (SAS) with only a primary ring. Figure 7-1 shows a multimode/multimode FIP on the bottom (CX-FIP-MM) and a single-mode/multimode FIP on the top (CX-FIP-SM).
The multimode or single-mode ports on the FIP provide a direct connection to external FDDI networks. The FIP contains a 16-million-instructions-per-second (MIPS) processor for high-speed (100-Mbps) FDDI rates and the industry-standard, AMD SuperNet chipset for interoperability. The default FIP microcode resides on a ROM in socket U23.
Two receptacles on the FIP are available in any combination of multimode (MIC) or single-mode (SC) connections for matching multimode and single-mode fiber in the same FDDI network.
A 6-pin mini-DIN connector on the multimode-multimode FIP (CX-FIP-MM) and the single-mode/single-mode FIP (CX-FIP-SS) provides the connection for an optical bypass switch. When the interface is shut down, the bypass switch allows the light signal to pass directly from the receive port to the transmit port on the bypass switch, completely bypassing the FIP transceivers. The bypass switch does not repeat the signal, and significant signal loss might occur when transmitting to stations at maximum distances.
Optical bypass switches typically use a 6-pin DIN or mini-DIN connector. A DIN-to-mini-DIN adapter cable is included with the CX-FIP-MM to allow connection to either type of connector. For a detailed description of optical bypass switch connections, refer to the section "Installing an Optical Bypass Switch."
This section provides information about hardware requirements for the FIP. There are two hardware versions of the FIP models CX-FIP-MM(=), CX-FIP-SS(=), and CX-FIP-MS(=): an older version that uses FC-type optical-fiber connections for the single-mode applications, and a newer version that uses SC-type optical-fiber connections. An SC-to-FC adapter (FC-SC-ADAPTER=) ships with the newer FIP models so that they can be used in networks that have FC-type, single-mode optical fiber.
The following FIP interface combinations are available:
(An equal sign [=] indicates the entire FIP assembly is available as a spare part.)
This section provides and overview of the Fiber Distributed Data Interface. Typically, FDDI uses two types of fiber-optic cable:
Mode refers to the angle at which light rays (signals) are reflected and propagated through the optical fiber core, which acts as a waveguide for the light signals. Multimode fiber has a relatively thick core (62.5/125-micron) that reflects light rays at many angles. Single-mode fiber has a narrow core (8.7 to 10/125-micron) that allows the light to enter only at a single angle. Although multimode fiber allows more light signals to enter at a greater variety of angles (modes), the different angles create propagation paths that cause the signals to spread out in time and limits the rate at which data can be accurately received. This distortion does not occur on the single path of the single-mode signal; therefore, single-mode fiber is capable of higher bandwidth and greater cable run distances than multimode fiber.
Multimode transmitters usually use LEDs as a light source, and single-mode transmitters use a laser diode, which is capable of sustaining faster data rates. Both types use a photodiode detector at the receiver to translate the light signal into electrical signals.
The FDDI standard sets total fiber lengths as shown in Table 7-1. The maximum circumference of the FDDI network is only half the specified distance because of signal wrapping or loopback that occurs during fault correction. The FDDI standard allows a maximum of 500 stations with a maximum distance between active stations of 1.2 miles (2 kilometers).
The FIP supports both Class A and Class B station connections and provides an interface for both single-mode and multimode fiber-optic cable. The two physical ports (PHY A and PHY B) are available with either single-mode connectors (SC type) or multimode, media interface connectors (MICs), or with a combination of one of each for matching multimode and single-mode fiber in the same FDDI network.
The FIP FDDI implementation complies with Version 6.1 of the X3T9.5 FDDI specification, offering a Class A dual attachment interface that supports the fault-recovery methods of DAS. The FIP supports dual homing and optical bypass and complies with ANSI X3.1 and ISO 9314 FDDI standards. The single-mode products comply with the Class 1 limits of the European safety standard EN 60825 and with the Class 1 laser limits of the equivalent North American standard.
The maximum transmission distances for single-mode and multimode FDDI stations are shown in Table 7-1. If the distance between two connected stations is greater than the maximum distance shown, significant signal loss can result.
| Transceiver Type | Maximum Distance Between Stations |
|---|---|
| Single-mode | Up to 9.3 miles (up to 15 km) |
| Multimode | Up to 1.2 miles (up to 2 km) |
The multimode and single-mode optical-fiber connections conform to the following optical power parameters per physical media dependent (PMD) ANSI X3T9.5 FDDI specifications:
The single-mode FDDI uses simplex or duplex SC-type connectors (see Figure 7-2 and Figure 7-3, respectively) for the transmit and receive ports. For FDDI single-mode connections, use two simplex SC connectors or one duplex SC connector at both the port adapter end and the network end. Single-mode optical fiber cable has a narrow core (8.7 to 10/125-micron), which allows the light to enter only at a single angle.
Newer versions of the single-mode FIPs are shipped with an FC-to-SC adapter (FC-SC-ADAPTER=) that allows the newer version of the single-mode FIPs to be used with existing FC-type cables installed for the earlier versions of the FIPs. (See Figure 7-4 and Figure 7-5, which show both ends of the FC-to-SC adapter.)
The multimode FDDI uses an FDDI-standard, physical sublayer (PHY) connector that encodes and decodes the data into a format acceptable for fiber transmission. The multimode connector accepts standard 62.5/125-micron, multimode fiber-optic cable using the media interface cable (MIC) and, with proper cable terminators, can accept 50/125 micron fiber-optic cable.
The multimode FDDI uses the integrated MIC at the FIP and network end of the cable. Each end is keyed to ensure proper connection for the receive and transmit optical fiber. Figure 7-6 shows the MIC connector.
The single-mode/single-mode FIP (CX-FIP-SS) and multimode/multimode FIP (CX-FIP-MM) each provide a control port for an optical bypass switch, which allows the light signal to pass directly through the bypass switch, completely bypassing the FIP transceivers when the interface is shut down. Most optical bypass switches provide the necessary interface cables for connection to single-mode or multimode transceivers.
Table 7-2 lists the signal descriptions for the mini-DIN optical bypass switch available on the CX-FIP-SS and CX-FIP-MM. The mini-DIN-to-DIN adapter cable (CAB-FMDD=) allows connection to an optical bypass switch with a DIN connector (which is larger than the mini-DIN connector).
| Pin | Direction | Description1 |
|---|---|---|
| 1 | Out | +5V to secondary switch |
| 2 | Out | +5V to primary switch |
| 3 | Out | Enable optical bypass switch primary |
| 4 | Out | Enable optical bypass switch secondary |
| 5 | In | Sense optical bypass switch--1 kohm to +5 V |
| 6 | Out | Ground--Sense optical bypass switch return |
This section provides detailed instructions for connecting the FIP as either a single attachment or dual attachment station to both single-mode and multimode networks. Single-mode uses separate transmit and receive cables. You will need two single-mode cables for a single attachment connection or four cables for a dual attachment connection.
 | Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode FDDI products when no fiber cable is connected. Avoid exposure and do not stare into open apertures. This product meets the Class 1 Laser Emission Requirement from the CDRH FDDI. |
The aperture port contains a warning label, as shown in Figure 7-7.
Multimode uses one integrated transmit/receive cable for each physical interface (one for PHY A and one for PHY B). You will need one multimode cable for a single attachment connection, and two cables for a dual attachment connection.
This section also provides instructions for connecting an optical bypass switch to a dual attachment multimode network connection. Because the method of connecting optical bypass switches varies between different manufacturer's models, refer to the documentation for your particular bypass switch for correct connection instructions. If you are installing an optical bypass switch, proceed to the section "Installing an Optical Bypass Switch."
A FIP that is connected as a single attachment station (SAS) typically is connected to the ring through a concentrator. The FIP receives and transmits the signal through the same physical interface, usually PHY A.
Depending on whether you are connecting to a single-mode or multimode fiber network, connect the FIP as follows:
If you plan to connect FIPs to an optical bypass switch and do not require DAS connections, proceed to the section "Installing an Optical Bypass Switch" on page 7-16. Otherwise, proceed to the next section. If you do not plan to use either DAS connections or optical bypass connections, proceed to the section "Using LEDs to Verify FIP Status" on page 7-19.
A FIP that is connected as a dual attachment station (DAS) connects to both the primary and secondary rings. The signal for each ring is received on one physical interface (PHY A or PHY B) and transmitted from the other. The standard connection scheme (shown in Figure 7-10) for a dual attachment station dictates that the primary ring signal comes into the FIP on the PHY A receive port and returns to the primary ring from the PHY B transmit port.
The secondary ring signal comes into the FIP on the PHY B receive port and returns to the primary ring from the PHY A transmit port. Failure to observe this relationship will prevent the FDDI from initializing. (Figure 7-13 shows the connections for a dual attachment that uses both multimode and single-mode fiber.)
Depending on whether you are connecting to a single-mode or multimode fiber network, or both, connect the FIP for DAS operation as described in the following sections:
Use the following guidelines when connecting DAS with single-mode cable.
Observe the standard connection scheme described previously and refer to Figure 7-11 while you connect the interface cables.
If you plan to connect FIPs to an optical bypass switch, proceed to the section "Installing an Optical Bypass Switch" on page 7-16. Otherwise, proceed to the section "Using LEDs to Verify FIP Status" on page 7-19.
Use the following guidelines when connecting DAS with multimode cable.
Each of the integrated transmit/receive multimode interface cables attaches to both the primary and secondary ring; each one receives the signal from one ring and transmits to the other ring. (See Figure 7-12.)
To help avoid confusion, use the receive label on the cable MIC connector as a key and connect the cables to the FIP ports as follows:
If you plan to connect FIPs to an optical bypass switch, proceed to the section "Installing an Optical Bypass Switch" on page 7-16. Otherwise, proceed to the section "Using LEDs to Verify FIP Status" on page 7-19.
Use the following guidelines when connecting DAS with single-mode and multimode cable (mixed mode). Either CX-FIP-SM or CX-FIP-MM can be used.
Follow the cabling guidelines described previously to connect the multimode and single-mode interface cables. Figure 7-13 shows that the primary ring signal is received on the multimode PHY A receive port and transmitted from the single-mode PHY B transmit port. Your configuration might be opposite, with multimode on PHY B and single-mode on PHY A.
Connect the cables to the FIP ports as follows:
Proceed to the section "Using LEDs to Verify FIP Status" on page 7-19.
An optical bypass switch is a device installed between the ring and the station that provides additional fault tolerance to the network. If a FIP that is connected to a bypass switch fails or shuts down, the bypass switch activates automatically and allows the light signal to pass directly through it, bypassing the FIP completely. A port for connecting an optical bypass switch is provided on the multimode/multimode FIP (CX-FIP-MM, shown in Figure 7-14), and the single-mode/single-mode FIP (CX-FIP-SS, shown in Figure 7-15).
The following general instructions apply to connecting an optical bypass switch to the FIP; however, your particular bypass switch might require a different connection scheme. Use these steps and the illustrations in Figure 7-14 and Figure 7-15 as general guidelines; for specific connection requirements, refer to the instructions provided by the manufacturer of the switch.
Proceed to the following section to check the installation.
The FIP has seven status LEDs on its faceplate that indicate status on the FIP and the PHY A and PHY B ports. (See Figure 7-16.)
The enabled LED goes on to indicate that the FIP is operational and that it is enabled for operation. It does not mean that the interface ports are functional or enabled.
The following conditions must be met before the FIP is enabled:
If any one of the preceding conditions is not met, or if the initialization fails, the enabled LED does not go on.
The vertical rows of three LEDs each indicate the status of PHY B and PHY A (the PHY B interface is located next to the PHY A interface on the faceplate of the FIP). The state of each PHY B/A pair of LEDs indicates the status of one type of three possible station connections: DAS, SAS, or dual homed.
The indications for the DAS, SAS, and dual homed LEDs are described in Table 7-3 and illustrated in Figure 7-16.
| LED Pattern1 | State | Indication |
|---|---|---|
| B A | DAS | |
| - - X X X X | Both lights off | Not connected |
| O O X X X X | Both lights on | Through A |
| O - X X X X | B on and A off | Wrap B |
| - O X X X X | B off and A on | Wrap A |
| B A | SAS | |
| X X - - X X | Both lights off | Not connected |
| X X O - X X | B on and A off | Single attachment B (PHY A shut down) |
| X X - O X X | B off and A on | Single attachment A (PHY B shut down) |
| B A | Dual Homed | |
| X X X X - - | Dual homed B and A off | Not connected |
| X X X O O O | Single attachment A on Dual homed B and A on | Dual homed with A active; not a normal condition; indicates potential problem on B Dual homed with B and A active |
| X X O X O O | Single attachment B on Dual homed B and A on | Dual homed with B active; a normal condition Dual homed with B and A active |
| X X O X O X | Single attachment B on Dual homed B on | Single attachment B Dual homed A failed |
| X X X O X O | Single attachment A on Dual homed A on | Single attachment A Dual homed B failed |
Verify that the FIP is connected correctly as follows:
Step 1 While the system reinitializes each interface, observe the console display messages and verify that the system discovers the FIP. The system should recognize the FIP interfaces but leave them configured as down.
Step 2 When the reinitialization is complete, verify that the enabled LED on the FIP is on and remains on. If the LED does stay on, proceed to Step 5. If the enabled LED does not stay on, proceed to the next step.
Step 3 If the enabled LED on the FIP fails to go on, suspect that the FIP board connector is not fully seated in the backplane. Loosen the captive installation screws, then firmly push the top ejector down while pushing the bottom ejector up until both are parallel to the FIP faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the FIP should go on. If the enabled LED goes on, proceed to Step 5. If the enabled LED does not go on, proceed to the next step.
Step 4 If the enabled LED still fails to go on, remove the FIP and try installing it in another available interface processor slot.
Step 5 Use the show interfaces or show controllers cbus command to verify the status of the FIP's interfaces. (If the interfaces are not configured, configure them using the procedures in the section "Configuring the FIP.")
If an error message displays on the console terminal, refer to the appropriate reference publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.
If you want to change the configuration of an existing interface, you must enter configuration mode to change its configuration. If you replaced a FIP that was previously configured, the system will recognize the new interface and bring it up in its existing configuration.
After you verify that the new FIP is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. Be prepared with the information you will need, such as the following:
For a summary of the configuration options available and instructions for configuring the interfaces, refer to the appropriate software configuration publications listed in the section "If You Need More Information" in the chapter "Using Interface Processors."
Configuring the FIP first requires privileged-level access to the EXEC command interpreter. (Refer to the section "Using the EXEC Command Interpreter" in the chapter "Using Interface Processors.") Also, privileged-level access usually requires a password. (Contact your system administrator, if necessary, to obtain privileged-level access.)
Cisco 7000 series and 7500 series routers identify an interface address by its interface processor slot number and port number in the format slot/port. Each FIP contains one FDDI, which is always port (interface) 0. For example, the slot/port address of the FDDI on a FIP installed in interface processor slot 1 is 1/0. The address of an FDDI port on a FIP in slot 2 would be 2/0.
This section provides descriptions and examples of the basic commands required to configure the FDDI. Depending on the requirements for your system configuration and the protocols you plan to route on the interface, you might also need to enter other configuration subcommands.
Use the following instructions to perform a basic configuration: enabling FDDIs and specifying IP routing. Descriptions are limited to fields that are relevant for establishing and verifying a basic configuration. After configuring the new FIP interface, use show commands to display the status of the new interface or all interfaces, or to verify changes you have made. Press the Return key after each configuration step unless otherwise noted.
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:
configure terminal
Step 2 At the prompt, specify the first interface to configure by entering the subcommand interface, followed by the type (fddi) and slot/port (interface processor slot number/0). The example that follows is for the FDDI port on a FIP in interface processor slot 0:
interface fddi 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:
ip address 1.1.1.1 255.255.255.0
Step 4 Add any additional configuration subcommands required to enable routing protocols and adjust the interface characteristics.
Step 5 Change the default shutdown state to up and enable the interface as follows:
no shutdown
Step 6 When you have included all of the configuration subcommands to complete the configuration, press Ctrl-Z (hold down the Control key while you press Z) to exit configuration mode.
Step 7 Write the new configuration to memory as follows:
copy running-config startup-config
The system will display an OK message when the configuration has been stored.
Step 8 Exit privileged level and return to user level by entering disable at the prompt as follows:
disable
Proceed to the following section to check the interface configuration using show commands.
The following procedure describes how to use the show commands to verify that the new interfaces are configured correctly:
Step 1 Display the system hardware configuration with the show version command. Ensure that the list includes the new FDDI.
Step 2 Display all of the current interface processors and their interfaces with the show controllers cbus command. Verify that the new FIP appears in the correct interface processor slot.
Step 3 Specify one of the new FIP interfaces with the show interface fddi slot/port adapter/port command and verify that the first line of the display specifies the interface with the correct slot number. Also 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 command show protocols. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.
Step 5 Display the entire, saved system configuration file with the show running-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.
Following are descriptions and examples of the show commands. Descriptions are limited to fields that are relevant for verifying the configuration.
Router> show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-JV-M), Released Version 11.1(10)CA [biff 135]
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Sat 10-May-97 06:02 by mpo
Image text-base: 0x600108A0, data-base: 0x60982000
ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1)
ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(8), RELEASE SOFTWARE (fc2)
Router uptime is 23 minutes
System restarted by reload
System image file is "biff/rsp-jv-mz", booted via tftp from 223.255.254.254
cisco RSP2 (R4600) 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 (copyright 1994 by TGV Inc).
Chassis Interface.
(additional displayed text omitted from this example)
1 FIP controller (1 FDDI).
1 FDDI interface.
(additional displayed text omitted from this example)
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 7.
Configuration register is 0x0
Router> show protocols
Global values:
Internet Protocol routing is enabled
FDDI0/0 is up, line protocol is up
(additional displayed text omitted from this example)
Router# show running-config
Using 1652 out of 130048 bytes
version 10.1(10)
!
hostname Router
!
enable-password guessagain
!
microcode FIP flash fip10-0
microcode reload
(additional displayed text omitted from this example)!
interface Fddi0/0
ip address 1.1.1.14 255.255.255.0
ip route-cache cbus
no keepalive
novell network 1033
!
(additional displayed text omitted from this example)
Router> show cont cbus
(additional displayed text omitted from this example)
FIP 0, hardware version 1.3, microcode version 141.12
Interface 24 - Fddi3/0, station addr 0000.0c02.adf1 (bia 0000.0c02.adf1)
13 buffer RX queue threshold, 33 buffer TX queue limit, buffer size 4484
ift 0006, rql 9, tq 0000 0000, tql 32
(additional displayed text omitted from this example)
Router> show int fddi0/0
Fddi0/0 is up, line protocol is up
Hardware is cxBus Fddi, address is 0000.0c02.adf1 (bia 0000.0c02.adf1)
Internet address is 1.1.1.14, subnet mask is 255.255.255.0
MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive not set
ARP type: SNAP, ARP Timeout 4:00:00
PHY A state is active, neighbor is B, cmt signal bits 008/20C, status ILS
PHY B state is active, neighbor is A, cmt signal bits 20C/008, status ILS
CFM is thru A, token rotation 5000 usec, ring operational 15:25:31
Upstream neighbor 0000.0c01.261a, downstream neighbor 0000.0c01.4117
(additional displayed text omitted from this example)
|
|