Default WLAN Password of Ruckus ZoneFlex 7352 – How to Find

If you don't need to confuse your users with multiple VLANs, don't do it. Leverage the tools you have. You mentioned you have ISE and you should be able to do all this with one SSID. As AdnanG already mentioned, you can utilize the profiling features of ISE to classify the devices.

Your ACS should be able to tie into the MS AD authentication and be able to provide user authentication and group information.

From there, you just need to combine the user/groups with the device profiles and then tie it to a VLAN. So, for instance, if the device is identified as a cell phone and the user is part of "group A", then the get put in the "group A - internet" VLAN.

I haven't done it personally with ISE, so can't give exact steps, but this is how Cisco marketing is selling ISE in the BYOD space. I also know of several people who have done similar setups to what is suggested. I would start by looking through this Cisco BYOD document that would give you a general overview of how BYOD is done with with Cisco ISE.

The issue was to do with VLAN tagging. While I was tagging on the correct VLAN, the WAP didn't respond well to this. After a support call with Ruckus we decided to untag the VLAN on the WLAN the WAP provides. By setting the Access VLAN to 1 it makes no attempt to tag the traffic. Since the port to the Ruckus is already trunked to a specific VLAN this is fine for our network.

To fix this issue in the future using the same method do the following:

1. Log in to Zone Director
2. Click on "Configure" Tab
3. Click on "WLANs" on the left menu
4. Click "Edit" on the WLAN you want to provide to the WAP
5. Click "Advanced Options"
6. Set the "ACCESS VLAN" setting to "1" to untag