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 (see Figure below): VLAN 20 is used for internal clients, VLAN 30
is used for guest clients, and Management VLAN configuration is optional.
Figure 120: Sample VLAN configuration
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)
The following factors need to be taken into consideration:
• Default/Native VLAN configuration
173
Ruckus Wireless ZoneDirector™ Release 10.0 User Guide
Managing a Wireless Local Area Network
Deploying ZoneDirector WLANs in a VLAN Environment
