Re: AP's losing config and becoming non-broadcasting potatoes....
05-06-2015 04:05 AM
That is essentially what is going on with some of mine with one exception, reboots will not bring them back up. Like I said earlier, I have to fully factory reset them. very odd. Someone asked what version I am running on my controllers - 184.108.40.206 is what I am running on all of mine. Also, this is not restricted to a single controller. I have it happening on a few at out North Campus on a 3600US controller and a few at our main Downtown Campus on a 7210US controller.
Please upgrade from 220.127.116.11 when you can. There are plenty issues fixed with 18.104.22.168 and beyond.
In addition, very few users actually deploy static ip addresses, but when you do, you can run the serious risk of assigning a device that already has that ip address, or a device TAKES the ip address of an existing access point and it will function like you said. Aruba APs were designed primarily to have dynamic ip addresses because it is such a chore to maintain static ip addresses. They are normally monitored using an NMS that polls the controller to get up to date information about the devices like ip addressing. You have only given us limited information about your issue, so it is hard to say what is happening, but the initial step of upgrading your ArubaOS could definitely help other problems.
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars