Open the Table of Contents

You are here: Redundant License Managers > Requirements and Recommendations

# Requirements and Recommendations for Setting Up Redundant License Managers

Please read the following requirements and recommendations before you set up the redundant License Managers:

- First, you must decide how many redundant License Managers to set up and select the computers on which they will reside.
  - Various factors, including network performance, affect this decision. Because the leader must communicate with all other redundant License Managers, the leader should be in an area of the network with good bandwidth.
  - You must define at least three redundant License Managers. If the pool is set up with only a single server specified in lservrlf, the redundant server pool will never be formed.
  - A License Manager can exist only in one license pool.
- Each computer on which a redundant License Manager resides must have a static, fixed IP address. Therefore, do not use DHCP to dynamically allocate IP addresses for those computers.
- Reverse DNS resolution is necessary for the redundant License Manager setup.
- Make sure that you specify IP addresses in either IPv4 or IPv6 format. A redundant pool cannot have mixed servers (both IPv4 and IPv6). Consequently, a redundant server can work either in IPv6 or IPv4 mode—as long as the server is running or not removed from the redundant pool.
- After deciding the License Managers for redundant setup, obtain their locking codes and pass them to your vendor. Your 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. Afterward, you bring up the redundant License Managers. You can use the lspool and WlmAdmin utilities to dynamically reconfigure the redundant License Manager pool.

- Setting up redundant License Managers requires you to have access privileges to all computers and areas of the network on which 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 computers. If any of these computers run Windows, you must have administrator privileges to make changes that affect the License Managers on those computers.
- The License Managers in the redundant License Manager pool must have the same version.
- The License Managers should preferably be running on the same platforms (such as, Windows only or Linux only).
- You can include NICs, other than the one at index 0, in the redundant License Manager pool.

When a supported server-grade Windows machine (such as, Windows Server 2003 and 2008) is used as a client with firewall settings “on,” communication with License Manager on IPs other than the one at index 0 does not succeed. To overcome this, add the IP corresponding to the index 0 NIC to unblock responses.