Wireless Hardware and VLANs

[TechMonkey]

I may be over thinking this.

 

We have VLANs setup. We have Ruckus kit. Should the controller and APs sit in the WIFI VLAN or the Management (Switches) VLAN? My first thought is it should be the Management VLAN as we could potentially have multiple VLANS going through the APs, but how do you set the traffic to go through a different VLAN than the AP is on?

[FN-GM]

You would be best putting the controller and AP's in the management VLAN.

 

To get your SSID's on separate VLANs you set the VLAN ID for the SSID on the controller and connect your access point to the switch via 802.1q trunk (or whatever your particular switch vendor calls it)

[jtotheb]

I may be over thinking this.

 

We have VLANs setup. We have Ruckus kit. Should the controller and APs sit in the WIFI VLAN or the Management (Switches) VLAN?

 

We went as far as to have a VLAN for controllers and AP management as we've a moderately large deployment. The Wifi management VLAN doesn't carry wifi client data. The connection to the AP is a trunk with all of the appropriate VLANs allowed.

 

The VLAN to SSID setting is tucked away under the advanced options of the WLAN.

[dapaulio]

Our controller sits on the same vlan as our switches then the ap' s have their own management vlan and then we have two ssid (clients and byod) who each have their own vlan.

I think it's personal preference really if you have the resources to achieve it. Some networks may not have the ip range to accommodate a wide segregation of vlans so some consolidation may be necessary to keep it tidy

[White_Fi]

Best setup would be to have the ZD and APs in there own VLAN or an existing mgmt VLAN.

The switch ports should be untagged (native) on this VLAN and tag on any VLANs you wish to carry over the WLANs.

 

It is not necessary to have the ZD switch ports also tagged with your WLAN VLANs unless you want to make use of the Bonjour Gateway feature on the ZD.