Users Guide

Table Of Contents
Topology Example
All controllers are master controllers.
The master and standby licensing servers must
be defined.
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.
A licensing server supports multiple
master/local domains.
Starting with ArubaOS 6.5, the centralized
licensing feature supports topologies where
multiple master controllers have one or more
attached local controllers.
NOTE: This topology requires that all local
controllers are able to access the licensing
server.
Table 23: Centralized Licensing Topologies
Multi-Version Licensing
ArubaOS supports multi-version licensing, which allows centralized licensing clients to run a different version of
ArubaOS than the primary and backup licensing servers. If a license is introduced in a newer version of
ArubaOS, the primary and backup licensing servers set can still distribute licenses to licensing clients running an
older version of ArubaOS, even if the licensing client does not recognize the newer license type.
This feature is only supported in deployment topologies where all are configured as master controllers. Both
the licensing server(s) and licensing clients must be running a version of that supports this feature. The multi-
Dell Networking W-Series ArubaOS 6.5.x | User Guide Software Licenses |
83