Controller Based WLANs

How to configure Centralized licensing?

Introduction- Instead of installing licenses on individual controllers, licenses can be pooled and shared among two or more controllers.  This eliminates tedious capacity planning, and eliminates the need for customers to buy extra licenses just for failover purposes. This is the function of Centralized Licensing.

 

Feature Notes- Essentially, after enabling centralized licensing, each controller will send all eligible licenses to a centralized pool on the master license server.  Once this is done, the master license server will notify the license clients about how many of the licenses are available during each system heartbeat.  Clients will request licenses, which will be subtracted from the total in the next heartbeat. 

 

Network Topology-

Master/Local individual clusters with the master acting as the licensing server - where the master will serve as the license server. The standby master will serve as the standby license server. There will be no support for a redundant license server in a topology with a single master. In a network with multiple master-local setups, each master will serve as the license server for its locals. License information will not be shared between those masters in such a topology. Local controllers cannot be a "license server".
All masters with one of the controllers acting as the designated licensing server -  The customer will need to designate one of the masters as the license server. Another of the controllers can be designated as the standby license server.
 
Configuration Steps- (config) # license profile
(License provisioning profile) #centralized-licensing-enable

## The following command can be used to specify the license server IP on the license client
(config)#License server-ip <ip>

## The following command can be used to specify the VRID and peer IP address for the standby license server.
(config)#License server-redundancy
(license-server-redundancy)#License-vrrp <vrId>
(license-server-redundancy)#Peer-ip-address <ip>
 
Answer- (Master-6.4.3-Beta-Abilash) #show license aggregate

Aggregate License Table
-----------------------
Hostname                   IP Address     AP    PEF   RF Protect  xSec Module  ACR   Last update (secs. ago)
--------                   ----------     ---   ---   ----------  -----------  ---   -----------------------
                           10.17.164.231  0     0     0           0            0     22
Aruba7240                  10.17.164.232  1024  0     0           0            0     4
Master-6.4.3-Beta-Abilash  10.17.164.230  1024  1024  1024        0            1024  13

Total AP License Count          :2048
Total PEF License Count         :1024
Total RF Protect License Count  :1024
Total XSEC License Count        :0
Total ACR License Count         :1024

(Master-6.4.3-Beta-Abilash) #
 
Verification- (Master-6.4.3-Beta-Abilash) #show license server-redundancy


 License Server redundancy configuration:
   License VRRP Id 164 current state is MASTER
   License Peer's IP Address is 10.17.164.231

Note: This config will be used only if this box is a master/backup license server

(Master-6.4.3-Beta-Abilash) #
 
Troubleshooting- (Master-6.4.3-Beta-Abilash) #show license heartbeat stats

License Heartbeat Table
-----------------------
Client IP Address HB Req HB Resp Total Missed Last Update (secs. ago)
----------------- ------ ------- ------------ -----------------------
10.17.164.231 58 58 0 1
10.17.164.232 26 26 0 13
10.17.164.230 29 29 0 22

(Master-6.4.3-Beta-Abilash) #
Version history
Revision #:
1 of 1
Last update:
‎04-01-2015 10:37 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.