Wireless Access

Occasional Contributor II

setting up centralized lic on controller

I am preping my environment to add a second controller.  I updated to this morning and was going to turn on Centralized Lic.  If this controller (my only prod controller right now) will be the master, do I simply put a check in the box to enable centralized lic and not put anything in for server address?


When I enable will this cause APs to bootstrap or an outage of any type?

Guru Elite

Re: setting up centralized lic on controller

Centralized Licensing is a global option in a master/local or master/backup master configuration.  Once you turn it on, it is turned on for any contoller you add as a local.  Enable centralized licensing on your Master (only) controller and when you add a local, it will automatically inherit thta setting.  You do not have to put anything in for the server address.  Putting in a server address is necessary if you want to add/point a separate Master controller to an existing Centralized Licensing Server Deployment.




 Access points will not bootstrap.

*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.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Regular Contributor II

Re: setting up centralized lic on controller

I have a Master/Local setup. We have only one Master and two local controllers. I have the question of if the Master is setup as the license server and it goes down what happens to the local controllers to get licenses for APs? Do I configure one of the controllers as a backup license server?

Trusted Contributor I

Re: setting up centralized lic on controller

i believe (still getting up to speed on this) that you will be fine for 30 days without a license server. probably as long as you dont need to add new APs.


from the 6.3 user guide:


  • Server is Unreachable

If a licensing client does not receive 3 consecutive heartbeats from the server, it assumes that the server is down, and that any APs directly associated to the server are also down or have failed over to another controller. The client then adds any licenses used by the licensing server into to the pool of available licenses on that client. When a license client is unable to reach a license server for 30 consecutive days, it removes any shared licenses pushed to it from the licensing server, and reverts to its installed licenses. If the 30-day window has passed and yet controller does not have enough installed licenses for all its associated APs, the controller will nonetheless continue to support each AP. However, when an AP reboots and its controller does not have enough licenses, that AP will not come up.


a backup license server would help, but i dont believe you can make a local a license server.


from the 6.3 user guide:


  • A single master controller is connected to one or more local controllers.

Only the master controller can be a license server. A local controller can only be license client, not a license server.


  • A master and standby master are connected to one or more local controllers.

The master license server will reside on the master controller, and the standby license server will reside on the standby master controller. Local controllers can only be license clients, not license servers.

Search Airheads
Showing results for 
Search instead for 
Did you mean: