Open the Table of Contents
You are here: Setting Up the Redundant License Managers > Before You Set up Redundant License Managers...
Before You Set up Redundant License Managers...
There are three aspects to setting up and using 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. However, you must define at least two.
- If you want the License Managers to be locked to specific computers, you must give your vendor
the locking code for each computer on which a redundant License Manager
will be installed. 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 thelspool andWlmAdmin utilities
to dynamically reconfigure
the redundant License Manager pool.
Tips and Recommendations
- Before the License Manager pool is set up, decide how many redundant License Managers to set up and select the computers on which they will reside?
- 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).
- Because the leader must
communicate with all other redundant License Managers, the leader should
be in an area of the network with good bandwidth.
- 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.
- A License Manager can exists only
in one license 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, the customer must have administrator privileges
to make changes that affect the License Managers on those computers.
- 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.