VLAN Configuration
11-2
11
Note:
VLAN-tagged frames can pass through VLAN-aware or VLAN-unaware network
interconnection devices, but the VLAN tags should be stripped off before passing it
on to any end-node host that does not support VLAN tagging.
VLAN Classification
– When the switch receives a frame, it classifies the frame in
one of two ways. If the frame is untagged, the switch assigns the frame to an
associated VLAN (based on the default VLAN ID of the receiving port). But if the
frame is tagged, the switch uses the tagged VLAN ID to identify the port broadcast
domain of the frame.
Port Overlapping
– Port overlapping can be used to allow access to commonly
shared network resources among different VLAN groups, such as file servers or
printers. Note that if you implement VLANs which do not overlap, but still need to
communicate, you can connect them by enabled routing on this switch.
Untagged VLANs
– Untagged (or static) VLANs are typically used to reduce
broadcast traffic and to increase security. A group of network users assigned to a
VLAN form a broadcast domain that is separate from other VLANs configured on the
switch. Packets are forwarded only between ports that are designated for the same
VLAN. Untagged VLANs can be used to manually isolate user groups or subnets.
However, you should use IEEE 802.3 tagged VLANs with GVRP whenever possible
to fully automate VLAN registration.
Automatic VLAN Registration
– GVRP (GARP VLAN Registration Protocol)
defines a system whereby the switch can automatically learn the VLANs to which
each end station should be assigned. If an end station (or its network adapter)
supports the IEEE 802.1Q VLAN protocol, it can be configured to broadcast a
message to your network indicating the VLAN groups it wants to join. When this
switch receives these messages, it will automatically place the receiving port in the
specified VLANs, and then forward the message to all other ports. When the
message arrives at another switch that supports GVRP, it will also place the
receiving port in the specified VLANs, and pass the message on to all other ports.
VLAN requirements are propagated in this way throughout the network. This allows
GVRP-compliant devices to be automatically configured for VLAN groups based
solely on endstation requests.
To implement GVRP in a network, first add the host devices to the required VLANs
(using the operating system or other application software), so that these VLANs can
be propagated onto the network. For both the edge switches attached directly to
VA
VA: VLAN Aware
VU: VLAN Unaware
VA
tagged frames
VA
VU
VA
tagged
frames
untagged
frames
Summary of Contents for 8926EM
Page 6: ...ii ...
Page 34: ...Getting Started ...
Page 44: ...Introduction 1 10 1 ...
Page 62: ...Initial Configuration 2 18 2 ...
Page 64: ...Switch Management ...
Page 76: ...Configuring the Switch 3 12 3 ...
Page 118: ...Basic Management Tasks 4 42 4 ...
Page 164: ...User Authentication 6 28 6 ...
Page 176: ...Access Control Lists 7 12 7 ...
Page 284: ...Quality of Service 14 8 14 ...
Page 294: ...Multicast Filtering 15 10 15 ...
Page 300: ...Domain Name Service 16 6 16 ...
Page 310: ...Dynamic Host Configuration Protocol 17 10 17 ...
Page 320: ...Configuring Router Redundancy 18 10 18 ...
Page 344: ...IP Routing 19 24 19 ...
Page 356: ...Unicast Routing 20 12 20 Web Click Routing Protocol RIP Statistics Figure 20 5 RIP Statistics ...
Page 386: ...Unicast Routing 20 42 20 ...
Page 388: ...Command Line Interface ...
Page 400: ...Overview of the Command Line Interface 21 12 21 ...
Page 466: ...SNMP Commands 24 16 24 ...
Page 520: ...Access Control List Commands 26 18 26 ...
Page 546: ...Rate Limit Commands 30 2 30 ...
Page 612: ...VLAN Commands 34 24 34 ...
Page 626: ...Class of Service Commands 35 14 35 ...
Page 670: ...DHCP Commands 39 16 39 ...
Page 716: ...IP Interface Commands 41 36 41 ...
Page 768: ...IP Routing Commands 42 52 42 ...
Page 770: ...Appendices ...
Page 791: ......