EasyManua.ls Logo

Alcatel-Lucent AOS-W 6.5.3.x - Page 88

Alcatel-Lucent AOS-W 6.5.3.x
1160 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
88| Software Licenses AOS-W 6.5.3.x| User Guide
Topology Example
A licensing server supports multiple
master/local domains.
Starting with AOS-W 6.5, the centralized licensing
feature supports topologies where multiple
master switches have one or more attached local
switches.
NOTE: This topology requires that all local
switches are able to access the licensing server.
A licensing server supports standalone and
local licensing clients
Starting with AOS-W 6.5.2, the centralized
licensing feature supports topologies where a
licensing master is connected to a standalone
master licensing client switch, a standalone
master redundant licensing server, and a local
licensing client switch.
NOTE: This topology requires additional
configuration steps to define the license server
IPaddress for the local switches in this topology.
For details, see Enabling Centralized Licensing on
page 90
Table 28: Centralized Licensing Topologies
Multi-Version Licensing
AOS-W supports multi-version licensing, which allows centralized licensing clients to run a different version of
AOS-W than the primary and backup licensing servers. If a license is introduced in a newer version of AOS-W,
the primary and backup licensing servers set can still distribute licenses to licensing clients running an older
version of AOS-W, 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 switches. Both the
licensing server(s) and licensing clients must be running a version of that supports this feature. The multi-
version licensing feature is not supported in a topology where a single licensing server or a pair of primary and
backup licensing servers are connected to one or more local switches.
Replacing a Switch
If you need to replace the switch acting as a license server, the keys installed on the previous license server
must be regenerated and added to the new license server. If you need to replace a switch acting as license
client, you must regenerate the license keys installed on the client and reinstall them on the replacement client
or the licensing server.
Failover Behaviors
If the primary licensing server fails, the switch acting as a backup license server will retain the shared license
limits until the backup server reboots. If both the primary and the backup license servers fail, or if the backup
switch reboots before the primary switch comes back up, License clients will retain the license limits sent to
them by the licensing server for 30 days.

Table of Contents