ANSYS Inc. Licensing Guide
ANSYS Inc. Licensing Guide
ANSYS Inc. Licensing Guide
The information in this guide applies to all ANSYS, Inc. products released on or after this date, until superseded
by a newer version of this guide.
ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature
names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the
United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark
of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property
of their respective owners. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.
ANSYS, Inc. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.
For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, contact ANSYS, Inc.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. iii
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
iv information of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
ANSYS, Inc. uses the FlexNet license manager for all its licensed products. This guide provides you with
the instructions necessary to configure the client-side license manager settings.
For specific operating system requirements, refer to the installation guide for the platform you are
running. For platform support information, see the Platform Support section of the ANSYS Website.
• For ANSYS release 2021 R1 and newer, the Ansys Licensing Interconnect has been replaced with Ansys
Common Licensing (ACL). Ansys Common Licensing creates direct communication from all Ansys
applications to the FlexNet Publisher server.
• If the parent checks out the increment "meba" and the child tries to check out the same increment
"meba" then the net result is there is only one increment "meba" consumed from the license serv-
er/pool.
• If the parent checks out increment "meba" and the child tries to check out the 2 counts of the
same increment "meba" then the net result is there are two tasks of "meba" consumed from the
license server/pool. This is an example of max logic
• If the parent checks out 1 count of the increment "meba" N number of times, then the net result
is there is only increment "meba" consumed from the licensing server/pool.
Parent/Child max across machines/process tree: This process enables the parent child sharing for
the specified license features with child being on a different machine.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. v
Introduction
User Host Display: This process enables applications to share the same listed features across multiple
instance of the applications for a specific user tied to the host/display.
HPC Parametric Sharing: HPC parametric sharing enables applications to use a single solver license
and anshpc_pack or 8 anshpc features for each additional variance. This also allows applications to
share anshpc_pack increments for core checkouts from the solves started as variances of the same
context. For more information on HPC Licensing, see HPC Licensing (p. 17).
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
vi information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: ANSYS Client Settings Utility
This chapter explains how to use the Client Settings Utility to configure connections with both FlexNet
Publisher and Elastic Licensing servers. The Client Settings Utility is installed automatically when the
product is installed; you do not have to take any further steps to run as a client if you have installed a
product.
The order that the SERVER lines are listed in the ansyslmd.ini file dictates the order in which the
license servers are queried when attempting to check out a license.
You are not limited to designating one set of license server machines for your network. You can have
multiple single-server or three-server (redundant triad) licensing systems on your network. In this situation,
you would have certain licenses connected to a set of server machines (one or three) on the network,
and other licenses connected to a different set of server machines (one or three) on the network.
Each server's specification entry in this file will typically begin with SERVER= to specify the server port
numbers.
On a single server:
SERVER=<flexnetport>@<host>
For multiple single servers, each server should have its own SERVER= lines.
SERVER=<flexnetport>@<host1>:<flexnetport>@<host2>:<flexnetport>@<host3>
SERVER=<flexnetport>@<host1>;<flexnetport>@<host2>;<flexnetport>@<host3>
Do not use commas as separators; use colons (:) on Linux machines and semicolons (;) on Windows
machines.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 7
ANSYS Client Settings Utility
The order of the SERVER lines in the ansyslmd.ini file specifies the order in which the requested li-
cense will be granted.
You must use the port@host format; you cannot enter a path or a filename in place of the hostname.
If you want to override the server specification settings in the ansyslmd.ini file, you can do so
by setting the ANSYSLMD_LICENSE_FILE environment variable on individual machines. These
environment variables are useful if you want to temporarily point to a different license server ma-
chine without disrupting the machine's configuration. Use the ANSYSLMD_LICENSE_FILE to specify
the FlexNet port number.
To use the utility, select an action from the list of options on the left.
1.2.1. Defining FlexNet Publisher License Servers
1.2.2. Enabling Elastic Licensing
1.2.3. Setting HPC User Preferences
1.2.4. Setting Borrowed Increments
1.2.5. Gathering Diagnostics
• To add license servers, click the "plus" icon (located below the existing servers) and enter the
communications port and server hostname(s) then click Test to verify the configuration. If the
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
8 information of ANSYS, Inc. and its subsidiaries and affiliates.
Using the ANSYS Client Settings Utility
server is available, a green check mark is displayed to the right of the server information. Click Save
to complete this process.
Note:
To specify redundant triad servers, enter the hostname for each of the three servers in
the spaces available.
• To remove a license server, click the "minus" icon to the left of the appropriate server and then
click Save to complete this process.
• To adjust the order of the servers in your list, click and hold the "double arrow" icon to the left of
the appropriate server and drag the selection to the new postion within your list. Click Save to
complete this process. The order of the servers dictates the order in which they are queried when
attempting to check out a license.
2. Click Import CLS ID and CLS Pin and browse to the directory containing json file supplied by
your elastic licensing administrator.
4. Click Save.
2. Click Save.
If license administrator changes the PIN for the Elastic License Server, client-side users should perform
the following steps.
1. From the Elastic Licensing screen, click the Import CLS ID and CLS Pin button.
2. Browse to the directory containing json file supplied by your elastic licensing administrator.
4. Click Save.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 9
ANSYS Client Settings Utility
Your ansyslmd.ini file is updated, and the ID and PIN are displayed in the ANSYS Client
Settings Utility.
• To change the license priority, click and hold the "double arrow" icon to the left of the appropriate
license and drag the selection to the new position within your list. After you have modified your
list, click Save to retain your changes.
• To disable an HPC license, disable the check box to the left of the appropriate license and then
click Save.
Note:
1. From the Borrow screen, select the license increments you wish to borrow from the Borrowable
Increments drop-down menu.
3. When you have finished selecting your increments and setting the dates for each, click Borrow.
4. When you are finished with the license increments, return to the Borrow screen and click Return
for the appropriate increment or Return All to return all increments.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
10 information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: End-User Configuration
This section contains licensing configuration instructions for ANSYS Workbench and client environment
variable settings used to modify licensing behavior on indivdual machines.
If you are using an ANSYS product other than workbench, you can manually migrate your customized
user licensing preferences by running the ansysli_util.exe file.
To run the ansysli_util.exe, follow the steps for your platform below:
Windows:
Where <Installation Directory> represents the path to the latest ANSYS Product install, open an admin-
istrator command prompt window and issue the following command:
Example:
Linux:
Where <Installation Directory> represents the path to the latest ANSYS Product install, open a command
line window and issue the following command:
Example:
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 11
End-User Configuration
"/ansys_inc/v211/licensingclient/linx64/ansysli_util" -updateuserprefs -
fromrevn 190
Note:
For both the automatic and the manual user licensing preferences migration, ansysli_util
reads the ansyslmd.ini file or the ANSYSLMD_LICENSE_FILE environment variables to determine
the correct license server.
• Share a single license between applications (shared mode). The Share a single license between
applications if possible is enabled by default in ANSYS Workbench.
• Use a separate license for each application (separate mode) by disabling the Share a single li-
cense between applications if possible option in ANSYS Workbench.
ANSYS Workbench allows you to work across multiple instances of the same applications in ANSYS
Workbench while consuming only one of a single type of license per user per session. Using shared
licensing, the active application holds the license, preventing other applications that are sharing
that same license increment/key from using it during that time. For example, trying to do multiple
solves of same type at the same time would be a concurrent event.
Sharing licenses is tied to the license keys the application is using. For example, if the application is
using license key "meba" then you cannot run other application instances or applications sharing the
license key "meba" at the same time.
Single license sharing allows you to progress through your analysis, from specifying engineering data
through building, setup, solving, and finally, reviewing your results, all under the same licenses. The
application holding the license must close or issue a PAUSE command or receive an automatic release
request to release the license and allow another application to use it. Licenses cannot be released while
an application is actively performing a concurrency event (for example, an application cannot release
a license in the middle of a solve operation because the license cannot be released until the solve op-
eration is completed).
Single license sharing applies only to licenses of the same type (for example, ANSYS Mechanical Enter-
prise). Choosing this option does not affect your ability to use licenses of different types simultaneously
(for example, ANSYS Mechanical Enterprise for one task and ANSYS CFD for another).
Because this method is the default, you do not have to take any action to run this way.
License type is primarily by license increment. It is possible to use different license increments
based on the operations performed within a single ANSYS Workbench session. For example, Geo-
metry import, meshing and solving will checkout different license keys based on the capabilities
the application is requesting. For all applications, ANSYS licensing will first look at what other licenses
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
12 information of ANSYS, Inc. and its subsidiaries and affiliates.
ANSYS Workbench Licensing Methods
are opened within this session: if any other licenses being used within this session fulfill the needed
capabilities ANSYS licensing will share an existing license. If not, a new, different license is checked
out.
You cannot run two concurrency events simultaneously (for example, you cannot solve two models of
the same type simultaneously) with one license.
If you are using a license for one application, other applications may still not be able to share that license
if those applications require capabilities not supported by the license. For example, you cannot share
a Mechanical Enterprise license with a Fluent application.
Mechanical:
You can launch the Mechanical application and move between its components (such as Meshing, Setup,
and Solve). The active component will control the license while completing its operations and will release
the license as soon as the operation is completed. For example, when you mesh, the meshing component
will control the license during the meshing operation and then immediately release the license when
the operation is completed. During the meshing operation you cannot use the meshing increment in
any other systems under ANSYS Workbench until the first system mesh is done and the license is released.
The other meshing component, if present in the subsequent systems, will go into read-only mode while
the first system mesh is still in progress.
Note:
Applications in read-only mode because of shared licensing do not refresh their license
status automatically. Once the shared license is released by the editor that had consumed
it, you must trigger Mechanical to query the license status. The most straightforward
way to do this is click outside the Mechanical application window and then click back
in the window to cause the license availability to be rechecked.
Mechanical APDL:
This application consumes a license as soon as you launch it and retains that license until it is finished.
If you launch the Mechanical APDL application interactively, the license is retained until you either close
the application or issue a PAUSE command at the Mechanical APDL command line. PAUSE allows you
to temporarily release the license for another application to use. No other operation other than SAVE
or EXIT is permitted while PAUSED. When the second application has finished and releases the license,
issue an UNPAUSE command from the Mechanical APDL command line to resume its use of the license.
These applications consume a license when launched and retain the license until they receive a request
from another application to release it. For example, when you open CFX-Pre, it will obtain and control
the license. It will retain the license until you close the application or until another application (such as
the CFX solver) requests it.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 13
End-User Configuration
Autodyn and Polyflow also provide a manual PAUSE increment that allows you to interrupt Autodyn
or Polyflow and release the license, temporarily, for another application to use.
Electronics:
Separate Licenses
By using the separate-licenses method, ANSYS Workbench requires a separate license for each
application. By using this method, you can move freely between the many applications that you
might require during an analysis in ANSYS Workbench if you have sufficient licenses. You can leave
each application running and easily move between them at any point during the analysis, even if
one of the applications is actively using the license (such as during a solve process). The disadvantage
to this method is that you could potentially consume many licenses.
To activate the separate licenses method, open ANSYS Workbench and click Tools>Options. From the
Project Management view, disable the Share a single license between applications if possible option.
After disabling this option, close options dialog box and restart ANSYS Workbench.
You have two "ansys" increments. When you open and solve a model in the Mechanical application,
you consume one "ansys" increment. If you link that Mechanical analysis to a Mechanical APDL
system, you would consume a second "ansys" increment when you launch the Mechanical APDL
application, if you have not closed out of the Mechanical application. Neither of these licenses
would then be available for other users until you closed out of one or both applications.
ANSYSLMD_LICENSE_FILE
Can be used to identify a license server machine or license file. If set, this specification is used
before any other license path information. The default port number assigned to ANSYS, Inc. is
1055. Therefore, if your server has the hostname alpha1 and the IP address of 10.3.1.69, you
can identify the server to use as 1055@alpha1 or 1055@10.3.1.69.
ANS_FLEXLM_DISABLE_DEFLICPATH
Indicates that the default license path should not be searched when determining the licensing
path in the ANSYS product. When this environment variable is set:
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
14 information of ANSYS, Inc. and its subsidiaries and affiliates.
Client Environment Variable Settings
• Settings in the ansyslmd.ini file and the license file in the licensing directory will
NOT be used. It will ignore the local server and will ignore the Specify the License
Server setting.
ANSYSLI_TIMEOUT_CONNECT
Used to specify the amount of time that elapses before the client times out if it cannot connect
to the server. Default is 20 seconds. Minimum timeout period you can specify is 5 seconds and
the maximum is 60 seconds. If the client determines that a server is not available in less time,
it will cancel immediately.
ANSYSLI_TIMEOUT_TCP
Used to specify the amount of time that elapses before the client times out if it cannot get a
response from the server. This setting applies only when the license server is running but is
responding slowly (generally because of network issues or server load). Default is 60 seconds.
Minimum timeout period you can specify is 30 seconds and the maximum is 300 seconds.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 15
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
16 information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: HPC Licensing
ANSYS, Inc. offers multiple high performance computing license options, described below.
The HPC license options below cannot be combined with each other in a single solution; for example,
you cannot use both ANSYS HPC and ANSYS HPC Pack licenses in the same analysis solution.
See the applicable product documentation for instructions on configuring and running a distributed
solution.
ANSYS HPC
These physics-neutral licenses can be used to run a simulation across multiple cores and work with
most ANSYS applications. Some ANSYS applications can utilize any combination of CPU and GPU
processors. Other applications are limited to CPU processors only. Contact your ANSYS sales repres-
entative for a complete list of products that can be used with ANSYS HPC.
A number of ANSYS applications allow you to use four cores without using any HPC licenses; ANSYS
HPC licenses add to this base functionality. For example, an ANSYS CFD Enterprise user using twelve
cores will consume only eight ANSYS HPC licenses. Contact your ANSYS sales representative for a
complete list of applications with this option.
You cannot combine ANSYS HPC licenses with any other type of HPC licenses, including HPC Pack
licenses, in the same solution.
These physics-neutral licenses can be used to run a simulation across multiple cores and work with
most ANSYS applications. Contact your ANSYS sales representative for a complete list of applications
that can be used with ANSYS HPC Pack Licenses. n HPC Packs enables 2*4^n parallel cores, so for
instance 1 pack enables 8 cores, 2 packs enable 32 cores, etc. Individual HPC Pack Licenses cannot
be split between multiple users or between multiple analyses.
A number of ANSYS products allow you to use four cores without using any HPC licenses. ANSYS
HPC Pack licenses add to this basic functionality. For example, an ANSYS Mechanical Enterprise user
using twelve cores will consume only one ANSYS HPC Pack license.
You may only borrow one ANSYS HPC Pack license at a time.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 17
HPC Licensing
provides 4 included parallel cores per variation. Additional HPC parallel cores are shared across all
variations, using the same HPC rules. All licenses that are consumed during a concurrent parametric
simulation are held for the duration of the simulation, based on the max count of each license required
for a given variation.
You can use the Ansys Parametric Licensing Calculator (https://ansys.com/parametric) to determine the
number of HPC Workgroup or HPC Pack licenses required.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
18 information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 4: Troubleshooting
This section contains information that may be useful when working with ANSYS customer support.
• View the licdebug file. The licdebug file is generated when you run an ANSYS, Inc. application
and resides in the .ansys subdirectory under the directory specified by the TEMP environment
variable (Windows) or in the $HOME directory (Linux). The licdebug filename will vary depending
on the product but will follow the format licdebug.<product>.211.out. For example:
If a licdebug file already exists and is dated today, the information is appended. If it is dated before
today, the existing file will be renamed with a .old extension and a new file will be started.
– Mechanical: licdebug.MECH.211.out
Note:
The license debug file names include the current release of the application. Because not
all applications are updated with each release, it is possible to have lic\debug file names
that are appended with older release numbers. For example, it is possible to be running
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
information of ANSYS, Inc. and its subsidiaries and affiliates. 19
Troubleshooting
ANSYS Release 16.1 but still have a product license debug log file name include 160 as in
licedbug.POLYFLOW.160.out.
The directory specified by the TEMP environment variable may be hidden on your system. To view
the directory and file, click My Computer. Choose Tools from the menu, and then click Folder options.
Click the View tab and select Show hidden files and folders. Click OK.
If after following these suggestions, the resulting debug information does not make sense, try these
suggestions:
• Confirm that the license manager was restarted or the license file was reread after any changes
were made to the license file. If you did not make any changes to the license file for the server,
check the date/time that it was last changed. Get the relevant path information from the debug
output. Also, confirm that the same path is being used.
• Try restarting the license manager and then attempt to run again. See if the same situation occurs.
• If you installed a new license file but are not seeing it even after restarting the license manager,
confirm that the correct license file is being used to start the license manager. In this case, neither
the client application nor the license manager is using the changed file. Also confirm that if site
or user license preferences were set, the preferences were updated with the new license inform-
ation.
• If the ansyslmd.lic file is at the end of the path and it is a license file that uses the license
manager daemon/service, then confirm that the license manager is started with the same path
as the ansyslmd.lic file's path. The license manager could be looking at one file in the client
application but the license manager daemon/service was started with another file.
Release Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential
20 information of ANSYS, Inc. and its subsidiaries and affiliates.