cancel
Showing results for 
Search instead for 
Did you mean: 

Issues configuring VLANs on Single AP Deployment of 7372

steven_yurgelev
New Contributor II
Hi Everyone,

As a preface, I worked with Ruckus support directly on this issue and the tech stated that my configuration looks correct and it might be the AP, but I am having this issue on another AP as well.

In short, when attempting to connect to either of the SSIDs from the AP, it sits at the point where it states "Obtaining IP Address" but the device never hands out the address.

In this environment, I have a SonicWall NSA 220 with two VLANs configured as 10 and 20. The 10 VLAN is for the corporate WIFI and is a seperate subnet from their primary subnet. The same is true for VLAN 20 as well but this is another subnet for the guest network.

DHCP is turned on on the SonicWall for both of these VLANs. The AP is connected to a 1900 series HP POE switch on port 9 which is untagged on VLAN1 (default VLAN) and has tagged memebership on VLAN 10 and 20. Then on the AP itself, obviously each SSID is specified to use the specific VLAN.

I simply can't figure out why the hell this device is unable to assign an address out from the WAP. Does anyone have any ideas or can maybe set me on the right path? Please let me know if you require more information.
14 REPLIES 14

steven_yurgelev
New Contributor II
Also, same issue with a ZoneDirector involved as well....

cordelia_cordel
Contributor
Hi Steven,

I went and looked at your recent cases and I saw that you last talked with a TSE in late November. We tried to contact you to see if we resolved your issue re: the AP -- perhaps you were on vacation or did not receive the pings? Can we open another case for you with one of our Tier 2 specialists?

We want to make sure we give you the full support you need.

Best regards,

Cordelia

raghavendra_rag
New Contributor II
Hi Steven,

As per our last discussion, everything is working fine without any issue.
Any further queries please do let us know.

Regards,
Raghavendra.

steven_yurgelev
New Contributor II
Yep, would like to let everyone know who reads this that the 100.x version firmware for the devices seems to resolve the issue.

Anyone have an idea what change was made that might have helped resolve this?

raghavendra_rag
New Contributor II
Hi Steven, 

We need to debug live by taking packet captures. It should have worked on previous code but not sure what happened.

If you have some time, we can definitely do some more debugging to find the root cause.

Thanks & Regards,
Raghavendra.