NX allows clients be configured to search 2 or more (multiple) license servers.
What are the caveats with respect to minimizing network latency?
A license server search list is a mechanism that allows an NX client to search
two or more license servers for requested license feature(s).
Typical uses are to allow multiple physical sites to share each others license
servers but still allow independent local control.REVIEW:
How is a license server search list defined?FOR NX/1847 or higher
If using csh (C-shell), add to /etc/csh.login:
setenv SPLM_LICENSE_SERVER "28000@serverA:28000@serverB"
If using sh (Bourne shell or Korn shell), add to /etc/profile:
Control Panel ->
Variable Name: SPLM_LICENSE_SERVER
Variable Value: 28000@serverA;28000@serverB
License server search list caveats.
TO MINIMIZE Network Latency
The order in which the servers are listed in the UGS_LICENSE_SERVER or
SPLM_LICENSE_SERVER is the order in which they are searched.
The first server listed should be your primary server.
Usually (but not always) the primary server is a server that is physically
closest to the client. Thus network latency delays are minimized.Example:
SPLM_LICENSE_SERVER = 28000@serverA;28000@serverB
In this example the client would normally get all of their licenses from
ServerA. In the event that ServerA did not offer the license or was
unavailable, the license search would move to ServerB.
"License not available" message would be raised only if the license was not
available on any of the two license server configurations.
Search lists cross search back and forth between serverA and serverB.
Average checkout latency times are on the average, significantly slower.
Checkout latency times also increase if the license file itself contains many
Thus, license server search lists should only be used after careful
GTAC suggests that a test client be setup and NX used under production
conditions to determine if overall license feature checkout times
Notes and References
OS Version: 2012_R2