Users Guide

Client controllers do not share information about built-in licenses to the licensing server. A controller using the
centralized licensing feature will use its built-in licenses before it consumes available licenses from the license
pool. As a result, when a client controller sends the licensing server information about the licenses that a client
is using, it only reports licenses taken from the licensing pool, and disregards any built-in licenses used. For
example, if a controller has a built-in 16-AP license and twenty connected APs, it will disregard the built-in
licenses being used and report to the licensing server that it is using only four AP licenses from the license pool.
When centralized licensing is first enabled on the licensing server, its licensing table only contains information
about the licenses installed on that server. When the clients contact the server, the licensing server adds the
client licenses to the licensing table, then sends the clients information about the total available licenses for
each license type. In the following example, the licenses installed on two client controllers are imported into the
license table on the license server. The licensing server then shares the total number of available licenses with
other controllers on the network.
Figure 11 Licenses Shared by Licensing Clients
When a new AP associates with a licensing client, the client sends updated licensing information to the server.
The licensing server then recalculates the available total, and sends the revised license count back to the clients.
If a client uses an AP license from the license pool, it also consumes a PEFNG and a RFProtect license from the
pool, even if that AP has not enabled any features that would require that license. A controller cannot use more
licenses than what is supported by its controller platform, regardless of how many licenses are available in the
license pool.
Dell Networking W-Series ArubaOS 6.4.x | User Guide Software Licenses | 150