Troubleshooting Tips and Limitations for Three-Server Redundancy
Three-server redundancy configurations require all three servers use the same platform type. You can use any of the following platform types in the configuration, but each server must use the same platform type: VM_UUID or PHY_*.
Separating the Contents of a License File
Because the hostid values in the SERVER lines are computed into the signature of each feature definition line, make sure you keep SERVER lines together with any feature definition lines as they were generated. This means that if you move a feature definition line to another file, you must also move the respective SERVER lines and VENDOR line.
Putting the License File on a Network File Server
Do not put the license file on a network file server. If you do this, you lose the advantages of having failover protection because the file server becomes a possible single point of failure.
Using License Servers in Heavy Network Traffic
On a network with excessive traffic, the license servers may miss heartbeats which causes them to shut down the vendor daemon. The master may then stop serving licenses. If you find that heavy network traffic causes this to occur, you should set the HEARTBEAT_INTERVAL to a larger value. Enterprises can experience a performance issue when there is slow network communication or if FlexEnabled clients are using a dial-up link to connect to the network.
The license server manager (lmadmin or lmgrd) can not start vendor daemons from multiple software publishers when configured for three-server redundancy. The license server manager can only manage one vendor daemon. If one of the systems runs more that one vendor daemon, then the license administrator must run separate instances of the license server on that system to support the other vendor daemons. Make sure that the port numbers do not clash.
Switching Between Three-Server Redundancy and Single-Server Configuration
While running, the license server manager (lmadmin or lmgrd) is not designed for switching from three-server redundancy to a single-server configuration (and vice-versa). To switch configurations, you need to do the following:
| 1. | Shut down the license server manager in the single-server configuration or, in a three-server redundancy, all the license server managers currently running. |
| 2. | Do one of the following: |
| • | For lmadmin: |
| a. | From the lmadmin installation directory on a given machine, import the required license files for the new configuration to which you are switching (either the three-server-redundant or single-server configuration): |
lmadmin -import <new_license_file_list> -force
| b. | Restart lmadmin. |
| • | For lmgrd: |
To restart lmgrd on a given machine in the configuration to which you are switching (either the three-server-redundant or single-server configuration), enter the following from the directory in which lmgrd is located:
lmgrd -c <new_license_file_list>
Avoiding Undefined lmdown Behavior
If any two license servers in a three-server redundancy group are started with the -allowStopServer no option (lmadmin) or the -x lmdown option (lmgrd), then the behavior of lmdown is undefined for that system.