|
This chapter contains the following information about interconnecting Catalyst 3900 switches:
The Catalyst 3900 allows you to configure two types of channels: ISL Channels and TokenChannels.
Using channels provides the following benefits:
Catalyst 3900 channel configurations are fault-tolerant. This feature enables channels to continue to function as long as there is at least one link active within the channel. This capability ensures that large portions of a network are not disrupted in the event a port or cable fails within the channel by transferring the traffic to one or more of the remaining ports in the channel.
Caution Physically disconnect or disable the Catalyst 3900 ports before configuring a TokenChannel or an ISL Channel. Failure to disconnect or disable the ports might result in network loops. |
A TokenChannel consists of two to eight parallel channels between two Catalyst 3900s. These parallel channels provide improved performance between Catalyst 3900s.
A single TokenChannel can consist of a combination of HDX and FDX connections. For example, a TokenChannel consisting of three connections can have one HDX and two FDX connections. However, both ports in each interconnected pair must be either HDX or FDX. In addition, all ports in a single TokenChannel must belong to the same TrCRF on the Catalyst 3900.
Caution While you can use TokenChannels to interconnect Catalyst 3900s and Catalyst 3920s, you cannot use TokenChannels to interconnect other different models of switches. For example, you cannot use a TokenChannel to interconnect a Catalyst 2600 and a Catalyst 3900. Likewise, you cannot use a TokenChannel to interconnect a Catalyst 3900 and a non-Cisco switch. |
For more information on TokenChannels, refer to the "Using Channels" section of the "Configuring the Catalyst 3900" chapter.
A single ISL Channel can consist of two to four Token Ring ISL ports. Configuring an ISL Channel provides Fast EtherChannel connectivity on the Catalyst 3900. You can configure an ISL Channel between two Catalyst 3900 switches or between a Catalyst 3900 switch and a Catalyst 5000, a Token Ring ISL-capable Cisco router, or a Token Ring ISL network adapter. All connections in an ISL channel must be FDX.
For more information on ISL Channels, refer to the "Using Channels" section of the "Configuring the Catalyst 3900" chapter.
A Catalyst stack is configured in one of the following two ways:
Two Catalyst 39xx switches can be connected to form a stack by using only a stack port cable and an interface card (Catalyst stack port module) plugged into the back of each Catalyst 39xx. This creates a direct connection between the two Catalyst 39xx switches, which is referred to as a back-to-back stack. As an alternative, you can use an 8-port Catalyst Matrix switch to create a stack of up to eight Catalyst 39xx switches. The ProStack port operates in FDX mode at speeds of 140 Mbps. It switches packets at wire speeds with low forwarding latency. A proprietary 4-byte header is used to allow the members of the stack to function as one operational system.
When you power-on a Catalyst 39xx, it runs through a set of self-diagnostics. Immediately after the diagnostics are completed, the Catalyst 39xx runs through a stack discovery mode. This discovery mode detects whether the switch is cabled to another Catalyst 39xx. If it is determined during the discovery mode that the Catalyst 39xx is connected to other switches, the switches are automatically combined to form a stack. At the end of the discovery mode, if it is determined that the Catalyst 39xx is not connected to another switch, it will operate as a stand alone switch.
Advantages of the stack include the following:
Catalyst 3900 Release 2.1(1) and later includes support for larger frame sizes. The use of larger frame sizes in a stacked configuration requires Revision B of the Stack Port module. The initial release of the Catalyst 3900 Stack Port module (which is identified as Revision A) did not support MTUs greater than 4472. Revision B of the Catalyst 3900 Stack Port module supports MTUs of up to 18190. When configuring MTUs, keep the following in mind:
If you attempt to create a stack that contains switches that have both Revision A and Revision B stack ports, the stack will not completely form. If the controlling switch (the first switch in the stack to come up) contains a Revision A module, only the switches with Revision A modules will be able to join the stack. Likewise, if the controlling switch contains a Revision B module, only the switches with Revision B modules will be able to join the stack.
To verify the revision level of a stack port module on a Catalyst 3900, see the Module Information panel. The panel has been updated to include the revision level of the stack port module in the HW Rev field. A Stack Port module Revision B will be displayed as 0.B.
As soon as the stack discovery mode is completed, two things happen:
After a stack has formed and sets up the interbox parameters, the stack operates the same way whether it is in a back-to-back configuration or is in a multi-unit configuration using the Catalyst Matrix interface.
Any combination of up to eight Catalyst 39xx switches can be connected to or disconnected from the Catalyst Matrix while it, or any of the switches, are powered on or powered off. A proprietary shielded cable, 1 meter in length, with 50-pin connectors, is used to connect the Catalyst stack equipment together. The cable has cross-over wiring so either end can connect to the Catalyst Matrix, or to the Catalyst 39xx switches. The cable is plugged directly into a stack port I/O connector on the back of the Catalyst Matrix. The other end is plugged into a Catalyst stack port module interface card that is installed in the rear expansion slot in the Catalyst 39xx.
When Catalyst 39xx switches first power up, they run through a set of self-diagnostics. Immediately after the diagnostics are completed, the Catalyst 39xx switches run through a stack discovery mode. During this stack discovery mode, if two or more Catalyst 39xx switches are connected to a Catalyst Matrix, the switches will detect the connection and combine logically to create a stack configuration.
As soon as the stack discovery mode is completed, each Catalyst 39xx is assigned a box number. With a Catalyst Matrix configuration, the box number for a Catalyst 39xx is determined by the port number the Catalyst 39xx is connected to on the Catalyst Matrix. For example, the Catalyst 39xx plugged into port 3 on the Catalyst Matrix becomes box 3. The box number remains constant as long as that switch is plugged in to that port. If a Catalyst 39xx is moved to another port, the box number for that Catalyst 39xx will change to the number of the port it is moved to.
For a stack to operate as a single entity, the interbox parameters must be the same in all of the switches in a stack. The "Interbox Parameters" section later in this chapter lists the shared parameters. There are two possible ways of providing configuration information to the Catalyst 39xx switches in a stack. These methods are as follows:
If Catalyst 39xx switches have formed a stack and any additional Catalyst 39xx switches are added to the stack, the new switches will join the existing stack by altering their interbox parameters to match those of the existing stack.
After a stack has formed and sets up the interbox parameters, the stack operates the same way whether it is in a back-to-back configuration or is in a multi-unit configuration using the Catalyst Matrix interface.
The following is a list of these shared interbox parameters. The parameters in this list are accessed through the console configuration menus. The console menus are described in "Configuring the Catalyst 3900" chapter.
Figure 3-1 shows how the ATM expansion module can be used to connect Catalyst 3900 switches through an ATM switch.
The ATM expansion module is well suited for the following environments:
A Catalyst 3900 with an ATM expansion module provides a seamless, switched network between legacy LANs communicating over ATM. Therefore, as a first step in migrating from legacy LANs, many users deploy ATM in the backbone or as the WAN technology to connect geographically dispersed legacy LANs.
A Catalyst 3900 with one or more ATM expansion modules can help protect your legacy LAN investment by providing transparent LAN-to-ATM switching. Therefore, as the next step in a legacy LAN-to-ATM migration, users place high-speed or frequently accessed servers, or both, on the ATM network to take advantage of ATM's scalability. By using LANE over ATM, ATM-based workstations are able to use existing legacy LAN applications with minimal or no upgrade costs for moving to ATM.
Because one ATM expansion module can support as many LECs as there are VLANs in a Catalyst 3900, the question arises: Why use two ATM expansion modules?
The first reason is to provide a backup LEC. By enabling two LECs on two different ATM expansion modules to be members of both the same VLAN and the same emulated LAN (ELAN), the Catalyst 3900's spanning-tree operation will automatically use one LEC for forwarding frames and the other LEC for blocking frames (active standby). For the backup LEC configuration to work, spanning tree must be enabled for the related LAN switch domain.
The second reason to use two ATM expansion modules is to increase system resources. In some environments the resources associated with a single ATM expansion module (such as a maximum of 2048 VCCs per ATM expansion module and a maximum data rate of 155 Mbps) might affect individual LEC performance. By moving one or more LECs to a second ATM expansion module, you can significantly increase the resources available to each LEC.
The ISL backbone design looks very much like an ATM design, however, ISL is less expensive than ATM and avoids the need for LANE services. It is primarily intended for network managers who do not want an ATM backbone for the campus.
Routing between Token Ring VLANs is provided via an ISL-attached router or the route switch module in the Catalyst 5500. Figure 3-2 shows an example of the ISL backbone design.
The Catalyst 5000 family of switches should be used to provide the ISL backbone. The Catalyst 3900 switch can then be connected to this backbone via the dual 100-Mbps ISL expansion module. In addition, vendors provide ISL network interface cards (NICs) that supports both Token Ring and Ethernet VLANs. These NICs can be used for high-speed attachment to servers.
If you want to attach the Catalyst 3900 ISL port to the ISL port of a Catalyst 5000, you must manually configure the ISL port on the Catalyst 5000 for 100 Mbps (using the set port speed command) and full-duplex mode (using the set port duplex command).
While your Catalyst 3900 can contain both an ATM expansion module and an ISL expansion module, use caution when using ISL in a parallel configurations with ATM or Token Ring. Because the Catalyst 3900 supports the propagation of VLAN trunking information via ISL connections only, it is important that the ISL be the active path in an ISL-ATM parallel connection.
If the ISL module is configured in parallel connections with ATM or Token Ring, the STP allows only one of the ports to be active at a time. When using the default Catalyst 3900 STP values, the path cost is calculated based on a 200-Mbps connection which results in a path cost of 5 and causes the STP to place the ISL port in forwarding mode and the ATM port or Token Ring port in blocked mode.
However, if you modify the Catalyst 3900 port STP values or use devices from other vendors that use different STP default values can, you might cause the ISL port to become blocked. If an ISL port becomes blocked in an ISL-ATM parallel connection, traffic will be passed via the ATM link but VLAN trunking data will not. Also, if your STP configuration causes an ATM or Token Ring port to become the forwarding path to the root switch instead of the ISL link, the switch on the other end of a blocked ISL port might incorrectly limit all-routes explorers (AREs) to the incoming TrCRF.
Therefore, when modifying STP values, always ensure that the STP port path costs are configured such that the ISL port is the preferred path. In an ISL parallel configuration, a Token Ring or ATM link should never have a lower cost to the root bridge than the ISL link.
Posted: Tue Oct 12 11:55:12 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.