Installing and Configuring a License Server on Linux

You must perform certain tasks to install licensing on a license server for the first time.

Prerequisites

You determined which machines you will use as license servers and determined their host IDs. For information on the latter, refer to “Determine Your Host ID for Licensing”.
You received your Mentor license file either by email or Account Center download. If you have questions, contact Mentor.
You ensured that the proper networking components are installed and correctly configured. For Mentor licensing software to work correctly, workstation hardware and operating system versions must be at a level adequate to support the current versions of software. For hardware and operating system information, refer to your application’s configuration information.
You ensured that TCP/IP is configured on your network.

Procedure

From Account Center (https://account.mentor.com), click Licenses > Licensing Software to show a list of Licensing releases.
Click the most recent Licensing release. The window expands to show four tabs: Files, Important Info, Documentation, and System Requirements.
From the Files tab, click the Licensing release name. The Release Information and Downloads window opens.
To download the release, click the MGLS file that corresponds to your platform.
Copy the downloaded file to the directory where the licensing software is to be installed and navigate to the location.
Unzip the file.
For example (Linux 64-bit, FlexNet v11.13.0.2):
```
$ gzip -d mgls_v9-13_5-2-0.aol.tar.gz
```
Note:
After unzipping the file, the .gz suffix no longer appears on the original file. For example: mgls_v9-13_5-2-0.aol.tar.
Untar the resulting file.
For example:
```
$ tar -xvf mgls_v9-13_5-2-0.aol.tar
```
The command creates a licensing software subdirectory for MGLS. For example: mgls_v9-13_5-2-0.aol. Inside this subdirectory is the bin directory that contains lmgrd, mgcld (the Mentor vendor daemon), and FlexNet utilities.
Save your licenses in a file on your local hard drive.
If you received the license file as an attachment to an email or downloaded the file from Account Center, copy and save the file to a directory that permits you to edit the file. If the licensing information is embedded in an email, copy the contents of the email to a file that permits you to edit the file. Edit the file to remove any email header information. The license file must adhere to the following:
- Be plain-text only
- Have a name that does not contain any spaces
- End in .dat, .lic or .txt
You are not restricted as to where you put the license file. However, you should keep a backup copy of your license file in a safe location.
Open the license file in a text editor.
Specify the server name.
Edit the SERVER line in the license file with the correct license server host name. For example:

Before
```
SERVER put_server_name_here 0024e8477136 1717
```
After
```
SERVER enterprise 0024e8477136 1717
```
If you are administering licenses using a redundant server configuration, you must supply the host name for each license server in your configuration.
If necessary, change the port number in the license file from the default value of 1717 to an open port on your system.
If you are using a redundant server configuration, you must perform this task for each server listed in the license file that cannot use port 1717.

CAUTION:
Running multiple networked applications on the same port can introduce instability into the environment and cause unpredictable results that may be extremely difficult to diagnose. Ensure that the port number you choose is dedicated to license server communications only.
If you are using a redundant server configuration, copy the license file to the other license servers in your configuration.
Each redundant license server requires a local copy of the same license file.
Edit the DAEMON line to include the path to the vendor daemon mgcld.
Note:
Firewalls can interfere with licensing communication. For more information, refer to “Firewall Considerations”.
Locate the path to the vendor daemon in the licensing software directory that you created in Step 7. For example: /usr1/mgls_v9-13_5-2-0.aol/bin/mgcld. You must use the absolute path to the daemon. An absolute pathname begins with a “/” (slash). Currently, FlexNet does not allow an environment variable in this pathname. You can add the path to the daemon options file on the DAEMON line. For more information, refer to “Vendor Daemon Options File”.

The following is an example of an edited DAEMON line without a daemon options file:
```
DAEMON mgcld /usr1/mgls_v9-13_5-2-0.aol/bin/mgcld
```
Optionally, adjust the order of your INCREMENT lines to help control license consumption. For more information, refer to “License Ordering in a License File”.
If you want to customize license usage, edit the daemon options file.
For more information, refer to “Vendor Daemon Options File”.
Start the license manager daemon on the license server.
```
$ lmgrd -c license_file
```
Where license_file is the path to the license file you configured in the previous steps.

You also can create a server debug log file. For example:
```
$ lmgrd -c license_file -l logfile
```
Then you can use the Linux tail -f logfile command to monitor the status of the license server.

Note:
We recommend that you do not run license servers as “root.”
Verify that the server is valid and has started.
```
$ lmutil lmstat [-c {license_file | port@host}]
```
The command reports the server and daemon status and the product usage.

Note:
If you do not set LM_LICENSE_FILE, you must use the -c switch with all lm* commands.
For redundant servers, repeat this process for each server in the cluster.