Using Stp On A Network With Multiple Vlans - 3Com SuperStack 3 3812 Implementation Manual

48 C 4: U
HAPTER SING
Using STP on a
Network with
Multiple VLANs
R F
ESILIENCE EATURES
The IEEE Std 802.1D, 1998 Edition does not take into account VLANs
when it calculates STP information — the calculations are only performed
on the basis of physical connections. For this reason, some network
configurations can result in VLANs being subdivided into a number of
isolated sections by the STP system. Therefore, you must ensure that any
VLAN configuration on your network takes into account the expected STP
topology and alternative topologies that may result from link failures.
For example, Figure 11
are connected using the 802.1Q-tagged link between Switch B and
Switch C. By default, this link has a path cost of 100 and is automatically
blocked because the other Switch-to-Switch connections have a path cost
of 36 (18+18). This means that both VLANs are now subdivided — VLAN
1 on Switch units A and B cannot communicate with VLAN 1 on Switch
C, and VLAN 2 on Switch units A and C cannot communicate with VLAN
2 on Switch B.
Figure 11 Configuration that separates VLANs
100BASE-TX
full duplex link
carrying VLAN 1 only
(path cost 18)
To avoid any VLAN subdivision, it is recommended that all inter-Switch
connections are made members of all available 802.1Q VLANs to ensure
connectivity at all times. For example, the connections between Switches
A and B, and between Switches A and C should be 802.1Q tagged and
carrying VLANs 1 and 2 to ensure connectivity.
For more information about VLAN Tagging, see
Virtual LANs".
shows a network containing VLANs 1 and 2. They
Switch B
Block
802.1Q-tagged,
10BASE-T half duplex link
carrying VLANs 1 and 2
(path cost 100)
Switch A
100BASE-TX
full duplex link
carrying VLAN 2 only
(path cost 18)
Switch C
Chapter 8 "Setting Up