Wireless Access

Reply
Contributor II
Posts: 44
Registered: ‎04-06-2011

IOS / Android / DHCP / Aruba issues

Hello,

 

At our facility, we have about 1000 guests stay for a week, with a new group rotating in/out every week.  Most of them have multiple devices so we see a large number of  IOS WiFi clients.  For our guest Internet WiFi, we have two Windows 2003 DHCP servers, with the DHCP scope split for redundancy.

 

There seems to be an issue with IOS and some Android devices obtaining new IP addresses much sooner than the 24 hour lease we have configured.  We have seen a device have five different IP addresses during an 8 hour period.  Because of this DHCP turnover, some valid clients boot up and get an IP address that an IOS/Android device had previously only a few minutes earlier.  When this happens, often the valid customer isn't able to reach our captive portal page or may have other connectivity issues.  Looking at their session in the controller, we see the customer's IP mismatched with the MAC of a different device (usually IOS or Android) that previously had the IP address.  Doing an "aaa user delete" for both the MAC and IP fixes the problem, but this isn't a long-term solution. 

 

Has anyone else experienced this IOS/Android DHCP turnover and related client issues it creates?

 

Thanks,

Bryan

 

 

Guru Elite
Posts: 21,023
Registered: ‎03-29-2007

Re: IOS / Android / DHCP / Aruba issues

What version of code are you running?

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor II
Posts: 44
Registered: ‎04-06-2011

Re: IOS / Android / DHCP / Aruba issues

We're on 6.1.3.0 -- two 6000 controllers in a redundant master setup.  We saw similar behavior on 6.0.2.0 but had to get off that version because of bandwidth contract issues.

 

 

Thanks,

Bryan

 

Guru Elite
Posts: 21,023
Registered: ‎03-29-2007

Re: IOS / Android / DHCP / Aruba issues

Thank you.

 

You have the option of trying "Enforce DHCP" in the AAA profile to deal with this.  If a device has an address that is statically assigned or did not receive his ip address as a result of a DHCP transation, he will be denied entry to the user table.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: