Installation and Licensing Documentation

Installation and Licensing Documentation
Copyright and Trademark Information

2011 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited. ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademark used
by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property of their respective owners.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFIDENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions of that software license agreement. ANSYS, Inc. is certified to ISO 9001:2008.
U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use, duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc. software license agreement and FAR 12.212 (for non-DOD licenses).
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software and third-party software. If you are unable to access the Legal Notice, please contact ANSYS, Inc. Published in the U.S.A.
ANSYS, Inc. Licensing Guide
ANSYS, Inc. Southpointe 275 Technology Drive Canonsburg, PA 15317 ansysinfo@ansys.com http://www.ansys.com (T) 724-746-3304 (F) 724-514-9494
Release 14.0 November 2011 000289

ANSYS, Inc. is certified to ISO 9001:2008.
Revision Information
The information in this guide applies to all ANSYS, Inc. products released on or after this date, until superceded by a newer version of this guide.

2011 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited. ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property of their respective owners.
Disclaimer Notice

Table of Contents
Preface ....................................................................................................................................................... vii 1. Introduction ............................................................................................................................................ 1 1.1. Explanation of Licensing Terms ......................................................................................................... 2 1.1.1. The FLEXlm License Server Manager (lmgrd) ............................................................................. 2 1.1.2. The Vendor Daemon (ansyslmd) ............................................................................................... 2 1.1.3. ANSYS Licensing Interconnect (ansysli_server) .......................................................................... 3 1.1.4. The License File ........................................................................................................................ 3 1.1.4.1. License Files Format ........................................................................................................ 3 1.1.4.1.1. SERVER Lines .......................................................................................................... 4 1.1.4.1.2. VENDOR Lines ......................................................................................................... 4 1.1.4.1.3. INCREMENT Lines ................................................................................................... 5 1.1.4.1.4. Sample License Files ............................................................................................... 6 1.1.4.1.5. Recognizing an ANSYS, Inc. License File ................................................................... 6 1.1.5. The Application Programs ........................................................................................................ 7 1.1.6. The License Server Machines .................................................................................................... 7 1.1.6.1. Selecting License Server Machines ................................................................................... 7 1.1.6.2. Redundant Server Options ............................................................................................... 8 2. Installing the ANSYS License Manager ................................................................................................. 11 2.1. Communications Requirements ...................................................................................................... 12 2.1.1. Configuring TCP/IP ................................................................................................................. 12 2.1.1.1. Determining Whether TCP/IP Is Installed on a Microsoft Windows System ....................... 12 2.1.2. Changing the Default ANSYS Licensing Interconnect and FLEXlm Port Numbers ...................... 13 2.2. Installing the License Manager ....................................................................................................... 13 2.2.1. License Manager Installation Instructions - Windows ............................................................... 14 2.2.2. License Manager Installation Instructions - UNIX/Linux ........................................................... 15 2.2.3. Silent License Manager Installation Instructions ...................................................................... 16 2.2.4. Advanced Licensing Configuration Options ............................................................................ 17 2.3. Post-Installation Instructions ........................................................................................................... 21 2.3.1. Start the ANSYS License Manager at System Boot Time ........................................................... 21 2.3.2. Configuring the License Server Machine(s) .............................................................................. 22 2.3.3. Modify License Manager Startup Options ............................................................................... 23 2.3.4. Create a Group ....................................................................................................................... 23 2.3.4.1. Defining Group Restrictions for the Licensing Interconnect ............................................ 24 2.3.5. Specify User Privileges ............................................................................................................ 24 2.3.6. Specifying the License Server and License Files ....................................................................... 25 2.3.7. Specifying Firewall Settings .................................................................................................... 25 2.3.8. Setting Up Redundant (Triad) Servers ..................................................................................... 26 3. License Administration Using ANSLIC_ADMIN ..................................................................................... 27 3.1. Using the ANSLIC_ADMIN Utility ..................................................................................................... 27 3.1.1. Register License Server Machine Information .......................................................................... 30 3.1.2. Display the License Server Machine Hostid ............................................................................. 30 3.1.3. Run the License Wizard ........................................................................................................... 31 3.1.4. Install the License File ............................................................................................................. 32 3.1.5. Start the ANSYS, Inc. License Manager ..................................................................................... 32 3.1.6. Stop the ANSYS, Inc. License Manager ..................................................................................... 33 3.1.7. Reread the License Manager Settings ..................................................................................... 34 3.1.8. Specify the License Server Machine ........................................................................................ 34 3.1.8.1. Sample Scenario ............................................................................................................ 36 3.1.9. Remove a Client License ......................................................................................................... 37 3.1.10. Set License Preferences for User .......................................................................................... 37
Release 14.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
iii
ANSYS, Inc. Licensing Guide 3.1.11. Run the ANSYS Borrow Utility ............................................................................................... 38 3.1.11.1. Setting up License Borrowing ...................................................................................... 39 3.1.11.2. Running the Borrowing Utility ...................................................................................... 39 3.1.12. Set Site Preferences .............................................................................................................. 40 3.1.12.1. Edit the FLEXlm Options File ........................................................................................ 41 3.1.12.1.1. The Options File Format ...................................................................................... 41 3.1.12.1.2. Sample Options File ............................................................................................ 44 3.1.12.2. Specify Product Order .................................................................................................. 44 3.1.12.3. Modify Startup Options ............................................................................................... 45 3.1.12.4. Specify License Servers to Cache .................................................................................. 46 3.1.13. View Status/Diagnostic Options ............................................................................................ 46 3.1.13.1. Display the License Status ............................................................................................ 47 3.1.13.2. Display Queued Licenses ............................................................................................. 47 3.1.13.3. Display the Customer Number ..................................................................................... 48 3.1.13.4. View the ANSYS Licensing Interconnect Debug Log File ................................................ 48 3.1.13.5. View the ANSYS FLEXlm License File ............................................................................. 48 3.1.13.6. View the ANSYS FLEXlm Debug Log File ....................................................................... 48 3.1.13.7. Gather Diagnostic Information ..................................................................................... 48 3.1.14. Uninstall the License Manager .............................................................................................. 49 4. End-User Settings .................................................................................................................................. 51 4.1. Client Environment Variable Settings ............................................................................................... 51 4.1.1. License Files Settings Precedence ........................................................................................... 51 4.2. Establishing User Licensing Preferences ........................................................................................... 52 4.2.1. ANSYS Workbench Licensing Methods .................................................................................... 53 4.2.2. HPC Licensing ........................................................................................................................ 55 4.2.2.1. Specifying HPC License Order ........................................................................................ 56 4.3. Setting Up License Queuing ............................................................................................................ 57 4.4. Using License Borrowing ................................................................................................................. 57 5. Troubleshooting .................................................................................................................................... 59 5.1. Getting Additional License Debug Information ................................................................................ 59 5.2. Gathering Diagnostic Information ................................................................................................... 60 5.3. Problem Situations ......................................................................................................................... 60 5.3.1. License Manager Will Not Start ............................................................................................... 60 5.3.2. License Manager Will Not Stop ............................................................................................... 61 5.3.3. License Manager Will Not Stop in a Three-Server Environment ................................................ 61 5.3.4. The Application Does Not Show the Correct License(s) ............................................................ 62 5.3.5. I Do Not See an HPC Product Category in the Specify Product Order or the Set License Preferences for User Dialogs ............................................................................................................................ 62 5.3.6. FLEXlm Log File Shows Unexpected Messages When the License Manager Is Stopped ............. 62 5.3.7. Unable to Check Out Licenses ................................................................................................. 63 5.3.8. Entries in the FLEXlm Options File Are Ignored ........................................................................ 63 5.3.9. Jobs Abort When License Manager Goes Down in Three-Server Environment .......................... 63 5.3.10. Licensing Log File Not Created .............................................................................................. 64 5.3.11. Queuing Does Not Work ....................................................................................................... 64 5.3.12. The FLEXlm Utility lmutil Does Not Shut Down License Manager ........................................... 65 5.3.13.The FLEXlm Utility lmcksum May Give Misleading Information ............................................... 65 5.3.14. The Mechanical APDL Launcher is Excessively Slow to Start ................................................... 65 5.3.15. Mechanical APDL Launcher is Not Using ANSYS140_PRODUCT Environment Variable Correctly .............................................................................................................................................. 65 5.3.16. Cannot Run a Product Listed in the Mechanical APDL Product Launcher ............................... 65 5.3.17. Remove a Client Option Does Not Work ................................................................................ 66
iv
ANSYS, Inc. Licensing Guide 5.3.18. No Licensing Interconnect or FLEXlm Path Available from Display the License Status Option ................................................................................................................................................ 66 5.3.19. Cannot Enter Data in Text Fields ............................................................................................ 66 5.3.20. Cannot See the Entire Run License Wizard Dialog Box ............................................................ 67 5.4. Licensing Installation Process Errors ................................................................................................ 67 5.5. Licensing-Related Mechanical APDL Launcher Error Messages ......................................................... 67 5.6. Licensing Error Messages ................................................................................................................ 68 5.7. ANSYS License Borrowing Errors ...................................................................................................... 73 5.8. FLEXlm License Log File Errors ......................................................................................................... 74 6. Product Variable Table .......................................................................................................................... 77 Glossary ..................................................................................................................................................... 85 Index .......................................................................................................................................................... 91
List of Tables
1.1. Identifying License Files .......................................................................................................................... 7 2.1. Configuring TCP/IP ................................................................................................................................ 12 2.2. License Manager Automatic Startup Instructions ................................................................................... 21 2.3. Removing License Manager Automatic Startup Instructions ................................................................... 22 6.1. Product/Feature Names for Licensed Products ....................................................................................... 77
vi
Preface
This document contains information for running the ANSYS, Inc. License Manager with all ANSYS, Inc. products. However, some information may pertain only to specific products/licensing levels, such as Mechanical APDL (ANSYS) or ANSYS FLUENT.
Important Notice
If you wish to run multiple releases of ANSYS, Inc. software, you MUST install them chronologically (i.e., Release 12.1 followed by Release 14.0). If you install an earlier release after installing Release 14.0, you will encounter licensing issues that may prevent you from running any products/releases. If you need to install an earlier release after you have already installed Release 14.0, you MUST uninstall Release 14.0, then re-install the releases in order.
Supported Hardware Platforms

This document details information about licensing ANSYS, Inc. products on the hardware platforms listed below. Not all products support all platforms listed below. Please refer to the installation documentation for platform specifics, including the platforms on which your specific product runs. The name in parentheses indicates the directory name for each platform (referred to as <platform> throughout this document). Sun SPARC 64 (solus64) Sun Solaris x64 (solx64) Linux 32 (lin32) Linux Itanium 64 (linia64) Linux x64 (linx64) Windows x64 (winx64) Windows 32 (win32)
For specific operating system requirements, refer to the installation guide for the product and platform you are running. For the Solaris x64, Linux 32, and Windows 32 platforms, please see our platform support information at http://www.ansys.com/Support/Platform+Support. (This URL is case-sensitive.)
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. End users of the product may also find this information useful, especially client options.
Applicability
This guide applies to all products licensed with the ANSYS License Manager. See Product Variable Table (p. 77) for a list of products.
vii
Preface
Summary of New and Changed Features

Listed below is a summary of those licensing items that are either new or have been changed since the last release. For a list of all major new and changed features of any product, see the Release Notes document for that product. ANSYS, Inc. has discontinued support for the HP-UX Itanium 64 and the IBM AIX 64 platforms for the ANSYS, Inc. License Manager. At ANSYS Release 14.0, the license manager daemons (lmgrd and ansyslmd) have been upgraded to FLEXlm 11.9.1 (FLEXnet 11.9.1). We strongly recommend that you upgrade to this version of the license manager, regardless of whether you are upgrading to ANSYS Release 14.0. You can now use the -setliclang option to change the language used by ANSLIC_ADMIN and the ANSYS, Inc. Licensing Interconnect log file. This option changes the language for all users running the ANSLIC_ADMIN utility (only the server ANSLIC_ADMIN on Windows). To change the language setting locally for only the current session of the ANSLIC_ADMIN utility, you can launch the utility using the -lang option. To always use this setting locally without having to set this command line option each time, you can set an alias on UNIX/Linux or modify your Start menu shortcut on Windows. Please refer to your operating system documentation for those instructions. For more information on using these language settings, please see the silent license manager installation instructions in the ANSYS, Inc. Installation Guide for your platform and the ANSLIC_ADMIN discussion in the ANSYS, Inc. Licensing Guide. ANSYS HPC Pack licenses are now available for borrowing. Only a single HPC Pack license can be borrowed at one time. CFX now respects licensing preferences. Previously, CFX would always use the lowest capability first. It will now use the licenses specified with User License Preferences. See the ANSYS, Inc. Licensing Guide for more information on setting licensing preferences. The default handling of the FLEXlm options file has changed. The Licensing Interconnect will no longer process the FLEXlm options file by default. If you need to have the Licensing Interconnect process the FLEXlm options file (needed when the FLEXlm options file contains IP addresses), add the following entry to the ansyslmd.ini file on the license server:
ANSYSLI_USE_FLEXOPTS=1
Then, either reread or restart the Licensing Interconnect.
Conventions Used in This Document

Computer prompts and responses and user input are printed using this font:
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin
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\ansys140\ac4 \bin\pro\<platform>\ac4pro140.exe
Wild card arguments and variables are italicized. Commands appear in bold face.
viii
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.
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.
ix
Chapter 1: Introduction
ANSYS, Inc. uses the FLEXlm license manager (also called the FLEXnet License Manager) for all of its licensed products. FLEXlm 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. The license server machine and the computer running an application can be different hardware platforms or even different operating systems (Windows and UNIX/Linux, for example). The actual communication between the ANSYS applications and lmgrd occurs through an intermediary process call the ANSYS Licensing Interconnect. The Licensing Interconnect is nearly transparent; you should not see any noticeable difference in your day-to-day operation of ANSYS products. To get the full set of files necessary to run as a server, you will need to run the license server installation. The general licensing process is explained here; for detailed installation instructions, see Installing the ANSYS License Manager (p. 11). All files necessary to run as a client are automatically installed during the product installation.
The Licensing Process

The licensing process for ANSYS, Inc. products is as follows: 1. 2. 3. 4. 5. 6. Select the license server machine(s). See Selecting License Server Machines (p. 7) for guidelines. Install and configure TCP/IP. See Communications Requirements (p. 12) for information on configuring TCP/IP. Install the software. See Installing the ANSYS License Manager (p. 11), or see the appropriate installation manual for your product and platforms for detailed installation instructions. Register the license server machine(s). See Register License Server Machine Information (p. 30). After you receive your license file, run the License Wizard. See Run the License Wizard (p. 31) for information on installing your license file. Set up the licensing environment. See Post-Installation Instructions (p. 21).
Compatibility with Other FLEXlm-Licensed Software

Because of FLEXlm's popularity, you may have FLEXlm licenses from more than one vendor. The ANSYS License Manager uses FLEXlm 11.9.1. If you do have other FLEXlm-licensed products running FLEXlm 11.9.1 or higher, you can run them in conjunction with ANSYS products with no intervention or special configuration requirements. However, we do not support combining ANSYS, Inc. license files with other license files using one lmgrd license manager.
Links to FLEXlm
For more information on using FLEXlm, please visit the FLEXlm web site at http://www.flexerasoftware.com/. You can refer to the FLEXnet Licensing End User Guide for more detailed information on all FLEXlm features. You can access this document from the ANSLIC_ADMIN Help menu option View the FLEXnet Licensing End User Guide.
1.1. Explanation of Licensing Terms

The main components of our licensing are: The ANSYS, Inc. license manager, including: Licensing Interconnect (ansysli_server) -- Also includes ansysli_monitor, which ensures that the license server is functioning correctly and attempts to correct the situation if the license server is not running or is unresponsive. FLEXlm license server manager (lmgrd) Vendor daemon (ansyslmd)
License files Application program (e.g., Mechanical APDL (ANSYS) or ANSYS FLUENT) License server machines
These components are explained in more detail in the following sections. The ANSYS, Inc. License Manager monitors what products are being run, who is running them, and from what computer system. It grants or denies permission to run products. When an ANSYS product begins, it requests permission to execute from a server. The server checks the pool of available license tasks and grants the request only if the required tasks are available. For each request that is granted, the required license tasks are removed from the pool. As each ANSYS product execution ends, these license tasks are returned to the pool of available tasks.
1.1.1. The FLEXlm License Server Manager (lmgrd)

lmgrd is one of the FLEXlm components of the ANSYS, Inc. License Manager. Its primary purpose is to start and maintain the vendor daemon (ansyslmd). It also refers application checkout requests to the vendor daemon (ansyslmd). lmgrd must be running on the license server machine to run ANSYS, Inc. products.
1.1.2. The Vendor Daemon (ansyslmd)

Licenses are granted by running processes. Each vendor who has a FLEXlm-licensed product on the network has one process, called the vendor daemon. The vendor daemon keeps track of how many licenses are checked out, and who has them. If the vendor daemon terminates for any reason, all users for that product lose their licenses. The ANSYS vendor daemon is ansyslmd. Client programs, including ansysli, communicate with ansyslmd, usually through TCP/IP network communications. The vendor daemon (ansyslmd) is started by lmgrd. The vendor daemon ansyslmd must be running on the license server machine to run ANSYS, Inc. products.
Explanation of Licensing Terms
1.1.3. ANSYS Licensing Interconnect (ansysli_server)

The ANSYS Licensing Interconnect (ansysli_server) is an intermediary process that communicates with the FLEXlm component of the license manager to authenticate and process all license requests. In a typical configuration, the ANSYS Licensing Interconnect starts the FLEXlm component lmgrd, which then starts ansyslmd. We do offer advanced licensing configuration options for sites with well-established procedures; please see Advanced Licensing Configuration Options (p. 17) for more details. With the Licensing Interconnect, your license file and license options file are still applicable and in effect. Using an intermediary process allows us to seamlessly integrate our full range of product offerings to continually offer you access to the latest products with minimal disruption to your licensing environment. It also allows us a platform on which to enhance important licensing features. The Licensing Interconnect must be running on the license server machine to run ANSYS, Inc. products.
1.1.4. The License File

Licensing data is stored in a text file called the license file. The license file is created by ANSYS, Inc. and is installed by the license administrator. It contains information about the server machines and vendor daemon, and at least one line of data (called INCREMENT lines) for each licensed product. Each INCREMENT line contains a license key based on the data in that line, the hostids specified in the SERVER line(s), and other vendor-specific data. The default and recommended location for the ANSYS license file (license.dat) is in the licensing directory. End users can override this location by setting the environment variable ANSYSLMD_LICENSE_FILE to point elsewhere. License files need to reside only on license server machines.
1.1.4.1. License Files Format

License files usually begin with a SERVER line (or three SERVER lines for redundant triad servers) followed by a VENDOR line, followed by one or more INCREMENT lines. You can modify only these data items in the license file: System host names on the SERVER line(s) Port numbers on the SERVER line(s) Vendor daemon file paths on the VENDOR line(s) Options file paths on the VENDOR line(s) Optional port numbers on the VENDOR line(s) (for firewall support only)
Long lines normally use the "\" line-continuation character to break up long lines. A space character must precede the line-continuation character.
Note
Everything else is used to compute the license key and should be entered exactly as supplied. All data in the license file is case sensitive, unless otherwise indicated.
1.1.4.1.1. SERVER Lines

The SERVER line specifies the hostname and hostid of the license server machine and the lmgrd port number. Normally a license file has one SERVER line. Three SERVER lines mean that you are using redundant servers. License administrators do not have the option of deleting SERVER lines from a license file because the hostids from all of the SERVER lines are computed into the license keys on every INCREMENT line. The format of the SERVER line is:
SERVER host hostid 1055
where: host is the license server machine host name or IP address; a string returned by the UNIX/Linux hostname or uname -n command. On Windows systems, ipconfig /all returns the host name. This can also be an IP address (nnn.nnn.nnn.nnn format). hostid is usually the string returned by the Display the License Server Hostid option of the ANSLIC_ADMIN utility. 1055 is the FLEXlm TCP port number to use. ANSYS' default FLEXlm 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 FLEXlm port number, then you must also change the FLEXlm port number that is specified in the ansyslmd.ini file (see Specify the License Server Machine (p. 34)) or in the ANSYSLMD_LICENSE_FILE environment variable on all client machines to match the port number specified in the SERVER line.
1.1.4.1.2. VENDOR Lines

The VENDOR line specifies the vendor daemon's name and path. lmgrd uses this line to start the vendor daemon, and the vendor daemon reads it to find its options file. The format of the VENDOR line is shown below.
VENDOR ansyslmd [vendor_daemon_path] [[options=]options_file_path] [[port=]port]
where: ansyslmd is the name of the ANSYS vendor daemon. vendor_daemon_path is the path to the executable for this daemon. This path is optional. ANSYS, Inc. does not supply this field because lmgrd will look for the vendor daemon ansyslmd executable in the directory where lmgrd is located and all ANSYS products install both of these daemons into the same directory.
Note
If you do supply this path and the path includes spaces, enclose the entire directory path in double quotes, as in the following example:
VENDOR ansyslmd "C:\Program Files\Ansys Inc\Shared Files\Licensing \win32"
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=####
1.1.4.1.3. INCREMENT Lines

An INCREMENT line describes the license to use a product. The syntax of the INCREMENT line is:
INCREMENT feature ansyslmd feat_version exp_date #lic key [VENDOR_STRING="vendor_str"] [ISSUED="..."] [START="..."]
where: feature is the name representing the product/capability being licensed. ansyslmd is the name of the ANSYS vendor daemon; also found in the VENDOR line. The specified daemon serves this feature. feat_version is the latest build date of this feature that is supported by this license. For paid-up customers, this is usually set to the expiration date of the maintenance agreement. The value of 9999.9999 is used when this field is not applicable. exp_date is the expiration date of license, e.g., 7-may-2010. #lic is the number of concurrent licenses for this feature. key is the encryption key for this INCREMENT line. Additional fields may follow. See the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility) for more information. Note that ANSYS, Inc. may not support all options described in the FLEXnet Licensing End User Guide. VENDOR_STRING Keywords timezones
ANSYS, Inc. has created two VENDOR_STRING keywords:
Chapter 1: Introduction customer
The timezones keyword specifies the time zone in which the client needs to be running. The absence of the timezones keyword indicates that a client can run in any time zone. The format is timezones:X[,Y,Z,...], where X is a numeric value from 0-23, beginning with GMT. Values move to the east in one hour increments. For example, 0 represents GMT, and 19 represents EST. Multiple time zones are separated by commas (,): timezones:17,18,19. This keyword cannot be modified by the user. The customer keyword specifies the customer number. The format is customer:<cust_num>, where cust_num is the customer's number. This keyword cannot be modified by the user.
1.1.4.1.4. Sample License Files

A sample license file is shown here. This file is for 15 ANSYS Mechanical tasks and 12 ANSYS CFD tasks.
SERVER gagh 690daec6 1055 VENDOR ansyslmd INCREMENT ansys ansyslmd 9999.9999 30-sep-2011 15 8C59A481BA50 \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2011 \ START=10-sep-2010 INCREMENT acfd ansyslmd 9999.9999 30-sep-2010 12 47A354CA1291 \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2011 \ START=10-sep-2010
where: gagh is the hostname of the license server 690daec6 is the hostid 1055 is the FLEXlm port number ansyslmd is the vendor daemon ansys is the feature representing ANSYS Mechanical and acfd is the feature representing ANSYS CFD. 9999.9999 indicates that the maintenance agreement is not applicable. Otherwise, this the highest supported build date for the product. For Mechanical APDL (ANSYS) only, you can view the build date by running Mechanical APDL (ANSYS) with the -v command option. 30-sep-2011 is the expiration date 15 and 12 are the number of tasks for ANSYS Mechanical and ANSYS CFD, respectively 8C59A481BA50 and 47A354CA1291 are encryption keys for ANSYS Mechanical and ANSYS CFD, respectively customer:00012345 is the customer number ISSUED=10-sep-2010 is the date the license was created START=10-sep-2010 is the start date
1.1.4.1.5. Recognizing an ANSYS, Inc. License File

If you receive a license file and are not sure if it is an ANSYS, Inc. license file, you can determine if it is by looking at the contents of the license file. If it is an ANSYS, Inc. license file, then: In the line beginning with the word VENDOR, the next field/item is ansyslmd. In the line(s) beginning with the word INCREMENT, the third field/item is ansyslmd.
Explanation of Licensing Terms ANSYS, Inc. supplies some licenses for other applications that use different license managers. These license files are not compatible with the ANSYS License Manager. The applications and how to recognize their license files are explained below. Look for the words shown in the VENDOR, DAEMON, INCREMENT, and FEATURE lines for each application. For these license files, you must use their respective license manager tools.
Table 1.1 Identifying License Files

Application ANSYS CFX ANSYS ICEM CFD ANSYS AUTODYN ASAS, AQWA FLUENT,POLYFLOW, Icepak ANSOFT ansoftd ICEM_CFD AUTODYN ASASLM FluentLM FluentLM ansoftd VENDOR DAEMON CFDS INCREMENT CFDS ICEM_CFD AUTODYN ASASLM FEATURE
1.1.5. The Application Programs

Application programs are software programs such as Mechanical APDL (ANSYS), CFX, FLUENT, etc. ANSYS application programs need to be able to communicate with the ANSYS License Manager.
1.1.6. The License Server Machines

License administration is controlled from specific computers on the network called license server machines. License server machines run the license manager, which controls access to all licenses. The server machine or machines are designated by you--the end user. You have the option of designating one server or three servers. In a one-server network, if the server machine goes down, the licenses are no longer available for use until the server machine is back in service. In a three-server (redundant triad) network, as long as two of the three machines are still running, the licenses are still available for use. The master server actually controls the license administration. If a network has only one server machine, then that server machine is automatically the master server. In a three server environment, the order of the SERVER lines in the license file determines which server is the master. The order of the servers must match on all machines in a three server environment. The first is the master, the second is the first backup, etc. If the order of the SERVER lines does not match on the three servers, then the servers will attempt to determine the master server; however, this attempt may not be successful. In a three-server network, if the master server is unavailable, then the first backup acts as the master. You must make sure the order of the SERVER lines is consistent between redundant servers; otherwise, reconnections may fail.
1.1.6.1. Selecting License Server Machines

Before running any ANSYS, Inc. software, you must select which machine(s) will be license servers, and provide the hostid and hostname of those machines to ANSYS, Inc. Use the Register License Server Information option of the ANSLIC_ADMIN utility to capture the necessary system information and create the licserver.info file, which then needs to be forwarded to your ANSYS sales representative. If the ANSYS license manager software is not available for installation on a license server machine, you can download a utility to capture license server machine information from http://www.ansys.com/Support/Licensing/Capture+License+Server+Information.
Chapter 1: Introduction You need to select the computer systems that will act as server machines before we can supply you with the licenses that are required to activate your licensed product(s). Information about the server machines is used to generate the necessary license key(s). Consider the following points when deciding which computer(s) will be used as server(s): All files used in conjunction with the license manager software must be located on a disk that is physically local to the server computer(s). Computers must have a high-speed, reliable Ethernet connection. Computers that experience extremely high levels of network traffic or processing lags due to high CPU and/or I/O usage are poor candidates for servers. Do not use computers that are frequently rebooted as servers. The license server machine must have a static IP address. We do not allow the use of wide area networks (WANs) for license servers (with the standard ANSYS contract). You cannot use DHCP for license server machines. If using a three-server network, we recommend that you choose three machines that are of the same platform type (that is, three Linux, three Windows machines, etc.). If using a three-server network, we highly recommend that all three server machines be on the same subnet in the same physical location.
If these guidelines are not followed, the ability of the ANSYS License Manager to perform consistently will be compromised.
Caution
Do not change the date on the license server machine. Doing so will prohibit the ANSYS product from running. Restoring the system to its original state prior to the date change may require significant effort.
1.1.6.2. Redundant Server Options

Throughout this document, we use the term three-server network when referring to redundant triad servers. Redundant server setup is a network configuration where multiple machines are designated as license servers. Redundancy can be achieved in two ways: Any number of license server machines can be running independently. The total number of licenses is split between each license server. For example, if you are licensed for 20 tasks of a certain product, and you have two license server machines, each license server machine will serve ten licenses. In this example, if one of these machines fails, only ten licenses will be available. Three different machines can be selected to work together in tandem, where two of the three must be running at all times. These three license server machines work from a single set of licenses. This option is not recommended.
We recommend the first option if your site requires redundancy. Be sure to review Selecting License Server Machines (p. 7) for guidelines and special considerations when choosing license servers. Single license server networks are usually sufficient for most sites.
Note
If you are running redundant servers, you should have the license file (as well as the entire licensing directory) installed locally on each license server. If you do not, you lose all the advantages of having redundant servers, since the file server holding these files becomes a single point of failure.
10
Chapter 2: Installing the ANSYS License Manager

The ANSYS, Inc. License Manager installation includes both a server and a client component. You must install the license manager software on your server machine(s) at this release in order to be able to run ANSYS, Inc. products. The updates at this release include the new ANSYS Licensing Interconnect, the latest daemons/services, and the latest ANSLIC_ADMIN updates. If you do not install the license manager at this release, your ANSYS, Inc. products will not run. You will find detailed instructions for installing the license manager on your server machines later in this chapter. References in this chapter to licensing installation refer to installing all necessary licensing components on a machine designated as a license server machine. Once the updated License Manager is installed on your server machine(s) and you have installed the product(s), the client component will run successfully. The client component is installed automatically during a product installation; users running as a client will not need to perform any additional installation steps to successfully run the product(s). UNIX/Linux Server Installation Notes: If you are installing the License Manager on the same machine where the product will be run, use the same top level directory path for both the product installation and the License Manager installation. We strongly recommend that you install the licensing files relative to the product installation directory to avoid manually editing the product run scripts. A typical product installation on a UNIX/Linux machine allows you to install the product anywhere on the system and then creates a symbolic link from the installation directory to /ansys_inc. If you did not set the symbolic link during the product installation, or if you installed the licensing files somewhere other than relative to the installation directory, 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/Linux platforms means /ansys_inc/shared_files/licensing. Windows License Server Installation Notes: The licensing installation on a Windows machine installs all necessary licensing files into the \Program Files\ANSYS Inc\Shared Files directory, located on the same drive as the operating system, regardless of where your product installation resides. You cannot change this location. You must have administrative privileges on your machine to install the licensing files. The license manager components are shared across all ANSYS, Inc. products and need to reside in a fixed location. 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. Windows/UNIX/Linux License Client Installation Notes: The license client files are automatically installed into the \Shared Files\Licensing (Windows) or the /shared_files/licensing (UNIX/Linux) subdirectory of the product installation at the end of the product installation.
11
2.1. Communications Requirements

2.1.1. Configuring TCP/IP
TCP/IP needs to be configured and started for any ANSYS, Inc. product and the license manager to be able to run. You should consult your network administrator for assistance with this configuration. The TCP/IP protocol must be installed on any machine on which you want to run an ANSYS product. TCP/IP is supplied as part of the UNIX/Linux operating system. Table 2.1: Configuring TCP/IP (p. 12) specifies the system utility used to configure TCP/IP on the various hardware platforms. You should consult your network administrator for assistance with this configuration.
Note
Linux systems require an Ethernet card.
Table 2.1 Configuring TCP/IP

Hardware Platform Sun (including x64) Linux (Red Hat Enterprise) (32- and 64-bit) TCP/IP Configuration Utility System Management Console (/usr/sadm/bin/smc ) system-config-network
Linux (SUSE Enterprise) (32- and 64- yast bit) 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.
2.1.1.1. Determining Whether TCP/IP Is Installed on a Microsoft Windows System

To determine if TCP/IP is installed on your system, open the Control Panel. Continue as follows based upon the machine's operating system: Windows XP -- Open Network Connections, highlight Local Area Connection and right-mouse click. Select Properties. Internet Protocol (TCP/IP) should be listed. Windows 7/Vista -- Select Control Panel> Network and Sharing Center. For Local Area Connection, click View Status. Click Properties. Internet Protocol (TCP/IP) should be listed.
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:.
12
Installing the License Manager
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.
2.1.2. Changing the Default ANSYS Licensing Interconnect and FLEXlm Port Numbers
A port number specifies the communications channel by which two or more processes can communicate. ANSYS uses 2325 as the default port number for the ANSYS Licensing Interconnect and 1055 as the default port number for the FLEXlm component of the license manager. ansyslmd also uses a port designated by the operating system, unless one is manually specified in the license file on the VENDOR line. If you encounter a conflict in port numbers, you can change the default by modifying all of the following files: ANSYS Licensing Interconnect Port Number The ANSYS Licensing Interconnect port number is defined in the ansyslmd.ini file. You can change this file by selecting Specify the License Server Machine on the ANSLIC_ADMIN utility. Enter the new port number in the ANSYS Licensing Interconnect Port Number field. The Licensing Interconnect port number may also be specified via theANSYSLI_SERVERS environment variable, if set. FLEXlm Port Number files: To change the default FLEXlm port number, you need to change the following
On the license server machine(s): the port number listed on the SERVER line in the license file (license.dat). On the client machine(s): the port number listed in the ansyslmd.ini file. Use the Specify the License Server Machine option of the ANSLIC_ADMIN utility to change the ansyslmd.ini file. The FLEXlm port number may also be specified via the ANSYSLMD_LICENSE_FILE environment variable, if set.
ansyslmd Port Number The ansyslmd daemon uses a port designated by the operating system, unless one is manually specified in the license file on the VENDOR line. See VENDOR Lines (p. 4) for information on specifying this port number on the VENDOR line. You should need to specify this port number manually only if using a firewall. For information on firewall settings, see Specifying Firewall Settings (p. 25).
2.2. Installing the License Manager

You must have administrator privileges to install the ANSYS, Inc. License Manager on Windows systems. On UNIX/Linux systems, you can install using the -noroot option, but you may encounter permission problems during the installation. To proceed with the installation, the current license manager must be shut down if it's running. The installation process will shut down the license manager; however, you should verify that no users will be affected while you run the installation. The licensing installation process will install all necessary files, including the newest ANSLIC_ADMIN files, as well as set the ANSYSLIC_DIR environment variable in the product run scripts. You cannot perform a platform license server installation (i.e., installing files for a different machine type than you're running on) on Windows systems.
13
Chapter 2: Installing the ANSYS License Manager New licenses for existing customers may not be supplied with the ANSYS Release 14.0 package. They will be supplied when the current licenses expire or when TECS expires. Run the license manager installation on all machines that will act as license servers. If you encounter a problem during the licensing installation process that results in a failure or abort, or if you are concerned that the licensing installation did not complete correctly, try running the Complete Unfinished Licensing Installation Configuration option from the ANSLIC_ADMIN utility's Tools menu.
2.2.1. License Manager Installation Instructions - Windows

Follow the instructions below to install the ANSYS License Manager on Windows systems that will act as license servers. Client licensing is installed automatically when the product is installed; you do not have to take any further steps to run as a client if you have installed a product. 1. Run setup.exe. Select Install ANSYS, Inc. License Manager. If you downloaded only the license manager installation, run setupLM.exe. 2. 3. 4. 5. Select a language. You will be notified that the license manager, if running, will be shut down. Click OK. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. License Manager. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. Click Next to continue. The mount directory (location where the installation is located) is specified. You should accept the default. The installation directory is set to <OS_Drive>\Program Files\ANSYS Inc\Shared Files. You cannot change this directory. Click Next to continue. Select the components you want to install. You can choose to install the ANSYS, Inc. License Manager. The amount of disk space required and the disk space available appear at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. However, if you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully. Click Next to continue. 8. A licensing file date verification summary appears. If no conflicts are found between the installation files and the files already on your machine from a previous installation, the message Date verification complete appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next. A summary of the selected installation data appears. Information shown includes platform, installation directory, and product. Review the information carefully, and if correct, click Next to continue the installation. The ANSYS License Manager is now being installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation.
6.
7.
9.
14
Installing the License Manager 10. The Licensing Server Installation Configuration box appears. As the license manager is configured, progress messages appear in the box. 11. The License Wizard will be launched. This wizard walks you through the process of installing or updating a license file, specifying the license server(s) (which updates the ansyslmd.ini file), and starting the license manager. The wizard will prompt you for the necessary information at each step. During this process, the license manager will be shut down if it is running. Be aware that this can impact any users currently running using the license manager. Click Continue on the License Wizard to begin, and follow the instructions on the screen. If you are not performing a default License Server installation or require more information on Types of License Servers, please refer to Advanced Licensing Configuration Options (p. 17). 12. When the License Wizard is complete, click Finish on the wizard screen and then click Finish again on the Licensing Installation Configuration Log screen. 13. When the license manager installation is complete, click Finish. A new Start Menu item named ANSYS, Inc. License Manager will be created automatically. It will include selections for the ANSLIC_ADMIN server utility, the ANSYS, Inc. Licensing Guide, and the FLEXnet Licensing End User Guide.
Note
Client machines will also include a Client ANSLIC_ADMIN option under the ANSYS Release 14.0 Start Menu item. The client-only version of ANSLIC_ADMIN offers access to a limited number of ANSLIC_ADMIN features, such as user configuration and status/reporting options.
2.2.2. License Manager Installation Instructions - UNIX/Linux

Follow the instructions below to install the ANSYS License Manager on UNIX/Linux systems that will act as license servers. Client licensing is installed automatically when the product is installed; you do not have to take any further steps to run as a client if you have installed a product. 1. Run INSTALL.LM to launch the license manager installation. If you downloaded the license manager installation package, this file will reside in the directory where you untarred the files. If you are running from a DVD, this file will reside in the top level of the DVD. Select a language. You will be notified that the license manager, if running, will be shut down. Click OK. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. License Manager. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. Click Next to continue. The mount directory (location where the installation is located) is specified. You should accept the default. You can also accept the default installation directory or specify an alternate path and directory name where the products are to be installed. We recommend that you also set the symbolic link /ansys_inc to the directory where the ANSYS, Inc. product is installed. The /ansys_inc symbolic link is set by default. The symbolic link option
2. 3. 4. 5.
6.
15
Chapter 2: Installing the ANSYS License Manager is available only if you are installing as root. If you chose to set the symbolic link during the product installation, you should set it here as well. Click Next to continue. 7. Select the components you want to install. You can choose to install the ANSYS, Inc. License Manager. The amount of disk space required and the disk space available appear at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. However, if you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully. Click Next to continue. 8. A licensing file date verification summary appears. If no conflicts are found between the installation files and the files already on your machine from a previous installation, the message No conflicts found appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next. A summary of the selected installation data appears. Information shown includes platform, installation directory, and product. Review the information carefully, and if correct, click Next to continue the installation. The ANSYS License Manager is now being installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation and install the license manager. 10. The Licensing Server Installation Configuration box appears. As the license manager is installed, progress messages appear in the box. 11. The License Wizard will be launched. This wizard walks you through the process of installing or updating a license file, specifying the license server(s) (which updates the ansyslmd.ini file), and starting the license manager. The wizard will prompt you for the necessary information at each step. During this process, the license manager will be shut down if it is running. Be aware that this can impact any users currently running using the license manager. Click Continue on the License Wizard to begin, and follow the instructions on the screen. If you are not performing a default License Server installation or require more information on Types of License Servers, please refer to Advanced Licensing Configuration Options (p. 17). 12. When the License Wizard is complete, click Finish on the wizard screen and then click Finish again on the Licensing Installation Configuration Log screen. 13. When the license manager installation is complete, click Finish.
9.
2.2.3. Silent License Manager Installation Instructions

You can deploy an ANSYS, Inc. License Manager installation in silent mode on both Windows and UNIX/Linux systems. Client licensing is installed automatically when the product is installed; you do not have to take any further steps to run as a client if you have installed a product. To run a silent product installation, including the client licensing, please see Silent Product and License Manager Installation in the ANSYS, Inc. Installation Guide for your platform. To silently install the ANSYS License Manager on Windows systems that will act as license servers, you must run the setupLM.exe with the -silent option:
16
Installing the License Manager

setupLM.exe -silent
To install the ANSYS License Manager on UNIX/Linux systems that will act as license servers, you must run the INSTALL.LM with the -silent option:
INSTALL.LM -silent -install_dir path
The silent license manager installation is valid only for the default Licensing Configuration option Run the ANSYS Licensing Interconnect with FLEXlm. You can use the following arguments when running a silent license manager installation: -silent -install_dir path Initiates a silent installation. Specifies the directory to which the license manager is to be installed (UNIX/Linux only). If you want to install to the default location, you can omit the -install_dir argument.The default location on UNIX/Linux is /ansys_inc if the symbolic link is set; otherwise, it will default to /usr/ansys_inc. For the license manager installation on Windows, it will always be installed to <os drive>:\Program Files\ANSYS Inc\. Specifies the location of the license file to install. If the path is not specified or if the path is the same as the existing license file, the license file will not be installed. For the license file path on Windows, you must enclose the path in quotes if you have spaces in the pathname. Specifies a language to use for the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect log file. Use the language directory name in the language subdirectory of the licensing directory (en-us, fr, de, etc.) as the language value. This flag can be used during a GUI installation as well.
-licfilepath path
-setliclang language
During a silent installation, any messages will be written to the licensing installation log file, install_licconfig.log, located in the installation directory. In rare circumstances with a silent licensing installation, the licensing installation messages may not be written to the install_licconfig.log (for example, if the silent licensing installation aborts); in these cases, you may find error messages in the .ansys_install_temp_licconfig_<user>_<index>.log file, located in %TEMP% on Windows or in /var/tmp on UNIX/Linux.
Caution
A silent license manager installation could shut down the ANSYS, Inc. License Manager, affecting other users who are using that license server machine. If you are running a silent client installation, you can specify license server information as well. -licserverinfo Specifies information to be used by the client for the license server. Valid only in conjunction with a silent product installation (setup.exe or INSTALL). Please see the ANSYS, Inc. Installation Guide for your platform for details on running a silent product installation, including client licensing.
2.2.4. Advanced Licensing Configuration Options

In addition to the default configuration, ANSYS, Inc. offers two advanced licensing configuration options when you run the License Wizard:
17
Chapter 2: Installing the ANSYS License Manager Run the ANSYS Licensing Interconnect without FLEXlm -- Use this option if you want to run a local copy of the ANSYS Licensing Interconnect for better performance, such as if your server machine is in a remote location, or to manage the server load better if your license server machine serves many users. With this option, FLEXlm licenses will be taken from another server machine. Run the ANSYS Licensing Interconnect and FLEXlm independently -- Use this option if you want to manage your FLEXlm licenses independently of the ANSYS, Inc. tools (for example, using Flexera Software's FLEXnet Manager to manage multiple companies' product licenses). This option should be used only by experienced users with well-established licensing procedures. Use this option to run the Licensing Interconnect on additional systems other than your license server; your site must still have the Licensing Interconnect running on the license server machine.
These options are available only for license server machines and are available only with a license manager installation or via the server ANSLIC_ADMIN option Run the License Wizard after a license manager installation has been run on this machine. You can select either of these options by clicking the appropriate button in the Type of License Server field in the License Wizard. You can also set up these types of license servers manually. Instructions for both using the wizard and configuring manually are provided in the following sections. If you have already configured your licensing and are changing to a different configuration option, you must stop and restart the ANSYS, Inc. License Manager for these changes to take effect. Rereading the license manager settings will not be sufficient.
Run the ANSYS Licensing Interconnect without FLEXlm

To use the License Wizard to set up a license server that will run the Licensing Interconnect without FLEXlm, follow the steps below.
Important
When using this advanced option, the license server holding the FLEXlm licenses must also have the Licensing Interconnect installed and running. 1. 2. 3. 4. 5. Select Run the License Wizard from the ANSLIC_ADMIN utility. In the Type of License Server field, select Run the ANSYS Licensing Interconnect without FLEXlm. Click Continue on the message box. Click Continue to begin the configuration process. Click Continue to specify the local machine as the primary Licensing Interconnect. If you have not yet specified license server machines, you will need to specify the server from which you will check out ANSYS, Inc. FLEXlm licenses. If you have already specified license server machines, that specification will be used. If you need to change the server specification, use the Specify the License Server Machine option of ANSLIC_ADMIN after you have completed the wizard. Click Continue. 6. 7. You will now be asked to start or restart the license manager. Click Continue. Click Exit.
You can also configure a machine manually to run the Licensing Interconnect without FLEXlm: 1. 18 Choose Modify Startup Options from the ANSLIC_ADMIN utility.
Installing the License Manager 2. 3. 4. Under FLEXlm Options, select Start ANSYS Licensing Interconnect without FLEXlm and click OK. Choose Specify the License Server Machine from the ANSLIC_ADMIN utility. If you see a message, click OK on the message box. In the Specify the License Server Machine dialog box, add this machine to be the primary Licensing Interconnect and specify the Licensing Interconnect port number but not the FLEXlm port number. If necessary, use the Move up button to move this machine to the beginning of the list of servers. Verify that you also have a machine specified from which you will use FLEXlm licenses. This machine must appear below the primary Licensing Interconnect in the list of servers. If you do not have a machine specified, add it.
5.
Note
For the machine holding the FLEXlm licenses, you must specify both the FLEXlm and the Licensing Interconnect port numbers, even though the Licensing Interconnect running on that machine will only be used as a backup. 6. Start or restart the license manager using the Start the ANSYS, Inc. License Manager option of the ANSLIC_ADMIN utility.
The above procedures configure your local machine to be the primary Licensing Interconnect. If you do not want your machine to be the primary Licensing Interconnect (i.e., your machine is a client machine), but you do want to connect to another machine that is a Licensing Interconnect machine not running FLEXlm, follow the steps below: 1. 2. Choose Specify the License Server Machine from the ANSLIC_ADMIN utility. Click OK on the message box. Add or select the machine that is to be the primary Licensing Interconnect, and use the Move up button to move that machine to the beginning of the list of servers. If you are adding the machine, specify only the Licensing Interconnect port number. If the machine is already listed and includes a FLEXlm port number, you will need to select Edit Selected Server Machine to remove the FLEXlm port number. Add or verify the machine from which you will use FLEXlm licenses. This machine must appear below the primary Licensing Interconnect in the list of servers.
3.
Note
For the machine holding the FLEXlm licenses, you must specify both the FLEXlm and the Licensing Interconnect port numbers, even though the Licensing Interconnect running on that machine will only be used as a backup.
Run the ANSYS Licensing Interconnect and FLEXlm independently

Use this option if you want to manage your FLEXlm licenses on a server machine independently of the ANSYS, Inc. tools (for example, using Flexera Software's FLEXnet Manager to manage multiple companies' product licenses). This option should be used only by experienced users with well-established licensing procedures. To use the License Wizard to set up a license server that will run the Licensing Interconnect independently of FLEXlm, follow the steps below. Running these processes separately requires caching the license file, meaning that you specify the location of an existing license file that contains FLEXlm
19
Chapter 2: Installing the ANSYS License Manager licenses for ANSYS, Inc. products. Because the ANSLIC_ADMIN will no longer be managing FLEXlm, you will need to use your license management tools (such as FLEXNet Manager) to start/restart FLEXlm or to reread the license file if you make changes to the license file.
Important
If you make changes to the license file, in addition to rereading the license file in FLEXlm (using your license management tools), you must also recache the license file in the Licensing Interconnect by restarting the Licensing Interconnect or by using the Reread the License Manager Settings option of ANSLIC_ADMIN. To use the License Wizard to set up a license server that will run the Licensing Interconnect and FLEXlm independently, follow the steps below: 1. 2. 3. 4. Select Run the License Wizard from the ANSLIC_ADMIN utility. In the Type of License Server field, select Run the ANSYS Licensing Interconnect and FLEXlm independently. Click Continue on the message box. Click Continue to begin the configuration process. Specify the location of an existing license file that contains FLEXlm licenses for ANSYS, Inc. products. Note that the license file will not be installed, (i.e., moved into the default ANSYS license file location). Click Continue. Specify your local machine as the license server machine. Click Continue. 6. 7. You will now be asked to start or restart the license manager. Click Continue. Click Exit.
5.
Note
Starting or restarting the license manager using this procedure will start ONLY the Licensing Interconnect. You must start or restart FLEXlm using whatever license management tool(s) you will be using to manage FLEXlm (such as FLEXNet Manager or LMTOOLS). You can also configure your licensing manually to run the Licensing Interconnect independently of FLEXlm: 1. 2. 3. 4. 5. Choose Modify Startup Options from the ANSLIC_ADMIN utility. Under FLEXlm Options, select Start ANSYS Licensing Interconnect without FLEXlm. Select Cache FLEXlm Licenses. Verify the license path shown in the License File Path field and correct it if necessary. Click OK. If you wish to use ANSYS licenses from this machine when running ANSYS products on it, choose Specify the License Server Machine from the ANSLIC_ADMIN utility. If this machine is not in the list of servers, add it. Specify both the Licensing Interconnect and FLEXlm port numbers. Start or restart the license manager using the Start the ANSYS, Inc. License Manager option of the ANSLIC_ADMIN utility. This step will start (or restart) only the Licensing Interconnect component of the license manager.
6.
20
Post-Installation Instructions 7. Use your license management tools (such as FLEXNet Manager) to start FLEXlm if it is not already started.
2.3. Post-Installation Instructions

After you have installed the ANSYS, Inc. License Manager, you may want to complete some post-installation steps in order to optimize the performance of the ANSYS, Inc. License Manager at your site. We recommend that you set your license manager to boot at system startup. Other optional post-installation tasks are included here. You will only need to configure your license server machine and configure your client machines if those steps were not completed during the product or license server installation processes.
2.3.1. Start the ANSYS License Manager at System Boot Time

You can set the license manager to start automatically at system boot time. This task is optional but is recommended and should be done regardless of which type of license server configuration you use. Table 2.2: License Manager Automatic Startup Instructions (p. 21) details the steps for each UNIX/Linux hardware platform that must be performed on each license server to start the license manager automatically when the system is rebooted. You should substitute your platform name (see Supported Hardware Platforms (p. vii)) wherever you see <platform>. The instructions below include steps to remove any existing boot_ansflex; if you have already removed the boot_ansflex, you can safely skip that step. On Windows systems, the license manager is set to start up automatically at system reboot.
Note
The procedure described in this section starts the license manager at boot time as root. It is not essential that the license manager be started by the root user; it may be run by a nonprivileged user, depending on your preference. If you do not want the license manager to be started by root, see the FLEXnet Licensing End User Guide for an example of starting the license manager as a non-root user at boot time.
Table 2.2 License Manager Automatic Startup Instructions

Platform Sun Instructions Remove existing license manager startup information: 1. Locate all instances of the boot_ansflex script:
find /etc -name "*ansflex" -print
2.
Remove each file, one at a time using rm.
Issue the new license manager startup instructions:

cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d chmod 555 /etc/init.d/init_ansysli ln -s /etc/init.d/init_ansysli /etc/rc0.d/K03init_ansysli ln -s /etc/init.d/init_ansysli /etc/rc2.d/S97init_ansysli
Linux: Red Hat
Remove existing license manager startup information. Edit the file /etc/rc.d/rc.local and delete the ANSYS boot_ansflex lines. Issue the new license manager startup instructions:
21
Chapter 2: Installing the ANSYS License Manager Platform Instructions

cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d chmod 555 /etc/init.d/init_ansysli chkconfig --add init_ansysli chkconfig init_ansysli on
Linux: SUSE
Remove existing license manager startup information. Edit the file /etc/rc.d/boot.local and delete the ANSYS boot_ansflex lines. Issue the new license manager startup instructions:
cp /ansys_inc/shared_files/licensing/init_ansysli /etc/init.d chmod 555 /etc/init.d/init_ansysli chkconfig --add init_ansysli chkconfig init_ansysli on
Once the procedure is in place for starting the license manager automatically at boot time, reboot the system to verify that the automatic boot procedure is working correctly. 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 and ansysli_server in the resulting display under the column labeled COMMAND. For example:
ps -ef|grep ansysli; ps -ef|grep ansyslmd
Next, check the license.log and the ansysli_server.log files 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 start-up messages and possibly error messages.
Removing the Automatic Startup Information

If you remove the license manager server installation from a machine and need to remove this capability, follow the instructions below.
Table 2.3 Removing License Manager Automatic Startup Instructions

Platform Sun Instructions Issue the following commands:
/etc/init.d/init_ansysli stop rm /etc/init.d/init_ansysli rm /etc/rc0.d/K03init_ansysli rm /etc/rc2.d/S97init_ansysli
Linux
Issue the following commands:

/etc/init.d/init_ansysli stop chkconfig --del init_ansysli rm /etc/init.d/init_ansysli
2.3.2. Configuring the License Server Machine(s)

If you did not complete the configuration tasks when you installed the license manager on your license server machines, you should complete the steps below to register your license server information and then run the license wizard to complete the configuration. 22
Post-Installation Instructions 1. Register your license server information. Run the Register License Server Information option of the ANSLIC_ADMIN utility if you do not have a license file. This option creates a file named licserver.info in the home and licensing directory. The content of this file is generated by prompting you for information about your company and you (the person running the utility). This is important so that we know to which of our customers this information belongs and to whom we may speak if we have questions about the data. The option also pulls necessary information from your license server (such as computer type, operating system level, and hostid) and places it in the file. Create this file on each system that will be a license server. Return the licserver.info file(s) to your ANSYS sales representative so that licenses can be supplied to you. 2. Run the license wizard. This wizard walks you through the process of installing or updating a license file, specifying the license server(s) (which updates the ansyslmd.ini file), and starting the license manager or rereading the license file. The wizard will prompt you for the necessary information at each step. The license file will be named license.dat and will be created in the licensing directory. You should use this option when you receive a new license file as it will walk you through the necessary steps to activate the new license. If you are running in a three-server environment, the license file must reside on all three servers and must match on all three servers. Therefore, run the license wizard on all three servers, installing the same license file on each machine.
2.3.3. Modify License Manager Startup Options

This ANSLIC_ADMIN utility option writes an ansyslmd.ini file in the licensing directory. This file contains any changes to the default values as well as your license server specifications and other settings (such as log file locations). Use this ANSLIC_ADMIN utility option to change the default values. For a detailed description of the settings that you can change with this option, see Modify Startup Options (p. 45).
2.3.4. Create a Group

You may want to create a group of users with specific usage capabilities, such as users with licensing administrative privileges, or users who are authorized to shut down the license manager. An lmadmin group is the most common type of group. To specify a list of users with access to licensing administrative options, you need to create an lmadmin group on computers from which license administration will be performed. If you create an lmadmin group, you must include root in order for root to continue to have access to these functions. For more details on using an lmadmin group, see the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility). This option is available for UNIX/Linux platforms only. Follow the instructions below for your hardware platform to create an lmadmin group. Sun, Linux Add a line to the file /etc/group as follows:
lmadmin:*:nn:root,user1,user2,user3...usern
where nn represents any unique group number and user1, user2, user3, ..., usern represent a list of n users in the group.
23
2.3.4.1. Defining Group Restrictions for the Licensing Interconnect

On UNIX/Linux machines only, you can also specify who can shut down the ANSYS, Inc. License Manager by using the ANSLIC_ADMIN utility's Modify Startup Options. By default, anyone can stop the license manager. You can restrict shutdown capabilities to only the user who started it, or to a group, such as lmadmin. If you choose group, you will need to specify the name of the group. Note that the user who started the license manager will still be able to shut it down, even if he is not part of a group with shutdown capabilities. If you specify a group restriction, any users in that group who wish to perform that operation must have the specified group as their primary group. For example, adding the following restriction: RESTRICT_SHUTDOWN=GROUP:lmadmin restricts the ability to shut down the license manager to only members of the lmadmin group. Any user who is a member of the lmadmin group and wants to shut down the license manager must have lmadmin as his primary group: machineabc{user1}: groups other testing dev1 lmadmin In the above example, user1 is a member of the groups other, testing, dev1, and lmadmin, where other is the primary group and testing, dev1, and lmadmin are secondary groups. To change a group from a secondary to a primary group, issue the newgrp (or equivalent) command:
machineabc{user1}: newgrp lmadmin
In this example, user1 now has lmadmin as his primary group and will be able to shut down the license manager: machineabc{user1}: groups lmadmin other testing dev1
2.3.5. Specify User Privileges

Establish user privileges by editing the FLEXlm Options file. The options file allows you, the license administrator, to control various operating parameters of FLEXlm: Allow or deny the use of features based on user, hostname, display name, group, etc. Reserve licenses based on user, hostname, display name, group, etc. Control the amount of information logged about license usage.
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/Linux 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
24
Post-Installation Instructions 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"
Use the Edit the FLEXlm Options File option of the ANSLIC_ADMIN utility to edit the license options file. The license options files must match on all three systems if you are using redundant systems. See Edit the FLEXlm Options File (p. 41) for details on editing the FLEXlm Options file.
2.3.6. Specifying the License Server and License Files

ANSYS products need to be able to locate and communicate with the license server for your ANSYS, Inc. products to run correctly. The license server and license files should be specified correctly during the product and license manager installations. Use the Specify the License Server Machine option of the ANSLIC_ADMIN utility only if you need to change the settings already specified. The Specify the License Server Machine option of the ANSLIC_ADMIN utility creates a file named ansyslmd.ini in the licensing directory. The ansyslmd.ini file contains your license server specification. For more information on specifying the license server, see Specify the License Server Machine (p. 34) in License Administration Using ANSLIC_ADMIN (p. 27). On Windows server machines, use the Server ANSLIC_ADMIN utility (accessed via Start> All Programs> ANSYS, Inc. License Manager> Server ANSLIC_ADMIN Utility) to modify the ansyslmd.ini file. On client machines, use the Client ANSLIC_ADMIN utility (accessed via Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0). If you have both the server and the client ANSLIC_ADMIN utilities on the same system, use the Client ANSLIC_ADMIN to specify machine-specific (local) settings. If you want to set your license paths to have a particular license server machine for your use only (not used by others who are running ANSYS products on this machine), you can do so by setting the ANSYSLI_SERVERS and/or ANSYSLMD_LICENSE_FILE environment variables. Use the ANSYSLI_SERVERS environment variable to specify the Licensing Interconnect port number. Use the ANSYSLMD_LICENSE_FILE to specify the FLEXlm port number. If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environment variable is not set, the same server machines will be used to specify the Licensing Interconnect but the port number will be replaced by the Licensing Interconnect default port of 2325. When both variables are set, ANSYSLMD_LICENSE_FILE explicitly defines the FLEXlm servers while ANSYSLI_SERVERS explicitly defines the Licensing Interconnect servers.
2.3.7. Specifying Firewall Settings

If you use a firewall at your site and if you run ANSYS products outside the firewall but access the license server within the firewall, you will need to add the Licensing Interconnect and FLEXlm port numbers to the exceptions list, as well as the PORT designated on the VENDOR line of the license file. By default, these port numbers are: Licensing Interconnect: 2325 FLEXlm: 1055 PORT designated by PORT=#### on the VENDOR LINE in the license.dat file (see VENDOR Lines (p. 4) for information on this PORT number)
25
2.3.8. Setting Up Redundant (Triad) Servers

Redundant server setup is a network configuration where multiple machines are designated as license servers. Redundancy can be achieved by running any number of license server machines independently, or by running three different machines to work in tandem. We recommend using multiple independent license server machines to achieve redundancy; however, if your site requires the use of three license server machines working in tandem, follow the guidelines in this section to configure the servers. 1. 2. Install the License Manager on each of the three servers as described in Installing the License Manager (p. 13). Be sure that each machine meets all of the prerequisites. Start each of the license servers using the same license file on each machine. The license file for the three-server setup will begin with three SERVER lines: SERVER myserver1 00e2463 1055 SERVER myserver2 00132460b724 1055 SERVER myserver3 001a246d4e64 1055 The first SERVER line is the license server you have designated as the primary server followed by the second and third servers, which act as the backup servers. 3. Always start the primary server first. If not, the second or third server will take over as the master server. When you start each license server, you will see a message indicating that the server is starting . The primary server will not be fully started until you start the second or third server, creating a quorum. Until you have a quorum of servers started, the Status window on the ANSLIC_ADMIN utility will show the Licensing Interconnect and monitor running while FLEXlm will show as not running. You could see a delay of up to five minutes in the startup of a server's FLEXlm component while the communication between all three servers is being established. If a connection cannot be established within the five minutes, the Licensing Interconnect and Licensing Interconnect Monitor will stop. Check the status box in ANSLIC_ADMIN to verify that all components have stopped before you attempt to restart the ANSYS, Inc. License Manager on any server. To stop redundant servers, use the Stop the ANSYS, Inc. License Manager option of the Server ANSLIC_ADMIN utility. In a redundant server configuration, the Licensing Interconnect will stop all three servers when you choose to stop any one of the three servers. As with starting the license servers, if one person is stopping each of the three servers, you could see a similar delay of five or more minutes before all three are fully shut down.
26
Chapter 3: License Administration Using ANSLIC_ADMIN

This chapter explains how to use the ANSLIC_ADMIN utility to perform many of the procedures necessary to administer licenses. You can use the ANSLIC_ADMIN utility to perform most licensing procedures. On Windows license server machines, you will have access to a server (full) version of the ANSLIC_ADMIN utility and a client version. The option descriptions below note which options are available on the Client ANSLIC_ADMIN utility as well as the Server ANSLIC_ADMIN utility. The Server ANSLIC_ADMIN utility is accessed via Start> All Programs> ANSYS, Inc. License Manager> Server ANSLIC_ADMIN Utility and updates the ansyslmd.ini file in the global license directory that resides at <os drive>\Program Files\Ansys Inc\Shared Files\Licensing. The Server ANSLIC_ADMIN offers access to all options and should be used to administer all licenses across a site that use that machine as a license server machine. Changes made using the Server ANSLIC_ADMIN utility will affect all users who use that machine as a license server machine, where appropriate. Note that settings such as Specifying the License Server are always local settings and do not affect other machines, even on a license server. From a client machine, you will have access to a limited client version of the ANSLIC_ADMIN utility. The Client ANSLIC_ADMIN utility is accessed via Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0 and updates the ansyslmd.ini file in the licensing directory that resides with the product installation. The Client ANSLIC_ADMIN utility should be used only to make changes to that local machine's configuration. Changes made using the Client ANSLIC_ADMIN utility will affect only this machine and will not affect other users. On UNIX/Linux machines, you can access only the full version of ANSLIC_ADMIN; no client version is available. Some options may apply to UNIX/Linux or Windows systems only and are so noted. See Advanced Licensing Configuration Options (p. 17) for details on configuring your license server to use LMTOOLS or FLEXNet Manager to manage FLEXlm. For more information on advanced FLEXlm operations, select Help > View FLEXnet Licensing End User Guide.
3.1. Using the ANSLIC_ADMIN Utility

To run ANSLIC_ADMIN on Windows, choose Start> All Programs> ANSYS, Inc. License Manager> Server ANSLIC_ADMIN Utility (for the server version) or Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0 (for the client version). To run the utility on UNIX/Linux, type the following:
To change the language to a localized version of the utility, first issue the following command with the -setliclang option. On Windows, run:
"<os drive>\Program Files\ANSYS Inc\Shared Files\Licensing\licadmin\anslic_admin.bat" -setliclang language
27
Chapter 3: License Administration Using ANSLIC_ADMIN On UNIX/Linux, run:

/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -setliclang language
This command changes the language used for both the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect log file. Use the language directory name in the language subdirectory of the licensing directory (en-us, fr, de, etc.) as the language value. This option is valid only with the server ANSLIC_ADMIN. Then launch the ANSLIC_ADMIN utility using the above methods.
Important
Changing the language will affect all users of the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect. Please verify with your licensing system administrator before making this change. To change the language setting locally for only the current session of the server or client ANSLIC_ADMIN utility, you can launch the utility using the -lang option:
<os drive>:\Program Files\Ansys Inc\Shared Files\Licensing\licadmin\anslic_admin -lang language
or
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -lang language
You do not need system administrator privileges to run the ANSLIC_ADMIN utility; however, you must have system administrator privileges or be a member of an lmadmin group to run the Remove a Client License and the Uninstall the License Manager options. Additionally, you need to have system administrator privileges on Windows machines to use the Start the ANSYS, Inc. License Manager and Stop the ANSYS, Inc. License Manager options. Windows 7/Vista Administrator Privileges On Windows 7/Vista machines, you need to always run these ANSLIC_ADMIN options as an administrator, preferably with UAC turned off. If UAC is on, even as administrator, you must right-mouse click on the ANSLIC_ADMIN selection from the Start menu and choose Run as Administrator. See the Windows 7/Vista discussion in the Platform Specifics section of the ANSYS, Inc. Windows Installation Guide for more details on working with Windows 7/Vista and UAC. We do not recommend running the ANSLIC_ADMIN on Windows machines by double-clicking the executable directly, especially on Windows 7/Vista systems. Doing so could launch the utility with unexpected permission levels. For server machines, status of your machine appears on the bottom left-hand side of the screen, in the Machine Name status area. Status of the Licensing Interconnect, the ansysli monitor, and FLEXlm are all displayed. The status will update automatically when the machine's status changes. 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 contact customer 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. To use the utility, select an action from the list of buttons on the left.
28
Using the ANSLIC_ADMIN Utility The ANSLIC_ADMIN utility consists of the following options: Register License Server Machine Information (p. 30) Display the License Server Machine Hostid (p. 30) Run the License Wizard (p. 31) Install the License File (p. 32) Start the ANSYS, Inc. License Manager (p. 32) Stop the ANSYS, Inc. License Manager (p. 33) Reread the License Manager Settings (p. 34) Specify the License Server Machine (p. 34) Remove a Client License (p. 37) Set License Preferences for User (p. 37) Run the ANSYS Borrow Utility (p. 38) (Windows only) Set Site Preferences (p. 40) -- includes the following options: Edit the FLEXlm Options File (p. 41) Specify Product Order (p. 44) Modify Startup Options (p. 45) Specify License Servers to Cache (p. 46) Display the License Status (p. 47) Display Queued Licenses (p. 47) Display the Customer Number (p. 48) View the ANSYS Licensing Interconnect Debug Log File (p. 48) View the ANSYS FLEXlm License File (p. 48) View the ANSYS FLEXlm Debug Log File (p. 48) Gather Diagnostic Information (p. 48)
View Status/Diagnostic Options (p. 46) -- includes the following options:
From the Tools> Uninstall menu (UNIX/Linux only), you can select Uninstall the License Manager. See Uninstall the License Manager (p. 49) for more information on uninstalling the License Manager. From the Tools menu, you can select Complete Unfinished Licensing Installation Configuration. This option will re-run the licensing installation configuration process, allowing you to complete any unfinished configuration steps. Note that the license manager will need to be shut down to proceed with this option. Use this option if your licensing installation configuration process was unable to complete (for example, the license manager was not able to be shut down). Also from the Tools menu, you can select Set Language Options and then choose a different language in which to view the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect log file. You must close and reopen the ANSLIC_ADMIN utility for this setting to take effect. This option is valid only with the server ANSLIC_ADMIN. From the Help menu, you can select: View the ANSLIC_ADMIN Help
29
Chapter 3: License Administration Using ANSLIC_ADMIN View the ANSYS, Inc. Licensing Guide View the FLEXnet Licensing End User Guide About ANSYS, Inc. Licensing About ANSLIC_ADMIN
To exit the ANSLIC_ADMIN utility, choose File>Exit.
3.1.1. Register License Server Machine Information

This option is used for license server machines only. Use this option to register your license server information (including the machine identifier to use as your FLEXlm hostid) with ANSYS, Inc. If you want to use a dongle for your license server information, please make sure the device is inserted and the correct device driver is installed. Not all platforms support dongles; please contact your ANSYS, Inc. sales representative for platform support and dongle usage information. If the ANSLIC_ADMIN utility detects a properly installed dongle, you will be asked if you want to use that device for your license server machine information. If you are running a 32-bit version of the license manager and have multiple dongles on the machine, you will be asked to select the dongle to use. Be sure to choose the correct device from the list presented. If you choose to use a dongle, the device information will be used. Otherwise, the physical machine information will be used. You will then be prompted to supply your customer (agreement) number (optional), company name, your name, email address, etc. This utility also obtains information about your machine, such as hostname, hostid, hardware platform, operating system level, and current date. In addition, this utility requires you to identify the type of license server machine. In the case of a three-server system, you must supply the server information on each server machine. The utility places the information it gathers into a file named licserver.info. By default, this file is written to the licensing directory, or you can specify an alternate location. You can browse to a directory other than the home directory. You must forward the file, created on each license server machine, to your ANSYS sales representative.
3.1.2. Display the License Server Machine Hostid

Use this option to obtain and display the machine identifier to use as the FLEXlm hostid of the machine on which you are currently running. If you are using a dongle that you want to use for your license server information, please make sure the device is inserted and the correct device driver is installed. Not all platforms support dongles; please contact your ANSYS, Inc. sales representative for platform support and dongle usage information. If the ANSLIC_ADMIN utility detects a properly installed dongle, you will be asked if you want to use that device for your license server machine information. If you are running a 32-bit version of the license manager and have multiple dongles on the machine, you will be asked to select the dongle to use. Be sure to choose the correct device from the list presented. If you choose to use a dongle, the device information will be used. Otherwise, the physical machine information will be used. To write this information out to a file, click the Create File button. By default, the file is named ansysid.machinename.txt, although you can change the filename. This option is available for both the server and client versions of ANSLIC_ADMIN.
30
Using the ANSLIC_ADMIN Utility
3.1.3. Run the License Wizard

You can run the license wizard either from the ANSLIC_ADMIN utility or as part of the license manager installation. The license wizard is used to configure license server machines only. This wizard walks you through the process of installing or updating a license file, specifying the license server machine(s) (which updates the ansyslmd.ini file), and starting/restarting the license manager. The wizard will prompt you for the necessary information at each step. You should use this option when you receive a new license file as it will walk you through the necessary steps to activate the new license. Advanced users can also use the wizard to configure their license servers to run the Licensing Interconnect without FLEXlm or independently of FLEXlm. See Advanced Licensing Configuration Options for more information. You can alternatively perform each of these steps individually using the separate options on the ANSLIC_ADMIN utility. 1. When the License Wizard is launched, you will need to specify the type of license server. You can choose from three options: Run the ANSYS Licensing Interconnect with FLEXlm (default) Run the ANSYS Licensing Interconnect without FLEXlm Run the ANSYS Licensing Interconnect and FLEXlm independently
Accept or select the default and click Continue. Most customers will use the default option. The other options are more advanced and should be used only by experienced customers. Instructions for using the other options are found under Advanced Licensing Configuration Options in the ANSYS, Inc. Licensing Guide and are not included here. 2. Next, you must install a valid license file if one is not already installed. Click Continue, and then browse to and select the license file provided to you by ANSYS, Inc. You must complete this step to continue with the wizard. If you do not have a license file, you must exit the wizard. You can rerun the license wizard when you receive your license file. The license wizard will next specify the local machine as the license server, meaning you will use the local machine as the license manager from which licenses are checked out. Click Continue. This step updates the ansyslmd.ini file to contain the local machine information as the license server. If you wish to specify a different or additional machine as the license server, you can use the Specify the License Server Machine option of the ANSLIC_ADMIN utility. The final step is to start the ANSYS, Inc. License Manager. Click Continue to start the license manager. If the license manager is already running, the license wizard will stop and restart it. Be aware that stopping the license manager could impact other users who are using this machine as their license server.
3.
4.
When all steps of the wizard have been successfully completed, you can click Exit to leave the license wizard.
Note
You can choose to skip steps when applicable; however, if you choose to skip any steps and you have not otherwise configured your system, your license server may not function correctly and you may not be able to run ANSYS, Inc. products.
31
3.1.4. Install the License File

This option is used for license server machines only. If you received a new license and your server and hostid are unchanged, use this option to replace your existing license file. This utility creates the license file, called license.dat by default, in the licensing directory. The license file contains your licensing information and allows you to run ANSYS, Inc. products. After you run this option, select Reread the License Manager Settings to reread the FLEXlm license file, which allows you to update the license manager with the new license without the need to stop and restart the license server. 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 (redundant triad) system, you must use this option on each license server machine.
Caution
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. You can use this option to install ANSYS license files only. To determine if you have an ANSYS license file, see Recognizing an ANSYS License File. If you have users who borrow licenses, you should check the output from Display the License Status to see if anyone currently has borrowed licenses before you update your license file. If you see borrowed licenses, notify those users to return the borrowed licenses prior to the update.
3.1.5. Start the ANSYS, Inc. License Manager

This option is used for license server machines only. Use this option to start the license manager. This option starts ansysli_monitor and ansysli_server, which automatically starts the FLEXlm components of the license manager: lmgrd and ansyslmd. The license file must exist prior to starting the license manager. The license manager must be running to run an ANSYS, Inc. product.
Note
If you chose to configure your license manager such that you run the Licensing Interconnect without FLEXlm or run the Licensing Interconnect and FLEXlm independently, then selecting this option will start only the Licensing Interconnect. In a three-server license environment, the license manager must be running on at least two of the three servers before an ANSYS product can be run. In a one-license server system, the license manager must be started on that server. 32
Note
In a three-server environment, you may see a delay in starting the license manager until two of the three servers are running. Do not press the Start the License Manager button more than once for the same server. The ansysli_server.log and the license.log files in the licensing directory contain a history of the Licensing Interconnect and FLEXlm activity, respectively, across your network since the last time the license manager was started.
3.1.6. Stop the ANSYS, Inc. License Manager

This option is used for license server machines only. Use this option to shut down the license manager. This option will shut down the ANSYS, Inc. License Manager, including ansysli_monitor, the Licensing Interconnect and the FLEXlm components of the license manager (lmgrd and ansyslmd) on all machines listed in the license file. You will be asked to confirm that the license manager should be shut down. Remember that the license manager must be running in order to run an ANSYS, Inc. product. Before shutting down the license manager, check that no ANSYS, Inc. product processes are currently running. Any processes that are running will be terminated when you shut down the license manager.
Note
If you chose to configure your license manager such that you run the Licensing Interconnect without FLEXlm or run the Licensing Interconnect and FLEXlm independently, then selecting this option will stop only the Licensing Interconnect.
Caution
Do not use kill -9 (on UNIX/Linux systems) to shut down the license manager. Use the ANSLIC_ADMIN utility option or ansysli_server -k stop.
Note
In a three-server (redundant triad) 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. This option will shut down all three server machines of a three-server (redundant triad) system, unless the license manager was started with the -local option. However, it will only stop the Licensing Interconnect running on the machine where this option was run. You will need to manually stop the Licensing Interconnects that are running on the other two machines of the three-server system, or those Licensing Interconnects will continue to restart FLEXlm on the other machines. We do not recommend stopping the license manager manually; however, if you choose to do so, you must stop the components in the following order: 1. 2. ansysli monitor (ansysli_monitor) Licensing Interconnect (ansysli_server)
33
Chapter 3: License Administration Using ANSLIC_ADMIN 3. FLEXlm components (lmgrd first, followed by ansyslmd)
3.1.7. Reread the License Manager Settings

This option is used for license server machines only. Use this option to reread the FLEXlm license file and reread the license manager settings. You will need to use this option to reread the FLEXlm license file when the license manager is already running and you have updated the license file or the license options file so that changes will take effect. Otherwise, the license manager will not be aware of the changes until it is stopped and restarted. This option: rereads the ansyslmd.ini file to get any new settings, such as log file size or change of name appends or opens a new log file rereads the site preferences Recaches the license file Issues a FLEXlm reread Recaches the servers Informs other servers about changes
Be aware that if you change the Licensing Interconnect port number, you will need to restart the license manager; a reread will not update the port number.
Note
If you chose to configure your license manager such that you run the Licensing Interconnect without FLEXlm or run the Licensing Interconnect and FLEXlm independently, then selecting this option will affect only the Licensing Interconnect components and recache the license file.
3.1.8. Specify the License Server Machine

Use this option to set the ANSYS Licensing Interconnect and ANSYS FLEXlm servers. Using this option creates or updates (lists, adds, modifies, deletes, or reorders) entries in the ansyslmd.ini file in the licensing directory for the local machine. With this option, you can specify single servers, multiple single servers, or redundant triad servers. You also use this option to specify the Licensing Interconnect and ANSYS FLEXlm port numbers. Run this option on every machine where you installed an ANSYS product. We recommend using this method for specifying your license server preference. This option is available for both the server and client versions of ANSLIC_ADMIN on Windows machines. In most situations, you should use the client version. The client version is appropriate regardless of where you have installed the product. You should use the server version of this option only to specify the license server machines for Release 11.0 and lower versions. You can also use the server version to specify license server machines if you have installed the product into <os drive>\Program Files, but we recommend using the client version anytime you are working with the current release. If the product is installed in <os drive>\Program Files (by a user with administrative privileges), you must have administrative privileges in order to add or modify your server specification. If you are running on a Windows 7/Vista machine, you must run as an administrator, preferably with UAC turned 34
Using the ANSLIC_ADMIN Utility off. If you are running with UAC turned on, you must launch ANSLIC_ADMIN using the Run as Administrator option. For more information on Windows 7/Vista behavior with UAC turned on, see Platform Specifics in the ANSYS, Inc. Windows Installation Guide. To add a server: 1. 2. Click Add Server Specification. Enter the ANSYS Licensing Interconnect and FLEXlm port numbers (2325 and 1055 by default, respectively). Specify the number of servers and enter the host name(s) of your license server(s). You cannot enter a path or a filename in place of the hostname. To specify multiple single servers, click OK on this screen after adding the first server. Then click the Add Server Specification button again and add information for the next server. Repeat this process for each single server. To specify redundant triad servers, click the 3-server (redundant triad) option and enter the hostname for each of the three servers in the spaces available. 3. Click OK.
To delete a server, highlight the server in the list and click Delete Selected Server. To edit a server, click on one of the listed servers and click Edit Selected Server. You can then change the ANSYS Licensing Interconnect and the FLEXlm port numbers, the number of license servers, or the hostname(s). You can choose to start the ANSYS Licensing Interconnect without FLEXlm, and to manage FLEXlm separately by caching the FLEXlm license. If you choose to run these advanced options, please read Advanced Licensing Configuration Options for detailed instructions, limitations, and caveats. The ansyslmd.ini File The Specify the License Server Machine option creates or updates the ansyslmd.ini file that is located in the licensing directory. Entries in the ansyslmd.ini 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 the ANSYSLMD_LICENSE_FILE or ANSYSLI_SERVERS environment variables to specify the license server machine(s). It also eliminates the need to have a copy of the license file on every system at your site. 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. You are not limited to designating one set of license server machines for your network. You can have multiple single-server or three-server (redundant triad) licensing systems on your network. In this situation, you would have certain licenses connected to a set of server machines (one or three) on the network, and other licenses connected to a different set of server machines (one or three) on the network. The format of the ansyslmd.ini file created by ANSLIC_ADMIN follows. Each server's specification entry in this file will typically begin with ANSYSLI_SERVERS= and SERVER= to specify the Licensing Interconnect and FLEXlm port numbers, respectively. On a single server:
ANSYSLI_SERVERS=<ansysliport>@<host> SERVER=<flexlmport>@<host>
For multiple single servers, each server should have its own ANSYSLI_SERVERS= and SERVER= lines.
35
Chapter 3: License Administration Using ANSLIC_ADMIN On redundant (triad) servers on UNIX/Linux platforms:
ANSYSLI_SERVERS=<ansysliport>@<host1>:<ansysliport>@<host2>:<ansysliport>@<host3> SERVER=<flexlmport>@<host1>:<flexlmport>@<host2>:<flexlmport>@<host3>
Windows platforms use semicolons (;) instead of colons:

ANSYSLI_SERVERS=<ansysliport>@<host1>;<ansysliport>@<host2>;<ansysliport>@<host3> SERVER=<flexlmport>@<host1>;<flexlmport>@<host2>;<flexlmport>@<host3>
The ANSYS Licensing Interconnect default port number is 2325 and the ANSYS FLEXlm default port number is 1055. The host is the license server hostname. For example, if the license server name is alpha1:
ANSYSLI_SERVERS=2325@alpha1 SERVER=1055@alpha1
The order of the ANSYSLI_SERVERS and the SERVER lines in the ansyslmd.ini file specifies the order in which the requested license will be granted. You must use the port@host format; you cannot enter a path or a filename in place of the hostname. Overriding the ansyslmd.ini File If you want to override the server specification settings in the ansyslmd.ini file, you can do so by setting the ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS environment variables on individual machines. These environment variables are useful if you want to temporarily point to a different license server machine without disrupting the machine's configuration. Use the ANSYSLI_SERVERS environment variable to specify the Licensing Interconnect port number. Use the ANSYSLMD_LICENSE_FILE to specify the FLEXlm port number. If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environment variable is not set, the same server machines will be used to specify the Licensing Interconnect but the port number will be replaced by the Licensing Interconnect default port of 2325. When both variables are set, ANSYSLMD_LICENSE_FILE explicitly defines the FLEXlm servers while ANSYSLI_SERVERS explicitly defines the Licensing Interconnect servers. If you set the ANSYSLMD_LICENSE_FILE or ANSYSLI_SERVERS environment variables on a threeserver (redundant) system, specify all three systems, in the same order as the SERVER lines are listed in the license file. If you specify only the master and it is down, you could see a License Server Down or No License Found message and the search for a license could fail. Join redundant or multiple single server systems by separating the system names with colons on UNIX/Linux systems and semicolons on Windows systems. To have your license server preference known each time you log in, set the environment variables ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS (both Windows and UNIX systems). On UNIX systems, place these environment variables in your login startup file (e.g., .cshrc file).
3.1.8.1. Sample Scenario

Suppose that you have a company with two departments, Design and Engineering. The Design Department has one license of ANSYS Mechanical and one license of DesignSpace with the server DES1, and all users in the Design Department run on DES1. The second department, Engineering, has two licenses of ANSYS Multiphysics with the server ENG1, and all users in the Engineering Department run on ENG1. The ansyslmd.ini file states ANSYSLI_SERVERS=2325@DES1 and SERVER=1055@DES1 for the Design Department, and ANSYSLI_SERVERS=2325@ENG1 and SERVER=1055@ENG1 for the Engineering Department. These settings limit users in each department to work only on their own server. If individual users in the Design Department need to run on the engineering server, ENG1, they could set the following environment variable:
36

setenv ANSYSLMD_LICENSE_FILE 1055@ENG1
This example would automatically use 2325@ENG1 for the Licensing Interconnect license path. For this example, you would need to set ANSYSLI_SERVERS only if you were not using the default Licensing Interconnect port number.
3.1.9. Remove a Client License

This option is used for license server machines only. You may need to free a license when a licensed user was running an ANSYS, Inc. product on a node that subsequently crashed. This situation will sometimes cause the license to become unusable. Free the license to allow the license to return to the pool of available licenses. Only those with FLEXlm administrative privileges (UNIX/Linux) or administrative privileges (Windows) can use this procedure because removing a user's license can be disruptive. You will be prompted for the following information: feature name user name host name display
If you are not sure of any of the above items, run the Display the License Status (p. 47) option to obtain the correct information. The messages display in the following format:
user hostname display version servername/port start date
For example:
user1 user2 user3 user4 hostabc hostdef hostghi hostjkl /dev/pts/5 (v2009.0213) (pghlicserver/1055 301), start Mon 2/16 6:09 NONE (v2009.0112) (pghlicserver/1055 2901), start Mon 2/16 6:10 pghxpuser3 (v2007.0830) (pghlicserver/1055 5151), start Tue 2/17 10:30 /dev/tty (v2009.0213) (pghlicserver/1055 5062), start Mon 2/16 9:00
In the above example, the following are display names: /dev/pts/5 NONE pghxpuser3 /dev/tty Note that display names at your site may or may not follow one of these conventions. 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.
3.1.10. Set License Preferences for User

Use this option to review the licenses available and prioritize the licenses. Settings specified here apply only to the username shown in the button title. When you select this option, you will first choose the
37
Chapter 3: License Administration Using ANSLIC_ADMIN release for which you want to set preferences. Select the release and click OK. All licenses available to you on your license server machine(s) are shown under the appropriate tab on the next dialog: Solver PrepPost Geometry HPC
You control the order in which the system attempts to check-out a license by moving the licenses up and down in the list using the Move Up or Move Down buttons. When you open an application, the license manager attempts to check-out the license listed first in the list. If unable to check-out that license, then the license manager attempts to check out the next license in the list that can be used by the application. The license manager will continue through the list until an available license is found. If none are found, a message displays. By default, all licenses available from your license server are shown and marked as available for use. If you do not want a particular license to be available for your use, select the license in the list, and set the Use/Don't Use field to 0. If you received a new license, you may need to reset your preferences. If you had previously set your license preferences using this option, add the new license to your list in the desired order. If you have made changes to your license preferences, you can return the settings to the default state by selecting the Reset to Default button. When you have completed your changes, click OK to make the changes and close the dialog box. Click Apply to make the changes without closing the dialog box. Selections you make here will take effect with any new sessions/license checkouts but will not affect the current session or change the license(s) currently in use. ANSYS Workbench users can also specify whether to use the shared or separate licensing method. For details on setting user license preferences, including shared vs. separate licensing for ANSYS Workbench and specifying HPC licensing settings, see Establishing User Licensing Preferences in End-User Settings.
3.1.11. Run the ANSYS Borrow Utility

License borrowing (available only on Windows machines) 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. Before users can take advantage of license borrowing, you need to set up the borrowing environment. License borrowing is available only if you have borrowable licenses and only on Windows machines; however, the license server machine that is managing the licenses can be any system that ANSYS, Inc. supports as a license server. You cannot run both borrowed and non-borrowed licenses simultaneously. For example, if you borrow licenses but remain connected to a network from which you can use licenses, you will be able to use only the borrowed licenses. Likewise, if the machine on which you borrowed licenses is also a license server from which you could normally use licenses, you would be able to use only the borrowed licenses. This option is available for both the server and client versions of ANSLIC_ADMIN.
38
3.1.11.1. Setting up License Borrowing

To use license borrowing, you must have license keys that specify borrowable licenses. License features that can be borrowed will contain the keyword BORROW. You can use the optional FLEXlm options file settings to further control borrowing at your site. To use these settings, you must first specify which users are allowed to borrow licenses by adding an INCLUDE_BORROW group to the options file. Any user not in the INCLUDE_BORROW group will not be allowed to borrow licenses. You may also wish to set up an EXCLUDE_BORROW group to prevent specific users from borrowing licenses. You can also limit the number of licenses that can be borrowed from your total pool of borrowable licenses. Set the BORROW_LOWWATER option in the options file to the number of licenses that cannot be borrowed. For example, if you have 15 licenses total and want to limit the number that can be borrowed to 5, set BORROW_LOWWATER=10. The maximum number of hours a license can be borrowed at any one time is defined by your license file. You can set that limit lower for your users by setting the MAX_BORROW_HOURS option in the options file. MAX_BORROW_HOURS cannot exceed the limit specified in your license file. The total maximum number of borrowable hours is defined by your license agreement. Compatibility between versions Flexera Software has created an incompatibility in license borrowing between FLEXlm releases. Since different versions of FLEXlm are used at most releases, the borrowed licenses are not compatible between different ANSYS releases. The ANSBORROW utility includes a selection for the ANSYS version you are planning to run using the borrowed license. Choose your version carefully, because you will only be able to run one of the versions at a time with borrowed licenses. Another incompatibility exists within the same release, between platforms. If you borrow a license with one of the Windows versions (32-bit or x64), you cant use the borrowed license on one of the other Windows versions, even on the same computer. For example, you have an x64 machine running the Windows 32-bit version, and then you install the x64 version when it is released. If you borrow the license using the 32-bit ANSBORROW, you wont be able to run the x64 version of ANSYS. The ANSBORROW utility allows you to borrow either initial release or service pack (SP) versions. The SP versions for a given platform use the same FLEXlm version as the initial release; therefore, licenses selected for SP should work for the initial release.
3.1.11.2. Running the Borrowing Utility

To run the license borrowing utility, you must be running on a Windows machine connected to a network, and you must have borrowable licenses. For more information about borrowable licenses, please contact your ANSYS sales representative. 1. 2. 3. Connect to the network where the license server machine is running. Launch the client license borrowing utility: Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0. Select Run the ANSYS Borrow Utility. On the Borrow tab, specify the version number and return date. The return date defaults to the third day from the current date. If you change any of the borrowing criteria, the product list will automatically update in five seconds. To update the list immediately, click the Update Delay (sec) button.
39
Chapter 3: License Administration Using ANSLIC_ADMIN 4. Select the product(s) you want to borrow. The product list includes add-on features or geometry interfaces. If you do not see a product listed that you think should be available, verify that you have selected the correct version. 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. Be sure to verify that you can run the correct product with the borrowed licenses from your machine AFTER you've disconnected from the network. If you encounter any difficulties, reconnect to the network, return the license, and then re-borrow the correct license. 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 client license borrowing utility: Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0. Select Run the ANSYS Borrow Utility. Select the Return tab. Click Return all. If you wish to keep some but not all of the licenses you borrowed, you will need to re-borrow them. Disconnect from the network.
5. 6.
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.
3.1.12. Set Site Preferences

This option is used for license server machines only. The following site preference settings are available: Edit the FLEXlm Options File (p. 41) Specify Product Order (p. 44) Modify Startup Options (p. 45) Specify License Servers to Cache (p. 46)
40
3.1.12.1. Edit the FLEXlm Options File

To set specific user privileges with FLEXlm, you need to use the options file. The options file allows you, the license administrator, to control various operating parameters of FLEXlm: Allow or deny the use of features based on user, hostname, display name, group, etc. Reserve licenses based on user, hostname, display name, group, etc. Control the amount of information logged about license usage.
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 (redundant triad) 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/Linux 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
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"
Use the Edit the FLEXlm Options File option to edit the license options file ansyslmd.opt. The license options files must match on all three systems if you are using redundant systems. Restart the license manager or Reread the License Manager Settings (p. 34) for changes to take effect. The Licensing Interconnect does not process the FLEXlm options file by default. If you need to have the Licensing Interconnect process the FLEXlm options file (needed when the FLEXlm options file contains IP addresses), add the following entry to the ansyslmd.ini file on the license server:
ANSYSLI_USE_FLEXOPTS=1
Then, either reread or restart the Licensing Interconnect. Because the Licensing Interconnect checks out licenses on behalf of the client, if you are using IP addresses, be certain to INCLUDE the IP address of the system running the Licensing Interconnect in the FLEXlm options file where appropriate.
Note
Use IP addresses only for the INCLUDE, INCLUDEALL, EXCLUDE, and EXCLUDEALL options. IP addresses are not processed correctly for other options.
3.1.12.1.1. The Options File Format

The maximum line length is 2048 characters. FLEXlm allows the "\" character as a continuation character in options file lines. You can include comments in your options file by starting each comment line with a pound sign "#." Everything in an options file is case sensitive. Be sure that user names and feature names, for example, are entered correctly. Some commonly used lines in the options file are shown below. See the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility) for information on additional options.
41
Chapter 3: License Administration Using ANSLIC_ADMIN EXCLUDE EXCLUDEALL GROUP HOST_GROUP INCLUDE INCLUDEALL RESERVE BORROW_LOWWATER EXCLUDE_BORROW INCLUDE_BORROW MAX_BORROW_HOURS Deny a user access to a feature. Deny a user access to all features served by this vendor daemon. Define a group of users for use with any options. Define a group of hosts for use with any options. Allow a user to use a feature. Allow a user to use all features served by this vendor daemon. Reserve licenses for a user. Sets the number of licenses for a BORROW feature that cannot be borrowed. Excludes a user or predefined group of users from the list of who is allowed to borrow licenses for a BORROW feature. Includes a user or predefined group of users in the list of who is allowed to borrow a BORROW feature. 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.
Note
You must stop and restart the license manager (rather than rereading the license file) when a change is made to the options file. 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. 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. Keyword Format The format for these keywords follow:
RESERVE number feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name
42

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 the 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 blankseparated list of host names; and num_hours is the number of hours for which a license can be borrowed, up to the limit specified in the license file. On UNIX/Linux 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 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 2010.0331 permanent 1 AA1DE4A0E7BB \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2010 START=01-Jan-2010 INCREMENT struct ansyslmd 2010.0430 permanent 1 3D967A3ECF4E \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2010 START=01-Jan-2010
If you create the following entry in the options file:

RESERVE 1 struct USER smith
then you will reserve two licenses, one from each INCREMENT line, for user smith.
43
Chapter 3: License Administration Using ANSLIC_ADMIN To reserve only one license, create an entry that contains the differing information:
RESERVE 1 struct:VERSION=2010.0430 USER smith
For a complete list of license features, see the Product Variable Table. For more information on the options file, see the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility).
Note
ANSYS products use a TIMEOUT and TIMEOUTALL default of 55 minutes (3300 seconds). You cannot set the minimum value below 15 minutes (900 seconds). Application idle TIMEOUTs are not supported, i.e., the TIMEOUT options will not work for applications that are not actively in use.
3.1.12.1.2. Sample Options File

In the following example options file, one license to execute ANSYS Mechanical is reserved for user pat, three licenses for user lee, and one license for anyone on the computer with the hostname of client3. In addition, user joe is not allowed to use the ANSYS Mechanical license.
RESERVE RESERVE RESERVE EXCLUDE 1 ansys USER pat 3 ansys USER lee 1 ansys HOST client3 ansys USER joe
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.
3.1.12.2. Specify Product Order

This option launches a utility that allows you to designate the order that the licensed products are listed in the Mechanical APDL launcher and the order in which licenses are tried in all applications. You first will need to select the product release. You can choose one of the following: Release 11.0: Selecting this option affects the product ordering for Release 11.0 for this machine (including all users who run a Release 11.0 product on this machine or mount to this machine). If you select this option, the product ordering you specify will NOT affect any releases after 11.0. Release 12.0 and higher: Selecting this option affects the product ordering for Releases 12.0 or later and is applicable ONLY if this machine is a license server machine. The product ordering you select with this option will affect all users who use this machine as a license server machine.
After you choose a release level, click OK. You will then need to select the installation directory (Release 11.0 only), product category (Solver, PrepPost, or Geometry). To re-order the products, select a product and click the Move up or Move down button. When you have finished reordering all products that you wish to reorder, click Save and then Close. All products available in a given category are shown, regardless of whether you have licenses for them.
44
Using the ANSLIC_ADMIN Utility If you have made changes to your product ordering, you can return the settings to the default state by selecting the Reset to Default button. For Release 12.0 and higher, after making changes to the product order (including resetting to the default), you will need to reread the license or restart the license manager for the changes to take effect. Only those logged in as root or superuser (UNIX/Linux) or with administrative privileges (Windows) can use this utility. You should set the product order before any of the users at your site run; once a user sets his preferences, the user preferences will take precedence.
3.1.12.3. Modify Startup Options

Use this option to modify your license manager startup options. License manager startup options that you can modify include: ANSYS Licensing Interconnect Debug Log File You can specify the path to the ANSYS Licensing Interconnect debug log file (ansysli_server.log, by default), the detail level of the file (standard or verbose), the size limit of the file, and the number of log files to save (default is 1; minimum is 1). The default file size is unlimited (blank), and the minimum size is 1 MB. By default, a new file is created each time; you can choose to have new information appended to the existing file instead. ANSYS Licensing Interconnect Report File The Licensing Interconnect has the ability to track and log your usage data into a report file (<timestamp>.rprt). By default, this feature is turned off. Use this option to enable this feature. Report files are saved and time-stamped for future reference. You can specify a directory other than the default where the report files will be saved, but you cannot change the file name. You can also specify the size of the report file in megabytes. While we are able to collect this data into a report file, we currently do not offer a reporting tool that will display the data. FLEXlm Options You can specify the path to the FLEXlm license file (license.dat, by default), as well as to the FLEXlm debug log file (license.log, by default). By default, a new license.log file is created each time you start the license manager; you can choose to have new information appended to the existing file instead. You can also set the -local setting (UNIX/Linux only). The -local option restricts the ability to shut down the FLEXlm components of the license manager to only an administrator running on the same machine where the FLEXlm components of the license manager was started. This option is off by default. See the FLEXnet Licensing End Users Guide (accessible from the ANSLIC_ADMIN utility) for more information on using this option. The -local option is not recommended if you will be using license borrowing. You can also choose to start the ANSYS Licensing Interconnect without FLEXlm and to cache FLEXlm licenses. Use these two options together to run the ANSYS Licensing Interconnect and FLEXlm independently. These options are advanced configuration options and require additional steps. Please see Advanced Licensing Configuration Options for more information, including detailed procedures for using these options. Miscellaneous Options You can specify the ANSYS Licensing Interconnect port number here. The default port number is 2325. All machines that have this server machine in their Licensing Interconnect paths must use the same port number. If you change the Licensing Interconnect port number here, and other machines use
45
Chapter 3: License Administration Using ANSLIC_ADMIN this machine's Licensing Interconnect, then on each of those machines, you must change the Licensing Interconnect port number by one or both of the following options, as appropriate for your configuration: Specify the License Server Machine option of the ANSLIC_ADMIN utility Specify License Servers to Cache option of the ANSLIC_ADMIN utility
On UNIX/Linux machines only, you can also specify who can shut down the ANSYS, Inc. License Manager. By default, anyone can stop the license manager. You can restrict shutdown capabilities to only the user who started it, or to a group, such as lmadmin. If you choose group, you will need to specify the name of the group. If you specify a group restriction, any users in that group who wish to stop the license manager must have the specified group as their primary group. Note that the user who started the license manager will still be able to shut it down, even if he is not part of a group with shutdown capabilities.
Warning
The license.log file and the ansysli_server.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 these files crashes, the license manager would be unable to log license transaction data. This would create a fatal error condition.
3.1.12.4. Specify License Servers to Cache

When the Licensing Interconnect starts, it caches the licenses for any ANSYSLI_SERVERS lines that are in the ansyslmd.ini file in addition to its own licenses. As you run ANSYS applications and they connect with the Licensing Interconnect, it caches the licenses for any servers in your ANSYSLI_SERVERS path that have not yet been cached. Sometimes, especially due to network traffic, this caching process can impact the time it takes to check out a license. Use this option to cache your servers when you start the ANSYS, Inc. License Manager, rather than at the point that you request individual licenses. When you select this option: 1. 2. 3. 4. 5. 6. On the Specify License Servers to Cache dialog, click Add Server Specification. On the Specify License Servers to Cache - Add Server Machine Specification dialog box, enter the Licensing Interconnect port number. The default Licensing Interconnect port number is 2325. Enter the hostname of the server. Click OK. Repeat steps 1 - 4 for any additional servers that you want to cache. When you have finished specifying servers, click Close on the Specify License Servers to Cache dialog.
To delete a cached server, highlight the server in the list and click Delete Selected Server. To edit a cached server, click on one of the listed servers and click Edit Selected Server. You can then change the ANSYS Licensing Interconnect port number or the hostname(s).
3.1.13. View Status/Diagnostic Options

The following reporting options are available:
46
Using the ANSLIC_ADMIN Utility Display the License Status (p. 47) Display Queued Licenses (p. 47) Display the Customer Number (p. 48) View the ANSYS Licensing Interconnect Debug Log File (p. 48) View the ANSYS FLEXlm License File (p. 48) View the ANSYS FLEXlm Debug Log File (p. 48) Gather Diagnostic Information (p. 48)
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. Not all of these options are available for both the server and client versions of ANSLIC_ADMIN.
3.1.13.1. Display the License Status

Use this option to see the status of licensing activity. All features are displayed in the status window, along with the users of those features. You can append this information to the session log or write it directly to a file using the buttons at the bottom of the window. This option displays information based on the same license path rules as ANSYS, Inc. products, taking into account the settings in the ANSYSLMD_LICENSE_FILE environment variable and the ansyslmd.ini and license files. Setting the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable will affect the information displayed by this option.
3.1.13.2. Display Queued Licenses

Use this option to see a list of capabilities that are queued and awaiting availability, and the applicable licenses that are being used. The report will have the following format:
Capability Product1 Timestamp Timestamp Timestamp Product2 Timestamp Timestamp Timestamp User1 User2 Usern User1 User2 Usern Timestamp User Count Count Count Count Count Count Count Count Count Host Host Host Host Host Host Host PID PID PID PID PID PID PID Platform Platform Platform Platform Platform Platform Platform
Where the first line shows information for the requesting user, and subsequent lines under that capability show information for the users who are currently using the licenses for each of the licensed products that satisfy the requested capability. An example report is shown below. Each line is numbered for reference in the discussion following the example. Note that the actual report does not contain line numbers.
Capability 1 ANS_SOLVER 2 3 4 Product Timestamp 2010/04/27 09:39:27 ane3fl 2010/04/27 08:01:10 2010/04/27 07:29:13 User Count Host JQD 1 mach1.win.acme.com 3 JXS 1 mach2.win.acme.com MQD 2 mach3.win.acme.com PID 1234 5678 8765 Platform winx64 winx64 winx64
Line 1: User JQD is running a process, 1234, on the machine mach1.win.acme.com, which has requested one license with the ANS_SOLVER capability.
47
Chapter 3: License Administration Using ANSLIC_ADMIN Line 2: Based on the site/user preferences, the ane3fl product can satisfy the requested capability, and this site/user is permitted to use up to 3 licenses of this product. Line 3: User JXS has been using 1 of the available licenses since 8:01:10, from machine mach2.win.acme.com, running process number 5678. Line 4: User MQD has been using 2 of the available licenses since 7:29:13, from machine mach3.win.acme.com, running process number 8675. Since users JXS and MQD are already using all of the available licenses, user JQD must either wait for one of those licenses to be freed, or contact one of those users and request that a license be freed. Select the Auto-Refresh button to have the information automatically refresh every five (5) seconds. You can also display the queuing report via command line, without launching the ANSLIC_ADMIN GUI. To do so, run the following command on Windows systems:
"C:\Program Files\Ansys Inc\Shared Files\Licensing\licadmin\anslic_admin" -queueinfo
If you need to view the queuing report frequently, you may find it convenient to set a desktop shortcut using the above command. Run the following command on UNIX/Linux systems:
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -queueinfo
3.1.13.3. Display the Customer Number

Use this option to display your customer number (necessary when requesting customer support). The license manager must be running for you to obtain your customer number.
3.1.13.4. View the ANSYS Licensing Interconnect Debug Log File

This option is available only on the license server machine(s). Use this option to view the Licensing Interconnect debug log file (named ansysli_server.log by default).
3.1.13.5. View the ANSYS FLEXlm License File

This option is available only on the license server machine(s). This option displays the contents of your current license file in the reporting area. You can append this information to the session log or write it out to a separate file. Do not use this option to create a new license file. The Write to File option here will create a text file that includes extraneous information that is not valid in a license file, and should be used only to create a file for reference purposes.
3.1.13.6. View the ANSYS FLEXlm Debug Log File

This option is available only on the license server machine(s). Use this option to view the license log file (named license.log by default).
3.1.13.7. Gather Diagnostic Information

When you choose this option, you will be given the option to gather all relevant log and error files into a single directory. Files that will be gathered include the license.log file, the ansysli_server.log file, relevant ansyslmd.ini files, etc.
48
Using the ANSLIC_ADMIN Utility This feature is useful if you want to easily review the files from a single location, or if you need to compress the files and send them to a technical support representative. Every time you choose to gather these files, they will be copied into a new, date-stamped subdirectory in your /var/tmp directory on UNIX/Linux or in the directory specified by the TEMP environment variable on Windows. Be aware when choosing this option that some of these files can be large and could require significant disk space. You may wish to delete these directories when you are finished reviewing them because of the disk space usage. After all relevant files are gathered (if selected), this option runs the ansys_pid utility, which queries the system for information that may be useful for troubleshooting certain problems. This operation may take a few minutes. You can append this information to the session log, or you can write it out directly to a file using the buttons at the bottom of the window. When you run this utility, information about your licensing information is displayed in the ANSLIC_ADMIN log area. Information displayed may include: operating system info environment information, including environment variable settings firewall information ANSYS, Inc. License Manager version and status information available license information
The contents of specific log and error files will not be displayed in the ANSLIC_ADMIN log area. You will need to review these files individually for specific errors and other status/log information.
Note
If you have set the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable, the information will be displayed based on the ANSYSLMD_LICENSE_FILE environment variable setting; settings in the ansyslmd.ini file in the licensing directory will NOT be used.
3.1.14. Uninstall the License Manager

UNIX/Linux On UNIX/Linux machines only, you can use this ANSLIC_ADMIN option to remove the entire ANSYS, Inc. license manager installation from your system. To use this option, you must be logged in as root or superuser. You should not uninstall the license manager if you still have products installed that use the license manager. You will be asked to verify that the license manager should be uninstalled from this system. The contents of the licensing directory will be deleted. Also, if the license manager is running, it will be shut down. Windows On Windows machines, you must follow the procedure below. You should not uninstall the license manager if you still have products installed that use the license manager. License Servers 1. 2. Follow these steps on a license server machine:
Stop the ANSYS, Inc. License Manager via the ANSLIC_ADMIN utility (Start> All Programs> ANSYS Inc. License Manager> Server ANSLIC_ADMIN Utility). Uninstall the ANSYS, Inc. License Manager service. You must use the following command to do so:
49

"C:\Program Files\Ansys Inc\Shared Files\Licensing\<platform>\ansysli_server" -k uninstall
3. 4. 5.
Delete the licensing subdirectory (C:\Program Files\Ansys Inc\Shared Files\Licensing by default). Remove the ANSYS, Inc. License Manager folder from the Start menu. Remove the ANSYSLIC_DIR and the ANSYSLIC_SYSDIR environment variables, if set. Follow these steps on client machines:
Clients 1. 2.
Delete the licensing subdirectory (C:\Program Files\Ansys Inc\Shared Files\Licensing by default). Remove the ANSYS 14.0> ANSYS Client Licensing folder from the Start menu.
50
Chapter 4: End-User Settings

End users can set several controls for a customized licensing environment. These controls are explained in this chapter.
4.1. Client Environment Variable Settings

You can set following environment variables on individual machines to control their behavior, especially if you need it to be different from the general site configuration. These settings are especially useful for situations where you are testing a new product installation/license manager installation on a single machine before full site deployment, or other similar situations. ANSYSLMD_LICENSE_FILE Can be used to identify a license server machine or license file. If set, this specification is used before any other license path information. See License Files Settings Precedence (p. 51) for precedence information. The default port number assigned to ANSYS, Inc. is 1055. Therefore, if your server has the hostname alpha1 and the IP address of 10.3.1.69, you can identify the server to use as 1055@alpha1 or 1055@10.3.1.69. ANS_FLEXLM_DISABLE_DEFLICPATH Indicates that the default license path should not be searched when determining the licensing path in the ANSYS product: 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.
ANSYSLI_SERVERS Used to identify the server machine for the Licensing Interconnect. Set to port@host. The default port is 2325. This setting takes precedence over settings specified in the ansyslmd.ini file. ANSYSLI_TIMEOUT_CONNECT Used to specify the amount of time that elapses before the client times out if it cannot connect to the server. Default is 20 seconds. Minimum timeout period you can specify is 5 seconds and the maximum is 60 seconds. ANSYSLI_TIMEOUT_TCP Used to specify the amount of time that elapses before the client times out if it cannot get a response from the server. Default is 60 seconds. Minimum timeout period you can specify is 30 seconds and the maximum is 300 seconds.
4.1.1. License Files Settings Precedence

ANSYS Licensing Interconnect settings have precedence in the following order: 1. 2. ANSYSLI_SERVERS environment variable If ANSYSLI_SERVERS is not set, use ANSYSLMD_LICENSE_FILE environment variable, replacing the FLEXlm port number with the default Licensing Interconnect port number of 2325.
51
Chapter 4: End-User Settings 3. Settings in the ansyslmd.ini file in the relative client licensing directory for ANSYSLI_SERVERS= keyword
FLEXlm settings have precedence in the following order: 1. 2. ANSYSLMD_LICENSE_FILE environment variable Settings in the ansyslmd.ini file in the relative client licensing directory for SERVER= keyword.
Note
The FLEXlm environment variable LM_LICENSE_FILE is not supported with the ANSYS, Inc. License Manager.
4.2. Establishing User Licensing Preferences

Before running ANSYS, Inc. products, you should establish your licensing preferences, especially if you have multiple licenses at your site. Use the Set License Preferences for User option of the ANSLIC_ADMIN utility or choose Start> All Programs> ANSYS 14.0> ANSYS Client Licensing> User License Preferences 14.0 to set your own licensing preferences. Preferences specified with this option apply only to you and will not affect other users at your site. You can use this option to review the licenses available, prioritize the licenses, and establish which licenses you will use. When you select this option, a dialog box opens. All licenses available to you on your license server machine(s) are shown under the appropriate tab: Solver PrepPost Geometry HPC
You control the order in which the system attempts to check-out a license by moving the licenses up and down in the list using the Move Up or Move Down buttons. When you open an application, the license manager attempts to check-out the license listed first in the list. If unable to check-out that license, then the license manager attempts to check out the next license in the list that can be used by the application. The license manager will continue through the list until an available license is found. If none are found, a message displays. By default, all licenses available from your license server are shown and marked as available for use. If you do not want a particular license to be available for your use, select the license in the list, and set the Use/Don't Use field to 0. If you received a new license, you may need to reset your preferences. If you had previously set your license preferences using this option, add the new license to your list in the desired order. If you have made changes to your license preferences, you can return the settings to the default state by selecting the Reset to Default button. When you have completed your changes, click OK to make the changes and close the dialog box. Click Apply to make the changes without closing the dialog box. Selections you make here will take effect with any new sessions/license checkouts but will not affect the current session or change the license(s) currently in use.
52
Establishing User Licensing Preferences
4.2.1. ANSYS Workbench Licensing Methods

ANSYS Workbench users can also specify the licensing method to use. ANSYS Workbench offers two licensing methods at Release 14.0: Share a single license between applications (default) (shared mode) Use a separate license for each application (separate mode)
Use the Licensing Preferences dialog box (Start> All Programs > ANSYS 14.0 > ANSYS Client Licensing > User License Preferences 14.0) to specify which method to use and which licenses to use. You must specify the licensing method before starting an ANSYS Workbench session. If you access the Licensing Preferences dialog box from the ANSYS Workbench Tools menu, you will not be able to choose a licensing preference from there.
Single License Sharing

ANSYS Workbench allows you to work across multiple applications and workspaces in ANSYS Workbench while consuming only one of a single type of license per user per session. Using shared licensing, the active application holds the license, preventing other applications that are sharing that license from using it during that time. The application or operation requiring use of the license is called a concurrency event. For example, meshing and solving would each be a concurrency event. Single license sharing allows you to progress through your analysis, from specifying engineering data through building or attaching a geometry, meshing, setup, solving, and finally, reviewing your results, all under the same license. The application holding the license must close or issue a PAUSE command, or receive an automatic release request to release the license and allow another application to use it. Licenses cannot be released while an application is actively performing a licensed operation (for example, an application cannot release a license in the middle of a solve operation; the license cannot be released until the solve operation is completed). Single license sharing applies only to licenses of the same type (e.g., Mechanical). Choosing this option does not affect your ability to use licenses of different types simultaneously (e.g., Mechanical for one task and Fluid Dynamics for another). Because this method is the default, you do not have to take any action to run this way. Explanation of License Type and Examples License type is primarily by license feature. It is possible to use both a Mechanical and an Emag license within a single ANSYS Workbench session. It is also possible to use both a Multiphysics and a Mechanical license within a single ANSYS Workbench session. The first license checked out within a session will be based on your preferences and what capabilities are being requested. For all applications other than the first (subsequent) one opened (within ANSYS Workbench), ANSYS licensing will first look at what other licenses are opened within this session. These subsequent license requests will look at sharing first to satisfy their request: do any other licenses being used within this session fulfill the needed capabilities? If yes, share an existing license. If not, preferences are used and a new, different license is checked out. Example 1: You have one license for Multiphysics and one license for Mechanical, with Multiphysics listed first in your preferences. The first application starts and only needs capabilities in Mechanical. Since Multiphysics contains Mechanical capabilities and is first in your preferences, Multiphysics will be checked out. The second application starts and needs Multiphysics; since Multiphysics is already checked out, the second application will share it with the first. Only the Multiphysics license is consumed in this session.
53
Chapter 4: End-User Settings Example 2: You have one license for Multiphysics and one license for Mechanical, with Mechanical listed first in your preferences. The first application starts and only needs capabilities provided in Mechanical, so Mechanical is checked out. The second application starts and needs capabilities provided on Multiphysics; since (the already in use) Mechanical cannot satisfy its requirements, it checks out Multiphysics. Both a Multiphysics and a Mechanical license are consumed in this session. Restrictions of Single License Sharing You cannot run two concurrency events simultaneously (for example, you cannot mesh one model and solve another simultaneously) with one license. If you are using a license for one application, other applications may still not be able to share that license if those applications require capabilities not supported by the license. For example, you cannot share a Mechanical license with a FLUENT application. Single License Sharing in ANSYS Workbench Applications single license sharing differently: ANSYS Workbench applications handle
The Mechanical Application: You can launch the Mechanical application and move between its components (such as Meshing, Setup, and Solve). The active component will control the license while completing its operations and will release the license as soon as the operation is completed. For example, when you mesh, the Meshing component will control the license during the meshing operation and then immediately release the license when the operation is completed. The other components will remain in a read-only mode while Meshing uses the license, allowing you to view the data in other components but not operate on it.
Note
Applications in read-only mode because of shared licensing do not refresh their license status automatically. Once the shared license is released by the editor that had consumed it, you must trigger Mechanical to query the license status. The most straightforward way to do this is click outside the Mechanical application window and then click back in the window to cause the license availability to be rechecked. The Mechanical APDL Application: This application consumes a license as soon as you launch it, and retains that license until it is finished. If you launch the Mechanical APDL application interactively, the license is retained until you either close the application or issue a PAUSE command at the Mechanical APDL command line. PAUSE allows you to temporarily release the license for another application to use. No other operation other than SAVE or /EXIT is permitted while PAUSED. When the second application has finished and releases the license, issue an UNPAUSE command from the Mechanical APDL command line to resume its use of the license. CFX, FLUENT, AUTODYN, POLYFLOW: These applications consume a license when launched and retain the license until they receive a request from another application to release it. For example, if you open CFX-Pre, CFX-Pre will obtain and control the license. It will retain the license until you close the application or until another application (such as the CFX solver) requests it. AUTODYN and POLYFLOW also provide a manual PAUSE feature that allows you to interrupt AUTODYN or POLYFLOW and release the license, temporarily, for another application to use. To unpause the Mechanical APDL application and resume its use of the license, issue UNPAUSE in Mechanical APDL.
54
Establishing User Licensing Preferences
Separate Licenses
By using the separate licenses method, ANSYS Workbench requires a separate license for each application. By using this method, you can move freely between the many applications that you might require during an analysis in ANSYS Workbench, provided that you have sufficient licenses. You can leave each application running and easily move between them at any point during the analysis, even if one of the applications is actively using the license (such as during a solve process). The disadvantage to this method is that you could potentially consume many licenses. To activate the separate licenses method, choose Use a separate license for each application in the Licensing Preferences dialog box (Start> All Programs > ANSYS 14.0 > ANSYS Client Licensing > User License Preferences 14.0). You must specify the licensing method before starting an ANSYS Workbench session. Examples of Using Separate Licenses You have two Mechanical licenses. When you open and mesh or solve a model in the Mechanical application, you consume one Mechanical license. If you link that Mechanical analysis to a Mechanical APDL system, you would consume a second Mechanical license when you launch the Mechanical APDL application, if you have not closed out of the Mechanical application. Neither of these licenses would then be available for other users until you closed out of one or both of the applications.
4.2.2. HPC Licensing

ANSYS, Inc. offers multiple high performance computing license options, described below. These license options apply to ANSYS, Inc. commercial and academic associate licenses only. These license options do not apply to ANSYS LS-DYNA; see the ANSYS LS-DYNA User's Guide for details on parallel processing options with ANSYS LS-DYNA. The HPC license options below cannot be combined with each other in a single solution; for example, you cannot use both ANSYS HPC and ANSYS HPC Packs in the same analysis solution. See the applicable product documentation for instructions on configuring and running a distributed solution. ANSYS HPC These physics-neutral licenses can be used to run multiple analysis jobs across multiple processors and work with most ANSYS, Inc. applications. Contact your ANSYS sales representative for a complete list of applications that can be used with ANSYS HPC. The Mechanical APDL application allows you to use two processors without using any HPC licenses; ANSYS HPC licenses add to this base functionality. For example, a Mechanical APDL user using twelve processors (or cores) will consume only ten ANSYS HPC tasks. ANSYS HPC licenses do work with ANSYS Workbench's Remote Solve capability; however, ANSYS HPC licenses are not subject to single license sharing as described in ANSYS Workbench Licensing Methods (p. 53). You cannot combine ANSYS HPC licenses with any other type of HPC licenses, including HPC Packs, in the same solution. ANSYS HPC licenses are not valid with academic products; instead, use the appropriate ANSYS Academic HPC license.
55
Chapter 4: End-User Settings ANSYS HPC Packs These physics-neutral licenses can be used to run a single analysis across multiple processors and work with most ANSYS, Inc. applications. Contact your ANSYS sales representative for a complete list of applications that can be used with ANSYS HPC Packs. ANSYS HPC Packs enable parallel for single simulations according to the following schedule: 1 ANSYS HPC Pack per simulation: 8 processors 2 ANSYS HPC Packs per simulation: 32 processors 3 ANSYS HPC Packs per simulation: 128 processors 4 ANSYS HPC Packs per simulation: 512 processors 5 ANSYS HPC Packs per simulation: 2048 processors
You cannot use more than five HPC Packs on a single analysis. Individual HPC Packs cannot be split between multiple users or between multiple analyses. Mechanical APDL allows you to use two processors without using any HPC licenses; ANSYS HPC Pack licenses function independently of this base capability. For example, a Mechanical APDL simulation using a single ANSYS HPC Pack can access up to eight processors (or cores), as noted above, and not ten processors (or cores). HPC Packs do work with ANSYS Workbench's Remote Solve capability; however, HPC Packs are not subject to single license sharing as described in ANSYS Workbench Licensing Methods (p. 53). You cannot combine ANSYS HPC Pack licenses with any other type of HPC licenses, including ANSYS HPC licenses, in the same solution. ANSYS HPC Pack licenses are not valid with academic products. One ANSYS HPC Pack license can be borrowed at a time. Multiple HPC Pack licenses or other HPC licenses cannot be borrowed. GPU acceleration is allowed when using HPC Packs with Mechanical APDL or with the Mechanical Application. GPU acceleration is available on 64-bit Windows and Linux x64 systems only. One HPC Pack enables one GPU, in addition to enabling up to eight traditional processors. For more information on GPU acceleration, see GPU Accelerator Capability in the Mechanical APDL Parallel Processing Guide. Mechanical HPC, CFX Parallel Computing, CFD HPC, etc. These physics-specific licenses will continue to work. The Mechanical APDL application allows you to use two processors without using any HPC licenses; Mechanical HPC licenses accommodate this feature. For example, a Mechanical APDL user with two Mechanical HPC tasks can access four processors/cores. You cannot combine physics-specific HPC licenses with any other type of HPC licenses, including ANSYS HPC or HPC Pack licenses, in the same solution.
4.2.2.1. Specifying HPC License Order

Use the HPC tab to define the order in which HPC licenses are used. By default, the physics-neutral HPC licenses are listed before the physics-specific HPC licenses. If you wish to change the order, select licenses and click the Move up or Move down button to reorder the list.
56
Using License Borrowing
Note
Be aware that you can only use five (5) HPC Packs (a maximum of 2048 processors) for a single analysis. If you configure your distributed analysis such that it requires more than 2048 processors, the HPC Pack licenses will not be used, regardless of how many HPC Pack licenses are available. The analysis will use the next available HPC license category (for example, ANSYS HPC or Mechanical HPC), and will consume as many licenses as necessary to accommodate the specified number of processors.
4.3. Setting Up License Queuing

The License Queuing option allows an ANSYS process to wait (queue) for an available license in the event all licenses are checked out. Activate this option by setting the environment variable ANSWAIT to 1. 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)
The License Queuing option may not be available on all products.
4.4. Using License Borrowing

License borrowing (available only on Windows machines) 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. Before users can take advantage of license borrowing, the site administrator needs to set up the borrowing environment (see Run the ANSYS Borrow Utility (p. 38)). License borrowing is available only if you have borrowable licenses and only on Windows machines; however, the license server machine that is managing the licenses can be any system that ANSYS, Inc. supports as a license server. You cannot run both borrowed and non-borrowed licenses simultaneously. For example, if you borrow licenses but remain connected to a network from which you can use licenses, you will be able to use only the borrowed licenses. Likewise, if the machine on which you borrowed licenses is also a license server from which you could normally use licenses, you would be able to use only the borrowed licenses. You can borrow only one task of any particular license. 1. 2. 3. Connect to the network where the license server machine is running. Launch the client license borrowing utility: Start> Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0. Select Run the ANSYS Borrow Utility. On the Borrow tab, specify the version number and return date. The return date defaults to the third day from the current date. If you change any of the borrowing criteria, the product list will automatically update in five seconds. To update the list immediately, click the Update Delay (sec) button. 4. Select the product(s) you want to borrow. The product list includes add-on features or geometry interfaces. If you do not see a product listed that you think should be available, verify that you have selected the correct version. Click Borrow.
5.
57
Chapter 4: End-User Settings 6. 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. Be sure to verify that you can run the correct product with the borrowed licenses from your machine AFTER you've disconnected from the network. If you encounter any difficulties, reconnect to the network, return the license, and then re-borrow the correct license. 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 client license borrowing utility: Start> Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 14.0. Select Run the ANSYS Borrow Utility. Select the Return tab. Click Return all. If you wish to keep some but not all of the licenses you borrowed, you will need to re-borrow them. 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.
58
Chapter 5: 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 FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility) . The following troubleshooting topics are available: 5.1. Getting Additional License Debug Information 5.2. Gathering Diagnostic Information 5.3. Problem Situations 5.4. Licensing Installation Process Errors 5.5. Licensing-Related Mechanical APDL Launcher Error Messages 5.6. Licensing Error Messages 5.7. ANSYS License Borrowing Errors 5.8. FLEXlm License Log File Errors
5.1. Getting Additional License Debug Information

Use the following suggestions to display or generate additional error messages and debugging information. View the licdebug file. The licdebug file is generated when you run an ANSYS, Inc. application and resides in the .ansys subdirectory under the directory specified by the TEMP environment variable (Windows) or in the $HOME directory (UNIX/Linux). The licdebug filename will vary depending on the product but will follow the format licdebug.<product>.140.out. For example: If a licdebug file already exists and is dated today, the information is appended. If it is dated before today, the existing file will be renamed with a .old extension and a new file will be started. Mechanical APDL (ANSYS): licdebug.ANS_SOLVER.140.out ANSYS Workbench: licdebug.ANS_WB.140.out Mechanical: licdebug.MECH.140.out ANSYS FLUENT: licdebug.FLUENT_SOLVER.140.out ANSYS POLYFLOW: licdebug.POLYFLOW.140.out ANSYS CFX-Pre: licdebug.CFX_PRE.140.out ANSYS CFX Solver: licdebug.CFX_SOLVER.140.out ANSYS CFD-Post: licdebug.CFD_POST.140.out. ANSYS ICEM CFD (includes AI*Environment): licdebug.ICEM_AM.140.out ANSYS Icepak: licdebug.ICE_PAK.140.out ANSYS LS-DYNA: licdebug.DYNA_SOLVER.140.out Connection functionality: licdebug.ANS_PM.140.out
59
Chapter 5: Troubleshooting 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. 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 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 installed a new 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 license manager. In this case, neither the client application nor the license manager is using the changed file. Also confirm that if site or user license preferences were set, the preferences were updated with the new license information. 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.
5.2. Gathering Diagnostic Information

You can use the Gather Diagnostic Information option of the ANSLIC_ADMIN utility to query the system for various pieces of information that may be needed for troubleshooting certain problems. This option collects information about the system as well as about ANSYS licenses and sends all of the information that it collects to the log area. At times it may be necessary to provide the information for technical support. Use the Write to File button at the bottom of the ANSLIC_ADMIN to write a file. Then forward the file to the appropriate person.
5.3. Problem Situations

This section describes problems you may encounter when setting up licensing or running an ANSYS product, as well as actions you can take to correct the problems.
5.3.1. License Manager Will Not Start

If the license manager will not start, perform the tests that are listed below. Perform the tests in the order that they are listed. 1. 2. 3. 4. Check the license.log file in the licensing directory on the license server for errors. See the remainder of this chapter for a list of possible errors and their resolutions. Check the ansysli_server.log file in the licensing directory on the license server for errors. Verify that TCP/IP is installed and configured correctly. Verify that the IP address is static. See Communications Requirements (p. 12) for information about configuring TCP/IP. Verify that the hostid has not changed. If the hostid has changed, you must obtain a new license.
Windows Pentium III Systems The version of FLEXlm used at ANSYS Release 14.0 no longer supports using a CPU ID as the hostid. As a result, if you are using a Windows Pentium III system as a license server, you will need to obtain a new license file to be able to run this release. To obtain your new license, run the Register License Server Information option on the ANSLIC_ADMIN utility on the system you 60
Problem Situations have designated as your license server. Send the resulting file LICSERVER.INFO to your ANSYS sales representative. We will then supply you with a new license file. Linux 32 and Linux x64 Systems Linux 32 and Linux x64 systems running the ANSYS, Inc. License Manager require the Linux Standard Base (LSB) package. If this package is missing, you will see one of the following errors when the license manager attempts to run:
/lmgrd -h ./lmgrd: No such file or directory
In this case, try installing the LSB package from the Linux installation media. Three-Server Environment In a three-server environment, you could also see a message similar to 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. 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 ANSLIC_ADMIN 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 ANSYS, Inc. 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 in License Manager Will Not Start (p. 60).
Caution
When you see this message, do NOT press the Start the ANSYS, Inc. License Manager button again.
5.3.2. License Manager Will Not Stop

When you attempt to stop the license manager, it may not stop immediately. You should use the Stop the ANSYS, Inc. License Manager option of the ANSLIC_ADMIN utility to stop the license manager. We do not recommend stopping the license manager manually; however, if you choose to do so, you must stop the components in the following order: 1. 2. 3. ansysli_monitor Licensing Interconnect (ansysli_server) FLEXlm components (lmgrd first, followed by ansyslmd)
5.3.3. License Manager Will Not Stop in a Three-Server Environment

When you attempt to stop the license manager in a three-server environment, the license manager does not stop immediately. You will see a message stating that the currently-installed license file is a three-server license file. With three-server license files, the license manager could take 60 seconds or
61
Chapter 5: Troubleshooting longer to successfully stop. Wait at least 60 seconds. When the license manager has successfully stopped, the ANSLIC_ADMIN status window will show that it is stopped.
5.3.4. The Application Does Not Show the Correct License(s)

If you do not see the correct licenses in your application, in ANSLIC_ADMIN's Set License Preferences for User option, or in the Mechanical APDL Product Launcher, check the following: 1. If you received a new license but your application does not recognize it, you may need to reset your preferences. If you had previously set your license preferences, select Set License Preferences for User from the ANSLIC_ADMIN utility and add the new license to your list in the desired order. If you do not see the correct licenses in the ANSLIC_ADMIN's Set License Preferences for User option or in the Mechanical APDL Product Launcher, and you updated your product order at a previous release, you may need to manually update your product order again. Use the Specify Product Order option under ANSLIC_ADMIN's Set Site Preferences. On the license server machine: 1. 2. Select the Reset to Default button to see the current release's default product order. Reorder the products as you wish, including any new products.
2.
For more information on setting product order, see Specify Product Order (p. 44). For information on setting user license preferences, see Establishing User Licensing Preferences (p. 52).
5.3.5. I Do Not See an HPC Product Category in the Specify Product Order or the Set License Preferences for User Dialogs
If your site has HPC licenses but you do not see an HPC Product Category in the Specify Product Order or the Set License Preferences for User dialog boxes, you may already have site license preferences set (via the Specify Product Order option) from an earlier release. To correct this problem, reset the site preferences again after installing the current release by selecting the Reset to Default button and then resetting your product order preferences.
5.3.6. FLEXlm Log File Shows Unexpected Messages When the License Manager Is Stopped
On Windows systems, you may see unexpected error messages in the FLEXlm licensing log file when you shut down the license manager. Messages similar to the following could appear: 13:47:49 (lmgrd) Shutting down ansyslmd pid=1860 because of signal 15 13:47:49 (lmgrd) Can't connect to the license server system. Shutdown ansyslmd failed. 13:47:49 ((lmgrd)) 13:47:49 Loop info:(lmgrd) Cannot read data from license server system. (16,10009:10054 "WinSock: Connection reset by peer") MT:0 VD_HB:5913:47:49 (lmgrd) reset:0Can't shutdown the license server system. Shutdown ansyslmd failed. clients:013:47:49 (lmgrd) fd's:0EXITING DUE TO SIGNAL 15 13:47:49 (lmgrd) ansyslmd exited with status 58 () 13:47:49 (lmgrd) Since this is an unknown status, license server 62
Problem Situations 13:47:49 (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon. 13:47:49 (lmgrd) EXITING DUE TO SIGNAL 1 13:47:49 (lmgrd) Can't remove statfile C:\Documents and Settings\All Users\Application Data\Macrovision\FLEXlm\lmgrd.620: errno No such file or directory These or similar messages in the FLEXlm log file can be safely ignored in most cases. You can verify that the service is shown as stopped, and that the ansysli_server, ansysli_monitor, lmgrd, and ansyslmd processes are stopped via Task Manager.
5.3.7. Unable to Check Out Licenses

If the license manager appears to start but you cannot check out any licenses, perform the tests that are listed below. Perform the tests in the order that they are listed. 1. Review the Licensing Interconnect debug log file for more information. Use the View Status/Diagnostic options > View the ANSYS Licensing Interconnect Debug Log File option of the ANSLIC_ADMIN utility (the Server ANSLIC_ADMIN Utility on Windows) to view the file. On the license server machine(s), review the FLEXlm license.log file for error messages. Use the View Status/Diagnostic options > View the ANSYS FLEXlm Debug Log File option of the ANSLIC_ADMIN utility (the Server ANSLIC_ADMIN Utility on Windows) to view the file. If neither log file exists or has a zero length, verify that you have write permissions on the files and on the directory containing the files (the licensing directory by default). If you have borrowed licenses, verify that you are not attempting to check out a non-borrowed license. Once you have borrowed one or more licenses, you will not be able to use non-borrowed licenses until you have returned all borrowed licenses.
2.
3. 4.
You could also encounter problems with obtaining a license if the Licensing Interconnect is still attempting to restart the FLEXlm server. Check the FLEXlm license.log file. If you see the following lines multiple times, try rebooting your license server machine:
(lmgrd) (lmgrd) (lmgrd) (lmgrd) ansyslmd exited with status 28 (Communications error) Since this is an unknown status, license server manager (lmgrd) will attempt to re-start the vendor daemon. REStarted ansyslmd (pid 103864)
5.3.8. Entries in the FLEXlm Options File Are Ignored

If you are using a FLEXlm Options file and the Licensing Interconnect is not recognizing those entries (such as INCLUDE statements), and you are using IP addresses, you must also include the IP address of the system on which the Licensing Interconnect is running.
5.3.9. Jobs Abort When License Manager Goes Down in Three-Server 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.
63
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. 1. 2. 3. 4. 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 ANSYSLI_SERVERS or ANSYSLMD_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 installation media 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 FLEXlm license.log and the licensing interconnect ansysli_server.log files for error messages. See the remainder of this chapter for a list of possible errors and their resolutions.
5. 6. 7.
8. 9.
5.3.10. Licensing Log File Not Created

On Windows, if the license manager starts and licenses can be taken from the license server, but the FLEXlm licensing log file and the ansysli_server.log file are not written, check the Administrator account. Verify that the Administrator (as well as the individual user) has write privileges to the directory where the log files are to be written.
5.3.11. Queuing Does Not Work

If queuing does not work, refer to the following list of possible causes and corrections: Verify that the environment variable ANSWAIT is set to 1. The license manager is down. In this case, use ANSLIC_ADMIN to start the license manager. The hostname is mistyped in the ansyslmd.ini file or the ANSYSLMD_LICENSE_FILE environment variable. If so, correct the name and retry. You are not licensed for the requested feature. In this case, request a product for which you are licensed.
64
Problem Situations All licenses for the requested feature are reserved in the license options file. If so, have the license administrator correct the license options file. The user is excluded via the license options file from using the licenses for the feature(s) that are installed on this machine. You are running an application that does not support queuing.
5.3.12. The FLEXlm Utility lmutil Does Not Shut Down License Manager
If you attempt to use the FLEXlm utility lmutil from an earlier release (such as the FLEXlm 10.8.8 version of the daemons) to shut down the ANSYS, Inc. Release 14.0 License Manager, you may see the prompt to shut down the license manager repeatedly:
lmutil - Copyright (c) 1989-2008 Acresso Software Inc. All Rights Reserved. [Detecting lmgrd processes...] Port@Host 1) 1055@pghxpuser7 Are you sure (y/n)? Vendors ansyslmd y
If the current version of the lmutil is not in the licensing directory, the older version of lmutil may or may not shut down the ansyslmd daemon, but it will not shut down the lmgrd daemon. To correct this error, use the most current version of lmutil to shut down the license manager.
5.3.13. The FLEXlm Utility lmcksum May Give Misleading Information

The FLEXlm utility lmcksum may give misleading information. Do not rely on its results to verify the accuracy of your license file.
5.3.14. The Mechanical APDL Launcher is Excessively Slow to Start

If the Mechanical APDL launcher takes an excessively long time to startup (Windows only), make sure the hostnames in the ansyslmd.ini file and in the ANSYSLMD_LICENSE_FILE and the ANSYSLI_SERVERS environment variables are typed correctly and that the hosts specified by the hostnames exist. Replacing hostnames with IP addresses may improve the speed as well. Also verify that the port number is correct.
5.3.15. Mechanical APDL Launcher is Not Using ANSYS140_PRODUCT Environment Variable Correctly
If the Mechanical APDL Product Launcher does not use the product specified by the ANSYS140_PRODUCT environment variable the first time that the launcher is run, you may need to clear your profiles and settings. In the launcher, choose Options >Delete All Settings/Profiles. This option will remove any profiles you have saved for this release, and revert back to using the ANSYS140_PRODUCT setting. Please see the discussion on Launcher Menu Options in the Operations Guide for more details on using the Delete All Settings/Profiles option before choosing this option.
5.3.16. Cannot Run a Product Listed in the Mechanical APDL Product Launcher
When running the Mechanical APDL Product Launcher, if you see the products listed correctly under the License field but are not able to run a product (you may see various error messages), the FLEXlm
65
Chapter 5: Troubleshooting license path (usually <port>@<host>) may not be specified correctly. If you see the products listed but are not able to run a product, select Tools> Display License Status and review the FLEXlm license path for errors.
5.3.17. Remove a Client Option Does Not Work

Due to FLEXlm limitations, the Remove a Client option may not work correctly for products running in the Workbench environment. If it does not, you will need to shut down and restart the license manager in order to remove a client.
5.3.18. No Licensing Interconnect or FLEXlm Path Available from Display the License Status Option
If you select the Display the License Status option from the ANSLIC_ADMIN utility and see a message stating that the Licensing Interconnect or FLEXlm path is empty, try the following: 1. Use the Specify the License Server Machine option of the ANSLIC_ADMIN utility to specify the missing Licensing Interconnect or FLEXlm port number. (On Windows, use the Client ANSLIC_ADMIN utility.) If the machine is already specified but the error message states that no FLEXlm path has been specified, the FLEXlm port number may be missing from the license server specification shown in the Specify the License Server window. Add the machine's FLEXlm port number using the Specify the License Server Machine option to add this machine to your FLEXlm license path.
Note
This particular machine may have been configured to run the ANSYS Licensing Interconnect without starting FLEXlm. Verify that FLEXlm is running on this machine before changing this setting. 2. Check the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable setting. If this environment variable is set, the ANSYS, Inc. License Manager will not use the license server machine specifications in the ansyslmd.ini file. In this case, only the ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS environment variable settings will be used.
See Specify the License Server Machine (p. 34) for more information on specifying license server machines.
5.3.19. Cannot Enter Data in Text Fields

On some SUSE Linux systems and possibly other systems, if you cannot enter data in text fields during the installation or when using the ANSLIC_ADMIN utility, you may be encountering a Tcl incompatibility. To correct the problem, unset the following environment variables before running the installation or the ANSLIC_ADMIN utility: QT_IM_MODULE XMODIFIERS GTK_IM_MODULE You should reset these environment variables when you are finished running the installation or using ANSLIC_ADMIN. Do not permanently unset these environment variables as doing so could affect other applications.
66
Licensing-Related Mechanical APDL Launcher Error Messages
5.3.20. Cannot See the Entire Run License Wizard Dialog Box
On some SUSE Linux systems and possibly other systems, you may not be able to see the entire dialog box when you select Run License Wizard from the ANSLIC_ADMIN utility. To correct the problem, resize the window vertically until the entire dialog box is visible.
5.4. Licensing Installation Process Errors

If you encounter a problem during the configuration steps of the licensing installation process that results in a failure or abort, or if you are concerned that the licensing installation did not complete correctly, try running the Complete Unfinished Licensing Installation Configuration option from the ANSLIC_ADMIN utility's Tools menu. This option will only repeat the licensing installation configuration steps that correspond to the version of the ANSLIC_ADMIN utility you are running (client or server) and cannot be used as an alternative means of installing.
5.5. Licensing-Related Mechanical APDL Launcher Error Messages

Some messages that you see from the Mechanical APDL launcher are related to product licensing. These messages follow. For additional Mechanical APDL launcher error messages, see the Troubleshooting section of the ANSYS, Inc. Installation Guide for your platform. Various Messages If you see any licensing-related 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. If any of these messages appear, perform the tests that are listed below in the order presented: 1. Verify that the license manager is running on all license servers by viewing the status window on the ANSLIC_ADMIN utility. If the license manager is not running, start it on the license server machine(s). Check the license.log and ansysli_server.log file on each license server for errors. Run Mechanical APDL (ANSYS) from a command prompt to check for additional error messages. Example (Windows):
"C:\Program Files\Ansys Inc\V140\ANSYS\bin\intel\ansys140"
2. 3.
Check the Mechanical APDL (ANSYS) Output window for error messages and additional information about the failure. 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 client licensing directory and that it contains the correct hostname and port numbers of the license server. If this file does not exist, see Specify the License Server Machine (p. 34) to specify the license server. If the ANSYSLMD_LICENSE_FILE variable is used to specify the license server, verify that the hostname of the license server is correct.
67
Chapter 5: Troubleshooting 6. Verify that the correct version of the license manager daemons (lmgrd and ansyslmd) is being used. The current version is FLEXlm 11.9.1.
***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.
5.6. Licensing Error Messages

*** Licensed number of users already reached. You may have reached the number of ANSYS product tasks that you have licensed. Wait until a task has been freed up and try again. If this error occurs on a regular basis, you may want to talk to your ANSYS sales representative about obtaining additional licenses. This error may also occur when licenses have been reserved for certain users, or when certain users have been excluded from licenses via the license options file. *** 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. or ***Unable to connect to FLEXlm 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 install the license manager and a license file, and it appears that the server is running, but you cannot connect to your license server, try rebooting. If you think the license manager should already be running, check the FLEXlm license log file and the ansysli_server.log file for errors. Some other possible causes for this error include: If Windows Firewall is enabled on the license server, ansyslmd.exe, lmgrd.exe, and ansysli_server.exe need to be included in the exceptions. 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.
68
Licensing Error Messages 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 variable ANSYSLMD_LICENSE_FILE All of the installed license files have expired.
If none of the above causes are applicable, the Licensing Interconnect may not have started because it was not able to start the FLEXlm server or may have exited after failing to restart the FLEXlm server. Check the FLEXlm license log file (license.log). If you see the following lines multiple times, try rebooting your license server machine:
(lmgrd) (lmgrd) (lmgrd) (lmgrd) ansyslmd exited with status 28 (Communications error) Since this is an unknown status, license server manager (lmgrd) will attempt to re-start the vendor daemon. REStarted ansyslmd (pid 103864)
*** 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 client machine has changed. The date should never be set ahead or behind the actual date. *** 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.
69
Chapter 5: Troubleshooting 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. *** No such feature exists. A license does not exist for the requested product. Verify that the ANSYSLMD_LICENSE_FILE environment variable and the ansyslmd.ini file are pointing to the correct license server. Verify that you are running the correct product. Use the Set License Preferences for User option of the ANSLIC_ADMIN utility to specify the products and the product order you want to use. 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 11.9.1.
Failover feature <product name> specified in license preferences is not available. You may see this message if you specify a particular license (such as with the -p command line option on the Mechanical APDL (ANSYS) product) and no license for that product is currently available in the license path. Check the following: The license may have expired. All of your licenses may be in use. You do not have the specified license. The license is not included in your license preferences as set with the Specify License Preferences for User in the ANSLIC_ADMIN utility. Your TECS for this version may have expired.
*** 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 Mechanical APDL (ANSYS), use the -v command line option. *** Invalid (inconsistent) license key The license manager daemons for this release are FLEXlm 11.9.1 (lmgrd and ansyslmd). Verify that you are not using the license manager daemons supplied with a previous release. This error can also occur if the license key contains incorrect characters or format (sometimes caused by transferring the file). Invalid license file: None of the hostnames in the license file match the system hostname.
70
Licensing Error Messages This message occurs when you install the license file if the hostname of the system you are running on does not match any of the hostnames in your license file. Some possible reasons why this can happen include: You are attempting to run on a system that has not been included in your license. The hostname of the system you are working on has been changed since it was used to generate the license information. A typographical error was introduced when the hostname was entered when creating the license key. On some newer Linux machines, the system hostname is not listed consistently in the /etc/hosts file. When you run the Register License Server Information or the Display the License Server Hostid option of the ANSLIC_ADMIN utility, the utility uses the localhost information instead of the correct system hostname. An example of the problematic /etc/hosts file might look like this:
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost abclinux5 10.99.9.99 abclinux5 abclinux5 [root@abclinux5 ~]$ hostname abclinux5 [root@abclinux5 ~]$ hostname -s localhost [root@abclinux5 ~]$
In this example, the Register License Server Information or the Display the License Server Hostid option would incorrectly use the localhost information. To correct the problem, you need to edit the /etc/hosts file and change the order of the hostname lines. The example shown above would then look like this:
# Do not remove the following line, or various programs # that require network functionality will fail. 10.99.9.99 abclinux5 abclinux5 127.0.0.1 localhost.localdomain localhost abclinux5 [root@abclinux5 ~]$ hostname abclinux5 [root@abclinux5 ~]$ hostname -s abclinux5 [root@abclinux5 ~]$
In the corrected example, the Register License Server Information or the Display the License Server Hostid option would correctly use the abclinux5 hostname. *** Local checkout filter rejected request. View the license debug log files (FLEXlm license.log and the Licensing Interconnect ansysli_server.log) 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/Linux) or the services file (Windows). ***The ANSYS license manager server is down. Unless a connection is reestablished, ANSYS will exit in nn minutes. A message similar to this one occurs in a one-server license environment if your license manager has quit running. In a three-license server environment, the ANSYS, Inc. license manager must be running on at least two of the three license server machines at all times. If two of the license server
71
Chapter 5: Troubleshooting 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. ***FLEXlm version of vendor daemon is too old. The license manager daemons at this release are FLEXlm 11.9.1 (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>@<ipaddress> when specifying the server.
***The license server is taking too long to respond. The application has stopped waiting for a reply. The license server may be experiencing a high demand or a temporary outage. Try again later. If you see the above message and the server is not experiencing any demand, a virus scanner may be blocking connections to your license server. Rebooting your license server may also resolve the issue. Could not bind socket on port 2325. Address already in use. If you see the above message in your licensing log file, your operating system was not able to free a port before the timeout period expired. This situation could happen if the port is being used by some other application, or after you shut down a server if you did not wait long enough for the ports to free before restarting it. This situation appears to occur more frequently on Sun systems,
72
ANSYS License Borrowing Errors because these operating systems have a default timeout period to free a port that may not be sufficient. On Sun systems, the default is 4 minutes for the CLOSE_WAIT and TIME_WAIT port states. You can adjust the default timeout period to 30 seconds by issuing either of the following commands as appropriate for your operating system level:
ndd /dev/tcp -set tcp_time_wait_interval 30000 ndd /dev/tcp -set tcp_close_wait_interval 30000
Consult your system administrator before making changes to your default operating system settings or to determine which command is appropriate for your operating system level. ***Failed to retrieve license preferences. Please be sure that you are able to connect to the license server. If you attempt to set your license preferences and the client information is at a higher release than the server information, you may see this message. To verify, see the getuserprefs.log file (on UNIX/Linux machines, in .ansys in your home directory; on Windows, in %TEMP%\.ansys). Note the last lines in the example below:
2009/08/24 17:18:00 INFO Not connected to a local port. 2009/08/24 17:18:00 NEW_CONNECTION Connected to license server: 2325@linux10.ansys.com. ANSYSLI_SERVERS: 2325@linux10.ansys.com FLEXlm Servers: 1055@linux10.ansys.com 2009/08/24 17:18:01 SITE_PREFS 2009.0806 Your version of the ANSYS license manager software is out of date. Please download and install the current ANSYS license manager from the ANSYS Customer Portal. The version of the license server 2325@linux10.ansys.com [1.1.2] must be greater or equal to the client ALI_UTIL version [1.1.3].
***License File filename has changed. Please do a reread to update the server. The license file or the FLEXlm options file has been changed since the last restart of the license manager or reread of the license file. The changes will not be available until you restart the license manager or reread the license file. If you are running the ANSYS Licensing Interconnect and FLEXlm independently and have cached the license file, the cached license file may be out of date. Restart FLEXlm or reread the license file to update the cached license file. If you make changes to the license file, in addition to rereading the license file in FLEXlm, you must also recache the license file in the Licensing Interconnect by restarting the Licensing Interconnect or by using the Reread the License Manager Settings option of ANSLIC_ADMIN.
5.7. ANSYS License Borrowing Errors

***Unable to return <Product>, encountered feature not found attempting to return license feature <Product.> If you see the above message when attempting to return a borrowed license before the expiration date, the -2 -p license manager startup option might have been set. The -2 -p option is not supported. If you are running an earlier release, you must manually unset the option. In this case, you may also see the following in the log file: UNAUTHORIZED lmremove request from <user> at node <host>. You may also see the above message if the existing server specification does not contain the machine from which the license was borrowed. To correct the problem, add the machine to the server speRelease 14.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
73
Chapter 5: Troubleshooting cification. If the ANSYS Borrow Utility is open when the server specification is changed to contain this server, you must close and restart the utility after changing the license server specification and before returning the borrowed license.
5.8. FLEXlm License Log File Errors

***Not a valid server hostname, exiting. Valid server hosts are: xxx The hostname in the SERVER line of the license file does not match the hostname of the system. In this case, change the hostname in the license file. Other possible causes include: The license file was put on a machine other than the one for which it was created; therefore, the hostname is not correct. The hostname of the license server changed. Change the hostname on the SERVER line of the license file to correct this problem. REMEMBER to send ANSYS the new hostname so that future license files are made with the correct hostname. The license file was put on a machine other than the one for which it was created AND the user changed the machine's ID on the SERVER line but did not change the hostname. If the machine ID is also wrong, you will also see a message about the wrong hostid on SERVER line after correcting the hostname. The wrong hostname was used to create the license file. As long as the correct machine ID was used, you should be able to change the hostname on the SERVER line of the license file to fix this problem. REMEMBER to send ANSYS the correct hostname so that future license files are made with the correct hostname.
***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.
***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.
74
FLEXlm License Log File Errors 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).
75
76
Chapter 6: Product Variable Table

The following table shows all ANSYS, Inc. products and their associated feature name as used in the INCREMENT lines. This table is provided as a reference for both current and legacy products. Not all products listed are generally available but are included here for customers running an older release. Please contact your ANSYS sales representative or technical support representative for details regarding product availability.
Table 6.1 Product/Feature Names for Licensed Products

Product ANSYS Multiphysics ANSYS Multiphysics/LS-DYNA ANSYS Multiphysics 1 ANSYS Multiphysics 2 ANSYS Multiphysics 3 ANSYS Multiphysics/LS-DYNA PrepPost ANSYS Mechanical ANSYS Mechanical/Emag ANSYS Mechanical/FLOTRAN ANSYS Mechanical/LS-DYNA ANSYS Mechanical/Emag/LS-DYNA ANSYS Mechanical/CFD-Flo/LS-DYNA ANSYS Mechanical/LS-DYNA PrepPost ANSYS Mechanical/Emag/LS-DYNA PrepPost ANSYS Mechanical/CFD-Flo ANSYS Structural ANSYS Structural/Emag ANSYS Structural/FLOTRAN ANSYS Structural/Emag/CFD-Flo ANSYS Structural/LS-DYNA ANSYS Structural/Emag/LS-DYNA ANSYS Structural/CFD-Flo/LS-DYNA ANSYS Structural/Emag/CFD-Flo/LS-DYNA ANSYS Structural/LS-DYNA PrepPost ANSYS Structural/Emag/LS-DYNA PrepPost Feature Names ane3fl* ane3flds* ane3fl1* ane3fl2* ane3fl3* ane3fldp* ansys* ane3* anfl* ansysds* ane3ds* anflds* ansysdp* ane3dp* ancfx* struct* ste3* stfl* ste3fl* structds* ste3ds* stflds* ste3flds* structdp* ste3dp*
ANSYS Mechanical/CFD-Flo/LS-DYNA PrepPost anfldp*
77
Chapter 6: Product Variable Table Product ANSYS Structural/CFD-Flo/LS-DYNA PrepPost ANSYS Structural/Emag/CFD-Flo/LS-DYNA PrepPost ANSYS Structural/CFD-Flo ANSYS Professional NLT ANSYS Professional NLS ANSYS Professional NLT Emag ANSYS Professional/FLOTRAN ANSYS Professional/Emag/FLOTRAN ANSYS Emag ANSYS Emag HF ANSYS Emag/FLOTRAN ANSYS FLOTRAN ANSYS Mechanical PrepPost ANSYS PrepPost/LS-DYNA PrepPost ANSYS LS-DYNA ANSYS LS-DYNA PrepPost ANSYS LS-DYNA PC ANSYS Multiphysics Solver ANSYS Mechanical Solver ANSYS Professional Solver ANSYS Structural Solver ANSYS FLOTRAN Solver ANSYS Emag Solver ANSYS DesignSpace Batch Child ANSYS Emag Batch Child ANSYS FLOTRAN Batch Child ANSYS Mechanical Batch Child ANSYS Multiphysics Batch Child ANSYS Professional Batch Child ANSYS Structural Batch Child ANSYS DesignSpace Entra ANSYS DesignSpace Structural ANSYS DesignSpace ANSYS Workbench SDK Feature Names stfldp* ste3fldp* stcfx* prf* prfnls prfe3* prffl* prfe3fl* emag* emaghf* emagfl* flotran* preppost* prpostdy* dyna* dynapp* dynapc* mpba* meba* prba* stba* flba* e3ba* debach e3bach flbach mebach mpbach prbach stbach caewbpl1 dsstruct caewbpl3 caewbplh, caetmpl, piautoin, pimedesk, pisolwor, pisoledg, piproe, dsdxm caewbplh, caetmpl
ANSYS Workbench Runtime
78
Product ANSYS CFX-CAD2Mesh with DesignModeler
Feature Names cad2mesh, aimed, aioutput, aiprism, aitetra, agppi, aiiges, aiacis, aipips, aidxf, acfx_pre cad2mesh acfx_flotran_upgrade acfx_anymodule acfx_anymodule acfx_pre, acfx_solver, acfx_nolimit, acfx_parallel acfx_mfr acfx_multiphase acfx_radiation acfx_advanced_turbulence, acfx_turbulence_transition acfx_par_proc acfx_pre, acfx_solver acfx_nolimit, acfx_mfr, acfx_multiphase, acfx_combustion, acfx_radiation, acfx_parallel, acfx_advanced_turbulence, acfx_turbulence_transition acfx_post acfx_bldmdlr acfx_turbogrid acfd acfd_cfx acfd_cfx_solver acfd_fluent acfd_fluent_solver acfd_v2f acfd_fcell acfd_fcell acfd_ib acfd_polyflow acfd_polyflow_extrusion acfd_polyflow_blowmolding acfd_polyflow_solver acfd_rif
ANSYS CFX-Mesh ANSYS CFX FLOTRAN Upgrade ANSYS CFX-Flo ANSYS CFX PrepPost ANSYS CFX Basic Capability Solver ANSYS CFX Multiple Frames of Reference ANSYS CFX Multi-Phase Flows ANSYS CFX Radiation Models ANSYS CFX Advanced Turbulence Models ANSYS CFX Parallel Computing ANSYS CFX Full Capability Solver
ANSYS CFX Reacting and Combusting Species acfx_combustion
ANSYS CFD-Post ANSYS BladeModeler ANSYS TurboGrid ANSYS CFD ANSYS CFX ANSYS CFX Solver ANSYS FLUENT ANSYS FLUENT Solver ANSYS FLUENT V2F Module ANSYS FLUENT PEM Fuel Cell Module ANSYS FLUENT SOFC Fuell Cell Module ANSYS FLUENT Immersed Boundary Module ANSYS POLYFLOW ANSYS POLYFLOW Extrusion ANSYS POLYFLOW BlowMolding ANSYS POLYFLOW Solver ANSYS CFX-RIF Flamelet Library Generator
79
Chapter 6: Product Variable Table Product ANSYS Vista TF ANSYS CFD Solver ANSYS CFD PrepPost ANSYS CFD-Flo ANSYS CFD HPC ANSYS CFD MHD ANSYS HPC ANSYS HPC Pack ANSYS Robust Design Pack ANSYS ICEM CFD Feature Names acfd_vista_tf acfd_solver acfd_preppost acfd_flo acfd_par_proc acfd_mhd anshpc anshpc_pack ans_rdpack aienv, aienvsub, aiprism, aiiges, aiacis, aiedgeom, aioutcfd, aidxf aiaddon aihexa aioutput, aiiges, aiacis, aiedgeom, aioutcfd, aidxf aioutput, aiiges, aiacis, aipiug, aioutcfd, aidxf aioutput, aiiges, aiacis, aipicat, aioutcfd, aidxf aioutput, aiiges, aiacis, aipipro, aioutcfd, aidxf aioutput, aiiges, aiacis, aipiidea, aioutcfd, aidxf aioutput, aiiges, aiacis, aipisw, aioutcfd, aidxf aioutput, aiiges, aiacis, aipise, aioutcfd, aidxf aimed, aihexa, aimshcrt, aibfcart, aiiges, aiacis, aioutput, aioutcfd, aidxf, aiquad, aimshcrt aimed, aitetra, aiprism, aiiges, aiacis, aioutput, aioutcfd, aidxf, aiquad aimed, aiquad aimed, aiglobal aimed, aiautmdl, aiautmsh aihexct5, aihexct5e aiiges, aiacis, aimed, aitetra, aimshprt
ANSYS ICEM CFD AddOn ANSYS ICEM CFD Hexa Add-on ANSYS ICEM CFD Basic with Advanced Geometry Support ANSYS ICEM CFD Basic with Geometry Interface for NX ANSYS ICEM CFD Basic with Geometry Interface for CATIA V4 ANSYS ICEM CFD Basic with Geometry Interface for Creo Parametric ANSYS ICEM CFD Basic with Geometry Interface for SDRC-IDEAS ANSYS ICEM CFD Basic with Geometry Interface for SolidWorks ANSYS ICEM CFD Basic with Geometry Interface for SolidEdge ANSYS ICEM CFD Hexa
ANSYS ICEM CFD Tetra/Prism
ANSYS ICEM CFD Quad ANSYS ICEM CFD Global ANSYS ICEM CFD Autohexa ANSYS ICEM CFD Hexa CAA V5 Based (for CATIA V5) ANSYS ICEM CFD Mesh Prototyper
80
Product ANSYS ICEM CFD BF-Cart ANSYS ICEM CFD Cabin Modeler Stand-alone ANSYS ICEM CFD IC3M Stand-alone ANSYS ICEM CFD Comak ANSYS ICEM CFD Visual3 / PV3 ANSYS ICEM CFD OptiMesh ANSYS AUTODYN-2D ANSYS AUTODYN-3D ANSYS AUTODYN ANSYS AUTODYN HPC ANSYS AUTODYN PrepPost ANSYS Explicit STR ANSYS AI*Environment Direct CAD Interface - CATIA V4 Direct CAD Interface - SDRC-IDEAS ANSYS ICEM CFD Parasolid Reader Direct CAD Interface - Creo Elements/Pro Direct CAD Interface -Solid Edge Direct CAD Interface -SolidWorks Direct CAD Interface - NX
Feature Names aibfcart, aimed aimed, aitetra, aiprism, aicabin aimed, aitetra, aihexa, aiic3m, aiic3msb aimed, aicomak aivis3 aioptmsh acdi_ad2dfull acdi_ad3dfull, int4nas acdi_ad3dfull, acdi_adhpc, acdi_adprepost, int4nas acdi_adhpc acdi_adprepost acdi_explprof aienv, aienvsub aipicat aipiidea aipips aipipro aipise aipisw aipiug
Batch Meshing Module Add-on to AI*Environ- batmesh, bmeshsub ment CFD Utilities Add-on for AI*Environment ANSYS Connection for CATIA V4 ANSYS Connection for CATIA V5 ANSYS Connection for Parasolid ANSYS Connection for Creo Parametric ANSYS Connection for SAT ANSYS Connection for NX Geometry Interface for Autodesk Geometry Interface for CATIA V4 Geometry Interface for CATIA V5 Geometry Interface for Parasolid Geometry Interface for Creo Parametric Geometry Interface for SAT Geometry Interface for SolidEdge aiprism, aioutput, aioutcfd concatia concatv5 conpara conproe consat conug piautoin picatia picatv5 rdpara piproe rdacis pisoledg
81
Chapter 6: Product Variable Table Product Geometry Interface for SolidWorks Geometry Interface for NX Geometry Interface for Creo Elements/Direct Modeling CADNexus/CAPRI CAE Gateway for CATIA V5 ANSYS SpaceClaim Direct Modeler ANSYS SpaceClaim CATIA V5 Interface Geometry Interface for JT Geometry Reader for Creo Elements/Pro ANSYS Composite PrepPost TAS TASTEC TAS Pultrusion TAS Sinda/3D TASStress FET Module for TAS ICEBoard ICEChip ANSYS DesignModeler ANSYS DesignXplorer ANSYS CAE Templates ANSYS Fatigue Module Pressure Equipment Module ANSYS Meshing ANSYS Extended Meshing ANSYS TGrid ANSYS LS-DYNA Parallel ANSYS Mechanical HPC ANSYS MeshMorpher ANSYS MeshMorpher Target Geometry Module ANSYS Academic Associate ANSYS Academic Associate CFD ANSYS Academic Associate HPC ANSYS Academic Research ANSYS Academic Research CFD ANSYS Academic Research LS-DYNA ANSYS Academic Research Offshore/Marine Feature Names pisolwor piug 1spacdes capricatv5 a_spaceclaim_dirmod a_spaceclaim_catv5 a_jt_reader a_proe_reader acpreppost ahti_tas ahti_tastec ahti_tas_pultrusion ahti_tas_sinda3d ahti_tas_stress ahti_tas_fet anti_taspcb ahti_ptd agppi dsdxm caetmpl dfatigue preqmo amesh amesh_extended amesh_tgrid dysmp mechhpc paramesh pmeshgeo aa_a*, aa_mcad aa_a_cfd, aa_mcad aa_a_hpc aa_r*, aa_mcad aa_r_cfd, aa_mcad aa_r_dy*, aa_mcad aa_r_om, aa_mcad, aa_r_aql
ANSYS Interface for Team Center Engineering pdmiman
82
Product ANSYS Academic Research AUTODYN ANSYS Academic Research Mechanical ANSYS Academic Research HPC ANSYS Academic Research LS-DYNA HPC ANSYS Academic Research POLYFLOW ANSYS Academic Research Electronics Thermal ANSYS Academic Teaching Introductory ANSYS Academic Teaching Advanced ANSYS Academic Teaching Mechanical ANSYS Academic Teaching CFD ANSYS Academic Meshing Tools ANSYS Academic CFD Turbo Tools ANSYS Academic Fuel Cell Tools ANSYS Academic Mechanical HPC ANSYS Academic AUTODYN HPC ANSYS Academic CFD HPC ANSYS Rigid Dynamics EKM Workgroup 1
Feature Names aa_r_ad, aa_mcad aa_r_me, aa_mcad aa_r_hpc aa_dy_p aa_r_pf, aa_mcad aa_r_et, aa_mcad aa_t_i*, aa_mcad, aa_ds aa_t_a*, aa_mcad, aa_ds aa_t_me*, aa_mcad, aa_ds aa_t_cfd, aa_mcad aa_mesh, aa_mcad aa_turbo aa_fcell aa_p_me aa_p_ad aa_p_c kinemat, dynamics ekm_wg_server, ekm_named_user, ekm_user, ekm_test_server, ekm_test_named_user, ekm_test_user ekm_wg_server, ekm_named_user, ekm_user, ekm_test_server, ekm_test_named_user, ekm_test_user ekm_server, ekm_test_server, ekm_test_named_user, ekm_test_user ekm_desktop ekm_datalink_server, ekm_datalink_user, ekm_datalink_named_user acdi_asas, acdi_asaslink, acdi_asasnl, acdi_asas-vis, acdi_beamst, acdi_comped, acdi_loco, acdi_maxmin, acdi_post, acdi_postnl, acdi_prebeam, acdi_prenl, acdi_response, acdi_xtract, preppost
EKM Workgroup 2
EKM Enterprise Server
EKM Desktop EKM Datalink
ANSYS ASAS
83
Chapter 6: Product Variable Table Product ANSYS BEAMCHECK ANSYS ASAS-OFFSHORE Feature Names acdi_asas-vis, acdi_beamst acdi_asas, acdi_asaslink, acdi_asasnl, acdi_asas-vis, acdi_beamst, acdi_comped, acdi_fatjack, acdi_loco, acdi_mass, acdi_maxmin, acdi_post, acdi_postnl, acdi_prebeam, acdi_prenl, acdi_response, acdi_splinter, acdi_wave, acdi_windspec, acdi_xtract, preppost acdi_concrete acdi_panel acdi_femgv, acdi_fgv_asas acdi_aqwags, acdi_aqwaline, acdi_aqwawave, acdi_hydrodiff acdi_aqwadrft, acdi_aqwafer, acdi_aqwags, acdi_aqwalbrm, acdi_aqwaline, acdi_aqwanaut, acdi_aqwawave, acdi_hydrodiff acdi_aqwaline, acdi_aqwags, acdi_aqwawave, acdi_aqwafer, acdi_aqwalbrm, acdi_hydrodiff acdi_aqwaline, acdi_aqwawave, acdi_cdags, acdi_cd-drift, acdi_cdfer, acdi_cd-libr, acdi_cdnaut, acdi_hydrodiff acdi_fatjack aice_pak aice_mesher aice_solv aice_opt
ANSYS ASAS CONCRETE ANSYS ASAS PANEL ANSYS ASAS FEMGV ANSYS AQWA DIFFRACTION
ANSYS AQWA SUITE
ANSYS AQWA FREQUENCY
ANSYS AQWA SUITE with Coupled Cable Dynamics
ANSYS FATJACK ANSYS Icepak ANSYS Icepak Mesher ANSYS Icepak Solver ANSYS Iceopt
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 in the Mechanical APDL (ANSYS) application. Products listed here use the ANSYS license manager (ansyslmd vendor daemon). ANSYS, Inc. does supply licenses for products that use other license managers, such as Fluent and Ansoft products which are not listed above; however, those products will use their respective license manager. To determine the license manager to which the license applies, see Recognizing an ANSYS, Inc. License File (p. 6)
84
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. The ANSYS, Inc. License Manager consists of three components. The first two are FLEXlm components; the last one is an ANSYS component. See the definitions of each for more information. lmgrd ansyslmd ansysli
ANSYS, Inc. License Manager
ansysli ansysli_client
see Licensing Interconnect A component of the Licensing Interconnect that is run by ANSYS applications on client systems. No user configuration or administration is required or associated with this component. The ansysli_monitor runs on the same machine where the ansysli_server is running and ensures that the license server is functioning correctly. If the license server is not running, ansysli_monitor can restart it. If the server is running but is not responsive, ansysli_monitor can kill and restart it. A component of the Licensing Interconnect that is run on the license server systems. Use ANSLIC_ADMIN to manage (start, stop, etc.). The Licensing Interconnect log file, it provides a chronicle of Licensing Interconnect licensing activity, including problems. The Licensing Interconnect log file is located in the licensing directory by default. Communication channel by which the ANSYS, Inc. applications communicate with the Licensing Interconnect. The default ansysli port number is 2325. An environment variable that may be used to specify the license server machine from which you want to check out a license.
ansysli_monitor
ansysli_server
ansysli_server.log
ansysli port number
ANSYSLMD_LICENSE_FILE
85
Glossary ansyslmd This is one of the FLEXlm components of the ANSYS, Inc. license manager used to process ANSYS product licensing requests, including issuing and returning licenses. ansyslmd, often referred to as the vendor daemon, is started by 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 machine and Modify license manager startup options. ANSYS Support Distributor. In a three-server (redundant triad) 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. The build date is the year, month, and date the ANSYS application 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. ANSYS, Inc. has assigned identifiers to each of the specific areas of functionality in the software. We refer to these identifiers as capabilities, which you may see in ANSYS, Inc. licensing displays and logs. Each capability can be satisfied by at least one license feature; often, multiple license features can satisfy a particular capability. A client is a machine that requests licenses but is not a license server machine (i.e., does not have licenses installed on it). The word feature, when used in the descriptions of the licensing utilities, refers to the ANSYS product. See Product Variable Table (p. 77) for the list of ANSYS products and their corresponding license features. A component of the ANSYS, Inc. license manager used for all ANSYS products. Also called FLEXnet License Manager. The FLEXlm component authenticates and processes all license requests. Typically referred to as the FLEXlm Debug Log File, it contains 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. Communication channel by which the license manager communicates with the client (Licensing Interconnect). The default FLEXlm port number is 1055.
ansyslmd.ini
ASD backup server
borrowable license
build date
Capability
client feature
FLEXlm
FLEXlm license log file
FLEXlm port number
86
floating license
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. IA-32 refers to the Intel architecture, 32-bit processor. IA-64 refers to the Intel architecture, 64-bit processor. 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 license file grants access to run specified products. 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. Install the license file using the Run License Wizard or the Install the License File options of the ANSLIC_ADMIN utility or during the installation process. The actual full license for the product. Typically referred to as the FLEXlm Debug Log File, it contains information relevant to licensing activity. This file provides a way of tracking licensing problems that may occur. The licensing log file is located in the licensing directory by default. Software used for licensing ANSYS, Inc. products. The ANSYS, Inc. License Manager is comprised of two components: the FLEXlm software and the Licensing Interconnect. A FLEXlm file containing license manager-related resource information. This file is created on license server machines 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 options file: Licenses that are reserved for individuals, groups, or machines Those individuals, groups, or machines that are denied access to licenses
IA-32 IA-64 license license borrowing
license file
license key license.log
license manager
license options file
license server machine
A license server machine is a computer 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 (redundant triad) 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.
license task
87
Glossary licensing directory The default location for the licensing files. On UNIX/Linux 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. Communications between the ANSYS applications, lmgrd, and ansyslmd are handled by an intermediary process called the ANSYS Licensing Interconnect. The ANSYS Licensing Interconnect communicates with the FLEXlm license manager to authenticate and process all license requests. Provides a chronicle of Licensing Interconnect licensing activity, including problems. The Licensing Interconnect log file, ansysli_server.log, is located in the licensing directory by default. A group of users that you designate to have the ability to perform license administrative tasks that are considered disruptive. One of the FLEXlm components of the ANSYS, Inc. License Manager, used to process ANSYS product licensing requests, including issuing and returning licenses. LMTOOLS is a Windows-only utility that will perform various license administrator functions, such as listing the users of licensed products. LMTOOLS is no longer sufficient to manage the ANSYS, Inc. License Manager and the Licensing Interconnect. You should use the ANSLIC_ADMIN utility to start or stop the license manager, check the license status, etc. However, if you have well-established processes to manage FLEXlm, you can continue to use LMTOOLS (see Advanced Licensing Configuration Options). lmutil is a FLEXlm-supplied 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. In a three-server (redundant triad) 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 machines are shadow servers (or backup servers). In a one-server network, that server is automatically the master. See license options file. When used in the context of a license file path, the list of places that are searched in order to locate a valid license file. The path is built from values in the ANSYSLMD_LICENSE_FILE environment variable, settings in the ansyslmd.ini file, or an actual license file.
Licensing Interconnect
Licensing Interconnect Log File lmadmin lmgrd
LMTOOLS
lmutil
master server
options file path
88
product variable
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. For Mechanical APDL, the product variable may be set by using the -p command line option, the ANSYS140_PRODUCT environment variable, or the Mechanical APDL launcher. See Product Variable Table (p. 77) for a list of ANSYS products and their associated product variables/feature names. You may designate either one or three machines to be license servers. In a three-server (redundant triad) network, license manager daemons must be running on the majority (2) of the server machines (a quorum) before requests for licenses will be processed. Having multiple machines designated as license servers for an ANSYS product. Redundancy can be achieved either by having three license server machines working together in tandem, where two of the three must be running at all times but serving from a single set of licenses, or by having any number of license server machines 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 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. See backup server. See license task. The timezones keyword as part of the INCREMENT line's VENDOR_STRING specifies which time zone the client needs to be running in. The absence of the timezones keyword indicates that a client can run in any time zone. The format is timezones:X[,Y,Z,...], where X is a numeric value from 023, where 0 represents GMT, and 19 represents EST. Multiple time zones are separated by commas (,): for example, timezones:17,18,19. This keyword cannot be modified by the user. FLEXlm terminology used to refer to the vendor-specific component of the FLEXlm license manager. The ANSYS vendor daemon is ansyslmd.
quorum
redundant (triad) servers
server session log
shadow server task timezones
vendor daemon
89
90
Index
Symbols A
Academic licenses, 37, 52 Agreement number, 48 All licenses reserved, 68 ANS_FLEXLM_DISABLE_DEFLICPATH, 51 ANSLIC_ADMIN utility, 27 definition, 85 display customer number, 48 display license server hostid, 30 display queued licenses, 47 display the license status, 47 editing the FLEXlm license options file, 24 editing the license options file, 41 gather diagnostic information, 48 install license, 32 modify startup options, 45 register license server information, 30 remove a client license, 37 reread the license settings, 34 run the ANSYS borrow utility, 38 run the license wizard, 31 set license preferences, 37 set site preferences, 40 shutdown the license manager, 33 specify product order, 44 specifying the license server, 34 start the license manager, 32 uninstall the license manager, 49 update license, 32 using its options (UNIX/Linux), 27 view FLEXlm debug log file, 48 View status/diagnostic options, 46 view the ansysli debug log file, 48 view the FLEXlm license file, 48 ANSWAIT environment variable, 57 definition, 85 ANSYS licenses, 7 ansys_pid utility, 60 ansysli, 2 definition, 85 port number, 13 ansysli port number definition, 85 ansysli_client definition, 85 ansysli_monitor
definition, 85 ansysli_server, 3 definition, 85 ansysli_server log file definition, 85 ANSYSLI_SERVERS, 51 ANSYSLI_TIMEOUT_CONNECT, 51 ANSYSLI_TIMEOUT_TCP, 51 ansyslmd, 2, 45 definition, 86 ansyslmd.ini definition, 86 ansyslmd.ini file, 23, 34, 51 ansyslmd.opt file, 24, 36, 41 ANSYSLMD_LICENSE_FILE, 3, 23, 51 ANSYSLMD_LICENSE_FILE environment variable definition, 85 ASD definition, 86
B
Backup server definition, 86 boot_ansflex file, 21 Borrowable license definition, 86 Borrowing licenses, 38, 57 Build date definition, 86
C
Caching FLEXlm licenses, 17, 45 Caching license servers, 46 Capability definition, 86 Client configuration, 51 Clients definition, 86 Commands (UNIX/Linux) PS, 21 Commercial licenses, 37, 52 Communications requirements, 12 Complete unfinished licensing installation configuration, 27 Configuring redundant (triad) servers, 26 Configuring TCP/IP, 12 Configuring the license server machine, 22 .cshrc file, 34 customer number, 48
91
Index
D
daemon vendor, 45 Daemons starting at system boot time, 21 starting manually, 32 vendor (ansyslmd), 2 Debugging, 59 Diagnostic information gathering, 48 Display customer number, 48 Display license server hostid, 30 Display license status, 47 Display queued licenses, 47
E
Environment variables ANS_FLEXLM_DISABLE_DEFLICPATH, 51 ANSWAIT, 57 ANSYSLI_SERVERS, 51 ANSYSLI_TIMEOUT_CONNECT, 51 ANSYSLI_TIMEOUT_TCP, 51 ANSYSLMD_LICENSE_FILE, 3, 23, 51 Error messages, 59 launcher , 67 license borrowing, 73 license log file, 74 licensing, 21, 68 licensing installation, 67 Establishing user licensing preferences, 52 Expired license, 70
sample license files, 6 Firewall settings, 25 FLEXlm compatibility with other software, 1 definition, 86 port number, 13 FLEXlm debug log file (license.log) viewing, 48 FLEXlm license options file (ansyslmd.opt) editing, 24 FLEXlm port number definition, 86 FLEXNet Manager, 17, 27 floating license definition, 87 Floating licenses, 1, 7 Format of license files, 3 Freeing a license, 27, 37 Functions requiring lmadmin group privileges, 23
G
Gather diagnostic information, 48 Group creating, 23 Group restrictions defining, 24
H
high performance computing licensing, 55 hostid, 4, 7, 30 hostname, 4, 7, 30 HPC licensing, 55
F
Feature definition, 86 Feature names, 77 Files ansyslmd.ini, 23, 34, 51 ansyslmd.opt, 24, 36, 41 boot_ansflex init_ansysli, 21 .cshrc, 34 init_ansysli, 21 license, 23 installing, 23 license (license.dat), 23 license files format, 3 license.dat, 32, 51 license.log, 21, 32 viewing, 48 licserver.info, 23, 30
I
IA-32, 87 IA-64, 87 INCREMENT lines, 5, 77 init_ansysli, 21 Installation license, 32 uninstalling the license manager, 49 Installing license files, 23 Installing the license manager, 11 post-installation instructions, 21 UNIX/Linux, 15 Windows, 14 installing the license manager, 13 Complete unfinished licensing installation configuration, 27
92
L
Launcher error messages, 67 License error message: has expired, 70 installing, 32 updating, 32 License administration, 27 creating lmadmin group, 27 License borrowing, 38, 57 definition, 87 running, 57 running the borrow utility, 39 setup, 39 License borrowing error messages, 73 License file installation, 23 License files, 23 definition, 87 example, 6 format, 3 INCREMENT lines, 5 recognizing, 6 reread, 34 SERVER lines, 4 settings precedence, 51 specifying the location, 23 VENDOR lines, 4 License key definition, 87 License log file (license.log) definition, 8687 error messages, 74 License log file error messages, 74 License manager advanced configuration, 17 compatibility with other software, 1 Complete unfinished licensing installation configuration, 27 components, 2 daemon, 88 defined, 1 definition, 87 installing, 11, 13 installing on UNIX/Linux, 15 installing on Windows, 14 modifying startup command options, 23 modifying startup options, 45 post-installation instructions, 21 shutting down, 33 shutting down with ANSLIC_ADMIN, 33 starting at system boot time, 21 starting manually, 32
starting with ANSLIC_ADMIN, 32 uninstalling, 49 License methods sharing vs. separate, 37 License options file (ansyslmd.opt) definition, 87 editing, 41 sample, 44 License preferences academic vs. commercial, 37, 52 License queuing, 27, 57 License server error message: is down, 68 specifying, 25 license server machines, 2 License server machines definition, 7, 87 display hostid, 30 master, 7 selecting, 7 three-server network, 7 License server manager, 2 License servers caching, 46 configuring, 22 designating for license checkout, 27, 34 error messages, 21 network licensing , 2 redundancy, 8 registering, 23, 30 shutting down the license manager daemon, 33 specifying, 34 License status display, 47 License task definition, 87 License wizard, 31 license.dat file, 23, 23, 32, 51 license.log file, 21, 32 viewing, 48 Licenses customer number, 48 floating, 7 freeing, 27, 37 installing/updating, 32 waiting for available, 57 Licensing debugging, 59 error messages, 59 problem situations, 60 process, 1 sample scenario, 36
93
Index selecting server machines, 7 separate method, 37 sharing method, 37 tasks, 7 three-server license network, 7 Licensing directory, 1 Licensing environment setting up, 27 Licensing error messages, 68 Licensing installation error messages, 67 Licensing Interconnect, 2 defining group restrictions, 24 port number, 13 running independently of FLEXlm, 17 running without FLEXlm, 17 Licensing Interconnect (ansysli_server), 3 Licensing preferences establishing for users, 52 licserver.info file, 23, 30 lmadmin group, 23, 27 lmdown, 23 lmgrd, 2, 32 utility definition, 88 lmhostid, 30 lmremove, 23 lmreread, 23 LMTOOLS, 17, 27 lmutil utility definition, 88 Log file, 88 (see also license log file) definition, 88 Pool of available tasks, 7 Port number FLEXlm, 4 Port numbers changing, 13 FLEXlm, 13 Licensing Interconnect, 13 Preferences setting, 37, 52 Product list, 77 Product order specifying , 44 Product variable definition, 89 PS command, 21
Q
Queued licenses display, 47 Queuing, 27, 57 Quorum definition, 89
R
Redundant (triad) servers setting up, 26 Redundant server options, 8 Redundant servers definition, 89 Registering license server information, 23, 30 Reread the license settings, 34 root login, 27, 49 Running the Licensing Interconnect and FLEXlm independently, 17, 19 Running the Licensing Interconnect without FLEXlm, 1718
M
Master server, 7, 21 definition, 88
N
Network File System licensing failures on, 23 Network licensing network licensing considerations, 7 queuing facility, 57 shutting down the license manager, 33 starting license manager at system boot time, 21 starting license manager manually, 32 No license file found for feature error message, 70 No licenses are currently available error message, 68
S
Sample license files, 6 Sample licensing scenario, 36 SERVER lines, 4 Session log definition, 89 Set site preferences, 40 Shadow server definition, 89 Shutting down the license manager, 33 Site preferences setting , 40 Specify product order, 44
P
Path
94
Specifying firewall settings, 25 Specifying the license server, 25, 34 Starting the license manager, 32 Starting the license manager at system boot time, 21 Startup options for license manager modifying, 45 Status viewing, 46 superuser login, 27, 49 Symbolic links, 1
T
Tasks, 7 TCP/IP dial-up connection, 12 testing whether TCP/IP is installed, 12 TCP/IP requirements, 12 Three-server network, 7 timezones, 89 Troubleshooting ansys_pid utility, 60 getting additional debugging information, 59 license borrowing errors, 73 license log file errors, 74 licensing error messages, 68 problem situations, 60 Troubleshooting ANSYS error messages, 59
U
Unavailable licenses, 68 Uninstalling the license manager, 49 Updating license, 32 User privileges, 27 Using the FLEXlm options file, 24 Using the options file, 41
V
Vendor daemon, 2, 5 vendor daemon definition, 89 Vendor daemon (ansyslmd), 4 VENDOR lines, 4 View status/diagnostic options, 46 View the ansysli debug log file, 48 View the FLEXlm license file, 48 Viewing the FLEXlm debug log file, 48
W
WANs, 7 Wide area networks, 7
95
96
ANSYS, Inc. Installation Guide for Linux
Release 14.0 November 2011 00XXXX

The information in this guide applies to all ANSYS, Inc. products released on or after this date, until superceded by a newer version of this guide. This guide replaces individual product installation guides from previous releases.

Disclaimer Notice

Table of Contents
1. Installation Prerequisites for Linux ........................................................................................................ 1 1.1. System Prerequisites ......................................................................................................................... 3 1.1.1. CAD Support ............................................................................................................................ 4 1.2. Disk Space and Memory Requirements ............................................................................................. 5 1.3. GPU Requirements ........................................................................................................................... 5 1.4. Additional Hardware and Software Requirements ............................................................................. 5 1.5. Third-Party Software and Other Security Considerations .................................................................... 6 2. Platform Details ...................................................................................................................................... 7 3. Pre-Installation Instructions ................................................................................................................. 13 3.1. Pre-Installation Instructions for Download Installations .................................................................... 13 3.1.1. Downloading the Installation Files .......................................................................................... 13 3.2. Mounting the DVD Instructions for DVD Installations (Linux x64 Only) .............................................. 14 4. Installing the Software .......................................................................................................................... 15 4.1. Installing ANSYS, Inc. Products ......................................................................................................... 15 4.1.1. Product Installation ................................................................................................................ 15 4.1.2. License Manager Installation .................................................................................................. 17 4.1.2.1. Registering the License Server ....................................................................................... 18 4.1.3. Network Installation and Product Configuration ...................................................................... 18 4.1.3.1. Export the /ansys_inc Directory ............................................................................... 19 4.1.3.2. Run the Product Configuration Utility on All Client Machines .......................................... 20 4.1.3.3. Configure Licensing for File Server Installations .............................................................. 20 4.1.4. Silent Mode Operations .......................................................................................................... 20 4.1.4.1. Silent Product and License Manager Installation ............................................................. 21 4.1.4.2. Silent Product Configuration/Unconfiguration ............................................................... 23 4.1.4.3. Silent Media Installation ................................................................................................. 24 4.1.4.4. Silent Uninstall .............................................................................................................. 24 5. Post-Installation Instructions ............................................................................................................... 27 5.1. Post-Installation Procedures for All Products .................................................................................... 27 5.1.1. Post-Installation Procedures for Mechanical APDL (ANSYS) and ANSYS Workbench Products .... 28 5.1.2. Post-Installation Procedures for ANSYS CFX ............................................................................. 29 5.1.2.1. Setting up ANSYS TurboGrid Release 14.0 ....................................................................... 30 5.1.2.2. Using the ANSYS CFX Launcher to Set Up Users .............................................................. 30 5.1.2.3. Verifying the Installation of ANSYS CFX Products ............................................................ 31 5.1.3. Post-Installation Procedures for ANSYS FLUENT ....................................................................... 31 5.1.4. Post-Installation Procedures for ANSYS POLYFLOW .................................................................. 32 5.1.5. Post-Installation Procedures for ANSYS ICEM CFD .................................................................... 32 5.1.6. Post-Installation Procedures for ANSYS AUTODYN ................................................................... 32 5.2. Product Localization ....................................................................................................................... 33 5.2.1. Translated Message File Installation for Mechanical APDL (ANSYS) ........................................... 33 5.3. Launching ANSYS, Inc. Products ....................................................................................................... 34 6. Uninstalling the Software ..................................................................................................................... 35 6.1. Uninstalling ANSYS, Inc. Products .................................................................................................... 35 7. Configuring CAD Products .................................................................................................................... 37 7.1. Using the CAD Configuration Manager ............................................................................................ 37 7.1.1. Unconfiguring ........................................................................................................................ 38 7.1.2. Running the CAD Configuration Manager in Batch Mode ..................................................... 38 7.1.3. NX Configuration ................................................................................................................... 39 7.2. Configuring NX ............................................................................................................................... 40 7.2.1. Configuring the Connection for NX ......................................................................................... 40 7.2.2. Configuring the Geometry Interface for NX for ANSYS Workbench Products ............................ 41
iii
ANSYS, Inc. Installation Guide for Linux 8. Troubleshooting .................................................................................................................................... 43 8.1. Installation Troubleshooting ............................................................................................................ 43 8.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information ......................................................... 43 8.1.2. The GUI Installation Process Hangs ......................................................................................... 43 8.1.3.The Target Machine Does Not Have a DVD Drive ...................................................................... 43 8.1.4. The Online Help System Does Not Run Properly ...................................................................... 44 8.1.5. CAD Configuration Manager Help Does Not Load ................................................................... 44 8.1.6. Cannot Enter Data in Text Fields .............................................................................................. 44 8.1.7. Download and Installation Error Messages .............................................................................. 45 8.1.8. System-related Error Messages ............................................................................................... 46 8.1.9. High Performance Computing Error Messages ........................................................................ 46 8.2. Installation Troubleshooting - Mechanical APDL (ANSYS) ................................................................ 46 8.2.1.Your batch jobs terminate when you log out of a session ......................................................... 46 8.2.2. Japanese/Chinese characters display in status bar windows on Mechanical APDL (ANSYS) on Red Hat AS 4.0 ................................................................................................................................ 46 8.2.3. Mechanical APDL (ANSYS) Documentation File for User Interface Error Messages .................... 46 8.2.4. Launcher Error Messages ........................................................................................................ 47 8.2.5. FORTRAN Runtime Error Messages ......................................................................................... 47 8.2.5.1. Intel Linux 64 Systems ................................................................................................... 47 8.2.5.2. Intel EM64T Linux x64 Systems ....................................................................................... 47 8.2.5.3. AMD Opteron Linux x64 Systems ................................................................................... 47 8.3. Installation Troubleshooting - ANSYS Workbench ............................................................................ 48 8.3.1. Startup or Graphics Problems ................................................................................................. 48 8.4. Installation Troubleshooting - ANSYS CFX ........................................................................................ 48 8.4.1. CFX Distributed Parallel Runs Fail ............................................................................................ 48 8.5. Contacting Technical Support ......................................................................................................... 48
List of Tables
1.1. Supported Platforms ............................................................................................................................... 3 1.2. Supported Platforms by Product ............................................................................................................. 3 1.3. CAD Support by Platform ........................................................................................................................ 4 2.1. Compiler Requirements ........................................................................................................................ 11 5.1. Startup Commands ............................................................................................................................... 34
iv
Chapter 1: Installation Prerequisites for Linux

This document describes the steps necessary to correctly install and configure all ANSYS, Inc. products on Linux platforms for Release 14.0. These products include: ANSYS Structural Mechanics ANSYS Mechanical Products (includes Mechanical APDL and Mechanical, where supported) ANSYS Customization Files ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFX (includes ANSYS CFD-Post) ANSYS FLUENT (includes ANSYS CFD-Post) ANSYS TurboGrid ANSYS POLYFLOW (includes ANSYS CFD-Post) ANSYS CFD-Post only ANSYS ICEM CFD ANSYS ICEM CFD Creo Parametric Interface ANSYS ICEM CFD NX Interface ANSYS Icepak (includes ANSYS CFD-Post) Remote Solve Manager Standalone Services ANSYS Geometry Interfaces ACIS CATIA, Version 4 NX Parasolid
ANSYS Explicit Dynamics
ANSYS Fluid Dynamics
ANSYS Additional Tools
Notes Not all products may be available on all Linux platforms. Please see the remainder of this document for detailed information on which products are available on which platforms. At Release 14.0, ANSYS BladeGen, BladeEditor, Vista CCD, Vista CPD, Vista RTD, and Vista AFD are not supported on Linux platforms. ANSYS Workbench and ANSYS EKM Desktop are installed by default as product components to most ANSYS, Inc. product (Linux 64-bit systems only).ANSYS Workbench is not installed as part of the products
Chapter 1: Installation Prerequisites for Linux under ANSYS Additional Tools, nor with the CFD-Post only option. ANSYS Workbench includes the following applications: The Mechanical Application DesignModeler Design Exploration Meshing Remote Solve Manager TGrid FE Modeler EKM Desktop
Because some of these applications can be run as standalone applications without ANSYS Workbench, you will see some but not all of these listed separately as options when you uninstall. In such cases, you will need to select those options in order to uninstall those components.
Important Notice

The following features are new or changed at Release 14.0. Please review these items carefully. ANSYS, Inc. has discontinued support for the HP-UX Itanium 64, the Sun Solaris x64, IBM AIX 64, and the Linux 32-bit platforms for all products. ANSYS, Inc. has discontinued support for the Linux Itanium 64 platform for the ICEM CFD product. Third-party products that are used as part of the installation process are now documented in the ANSYS, Inc. Installation Guides. The ASAS product has been retired. The FATJACK, BEAMCHECK, and Splinter products are now installed automatically with the Mechanical application. The Pro/ENGINEER CAD product has been rebranded to Creo Parametric. The ANSYS, Inc. product installation now supports Creo Parametric, NX, SolidWorks, and Autodesk Inventor reader options. You can now choose to install the Reader (no CAD installation required) or the Associative Plug-in (CAD installation required) options for these CAD products. The release version now appears with each product selection in the Start menu on Windows. You can now specify two DVD drives during a silent installation to accommodate the installation process spanning two DVDs. See the discussion on Silent Mode Operations in the Installation Guide for your platform for more information. You can now choose to install and uninstall only Remote Solve Manager (RSM). RSM will continue to be installed as part of ANSYS Workbench. You can now choose to install and uninstall only the EKM Server on Windows platforms.
System Prerequisites The use of files requiring 777 permissions on Linux has been minimized. For more information on remaining full-permission files and softlinks, see the section Third-Party Software and Other Security Considerations in the ANSYS, Inc. Linux Installation Guide. The PDF version of the documentation that is available on the Customer Portal is now unprotected, allowing you to copy and paste content from the PDFs into other locations. This capability is especially useful if you want to use command snippets that are available throughout the documentation.
1.1. System Prerequisites

ANSYS, Inc. Release 14.0 products are supported on the Linux platforms and operating system levels listed in the following tables. Patches listed may be superseded by newer versions; see your vendor for the most current version. See the individual Platform Certification Specifics in this guide for more information on specific platform requirements. For up-to-date information on hardware platforms or operating systems that have been certified, go to http://www.ansys.com/Support/Platform+Support. (This URL is case-sensitive.)
Note
The ANSYS, Inc. License Manager supports additional UNIX/Linux platforms. Please see the ANSYS, Inc. Licensing Guide for the complete list of platforms supported by the ANSYS, Inc. License Manager.
Table 1.1 Supported Platforms

Platform Processor Operating System Platform architecture (directory name) linia64 Availability
Linux Itanium 64 Linux x64
Itanium2
Red Hat Enterprise Linux 5; SUSE Linux Enterprise 10 and Enterprise 11 SP1 Red Hat Enterprise Linux 5; Red Hat Enterprise Linux 6, SUSE Linux Enterprise 10 [1] and Enterprise 11 SP1
Download only Download / DVD
EM64T/Opteron 64
linx64
1.
We recommend that you run ANSYS Workbench on Red Hat Enterprise Linux 5.3 or higher or SUSE Linux Enterprise 10.2 or higher.
Supported Platforms for High Performance Computing Please see the discussions on Configuring Distributed ANSYS and Configuring ANSYS CFX Parallel later in this guide for detailed information on supported platforms for distributed computing.
Table 1.2 Supported Platforms by Product

Linux Itanium 64 Mechanical APDL Workbench AUTODYN (solver only) LS-DYNA X X X Linux x64 X X [1] X X
Chapter 1: Installation Prerequisites for Linux Linux Itanium 64 CFX FLUENT TurboGrid ICEM CFD POLYFLOW Icepak 1. X X Linux x64 X X X X X X
We recommend that you run ANSYS Workbench on Red Hat Enterprise Linux 5.3 or higher or SUSE Linux Enterprise 10.2 or higher on Linux x64 systems.
1.1.1. CAD Support

The following CAD and auxiliary programs are supported on the indicated products and platforms. Products are: A = Mechanical APDL W = ANSYS Workbench I = ANSYS ICEM CFD standalone (some CAD systems may require the integrated ANSYS Workbench Reader)
Table 1.3 CAD Support by Platform

Linux Itanium 64 CATIA 4.2.4 Parasolid 22.1 Parasolid 24 SAT ACIS 21 [1] NX 6.0 [2] NX 7.5 NX 8.0 STEP AP203, AP214 IGES 4.0, 5.2, 5.3 DWG GEMS 1. 2. 3. 4. 5. A [4] A [4] A Linux x64 A [4], I A, W, I A, W, I A, W, I A, W, I W [3], I [3] W [5] W, I W, I I I
For ANSYS ICEM CFD standalone, ACIS 18.0.1 is the supported version for all platforms. NX 6.0 has dropped support for all Linux platforms except Linux SUSE 10 SP2. NX 7.5 supports Red Hat 5.3 and SUSE Linux Enterprise 10 SP2. Red Hat requires the installation of i686 (32-bit) glibc & libstdc++ libraries. NX 8.0 supports Red Hat 6.0 and SUSE Linux Enterprise 11 SP1.
Additional Hardware and Software Requirements
1.2. Disk Space and Memory Requirements

You will need the disk space shown here for each product for installation and proper functioning. The numbers listed here are the maximum amount of disk space you will need. Depending on the options selected for each product, you may require less. Product Mechanical APDL (ANSYS) ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFX ANSYS TurboGrid ANSYS FLUENT POLYFLOW ANSYS ICEM CFD ANSYS Icepak ANSYS TGrid CFD Post only ANSYS Geometry Interfaces Memory Requirements product installations. Disk Space 8.1 GB 7.1 GB 7.3 GB 9.1 GB 8.0 GB 8.8 GB 10.2 GB 2.2 GB 2.7 GB 5.5 GB 8.0 GB 170 MB
We recommend that you have at least 2 GB of memory available for running
1.3. GPU Requirements

Your system must meet the following requirements to use the GPU capability in Mechanical APDL: The machine(s) being used for the simulation must contain at least one nVIDIA Tesla series GPU card (a Tesla 20-series card is recommended for optimal performance) or one Quadro 6000 card. If both a Tesla and Quadro card are detected, Mechanical APDL will choose the Tesla card. On Linux, the driver version for the nVIDIA Tesla series GPU card must be 275.09.07 or newer. You must be running on a Linux x64 operating system. Linux Itanium (Linux IA-64) is not supported.
1.4. Additional Hardware and Software Requirements

TCP/IP for the license manager (see the ANSYS, Inc. Licensing Guide for more information on TCP/IP) If you use a spaceball, ensure that you have the latest version of the drivers installed. Spaceball devices are not supported on Linux with ANSYS Workbench applications, including the Mechanical Application, DesignModeler, Meshing, etc. Approximately twice as much swap space as memory. The amount of memory swap space on the system may limit the size of the model that can be created and/or solved. Graphics card compatible with the supported operating systems, capable of supporting 1024x768 High Color (16-bit) and a 17-inch monitor compatible with this type of graphics card; ANSYS CFX products and ANSYS TurboGrid require 24-bit color and that antialiasing on your graphics card be disabled. Refer to your operating system's documentation for specific instructions.
Chapter 1: Installation Prerequisites for Linux X11, OpenGL graphics libraries Mesa-libGL (OpenGL) is required to run data-integrated ANSYS Workbench applications such as Mechanical. If you are using Exceed to run ANSYS Workbench products, Exceed 3D is required. Exceed 3D 2008 Service Pack 9 or higher is recommended. For FLUENT, CFX-Pre, and CFD-Post, a three-button mouse is required to access all available functionality. Adobe Acrobat Reader is required to read the installation guides and other user documentation. ANSYS CFX requires Exceed 2006 or newer to remote display from some platforms. FLUENT graphics are not officially supported when running under Exceed.
1.5. Third-Party Software and Other Security Considerations

The following third-party products are used as part of the installation process. In order for the installation to work properly, you must allow access to these products. Product Name Tcl Tk Perl GNU gzip GNU tar Executable Name tclsh wish perl gzip tar
ANSYS, Inc. products may have softlinks that require 777 permissions. In addition, the following thirdparty products are known to contain softlinks that require 777 permissions: MainWin CPython Mono Python Perl GCC Qt Qwt HPMPI PCMPI IMPI MPICH OPENMPI INTELMPI PCMPI
Chapter 2: Platform Details

Linux
For ALL 64-bit Linux platforms, OpenMotif, and Mesa libraries should be installed. These libraries are typically installed during a normal Linux installation. You will also need the xpdf package to view the online help. You can find the necessary OpenMotif libraries for your platform at http://www.motifzone.net. SUSE Linux Enterprise 11 requires SP1. After installing the SP1 updates, you must also install OpenMotif and the prerequisites from the SLES11 SDK DVD, as well as the OpenMotif22 packages (recommended packages are openmotif22-libs-2.2.4-138.18.1.x86_64.rpm and openmotif22-libs-32bit-2.2.4138.18.1.x86_64.rpm from SLED11 SP1 x86_64 distribution. You may need to use "rpm -iv -force" to install these). Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 6 base install requires patch kernel-2.6.3271.14.1.el6.x86_64.rpm and kernel-devel-2.6.32-71.14.1.el6.x86_64.rpm. In addition, you need to install the following libraries: libXp.x86_64 xorg-x11-fonts-cyrillic.noarch xterm.x86_64 libXp.x86_64 openmotif.x86_64 compat-libstdc++-33.x86_64 libstdc++.x86_64 libstdc++.i686 gcc-c++.x86_64 compat-libstdc++-33.i686 libstdc++-devel.x86_64 libstdc++-devel.i686 compat-gcc-34.x86_64 gtk2.i686 libXxf86vm.i686 libSM.i686 libXt.i686 xorg-x11-fonts-ISO8859-1-75dpi.noarch
Chapter 2: Platform Details Red Hat no longer includes the 32-bit libraries in the base configuration so you must install those separately. Additional requirements for Intel, AMD Opteron, and EM64T Linux systems are detailed below. ANSYS, Inc. License Manager Linux 32 and Linux x64 systems running the ANSYS, Inc. License Manager require the Linux Standard Base (LSB) 3.0 package. CATIA V4 with Mechanical APDL To run CATIA V4 with Mechanical APDL on Linux 64-bit platforms, you must have the following Linux 32-bit i686 libraries: glibc libstdc++
ANSYS Workbench For ANSYS Workbench, install the following gamin .rpm for your platform to prevent ANSYS Workbench from hanging when the Linux file alteration monitor, gam_server, is using 100% of the CPU. gamin-0.1.7-1.4.EL4.x86_64.rpm
If you are running ANSYS Workbench using the KDE desktop environment, set the focus stealing prevention level to "None" to prevent the project save dialog boxes from appearing behind the application window: 1. 2. 3. 4. Use the kcontrol command to launch the KDE Control Center. In the Control Center window, select Desktop> Window Behaviour> Advanced. Change Focus Stealing Prevention Level to None. Click Apply.
If you are running on KDE 4 or if the kcontrol command does not exist, use System Settings to set the focus stealing prevention setting level to "None": 1. 2. 3. 4. Use the systemsettings command to launch the System Settings. In the System Settings window, select General> Window Behaviour> Focus. Change Focus Stealing Prevention Level to None. Click Apply.
Mechanical, Meshing, DesignModeler, and FE Modeler Applications If you are using a localized operating system (such as French or German), you must set the mwcontrol VisualMainWin control on any machines running these applications in order for these applications to recognize the correct numerical format. ANSYS Workbench must already be installed before setting this control. First, you need to ensure that the /v140/aisol/WBMWRegistry/ directory has write permissions. From the /v140/aisol/ directory, issue the following command:
chmod -R 777 WBMWRegistry/
Then, use the following procedure to set mwcontrol for your locale: 1. 2. cd to <wb_install directory>/v140/aisol Issue the following command:
./.workbench -cmd mwcontrol
3. 4. 5. 6. 7.
On the MainWin Control Panel, select Regional Settings. Select the Regional Settings tab. Change the language in the dropdown to match the language you want to use. Check the Set as system default locale option. Click Apply to accept the changes, and then click OK to dismiss the Change Regional Settings notification.
Using FLUENT with Infiniband On some operating systems, the default amount of physical memory that can be pinned/locked by a user application is set to a low value and must be explicitly increased. A value recommended by Intel is 90% of the physical memory. Therefore, for a system with 8GB of memory, the following should be added to the /etc/security/limits.conf file:
* soft memlock 7500000 * hard memlock 7500000
The need for increasing the limits may be indicated by the following error message with Platform MPI:
fluent_mpi.6.3.26: Rank 0:0: MPI_Init: ibv_create_qp() failed fluent_mpi.6.3.26: Rank 0:0: MPI_Init: Can't initialize RDMA device
After setting soft and hard memlock to a proper value you still receive memory errors:
libibverbs: Warning: RLIMIT_MEMLOCK is 32768 bytes. This will severely limit memory registrations
Semaphore Limit On some Linux systems, ANSYS Workbench reaches a system limit on the number of semaphores in the Linux configuration. In this case, you will see a message similar to the following: sem_lock->semop->op_op: Invalid argument sem_unlock->semctl: Invalid argument To increase the number of semaphores, run the following command as owner or root:
% echo 256 40000 32 32000 > /proc/sys/kernel/sem
This modification takes effect immediately, but is reset at the next reboot. To avoid resetting the limit when rebooting, add the above command to one of your systems startup scripts by copying the command into a file called mod_sem and then setting up the following links to execute the file each time you restart your system:
cp mod_sem /etc/init.d ln -s /etc/init.d/mod_sem /etc/rc3.d/S61mod_sem ln -s /etc/init.d/mod_sem /etc/rc5.d/S61mod_sem
Using the FLUENT Launcher On Linux systems, you must have the following package (as appropriate for your platform) installed in order to use the FLUENT launcher: Red Hat 4: compat-libstdc++-33-3.2.3-47.3 Red Hat 5: compat-libstdc++-33-3.2.3-61 SUSE 10: compat-libstdc++-5.0.7-22.2 Using ANSCUSTOM If you use ANSCUSTOM to link your own version of ANSYS Release 14.0 on a SUSE SLES10.x box, you may see two unsatisfied externals that are system, not ANSYS files, due to the linker looking for some system files in a Red Hat directory on a SUSE box. To work around this problem, run the following as root:

mkdir p /usr/lib/gcc/x86_64-redhat-linux/3.4.6 ln -sf /usr/lib/gcc/i586-suse-linux/2.95.3/crtbegin.o /usr/lib/gcc/x86_64-redhat-linux/ 3.4.6/crtbegin.o ln -sf /usr/lib/gcc/i586-suse-linux/2.95.3/crtend.o /usr/lib/gcc/x86_64-redhat-linux/ 3.4.6/crtend.o
The revision numbers shown in the examples (2.95.3 and 3.4.6) may be different on your system. The linker will specify where it is trying to find the crtbegin.o and crtend.o files; that location will be the last part of the above commands. You can use the Linux locate command to find the existing crtbegin.o and crtend.o files; that location would be the first part of the above commands. System Libraries On 64-bit Linux linx64 systems (not Itanium systems), the ANSYS Release 14.0 executable is looking for system libraries that do not have revision numbers appended to the end of their file names. On some SUSE systems, the graphics libraries all have revision numbers appended to the end of the library filenames. In these cases, ANSYS quits because the loader cannot find all of the libraries that it is looking for. When running ANSYS Release 14.0, the loader will inform you that it is unable to locate a specific library (for example, libXm.so). Using the Linux locate command, find the library (libXm.so in this example) on your system and add the appropriate symbolic link as seen below. To overcome this possible problem, run the following as root:
ln ln ln ln ln ln ln ln ln ln -sf -sf -sf -sf -sf -sf -sf -sf -sf -sf /usr/lib64/libGLU.so.1.3.060402 /usr/X11R6/lib64/libXm.so.3.0.3 /usr/X11R6/lib64/libXp.so.6.2 /usr/X11R6/lib64/libXt.so.6.0 /usr/X11R6/lib64/libXext.so.6.4 /usr/X11R6/lib64/libXi.so.6.0 /usr/X11R6/lib64/libX11.so.6.2 /usr/X11R6/lib64/libSM.so.6.0 /usr/X11R6/lib64/libICE.so.6.4 /lib64/libgcc_s.so.1 /usr/lib64/libGLU.so /usr/X11R6/lib64/libXm.so /usr/X11R6/lib64/libXp.so /usr/X11R6/lib64/libXt.so /usr/X11R6/lib64/libXext.so /usr/X11R6/lib64/libXi.so /usr/X11R6/lib64/libX11.so /usr/X11R6/lib64/libSM.so /usr/X11R6/lib64/libICE.so /lib64/libgcc.so
For Linux, you may need the following:

sudo ln -sf /usr/lib64/libXm.so.4.0.0 /usr/lib64/libXm.so.3
The revision numbers appended to the filenames on the left may be different on your system. Intel Linux ANSYS was built and tested on Red Hat using the compilers as noted in Table 2.1: Compiler Requirements (p. 11). The ANSYS solver is built on Red Hat Enterprise Linux AS release 4 (Update 5). For ANSYS Workbench and ANSYS AUTODYN, you need to unlimit the stack size. Add the following to your .cshrc file:
limit stack unlimit
ANSYS TurboGrid 14.0 is not supported on Linux IA-64. AMD Opteron ANSYS was tested on a generic Opterontm system running Red Hat Enterprise Linux AS release 4 (Update 5). Intel Xeon EM64T ANSYS was built and tested on a generic Intel EM64T system running Red Hat Enterprise Linux AS release 4 (Update 5).
10
If you are running on Intel's Xeon EM64T system, we recommend that you turn CPU hyperthreading off (default is on). A system administrator needs to reboot the system and enter the BIOS to turn the hyperthreading option off.
Table 2.1 Compiler Requirements

Mechanical APDL (ANSYS), ANSYS Workbench Compilers* Linux (all versions) Intel 11.1.069 (FORTRAN, C, C++) PGI Fortran 10.3 Intel 11.1.069 (FORTRAN, C, C++) Intel 11.1.069 (FORTRAN, C, C++) CFX Compilers* FLUENT Compilers* AUTODYN Compilers*
* Compilers are required only if you will be using User Programmable Features or other customization options.
11
12
Chapter 3: Pre-Installation Instructions

3.1. Pre-Installation Instructions for Download Installations
Before downloading the installation files, you need to accurately determine your platform type. Versions that are optimized for different chip sets from the same vendor can have similar names, causing confusion. We strongly recommend that you run the get_ansys_platform140 script on each machine first. This script will output the correct platform name for each machine on which it is run. You can download this script by clicking the Which UNIX/Linux platform am I using? button on the download site. We strongly recommend that you review the Read Download Instructions and Product Information file included on the download site for the most current download instructions. We also recommend that you review the What Should I Download? file to understand which package(s) you need to download, depending on which product(s) you purchased and wish to run.
3.1.1. Downloading the Installation Files

To download the installation files from our website, you will need to be a TECS customer. Depending on the product/platform combination(s) you choose, you may need to download multiple tar files. 1. 2. 3. 4. From the Customer Portal, click on Download Software. The ANSYS Download Center Wizard page displays an overview of the download process. Review the overview and click Next. For the Download Type, choose Current Release and Updates. Click Next Step. Choose the hardware platform for which you want to download installation packages. You can select only one platform at a time. You will need to repeat the download procedure for each platform that you want to download. Click Next Step. Choose the products you wish to download. Products are listed by product names that correspond to the licensing product names. You can choose to list products grouped by product group or alphabetically. All products that you currently have licensed are highlighted and pre-selected for your convenience. After you have selected all products that you wish to download, click Next Step. The license manager, product, and documentation packages that you've selected to download are listed. Click on each link provided to begin the downloads. After the downloads have completed, uncompress each package using standard uncompression utilities for your specific platform. We strongly recommend that you extract the files into a new, temporary directory. Begin the product installation as described in Installing the Software (p. 15).
5.
6. 7.
8.
13
3.2. Mounting the DVD Instructions for DVD Installations (Linux x64 Only)
If you install ANSYS, Inc. products from the installation media (DVD), you will need to run the installation procedure using either a locally- or remotely-mounted DVD, depending on your site's system. For a locally-mounted DVD installation, issue the following commands:
mkdir dvdrom_dir mount -t iso9660 /dev/cdrom dvdrom_dir
If the target machine does not have a DVD reader, first follow the steps for locally-mounted DVD, and then follow the procedure below for remotely-mounted DVDs:
Remotely-Mounted DVD Procedure

1. Add the dvdrom_dir directory to the /etc/exports file on the machine with the DVD device. A sample /etc/exports entry is:
/dvdrom_dir *(ro)
or
/dvdrom_dir (ro)
2.
Run exportfs to export the dvdrom_dir directory:

exportfs a
Check the manual page for 'exports' for the correct syntax, as different Linux versions can have different syntax. 3. Log on to the machine where you wish to install ANSYS, Inc. products and issue the following commands:
mkdir dvdrom_dir2 mount -t nfs Host:cdrom_dir dvdrom_dir2
where Host is the hostname of the machine where the DVD device is located. Run man exports for more information. If you are installing from media, you will be prompted to change DVDs during the installation. Please make sure you have all installation DVDs before beginning the installation.
14
Chapter 4: Installing the Software

4.1. Installing ANSYS, Inc. Products
This section explains how to install ANSYS, Inc. products, including ANSYS client licensing, as well as the ANSYS, Inc. License Manager. The default installation expects you to be logged in as root. You can override that setting and run the installation as a regular user by starting the installation with the -noroot command option. If you are not logged in as root, however, you will not be able to set the /ansys_inc symbolic link and may potentially experience permission problems. The inability to set the /ansys_inc symbolic link will in no way inhibit your ability to run ANSYS, Inc. products; it is provided as a convenience. If you do not use the /ansys_inc symbolic link, you must install all releases into a common directory to ensure license manager compatibility and availability among releases and products.
4.1.1. Product Installation

1. To launch the product install, enter the full path to the installation program and run the INSTALL program:
/<mount_dir>/INSTALL
To invoke the license manager only install, run INSTALL.LM and proceed directly to License Manager Installation, below. Use /INSTALL.LM only to install the license manager; use INSTALL to install the product(s). To invoke the EKM Server installation, run INSTALL.EKMSVR to launch the EKM server setup. You must install the EKM client, ANSYS Workbench, and any other desired components before installing the EKM Server. 2. 3. 4. Select the language. Click Next. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. products. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. You can choose as many platforms as you wish; however, you must run the platform configuration procedure (see Run the Product Configuration Utility in Network Installation and Product Configuration (p. 18)) for each platform other than your current machine type. See Network Installation and Product Configuration (p. 18) for specific instructions on how to configure a shared installation directory across multiple machines using a common network file system. Click Next to continue. 5. Specify the installation directory. You can accept the default or specify an alternate directory name where the products are to be installed. When you choose an install directory via the Browse feature, the installation will automatically append /ansys_inc/ to the chosen directory. The installation path
15
Chapter 4: Installing the Software can have a maximum of 100 characters. You must install all ANSYS, Inc. products into the same location. Installing products into different locations can cause product components to fail. Default directory is /ansys_inc, if it exists, or /usr/ansys_inc if not. We strongly recommend that you also set the symbolic link /ansys_inc to the directory where the ANSYS, Inc. product is installed. The /ansys_inc symbolic link is set by default. If you choose not to specify the symbolic link, substitute the directory path where you installed the product for all subsequent occurrences of /ansys_inc in this guide. The symbolic link option is available only if you are installing as root. If you do not use the /ansys_inc symbolic link, you must install all releases into a common directory to ensure license manager compatibility and availability among releases and products. If you have already installed the ANSYS Workbench Framework for Ansoft, you must install any additional ANSYS, Inc. products into the same directory. On Linux, you can choose Disable RSS to disable automatic internet feeds to ANSYS, Inc. products. Click Next to continue. 6. Select the components you want to install. You can select as many components as you wish to install. The amount of disk space required for the available components and the disk space available appears at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. If you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully. The components listed represent all available components for the platforms you selected earlier. Not all components are available on all platforms or with all products. Click Next to continue. 7. If you selected NX, you will have to choose which NX product to configure. You can choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD product be installed), or skip and configure later (using the CAD Configuration Manager). If you choose the Workbench Associative Interface and the UGII environment variables were not set, you may need to specify the NX installation path for an existing NX installation. Click Next. 8. 9. A licensing file date verification summary appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next. A summary of the selected installation data appears. Information shown includes platform, installation directory, and products. Review the information carefully, and if correct, click Next to continue the installation. The selected products and components are now being installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation and install the licensing client. 10. The Licensing Client Installation Configuration box appears. As the licensing client is installed, progress messages appear in the box.
16
Installing ANSYS, Inc. Products 11. If you do not have an existing ansyslmd.ini file, the Specify License Server Machine - Add Server Specification box appears. Enter the hostname of your license server machine and click Next. If you already have an existing ansyslmd.ini file, you will not see this box and you will proceed directly to the next step. 12. When the client installation is complete, click Exit. 13. On the product installation window, click Next. You will be asked to participate in an Install Survey. To take the survey, enter the path to a valid browser for your system, and click Next. You can also click Finish now to skip the survey or when you have completed the survey. If you have installed ANSYS, Inc. products on a file server, follow the instructions under Network Installation and Product Configuration (p. 18).
Caution
If you have a three-license server network, we do not recommend that you load ANSYS, Inc. products on a single file server; doing so eliminates the inherent safety of a redundant setup.
4.1.2. License Manager Installation

Follow the instructions below to install the ANSYS License Manager server on Linux systems. Client licensing is installed automatically when the product is installed; you do not have to take any further steps to run as a client if you have installed a product. You may safely install the ANSYS License Manager over a client installation. Install the client first (as part of the product installation), and then install the ANSYS License Manager following the steps below. If you are installing both the client and the ANSYS License Manager to the same directory, you will need to do both installations in order to properly configure the ANSYS License Manager. 1. Run INSTALL.LM to launch the license manager installation. If you downloaded the license manager installation package, this file will reside in the directory where you untarred the downloaded files. If you are running from a DVD, this file will reside in the top level of the DVD. You will be notified that the license manager, if running, will be shut down. Click OK. Select the language. Click Next. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. License Manager. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. Click Next to continue. The installation directory is specified. You can accept the default or specify an alternate path and directory name where the products are to be installed. Click Next to continue. 7. Select the components you want to install. You can choose to install the ANSYS, Inc. License Manager. The amount of disk space required and the disk space available appear at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. If you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully.
2. 3. 4. 5.
6.
17
Chapter 4: Installing the Software Click Next to continue. 8. 9. A licensing file date verification summary appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next. A summary of the selected installation data appears. Information shown includes platform, installation directory, and product. Review the information carefully, and if correct, click Next to continue the installation. The ANSYS License Manager is now being installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation and install the license manager. 10. The Licensing Server Installation Configuration box appears. As the license manager is installed, progress messages appear in the box. 11. The License Wizard will be launched. This wizard walks you through the process of installing or updating a license file, specifying the license server(s) (which updates the ansyslmd.ini file), and starting the license manager. The wizard will prompt you for the necessary information at each step. During this process, the license manager will be shut down if it is running. Be aware that this can impact any users currently running using the license manager. Click Continue on the License Wizard to begin, and follow the instructions on the screen. 12. When the License Wizard is complete, click Exit on the wizard screen and then click Finish again on the Licensing Installation Configuration Log screen. 13. When the license manager installation is complete, click Finish.
4.1.2.1. Registering the License Server

Follow this procedure to register your license server information if you are a new user or if you are adding or changing a license server machine. See the ANSYS, Inc. Licensing Guide for more information on selecting license servers and on using the ANSLIC_ADMIN utility. 1. Use the ANSLIC_ADMIN utility to register license server information on each license server. To run the ANSLIC_ADMIN utility on a Linux platform, type:
2.
Return the resulting file to your ANSYS, Inc. sales representative. ANSYS, Inc. or your sales representative will then supply you with your license keys. This file is located in /ansys_inc/shared_files/licensing/licserver.info by default. Use the Run the License Wizard option of the ANSLIC_ADMIN utility to enter your license key and start the license manager.
3.
4.1.3. Network Installation and Product Configuration

To complete a network installation (where the product is installed on one machine and one or more clients access that installation to run the product) to a file server machine or a cross-platform installation (where the product for one machine type is installed on a different machine type), follow the steps below. These steps apply to the following products: Mechanical APDL, ANSYS Workbench, ANSYS CFX, ANSYS ICEM CFD, ANSYS FLUENT, ANSYS POLYFLOW, ANSYS Icepak, Common/CAD, and Remote Solve Manager (RSM).
18
Installing ANSYS, Inc. Products A network installation must be homogeneous, although you can install on different operating systems and architectures within the same platform. For example, you can install multiple Linux platforms on a single Linux file server, and clients of those platform types will access the product installation on that single Linux file server. However, you must install different platforms into different directories. You must complete the following steps to run products across a network: 4.1.3.1. Export the /ansys_inc Directory 4.1.3.2. Run the Product Configuration Utility on All Client Machines 4.1.3.3. Configure Licensing for File Server Installations We strongly recommend that these steps be performed by the same non-root user. Installing and configuring as different users may create permissions problems. Likewise, installing and/or configuring as a root user may also result in permissions problems.
4.1.3.1. Export the /ansys_inc Directory

If you are installing an ANSYS, Inc. product on a file server, you need to export the /ansys_inc directory to all client machines so that all users can access the program. You will also need to share the ANSYS directory if the machine you are installing on does not have a DVD drive or an internet connection for downloading files and you need to share files with a machine that does have a DVD drive or internet connection. The instructions below assume ANSYS, Inc. products were installed in the specified directory. 1. 2. Install the ANSYS, Inc. products. The following example uses /usr/ansys_inc. Export the ansys_inc directory by adding the following line to the /etc/exports file:
/usr/ansys_inc
The default behavior on Linux provides read-only access from all clients. To enable read/write permission from all clients, use *(rw):
/usr/ansys_inc *(rw)
3.
Run
exportfs -a
4.
On all client computers, mount the ansys_inc directory.
If you perform a network install where the server and client are on the same platform and you want the clients to be able to modify the licensing configuration, you need to consider the NFS write options for the exported file system as shown in the above examples. You also need local permissions to the licensing directory (/shared_files/licensing/<platform>/) if you want to be able to create the install_licconfig.log that the license configuration produces. If you need to transfer the files from a Windows machine with a DVD drive to a Linux machine without one, copy the DVD contents using a Samba mount or some other transfer method that is safe to use between Windows and Linux. If sharing the ANSYS directory between Linux machines, you must use the same mount point for both the client and server. For example, if you installed to a file server in a directory named /apps/ansys_inc and you did not choose the symbolic link to /ansys_inc, then you must mount this directory on the client machine using /apps/ansys_inc as the mount point. If you did choose the symbolic link to /ansys_inc during installation on the file server, you must either use /ansys_inc as the
19
Chapter 4: Installing the Software mount point on the client or you must create a symbolic link to /ansys_inc on the client machine. (The symbolic link is created by default during installation if you installed as root).
4.1.3.2. Run the Product Configuration Utility on All Client Machines

For both network and cross-platform installations, you must run this step on every client machine. 1. On each client machine, issue the following command to run the Product Configuration utility:
/ansys_inc/v140/commonfiles/tools/<platform>/ProductConfig.sh
2. 3.
Select Configure Products. Select the products you want to configure and click Configure.
Note
ANSYS Workbench is configured when Mechanical APDL, ANSYS CFX, ANSYS FLUENT, ANSYS POLYFLOW, ANSYS Icepak, or Remote Solve Manager Standalone Services is selected. CFD-Post is configured when either ANSYS CFX or ANSYS FLUENT is configured. Select Common/CAD to configure the NX CAD packages. 4. If you selected Common/CAD and are configuring NX, you will need to supply the NX installation directory path. You can choose to skip the configuration. If you skip the configuration here, you must manually configure NX or use the ANS_ADMIN utility or the CAD Configuration Manager to configure NX later. See Configuring CAD Products (p. 37) for detailed information on using alternative methods to configure NX. 5. On the Configuration Complete dialog box, click Finish.
4.1.3.3. Configure Licensing for File Server Installations

When you run a cross-platform/file server installation where the product is installed on one platform and run on a different platform, you will need to complete the client licensing configuration on the client machines where you will be running the product. 1. Run the ANSLIC_ADMIN utility:
2. 3. 4.
Choose Tools> Complete Unfinished Licensing Installation Configuration. Follow the on-screen prompts to provide any necessary information. Click Exit.
4.1.4. Silent Mode Operations

ANSYS, Inc. supports silent mode operations, including installation, product configuration/unconfiguration, and uninstall. You can specify the following product flags. These flags are all valid for a silent install. However, because of the way the products are packaged, not all of these flags may be valid for a silent configuration/unconfiguration, or uninstall. 20
Installing ANSYS, Inc. Products
Product Flags
Product Mechanical APDL (ANSYS) ANSYS Customization Files ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFD-Post ANSYS CFX ANSYS TurboGrid ANSYS FLUENT ANSYS POLYFLOW ANSYS AQWA ANSYS Icepak ANSYS ICEM CFD product_flag -mechapdl -ansyscust -autodyn -lsdyna -cfdpost -cfx -turbogrid -fluent -polyflow -aqwa -icepak -icemcfd
Note: Installing any of the above products will install ANSYS Workbench. ANSYS ICEM CFD Unigraphics NX Interface ANSYS Remote Solve Manager Standalone Services NX Geometry Interface CATIA 4.x Geometry Interface Parasolid Geometry Interface ACIS Geometry Interface -icemug -rsm -ug -catia4 -parasolid -acis
4.1.4.1. Silent Product and License Manager Installation

You can deploy an ANSYS, Inc. product installation in silent mode. The general form to run a silent product installation, including the client licensing, is:
INSTALL -silent -install_dir path -product_flag
If no product flags from the list above are specified, all products will be installed. To install specific products, run the silent install with any combination of the product flags listed above (not all products are available on all platforms). For example, to install only TurboGrid and Icepak, issue the following command:
INSTALL -silent install_dir /ansys_inc/ -turbogrid -icepak
Additional command line arguments are available; please see the list below. To install the ANSYS License Manager on Linux systems that will act as license servers, you must run the INSTALL.LM command:
INSTALL.LM -silent -install_dir path
21
Chapter 4: Installing the Software The silent license manager installation is valid only for the default Licensing Configuration option "Run the ANSYS Licensing Interconnect with FLEXlm." Please see the ANSYS, Inc. Licensing Guide for more information. You can use the following arguments when running a silent installation. Note that some options are available only for a silent license manager installation. -silent -help -install_dir path Initiates a silent installation. Displays a list of valid arguments for a silent installation. Specifies the directory to which the product or license manager is to be installed. If you want to install to the default location, you can omit the -install_dir argument.The default location is /ansys_inc if the symbolic link is set; otherwise, it will default to /usr/ansys_inc. Specifies one or more products to install specific products. If you omit the -product_flag argument, all products will be installed. See the list of valid product_flags below. You can specify an options file that lists the products you want to install.To do so, you must provide a full path to a file containing desired products. See Specifying Products with an Options File below for more details. Disables automatic internet feeds to ANSYS, Inc. products (Linux only). Specifies the location of the license file to install. If the path is not specified or if the path is the same as the existing license file, the license file will not be installed. Valid only when doing a silent license manager installation (INSTALL.LM). Specifies a language to use for the ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect log file. Use the language directory name in the language subdirectory of the licensing directory (en-us, fr, de, etc.) as the language value.This flag can be used during a GUI installation as well. Valid only when doing a license manager installation (INSTALL.LM). Specifies information to be used by the client for the license server. Valid only in conjunction with a silent installation (INSTALL).The format is: Single license server: LI_port_number:FLEXlm_port_number:hostname Example: 2325:1055:abc Three license servers: LI_port_number:FLEXlm_port_number:hostname1,hostname2,hostname3 Example: 2325:1055:abc,def,xyz The default values for the Licensing Interconnect and FLEXlm port numbers (2325 and 1055, respectively) will be used if they are not specified. However, you do need to include the colons. 22
-product_flag
-productfile path -disablerss -licfilepath path -setliclang language
-licserverinfo
Installing ANSYS, Inc. Products Example: ::abc or ::abc,def,xyz Information specified via -licserverinfo will be appended to existing information in the ansyslmd.ini file. To change information already in your ansyslmd.ini file, you must use the ANSLIC_ADMIN utility. Any messages will be written to the appropriate installation log files. Installation log files are located in the installation directory: install.log contains installation messages, and install_licconfig.log contains licensing installation messages. In rare circumstances with a silent licensing installation, the licensing installation messages may not be written to the install_licconfig.log (for example, if the silent licensing installation aborts); in these cases, you may find error messages in the .ansys_install_temp_licconfig_<user>_<index>.log file, located in /var/tmp.
Caution
A silent license manager installation could shut down the ANSYS, Inc. License Manager, affecting other users who are using that license server machine. For more information on the silent license manager installation, see the ANSYS, Inc. Licensing Guide.
Specifying Products with an Options File

You can also specify an options file on the command line using the -productfile path option. The options file can have any name and extension, but the path must include the full path and filename, including any extension used. The options file can specify which products you want to install. The options file can contain all possible products, with the products you do not want to install commented out, or it can contain only the products you want to install. An example options file is shown below. In the example, NX is commented out using an acceptable comment indicator. When using the options file, do not include the dash (-) before the product name.
mechapdl ansyscust autodyn lsdyna cfdpost cfx turbogrid fluent polyflow icemug icepak #ug
4.1.4.2. Silent Product Configuration/Unconfiguration

You can also run the ProductConfig utility via command line (i.e., silent mode) to configure products. To run in silent mode, from each client machine, run the ProductConfig with the -silent option:
/ansys_inc/v140/commonfiles/tools/<platform>/ProductConfig.sh -silent
23
Chapter 4: Installing the Software Use the -product_flag argument to specify which products should be configured. If you do not specify one or more products, all products that have been installed will be configured. The valid product_flags are: Product Mechanical APDL (ANSYS) ANSYS CFD-Post ANSYS CFX ANSYS TurboGrid ANSYS FLUENT ANSYS POLYFLOW ANSYS Icepak ANSYS ICEM CFD ANSYS Remote Solve Manager Standalone Services product_flag -mechapdl -cfdpost -cfx -turbogrid -fluent -polyflow -icepak -icemcfd -rsm
Errors will be written to the install.err on the server machine if you have write access to that machine.
4.1.4.3. Silent Media Installation

To run a silent installation from the media, you can either: Copy the contents of each DVD to a folder on the machine's hard disk such that the 140-<number>.dvd files of each DVD are located in the same directory. You can then proceed with the silent installation as described earlier. Place all of the media in separate drives (any combination of virtual ISO mounts or hardware drives) so that they can be accessed simultaneously during the installation. Then run the silent installation as described earlier, but include the additional -media_path2 <path> option for each drive:
INSTALL -silent -install_dir path -product_flag -media_path2 <path>
The installer uses the mount directory from which it was launched as the first media path; you need to specify only the location of the subsequent DVD(s) using the -media_path2 option shown in the example above.
4.1.4.4. Silent Uninstall

You can also run the uninstall silently by issuing the following command:
/ansys_inc/v140/ans_uninstall140 silent
The silent uninstall will automatically uninstall all products for this release and delete the v140 directory and all subdirectories. You will not be prompted for confirmation. To uninstall individual products, use the following product options in conjunction with the -silent argument: Mechanical APDL ANSYS CFX ANSYS CFD-Post -mechapdl -cfx -cfdpost
24
Installing ANSYS, Inc. Products ANSYS FLUENT ANSYS POLYFLOW ANSYS ICEM CFD ANSYS TurboGrid ANSYS Icepak ANSYS Remote Solve Manager Standalone Services -fluent -polyflow -icemcfd -turbogrid -icepak -rsm
For example, to uninstall only TurboGrid and Icepak, issue the following command:
/ansys_inc/v140/ans_uninstall140 silent -turbogrid -icepak
You can also issue the -help option to see a list of valid arguments for a silent uninstall. A record of the uninstall process will be written to ansys_inc/install.log. Any errors messages will be written to ansys_inc/install.err.
25
26
Chapter 5: Post-Installation Instructions

5.1. Post-Installation Procedures for All Products
The following post-installation procedures apply to all products. Individual products may have additional post-installation procedures; please refer to the following sections. After the product is installed, you need to establish some system settings, including pathnames and environment variables. See your shell documentation or man pages file for the shell being used for specific instructions on setting paths and environment variables. 1. Add the following paths to all users' login startup files (i.e., .cshrc , .profile, or .login files).
/ansys_inc/v140/ansys/bin
(or appropriate path to the individual products' executables) (contains ANSLIC_ADMIN utility)
/ansys_inc/shared_files/licensing/lic_admin
2.
Set the following environment variables based on the behavior you want. Set the environment variables following the conventions of your shell. For example, to set an environment variable in the C shell, type:
setenv environment_variable value
For example, to set the DISPLAY environment variable, you type the following, where dev is the workstation hostname or IP address on which to display graphics:
setenv DISPLAY dev:0.0
DISPLAY - set this to the IP address or hostname of the workstation to which the users will output their analysis results. Note that the X server must have permission to connect to the host machine. If you will be using connection functionality, you may have additional environment variables to set. See the section Configuring CAD Products (p. 37) later in this guide for more information. 3. 4. Set the license manager to start automatically at boot time. For platform-specific instructions, see License Manager Automatic Startup Instructions in the ANSYS, Inc. Licensing Guide. Designate server(s) for license checkout and establish necessary user privileges (recommended but not required). For information on these tasks, see Post-Installation Instructions for the License Manager in the ANSYS, Inc. Licensing Guide. Make a backup copy of the /ansys_inc directory using a tape backup command such as tar. Verify the installation by logging out as root (if you installed as root) and logging back in as a regular user and then starting the product to verify that it starts and runs correctly.
5. 6.
Quality Assurance Program: If you require verification of Mechanical APDL, the Mechanical Application, FLUENT, or CFX, ANSYS, Inc. offers Quality Assurance programs. If you are interested in this service, go
27
Chapter 5: Post-Installation Instructions to http://www.ansys.com/About+ANSYS/Quality+Assurance/Quality+Services or call the ANSYS, Inc. Corporate Quality Group at (724) 746-3304.
5.1.1. Post-Installation Procedures for Mechanical APDL (ANSYS) and ANSYS Workbench Products
The following post-installation procedures apply only to the Mechanical APDL (ANSYS) and ANSYS Workbench products. These are in addition to the post-installation procedures noted above for all products. 1. Set the following environment variables based on the behavior you want. Set the environment variables following the conventions of your shell. Not all of these are required for all integrated ANSYS Workbench products (such as ANSYS AUTODYN), but setting them correctly for ANSYS Workbench will in no way hinder the performance of the other products. The ANSYS140_DIR environment variable sets the location of the ANSYS directory hierarchy. The default value is /ansys_inc/v140/ansys. You probably will not need to reset this variable, unless you change the location of the installed files. The ANSYSLIC_DIR environment variable sets the location of the ANSYS licensing directory hierarchy. The default value is /ansys_inc/shared_files/licensing . You probably will not need to reset this variable, unless you change the location of the licensing files. ANSYS140_PRODUCT - set this to the correct product variable to run Mechanical APDL (ANSYS) to start with the correct product without specifying the -p command modifier each time. See the Product Variable Table in the ANSYS, Inc. Licensing Guide for a list of valid product variables. ANSYS_LOCK - set to ON (default) to create file locks to prevent users from opening a new job with the same name and in the same directory as the current job. ANSYS140_WORKING_DIRECTORY - set this variable to the directory you want designated as your working directory. The working directory setting in the launcher will reflect this setting. SPACEBALL2 - set this environment variable to 1 to use a spaceball with Mechanical APDL. ANSYS140_MAT161 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_MSC material (requires an LS-DYNA MAT_161 license). ANSYS140_MAT162 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_DMG_MSG material (requires an LS-DYNA MAT_162 license). ANSBROWSER - set this environment variable to the browser on your system (specify the full path) if the automatic browser detection fails. A browser is needed to view HTML reports and help for the ANS_ADMIN utility and the Mechanical APDL (ANSYS) launcher. By default, ANSBROWSER points to one of several Linux browsers, based on the browser specified in your path (if any). If you will be using connection functionality, you may have additional environment variables to set. See the section Configuring CAD Products (p. 37) later in this guide for more information. 2. Create or update the at. files. The at.allow file should contain the username of all users allowed to run batch jobs; the at.deny file should contain the username of users who are not permitted to run batch jobs. The files consist of one username per line and can be modified only by the superuser. If neither file exists, only root will be able to run batch jobs. The at. files are located in the /etc directory on Linux machines. 3. 4. Run the ANS_ADMIN utility to properly configure ANSYS (depending on the products you are running) or relink ANSYS. Specify the product order as it will appear in the Mechanical APDL (ANSYS) launcher (optional). If you want to specify product order, use the ANSLIC_ADMIN utility. See the ANSYS, Inc. Licensing Guide for more information.
28
Post-Installation Procedures for All Products Explicit Dynamics, Rigid Dynamics, My Computer Background, and Remote Solve Manager (RSM) Users: If you are running ANSYS Workbench on a multi-user RSM machine, the My Computer, Background Solve Process Settings will likely not function as expected due to write permissions for RSM working directories. In this situation, we strongly recommend that you set up RSM as a daemon. This issue also affects Rigid Dynamics and Explicit Dynamics using both My Computer and My Computer, Background Solve Process Settings. Please see Configuring a Multi-User RSM Machine in the RSM documentation for more information.
5.1.2. Post-Installation Procedures for ANSYS CFX

The following post-installation procedures apply only to the ANSYS CFX product. The Linux installation of ANSYS CFX or ANSYS TurboGrid automatically installs the Sun Java 2 Runtime Environment in the /ansys_inc/v140/commonfiles/jre directory. Regardless of whether you have modified your setup files, you can still run ANSYS CFX commands by specifying the full pathname of the commands you want to run. This procedure may be useful if you have several releases of ANSYS CFX installed and you want to run more than one release. Unless you want to run ANSYS CFX commands by typing their full path names, for example cfxroot/bin/cfx5 (where cfxroot is the directory in which ANSYS CFX is installed), your command search paths must be modified to search the directory cfxroot/bin. This can be done by one of the following methods: Modification of individual user setup files You can select Tools> Configure User Startup Files from the ANSYS CFX Launcher to modify your own setup files: .login for the C shell, .profile for the Bourne and Korn shells. The utility can also be run from the command line by entering:
cfxroot/bin/cfx5setupuser
If this modification is done, the ANSYS CFX software will be available every time you log in, just by running the ANSYS CFX commands by name. This method has the advantage that it need not be done by the system administrator, but has the disadvantage that it must be done by each user. User setup can also be run from the command line by entering:
Use the -h option to view the optional commands. If you choose to modify your setup files, you will see a message indicating that your setup files have been changed. You will then need to log out and log in again or source your setup files before you can use the software. Manual execution of a setup script each time the software is used You can also use the Tools menu of the launcher to launch an editor to create new setup scripts which need to be run each time you want to use the ANSYS CFX software. This method has the advantage of not requiring changes to existing setup files and allows you to use different versions of ANSYS CFX software by running different setup files. The disadvantages are that all users must create their own setup files and run them manually in every session in which they want to run ANSYS CFX software. Having created the setup files, users of the C shell then need to do the following to run ANSYS CFX:
source ~/cfx5.login cfx5
29
Chapter 5: Post-Installation Instructions Having created the setup files, users of the Bourne or Korn shell then need to do the following before running ANSYS CFX:
.$HOME/cfx5.profile cfx5
Modification of system setup files The system administrator modifies the setup files (normally /etc/profile), which are run by all users during login, to include the directory cfxroot/bin in the command search path. While this has the advantage of only one file needing to be modified in order to allow all users to use the software, it also: Affects users regardless of whether they use ANSYS CFX Can only be done by the root user Is system dependent
Refer to your system documentation for information about which files to change for your workstations.
5.1.2.1. Setting up ANSYS TurboGrid Release 14.0

Manual modification of individual user setup files To start ANSYS TurboGrid without using full pathnames every time you want to run the ANSYS TurboGrid software, your path must be altered to include the ANSYS TurboGrid directory. This can be done by adding the following line to the .login and .cshrc files in your home directory:
set path=(cfxroot/bin $path)
and these lines to the .profile file in your home directory, and also the .bash_profile if it exists:
PATH=cfxroot/bin:$PATH export PATH
and these lines to the .dtprofile file in your home directory:

PATH=cfxroot/bin:$PATH \ export PATH
With the path altered in this way, you can start ANSYS TurboGrid in the current working directory by typing cfxtg. Modification of system setup files The system administrator modifies the setup files ( normally etc/profile), which are run by all users during login, to include the directory cfxroot/bin in the command search path. While this method has the advantage that only one file needs to be modified to allow all users to use the software, it: Affects users regardless of whether they use ANSYS TurboGrid Can only be done by the root user Is system dependent
Refer to your system documentation for information about which files to change for your workstations.
5.1.2.2. Using the ANSYS CFX Launcher to Set Up Users

To create setup files to be merged or run manually, start the ANSYS CFX Launcher using the command:
cfxroot/bin/cfx5
30
Post-Installation Procedures for All Products and select Tools> Configure User Startup Files. This option runs cfxroot/bin/cfx5setupuser that modifies your setup files or writes the necessary commands to files, which you can merge manually with your existing setup files. If you choose to modify your setup files, you will see a message indicating that your setup files have been changed. You will then need to log out and log in again or source your setup files before you can use the software. User setup can also be run from the command line by entering:
Enter the flag -h to view the optional commands.
5.1.2.3. Verifying the Installation of ANSYS CFX Products

If you are working on a Linux machine and have not used ANSYS CFX before, you will first need to set yourself up to run the ANSYS CFX commands. To keep all the files for the example together, you should first create a new directory in which to run the example. This can be done by typing:
mkdir cfx_example
at the command line. You should then change to this directory by typing:
cd cfx_example
Start the ANSYS CFX Launcher by typing cfx5. To complete testing, perform all the steps in Flow in a Static Mixer. Note: To speed up the process of testing, consider using the provided session files when working with ANSYS CFX-Pre.
5.1.3. Post-Installation Procedures for ANSYS FLUENT

To start ANSYS FLUENT without using full pathnames every time you want to run the FLUENT software, your path must be altered to include the ANSYS FLUENT bin directory. You can do this in the C shell and its derivatives by entering:
set path = (/ansys_inc/v140/fluent/bin $path)
or in the Bourne/Korn shell or bash, by entering:

PATH=(/ansys_inc/v140/fluent/bin $path) export PATH
We recommend adding these statements to your $HOME/.cshrc (C shell), $HOME/.profile (Bourne/Korn shell), or $HOME/.bashrc (bash shell) file for regular use. After installing the ANSYS FLUENT software, you will need to reset the default values in the ANSYS FLUENT launcher as follows: 1. Verify that the FLUENT_INC environment variable is not set. Remove the FLUENT_INC setting from your .cshrc, .profile, or .bashrc file if you have added it for previous versions. Verify that the environment variable is unset by typing:
31

printenv FLUENT_INC
This command should not return anything. 2. Add the following paths to all users' login startup files:
<install_dir>/ansys_inc/v140/fluent/bin
3.
Run the following command:

<install_dir>/ansys_inc/v140/fluent/bin/fluent
4. 5. 6.
Click Default. Click Yes when asked if you want to discard the LAUNCHER history. Click Cancel if you do not wish to start FLUENT at this time. The new defaults will have been saved.
Please refer to the ANSYS FLUENT Quick Start Guide for more information.
5.1.4. Post-Installation Procedures for ANSYS POLYFLOW

POLYFLOW no longer requires the FLUENT_INC environmental variable. It should be deleted as is recommended for FLUENT: Remove the FLUENT_INC setting from your .cshrc, .profile, or .bashrc file if you have added it for previous versions. Verify that the environment variable is unset by typing:
printenv FLUENT_INC
This command should not return anything.
5.1.5. Post-Installation Procedures for ANSYS ICEM CFD

The following post-installation procedures apply only to the ANSYS ICEM CFD product. 1. Add the following paths to all users' login startup files (i.e., .cshrc or .login files). /ansys_inc/v140/icemcfd/<ICEMCFD_OS_DIR>/bin ANSYS ICEM CFD operating system directories are: Hardware Linux Itanium 64 Linux x64 (AMD Opteron) Linux x64 (EM64T) 2. ICEMCFD_OS_DIR linux64 linux64_amd linux64_amd
Add the following environment variable to all users' login startup files. ICEM_ACN - set to /ansys_inc/v140/icemcfd/<ICEMCFD_OS_DIR>/bin
3.
Start ANSYS ICEM CFD by typing icemcfd.
5.1.6. Post-Installation Procedures for ANSYS AUTODYN

The following post-installation procedures apply only to the AUTODYN product.
32
Product Localization Add the following paths to all users' login startup files (i.e., .cshrc or .login files).
/ansys_inc/v140/autodyn/bin
path to the AUTODYN executable
Please refer to the ANSYS AUTODYN Quick Start Guide and What's New documents in the ANSYS AUTODYN help directory for information on starting and running ANSYS AUTODYN.
5.2. Product Localization

Some ANSYS, Inc. products are available in multiple languages, including English, German, and French. For those products that are localized, you are able to view the GUI and messages in the specified language. See your specific product documentation for instructions on choosing a localized version of the product. All products that are localized define the language via the languagesettings.txt file. In most cases, you will not have to manually edit this file. If you do need to edit it manually, you can use one of the following values: en-us (English, default) de (German) fr (French) ANSYS, Inc. applications will look for the languagesettings.txt file in the following locations, in order: 1. 2. $Home/.ansys/v140 <install_dir>/ansys_inc/v140/commonfiles/language
ANSYS, Inc. licensing also looks for the languagesettings.txt in the licensing languages subdirectories in order to display the ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect message and log files in a different language. Some products are not fully localized but offer only the messages in a translated version. See the following section for instructions on translated message file installation.
5.2.1. Translated Message File Installation for Mechanical APDL (ANSYS)

If your ANSYS sales representative has supplied you with message files in your local language, use the following procedures to install and access these files. You must create new message files for each release because error messages may occur in a different order for each release. 1. Create a language-named subdirectory (for example, fr for French) under the /docu directory:
mkdir /ansys_inc/v140/ansys/docu/fr
2. 3.
Copy the message files msgcat.140, msgidx.140, and msgfnm.140 into that subdirectory. Access these files from the Language Selection option of the launcher or via the -l command line option:
ansys140 -l fr
33
5.3. Launching ANSYS, Inc. Products

To launch ANSYS, Inc. products on Linux platforms, issue the appropriate command from the list below. The paths specified assume that you installed the product using the symbolic link to /ansys_inc. If you did not, substitute your installation path for the path given below.
Table 5.1 Startup Commands

Product Mechanical APDL Command /ansys_inc/v140/ansys/bin/ansys140 Notes For a complete list of command line options, see Starting an ANSYS Session from the Command Level in the Operations Guide.
ANSYS Workbench ANSYS CFX ANSYS FLUENT
/ansys_inc/v140/Framework/bin/<platform>/runwb2 /ansys_inc/v140/CFX/bin/cfx5 /ansys_inc/v140/fluent/bin/flu- For a complete list of command line and launcher options, see Starting ent ANSYS FLUENT in the FLUENT Users Guide. /ansys_inc/v140/icemcfd/<platform>/bin/icemcfd /ansys_inc/v140/polyflow/bin/polyman Starts the POLYFLOW MANager. For any other tool, use /ansys_inc/v140/polyflow/bin/<tool>
ANSYS ICEM CFD ANSYS POLYFLOW
ANSYS CFD-Post ANSYS Icepak ANSYS TurboGrid ANSYS AUTODYN
/ansys_inc/v140/CFDPost/bin/cfdpost /ansys_inc/v140/Icepak/bin/icepak /ansys_inc/v140/TurboGrid/bin/cfxtg /ansys_inc/v140/autodyn/bin/autodyn140 solver only
34
Chapter 6: Uninstalling the Software

6.1. Uninstalling ANSYS, Inc. Products
To uninstall a product, issue the following command:
/ansys_inc/v140/ans_uninstall140
Alternatively, if you are using the Mechanical APDL product, you can use the Uninstall option of the ANS_ADMIN utility. To launch ANS_ADMIN, issue the following command:
/ansys_inc/v140/ansys/bin/ans_admin140
1.
From the uninstall panel, choose one of the following uninstall options: Select Products to Uninstall Uninstall all ANSYS Products
If you are not a superuser, you will see a warning message, and then the uninstall continues. 2. If you chose Select Products to Uninstall, you will see a list of products that are installed. Select those products you want to uninstall and click Continue. Then click OK to confirm the list of products to be uninstalled. If you chose Uninstall all ANSYS Products, you will be asked to confirm that you want to uninstall all products. Click Yes. This process will remove all files and directories under and including the /ansys_inc/v140 directory. 3. When the uninstall has completed, click Finish.
In the case of a platform (file server) installation, the uninstall will remove the selected product(s) from all of the Linux platforms.
35
36
Chapter 7: Configuring CAD Products

The connection functionality of all supported CAD products is included with the ANSYS release media, and all CAD functionality except NX is installed by default. To use the connection functionality, you need to ensure that the product is properly licensed, and set any necessary environment variables or other configuration as appropriate. See the manuals for the individual CAD products for information about environment variables and other configuration requirements. For complete information about the files you can import, see Introduction to Import in the ANSYS Connection User's Guide.
Caution
Be sure to install Mechanical APDL (ANSYS) and the connection functionality from the same release. If you attempt to run the latest connection functionality on a machine that is running an earlier release of Mechanical APDL, or vice versa, the connection may fail. If you are running NX, some additional configuration may be required, especially if you chose to skip configuring these products during the installation process. The following sections describe any postinstallation configuration procedures that are required and how to manually configure NX if you did not configure NX during installation or if you are updating your CAD versions. These methods are all described in the following sections.
7.1. Using the CAD Configuration Manager

The CAD Configuration Manager utility allows you to configure geometry interfaces for ANSYS Workbench and ICEM CFD Direct CAD interfaces on Linux systems. CAD configuration is typically handled during the product installation; however, if you chose to skip those steps, or if you make changes to your local CAD configuration between releases (for example, you move or update your CAD package, or remove it entirely), you can use this utility. Note that only Reader mode for NX is supported on Linux. The CAD Configuration Manager on Linux is organized into several tabs: CAD Selection Creo Parametric (options are active on Windows only) NX Teamcenter Engineering (options are active on Windows only) CAD Configuration
An administrative user has the option to configure or unconfigure any selected CAD systems either for the present user's environment or for all users, as indicated by the Configuration actions apply to options. When the original installation was performed by a non-administrative user, an administrative user will only be allowed to configure or unconfigure for all users. In this situation, NX configure and unconfigure actions are skipped. Non-administrative users will only be allowed to configure for themselves. Any user-specific configuration settings take precedence over global configuration settings.
37
Chapter 7: Configuring CAD Products This document describes how to use the CAD Configuration Manager as a wizard on Linux systems, beginning with the CAD Selection tab and using the Next button to progress through the configuration process. You can also manually select each tab to progress through the configuration process; both methods work the same. However, the applicable tabs will not be enabled until you choose the associated product on the CAD Selection tab. You can choose Help to view instructions on using the CAD Configuration Manager at any time. If the help does not load into your default browser, set the BROWSER environment variable to the path of your HTML viewer (such as Mozilla or Firefox) and restart the CAD Configuration Manager. 1. Run the following command to start the CAD Configuration Manager, substituting the full installation path if different than /ansys_inc:
/ansys_inc/v140/commonfiles/CAD/bin/ansmono Ans.CadInt.CADConfigUtilityGUI.exe.
2.
On the CAD Selection tab, choose the ANSYS products and the CAD products that you need to configure. You must select at least one ANSYS product and at least one CAD product to enable the remaining functionality. If you selected NX as one of your CAD products, the NX tab opens. a. b. c. Enter or browse to the NX installation location. The NX custom directory file is not applicable on Linux and can be ignored as it will be disabled. Click Next.
3.
4.
The CAD Configuration tab opens. a. b. c. Click the Configure Selected CAD Interfaces button. When the configuration for all products is complete, log entries appear, listing those products that were successfully configured and those that were not. Address any errors and reconfigure. For more details, click the Display Configuration Log File button to see a detailed log file.
5.
When all of your CAD products have been successfully configured, click Exit.
You can review the CAD Configuration Manager log file, CADConfigurationMgr.log, in /ansys_inc. If you do not have write permissions to the /ansys_inc directory, the log file will be written to $TEMP. If you have not defined $TEMP, the log file is written to /tmp. When /tmp is not accessible, this file will be written to the current working directory.
7.1.1. Unconfiguring
If you need to unconfigure any of your CAD products, follow the steps above, but choose Unconfigure Selected CAD Interfaces on the CAD Configuration tab.
7.1.2. Running the CAD Configuration Manager in Batch Mode

You can configure ANSYS Geometry Interfaces by supplying the CAD Configuration Manager with arguments specific to the CAD sources you want to make available. The following table contains a list of supported arguments. The command to run the CAD Configuration Manager in batch mode on Linux is:
/ansys_inc/v140/commonfiles/CAD/bin/ansmono Ans.CadInt.CADConfigurationUtility.exe -arguments
38
Using the CAD Configuration Manager Argument unconfigure Value None Comment Results in any specified CAD sources being unconfigured. When this flag is absent, the CAD Configuration Manager will attempt to configure all designated CAD sources. Configure/unconfigure NX Geometry Interface to Workbench.The argument UGII_BASE_DIR must also be specified. This should agree with environment variable UGII_BASE_DIR. Not required with unconfigure operation.
UG_CONFIG_WB UGII_BASE_DIR
None Full path to NX installation (quotations are required if there are spaces in the path). None
UG_USE_COLORS
Process NX entity colors as possible source of attributes and named selections. Not required with unconfigure operation.
Note
All arguments require a dash (-) before them in order to be properly recognized by the CAD Configuration Manager. Arguments' values should not have a dash preceding them. For example, you can configure the NX Geometry Interface to ANSYS Workbench from the command line by using the following:
<installpath>/commonfiles/CAD/bin/ansmono Ans.CadInt.CADConfigurationUtility.exe -UG_CONFIG_WB -UGII_BASE_DIR "<pathtonx>" -UG_USE_COLORS
where installpath is the /v140 directory under the installation directory. To unconfigure the same CAD Interface, the command would be:
<installpath>/commonfiles/CAD/bin/ansmono -unconfigure -UG_CONFIG_WB Ans.CadInt.CADConfigurationUtility.exe
Although the argument order does not matter, an argument value must immediately follow its argument.
7.1.3. NX Configuration
Running the CAD Configuration Manager for NX performs the following steps to activate the NX reader: Registers the NX Reader for ANSYS Workbench by copying the file UGNX#.Component.XML from /ansys_inc/v140/aisol/CADIntegration/UG to either /ansys_inc/v140/commonfiles/registry/linx64/append when the configuration manager is in administrative mode or to $HOME/.config/Ansys/140/UserRegFiles_NNNN/append, when the CAD Configuration Manager is run by a non-administrator. The CAD Configuration Manager ensures that only one version of the file exists in the target location. UGNX# is the NX version detected by the CAD Configuration Manager, and NNNN is a numeric identifier appended to the UserRegFiles directory. You must specify the environment variable UGII_BASE_DIR, which must match the install location supplied to the CAD Configuration Manager. The WorkBench Reader for NX will not work without this variable set properly, as it is required for proper startup of the CAD.
The CAD Configuration Manager does not configure the ICEM CFD Direct CAD Interface to NX on Linux. To manually configure this product, set the environment variable UGII_VENDOR_DIR to /anRelease 14.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
39
Chapter 7: Configuring CAD Products sys_inc/v140/icemcfd/linux64_amd/dif/ug/lib/ug/ugXX_vendor_dir. Here, XX corresponds to the version of NX intended to load the NX Direct CAD Interface: XX=22 for NX4 XX=23 for NX5
7.2. Configuring NX
To use NX in reader mode, you will not need to perform any additional configuration steps. Mechanical APDL (ANSYS) and ICEM CFD use the following three NX environment variables, which are set during the NX installation: UGII_BASE_DIR UGII_ROOT_DIR UGS_LICENSE_SERVER To use NX in plug-in mode, you need to set additional environment variables. ANSYS provides default settings for some of the necessary environment variables. In general, you will not need to reset these variables. They are described below should you need to modify or reset them. ANSCON_CONFIG_DIR: Sets the location of the config.anscon.140 configuration file. This environment variable is used only if the ANSYS140_DIR has not been set. Defaults to /ansys_inc/v140/ansys/ac4/data. UGII_VENDOR_DIR: This environment variable is not set during the installation process and can only be set in a user's start-up file or at command level before running NX. This environment variable defines the Mechanical APDL (ANSYS) or ICEM CFD menu for NX. You must set this environment variable if you will be running the connection for NX product from inside NX. This environment variable tells NX where to find the Mechanical APDL or ICEM CFD program.
Note
You cannot set the UGII_VENDOR_DIR for both Mechanical APDL and ICEM CFD. You must set it for only one product. For Mechanical APDL, set this environment variable as follows:
setenv UGII_VENDOR_DIR /ansys_inc/v140/ansys/ac4/bin/ug50/<platform>
For ICEM CFD, set this environment variable as follows:

setenv UGII_VENDOR_DIR $ICEM_ACN/dif/ug/lib/ug/ugNN_vendor_dir
Where NN = 22 for NX4, 24 for NX6 UGII_OPTION: This environment variable sets the case of characters in directory names on the current system. You must set this environment variable if the directory names in this environment variable or in ANSCON_CONFIG_DIR contain uppercase characters. Possible options are MIXED, LOWER or UPPER. We recommend the following setting:
setenv UGII_OPTION MIXED
7.2.1. Configuring the Connection for NX

No additional configuration is needed to configure the connection capability for NX. 40
Configuring NX However, to export to Mechanical APDL (ANSYS) from NX, you will need the config.anscon.140 file. This file is installed for all users in /ansys_inc/v140/ansys/ac4/data/. Here is a sample config.anscon.140 file:
ANSYS_CMD ANSYS_GRAPHIC_DEVICE ANSYS_SOLVER ANSYS_SELECTED_LAYERS ANSYS_GEOMETRY_TYPE ANSYS_NEUTRAL_FORMAT ANSYS_PRODUCT_NAME /ansys_inc/v140/ansys/bin/ansys140 x11-stat Sparse** 1-256** Solids Only** Yes ANSYS
You can modify the config.anscon.140 file to set information for all NX users. NX users can copy this file to their working directory and configure it for their own projects. NX users should see Using the Configuration Editor in the ANSYS Connection User's Guide for more information. See Setting ANSYS Configuration Parameters in the ANSYS Connection User's Guide for more information about the config.anscon.140 file.
7.2.2. Configuring the Geometry Interface for NX for ANSYS Workbench Products
If you chose to skip configuring the Geometry Interface for NX during the ANSYS Workbench installation, you may need to run the CAD Configuration Utility's CAD Interface Configuration > Configure UG NX Reader for Workbench option. 1. 2. 3. 4. 5. Launch CAD Configuration Utility. Select CAD Interface Configuration to continue. Select Configure UG NX Reader for Workbench to continue. Enter the directory path to the NX installation path. Select OK to continue. Select EXIT to close CAD Configuration Utility.
41
42
8.1. Installation Troubleshooting
This section lists problems and error messages that you may encounter while installing and/or running ANSYS, Inc. products. After each situation description or error message is the user action required to correct the problem. You can also find answers to commonly-asked questions on our customer portal. After you log in to the customer portal, select Online Support> Installation/System FAQs. Then select either the Windows or Linux link. For information on licensing-related errors, see the Troubleshooting section of the ANSYS, Inc. Licensing Guide. In addition, this appendix describes the ansys_pid utility, which is useful for troubleshooting some problems.
8.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information

You can use the Gather Diagnostic Information option of the ANSLIC_ADMIN utility to query the system for various pieces of information that may be needed for troubleshooting certain problems. This option collects information about the system as well as about ANSYS licenses and sends all of the information that it collects to the log area. At times it may be necessary to provide the information for technical support. Use the Write to File button at the bottom of the ANSLIC_ADMIN to write a file. Then forward the file to the appropriate person.
8.1.2. The GUI Installation Process Hangs

If the GUI installation process appears to hang during file extraction, with no activity appearing in the message window, press ENTER on the command window used to start the installation. When the installation is complete, check the message window carefully for any installation errors or warnings; however, this situation rarely causes installation errors. If the installation does not progress beyond the extraction of any single file during the file extraction phase, you may have insufficient disk space in the temporary directory that the file extraction utility uses. Be aware that some components require a lengthy extraction time; we recommend allowing up to 30 minutes for these components to extract if you are running on a particularly old or slow system. To resolve this problem, remove files from your $TEMP directory to free up disk space, or increase the size of any disk quotas on your $TEMP directory.
8.1.3. The Target Machine Does Not Have a DVD Drive

If the target machine does not have a DVD drive, we recommend that you download the installation files from the Customer Portal on www.ansys.com or follow the instructions in Mounting the DVD Instructions for DVD Installations (Linux x64 Only) (p. 14) to mount to a machine that does have a DVD drive. You can also mount the DVD on a Windows machine, then copy all of the files (using binary format) to
43
Chapter 8: Troubleshooting the target Linux machine in the exact same directory structure as is on the DVD, and follow the instructions in Downloading the Installation Files. However, we strongly recommend against copying the Linux installation files from a Windows machine; such a file transfer can result in unpredictable behavior.
8.1.4. The Online Help System Does Not Run Properly

The online documentation for the Linux versions of the ANSYS ICEM CFD and ANSYS Icepak products uses the Oracle Help browser. Several unusual behaviors and their cause and resolution are listed. If you request help and nothing happens: On a few machine configurations, the online help system can take up to 60 seconds longer than the product to initialize, due to the large amount of documentation available. If you request help within 60 seconds of running the product, you may simply need to wait a few more seconds for help to start. If you have minimized the help windows, activating help will not restore them to their original size. Instead of minimizing help, you can close the help windows when you are done using help. This does not exit the help, so the help system will still be available quickly next time you request help. The help system may have aborted due to a system error. You cannot restart the help system from your current session. You can save your work and restart a new session.
If the text in the online help is unclear (the fonts are too small, too large, or rough around the edges): Use the [+] or [-] keys to enlarge or reduce the fonts. Depending on your system's configuration and installed fonts, you may need to experiment with the [+] and [-] keys to adjust your font size. The [+] will increase the font size, and the [-] will decrease it. On some systems, you need to use the [+] and [-] keys on the standard keypad, rather than those on the number pad.
If, when starting ICEM CFD or Icepak over Exceed, all of the Linux window controls (borders, close buttons, etc.) disappear, or the help windows appear but are small and in the top left corner of the screen: You need to change your window manager settings in Exceed. See the section Note to Exceed Users earlier in this guide for information on changing your window manager settings. If changing the window manager settings does not correct the problem, we recommend upgrading to Exceed 7.0 or higher. If the problem still occurs, change the Window Manager to X. You must start an X Windows manager like mwm before running ICEM CFD or Icepak.
Mouse clicks are slow to initiate an action. This is a result of the mouse click signals traveling over the network via an Exceed connection. Try adjusting the Exceed Performance settings. See the section Note to Exceed Users earlier in this guide for information on specific changes we suggest.
8.1.5. CAD Configuration Manager Help Does Not Load

If the help for the CAD Configuration Manager does not load into your default browser, set the BROWSER environment variable to the path of your HTML viewer (such as Mozilla or Firefox) and restart the CAD Configuration Manager.
8.1.6. Cannot Enter Data in Text Fields

SUSE On some SUSE Linux systems, if you cannot enter data in text fields during the installation or when using the ANSLIC_ADMIN utility, you may be encountering a Tcl incompatibility. To correct the 44
Installation Troubleshooting problem, unset the following environment variables before running the installation or the ANSLIC_ADMIN utility: QT_IM_MODULE XMODIFIERS GTK_IM_MODULE You should reset these environment variables when you are finished running the installation or using ANSLIC_ADMIN. Do not permanently unset these environment variables as doing so could affect other applications. Red Hat If you are installing on Linux Red Hat 5 machines on the local console, and you are unable to enter text into any of the text fields in the installer, you may have to disable SCIM (Smart Common Input Method) as follows: In KDE: Choose [K Menu] >Settings >Input Method In GNOME: Choose System >Preferences >More Preferences >Input Methods. In other window managers: Run program im-chooser. Select Never Use Input Methods. Then rerun the installation.
8.1.7. Download and Installation Error Messages

The current platform type is not selected and is not included in current download files. Please make sure that you are using the correct media or downloaded file. Continuing with a platform installation may require additional post-install configuration. Do you wish to continue? This message occurs if you have selected a platform for installation that does not match the files you are trying to install (either from the installation DVD or from downloaded installation files). Cannot find file <product>.tar in directory <dvd_dir> This error may appear during the ANSYS installation if you have entered the wrong DVD pathname. Check Mounting the DVD Instructions for DVD Installations (Linux x64 Only) (p. 14) and enter the correct pathname for your platform. Licensing files currently installed for <platform> are more recent than those on the installation media. The <platform> files will not be installed and will be deselected. This Linux-only message appears during an ANSYS, Inc. product installation if the installed license manager files are newer than the ones being installed. You should always use the newest files. However, due to system format changes or other unlikely scenarios, the date check could produce incorrect results. To override the date check and force the installation to always install the files from the media, regardless of the file dates, re-run the installation with the -nodatecheck option. We strongly recommend that you exercise caution when running the installation with the -nodat-
45
Chapter 8: Troubleshooting echeck option; installing older license files can result in licensing errors and the inability to run ANSYS, Inc. products.
8.1.8. System-related Error Messages

Error, could not open display. Either the DISPLAY environment variable is not correct or the xhosts command was not properly set. See the Basic Analysis Guide for specific graphics information. ***Error, ANSYS140_DIR environment variable is not set. This is a fatal error exiting. This message indicates that the ANSYS140_DIR environment variable was not set where necessary for licensing. This environment variable (which is set in the scripts that run ANSYS) should be set to the release-specific installation directory.
8.1.9. High Performance Computing Error Messages

The following error messages are associated with the High Performance Computing solvers. mpid: Error: HP MPI version incompatibility detected You may encounter this or a similar message if you attempt to use ANSYS 14.0 with a different version of MPI than is supported. See the Parallel Processing Guide for a complete list of supported MPI versions.
8.2. Installation Troubleshooting - Mechanical APDL (ANSYS)

The items listed below apply only to the Mechanical APDL (ANSYS) product.
8.2.1. Your batch jobs terminate when you log out of a session
On some systems, you may need to use the nohup option to allow batch jobs to continue running after you log out of a session. If you are running via the Launcher, select Options> Use nohup To Start Batch Runs With Output Sent to File Only. We do not recommend using this setting on systems that automatically set nohup.
8.2.2. Japanese/Chinese characters display in status bar windows on Mechanical APDL (ANSYS) on Red Hat AS 4.0
If you are running the traditional Mechanical APDL (ANSYS) interface and see Japanese/Chinese characters in the status bar windows, you will need to reinstall Red Hat, picking only English. This problem is caused by choosing to install "Everything" during the Red Hat Linux OS setup, thus installing all languages. If you then install Mechanical APDL and do a solve with the traditional interface, you will see Japanese or Chinese text in the solve status window. This bug will not be fixed.
8.2.3. Mechanical APDL (ANSYS) Documentation File for User Interface Error Messages
Missing or erroneous documentation files for user interface. Command ignored.
46
Installation Troubleshooting - Mechanical APDL (ANSYS) Verify that the documentation list file for the user interface exists in the /ansys_inc/v140/ansys/gui/en-us/UIDL subdirectory.
ls -l /ansys_inc/v140/ansys/gui/en-us/UIDL/menulist140.ans
The system should respond with:

-rw-r--r-- 1 root 23 Jan 8 11:50 /ansys_inc/v140/ansys/gui /en-us/UIDL/menulist140.ans
Make sure that the pathnames in the menulist140.ans file are correct.
8.2.4. Launcher Error Messages

Some of the more common error messages follow. See the ANSYS, Inc. Licensing Guide for licensing-related launcher messages. ***Cannot create required <profile> file. Therefore, cannot write to profile information during this launcher session. If you see this error, you cannot add or modify profile information during this launcher session. Verify that you have write access to the directory and restart the launcher session. Typically, this directory is C:\Documents and Settings\<user name>\Application Data\Ansys\v140\launcher on Windows or ~/.ansys/v140/launcher on Linux.
8.2.5. FORTRAN Runtime Error Messages

The following error messages occur if the user is running Mechanical APDL (ANSYS) in a directory in which the user does not have write permission, or if Mechanical APDL files (i.e., Jobname.RST, Jobname.DB) exist in the current directory but the user does not have write permissions to the files. The specific messages that appear on each system are shown below.
8.2.5.1. Intel Linux 64 Systems

Input/Output Error 177: Creat Failure In Procedure: fappnd At Line: 72 Statement: Formatted WRITE Unit: 19
8.2.5.2. Intel EM64T Linux x64 Systems

forrtl: Permission denied forrtl: severe (9): permission to access file denied, unit 19, file /build/v140/ansys/objs
8.2.5.3. AMD Opteron Linux x64 Systems

***ERROR
47
Chapter 8: Troubleshooting Unable to open file /build/v140/ansys/objs/file.err for WRITE. Check directory and file permissions.
8.3. Installation Troubleshooting - ANSYS Workbench

8.3.1. Startup or Graphics Problems
To minimize graphics problems, always verify that you are running the latest graphics drivers provided by your computer's hardware manufacturer. If you are running ANSYS Workbench on Linux and experience problems at startup or with the GUI or graphics displaying correctly, and you are running in accelerated graphics mode, you may need to relaunch ANSYS Workbench using the -oglmesa flag to activate software rendering:
runwb2 -oglmesa
If ANSYS Workbench detects that graphics problems are causing crashes, it will automatically switch to software rendering. ANSYS Workbench also will use software rending mode by default when running on a remote display, or on a local display if the hardware does not appear to be accelerated. To revert to accelerated graphics mode, launch ANSYS Workbench using the -oglhw flag:
runwb2 -oglhw
If you are running under Exceed3D, try the following settings if you are having graphics problems: Turn off the graphics (hardware) acceleration option in Exceed3D options. If graphics acceleration is on, turn on the GLX 1.3 option.
Any version of Exceed that does not have the GLX 1.3 option is unlikely to function correctly with graphics acceleration.
8.4. Installation Troubleshooting - ANSYS CFX

8.4.1. CFX Distributed Parallel Runs Fail
On some SLES machines (typically ones with more than one network card), the default configuration of /etc/hosts will cause CFX distributed parallel runs to fail. In such cases, the problem might be solved by editing the /etc/hosts file to remove all lines that contain redundant loopback addresses. Do not remove the line with the first loopback address, which is typically 127.0.0.1.
8.5. Contacting Technical Support

Technical Support for ANSYS, Inc. products is provided either by ANSYS, Inc. directly or by one of our certified ANSYS Support Providers. Please check with the ANSYS Support Coordinator (ASC) at your company to determine who provides support for your company, or go to www.ansys.com and select About ANSYS> Contacts and Locations. The direct URL is: http://www1.ansys.com/customer/public/supportlist.asp. Follow the on-screen instructions to obtain your support provider contact information. You will need your customer number. If you don't know your customer number, contact the ASC at your company. If your support is provided by ANSYS, Inc. directly, Technical Support can be accessed quickly and efficiently from the ANSYS Customer Portal, which is available from the ANSYS Website (www.ansys.com) under Support> Technical Support where the Customer Portal is located. The direct URL is: http://www.ansys.com/customerportal. 48
Contacting Technical Support One of the many useful features of the Customer Portal is the Knowledge Resources Search, which can be found on the Home page of the Customer Portal. Systems and installation Knowledge Resources are easily accessible via the Customer Portal by using the following keywords in the search box: Systems/Installation. These Knowledge Resources provide solutions and guidance on how to resolve installation and licensing issues quickly. NORTH AMERICA All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Toll-Free Telephone: 1.800.711.7199 Fax: 1.724.514.5096 Support for University customers is provided only through the ANSYS Customer Portal. GERMANY ANSYS Mechanical Products Telephone: +49 (0) 8092 7005-55 Email: support@cadfem.de All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. National Toll-Free Telephone: German language: 0800 181 8499 English language: 0800 181 1565 International Telephone: German language: +49 6151 3644 300 English language: +49 6151 3644 400 Email: support-germany@ansys.com UNITED KINGDOM All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +44 (0) 870 142 0300 Fax: +44 (0) 870 142 0302 Email: support-uk@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. JAPAN CFX , ICEM CFD and Mechanical Products
49
Chapter 8: Troubleshooting Telephone: +81-3-5324-8333 Fax: +81-3-5324-7308 Email: CFX: japan-cfx-support@ansys.com; Mechanical: japan-ansys-support@ansys.com FLUENT Products Telephone: +81-3-5324-7305 Email: FLUENT: japan-fluent-support@ansys.com;POLYFLOW: japan-polyflow-support@ansys.com;FfC: japanffc-support@ansys.com; FloWizard: japan-flowizard-support@ansys.com Icepak Telephone: +81-3-5324-7444 Email: japan-icepak-support@ansys.com Licensing and Installation Email: japan-license-support@ansys.com INDIA ANSYS Products (including FLUENT, CFX, ICEM-CFD) Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +91 1 800 233 3475 (toll free) or +91 1 800 209 3475 (toll free) Fax: +91 80 2529 1271 Email: FEA products: feasup-india@ansys.com;CFD products: cfdsup-india@ansys.com;Installation: installationindia@ansys.com FRANCE All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Toll-Free Telephone: +33 (0) 800 919 225 Email: support-france@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. BELGIUM All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +32 (0) 10 45 28 61 Email: support-belgium@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. SWEDEN All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. 50
Contacting Technical Support Telephone: +44 (0) 870 142 0300 Email: support-sweden@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. SPAIN and PORTUGAL All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +33 1 30 60 15 63 Email: support-spain@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. ITALY All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +39 02 89013378 Email: support-italy@ansys.com Support for University customers is provided only through the ANSYS Customer Portal.
51
52
ANSYS, Inc. Installation Guide for Windows
Release 14.0 November 2011 00XXXX


Disclaimer Notice

Table of Contents
1. Installation Prerequisites for Windows ................................................................................................... 1 1.1. System Prerequisites ......................................................................................................................... 3 1.1.1. CAD Support ............................................................................................................................ 4 1.2. Disk Space and Memory Requirements ............................................................................................. 6 1.2.1. Setting the /3GB Switch on Windows 32-bit .............................................................................. 6 1.3. Software Prerequisites ...................................................................................................................... 7 1.4. GPU Requirements ........................................................................................................................... 7 1.5. Additional Hardware and Software Requirements ............................................................................. 8 1.5.1. SpaceBall Support .................................................................................................................... 9 1.5.1.1. SpaceBall Support for FLUENT Components ..................................................................... 9 1.5.2. Using Exceed ........................................................................................................................... 9 1.6.Third-Party Software and other Security Considerations ..................................................................... 9 2. Platform Details .................................................................................................................................... 11 3. Pre-Installation Instructions ................................................................................................................. 15 3.1. Downloading the Installation Files ................................................................................................... 15 3.2. Installing from a DVD ..................................................................................................................... 15 4. Installing the Software .......................................................................................................................... 17 4.1. Installing ANSYS, Inc. Products ......................................................................................................... 17 4.1.1. Product Installation ................................................................................................................ 17 4.1.2. License Manager Installation .................................................................................................. 21 4.1.2.1. Registering the License Server ....................................................................................... 22 4.1.3. Network Installation and Product Configuration ...................................................................... 22 4.1.4. Silent Mode Operations .......................................................................................................... 25 4.1.4.1. Silent Product and License Manager Installation ............................................................. 26 4.1.4.2. Silent Product Configuration/Unconfiguration ............................................................... 29 4.1.4.3. Silent Media Installation ................................................................................................. 29 4.1.4.4. Silent Uninstall .............................................................................................................. 29 5. Post-Installation Instructions ............................................................................................................... 31 5.1. Post-Installation Procedures for All Products .................................................................................... 31 5.1.1. Post-Installation Procedures for Mechanical APDL (ANSYS) and ANSYS Workbench Products .... 32 5.1.2. Post-Installation Procedures for ANSYS CFX and ANSYS CFD-Post ............................................ 33 5.1.3. Post-Installation Procedures for ANSYS AUTODYN ................................................................... 33 5.1.4. Post-Installation Procedures for ANSYS FLUENT ....................................................................... 34 5.1.5. Post-Installation Procedures for ANSYS POLYFLOW .................................................................. 34 5.1.6. Post-Installation Procedures for Other Products ...................................................................... 34 5.2. Launching ANSYS, Inc. Products ....................................................................................................... 35 5.3. Running the ANS_ADMIN Utility for Mechanical APDL (ANSYS) /ANSYS Workbench Products ........... 35 5.4. Product Localization ....................................................................................................................... 35 5.4.1.Translated Message File Installation for Mechanical APDL (ANSYS) /ANSYS Workbench Products ......................................................................................................................................... 36 6. Uninstalling the Software ..................................................................................................................... 37 6.1. Uninstalling ANSYS, Inc. Products .................................................................................................... 37 6.1.1. Uninstalling Licensing Components ........................................................................................ 38 7. Configuring CAD Products .................................................................................................................... 39 7.1. Using the CAD Configuration Manager ............................................................................................ 39 7.1.1. Unconfiguring ........................................................................................................................ 42 7.1.2. Running the CAD Configuration Manager in Batch Mode ..................................................... 42 7.1.3. Uninstalling ........................................................................................................................... 44 7.1.4. Creo Parametric Configuration ............................................................................................... 44 7.1.4.1. Configuring the Connection for Creo Parametric ............................................................ 45
iii
ANSYS, Inc. Installation Guide for Windows 7.1.4.1.1. The WBPlugInPE.dat File and config.pro File ........................................................... 46 7.1.4.1.2.The config.pro File ................................................................................................. 46 7.1.4.1.3.The config.anscon.140 File ..................................................................................... 47 7.1.4.2. Creo Parametric Environment Variables .......................................................................... 47 7.1.5. NX Configuration ................................................................................................................... 47 7.1.5.1. Configuring the Connection for NX ................................................................................ 47 7.1.5.2. Configuring for Teamcenter Engineering ........................................................................ 48 7.1.6. ANSYS ICEM CFD Configuration .............................................................................................. 48 7.2. Configuring CADNexus/CAPRI CAE Gateway for CATIA V5 ................................................................ 48 8. Troubleshooting .................................................................................................................................... 51 8.1. Installation Troubleshooting ............................................................................................................ 51 8.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information ......................................................... 51 8.1.2. Uninstall Gives Access Denied Error Message .......................................................................... 51 8.1.3. Uninstall on Windows 7 and Vista Systems Gives Compatibility Error Message ......................... 51 8.1.4. A .chm File Does Not Display Properly Across a Network .......................................................... 52 8.1.5. Products Crash with an Application Error ................................................................................ 52 8.1.6. Product Installation Does Not Create Start Menu Item for ANSYS and CAD Plugins Do Not Work .............................................................................................................................................. 52 8.1.7. Product Installation Displays Security Warning Dialogs or Silent Product Installation Hangs on a Network Install ............................................................................................................................. 52 8.1.8. System-related Error Messages ............................................................................................... 53 8.1.9. CasPol Error Messages ............................................................................................................ 53 8.2. Installation Troubleshooting - Mechanical APDL (ANSYS) and ANSYS Workbench Products ............... 53 8.2.1. The Mechanical APDL Launcher is Excessively Slow to Start ..................................................... 53 8.2.2. Display Problems on Windows XP ........................................................................................... 53 8.2.3. Display Problems on Windows 7 and Vista .............................................................................. 54 8.2.4. ANS_ADMIN Error Messages ................................................................................................... 54 8.2.5. Mechanical APDL Product Launcher Error Messages ................................................................ 54 8.2.6. Distributed ANSYS Platform MPI Error Messages ..................................................................... 54 8.2.7. ANSYS Workbench Products Troubleshooting ......................................................................... 55 8.3. Installation Troubleshooting - ANSYS CFX ........................................................................................ 56 8.3.1. TurboGrid Mouse Behavior Problems ...................................................................................... 56 8.4. Contacting Technical Support ......................................................................................................... 56
List of Tables
1.1. Supported Windows Platforms ................................................................................................................ 3 1.2. Supported Products by Platform ............................................................................................................. 4 1.3. CAD Support by Platform ........................................................................................................................ 4
iv
Chapter 1: Installation Prerequisites for Windows

This document describes the steps necessary to correctly install and configure all ANSYS, Inc. products on Windows platforms for Release 14.0. These products include: ANSYS Structural Mechanics ANSYS Mechanical Products (includes ANSYS Mechanical and Mechanical APDL) ANSYS Customization Files ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFX (includes ANSYS CFD-Post) ANSYS FLUENT (includes ANSYS CFD-Post) ANSYS TurboGrid ANSYS POLYFLOW (includes ANSYS CFD-Post) ANSYS CFD-Post only ANSYS AQWA ANSYS ICEM CFD ANSYS ICEM CFD Creo Parametric Interface ANSYS ICEM CFD NX Interface ANSYS Icepak (includes ANSYS CFD-Post) Remote Solve Manager Standalone Services TeamCenter Engineering AutoCAD ACIS CATIA, Version 4 CATIA, Version 5 Creo Elements/Direct Modeling Autodesk Inventor JTOpen
ANSYS Explicit Dynamics
ANSYS Fluid Dynamics
ANSYS Offshore ANSYS Additional Tools
ANSYS PDM Interfaces ANSYS Geometry Interfaces
Chapter 1: Installation Prerequisites for Windows NX Parasolid Creo Parametric Solid Edge SolidWorks
Note
ANSYS Workbench and ANSYS EKM Desktop are installed by default as product components to most ANSYS, Inc. products. ANSYS Workbench is not installed as part of the products under ANSYS Additional Tools, nor with the CFD-Post only option. ANSYS Workbench includes the following applications: The Mechanical Application DesignModeler Design Exploration Meshing Remote Solve Manager TGrid FE Modeler EKM Desktop
Because some of these applications can be run as standalone applications without ANSYS Workbench, you will see some but not all of these listed separately as options when you uninstall. In such cases, you will need to select those options in order to uninstall those components. Where supported, IGES and STEP Geometry Interfaces will be installed. Some procedures apply only to specific products and are so noted.
Important Notice

The following features are new or changed at Release 14.0. Please review these items carefully. ANSYS, Inc. has discontinued support for the HP-UX Itanium 64, the Sun Solaris x64, IBM AIX 64, and the Linux 32-bit platforms for all products. ANSYS, Inc. has discontinued support for the Linux Itanium 64 platform for the ICEM CFD product.
System Prerequisites Third-party products that are used as part of the installation process are now documented in the ANSYS, Inc. Installation Guides. The ASAS product has been retired. The FATJACK, BEAMCHECK, and Splinter products are now installed automatically with the Mechanical application. The Pro/ENGINEER CAD product has been rebranded to Creo Parametric. The ANSYS, Inc. product installation now supports Creo Parametric, NX, SolidWorks, and Autodesk Inventor reader options. You can now choose to install the Reader (no CAD installation required) or the Associative Plug-in (CAD installation required) options for these CAD products. The release version now appears with each product selection in the Start menu on Windows. You can now specify two DVD drives during a silent installation to accommodate the installation process spanning two DVDs. See the discussion on Silent Mode Operations in the Installation Guide for your platform for more information. You can now choose to install and uninstall only Remote Solve Manager (RSM). RSM will continue to be installed as part of ANSYS Workbench. You can now choose to install and uninstall only the EKM Server on Windows platforms. The use of files requiring 777 permissions on Linux has been minimized. For more information on remaining full-permission files and softlinks, see the section Third-Party Software and Other Security Considerations in the ANSYS, Inc. Linux Installation Guide. The PDF version of the documentation that is available on the Customer Portal is now unprotected, allowing you to copy and paste content from the PDFs into other locations. This capability is especially useful if you want to use command snippets that are available throughout the documentation.
1.1. System Prerequisites

ANSYS 14.0 is supported on the following Windows platforms and operating system levels. For up-todate information on hardware platforms or operating systems that have been certified, go to http://www.ansys.com/Support/Platform+Support. (This URL is case-sensitive.)
Table 1.1 Supported Windows Platforms

Processor x64 (64-bit) Operating System Windows XP 64 SP2, Windows Vista 64 SP1, Windows 7, Windows HPC Server 2008 R2[1] Windows XP SP2, Windows Vista SP1, Windows 7 Platform architecture Availability (directory name) winx64 Download, DVD
x86 (32-bit)
intel
Download, DVD
1.
Windows HPC Server 2008 R2 is supported only for select solvers for parallel high performance execution.
Note
Home editions of Windows operating systems are not supported. If you are running Internet Explorer 8 on Windows XP 32-bit, you must use Windows XP SP3.
Chapter 1: Installation Prerequisites for Windows Supported Platforms for High Performance Computing Please see the discussions on Configuring Distributed ANSYS and Configuring ANSYS CFX Parallel later in this guide for detailed information on supported platforms for distributed computing.
Table 1.2 Supported Products by Platform

Product Windows 64-bit X Windows 32-bit X Windows HPC Server 2008
ANSYS Workbench data-integrated and native applications Mechanical APDL (ANSYS) CFX TurboGrid ICEM CFD AUTODYN LS-DYNA FLUENT AQWA POLYFLOW Icepak EKM Server 1. 2.
Standalone Solvers and Applications X X X X X X X 1 X X X X X X X X X X X X X 2 2 2 2
Supported as a 32-bit application Solver only support
1.1.1. CAD Support

The following CAD and auxiliary programs are supported on the indicated products and platforms (where the CAD product is supported on the noted platforms). Products are: A = Mechanical APDL (ANSYS) W = ANSYS Workbench I = ANSYS ICEM CFD standalone (some CAD systems may require the integrated ANSYS Workbench Reader)
Table 1.3 CAD Support by Platform

Product XP 64bit A, W, I A, W, I W A Vista 64-bit A, W, I A, W, I W A Windows 7 64-bit A, W, I A, W, I W [6] A XP 32bit A, W, I A, W, I W A Vista 32bit A, W, I A, W, I W A Windows 7 32-bit A, W, I A, W, I W [6] A
CATIA 4.x CATIA V5 R20 CADNexus/CAPRI CAE Gateway for CATIA V5 R19, 20, 21 Parasolid 22.1 4
System Prerequisites Product XP 64bit A, W, I A, W, I A, W, I A, W, I A, W, I A, W, I A, W, I W W, I W, I W, I W, I W, I W, I W, I W, I W W W I I I I I I W W I I I A, W, I A, W, I A, W, I W W, I W, I W, I W, I W, I W, I W, I W, I Vista 64-bit A, W, I A, W, I A, W Windows 7 64-bit A, W, I A, W, I A, W, I A, W, I A, W, I W, I A, W, I W W, I W, I [5] W, I W, I W, I W, I W, I W, I XP 32bit A, W, I A, W, I A, W, I A, W, I A, W, I A, W, I A, W, I W W, I W, I W, I W, I W, I W, I W, I W, I W W W I I I I I I W W I I I A, W, I A, W, I A, W, I W W, I W, I W, I W, I W, I W, I W, I W, I Vista 32bit A, W, I A, W, I A, W Windows 7 32-bit A, W, I A, W, I A, W, I A, W, I A, W, I W, I A, W, I W W, I W, I [5] W, I W, I W, I W, I W, I W, I
Parasolid 24 Pro/ENGINEER Wildfire 4 [2] Pro/ENGINEER Wildfire 5 [3, 7] Creo Parametric 1 [3] ACIS 21 [1] NX 6.0 NX 7.5 NX 8.0 SolidWorks 2010 [4], 2011 Solid Edge ST3, ST4 Autodesk Inventor 2011, 2012 AutoCAD 2011, 2012 IGES 4.0, 5.2, 5.3 JTOpen 8.0, 8.1 STEP AP203, AP214 Creo Elements/Direct Modeling 17.0, 18.0 Teamcenter Engineering 8.0 with NX 6.0 Teamcenter Unified 8.1 with NX 7.5 Teamcenter Unified 8.3 with NX 7.5.2 DWG GEMS IDI MS8/9 1. 2. 3. 4. 5. 6. 7.
For ICEM CFD standalone, ACIS 18.0.1 is the supported version for all platforms. Requires Pro/ENGINEER Wildfire 4 Build Date M120 or higher for Windows 7. Requires Pro/ENGINEER 5 Build Date M020 or higher for Windows 7. Requires SolidWorks 2010 SP1 for Windows 7. On Windows 7, ANSYS Workbench and ICEM CFD run only on Solid Edge ST4. Requires CATIA V5R19 SP6 or higher for Windows 7. Pro/ENGINEER Wildfire 5 is also named Creo Elements/Pro 5.0
1.2. Disk Space and Memory Requirements

You will need the disk space shown here for each product for installation and proper functioning. The numbers listed here are the maximum amount of disk space you will need for each ANSYS, Inc. product. Depending on the options selected for each product, you may require less. Product Mechanical APDL (ANSYS) ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFX ANSYS TurboGrid ANSYS FLUENT POLYFLOW ANSYS AQWA ANSYS ICEM CFD ANSYS Icepak ANSYS TGrid CFD Post only ANSYS Geometry Interfaces CATIA v5 ANSYS Remote Solve Manager Standalone Services 6.1 GB 4.7 GB 4.8 GB 5.2 GB 4.5 GB 5.5 GB 5.5 MB 4.3 GB 5.4 GB 5.7 GB 3.0 GB 4.5 GB 1 GB 625 MB 4.1 GB Disk Space
Product installations also require an additional 500 MB of free disk space during an installation. Memory Requirements product installations. We recommend that you have at least 2 GB of memory available for running
1.2.1. Setting the /3GB Switch on Windows 32-bit

On Windows 32-bit systems, you can allocate additional memory to an application (such as Mechanical APDL) via the /3GB switch. Normally, Windows allocates 2 GB of memory for the Windows kernel and 2 GB for the application. When /3GB is enabled, the OS reduces the potential memory allocated to the kernel and makes 3 GB of memory available to the ANSYS, Inc. product. Be aware that when using the /3GB switch with Mechanical APDL, you will not be able to specify a -m setting any higher than was possible without this switch. However, with this switch enabled, Mechanical APDL can dynamically allocate more memory; dynamic memory allocation is the recommended memory allocation method. Windows XP To enable this memory allocation on Windows XP systems, add the /3GB parameter to the startup line of the boot.ini file and reboot the system. The boot.ini file may be hidden. To view hidden files, go to Windows Explorer or My Computer and select Tools>Folder Options>View. Under Hidden files and folders, check Show hidden files and folders. Windows 7 and Vista To enable this memory allocation on Windows 7 and Vista systems, open a command prompt window and type the following command:
bcdedit /set IncreaseUserVA 3072
GPU Requirements Then reboot. Windows 64-bit Windows 64-bit systems already have the capability to address greater amounts of memory, so the /3GB switch is not applicable to those systems.
1.3. Software Prerequisites

You must have the following software installed on your system. Administrator privileges are required to install these files. These software prerequisites will be installed automatically when you launch the product installation. If you've completed an installation successfully, the executables are also located under the \v140\prereq directory should you need to manually install them at a later date. Prior to installing, you can find them in the root /prereq directory of the media/download package. Microsoft .NET Framework 3.5 SP1, with Update KB959209. Version 3.5 includes versions 2.0 and 3.0, and the following patches: XP (32-bit) NDP20SP2-KB958481x86.exe NDP30SP2-KB958483x86.exe NDP35SP1-KB958484x86.exe XP (64-bit) NDP20SP2-KB958481x64.exe NDP30SP2-KB958483x64.exe NDP35SP1-KB958484x64.exe Vista (32-bit) --NDP35SP1-KB958484x86.exe Vista (64-bit) --NDP35SP1-KB958484x64.exe
.NET Framework 3.5 SP1 is native on Windows 7 and does not require any additional patches. Microsoft Visual C++ 2005 SP1 Redistributable, 2.0.50727.762 Microsoft Visual C++ 2008 SP1 ATL Redistributable Package
1.4. GPU Requirements

Your system must meet the following requirements to use the GPU capability in Mechanical APDL: The machine(s) being used for the simulation must contain at least one nVIDIA Tesla series GPU card (a Tesla 20-series card is recommended for optimal performance) or one Quadro 6000 card. If both a Tesla and Quadro card are detected, Mechanical APDL will choose the Tesla card. On Windows, the driver version for the nVIDIA Tesla series GPU card must be 270.90 or newer. For optimal performance on Windows, the TCC (Tesla Compute Cluster) driver mode is recommended when using Tesla series GPU cards. Some limitations exist when using this driver mode (e.g., no support for Windows XP). Check your GPU card documentation for more details on how to set this driver mode and the existing limitations. You must be running on a Windows 64-bit operating system.
Note
On Windows, the use of Remote Desktop may disable the use of a GPU, which means the GPU Accelerator Capability cannot function under Remote Desktop. Using the TCC driver mode, if applicable, can circumvent this restriction. Alternative means of remotely logging into a machine can also be used (e.g., third-party software such as VNC or other).
1.5. Additional Hardware and Software Requirements

Pentium-class or Intel 64 / AMD64 system with the correct operating system version installed 1GB of RAM. On some 32-bit systems, you can use the /3GB switch to allocate additional RAM to the application and less to the Windows kernel. See Setting the /3GB Switch on Windows 32-bit (p. 6) for more information. For 32-bit systems, 4 GB free on the hard drive; up to 4.5 GB with CATIA V5. For 64-bit systems, 8 GB is recommended. DVD drive Certified graphics card with the latest drivers, compatible with the supported operating systems, capable of supporting 1024x768 High Color (32-bit), and a 17-inch monitor compatible with this type of graphics card. We recommend using certified graphics card from the Nvidia Quadro FX or ATI FireGL line. ANSYS CFX products and ANSYS TurboGrid require at least 24-bit color and that antialiasing on your graphics card be disabled.
Note
How you determine whether antialiasing is enabled varies according to the graphics card you have. To determine the status of an NVIDIA card on Windows, right-click on your desktop and select NVIDIA Display > monitor type. In the dialog box that appears, disable Application-controlled and slide the Antialiasing settings slider to Off. Click OK to save the changes. If this process does not work on your machine, please contact your system administrator or refer to your system documentation for detailed instructions on changing antialiasing settings.
Note
Some combinations of graphics card type, operating system, and MPEG resolution fail to play MPEGs properly. You may be able to get normal playback results simply by changing the MPEG settings. Alternatively, you can upgrade your graphics card. For laptop systems, ANSYS Workbench requires the latest graphics drivers. Microsoft Mouse or a mouse compatible with the supported operating systems; ANSYS CFX-Pre and ANSYS CFD-Post require a three-button mouse. If you use a spaceball, ensure that you have the latest version of the drivers installed. Approximately twice as much swap space as memory. The amount of memory swap space on the system may limit the size of the ANSYS model that can be created and/or solved. TCP/IP for the license manager (see the ANSYS, Inc. Licensing Guide for more information on TCP/IP). Although TCP/IP is included as part of the operating system, it may not be installed by default. When TCP/IP is installed, 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 the Remote Access Service. Also, the Autodial option of the Internet Options must be disabled so that the machine does not attempt to connect to the Internet every time ANSYS is run. See the ANSYS, Inc. Licensing Guide for more information. 8
Third-Party Software and other Security Considerations Microsoft Internet Explorer (IE) 7, 8, or 9 is recommended for proper operation of ANSYS Workbench. Once the correct version of IE is installed, it does not have to be your default Internet browser. After installation, simply run your preferred browser and reestablish it as the default. If you are running Internet Explorer 8 on Windows XP 32-bit, you must use XP SP3.
1.5.1. SpaceBall Support

DesignModeler, Mechanical, Design Exploration, FE Modeler, and ANSYS ICEM CFD all support the 3Dconnexion SpaceBall for manipulating the model (turning, zooming, panning, etc.). While the SpaceBall does provide significantly enhanced 3D control over viewing the model, it does not function as a mouse replacement and selection operations still require a mouse. To use a SpaceBall with the listed products, you must download and install the appropriate Microsoft Windows driver for your version of Windows. These are kept in the download area of the http://www.3dconnexion.com web site. At the time of publication of this document, the exact link was http://www.3dconnexion.com/downlink.asp and the file name for 32-bit versions of Windows was 3DxSoftware_v1-1-0_win32.exe; however, this is subject to change by 3Dconnexion.
1.5.1.1. SpaceBall Support for FLUENT Components

FLUENT products do not support SpaceBall.
1.5.2. Using Exceed

If you run Hummingbird, Communications Ltd.'s ExceedTM product, we recommend that you adjust the Window Manager settings in order for the ANSYS Workbench GUI and the online help system to work properly. This setting affects the behavior of Windows, not just applications that are running through Exceed, and may vary depending on the version of Exceed you are running. Note that changing this setting may affect other applications that you run through Exceed; please check with your system administrator before making any changes. FLUENT or Fluent legacy products do not support running from an Windows machine to a Linux or UNIX machine using Exceed or any remote software. To ensure that the ANSYS Workbench GUI works properly, follow these steps: 1. 2. 3. 4. 5. Right-click on the Exceed icon in the Windows Task Bar. Select Tools> Configuration... menu item. Click on the Display and Video category. Click on the Common Settings tab. Set Native Window Manager Focus Policy to Click.
1.6. Third-Party Software and other Security Considerations

The following third-party products are used as part of the installation process. In order for the installation to work properly, you must allow access to these products. Product Name Tcl Tk Executable Name tclsh.exe wish.exe
Chapter 1: Installation Prerequisites for Windows Product Name Perl 7zip Microsoft .NET Framework Executable Name perl.exe 7z.exe .net
10

Windows 7, Windows Vista
Generally speaking, you need full administrative privileges to install any software on Microsoft Windows 7 and Vista. Non-administrative accounts do not usually have the permissions required to access system areas that installation programs often need to modify. Full administrative privileges means that you are running as administrator with UAC turned off, or you are running as administrator with UAC turned on and Run as Administrator selected. Windows 7 and Vista use a feature called User Account Control (UAC) to control privileges and automatically reduce the potential of security breaches in the operation system. However, UAC limits your accessibility to system areas and can cause unpredictable behavior in ANSYS, Inc. products, as noted below. Full administrative options with Windows 7 and Vista include: Recommended Options: UAC turned off and install as full administrator (preferred method) UAC turned on and install with full administrative privileges (using Run as Administrator from the context menu)
Note
If you are running with UAC on, even if you have administrative privileges, you will have limited account control unless you specifically choose Run as Administrator. Other Options: UAC turned off and install as non-administrative user UAC turned on and not install with full administrative privileges (you did not select Run as Administrator from the context menu) UAC turned on and install as non-administrative user
When installing ANSYS, Inc. products, we strongly recommend that you use one of the two recommended options above. If UAC is enabled, we recommend that you turn UAC off before installing ANSYS, Inc. products, and then turn it back on when finished installing. You must be an administrative user in order to disable UAC. Follow the instructions for your operating system for disabling UAC. Once you have installed your applications, you can enable UAC again. If you have upgraded to Vista from Windows XP, the TEMP environment variable may point to an inaccessible location. For example, it may point to %USERPROFILE%\Local Settings\Temp. As a result, the product installation could end without configuring the product correctly. You should ensure
11
Chapter 2: Platform Details that the TEMP user variable points to a valid location, such as %USERPROFILE%\AppData\Local\Temp.
Installing with UAC On

If you cannot disable UAC and need to install with UAC on, you must run all applications, including the installation setup, as an administrator. Otherwise, the files may be written to AppData\Local\VirtualStore\<path> (or similar) rather than directly to <path>, if <path> is a protected directory (such as C:\Program Files). As a result, some applications and utilities may behave unpredictably. If you cannot disable UAC, you should: Always run ANSLIC_ADMIN, the File Association utility, and the CAD Configuration Manager by selecting the utility or application from the Start menu and right-mouse clicking and selecting Run as Administrator. Set your Start menu shortcuts to always run as administrator with the following procedure (or similar): 1. 2. 3. 4. Right-click the shortcut you wish to modify and select Properties. Click Advanced on the Shortcut tab. Select Run as administrator and click OK. Click OK.
Refer to your operating system documentation or visit www.microsoft.com for more instructions on setting Run as Administrator at various levels within the operating system.
Notes about UAC

When installing ANSYS, Inc. products, including the license manager, on Windows 7 or Vista machines, you need to be aware of several factors involving User Access Control (UAC): You should install the ANSYS, Inc. License Manager using the same permissions as you used to install the product. If you install both the product and the license manager with full administrative privileges, the product and licensing installation and configuration will proceed as normal. If you install the product as a non-administrative user with UAC turned off, you will see some expected restrictions (i.e., you will not be able to install prerequisites, you may need to run some additional postinstallation product configuration steps, etc.). Likewise, if you run as a non-administrative user with UAC turned off, you will also see expected restrictions (i.e., you will not be able to start and stop the license manager.) If you install as an administrative user with UAC turned on, you may encounter unpredictable behavior with both the product and license manager installations and subsequent behavior. As an administrator, you should choose to install and run applications with full administrative privileges to avoid any unpredictable situations. We strongly recommend against running with UAC on and not selecting Run as Administrator. These situations are described below. 1. If you have UAC turned on and you do not install (and run) with full administrative privileges, be aware that files may be written to and read from the %localappdata%\VirtualStore\ location (in the case of licensing, to %localappdata%\VirtualStore\Program Files\Ansys Inc\Shared Files\Licensing) instead of to the <os drive>.
12
In this situation, ANSLIC_ADMIN settings, such as Specify the License Server Machine, will indicate that files are being written to and read from <os drive>\Program Files\Ansys Inc\Shared Files\Licensing. Log files may behave in the same way. However, when you view the ansyslmd.ini file located in <os drive>\Program Files\Ansys Inc\Shared Files\Licensing, you will not see the ANSLIC_ADMIN settings you specified. 2. 3. To ensure that files are correctly written to and read from <os drive>\Program Files\Ansys Inc\Shared Files\Licensing, you should always run with full administrative privileges. If you are not running with full administrative privileges, you will not be able to use those ANSLIC_ADMIN options that require administrative privileges, such as starting and stopping the license manager.
Compiler Requirements for Windows Systems

All ANSYS, Inc. products are built and tested using the Visual Studio 2008 SP1 (including the MS C++ compiler) and Intel FORTRAN 11.1 compilers. Compilers are required only if you will be using User Programmable Features or other customization options.
13
14

3.1. Downloading the Installation Files
We strongly recommend that you review the Read Download Instructions and Product Information file included on the download site for the most current download instructions. We also recommend that you review the What Should I Download? file to understand which package(s) you need to download, depending on which product(s) you purchased and wish to run. To download the installation files from our website, you will need to be a TECS customer. Depending on the product/platform combination(s) you choose, you may need to download multiple files. 1. 2. 3. 4. From the Customer Portal, click on Download Software. The ANSYS Download Center Wizard page displays an overview of the download process. Review the overview and click Next. For the Download Type, choose Current Release and Updates. Click Next Step. Choose the hardware platform for which you want to download installation packages. You can select only one platform at a time. You will need to repeat the download procedure for each platform that you want to download. Click Next Step. Choose the products you wish to download. Products are listed by product names that correspond to the licensing product names. You can choose to list products grouped by product group or alphabetically. All products that you currently have licensed are highlighted and pre-selected for your convenience. After you have selected all products that you wish to download, click Next Step. The license manager, product, and documentation packages that you've selected to download are listed. Click on each link provided to begin the downloads. After the downloads have completed, uncompress each package using standard uncompression utilities for your specific platform. We strongly recommend that you extract the files into a new, temporary directory. Begin the product installation as described in Installing the Software (p. 17).
5.
6. 7.
8.
3.2. Installing from a DVD

To install ANSYS, Inc. products from the installation media, place the DVD in your DVD drive. If autorun is enabled, the installation will begin automatically. If autorun is disabled, choose Start>Run and type D:\setup.exe (replace D with the letter of your DVD drive) and continue with the steps in Installing ANSYS, Inc. Products (p. 17). If you are installing from media, you will be prompted to change DVDs during the installation. Please make sure you have all installation DVDs before beginning the installation.
15
16
Chapter 4: Installing the Software

4.1. Installing ANSYS, Inc. Products
This section explains how to install ANSYS, Inc. products. Although administrative privileges are not required for installation, we recommend that you use a login with administrative privileges. On Windows 7 and Vista systems, we prefer that you run as an administrator with UAC turned off. If you run as a non-administrative user on Windows 7 or Vista systems, you must have UAC turned off. See Platform Details (p. 11) for details on UAC. Some product components, including CAD programs, require administrative permissions to register. If you install with non-administrative privileges, you must follow the post-installation procedures as an administrator for your product to ensure that all components are successfully registered.
4.1.1. Product Installation

To install ANSYS, Inc. products, including client licensing, follow the steps below. You must also install the ANSYS, Inc. License Manager on at least one server machine in order to run ANSYS, Inc. products. See License Manager Installation (p. 21) for license manager installation instructions. 1. 2. 3. Save all data and close all Windows applications before continuing. To install, double-click the setup.exe file. The installation launcher appears. Choose a language. You will also see the following options: 4. Install ANSYS, Inc. Products Install ANSYS, Inc. EKM Server Install MPI for ANSYS, Inc. Parallel Processing Install ANSYS, Inc. License Manager Exit
If you want to install the EKM server, choose Install ANSYS, Inc. EKM Server to launch the EKM server setup. Upon completion of the setup, the ANSYS 14.0> EKM>Server Upgrade and Server Diagnostics menu items will appear under the Start menu. You must install the EKM client, ANSYS Workbench, and any other desired components before installing the EKM Server. The EKM Server installation may not be available with all packages. If you will be running FLUENT Parallel, CFX Distributed Parallel, or Distributed ANSYS and need to install Platform MPI or Intel MPI, choose Install MPI for ANSYS, Inc. Parallel Processing. On the following screen, choose to install Intel MPI or Platform MPI. The appropriate installation program will start. An installation README file will open simultaneously. Follow the instructions in the README file as you complete the installation. After the MPI installation has completed (if selected), choose Install ANSYS, Inc. Products from the installation launcher. During the installation process, the installation program will check your system to determine if you have the necessary prerequisites and will install any necessary prerequisites. You will need administrative privileges during the installation to install prerequisites. If you want to install
5.
6.
17
Chapter 4: Installing the Software as a non-administrative user but require prerequisites, you can install the prerequisites separately by running InstallPreReqs.exe from the top level directory as an administrator. Then you can log back in as a non-administrative user to continue with the installation. 7. 8. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. products. You can choose as many platforms as you wish. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. When you run a platform installation (i.e., install another platform's version onto the current system), ANSYS installs all necessary files. You can then mount to that installation from the appropriate platform. However, you may still need to run platform-specific configuration procedures (such as using the CAD Configuration Manager) from that platform before running an ANSYS, Inc. product. See Network Installation and Product Configuration (p. 22) for more information. Click Next to continue. 9. Specify the installation directory. You can accept the default or specify an alternate path and the directory name where the products are to be installed. When you choose an install directory via the Browse feature, the installation will automatically append \ANSYS Inc\ to the chosen directory. The installation path can have a maximum of 100 characters, except on AUTODYN, which has a maximum of 40 characters. You must install all ANSYS, Inc. products into the same location. Installing products into different locations can cause product components to fail. If you have already installed the ANSYS Workbench Framework for Ansoft, you must install any additional ANSYS, Inc. products into the same directory. You can also choose to have file extensions associated with the appropriate ANSYS program. Associating file extensions allows you to open the files with the appropriate program by doubleclicking the file in Windows Explorer. Otherwise, the files must be opened through the program with which they are associated. File association occurs only for those products that you install. If a product is not installed, the file association for that product's filename extension(s) will not be created. If you choose not to associate file extensions during the installation, you can do so later by running the File Association utility (Start> Programs> ANSYS 14.0> Utilities> File Association 14.0). Administrative privileges are required for file association; this option will not be available if you do not have administrative privileges. Choose Disable RSS to disable automatic internet feeds to ANSYS, Inc. products. Click Next to continue. 10. Select the components you want to install. You can select as many components as you wish to install. The amount of disk space required for the selected components and the disk space available appears at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. If you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully. Note that an additional 500 MB of free disk space must be available during the installation process. The components listed represent all available components for the platforms you selected earlier. Not all components are available on all platforms or with all products.
18
Installing ANSYS, Inc. Products ICEM CFD: The CATIA v5 interface and the native ANSYS Workbench formats, such as .mechdat or .meshdat are only supported with the ANSYS Workbench interface. (Legacy formats such as .agdb, .dsdb and .cmdb are also supported.) To have access to those formats from within the ICEM CFD interface, you must install a product that includes ANSYS Workbench along with ICEM CFD. Click Next to continue. 11. Specify the CAD configurations:
Creo Parametric
1. If you selected Creo Parametric, you will have to choose which Creo Parametric product to configure. You can choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD product be installed), or skip and configure later (using the CAD Configuration Manager). If you choose the Workbench Associative Interface, you may need to specify the Creo Parametric language, the Creo Parametric command, and the full Creo Parametric installation path (C:\Program Files\PTC\Creo 1.0\Parametric by default) for an existing Creo Parametric installation. Click Next.
2.
NX
1. If you selected NX, you will have to choose which NX product to configure. You can choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD product be installed), or skip and configure later (using the CAD Configuration Manager). If you choose the Workbench Associative Interface and the UGII environment variables were not set, you may need to specify the NX installation path for an existing NX installation. If you are an administrative user, a file required to load the NX plug-in is placed in the administrative user's Application Data folder by default, which may not be accessible by other, non-administrative users. To allow non-administrative users to run, you will need to define the environment variable UGII_CUSTOM_DIRECTORY_FILE prior to installation and specify a location where other users have read access. Alternatively, you can run the CAD Configuration Manager after the installation and provide an updated location for the NX Custom Directory File Path under the NX tab. If you selected the ANSYS ICEM CFD NX Interface product but not the NX Geometry Interface product on the product selection screen, you may need to specify the NX installation path or choose to skip configuring NX and use the CAD Configuration Manager to configure later.
2.
3.
CATIA v5
If you selected CATIA v5 and any product that includes ANSYS Workbench, you will be required to select the appropriate CAD plugin for ANSYS Workbench. You can choose to configure Spatial, Capri, or skip and configure later (using the CAD Configuration Manager).
SolidWorks and Autodesk Inventor

If you selected Inventor and/or SolidWorks as one of your CAD products, you will have to choose which Inventor and/or SolidWorks product to configure. You can choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).
If you have not yet installed these programs, or do not know the requested information, you can choose to skip these configuration steps. If you skip these steps, you will need to manually configure these CAD interfaces using the CAD Configuration Manager before you can successfully
19
Chapter 4: Installing the Software import models into Mechanical APDL (ANSYS), ANSYS Workbench, or ICEM CFD. You can access the CAD Configuration Manager via Start> Programs > ANSYS 14.0 > Utilities > CAD Configuration Manager 14.0. See Configuring CAD Products (p. 39) for more information on using the CAD Configuration Manager. When all CAD configuration information has been specified or skipped, click Next. 12. A licensing file date verification summary appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next. 13. A summary of the selected installation data appears. Information shown includes platform, installation directory, and products. Review the information carefully, and if correct, click Next to continue the installation. The installation program will first check your system to determine if you have the necessary prerequisites. Installing prerequisites requires administrator privileges; if you do not have administrative privileges, you will not be able to continue. You will be asked to log out as a non-administrative user and log in as an administrative user to install the prerequisites. If you want to install as a non-administrative user but require prerequisites, you can install the prerequisites by running InstallPreReqs.exe from the top level directory as an administrator. Then you can log back in as a non-administrative user to continue with the installation. If the prerequisites are not already on your system, and you have administrative privileges, the prerequisites will be installed automatically. In this case, you will see messages in the installation window indicating that prerequisites are being installed. You may be asked to run the necessary files (such as the .NET exe), or to reboot your machine, depending on your existing machine configuration. If you are asked, you will need to reboot in order to complete the prerequisite installation successfully. The selected products and components are then installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation and install the licensing client. 14. The Licensing Client Installation Configuration box appears. As the licensing client is installed, progress messages appear in the box. 15. If you do not have an existing ansyslmd.ini file, the Specify License Server Machine - Add Server Specification box appears. Enter the hostname of your license server machine and click Next. If you already have an existing ansyslmd.ini file, you will not see this box and you will proceed directly to the next step. 16. When the client installation is complete, click Exit. 17. On the product installation window, click Next. You will be asked to participate in an Install Survey. To take the survey, enter the path to a valid browser for your system, and click Next. You can also click Finish now to skip the survey or when you have completed the survey. 18. Click Exit on the installation launcher, or choose Install ANSYS, Inc. license manager to go on to the License Manager Installation. You do not have to take any further steps to run as a client; however, each site must install the License Manager on at least one machine that will act as a license server. If you installed as a non-administrative user, you will need to run additional post-installation steps as an administrative user to finish configuring CFD Viewer, BladeGen, and most CAD products. See PostInstallation Instructions (p. 31) for specific procedures for each product.
20
4.1.2. License Manager Installation

Follow the instructions below to install the ANSYS License Manager on Windows systems that will act as license servers. You must be an administrative user to install the ANSYS License Manager on Windows. Client licensing is installed automatically when the product is installed; once you have installed the ANSYS License Manager, you do not have to take any further steps to run as a client if you have installed a product.
Note
You do not have to install the prerequisites to install the ANSYS License Manager. 1. 2. 3. To install, double-click the setup.exe file. The installation launcher appears. Choose a language. Choose to Install ANSYS, Inc. License Manager from the installation launcher. You must be an administrative user to install the license manager; this option will not be available if you are not an administrative user. You will be warned that if the License Manager is currently running, it will be shut down if you continue with the installation. Click OK. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree to accept the terms and click Next. You must select I Agree to continue with the installation. If you are installing more than one platform or if you are installing a platform other than your current machine type, you will need to select the platform(s) on which you want to install the ANSYS, Inc. License Manager. The platform on which you launched the installation will be selected by default and is shown at the bottom of the window. Click Next to continue. The installation directory is shown; however, you cannot change the default or specify an alternate path or directory name where the license manager is to be installed. Click Next to continue. 8. Select the component you want to install. You can choose to install the ANSYS, Inc. License Manager. The amount of disk space required and the disk space available appear at the bottom of the window. If the disk space required exceeds the disk space available, be sure that you have sufficient space before continuing. The disk space required as calculated by the installation program may be greater than the actual amount needed. If you choose to continue the installation, you should carefully review any log and error files at the end of the installation to ensure that the installation completed successfully. Click Next to continue. 9. A licensing file date verification summary appears. If the date verification finds a conflict, a message box appears with details of the conflict and steps for resolution. If no conflicts are found, click Next.
4. 5. 6.
7.
10. A summary of the selected installation data appears. Information shown includes platform, installation directory, and product. Review the information carefully, and if correct, click Next to continue the installation. The ANSYS License Manager is now being installed and configured on your system. The installation window displays the individual actions as they occur. When the installation is complete, the window displays any installation errors or warnings. Review this information carefully. Click Next to continue the installation and install the license manager.
21
Chapter 4: Installing the Software 11. The Licensing Server Installation Configuration box appears. As the license manager is installed, progress messages appear in the box. 12. The License Wizard will be launched. This wizard walks you through the process of installing or updating a license file, specifying the license server(s) (which updates the ansyslmd.ini file), and starting the license manager. The wizard will prompt you for the necessary information at each step. During this process, the license manager will be shut down if it is running. Be aware that this can impact any users currently running using the license manager. Click Continue on the License Wizard to begin, and follow the instructions on the screen. If you choose either of the non-default server configurations, please see Advanced Licensing Configuration Options in the ANSYS, Inc. Licensing Guide for detailed installation instructions. 13. When the License Wizard is complete, click Exit on the wizard screen and then click Exit again on the Licensing Installation Configuration Log screen. 14. When the license manager installation is complete, click Finish. A new Start Menu item named ANSYS, Inc. License Manager will be created automatically. It will include selections for the Server ANSLIC_ADMIN utility, the ANSYS, Inc. Licensing Guide, and the FLEXnet Licensing End User Guide.
Note
Client machines will also include a Client ANSLIC_ADMIN option under Start> All Programs> ANSYS 14.0> ANSYS Client Licensing. The client-only version of ANSLIC_ADMIN offers access to a limited number of ANSLIC_ADMIN features, such as status/reporting options.
4.1.2.1. Registering the License Server

Follow this procedure to register your license server information if you are a new user or if you add or change a license server machine. See the ANSYS, Inc. Licensing Guide for more information on selecting license servers and on using the ANSLIC_ADMIN utility. 1. 2. Use the ANSLIC_ADMIN utility to register license server information on each license server. Return the resulting file to your ANSYS sales representative. ANSYS, Inc. or your sales representative will then supply you with your license keys. This file is located in Program Files\Ansys Inc\Shared Files\Licensing\licserver.info by default. Use the Run the License Wizard option of the ANSLIC_ADMIN utility to enter your license key and start the license manager.
3.
4.1.3. Network Installation and Product Configuration

The procedure for a network, file server, or platform installation follows. Running AUTODYN from a file server is not recommended. To complete a network installation (where the product is installed on one machine and multiple clients access that installation to run the product) to a file server machine, follow the steps below. A network installation must be homogeneous, although you can install on different operating systems and architectures within the same platform. For example, you can install both Windows 32- and 64-bit platforms on a single Windows file server, and clients of those Windows platform types will access the product installation on that single Windows file server.
22
Installing ANSYS, Inc. Products For a platform installation (installing multiple platforms), you will need to map a drive to the shared install location. UNC paths will not work correctly for a platform installation. 1. Install the product(s) to be shared in a location that all clients can access. Install all platforms that this machine will host. You must share the entire \Ansys Inc directory, not just the \v140 directory. If mapping a drive to the shared location, it must be mapped to the \Ansys Inc folder. 2. Open the Product Configuration Manager (\\fileservermachine\Ansys Inc\v140\commonfiles\tools\<platform>\ProductConfig.exe). Select Install Required Prerequisites. You must be logged in as an administrative user to install the prerequisites. This step must be completed on all client Windows systems. On each Windows client, update the .NET security settings. By default, the .NET 3.5 Framework prevents applications from being run over a network. In order to install over a network, each Windows client that accesses the shared directory requires a modification to its security settings. This modification allows the .NET binaries that are located under the \Ansys Inc directory on the shared machine to be run from the network. To make this modification from the Product Configuration Manager, select Add .NET security exception for ANSYS, Inc. products. You must have administrative privileges to modify the security policy. To understand the implications of this security exception for .NET, please contact your system administrator or see Microsofts website http://msdn.microsoft.com/en-us/library/7c9c2y1w(v=vs.80).aspx. Alternatively, you can allow network execution by running the Microsoft Caspol utility from the command line. The Caspol utility is located under the .NET Framework installation, in C:\Windows\Microsoft.NET\Framework\v2.0.50727 for a 32-bit machine. The security exception executed by the Product Configuration Manager runs the following command, which opens full trust to files on the shared drive:
<os drive>\Windows\Microsoft.NET\Framework\v2.0.50727\Caspol.exe -m -ag <CodeGroup> -url file://x:/* FullTrust
3.
where x is the mapped drive or UNC path where the product is installed, and CodeGroup is the appropriate Caspol permissions level. We recommend a CodeGroup setting of 1.2. If that setting does not work or is not appropriate for your environment, please see the Caspol documentation available from Microsoft or contact your system administrator. On a 64-bit machine, use the following command:
<os drive>\Windows\Microsoft.NET\Framework64\v2.0.50727\Caspol.exe -m -ag <CodeGroup> -url file://x:/* FullTrust
To enter this command, choose Start> Run, and enter the above command in the Open: field. Replace CodeGroup and x: in the above command with the correct values and press Enter. You must install Caspol as an administrative user. If running this from the command line in Windows 7 or Vista, you must start the command prompt as Administrator, or the command will fail. 4. If you are sharing the Mechanical APDL (ANSYS) product, edit the tlbrlist140.ans file, located in \v140\ansys\gui\en-us\toolbars on the Windows file server. The file should read as follows:
\\fileservermachine\Ansys Inc\v140\ansys\gui\en-us\toolbars\ANSYSSTANDARD.TLB \\fileservermachine\Ansys Inc\v140\ansys\gui\en-us\toolbars\ANSYSABBR.TLB \\fileservermachine\Ansys Inc\v140\ansys\gui\en-us\toolbars\ANSYSGRAPHICAL.TLB
23
Chapter 4: Installing the Software 5. 6. 7. For all types of network installations, from each client Windows machine, navigate to the v140\commonfiles\tools\<platform> directory and run ProductConfig.exe. Select Configure Products. Select the products you want to configure. Click Configure.
Note
CFD-Post is automatically configured when CFX, FLUENT, POLYFLOW, or Icepak is configured, or if CFD-Post is selected. 8. An informational message box appears as each product is configured. All operations and error messages that are encountered while using the product configuration (or unconfiguration) option are written to the productConfig.txt file in the %TEMP% directory of the client machine. No log files are written to the machine that is hosting ProductConfig.exe. 9. If you are installing multiple platforms, you must go to one client of each platform type and run the Complete Unfinished Licensing Installation Configuration from the client ANSLIC_ADMIN utility's Tools menu. You can access the client ANSLIC_ADMIN via Start> Programs> ANSYS 14.0> ANSYS Client Licensing> Client ANSLIC_ADMIN Utility.
10. Select Configure CADs. 11. The CAD Configuration Manager opens. Run this utility for all of the CAD products you need to configure. See Using the CAD Configuration Manager for detailed instructions on running this utility, or select Help from the menu bar in the CAD Configuration Manager . 12. When the configuration is completed, you will see shortcuts to each product under Start> Programs> ANSYS 14.0. Unconfigure 1. 2. 3. To unconfigure products that have previously been shared, use the following procedure:
From each client machine, select Start> Programs> ANSYS 14.0> Utilities> Product Configuration 14.0. Select Unconfigure Products. Select the products you want to unconfigure. Click Unconfigure. When unconfiguring products, be aware that WB/Common should be unconfigured last, after all other products are unconfigured. If you are unconfiguring some but not all products, do NOT unconfigure WB/Common, or your remaining products will not run correctly. You will be notified if any currently-running processes will be closed. Click Yes to continue or No to exit the unconfigure. CFD-Post CFD-Post can be configured as a standalone product; however, as a standalone product, it is also automatically configured with FLUENT, POLYFLOW, and Icepak. To unconfigure CFD-Post, you must select all of these products to unconfigure, regardless if they are configured locally. If you choose to unconfigure standalone CFD-Post without unconfiguring the other products, you will not be able to proceed with the unconfigure. You will need to revise your selections before continuing.
24
Installing ANSYS, Inc. Products If you choose to unconfigure all of the other products that include CFD-Post but you do not select CFD-Post, then CFD-Post will not be unconfigured.
4.
An informational message box appears as each product is unconfigured. The shortcuts to each product under Start> Programs> ANSYS 14.0 are now removed.
4.1.4. Silent Mode Operations

ANSYS, Inc. supports silent mode operations, including installation, configuring/unconfiguring, and uninstalling. You can specify the following product flags. These flags are all valid for a silent install. However, because of the way the products are packaged, not all of these flags may be valid for a silent configuration/unconfiguration or uninstall. Not all products are available on all platforms. For silent mode operations, if you do not specify any product arguments, all available products will be installed, configured, or uninstalled.
Product Flags
Product Mechanical APDL (ANSYS) ANSYS Customization Files ANSYS AUTODYN ANSYS LS-DYNA ANSYS CFD-Post ANSYS CFX ANSYS TurboGrid ANSYS FLUENT ANSYS POLYFLOW ANSYS AQWA ANSYS ICEM CFD product_flag -mechapdl -ansyscust -autodyn -lsdyna -cfdpost -cfx -turbogrid -fluent -polyflow -aqwa -icemcfd
Note: Installing any of the above products will install ANSYS Workbench. ANSYS ICEM CFD Creo Parametric Interface ANSYS ICEM CFD Unigraphics NX Interface ANSYS Icepak Remote Solve Manager Standalone Services ANSYS TeamCenter Engineering Creo Parametric NX CATIA 4.x CATIA V5 Parasolid -icemproe -icemug -icepak -rsm -tceng -proe -ug -catia4 -catia5 -parasolid
25
Chapter 4: Installing the Software Product ACIS SolidWorks Solid Edge Autodesk Inventor Creo Elements/Direct Modeling JTOpen AutoCAD product_flag -acis -solidworks -solidedge -adinventor -cocreate -jtopen -acad
4.1.4.1. Silent Product and License Manager Installation

You can deploy an ANSYS, Inc. product installation in silent mode. The general form to run a silent product installation, including the client licensing, from the Start>Run menu is:
setup.exe -silent -product_flag
The above form will install the products specified (see the list of product_flags above). Additional command line arguments are available; please see the list below. For example, to install TurboGrid and Icepak to the default installation directory, issue the following command:
setup.exe silent install_dir C:\Program Files\ANSYS Inc -turbogrid -icepak
To install the ANSYS License Manager on Windows systems that will act as license servers, you must run the setupLM.exe:
setupLM.exe -silent
The silent license manager installation is valid only for the default Licensing Configuration option "Run the ANSYS Licensing Interconnect with FLEXlm." Please see the ANSYS, Inc. Licensing Guide for more information. You can use the following arguments when running a silent installation: -silent -install_dir "path" Initiates a silent installation. Specifies the directory to which the product is to be installed. For the installation directory, you must enclose the path in quotes if you have spaces in the pathname. If you want the product to install to the default location, you can omit the -install_dir argument.The default location is <os drive>:\Program Files\ANSYS Inc\. For the license manager installation, it will always be installed to <os drive>:\Program Files\ANSYS Inc\. Specifies one or more products to install. If you omit the -product_flag argument, all products will be installed. See the list of valid product_flags above. You can specify an options file that lists the products you want to install.To do so, you must provide a full path to a file containing desired products. See Specifying Products with an Options File for more details. Disables automatic internet feeds to ANSYS, Inc. products. Displays a list of valid arguments for a silent installation.
-product_flag -productfile "path" -disablerss -help
26
Installing ANSYS, Inc. Products -licfilepath "path" -setliclang language Specifies the location of the license file to install. If the path is not specified or if the path is the same as the existing license file, the license file will not be installed. Valid only when doing a silent license manager installation (setupLM.exe). Specifies a language to use for the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect log file. Use the language directory name in the language subdirectory of the licensing directory (en-us, fr, de, etc.) as the language value. This flag can be used during a GUI installation as well.Valid only when doing a license manager installation (setupLM.exe). Specifies information to be used by the client for the license server. Valid only in conjunction with a silent installation (setup.exe).The format is: Single license server: LI port number:FLEXlm port number:hostname Example: 2325:1055:abc Three license servers: LI port number:FLEXlm port number:hostname,hostname,hostname Example: 2325:1055:abc,def,xyz The default values for the Licensing Interconnect and FLEXlm port numbers (2325 and 1055, respectively) will be used if they are not specified. However, you do need to include the colons. In a three-server environment, you also need to enclose the values in quotes (Windows only). Example: ::abc or ::abc,def,xyz Information specified via -licserverinfo will be appended to existing information in the ansyslmd.ini file. To change information already in your ansyslmd.ini file, you must use the ANSLIC_ADMIN utility. The silent installation process will automatically close certain applications, possibly resulting in lost data. You should always close all programs before starting a silent install. A silent install will first install any necessary prerequisites that are not already on your system and then continue with the installation. You must have administrative privileges to install prerequisites; if not, the silent install will exit and write a message to the log file. Installation log files are located in the installation directory: install.log contains installation messages, and install_licconfig.log contains licensing installation messages. In rare circumstances with a silent licensing installation, the licensing installation messages may not be written to the install_licRelease 14.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
-licserverinfo
27
Chapter 4: Installing the Software config.log (for example, if the silent licensing installation aborts); in these cases, you may find error messages in the .ansys_install_temp_licconfig_<user>_<index>.log file, located in %TEMP%.
Caution
A silent license manager installation could shut down the ANSYS, Inc. License Manager, affecting other users who are using that license server machine. For more information on the silent license manager installation, see the ANSYS, Inc. Licensing Guide.
Specifying Products with an Options File

You can also specify an options file on the command line using the -productfile "path option. The options file can specify which products you want to install. The options file can contain all possible products, with the products you do not want to install commented out, or it can contain only the products you want to install. An example options file is shown below. In the example, Creo Parametric and NX are commented out using the acceptable comment indicators. When using the options file, do not include the dash (-) before the product name.
mechapdl ansyscust autodyn cfdpost cfx turbogrid fluent polyflow icemproe icemug icepak ::proe REM ug
To run with NX and Creo Parametric: NX: Verify that your UGII environment variables are set, and the configuration will pick them up automatically. Creo Parametric: Verify that the following environment variables are set: PROE_START_CMD140=C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat (or your Creo Parametric start command) PROELOADPOINT= C:\Program Files\<Creo_dir>
Silent Prerequisites Installation

The ANSYS, Inc. product installation requires several prerequisites. These prerequisites often require administrative permissions to install. If you want to install as a non-administrative user but require prerequisites, you can install the prerequisites separately by running InstallPreReqs.exe from the top level directory as an administrator. You can also install the prerequisites silently using the following command:
InstallPreReqs.exe -silent
28
4.1.4.2. Silent Product Configuration/Unconfiguration

You can also run the ProductConfig.exe via command line (i.e., silent mode) to configure or unconfigure products. From each client machine, run the ProductConfig.exe -silent with the following options: -config, -unconfig, -prereqs, -caspol, and -product_flag. These options are described below. -config/-unconfig -- Use with the -silent option to indicate that products should be configured/unconfigured. -prereqs -- Required to install the necessary prerequisites on your system. Prerequisites must be installed once on each machine. -caspol -- Required to modify the necessary .NET security settings to allow the product to run across the network. This option needs to be run once on each machine. -product_flag -- Use to specify which products should be configured; see the above list of product_flags. If you do not specify one or more products, all products that have been installed will be configured. Use the -help option for a list of commands available for use with ProductConfig.exe.
An example command for silent configuration is:

"\\machineabc\ANSYS Inc\v140\commonfiles\tools\winx64\ProductConfig.exe" -silent -prereqs -caspol -config
All operations and error messages that are encountered while using the silent product configuration/unconfiguration option are written to the productConfig.txt file in the %TEMP% directory of the client machine. No log files are written to the machine that is hosting ProductConfig.exe.
4.1.4.3. Silent Media Installation

To run a silent installation from the media, you can either: Copy the contents of each DVD to a folder on the machine's hard disk such that the 140-<number>.dvd files of each DVD are located in the same directory. You can then proceed with the silent installation as described earlier. Place all of the media in separate drives (any combination of virtual ISO mounts or hardware drives) so that they can be accessed simultaneously during the installation. Then run the silent installation as described earlier, but include the additional -media_path2 <path> option for each drive:
setup.exe -silent -product_flag -media_path2 <path>
The installer uses the mount directory from which it was launched as the first media path; you need to specify only the location of the subsequent DVD(s) using the -media_path2 option shown in the example above.
4.1.4.4. Silent Uninstall

To run a silent uninstall, run the following from some location other than the \v140 directory:
C:\> <installation path>\v140\Uninstall.exe -silent
The silent uninstall will unconfigure and remove all products and remove the entire \v140 directory, including any user files or subdirectories that you have added to the \v140 directory.
29
Chapter 4: Installing the Software Because of the way ANSYS, Inc. products are packaged, not all of the product_flags shown above are valid. To uninstall individual products, use the following product options in conjunction with the -silent argument: Mechanical APDL ANSYS AQWA ANSYS CFX ANSYS CFD-Post ANSYS FLUENT ANSYS POLYFLOW ANSYS ICEM CFD ANSYS TurboGrid ANSYS Icepak Remote Solve Manager Standalone Services -mechapdl -aqwa -cfx -cfdpost -fluent -polyflow -icemcfd -turbogrid -icepak -rsm
For example, to uninstall only TurboGrid and Icepak, issue the following command:
C:\> <installation path>\v140\Uninstall.exe -silent -turbogrid -icepak
You can also issue the -help option to see a list of valid arguments for a silent uninstall. Uninstalling CFD-Post CFD-Post can be installed as a standalone product. As a standalone product, it is also automatically installed with FLUENT, POLYFLOW, and Icepak. To uninstall the standalone version of CFD-Post, you must specify -cfdpost as well as all of the above products that you have installed. If you choose to uninstall CFD-Post without uninstalling the other products, the uninstall will stop and an error message will be written to the log file (uninstall.err). You will need to reissue your uninstall command with the correct product selections. Note that CFD-Post is also installed with CFX; however, you do not need to uninstall CFX to uninstall the standalone version of CFD-Post, and uninstalling the standalone version of CFD-Post will not remove the CFD-Post capability from CFX. Uninstalling a Non-Administrative Installation If an administrative user attempts to uninstall a nonadministrative user's installation, the uninstall will write a log file and terminate. The log file, uninstall.err, will be located in the \v140 directory. If you wish to proceed with the uninstall, issue the following command:
<installation path>\v140\Uninstall.exe -silent forceNonAdmin
30

5.1. Post-Installation Procedures for All Products
The following post-installation procedures apply to all ANSYS, Inc. products. Individual products may have additional post-installation procedures; please refer to the following sections for each product. 5.1.1. Post-Installation Procedures for Mechanical APDL (ANSYS) and ANSYS Workbench Products 5.1.2. Post-Installation Procedures for ANSYS CFX and ANSYS CFD-Post 5.1.3. Post-Installation Procedures for ANSYS AUTODYN 5.1.4. Post-Installation Procedures for ANSYS FLUENT 5.1.5. Post-Installation Procedures for ANSYS POLYFLOW 5.1.6. Post-Installation Procedures for Other Products After the product is installed, you need to establish some system settings, including pathnames and environment variables. See your operating system documentation for specific instructions on setting paths and environment variables. 1. Set the following environment variables based on the behavior you want. The ANSYSLIC_DIR environment variable sets the location of the ANSYS licensing directory hierarchy. The default value is c:\Program Files\ANSYS Inc\Shared Files\Licensing . You probably will not need to reset this variable, unless you change the location of the licensing files.
To set environment variables: Windows XP: Right click My Computer and choose Properties> Advanced> Environment Variables. Click New. Type the name in the Variable Name field and the desired setting in the Variable Value field. Click OK on all dialog boxes. Windows 7 / Vista: Right click Computer and choose Properties. Click Advanced System Settings, and click Environment Variables. Click New. Type the name in the Variable Name field and the desired setting in the Variable Value field. Click OK on all dialog boxes. If you have any command prompts or console windows open when you set or reset environment variables, those windows need to be closed and restarted in order to pick up the new settings. 2. Set the home directory. To set a home directory in Windows, you need to set a HOMEDRIVE environment variable to the desired drive letter (including the colon) and a HOMEPATH environment variable to the desired path. For example:
HOMEDRIVE=C: HOMEPATH=\Users\Mine
3. 4.
Set the license manager to start automatically at boot time. For platform-specific instructions, see License Manager Automatic Startup Instructions in the ANSYS, Inc. Licensing Guide. Designate server(s) for license checkout and establish necessary user privileges (recommended but not required). For information on these tasks, see Post-Installation Instructions for the License Manager in the ANSYS, Inc. Licensing Guide. Make a backup copy of the \ANSYS Inc directory.
5.
31
Chapter 5: Post-Installation Instructions 6. Verify the product installation by selecting each product from the Start menu to verify that they each start and run correctly. You must be pointing to a valid license server machine before you can verify the installation. If you chose not to set file associations during the installation, you may want to run the File Association utility now. Select Start> Programs> ANSYS 14.0> Utilities> File Association 14.0. Administrative privileges are required to run this utility. You can also run the File Association utility in silent mode:
<install_dir>\v140\commonfiles\tools\<platform>\fileassoc.exe -silent
7.
You can see help on the fileassoc.exe by issuing -help. File associations are as follows: ANSYS, Inc. Product Mechanical APDL (ANSYS) ANSYS CFD-Post ANSYS CFX ANSYS FLUENT ANSYS ICEM CFD ANSYS Workbench File Extension .db, .dbb, .grph .mres, .res .cfx, .cvf, .def, .mdef .cas .blk, .jrf, .prj, .rpl, .tin, .uns .ad,.agdb, .aqdb,.bgd,.cmdb,.dsdb,.engd,.fedb,.mechdat, .meshdat, .wbdb, .wbpj, .wbpz
Quality Assurance Program: If you require verification of Mechanical APDL, the Mechanical Application, FLUENT, or CFX, ANSYS, Inc. offers Quality Assurance programs. If you are interested in this service, go to http://www.ansys.com/About+ANSYS/Quality+Assurance/Quality+Services or call the ANSYS, Inc. Corporate Quality Group at (724) 746-3304.
5.1.1. Post-Installation Procedures for Mechanical APDL (ANSYS) and ANSYS Workbench Products
The following post-installation procedures apply only to the Mechanical APDL (ANSYS) and ANSYS Workbench products. These are in addition to the post-installation procedures noted above for all products. 1. If you installed as a non-administrative user, run the CAD Configuration Manager as administrator to configure the CAD products appropriately. See Configuring CAD Products (p. 39) for details on running the CAD Configuration Manager. If you do not have the shortcut to access the CAD Configuration Manager, you can find it at:
<install_dir>\v140\commonfiles\CAD\bin\<platform> \Ans.CadInt.CADConfigUtilityGUI.exe
2.
Set the following environment variables based on the behavior you want. Set the environment variables following the conventions of your operating system. Not all of these are required for all integrated ANSYS Workbench products (such as ANSYS AUTODYN), but setting them correctly for ANSYS Workbench will in no way hinder the performance of the other products. The ANSYS140_DIR environment variable sets the location of the ANSYS directory hierarchy. The default value is c:\Program Files\Ansys Inc\V140\ANSYS. You probably will not need to reset this variable, unless you change the location of the installed files. ANSYS140_PRODUCT - set this to the correct product variable to run Mechanical APDL to start with the correct Mechanical APDL product without specifying the -p command modifier each time.
32
Post-Installation Procedures for All Products ANS_CONSEC - set this to YES to disable Mechanical APDL dialog boxes and allow multiple jobs to run consecutively without waiting for user input. Settings for ANS_CONSEC are: Value of ANS_CONSEC Not defined/default YES NO Batch Dialog Box No No Yes GPF Dialog Box on Error Yes No Yes
ANSYS_LOCK - set to ON (default) to create file locks to prevent users from opening a new job with the same name and in the same directory as the current job. ANSYS140_MAT161 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_MSC material (requires an LS-DYNA MAT_161 license). ANSYS140_MAT162 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_DMG_MSG material (requires an LS-DYNA MAT_162 license). LSTC_LICENSE - This is an LS-DYNA environment variable that controls which license manager is used by the LS-DYNA executable. It is set to ANSYS during installation; changing this environment variable will prevent ANSYS LS-DYNA from using your ANSYS licenses when running the executable.
5.1.2. Post-Installation Procedures for ANSYS CFX and ANSYS CFD-Post

After installing the ANSYS CFX or ANSYS CFD-Post software, verify the installation as follows: 1. Select Start> Programs> ANSYS 14.0> Fluid Dynamics> CFX 14.0 The CFX 14.0 Launcher opens. 2. 3. 4. 5. In the Working Directory field of the Launcher, type the path to the examples directory, which by default is: C:\Program Files\ANSYS Inc\14.0\CFX\examples Click CFD-Post 14.0. CFD-Post opens. Select File > Load Results. The Load Results File window opens. Select StaticMixer_001.res and click Open. A wireframe of a mixer appears in the 3D Viewer. 6. Select Session > Play Session. The Play Session File window opens. Select StaticMixerPost.cse and click Open. The mixer changes orientation, displays a plane colored by temperature, hides the plane, then loads a vector plot of temperature located on the plane. 7. 8. Select File > Close and close the case without saving. To exit CFD-Post, select File > Quit.
If any of the installation verification steps fails, contact your ANSYS Support representative.
5.1.3. Post-Installation Procedures for ANSYS AUTODYN

Please refer to the ANSYS AUTODYN Quick Start Guide and What's New sections in the ANSYS AUTODYN help for information on starting and running ANSYS AUTODYN in either GUI or batch modes.
33
5.1.4. Post-Installation Procedures for ANSYS FLUENT

After installing the ANSYS FLUENT software, you will need to reset the default values in the ANSYS FLUENT launcher as follows: 1. 2. 3. 4. 5. Verify that the FLUENT_INC environment variable is not set. From the Control Panel, select System and click the Advanced tab. Click Environment Variables. Find and delete the FLUENT_INC variable. Select Start> Programs> ANSYS 14.0> Fluid Dynamics> FLUENT 14.0. Click Default. Click Yes when asked if you want to discard the LAUNCHER history. Click Cancel if you do not wish to start FLUENT at this time. The new defaults will have been saved.
Please refer to the ANSYS FLUENT Quick Start Guide for more information.
5.1.5. Post-Installation Procedures for ANSYS POLYFLOW

POLYFLOW no longer requires the FLUENT_INC environmental variable. It should be deleted as is recommended for FLUENT: From the Control Panel, select System and click the Advanced tab. Click Environment Variables. Find and delete the FLUENT_INC variable.
5.1.6. Post-Installation Procedures for Other Products

BladeGen If you are running BladeGen on Windows 7 and Vista, in order to access the BladeGen online help, you need to install WinHlp32.exe, which is available from Microsoft. During installation, BladeGen will not be configured. It can be configured separately after the overall installation is complete by running the following executable as administrator:
<install_dir>\v140\AISOL\BladeModeler\BladeGen\BladeGenConfigure.exe
BladeEditor In order to use BladeEditor, you must set the Geometry license preference to ANSYS BladeModeler as follows: 1. 2. 3. In the ANSYS Workbench menu, select Tools> License Preferences. In the License Preferences dialog box, click the Geometry tab. If ANSYS BladeModeler is not the first license listed, then select it and click Move up as required to move it to the top of the list. If ANSYS BladeModeler is not in the list, then you need to obtain an ANSYS BladeModeler license. Select ANSYS DesignModeler in the list and set its value to 0 (which means Don't Use). This step prevents DesignModeler from using an ANSYS DesignModeler license when an ANSYS BladeModeler license is not available. Click OK to close the dialog box.
4.
5.
FEMGV For ANSYS AQWA customers, FEMGV is also available as a separate, standalone installation, available via media or the ANSYS Customer Download Center.
34
Product Localization
5.2. Launching ANSYS, Inc. Products

To launch ANSYS, Inc. products on Windows platforms, choose the product from the ANSYS 14.0 program group under the Start menu (Start> Programs> ANSYS 14.0). For Mechanical APDL (ANSYS), you can also use the launcher: Start> Programs> ANSYS 14.0> Mechanical APDL Product Launcher 14.0.
5.3. Running the ANS_ADMIN Utility for Mechanical APDL (ANSYS) /ANSYS Workbench Products
You may need to run the ANS_ADMIN utility to relink Mechanical APDL (ANSYS) if you use the customization tools. For more information on individual options available with this utility, see the online help accessible from Help buttons on the utility dialog boxes. You can launch ANS_ADMIN without administrative privileges, but some of the options require administrative privileges. If certain options are grayed out, you do not have the necessary system administrator privileges necessary for that option, or the corresponding product may not be installed. To run the ANS_ADMIN utility, choose Start> Programs> ANSYS 14.0> Utilities> ANS_ADMIN 14.0.
5.4. Product Localization

Many ANSYS, Inc. products are available in multiple languages, including English, German, French, and Japanese. For those products that are localized, you are able to view the GUI and messages in the specified language. See your specific product documentation for instructions on choosing a localized version of the product. All products that are localized define the language via the languagesettings.txt file. In most cases, you will not have to manually edit this file. If you do need to edit it manually, you can use one of the following values: en-us (English, default) de (German) fr (French) ja (Japanese) ANSYS, Inc. applications will look for the languagesettings.txt file in the following locations, in order: 1. 2. %appdata%\Ansys\v140 <install_dir>\Ansys Inc\v140\commonfiles\Language
ANSYS, Inc. licensing also looks for the languagesettings.txt in the licensing languages subdirectories in order to display the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnect message and log files in a different language. Some products are not fully localized but offer only the messages in a translated version. See the following section for instructions on translated message file installation.
35
5.4.1. Translated Message File Installation for Mechanical APDL (ANSYS) /ANSYS Workbench Products
If your ANSYS, Inc. sales representative has supplied you with message files translated into your local language, use the following procedure to install and access these files from within Mechanical APDL (ANSYS): 1. Create an appropriately named subdirectory to hold the message files. For example, if your local language is French, create a directory in the following location:
<os drive>\Program Files\Ansys Inc\V140\ANSYS\docu\fr
2. 3.
Copy the message files (msgcat.140, msgidx.140, and msgfnm.140) into the newly created subdirectory. Access these message files by using the -l command line option. For example:
ansys140 -l fr
Or, when you are running Mechanical APDL from the Mechanical APDL launcher, choose the Language Selection option and then pick the desired language. You must create a newly translated message file for each release of Mechanical APDL because error messages may occur in a different order for each release.
36
Chapter 6: Uninstalling the Software

6.1. Uninstalling ANSYS, Inc. Products
Use this process to uninstall any ANSYS, Inc. product that was installed using the Unified Installation process. Note to CFX Users The provided uninstall tool cannot uninstall MPI services. If you have CFX products installed that you are uninstalling, you must stop the MPI services before continuing with the uninstall: 1. 2. 3. As an administrator, go to Start> Run and type Services.msc. Search for " Platform MPI Remote Launch" and if found, click Stop. Continue with the uninstallation procedure, below. All users should use the following procedure to uninstall ANSYS,
Uninstall Procedure for All Users Inc. products.
Note
If you configured your CAD programs using the CAD Configuration Manager as an administrative user (required to register the necessary prerequisites), you must unconfigure your CAD programs as an administrative user before uninstalling ANSYS products as a non-administrative user. Failing to do so could result in undesirable CAD behavior. 1. 2. Close down all applications that are currently running. Select Start> Programs> ANSYS 14.0> Uninstall 14.0. You must uninstall with the same or higher privileges than were used to install the product, and we strongly recommend uninstalling as the same user who installed the product originally. If you are a non-administrative user and you attempt to uninstall a product that was installed by an administrative user, you will not be able to proceed. Likewise, if you are a non-administrative user and you attempt to uninstall a product that was installed by a different non-administrative user, you will not be able to proceed. If you are an administrative user and you are uninstalling a product that was installed by a nonadministrative user, we recommend that you log in as the same non-administrative user who installed the product and uninstall the product as that user. If you wish to proceed with the uninstall as an administrative user, you should first run %AWP_ROOT140%\commonfiles\tools\<platform\ProductConfig.exe as the same non-administrative user who installed the product and unconfigure each product. After you have unconfigured the installed products as a non-administrative user, you can then proceed with the administrative uninstall. If you do not run the ProductConfig.exe as the installing non-administrative user, the Start menu options and environment variables will not be removed for that user. 3. Select the product(s) to be uninstalled and unconfigured and click Uninstall Selected Item(s). Not all products and product components may be listed individually.
37
Chapter 6: Uninstalling the Software 4. 5. You will be asked to save all data and close all Windows applications before continuing. Click OK. After all products are uninstalled, click Yes to delete the \v140 directory. This will remove all files and subdirectories under the \v140 directory, including any user or customized files that you may have added. If you have added any files or subdirectories, you may want to copy them to a temporary location so they are not deleted. A message appears indicating that the uninstallation is complete. Click OK.
6.
CFD-Post CFD-Post can be installed as a standalone product; however, as a standalone product, it is also automatically installed with FLUENT, POLYFLOW, and Icepak. To uninstall CFD-Post, you must uninstall all of the above products that you have installed. If you choose to uninstall standalone CFD-Post without uninstalling the other products, you will not be able to proceed with the uninstall. You will need to revise your uninstall selections before continuing. If you choose to uninstall all of the other products that include standalone CFD-Post but you do not select CFD-Post, then CFD-Post will not be removed.
Individual product directories may not be removed if they contain components that are shared with other products that have not been uninstalled. However, the uninstalled product will no longer run. In the case of a platform (file server) installation, the uninstall will remove the selected product(s) from all of the Windows platforms. This procedure removes the specified ANSYS, Inc. program from your system but will not remove the ANSYS licensing components. Follow the steps in Uninstalling Licensing Components (p. 38) to uninstall the licensing components.
6.1.1. Uninstalling Licensing Components

Before proceeding with the following steps to remove the ANSYS licensing components from your system, make certain that there are no ANSYS, Inc. products on this machine or any other machines on the network that rely on these ANSYS licensing components. License Servers 1. 2. Follow these steps on a license server machine:
Stop the ANSYS, Inc. License Manager via the ANSLIC_ADMIN utility (Start> Programs> ANSYS Inc. License Manager> Server ANSLIC_ADMIN Utility). Uninstall the ANSYS, Inc. License Manager service. You must use the following command to do so:
"C:\Program Files\Ansys Inc\Shared Files\Licensing\<platform>\ansysli_server" -k uninstall
3. 4. 5.
Delete the licensing subdirectory. Remove the ANSYS, Inc. License Manager folder from the Start menu. Remove the ANSYSLIC_DIR and the ANSYSLIC_SYSDIR environment variables, if set. Follow these steps on client machines:
Clients 1. 2.
Delete the licensing subdirectory. Remove the ANSYS 14.0> ANSYS Client Licensing folder from the Start menu.
38

The connection, geometry interface, and other CAD functionality for all supported CAD products is included with the ANSYS release media. Select the CAD systems you want to install during the installation process. If you choose not to install CAD systems during the installation, you can install them at a later date. To run the connection or geometry interface functionality, you need to: 1. 2. 3. Ensure that the CAD product is correctly installed and licensed. Ensure that you have the correct ANSYS, Inc. license(s). Run the installation setup.
For complete information about the files you can import and the platforms supported by the connection capability, see Introduction to Import in the Connection User's Guide. For more information about geometry interface information in ANSYS Workbench, see the topics Attach to Active CAD Geometry and Import External Geometry File in the ANSYS DesignModeler help.
Caution
Be sure to install Mechanical APDL (ANSYS) and the connection functionality from the same release. If you attempt to run the latest connection functionality on a machine that is running an earlier release of Mechanical APDL, or vice versa, the connection may fail. The connection for Creo Parametric (formerly Pro/ENGINEER) requires you to run Mechanical APDL, Creo Parametric and the connection for Creo Parametric on the same machine. The connection for NX requires you to run Mechanical APDL, NX, and the connection for NX on the same machine. The connections for CATIA, SAT, and Parasolid do not require any additional CAD installation.
7.1. Using the CAD Configuration Manager

The CAD Configuration Manager allows you to configure geometry interfaces for Mechanical APDL (ANSYS), ANSYS Workbench, and ICEM CFD Direct CAD interfaces. CAD configuration is typically handled during the product installation; however, if you chose to skip those steps, or if you make changes to your local CAD configuration between releases (for example, you install, move, or update your CAD package, or remove it entirely), you can use this utility. You can run the CAD Configuration Manager as an administrative or as a non-administrative user. However, in order for the necessary prerequisites to be registered to run the ANSYS Workbench readers, and some other components (see Step 3, below), you must run as an administrative user. Administrative rights are also required to fully configure several ANSYS CAD products, including the ANSYS Workbench reader for Catia V5, and the ANSYS Workbench Plug-ins for Inventor, Creo Elements/Direct Modeling, AutoCAD, Solid Edge, and SolidWorks. NX in reader mode also requires administrative rights to configure. Likewise, when unconfiguring, you should unconfigure CAD products as an administrative user before uninstalling the product as a non-administrative user. Otherwise, your CAD products could end up in an undesirable state, resulting in unpredictable behavior.
39
Chapter 7: Configuring CAD Products If you are running as an administrative user on a machine with a non-administrative installation, you may not see a CAD Configuration Manager shortcut. You can run the tool from <os drive>\Ansys Inc\V140\commonfiles\CAD\bin\<platform>\Ans.CadInt.CADConfigUtilityGUI.exe. The CAD Configuration Manager is organized into several tabs: CAD Selection Creo Parametric NX Teamcenter Engineering (active on Windows only) CAD Configuration
An administrative user has the option to configure or unconfigure any selected CAD systems either for the present user's environment or for all users, as indicated by the Configuration actions apply to options. When the original installation was performed by a non-administrative user, an administrative user will only be allowed to configure or unconfigure for all users. In this situation, Creo Parametric and NX configure and unconfigure actions are skipped. Non-administrative users will only be allowed to configure for themselves. Any user-specific configuration settings take precedence over global configuration settings. This document describes how to use the CAD Configuration Manager as a wizard, beginning with the CAD Selection tab and using the Next button to progress through the configuration process. You can also manually select each tab to progress through the configuration process; both methods work the same. However, the applicable tabs will not be enabled until you choose the associated product on the CAD Selection tab. 1. 2. 3. Run Start> Programs> ANSYS 14.0> Utilities> CAD Configuration Manager 14.0. On the CAD Selection tab, choose the ANSYS products and the CAD products that you need to configure. You must select at least one ANSYS product to enable the remaining functionality. Click Next. If you selected only Workbench and ANSYS Geometry Interfaces with no CAD Products selected, the necessary prerequisites will be registered, enabling Geometry (DesignModeler) and all the Readers. You must run the CAD Configuration Manager as an administrative user for some CAD registrations to take place. Select the CAD Configuration tab and click Configure Selected CAD Interfaces to register the prerequisites. If you selected Creo Parametric (formerly Pro/ENGINEER) as one of your CAD products, you will have to choose which Creo Parametric product to configure: a. b. The Reader option specifies the non-associative source and doesn't require a Creo Parametric installation. The Workbench Associative Plug-In option requires Creo Parametric to be installed. When you chooose this option, the Creo Parametric tab opens. i. ii. Enter or browse to the Creo Parametric installation location (for example, C:\Program Files\PTC\Creo 1.0\Parametric). Enter or browse to the Creo Parametric start command (for example, C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat). Include the complete path if entering the command manually. Click Next.
4.
iii.
40
Using the CAD Configuration Manager
Note
When ANSYS Workbench is installed by an administrative user, the Creo Parametric plug-in will load for all users of the designated CAD install. However, when multiple Creo Parametric installations are present on the system, the plug-in should only be configured for a single installation of Creo Parametric; otherwise unconfiguring the plug-in will cause load problems for all other installations of the CAD. 5. If you selected NX as one of your CAD products, you will have to choose which NX product to configure: a. b. The Reader option specifies the non-associative source and doesn't require an NX installation. The Workbench Associative Plug-In option requires NX to be installed. When you chooose this option, the NX tab opens. i. ii. Enter or browse to the NX installation location (for example, C:\Program Files\UGS\NX 6.0). Enter or browse to the NX custom directory file path (for example, C:\Documents and Settings\UserName\Application Data\Ansys\v140\Unigraphics).
Note
If you are installing as an administrator, this file path will be defined in your administrator's user space by default and non-administrative users will not be able to run. Use this setting to specify a new location for the custom directory file path that is accessible by all users. iii. iv. 6. Choose to enable or disable color attribute processing. Click Next.
If you selected Inventor and/or SolidWorks as one of your CAD products, you will have to choose which Inventor and/or SolidWorks product to configure: a. b. The Reader option specifies the non-associative source and doesn't require an Inventor or SolidWorks installation. The Workbench Associative Plug-In option requires Inventor or SolidWorks to be installed.
7.
If you selected Teamcenter Engineering as one of your CAD products, the Teamcenter Engineering tab opens: a. b. Enter or browse to the Teamcenter Engineering installation location (for example, C:\SIEMENS\Teamcenter2007). Choose Next.
8.
If you selected Catia V5 as one of your CAD products, you will have the option to choose which CATIA V5 product to configure. a. Select the Standard Interface option to configure the CATIA V5 standalone reader that does not require an installation of the CATIA V5 CAD program (this reader does not support CAD associativity or parameters).
41
Chapter 7: Configuring CAD Products b. Select the CADNexus/CAPRI CAE Gateway option to configure the CATIA V5 associative reader that does require an installation of the CATIA V5 CAD program and the CADNexus/CAPRI CAE Gateway (this geometry interface does support CAD associativity and parameter modifications). Click Next.
c. 9.
The CAD Configuration tab opens. a. b. c. Click the Configure Selected CAD Interfaces button. When the configuration for all products is complete, log entries appear, listing those products that were successfully configured and those that were not. Address any errors and reconfigure. For more details, click the Display Configuration Log File button to see a detailed log file.
10. When all of your CAD products have been successfully configured, click Exit. You can review the CAD Configuration Manager log file, CADConfigurationMgr.log, in \ANSYS Inc.
Important
If you change your source from reader to associative plug-in or vice-versa (Creo Parametric, NX, SolidWorks, Autodesk Inventor, or Catia), you must first unconfigure the existing source and then configure using the new source.
7.1.1. Unconfiguring
If you need to unconfigure any of your CAD products, follow the steps above, but choose Unconfigure Selected CAD Interfaces on the CAD Configuration tab.
7.1.2. Running the CAD Configuration Manager in Batch Mode

You can configure ANSYS Geometry Interfaces by supplying the CAD Configuration Manager with arguments specific to the CAD sources you want to make available. The following table contains a list of supported arguments. The command to run the CAD Configuration Manager in batch mode on Windows is:
"<installpath>\commonfiles\CAD\bin\<platform>\Ans.CadInt.CADConfigurationUtility.exe" -arguments
Argument unconfigure
Value None
Comment Results in any specified CAD sources being unconfigured. When this flag is absent, the CAD Configuration Manager will attempt to configure all designated CAD sources. Specify Creo Parametric source as either the associative plug-in or the reader (Spatial, no Creo Parametric install required). When the plug-in is specified, additional arguments PROELOADPOINT and PROE_START_CMD are required. Not required with unconfigure operation.
Either: PE_CONFIG_WB or PE_CONFIG_WBSPATIAL
None
PROELOADPOINT
Full path to Creo Parametric installa-
42
Using the CAD Configuration Manager Argument Value tion (quotes required on Windows). PROE_START_CMD Full path to command used to launch Creo Parametric (quotes required on Windows) None Not required with unconfigure operation. Comment
Either: UG_CONFIG_WB or UG_CONFIG_WBSPATIAL
Specify NX source as either the associative plug-in or the reader (Spatial, no NX install required). When the plug-in is specified, the argument UGII_BASE_DIR must also be specified. This should agree with environment variable UGII_BASE_DIR. Not required with unconfigure operation. Process NX entity colors as possible source of attributes and named selections. Not required with unconfigure operation. Specify Catia V5 source as either the Reader (Spatial, no Catia install required) or CAPRI (CADNexus install required). Configure/unconfigure Creo Elements/Direct Modeling. Specify Inventor source as either the associative plugin or the reader (Spatial, no Inventor install required). Specify SolidWorks source as either the associative plugin or the reader (Spatial, no SolidWorks install required). Configure/unconfigure Solid Edge. Configure/unconfigure AutoCAD. Configure/unconfigure the ICEM CFD Direct CAD Interface to Creo Parametric.The arguments PROELOADPOINT and PROE_START_CMD must also be specified. Configure/unconfigure the ICEM CFD Direct CAD Interface to NX.The argument UGII_BASE_DIR must also be specified. Configure/unconfigure Teamcenter Engineering; for configuration requires IMAN_ROOT flag. Not required with unconfiguration operation.
UGII_BASE_DIR
Full path to NX installation None
UG_USE_COLORS
Either: CATIA_SPATIAL or CATIA_CAPRI OSDM_CONFIG Either: INVENTOR_CONFIG or INVENTOR_CONFIG_WBSPATIAL Either: SOLIDWORKS_CONFIG or SW_CONFIG_WBSPATIAL SOLIDEDGE_CONFIG ACAD_CONFIG PE_CONFIG_ICEM
None
None None
None
None None None
UG_CONFIG_ICEM
None
TEAMCENTER_CONFIG IMAN_ROOT
None Path to Teamcenter Engineering installation. None None
JTOPEN_CONFIG CATIA4_CONFIG
Configure/unconfigure JTOpen. Configure/unconfigure CATIA v4.
43
Note
All arguments require a dash (-) before them in order to be properly recognized by the CAD Configuration Manager. Arguments' values should not have a dash preceding them. For example, you can configure Creo Parametric and SolidWorks Geometry Interfaces to ANSYS Workbench from the command line by using the following:
"<installpath>\commonfiles\CAD\bin\<platform>\Ans.CadInt.CADConfigurationUtility.exe" -SW_CONFIG -PE_CONFIG_WB -PROELOADPOINT "C:\Program Files\PTC\Creo 1.0\Parametric" -PROE_START_CMD "C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat"
where installpath is the same as the value of environment variable %AWP_ROOT140%, platform is the value of environment variable %ANSYS_SYSDIR%, and Creo Parametric is installed to C:\Program Files\PTC\Creo 1.0\Parametric. To unconfigure the same CAD Interfaces, the command would be:
"<installpath>\commonfiles\CAD\bin\<platform>\Ans.CadInt.CADConfigurationUtility.exe" -unconfigure -SW_CONFIG -PE_CONFIG_WB
Although the argument order does not matter, an argument value must immediately follow its argument.
7.1.3. Uninstalling
If you performed your installation as a non-administrative user and you are unconfiguring CADs as an administrative user in preparation for a product uninstall, then use the Uninstall All Products button on the CAD Configuration tab. This action will also unconfigure prerequisites for geometry and readers.
Warning
Do not proceed with an uninstall for CAD-specific unconfigure actions or you will leave some ANSYS Workbench products unusable.
7.1.4. Creo Parametric Configuration

Running the CAD Configuration Manager for Creo Parametric (formerly Pro/ENGINEER) performs the following steps to activate the Creo Parametric plug-in: Sets the environment variable PROE_START_CMD140 to the file used to launch Creo Parametric (for example C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat). Sets the environment variable ANSYS_PROEWF_VER to ProE on Windows 32bit, or to ProE_Wildfire4 if running Wildfire 4.0, Wildfire 5.0, Creo Elements/Pro 5.0 or Creo Parametric on 64-bit Windows. For administrative installations, adds the ANSYS 14.0 entry to the config.pro file located in <creo_path>\text. An example for Creo Parametric would be:
C:\Program Files\PTC\Creo 1.0\Common Files\F000\text
An example for Wildfire 5.0 would be:

C:\Program Files\proeWildfire 5.0\text
44
Using the CAD Configuration Manager For non-administrative installs, or when the administrative user does not have access to the Creo installation, the config.pro located in either %HOME% or %HOMEDRIVE%%HOMEPATH% will be modified with the 14.0 entry. Updates the WBPlugInPE.dat file referenced in the config.pro file, so that it contains information for loading the WorkBench Plug-In and the ANSYS Connection product. Registers the Plug-In file WBPlugInPECOM.dll referenced in the WBPlugInPE.dat file.
If you do not have write access to your ANSYS Workbench installation, you may encounter the following error when attempting to import Creo Parametric models without an active CAD session: No write access, please choose another startup directory for trail file creation. To prevent this issue, add the following line to your config.pro file:
trail_dir $TEMP
WBPlugInPE.dat File Contents
The WBPlugInPE.dat file should look like this example:
NAME WB140PluginProWF EXEC_FILE E:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\%ANSYS_PROEWF_VER%\ %ANSYS_SYSDIR%\WBPlugInPECOM.dll TEXT_DIR E:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\%ANSYS_PROEWF_VER%\ ProEPages\Language\%AWP_LOCALE140% STARTUP dll delay_start FALSE allow_stop TRUE unicode_encoding FALSE REVISION ProEWildfire END NAME ac4pro140dll exec_path E:\Program Files\Ansys Inc\V140\ANSYS\ac4\bin\pro\%ANSYS_SYSDIR%\ac4pro.exe text_path E:\Program Files\Ansys Inc\V140\ANSYS\ac4\data\pro\text STARTUP dll delay_start FALSE allow_stop TRUE unicode_encoding FALSE revision 24.0 end
Do not delete any of these lines. If you modify this file, do NOT enter a carriage return after the END line. The file may be customized with other information. If these lines are deleted, or if the WBPlugInPE.dat file is not present in any of the directories in the search path, Creo Parametric will not load ANSYS-related CAD interfaces. You should typically never have to edit these files for path information contained within them. Paths are determined by environment variable settings, which are set automatically during installation. If you encounter problems when attempting to run Creo Parametric, use the CAD Configuration Manager to reconfigure rather than attempting to edit files directly. Following an update of an existing Creo Parametric 1.0 installation to a different maintenance release (for example upgrading from datecode F000 to M010), the ANSYS Workbench Associative Plug-In will no longer be configured. To reactivate your plug-in, follow the steps described in Using the CAD Configuration Manager (p. 39). This situation does not apply to Pro/ENGINEER Wildfire 4.0, Pro/ENGINEER Wildfire 5.0, or Creo Elements/Pro 5.0.
7.1.4.1. Configuring the Connection for Creo Parametric

All Creo Parametric users must have copies of the WBPlugInPE.dat file and the config.anscon.140 (connection for Creo Parametric) files. The config.anscon.140 file is placed in the Program
45
Chapter 7: Configuring CAD Products Files\Ansys Inc\V140\ansys\ac4\data\<platform> directory. config.anscon.140 must be copied into the user's working directory at the time Creo Parametric is started. The WBPlugInPE.dat file is placed in the Program Files\Ansys Inc\V140\AISOL\CADIntegration\%ANSYS_PROEWF_VER%\ProEPages\config directory. This file defines the name of the executable, the path to the executable, the path to the message file, and the current revision of Creo Parametric.
Note
If the ANSGeom menu in Creo Parametric does not appear correctly, copy the config.anscon.140 file into your working directory and restart Creo Parametric.
7.1.4.1.1. The WBPlugInPE.dat File and config.pro File

Creo Parametric uses the WBPlugInPE.dat file to locate related executables such as the connection for Creo Parametric. Mechanical APDL (ANSYS) /ANSYS Workbench also requires a config.pro file. For administrative installations, the config.pro file resides in <path-to-proe>\text for any Pro/ENGINEER Wildfire release and <path-to-creo-parametric>\..\Common Files\<Creo Ship Code>\text for Creo Parametric. The Creo Ship Code is a three digit number preceded by a single letter. The ship code is specified in the Creo Parametric installation log, which can be found in <path-to-creo-parametric>\uninstall\instlog.txt. For non-administrative installs, the config.pro file resides in the %HOME% directory, and when HOME is not defined, in the %HOMEDRIVE%%HOMEPATH% directory.
The config.pro file contains a PROTKDAT line that points to the WBPlugInPE.dat file. This file is generated either during the product install or by running the CAD Configuration Manager to configure the Mechanical APDL (ANSYS) /ANSYS Workbench products for Creo Parametric. The <proe_platform> variable is the name that Creo Parametric gives to its platform directories: WBPlugInPECOM Hardware Platform ANSYS Platform <platform> Creo Parametric Platform <proe_platform> i486_nt x86e_win64
Intel 32-bit XP x64
win32 winx64
7.1.4.1.2. The config.pro File

A typical config.pro file might look like the following example. This example has an entry for ANSYS Workbench and another for ANSYS ICEM CFD. You may have other Creo Parametric specific customizations.
PROTKDAT E:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\$ANSYS_PROEWF_VER\ ProEPages\config\WBPlugInPE.dat PROTKDAT $PROMIF_ACN\protk.dat
46
Using the CAD Configuration Manager
7.1.4.1.3. The config.anscon.140 File

Users who launch Mechanical APDL (ANSYS) from Creo Parametric will need the information from the config.anscon.140 file. This file is installed for all users in the \ac4\data\<platform> subdirectory. You typically do not need to edit this file. Here is a sample config.anscon.140 file:
ANSYS_CMD %AWP_ROOT140%\ANSYS\bin\%ANSYS_SYSDIR%\ansys.exe ANSYS_GRAPHICS_DEVICE WIN32 ANSYS_SOLVER Sparse** ANSYS_SELECTED_LAYERS 1-256** ANSYS_GEOMETRY_TYPE Solids Only** ANSYS_NEUTRAL_FORMAT Yes ANSYS_PRODUCT_NAME ANFL
**These variables are not supported by Creo Parametric and are ignored by Creo Parametric. See Setting ANSYS Configuration Parameters in the Connection User's Guide for more information about the config.anscon.140 file.
7.1.4.2. Creo Parametric Environment Variables

Most environment variables are set during product installation. In general, you will not need to reset these variables. Check the manuals for the individual CAD products for information about environment variables and their settings. PROE_START_CMD140 Specifies the name of the .bat file which launches Creo Parametric on the system. The path to the executable should be already set if the Creo Parametric installation path has been defined for the PATH environment setting. PROE_START_CMD140 Default = C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat
7.1.5. NX Configuration
Running the CAD Configuration Manager for NX performs the following steps to activate the NX plugin: If not already existing, sets the environment variable UGII_CUSTOM_DIRECTORY_FILE to %APPDATA%\Ansys\v140\Unigraphics\custom_dirs.dat. If not already present, adds an entry to the custom_dirs.dat file specifying the location of the PlugIn, e.g., C:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\UnigraphicsNX6\%ANSYS_SYSDIR%. Registers the Plug-In file (DSPlugInUG6COM.dll). For the previous example, these files would be located in C:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\UnigraphicsNX6\winx64\startup. Registers AGPSUtilCOM.dll. For the previous example, this file would be located in C:\Program Files\Ansys Inc\V140\AISOL\CADIntegration\ UnigraphicsNX6\winx64.
7.1.5.1. Configuring the Connection for NX

User-Defined Environment Variables You will need to have the following environment variable set if you will be running the connection for NX product from inside NX.
47
Chapter 7: Configuring CAD Products UGII_VENDOR_DIR for Mechanical APDL This environment variable is not set during the installation process and can only be set in a user's startup file or at command level before running NX. This environment variable defines the ANSYS menu for NX. You must set this environment variable if you will be running the connection for NX product from inside NX. This environment variable tells NX where to find the ANSYS program, for example: Program Files\Ansys Inc\V140\ANSYS\ac4\bin\ug30\<platform>. UGII_BASE_DIR The environment variable UGII_BASE_DIR must be defined for proper operation of NX and the ANSYS Workbench Plug-In to NX. This environment variable is typically created by the NX installer; however, in rare cases, you may have to create/update the variable. In these situations, the NX Installation Location field will be left blank within the CAD Configuration Manager's NX tab. When multiple NX versions are installed on a system, the UGII_BASE_DIR environment variable must be set to the install path of the NX version to be launched, prior to starting that version of the CAD. Otherwise errors will be encountered during CAD startup and the plug-in will not load. For example, if switching from NX 6 to run NX 8, you must update UGII_BASE_DIR to the NX 8 path before starting NX 8.
7.1.5.2. Configuring for Teamcenter Engineering

Running the CAD Configuration Manager for NX performs the following steps to activate the Teamcenter plug-in: When Teamcenter Engineering is detected, the environment variable IMAN_ROOT is set to the Teamcenter Engineering installation path. When Teamcenter Unified is detected, the environment variable TC_ROOT is set to the Teamcenter Unified installation path.
7.1.6. ANSYS ICEM CFD Configuration

Running the CAD Configuration Manager for ANSYS ICEM CFD performs the following steps to activate the ANSYS ICEM CFD plug-in: For Creo Parametric, sets the environment variable PROE_START_CMD140 to the file used to launch Creo Parametric (for example C:\Program Files\PTC\Creo 1.0\Parametric\bin\parametric1.bat). Sets the PROMIF_ACN environment variable to the directory where the ANSYS ICEM CFD interface resides (C:\Program Files\Ansys Inc\V140\icemcfd\<platform>\dif/pro by default). For NX, sets the UGII_VENDOR_DIR environment variable to the directory where the ANSYS ICEM CFD interface resides (C:\Program Files\Ansys Inc\V140\icemcfd\<platform>\dif/ug by default).
7.2. Configuring CADNexus/CAPRI CAE Gateway for CATIA V5

The CADNexus/CAPRI CAE Gateway for CATIA V5 product is available for ANSYS Workbench. The ANSYS Workbench-specific portions are included in the installation. However, to run this product, you must complete the configuration as follows: 1. 2. Install ANSYS Workbench according to the instructions in this guide. Install CATIA V5 and LUM licensing (requires a CATIAV5 license key MD2, HD2 or ME2).
48
Configuring CADNexus/CAPRI CAE Gateway for CATIA V5 3. From the ANSYS, Inc. Customer Portal, download the CADNexus/CAPRI CAE Gateway for CATIA V5 for your platform (Windows 32 or Windows x64) to a temporary folder. (Do not download to a folder containing blank spaces in the folder name, e.g., Program Files). Follow the download procedures described in Downloading the Installation Files (p. 15). Extract the contents of the zip file using your standard zip utility. Install CADNexus/CAPRI CAE Gateway for CATIA V5 using the appropriate exe for your platform. Follow the instructions on the CAPRI installation screens to complete the installation. When specifying the component to install, you will need to select the desired CatiaV5 release under CAPRI CAD Applications. When asked if CAPRI should set the environment variables, click Yes. Run the CAD Configuration Manager and select the Catia V5: CADNexus/CAPRI CAE Gateway option to complete the configuration as described in Using the CAD Configuration Manager (p. 39).
4. 5. 6.
7.
Note
Using the CAD Configuration Manager to set up the CADNexus/CAPRI CAE Gateway does not require administrative rights, although installing that product (step 5) requires these rights. However, if you wish to reconfigure to use the ANSYS Workbench Reader for Catia V5, administrative rights are required.
If you wish to revert to the standard CATIA V5 interface, run the CAD Configuration Manager and select the Catia V5: Standard Interface option to complete the configuration as described in Using the CAD Configuration Manager (p. 39). You cannot run the standard CATIA V5 interface simultaneously with the CADNexus/CAPRI CAE Gateway for CATIA V5 interface.
49
50
8.1. Installation Troubleshooting
This section lists problems and error messages that you may encounter while installing and/or running ANSYS, Inc. products. After each situation description or error message is the user action required to correct the problem. You can also find answers to commonly-asked questions on our customer portal. After you log in to the customer portal, select Online Support> Installation/System FAQs. Then select either the Windows or UNIX/Linux link. For information on licensing-related errors, see the Troubleshooting section of the ANSYS, Inc. Licensing Guide. In addition, this appendix describes the ANSYS diagnostic tools, which are useful for troubleshooting some problems.
8.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information

You can use the Gather Diagnostic Information option of the ANSLIC_ADMIN utility to query the system for various pieces of information that may be needed for troubleshooting certain problems. This option collects information about the system as well as about ANSYS licenses and sends all of the information that it collects to the log area. At times it may be necessary to provide the information for technical support. Use the Write to File button at the bottom of the ANSLIC_ADMIN to write a file. Then forward the file to the appropriate person. You can also use the AnsysInstallationDiagnostics.exe, in the \v140\instutil directory, for additional installation diagnostics. This tool is helpful to diagnose installation and runtime issues. One or more log files will be generated either at the same location as the tool or in your temporary directory, depending on directory permissions. The log files are intended to help ANSYS, Inc. technical support personnel expedite any technical issues. It would be useful to have the files ready to provide before contacting Technical Support.
8.1.2. Uninstall Gives Access Denied Error Message

If you run the uninstall utility as a non-administrative user, you may get access denied error messages when removing product components. Run the uninstall as an administrative user, and close all applications before running the uninstall.
8.1.3. Uninstall on Windows 7 and Vista Systems Gives Compatibility Error Message
If you uninstall an ANSYS, Inc. product on Windows 7 or Vista systems using the ANSYS, Inc. Uninstall utility, you may see the following error message: This program might not have installed correctly.
51
Chapter 8: Troubleshooting If this program didn't install correctly, try reinstalling using settings that are compatible with this version of Windows. This message is caused by Windows 7/Vista's Program Compatibility Assistant and can safely be ignored. Click Cancel and continue with the uninstall.
8.1.4. A .chm File Does Not Display Properly Across a Network

Help system .chm files may not display topics correctly when you try to use a Universal Naming Convention (UNC) path to open the file on a network shared folder, typical with a Network Configuration install. This is a known issue with security update 896358, security update 840315, or Microsoft Windows Server 2003 Service Pack 1 (SP1). Please go to http://support.microsoft.com./kb/896358 and http://support.microsoft.com./kb/896054 for more information on this problem and Microsoft's recommended fix.
8.1.5. Products Crash with an Application Error

On Windows Server 2008 or Windows XP systems, ANSYS applications may crash with an application error if the DEP (Data Execution Prevention) flag is set. To check your DEP setting, right mouse click on My Computer, and select Properties. Select the Advanced tab, and under Performance, click Settings. Then select the Data Execution Prevention tab. If DEP is set, you will need to add ANSYS to the list of exceptions. For more information on DEP and how to change the settings, see http://support.microsoft.com/kb/875351.
8.1.6. Product Installation Does Not Create Start Menu Item for ANSYS and CAD Plugins Do Not Work
On Windows Vista and Windows 7 systems, if you install ANSYS, Inc. products but do not see a Start Menu item and your CAD plugins do not work, the TEMP environment variable may be pointing to an inaccessible location. For example, it may point to a location such as %USERPROFILE%\Local Settings\Temp. As a result, the product installation could end without configuring the product correctly. You should ensure that the TEMP variable points to a valid location, such as %USERPROFILE%\AppData\Local\Temp.
8.1.7. Product Installation Displays Security Warning Dialogs or Silent Product Installation Hangs on a Network Install
If you see a security warning dialog box during a GUI installation/product configuration, or if your installation hangs during a silent installation, you may need to modify your security settings. Set the machine you are installing from as a trusted site and allow launching of unsafe applications so that the prerequisite installation can complete. Then re-run the installation. Contact your system administrator or refer to your operating system documentation for details on modifying security settings. Alternatively, you can run the prerequisite check to verify that you have all the necessary prerequisites. If necessary, install any prerequisites and rerun the installation: 1. 2. Run PreReqCheck.exe from the top level directory. Install any missing prerequisites by running InstallPreReqs.exe from the top level directory as an administrator.
52
Installation Troubleshooting - Mechanical APDL (ANSYS) and ANSYS Workbench Products 3. When the prerequisites have finished installing, run the installation as you normally would (GUI or silently).
8.1.8. System-related Error Messages

***Error, ANSYS140_DIR environment variable is not set. This is a fatal error exiting. This message indicates that the ANSYS140_DIR environment variable was not set where necessary for licensing. This environment variable should be set to the installation directory. Unexpected error: Request for the permission of type ... failed. If you encounter this type of message on a server configuration, you may need to set the machine as a trusted site. On Windows XP machines, in the Control Panel, select Internet Options and select Security. Click on Trusted Sites and click Sites. Add the machine as file://servername. On Windows Vista and Windows 7 machines, in the Control Panel, select Network and Internet, select Internet Options, and select Security. Click on Trusted Sites and click Sites. Add the machine as file://servername.
8.1.9. CasPol Error Messages

ERROR: Not enough arguments, no permission set specified If you are configuring to a server with spaces in the path and get this error, then you must put quotes around your server specification as shown in the following example:
C:\Users\>C:\Windows\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -m -a g 1.2 -url file://"\\machineabc\ANSYS Inc\*" FullTrust
8.2. Installation Troubleshooting - Mechanical APDL (ANSYS) and ANSYS Workbench Products
The items listed below apply only to the Mechanical APDL (ANSYS) and/or ANSYS Workbench products.
8.2.1. The Mechanical APDL Launcher is Excessively Slow to Start

If the Mechanical APDL launcher takes an excessively long time to startup (Windows only), make sure the hostnames in the ansyslmd.ini file and in the ANSYSLMD_LICENSE_FILE and the ANSYSLI_SERVERS environment variables are typed correctly and that the hosts specified by the hostnames exist. Replacing hostnames with IP addresses may improve the speed as well. Also verify that the port number is correct.
8.2.2. Display Problems on Windows XP

This situation applies only to 32-bit Windows systems running Mechanical APDL (ANSYS). Windows XP includes a feature called Windows Ghosting that may cause Mechanical APDL graphing or plotting problems in 3-D mode on some XP systems. If this problem occurs, follow the procedure below to turn Windows Ghosting off for Mechanical APDL: 1. 2. Open the file ansys140.sdb, located in Program Files\Ansys Inc\V140\ANSYS\bin\intel. A Compatibility Database Installer dialog box stating "Installation of ANSYS140 complete" will be displayed. Click OK.
53
Chapter 8: Troubleshooting To reset Windows XP Windows Ghosting for Mechanical APDL, follow the procedure below: 1. Open a DOS command prompt and type the following command:
sdbinst /U "%ANSYS140_DIR%\bin\intel\ansys140.sdb"
2.
A Compatibility Database Installer dialog box stating "Uninstallation of ANSYS140 complete" will be displayed. Click OK.
8.2.3. Display Problems on Windows 7 and Vista

This situation applies only to Windows systems running Mechanical APDL (ANSYS). Windows Vista and 7 include a theme called Aero that may cause Mechanical APDL graphing or plotting problems in 3-D mode on some systems. If this problem occurs, disable the Windows Aero theme when running Mechanical APDL.
8.2.4. ANS_ADMIN Error Messages

Grayed out options If certain options are grayed out, your account may not have the necessary system administrator privileges necessary to run those options.
8.2.5. Mechanical APDL Product Launcher Error Messages

Some of the more common error messages follow. See the ANSYS, Inc. Licensing Guide for licensing-related launcher messages. ***Cannot create required <profile> file. Therefore, cannot write to profile information during this launcher session. If you see this error, you cannot add or modify profile information during this launcher session. Verify that you have write access to the directory and restart the launcher session. Typically, this directory is C:\Documents and Settings\<user name>\Application Data\Ansys\v140\launcher on Windows or ~/.ansys/v140/launcher/ on UNIX. ***No ANSYS product installations found. Verify your Mechanical APDL (ANSYS) product installation. If the desired product was not installed, install it.
8.2.6. Distributed ANSYS Platform MPI Error Messages

You may encounter the following message when setting up Platform MPI or running Distributed ANSYS using Platform MPI. Error executing ANSYS. Refer to System-related Error Messages in the ANSYS online help. If this was a Distributed ANSYS job, verify that your MPI software is installed correctly, check your environment settings, or check for an invalid command line option. You may see this error if you did not correctly run the set password bat file. Verify that you completed this item according to the Platform MPI installation readme instructions.
54
Installation Troubleshooting - Mechanical APDL (ANSYS) and ANSYS Workbench Products You may also see this error if Ansys Inc\v140\ansys\bin\<platform> (where <platform> is intel or winx64) is not in your PATH. If you need more detailed debugging information, use the following: 1. Open a Command Prompt window and set the following: SET ANS_SEE_RUN=TRUE SET ANS_CMD_NODIAG=TRUE 2. Run the following command line: ansys140 -b -dis -i myinput.inp -o myoutput.out.
8.2.7. ANSYS Workbench Products Troubleshooting

This section lists problems and error messages that you may encounter while installing and/or running ANSYS Workbench. After each situation description or error message is the user action required to correct the problem. Always try the suggested user action before contacting your technical support representative.
Problem Situations
During setup, if you encounter any errors containing the text 0x8000FFFF you will need to install the , required installation prerequisites. Run the installation launcher (setup.exe) and choose Install Required Prerequisites. CAD System Plug-In Menus Do Not Appear for NX or Creo Parametric ANSYS Workbench on Windows platforms will append its information to an existing customization file for NX and/or Creo Parametric. If no customization file exists, ANSYS Workbench will create a file. For NX, ANSYS Workbench looks for the custom_dirs.dat file in the directory specified via the UGII_CUSTOM_DIRECTORY_FILE environment variable. For Creo Parametric, ANSYS Workbench looks for the config.pro file in the %HOMEDRIVE%%HOMEPATH% directory. In addition, during setup of the Creo Parametric Geometry Interface, ANSYS Workbench will also append its information to the config.pro file located in the Creo Parametric installation path, under the \text directory (e.g., Proewildfire2\text\config.pro). If ANSYS Workbench encounters a read-only file, it will not be able to write the necessary information to the file. In this case, you will need to revise the permissions on the file and manually add the appropriate ANSYS Workbench-specific information in order for the ANSYS menu to appear in NX or Creo Parametric. Script Errors When Running ANSYS Workbench If you encounter script errors such as "Error: Unable to create object microsoft.XMLDOM," you may need to install the latest version of Microsoft's MSXML. Please visit Microsoft's web site at http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf3bcf-4009-be21-27e85e1857b1&DisplayLang=en for more information on downloading and installing MSXML.
ANSYS Workbench Error Messages

***Unable to connect to Solver Manager. Another application might be using the Solver Manager port (10002 by default). Try changing the port number by editing the Ansys.SolverManager.exe.config file located in the installation directory at \AISOL\Bin\<platform>.
55
Chapter 8: Troubleshooting If you are getting the "Unable to connect to Solver Manager" error message or are having difficulty launching other applications/editors, it is also possible that the Windows hosts file has been corrupted. Please make sure that localhost is specified in the Windows <os drive>:\Windows\system32\drivers\etc\hosts file.
8.3. Installation Troubleshooting - ANSYS CFX

The items listed below apply only to the ANSYS CFX products.
8.3.1. TurboGrid Mouse Behavior Problems

Depending on the graphics card and driver version, you may experience problems with the accuracy of mouse clicks in the 3D Viewer. For example, you may try to insert a control point at a given location by using the mouse, but the control point appears at a location far from where you clicked the mouse. If you experience such problems, try lowering the hardware acceleration setting of your graphics card.
8.4. Contacting Technical Support

Technical Support for ANSYS, Inc. products is provided either by ANSYS, Inc. directly or by one of our certified ANSYS Support Providers. Please check with the ANSYS Support Coordinator (ASC) at your company to determine who provides support for your company, or go to www.ansys.com and select About ANSYS> Contacts and Locations. The direct URL is: http://www1.ansys.com/customer/public/supportlist.asp. Follow the on-screen instructions to obtain your support provider contact information. You will need your customer number. If you don't know your customer number, contact the ASC at your company. If your support is provided by ANSYS, Inc. directly, Technical Support can be accessed quickly and efficiently from the ANSYS Customer Portal, which is available from the ANSYS Website (www.ansys.com) under Support> Technical Support where the Customer Portal is located. The direct URL is: http://www.ansys.com/customerportal. One of the many useful features of the Customer Portal is the Knowledge Resources Search, which can be found on the Home page of the Customer Portal. Systems and installation Knowledge Resources are easily accessible via the Customer Portal by using the following keywords in the search box: Systems/Installation. These Knowledge Resources provide solutions and guidance on how to resolve installation and licensing issues quickly. NORTH AMERICA All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Toll-Free Telephone: 1.800.711.7199 Fax: 1.724.514.5096 Support for University customers is provided only through the ANSYS Customer Portal. GERMANY ANSYS Mechanical Products Telephone: +49 (0) 8092 7005-55
56
Contacting Technical Support Email: support@cadfem.de All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. National Toll-Free Telephone: German language: 0800 181 8499 English language: 0800 181 1565 International Telephone: German language: +49 6151 3644 300 English language: +49 6151 3644 400 Email: support-germany@ansys.com UNITED KINGDOM All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +44 (0) 870 142 0300 Fax: +44 (0) 870 142 0302 Email: support-uk@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. JAPAN CFX , ICEM CFD and Mechanical Products Telephone: +81-3-5324-8333 Fax: +81-3-5324-7308 Email: CFX: japan-cfx-support@ansys.com; Mechanical: japan-ansys-support@ansys.com FLUENT Products Telephone: +81-3-5324-7305 Email: FLUENT: japan-fluent-support@ansys.com;POLYFLOW: japan-polyflow-support@ansys.com;FfC: japanffc-support@ansys.com; FloWizard: japan-flowizard-support@ansys.com Icepak Telephone: +81-3-5324-7444 Email: japan-icepak-support@ansys.com Licensing and Installation Email: japan-license-support@ansys.com INDIA ANSYS Products (including FLUENT, CFX, ICEM-CFD)
57
Chapter 8: Troubleshooting Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +91 1 800 233 3475 (toll free) or +91 1 800 209 3475 (toll free) Fax: +91 80 2529 1271 Email: FEA products: feasup-india@ansys.com;CFD products: cfdsup-india@ansys.com;Installation: installationindia@ansys.com FRANCE All ANSYS, Inc. Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Toll-Free Telephone: +33 (0) 800 919 225 Email: support-france@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. BELGIUM All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +32 (0) 10 45 28 61 Email: support-belgium@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. SWEDEN All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +44 (0) 870 142 0300 Email: support-sweden@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. SPAIN and PORTUGAL All ANSYS Products Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +33 1 30 60 15 63 Email: support-spain@ansys.com Support for University customers is provided only through the ANSYS Customer Portal. ITALY All ANSYS Products
58
Contacting Technical Support Web: Go to the ANSYS Customer Portal (http://www.ansys.com/customerportal) and select the appropriate option. Telephone: +39 02 89013378 Email: support-italy@ansys.com Support for University customers is provided only through the ANSYS Customer Portal.
59
60
Configuring High Performance Computing
Release 14.0 November 2011 002310


Disclaimer Notice

Table of Contents
Configuring Distributed ANSYS ..................................................................................................................... 1 1. Setting up Distributed ANSYS .............................................................................................................. 1 1.1. Prerequisites for Running Distributed ANSYS ............................................................................... 1 1.1.1. MPI Software ..................................................................................................................... 2 1.1.2. Installing the Software ....................................................................................................... 3 1.2. Setting Up the Cluster Environment for Distributed ANSYS .......................................................... 4 1.2.1. Optional Setup Tasks .......................................................................................................... 6 1.2.2. Using the mpitest Program ................................................................................................. 7 1.2.3. Interconnect Configuration ................................................................................................ 8 2. Running a Distributed Job ................................................................................................................... 8 Configuring ANSYS CFX Parallel .................................................................................................................... 9 1. ANSYS CFX UNIX Parallel Setup ............................................................................................................ 9 1.1. Setting Up Remote Access on UNIX/Linux ................................................................................... 9 1.1.1. Testing Remote Access ....................................................................................................... 9 1.1.2. Global Set Up of rsh .......................................................................................................... 10 1.1.3. Individual User Set Up for rsh ........................................................................................... 10 1.1.4. Set Up of ssh .................................................................................................................... 10 1.2. hostinfo.ccl File ........................................................................................................................ 10 1.2.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility ...................................... 12 1.3. Using Platform MPI (Message Passing Interface Library) ............................................................. 13 1.3.1. Environment Variables ...................................................................................................... 14 1.3.2. Interconnect Selection ..................................................................................................... 14 2. ANSYS CFX Windows Parallel Setup .................................................................................................... 15 2.1. hostinfo.ccl file .......................................................................................................................... 15 2.1.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility ...................................... 17 2.2. Setting Up Platform MPI for Windows ........................................................................................ 18 2.2.1. Setting Up Distributed Parallel or Remote Access .............................................................. 18 2.2.2. Installing the Platform MPI Service and Registering Users on Windows Vista ...................... 19 2.2.3. Installing the Platform MPI Service and Registering Users on Windows XP ......................... 19 2.2.4. Enabling Parallel Through a Windows Firewall ................................................................... 20 2.3. Setting up and Running CCS 2003/HPC 2008 ............................................................................. 20
List of Tables
1. Products with Limited HPC Functionality ................................................................................................... 1 2. Platforms and MPI Software ....................................................................................................................... 2 3. LS-DYNA MPP MPI Support on Windows and Linux .................................................................................... 3
iii
iv
Configuring Distributed ANSYS

This section explains how to configure your network/cluster to run Distributed ANSYS. It is important that you follow these steps in order to run successfully in a distributed environment. For more information on using Distributed ANSYS, see the Parallel Processing Guide. You will need an ANSYS Mechanical HPC (HPC) license for each processor after the first two. For example, if you want to run four processors, you will need two HPC licenses. Some products cannot use all HPC functionality, as noted in the following table.
Table 1 Products with Limited HPC Functionality

Product ANSYS Academic Teaching Products ANSYS LS-DYNA ANSYS DesignSpace ANSYS Professional NLS Mechanical APDL Solver Distributed ANSYS Capability Yes No No No Yes SMP Capability 4 processors default limit No 2 processors max Yes Yes VT Accelerator Capability Yes No No Yes Yes
1. Setting up Distributed ANSYS

This section describes the prerequisites, including software requirements, for running Distributed ANSYS and the steps necessary to set up the environment for Distributed ANSYS.
1.1. Prerequisites for Running Distributed ANSYS

Whether you are running on a single machine or multiple machines, the following condition is true: Distributed ANSYS allows you to use two cores without using any HPC licenses. Additional licenses will be needed to run Distributed ANSYS with more than two cores. Several HPC license options are available. For more information, see HPC Licensing in the Parallel Processing Guide.
If you are running on a single machine, there are no additional requirements for running Distributed ANSYS. If you are running across multiple machines (e.g., a cluster), your system must meet these additional requirements to run Distributed ANSYS. Homogeneous network: All machines in the cluster must be the same type, OS level, chip set, and interconnects.
Configuring Distributed ANSYS You must be able to remotely log in to all machines, and all machines in the cluster must have identical directory structures (including the ANSYS installation, MPI installation, and on some systems, working directories). Do not change or rename directories after you've launched ANSYS. For more information on files that are written and their location, see Controlling Files that Distributed ANSYS Writes in the Parallel Processing Guide. All machines in the cluster must have ANSYS installed, or must have an NFS mount to the ANSYS installation. If not installed on a shared file system, ANSYS must be installed in the same directory path on all systems. All machines must have the same version of MPI software installed and running. The table below shows the MPI software and version level supported for each platform. For Linux platforms, the MPI software is included with the ANSYS installation. For Windows platforms, you must install the MPI software as described later in this document.
1.1.1. MPI Software

The MPI software supported by Distributed ANSYS depends on the platform. The following table lists the type of MPI software supported for each platform. Platform MPI and Intel MPI are included on the Linux installation media and are installed automatically when you install ANSYS. Instructions for installing the MPI software on Windows systems can be found later in this document (see Installing the Software). Distributed ANSYS runs on the following platforms: Intel IA-64 Linux (Platform MPI, SGI MPT) Intel Xeon EM64T 64-bit Linux (Platform MPI, Intel MPI) AMD Opteron 64-bit Linux (Platform MPI, Intel MPI) Windows 32-bit (Platform MPI, Intel MPI) Windows 64-bit (Platform MPI, MS MPI, Intel MPI) Windows HPC Server 2008 x64 (Microsoft HPC Pack (MS MPI))
Table 2 Platforms and MPI Software

Platform Linux, Intel IA-64 MPI Software Platform MPI 8.1.2 SGI MPT 1.14 (SuSE 10) SGI MPT 1.26 (SuSE 11) More Information Platform MPI: http://www.platform.com/cluster-computing/platform-mpi SGI MPT
Linux, Intel Xeon Platform MPI EM64T and AMD Opter- 8.1.2 Intel MPI on 64-bit 4.0.2
Platform MPI: http://www.platform.com/cluster-computing/platform-mpi Intel MPI: http://software.intel.com/en-us/articles/intel-mpi-library-documentation/ Platform MPI: http://www.platform.com/cluster-computing/platform-mpi Intel MPI: http://software.intel.com/en-us/articles/intel-mpi-library-documentation/
Windows 32-bit / Windows XP / Windows Vista / Windows 7 Windows 64-bit / Windows XP x64
Platform MPI 8.1.2 Intel MPI 4.0.1
Setting up Distributed ANSYS Platform / Windows Vista x64 / Windows 7 x64 Windows HPC Server 2008 x64 Microsoft HPC Pack (MS MPI) http://www.microsoft.com/hpc/ MPI Software More Information
ANSYS LS-DYNA If you are running ANSYS LS-DYNA, you can use LS-DYNA's parallel processing (MPP or SMP) capabilities. Use the launcher or the command line method as described in Activating Distributed ANSYS in the Parallel Processing Guide to run LS-DYNA MPP. For Windows and Linux systems, please see the following table for LS-DYNA MPP MPI support. For more information on using ANSYS LS-DYNA in general, and its parallel processing capabilities specifically, see the ANSYS LS-DYNA User's Guide.
Table 3 LS-DYNA MPP MPI Support on Windows and Linux

MPI version for DYNA MPP 32-bit Windows Platform MPI MS MPI n/a n/a 64-bit Windows X X 64-bit Linux X n/a
1.1.2. Installing the Software

To run Distributed ANSYS on a cluster, you must install ANSYS on all machines in the cluster, or have an NFS mount to the ANSYS installation. Install ANSYS following the instructions in the ANSYS, Inc. Installation Guide for your platform. Be sure to complete the installation, including all required post-installation procedures. On Windows systems, you must use the Universal Naming Convention (UNC) for all file and path names for Distributed ANSYS to work correctly.
Installing Platform MPI on Windows

You can install Platform MPI from the installation launcher by choosing Install MPI for ANSYS, Inc. Parallel Processing. On the following screen, choose to install Platform MPI. The Platform MPI installation program will start. A Platform MPI installation README file will open simultaneously. Follow the instructions in the README file as you complete the Platform MPI installation. The instructions for installing Platform MPI are also found in the ANSYS installation directory in the following README files: Program Files\Ansys Inc\V140\commonfiles\MPI\Platform\8.1.2\Windows\INSTALL_PLATFORM-MPI_README.mht or Program Files\Ansys Inc\V140\commonfiles\MPI\Platform\8.1.2\Windows\INSTALL_PLATFORM-MPI_README.doc
Installing Intel MPI on Windows

You can install Intel MPI from the Installation launcher by choosing Install MPI for ANSYS, Inc. Parallel Processing. On the following screen, choose to install Intel MPI. The Intel MPI installation program will start. An Intel MPI installation README file will open simultaneously. Follow the instructions in the README file as you complete the Intel MPI installation.
Configuring Distributed ANSYS The instructions for installing Intel MPI are also found in the ANSYS installation directory in the following README files: Program Files\Ansys Inc\V140\commonfiles\MPI\Intel\4.0.2\Windows\INSTALL_INTEL-MPI_README.mht or Program Files\Ansys Inc\V140\commonfiles\MPI\Intel\4.0.2\Windows\INSTALL_INTEL-MPI_README.doc
Microsoft HPC Pack (Windows HPC Server 2008)

You must complete certain post-installation steps before running Distributed ANSYS on a Microsoft HPC Server 2008 system. The post-installation instructions provided below assume that Microsoft HPC Server 2008 and Microsoft HPC Pack (which includes MS MPI) are already installed on your system. The post-installation instructions can be found in the following README files: Program Files\Ansys Inc\V140\commonfiles\MPI\MicrosoftHPC2008\README.mht or Program Files\Ansys Inc\V140\commonfiles\MPI\MicrosoftHPC2008\README.docx Microsoft HPC Pack examples are also located in Program Files\Ansys Inc\V140\commonfiles\MPI\MicrosoftHPC2008. Jobs are submitted to the Microsoft HPC Job Manager either from the command line or the Job Manager GUI. To submit a job via the GUI, go to Start> All Programs> Microsoft HPC Pack> HPC Job Manager. Then click on Create New Job from Description File.
1.2. Setting Up the Cluster Environment for Distributed ANSYS

After you've ensured that your cluster meets the prerequisites and you have ANSYS and the correct version of MPI installed, you need to configure your distributed environment using the following procedure. 1. Obtain the machine name for each machine on the cluster. Windows: Right-click on My Computer, left-click on Properties, and select the Network Identification or Computer Name tab. The full computer name will be listed. Note the name of each machine (not including the domain). Linux: Type hostname on each machine in the cluster. Note the name of each machine. You will need this name to set up the .rhosts file, as well as for the ANS_ADMIN utility. 2. Linux only: Set up the .rhosts file on each machine. The .rhosts file lists all machines in the cluster. The machines should be listed using their complete system name, as taken from hostname. For example, an .rhosts file for a two-machine cluster might look like this:
golinux1.ansys.com jqd golinux2 jqd
Change/verify .rhosts file permissions on all machines by issuing: 4

Setting up Distributed ANSYS

chmod 600 .rhosts
Verify communication between machines via rsh or ssh (e.g., rsh golinux2 ls). You should not be prompted for a password. If you are, check the .rhosts permissions and machine names for correctness. For more information on using remote shells, see the man pages for rsh or ssh. 3. If you want the list of machines to be populated in the Mechanical APDL Product Launcher, you need to configure the hosts140.ans file. You can use the ANS_ADMIN utility to configure this file. You can manually modify the file later, but we strongly recommend that you use ANS_ADMIN to create this file initially to ensure that you establish the correct format. Windows: Start >Programs >ANSYS 14.0 >Utilities >ANS_ADMIN 14.0 Choose Configuration options, and then Configure Cluster to configure the hosts140.ans file. 1. Specify the directory in which the hosts140.ans will be configured: Select the Configure a hosts140.ans file in a directory you specify option and click OK. Enter a working directory. Click OK. Enter the system name (from Step 1) in the Machine hostname field and click Add. On the next dialog box, enter the system type in the Machine type drop-down, and the number of processors in the Max number of jobs/processors field and click OK for each machine in the cluster. When you are finished adding machines, click Close, then Exit. An example hosts140.ans file where machine1 has 2 processors and machine2 has 4 processors would look like this:
machine1 intel 0 2 0 0 MPI 1 1 machine2 intel 0 4 0 0 MPI 1 1
2.
Linux: /ansys_inc/v140/ansys/bin/ans_admin140 Choose ANSYS/Workbench Configuration, and then click Configure Cluster. Under Select file to configure, choose the hosts140.ans file to be configured and choose Configure for Distributed ANSYS. Click OK. Then enter the system name (from Step 1) in the Machine hostname field and click Add. On the next dialog box, enter the system type in the Machine type dropdown, and the number of processors in the Max number of jobs/processors field for each machine in the cluster. Click Add. When you are finished adding machines, click Close. The hosts140.ans should be located in your current working directory, your home directory, or the apdl directory. 4. Windows only: Setting up environment variables. On the head node, where ANSYS and ANSYS Licensing is installed, set the following: ANSYS140_DIR=C:\Program Files\ANSYS Inc\v140\ansys ANSYSLIC_DIR=C:\Program Files\ANSYS Inc\Shared Files\Licensing where C:\Program Files\ANSYS Inc is the location of the product install. If your installation location is different than this, specify it instead.
Configuring Distributed ANSYS On Windows systems, you must use the Universal Naming Convention (UNC) for all ANSYS environment variables on the compute nodes for Distributed ANSYS to work correctly. On the compute nodes, set the following: ANSYS140_DIR=\\head_node_machine_name\ANSYS Inc\v140\ansys ANSYSLIC_DIR=\\head_node_machine_name\ANSYS Inc\Shared Files\Licensing For Distributed LS-DYNA: On the head node and the compute nodes, set LSTC_LICENSE to ANSYS. This tells the LS-DYNA executable to use ANSYS licensing. Since the LS-DYNA run will use ANSYS licensing for LS-DYNA, you do not need to set LSTC_LICENSE_SERVER. 5. Windows only: Share out the ANSYS Inc directory on the head node with full permissions so that the compute nodes can access it.
1.2.1. Optional Setup Tasks

The tasks explained in this section are optional. They are not required to get Distributed ANSYS to run correctly, but they may be useful for achieving the most usability and efficiency, depending on your system configuration. On Linux systems, you can also set the following environment variables: ANSYS_NETWORK_START - This is the time, in seconds, to wait before timing out on the start-up of the client (default is 15 seconds). ANSYS_NETWORK_COMM - This is the time to wait, in seconds, before timing out while communicating with the client machine (default is 5 seconds). ANS_SEE_RUN_COMMAND - Set this ANSYS environment variable to 1 to display the actual mpirun command issued from ANSYS.
On Linux systems running Platform MPI: MPI_REMSH - This is the path to the remote shell (ssh or rsh). Set this environment variable to specify a full path to a remote shell. For example, setting MPI_REMSH = /usr/bin/ssh will use ssh instead of the default remote shell (rsh). Note that selecting the Use Secure Shell instead of Remote Shell option on the launcher will override MPI_REMSH, if MPI_REMSH is not set or is set to a different location. You can also issue the - usessh command line option to use ssh instead of rsh. The command line option will override the environment variable setting as well. MPI_WORKDIR - Set this environment variable to specify a working directory on either the master and all nodes, or on specific nodes individually. For more information, see Controlling Files that Distributed ANSYS Writes. MPI_IC_ORDER - Set this environment variable to specify the order in which the interconnects on the system are to be used. The interconnects will be tried in the order listed from left to right. If an interconnect is listed in uppercase, no interconnects listed after that one will be tried. If MPI_IC_ORDER is not set, the fastest interconnect available on the system is used. See the Platform MPI documentation for more details. MPI_ICLIB_<interconnect> - Set this environment variable to the interconnect location if the interconnect is not installed in the default location:
Setting up Distributed ANSYS

setenv MPI_ICLIB_GM <path>/lib64/libgm.so
See the Platform MPI documentation for the specific interconnect names (e.g., MPI_ICLIB_GM). MPIRUN_OPTIONS - Set this environment variable to -prot to display a grid of interconnects among the systems being used for distributed processing.
On Linux systems running Intel MPI: Issue the command line option -usessh to use ssh instead of rsh. See the Intel MPI reference manual (for Linux) for further information and additional environment variables and their settings: http://software.intel.com/en-us/articles/intel-mpi-library-documentation/.
To verify that these environment variables are set correctly on each machine, run:
rsh machine1 env
On Windows systems, you can set the following environment variables to display the actual mpirun command issued from ANSYS: ANS_SEE_RUN = TRUE ANS_CMD_NODIAG = TRUE
1.2.2. Using the mpitest Program

The mpitest program performs a simple communication test to verify that the MPI software is set up correctly. The mpitest program should start without errors. If it does not, check your paths, .rhosts file, and permissions; correct any errors, and rerun. When running the mpitest program, you must use an even number of nodes. On Linux: For Platform MPI (default), issue the following command:
mpitest140 -machines machine1:2
For Intel MPI, issue the following command:

mpitest140 -mpi intelmpi -machines machine1:2
You can use any of the same command line arguments (such as -machines) with the mpitest program as you can with Distributed ANSYS. On Windows: Issue the following command to run a local test on Windows using Platform MPI:
ansys140 -np 2 -mpitest
Use the following procedure to run a distributed test on Windows using Platform MPI: 1. 2. Create a file named machines in your local/home directory. Open the machines file in an editor. Add your master and slave machines in your cluster. For example, in this cluster of two machines, the master machine is gowindows1. List the machine name separately for each core on that machine. For example, if gowindows1 has four processors and gowindows2 has two, the machines file would look like this:
Configuring Distributed ANSYS gowindows1 gowindows1 gowindows1 gowindows1 gowindows2 gowindows2 3. From a command prompt, navigate to your working directory. Run the following:
ansys140 -mpifile machines -mpitest
1.2.3. Interconnect Configuration

Low-end hardware, such as slow interconnects, will reduce the speed improvements you see in a distributed analysis. For optimal performance, we typically recommend that you use an interconnect with a communication speed of 1000 megabytes/second or higher. Distributed ANSYS supports the following interconnects. Not all interconnects are available on all platforms; see http://www.ansys.com/services/ss-platform-support.asp for a current list of supported interconnects. Other interconnects may work but have not been tested. InfiniBand (recommended) Myrinet GigE Ethernet (not recommended)
Interconnects plug into a PCI (Peripheral Component Interconnect), PCI-X (extended), or PCIe (PCI Express) slot on the system. You will need a PCI-X or a PCIe slot for the faster interconnects to accommodate the higher speeds. Hardware for specific types of interconnects is generally incompatible with other proprietary interconnect types (except Ethernet and GiGE). Systems can have a network of several different types of interconnects. Each interconnect must be assigned a unique hostname and IP address. On Windows x64 systems, use the Network Wizard in the Compute Cluster Administrator to configure your interconnects. See the Compute Cluster Pack documentation for specific details on setting up the interconnects. You may need to ensure that Windows Firewall is disabled for Distributed ANSYS to work correctly.
2. Running a Distributed Job

For information on running Distributed ANSYS after you have your environment configured, see the Parallel Processing Guide.
Configuring ANSYS CFX Parallel

If you have purchased the ANSYS CFX-Solver parallel option, you will need to follow the procedures in this chapter to ensure that users can execute ANSYS CFX jobs in parallel. Several parallel communication methods are available that use either PVM (Parallel Virtual Machine) or MPI (Message Passing Interface). Platform-specific versions of MPI are available in some instances. The ANSYS CFX-Solver parallel option is supported on all platforms that support the CFX-Solver.
1. ANSYS CFX UNIX Parallel Setup

The following are required in order for you to execute ANSYS CFX parallel: The ANSYS CFX-Solver must be installed on both master and slave nodes. To run distributed parallel (where slave processes run on a different host to the master process), remote or secure shell access must be available from the master nodes (systems on which parallel runs will be started) to slave nodes (systems on which the ANSYS CFX-Solver will actually run). See Setting Up Remote Access on UNIX/Linux (p. 9), below. You must have the same user name on all systems. The hostinfo.ccl file should be set up, as described in hostinfo.ccl File (p. 10).
1.1. Setting Up Remote Access on UNIX/Linux

Each system that will be used as a slave node must be configured to allow access via remote shell commands from the master node. This can be done globally for all users or on a per-user basis. Often, networks where rlogin and rsh or ssh are used frequently will already be configured to allow remote access to all users. If this is the case, nothing more needs to be done. The CFX5RSH environment variable is used to select either ssh or rsh access. The default is rsh. If you want to use ssh, then set "CFX5RSH=ssh" either in the environment or in the cfx5rc file (see Resources Set in cfx5rc Files in the CFX Introduction). In either case, rsh or ssh, the remote machine must not prompt for a password when you run remote commands.
1.1.1. Testing Remote Access

You can test remote access using rsh for a UNIX/Linux slave node using the command:
rsh unixhost echo working
Note
On systems running HP-UX, use "remsh" instead of "rsh". You can test remote access using ssh using the command:

ssh unixhost echo working
1.1.2. Global Set Up of rsh

This method, which is used to allow remote access for all users, depends on whether NIS is used to maintain netgroups, as well as common password and group databases. If this is not the case, then you should log in to each slave node as root and create a file called /etc/hosts.equiv containing a line:
<master>
where <master> is the hostname of the master node. See your system documentation for more information about the use of rsh and the syntax of the hosts.equiv file. If NIS is used to control remote access, then a netgroup must be created for users of ANSYS CFX by the root user on the NIS master server, and a line such as the one below added to /etc/hosts.equiv on each slave node by the root user:
+@<netgroup>
where <netgroup> is the name of a netgroup to which users of ANSYS CFX belong. A detailed description of how to configure NIS is beyond the scope of this manual. Please see your system documentation for more information about NIS.
1.1.3. Individual User Set Up for rsh

Individual users can create a file called .rhosts in their home directory on each slave containing a line:
<master> <user>
where <master> is the hostname of the master and <user> is their username on the master. This file should be made readable only by the user, for example, by running:
chmod 600 ~/.rhosts
1.1.4. Set Up of ssh

If you use ssh for remote access, please consult your system documentation on how to set up ssh between machines so that it does not require the user to enter a password.
1.2. hostinfo.ccl File

In order to use the Distributed Parallel mode of ANSYS CFX, the file hostinfo.ccl must exist in the <CFXROOT>/config/ directory of the ANSYS CFX installation on the master node and be made readable by all users of the software. This file is a database containing information about the available hosts and where ANSYS CFX has been installed on each of them. The file is used by the ANSYS CFXSolver when constructing a parallel run. This file is written using the CFX Command Language. It defines a set of HOST DEFINITION objects, one for each available node. For example:
SIMULATION CONTROL: EXECUTION CONTROL: PARALLEL HOST LIBRARY: HOST DEFINITION: kangaroo Installation Root = /ansys_inc/v%v/CFX END
10
ANSYS CFX UNIX Parallel Setup

HOST DEFINITION:wallaby Installation Root = /usr/local/cfx Host Architecture String = linux-amd64 Number of Processors = 16 Relative Speed = 1.7 END HOST DEFINITION: mypc Remote Host Name = my_pc END END END END
Note
The SIMULATION CONTROL...END wrapper is a requirement for Release 12.0 and later. If you manually create your hostinfo.ccl file, you must ensure that this wrapper is present. None of the values for each host are mandatory, and the following empty host definition is perfectly valid:
HOST DEFINITION: parakeet END
Host names are limited to the set of valid CCL object names. In particular, they must not contain full stops (.) or underscores (_) and must start with a letter. If a hostinfo.ccl file does not already exist when ANSYS CFX is installed, one will be created containing the installation host. You can add hosts to the hostinfo.ccl file using the cfx5parhosts utility, or by modifying the file using a text editor. Individual users may also create their own versions of this file in:
~/.hostinfo.ccl
which will be used in preference if it exists. For most installations, it will be necessary to supply only the Installation Root parameter, which should point to the <CFXROOT> directory in which ANSYS CFX is installed. On mixed networks, you may find it useful to supply the Number of Processors and/or Relative Speed parameters. A little time may be saved at startup by giving the Host Architecture String parameter explicitly, for example, using the cfx5parhosts utility.
Tip
If an individual user wants to use a host that is not present in either the hostinfo.ccl in the installation config directory or the user's own version of this file, then the user can add this host to the list for a particular run by using the CFX-Solver Manager. However, this would have to be done each time a run is started. The available parameters for the hostinfo.ccl file are as follows: Installation Root This is set to the <CFXROOT> installation directory on this host. If it is set to the special string none, this indicates that there is no ANSYS CFX installation on the remote host, which can sometimes be useful if only the solver binary is available.
11
Configuring ANSYS CFX Parallel Host Architecture String ANSYS CFX will use this value to select the most appropriate solver executable for this node. These strings can be obtained by giving the command <CFXROOT>/bin/cfx5info -os on the node in question. When these short os values (for example, linux-amd64) are given in this position, the generic solver executable will always be used for this host. The string can also be set to the actual architecture of the remote host (for example, intel_xeon64.sse2_linux2.3.4), which is determined by giving the command <CFXROOT>/bin/cfx5info -arch. If these longer strings are used then CFX could use this information to select between solvers optimized for specific architectures. However, since there are currently no solvers optimized for specific architectures, this extra information is currently unused. Number of Processors As implied, this is the number of processors on the machine. It is used for display purposes only and can be safely omitted. Relative Speed The Relative Speed is a real number that is used by the ANSYS CFX-Solver when partition sizes are calculated. The ratio of relative speeds of each host is used to determine the size of each partition. As an example, consider a parallel run involving two machines, one with a relative speed of 2.0 and the other with a relative speed of 1.0. The faster machine would work on a partition size twice as large as the slower machine in this case. The numbers themselves are arbitrary; as a guide you may wish to set 1.0 for a 1GHz processor, 0.75 for a 750 MHz processor, and so on. If a relative speed entry is not entered, a default of 1.0 is assumed for that host. You can obtain relative speed values using the cfx5parhosts utility. Remote Host Name To include hosts in the parallel run with names that contain, for example, underscore characters, you can add the Remote Host Name parameter to the HOST DEFINITION with the correct network name for the host and use a readable alias as the name of the object. Solver Executable A solver executable may be explicitly supplied, if necessary. This is usually only required when using Installation Root = none, and is recommended for advanced users only. The following substitutions are made on the string: %r %p %v %o %a root directory of the installation parallel suffix for the executable version of ANSYS CFX being run operating system string architecture subdirectory specification; for example, linux/double
If it is not supplied, this parameter has the default value %r/bin/%a/solver%p.exe
1.2.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility
You can add new hosts to ANSYS CFX's database for parallel runs using the cfx5parhosts utility:
CFXROOT\bin\cfx5parhosts argument list
where argument list corresponds to one or more of the arguments listed below:
12
ANSYS CFX UNIX Parallel Setup Argument -add host[,host,...] Description Add information about the named hosts to the file. This assumes that ANSYS CFX is installed in the same directory on each listed host as on the host on which you are running. host may be specified as [user@]hostname[:cfx-5 root] if the user name or the ANSYS CFX installation root directory differs from the local host. -benchmark Runs a standard benchmark case, and fills in the Relative Speed for the local host. The benchmark case will usually take less than 5 minutes to run. Use the specified file as the hostinfo.ccl file. Merge host information from the named file. After modifying the file, write back the information available without attempting to fill in any missing pieces. Used with -update. Normally, hosts which exist on the network but cannot be connected to with rsh or ssh are included in the resulting file with a comment. This switch will exclude these hosts. Use the system host file.This is the default. Updates the specified host information file. If any hosts do not have an architecture specified in the existing hostinfo.ccl file (for example, because it was added via the -add switch), it will connect to the host and query it to fill in the Host Architecture String parameter.This is the default behavior. Note that if the Installation Root parameter is incorrect for the host, it will use the standard system commands to guess a generic architecture string.This can happen if you use -add to include a host with a different installation directory than the local one. Use the per-user host file.
-file file -merge file -no-update -strict
-system -update
-user
1.3. Using Platform MPI (Message Passing Interface Library)

Most UNIX/Linux systems support three parallel run modes: PVM, MPICH, and Platform MPI. Platform MPI is the preferred parallel run mode on all the supported ANSYS CFX platforms. Platform MPI supports several communication modes including shared memory and networked TCP/IP (Ethernet), luDAPL, VAPI, OpenFabrics (IB), GM-2, MX (Myrinet), Elan4 (Quadrics), QLogic InfiniPath, and EtherFabric (Level 5 Networks). Platform MPI is automatically installed with ANSYS CFX in the <CFXROOT>/tools directory. You do not need a license from Platform to run the ANSYS CFX-Solver using Platform MPI. If there is no CFX installation on any slave node, you must ensure that Platform MPI is manually installed on any such node. Platform MPI run modes are selected in the ANSYS CFX-Solver Manager or on the command line (using the -start-method command line option) using the Platform MPI Local Parallel or Platform MPI Distributed Parallel start method options. For Platform MPI, the cpu_bind option is used by default and binds processes to cores using a cyclic order. This leads to better performance but, on multi-user clusters having scheduling systems that do not enforce exclusive use of cluster nodes, may cause problems because multiple jobs may be bound
13
Configuring ANSYS CFX Parallel to the same CPU on the same node. In this case, the cpu_bind argument to mpirun should be removed from the Platform MPI start methods in the <CFXROOT>/etc/start_methods.ccl file.
1.3.1. Environment Variables

ANSYS CFX uses the environment variable CFX5_PCMPI_DIR to select which Platform MPI installation is used. The default setting points to the version installed by ANSYS CFX in the <CFXROOT>/../commonfiles/MPI/Platform directory. If you want to use a different Platform MPI version than what is installed then you can install that version in an alternative location and set CFX5_PCMPI_DIR to that location instead of the default. There are several environment variables that can be used to control Platform MPI (documented in the Platform MPI documentation) that may provide additional flexibility not directly accessible through the ANSYS CFX startup scripts. If these environment variables are set the startup scripts automatically set them for your CFX runs. Some useful environment variables include: MPI_REMSH Enables you to change which method is used by Platform MPI to spawn jobs on remote machines. The Platform MPI default is ssh. However, by default the CFX software sets this to be the same as the setting used for CFX5RSH, and rsh if CFX5RSH is not set. This variable is applicable only to Linux and HP-UX. MPI_IC_ORDER Enables you to change the default order in which Platform MPI searches for interconnects. See the next section.
1.3.2. Interconnect Selection

Platform MPI start methods use the default communication mode selection built into Platform MPI. The default order in which Platform MPI checks for interconnects is OpenFabric, VAPI, UDAPL, ITAPI, PSM, Myrinet MX, Myrinet GM, Elan, TCP/IP. If you want to force selection of a specific device, then you can either modify the start command in the etc/start-methods.ccl file and add the necessary command line flags (for example: -GM to force selection of the Myrinet interconnect) or use the appropriate Platform MPI environment variables. Some useful command line options include forcing other interconnect types (-TCP, -HMP, -ELAN, -ITAPI, -VAPI, -UDAPL, and so on), using prun on systems with quadrics support (-prun), XC support (-srun) and setting the subnet you want to use (-subnet, sometimes useful for selecting particular interconnects as well if your system is configured that way). For some Linux-based cluster environments not supported by Platform MPI, it is possible that the Myrinet, Infiniband or Quadrics hardware drivers are not located where Platform MPI expects. If Platform MPI cannot detect the drivers for fast interconnects, it will generally default back to the lowest speed connection that it can detect (usually TCP/IP socket communication). The following table gives information on the default search path Platform MPI uses to find drivers for the various communication interfaces: Interconnect Infiniband (IB) Myrinet (GM) 1st attempt Environment variable MPI_ICLIB_ITAPI Environment variable MPI_ICLIB_GM 2nd attempt libitapi.so libgm.so OR libgm32.so 3rd attempt /usr/voltaire/lib/libitapi.so /opt/gm/lib/libgm.so OR /opt/gm/lib/libgm32.so
14
ANSYS CFX Windows Parallel Setup Interconnect ELAN UDAPL VAPI Infinipath 1st attempt Environment variable MPI_ICLIB_ELAN Environment variable MPI_ICLIB_UDAPL Environment variable MPI_ICLIB_VAPI Environment variable MPI_ICLIB_PSM 2nd attempt libelan.so libdat.so Environment variable MPI_ICLIB_VAPIDIR libpsm_infinipath.so.1 3rd attempt none none libmtl_common.so, libmpga.so, libmosal.so, libvapi.so /usr/lib64/ libpsm_infinipath.so.1
For example, Platform MPI expects that GM stack shared libraries for Myrinet interconnects are located either in the default library search path or in the /opt/gm/lib (32 bit x86) or /opt/gm/lib64 (64 bit x86) directories. If the shared libraries are not in either location, Platform MPI will not take advantage of the high-speed interconnects. To fix this, you will have to copy the shared libraries into the correct location or set the environment variable MPI_ICLIB_GM to point to the correct GM stack shared library.
2. ANSYS CFX Windows Parallel Setup

The following are required in order for you to use ANSYS CFX in parallel on Windows platforms: ANSYS CFX-Solver must be installed on all nodes to be used for a parallel run. To run distributed parallel (where slave processes run on hosts other than the host with the master process), you must either configure the parallel host setup properly or set up remote access to slave nodes. You must have the same user name on all systems. To run distributed parallel, you must install and configure the Platform MPI service and register your user name on all nodes involved in the parallel run. (See Installing the Platform MPI Service and Registering Users on Windows Vista (p. 19).) You must register your user name each time your password changes.
2.1. hostinfo.ccl file

In order to use the Distributed Parallel modes effectively, the file hostinfo.ccl must exist in the <CFXROOT>/config/ directory of the ANSYS CFX installation on the master node and be made readable by all users of the software. This file is a database containing information about the available nodes and where ANSYS CFX has been installed on each of them. The file is used by the ANSYS CFXSolver when constructing a parallel run. The hostinfo.ccl file is written using the CFX Command Language. It defines a set of HOST DEFINITION objects, one for each available node. For example:
SIMULATION CONTROL: EXECUTION CONTROL: PARALLEL HOST LIBRARY: HOST DEFINITION: hostname1 Installation Root = C:\Program Files\ANSYS Inc\v%v\CFX Host Architecture String = winnt-amd64 END # HOST DEFINITION hostname1 END # PARALLEL HOST LIBRARY END # EXECUTION CONTROL END # SIMULATION CONTROL
15
Note
The SIMULATION CONTROL...END wrapper is a requirement for Release 12.0 and later. If you manually create your hostinfo.ccl file, you must ensure that this wrapper is present. None of the values for each host are mandatory. For example, the following empty host definition is perfectly valid:
HOST DEFINITION: parakeet END
Host names are limited to the set of valid CCL object names. In particular, they must not contain full stops (.) or underscores (_) and must start with a letter. If a hostinfo.ccl file does not already exist when ANSYS CFX is installed, one will be created containing the installation host. You can add hosts to the hostinfo.ccl file using the cfx5parhosts utility, or by modifying the file using a text editor. For most installations, it will be necessary only to supply the Installation Root parameter, which should point to the <CFXROOT> directory in which ANSYS CFX is installed. On mixed networks, you may find it useful to supply the Number of Processors and/or Relative Speed parameters. A little time may be saved at startup by giving the Host Architecture String parameter explicitly, for example, using the cfx5parhosts utility. The available parameters are as follows: Installation Root This is set to the <CFXROOT> installation directory on this host. If it is set to the special string none, this indicates that there is no ANSYS CFX installation on the remote host, which can sometimes be useful if only the solver binary is available. Host Architecture String This should be set to the actual architecture <arch> of the remote host. ANSYS CFX will use this value to select the most appropriate solver executable for this node. These strings can be obtained by giving the command <CFXROOT>/bin/cfx5info -os on the node in question. If the shorter <os> values (for example, solaris) are given in this position, the generic solver executable will always be used for this host. Number of Processors As implied, this is the number of processors on the machine. It is used for display purposes only and can be safely omitted. Relative Speed The Relative Speed is a real number that is used by the ANSYS CFX-Solver when partition sizes are calculated. The ratio of relative speeds of each host is used to determine the size of each partition. As an example, consider a parallel run involving two machines, one with a relative speed of 2.0 and the other with a relative speed of 1.0. The faster machine would work on a partition size twice as large as the slower machine in this case. The numbers themselves are arbitrary; as a guide you may want to set 1.0 for a 1GHz processor, 0.75 for a 750 MHz processor, and so on. If a relative speed entry is not entered, a default of 1.0 is assumed for that host. You can obtain relative speed values using the cfx5parhosts utility.
16
ANSYS CFX Windows Parallel Setup Remote Host Name To include hosts in the parallel run with names that contain, for example, underscore characters, you can add the Remote Host Name parameter to the HOST DEFINITION with the correct network name for the host and use a readable alias as the name of the object. Solver Executable A solver executable may be explicitly supplied, if necessary. This is usually only required when using Installation Root = none, and is recommended for advanced users only. The following substitutions are made on the string: %r %p %v %o %a root directory of the installation parallel suffix for the executable version of ANSYS CFX being run operating system string architecture subdirectory specification, for example, linux/double
If it is not supplied, this parameter has the default value %r/bin/%a/solver%p.exe
2.1.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility
You can add new hosts to ANSYS CFX's database for parallel runs using the cfx5parhosts utility; this is done by running:
CFXROOT\bin\cfx5parhosts argument list
where argument list corresponds to one or more of the arguments listed below. On Windows Vista, cfx5parhosts must be run with administrator privileges. This is because the hostinfo.ccl file, like all files in Program Files, requires administrative privileges to edit. Argument -add host[,host,...] Description Add information about the named host(s) to the file. This assumes that ANSYS CFX is installed in the same directory on each listed host as on the host on which you are running. host may be specified as [user@]hostname[:cfx-5 root] if the user name or the ANSYS CFX installation root directory differs from the local host. To add a set of separately-installed Windows hosts to the hostinfo.ccl file, where the installation may be in a different place on each host, the recommended method is to gather the hostinfo.ccl files created on each host by the installation process, and merge them together using the -merge switch. -benchmark -file file -merge file -no-update Runs a standard benchmark case, and fills in the Relative Speed for the local host. The benchmark case will usually take less than 5 minutes to run. Use the specified file as the hostinfo.ccl file. Merge host information from the named file. After modifying the file, write back the information available without attempting to fill in any missing pieces.
17
Configuring ANSYS CFX Parallel Argument -strict Description Used with -update. Normally, hosts which exist on the network but cannot be connected to with rsh or ssh are included in the resulting file with a comment. This switch will exclude these hosts. Use the system host file.This is the default. Updates the specified host information file. If any hosts do not have an architecture specified in the existing hostinfo.ccl file (for example, because it was added via the -add switch), it will connect to the host and query it to fill in the Host Architecture String parameter.This is the default behavior. Note that if the Installation Root parameter is incorrect for the host, it will use the standard system commands to guess a generic architecture string.This can happen if you use -add to include a host with a different installation directory than the local one. Use the per-user host file.
-system -update
-user
2.2. Setting Up Platform MPI for Windows

Platform MPI requires that you must either configure the parallel host setup properly or set up remote access to slave nodes. See Setting Up Distributed Parallel or Remote Access (p. 18) for details. In addition, Platform MPI has other requirements as follows.
Note
All nodes must be on the same domain and the user must have an account for that domain. The Platform MPI service is required only for distributed parallel runs. Platform MPI uses the cpu_bind option by default and binds processes to cores using a cyclic order. This leads to better performance but, on multi-user clusters having scheduling systems that do not enforce exclusive use of cluster nodes, may cause problems because multiple jobs may be bound to the same CPU on the same node. In this case, the cpu_bind argument to mpirun should be removed from the Platform MPI start methods in the start_methods.ccl file in the <CFXROOT>/etc directory.
2.2.1. Setting Up Distributed Parallel or Remote Access

When the ANSYS CFX distributed parallel starts, it needs to know where to find the CFX-Solver executable on every host and which solver executable it should run (for example, 64-bit or 32-bit). This can be set up in two ways: (Preferred method) Explicitly specify the required information: 1. Ensure that every host used in the distributed parallel run is included in the hostinfo.ccl file, including the Installation Root and Host Architecture String parameters for each host. See hostinfo.ccl file (p. 15) for details on how to set this up. Set the environment variable CFX_SOLVE_DISABLE_REMOTE_CHECKS in your user or site cfx5rc.txt file. See Resources Set in cfx5rc Files in the CFX Introduction for details.
2.
Have ANSYS CFX determine the required information for itself.
18
ANSYS CFX Windows Parallel Setup If ANSYS CFX is to determine the required information for itself, then remote- or secure-shell access must be available from the master node (the system on which parallel runs will be started) to slave nodes (systems on which the ANSYS CFX-Solver will actually run). You must be able to execute an rsh or ssh command on the remote host without typing in your password. Unless you already have your Windows systems set up to allow this type of access, this method of setting up distributed parallel is not recommended.
2.2.2. Installing the Platform MPI Service and Registering Users on Windows Vista
On Windows Vista, you must start a command window and install the Platform MPI service as Administrator: 1. 2. From Explorer, right-click C:\WINDOWS\system32\cmd.exe and select Run As. In the Run As dialog, select The following user and login as Administrator. Enter the username and password information. 3. The username should be entered in full (for example DOMAIN\user). The password information is encrypted and added to the registry.
If necessary, change to the disk drive that has the ANSYS software installed. For example, to change to the C drive, enter:
C:
4.
Run the Platform MPI Service installation with Administrator privileges:

"<install_dir>\v140\CFX\bin\cfx5parallel" -install-pcmpi-service
A message appears in the terminal when the installation is complete. On the master host, details of a user with access to all of the hosts in the run must now be set. The username and password information is used during the run to access the hosts. 5. Start the service; enter:
"<install_dir>\v140\CFX\bin\cfx5parallel" -start-pcmpi-service
If you need to change the port number used by the service, you can run a command of the following form:
"<install_dir>\v140\CFX\bin\cfx5parallel" -setportkey-pcmpi-service <port number>
For details on the cfx5parallel utility, enter "<install_dir>\v&ansys_version;\CFX\bin\cfx5parallel" -help at the command prompt.
2.2.3. Installing the Platform MPI Service and Registering Users on Windows XP
As a user with administrative privileges: 1. 2. From the launcher, select Tools > Command Line. Enter:
cfx5parallel -install-pcmpi-service
A message appears in the terminal when the installation is complete. On the master host, details of a user with access to all of the hosts in the run must now be set. The username and password information is used during the run to access the hosts.
19
Configuring ANSYS CFX Parallel 3. Enter your username and password information. 4. If prompted, the username should be entered in full (for example DOMAIN\user). The password information is encrypted and added to the registry.
From the command line invoked from the launcher, enter:

cfx5parallel -start-pcmpi-service
If you need to change the port number used by the service, you can run a command of the following form:
cfx5parallel -setportkey-pcmpi-service <port number>
For details on the cfx5parallel utility, enter cfx5parallel -help at the command prompt.
2.2.4. Enabling Parallel Through a Windows Firewall

To enable Parallel Processing through a Windows firewall: 1. 2. 3. 4. 5. Click on Start and select Control Panel. On the Control Panel dialog, double-click Security Center. Click Windows Firewall. On the Windows Firewall dialog, click the Exceptions tab and then click Add Program. Browse to the following programs: For Platform MPI: <CFXROOT>\bin\<CFX5OS>\solver-pcmpi.exe <CFXROOT>\bin\<CFX5OS>\double\solver-pcmpi.exe <CFXROOT>\..\commonfiles\MPI\Platform\8.1\<winx64|win32>\sbin\pcmpiwin32service.exe <CFXROOT>\..\commonfiles\MPI\Platform\8.1\<winx64|win32>\bin\mpirun.exe <CFXROOT>\..\commonfiles\MPI\Platform\8.1\<winx64|win32>\bin\mpid.exe
After each selection, click OK to add that program to the list of programs that are permitted to pass through the Windows firewall. 6. When you are finished, click OK to close the Windows Firewall dialog, then close the Windows Security Center and the Control Panel.
2.3. Setting up and Running CCS 2003/HPC 2008

To set up running CCS 2003/HPC2008 steps must be taken so that: The installed software is on a shared location that can be accessed by all hosts The working directory is a shared location A mechanism is provided so that all local paths can be properly resolved.
For running ANSYS CFX with CCS 2003/HPC 2008, this can be accomplished by following the steps below (terms in angle brackets < > should be replaced with the required entry): 1. 20 Install ANSYS Licensing, ANSYS Workbench and ANSYS CFX on the head node.
ANSYS CFX Windows Parallel Setup 2. Share the installation directory. For example, on a typical installation share C:\Program Files\ANSYS Inc as \\<HeadNodeName>\ANSYS Inc where <HeadNodeName> is the name of the head node. Install the ANSYS prerequisites on all of the cluster nodes. You can do this either by: Executing the following commands directly on each node:
\\<HeadNodeName>\ANSYS Inc\v140\prereq\vcredist_x64_SP1.exe \\<HeadNodeName>\ANSYS Inc\v140\prereq\vcredist_x86_SP1.exe \\<HeadNodeName>\ANSYS Inc\v140\prereq\2008vcredist_x64.exe /qn
3.
or by using theclusrun command on the headnode to execute these commands on all the nodes (refer to your Windows CCS or HPC documentation for details).
4.
Share the working directory on the head node. For example, share C:\Users\<UserName> as \\<HeadNodeName>\<UserName> where <UserName> is the user name. Alternatively, share the working directory of the submitting machine. For example share C:\Users\<UserName> on the submitting machine as \\<SubmitHostName>\<UserName> where <SubmitHostName> is the name of the submitting machine.
5.
If the submitting machine is different from the server head node, it is necessary to install HPC Pack 2008 R2 Client Utilities on the submitting machine. This is available for download from Microsoft. This sets the CCP_HOME environment variable, enabling the Submit to Windows CCS or HPC Queue start method in the CFX-Solver Manager. On the submitting machine, create %USERPROFILE%\.cfx\cfxccs_options.txt with the following content to define the required CCS options: PATHMAP=C:\Program Files\Ansys Inc;\\<HeadNodeName>\Ansys Inc PATHMAP= C:\Users\<UserName>;\\<HeadNodeName>\<UserName> or PATHMAP=C:\Users\<UserName>;\\<SubmitHostName>\<UserName> if the working directory has been shared from the submitting machine. CLUSTERHOST=<HeadNodeName> to be used when submitting jobs from machines other than the headnode. ACCOUNT=<OtherUserDomain>\<OtherUserName> to be used when submitting jobs using different credentials, where <OtherUserDomain> and <OtherUserName> are the domain and user names of another user, respectively. PROCESSORSPERSOLVER=2 an optional setting (default setting is 1) that allocates the number of cores per partition. This is typically used on hosts that are limited by memory bandwidth such as Xeon-based machines.
6.
7.
Set up ANSYS Workbench for a network as described in Network Installation and Product Configuration (p. 22).
To submit a job: 1. 2. 3. Start the CFX-Solver Manager (either using CFX standalone or from ANSYS Workbench) on the submitting machine using the software installed on the headnode. Ensure that the Run Mode on the Run Definition tab of the CFX-Solver Manager is set to Submit to Windows CCS or HPC Queue. Otherwise, set up the CFX-Solver Manager as normal. Click Start Run on the CFX-Solver Manager to start the simulation. The first time a simulation is run, supply the required credentials that are prompted (this prompt may appear behind the CFX-Solver Manager window). You may elect to have these credentials saved to avoid repeated prompting of these credentials.
21
Note
1. For simulations making use of User Fortran, you must ensure that the Fortran is linked against the solver-msmpi.lib. This is done by making the appropriate changes to cfx5mkext.ccl. %USERPROFILE% is typically C:\Documents and Settings\<Username>\ on XP, or C:\Users\<UserName> on Vista or Server HPC 2008. To use on ANSYS Workbench with Parameters and Design Points, start the CFX-Solver Manager ensure that the Run Mode on the Run Definition tab of the CFX-Solver Manager is set to Submit to Windows CCS or HPC Queue, set the number of processes, then click Save Settings. When the user clicks Update all Design Points each parameter or design point will be solved on the cluster.
2. 3.
22

Installation and Licensing Documentation

Uploaded by

Copyright:

Available Formats

Installation and Licensing Documentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Licensing Documentation

Uploaded by

Copyright:

Available Formats

Installation and Licensing Documentation

Copyright and Trademark Information

U.S. Government Rights

ANSYS, Inc. Licensing Guide

Release 14.0 November 2011 000289

Copyright and Trademark Information

U.S. Government Rights

Supported Hardware Platforms

Summary of New and Changed Features

Then, either reread or restart the Licensing Interconnect.

Conventions Used in This Document

The Licensing Process

Compatibility with Other FLEXlm-Licensed Software

1.1. Explanation of Licensing Terms

1.1.1. The FLEXlm License Server Manager (lmgrd)

1.1.2. The Vendor Daemon (ansyslmd)

Explanation of Licensing Terms

1.1.3. ANSYS Licensing Interconnect (ansysli_server)

1.1.4. The License File

1.1.4.1. License Files Format

1.1.4.1.1. SERVER Lines

1.1.4.1.2. VENDOR Lines

Explanation of Licensing Terms

1.1.4.1.3. INCREMENT Lines

ANSYS, Inc. has created two VENDOR_STRING keywords:

Chapter 1: Introduction customer

1.1.4.1.4. Sample License Files

1.1.4.1.5. Recognizing an ANSYS, Inc. License File

Table 1.1 Identifying License Files

1.1.5. The Application Programs

1.1.6. The License Server Machines

1.1.6.1. Selecting License Server Machines

1.1.6.2. Redundant Server Options

Explanation of Licensing Terms

Chapter 2: Installing the ANSYS License Manager

Chapter 2: Installing the ANSYS License Manager

2.1. Communications Requirements

Table 2.1 Configuring TCP/IP

2.1.1.1. Determining Whether TCP/IP Is Installed on a Microsoft Windows System

Installing the License Manager

2.2. Installing the License Manager

2.2.1. License Manager Installation Instructions - Windows

2.2.2. License Manager Installation Instructions - UNIX/Linux

2.2.3. Silent License Manager Installation Instructions

Installing the License Manager

2.2.4. Advanced Licensing Configuration Options

Run the ANSYS Licensing Interconnect without FLEXlm

Run the ANSYS Licensing Interconnect and FLEXlm independently

2.3. Post-Installation Instructions

2.3.1. Start the ANSYS License Manager at System Boot Time

Table 2.2 License Manager Automatic Startup Instructions

Remove each file, one at a time using rm.

Issue the new license manager startup instructions:

Linux: Red Hat

Chapter 2: Installing the ANSYS License Manager Platform Instructions

Removing the Automatic Startup Information

Table 2.3 Removing License Manager Automatic Startup Instructions

Issue the following commands:

2.3.2. Configuring the License Server Machine(s)