Wireless Access

Interesting problem after a power outage. We have 250 or some Aruba Ap's with a license pool of 582 AP licenses on the Mobility Conductor. 

For some reason, after a power outage we had, none of the APs are able to remain on, try to connect to the Conductor but fail to pull a license. Because they don't have a license, they reboot. 

I've even gone so far as disabling CPSEC just to allow anything to connect to the Conductor, but that hasn't changed anything. 

Has anyone here ever had APs not be able to pull a license from the Conductor before?? 

Conductor or controller?  The Mobility Conductor is meant for managing the Mobility Controllers.  APs should always be connecting to a controller.

If this was an operational environment before the power outage, and non-functional afterwards, you should be opening a P1 case with TAC.

Thanks for the reply. You're right. I meant to say "When AP's tried connecting to the controllers, they weren't pulling a license from the conductor".
------------------------------------------------------------------------------------------
If anyone else runs across this, make sure the AP's can communicate with the controllers.

Thinking about the design, I'm sure if your APs once were imported into the conductor, it would remember them and show in the dashboard, just not sure why they would show UP for a brief moment of time and then DOWN. This led me down a APs aren't getting a license rabbit hole thinking that was the problem. 

The root cause was a heartbeat issue. The controllers weren't able to communicate with the APs, as chucher suggested.

The switch the controllers were plugged into lost the vlan config trunking the "data vlan" the aps were on to the controllers during a power outage. 

Once we readded the vlans to the links heading to the controllers and verified we could ping an AP from the controller, our APs started to get the licensing from the conductor as expected and the problem resolved. 

Hope this helps.