The Intel® Software License Manager is required to manage Intel® Software Development Products floating licenses in a development environment. The license manager is NOT required for single-user licenses.
This tutorial will help to setup your floating license environment very quickly.
Follow these steps and choose the setup scenario that matches best:
This step can be skipped if the following conditions are true:
Please refer to the note 'Who is eligible to obtain a license file?' below.
You need a MAC address of the license server (optional the license server name) to register and create your license file.
Note: Remove all special characters from the string and - if required - fill up with leading zeros to get your 12-digits alphanumeric string which is your Host ID.
If you have the license manager tools already installed you can run:
and take any of the addresses issued.
If you have not registered your serial number yet, you must browse to the Intel® Registration Center and enter your SN and email, or if you are already logged in, your SN at the top right of the "My Products" page.
Once your serial number is registered, you can activate it in the registration center by entering the host ID and hostname you obtained earlier by following these steps:
Once the serial number is activated, you may download it. If your license server is not connected to the internet, you must copy the full server license file to the server. The default directory used by the license manager is:
You do not have to use the default, however.
Only the license owner or license administrator can perform a license registration and obtain a license file. Registered users have the right to download products and have read-access to the license history only.
You can use an existing FlexNet* or FlexNet Publisher* license manager (lmgrd) if its version is the same or higher as the version of the Intel® vendor daemon (INTEL). You can also run multiple instances of lmgrd on the same server as long as different ports are used. Please refer also to the Floating Licenses and Software License Manager Compatibility section.
The steps in this section also apply to a redundant servers installation where all steps need to be done on all 3 license servers.
A single license server or a redundant license server configuration can manage licenses from clients running on different operating systems.
Please set up your license manager according to one of the following scenarios that match best:
The Intel® Software License Manager User's Guide is available here.
When prompted for the license, you can either enter the serial number if the server is connected to the internet, or you can provide the path to the license file. If you put the license file in the default directory, it should detect it automatically.
Providing the serial number will automatically download the server license file to the default license directory. If your license was not already activated, it will automatically activate it with the server's host ID, hostname, and default ports.
When the installer is completed, it will start the license manager processes automatically as long as no other FlexNet* processes are already running. There are two ports used by the license manager: one for the FlexNet daemon (lmgrd), and one for the INTEL daemon. If these ports are blocked, the license checkouts will fail.
You can skip this section if your license manager was already started by the installer.
From the license manager directory (/licenseserver) start the license manager lmgrd. You can specify a single license file or a license directory (if you more license files). By default, the license file name is server.lic which was created by the license manager installation. However you can move any valid floating license into the /flexlm directory and start it with the license manager.
lmgrd -c server.lic -l lmgrd.log (reads server.lic license file and creates lmgrd.log)
lmgrd -c . -l lmgrd.log (reads all .lic files from the serverlicenses directory and creates lmgrd.log)
You can run the license manager under Windows as system service (recommended) or as user application in a command shell (sometimes required for some Windows OS versions).
Important! Make sure *both* ports used by the license manager are not blocked by the firewall!
First make sure you are using the latest version of the Intel Software License Manager.
You can copy all license files into a license directory or combine licenses into one single license file (.lic).
On Windows you can re-read the new license also via the license manager GUI (Start > Intel(R) Software Development Products).
Intel no longer recommends using combined license files with newer versions of the license manager, but the process is documented here for the sake of completeness.
*Note that using a word processor may introduce invalid characters and corrupt the license file.
Same as above, but you need to make sure that the license manager lmgrd is of same or higher version as the Intel® vendor daemon INTEL/INTEL.exe.
Important! Make sure *both* ports used by the license manager are not blocked by the firewall!
There are two core components to the license server, both of which must not be blocked by a firewall:
To change the lmgrd port number from 27009 to 27005, change the SERVER line(s) to:
SERVER hostname 000000000000 27005
To specify the INTEL vendor port number as 28519, change the VENDOR line to:
VENDOR INTEL port=28519
Take care in changing the license file, or you may invalidate it.
There are several ways to setup a floating licensed product on client machine, but the most appropriate ones for an existing product installation or new / update installation on clients are listed in this section.
Please note that this section applies to a single-license-server configuration only. Please refer to the Tips & Tricks section to use this method also for a redundant server configuration.
CAVEAT! In complex environments this step may take long time (several minutes) until client-server connection and license verification/installation is finished.
First make sure that any invalid licenses are not left on the client system. This can cause slow license checks.
There are two ways to provide the license information:
You can download the client version of the license file from the Intel® Registration Center. This contains the top line of the server license, followed by USE_SERVER on the next line. You can also modify the server license to have the same:
SERVER <server_name|IP-address> <ANY|<server_MAC_address> <port>
Next, copy the file to the default license directory:
If the environment variable INTEL_LICENSE_FILE does not already exist, you can create it with the value port@host where the port is the one specified in the first line of the license file (lmgrd), and the host is the server hostname. If the INTEL_LICENSE_FILE environment variable does exist, you can overwrite it.
Again, be sure to remove (or rename) all old or unused .lic files in the license directory.
Setup of a redundant license server configuration remotely as described above is not supported by default, but you can perform the same steps as described above by referencing one of the servers only. After installation and server set up you can "expand" your client license by adding the other 2 servers in the client license, such as:
SERVER <servername1> ANY <port>
SERVER <servername2> ANY <port>
SERVER <servername3> ANY <port>
You can use the license manager diagnostic tools also on the client to perform the same license server checks as on the server.
Copy over the lmstat tool from the license server to the client.
Instead of using the license file or license directory use port@server as license parameter to invoke lmstat on the client, for example:
lmstat -a -c <port>@<servername>
On Linux a very comfortable method is available to check which license and license server are being used. Create the enviornment variable FLEXLM_DIAGNOSTICS, assign it value 3 and invoke any of the tools: icc, ifort, amplxe-cl, inpxe-cl or idbc. For example:
Create the INTEL_LMD_DEBUG enviornment variable, assigning it a log file name and invoke the compiler, such as icc. Search the logfile for any occurrence of the string SMSAxxxxxxxx. This 8-characters suffix is the serial number of the product that was used by invoking the product. For example:
Open an Intel Software Development Product command prompt from the Start menu, create the INTEL_LMD_DEBUG environment variable, assigning it a log file name and invoke the compiler, such as icl. Search the logfile for any occurrence of the string SMSAxxxxxxxx. This 8-characters suffix is the serial number of the product that was used by invoking the product. For example:
You can run a single license server to manage a combined license for different client operating systems. The license server can run on Windows* or Linux*. In a heterogeneous environment it may be required to specify the full license server name including the full primary DNS suffix or the IP address in the license files of the clients.
In order to have full functionality of floating licensing service it is strongly recommended to use a license manager version that is specified for use with your product (please refer to the 'System Requirements' in the product release notes). Incompatible Intel® Software License Manager versions may result in reduced functionality when updating products on your client machines; for example they may not detect existing product activations or allow product activation via license server.
If you encounter problems updating products try one of the following workarounds:
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804