Although a client switch retains its licensing information for 30 days after it loses contact with the licensing server, if
the client reboots at any time during this 30-day window, the window will restart, and the client will retain its
information for another 30 days.
APs that use centralized licensing in conjunction with an AOS-W high availability feature behave differently than
APs that do not use a high availability solution. APs using VRRP redundancy, a backup LMS, or the AOS-W fast
failover feature can quickly fail over to a backup switch, even if that backup switch does not have any AP
licenses at the time of the failover. However, if that AP reboots, it will not obtain its licenses until the backup
switch receives the required licenses from the licensing master.
Client is Unreachable
The centralized licensing feature sends keepalive heartbeats between the license server and the licensing client
switches every 30 seconds. If the licensing server fails to receive three consecutive heartbeats from a client, it
assumes that the licensing client is down, and that any APs associated with that client are also down or have
failed over to another switch . Therefore, the licensing server adds any licenses used by that client back into the
available pool of licenses. If the license server fails to contact a license client for 30 consecutive days, any
licenses individually installed on that client will be removed from the server’s license database.
The WebUI of the licensing client and the licensing server both display a warning message when a licensing client
and licensing server are unable to communicate.
Server is Unreachable
If a licensing client does not receive three 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 switch.
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 the switch does not have enough installed licenses for all of its associated APs, the switch will
nonetheless continue to support each AP. However, when an AP reboots and its switch does not have enough
licenses, that AP will not come up.
For more information on replacing a switch using the centralized licensing feature, see Replacing a Switch on page
49
Configuring Centralized Licensing
The steps to configure centralized licensing on your network vary, depending upon whether you are enabling
this feature in a network with a master-local switch topology, or in a network where all switches are configured
as masters. Before you enable this feature, you must ensure that the switches are able to properly
communicate with the licensing master. Once you have identified your deployment type, follow the steps in
the appropriate section below.
Pre-configuration Setup in an All-Master Deployment
Follow the steps described below to configure the centralized licensing feature in a network with all master
switches:
1. Ensure that the switches using this feature are associated with the same OmniVista server.
2. Identify a switch you want to designate as the primary licensing server. If that switch already has a
redundant backup switch, that backup switch will automatically become the backup license server.
AOS-W 6.5.3.x | User Guide Software Licenses | 89
To Next Page
Loading...