Port-based VLANs
179
■
If you define FDDI DAS ports, select the lowest-numbered port in the
DAS pair when you define the ports in the VLAN. The
higher-numbered port in the DAS pair is not selectable. See Chapter 6.
■
Decide whether you want the ports that you are specifying for the
VLAN interface to be shared by any other VLAN interface on the
system. Shared ports produce
overlapped
VLANs; ports that are not
shared produce
nonoverlapped
VLANs.
■
The per-port tagging options are IEEE 802.1Q tagging or no tagging.
The IEEE 802.1Q tagging option embeds explicit VLAN membership
information in each frame.
■
Overlapped VLANs require tagging; that is, two port-based VLAN
interfaces may contain the same bridge port if one of the VLAN
interfaces defines the shared port to use IEEE 802.1Q tagging. This
rule is true for either allOpen or allClosed mode. For example, a shared
bridge port is set to tagging none for one VLAN and IEEE 802.1Q
tagging for the other VLAN, or IEEE 802.1Q tagging for each VLAN.
■
Port-based VLANs use the protocol type unspecified.
■
To define a port-based VLAN interface, specify this information:
■
A VID in the range 2 through 4094, or accept the next available
VID.
■
The bridge ports that are part of the VLAN. If you have trunk ports,
specify the anchor port for the trunk. For FDDI DAS ports, specify
the lowest-numbered port in the DAS pair.
■
The protocol type unspecified.
■
Tag status (none or IEEE 802.1Q).
■
The unique name of the VLAN interface.
Example 1: Nonoverlapped VLANs
Figure 28 shows two systems that have nonoverlapping port-based
VLANs and no port tagging. Ports 1 through 4 on Device1 make up the
VLAN called unspecA, while ports 5 through 8 make up unspecB. All
frames that are received on a port are assigned to the VLAN that is
associated with that port. For instance, all frames that are received on
port 2 in unspecA are assigned to unspecA, regardless of the data
contained in the frames. After an incoming frame is assigned to a VLAN,
the frame is forwarded, filtered, or flooded within its VLAN, based on the
standard bridging rules.
Summary of Contents for CoreBuilder 3500
Page 44: ...44 CHAPTER 2 MANAGEMENT ACCESS ...
Page 58: ...58 CHAPTER 3 SYSTEM PARAMETERS ...
Page 86: ...86 CHAPTER 5 ETHERNET ...
Page 112: ...112 CHAPTER 6 FIBER DISTRIBUTED DATA INTERFACE FDDI ...
Page 208: ...208 CHAPTER 9 VIRTUAL LANS ...
Page 256: ...256 CHAPTER 10 PACKET FILTERING ...
Page 330: ...330 CHAPTER 12 VIRTUAL ROUTER REDUNDANCY PROTOCOL VRRP ...
Page 356: ...356 CHAPTER 13 IP MULTICAST ROUTING ...
Page 418: ...418 CHAPTER 14 OPEN SHORTEST PATH FIRST OSPF ...
Page 519: ...RSVP 519 Figure 94 Sample RSVP Configuration Source station End stations Routers ...
Page 566: ...566 CHAPTER 18 DEVICE MONITORING ...
Page 572: ...572 APPENDIX A TECHNICAL SUPPORT ...
Page 592: ...592 INDEX ...