10-09-2015 08:15 AM
we have a site of 26 Aruba's AP, some 205 model and some 225 model In this site, we have only 1 of the AP's that is having a problem, and computers can not see the DHCP and get APIPA, but not always. we restart the AP and it will be good, some times for a day or two up to a week.
Last time this occured we had 25 connections, 12 had a correct IP address scheme, and the other 13 had an APIPA IP.
Lease wise the DHCP is fine, we have 3 SSID's broadcast, 2 of them with a /21 and the third a /22, and only have a total 250ish connections. and double checked the DHCP, none of the scopes are even close to be out of IP's.
We have replaced the AP and still have problems.
We are going to upgrade the firmware this Tuesday but having a problem understanding why nly ONE AP is having a problem. and none of the other 25.
Any thoughts as to why this might occur?
10-09-2015 08:20 AM - edited 10-09-2015 08:21 AM
Forgot to mention we have a total of 80 AP's throughout 2 campus' , and this is the ONLY AP that is having this problem. We have a seperate control on each Campus.
10-18-2015 10:37 AM
did the firmware solve the issue?
i would try another replace, just to rule out the obvious. if the issue remains, compare the other things, switchport config, switch itself, uplink towards rest of network.
10-19-2015 03:47 AM
what AOS version are you on ? There was a known bug in client match that could manifest in the way you are describing here.
10-19-2015 02:58 PM
If the known bug in prior code gets ruled out, I'd look at layer2 -- is the cable/jack/switch AOK?
Packet cappture a client DHCP request from the PA or on the wire (at the controller edge unless you're trerminating connections at the AP) and see if everything looks good.
if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it