Deploying ZoneDirector WLANs in a VLAN Environment
You can set up a ZoneDirector wireless LAN as an extension of a VLAN network environment by tagging wireless client traffic to specific VLANs. Then, when wireless traffic enters the wired network through an access point, it is automatically segmented into the proper VLAN before being forwarded toward its destination.
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 (see Figure below): VLAN 20 is used for internal clients, VLAN 30 is used for guest clients, and Management VLAN configuration is optional.
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:
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 an L3 connection between ZD and APs)
The following factors need to be taken into consideration:
- Default/Native VLAN configuration
- Where the DHCP/DNS servers sit in the architecture
- If tunneling is used for WLANs
- Trunking between switch ports