Vlan Workgroups And Traffic Management; Typical User Vlan Configurations - HP WL520 User Manual

vlan workgroups and traffic management

vlan workgroups and traffic management
vlan workgroups and traffic management vlan workgroups and traffic management
Traditional, dual-slot access point devices that are not VLAN-capable typically broadcast and multicast traffic on wireless
Network Interface Cards (NICs). This process wastes wireless bandwidth and degrades throughput performance. In
comparison, the dual-slot, VLAN-capable HP WL520 device is designed to efficiently manage delivery of broadcast, multicast,
and unicast traffic to wireless clients.
The HP WL520 device assigns clients to one of two VLANs designated by a network name. First, each one of the wireless NICs
in the HP WL520 device is configured with a unique network name and an 802.1Q-compliant VLAN identifier. Each NIC
represents a VLAN.
Each network client is then assigned one of the two wireless NIC network names. The HP WL520 device matches packets
transmitted or received to a network name with the associated VLAN. Traffic received by a VLAN is only sent on the wireless
NIC associated with that same VLAN. This eliminates unnecessary traffic on the wireless LAN, conserving bandwidth and
maximizing throughput.
traffic management traffic management traffic management traffic management
In addition to enhancing wireless traffic management, the VLAN-capable HP WL520 device supports easy assignment of
wireless users to workgroups. In a typical scenario, each user VLAN represents a workgroup; for example, one VLAN could be
used for an EMPLOYEE workgroup and the other, for a GUEST workgroup.
In this scenario, the HP WL520 device would assign every packet it accepted to a VLAN. Each packet would then be identified
as EMPLOYEE or GUEST, depending on which wireless NIC received it. The HP WL520 device would insert VLAN headers or
"tags" with identifiers into the packets transmitted on the wired backbone to a network switch.
Finally, the switch would be configured to route packets from the EMPLOYEE workgroup to the appropriate corporate resources
such as printers and servers. Packets from the GUEST workgroup transmitted on the same network as packets from the
EMPLOYEE workgroup, could, in contrast, be restricted to a gateway that allowed access to only the Internet. A member of the
GUEST workgroup could send and receive e-mail and access the Internet, but would be prevented from accessing servers or
hosts on the local corporate network.

typical user vlan configurations

typical user vlan configurations typical user vlan configurations typical user vlan configurations
VLANs segment network traffic into workgroups, which enable you to limit broadcast and multicast traffic. Workgroups enable
clients from different VLANs to access different resources using the same network infrastructure. Clients using the same physical
network are limited to those resources available to their workgroup. The three primary scenarios for use of the VLAN support
feature are detailed as follows:
– Scenario 1: Setting Up Independent VLAN Workgroups ("Tagged" User VLANs)
– Scenario 2: Setting Up Independent VLAN Workgroups (Tagged & Untagged User VLANs)
– Scenario 3: Setting Up One VLAN Workgroup (One Tagged VLAN)
setting up independent "tagged" user vlan workgroups setting up independent "tagged" user vlan workgroups
setting up independent "tagged" user vlan workgroups setting up independent "tagged" user vlan workgroups
The HP WL520 tags all traffic received from wireless clients transmitted on either the wired or the wireless backbone (see
description of Wireless Distribution System (WDS) feature in this User Guide) with a header identifying each packet as
belonging to one VLAN workgroup, or another.
To configure this scenario, set up two different workgroups with separate VLAN Identifiers (IDs).
VLAN ID for Wireless NIC in Slot A = a number between 1 and 4094 (per the IEEE 802.1Q standard)
VLAN ID for Wireless NIC in Slot B = a number between 1 and 4094
NOTE:
The number configured for the wireless NIC in Slot A must be different than the number configured
for the wireless NIC in Slot B.
VLAN Support
4-5