Home > |
|
---|
A License Manager program need not run on a file server system or any specific hardware server. Any computer that meets the minimum requirements is acceptable. Realistically, a system running on Pentium Processor 3 (or higher), 550 MHz and having 128 MB RAM is acceptable.
The License Manager can be installed and run on multiple computers. It can be installed on any computer, even a computer that is used to run one of the licensed applications. The application running on a client may choose any available License Manager with a valid license code for that client.
NOTE RMS does not support servers with numeric host names. The License Manager may not start on such machines due to external dependencies.
>On Windows, you can install the Sentinel RMS License Manager using its installer (provided by your vendor). For UNIX, you can share the License Manager executable (lserv) available in the /bin directory.
>If you already have an older version of the Sentinel RMS License Manager installed on your system, upgrade with the latest version.
>Administrator or root privileges are required to install and run the RMS License Manager.
>By default, the License Manager is installed at the following path:
•On Windows: <OSDrive>:\Program Files\Common Files\SafeNet Sentinel. However, you may change it when prompted for it during the installation process.
•On UNIX, you can place the License Manager executable (lserv) at any chosen location.
Here are few recommendation that you can make use while setting up the RMS License Manager:
>The computers on which License Managers run should use static IP addresses rather than dynamically allocated IP addresses (DHCP). In fact, redundant License Manager computers must use static IP addresses (see also: Requirements and Recommendations for Setting Up Redundant License Managers).
>The RMS License Manager supports UDP (User Datagram Protocol) that can support both IPv4 and IPv6 addresses. That is, a client can contact the License Manager using the IPv4 or IPv6 communication protocol. When the License Manager is hosted on a dual stack system, both IPv4 and IPv6 clients can communicate with it, however, not all combinations are supported (see the illustration below for more information):
License Manager Host Protocol | Client-side Protocol | |
---|---|---|
IPv4 | IPv6 | |
IPv4 | Supported | Not supported |
IPv6 | Not supported | Supported |
Dual stack | Supported | Supported |
>Client computers should directly contact the License Manager that services the licenses used by that client. The LSHOST and LSFORCEHOST environment variables or the lshost file can be used to do this.
>Client computers should contain a 'hosts' file that maps IP addresses to the host names of the computers on which License Managers runs; this speeds up contacting those License Managers.
•For certain supported versions of Windows, this file is probably located in <rootdir>:\Windows\system32\drivers\etc The file itself contains instructions on entry format.
•On UNIX, this file is probably located in the /etc directory.
NOTE The License Manager can communicate over a single IP address only on a multi-home PC. You do not have choice to specify any particular IP address for use by the License Manager. If the IP address to which License Manager is bound becomes unavailable for any reason, then the License Manager needs to be restarted to allow using any other IP address on the system.
>For successful communication between network clients and the License Manager:
> The MTU value should be set to 1474 or above.
>For larger packets having size larger than MTU size, packet fragmentation should be allowed.
>If you experience communication problems, you may diagnose your network using the following command:
•Prior to RMS SDK v8.4.1: ping –l 1500 <machine -name>
•Post RMS SDK v8.4.1: ping –l 7554 <machine -name>
>Restart the License Manager in the case of time zone change.
To check for the presence of the License Manager:
>On Windows, look for the Sentinel RMS License Manager entry in the list of the services installed on the system.
>On UNIX, use the ps -ef|grep lserv command.
Manually Adding Sentinel RMS License Manager Entry in System Firewall
If the Sentinel RMS License Manager is not added under the system Firewall exceptions, the communication between the clients requesting licenses and the RMS License Manager cannot take place.
>On Windows, by default, the installer adds the Sentinel RMS License Manager entry. If you change this default addition during the installation, you need to manually allow it.
>On UNIX, you need to allow the 5093 (default port) as the trusted port for the RMS License Manager . The underlying protocol used is UDP.