12-02-2013 10:23 PM
We have configured two aruba controllers as master and local with more than 70 Aps. DHCP servers are configured in controllers as bellow.
Master VLAN -192.168.32.0 Excluding 192.168.32.1 to192.168.32.128
Local VLAN-192.168.32.0 Excluding 192.168.32.129 to192.168.32.253
Lease time on both controllers 1Day 1Hour 10min
Aruba OS version is 18.104.22.168
Sometimes users get IP s from 169.X.X.X range when disconnecting and connecting to that SSID. How i resolve/find that problem?
IS this because the longer lease time? What is the recommended lease time for DHCP server?
Solved! Go to Solution.
12-03-2013 12:51 AM
The 169.xx address range is usually self assigned by the device when it fails to receive a DHCP address. The lease time can be anything that works in your situation - for regular corporate clients could be up to a month but for busy guest networks can be as low as five minutes.
12-03-2013 04:26 AM
You can setup debugging on the controller - "logging level debugging network subcat dhcp". the after the clients have failed run -
show log network all. Additionally the lease can be viewed on the controller using - show ip dhcp binding.
12-03-2013 04:29 AM
How i verify the reason for not issuing IP address for this device.(this is not continuous problem, but we have find the reason)
You could try using an external DHCP server to see if the problem goes away. Using a split scope is tricky. It is quite possible that you are running out of DHCP addresses, or your clients are not handling the duplicate addresses possibly. Is that the only DHCP scope you are running on the controller(s)?
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
12-05-2013 03:17 AM
Thanks for your all replies. We found this is happen due to issues all ip addresses for wireless devices from DHCP server(There is no free leases). Hence we reduce our DHCP lease time. Now we are work fine.