Requirements and Recommendations for Setting up Redundant License Managers
Read the following requirements and recommendations before setting up redundant License Managers.
>First, you must decide how many redundant License Managers to set up and select the machines on which they will reside.
•Various factors, including network performance, affect this decision. The leader must communicate with all other redundant License Managers, therefore, it is imperative that the leader is in an area where good network bandwidth is available.
•The number of redundant License Managers can be a minimum of two (when the majority rule is not applied) or three (when the majority is applied) and a maximum of 11. If only a single server is specified in lservrlf, the redundant server pool is never formed.
•A License Manager can exist only in one license pool.
>A pool can have License Managers running on different operating systems. However, the same version of a License Manager must be installed in all the machines in a pool to avoid inconsistencies due to inter License Manager communication.
>Reverse DNS resolution is necessary for the redundant License Manager setup.
> It is possible to create a redundant License Manager pool consisting of IPv6 based systems. However, the redundant License Manager configuration file can store either IPv6 or IPv4 addresses i.e. a redundant License Manager pool consisting of both License Managers (both IPv4 and IPv6) is not supported. So, if the pool consists of IPv6 systems, only IPv6 based clients can communicate in the setup. The similar behavior is true for IPv4 setup.
>Redundant License Manager pool is not supported when link local addresses of the License Managers are used.
>Setting up a redundant License Managers requires access rights to all computers and areas of the network where the License Managers will be installed. If you make changes to the redundant license file, those changes will not be transferred to all License Managers in the redundant License Manager pool; unless you have network and write access to each of the redundant License Manager machines. If any of these computers run on Windows, you must have administrator privileges to make changes that affect the License Managers on those machines.
>You can include NICs (other than the one at index 0) in the redundant License Manager pool.
NOTE When a supported server-grade Windows machine is used as a client with firewall settings set to 'on', communication with License Manager on IPs other than the one at index 0 does not succeed. To overcome this, add the IP address corresponding to the index 0 NIC to unblock responses.
>After deciding the License Managers for redundant setup, obtain their locking codes and pass them to your software vendor. Your software vendor includes the computer locking code when defining the license code.
>You create the redundant license file, lservrlf, using the rlftool or WRlfTool utility (or by using WlmAdmin to call WRlfTool) to define the redundant License Manager pool. After this, you bring up the redundant License Managers. You can use the lspool and WlmAdmin utilities to dynamically reconfigure the redundant License Manager pool.