Professional Documents
Culture Documents
Licensing Guide
9.0 Release
ANSYS, Inc. Southpointe 275 Technology Drive Canonsburg, PA 15317 ansysinfo@ansys.com http://www.ansys.com (T) 724-746-3304 (F) 724-514-9494
Revision History Date May 2003 October 2003 April 2004 November 2004
*The information in this guide applies to all ANSYS, Inc. products (including the ANSYS and ANSYS Workbench Products) released on or after this date, until superceded by a newer version of this guide.
Table of Contents
Preface .................................................................................................................... ix 1. Supported Products ....................................................................................... ix 1. Introduction .................................................................................................... 11 1.1. ANSYS and FLEXlm ................................................................................... 11 1.1.1. The Licensing Process ...................................................................... 12 1.1.2. Compatibility with Other FLEXlm-Licensed Software ......................... 12 1.1.3. Links to FLEXlm ................................................................................ 12 1.2. Communications Requirements ................................................................ 13 1.2.1. Configuring TCP/IP ........................................................................... 13 1.2.1.1. Determining Whether TCP/IP Is Installed on a Microsoft Windows System ............................................................................................... 14 1.2.2. Changing the Default Port Number .................................................. 14 1.3. Explanation of Licensing Terms ................................................................. 14 1.3.1. The License Manager Daemon (lmgrd) ............................................. 15 1.3.2. The Vendor Daemon (ansyslmd) ....................................................... 15 1.3.3. The License File ................................................................................ 15 1.3.4. The Application Programs ................................................................ 16 2. License Servers ................................................................................................ 21 2.1. What Are License Servers? ......................................................................... 21 2.2. Selecting License Servers .......................................................................... 21 2.2.1. Redundant Server Options ............................................................... 22 2.2.2. Registering License Server Information ............................................. 23 3. License Files ..................................................................................................... 31 3.1. Installing License Files ............................................................................... 31 3.2. Specifying the License Server and License Files ......................................... 31 3.2.1. Setting the Path with an Environment Variable ................................. 33 3.2.2. License Files Settings Precedence ..................................................... 34 3.3. License Files Format .................................................................................. 34 3.3.1. SERVER Lines .................................................................................... 34 3.3.2. VENDOR Lines .................................................................................. 35 3.3.3. INCREMENT Lines ............................................................................. 36 3.3.4. Sample License Files ......................................................................... 37 3.3.5. Recognizing an ANSYS License File ................................................... 38 3.4. Product Variable Table .............................................................................. 39 4. The ANSYS License Manager ........................................................................... 41 4.1. License Manager Daemon ......................................................................... 41 4.1.1. Modifying License Manager Startup Options .................................... 41 4.1.2. Starting the License Manager Manually ............................................ 42 4.1.3. Starting the License Manager at System Boot Time ........................... 42
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide 4.1.4. Shutting Down the License Manager ................................................ 44 5. The Licensing Environment ............................................................................. 51 5.1. Designating Server(s) for License Check-out .............................................. 51 5.1.1. Sample Scenario .............................................................................. 52 5.2. Establishing User Privileges ....................................................................... 52 5.2.1. Editing the Licensing Options File ..................................................... 53 5.2.2. Sample Options File ......................................................................... 56 5.3. Other Environment Variable Settings ........................................................ 56 5.4. Creating the lmadmin Group .................................................................... 58 5.4.1. HP AlphaServer (Compaq), HP, SGI, Sun, Linux .................................. 58 5.4.2. IBM RS/6000 ..................................................................................... 58 5.5. Setting Up License Queuing ...................................................................... 59 5.6. Using License Borrowing ......................................................................... 510 5.6.1. Setting up License Borrowing ......................................................... 510 5.6.2. Running the License Borrowing Utility ............................................ 510 6. License Administration ................................................................................... 61 6.1. Using the ANSLIC_ADMIN Utility ............................................................... 61 6.1.1. Register License Server Information .................................................. 62 6.1.2. Display the License Server Hostid ..................................................... 63 6.1.3. Run the License Wizard .................................................................... 63 6.1.4. Install the License File ...................................................................... 63 6.1.5. Start the License Manager ................................................................ 64 6.1.6. Stop the License Manager ................................................................ 64 6.1.7. Reread the License File ..................................................................... 65 6.1.8. Specify the License Server ................................................................ 65 6.1.9. Edit the FLEXlm Options File ............................................................. 65 6.1.10. Modify Startup Options .................................................................. 66 6.1.11. Remove a Client License ................................................................. 66 6.1.12. Run the ANSYS Borrow Utility ......................................................... 67 6.1.13. View Status/Diagnostic Options ...................................................... 67 6.1.13.1. Display the License Status ...................................................... 67 6.1.13.2. Display the Customer Number ............................................... 67 6.1.13.3. View the License File .............................................................. 68 6.1.13.4. View the License Log File ....................................................... 68 6.1.13.5. Gather Diagnostic Information ............................................... 68 6.1.14. Uninstall the License Manager ........................................................ 68 6.2. Using the LMTOOLS Utility ........................................................................ 69 7. Troubleshooting .............................................................................................. 71 7.1. Getting Additional License Debug Information .......................................... 71 7.2. Using the ansys_pid Utility ........................................................................ 73 7.3. Problem Situations ................................................................................... 73
vi
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide 7.3.1. License Manager Will Not Start ......................................................... 73 7.3.2. License Manager Will Not Stop in a Three-Server Environment .......... 75 7.3.3. Unable to Check Out Licenses .......................................................... 75 7.3.4. Jobs Abort When License Manager Goes Down in Three-Server Environment .................................................................................................... 75 7.3.5. Ethernet Address Shows All Zeroes ................................................... 76 7.3.6. Licensing Log File Not Created ......................................................... 76 7.3.7. Queuing Does Not Work ................................................................... 77 7.3.8. The FLEXlm Utility lmcksum May Give Misleading Information .......... 77 7.3.9. The Launcher is Excessively Slow to Start .......................................... 77 7.4. Licensing-Related Launcher Error Messages .............................................. 77 7.5. Licensing Error Messages .......................................................................... 79 7.6. ANSYS License Borrowing Errors .............................................................. 716 7.7. ANSYS License Log File Errors .................................................................. 717 Glossary ............................................................................................................. G21 Index ............................................................................................................. Index1
List of Tables
1.1. Configuring TCP/IP ......................................................................................... 3.1. Product/Feature Names for Licensed Products ................................................ 4.1. License Manager Automatic Startup Instructions ............................................. 7.1. ANS_FLEXLM_DEBUG Output Locations .......................................................... 13 39 43 72
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
vii
viii
Preface
1. Supported Products
This document contains information for running the FLEXlm License Manager with all ANSYS, Inc. products, including ANSYS, ANSYS Workbench, ANSYS ICEM CFD, and ANSYS CFX products. However, some information may pertain only to specific products/licensing levels, such as ANSYS or DesignSpace.
For specific operating system requirements, refer to the installation guide for the product and platform you are running.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Preface
Intended Audience
The ANSYS Licensing Guide is intended for the person responsible for licensing administration of all ANSYS, Inc. products at a site. This person is typically the system administrator.
Product Definitions
This guide applies to all licensed ANSYS, Inc. products, including ANSYS, ANSYS Workbench, ANSYS ICEM CFD, and ANSYS CFX products, unless otherwise noted.
Lengthy user input lines that exceed the width of the page are listed in multiple lines, with the second and subsequent lines indented:
exec_path <drive>:\Program Files\Ansys Inc\ansys90\ac4 \bin\pro\<platform>\ac4pro90.exe
Wild card arguments and variables are italicized. Commands appear in bold face. Note Note paragraphs are introduced by the text Note. A note contains information that supplements the main topic being discussed. Caution: Paragraphs that begin with the word Caution in bold, with the rest of the text in normal type, warn you about actions or situations that potentially may cause problems or unexpected behavior or results in ANSYS, Inc. products.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 1: Supported Products Warning: Paragraphs that begin with the word Warning in bold warn you about actions or situations that can shut down ANSYS, Inc. products, damage files, etc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
xi
xii
Chapter 1: Introduction
1.1. ANSYS and FLEXlm
ANSYS, Inc. uses the FLEXlm (FLEXnet Publisher Licensing Module) license manager for all of its licensed products. FLEXlm, the most popular license manager used in the software industry, is best known for its ability to allow software licenses to be available (or float) anywhere on a network. Floating licensing benefits both users and license administrators. Users can make more efficient use of fewer licenses by sharing them on the network. License administrators can control who uses the licensed application and the machine(s) where the licenses will be available. The format of the traffic between the ANSYS product(s) and the license manager is machine independent, allowing for heterogeneous networks. This means the license server and the computer running an application can be either different hardware platforms or even different operating systems (Windows and UNIX, for example). The license manager, daemons or services, and license utility files are installed during the installation process. A typical installation on a Unix machine allows you to install the product anywhere on the system. The installation then creates a symbolic link from the installation directory to /ansys_inc. All licensing files and utilities are provided in the /ansys_inc/shared_files/licensing subdirectory. If you installed the product elsewhere on your system, replace all references to /ansys_inc in this guide with the name of the installation directory you used. Any reference throughout this manual to the licensing directory on Unix platforms means /ansys_inc/shared_files/licensing. A typical installation on a Windows machine (choosing the default installation directory) installs the products in the product subdirectory in \Program Files\Ansys Inc, located on the same drive as the operating system. The \Shared Files\Licensing subdirectory is also created in this installation directory. If you installed the product in a different directory, replace all references to \Program Files\ANSYS Inc\<product> in this guide with the name of the installation directory you used. However, the licensing directory will still remain in the default location; you cannot change this location. The licensing components are shared across all ANSYS, Inc. products and need to reside in a fixed location.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 1: Introduction Any reference throughout this manual to the licensing directory on Windows platforms means \Program Files\Ansys Inc\Shared Files\Licensing, located on the same drive as the operating system.
For Windows systems, the TCP/IP protocol is included as part of the operating system and is typically installed by default. If you do need to install TCP/IP, remember that it must be bound to a network adapter. On machines that are connected to an internal network, TCP/IP must be bound to a network card such as an Ethernet adapter. The vast majority of systems using TCP/IP will fall into this category. On machines that connect to the Internet or corporate intranet through a modem, TCP/IP can be bound to a dial-up connection.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
13
Chapter 1: Introduction
If TCP/IP is installed, you must determine whether it is bound to a network adapter card or a dial-up connection. A network card or a Dial-Up Adapter will be shown under Connect Using:. Caution: If your computer is connected to a network, it is highly recommended that you contact your Information Technology Department before installing or modifying TCP/IP on your machine.
14
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
These components are explained in more detail in the following sections. Note that the term daemon is used throughout this document. A daemon on Unix systems is the same as a service on Windows systems.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
15
Chapter 1: Introduction
16
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 2: License Servers You need to select the computer systems that will act as servers before we can supply you with the licenses that are required to activate your licensed product(s). Information about the servers 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 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. The license server 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). You cannot use DHCP for license servers. If using a three-server network, we recommend that you choose three machines that are of the same platform type (that is, three HPs, three SGIs, etc.). If using a three-server network, we highly recommend that all three servers be on the same subnet in the same physical location.
If these guidelines are not followed, the ability of the license software 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.
22
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 2.2: Selecting License Servers Any number of license servers 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 servers, each license server will serve ten licenses. In this example, if one of these systems fails, only ten licenses will be available.
We recommend the second option if your site requires redundancy. Be sure to review Section 2.2: Selecting License Servers for guidelines and special considerations when choosing license servers. Single license server networks are usually sufficient for most sites.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
23
24
In general, the license file must exist on every machine designated as a license server. If the license file contains counted (also called "floating") licenses, you have to start the license manager daemon (lmgrd) before you can use the application on Unix systems. On Windows systems, the license manager daemon is installed as a service named ANSYS FLEXlm License Manager. You can use the License Wizard available from the ANSLIC_ADMIN utility to install or update a license file, specify the license server, and start or reread the license file. The wizard will prompt you for the necessary information at each step.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 3: License Files multiple machines, you have these options for making your license available on all the client machines: Choose the Specify the License Server option of the ANSLIC_ADMIN utility to create a file named ansyslmd.ini in the licensing directory. Each server's specification entry in this file must begin with SERVER=. This option is highly recommended. The format of the ansyslmd.ini file created by ANSLIC_ADMIN follow. On a single server:
SERVER=<port>@<host>
The ANSYS default port number is 1055 and the host is the license server hostname. For example, if the license server name is alpha1:
SERVER=1055@alpha1
This specification can also be set to the path and filename of a valid license file:
SERVER=<full path to the license file>
The order of the SERVER lines in the ansyslmd.ini file specifies the order in which the requested license will be granted. Set the ANSYSLMD_LICENSE_FILE environment variable to port@host, where host and port come from the SERVER line in the license file. The ANSYS default port number is 1055. This environment variable can also be set to the path and filename of a valid license file. This option is NOT recommended. Set the LM_LICENSE_FILE environment variable to port@host. This environment variable can also be set to the path and filename of a valid license file. Be aware that setting this environment variable can be disruptive to other software companies' products that use FLEXlm as their license manager. This option is NOT recommended.
The license file path specified in the ANSYSLMD_LICENSE_FILE or the LM_LICENSE_FILE environment variables can be port@host, a directory name, a file, or a list of files separated by colons on UNIX or semi-colons on Windows. If there is a directory name in this list, all files named *.lic in that directory are used. 32
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 3.2: Specifying the License Server and License Files You can only start the license manager on the server machine specified in the license file. 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.
Using the earlier example of a license server named alpha1, the line would look like this:
setenv ANSYSLMD_LICENSE_FILE 1055@alpha1
or
setenv ANSYSLMD_LICENSE_FILE /ansys_inc/shared_files/licensing/license.dat
The second example above would look only in the specified directory on the local machine. In the UNIX Korn and Bourne shells:
# ANSYSLMD_LICENSE_FILE=license_file_path # export ANSYSLMD_LICENSE_FILE
On Windows, use the Control Panel to change the system environment, setting ANSYSLMD_LICENSE_FILE to license_file_path, where license_file_path is the full path to the license file. This can also be a port@host setting, where port and host are the port number and host name from the SERVER line in the license file. The ANSYS default port number is 1055. With lmgrd and lmutil (lmstat, lmdown, etc.), the -c option overrides the setting of the ANSYSLMD_LICENSE_FILE environment variable (UNIX only).
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
33
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.
34
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 3.3: License Files Format do not have the option of deleting SERVER lines from a license file because the hostids from the SERVER lines are computed into the license keys on every INCREMENT line. The format of the SERVER line is:
SERVER host hostid 1055
where: host is the license server host name or IP address; a string returned by the UNIX 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 usually the string returned by the Display the License Server Hostid option of the ANSLIC_ADMIN utility. 1055 is the TCP port number to use. ANSYS' port number is 1055. This can be changed if port 1055 is already in use on your system. Example:
SERVER enterprise 0122345 1055
Note If you change the port number, then you must also change the port number that is specified in the ansyslmd.ini file, or in the ANSYSLMD_LICENSE_FILE or the LM_LICENSE_FILE environment variables to match the port number specified in the SERVER line.
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.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
35
Chapter 3: License Files 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 \Intel"
options_file_ path is the full path to the end-user options file for this daemon. FLEXlm 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 licensing directory), the vendor daemon will automatically find and use it. The Edit the FLEXlm Options File option of the ANSLIC_ADMIN utility will put the options file in the correct directory location. 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=####
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.
36
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
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-2004. #lic is the number of concurrent licenses for this feature. key is the encryption key for this INCREMENT line.
Many optional fields may follow. For example, the BORROW field indicates that borrowing is enabled for that license feature. n is the maximum number of hours that a license can be borrowed. The maximum is 336 hours (two weeks). See the FLEXlm End Users Guide for more information.
where: gagh is the hostname of the license server 690daec6 is the hostid 1055 is the port number ansyslmd is the vendor daemon ansys, dspi, caewbpl3, and deba are the features representing ANSYS Mechanical and ANSYS DesignSpace.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
37
Chapter 3: License Files 9999.9999 indicates that the maintenance agreement is not applicable. Otherwise, this the highest supported build date for the product. For ANSYS only, you can view the build date by running ANSYS with the -v command option. 30-sep-2004 is the expiration date 15 and 12 are the number of tasks for ANSYS Mechanical and ANSYS DesignSpace, respectively 8C59A481BA50, 424290D68B3D, 535301E79C4E, and 646412F80D5F, are encryption keys for ANSYS Mechanical and ANSYS DesignSpace, respectively customer:00012345 is the customer number ISSUED=10-sep-2003 is the date the license was created START=10-sep-2003 is the start date
ANSYS, Inc. supplies some licenses for CFX products that use the CFX license manager. Those CFX license files are not compatible with the ANSYS license manager. You can recognize CFX license files in two ways: In the line beginning with the word DAEMON, the second field/item is CFDS. In the line(s) beginning with the word INCREMENT, the third field/item is CFDS.
Please use the CFX license manager utility to administer CFX licenses. ANSYS, Inc. also supplies some licenses for ICEM CFD products that use the ICEM license manager. Those ICEM license files are not compatible with the ANSYS license manager. You can recognize ICEM license files in two ways: In the line beginning with the word VENDOR, the second field/item is ICEM_CFD. In the line(s) beginning with the word FEATURE, the third field/item is ICEM_CFD.
Please use the ICEM license manager tools to administer ICEM licenses.
38
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
39
310
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
311
ICEM Hexahedral Mesher ANSYS AI*Environment ANSYS ICEM CFD Direct Interface for CATIA V4 ANSYS ICEM CFD Direct Interface for I-DEAS
312
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
313
ANSYS Solver for Unigraphics ANSYS LS-DYNA SMP Drop Test Module for ANSYS LS-DYNA (-DTM) ANSYS Frequency Sweep VT (-FS) LS-DYNA MAT_161 Parallel Performance for ANSYS ( -PP ) Geometry Interface for Autodesk Inventor Geometry Interface for CATIA V4 Geometry Interface for CATIA V5 Geometry Interface for Mechanical Desktop Geometry Interface for Parasolid Geometry Interface for Pro/ENGINEER Geometry Interface for SAT Geometry Interface for SolidEdge Geometry Interface for SolidWorks Geometry Interface for Unigraphics iMan PDM System ANSYS ParaMesh ANSYS ParaMesh University ANSYS ParaMesh Geometry Add-on ANSYS ICEM CFD Basic with Advanced Geometry Support
ANSYS ICEM CFD Basic with Unigraphics Direct Inter- aioutput, aiiges, aiacis, face aipiug, aioutcfd ANSYS ICEM CFD Basic with CATIA V4 Direct Interface aioutput, aiiges, aiacis, aipicat, aioutcfd ANSYS ICEM CFD Basic with Pro/Engineer Direct Inter- aioutput, aiiges, aiacis, face aipipro, aioutcfd ANSYS ICEM CFD Basic with SDRC-IDEAS Direct Inter- aioutput, aiiges, aiacis, face aipiidea, aioutcfd
314
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS ICEM CFD Basic with SolidWorks Direct Inter- aioutput, aiiges, aiacis, aipface isw, aioutcfd ANSYS ICEM CFD Basic with SolidEdge Direct Interface aioutput, aiiges, aiacis, aipise, aioutcfd ANSYS ICEM CFD Hexa ANSYS ICEM CFD Tetra/Prism ANSYS ICEM CFD Quad ANSYS ICEM CFD Global ANSYS ICEM CFD Autohexa ANSYS ICEM CFD Mesh Prototyper ANSYS ICEM CFD Environment for CART3D ANSYS ICEM CFD Cart3D Product ANSYS ICEM CFD Cabin Modeler Add-on ANSYS ICEM CFD Cabin Modeler Stand-alone ANSYS ICEM CFD IC3M Add-on ANSYS ICEM CFD IC3M Stand-alone ANSYS ICEM CFD Comak ANSYS ICEM CFD Visula3 / PV3 ANSYS ICEM CFD OptiMesh aimed, aihexa aimed, aitetra, aiprism, aimed, aiquad aimed, aiglobal aimed, aiautmdl, aiautmsh aiiges, aiacis, aimed, aitetra, aimshprt aivis3, aiiges, aiacis aimed, aimshcrt, aiflowcrt, aiflowcrtp aicabin aimed, aitetra, aiprism, aicabin aiic3m, aiic3msb aimed, aitetra, aihexa, aiic3m, aiic3msb, aimed, aicomak aivis3 aioptmsh
ANSYS ICEM CFD Hexa CAA V5 Based (for CATIA V5) aihexct5, aihexct5e
An * after a feature name indicates that an item is a product variable and can be used on a stand-alone basis to start a product run. Products listed here use the ANSYS license manager. ANSYS, Inc. does supply licenses for ICEM CFD and CFX products not listed above; however, those licenses will use the ICEM or CFX license manager. To determine if the license is for the ANSYS, ICEM, or CFX license manager, see Section 3.3.5: Recognizing an ANSYS License File.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
315
316
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 4: The ANSYS License Manager Warning: The license.log file for each server should be located on a local disk. Writing to an NFS-mounted disk or remote file server creates a situation where the license server(s) may fail. If the remote system containing the license.log file crashes, the license manager would be unable to log license transaction data. This would create a fatal error condition. On Windows systems, run the FLEXlm LMTOOLS utility in the ANSYS FLEXlm License Manager folder to configure the service. See the documentation provided with LMTOOLS for more information.
42
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
HP
Sun, Fujitsu
Once the procedure is in place for starting the license manager automatically at boot time, reboot the system. When the system comes back up, check to see that the license manager is running by typing the appropriate ps command and looking for ansyslmd in the resulting display under the column labeled COMMAND. For SYS V UNIX systems:
ps -ef
Next, check the license.log file in the licensing directory for error messages. This file contains a history of ANSYS product activity across the network when this computer is chosen as the master license server by the licensing software. It will also contain startup messages and possibly error messages.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
43
44
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 5: The Licensing Environment To have your license server preference known each time you log in, set the environment variable ANSYSLMD_LICENSE_FILE (both Windows and Unix systems). On Unix systems, place this environment variable in your login startup file (i.e., .cshrc file).
For more information on using the license options file, please see Section 5.2: Establishing User Privileges.
By using the options file, you can be as secure or as open with licenses as you like. The default location of the options file, ansyslmd.opt, is in the licensing directory. If you have a three-server system, the options file must match exactly on all three servers. If you are using an options file, you must specify the pathname to the file on the VENDOR line in the license file, unless it resides in the same directory as the license file, which is the default when using the ANSLIC_ADMIN utility. On UNIX systems, the VENDOR line would look like this for an options file named my.opt:
VENDOR ansyslmd options=/ansys_inc/shared_files/licensing/my.opt
52
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 5.2: Establishing User Privileges On Windows systems, if the path has spaces in it, you must enclose it in quotes:
VENDOR ansyslmd options="c:\Program Files\Ansys Inc\Shared Files\Licensing\my.opt"
MAX_BORROW_HOURS Changes the maximum period for which a license can be borrowed. The new period must be less than that specified in the license file. If multiple MAX_BORROW_HOURS keywords appear in the options file, only the last one is applied to the license feature.
When creating an options file, you must understand the options file precedence. INCLUDE and EXCLUDE statements can be combined in the same options file and control access to the same features. When doing so, keep in mind the following: If there is only an EXCLUDE list, everyone who is not on the list will be allowed to use the feature.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
53
Chapter 5: The Licensing Environment If there is only an INCLUDE list, only those users on the list will be allowed to use the feature. If neither list exists, everyone is allowed to use the feature. The EXCLUDE list is checked before the INCLUDE list; someone who is on both lists will not be allowed to use the feature. EXCLUDE_BORROW supersedes INCLUDE_BORROW. Anyone not in an INCLUDE_BORROW statement is not allowed to borrow licenses.
Once you create an INCLUDE or EXCLUDE list, everyone else is implicitly "outside" the group. This feature allows you, as an administrator, the ability to control licenses without having to explicitly list each user that you wish to allow or deny access to. In other words, there are two approaches; you can either give most users access and list only the exceptions, or you can severely limit access and list only the those users that have access privileges. The format for these keywords follow:
RESERVE number feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name INCLUDE feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name EXCLUDE feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name GROUP name list_of_users INCLUDEALL {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name EXCLUDEALL {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name HOST_GROUP name host_list BORROW_LOWWATER feature number EXCLUDE_BORROW feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name INCLUDE_BORROW feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name MAX_BORROW_HOURS feature num_hours
Above, number is the number of tasks; feature is the license feature name (see Section 3.4: Product Variable Table for a list of license feature names for all ANSYS products); name is the user's login name or group; list_of_users is a blank-separated list of group member's login names; host_list is a blank-separated list of host names; and 54
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
specified in the license file. On UNIX systems, DISPLAY requires the tty device name, and not the DISPLAY environment variable name. Also, PROJECT refers to the LM_PROJECT environment variable. Note You can make groups arbitrarily large by listing the GROUP more than once; FLEXlm concatenates such entries. You can also specify feature as follows:
feature:name=value
You can specify a feature by any of the following fields, found in the license file INCREMENT lines:
VERSION HOSTID EXPDATE KEY VENDOR_STRING ISSUER NOTICE dist_info user_info asset_info
If your license file has multiple INCREMENT lines of the same feature and any of these fields (such as VENDOR_STRING and VERSION) differ between the INCREMENT lines, and you are reserving licenses for this feature, FLEXlm will reserve the same number of licenses from each INCREMENT line. This can result in more licenses being reserved than expected. Specify the differing field to reserve licenses from a single INCREMENT line. For example, the following license contains two INCREMENT lines that differ only by the version date:
INCREMENT struct ansyslmd 2001.0331 permanent 1 AA1DE4A0E7BB \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2001 START=01-Jan-2001 INCREMENT struct ansyslmd 2001.0430 permanent 1 3D967A3ECF4E \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2001 START=01-Jan-2001
then you will reserve two licenses, one from each INCREMENT line, for user smith. To reserve only one license, create an entry that contains the differing information:
RESERVE 1 struct:VERSION=2001.0430 USER smith
For a complete list of license features, see Section 3.4: Product Variable Table. For more information on the options file, see the FLEXlm End Users Guide.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
55
Chapter 5: The Licensing Environment Note The TIMEOUT and TIMEOUTALL options are not available with ANSYS products.
Note In a three license server environment, the same options file must be placed on all three systems. The options specified will not take effect until the license manager has been shut down and restarted or the license file has been reread.
56
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 5.3: Other Environment Variable Settings ANS_FLEXLM_DEBUG If set, provides licensing debugging information. Possible settings are: 0 or not set: Indicates that no licensing debug information should be displayed. 1: Indicates that basic licensing debug information should be displayed. 2: Indicates that all licensing debug information should be displayed.
You will not want to keep this environment variable set all of the time because it will generate a large quantity of information. For some ANSYS products, this information is sent to the file licdebug.out, which resides in the directory specified by the TEMP environment variable, and is not displayed on the screen. The directory specified by the TEMP environment variable may be hidden on your system. To view the directory and file, click on My Computer. Choose Tools from the menu, and then click on Folder options. Click on the View tab and select Show hidden files and folders. Click OK. ANS_FLEXLM_ENABLE_FLEX_DIAG Enables the use of FLEXLM_DIAGNOSTICS for ANSYS, Inc. products. See Chapter 7, Troubleshooting for more information on using this and the FLEXLM_DIAGNOSTICS environment variable. FLEXLM_DIAGNOSTICS Provides additional levels of debugging information. You should set this environment variable only under the direction of Macrovision or ANSYS technical support. For more information on this environment variable, see the FLEXlm End Users Guide. ANS_FLEXLM_DISABLE_DEFLICPATH Indicates that the default license path should not be searched when determining the licensing path in the ANSYS product: Only ANSYSLMD_LICENSE_FILE environment variable setting is used. Settings in the ansyslmd.ini file and the license file in the licensing directory will NOT be used.
ANS_FLEXLM_HBEAT Identifies the number of seconds between the FLEXlm heartbeats sent to the FLEXlm server from an ANSYS product (Windows systems only). Minimum Value: 30 seconds (values between 0 and 30 are set to 30) Maximum Value: 120 seconds (values above 120 are set to 120) Default Value: 60 seconds
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
57
Chapter 5: The Licensing Environment ANS_FLEXLM_LMSGS If set to a value other than 0 (zero), this environment variable indicates that all FLEXlm messages should be returned in FLEXlm's long format rather than ANSYS, Inc.'s default short. In some cases, this may provide more information to support staff. Long messages are automatically displayed if the ANS_FLEXLM_DEBUG environment variable is set to 1 or 2 (even if the ANS_FLEXLM_LMSGS environment variable is not set). ANS_FLEXLM_EXPWARN_DAYS By default, you will be notified of the upcoming expiration of your license beginning 30 days prior to the expiration date. Use this environment variable to change the number of days to any number between 7 and 90.
Follow the instructions below for your hardware platform to create an lmadmin group.
where nn represents any unique group number and user1, user2, user3, ..., usern represent a list of n users in the group.
58
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
On Windows systems, use the Control Panel to set the ANSWAIT environment variable. The following message will appear in the output if your process is waiting (queued) for an available ANSYS license:
Maximum number of licenses already checked out for feature name. Server host1: Queuing for 1 license(s) of feature name
If the ANSWAIT environment variable is not set, then the ANSYS process will terminate with the following message in the event all ANSYS licenses are checked out. This is the default condition.
Licensed number of users already reached (-4,132)
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
59
510
Section 5.6: Using License Borrowing 3. 4. 5. Specify the return date (defaults to 72 hours or 3 days). Click Borrow. Disconnect from the network. Note that even when you've disconnected from the network, you must still run the products from the same account you used to borrow the licenses. For example, if you use a network account to borrow the licenses, you cannot then run from a local account.
If you keep a license for the full amount of time, there is no need to check the license back in. Your borrowed license will simply expire at the end of the borrow period, and the license will be released into the pool of available licenses. To return a license early: 1. 2. 3. 4. Reconnect to the same license server from which you borrowed the license(s). Launch the license borrowing utility: Start>Programs>ANSYS FLEXlm License Manager>ANSLIC_ADMIN. Select Run the ANSYS Borrow Utility. Select the Return tab. Indicate which license(s) you are returning and click Return. Disconnect from the network.
The license(s) you borrowed will be returned to the pool of available licenses. Note You must return borrowed licenses from the same account you used to borrow the licenses originally. Some multi-feature products include other products and/or add-on features. The utility will automatically check out any such included products or add-on features. If you borrow one of these multi-feature products and then click on the Return tab, you will see the product you selected, as well as any other products and add-ons that it includes. If you return a multi-feature product early, these products and add-on features will also be returned.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
511
512
You do not need system administrator privileges to run the ANSLIC_ADMIN utility; however, you must have system administrator privileges to run certain options. To use the utility, select an action from the list of buttons on the left. The status of your machine appears on the bottom left-hand side of the screen, in the Machine Name status area. The machine can be a client (any machine with no valid license file installed is considered a client) or a license server. If a license server, the status can be running or not running. The status will update automatically when the machine's status changes. On Windows systems, if the machine is a client and you want to convert it to a server, you will need to use the installation media and install the license manager following the instructions in the ANSYS Installation and Configuration Guide for Windows. The right side of the utility usually displays a log of your session activities (the session log). The reporting options will also display information in this area. Use the buttons at the bottom to clear the session log or to write the log out to a file. If you need to contact Technical Support, you will need to send them this log file. For some items, such as Display the License Status, the right-hand window converts to a status window showing the requested information. Use the buttons underneath this status area to return to the session log, to write the status information to the session log, or to write the status information directly to a file. The ANSLIC_ADMIN utility consists of the following options: Register License Server Information Display the License Server Hostid
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Chapter 6: License Administration Run the License Wizard Install the License File Start the License Manager Stop the License Manager Reread the License File Specify the License Server Edit the FLEXlm Options File Modify Startup Options (UNIX only) Remove a Client License Run the ANSYS Borrow Utility (Windows only) View Status/Diagnostic Options -- includes the following options: Display the License Status Display the Customer Number View the License File View the License Log File Gather Diagnostic Information
From the Uninstall menu (UNIX only), you can select Uninstall the License Manager. See Section 6.1.14: Uninstall the License Manager for more details on uninstalling the license manager. From the Help menu, you can select: View the ANSLIC_ADMIN Help View the FLEXlm End Users Guide About
62
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 6.1: Using the ANSLIC_ADMIN Utility company name, your name, e-mail address, etc. This utility also obtains information about your system, such as hostname, hostid, hardware platform, operating system level, and current date. In addition, this utility requires information about the type of license server machine. In the case of a three-server system, you must supply the server information on each server. The utility places the information it gathers into a file named licserver.info. By default, this file is written to the home directory; it will also create it in the licensing directory. You can browse to a directory other than the home directory. You must forward the file, created on each license server, to your ANSYS sales representative. If you are running this utility on a Windows laptop system, you should disconnect from the docking station before running this option so that the laptop's hostid information is used and not the docking station's.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
63
Chapter 6: License Administration 1. 2. 3. Save the license file that you received from your ANSYS sales representative to a temporary file. Select this option from the ANSLIC_ADMIN utility. Browse to the file. If you do not already have a license file, the information from this temporary file will be used to create the license file. If you do have an existing license file, the existing file will be renamed to license.dat.old.
In a three-server setup, you must use this option on each license server. Warning: Do not save license files in Microsoft Word format. If the license manager is running when you add or update a license, you must restart the license manager or reread the license file for the new file to take effect.
64
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 6.1: Using the ANSLIC_ADMIN Utility Note In a three-server environment, you may see a delay in stopping the license manager. Do not press the Stop the License Manager button more than once for the same server.
To delete a server, highlight the server in the list and click Delete Selected Server. Entries in this file tell ANSYS, Inc. products which license server(s) to query to find a valid license. Using this option allows all users at your site to use this setting without having to individually set environment variables (ANSYSLMD_LICENSE_FILE and/or LM_LICENSE_FILE) to find the license file. It also eliminates the need to have a copy of the license file on every system at your site. Set the license server on all systems running an ANSYS, Inc. product. The order that the SERVER lines are listed in the ansyslmd.ini file dictates the order in which the license request is granted. To reorder the entries in the list, highlight a server and use the Move up or Move down buttons.
65
Chapter 6: License Administration dundant systems. The options file allows you, the license administrator, to control various operating parameters of FLEXlm. For more information on using the license options file, see Section 5.2: Establishing User Privileges. Restart the license manager or reread the license file for changes to take effect.
If you are not sure of any of the above items, run the Display the license status option to obtain the correct information. This option allows you to remove a client only from the license server machine on which the license is checked out. A client must be running at least two minutes before you can remove it. If you attempt to remove a client in less than two minutes, you will get an error. The license removal is not immediate.
66
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
When you select one of these options, the data will appear in the log area on the right side of the utility. Display the Customer Number appends the customer number to the session log itself; the other options create their own display in the log area. Each option is explained in the following sections.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
67
68
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 6.2: Using the LMTOOLS Utility 2. 3. 4. In the ANSYS FLEXlm License Manager program folder, click on the FLEXlm LMTOOLS utility. Select the Configure Services tab and highlight ANSYS FLEXlm License Manager. Click on the Remove Service button. Exit the LMTOOLS utility.
On all Windows systems, follow these steps. For more information on performing any of the following tasks, please refer to your Windows system documentation. 1. 2. 3. Delete the \Licensing subdirectory located under \Program Files\ANSYS Inc\Shared Files. Remove the ANSYS FLEXlm License Manager program folder from the Start menu. Remove the ANSYSLIC_DIR environment variable.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
69
610
Chapter 7: Troubleshooting
This chapter lists problems and error messages that you may encounter while setting up licensing. After each situation description or error message is the user action required to correct the problem. For more troubleshooting information, see the FLEXlm End Users Guide.
Set the ANS_FLEXLM_LMSGS environment variable to control whether error messages appear in long or short format. By default, when the ANS_FLEXLM_DEBUG environment variable is NOT set, ANSYS, Inc. displays error messages in short format. Set this environment variable to a value other than 0 (zero) to display the long format. Long messages are automatically displayed when the ANS_FLEXLM_DEBUG environment variable is set, even if ANS_FLEXLM_LMSGS is not set. Set the ANS_FLEXLM_ENABLE_FLEX_DIAG environment variable to 1 to enable the use of FLEXLM_DIAGNOSTICS for ANSYS, Inc. products. Set the FLEXLM_DIAGNOSTICS environment variable to a value of 1, 2, or 3, where 3 provides the most debugging information. You should set this environment variable only under the direction of Macrovision's technical support. For more information on this environment variable, see the FLEXlm End Users Guide.
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 the user did not make any changes to the license file for the server, check the date/time that it was last changed. Get
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
72
Section 7.3: Problem Situations 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 the user put a license key in a license file but is not seeing it even after restarting the license manager, confirm that the correct license file is being used to start the daemon/service. In this case, neither the client application nor the daemon/service is using the changed file. If the license.dat 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 license.dat 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.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
73
Chapter 7: Troubleshooting 2. Verify that TCP/IP is installed and configured correctly. Verify that the IP address is static. See Section 1.2: Communications Requirements for information about configuring TCP/IP. Verify that the hostid has not changed. If the hostid has changed, you must obtain a new license.
3.
In a three-server environment, you could also see the following message when you start the first of the three servers: ***Attempting to start the license manager... Start the License Manager status: The license manager failed to start. You may examine the license log file for more information or possible errors (by clicking the 'View Status/Diagnostic Options' button). Additionally, you can reference the Troubleshooting section in the ANSYS Licensing Guide for more details. NOTE: The currently-installed license file is a three-server license file. With threeserver license files, the license manager will not fully start until at least two of the three license servers are running. This message results when a quorum of servers (2 of the 3) are not yet started. Start the other servers, or verify that they are already started. When at least two of the three servers are started, you will see the status window of this server change to reflect that it is now running. Do NOT attempt to stop the license manager by pressing the Stop the License Manager button. If you verify that at least two servers are started and you still see this message, and the status window does not update to running in a reasonable time, follow the three steps noted above in Section 7.3.1: License Manager Will Not Start. Caution: When you see this message, do NOT press the Start the License Manager button again. Doing so will cause another copy of the lmgrd license manager daemon/service to start without the corresponding ansyslmd vendor daemon/service and will require you to carefully remove the extra ANSYS lmgrd manually.
74
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
2.
7.3.4. Jobs Abort When License Manager Goes Down in ThreeServer Environment
If you are running in a three-server environment and ANSYS program jobs abort when one of the license managers goes down, perform the tests that are listed below. Perform the tests in the order that they are listed. Note If this problem persists after you perform the steps below, you may want to consider switching to a single-server environment. Note When using a three-server environment, we strongly recommend that all three servers be on the same subnet. If this is not the case, you should consider using three machines which are in the same physical location and are on the same subnet.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
75
Chapter 7: Troubleshooting 1. Verify that two of the three license managers are still running. Use the ANSLIC_ADMIN utility (Display the License Status). If the license manager is not already running on all servers, start it on all of them. Check the ansyslmd.ini file in the licensing directory to make sure the server specification is correct. Check to see whether the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE environment variable is set. If it is, verify that the settings are correct. Verify that the same license file exists on all three license servers in the licensing directory. The hostnames of all three servers must appear in these files and in the same order. If the license files are not the same on all three servers, make corrections as necessary and restart the license manager. Verify that the date and time on all license servers are consistent and correct. Make corrections as necessary and restart the license manager. Verify that the hostid has not changed on any of the license servers. If any hostid has changed, you need to obtain and install new licenses on all license servers. Verify that the license manager and utilities are installed locally on each license server. If not, run the installation from the product CD and choose to install the license server only. See the installation manual for your product and platform for more information. Verify that the ansyslmd.opt files match exactly on all three license servers. Check the license.log file for error messages. See the remainder of this chapter for a list of possible errors and their resolutions.
2. 3. 4.
5. 6. 7.
8. 9.
76
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
77
Chapter 7: Troubleshooting ***Unable to retrieve any valid licenses for <simulation environment.> Please see the ANSYS, Inc. Licensing Guide's Troubleshooting section for more information. ***Required <Product> license was not found. Therefore, simulation environment simulation environment will not be available. ***Could not initialize FLEXlm licensing. ***Error: No license path found. ***No licensed products found. ***No products available for this simulation environment. ***Unable to load profile <name> because license <product> is not available. However, simulation environment <simulation environment> was selected. ***License list unavailable. [ANSYS Workbench Products Only] If you see any of the above messages (or any similar licensing error messages), the launcher has encountered an error while trying to find or retrieve a license. Possible causes are the license manager is not running, no licenses were found, or the existing licenses have expired. Also check the license manager log file in the licensing directory. If any of these messages appear, perform the tests that are listed below in the order presented: 1. Use the ANSLIC_ADMIN utility to verify that the license manager is running. Choose Display the License Status. If you are running in a three-server environment, verify that two of the three servers are running. Verify that the license manager is running. If the license manager is not running, start it on the license server machine(s). Check the license.log file on each license server for errors. Run ANSYS from a command prompt to check for additional error messages. (Use the -p command modifier to specify the correct product name. See Section 3.4: Product Variable Table for details.) Example (Windows):
"C:\Program Files\Ansys Inc\V90\ANSYS\bin\intel\ansys90" -p ane3
2.
3.
Check the ANSYS Output window for error messages and additional information about the failure.
78
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 7.5: Licensing Error Messages 4. Use the ping command to test communication between the client machine and the license server. If the ping command does not work, modify the hosts file or the DNS server to contain the correct host names and IP addresses. Verify that the license server and the client machines have unique IP addresses. 5. Verify that the ansyslmd.ini file exists in the licensing directory and that it contains the correct hostname of the license server. If this file does not exist, see Section 5.1: Designating Server(s) for License Check-out of the ANSYS, Inc. Licensing Guide to specify the license server. If the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE variable is used to specify the license server, verify that the hostname of the license server is correct. Verify that the port number used on the license server and the client machine match. Verify that the correct version of the license manager daemons (lmgrd and ansyslmd) is being used. The current version is FLEXlm 9.2.
6. 7.
***Unable to load profile <name> because simulation environment <simulation environment> is not available. If you see this message, the simulation environment specified in the named profile was uninstalled since the profile was created. You will need to specify a new simulation environment and re-specify any launcher settings to continue. To avoid seeing this message in subsequent launcher sessions, update and resave the profile, or reinstall the desired simulation environment.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
79
Chapter 7: Troubleshooting *** All licenses are reserved for others. This error may occur if you have multiple INCREMENT lines for the same feature in the license file, and there are differing fields on each INCREMENT line (such as VENDOR_STRING and the version field), and licenses have been reserved for this feature. In this situation, the number of reserved licenses is reserved out of each INCREMENT, rather than the sum total of both. *** Cannot connect to license server. The license manager is currently not running. Use the ANSLIC_ADMIN utility to start the license manager. Your license must exist on the license server prior to starting the license manager. If you think the license manager should already be running, check the license log file for errors. Some other possible causes for this error include: The wrong hostname is in the license file (machine ID is correct in the file and when the license keys were generated). The license manager could not be started. The wrong license file is on the system (both hostname and machine ID are incorrect and the license keys were created with the wrong ID). The license manager could not be started. The wrong license file is on the system AND the user changed the server line to have the machine's hostid but not the hostname. The license manager could not be started. An incorrect port number was used on the SERVER line(s) in the ansyslmd.ini file or in the setting of the licensing path environment variables (ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE)
710
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 7.5: Licensing Error Messages *** Feature removed during lmreread, or wrong SERVER line hostid Some possible causes of this message include: There is a typographical error in the license file's SERVER line. Typically, the machine ID was mistyped when manually entering the license file on a machine. The user tried to install another machine's license file on a machine and changed the SERVER line in the file to have this machine's hostname but not the machine ID. A laptop with a docking station (with an Ethernet card in it) is removed from the docking station and the license file was made using this card's Ethernet address. The feature was removed during lmreread but the client is reading an old copy of the license file that still contains the removed feature.
*** Clock difference too large between client and server. This message will appear if the date on the machine has changed. The date should never be set ahead or behind the actual date.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
711
Chapter 7: Troubleshooting *** License server does not support this feature. This message can be generated if the feature has expired (on the server), or has not yet started, or the version is greater than the highest supported version, or the license file has been edited while the license server is running and the license file is not reread. Additional causes for this message include: If the user is trying to install another machine's license file on a machine AND changes both the hostname and the machine ID information on the SERVER line to be this machine's information. The INCREMENT lines contained in the license file are still invalid for this machine. If new information for the requested feature was added to the license file but neither an lmreread was issued nor was the license manager restarted. If a laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license was made using this card's Ethernet address, AND the user edited the SERVER line, replacing the Ethernet address with the disk signature of the machine (in an attempt to fix the problem). Such an attempt will not succeed because the INCREMENT lines were created using the docking station's Ethernet address, which in this situation can no longer be seen on this machine. If one or more INCREMENT lines that were made for machine A were installed in machine B's license file and those features were trying to be checked out from machine B.
*** Feature has expired. Your license has expired; please contact your ANSYS sales representative for a renewal.
712
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 7.5: Licensing Error Messages *** No such feature exists. A license does not exist for the requested product. Verify that the ANSYSLMD_LICENSE_FILE and the LM_LICENSE_FILE environment variables and the ansyslmd.ini file are pointing to the correct license server. Verify that you are running the correct product. Use the ANSYS90_PRODUCT environment variable (for ANSYS), the -p command line option, or the Product selection box from the launcher to select the product that you are licensed to run. If you are not licensed to run this product, contact your ANSYS sales representative to obtain a license. If you are licensed to run this product, install the license from the license supplied by ANSYS, Inc. or your ANSYS sales representative using the ANSLIC_ADMIN utility. If you have already created the license, use ANSLIC_ADMIN to reread the license file. You could also see this message if you are trying to use a license manager daemon from a previous release. The license manager daemons (lmgrd and ansyslmd) at this release are FLEXlm 9.2. If you are an ANSYS Workbench customer, you could see these messages if only ANSYS Workbench is installed (no ANSYS installation) but the required Workbench Interface for UNIX license is not found. The No ANSYS product installations found message is a result of the first error and is not a separate situation. To correct this problem, you need a valid Workbench Interface for UNIX license. If you do not have one, contact your ANSYS sales representative. The Workbench Interface for UNIX licenses enable you to run the Workbench user interface and are a no charge product that you can request from your ANSYS sales representative. Because ANSYS licenses are designed to float on a network, you will need to request a quantity of Workbench Interface for UNIX licenses equal to the smaller of the two following scenarios: The number of Sun, HP, or Linux clients that may be running one of these ANSYS Workbench products The number of ANSYS product licenses (DesignSpace, Professional, Structural, Mechanical, Multiphysics, or Prep/Post) that your HP, Sun, or Linux clients have access to run with in the ANSYS Workbench environment.
For example, if you have 20 users sharing 10 ANSYS licenses, and 4 of these users are operating a Sun, HP, or Linux client in the ANSYS Workbench environment, you need only 4 Workbench Interface for UNIX licenses. If all 20 users are operating Sun, HP,
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
713
Chapter 7: Troubleshooting or Linux clients in the ANSYS Workbench environment and sharing 10 ANSYS licenses, then you need 10 Workbench Interface for UNIX licenses. *** License file does not support this version. The build date in the program is newer than the version in the license file. You may not be authorized to run a new release or you may not have installed your new license. If this is the case, install the license using the ANSLIC_ADMIN utility. If you have installed the new license, use ANSLIC_ADMIN to reread the license file. To view the build date in ANSYS, use the -v command line option. *** Licensing files currently installed are more recent than those on the CD. Do you want to load the older licensing files? You will get this message if you install an earlier version of the product after a later version. In almost all cases, you should answer no to preserve the most current copy of the licensing files. If you answer yes, any changes you made to the licensing files will be lost. *** Invalid (inconsistent) license key The license manager daemons for this release are FLEXlm 9.2 (lmgrd and ansyslmd). Verify that you are not using the license manager daemons supplied with a previous release. *** Local checkout filter rejected request. Set the ANS_FLEXLM_DEBUG environment variable to 2 to find the specific cause of this message. *** Cannot find server hostname in network database. This message will appear if one or more of the SERVER computer names do not appear in the client computer's /etc/hosts file (UNIX) or the services file (Windows). On SGI systems, if running under NIS, see the resolver man page for more information.
714
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 7.5: Licensing Error Messages *** The License Manager is currently running and failed to shutdown. There may be some remaining processes that need to be killed manually. If you attempt to uninstall the license manager without first successfully shutting it down, you may inadvertently leave an ansyslmd and an lmgrd process running on your system. These processes will be stopped when you reboot your system. You can stop these processes manually, but use extreme caution, because other products that use the FLEXlm license manager will also have lmgrd processes running. If you do want to stop an lmgrd process, use the ps command to find the ANSYS lmgrd process. ***The ANSYS license manager server is down. Unless a connection is reestablished, ANSYS will exit in nn minutes. This message occurs in a one-server license environment if your license manager has quit running. In a three-license server environment, the ANSYS license manager must be running on at least two of the three license server machines at all times. If two of the license server machines go down, or two of the machines are not running the license manager, this error message will appear in the program output or in a message box. The program will continue to run for nn minutes to allow the license manager to be restarted or to be started on a second machine if using redundant servers. When this error message appears, start the license manager on the other machines designated as license servers. If you get this message and determine that the license manager is still running, and you are running in a one-server environment, then the IP address of the license server machine was changed while the ANSYS product was running (this is usually caused by connecting to or disconnecting from an Internet Service Provider (ISP) that dynamically allocates IP addresses). To correct this situation, you must return the IP address to the same address that the license server had when the ANSYS product was started. If the IP address changes after you start the ANSYS product (either because you connected to or disconnected from your ISP), you can correct the error by restarting the ANSYS product. You should not need to restart the license manager. You can avoid this problem by remaining connected to or disconnected from the ISP the entire time you are running the application.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
715
Chapter 7: Troubleshooting ***FLEXlm version of vendor daemon is too old. The license manager daemons at this release are FLEXlm 9.2 (lmgrd and ansyslmd). Verify that you are not using the license manager daemons supplied with a previous release. ***Cannot read data from license server. The server and the client are having difficulties communicating. This error is usually caused by the network setup or by the network data being different from the data in the license file (for example, the server name, machine ID, port number, or vendor daemon). Confirm that the information on the SERVER line of the license file is the correct information for the server. Confirm that the syntax of the SERVER and VENDOR lines of the license file is correct. Verify that TCP/IP is enabled correctly. Check that the hosts file on the client machine contains the license server. Try using <port>@<host> when specifying the server.
716
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
717
Chapter 7: Troubleshooting ***Invalid license key (inconsistent authentication code) The INCREMENT lines in the license file are not valid for this system (HostID mismatch). This error will also occur if the license file was typed incorrectly. Additional causes for this message include: If a license file created for machine A is being installed on machine B AND the user changed the hostname and the machine ID to machine B's in the SERVER line. If INCREMENT lines created for machine A are appended to an existing license.dat file on machine B. If a laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license was made using this card's Ethernet address, AND the user edited the SERVER line, replacing the Ethernet address with the disk signature of the machine (in an attempt to fix the problem). Such an attempt will not succeed because the INCREMENT lines were created using the docking station's Ethernet address, which in this situation can no longer be seen on this machine. In a three-server license environment, if the license file was created using an incorrect hostid for one of the license servers, this message will appear and will prohibit an ANSYS product from running on any machine. Verify that the hostid in the license file matches the hostid on all three license servers. If it does not, the license file must be created using the correct hostid for all license server machines.
718
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Section 7.7: ANSYS License Log File Errors ***Wrong HostID on SERVER line for license file: <path to license file> License file is not valid for this machine. Possible causes include: There is a typographical error. If the license file was entered manually, the machine ID may have been incorrectly typed in the SERVER line. The user installed a license file created for machine A on machine B and changed the hostname in the SERVER line but did not change the machine ID. The hostid changed on a machine but the hostname stayed the same. A laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license file was made using this card's Ethernet address. A license file was made for a Pentium III CPU ID and the hyphen was not put after the first four characters of the ID (e.g., ABCDEF01 was entered as the ID rather than ABCD-EF01). Ethernet address would be expected. A license file was made using the Windows disk signature but the keyword 'DISK_SERIAL_NUM=' was not put before the ID. Ethernet address would be expected.
*** XXX : Not a valid server hostname, exiting. Valid server hosts are: YYY. The hostname listed in the license.dat (YYY) file does not match the hostname of the system (XXX).
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
719
720
Glossary
ANSLIC_ADMIN A utility that centralizes the various ANSYS product licensing administrative functions. Tasks include, but are not limited to: ANSWAIT starting and stopping the license manager installing licenses displaying license status
An environment variable that will allow you to queue your ANSYS job in the event that all ANSYS licenses are in use. Once a license becomes available and you are next on the queue, your ANSYS job will automatically start. This option is not available for some products.
ANSYSLMD_LICENSE_FILE ansyslmd
An environment variable that may be used to specify the license server from which you want to check out a license. This is the ANSYS, Inc. vendor daemon used to process ANSYS product licensing requests, including issuing and returning licenses. The vendor daemon is started by the license manager daemon (lmgrd) and must be running to perform the aforementioned tasks. File that resides in the licensing directory. It is created by ANSLIC_ADMIN utility options Specify the license server (UNIX and Windows) and Modify license manager startup options (UNIX only). ANSYS Support Distributor. The build date is the year, month, and date the ANSYS product was built. The version field in the license file specifies the latest build date that can be run using that license. It may also appear as 9999.9999 if a maintenance agreement is not applicable.
ansyslmd.ini
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Glossary backup server In a three-server network, the two servers not chosen to be the master are the backup servers. If the master server goes down, the backup server listed next in the license file automatically assumes the role of master. (A backup server is also known as a shadow server.) A borrowable license is a license that you can use temporarily outside of the company facility (such as at home on a laptop). A special license key is required before any license can be borrowed. A client is a machine that requests licenses but is not a license server (i.e., does not have licenses installed on it). A process that typically runs in the background. In the case of ANSYS licensing, the license manager daemon (lmgrd) and the vendor daemon (ansyslmd) are used to process client requests, including issuing and returning licenses. Windows systems refer to this process as a service. The word feature, when used in the descriptions of the licensing utilities, refers to the ANSYS product. See Section 3.4: Product Variable Table for the list of ANSYS products and their corresponding license features. License manager used for all ANSYS products. Anyone on the network can run a licensed ANSYS product, up to the limit specified in the license file. Floating licenses require the license manager daemon (lmgrd) and the vendor daemon (ansyslmd) to be running to count the concurrent usage of the licenses. Getcn is a utility that will display your customer number, which is contained in your license. Getcn may be run from the ANSLIC_ADMIN utility by choosing Display customer number. IA-32 refers to the Intel architecture, 32-bit processor. IA-64 refers to the Intel architecture, 64-bit processor.
borrowable license
client daemon
feature
getcn
IA-32 IA-64
G22
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Glossary license license borrowing See license task. License borrowing allows a user to take a license for use outside of the company facility, such as for an engineer to take a license home on his laptop. A file generated by the Licensing Wizard or the Install/update the license options of the ANSLIC_ADMIN utility or during the installation process. Each licensed product will have an entry in the license file, license.dat, which will reside in the licensing directory. Proper installation of a license file grants access to ANSYS products. The actual full license for the product. A file containing information relevant to licensing activity. This file provides a way of tracking licensing problems that may occur. The licensing log file, license.log, is located in the licensing directory by default. Software used for licensing ANSYS, Inc. products. ANSYS uses the FLEXlm software. A program generally run in the background that is used to process client requests, including issuing and returning licenses. The license manager daemon (lmgrd) starts the vendor daemon (ansyslmd) and is typically started when the system is booted and must be running to perform the aforementioned tasks. Windows systems refer to this process as a service. A file containing license manager-related resource information. This file is created on license server systems, by the ANSLIC_ADMIN utility. By default, the file is named ansyslmd.opt and resides in the licensing directory. You may specify the following information in the resource file: Licenses that are reserved for individuals, groups, or machines Those individuals, groups, or machines that are denied access to licenses G23
license file
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Glossary license server A license server is a system that you have designated to be the administrator of ANSYS product licenses; the licenses are installed on the server machine(s). One or three systems can be used to administer any particular set of ANSYS product licenses. Each concurrent use of an ANSYS product is a license task. Each use of an ANSYS product will take a number of license tasks from the total number available. The default location for the licensing files. On Unix systems, the licensing directory is /ansys_inc/shared_files/licensing. On Windows systems, the licensing directory is \Program Files\Ansys Inc\Shared Files\Licensing, located in the same drive as the operating system. The licensing directory cannot be changed from the default directory on Windows systems. A group of users that you designate to have the ability to perform license administrative tasks that are considered disruptive. A program generally run in the background that is used to process ANSYS product licensing requests, including issuing and returning licenses. The license manager daemon starts the vendor daemon (ansyslmd) and is typically started when the system is booted and must be running to perform the aforementioned tasks. The license manager daemon is lmgrd. LMTOOLS is a Windows-only utility that will perform various license administrator functions, such as listing the users of licensed products. See the LMTOOLS help for more information on using this utility. Lmutil is a utility that will perform various license administrator functions including: rereading the license file, shutting down the license manager, starting the license manager, and listing the users of licensed products. lmutil is the underlying process in several of the ANSLIC_ADMIN options.
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
license task
licensing directory
lmadmin
lmgrd
lmtools
lmutil
G24
Glossary log file master server See license log file. In a three-server network, one of the servers must be the master server. The server listed first in the license file automatically assumes the role of master. The other two license servers are shadow servers (or backup servers). In a one-server network, that server is automatically the master. See license options file. Communication channel by which the license manager communicates with the client. The ANSYS default port number is 1055. Each ANSYS product has been assigned a specific product variable value. Use this product variable value when starting a job to specify which ANSYS product is to be run. The product variable may be set by using the -p command line option, the ANSYS90_PRODUCT environment variable (for ANSYS), or the launcher. See Section 3.4: Product Variable Table for a list of ANSYS products and their associated product variables/feature names. You may designate either one or three systems to be license servers. In a three server network, license manager daemons must be running on the majority (2) of the servers before requests for licenses will be processed. Having multiple systems designated as license servers for an ANSYS product. Redundancy can be achieved either by having three license servers working together in tandem, whereby two of the three must be running at all times, serving from a single set of licenses, or by having any number of license servers running independently, each serving from different license files. See license server. In the ANSLIC_ADMIN utility, all licensing activity is written to an area on the right-hand side of the utility, called the session log area. The session log maintains a
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
product variable
quorum
redundant servers
G25
Glossary running tabulation of all activity (starting or stopping the license manager, rereading the license file, errors, etc.). The session log can also be written to a file that can be used for troubleshooting. service A process on a Windows machine that typically runs in the background. UNIX systems refer to this process as a daemon. In the case of ANSYS licensing, the license manager daemon (lmgrd) and the vendor daemon (ansyslmd) are services used to process client requests, including issuing and returning licenses. In a three-server network, the two servers not chosen to be the master are the shadow servers. If the master server goes down, the shadow server listed next in the license file automatically assumes the role of master. (A shadow server is also known as a backup server.) See license task. The ANSYS vendor daemon is ansyslmd. It is used to process ANSYS licensing requests, including issuing and returning licenses. The vendor daemon is started by the license manager daemon (lmgrd).
shadow server
G26
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index
A
Agreement number, 67 All licenses reserved, 710 ANSLIC_ADMIN utility definition, G21 display customer number, 67 display license server hostid, 63 editing the license options file, 65 install license, 63 register license server information, 62 reread the license file, 65 shutdown the license manager, 64 specifying the license server, 65 start the license manager, 64 uninstall the license manager, 68 update license, 63 using its options (UNIX), 61 view license log file, 68 ANSWAIT environment variable, 59 definition, G21 ANSYS licenses, 21 ansyslmd, 14, 15, 35, 36, 41 definition, G21 ansyslmd.ini definition, G21 ansyslmd.ini file, 31, 34, 51, 65 ansyslmd.opt file, 52, 52, 65 ANSYSLMD_LICENSE_FILE, 15, 31, 33, 33, 56 ANSYSLMD_LICENSE_FILE environment variable definition, G21 ansys_pid utility, 73 ANS_FLEXLM_DEBUG, 56, 71 ANS_FLEXLM_DISABLE_DEFLICPATH, 56 ANS_FLEXLM_DISABLE_ENV, 56
ANS_FLEXLM_ENABLE_FLEX_DIAG, 56, 71 ANS_FLEXLM_EXPWARN_DAYS, 56 ANS_FLEXLM_HBEAT, 56 ANS_FLEXLM_LMSGS, 56, 71 ASD definition, G21 autoexec.bat file, 59
B
Backup server definition, G22 boot_ansflex file, 41 Borrowable license definition, G22 Borrowing licenses, 510, 67 Build date definition, G21
C
Clients definition, G22 Commands (UNIX) PS, 42 .cshrc file, 51 customer number, 67
D
daemon vendor, 35, 36 Daemons definition, G22 license manager (lmgrd), 41 starting at system boot time, 42 starting manually, 42 vendor (ansyslmd), 41 Debugging, 71 Display customer number, 67 Display license server hostid, 63 Display license status, 67
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index
E
Environment variables ANSWAIT, 59 ANSYSLMD_LICENSE_FILE, 15, 31, 56 ANS_FLEXLM_DEBUG, 56, 71 ANS_FLEXLM_DISABLE_DEFLICPATH, 56 ANS_FLEXLM_DISABLE_ENV, 56 ANS_FLEXLM_ENABLE_FLEX_DIAG, 56, 71 ANS_FLEXLM_EXPWARN_DAYS, 56 ANS_FLEXLM_HBEAT, 56 ANS_FLEXLM_LMSGS, 56, 71 FLEXLM_DIAGNOSTICS, 56, 71 LM_LICENSE_FILE, 31, 33, 56 setting the path to the license files, 33 Error messages, 71 launcher , 77 license borrowing, 716 license log file, 717 licensing, 42, 79 Expired license, 712
sample license files, 37 FLEXlm compatibility with other software, 12 definition, G22 FLEXLM_DIAGNOSTICS, 56, 71 floating license definition, G22 Floating licenses, 11, 21, 31 Format of license files, 34 Freeing a license, 51, 66 Functions requiring lmadmin group privileges, 58
G
getcn utility definition, G22
H
hostid, 21, 34, 62 hostname, 21, 34, 62
I
IA-32, G22 IA-64, G22 INCREMENT lines, 36, 39 Installation license, 63 uninstalling the license manager, 68
F
Feature definition, G22 Feature names, 39 Files ansyslmd.ini, 31, 34, 51, 65 ansyslmd.opt, 52, 52, 65 autoexec.bat, 59 boot_ansflex, 41 .cshrc, 51 license, 14, 15 license (license.dat), 31, 31 license files format, 34 license.dat, 33, 34, 63 license.log, 42, 64, 68 viewing, 68 licserver.info, 23, 62 Index2
L
Launcher error messages, 77 License error message: has expired, 712 installing, 63 updating, 63 License administration creating lmadmin group, 51 License borrowing, 510, 67 definition, G23 License borrowing error messages, 716
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index License files, 14, 15, 31 definition, G23 example, 37 format, 34 INCREMENT lines, 36 recognizing, 38 reread, 65 SERVER lines, 34 settings precedence, 34 specifying the location, 31 VENDOR lines, 35 License key definition, G23 License log file (license.log) definition, G23 error messages, 717 viewing, 68 License log file error messages, 717 License manager, 41, 66 compatibility with other software, 12 daemon, 14, 15, G24 defined, 11 definition, G23 modifying startup command options, 41 modifying startup options, 66 shutting down, 44, 64 shutting down with ANSLIC_ADMIN, 64 starting at system boot time, 42 starting manually, 42 starting with ANSLIC_ADMIN, 64 uninstalling, 68 License manager daemon definition, G23 License options file (ansyslmd.opt), 52 editing, 53, 65 sample, 56 License options file (ansyslmd.opt), definition, G23 License queuing, 51, 59 License server error message: is down, 710 License servers definition, 21, G24 designating for license checkout, 51, 51 display hostid, 63 error messages, 42 master, 21 network licensing daemons, 41 redundancy, 22 registering, 23, 62 selecting, 21 shutting down the license manager daemon, 64 specifying, 65 three-server network, 21 License status display, 67 License task definition, G24 License wizard, 63 License.dat file, 14 license.dat file, 15, 31, 31, 33, 34, 63 license.log file, 42, 64 viewing, 68 Licenses customer number, 67 floating, 21, 31 freeing, 51, 66 installing/updating, 63 waiting for available, 59 Licensing debugging, 71 error messages, 71 problem situations, 73 process, 12 sample scenario, 52 selecting servers, 21 setting the path to the license files, 33 tasks, 21 three-server license network, 21 Index3
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index Licensing directory UNIX platforms, 11 Windows platforms, 11 Licensing environment setting up, 51 Licensing error messages, 79 licserver.info file, 23, 62 lmadmin group, 51, 58 lmdown, 58 lmgrd, 14, 15, 41, 42 utility definition, G24 lmhostid, 63 lmremove, 58 lmreread, 58 LMTOOLS, 69 lmutil utility definition, G24 LM_LICENSE_FILE, 31, 56 Log file (see also license log file)
P
Pool of available tasks, 21 Port number, 34 definition, G25 Product list, 39 Product variable definition, G25 PS command, 42
Q
Queuing, 51, 59 Quorum definition, G25
R
Redundant servers definition, G25 Registering license server information, 23, 62 Reread the license file, 65 root login, 61, 68
M
Master server, 21, 42 definition, G25
S
Sample license files, 37 Sample licensing scenario, 52 SERVER lines, 34 Service definition, G26 Session log definition, G25 Shadow server definition, G26 Shutting down the license manager, 44 Specifying the license server, 65 Starting the license manager, 64 Startup options for license manager modifying, 66 superuser login, 61, 68 Symbolic links, 11
N
Network File System licensing failures on, 41 Network licensing network licensing considerations, 21 network licensing daemons, 41 queuing facility, 59 shutting down the license manager, 44 starting license manager at system boot time, 42 starting license manager manually, 42 No license file found for feature error message, 713 No licenses are currently available error message, 79 Index4
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index
T
Tasks, 21 TCP/IP, 12 dial-up connection, 13 testing whether TCP/IP is installed, 14 Three-server network, 21 Troubleshooting ansys_pid utility, 73 getting additional debugging information, 71 license borrowing errors, 716 license log file errors, 717 licensing error messages, 79 problem situations, 73 Troubleshooting ANSYS error messages, 71
U
Unavailable licenses, 79 Uninstalling the license manager, 68 Updating license, 63 User privileges, 51 Using the options file, 52
V
Vendor daemon, 14, 15, 35, 36, 41 vendor daemon definition, G26 VENDOR lines, 35 Viewing license log file, 68
W
WANs, 21 Wide area networks, 21
ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . SAS IP, Inc.
Index5