|
|
This chapter describes how to use the console port to configure the Fiber Distributed Data Interface/Copper Distributed Data Interface (FDDI/CDDI) ports of the Catalyst 5000 series switch. For definitions of all commands discussed in this chapter, refer to the Catalyst 5000 Series Command Reference publication.
FDDI is a LAN standard, defined by ANSI X3T9.5, specifying a 100-Mbps, token-passing network using fiber-optic cable, with transmission distances of up to 2 kilometers (km). FDDI uses a dual-ring architecture to provide redundancy. CDDI is the implementation of FDDI protocols over shielded twisted-pair (STP) and unshielded twisted-pair (UTP) cabling. CDDI transmits at data rates of 100 Mbps over relatively short distances (about 100 meters), also using a dual-ring architecture to provide redundancy.
The default configuration values for FDDI/CDDI modules are as follows:
To customize your configuration, perform the appropriate tasks in the following sections.
The Catalyst 5000 series switch can forward IPX packets received on FDDI ports to Ethernet ports, or it can forward IPX packets received on Ethernet ports to FDDI ports. To do this, you must configure the switch for specific IPX protocol translations. By default, these IPX protocol translations are configured:
You can customize these settings if your environment requires it.
The FDDI SNAP frame can be translated into these Ethernet frames:
To specify the FDDI protocol to which Ethernet 802.3 RAW packets are translated, complete these steps in privileged mode:
| Task | Command |
|---|---|
| Step 1 Configure the appropriate translation protocol. | set bridge ipx snaptoether {8023 | SNAP | EII | 8023RAW} |
| Step 2 Verify that the correct translation protocol was configured. | show bridge |
After entering the set bridge ipx snaptoether 8023 command, you see this display:
Console> (enable) set bridge ipx snaptoether 8023 Bridge snaptoether default IPX translation set. Console> (enable)
Enter the show bridge command to verify the FDDI SNAP to Ethernet translation. You see this display:
Console> (enable) show bridge
IP fragmentation disabled
Default IPX translations:
FDDI SNAP to Ethernet 802.3
FDDI 802.2 to Ethernet 802.3
Ethernet 802.3 Raw to FDDI 802.2
Console> (enable)
The FDDI 802.2 frame can be translated into these Ethernet frames:
To specify the Ethernet frame to which IPX FDDI SNAP packets are translated, complete these steps in privileged mode:
| Task | Command |
|---|---|
| Step 1 Configure the appropriate protocol translation. | set bridge ipx 8022toether {8023 | SNAP | EII | 8023RAW} |
| Step 2 Verify that the correct protocol translation was configured. | show bridge |
After setting the IPX translation protocol for FDDI 802.2 to 802.3, you see this display:
Console> (enable) set bridge ipx8022 toether 8023 Module 4 8022toether translation set. Console> (enable)
After setting the IPX translation protocol for FDDI SNAP to Ethernet SNAP, you see this display:
Console> (enable) set bridge ipx snaptoether snap Module 4 snaptoether translation set Console> (enable)
Enter the show bridge command to verify the FDDI 802.2 to Ethernet translation. You see this display:
Console> (enable) show bridge
APaRT Enabled
FDDICHECK Enabled
IP fragmentation Enabled
Default IPX translations:
FDDI SNAP to Ethernet snap
FDDI 802.2 to Ethernet 8023
Ethernet 802.3 Raw to FDDI snap
Console> (enable)
The Ethernet 802.3 RAW protocol can be translated into these FDDI protocols:
To specify the FDDI frames to which 802.3 RAW Ethernet packets are translated, complete these steps in privileged mode:
| Task | Command |
|---|---|
| Step 1 Configure the appropriate protocol translation. | set bridge ipx 8023rawtofddi {8022 | SNAP | FDDIRAW} |
| Step 2 Verify that the correct translation protocol was configured. | show bridge |
After entering the set bridge ipx command, you see this display:
Console> (enable) set bridge ipx 8023rawtofddi 8022 Module 4 8023rawtofddi translation set. Console> (enable)
Enter the show bridge command to verify the Ethernet 802.3 RAW to FDDI translation. You see this display:
Console> (enable) show bridge
APaRT Enabled
FDDICHECK Enabled
IP fragmentation Enabled
Default IPX translations:
FDDI SNAP to Ethernet 8023raw
FDDI 802.2 to Ethernet 8023
Ethernet 802.3 Raw to FDDI 8023
Console> (enable)
The TL_MIN parameter sets the minimum time to transmit an FDDI physical sublayer (PHY) line state before advancing to the next physical connection management (PCM) state. This setting affects the station and switch interoperability and might hinder the implementation of FDDI repeaters. By default, the TL_MIN parameter is set to 40 microseconds. Normally, you do not need to adjust this parameter. However, you can customize the TL_MIN setting if needed.
To set the minimum time to transmit an FDDI PHY line state, enter this command in privileged mode:
| Task | Command |
|---|---|
| Set TL_MIN to a value between 40 and 1,340,006 microseconds. | set fddi tlmin mod_num/port_num microseconds |
After entering the set fddi tlmin command, you see this display:
Console> (enable) set fddi tlmin 4/1 40 Port 4/1 tlmin set to 40. Console> (enable)
To verify that you have correctly configured TL_MIN, enter the show fddi command. After entering this command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
The TNotify parameter sets the interval (in seconds) between neighbor notification frames. These frames are sent out to notify neighboring devices of FDDI module Media Access Control (MAC) addresses. Usually, the default setting of 30 seconds is sufficient. By shortening the interval, you cause more notification frames to be sent.
If you need to adjust the interval between neighbor notification frames, enter this command in privileged mode:
| Task | Command |
|---|---|
| Set TNotify to a value between 2 and 30 seconds. | set fddi tnotify mod_num time |
After entering the set fddi tnotify command, you see this display:
Console> (enable) set fddi tnotify 4/1 15 Module 4 tnotify set to 15. Console> (enable)
To verify that you correctly configured TNotify, enter the show fddi command. After entering the command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
The TRequest parameter specifies the FDDI switch's required value for the Token Ring Timer (TRT). This value is used to negotiate the TRT with other stations. The TRT allows you to control ring scheduling during normal operation and to detect and recover from serious ring error situations. Whenever the TRT value expires, the station uses the TRequest value to negotiate with other stations for the lowest value. The default setting of 165,000 microseconds is sufficient for most networks.
If you need to modify the setting for the TRequest parameter, enter this command in privileged mode:
| Task | Command |
|---|---|
| Set TRequest to a value between 2502 and 165,000 microseconds. | set fddi trequest mod_num time |
After entering the set fddi trequest command, you see this display:
Console> (enable) set fddi trequest 4 3500 Mac 4/1 treq set to 3500. Console> (enable)
To verify that you correctly configured TNotify, enter the show fddi command. After entering the command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
The user-data string identifies the user-data string in the Station Management (SMT) Management Information Base (MIB) of an FDDI module. The default value is Catalyst 5000. You should modify this value to a more meaningful description.
To modify the user-data string, enter this command in privileged mode:
| Task | Command |
|---|---|
| Enter a module number and a unique description or name to identify the FDDI module. | set fddi userdata mod_num userdata_string |
After entering the set fddi userdata command, you see this display:
Console> (enable) set fddi userdata 4 Engineering Module 4 userdata set to Engineering. Console> (enable)
To verify that you entered the description or name correctly, enter the show fddi command. After entering the command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
IP fragmentation allows the Catalyst 5000 series switch to fragment large FDDI IP frames (frames greater than 1514 bytes) into multiple smaller packets so that they can be transmitted on an Ethernet segment.
The procedures in this section describe disabling and reenabling IP fragmentation. By default, IP fragmentation is enabled.
If you want to drop the large packets (instead of fragmenting them), disable fragmentation by entering this command in privileged mode:
| Task | Command |
|---|---|
| Disable IP fragmentation. | set ip fragmentation disable |
After entering the set ip fragmentation disable command, you see this display:
Console> (enable) set ip fragmentation disable IP fragmentation disabled for module 4 Console> (enable)
To reenable IP fragmentation, enter this command in privileged mode:
| Task | Command |
|---|---|
| Enable IP fragmentation. | set ip fragmentation enable |
After disabling or reenabling IP fragmentation, verify that you correctly set IP fragmentation by entering the show ip route command. After entering the command, you see this display:
Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- disabled enabled disabled Destination Gateway Flags Use Interface --------------- --------------- ------ ---------- --------- 172.20.0.0 172.20.22.181 U 0 sc0 default default UH 0 sl0 Console> (enable)
When you enable the Internetworking Control Message Protocol (ICMP) Unreachable Messages feature, the switch returns an ICMP unreachable message to the Internet source host whenever it receives an IP datagram that it cannot deliver. When you disable the ICMP Unreachable Messages feature, the switch does not notify the Internet source host when it receives an IP datagram that it cannot deliver.
This section describes how to disable and reenable IP unreachable messages.
To disable unreachable messages, enter this command in privileged mode:
| Task | Command |
|---|---|
| Disable IP unreachable messages. | set ip unreachable disable |
To reenable IP unreachable messages, enter this command in privileged mode:
| Task | Command |
|---|---|
| Enable IP unreachable messages. | set ip unreachable enable |
To verify that IP unreachable messages are enabled or disabled, enter the show ip route command. After entering this command, you see this display:
Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled Destination Gateway Flags Use Interface ----------------------- ----------------------- ------ ---------- --------- default main-gw.cisco.com UG 2907 sc0 172.20.0.0 cat5000.cisco.com U 788 sc0 default default UH 0 sl0 Console> (enable)
The link error rate (LER)-alarm value defines the LER at which a link connection exceeds a preset alarm threshold. This value is used in the LER threshold test. The default setting of 8 (10¯8) link errors per second is sufficient for most networks.
To modify the setting for the LER-alarm, enter this command in privileged mode:
| Task | Command |
|---|---|
| Change the LER-alarm setting. | set fddi alarm mod_num/port_num value |
After entering the set fddi alarm command, you see this display:
Console> (enable) set fddi alarm 4/1 11 Port 4/1 alarm value set to 11. Console> (enable)
To verify that you have correctly set the LER-alarm value, enter the show fddi command. After entering this command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
The LER-cutoff value determines the LER at which a connection is flagged as faulty. This value is used in the LER threshold test. The default setting of 7 (10¯7) is sufficient for most networks.
To modify the LER-cutoff setting, enter this command in privileged mode:
| Task | Command |
|---|---|
| Change the LER-cutoff setting. | set fddi cutoff mod_num/port_num value |
After entering the set fddi cutoff command, you see this display:
Console> (enable) set fddi cutoff 4/1 10 Port 4/1 cutoff value set to 10. Console> (enable)
To verify that the LER-alarm setting is correct, enter the show fddi command. After entering this command, you see this display:
Console> show fddi Mod SMT User-Data T-Notify TReq --- -------------------------- -------- ------- 4 Engineering 15 3500 5 abc 20 150000 Port Tlmin Ler-CutOff Ler-Alarm ----- -------- ---------- --------- 4/1 40 10 11 4/2 40 10 11 5/1 40 10 11 5/2 40 9 12 Console>
This section describes how to assign a name to each port.
To set a port name, enter this command in privileged mode:
| Task | Command |
|---|---|
| Configure a name for a port. | set port name mod_num/port_num [name_string] |
After entering the set port name command, you see this display:
Console> (enable) set port name 1/1 Router Connection Port 1/1 name set.
To verify that you have correctly entered the port name, enter the show port mod_num/port_num command. After entering the command, you see this display:
Console> show port 4
Port Name Status Vlan Level Duplex Speed Type
---- -------------------- -------- ---------- ------ ------ ----- ------------
4/1 FDDI A standby 1 half 100 FDDI
4/2 FDDI B connect 1 half 100 FDDI
Ler
Port CE-State Conn-State Type Neig Con Est Alm Cut Lem-Ct Lem-Rej-Ct Tl-Min
---- -------- ---------- ---- ---- --------------- ---------- ---------- ------
4/1 isolated standby A U yes 9 11 10 0 0 40
4/2 isolated active B U yes 9 11 10 0 0 1340000
Last-Time-Cleared
----------------------------
Fri May 1 1998, 18:28:51
Console>
When ports request simultaneous access to the switching bus, the Catalyst 5000 series switch uses the port priority level to determine the order in which ports have access to the switching bus.
To set the priority level, enter this command in privileged mode:
| Task | Command |
|---|---|
| Configure the priority level for each CDDI or FDDI port. | set port level mod_num/port_num normal | high |
After entering the set port level command, you see this display:
Console> (enable) set port level 1/1 high Port 1/1 level set to high. Console> (enable) set port level 1/2 high Port 1/2 level set to high.
To verify that the port priority level is correct, enter the show port mod_num/port_num command. After entering this command, you see this display:
Console> (enable) show port 4 PortName Status Vlan Level Duplex Speed Type ----------------------------------------------------------------------------- 4/1FDDI ring notconnect 1 high half 100 FDDI 4/2 connected 1 high half 100 FDDI . . . Last-Time-Cleared ------------------------------ Fri May 1 1998, 16:27:24
To assign an Ethernet VLAN to map to the native VLAN on an FDDI port, perform the following task. The native VLAN must be an Ethernet type. The FDDI module translates all native (non-802.10) FDDI traffic to the assigned Ethernet VLAN.
To set up a native VLAN on FDDI, enter this command in privileged mode:
| Task | Command |
|---|---|
| Assign a VLAN to map to native traffic on an FDDI port. | set vlan vlan_num mod_num/port_num |
The VLAN designated in the set vlan command must be an Ethernet type VLAN. After entering the set vlan command, you see this display:
Console> (enable) set vlan 50 4/1 VLAN 50 modified. VLAN 1 modified. VLAN Mod/Ports ---- ----------------------- 50 4/1 Console> (enable)
To display VLAN information, enter the show vlan command. After entering this command, you see this display:
System1> (enable) show vlan 50
VLAN Name Type Status Mod/Ports
---- -------------------------- ----- --------- ----------------
50 VLAN0050 enet active 4/1-2
VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2
---- ---------- ----- ------ -------- ----- ------ ------ ------
50 100050 1500 0 0 0 0 0 0
This section describes how to set up an FDDI 802.10 VLAN trunk configuration. For information about how 802.10 trunks work, see the section "Understanding 802.10 Trunking on FDDI" later in this chapter.
These recommendations apply to setting up an FDDI 802.10 configuration:
Before setting up an FDDI 802.10 configuration, read the following sections:
After completing the prerequisites, complete these steps in privileged mode to set up the 802.10 VLAN configuration:
| Task | Command |
|---|---|
| Step 1 Provide a VLAN number and activate a VLAN in the management domain. | set vlan vlan_num |
| Step 2 Create a VLAN with the type FDDI. | set vlan vlan_num type fddi |
| Step 3 Map the Ethernet VLAN translation to an FDDI VLAN. | set vlan vlan_num translation vlan_num
or set vlan vlan_num translation vlan_num |
| Step 4 Turn trunking on for the FDDI port. | set trunk mod_num/port_num on |
Performing the task in Step 1 creates a VLAN but does not assign it to a port. VLAN Trunk Protocol (VTP) advertises the VLAN to available trunks of all types, such as Ethernet and FDDI, that are set to on for all Catalyst 5000 series switches in the same management domain.
To verify the VLAN configuration and mapping between Ethernet, FDDI, and Token Ring, enter the show vlan {trunk | no trunk} command and the show trunk command. If you enter the show trunk command after a 30-second delay, you see a display of the new VLAN that has been added to all Catalyst 5000 series switches. Refer to the FDDI 802.10 configuration example for a display of the show vlan command.
Figure 6-1 shows two Catalyst 5000 series switches in an FDDI 802.10 VLAN configuration.
The following prerequisites apply to the FDDI 802.10 configuration example shown in Figure 6-1:
After completing the tasks in "Configuring VTP, VLANs, VLAN Trunks, and VMPS," complete these steps in privileged mode to set up the FDDI 802.10 VLAN configuration for VLAN 33:
| Task | Command |
|---|---|
| Step 1 Provide a VLAN number and activate a VLAN in the management domain. | set vlan 33 |
| Step 2 Create a VLAN with the type FDDI. | set vlan 33 type fddi |
| Step 3 Map the Ethernet VLAN translation to an FDDI VLAN. | set vlan 333 translation 33
or set vlan 33 translation 333 |
| Step 4 Turn trunking on for the FDDI port. | set trunk 1/1 on |
After entering the set vlan 33 command, you see this display:
Console> (enable) set vlan 33 VTP: vlan addition successful
This command creates a VLAN but does not assign it to a port. VTP advertises the VLAN to all available trunks of all types (such as Ethernet or FDDI) that are set to on, for all Catalyst 5000 series switches in the same management domain.
After entering the set vlan vlan_num type fddi command, you see this display:
Console> (enable) set vlan 333 type fddi(said 338)VTP: vlan addition successful
After entering the set vlan vlan_num translation vlan_num command or the set vlan vlan_num translation vlan_num command, you see this display:
Console> (enable) set vlan 33 translation 333 VTP: vlan modification successful
After entering the set trunk 1/1 on command, you see this display:
Console> (enable) set trunk 1/1 on Port 1/1 mode set to on. Console> (enable)
To verify that the VLAN configuration is correct, including the mapping between Ethernet, FDDI, and Token Ring, enter the show vlan {trunk | no trunk} command and the show trunk command. After entering the show vlan command, you see this display:
Console> (enable) show vlan VLAN Name Type Status Mod/Ports ---- -------------------------- ----- --------- ---------------- 1 default enet active 1/1 2/3-4,2/7-12,2/14-16,2/18-24 11 VLAN0011 enet active 2/1-2 22 VLAN0022 enet active 2/5-6 33 VLAN0033 enet active 2/13,2/17 111 VLAN0111 fddi active 222 VLAN0222 fddi active 333 VLAN0333 fddi active 1002 fddi-default fddi active 1003 token-ring-default tring active 1004 fddinet-default fdnet active 1005 trnet-default trnet active VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2 ---- ---------- ----- ------ -------- ----- ------ ------ ------ 1 1 1500 0 0 0 0 0 0 11 11 1500 0 0 0 0 111 0 22 22 1500 0 0 0 0 222 0 33 100033 1500 0 0 0 0 333 0 111 111 1500 0 0 0 0 11 0 222 222 1500 0 0 0 0 22 0 333 338 1500 0 0 0 0 33 0 1002 1002 1500 0 0 0 0 0 0 1003 1003 1500 0 0 0 0 0 0 1004 1004 1500 0 0 0 0 0 0 1005 1005 1500 0 0 0 0 0 0 Console> (enable)
You can configure an FDDI interface so that it does not learn MAC addresses that it previously learned from an Ethernet interface by enabling the fddicheck option to the set bridge command. This feature resolves the problem that occurs when void frames on the FDDI ring and translated Ethernet frames sent by the FDDI interface are received and learned on the same FDDI interface instead of being stripped by the MAC hardware.
To reject MAC address learning, enter this command in privileged mode:
| Task | Command |
|---|---|
| Enable the set bridge fddicheck command. | set bridge fddicheck enable |
After entering the set bridge fddicheck enable command, you see this display:
Console> (enable) set bridge fddicheck enable FDDICHECK enabled Console> (enable)
To determine whether the fddicheck option is enabled, enter the show bridge command. After entering this command, you see this display:
Console> (enable) show bridge
APaRT Enabled
FDDICHECK Enabled
IP fragmentation Enabled
Default IPX translations:
FDDI SNAP to Ethernet 8023raw
FDDI 802.2 to Ethernet 8023
Ethernet 802.3 Raw to FDDI snap
Console> (enable)
To increase throughput performance, you can disable the software content-addressable memory (CAM) of the FDDI module. The CAM stores IPX translation information to support automatic packet recognition and translation (APaRT). Disabling the CAM disables APaRT, which automatically disables fddicheck. When APaRT is disabled, you can configure FDDI-to-Ethernet translation values using the set bridge ipx command. However, the Enhanced Address Recognition Logic (EARL) CAM continues to provide packet forwarding functionality. To enable fddicheck, first enable APaRT.
There are some serious drawbacks to disabling the CAM in the FDDI software. When you disable APaRT, only default IPX translations are used. Also, FDDI module hardware filtering is disabled, and all traffic from the FDDI ring is translated and forwarded to the Catalyst 5000 series switch backplane before the EARL CAM can filter it. This could greatly impact system performance.
To disable APaRT, enter this command in privileged mode:
| Task | Command |
|---|---|
| Disable the software CAM of the FDDI module. | set bridge apart disable |
After entering the set bridge apart disable command, you see this display:
Console> (enable) set bridge apart disable APaRT disabled Console> (enable)
To verify that the software CAM of the FDDI module, APaRT, and fddicheck command are disabled, enter the show bridge command. After entering this command, you see this display:
Console> (enable) show bridge
APaRT Disabled
FDDICHECK Disabled
IP fragmentation Enabled
Default IPX translations:
FDDI SNAP to Ethernet 8023raw
FDDI 802.2 to Ethernet 8023
Ethernet 802.3 Raw to FDDI snap
Console> (enable)
Enter the ping command to test the connection between a CDDI or FDDI module in the Catalyst 5000 series switch and a host residing anywhere in your network. The ping command pings a host once per second until a normal response is received. The host must be connected to a port with an address on the same IP network. Otherwise, you must configure a static route entry to reach the host network. To stop pinging, press Ctrl-C.
To check connectivity using the ping command, complete these steps:
| Task | Command |
|---|---|
| Step 1 Send an echo request from the Catalyst 5000 series switch to the host. Or, enter the traceroute command to display a hop-by-hop path through the IP network. | ping [-s] host [packet_size] [packet_count]
traceroute host |
| Step 2 If the host is unresponsive, check the configuration for the IP address of the Catalyst 5000 series switch and default IP route, if appropriate. | show interface
show ip route |
After entering the ping command, you see this display:
Console> (enable) ping 192.34.56.6 192.34.56.6 is alive
You can verify the results of a ping command in any one of the following ways:
The FDDI module functions as an FDDI-Ethernet translation bridge. It translates packets on the external FDDI ring into Ethernet packets within the Catalyst 5000 series switch. Inside a Catalyst 5000 series switch, Ethernet VLAN packets are translated into FDDI VLAN packets and encoded in 802.10 format with a SAID value before they are transmitted across an external FDDI trunk to another Catalyst 5000 series switch. The Catalyst 5000 series switch that receives the packets from the trunk decodes the 802.10 format using the SAID value and internally translates the FDDI VLAN packets into Ethernet VLAN packets. Each Ethernet VLAN requires a unique FDDI VLAN translation.
The Catalyst 1200 series switch is hardcoded with a specific VLAN-to-SAID configuration. Therefore, if you connect a Catalyst 5000 series switch Ethernet VLAN to a Catalyst 1200 Ethernet VLAN via an FDDI trunk, the SAID value of the FDDI VLAN must be the same value as the Ethernet VLAN. For example, if a Catalyst 1200 Ethernet VLAN value is 20, the translation FDDI VLAN SAID value must be 20.
VLANs can extend across an FDDI network by multiplexing switched packets over a CDDI/FDDI interface using the 802.10 protocol. Catalyst 5000 series CDDI/FDDI interface links can operate as interswitch trunks that provide broadcast control between configured VLANs. The 802.10 protocol encapsulates a VLAN identifier and packet data according to the IEEE 802.10 specification. CDDI/FDDI interfaces that support 802.10 make selective forwarding decisions within a network domain based upon the VLAN identifier.
The VLAN identifier is a user-configurable four-byte SAID. The SAID identifies traffic as belonging to a particular VLAN. It also determines to which VLAN each packet is switched.
See Figure 6-2 for an example of configuring FDDI trunks. In this example, the SAID ensures that packets destined for VLAN 1 only reach VLAN 1 after they are transmitted across the FDDI trunks. See Figure 6-3 for an example of an FDDI 802.10 VLAN network configuration.
VTP provides CDDI/FDDI module configuration for 802.10-based VLANs. VTP requires a protocol type (Ethernet, FDDI, or Token Ring) to be configured for each VLAN. A VLAN can only have one type associated with it. Each VLAN type must have its own unique identifier, and translations between different identifiers must be mapped. VTP advertises VLAN translation mappings to all Catalyst 5000 series switches in a management domain.
FDDI/CDDI modules integrate switched Ethernet and Fast Ethernet LANs into the FDDI network. To map an 802.10 FDDI VLAN to an Ethernet VLAN, you must map the 802.10 VLAN SAID to an Ethernet VLAN by mapping an Ethernet VLAN to an FDDI VLAN and assigning a SAID value to the FDDI VLAN.
If a CDDI/FDDI module receives a packet containing a VLAN SAID that maps to a locally supported Ethernet VLAN on the Catalyst 5000 series switch, the CDDI/FDDI module translates the packet into Ethernet format and forwards it across the switch backplane to the Ethernet module. CDDI/FDDI modules filter the packets they receive from reaching the backplane if the VLAN SAIDs in the packets do not map to a locally supported VLAN.
Figure 6-4 illustrates the configuration for forwarding a packet from the Ethernet module port 1 in slot 2 to the FDDI module port 1 in slot 5. For this example, you would specify the translation of Ethernet VLAN 2 to FDDI VLAN 22. FDDI VLAN 22 is translated automatically to Ethernet VLAN 2. The VLAN SAID must be identical on both FDDI modules. Since 802.10 CDDI/FDDI interface links can operate as interswitch trunks, you can configure multiple VLAN translations over a link.
CDDI/FDDI modules also support one native (nontrunk) VLAN, which handles all non-802.10 encapsulated FDDI traffic. You do not need to configure a translation number for the native VLAN since packets that are forwarded to the native VLAN do not contain VLAN identifiers. To map an Ethernet VLAN to an FDDI native VLAN, you must configure the FDDI port to be on the Ethernet VLAN. To do this, configure the Ethernet VLAN with the module number and port number of the FDDI-native VLAN.
This section contains examples of single and multiple switch configurations.
Figure 6-5 shows a simple Catalyst 5000 series switch configuration and includes these elements:
You can set up VLAN groups across multiple Catalyst 5000 series switches without trunking if the switches have any two ports of the same VLAN connected, as shown in Figure 6-6. You need to configure the VLANs individually for both switches using the set vlan command.
This example sets VLAN 10 for the Catalyst 5000 series switch in building A:
System1> (enable) set vlan 10 4/1-2 VLAN 10 modified. VLAN 1 modified. VLAN Mod/Ports ---- ----------------------- 10 4/1-2
This example sets VLAN 10 for the Catalyst 5000 series switch in building B:
System2> (enable) set vlan 10 4/1-2 VLAN 10 modified. VLAN 1 modified. VLAN Mod/Ports ---- ----------------------- 10 4/1-2
This example displays the VLAN 10 setting for the Catalyst 5000 series switch in building A:
System1> (enable) show vlan 10
VLAN Name Type Status Mod/Ports
---- -------------------------- ----- --------- ----------------
10 VLAN0010 enet active 4/1-2
VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2
---- ---------- ----- ------ -------- ----- ------ ------ ------
10 100010 1500 0 0 0 0 0 0
This example displays the VLAN setting for the Catalyst 5000 series switch:
System1> (enable) show vlan VLAN Name Type Status Mod/Ports ---- -------------------------- ----- --------- ---------------- 1 default enet active 1/1-2 10 VLAN0010 enet active 4/1-2 20 VLAN0020 enet active 2/1-24 1002 fddi-default fddi active 1003 token-ring-default tring active 1004 fddinet-default fdnet active 1005 trnet-default trnet active VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2 ---- ---------- ----- ------ -------- ----- ------ ------ ------ 1 100001 1500 0 0 0 0 0 0 10 100010 1500 0 0 0 0 0 0 20 100020 1500 0 0 0 0 0 0 1002 101002 1500 0 0 0 0 0 0 1003 101003 1500 0 0 0 0 0 0 1004 101004 1500 0 0 0 0 0 0 1005 101005 1500 0 0 0 0 0 0 System1> (enable)
This example displays the VLAN 10 setting for the Catalyst 5000 series switch in building B:
System2> (enable) show vlan 10 VLAN Name Type Status Mod/Ports ---- -------------------------- ----- --------- ---------------- 10 VLAN0010 enet active 4/1-2 VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2 ---- ---------- ----- ------ -------- ----- ------ ------ ------ 10 100010 1500 0 0 0 0 0 0
This example displays the VLAN 10 setting for the Catalyst 5000 series switch.
System2> (enable) show vlan VLAN Name Type Status Mod/Ports ---- -------------------------- ----- --------- ---------------- 1 default enet active 1/1-2 10 VLAN0010 enet active 4/1-2 20 VLAN0020 enet active 2/1-24 1002 fddi-default fddi active 1003 token-ring-default tring active 1004 fddinet-default fdnet active 1005 trnet-default trnet active VLAN SAID MTU RingNo BridgeNo StpNo Parent Trans1 Trans2 ---- ---------- ----- ------ -------- ----- ------ ------ ------ 1 100001 1500 0 0 0 0 0 0 10 100010 1500 0 0 0 0 0 0 20 100020 1500 0 0 0 0 0 0 1002 101002 1500 0 0 0 0 0 0 1003 101003 1500 0 0 0 0 0 0 1004 101004 1500 0 0 0 0 0 0 1005 101005 1500 0 0 0 0 0 0
|
|