Checklist for Installation and Troubleshooting Intel® FLEXlm* License Manager

NOTE: Many of the following steps should be reviewed and performed when a floating product license is renewed or added to an existing set of floating licenses, and when a combined license file is updated.


1. Download the latest Intel FLEXlm* License Manager user guide. Click here to download the user guide.

Steps to complete FOR THE LICENSE HOST SERVER SYSTEM(S)

2. Download the Intel® FLEXlm* license server that best matches your license host server OS. Click here to download license servers.

3. Verify your license host server machine’s host name and host id. If you are using three redundant license host server systems, verify the host name and host id for all three machines. Click here for more information. 

4. Verify your floating licenses are registered with the correct host name and host id specified. If you are using three redundant license host server systems, verify all three host names and host ids are specified for each floating license.
You can find this information by logging  into the Intel Registration Center and checking your floating license information.

5. If any of your floating licenses have incorrect or out-of-date host name or host id information, follow the instructions in this user guide to correct the information in the floating license(s), and obtain updated license file(s). Click here for more information.

6. If you wish to combine your floating license files into one file, follow the instructions in section 4.3 of the Intel® FLEXlm* License Manager user guide, or follow the instructions here.

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

On Linux*: /opt/intel/flexlm/
On Mac OS* X: /opt/intel/flexlm/
On Windows*: C:\Program Files\Common Files\Intel\FLEXlm

8. If you have specified three redundant license host server systems in your floating licenses, at least two of the three redundant license host servers must be up and running at all times. Click here for more information.

9. Install your Intel® FLEXlm* license server binary on your license host server system. If you have specified three redundant license host server systems in your floating licenses, complete all three license host server installations. Follow the instructions in Chapter 3 of the Intel FLEXlm* License Manager user guide.

10. Start your license host server process by following the instructions in Chapter 3 of the Intel FLEXlm* License Manager user guide. If you are using a Vista or Windows Server 2008 system, please see the information at this link.

11. Ensure your license server is running by following the instructions in the user guide for the << lmstat >> command. Click here for more information.


Steps to complete ON THE CLIENT SYSTEMS

12. On each client system, install the Intel software product(s) your users will be running from that client system. You will likely need a copy of the floating .lic license file on the client system for each product you will be installing; please put the copy of the Intel product floating license file(s) in the default Intel license file directory, and make sure you are using the same license file on the client system as you are using on the license host server system(s).

There is a different default Intel license file directory on Windows*, Linux* and Mac OS* X.

Windows*:   C:\Program Files\Common Files\Intel\Licenses

Linux*:   /opt/intel/licenses/

Mac OS* X:  /Users/Shared/Library/Application Support/Intel/Licenses/


13. Set the INTEL_LICENSE_FILE environment variable on each client system. Click here for more information.

14. Try launching the Intel product, such as the Intel® C++ Compiler product.

15. If problems occur with floating license seat check-out, or with any of these steps, please follow the steps in Chapter 5 of the user guide to capture a debug log for your license host server. 

Then submit a new issue to Intel® Premier Support and attach the debug log you generated.
If you do not have access to Premier Support, please post a new question on the user forum.

15. To help the Support team assist you efficiently with your problem, please provide the following information:

     a. OS and architecture for your license host server system(s)

     b. the name of the specific Intel FLEXlm license manager server file you downloaded and installed

     c. the serial number for the floating license you are using
[NOTE: DO NOT POST SERIAL NUMBERS IN USER FORUM COMMUNICATIONS UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     d. the environment variable setting for INTEL_LICENSE_FILE

     e. a copy of each floating license file you are using
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     f. the combined license file (only if customer is using a combined license file)
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     g. host server name and host server id for the license host server(s)

      h. verification that Intel License manager is running (capture of the results of running the appropriate lmstat command)
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     i. license server debug log and client-side debug log
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]



For more complete information about compiler optimizations, see our Optimization Notice.

Comments

Hi,

Hi,

I want access to specific versions of intel compilers from the past;
fi. I need ifort/l_cprof_p_11.1.073.tgz & icc/l_cproc_p_11.1.073.tgz
including older IMPI, namely v. l_mpi_pu_4.0.0.028.tgz (flexlm complained on that)

Where do I find them?

N.B.: I don't want a slightly later or earlier version; just these specific ones
and the specific tarball format they have been released in the past.
This is crucial for our HPC setup workflow which relies on reproducibility principles.

tia,
Fotis



fyi.

fyi.
to other readers; we are now tracking these cases, as issues 691555 (old tarballs) & 691558 (old impi); so far, the progress is that an evaluation license can get you unstuck for compiling against an older impi, meanwhile a long term solution is being sought...

cheers,
Fotis