03-20-2014 07:51 PM
I have a found a quirk with my Aruba Instant Wireless network.
I have 18 IAP 105's and 2 recently added 2 x 225's. One of the 225's has assumed master of the Virtual Controller but I found a quirk with random ipad/iphones trying to connect on the 225.
I receive an alert saying "
DHCP request timed out
AP20 C BLOCK C2.
It then just gives it an IP address starting with 169.254._._
If i then walk over to another AP which is an IAP 105 and turn my wifi on and off my device it then instantly connects.
Does anyone have a similar thing happen or any ideas as to what im missing??
03-22-2014 07:06 AM
What is providing DHCP on that network?
What version of instant are you running?
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
Validated Reference Design Guides : http://community.arubanetworks.com/t5/Validated-Reference-Design/tkb-p/Aruba-VRDs
03-26-2014 05:08 AM
I ran into the same issue with IAP 225 running 184.108.40.206-220.127.116.11 specialy with the 2.4GHZ clients. the clients werent getting the ip address and in the VC it was showing DHCP request timeout.
1st i reduce the power but it didnt work well and still the clients werent getting the IP address after that disabled the client match, on restarting the IAP i was able to get the ip address.
So far its working fine have to check the behaviour for some time.
03-26-2014 03:01 PM
The version of firmware is 18.104.22.168-22.214.171.124_42384.
I am using windows Server 2008 R2 to give out DHCP. I have 2 of these running on my network.
I use radius to authenticate against windows AD.
I have 20 x IAP 105's and 2 x 225's. I have noted that the wireless network will not run cohesively unless one of the 225's is the master.
I use a virtual controller which is why we bought the IAP series in the first place.
Can you think of anything else which would help.
04-02-2014 08:54 PM