Ruckus Wireless ZoneDirector 1100 User Manual page 144

Managing a Wireless Local Area Network
Deploying ZoneDirector WLANs in a VLAN Environment
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
guest clients, and Management VLAN configuration is optional.
Figure 85.
You must ensure that switch ports are configured properly to pass the VLAN traffic necessary
for ZoneDirector, AP and client communications. In the sample VLAN scenario above, the switch
ports would need to be configured as follows:
• Corp VLAN: 20
• Guest VLAN: 30
• Management VLAN: (optional)
Some common VLAN scenarios include:
• WLANs assigned to specific VLANs; ZD and APs with no management VLAN
• WLANs assigned to specific VLANs; ZD and APs within their own single management VLAN
• WLANs assigned to specific VLANs; ZD and APs are configured for management VLAN,
but are different VLANs and there is an L3 connection between (typical branch/remote office
deployments)
• WLANs assigned to specific VLANs; ZD or APs only (not both) configured with management
VLAN (again typically with a L3 connection between ZD and APs)
(Figure 85): VLAN 20 is used for internal clients, VLAN 30 is used for
Sample VLAN configuration
132