|
|
This chapter provides information on the Token Ring Interface Processor (TRIP). (See Figure 12-1.)
The TRIP provides two or four Token Ring ports for interconnection with IEEE 802.5 and IBM Token Ring media, and uses the IBM 16/4-Mbps chipset with an imbedded performance enhanced interface driver and 16.7-MHz bit slice processor for high-speed processing. The speed on each port is set independently with a software command for either 4 or 16 Mbps. The TRIP firmware (microcode), which contains card-specific software instructions, resides in a ROM in socket U41.
The TRIP is available in the following fixed configurations: two-port TRIP (CX-TRIP2[=]); four-port TRIP (CX-TRIP4[=]).
You will need an 802.5 media access unit (MAU) or a multistation access unit (MSAU) to provide the interface between the TRIP Token Ring interfaces and the external ring. You will also need a Token Ring lobe cable between each TRIP port and the MAU or MSAU. Patch cables can connect adjacent MSAUs to form one large ring.
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 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 cabling; however, some networks that operate at 4 Mbps use unshielded twisted-pair cable. Table 12-1 shows a comparison of the two types of specifications.
| Network Type/ Access Method | Data Rates | Stations/Segment | Media/ Topology | Signaling | Encoding |
|---|---|---|---|---|---|
| IBM Token Ring/ Token passing | 4, 16 Mbps | 260 shielded twisted-pair 72 unshielded twisted-pair | Twisted pair/ Star | Baseband | Differential Manchester |
| IEEE 802.5/ Token passing | 4, 16 Mbps | 250 | Not specified/ Not specified | Baseband | Differential Manchester |
In the typical Token Ring network shown in Figure 12-2, lobe cables connect each Token Ring station (TRIP port) to the MSAU (or MAU), and patch cables connect adjacent MSAUs (or MAUs) to form one large ring.
The maximum transmission distance is not defined for IEEE 802.5 (Token Ring) networks. Shielded twisted-pair 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, the network length and repeater spacing should be planned accordingly.
Before you install the TRIP, 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.
The default for all ports is for 4 Mbps operation and early token release disabled. Both states are enabled using configuration commands in configuration mode.
To enable 16 Mbps, specify the slot/port address 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 slot/port address and use the configuration command [no] early token release.
For more complete descriptions and examples of related Token Ring software commands, refer to the appropriate software configuration documentation listed in the section "If You Need More Information," in the chapter "Using Interface Processors."
The Token Ring ports on the TRIP are DB-9 (PC type) receptacles that require Type 1 or Type 3 lobe cables. Type 1 lobe cables use shielded twisted-pair cable and terminate at the network end with a large MAU plug. (See Figure 12-3.) Type 3 lobe cables use either shielded or unshielded twisted pair (UTP) cable and terminate at the network end with an RJ-11 plug. (See Figure 12-4.) The TRIP end of both cable types is a DB-9 plug. The Token Ring lobe cable provides the connection between the DB-9 connectors on the TRIP and the MAU.
Table 12-2 lists the pinout for the DB-9 Token Ring connector used on the TRIP.
| Pin | Signal |
|---|---|
| 1 | Ring-In B |
| 5 | Ring-Out A |
| 6 | Ring-In A |
| 9 | Ring-Out B |
| 10 and 11 | Ground |
Attach network interface cables or other connection equipment to the Token Ring interface ports as shown in Figure 12-5.
The TRIP has several status LEDs that indicate status of each port. (See Figure 12-6.)
The enabled LED turns on to indicate that the TRIP is enabled for operation. When the system has reinitialized all interfaces, the enabled LED on the TRIP should go on. The console screen will also display a message as the system discovers each interface during its reinitialization. The following conditions must be met before the TRIP is enabled:
If any one of these conditions are not met, or if the initialization fails, the enabled LED does not turn on.
The three LEDs for each port indicate the following:
Verify that the TRIP 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 TRIP. The system should recognize the TRIP interfaces but leave them configured as down.
Step 2 When the reinitialization is complete, verify that the enabled LED on the TRIP 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 TRIP fails to go on, suspect that the TRIP 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 TRIP faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the TRIP 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 TRIP 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 TRIP interfaces. (If the TRIP interfaces are not configured, you must use the procedures in the section "Configuring the TRIP" to configure the interfaces.)
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 configure it. If you replaced a TRIP that was previously configured, the system will recognize the new interfaces and bring each of them up in their existing configuration.
After you verify that the new TRIP 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 complete summary of the configuration options available and more detailed instructions for configuring the TRIP, refer to the appropriate software configuration and command reference publications, which are listed in the section "If You Need More Information," in the chapter "Using Interface Processors."
Configuring the TRIP 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 Cisco 7500 series routers identify an interface address by its interface processor slot number and port number in the format slot/port. Each TRIP can contain up to four Token Ring interfaces, and the port numbers range from 0 to 3. For example, the slot/port address of the Token Ring interfaces on a 2-port TRIP installed in interface processor slot 0 are 0/0 and 0/1; if installed in interface processor slot 1, the slot/port addresses changes to 1/0 and 1/1.
This section provides instructions for performing a basic configuration: enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending upon the requirements for your system configuration.
The system will prompt you for a password if one is set. Press the Return key after each configuration step unless otherwise noted.
Step 1 After you access the privileged level of the EXEC command interpreter, enter the configure command:
configure terminal
Step 2 Specify the first Token Ring interface to configure by entering the subcommand interface type slot/port. For example, if you are configuring Token Ring interface 0 on a TRIP installed in interface processor slot 0, enter the following command:
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:
ip address ip address subnet mask
Step 4 Change the default shutdown state and enable the interface:
no shutdown
When you enable the interface using the no shutdown command, the LED for 4 Mbps or 16 Mbps is turned on after about 5 seconds. The in ring LED for that interface is turned on about 5 to 18 seconds later, when the port is initialized and is connected to the ring.
 | Caution To prevent problem on the ring, each TRIP port must be configured for the same ring speed as the ring to which it is connected (either 4 or 16 Mbps) before it is connected to the ring. If the port is set for a different speed, it will cause the ring to beacon, which effectively brings down the ring and makes it inoperable. |
Step 5 Enter any additional configuration subcommands required.
Step 6 Repeat Steps 2 through 5 for each new Token Ring interface.
Step 7 When all new interfaces are configured, press Ctrl-Z (hold the Control key down and press the Z key).
Step 8 Write the new configuration to memory by entering the following:
copy running-config startup-config
Step 9 Enter quit to exit configuration mode:
quit
This completes the procedure for configuring the Token Ring interfaces. Check the configuration as described in the section "Using show Commands to Check the Configuration."
The following summary describes how to use the show commands to verify that the new interface is configured correctly:
Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new interface.
Step 2 Display all the current interface processors and their interfaces with the show controllers cbus command. Verify that the new TRIP appears in the correct slot.
Step 3 Specify the new interfaces with the show interfaces token slot/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 system configuration file with the show configuration 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, contact a customer service representative for assistance.
This completes the procedure for configuring the TRIP.
|
|