Ruckus Wireless ZoneDirector 3000, User Manual, Page: 200 / 430

Deploying ZoneDirector WLANs in a VLAN Environment
Viewing a List of APs That Belong to a WLAN Group
200
Ruckus Wireless, Inc.
Deploying ZoneDirector WLANs in
a VLAN Environment
NOTE: Configuring VLANs for ZoneDirector, Access Points and wireless clients is
not required for normal operation, and should not be undertaken without a thorough
understanding of your network’s VLAN environment and switch port configuration.
You can set up a ZoneDirector wireless LAN as an extension of a VLAN network
environment by tagging wireless client traffic to specific VLANs. Qualifications
include the following:
• Verifying that the VLAN switch supports native VLANs. A native VLAN is a
VLAN that allows the user to designate untagged frames going in/out of a
port to a specific VLAN.
• For example, if an 802.1Q port has VLANs 1, 20, and 30 enabled with VLAN
1 being the native VLAN, frames on VLAN 1 that egress (exit) the port are not
given an 802.1Q header (i.e., they are plain Ethernet frames). Frames which
ingress (enter) this port and have no 802.1Q header are assigned to VLAN
1. Traffic from WLANs configured with access VLANs 20 and 30 is tagged
with an 802.1Q header containing the respective VLAN assignment before
being forwarded to its destination on the Ethernet network.
• Connecting ZoneDirector and any Access Points (APs) to trunk ports on the
switch.
• Verifying that those trunk ports are on the same native VLAN.
Example configuration ( Figure 106 ): VLAN 20 is used for internal clients, VLAN 30
is used for guest clients, and Management VLAN configuration is optional.