You are here: Setting Up the Redundant License Servers > Before You Set up Redundant License Servers...

Before You Set up Redundant License Servers...

There are three aspects to setting up and using redundant license servers.

First, you must decide how many redundant license servers 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 three.
If you want the license servers to be locked to specific computers, you must give your vendor the locking code for each computer on which a redundant license server 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 server pool.
Afterward, you bring up the redundant license servers. You can use the lspool and WlmAdmin utilities to dynamically reconfigure the redundant license server pool.

Tips and Recommendations

The license servers in the redundant license server pool must have the same version.
The license servers 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 servers, the leader should be in an area of the network with good bandwidth.
Each computer on which a redundant license server resides must have a static, fixed IP address. Therefore, do not use DHCP to dynamically allocate IP addresses for those computers.
A server can exists only in one license pool.
Setting up redundant license servers requires you to have access privileges to all computers and areas of the network on which license servers will be installed. If you make changes to the redundant license file, those changes will not be transferred to all license servers in the redundant license server pool unless you have network and write access to each of the redundant license server computers. If any of these computers run Windows 2000/XP/Server 2003/Vista/Server 2008, the customer must have administrator privileges to make changes that affect the license servers on those computers.