You should already have a license file containing the
license data for the product you wish to run.
If this license contains at least one PACKAGE line,
at least one FEATURE line,
at least one SERVER line,
and at least one VENDOR line containing the word INTEL,
then it is a counted license that requires a license server.
Licenses that are not counted (i.e., do not have SERVER and VENDOR lines)
do not require a license server.
On the system where you will be installing the Intel(R) Software License Manager,
create a file that contains only the multi-line license data you wish to use.
Be sure to include all
SERVER,
VENDOR,
PACKAGE
and FEATURE lines (and their
continuation lines).
This document refers to this file as the
new-license-data-file.
The new-license-data-file
must be a normal ASCII text file.
Many large sites have central facilities for dealing with FLEXlm* licenses. If your site is one of those, give a copy of the license data to your local FLEXlm* support person, and let them perform their installation magic. Then skip to the Install the License Server section.
Examine the license data. If you have at least one line beginning
with the word SERVER and at least one line beginning with
the word VENDOR, which contains the word INTEL, then you will need the
license manager daemons.
If the license data does not contain these lines, then you will
not need the license manager daemons, and you can skip to the
Install the License Server section.
Login to the machine identified by the SERVER line of
the license data. See if a license manager daemon is already running
that serves Intel(R) FLEXlm* licenses by executing the following command:
ls /usr/tmp/.flexlm/lockINTEL
If this file does exist, then there should be license manager daemons running that are serving Intel(R) FLEXlm* licenses. Go to the section on adding license data to an existing license file.
Login to the machine where the Intel(R) Software License Manager will be installed.
Note that if you need license manager daemons,
this need not be the same machine as the one identified
on the SERVER line.
The installation process will ask you if the license data to be used with the server is stored in a file. Answer y and enter the full path to the new license file data.
Complete the installation process.
The installation process will place a copy of
new-license-data-file
into the server.lic file in the
Intel(R) Software License Manager installation directory.
If the license data does not contain a SERVER
or a VENDOR line, then you are done.
Otherwise you may have to start the license manager daemons.
cd to the directory where the
Intel(R) Software License Manager is installed. Use the following command to
determine if the license manager daemons are running:
./lmstat -c server.licIf the license manager daemons are running, you will see output that looks something like:
Flexible License Manager status on Mon ...
License server status: ...
License file(s) on <server>: <full-path-to-a-file>
<server>: license server UP (MASTER) v7.2
Vendor daemon status (on <server>):
...
INTEL: UP v7.2
If you see an output that looks like this, check:
UP
v7.2
INTEL is listed under the
vendor daemon status section
INTEL is UP
INTEL has a version
number greater than or equal to v7.2
./lmstat passes all of these checks,
then you are done. You should read the sections on
starting and
stopping
license manager daemons,
unless your site has a FLEXlm* guru to handle these tasks.
If the output ./lmstat looks close to
the above sample output, but fails one or more of the checks,
then there is a problem that needs to be resolved, and you need
help.
If the license manager daemons are not running,
the output from ./lmstat
will look something like:
License server status: ...
License file(s) on <server>: <full-path-to-a-file>
lmgrd is not running: Cannot connect to license server ...
(Connection refused)
The license manager daemons must be running in order to use your product.
First, make sure that you have the correct daemons
for the SERVERs platform type.
If the system identified on the SERVER
line of the license
data is not the same platform type as the machine where your product
is installed (that is, one is Linux and the other Windows,
or the server machine is a non-IA machine, etc.),
then you need to download the latest
FLEXlm* daemons and utilities for the SERVER
machine before proceeding.
Login to the system identified by the SERVER
line of the license data.
To start the license manager daemons:
<server-install-dir>/lmgrd.intel -c <server-install-dir>/server.licwhere
<server-install-dir> is the full path to
the flexlm subdirectory containing the FLEXlm* daemons
and utilities for the SERVER platform type.
Yes, it is a little annoying to use full paths for the previous command.
You will find it useful if you ever have to track down where
a license manager resides in the file system from the output of
a ps command.
The Intel(R) Software License Manager should now be operational.
To make things easier, we recommend that you talk to your system
administrator, so that these daemons are automatically started
when the system is booted and stopped when the system is taken down.
Show the system administrator the sections on this WEB page
about starting and
stopping
license manager daemons,
and the file: lmgrd.intel.rc from
the Intel(R) Software License Managerflexlm installation.
Login to the system identified by the SERVER
line of the license data.
To stop the license manager daemons:
<server-install-dir>/lmdown -c <server-install-dir>server.licwhere
<server-install-dir> is the full path to
the flexlm subdirectory containing the FLEXlm* daemons
and utilities for the SERVER platform type.
The following sections contain various detailed information about existing license data files. Yes, you can do these tasks yourself, but it is a lot easier to ask your local FLEXlm* guru for help ... if you have one.
Login to the machine where you will install the License Server. cd to the directory where the Intel(R) Software License Manager distribution file will be untar'ed. Uncompress (if necessary) and untar the Intel(R) Software License Manager distribution file. Look to see if the command lmutil is present with the following command:
find . -name lmutil -print
If lmutil is not present, then you need to download a copy for this system type.
cd to the directory that contains the lmutil command.
Make a copy of the new-license-data-file that you
created earlier in the current directory and call that file:
temporary.lic.
Edit ./temporary.lic, changing the last group of digits on
the SERVER line (the port number)
to 0001.
If you want to keep the original form of the SERVER
line around, any line that begins with a # character
is treated as a comment.
Then run the following command:
./lmutil lmdiag -c ./temporary.licIt is important to use the ./lmutil form of this command to make sure that you get the correct version of lmutil and not another version of lmutil that might happen to be on your path.
You will get an output that looks something like:
lmutil - Copyright (c) 1989-2008 Acresso Software Inc. All Rights Reserved.
FLEXlm diagnostics on ...
-----------------------------------------------------
License file: temporary.lic
-----------------------------------------------------
=== (lines edited out for brevity) ===
This license cannot be checked out because:
Cannot connect to license server
... I will try to determine what the problem is...
->Node <server> is UP and the network is working
->the lmgrd for this license file (1@<server>) does not respond
This means that either the license servers were not
started, or that lmgrd is running on another port. If
you would like to see if lmgrd is running on another port,
choose the extended connection diagnostics.
The extended connection diagnostics attempt to determine the
reason you cannot connect to the license server.
This process involves an attempt to connect to
every port on the server node. This operation can
take a few minutes.
Do you want to perform the extended connection diagnostics?: [y/n]:
Answer:y
The utility will search all of the ports on the system
identified on the SERVER line,
looking for license managers. The utility will
provide a list of active ports, and tell you which ones
are FLEXlm* license managers. If one of the license
managers is serving licenses for your product, then it will
contain an entry mentioning the vendor daemon INTEL.
Here is a typical output for a system running a single FLEXlm* license manager that is already serving licenses:
Running extended connection diagnostics to host <server>
There is an lmgrd running on port 1710
The vendor daemon "INTEL" is running with the lmgrd at port 1710
This means that the port number in your license file (1)
is wrong, and should be changed to 1710
6 ports are listening, 1 of them are lmgrd processes
Extended diagnostics done - all ports found reported above
-----------------------------------------------------
Enter <CR> to continue:
Answer: Control-C
At this point, we know that the port number on the SERVER
line should be the number indicated in the output that YOU RECEIVE
(not the number 1710 from the above sample output).
Edit both temporary.lic and
new-license-data-file and change the
final group of digits on the SERVER line
to the new port number.
Execute the following command:
./lmutil lmstat -c temporary.lic
Output from this command will look something like:
Flexible License Manager status on ...
License server status: ...
License file(s) on <server>: <server-license-file>:
<server>: license server UP (MASTER) v7.2
Vendor daemon status (on <server>):
INTEL: UP v7.2
Where <server> is the name of the
system identified by
the SERVER line in your license data, and
where <server-license-file> is the full path to the
license file that this license manager daemon is using.
There may be more than one server-license-file listed.
You have two choices: either add another
server-license-file to the
configuration of this license manager daemon, or add your
license data to one of the existing server-license-files.
In either case, you
have to discover who owns the license manager daemon. The best
way to do that is usually through the ownership of the
server-license-files that it uses.
Use ls -l on
each server-license-file to discover that,
or talk to your system administrator.
Adding another server-license-file to the
configuration of the license
manager daemon is beyond the scope of this page. If you want
to do this, ask for help.
Look through all of the listed license data files.
If only one references INTEL,
then select that one as the license data file to edit.
If more than one contains references to INTEL,
then pick the one that makes the most sense to you.
Otherwise, just pick any one of the listed
server-license-files.
If the SERVER line from the new-license-data
is EXACTLY the same as the existing SERVER line
(except for the port number), then
edit the selected license data file.
Place the new-license-data at the end of the file.
Comment out the SERVER
line from the new-license-data by adding
a # character to the front of the line.
If the SERVER lines are not comparable then you
must add another server-license-file to the
configuration of the license manager daemon.
Recall the output from the
./lmutil lmstat -c temporary.lic command issued earlier:
Flexible License Manager status on ...
License server status: ...
License file(s) on <server>: <server-license-file>:
<server>: license server UP (MASTER) v7.2
Vendor daemon status (on <server>):
INTEL: UP v7.2
Check that:
UP
v7.2 or higher
INTEL is listed as a vendor daemon
INTEL is UP
INTEL is version v7.2 or higher
flexlm subdirectory that contains the
./lmutil command also has a v7.2 license
server named: lmgrd.intel. You have to
locate the code that causes this license server to execute.
Normally, your system manager is the person to ask, as
the license servers are started automatically at boot time.
If INTEL is not listed as a vendor daemon
then INTEL needs to be added to the available daemons.
Edit the selected license data file (the one you just added
the new-license-data to).
The current version of INTEL resides in the
same directory as the lmutil command you have
been using on the machine identified by the SERVER line.
To the end of the VENDOR line for the license data
you just added, append a blank, and then the full path to
INTEL.
If the version number of INTEL is too small, then
the version of INTEL being run by the
license server must be updated.
The current version of INTEL resides in the
same directory as the lmutil command you have
been using on the machine identified by the SERVER line.
Edit all server-license-files
that contain references to INTEL.
Comment out all VENDOR and DAEMON
lines that reference INTEL
except for the VENDOR line
in the license data you just added.
(Any line beginning # character is treated as a comment.)
To the end of the VENDOR line for the license data
you just added, append a blank, and then the full path to
INTEL.
If you did not upgrade the license server to a new version, then all you have to do is make the license server reread the files you edited. Use the following command (execute once for each license file edited):
./lmutil lmreread -c <license-file-you-edited>
If you upgraded the license server, or are just a little paranoid about on-the-fly restart capabilities, you should shut down the license server, and then start it up again. Use the following command to shut down the license server:
./lmutil lmdown -c <license-file-you-edited>
Use the following command to start the license server (be sure to have a
-c xxx option for each existing license file):
<server-install-dir>/lmgrd.intel -c <server-license-file>where
<server-install-dir> is the full path to
the flexlm subdirectory containing the FLEXlm* daemons
and utilities for the SERVER platform type.
Yes, it is a little annoying to use full paths for the previous command.
You will find it useful if you ever have to track down where
a license manager resides in the file system from the output of
a ps command.
Execute the command:
./lmutil lmstat -c temporary.licThe output should be something like:
Flexible License Manager status on ...
License server status: ...
License file(s) on <server>: <server-license-file>:
<server>: license server UP (MASTER) v7.2
Vendor daemon status (on <server>):
INTEL: UP v7.2
Check:
UP
v7.2 or higher
INTEL is listed as a vendor daemon
INTEL is UP
INTEL is version v7.2 or higher
*Other names and brands may be claimed as the property of others.