The main components of our licensing are:
The ANSYS License Manager, including:
Licensing Interconnect (ansysli_server) -- Also includes ansysli_monitor, which ensures that the license server is functioning correctly and attempts to correct the situation if the license server is not running or is unresponsive.
FlexNet license manager daemon (lmgrd)
Vendor daemon (ansyslmd)
License files
Application program (e.g., Mechanical APDL (ANSYS) or ANSYS Fluent)
License server machines
These components are explained in more detail in the following sections.
The ANSYS License Manager monitors what products are being run, who is running them, and from what computer system. It grants or denies permission to run products. When an ANSYS product begins, it requests permission to execute from a license server. The ANSYS License Manager checks the pool of available licenses and grants the request only if the required licenses are available. For each request that is granted, the licenses are removed from the pool. As each product execution ends, its licenses are returned to the pool.
lmgrd is one of the FlexNet components of the ANSYS License Manager. Its primary purpose is to start and maintain the vendor daemon (ansyslmd). It also refers application checkout requests to the vendor daemon (ansyslmd).
lmgrd must be running on the license server machine to run ANSYS, Inc. products.
Licenses are granted by running processes. Each vendor who has a FlexNet-licensed product on the network has one process, called the vendor daemon. The vendor daemon keeps track of how many licenses are checked out, and who has them. If the vendor daemon terminates for any reason, all users for that product lose their licenses. The ANSYS vendor daemon is ansyslmd.
Client programs, including ansysli_server, communicate with ansyslmd, usually through TCP/IP network communications. The vendor daemon (ansyslmd) is started by lmgrd. The vendor daemon ansyslmd must be running on the license server machine to run ANSYS, Inc. products.
The ANSYS Licensing Interconnect (ansysli_server) is an intermediary process that communicates with the FlexNet component of the license manager to authenticate and process all license requests. In a typical configuration, the ANSYS Licensing Interconnect starts the FlexNet component lmgrd, which then starts ansyslmd.
With the Licensing Interconnect, your license file and license options file are still applicable and in effect. Using an intermediary process allows us to seamlessly integrate our full range of product offerings to continually offer you access to the latest products with minimal disruption to your licensing environment. It also allows us a platform on which to enhance important licensing features.
The Licensing Interconnect must be running on the license server machine to run ANSYS, Inc. products.
Licensing data is stored in a text file called the license file. The license file is created by ANSYS, Inc. and is installed by the license administrator. It contains information about the server machines and vendor daemon, and at least one line of data (called INCREMENT lines) for each licensed product. Each INCREMENT line contains a license key based on the data in that line and other vendor-specific information.
License files usually begin with a SERVER line (or three SERVER lines for redundant triad servers) followed by a VENDOR line, followed by one or more INCREMENT lines. Each INCREMENT line contains a license key based on the data in that line, the hostids specified in the SERVER lines, and other vendor-specific data.
You can modify only these data items in the license file:
System host names on the SERVER line(s)
Port numbers on the SERVER line(s)
Vendor daemon file paths on the VENDOR line(s)
Options file paths on the VENDOR line(s)
Optional port numbers on the VENDOR line(s) (for firewall support only)
Long lines normally use the "\" line-continuation character to break up long lines. A space character must precede the line-continuation character.
Note: Everything else is used to compute the license key and should be entered exactly as supplied. All data in the license file is case sensitive, unless otherwise indicated.
The SERVER line specifies the hostname and hostid of the license server machine and the lmgrd port number. Normally a license file has one SERVER line. Three SERVER lines mean that you are using redundant servers. License administrators do not have the option of deleting SERVER lines from a license file because the hostids from all of the SERVER lines are computed into the license keys on every INCREMENT line.
The format of the SERVER line is:
SERVER host hostid 1055where:
host is the license server machine
host name or IP address; a string returned by the Linux hostname or uname -n command. On Windows systems, ipconfig
/all returns the host name. This can also be an IP address
(nnn.nnn.nnn.nnn format).
hostid is returned by the option of the ANSYS License Management Center.
1055 is the ANSYS default port number for FlexNet TCP. If port 1055 is already in use on your system, you can change this value.
Example:
SERVER enterprise 0122345 1055
Note: If you change the FlexNet port number, then you must also change the FlexNet port number that is specified in the ansyslmd.ini file (see Specify the License Server Machine) or in the ANSYSLMD_LICENSE_FILE environment variable on all client machines to match the port number specified in the SERVER line.
The VENDOR line specifies the vendor daemon's name and path. lmgrd uses this line to start the vendor daemon, and the vendor daemon reads it to find its options file. The format of the VENDOR line is shown below.
VENDOR ansyslmd [vendor_daemon_path] [[options=]options_file_path] [[port=]port]
where:
ansyslmd is the name of the ANSYS vendor daemon.
vendor_daemon_path is the path to
the executable for this daemon. This path is optional. ANSYS, Inc.
does not supply this field because lmgrd will
look for the vendor daemon ansyslmd executable
in the directory where lmgrd is located and all
ANSYS products install both of these daemons into the same directory.
Note: If you do supply this path and the path includes spaces, enclose the entire directory path in double quotes, as in the following example:
VENDOR ansyslmd "C:\Program Files\ANSYS Inc\Shared Files\Licensing
\win64"options_file_path is the full path
to the end-user options file for this daemon. FlexNet does not
require an options file. The options file need not be specified on
this line. As long as the options file ansyslmd.opt is located in the same directory as the license file (the license_files
directory), the vendor daemon will automatically find and use it.
If the directory path includes spaces, enclose the entire directory path in double quotes, as in the following example:
VENDOR ansyslmd options="C:\Program Files\ANSYS Inc\Shared Files\
Licensing\ansyslmd.opt"port is the vendor daemon
port number. Note: This is for firewall support only and is otherwise
not recommended. In the following example, #### would be replaced with the port number you choose:
VENDOR ansyslmd options=/ansys_inc/shared_files/licensing
/ansyslmd.opt port=####An INCREMENT line describes the license to use a product. The syntax of the INCREMENT line is:
INCREMENTfeatureansyslmdfeat_versionexp_date #lic key[VENDOR_STRING="vendor_str"] [ISSUED="..."] [START="..."] [SIGN2="..."]
where:
feature is the name
representing the product/capability being licensed.
ansyslmd is the name of the ANSYS vendor daemon; also found in the VENDOR line. The specified daemon serves this feature.
feat_version is the
latest build date of this feature that is supported by this license.
For paid-up customers, this is usually set to the expiration date
of the maintenance agreement. The value of 9999.9999 is used when
this field is not applicable.
exp_date is the expiration
date of license, e.g., 7-may-2014.
#lic is the number
of concurrent licenses for this feature.
key is the encryption
key for this INCREMENT line.
Additional fields may follow. See the FlexNet License Administration Guide (accessible from the ANSYS License Management Center) for more information. Note that ANSYS, Inc. may not support all options described in the FlexNet License Administration Guide.
VENDOR_STRING Keywords ANSYS, Inc. has created the following VENDOR_STRING keywords:
customer
The customer keyword specifies the customer
number. The format is customer:<, where cust_num>cust_num is the customer's
number. You must not modify this keyword.
The SIGN2 keyword specifies the Tamper Resistant
License (TRL) encryption. The encryption is 60 characters (fifteen
4 character segments separated by spaces).
A sample license file is shown here. This file is for 15 ANSYS Mechanical tasks and 12 ANSYS CFD tasks.
SERVER gagh 690daec6 1055
VENDOR ansyslmd
INCREMENT ansys ansyslmd 9999.9999 30-sep-2013 15 8C59A481BA50 \
VENDOR_STRING=customer:00012345 ISSUED=10-sep-2012 \
START=10-sep-2014 SIGN2=”007B AC4B D3A2 \
E623 DC66 BC38 7B31 CE00 0055 DE8D 0E27 C6FD 6C07 EE27 BBCC"
INCREMENT acfd ansyslmd 9999.9999 30-sep-2013 12 47A354CA1291 \
VENDOR_STRING=customer:00012345 ISSUED=10-sep-2012 \
START=10-sep-2014 SIGN2=”0A03 2D61 0801 \
3B5C DC87 7B08 4AFC F780 0CD9 704E F9C5 2A72 0D23 2F38 64AC""where:
gagh is the hostname of the license server
690daec6 is the hostid
1055 is the FlexNet port number
ansyslmd is the vendor daemon
ansys is the feature representing ANSYS Mechanical and acfd is the feature representing ANSYS CFD.
9999.9999 indicates that the maintenance agreement is not applicable. Otherwise, this is highest supported build date for the product. For Mechanical APDL (ANSYS) only, you can view the build date by running Mechanical APDL (ANSYS) with the -v command option.
30-sep-2013 is the expiration date
15 and 12 are the number of tasks for ANSYS Mechanical and ANSYS CFD, respectively
8C59A481BA50 and 47A354CA1291 are encryption keys for ANSYS Mechanical and ANSYS CFD, respectively
customer:00012345 is the customer number
ISSUED=10-sep-2012 is the date the license was created
START=10-sep-2012 is the start date
SIGN2=<” fifteen 4 character segments” >
is the TRL encryption
If you receive a license file and are not sure if it is an ANSYS, Inc. license file, you can determine if it is by looking at the contents of the license file. If it is an ANSYS, Inc. license file, then:
In the line beginning with the word VENDOR, the next field/item is ansyslmd.
In the line(s) beginning with the word INCREMENT, the third field/item is ansyslmd.
Through use of the FlexNet Common Vendor Daemon technology, license files using the ansoftd vendor daemon are also supported by the ANSYS License Manager.
ANSYS, Inc. supplies some licenses for other applications that use different license managers. These license files are not compatible with the ANSYS License Manager. The applications and how to recognize their license files are explained below. Look for the words shown in the VENDOR, DAEMON, INCREMENT, and FEATURE lines for each application. For these license files, you must use their respective license manager tools.
Table 1.2: Identifying License Files
| Application | VENDOR | DAEMON | INCREMENT | FEATURE |
|---|---|---|---|---|
| ANSYS CFX | CFDS | CFDS | ||
| ANSYS ICEM CFD | ICEM_CFD | ICEM_CFD | ||
| ANSYS Autodyn | AUTODYN | AUTODYN | ||
| Fluent, Polyflow, Icepak | FluentLM | FluentLM | ||
| ANSOFT | ansoftd | ansoftd | ||
| Apache | apacheda | apacheda | ||
| Apache | seqld | seqld |
Application programs are software programs such as Mechanical APDL (ANSYS), CFX, Fluent, HFSS, etc. ANSYS application programs need to be able to communicate with the ANSYS License Manager.
License administration is controlled from specific computers on the network called license server machines. License server machines run the license manager, which controls access to all licenses.
The server machine or machines are designated by you--the end user. You have the option of designating one server or three servers. In a one-server network, if the server machine goes down, the licenses are no longer available for use until the server machine is back in service. In a three-server (redundant triad) network, as long as two of the three machines are still running, the licenses are still available for use.
The master server actually controls the license administration. If a network has only one server machine, then that server machine is automatically the master server. In a three server environment, the order of the SERVER lines in the license file determines which server is the master. The order of the servers must match on all machines in a three server environment. The first is the master, the second is the first backup, etc. If the order of the SERVER lines does not match on the three servers, then the servers will attempt to determine the master server; however, this attempt may not be successful. In a three-server network, if the master server is unavailable, then the first backup acts as the master.
You must make sure the order of the SERVER lines is consistent between redundant servers; otherwise, reconnections may fail.
Before running any ANSYS, Inc. software, you must select which machine(s) will be license servers, and provide the hostid and hostname of those machines to ANSYS, Inc. Use the option of the ANSYS License Management Center to capture the necessary system information and create the text file, which then needs to be forwarded to your ANSYS sales representative.
You need to select the computer systems that will act as server machines before we can supply you with the licenses that are required to activate your licensed product(s). Information about the server machines is used to generate the necessary license key(s).
Consider the following points when deciding which computer(s) will be used as server(s):
All files used in conjunction with the license manager software must be located on a disk that is physically local to the server computer(s).
Computers must have a high-speed, reliable Ethernet connection.
Computers that experience extremely high levels of network traffic or processing lags due to high CPU and/or I/O usage are poor candidates for servers.
Do not use computers that are frequently rebooted as servers.
Do not enable “sleep mode” for the computer you are using as a license server. Client computers are not able to connect with a license server that is in sleep mode.
The license server machine must have a static IP address.
We do not allow the use of wide area networks (WANs) for license servers (with the standard ANSYS contract).
If using a three-server network, we recommend that you choose three machines that are of the same platform type (that is, three Linux, three Windows machines, etc.).
If using a three-server network, we highly recommend that all three server machines be on the same subnet in the same physical location.
If these guidelines are not followed, the ability of the ANSYS License Manager to perform consistently will be compromised.
Caution: Do not change the date on the license server machine. Doing so will prohibit the ANSYS product from running. Restoring the system to its original state prior to the date change may require significant effort.
Throughout this document, we use the term “three-server network” when referring to redundant triad servers. Redundant server setup is a network configuration where multiple machines are designated as license servers. Redundancy can be achieved in two ways:
Any number of license server machines can be running independently. The total number of licenses is split between each license server. For example, if you are licensed for 20 tasks of a certain product, and you have two license server machines, each license server machine will serve ten licenses. In this example, if one of these machines fails, only ten licenses will be available.
Three different machines can be selected to work together in tandem (typically referred to as a redundant triad), where two of the three must be running at all times. These three license server machines work from a single set of licenses. This option is not recommended.
We recommend the first option if your site requires redundancy. Be sure to review Selecting License Server Machines for guidelines and special considerations when choosing license servers. Single license server networks are usually sufficient for most sites.
Note: If you are running redundant servers, you should have the license file (as well as the entire licensing directory) installed locally on each license server. If you do not, you lose all the advantages of having redundant servers, since the file server holding these files becomes a single point of failure.