Using the Intel® Software License Manager
User's Guide

Copyright © 2002–2015 Intel Corporation
All Rights Reserved
Document Number: 251879-014US
Revision: 2.4
World Wide Web: http://www.intel.com/

Document Number: 251879-014US

Using the Intel® Software License Manager

Legal Information
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL(R)PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANYINTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS
PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTELASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIEDWARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY
OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE,
MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHERINTELLECTUAL PROPERTY RIGHT.
UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOTDESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTELPRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY
OCCUR.
Intel may make changes to specifications and product descriptions at any time, without
notice. Designers must not rely on the absence or characteristics of any features or
instructions marked "reserved" or "undefined." Intel reserves these for future definitionand shall have no responsibility whatsoever for conflicts or incompatibilities arisingfrom future changes to them. The information here is subject to change without notice.
Do not finalize a design with this information.
The products described in this document may contain design defects or errors known aserrata which may cause the product to deviate from published specifications. Current
characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications
and before placing your product order.
Copies of documents which have an order number and are referenced in this document,or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel's
Web Site (http://www.intel.com/).
Intel processor numbers are not a measure of performance. Processor numbers
differentiate features within each processor family, not across different processorfamilies. See http://www.intel.com/products/processor_number for details.
Intel, Intel logo, Itanium, and VTune are trademarks of Intel Corporation in the U.S. andother countries.
* Other names and brands may be claimed as the property of others.
Copyright (C) 2002-2015, Intel Corporation. All rights reserved.

2

Document Number: 251879-014US

About this Guide

Contents
1

About this Guide ........................................................................................................... 5
1.1
1.2

2

About the Intel® Software License Manager .................................................... 7
2.1
2.2

2.3
2.4

3

Supported Platforms ....................................................................................... 7
License Types .................................................................................................... 8
2.2.1 Node-Locked License Configuration .......................................... 9
2.2.2 Floating License Configuration .................................................... 9
2.2.3 Sample License File ....................................................................... 10
Technical Support .......................................................................................... 11
Client/Server Backward Compatibility ................................................... 11
2.4.1 Clients Cannot Use Newer ISL than Servers ....................... 11
2.4.2 Servers Can be Newer than ISL Releases ............................ 11

Installing the Intel® Software License Manager ........................................... 12
3.1

3.2
3.3
3.4
3.5

User's Guide

Related Publications........................................................................................ 5
Conventions and Symbols ............................................................................ 6

Identifying the Host Name and Host ID ............................................... 12
3.1.1 Microsoft Windows* ...................................................................... 12
3.1.2 Linux* ................................................................................................. 13
3.1.3 OS X* on Intel® architecture ................................................... 13
Registering Your Product Serial Number .............................................. 14
Changing Server/Host Data for Your Product License .................... 15
Redundant License Host Servers ............................................................. 16
Downloads and Installs ............................................................................... 17
3.5.1 Product File Downloads................................................................ 17
3.5.2 Intel® Software License Manager downloads .................... 17
3.5.3 Starting the Intel® Software License Manager on
Windows ............................................................................................ 18
3.5.4 Installing the Intel® Software License Manager on
Linux* and OS X* .......................................................................... 19
3.5.5 Starting the Intel® Software License Manager
automatically on Linux* after reboot ..................................... 20
3.5.6 Verifying the Intel® Software License Manager on
Linux* and OS X* .......................................................................... 20
3.5.7 Compatible Versions of Intel® Software License Manager
and Vendor Daemons ................................................................... 20
3.5.8 Shutting Down or Removing the Intel® Software LicenseManager on Linux* and OS X* ................................................. 21
3

Using the Intel® Software License Manager

4

Using the Client Application for the First Time ............................................... 22
4.1
4.2

4.3

4.4

5

Troubleshooting .......................................................................................................... 32
5.1
5.2
5.3

5.4

6

License Host Server System Checklist .................................................. 37
Client Systems Checklist ............................................................................ 40

Appendices .................................................................................................................... 42
7.1
7.2

4

Where to Start ................................................................................................ 32
Creating Debug Logs for License Checkout Issues........................... 32
Information Needed for Support Requests .......................................... 34
5.3.1 Client Information .......................................................................... 34
5.3.2 Intel Software License Manager Information ...................... 34
Common Issues.............................................................................................. 35
5.4.1 License Checkout Failing Due to Terminal Server Client
or Remote Desktop Connection on Windows* .................... 35
5.4.2 Client and Server Not Able to Connect Due to Windows
Firewall ............................................................................................... 35

Checklist for Intel® Software License Manager Server/Client
Installation .................................................................................................................... 37
6.1
6.2

7

Installing the Client Application ............................................................... 22
Setting the INTEL_LICENSE_FILE Environment Variable............... 23
4.2.1 Counted Licenses and Alternatives ......................................... 24
4.2.2 How to Specify Ports for License Servers ............................. 24
Combining Multiple License Files ............................................................. 25
4.3.1 Criteria for Combining License Files ....................................... 25
4.3.2 Instructions for Combining License Files .............................. 25
4.3.3 Examples ........................................................................................... 27
License Seat Check-out and Check-in ................................................... 30
4.4.1 License Seat Allocation Overview ............................................ 30
4.4.2 Allocation status ............................................................................. 31

Appendix A: Latest Revision of User’s Guide ...................................... 42
Appendix B: Troubleshooting Guide ....................................................... 43

Document Number: 251879-014US

About this Guide

1

About this Guide
This guide helps you get started using the Intel® Software License Manager with yourIntel® Software Development Product. This guide contains the following chapters andappendices:
1: About This Guide – Describes the contents of this guide, related publications, andconventions used in this guide.
2: About the Intel® Software License Manager – Describes the supported platforms,
license types, and how to obtain technical support.
3: Installing the Intel® Software License Manager – Describes the necessary steps in
identifying host name and host id, registering your product serial number,
downloading and installing the product, using the product for the first time andtroubleshooting.
4: Using the Client Application for the First Time – Describes how to set up the client
application and use it for the first time.
5: Troubleshooting – Explains how to create a debug log, how to open a support
request, and addresses common issues and how to fix them.
6: Checklist – Order of steps for Intel® Software License Manager server/client
installation.
Appendices – Contains flowcharts showing troubleshooting steps.

1.1

Related Publications
For information on FLEXlm* and FlexNet* software created by Flexera* Software, see
http://www.flexerasoftware.com. For information on Intel® Software Development
Products, see http://developer.intel.com/software/products. More information aboutIntel® Software Development Product licenses and their usage is available in theknowledgebase at http://software.intel.com/en-us/articles/intel-softwaredevelopment-products-download-registration-licensing-kb-home/.

User's Guide

5

Using the Intel® Software License Manager

1.2

Conventions and Symbols
The following conventions are used in this document.

Table 1

6

Conventions and Symbols used in this Document
This type style

Indicates an element of syntax, reserved word, keyword,
filename, computer output, or part of a program example. The
text appears in lowercase unless uppercase is significant.

This type style

Indicates the exact characters you type as input. Also used tohighlight the elements of a graphical user interface such as
buttons and menu names.

<This type style>

Indicates a placeholder for an identifier, an expression, astring, a symbol, or a value. Substitute one of these items forthe placeholder.

Hyperlink

Indicates hyperlink.

Document Number: 251879-014US

About the Intel® Software License Manager

2

About the Intel® Software LicenseManager
The Intel® Software License Manager is a collection of software components that helps
you manage your license file in a multiple-user environment. Before you can use Intel®
Software Development Products, you must have the correct license installed for theIntel products. The Intel® Software License Manager can be downloaded separatelyfrom your product if you purchased a floating or counted node-locked license. This
document describes the installation and use of the Intel® Software License Manager forsupported platforms.
Counting and controlling the number of concurrent users of a software product is theprimary function of the Intel® Software License Manager. You only need the Intel®
Software License Manager when you have a floating or counted node-locked license(see License Types). For other license types, you need to install the license file, but not
the Intel® Software License Manager. See your product documentation for more
information on installing the license file.

2.1

Supported Platforms
The Intel® Software License Manager is supported on the following platforms:
Microsoft Windows* for IA-32 and Intel® 64 architecturesLinux* IA-32 and Intel® 64 LSB (Linux Standards Based) compliant architectures

OS X* IA-32 and Intel® 64 architectures

More information about downloading the Intel® Software License Manager license
server that best matches your license host server OS can be found in the Intel®
Software License Manager downloads section of this guide.
NOTE: The minimum LSB 3 requirement for installing and using the Intel® Software
License Manager is that the shared object ld-lsb.so.3 (32-bit systems) or ld-lsb-x8664.so.3 (64-bit systems) is located in /lib (32-bit) or /lib64 (64-bit).
Please refer to the installation section to setup the shared library if it's not in place on
your system.
You can run the Intel® Software License Manager on any supported platform, with
Windows*, Linux*, or OS X* applications running on separate network nodes. For
example, you can install the Intel® Software License Manager and license file on aLinux* operating system to manage floating licenses for Windows*, Linux*, or OS X*
applications.

User's Guide

7

Using the Intel® Software License Manager

2.2

License Types
Before installing the Intel® Software License Manager, you should be familiar with thedifferent license types and how they are used with Intel® Software Development
Products. License types supported by the Intel® Software License Manager are:

Floating License (counted)
Node-Locked License (counted or uncounted)
Single-User License (uncounted)

Only counted license types require the Intel® Software License Manager. Node-locked
and floating license types are used in multiple-user environments, and the Intel®
Software License Manager monitors the number of concurrent users permitted in thelicense file. For example, if your license permits 20 users, then the Intel® Software
License Manager “checks out” a license to the first 20 users. Whenever the license
count is less than 20, other licensed users may check out a license from the Intel®
Software License Manager to run their application.
The differences between node-locked and floating license types are:

8With node-locked license types, users access the Intel® Software Development
Product using an account on a central (node-locked) system on which both theIntel® Software Development Product and the Intel® Software License Manager are
installed. The Intel® Software Development Products are not installed on remotesystems. For example, a user might use a remote login program, such as Telnet oran SSH client, to log into an account on the central system and use the commandline window to run the Intel® Software Development Product on the node-locked
system. Also, Windows* Terminal Server* and related X-window capabilities allow
more than command-line window use.
With floating license types, users access the Intel® Software Development Producton their local system, while the license use is controlled by one central systemrunning the Intel® Software License Manager.

Document Number: 251879-014US

About the Intel® Software License Manager

2.2.1

Node-Locked License Configuration
There are two versions of the node-locked license:Counted – the license limits the number of concurrent users.
Uncounted – the number of concurrent users or running application instances is not
limited by the license file. Please refer to the End User License Agreement during
the installation of your Intel® product for usage policy.

In both cases, only the node running the application and Intel® Software LicenseManager needs a license file. Consider the example illustrated in the following table:
Node

Operating
SystemApplications

Intel® Software
LicenseManager

License
File

A

Linux

Intel® C++ Compiler for Linux*
Intel® Fortran Compiler for Linux*

X

X

In this example, the Intel® C++ Compiler for Linux*, the Intel® Fortran Compiler forLinux*, the Intel® Software License Manager, and license file all run on Node A. Anyone
on the network who can connect to Node A may run either application, as long as alicense is available.

2.2.2

Floating License Configuration
With a floating license you can manage, from a single node, applications running on
different nodes. Consider the example illustrated in the table below:
Node

Operating
SystemApplication

Intel® Software
LicenseManager

License
File

A

Linux

X

X

B

Windows

Intel® C++ Compiler for Windows*

X

C

Linux

Intel® C++ Compiler for Linux*
Intel® Fortran Compiler for Linux*

X

D

Linux

Intel® Fortran Compiler for Linux*

X

E

OS X*

Intel® C++ Compiler for OS X*

X

In the example above, the Intel® Software License Manager, running on Node A, counts
the number of licenses in use. The license file on each node must have identical
SERVER and VENDOR line information.

User's Guide

9

Using the Intel® Software License Manager

2.2.3

Sample License File
The sample counted license file below is for an Intel® Software License Manager
installed on Linux*. The same license file is used with Windows*, Linux*, and OS X*
products that rely on the Intel® Software License Manager to serve and count licenses.
Sample Counted License

SERVER mslid073 000629856A25 28518
VENDOR INTEL
PACKAGE I00000000002L INTEL 2003.1025 12222F8900CF \COMPONENTS="CCompW
SIGN=8BF3D0867076

CCompL CCompM" OPTIONS=SUITE ck=86 \FEATURE I00000000002L INTEL 2003.1025 permanent

20 FD312CFD3BA9 \VENDOR_STRING=SUPPORT=INT HOSTID=ANY PLATFORMS="i86_n ia64_n \i86_r i86_re it64_lr it64_re i86_mac" DUP_GROUP=UH ck=127 \SN=INT2002917543 SIGN=A3A79E168CD2

The essential components of the sample license file are listed below along with theircorresponding values:










Host name: mslid073
Host id (lmhostid): 000629856A25
Port Number: 28518
Supported Software Products: CCompW (Intel® C++ Compiler for Windows*),
CCompL (Intel® C++ Compiler for Linux*), CCompM (Intel® C++ Compiler for OS X*)
Supported Product Platforms: i86_n (Windows* on IA-32 architecture), i86_r,
i86_re (Linux* on IA-32 architecture), ia64_n (Windows* on IA-64 architecture),
it64_lr, it64_re (Linux* on IA-64 architecture), i86_mac (Intel®-based systems
running OS X*)Intel Support Expiration Date: 2003.1025 (October 25, 2003).
Product Expiration Date: permanent (Never expires).
License Count: 20.

Note: While host name and port numbers can be changed, editing many parts of thelicense file renders the entire license file invalid. References to IA-64 architecture
platforms are for legacy purposes only. New ISL releases starting with 2.2 do notsupport IA-64.

10

Document Number: 251879-014US

About the Intel® Software License Manager

2.3

Technical Support
Every new license purchase or renewal of an Intel® Software Development Productincludes one year of support services and free product upgrades, which provides accessto Intel® Premier Support. Customers also receive support through the Intel®
Software Development Products Forum.
If you purchased a CD-ROM version of your product, then you must register yourproduct with the Intel® Software Development Products Registration Center(https://registrationcenter.intel.com/) to activate your access to Intel® Premier Support(https://premier.intel.com/) or the Intel® Software Development Products Forum(http://software.intel.com/en-us/forums/). All license types for the eligible products
listed above, except the noncommercial-use license, qualify for Intel® Premier Support
accounts.

2.4

Client/Server Backward Compatibility
One aspect of Intel Software Licensing that has not always been clearly communicatedis that of version compatibility between client and server releases. To clarify, here are
the basic considerations to keep in mind when dealing with licensing:

2.4.1

Clients Cannot Use Newer ISL than Servers
If your product is upgraded to use a newer release of PSET (Product Startup Experience
Technology installation software), this version of PSET may have been built with anewer release of ISL. Also, a product that has recently been built may have been createdusing a newer version of ISL as well, so its internal licensing components will have been
upgraded. In nearly all of these cases, it is required that the ISL server also be upgradedin order for any client/server (a.k.a. “floating”) licensing to work. The license server
software is available for download from Intel Registration Center for all customers who
have floating licenses.

2.4.2

Servers Can be Newer than ISL Releases
License server software is backwards compatible, so if a customer upgrades their license
server software, it will continue to support older versions of the client software. Thismeans there is no risk to always keeping the licensing software updated to the mostrecent version available from the Intel Registration Center.

User's Guide

11

Using the Intel® Software License Manager

3

Installing the Intel® Software
License Manager
You only need to install the Intel® Software License Manager if you are using a floatingor counted node-locked license (see License Types). Once you have purchased an Intel®
Software Development Product, follow these steps to install the Intel® Software LicenseManager and invoke your product:
1. Identify host name and host id
2. Register your product serial number
3. Download and install the product3.1

Identifying the Host Name and Host ID
The host name and host ID are system-level identifiers on supported platforms that areused in the license file to identify the node on which you plan to install the Intel®
Software License Manager and license file. To enable you to obtain a counted license,
these unique values must be available when you register your product. For node-locked
licenses, you will also need the host name and host id of the node from which yourapplications will run (if different from the node for the Intel® Software LicenseManager). Follow these directions to obtain the host name and host id for eachsupported platform:

3.1.1

Microsoft Windows*
1. From the Start menu, click Run...
2. Type cmd in the Open: field, then click OK.
3. Type ipconfig /all at the command prompt, and press Enter.
In the resulting output, host name is the value that corresponds to Host Name, andhost id is the value that corresponds to Physical Address.
For example, if the output of ipconfig /all included the following:
Host Name . . . . . . . : mycomputer. . .
Physical Address . . . . : 00-06-29-CF-74-AA
then host name is mycomputer and the host ID is 00-06-29-CF-74-AA.

12

Document Number: 251879-014US

Installing the Intel® Software License Manager

3.1.2

Linux*
1. Run the hostname command to display the host name.
2. Run the command /sbin/ifconfig eth0 to display the hardware
address.
For example, if the /sbin/ifconfig eth0 command returns
HWaddr 00:D0:B7:A8:80:AA, then the host ID is 00:D0:B7:A8:80:AA.
It is strongly recommended that users run the lmhostid utility to obtain the hostid value
required to generate counted licenses. The lmhostid utility can be found in the install
location where the Intel® Software License Manager is installed.

3.1.3

OS X* on Intel® architecture
1. Run the hostname command to display the host name.
2. Run the command /sbin/ifconfig en0 ether to display the
hardware address.
The following is an example of an address that could be returned by this command:en0:
flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST>
mtu 1500 ether 00:13:20:60:23:4f
It is strongly recommended that users run the lmhostid utility to obtain the hostid value
required to generate counted licenses. The lmhostid utility is installed in the same
location as the Intel® Software License Manager.

User's Guide

13

Using the Intel® Software License Manager

3.2

Registering Your Product Serial Number
Next, register each product serial number at the Intel® Software Development Products
Registration Center (https://registrationcenter.intel.com/). The registration process isrequired for the following reasons:









For electronically-transferred products, registration is the only means to obtain therequired license file and download location for the software.
For boxed (CD-ROM) products, registration is the only means to activate Intel®
Premier Support and receive product updates. Note: CD-ROM products are encodedwith a Single-User license. Therefore, they cannot be used with the Intel® Software
License Manager.
For counted licenses, registration is the process by which the host name and host id
are sent to the Intel® Software Development Products Registration Center(https://registrationcenter.intel.com/) for license creation.
If you intend to install and configure three redundant license host servers, you mustspecify the host name and host id for each of your license host server systems when
you register your floating or node-locked license(s). If you have three license hostservers specified, at least two of them must be running and accessible from yourclient systems at all times.
To change your license host server information in your floating or node-locked
license, i.e. when you need to move your license host server to a new system,
please follow the instructions in the next section (Changing Server/Host Data forYour Product License).

Go to the Intel® Software Development Products Registration Center and complete
each step. If you do not have an existing Intel® Premier Support account for yourproduct, click on Register for Intel® Premier Support on the screen thanking you forregistration.

14

Document Number: 251879-014US

Installing the Intel® Software License Manager

3.3

Changing Server/Host Data for Your
Product License
Note: If your floating or node-locked licenses are active, you may make changes to thehost id information for your licenses. If your floating or node-locked licenses have
expired support, you must submit an issue to Intel® Premier Support or to the
Downloads, Licensing and Registration User Forum to request that an Intel Support
Engineer modify your license host id information.
1. Login to the Intel® Software Development Products Registration
Center (https://registrationcenter.intel.com/) by clicking the RegisteredUsers Login button in the lower section of the web page andentering your Login ID and Password on the next page. You will
see a list of all products you have registered.
2. On the My Products page, for each product you have registered,
you will see the product name, component names, links to thelatest versions available for download and posted date of theversion available for download. [Note: Expired registrations areshown only if you check the Show Expired Registrations checkbox at the top of the page.]
3. Click on any of the product names to see your product subscription
history. This includes serial number and support status with license
expiration date. You will also be provided with links to manage thelicense information and links to renew your subscriptions. [Note:
Expired serial numbers can be viewed by checking the Show
Expired Serial Numbers check box on the top right corner of thispage.]
4. Click on the Manage link for the serial number you wish to change.
5. You will be provided with the license file information page. Click on
the Modify Host Information link at the bottom of this page.
6. Enter the new server/host information and click Submit. If you do
not get any errors, click on Resend license file to my email. You
will receive your new license file via email shortly.
7. After you receive your updated .lic license file, you must replace
the old license file with the new one on your license host server
system(s). If you use a combined license file (see the Combining
Multiple License Files section in this user guide), you must update yourcombined license file with the new license information.
8. After your new license file or updated combined license file is on
your license host server system(s), you must restart your license
host server process on the license host server system(s) so yournew license file or updated combined license file will be re-read.

User's Guide

15

Using the Intel® Software License Manager

For more information, please see http://software.intel.com/en-

us/articles/change--serverhost-data-node-locked-or-floating-license/.

3.4

Redundant License Host Servers
Intel software product licenses can support up to three redundant license host server
systems. Please follow the steps below to ensure your floating licenses and your license
host server systems have been properly set up for the multiple license server
configuration.
1. Please ensure that your host ids and host names are unique for thethree servers. Using a duplicate host name and host ID will notallow the license file to generate successfully during registration.
2. If you intend to install and configure three redundant license hostservers, you must specify the host name and host id for each ofyour license host server systems when you register your floating or
node-locked license(s).
3. Please double-check that all your floating or node-locked licenses
are registered for the same three unique, correct host names/host
ids. If you need to update any of your floating or node-locked
licenses to correct the host names/host ids, please follow the
instructions in the previous section (Changing Server/Host Data for Your
Product License). You must also follow these instructions when you
move one or more of your license host servers to a new system.
4. Please make sure at least two license host servers are up andrunning when the license is checked out from the client system.
That is to say, the Intel® Software License Manager should bestarted by selecting the right license file(s) on at least two license
host servers where it is installed.
Note: If your floating or node-locked licenses are active, you may
make changes to the host id information for your licenses. If yourfloating or node-locked licenses have expired support, you must
submit an issue to Intel® Premier Support or to the Downloads, Licensing
and Registration User Forum to request that an Intel Support Engineer
modify your license host id information.
5. If you are using a three-server redundant configuration then atleast two must be up and running to make a “quorum” and permit
licenses to be checked out. If you do not intend to have all three ofthe servers running at all times, we recommend using a single
license server instead of a three-way redundant license server
configuration.

16

Document Number: 251879-014US

Installing the Intel® Software License Manager

6. If you have only one server running of the three servers keyed into
the license, you will likely see the -97 error (see below) for "vendor
daemon is down", so you also check that the daemon is running oneach server system.
FCompW: The desired vendor daemon is downa) Check the lmgrd log file, orb) Try the lmreread command:
Feature: FCompW
Vendor:Host: sl-ecs-snag-01
License path: 28518@sl-ecs-snag01;C:\PROGRA~2\Intel\Compiler\
Fortran\100~1.026\Ia32\Bin\*.lic
FLEXlm error: -97,121

3.5

Downloads and Installs

3.5.1

Product File Downloads
After you register your product serial number, you will receive e-mail instructions todownload your Intel® Software Development Product. Obtain your product download
by going to the URL included in the instructions.
If you have a current product license, you can download any version of the software,and if your current product license is entitled to Intel® Premier Support, you have accessto submit questions through the Intel® Premier Support system.
Once the support period has expired, downloads are only available to you for productversions with a Build Date on or before your license Support Expiration date.
After downloading your product, begin by unpacking the installation program, if
necessary. See the product Release Notes for installation details. When you begin the
product installation, you will need to identify the location of the license file you
received with your product. The installation will proceed only if you have a valid license
file.

3.5.2

Intel® Software License Manager downloads
If you are using counted licenses, you will also be required to install Intel® Software
License Manager. Do not use the Intel® Software License Manager for uncounted (Single
User) licenses – only for floating and node-locked licenses (see License Types).
Remember that the OS of the server system where the Intel® Software License Manager
is installed is irrelevant to the OS for the license(s) it supports. So the Intel® Software
License Manager can be installed on Windows*, Linux*, or OS X* machines regardless ofUser's Guide

17

Using the Intel® Software License Manager

the OS for each of your floating and node-locked Intel® Software Development Productlicenses.
You can download the Intel® Software License Manager from Intel® Software
Development Products Registration Center by following these steps:
1. Login to the Intel® Software Development Products Registration
Center at https://registrationcenter.intel.com/.
2. Select Search for older versions.
3. Select Intel® Software License Manager from the product list.
4. Select the appropriate operating system from the dropdown list.
5. Click on the hyperlink for the license server file you want todownload.
You must download the Intel® Software License Manager server corresponding to theoperating system where you are planning to install it, not for the operating system
where you are planning to run the client applications (Intel® Software Development
Products) Products). For example, you can install the license server on a OS X* system
to manage Intel product license seats for Windows*, Linux* and/or OS X* software
products.
The most recent version of the User Guide for the Intel® Software License Manager isalso available from the web site.
For more information about downloading the Intel® Software License Manager, see theIntel® Software License Manager Servers knowledgebase article.

3.5.3

Starting the Intel® Software License Manager on
Windows
1. Download the Intel® Software License Manager for Windows* thatmatches your environment(w_isl_server_<ver>_<architecture>.exe).
2. Run the self-extracting executable downloaded in the previous
step.
3. Provide the path to the license file during the installation of Intel®
Software License Manager.
4. Finish the installation process. The license manager should start
automatically as a service.

18

Document Number: 251879-014US

Installing the Intel® Software License Manager

If you do not have a license file during the installation process, you can still install thelicense server by checking the option to install without a license file. After installing theIntel® Software License Manager without the license file, you must start the license
server before running your product. Follow these steps to start the Intel® Software
License Manager on Windows*:
1. From the Windows* Start menu, select Programs > Intel® Software Development
Products > Intel(R) Software License Manager > Configure Intel(R) Software
License Manager.
2. Select the license file.
3. Click Apply and close the window.
Note: You will also be required to follow the above steps if you wish to restart thelicense server with a different license file.

3.5.4

Installing the Intel® Software License Manager on
Linux* and OS X*
Follow the steps below to install the software for the Intel® Software License Manager
on Linux* or OS X* systems:
1. Place the downloaded package<l|m>_isl_server_<ver>_<architecture>.tar.gz in the
directory to which you wish to extract its files. This need not be
the same location in which you plan to install the Intel® Software
License Manager files.
2. Extract the files from the package with the following command:tar -zxvf <l|m>_isl_server_<ver>_<architecture>.tar.gz
This command extracts the files and prepares you for installation.
3. Use the cd command to move to the flexlm/ directory created by
the above step.
4. Run the Install_INTEL script and follow the directions to installand configure the Intel® Software License Manager.
5. To run the license server, the user must have executable access tothe binary files lmgrd and INTEL. If executable access gets lost
during extraction and/or copying from a Windows* system, you can
use a command like one of the two listed below to set executable
access for the file:chmod 775 /flexlm/INTEL
orchmod +x "`pwd`/flexlm/lmgrd"
orchmod +x "$(pwd)/flexlm/lmgrd" (non-csh)

User's Guide

19

Using the Intel® Software License Manager

3.5.5

Starting the Intel® Software License Manager
automatically on Linux* after reboot
To set up the Intel® Software License Manager to start automatically follow the steps
below:
For Linux*, add the following steps to the system startup files (for example,/etc/init.d/rcX.d directories, where X is 1, 2, 3, or 5) to ensure that the Intel®
Software License Manager server starts after reboot. It is important that the network
has been initialized before the license server is started. Ensure that there is a whitespace (“ ”) between each argument. It is not necessary for server startup be done asroot.
1. cd <server-directory>
2. `pwd`/lmgrd –c `pwd`/<licensefile> -l `pwd`/<log file>or$(pwd)/lmgrd –c $(pwd)/<licensefile> -l $(pwd)/<log file>(non-csh)
Ensure that the change directory is set to the one created in Step 1 above. The-c <license file> should point to the license file copied to the server directoryfrom the registration e-mail. Use the full path to the license file, including the fulllicense file name.
The -l <log file> will capture information that will be useful for debugging
unanticipated server or license check-out problems. Use the full path where the log fileshould be created, including the log file filename.

3.5.6

Verifying the Intel® Software License Manager on
Linux* and OS X*
Follow these steps to verify that the Intel® Software License Manager is running on
Linux* or OS X* systems:
1. Use the cd command to move to the <server-directory>.
2. Execute the command lmstat –c <license file>. Use the fullpath to the license file, including the full license filename.

3.5.7

Compatible Versions of Intel® Software LicenseManager and Vendor Daemons
In a complex installation of multiple FLEXlm* and/or FlexNet Publisher* licensed
products, which include daemons from different vendors, a single lmgrd is used to
manage the use of all licensed products. You can use any lmgrd whose product version(lmgrd -v) is greater than or equal to all of the vendor daemons’ product versions. If
your lmgrd version is less than any of the vendor daemons’ versions, server startup
failures may result.

20

Document Number: 251879-014US

Installing the Intel® Software License Manager

3.5.8

Shutting Down or Removing the Intel® Software
License Manager on Linux* and OS X*
To shut down or remove the Intel® Software License Manager from Linux* or OS X*
systems, follow these steps:
1. Use the cd command to move to the <server-directory>.
2. Execute the command:lmdown –c <license file> (use the full path)
3. Killing the lmgrd and INTEL processes is not recommended.
However, if lmdown cannot successfully shut down the Intel®
Software License Manager, you may need to kill those processes.
4. To permanently remove the Intel® Software License Manager,
delete the lines that were added to the system startup files (forexample, /etc/init.d/rcX.d directories, where X is 1, 2, 3, or 5).
This step only applies to some Linux* systems.

User's Guide

21

Using the Intel® Software License Manager

4

Using the Client Application for theFirst TimeYou must complete the following steps to use the Intel® Software License Manager for
the first time:
1. Install the client application
2. Set the INTEL_LICENSE_FILE environment variable
3. Combine multiple license files

4.1

Installing the Client Application
If you are using counted licenses, you can install the client application without starting
the Intel® Software License Manager server by providing the full path to the complete
license file during the installation process. The complete license file includes:
 SERVER line(s) VENDOR line
 PACKAGE line(s) FEATURE/INCREMENT line(s)When using a license file to install a client application, you should put the license file
into the default license folder for the operating system on which you are installing.
Windows*: C:\Program Files\Common Files\Intel\Licenses
Linux*:/opt/intel/licenses/
OS X*: /Users/Shared/Library/Application
Support/Intel/Licenses/
Note: You need a complete license file residing on the client system or access to arunning license server during the process of installing a client application. You cannot
use the port@host mechanism or the USE_SERVER mechanism during the
installation of a client application unless the license server is running.

22

Document Number: 251879-014US

Using the Client Application for the First Time

4.2

Setting the INTEL_LICENSE_FILE
Environment Variable
Once you have installed the Intel® Software License Manager license server andinstalled the client application, the INTEL_LICENSE_FILE environment variablemust be set. Most Intel® Software Development Products have an environment
variables file (e.g. iccvars.sh for the Intel C++ Compiler for Linux*) that can be run to set
up the INTEL_LICENSE_FILE variable correctly. This environment variable must be
set for proper authentication of the product license file.
Other ways to set up the INTEL_LICENSE_FILE environment variable:
On Windows follow these steps, or the equivalent:
1. Click Start > Settings > Control Panel > System > Advanced> Environment Variables
2. Under system variables click New.
3. Enter INTEL_LICENSE_FILE in the text box for Variable Name.
4. In the Variable Value text box, input the full path to the folder
where one or more licenses reside. You may provide multiple pathvalues separated by semicolons “;”.
5. Click OK > OK > OK.
On Linux* and OS X* systems, the commands used to set the environment variables
depend on the shell.
Bash shell, Bourne shell (sh), and Korn shell (ksh) use the export and assignmentcommands:$ export INTEL_LICENSE_FILE=</path/to/license/file>where, </path/to/license/file> should be the folder in which one or morelicense files reside. You can provide multiple path values to the
INTEL_LICENSE_FILE variable by using “:” as a separator. For example,$ export
INTEL_LICENSE_FILE=/opt/intel/licenses:$HOME/intel/licens
es
C shell, use the setenv command:% setenv INTEL_LICENSE_FILE </path/to/license/file>

User's Guide

23

Using the Intel® Software License Manager

4.2.1

Counted Licenses and Alternatives
If the Intel® Software Development Product you are using is enabled for counted
licenses, which require a license server, you do not need to use the exact copy of thecounted license on the local system from which you run the Intel software product;
there are two alternatives:




4.2.2

Alternative 1
USE_SERVER mechanism for counted licenses: on the systems from which you will
execute Intel® Software Development Products, you can use a license file with the
USE_SERVER directive. The license file would be in the following format:
SERVER <server name> <hostid> <port>
USE_SERVER
where <server name>, <hostid>, and <port> all come from the SERVER
line in the license file which was used to install the license server. The
INTEL_LICENSE_FILE environment variable should point to the license file.
Alternative 2
port@host mechanism for counted licenses: on the systems from which you will
execute Intel® Software Development Products, you can set the
INTEL_LICENSE_FILE variable to port@host. The host and port information
are in the SERVER line in the license file used to install the Intel® Software LicenseManager server.
Note: The port@host mechanism does not work if you use it in a license fileinstead of setting the INTEL_LICENSE_FILE environment variable toport@host.

How to Specify Ports for License Servers
Intel’s license files specify two ports:
1. SERVER <host_name> <host_id> <port1>
2. VENDOR INTEL port=<port2>
Typically, Intel specifies port1 to 28518 and port2 is omitted, which causes thesystem to randomly assign the second port. You may specify port2 to a fixed value sothat you can open that port through any firewalls between the client application andthe server system running the Intel® Software License Manager.
When changing either port, you must ensure: The port numbers in all license files match on both the license host server andclient systems.
 The license server is restarted to read the updates.
 The INTEL_LICENSE_FILE environment variable on the client systems is
pointing to the correctly updated license file or port@host.
You may need to add a port exception to allow the FlexNet Publisher* license server
daemon, the Intel® Software License Manager vendor daemon, and the application

24

Document Number: 251879-014US

Using the Client Application for the First Timeusing these daemons to communicate. See the Add a Port Exception section of thisdocument for more information.

4.3

Combining Multiple License Files

4.3.1

Criteria for Combining License FilesYour product’s license file(s) define the license server(s) by host name and hostid in the
SERVER line(s) in the license file. License files may be combined provided they meetthe following criteria:
1. The number of SERVER lines in each license file is the same.
2. The hostid fields of SERVER lines in each license file match.
Note: You are not required to combine compatible license files. There is no
performance or system-load penalty for not combining the files.
Some possible reasons license files may not be compatible are:
 License files are set up to run on different server machines, so hostids are different.
 One file is set up for a single server (has only one SERVER line), the other is set up
for a three-server redundant license server (has multiple SERVER lines). For
further information on using redundant servers, see Redundant License Host
Servers and the information at http://software.intel.com/enus/articles/redundancy-server-notes/.

4.3.2

Instructions for Combining License Files
Combine multiple license server files into a single license file by performing these steps:
1. Concatenate the files.
2. Remove the duplicate SERVER and VENDOR lines.
Note: The expiration dates can be different and the number of seats can be different inlicense files but the lmhostid and hostname values in the license files should be thesame.
If you are combining multiple counted license files for a single product, you need tomake sure that following additional requirements are being met:

Only one license file has a FEATURE line and all other license files
have INCREMENT lines (see example below on how File0001.lic andFile0002.lic were combined into a single license file File0003.lic).
If this requirement is met, you can simply concatenate the license
files and remove the duplicate SERVER and VENDOR lines by making
sure that the license with the FEATURE line is the first key in the
combined license file and licenses with INCREMENT lines follow it(File0003.lic).

User's Guide

25

Using the Intel® Software License ManagerOr, all the license files of the same product have INCREMENT lines
instead of FEATURE lines (see below how File0004.lic andFile0005.lic were combined into a single license file File0006.lic).
If this requirement is met, you can simply concatenate the license
files and remove the duplicate SERVER and VENDOR lines(File0006.lic).
If you are combining multiple counted license files where each counted license file
is for a unique product, you can simply concatenate them and remove the duplicate
SERVER and VENDOR lines.
Note: If you update your license file, be sure to do the following:26



Verify that the license files on the client systems are the same as the license fileon the license host server.



Restart the Intel® Software License Manager license server to force it to readthe updated license file.



Verify that the INTEL_LICENSE_FILE environment variable is pointing to
the right license file or the correct port@host settings.

Document Number: 251879-014US

Using the Client Application for the First Time

4.3.3

ExamplesExamples are provided below for demonstration purposes only.
In the example below, both the File0001.lic and File0002.lic are for Intel® C++ Compiler
for Windows. File0001.lic has FEATURE line and is for 20 seats while File0002.lic has
INCREMENT line and has 20 seats. You can merge these two license files into a single
license file File0003.lic which can serve 40 seats.
File0001.lic
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CFEATURE I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY \PLATFORMS="i86_n ia64_n" DUP_GROUP=UH ck=92 SN=SMSA35123769 \SIGN=E7EDE36EB6AE

File0002.lic
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 \2C55559573D2 VENDOR_STRING=SUPPORT=COM HOSTID=ANY \PLATFORMS="i86_n ia64_n" DUP_GROUP=UH ck=92 SN=SMSA37693512 \SIGN= EB6AE E7EDE36

File0003.lic - Combined single file for Intel® C++ Compiler for Windows
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CFEATURE I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA35123769 SIGN=E7EDE36EB6AE
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 \2C55559573D2 VENDOR_STRING=SUPPORT=COM HOSTID=ANY \PLATFORMS="i86_n ia64_n" DUP_GROUP=UH ck=92 \SN=SMSA376935123769 SIGN= EB6AE E7EDE36

User's Guide

27

Using the Intel® Software License Manager

In the next example, both the File0004.lic and File0005.lic are for Intel® Visual FortranCompiler for Windows. Notice that both File0004.lic and File0005.lic have INCREMENT
lines (no FEATURE lines) and are for 20 seats. You can merge these two license files intoa single license file File0006.lic which can serve 40 seats.
File0004.lic
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA12373569 SIGN=DE36EE7EB6AE

File0005.lic
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA35912376 SIGN=E7EEDE36EB6A

File0006.lic - Combined single file for Intel® Visual Fortran Compiler for Windows
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA12373569 SIGN=DE36EE7EB6AE
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA35912376 SIGN=E7EEDE36EB6A

28

Document Number: 251879-014US

Using the Client Application for the First Time

Below is an example where you can combine license files of different products into asingle license file. File0003.lic is a combined license file for Intel® C++ Compiler for
Windows and File0006.lic is a combined license file for Intel® Visual Fortran Compiler for
Windows. You can combine these license files of two different products into a single
license file (File0007.lic) by concatenating them and simply removing the duplicate
vendor and server lines.
File0007.lic - Combined single file for Intel® C++ and Fortran Compiler for Windows
SERVER svr025.testserver.com 832d87d8 28518
SERVER svr026.testserver.com 832d7b86 28518
SERVER svr027.testserver.com 832d895e 28518
VENDOR INTEL <path to the vendor daemon options file (optional)>
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CFEATURE I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA35123769 SIGN=E7EDE36EB6AE
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=CCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA376935123769 SIGN= EB6AE E7EDE36
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA12373569 SIGN=DE36EE7EB6AE
PACKAGE I0000000000001 INTEL 2004.1003 2279DFB555D4 \COMPONENTS=FCompW OPTIONS=SUITE ck=88 SIGN=F452A16CA51CINCREMENT I0000000000001 INTEL 2004.1003 permanent 20 2C55559573D2 \VENDOR_STRING=SUPPORT=COM HOSTID=ANY PLATFORMS="i86_n ia64_n" \DUP_GROUP=UH ck=92 SN=SMSA35912376 SIGN=E7EEDE36EB6A

User's Guide

29

Using the Intel® Software License Manager

4.4

License Seat Check-out and Check-in

4.4.1

License Seat Allocation Overview
For an Intel® compiler product, the license seat is checked out (allocated) as soon as thecompiler or debugger is started; and returned when the compiler or debugger work is“done”.
Note: For performance libraries (Intel® Integrated Performance Primitives, Intel®
Threading Building Blocks, and Intel® Math Kernel Library), and some other Intel®
Software Development Products, license check-out is only done during productinstallation.
All floating license seats are available on a first-come first-served basis for check-out by
any number of products installed on client systems that have been configured to checkout floating license seats from the license host server system.
However, if all license seats are allocated for the requested product, additional users
are forced to wait for one of the client systems to release a floating license seat. This isautomatically done in our products, and means that some users may experience delays
if all license seats are simultaneously allocated. The wait time for a license seat isforever, until a license seat is available, and is not configurable by end users.
When all license seats are allocated, a new license check-out request will retry every 30
seconds until a license seat is available to be allocated to the request. A delay that
results from the wait for a license seat may appear to the end user that the product ishung or that performance has suddenly degraded.

30

Document Number: 251879-014US

Using the Client Application for the First Time

4.4.2

Allocation status
To determine how many floating license seats are checked-out, use the command
lmstat in one of the following ways:
On the license host server system, execute one of the following commands:
Linux*
lmstat -a -c <license file>
Windows*
lmutil lmstat –a –c <license file>license file is the full path including filename to the floating license file.
On the client system, execute one of the following commands:
Linux*
lmstat -a
Windows*
lmutil lmstat –a
Sample lmstat Output
The following is an example output of the lmstat command from a Linux* server
running Intel® Software License Manager. The output includes information about the
total number of licenses issued and total number in use.
$ ./lmstat –almstat - Copyright (c) 1989-2003 by MacrovisionCorporation. All rights reserved.
Flexible License Manager status on Wed 6/16/2010 02:11
License server status: 28518@spd16
License file(s) on spd16:/tmp/jsmith/bin/flexlm_ia32_RH8/spd16.lic:
spd16: license server UP (MASTER) v9.2
Vendor daemon status (on spd16):
INTEL: UP v9.2
Feature usage info:
Users of I00000000000000000080000000000: (Total of 2
licenses issued; Total of 0 licenses in use)
Users of FCompL: (Total of 2 licenses issued; Total of 0
licenses in use)

User's Guide

31

Using the Intel® Software License Manager

5

TroubleshootingThis chapter explains how to generate debug logs, lists the information you should
provide when opening a support request, and provides solutions for some common
problems.

5.1

Where to Start
You may visit the Getting-Started Support Page first to search for an answer to yourlicense manager problem. If you don’t find a solution, continue on with the next
section.

5.2

Creating Debug Logs for License Checkout
IssuesIf your licensing does not work properly, review the previous sections to verify the
installation. If the problem persists after you verify correct installation, you should open
a support case with Intel® Premier Support or the Intel® Software Development
Products Download, Registration & Licensing User Forum.
In preparation for opening the support case, set the environment variable
INTEL_LMD_DEBUG to 1 and execute the product (see Setting Environment
Variables). Doing so generates detailed information on the licensing failure. Pleaseprovide this information when filing a support issue. A product support engineer willthen work closely with you to resolve the outstanding issue.
If you are running a command-line application on Windows*, set the debugging
environment variable to the appropriate value on the command line. For example:
SET INTEL_LMD_DEBUG=1

View the current value of an environment variable. For example:
SET INTEL_LMD_DEBUG returns INTEL_LMD_DEBUG=1
Set the environment variable to a file name. For example:
SET INTEL_LMD_DEBUG="C:\temp\LicenseCheckout.log"
If the license debugging information is no longer needed, you can turn it off with thefollowing command:
SET INTEL_LMD_DEBUG="" or unset INTEL_LMD_DEBUG
Note: It is very important that you unset this debugging environment variable once yourissue has been resolved or once you have submitted the support request. Not doing so
will result in slower performance when the client application is running. Every time you
32

Document Number: 251879-014US

Troubleshooting

submit a license checkout log, you must make sure that the old log is deleted and the
new log has been created before it is attached to your support request.
If you are running a GUI application on Windows*, set the debugging environment
variable to the appropriate value by following the steps below:
1. Click Start > Settings > Control Panel > System > Advanced> Environment Variables.
2. Under system variables click New.
3. Enter INTEL_LMD_DEBUG in the text box for Variable Name.
4. In the Variable Value text box, input the full path to the log file inwhich you would like to capture the results. For example
C:\temp\LicenseCheckout.log.
5. Click OK > OK > OK.
Note: It is very important that you unset this debugging environment variable once yourissue has been resolved or once you have submitted the support request. Not doing so
will result in slower performance when the client application is running. Every time you
submit a license checkout log, you must make sure that the old log is deleted and the
new log has been created before it is attached to your support request.
On Linux* or OS X* systems, the commands used depend on the shell in use.
With the bash shell, Bourne shell (sh), and Korn shell (ksh), use the export command
and assignment command to set the environment variable:$ export INTEL_LMD_DEBUG=1
Alternatively, you can set the INTEL_LMD_DEBUG environment variable to a file
name. For example,



export INTEL_LMD_DEBUG="/tmp/licensecheckout.log"
To remove the association of an environment variable and an external file with theBourne, Korn, or bash shell, use the unset command:$ unset INTEL_LMD_DEBUG
With the C Shell, use the setenv command to set an environment variable:% setenv INTEL_LMD_DEBUG 1
To remove the association of an environment variable and an external file with the
C shell, use the unsetenv command:% unsetenv INTEL_LMD_DEBUG

Note: It is very important that you unset this debugging environment variable once yourissue has been resolved or once you have submitted the support request. Not doing so
will result in slower performance when the client application is running. Every time you

User's Guide

33

Using the Intel® Software License Manager

submit a license checkout log, you must make sure that the old log is deleted and the
new log has been created before it is attached to your support request.

5.3

Information Needed for Support Requests
When opening a support request, you should provide the following information to the
support team:



5.3.1

Client Information
Intel Software License Manager Information

Client Information








Package ID of the product. This is the name of the file you downloaded andinstalled.
Name of client application with all parameters.
Operating system, architecture, kernel, glibc, and any service packs installed on theclient system.
Values to which the LM_LICENSE_FILE and INTEL_LICENSE_FILE
environment variables are set.
A copy of all license files used on the client system. It is important to copy thelicense files themselves rather than copy/pasting the contents as this can maskother potential problems with the files.
On Linux* or OS X*, set INTEL_LMD_DEBUG to/tmp/licensecheckout.log and on Windows*, set INTEL_LMD_DEBUG to
C:\temp\licensecheckout.log and run the client. Once the client finishes
execution, attach the licensecheckout.log to the support issue.

If you are opening a support request about a segmentation fault issue, attach the stack
dump.

5.3.2

Intel Software License Manager Information
This section is applicable only if you are using counted licenses.




34

Operating system, architecture, kernel, glibc, and any service packs installed on thesystem on which the Intel® Software License Manager server is installed.
The Intel® Software License Manager server file name that you downloaded andinstalled
A copy of the server log file at one of the following locations, depending on youroperating system:
Windows*: <install drive>:\program files\common
files\intel\flexlm\iflexlmlog.txt
Linux * or OS X*: <install location of servers>/lmgrd.log

Document Number: 251879-014US

Troubleshooting





5.4

A copy of the license file you used to start the server. It is important to copy thelicense files themselves rather than copy/pasting the contents as this can maskother potential problems with the files.
Values to which the LM_LICENSE_FILE and INTEL_LICENSE_FILE
environment variables are set.

Common Issues
This section contains descriptions of two common issues and provides solutions tothose issues.

5.4.1

License Checkout Failing Due to Terminal Server
Client or Remote Desktop Connection on Windows*
Problem: You cannot use client applications on Windows* from a remote desktop
connection or terminal server client to checkout a license.
Solution: Using new client applications on Windows* with an old license may preventthe license checkout mechanism from working. You may, therefore, see the following
error message: Terminal Server remote client not allowed.
If you see this message, please contact the support team to obtain a new license filethat allows you to use Windows*-based products from a remote desktop connection or
terminal server. Please note that this message applies to new Windows*-based
products only and applies to uncounted licenses, also known as single user licenses.

5.4.2

Client and Server Not Able to Connect Due toWindows Firewall
Problem: The firewall for Windows* XP with Service Pack 2 or above prevents the client
application from connecting to the Intel® Software License Manager server on
Windows* XP.
Solutions: Windows* XP with Service Pack 2 or above comes with a firewall which isturned on by default. If the firewall is turned on your FlexNet Publisher* license server
daemon and Intel® Software License Manager license server vendor daemon may stopfunctioning. You can find more information about the firewall at msdn.microsoft.com.
There are two methods to make the FlexNet Publisher* license server daemon and theIntel® Software License Manager license server vendor daemon function properly.

5.4.2.1

Add a Program Exception in Windows* XP
Add a program exception to allow the FlexNet Publisher* license server daemon and theIntel® Software License Manager license server vendor daemon to use required ports.
You must execute both step 4 and step 5. Failure to do so causes the FlexNet Publisher*license server not to work.

User's Guide

35

Using the Intel® Software License Manager

Click Start >Run. Type Wscui.cpl, and click OK.
In the Windows* Security Center window, click Windows* Firewall.
Click on the Exceptions tab and click Add Program.
In the list of programs, look for lmgrd.exe.
a. If lmgrd.exe is in the list of programs, select it and click OK.
b. If lmgrd.exe is not in the list of programs, click Browse to locate it in
C:\Program Files\Common Files\Intel\FLEXlm.
c. Select lmgrd.exe. Click Open and OK.
5. In the list of programs, look for INTEL.exe.
a. If INTEL.exe is in the list of programs, select it and click OK.
b. If INTEL.exe is not in the list of programs, click Browse to locate it in
C:\Program Files\Common Files\Intel\FLEXlm.
c. Select INTEL.exe. Click Open and OK.
1.
2.
3.
4.

5.4.2.2

Add a Port Exception in Windows* XP
Add a port exception to allow the FlexNet Publisher* license server daemon, Intel®
Software License Manager license server vendor daemon, and application using these
daemons to communicate. You must execute both step 4 and step 5. Failure to do socauses the FlexNet Publisher* license server not to work.
1. Click Start > Run. Type Wscui.cpl and click OK.
2. In the Windows* Security Center window, click Windows* Firewall.
3. Click on the Exceptions tab and click Add Port.
4. In the dialog box, enter Intel(R) Software License Manager Vendor
Daemon in the Name field.
5. Enter the TCP/IP port number of the INTEL vendor daemon in the Port number
field.
a. This is the port number specified on the VENDOR line of the license file.
b. You can also obtain the port number from the log file IFLEXLmLog.txt in the
C:\Program Files\Common Files\Intel\LicenseServer folder in a line like this:INTEL using TCP-port <port>
6. Click OK.
7. Click Add Port again.
8. In the dialog box, enter FlexNet Publisher License Server Daemon(lmgrd.exe) in the Name field.
9. Enter the TCP/IP port number of the FlexNet Publisher* license server daemon in
the Port number field.
a. This is the port number specified on the SERVER line of the license file.
b. You can also obtain the port number from the log file IFLEXLmLog.txt in the
C:\Program Files\Common Files\Intel\LicenseServer folder in a line like this:lmgrd using tcp-port <port>
10. Click OK.

36

Document Number: 251879-014US

Checklist for Intel® Software License Manager Server/Client Installation

6

Checklist for Intel® Software
License Manager Server/Client
Installation
Note: Many of the following steps should be repeated when a floating product license isrenewed or added to an existing set of floating licenses and when a combined license
file is updated.

6.1

License Host Server System Checklist
Your
StatusUser's Guide

Step Task Description

For more information

1

Download the latest Intel®
Software License Manager User
Guide

http://software.intel.com/enus/articles/license-manager-for-flexlmusers-guide2

Download the Intel® Software
License Manager that best
matches your license hostserver OS and platform

http://software.intel.com/enus/articles/performance-tools-forsoftware-developers-intel-flexlmlicense-servers/

3

Verify your license host servermachine’s host name and hostid. If you are using three
redundant license host server
systems, verify the host nameand host id for all threemachines.

http://software.intel.com/enus/articles/how-to-find-host-id-forfloating-licenses/

4

Verify your floating licenses areregistered with the correct hostname and host id specified. If
you are using three redundant
license host server systems,
verify all three host names andhost ids are specified for eachfloating license.

Log in to the Intel® Software
Development Products Registration
Center at
https://registrationcenter.intel.com/

37

Using the Intel® Software License Manager

5

If any of your floating licenses
have incorrect or out-of-datehost name or host id
information, follow the
instructions in the user guide tocorrect the information in the
floating license(s) and obtain
updated license file(s).

http://software.intel.com/enus/articles/change--serverhost-datanode-locked-or-floating-license/

6

If you wish to combine you
floating license files into one
file, follow the instruction in the

http://software.intel.com/enus/articles/how-do-i-combine-multiplelicense-files/

Combining Multiple License Files

section of this user guide.
Your
Status38

Step Task Description

For more information

7

Verify that all individual floating
license files or the combined
license file resides on yourlicense host server system.
Ensure there are no Single User,evaluation, or Beta licenses
residing in the Intel license
folder on your license hostserver system.

On Linux*: /opt/intel/flexlm/

8

If you have specified three
redundant license host server
systems in your floating
licenses, at least two of thethree redundant license hosts
servers must be up and runningat all times.

http://software.intel.com/enus/articles/redundancy-server-notes/

9

Install your Intel® Software
License Manager server binary
on your license host server
system. If you have specified
three redundant license hostserver systems in your floating
licenses, complete all threelicense host server installations.

Follow the instructions in Chapter 3:

On OS X*: /opt/intel.flexlm/
On Windows*: C:\Program
Files\Common
Files\Intel\LicenseServer\

Installing the Intel® Software LicenseManager.

Document Number: 251879-014US

Checklist for Intel® Software License Manager Server/Client Installation

10

Start your license host server
process by following the
instructions in Chapter 3:
Installing the Intel® Software
License Manager.

11

User's Guide

Ensure your license server isrunning using the lmstat
command.

If you are using Windows* Vista,
Windows* 7, or Windows* Server
2008 system, please see theinformation at
http://software.intel.com/enus/articles/installing-license-server-onvista/.
http://software.intel.com/enus/articles/when-is-a-floating-licenseseat-checked-out-and-checked-in/

39

Using the Intel® Software License Manager

6.2

Client Systems Checklist
Your
StatusStep Task Description

For more information

1

Download the latest Intel®
Software License Manager User
Guide

http://software.intel.com/enus/articles/license-manager-for-flexlmusers-guide2

Install the Intel® Software
Development Products yourusers will be running on eachclient system. If using a copy ofthe complete server license file
to install the product, you need
to use an exact copy and place
it in the default license file
folder.

Follow the instructions for installinga client product in the Installing the
Client Application section of the user
guide.

3

Set the INTEL_LICENSE_FILE
environment variable on eachclient system.

http://software.intel.com/enus/articles/how-to-set-intel_license_fileenvironment-variable/4

Launch your Intel® Software
Development Product.

If problems occur with floating
license seat check-out, please follow
the steps in Chapter 5: Troubleshootingof the user guide to capture a debug
log and submit an issue. Be sure toinclude:1. OS and architecture for yourlicense host server system(s)2. The name of the specific Intel®
Software License Manager
package you downloaded andinstalled.
3. The serial number for thefloating license you are using.
4. The environment variablesettings for INTEL_LICENSE_FILE
and LM_LICENSE_FILE.
5. A copy of each floating license
file you are using.
6. The combined license file (ifapplicable).

40

Document Number: 251879-014US

Checklist for Intel® Software License Manager Server/Client Installation

7. Host server name and host id for
all license host servers.
8. Captured output of lmstat
command.
9. License server and client-side
debug logs

User's Guide

41

Using the Intel® Software License Manager

7

Appendices

7.1

Appendix A: Latest Revision of User’s
Guide
The latest information about the Intel® Software License Manager and use of FlexNet
Publisher* in Intel® Software Development Products can be found at:
http://software.intel.com/en-us/articles/license-manager-for-flexlm-users-guide/42

Document Number: 251879-014US

Appendices

7.2

Appendix B: Troubleshooting Guide
Step 1. Identify the OS and architecture for installing the Intel® Software License Manager.
a.
Choose a system and OS where you would like to install the Intel® Software License Manager. You mustchoose an operating system and architecture combination listed in the Supported Platforms section of
the user guide. Note: Make sure you have downloaded the latest version of the user guide fromhttp://software.intel.com/en-us/articles/license-manager-for-flexlm-users-guide.
1.
Determine the license server OS.
2.
Determine the host name and host id of your license server system. Refer to Installing the Intel®
Software License Manager in the user guide.
Note: It is very important that the host id is accurate. If it is not accurate, the license file will not work.
Step 2. Register your serial number at the Intel® Software Development Products Registration Center.
a.
Go to https://registrationcenter.intel.com/.
b.
Register your serial number using the host name and host id from the previous step.
c.
Receive the license file as an attachment via email from the Intel® Software Development Products
Registration Center
Step 3. Verify the validity of the license file for the system where you intend to install the Intel® Software LicenseManager.
a.
Note: This step needs to be executed on the system where you intend to install the license server.
b.
The server’s host id and hostname (collected in Step 1 above) should match the information in the license
file. The following optional steps may help ensure you have a valid license file:1.
Install Intel® Software License Manager without specifying a license file. (Refer to Installing theIntel® Software License Manager in the user guide for further information about downloading
and installing the license server).
2.
Run the lmhostid command (on Windows*, use lmutil lmhostid).
3.
Compare the output with the SERVER line in your license file.
4.
If the host id values do not match, follow the instructions in the Changing Server/Host Data forYour Product License section to obtain a corrected license file.
Step 4. Combine multiple license files into one license file.
a.
See the section Combining Multiple License Files in the user guide for further details.
Step 5. Download and Install the Intel® Software License Manager.
a.
Log in to the Intel® Software Development Products Registration Center athttps://registrationcenter.intel.com, click the Search for older versions link, and download thelicense server for your operating system and architecture as determined in Step 1.
b.
On Linux* or OS X*, you must unpack the .tar.gz file.
c.
Execute the license server install program to install the license server. On Linux* and OS X*, this is a script.
On Windows*, it is a self-extracting executable. (Refer to the Installing the Intel® Software LicenseManager chapter of the user guide for detailed instructions).
Provide the combined license file from Step 4 above or a single counted license to the license server install as
applicable.
d.
Verify the license server is running using the lmstat command (on Windows*, use lmutil lmstat).
These command binaries are available in the folder where you installed Intel® Software License Manager.
e.
Open and read the license server log file.
1.
For Linux* and OS X*, the license server log file (lmgrd.log) can be found in the license server
install location.
2.
For Windows*, the license server log file is C:\Program Files\Common
Files\Intel\LicenseServer\IFLEXlmLog.txt.
f.
If you see any issues in the log file that you are unable to resolve on your own, submit a support request.
1.
Attach the log file.
2.
Attach the license file used to start the Intel® Software License Manager.

User's Guide

43

Using the Intel® Software License Manager

Step 6. Start the license server with the license file (if you installed the license server without the license file).
Note: If you successfully started the license server in Step 5, you should skip this step.
For Linux* or OS X*:
a.
Copy the license file from either Step 4 if you combined licenses or the file your received from the Intel®
Software Development Products Registration Center in Step 2 into the license server install location.
b.
Change directory to the location where the license server is installed. (e.g. cd <install-directory>).
c.
Run the command `pwd`/lmgrd –c `pwd`/server.lic –l `pwd`/lmgrd.log.
d.
Open and read the license server log file (lmgrd.log).
For Windows*:a.
Copy the license file from either Step 4 if you combined licenses or the file your received from the Intel®
Software Development Products Registration Center in Step 2 into C:\Program Files\Common
Files\Intel\Licenses.
b.
Click on Start > Programs > Intel(R) Software Development Products > Intel(R) Software License Manager >Configure Intel(R) Software License Manager.
c.
Browse to the server license that was copied into C:\Program Files\Common
Files\Intel\Licenses in Step 6a.
d.
Open and read the license server log file (C:\Program Files\Common
Files\Intel\LicenseServer\IFLEXlmLog.txt).
For all supported operating systems:e.
If you see any issues in the log file that you are unable to resolve on your own, submit a support request.
1.
Attach the log file.
2.
Attach the license file used to start the Intel® Software License Manager.
Step 7. Configure the client systems before installing client applications.
a.
Ensure the client system has access to the license server or a copy of the floating license used to install theIntel® Software License Manager.
b.
If you wish to use a license file rather than the port@host mechanism, copy the floating license file from Step
2 or Step 4, as applicable, to the client system in the one of the following locations:
For Linux*: /opt/intel/licenses
For OS X*: /Users/Shared/Library/Application Support/Intel/Licenses
For Windows*: C:\Program Files\Common Files\Intel\Licensesc.
Set the INTEL_LICENSE_FILE environment variable to point to the server using the port@host format
or to the license file copied in Step 7b above.
d.
Verify that any firewall allows communication between the client and server systems. See theTroubleshooting chapter of the user guide for more details.
Step 8. Install the client application and make sure license checkout is successful.
a.
Install the client software.
b.
If installation fails, set the environment variable INTEL_LMD_DEBUG to <temp-directorylocation>/LicenseCheckout.log and run the install again.
c.
Search for the string “checkout: environment” in the LicenseCheckout.log created in the previous
step.
d.
Review the list of licenses and the order used.
e.
Verify the valid floating license is in the list.
f.
Look for error messages and correct if possible.
g.
If you are unable to solve any issues on your own, submit a support request according to the instructions in
the Support Requests section of the user guide.
Step 9. Make sure the product works.

44

Document Number: 251879-014US