Installation and Licensing · PDF fileSouthpointe April 2016 2600 ANSYS Drive 000409 Canonsburg, PA 15317 ANSYS, Inc. is certified to ISO 9001:2008. ... 1.1.2.The Vendor Daemon (ansyslmd)

Installation and Licensing Documentation

Release 17.1April 2016

Copyright and Trademark Information

© 2016 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, AIM and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogansare registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries in the United States or othercountries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark of Sony Cor-poration in Japan. All other brand, product, service and feature names or trademarks are the propertyof their respective owners.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS ANDARE CONFIDENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS.The software products and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliatesunder a software license agreement that contains provisions concerning non-disclosure, copying, lengthand nature of use, compliance with exporting laws, warranties, disclaimers, limitations of liability, andremedies, 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 licenseagreement.

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 inthe 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 proprietarysoftware and third-party software. If you are unable to access the Legal Notice, Contact ANSYS, Inc.

Published in the U.S.A.

Licensing Guide

Release 17.1ANSYS, Inc.April 2016Southpointe

2600 ANSYS Drive 000409Canonsburg, PA 15317 ANSYS, Inc. is

certified to ISO9001:2008.

[email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494

Revision Information

The information in this guide applies to all ANSYS, Inc. products released on or after this date, until supersededby a newer version of this guide.



ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIMand any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarksor trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademarkused 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 CONFID-ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software productsand documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreementthat contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exportinglaws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software productsand documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditionsof that software license agreement.



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).


See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary softwareand third-party software. If you are unable to access the Legal Notice, Contact ANSYS, Inc.


Table of Contents

Preface .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1. Explanation of Licensing Terms .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.1. The FlexNet License Manager Daemon (lmgrd) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2. The Vendor Daemon (ansyslmd) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.3. ANSYS Licensing Interconnect (ansysli_server) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.4. The License File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1.4.1. License File Format .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.4.1.1. SERVER Lines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.4.1.2. VENDOR Lines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.4.1.3. INCREMENT Lines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1.4.1.4. Sample License Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.4.1.5. Recognizing an ANSYS, Inc. License File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.5. The Application Programs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1.6. The License Server Machines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.6.1. Selecting License Server Machines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1.6.2. Redundant Server Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2. Installing the ANSYS License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1. Communications Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.1. Configuring TCP/IP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.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 FlexNet Port Numbers .... . . . . . . . . . . . . . . . . . 132.2. Installing the License Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1. License Manager Installation Prerequisites .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.2. License Manager Installation Instructions - Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.3. License Manager Installation Instructions - Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.4. Silent License Manager Installation Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.5. Advanced Licensing Configuration Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3. Post-Installation Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.1. Start the ANSYS License Manager at System Boot Time .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.2. Starting the ANSYS Licensing Tomcat Server at System Boot Time .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.3. Modifying the Tomcat Port Number .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3.4. Configuring the License Server Machine(s) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.5. Modify License Manager Startup Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.6. Create a Group (Linux Only) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.3.6.1. Defining Group Restrictions for the Licensing Interconnect .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.3.7. Specify User Privileges .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.8. Specifying the License Server and License Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.9. Specifying Firewall Settings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.10. Setting Up Redundant (Triad) Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.4. Uninstalling the License Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283. License Server Administration Using ANSYS License Management Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1. ANSYS License Management Center Browser Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.2. Accessing the ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3. Using the ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.3.1. Adding a License .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.2. Starting the ANSYS License Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.3. Stopping the ANSYS License Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.4. Rereading the License Manager Settings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.3.5. Displaying the License Server Machine Hostid Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

iiiRelease 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information

of ANSYS, Inc. and its subsidiaries and affiliates.

3.3.6.Viewing FlexNet Licenses .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.3.7. Viewing the Licensing Interconnect Log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.3.8. Viewing the FlexNet Debug Log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.3.9. Viewing the ANSYS License Management Center Log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.3.10. Displaying the FlexNet License Status .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.3.11. Gathering Diagnostic Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.3.11.1. Gathering Diagnostic Information outside of ANSYS License Management Center ... . . . . . 393.3.12. Specifying the License Manager Run Mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.3.13. Accessing the Help Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.4. Enabling Secure Connections to the Web Server (Optional) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.4.1. Understanding Certificates .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.4.2. Configuring Tomcat Using Keytool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.4.2.1. Preparing the Certificate Keystore .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.2.2. Editing the Tomcat Configuration File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5. Changing the Version of Java Used by ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.5.1. Changing the Java Version During a New Installation of ANSYS License Manager .... . . . . . . . . . . . . . . . . . 443.5.2. Changing the Java Version on an Existing Installation of ANSYS License Manager .... . . . . . . . . . . . . . . . . 44

4. End-User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.1. Client Environment Variable Settings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.1.1. License Files Settings Precedence .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.2. Establishing User Licensing Preferences .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.2.1. ANSYS Workbench Licensing Methods .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.2.2. HPC Licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.2.2.1. Specifying HPC License Order .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.2.3. HPC Parametric Pack Licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.3. Setting Up License Queuing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4. Borrowing Application Licenses on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5. License Administration Using ANSLIC_ADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.1. Using the ANSLIC_ADMIN Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.1.1. Launch the ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.1.2. Specify the License Server Machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5.1.2.1. Sample Scenario .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.1.3. Set License Preferences for User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.4. Run the ANSYS Borrow Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.1.4.1. Setting up License Borrowing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.1.4.2. Running the Borrowing Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.1.5. Set Site Preferences .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.5.1. Specify Product Order .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.5.2. Modify Startup Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.1.5.3. Specify License Servers to Cache .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.1.6. View Status/Diagnostic Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.6.1. Display the License Status .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.6.2. Display Queued Licenses .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1.6.3. Display the Customer Number .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1.6.4.View the ANSYS Licensing Interconnect Debug Log File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1.6.5. View the ANSYS FlexNet Debug Log File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1.6.6. Gather Client Diagnostic Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6. Using Dongles with the ANSYS License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716.1. Assumptions, Restrictions, and Notes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716.2. File Information and Supported Dongle Driver Versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726.3. Supported Platforms .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.4. Windows Procedures .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationof ANSYS, Inc. and its subsidiaries and affiliates.iv

ANSYS, Inc. Licensing Guide

6.4.1. Installing/Updating the Dongle Driver on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.4.2. Removing an Existing Dongle Driver on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6.5. Linux Procedures .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.5.1. Installing/Updating the Dongle Driver on Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.5.2. Removing an Existing Dongle Driver on Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.6. Dongle Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.1. Getting Additional License Debug Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.2. Gathering Diagnostic Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.3. Problem Situations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7.3.1. License Manager Will Not Start ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.3.1.1. License Manager Will Not Start After Adding a License File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.3.2. License Manager Will Not Stop .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3.3. License Manager Will Not Stop in a Three-Server Environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3.4. License Manager Installation's Licensing Configuration Step to Update Site Preferences (ProductOrder) Fails ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3.5. The Application Does Not Show the Correct License(s) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847.3.6. FlexNet Log File Shows Unexpected Messages When the License Manager Is Stopped .... . . . . . . . . . 847.3.7. Unable to Check Out Licenses .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857.3.8. Entries in the FlexNet Options File Are Ignored .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857.3.9. Jobs Abort When a License Manager Goes Down in Three-Server Environment .... . . . . . . . . . . . . . . . . . . . . 867.3.10. Licensing Log File Not Created .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867.3.11. Queuing Does Not Work .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867.3.12. No Licensing Interconnect or FlexNet Path Available from Display the License Status Op-tion .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.3.13. Cannot Enter Data in Text Fields .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.3.14. Design Point Project Locks Reserved Licenses During a Hang .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887.3.15. See a “File Not Found” Message When Running a Licensing Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3.16. Cannot See Attached Dongle .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3.17. Unable to Run a Bookmarked Version ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . 897.3.18. Unable to View PDF Files in ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3.19. Unable to Search PDF Files in ANSYS License Management Center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3.20. Starting ANSYS License Management Center Causes Error Messages (Linux Only) ... . . . . . . . . . . . . . . . 907.3.21. Manually Changing the Tomcat Port Number .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

7.4. Licensing Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907.5. License Manager Installation Directory Errors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977.6. ANSYS License Borrowing Errors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977.7. FlexNet License Log File Errors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

8. Product Variable Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Glossary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Index .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

vRelease 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information


ANSYS, Inc. Licensing Guide

Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationof ANSYS, Inc. and its subsidiaries and affiliates.vi

List of Tables

1.1. FlexNet Versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2. Identifying License Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1. Configuring TCP/IP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2. License Manager Automatic Startup Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3. Removing License Manager Automatic Startup Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4.Tomcat Automatic Startup Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5. Removing Tomcat Automatic Startup Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1. 64-bit Windows File Information and Supported Dongle Driver Version .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726.2. 64-bit Linux File Information and Supported Dongle Driver Version .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726.3. 64-bit Windows Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.4. 64-bit Linux Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738.1. Product/Feature Names for Licensed Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

viiRelease 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information


Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationof ANSYS, Inc. and its subsidiaries and affiliates.viii

PrefaceThis document contains information for running the ANSYS License Manager with all ANSYS, Inc.products, including ANSYS Electromagnetics (Ansoft) products. However, some information may pertainonly to specific products/licensing levels, such as Mechanical APDL (ANSYS) or ANSYS Fluent.

Supported Hardware Platforms

This document details information about licensing ANSYS, Inc. products on the hardware platforms listedbelow. Not all products support all platforms listed below. Refer to the installation documentation forplatform specifics, including the platforms on which your specific product runs. The name in parenthesesindicates the directory name for each platform (referred to as <platform> throughout this document).

• Linux x64 (linx64)

• Windows x64 (winx64)

For specific operating system requirements, refer to the installation guide for the product and platformyou are running. See our platform support information at http://www.ansys.com/Support/Platform+Sup-port. (This URL is case-sensitive.)

Intended Audience

The ANSYS Licensing Guide is intended for the person responsible for licensing administration of allANSYS, Inc. products at a site. This person is typically the system administrator. End users of the productmay also find this information useful, especially client options.

Applicability

This guide applies to all products licensed with the ANSYS License Manager. See Product VariableTable (p. 101) for a list of products.

Summary of New and Changed Features

Listed below is a summary of those licensing items that are either new or have been changed since thelast release. For a list of all major new and changed features of any product, see the Release Notesdocument for that product.

• The ANSYS License Manager Installation automatically updates your modified product order file to includeany product changes that have occurred in the most recently installed release.

• You may safely continue using the 17.0 License Manager; it is not necessary to upgrade to the 17.1 LicenseManager, unless you need to take advantage of any new features.

• ANSYS will soon begin issuing CVD licenses to Electronics customers. To ensure that this license is fullysupported, we recommend that Electronics customers upgrade to the 17.1 LM now.

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

ixRelease 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information


http://www.ansys.com/Support/Platform+Support


Lengthy user input lines that exceed the width of the page are listed in multiple lines, with the secondand subsequent lines indented:

exec_path <drive>:\Program Files\ANSYS Inc\ansys171\ac4 \bin\pro\<platform>\ac4pro171.exe

Wild card arguments and variables are italicized.

Commands appear in bold face.

Note

Note paragraphs are introduced by the text Note. A note contains information that supple-ments the main topic being discussed.

Caution

Paragraphs that begin with the word “Caution” in bold, with the rest of the text in normaltype, warn you about actions or situations that potentially may cause problems or unexpectedbehavior or results in ANSYS, Inc. products.

Warning

Paragraphs that begin with the word “Warning” in bold warn you about actions or situationsthat can shut down ANSYS, Inc. products, damage files, etc.

Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationof ANSYS, Inc. and its subsidiaries and affiliates.x

Preface

Chapter 1: Introduction

ANSYS, Inc. uses the FlexNet license manager for all of its licensed products. FlexNet is best known forits ability to allow software licenses to be available (or float) anywhere on a network. Floating licensingbenefits both users and license administrators. Users can make more efficient use of fewer licenses bysharing them on the network. License administrators can control who uses the licensed application andthe machine(s) where the licenses will be available. The format of the traffic between the ANSYSproduct(s) and the license manager is machine-independent, allowing for heterogeneous networks. Thelicense server machine and the computer running an application can be different hardware platformsor even different operating systems (Windows and Linux, for example).

The actual communication between the ANSYS applications and FlexNet occurs through an intermediaryprocess called the ANSYS Licensing Interconnect. The Licensing Interconnect is nearly transparent; youshould 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 manager install-ation. The general licensing process is explained here; for detailed installation instructions, see Installingthe ANSYS License Manager (p. 11). All files necessary to run as a client are automatically installedduring the product installation.

License administration functions are performed via the ANSYS License Management Center and theANSLIC_ADMIN utility (server and client). For more information on the using these tools, see LicenseServer Administration Using ANSYS License Management Center (p. 31) and Using the ANSLIC_ADMINUtility (p. 57).

The Licensing Process

The licensing process for ANSYS, Inc. products is as follows:

1. Select the license server machine(s). See Selecting License Server Machines (p. 8) for guidelines.

2. Install and configure TCP/IP. See Communications Requirements (p. 12) for information on configuringTCP/IP.

3. Install the software. See Installing the License Manager (p. 13), or see the appropriate installationmanual for your product and platforms for detailed installation instructions.

4. After you receive your license file, add your license file using the ANSYS License Management Center.See Adding a License (p. 32)

5. Set up the licensing environment. See Post-Installation Instructions (p. 20).

Compatibility with Other FlexNet-Licensed Software

Because of FlexNet's popularity, you may have FlexNet licenses from more than one vendor.

1Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information


The ANSYS License Manager uses the following versions of FlexNet:

Table 1.1: FlexNet Versions

FlexNet VersionPlatform

Version 11.13.1.2Windows

Version 11.13.1.2Linux

The ANSYS License Manager can run on the same server as other FlexNet license managers with nointervention or special configuration requirements. However, the ANSYS License Manager does notsupport the use or combination of license files from other vendors.

Links to FlexNet

For more information on using FlexNet, visit the FlexNet web site at http://www.flexerasoftware.com/.You can refer to the FlexNet License Administration Guide for more detailed information on all FlexNetfeatures. You can access this document from the ANSYS License Management Center.

1.1. Explanation of Licensing Terms

The main components of our licensing are:

• The ANSYS License Manager, including:

– Licensing Interconnect (ansysli_server) -- Also includes ansysli_monitor, which ensuresthat the license server is functioning correctly and attempts to correct the situation if the licenseserver is not running or is unresponsive.

– FlexNet license manager daemon (lmgrd)

– Vendor daemon (ansyslmd)

• License files

• Application program (e.g., Mechanical APDL (ANSYS) or ANSYS Fluent)

• License server machines

These components are explained in more detail in the following sections.

The ANSYS License Manager monitors what products are being run, who is running them, and fromwhat computer system. It grants or denies permission to run products. When an ANSYS product begins,it requests permission to execute from a license server. The ANSYS License Manager checks the poolof available licenses and grants the request only if the required licenses are available. For each requestthat is granted, the licenses are removed from the pool. As each product execution ends, its licensesare returned to the pool.

1.1.1. The FlexNet License Manager Daemon (lmgrd)

lmgrd is one of the FlexNet components of the ANSYS License Manager. Its primary purpose is to startand maintain the vendor daemon (ansyslmd). It also refers application checkout requests to the vendordaemon (ansyslmd).

lmgrd must be running on the license server machine to run ANSYS, Inc. products.

Release 17.1 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationof ANSYS, Inc. and its subsidiaries and affiliates.2

Introduction

http://www.flexerasoftware.com/

1.1.2. The Vendor Daemon (ansyslmd)

Licenses are granted by running processes. Each vendor who has a FlexNet-licensed product on thenetwork has one process, called the vendor daemon. The vendor daemon keeps track of how many li-censes are checked out, and who has them. If the vendor daemon terminates for any reason, all usersfor that product lose their licenses. The ANSYS vendor daemon is ansyslmd.

Client programs, including ansysli_server, communicate with ansyslmd, usually through TCP/IPnetwork communications. The vendor daemon (ansyslmd) is started by lmgrd. The vendor daemonansyslmd must be running on the license server machine to run ANSYS, Inc. products.

1.1.3. ANSYS Licensing Interconnect (ansysli_server)

The ANSYS Licensing Interconnect (ansysli_server) is an intermediary process that communicateswith the FlexNet component of the license manager to authenticate and process all license requests.In a typical configuration, the ANSYS Licensing Interconnect starts the FlexNet component lmgrd,which then starts ansyslmd.

With the Licensing Interconnect, your license file and license options file are still applicable and in effect.Using an intermediary process allows us to seamlessly integrate our full range of product offerings tocontinually 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. andis installed by the license administrator. It contains information about the server machines and vendordaemon, and at least one line of data (called INCREMENT lines) for each licensed product. Each INCRE-MENT line contains a license key based on the data in that line and other vendor-specific information.

1.1.4.1. License File Format

License files usually begin with a SERVER line (or three SERVER lines for redundant triad servers) followedby a VENDOR line, followed by one or more INCREMENT lines. Each INCREMENT line contains a licensekey based on the data in that line, the hostids specified in the SERVER lines, and other vendor-specificdata.

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)



Explanation of Licensing Terms

Long lines normally use the "\" line-continuation character to break up long lines. A space charactermust 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 portnumber. Normally a license file has one SERVER line. Three SERVER lines mean that you are using re-dundant servers. License administrators do not have the option of deleting SERVER lines from a licensefile because the hostids from all of the SERVER lines are computed into the license keys on every INCRE-MENT 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 Linux hostnameor uname -n command. On Windows systems, ipconfig /all returns the host name. This can alsobe an IP address (nnn.nnn.nnn.nnn format).

hostid is returned by the Get System Hostid Information option of the ANSYS License ManagementCenter.

1055 is the ANSYS default port number for FlexNet TCP. If port 1055 is already in use on your system,you can change this value.

Example:

SERVER enterprise 0122345 1055

Note

If you change the FlexNet port number, then you must also change the FlexNet port numberthat is specified in the ansyslmd.ini file (see Specify the License Server Machine (p. 59))or in the ANSYSLMD_LICENSE_FILE environment variable on all client machines to matchthe 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 vendordaemon, and the vendor daemon reads it to find its options file. The format of the VENDOR line isshown below.

VENDOR ansyslmd [vendor_daemon_path] [[options=]options_file_path] [[port=]port]

where:

ansyslmd is the name of the ANSYS vendor daemon.


Introduction

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 executablein the directory where lmgrd is located and all ANSYS products install both of these daemons into thesame directory.

Note

If you do supply this path and the path includes spaces, enclose the entire directory path indouble quotes, as in the following example:

VENDOR ansyslmd "C:\Program Files\ANSYS Inc\Shared Files\Licensing \win64"

options_file_path is the full path to the end-user options file for this daemon. FlexNet does notrequire an options file. The options file need not be specified on this line. As long as the options fileansyslmd.opt is located in the same directory as the license file (the license_files directory), thevendor daemon will automatically find and use it.

If the directory path includes spaces, enclose the entire directory path in double quotes, as in the fol-lowing 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 re-commended. 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="..."] [SIGN2="..."]

where:

feature is the name representing the product/capability being licensed.

ansyslmd is the name of the ANSYS vendor daemon; also found in the VENDOR line. The specifieddaemon serves this feature.

feat_version is the latest build date of this feature that is supported by this license. For paid-upcustomers, this is usually set to the expiration date of the maintenance agreement. The value of 9999.9999is used when this field is not applicable.

exp_date is the expiration date of license, e.g., 7-may-2014.

#lic is the number of concurrent licenses for this feature.

key is the encryption key for this INCREMENT line.

Additional fields may follow. See the FlexNet License Administration Guide (accessible from the ANSYSLicense Management Center) for more information. Note that ANSYS, Inc. may not support all optionsdescribed in the FlexNet License Administration Guide.




VENDOR_STRING Keywords ANSYS, Inc. has created the following VENDOR_STRING keywords:

• customer

The customer keyword specifies the customer number. The format is customer:<cust_num>,where cust_num is the customer's number. You must not modify this keyword.

The SIGN2 keyword specifies the Tamper Resistant License (TRL) encryption. The encryption is 60characters (fifteen 4 character segments separated by spaces).

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 1055VENDOR ansyslmdINCREMENT ansys ansyslmd 9999.9999 30-sep-2013 15 8C59A481BA50 \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2012 \ START=10-sep-2014 SIGN2=”007B AC4B D3A2 \ E623 DC66 BC38 7B31 CE00 0055 DE8D 0E27 C6FD 6C07 EE27 BBCC"INCREMENT acfd ansyslmd 9999.9999 30-sep-2013 12 47A354CA1291 \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2012 \ START=10-sep-2014 SIGN2=”0A03 2D61 0801 \ 3B5C DC87 7B08 4AFC F780 0CD9 704E F9C5 2A72 0D23 2F38 64AC""

where:

• gagh is the hostname of the license server

• 690daec6 is the hostid

• 1055 is the FlexNet port number

• ansyslmd is the vendor daemon

• ansys is the feature representing ANSYS Mechanical and acfd is the feature representing ANSYS CFD.

• 9999.9999 indicates that the maintenance agreement is not applicable. Otherwise, this is highest sup-ported build date for the product. For Mechanical APDL (ANSYS) only, you can view the build date byrunning Mechanical APDL (ANSYS) with the -v command option.

• 30-sep-2013 is the expiration date

• 15 and 12 are the number of tasks for ANSYS Mechanical and ANSYS CFD, respectively

• 8C59A481BA50 and 47A354CA1291 are encryption keys for ANSYS Mechanical and ANSYS CFD, respectively

• customer:00012345 is the customer number

• ISSUED=10-sep-2012 is the date the license was created

• START=10-sep-2012 is the start date

• SIGN2=<” fifteen 4 character segments” >

is the TRL encryption


Introduction

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 isby looking at the contents of the license file. If it is an ANSYS, Inc. license file, then:

• In the line beginning with the word VENDOR, the next field/item is ansyslmd.

• In the line(s) beginning with the word INCREMENT, the third field/item is ansyslmd.

Through use of the FlexNet Common Vendor Daemon technology, license files using the ansoftd vendordaemon are also supported by the ANSYS License Manager.

ANSYS, Inc. supplies some licenses for other applications that use different license managers. These licensefiles are not compatible with the ANSYS License Manager. The applications and how to recognize theirlicense files are explained below. Look for the words shown in the VENDOR, DAEMON, INCREMENT, andFEATURE lines for each application. For these license files, you must use their respective license managertools.

Table 1.2: Identifying License Files

FEATUREINCREMENTDAEMONVENDORApplication

CFDSCFDSANSYS CFX

ICEM_CFDICEM_CFDANSYS ICEM CFD

AUTODYNAUTODYNANSYS Autodyn

FluentLMFluentLMFluent, Polyflow,Icepak

ansoftdansoftdANSOFT

apachedaapachedaApache

seqldseqldApache

1.1.5. The Application Programs

Application programs are software programs such as Mechanical APDL (ANSYS), CFX, Fluent, HFSS, etc.ANSYS application programs need to be able to communicate with the ANSYS License Manager.

1.1.6. The License Server Machines

License administration is controlled from specific computers on the network called license server ma-chines. 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 designatingone server or three servers. In a one-server network, if the server machine goes down, the licenses areno 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 orderof the SERVER lines in the license file determines which server is the master. The order of the serversmust match on all machines in a three server environment. The first is the master, the second is the firstbackup, 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-servernetwork, 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, andprovide the hostid and hostname of those machines to ANSYS, Inc. Use the Get System Hostid Inform-ation option of the ANSYS License Management Center to capture the necessary system informationand create the text file, which then needs to be forwarded to your ANSYS sales representative.

You need to select the computer systems that will act as server machines before we can supply youwith the licenses that are required to activate your licensed product(s). Information about the servermachines 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 physicallylocal 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 CPUand/or I/O usage are poor candidates for servers.

• Do not use computers that are frequently rebooted as servers.

• Do not enable “sleep mode” for the computer you are using as a license server. Client computers are notable to connect with a license server that is in sleep mode.

• The license server machine must have a static IP address.

• We do not allow the use of wide area networks (WANs) for license servers (with the standard ANSYS contract).

• If using a three-server network, we recommend that you choose three machines that are of the same platformtype (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 subnetin the same physical location.

If these guidelines are not followed, the ability of the ANSYS License Manager to perform consistentlywill be compromised.

Caution

Do not change the date on the license server machine. Doing so will prohibit the ANSYSproduct from running. Restoring the system to its original state prior to the date changemay require significant effort.


Introduction

1.1.6.2. Redundant Server Options

Throughout this document, we use the term “three-server network” when referring to redundant triadservers. Redundant server setup is a network configuration where multiple machines are designated aslicense servers. Redundancy can be achieved in two ways:

• Any number of license server machines can be running independently. The total number of licenses issplit between each license server. For example, if you are licensed for 20 tasks of a certain product, andyou have two license server machines, each license server machine will serve ten licenses. In this example,if one of these machines fails, only ten licenses will be available.

• Three different machines can be selected to work together in tandem (typically referred to as a redundanttriad), where two of the three must be running at all times. These three license server machines workfrom 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 LicenseServer Machines (p. 8) for guidelines and special considerations when choosing license servers. Singlelicense 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 entirelicensing directory) installed locally on each license server. If you do not, you lose all theadvantages of having redundant servers, since the file server holding these files becomes asingle point of failure.





Chapter 2: Installing the ANSYS License Manager

The ANSYS License Manager installation includes both a server and a client component. You must installthe 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 ANSYS Licensing Interconnect, the latest dae-mons/services, and the latest ANSYS License Management Center and ANSLIC_ADMIN updates. Ifyou do not install the license manager at this release, your ANSYS, Inc. products will not run. You willfind 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 componentson a machine designated as a license server machine.

Once the updated License Manager is installed on your server machine(s) and you have installed theproduct(s), the client component will run successfully. The client component is installed automaticallyduring a product installation; users running as a client will not need to perform any additional installationsteps to successfully run the product(s). Note that the client component will not be installed withElectronics (Ansoft) products, nor is it needed.

Important Notice — Running Multiple Releases

If you want to run multiple releases of ANSYS, Inc. software, you MUST install them chronologically (i.e.,Release 16.0 followed by Release 17.1). If you install an earlier release after installing Release 17.1, youwill encounter licensing issues that may prevent you from running any products/releases. If you needto install an earlier release after you have already installed Release 17.1, you must uninstall Release17.1, then re-install the releases in order.

Linux Server Installation Notes: If you are installing the License Manager on the same machinewhere the product will be run, use the same top level directory path for both the product installationand the License Manager installation. We strongly recommend that you install the licensing files relativeto the product installation directory to avoid manually editing the product run scripts.

A typical product installation on a Linux machine allows you to install the product anywhere on thesystem and then creates a symbolic link from the installation directory to /ansys_inc. If you did notset the symbolic link during the product installation, or if you installed the licensing files somewhereother than relative to the installation directory, replace all references to /ansys_inc in this guidewith the name of the installation directory you used. Any reference throughout this manual to the li-censing directory on Linux platforms means /ansys_inc/shared_files/licensing.

Windows License Server Installation Notes: The licensing installation on a Windows machine installsall necessary licensing files into the \Program Files\ANSYS Inc\Shared Files directory bydefault, located on the same drive as the operating system or the directory where you installed the li-censing files, regardless of where your product installation resides. You must have administrative privilegeson your machine to install the licensing files. The license manager components are shared across allANSYS, Inc. products and need to reside in the same location for all ANSYS, Inc. products and releases.

Any reference throughout this manual to the licensing directory on Windows platforms means \ProgramFiles\ANSYS Inc\Shared Files\Licensing, located on the same drive as the operating system,or the directory where you installed the licensing files. If you choose to install the ANSYS License Manager



to a different location, you must replace any references to \Program Files\ANSYS Inc\SharedFiles\Licensing with the directory where you installed the license manager.

Windows/Linux License Client Installation Notes: The license client files are automatically installedinto the \Shared Files\Licensing (Windows) or the /shared_files/licensing (Linux)subdirectory of the product installation at the end of the product installation. Note that the clientcomponent will not be installed with Electronics (Ansoft) products, nor is it needed.

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 beable to run. You should consult your network administrator for assistance with this configuration. TheTCP/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 Linux operating system. Table 2.1: Configuring TCP/IP (p. 12) specifiesthe system utility used to configure TCP/IP on the various hardware platforms. You should consult yournetwork administrator for assistance with this configuration.

Note

Linux systems require an Ethernet card.

Table 2.1: Configuring TCP/IP

TCP/IP Configuration UtilityHardware Platform

system-config-networkLinux (Red Hat Enterprise) (64-bit)

yastLinux (SuSE Enterprise) (64-bit)

For Windows systems, the TCP/IP protocol is included as part of the operating system and is typicallyinstalled by default. If you do need to install TCP/IP, remember that it must be bound to a networkadapter.

On machines that are connected to an internal network, TCP/IP must be bound to a network card suchas 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 boundto 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, select Network and Internet>Network and Sharing Center. Click Local Area Connection and click Properties. Internet Protocol(TCP/IP) should be listed.


Installing the ANSYS License Manager

If TCP/IP is installed, you must determine whether it is bound to a network adapter card or a dial-upconnection. A network card or a Dial-Up Adapter will be shown under Connect Using:.

Caution

If your computer is connected to a network, it is highly recommended that you contact yourInformation Technology Department before installing or modifying TCP/IP on your machine.

2.1.2. Changing the Default ANSYS Licensing Interconnect and FlexNet PortNumbers

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 thedefault port number for the FlexNet component of the license manager. ansyslmd also uses a portdesignated by the operating system, unless one is manually specified in the license file on the VENDORline. If you encounter a conflict in port numbers, you can change the default by modifying all of thefollowing files:

ANSYS Licensing Interconnect Port Number The ANSYS Licensing Interconnect port number isdefined in the ansyslmd.ini file. You can change this file by selecting Specify the License ServerMachine on the ANSLIC_ADMIN utility. Enter the new port number in the ANSYS Licensing Intercon-nect Port Number field. The Licensing Interconnect port number may also be specified via the AN-SYSLI_SERVERS environment variable, if set.

FlexNet Port Number To change the default FlexNet port number, you need to change the followingfiles:

• On the license server machine(s): the port number listed on the SERVER line in the license file (ansyslmd.licand/or ansoft.lic).

• On the client machine(s): the port number listed in the ansyslmd.ini file. Use the Specify the LicenseServer Machine option of the ANSLIC_ADMIN utility to change the ansyslmd.ini file. The FlexNet portnumber 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) forinformation on specifying this port number on the VENDOR line. You should need to specify this portnumber manually only if using a firewall.

For information on firewall settings, see Specifying Firewall Settings (p. 27).

2.2. Installing the License Manager

You must have administrator privileges to install the ANSYS License Manager on Windows systems. OnLinux systems, you can install without administrative privileges but you may encounter permissionproblems during the installation.

To proceed with the installation, the current license manager must be shut down if it's running. Theinstallation process will shut down the license manager; however, you should verify that no users willbe affected while you run the installation.



Installing the License Manager

When you run the license manager installation on the license servers, the licensing installation processwill install all necessary files, as well as set the ANSYSLIC_DIR environment variable in the product-runscripts. If there is an existing license manager, the installation process will shut it down, so you shouldverify that no users will be affected while you run the installation.

Note that the FLEXlm for Ansoft (ansoftd) license manager will also be shut down and uninstalled if it’srunning; all associated license files will be migrated over to the ANSYS License Manager. Once migrated,you will no longer be able to run the ANSYS License Manager and the FLEXlm for Ansoft License Manageron the same system.

To support the ANSYS License Management Center, a Tomcat web server and Java will be installedwithin the license manager directory during the ANSYS License Manager installation . To view the latestTomcat and Java versions installed, access the View Licensing Configuration Details option describedin Accessing the Help Options (p. 41).

Existing customers may not be supplied with new licenses for the current release package. They willbe supplied when the current licenses expire or when TECS expires.

Run the license manager installation on all machines that will act as license servers.

2.2.1. License Manager Installation Prerequisites

On Linux systems, you can install without administrative privileges, but you may encounter permissionproblems during the installation.

On Windows systems you must have administrator privileges to perform the installation.

Note

On Windows systems, you cannot perform a platform license server installation (that is,install files for a different machine type than you are running on).

2.2.2. License Manager Installation Instructions - Windows

Follow the instructions below to install the ANSYS License Manager on Windows systems that will actas license servers. Client licensing is installed automatically when the product is installed; you do nothave to take any further steps to run as a client if you have installed a product.

1. Right-click the setup.exe file and select Run as administrator. If you downloaded the license managerinstallation package, this file will reside in the directory where you unzipped the files. If you are runningfrom media, this file will reside in the top level of the media.

If you downloaded only the license manager installation, run setupLM.exe by right-clicking thefile and selecting Run as administrator.

2. The installation launcher appears. Choose a language from the dropdown.

3. Select Install ANSYS License Manager.

4. You will be notified that the license manager (ANSYS or FLEXlm for Ansoft (ansoftd)), if running, will beshut down. Click OK.



5. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree toaccept the terms and click the Next arrow, located on the right side of the screen. You must select I Agreeto continue with the installation.

6. Specify the installation directory. You can accept the default or specify an alternate path and the directoryname where the license manager is to be installed. The installation directory is set to<OS_Drive>\Program Files\ANSYS Inc by default. You must have administrative privileges forthe directory you specify. In addition, the directory:

• Must be a local directory

• Must be a local, fixed-media drive

• Cannot be a UNC or relative path

• Cannot be a short (8.3) file name format path

• Cannot be a symbolic link or junction

• Cannot use wide character names/paths

Note

You are not permitted to change the installation directory for a computer that currentlycontains an instance of the ANSYS License Manager. To change the installation directorylocation, you must first uninstall any previous versions of the product.

7. The ANSYS License Manager is the only component available and is selected to be installed. The amountof disk space required and the disk space available appear at the bottom of the window. If the disk spacerequired exceeds the disk space available, be sure that you have sufficient space before continuing. Thedisk space required as calculated by the installation program may be greater than the actual amountneeded. However, if you choose to continue the installation, you should carefully review any log and errorfiles at the end of the installation to ensure that the installation completed successfully.

Click the Next arrow to continue.

8. A summary of the selected installation data appears. Information shown includes platform, installationdirectory, and product. Review the information carefully, and if correct, click the Next arrow to continuethe installation.

9. Once the license manager installation has occurred, the installation program performs a “silent” licensingconfiguration which includes updating the product order. Click the Next arrow to continue the installation.

The Launch License Management Center upon exiting option is included on the screen. TheANSYS License Management Center is a browser-based application that centralizes many of theANSYS licensing administrative functions. For more information, see License Server AdministrationUsing ANSYS License Management Center (p. 31).




If you do not want to launch the License Management Center, uncheck the Launch License Man-agement Center upon exiting option.

Note

If the installation did not complete or completed with errors, review the progresslog by clicking the View Detailed Progress Log button.

10. When the license manager installation is complete, click Exit. A new Start Menu item named ANSYS LicenseManager will be created automatically. It will include selections for the License Management Center,the ANSYS Licensing Guide, the FlexNet License Administration Guide and the server ANSLIC_ADMIN utility.

Note

Client machines will also include a Client ANSLIC_ADMIN option under the ANSYS 17.1Start Menu folder. The client-only version of ANSLIC_ADMIN offers access to a limitednumber of ANSLIC_ADMIN features, such as user configuration and status/reportingoptions. Note that the client component will not be installed with Electronics (Ansoft)products, nor is it needed.

On Windows, if you encounter a problem during the licensing installation process that results in a failureor abort, or if you are concerned that the licensing installation did not complete correctly, we recommendthat you re-run the License Manager installation.

2.2.3. License Manager Installation Instructions - Linux

Follow the instructions below to install the ANSYS License Manager on Linux systems that will act aslicense servers. Client licensing is installed automatically when the product is installed; you do not haveto take any further steps to run as a client if you have installed a product. Note that the client componentwill not be installed with Electronics (Ansoft) products, nor is it needed.

1. Run INSTALL.LM to launch the license manager installation. If you downloaded the license managerinstallation package, this file will reside in the directory where you untarred the files. If you are runningfrom media, this file will reside in the top level of the media.

2. Select a language.

3. You will be notified that the license manager (ansyslmd and/or ansoftd), if running, will be shut down.Click OK.

4. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree toaccept the terms and click Next. You must select I Agree to continue with the installation.

5. If you are installing more than one platform or if you are installing a platform other than your currentmachine type, you will need to select the platform(s) on which you want to install the ANSYS LicenseManager. The platform on which you launched the installation will be selected by default and is shownat the bottom of the window. Click Next to continue.

6. 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 license manager is to be installed. You cannot use wide character names/paths in the installationdirectory.

Note

You are not permitted to change the installation directory for a computer that currentlycontains an instance of the ANSYS License Manager. To change the installation directorylocation, you must first uninstall any previous versions.

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 optionis available only if you are installing as root. If you chose to set the symbolic link during the productinstallation, 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 License Manager. Theamount of disk space required and the disk space available appear at the bottom of the window. If thedisk space required exceeds the disk space available, be sure that you have sufficient space before con-tinuing. The disk space required as calculated by the installation program may be greater than the actualamount needed. However, if you choose to continue the installation, you should carefully review any logand error files at the end of the installation to ensure that the installation completed successfully.

Click Next to continue.

8. A summary of the selected installation data appears. Information shown includes platform, installationdirectory, and product. Review the information carefully, and if correct, click Next to continue the install-ation.

9. Once the license manager installation has occurred, the installation program performs a “silent” licensingconfiguration which includes updating the product order. Click Next to continue the installation.

The Launch License Management Center upon exiting option is included on the screen. TheANSYS License Management Center is a browser-based application that centralizes many of theANSYS licensing administrative functions. For more information, see License Server AdministrationUsing ANSYS License Management Center (p. 31).

If you do not want to launch the License Management Center, uncheck the Launch License Man-agement Center upon exiting option.

Note

If the installation did not complete or completed with errors, review the progresslog by clicking the View Detailed Progress Log button.

10. When the license manager installation is complete, click Exit.

On Linux, if you encounter a problem during the licensing installation process that results in a failureor abort, or if you are concerned that the licensing installation did not complete correctly, we recommendthat you re-run the License Manager installation.




2.2.4. Silent License Manager Installation Instructions

You can deploy an ANSYS License Manager installation in silent mode on both Windows and Linuxsystems. Client licensing is installed automatically when the product is installed; you do not have totake any further steps to run as a client if you have installed a product. Note that the client componentwill not be installed with Electronics (Ansoft) products, nor is it needed.

To run a silent product installation, including the client licensing, see Silent Product and License ManagerInstallation in the ANSYS Installation Guide for your platform.

To silently install the ANSYS License Manager on Windows systems that will act as license servers, youmust run the setupLM.exe with the -silent option:

setupLM.exe -silent

To install the ANSYS License Manager on Linux systems that will act as license servers, you must runthe 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 Runthe ANSYS Licensing Interconnect with FlexNet.

If you are installing the license manager to a non-default installation directory, you can use the silentinstallation method, but only for the initial installation. To change the license manager installation dir-ectory for future installations, you will need to either use the GUI installation or uninstall the licensemanager before reinstalling to a different directory.

Note

You are unable to change the installation directory for a computer that currently containsan instance of the ANSYS License Manager. To change the installation directory location, youmust first uninstall any previous versions of the ANSYS License Manager.

You can use the following arguments when running a silent license manager installation:

Initiates a silent installation.-silent

Specifies the directory to which the license manager is to be installed. If you want to installto the default location, you can omit the -install_dir argument. The default location

-in-stall_dirpath on Linux is /ansys_inc if the symbolic link is set; otherwise, it will default to /usr/an-

sys_inc.

Specifies the location of the license file to install. If the path is not specified or if the pathis the same as the existing license file, the license file will not be installed. For the license

-lic-file-

file path on Windows, you must enclose the path in quotes if you have spaces in thepathname.

pathpath



During a silent installation, any licensing configuration messages will be written to the licensing install-ation configuration log file, install_licconfig.log, located in the installation directory.

Caution

A silent license manager installation could shut down the ANSYS License Manager, affectingother users who are using that license server machine.

If you are running a silent client installation, you can specify license server information as well.

Specifies information to be used by the client for the license server. Valid onlyin conjunction with a silent product installation (setup.exe or INSTALL). See

-licserver-info

the ANSYS Installation Guide for your platform for details on running a silentproduct installation, including client licensing.

2.2.5. Advanced Licensing Configuration Options

In addition to the default configuration, ANSYS, Inc. offers two run mode options that can be selectedthrough the Specify the License Manager Run Mode option in the ANSYS License ManagementCenter:

• Run the ANSYS Licensing Interconnect without FlexNet -- Use this option if you want to run a localcopy of the ANSYS Licensing Interconnect for better performance, such as if your server machine is ina remote location, or to manage the server load better if your license server machine serves many users.With this option, FlexNet licenses will be taken from another server machine. Use this option to run theLicensing Interconnect on additional systems other than your license server; your site must still havethe Licensing Interconnect running on the license server machine.

• Run the ANSYS Licensing Interconnect and FlexNet independently -- Use this option if you wantto manage your FlexNet licenses independently of the ANSYS, Inc. tools (for example, using FlexeraSoftware's FLEXnet Manager to manage multiple companies' FlexNet product licenses). This optionshould be used only by experienced users with well-established licensing procedures.

These options are available through the Specifying the License Manager Run Mode option in theANSYS License Management Center after a license manager installation has been run on this machine.For more information, see Specifying the License Manager Run Mode (p. 40)

If you have already configured your licensing and are changing to a different configuration option, youmust stop and restart the ANSYS License Manager for these changes to take effect. Rereading the licensemanager settings will not be sufficient.

Run the ANSYS Licensing Interconnect without FlexNet

Important

When using this advanced option, the license server holding the FlexNet licenses must alsohave the Licensing Interconnect installed and running.

To use the ANSYS License Management Center to set up a license server that will run the LicensingInterconnect without FlexNet, see Specifying the License Manager Run Mode (p. 40).




Run the ANSYS Licensing Interconnect and FlexNet independently

Use this option if you want to manage your FlexNet licenses on a server machine independently of theANSYS, 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 licensingprocedures. Running these processes separately requires caching the license file, meaning that youspecify the location of an existing license file that contains FlexNet licenses for ANSYS, Inc. products.Because ANSYS License Management Center will no longer be managing FlexNet, you will need touse your license management tools (such as FLEXNet Manager) to start/restart FlexNet or to reread thelicense 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 FlexNet(using your license management tools), you must also recache the license file in the LicensingInterconnect by restarting the Licensing Interconnect or by using the Reread the LicenseManager Settings option in the ANSYS License Management Center.

To use the ANSYS License Management Center to set up a license server that will run the LicensingInterconnect and FlexNet independently, see Specifying the License Manager Run Mode (p. 40).

2.3. Post-Installation Instructions

After you have installed the ANSYS License Manager, you may want to complete some post-installationsteps in order to optimize the performance of the ANSYS License Manager at your site.

We recommend that you set your license manager to boot at system startup. Other optional post-in-stallation tasks are included here. You will only need to configure your license server machine andconfigure your client machines if those steps were not completed during the product or license serverinstallation processes.

2.3.1. Start the ANSYS License Manager at System Boot Time

On Windows systems, the license manager is set to start up automatically at system reboot. On Linuxmachines, you can set the license manager to start automatically at system boot time. This task is op-tional but is recommended and should be done regardless of which type of license server configurationyou use.

Table 2.2: License Manager Automatic Startup Instructions (p. 21) details the steps that must be performedon each license server to start the license manager automatically when the Linux system is rebooted.Substitute your platform name (see Supported Hardware Platforms (p. ix)) wherever you see <platform>.The instructions below include steps to remove any existing boot_ansflex; if you have already re-moved the boot_ansflex, you can safely skip that step.

Note

The procedure described in this section starts the license manager at boot time as root. It isnot essential that the license manager be started by the root user; it may be run by a non-privileged user, depending on your preference. If you do not want the license manager to



be started by root, modify LMUSER in the init_ansysli boot script to include the username you want to use at boot time.

Table 2.2: License Manager Automatic Startup Instructions

InstructionsPlatform

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:

Linux: RedHat

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

Remove existing license manager startup information. Edit the file/etc/rc.d/boot.local and delete the ANSYS boot_ansflexlines.

Issue the new license manager startup instructions:

Linux: SuSE

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 thesystem 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 appro-priate ps command and looking for ansyslmd and ansysli_server in the resulting display underthe 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 forerror messages. These files contains a history of ANSYS product activity across the network when thiscomputer is chosen as the master license server by the licensing software. They also contain start-upmessages 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


Issue the following commands:

/etc/init.d/init_ansysli stopchkconfig --del init_ansyslirm /etc/init.d/init_ansysli

Linux



Post-Installation Instructions

2.3.2. Starting the ANSYS Licensing Tomcat Server at System Boot Time

You can set Tomcat to start automatically at system boot time on Linux machines. This task is optionalbut is recommended and should be done regardless of which type of license server configuration youuse. The License Management Center runs using the Tomcat web server. You can set Tomcat to startautomatically at system boot on Linux machines. This task is required to be able to run the LicenseManagement Center.

Table 2.4: Tomcat Automatic Startup Instructions (p. 22) details the steps for each Linux hardwareplatform that must be performed on each license server to start Tomcat automatically when the systemis rebooted.

Note

The procedure described in this section starts Tomcat at boot time as root. It is not essentialthat Tomcat be started by the root user; it may be run by a non-privileged user, dependingon your preference. If you do not want Tomcat to be started by root, modify the LMUSERvalue in the init_ansyslm_tomcat boot script to include the user login name you wantto use at boot time. This user must have read/write access to all files contained in the followingdirectories:

<Install Directory>/shared_files/licensing/tools/tomcat/conf

<Install Directory>/shared_files/licensing/tools/tomcat/logs

<Install Directory>/shared_files/licensing/tools/tomcat/bin

Table 2.4: Tomcat Automatic Startup Instructions


Issue the Tomcat startup instructions:Linux: RedHat andSuSE

cp /ansys_inc/shared_files/licensing/init_ansyslm_tomcat /etc/init.d chmod 555 /etc/init.d/init_ansyslm_tomcat chkconfig --add init_ansyslm_tomcat chkconfig init_ansyslm_tomcat on

Once the procedure is in place for starting Tomcat automatically at boot time, reboot the system toverify that the automatic boot procedure is working correctly.

When the system comes back up, check to see that Tomcat is running by typing the appropriate pscommand and looking for init_ansyslm_tomcat in the resulting display under the column labeledCOMMAND. For example:

ps -ef|grep tomcat



Removing the Tomcat Automatic Startup Information

If you remove the license manager server installation from a machine and need to remove TomcatAutomatic Startup capability, follow the instructions below.

Table 2.5: Removing Tomcat Automatic Startup Instructions


Issue the following commands:

/etc/init.d/init_ansyslm_tomcat stopchkconfig --del init_ansyslm_tomcatrm /etc/init.d/init_ansyslm_tomcat

Linux: RedHat andSuSE

2.3.3. Modifying the Tomcat Port Number

Note

The following procedure can only be used with a default Tomcat installation. This pro-cedure cannot be used when Tomcat is installed as part of the secure connection option.For more information, see, Enabling Secure Connections to the Web Server (Option-al) (p. 41).

By default, the ANSYS License Manager installation sets the Tomcat port number to 1084. To manuallychange this value, you must modify the server.xml file located in the following directory:

Windows:

<install_dir>\Shared Files\Licensing\tools\tomcat\conf

Linux:

/ansys_inc/shared_files/licensing/tools/tomcat/conf

To change the Tomcat port number:

1. Open the server.xml file.

2. Locate the line that starts with

<Connector port="1084" protocol="HTTP/1.1"

3. Change the port number from 1084 to your desired number.

4. If Tomcat is already running, the new port value will not be used until Tomcat is restarted. This canbe done in the following manner:

Windows:

Open the Windows Services applet and stop and restart the ANSYS Licensing Tomcat service(ANSYSLicensingTomcat). The Windows Services applet can be started by issuing the commandservices.msc from an administrator command prompt window.

Linux:




a. Stop the Tomcat server process by executing the stop_lmcenter script.

b. Start the Tomcat server process with the new port number by executing the start_lmcenterscript.

These scripts can be found in the following directory:

/ansys_inc/shared_files/licensing

Note

Starting the Tomcat server process will also open ANSYS License Man-agement Center.

2.3.4. Configuring the License Server Machine(s)

If you did not complete the configuration tasks when you installed the license manager on your licenseserver machines, you should complete the steps below to register your license server information.

1. If you do not have a license file, follow these steps:

a. Open the ANSYS License Management Center. For Windows, click Start>All Programs>ANSYS,Inc. License Manager>ANSYS License Management Center and for Linux run the/shared_files/licensing/start_lmcenter script.

b. Click the Get System Hostid Information option to display your system ID code(s).

c. Select the system ID you wish to use and click SAVE TO FILE.

A text file containing your system ID information is created.

d. Forward this text file to your ANSYS sales representative so that a license file can be created foryou.

2. Add your license file(s)

Add your license files though the ANSYS License Management Center. For these steps, see Addinga License (p. 32).

If you are running in a three-server environment, the license file must reside on all three serversand must match on all three servers. Therefore, install the same license file on each machine.

2.3.5. Modify License Manager Startup Options

This ANSLIC_ADMIN utility option (Set Site Preferences>Modify Startup Options) writes an ansyslmd.inifile in the licensing directory. This file contains any changes to the default values as well as your licenseserver specifications and other settings (such as log file locations). Use this ANSLIC_ADMIN utility optionto change the default values.

For a detailed description of the settings that you can change with this option, see Modify StartupOptions (p. 66).



2.3.6. Create a Group (Linux Only)

You may want to create a group of users with specific usage capabilities, such as users with licensingadministrative privileges, or users who are authorized to shut down the license manager. An lmadmingroup is the most common type of group.

To specify a list of users with access to licensing administrative options, you need to create an lmadmingroup on computers from which license administration will be performed. If you create an lmadmingroup, you must include root in order for root to continue to have access to these functions. For moredetails on using an lmadmin group, see the FlexNet License Administration Guide (accessible from theANSYS License Management Center). This option is available for Linux platforms only.

Follow the instructions below for your hardware platform to create an lmadmin group.

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 listof n users in the group.

2.3.6.1. Defining Group Restrictions for the Licensing Interconnect

On Linux machines only, you can also specify who can shut down the ANSYS License Manager by usingthe 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 startedthe license manager will still be able to shut it down, even if he is not part of a group with shutdowncapabilities.

If you specify a group restriction, any users in that group who want to perform that operation musthave 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 userwho is a member of the lmadmin group and wants to shut down the license manager must havelmadmin as his primary group:

machineabc{user1}: groupsother testing dev1 lmadmin

In the above example, user1 is a member of the groups other, testing, dev1, and lmadmin, where otheris 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 licensemanager:

machineabc{user1}: groupslmadmin other testing dev1




2.3.7. Specify User Privileges

Establish user privileges by editing the FlexNet Options file. The options file allows you, the license ad-ministrator, to control various operating parameters of FlexNet:

• 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 license_files directory. If you have athree-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 thelicense file, unless it uses the default name, ansyslmd.opt, and resides in the same directory as thelicense file. On Linux systems, the VENDOR line would look like this for an options file named my.opt:

VENDOR ansyslmd options=/ansys_inc/shared_files/licensing/license_files/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\license_files\my.opt"

2.3.8. 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 duringthe product and license manager installations. Use the Specify the License Server Machine option ofthe Client 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 namedansyslmd.ini in the licensing directory. The ansyslmd.ini file contains your license server spe-cification. For more information on specifying the license server, see Specify the License Server Ma-chine (p. 59) in License Administration Using ANSLIC_ADMIN (p. 57).

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 > ANSYS17.1>ANSYS Client Licensing > Client ANSLIC_ADMIN Utility 17.1). If you have both the server andthe client ANSLIC_ADMIN utilities on the same system, use the Client ANSLIC_ADMIN to specify ma-chine-specific (local) settings.

If you want to set your license paths to have a particular license server machine for your use only (notused by others who are running ANSYS products on this machine), you can do so by setting the AN-SYSLI_SERVERS and/or ANSYSLMD_LICENSE_FILE environment variables. Use the ANSYSLI_SERVERSenvironment variable to specify the Licensing Interconnect port number. Use the ANSYSLMD_LI-CENSE_FILE to specify the FlexNet port number.

If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environmentvariable is not set, the same server machines will be used to specify the Licensing Interconnect but theport number will be replaced by the Licensing Interconnect default port of 2325. When both variables



are set, ANSYSLMD_LICENSE_FILE explicitly defines the FlexNet servers while ANSYSLI_SERVERS ex-plicitly defines the Licensing Interconnect servers.

2.3.9. Specifying Firewall Settings

If you use a firewall at your site and if you run ANSYS products outside the firewall but access the licenseserver within the firewall, you will need to add the Licensing Interconnect and FlexNet port numbersto 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: 2325FlexNet: 1055PORT designated by PORT=#### on the VENDOR LINE in the ansyslmd.lic file (see VENDORLines (p. 4) for information on this PORT number)

2.3.10. Setting Up Redundant (Triad) Servers

Redundant server setup is a network configuration where multiple machines are designated as licenseservers. 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 independentlicense server machines to achieve redundancy; however, if your site requires the use of three licenseserver machines working in tandem, follow the guidelines in this section to configure the servers.

1. Install the License Manager on each of the three servers as described in Installing the License Man-ager (p. 13). Be sure that each machine meets all of the prerequisites.

2. 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 1055SERVER myserver2 00132460b724 1055SERVER myserver3 001a246d4e64 1055

The first SERVER line is the license server you have designated as the primary server followed bythe 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 aquorum. Until you have a quorum of servers started, the ANSYS License Management Centerwill show the Licensing Interconnect and monitor running while FlexNet will show as not running.You could see a delay of up to five minutes in the startup of a server's FlexNet component whilethe communication between all three servers is being established. If a connection cannot be estab-lished within the five minutes, the Licensing Interconnect and Licensing Interconnect Monitor willstop. Check the ANSYS License Management Center to verify that all components have stoppedbefore you attempt to restart the ANSYS License Manager on any server.

To stop redundant servers, use the Stop the ANSYS, Inc. License Manager option of the ANSYS LicenseManagement Center to manually stop the License Manager on each server. The Stop the ANSYS, Inc.




License Manager option stops only the "local" instance of the License Manager, therefore it is necessaryfor you to stop each instance individually.

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 redundantsetup.

2.4. Uninstalling the License Manager

These instructions shut down and remove the entire ANSYS License Manager installation from yoursystem. You should not uninstall the license manager if you still have products installed that use thelicense manager.

The procedures described in this section assume that you have installed the ANSYS License Managerin the default locations. The default locations are:

Windows:

C:\Program Files\ANSYS Inc\

Linux:

/ansys_inc/

If you have installed the ANSYS License Manager to a non-default location, modify the steps accordingly.

Uninstalling on Linux License Servers

Follow these steps on the license server machine. You must be logged in as root or superuser.

1. Stop the ANSYS License Manager from the ANSYS License Management Center by following the stepscontained in Stopping the ANSYS License Manager (p. 34).

2. Stop any ANSYS Tomcat server processes running from this installation directory by running thestop_lmcenter script located in:

/ansys_inc/shared_files/licensing/

3. Delete the shared_files subdirectory (/ansys_inc/shared_files/ by default).

Note

Do not delete this directory if ANSYS products are also installed in the installation directory.

4. Remove the ANSYS License Manager automatic startup information by issuing the commands inTable 2.3: Removing License Manager Automatic Startup Instructions (p. 21).

5. Remove the Tomcat automatic startup information by issuing the commands in Table 2.5: RemovingTomcat Automatic Startup Instructions (p. 23).



Uninstalling on Windows License Servers

Follow these steps on the license server machine. All commands must be run in an administrator com-mand prompt window.

1. Stop the ANSYS License Manager from the ANSYS License Management Center by following the stepscontained in Stopping the ANSYS License Manager (p. 34).

2. Uninstall the ANSYS License Manager service. You must use the following command to do so:

"C:\Program Files\ANSYS Inc\Shared Files\Licensing\winx64\ansysli_server" -k uninstall

3. Uninstall the ANSYS Licensing Tomcat service. You must use the following commands to do so:

sc stop "ANSYSLicensingTomcat"sc delete "ANSYSLicensingTomcat"

4. Delete the Shared Files subdirectory (C:\Program Files\ANSYS Inc\Shared Files by default).

Note

Do not delete this directory if ANSYS products are also installed in the installation dir-ectory.

5. Remove the ANSYS License Manager folder from the Start menu.

6. Remove the ANSYSLIC_DIR and the ANSYSLIC_SYSDIR environment variables, if set.



Uninstalling the License Manager


Chapter 3: License Server Administration Using ANSYS LicenseManagement Center

This chapter explains how to use the ANSYS License Management Center (LM Center) to performmany of the procedures necessary to administer ANSYS licenses. The ANSYS License ManagementCenter is a browser-based user interface that centralizes many of the ANSYS licensing administrativefunctions. Basic license administration functionality has been incorporated into the ANSYS LicenseManagement Center; some advanced options remain in the ANSLIC_ADMIN utility. See Using the AN-SLIC_ADMIN Utility (p. 57) for more information on the ANSLIC_ADMIN utility.

Note

For Windows systems, ANSYS, Inc. requires that you have system administrator privileges tostart the ANSYS License Management Center. To use the ANSYS License ManagementCenter, you must access it from the local license server machine.

3.1. ANSYS License Management Center Browser Requirements

Supported Windows Browsers

• Internet Explorer 11 or greater

• Windows Edge Browser 20.10240.16384.0

• Firefox 41.0.1 or greater

• Chrome 45.0.2454.93 or greater

Note

ANSYS License Management Center uses your default browser when opening. Ifyou have not defined a default browser, ANSYS License Management Center attemptsto open using Windows Internet Explorer from the default installation location. IfWindows Internet Explorer is not installed in the default location, an error is reported.

Supported Linux Browsers

• Firefox 31.4.0 or greater

3.2. Accessing the ANSYS License Management Center

To open the ANSYS License Management Center:

Windows 7:



Click Start>All Programs>ANSYS, Inc. License Manager>ANSYS License Management Center

Windows 8:

1. From the Start screen, click the arrow located in the lower left portion of the screen to access the WindowsApps.

2. Scroll to find ANSYS, Inc. License Manager.

3. Click the ANSYS License Management Center option.

Linux

Run the start_lmcenter script located in the following directory:

ansys_Inc/shared_files/licensing/

3.3. Using the ANSYS License Management Center

The left side of the ANSYS License Management Center (LM Center) includes links accessing a varietyof licensing administration functions. Additionally, an icon informing you of the status of the ANSYSLicense Management Center is also located in the title bar. (Running is displayed as a green checkmark while Stopped is displayed as a red stop sign.)

The following sections provide instructions on how to perform the licensing administration functionsavailable through the ANSYS License Management Center:

3.3.1. Adding a License3.3.2. Starting the ANSYS License Manager3.3.3. Stopping the ANSYS License Manager3.3.4. Rereading the License Manager Settings3.3.5. Displaying the License Server Machine Hostid Information3.3.6.Viewing FlexNet Licenses3.3.7.Viewing the Licensing Interconnect Log3.3.8.Viewing the FlexNet Debug Log3.3.9.Viewing the ANSYS License Management Center Log3.3.10. Displaying the FlexNet License Status3.3.11. Gathering Diagnostic Information3.3.12. Specifying the License Manager Run Mode3.3.13. Accessing the Help Options

3.3.1. Adding a License

Important

When adding a license file, the Add a License File option in the ANSYS License Man-agement Center validates the new license file for the system, attempts to correct issuesthat it recognizes, and ensures port number consistency. For this reason, you must usethe ANSYS License Management Center to add license files, rather that manually placingthem in the license_files directory.

This option validates a user-specified license file and, if the license file is found to be valid, installs itinto the license_files directory. After installing the license file, this option communicates the new license


License Server Administration Using ANSYS License Management Center

file's information to the ANSYS License Manager either by starting /restarting the license manager orby rereading the license manager's settings.

The ANSYS License Manager supports both ANSYS and Electronics license files. ANSYS license filescontain the FlexNet vendor daemon ansyslmd and, after being installed, have the naming conventionansyslmd.lic. Electronics license files contain the FlexNet vendor daemon ansoftd and, after being installed,have the naming convention ansoftd.lic. Both ANSYS and Electronics license files contain the licensinginformation which allows you to run ANSYS, Inc. products.

If a vendor license file is already installed for the vendor contained in the license file you are installing,the previously-installed license file will be renamed to have the form license_<vendor>_<timestamp>.licand moved to the backup subdirectory in the license_files directory.

To add a license file:

1. Save the license file that you received from your ANSYS sales representative to a temporary file.

Caution

Do not save license files in Microsoft Word format.

2. Open the ANSYS License Management Center.

3. Click the Add a License File option.

The Add a License File page is displayed.

4. Click the Browse button.

5. Browse to locate the saved license file from step #1.

6. Select the license file and click Open.

7. If the selected license file is not valid, the process ends with the Status pane displaying an error messagecontaining details.

8. If the license file is valid, the Add a License File dialog box is displayed:

• If the ANSYS License Manager is not running, you are informed that it will be started when the li-cense file is added.

• If the ANSYS License Manager is running, you are given the option of either restarting it or rereadingthe license manager settings. For more information, see Rereading the License Manager Set-tings (p. 35)

9. Click the appropriate button.

The Status pane displays a message informing you of the steps taken successfully along with anyerrors that were encountered.

Special Considerations for Three Server (Redundant Triad) Environments

You must perform this process, using the same license file, on each license server machine.



Using the ANSYS License Management Center

3.3.2. Starting the ANSYS License Manager

In order for client machines to run licensed ANSYS products, the ANSYS License Manager must be runningon the license server.

To use the ANSYS License Management Center to start the license manager, ANSYS License Manage-ment Center (including the ANSYS Licensing Tomcat Server and the license manager) must be installedon the same computer. Additionally, a valid license file must be installed prior to starting the licensemanager.

To start the ANSYS License Manager:


2. Click the Start button located on the right side of the page.

The Status pane displays a message informing you whether the ANSYS License Manager startedsuccessfully or if any errors have been encountered. Additionally, a “green check mark” status iconis displayed indicating that the license manager is running.

Note

Every seven seconds, the ANSYS License Management Center verifies that the li-cense manager is running and updates the status icon.

The ansyslmd.lic and/or ansoft.lic file is provided by an ANSYS sales representative and containslicensing for all the ANSYS, Inc. products that you are entitled to use.


The ANSYS License Manager must be running on at least two of the three servers before an ANSYSproduct can be run.

In a three-server environment, you may see a delay in starting the ANSYS License Manager until twoof the three servers are running.

3.3.3. Stopping the ANSYS License Manager

The following procedure should be used to shut down the ANSYS License Manager on all machineslisted in the license file.

To stop the ANSYS License Manager:

Before shutting down the ANSYS License Manager, check that no products that use it are currentlyrunning.


2. Click the Stop button located on the right side of the page.

You are asked to confirm that the license manager should be shut down. Remember that the licensemanager must be running in order to run products that use it for their licensing.



The Status pane displays a message informing you whether the license manager stopped successfullyor if any errors have been encountered. Additionally, a “red stop sign” icon is displayed indicatingthat the license manager is no longer running.

Caution

(Linux systems) Do not use kill -9 to shut down the ANSYS License Manager. Use the ANSYSLicense Management Center, the anslysli_stop script or ansysli_server -kstop [port@host] to perform the shutdown.


In a three-server environment, you may see a delay in stopping the license manager until two of thethree servers are stopped.

3.3.4. Rereading the License Manager Settings

Use this option to reread the license manager settings. This option should be used when you havemade changes that will affect the license manager and want to incorporate these changes withoutstopping and restarting the license manager.

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 Licensing Interconnect log file

• Rereads the site license preferences

• Recaches the installed license files

• Issues a FlexNet 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 licensemanager; a reread will not update the port number.

Note

If you chose to configure your license manager to run the Licensing Interconnect withoutFlexNet or run the Licensing Interconnect and FlexNet independently, then selecting thisoption will affect only the Licensing Interconnect components including recaching the licensefile when running the Licensing Interconnect and FlexNet independently.

To reread the License Manager:


2. Click the Reread License Manager Settings option.




3. Click the Reread button.

The Status pane displays a message informing you whether the ANSYS License Manager's settingswere successfully reread.

3.3.5. Displaying the License Server Machine Hostid Information

Use this option to obtain and display the FlexNet hostid of the machine you wish to create licenses forand set up as a license server.

If you wish to use a FLEXID9 dongle as the hostid, make sure the device is inserted and the correctdevice driver is installed. For more information, see Using Dongles with the ANSYS License Man-ager (p. 71). Dongles are only available for those sites that require the ability to run ANSYS productson an isolated network.

Accessing the Hostid


2. Click the Get System Hostid Information option.

The hostid information is displayed on the right-hand side of the page. The HOSTNAME,Hostid, IDTYPE and PLATFORM information is included. Windows systems use the physicalmachine disk serial number and Linux systems use the MAC address by default.

3. To save this information out to a file, click the SAVE TO FILE button. By default, the file is named an-sysid.machinename.txt.

3.3.6. Viewing FlexNet Licenses

Use this option to view the FlexNet license files. You can view license files that are in use (or will be inuse) in the ANSYS License Manager.


2. Click the View FlexNet Licenses option.

A field containing the name of one of your FlexNet license files is displayed.

3. Select the FlexNet license file you want to view by clicking the arrow located on the right side of the fieldand choosing the appropriate file from the drop-down menu. Note the drop-down menu is populated withany FlexNet license files (.lic) contained in the following directory:

Windows:

\Program Files\ANSYS Inc\Shared Files\Licensing\license_files

Linux:

/ansys_inc/shared_files/licensing/license_files

4. The contents of the FlexNet license is displayed on the right side of the page.



3.3.7. Viewing the Licensing Interconnect Log

Use this option to view the Licensing Interconnect log file (named ansysli_server.log by default).The Licensing Interconnect log file contains all of the actions that the ANSYS license server has takensince startup.

Accessing the Licensing Interconnect Log


2. Click the View Licensing Interconnect Log option.

The Licensing Interconnect log file is displayed on the right side of the page.

3. To download a text version of the interconnect debug log file, click the SAVE TO FILE button.

4. To manually refresh the Licensing Interconnect log file, click the REFRESH button.

Note

The Licensing Interconnect log file does not automatically refresh.

The Licensing Interconnect log file (ansysli_server.log) can be found in the “licensing” directory. Tomanually access this file, go to the following locations (by default):

Windows:

\Program Files\ANSYS Inc\Shared Files\Licensing\ansysli_server.log

Linux:

/ansys_inc/shared_files/licensing/ansysli_server.log

3.3.8. Viewing the FlexNet Debug Log

Use this option to view the FlexNet license log file (named license.log by default). The FlexNetdebug log includes the following message types:

• General informational messages describing the current status of FlexNet features

• Messages describing configuration issues

• License manager error messages associated with the FlexNet component of the license manager.

Accessing the FlexNet Debug Log


2. Click the View FlexNet Debug Log option.

The FlexNet debug log is displayed on the right side of the page.

3. To download a text version of the FlexNet debug log, click the SAVE TO FILE button.




4. To manually refresh the FlexNet debug log, click the REFRESH button.

Note

The FlexNet debug log does not automatically refresh.

The FlexNet debug log (license.log) can be found within the “licensing” directory structure by default.To manually access this file, go to the following location:

Windows:

\Program Files\ANSYS Inc\Shared Files\Licensing\license.log

Linux:

/ansys_inc/shared_files/licensing/license.log

3.3.9. Viewing the ANSYS License Management Center Log

Use this option to view the ANSYS License Management Center log (named ansyslmcenter.logby default).

Accessing the ANSYS License Management Center Log


2. Click the View License Management Center Log option.

The ANSYS License Management Center log is displayed on the right side of the page.

3. To download a text version of the ANSYS License Management Center log, click the SAVE TO FILE button.

4. To manually refresh the ANSYS License Management Center log, click the REFRESH button.

Note

The log does not automatically refresh.

The ANSYS License Management Center log (ansyslmcenter.log) can be found within the “licensing”directory structure. To manually access this file, go to the following location:

Windows:

\Program Files\ANSYS Inc\Shared Files\Licensing\tools\lmcenter\logs\ansyslmcenter.log

Linux:

/ansys_inc/shared_files/licensing/tools/lmcenter/logs/ansyslmcenter.log

3.3.10. Displaying the FlexNet License Status

Use this option to display the FlexNet licensing activity (lmstat). The license server information, vendordaemon status and license usage information are displayed in the status window, along with the usersof those features.



Viewing the FlexNet License Status


2. Click the Display FlexNet License Status option.

The FlexNet license status is displayed on the right-hand side of the page.

3.3.11. Gathering Diagnostic Information

This option gathers various licensing-related files, logs and information about your license server systemand places them in a single compressed file. This information is useful when requesting support for theANSYS License Manager.

Note

On Windows, this process may take a few minutes when msinfo32.exe is running.

Using the Gather Diagnostic Information option:


2. Click the Gather Diagnostic Information option.

3. Click the SAVE TO FILE button.

The ANSYS License Management Center begins to collect the files and information. After the col-lection process is complete, all files that are found and included in the compressed file are listed.

4. Based upon how your default browser is configured, you will either be prompted for a location to save thecompressed file or the compressed file will be automatically saved to your pre-defined location.

3.3.11.1. Gathering Diagnostic Information outside of ANSYS License ManagementCenter

If you are unable to access the ANSYS License Management Center but still wish to gather diagnosticinformation about your server system, you can run the gatherdiagnostics script located in thefollowing directory:

Windows:

\Program Files\ANSYS Inc\Shared Files\Licensing\

Linux:


On Windows you must run this script from an administrator command line (do not double click thebatch file). Running this script from a command line produces a single compressed file. This file containsthe same licensing related files, logs and information produced by running the Gather Diagnostic In-formation option within the ANSYS License Management Center.




3.3.12. Specifying the License Manager Run Mode

This option specifies how the ANSYS Licensing Interconnect is administered in conjunction with FlexNet.In addition to the default configuration (Run the ANSYS Licensing Interconnect with FlexNet) whichshould satisfy most users, ANSYS, Inc. offers two advanced licensing configuration “modes”:

Run the ANSYS Licensing Interconnect without FlexNet –Use this option if you want to run a localcopy of the ANSYS Licensing Interconnect on another machine in addition to the Licensing Interconnectbeing run on the license server machine. Your site must still have the Licensing Interconnect and FlexNetrunning on the license server machine. With this option, FlexNet licenses will be taken from anotherserver machine. Note that this is not the default way to set up an ANSYS license server machine andshould be done only if it has been determined that you need this special type of setup. Examples ofwhen this special type of setup might be used include increasing performance if your server machineis in a remote location or managing the server load better if your license server machine serves manyusers.

Run the ANSYS Licensing Interconnect and FlexNet independently –Use this option if you want tomanage FlexNet Licensing independently of the ANSYS Licensing Interconnect. In this option, you wouldcontinue to manage the ANSYS Licensing Interconnect via the ANSYS License Management Center andFlexNet Licensing would be managed via another tool, such as Flexera Software's FlexNet Manager.Note that this is not the default way to set up an ANSYS license server machine and should be doneonly by experienced users with well-established licensing procedures.

These options are available for license server machines via the ANSYS License Management Center’sSpecify License Manager Run Mode option only after an ANSYS License Manager installation has beenrun on this machine.

Specifying the ANSYS License Manager run mode:

Caution

Changing the run mode will cause the ANSYS License Manager to be shut down and restarted.


2. Click the Specify License Manager Run Mode option.

The License Manager Run Mode Specification page, containing each of the run modes, is displayed.

Note

The default run mode is Run the ANSYS Licensing Interconnect with FlexNet.

3. Select the run mode you want to use.



4. Click the SUBMIT button to change the run mode.

Note

Clicking any option that is not relevant to your current run mode will cause ANSYSLicense Management Center to display a page informing you that this option isnot supported by the current run mode.

3.3.13. Accessing the Help Options

The ANSYS License Management Center “Help” options give you access to documentation and relatedproduct information.

The Help options are:

• View ANSYS Licensing Guide: This option accesses the current PDF version of the product manual.

• View FlexNet Licensing Guide: This option accesses the current PDF version of the FlexNet Publisher LicenseAdministration Guide.

• View Licensing Configuration Details: This option displays the version numbers and file locations forANSYS License Management Center related options (Java, Tomcat, FlexNet, etc.).

• About License Management Center: The option includes the ANSYS License Management Centerproduct information (version number, copyright, etc.).

3.4. Enabling Secure Connections to the Web Server (Optional)

This section presents instructions for enabling secure connections to ANSYS License ManagementCenter (LM Center), using a Tomcat web server.

When communications between the client browser and the front-end web server need to travel overan untrusted network such as the Internet, it is highly advisable to use secure connections betweenthe client browser and the front-end web server. SSL, or Secure Socket Layer, is a technology which allowsweb browsers and web servers to communicate over a secured connection. Data is encrypted by eachcommunicator, transmitted and then decrypted by the other communicator. Additionally, the SSL protocolauthenticates credentials during your initial attempt to communicate over the secure connection.

3.4.1. Understanding Certificates

When implementing SSL, a web server must have an associated Certificate for each external interface(IP address) that accepts secure connections. This provides a level of identity assurance during commu-nication. The certificate is cryptographically signed by its owner, and is therefore extremely difficult foranyone else to forge.

SSL/TLS certificates are typically purchased from well-known Certificate Authorities (CA) such as VeriSignand Thawte. Using a certificate from a well-established and widely recognized CA confers several benefitsto the web server operator. These include increased credibility and convenience because the root cer-tificates for popular CAs are prepackaged into major browsers, eliminating the need to distribute anythingto client browsers that will connect to the web site.



Enabling Secure Connections to the Web Server (Optional)

If a web server is to be used solely internally within an organization, then the benefits of using a certi-ficate from a well-recognized Certificate Authority may not be important. Any valid SSL/TLS certificatecan be used to encrypt traffic between client browser and web server as long as the client browseraccepts the certificate. For internal production use, and certainly for test use, it is often sufficient tocreate and use an in-house Certificate Authority that can sign SSL/TLS certificates for these use cases.

A certificate that is signed by the same party that created it is known as a self-signed certificate. Whenan internally-generated certificate is signed using an in-house Certificate Authority, then a self-signedcertificate is created. Self-signed certificates are perfectly usable for enabling HTTPS connections to aweb server. However, when a browser encounters a certificate that has been signed by an unknowncertificate authority, it will present the user with a warning, such as the following:

Once a user accepts the certificate, the HTTPS connection can proceed.

3.4.2. Configuring Tomcat Using Keytool

In cases where authenticity may be less of a concern but privacy is necessary, Java provides a relativelysimple command line tool called “keytool”. Keytool can create a simple, user-generated “self-signed”certificate. The following instructions describe how to configure keytool and Tomcat for SSL. We recom-mend that you read the Preparing the Certificate Keystore and Editing the Tomcat Configuration Filebefore beginning the configuration.

3.4.2.1. Preparing the Certificate Keystore

Tomcat currently operates only on JKS, PKCS11 or PKCS12 format keystores. The JKS format is Java'sstandard "Java KeyStore" format, and is the format created by the keytool command-line utility. Thistool is included in the JDK and is what can be set-up using ANSYS supplied tools. The PKCS12 formatis an internet standard, and can be manipulated via (among other things) OpenSSL and Microsoft's Key-Manager.

Using the keytool command line, create the keystore file as follow:



Go to the tools directory in your installation and execute the following platform specific commands:

Windows

cd "C:\Program Files\ANSYS Inc\Shared Files\licensing\tools"

Run the following command to create the file tomcat\conf\keystore:

java\winx64\bin\keytool.exe -genkey -alias tomcat -keyalg RSA -keystoretomcat\conf\keystore

Linux

cd /ansys_inc/shared_files/licensing/tools

Run the following command to create the file /licensing/tools/tomcat/conf/keystore:

java/linx64/bin/keytool -genkey -alias tomcat -keyalg RSA -keystore tom-cat/conf/keystore

3.4.2.2. Editing the Tomcat Configuration File

Tomcat can use two different implementations of SSL:

• JSSE implementation provided as part of the Java runtime (since 1.4)

• APR implementation, which uses the OpenSSL engine by default

The JSSE implementation can be set-up using ANSYS supplied tools.

To configure the server.xml file using JSSE do the following:

Go to the licensing/tools/tomcat/conf directory in your installation and edit the server.xml file by adding:

<Connector protocol="org.apache.coyote.http11.Http11NioProtocol" port="8443" maxThreads="150" scheme="https" secure="true" SSLEnabled="true" keystoreFile="conf/keystore" keystorePass="changeit" keyPass="changeit" clientAuth="false" sslProtocol="TLS" />

where "changeit" is the password you specified when you created the keystore file above.

You can now use ANSYS License Management Center with HTTPS by restarting your ANSYS LicensingTomcat service and pointing to https://localhost:8443/ANSYSLMCenter.html.

To use the HTTPS secure connection exclusively:

1. Open the server.xml file in the licensing/tools/tomcat/conf directory

2. Remove or comment out the following 1084 connector entry:

<Connector port="1084" protocol="HTTP/1.1" connectionTimeout="20000" compression="on" address="127.0.0.1" compressionMinSize="2048" noCompressionUserAgents="gozilla, traviata"



Enabling Secure Connections to the Web Server (Optional)

compressableMimeType="text/html,text/xml" redirectPort="8443" />

3.5. Changing the Version of Java Used by ANSYS License ManagementCenter

In some scenarios, it may be desirable to use a version of Java other than the version that was shippedand installed with ANSYS License Manager. This section contains instructions for changing the Javaversion used by ANSYS License Management Center.

Note

Changing the version of Java is only possible when the Java version is newer than theversion supplied as part of the ANSYS installation.

3.5.1. Changing the Java Version During a New Installation of ANSYS LicenseManager

Windows or Linux:

1. Prior to performing the ANSYS License Manager installation, set the following environment variable topoint to the location of the Java version you want to use.

ANSYSLM_USER_JAVA_HOME

2. Run the ANSYS License Manager installation.

3.5.2. Changing the Java Version on an Existing Installation of ANSYS LicenseManager

Windows:

1. Set the following environment variable to point to the location of the Java version you want to use.


2. As an administrator, re-run the ANSYS License Manager installation or run ansyslm_config.exe -usemyjava .

By default, ansyslm_config.exe is located in:

C:\Program Files\ANSYS Inc\Shared Files\Licensing\tools\bin\winx64\

Note

When running this command on Windows 8.1, the message "Qt: Untested Windows version6.2 detected!" may be displayed. You can safely ignore this message.

Linux:

1. Set the following environment variable to point to the location of the Java version you want to use.




2. Stop any active version of Tomcat by running the stop_lmcenter script.

3. Run the start_lmcenter script to configure Tomcat to use your version of Java and start Tomcat.

Both the start_lmcenter script and the stop_lmcenter script are located in:




Changing the Version of Java Used by ANSYS License Management Center


Chapter 4: End-User Settings

End users can set several controls for a customized licensing environment. These controls are explainedin this chapter.

4.1. Client Environment Variable Settings

You can set the following environment variables on individual machines to control their behavior, espe-cially if you need it to be different from the general site configuration. These settings are especiallyuseful for situations where you are testing a new product installation/license manager installation ona single machine before full site deployment, or other similar situations.

ANSYSLMD_LICENSE_FILECan be used to identify a license server machine or license file. If set, this specification is used beforeany other license path information. See License Files Settings Precedence (p. 48) for precedence in-formation. The default port number assigned to ANSYS, Inc. is 1055. Therefore, if your server has thehostname alpha1 and the IP address of 10.3.1.69, you can identify the server to use as 1055@alpha1or [email protected].

ANS_FLEXLM_DISABLE_DEFLICPATHIndicates that the default license path should not be searched when determining the licensing pathin the ANSYS product. When this environment variable is set:

• Only ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS environment variable settings are used.

• Only the ANSYSLMD_LICENSE_FILE environment variable setting is required.

• Settings in the ansyslmd.ini file and the license file in the licensing directory will NOT be used.It will ignore the local server and will ignore the Specify the License Server setting.

ANSYSLI_SERVERSUsed to identify the server machine for the Licensing Interconnect. Set to port@host. The defaultport is 2325. This setting takes precedence over settings specified in the ansyslmd.ini file.

ANSYSLI_TIMEOUT_CONNECTUsed to specify the amount of time that elapses before the client times out if it cannot connect tothe server. Default is 20 seconds. Minimum timeout period you can specify is 5 seconds and themaximum is 60 seconds. If the client determines that a server is not available in less time, it will cancelimmediately.

ANSYSLI_TIMEOUT_TCPUsed to specify the amount of time that elapses before the client times out if it cannot get a responsefrom the server. This setting applies only when the license server is running but is responding slowly(generally because of network issues or server load). Default is 60 seconds. Minimum timeout periodyou 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. ANSYSLI_SERVERS environment variable

2. If ANSYSLI_SERVERS is not set, use ANSYSLMD_LICENSE_FILE environment variable, replacing theFlexNet port number with the default Licensing Interconnect port number of 2325.

3. Settings in the ansyslmd.ini file in the relative client licensing directory for ANSYSLI_SERV-ERS=keyword

FlexNet settings have precedence in the following order:

1. ANSYSLMD_LICENSE_FILE environment variable

2. Settings in the ansyslmd.ini file in the relative client licensing directory for SERVER=keyword.

Note

The FlexNet environment variable LM_LICENSE_FILE is not supported with the ANSYS LicenseManager.

4.2. Establishing User Licensing Preferences

Before running ANSYS, Inc. products, you should establish your licensing preferences, especially if youhave multiple licenses at your site. Use the Set License Preferences for User option of the ANSLIC_AD-MIN utility or choose Start > All Programs > ANSYS 17.1 > ANSYS Client Licensing > User LicensePreferences 17.1 to set your own licensing preferences. Note, preferences specified with this optionapply only to you on the computer system on which the option was run and will not affect other usersat your site.

You can use this option to review the licenses available, prioritize the licenses, and establish which li-censes you will use. When you select this option, a dialog box opens. All licenses available to you onyour 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 upand down in the list using the Move Up or Move Down buttons. When you open an application, thelicense 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 theapplication. The license manager will continue through the list until an available license is found. Ifnone are found, a message displays.


End-User Settings

By default, all licenses available from your license server are shown and marked as available for use. Ifyou do not want a particular license to be available for your use, select the license in the list, and setthe 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 yourlicense 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 stateby selecting the Reset to Default button.

When you have completed your changes, click OK to make the changes and close the dialog box. ClickApply to make the changes without closing the dialog box. Selections you make here will take effectwith any new sessions/license checkouts but will not affect the current session or change the license(s)currently in use.

If you are sending solve jobs to a remote compute cluster via Remote Solve Manager (RSM), note thatyour license preferences set for your local machine (the RSM Client) may not be the same as the licensepreferences set for the remote cluster machine (the Compute Server). In cases where local and remotelicense preferences are different, the preferences for the local RSM Client machine will not be appliedwhen running on the remote Compute Server; instead, the preferences defined for the remote ComputeServer will be used. If the license preferences and/or the licensing checkout order do not make thenecessary licenses available to your remote solve, you must adjust the Compute Server preferences bysetting your license preferences on the remote machine. Remote license preferences may be definedaccording to corporate IT policy, so see your license administrator about adjustments to ComputeServer 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 17.1:

• 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 17.1 > ANSYS Client Licensing> User License Preferences 17.1) to specify which method to use and which licenses to use. You mustspecify the licensing method before starting an ANSYS Workbench session. If you access the LicensingPreferences dialog box from the ANSYS Workbench Tools menu, you will not be able to choose a licensingpreference from there.

Single License Sharing ANSYS Workbench allows you to work across multiple applications andworkspaces in ANSYS Workbench while consuming only one of a single type of license per user persession. Using shared licensing, the active application holds the license, preventing other applicationsthat are sharing that license from using it during that time. The application or operation requiring useof the license is called a concurrency event. For example, meshing and solving would each be a concur-rency event.

Single license sharing allows you to progress through your analysis, from specifying engineering datathrough 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,



Establishing User Licensing Preferences

an application cannot release a license in the middle of a solve operation; the license cannot be releaseduntil the solve operation is completed).

Single license sharing applies only to licenses of the same type (e.g., Mechanical). Choosing this optiondoes not affect your ability to use licenses of different types simultaneously (e.g., Mechanical for onetask 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 possibleto use both a Mechanical and an Emag license within a single ANSYS Workbench session. It is alsopossible 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 capabilitiesare being requested. For all applications other than the first (subsequent) one opened (within ANSYSWorkbench), ANSYS licensing will first look at what other licenses are opened within this session. Thesesubsequent license requests will look at sharing first to satisfy their request: do any other licenses beingused within this session fulfill the needed capabilities? If yes, share an existing license. If not, preferencesare used and a new, different license is checked out.

Example 1: You have one license for Multiphysics and one license for Mechanical, with Multiphysicslisted 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 bechecked out. The second application starts and needs Multiphysics; since Multiphysics is already checkedout, the second application will share it with the first. Only the Multiphysics license is consumed in thissession.

Example 2: You have one license for Multiphysics and one license for Mechanical, with Mechanical listedfirst 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 Mul-tiphysics; 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 (forexample, 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 licenseif those applications require capabilities not supported by the license. For example, you cannot sharea Mechanical license with a Fluent application.

Single License Sharing in ANSYS Workbench Applications ANSYS Workbench applications handlesingle license sharing differently:

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 andwill release the license as soon as the operation is completed. For example, when you mesh, theMeshing component will control the license during the meshing operation and then immediatelyrelease the license when the operation is completed. The other components will remain in a read-


End-User Settings

only mode while Meshing uses the license, allowing you to view the data in other components butnot operate on it.

Note

Applications in read-only mode because of shared licensing do not refresh their li-cense status automatically. Once the shared license is released by the editor thathad consumed it, you must trigger Mechanical to query the license status. The moststraightforward way to do this is click outside the Mechanical application windowand 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 eitherclose the application or issue a PAUSE command at the Mechanical APDL command line. PAUSE allowsyou to temporarily release the license for another application to use. No other operation other thanSAVE or /EXIT is permitted while PAUSED. When the second application has finished and releases thelicense, issue an UNPAUSE command from the Mechanical APDL command line to resume its use ofthe license.

CFX, Fluent, Autodyn, Polyflow:These applications consume a license when launched and retain the license until they receive a requestfrom another application to release it. For example, if you open CFX-Pre, CFX-Pre will obtain andcontrol 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 interruptAutodyn or Polyflow and release the license, temporarily, for another application to use.

Separate Licenses By using the separate-licenses method, ANSYS Workbench requires a separatelicense for each application. By using this method, you can move freely between the many applicationsthat 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 disad-vantage 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 theLicensing Preferences dialog box (Start > All Programs > ANSYS 17.1 > ANSYS Client Licensing >User License Preferences 17.1). You must specify the licensing method before starting an ANSYSWorkbench session.

Examples of Using Separate Licenses You have two Mechanical licenses. When you open and meshor solve a model in the Mechanical application, you consume one Mechanical license. If you link thatMechanical analysis to a Mechanical APDL system, you would consume a second Mechanical licensewhen you launch the Mechanical APDL application, if you have not closed out of the Mechanical applic-ation. Neither of these licenses would then be available for other users until you closed out of one orboth of the applications.

4.2.2. HPC Licensing

ANSYS, Inc. offers multiple high performance computing license options, described below. These licenseoptions 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 processingoptions 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 Pack licenses in the same analysis solution.

See the applicable product documentation for instructions on configuring and running a distributedsolution.

Notes on utilizing GPU acceleration:

• GPU acceleration is allowed when using either ANSYS HPC Licenses or HPC Pack Licenses with theMechanical APDL, Mechanical, Polyflow or Fluent applications.

• GPU acceleration is available on 64-bit Windows and Linux x64 systems only.

• For more information on GPU acceleration, see GPU Accelerator Capability in the Mechanical APDLParallel Processing Guide and GPU Accelerator Capability in the Polyflow User’s Guide .

ANSYS HPCThese physics-neutral licenses can be used to run multiple analysis jobs across multiple processors andwork with most ANSYS, Inc. applications. The Mechanical APDL, Mechanical and Fluent applications canutilize any combination of CPU and GPU processors. Other applications are limited to CPU processors only.Contact your ANSYS sales representative for a complete list of applications that can be used with ANSYSHPC.

The Mechanical APDL application allows you to use two non-GPU processors without using anyHPC licenses; ANSYS HPC licenses add to this base functionality. For example, a Mechanical APDLuser 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, ANSYSHPC licenses are not subject to single license sharing as described in ANSYS Workbench LicensingMethods (p. 49).

You cannot combine ANSYS HPC licenses with any other type of HPC licenses, including HPC PackLicenses, in the same solution.

ANSYS HPC licenses are not valid with academic products; instead, use the appropriate ANSYSAcademic HPC license.

ANSYS HPC Pack LicensesThese physics-neutral licenses can be used to run a single analysis across multiple processors and workwith most ANSYS, Inc. applications. Contact your ANSYS sales representative for a complete list of applic-ations that can be used with ANSYS HPC Pack Licenses. ANSYS HPC Pack Licenses enable parallel for singlesimulations according to the following schedule:

• 1 ANSYS HPC Pack License per simulation: Combined CPUs and GPUs not to exceed 8

• 2 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 32





End-User Settings

• 6 ANSYS HPC Pack License per simulation: Combined CPUs and GPUs not to exceed 8192









You cannot use more than 14 HPC Pack Licenses on a single analysis. Individual HPC Pack Licensescannot be split between multiple users or between multiple analyses.

Mechanical APDL allows you to use two processors without using any HPC licenses; ANSYS HPCPack licenses function independently of this base capability. For example, a Mechanical APDL simu-lation using a single ANSYS HPC Pack License can access up to eight processors (or cores), as notedabove, and not ten processors (or cores).

HPC Pack Licenses do work with ANSYS Workbench's Remote Solve capability; however, HPC PackLicenses are not subject to single license sharing as described in ANSYS Workbench LicensingMethods (p. 49).

You cannot combine ANSYS HPC Pack Licenses with any other type of HPC licenses, including ANSYSHPC 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 HPClicenses cannot be borrowed.

Mechanical HPC, CFX Parallel Computing, CFD HPC, etc. LicensesThese physics-specific licenses will continue to work. The Mechanical APDL application allows you to usetwo processors without using any HPC licenses; Mechanical HPC licenses accommodate this feature. Forexample, 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, includingANSYS HPC or HPC Pack Licenses, in the same solution.

4.2.2.1. Specifying HPC License Order

Use the HPC tab in the User License Preferences 17.1 dialog box to define the order in which HPC li-censes are used. By default, the physics-neutral HPC licenses are listed before the physics-specific HPClicenses. If you want to change the order, select licenses and click the Move up or Move down buttonto reorder the list.




4.2.3. HPC Parametric Pack Licensing

ANSYS, Inc. offers additional license options called HPC Parametric Packs for ANSYS Workbench jobsrequiring multiple design point updates. HPC Parametric Packs enable you to simultaneously updatemultiple design points of a single design study while using only a single license of each required baselicense. You must use the ANSYS Workbench reserved licensing feature to use HPC Parametric Pack li-censes.

HPC Parametric Packs enable a specific number of simultaneous design points, as follows:

• 1 HPC Parametric Pack: 4 simultaneous design points

• 2 HPC Parametric Packs: 8 simultaneous design points




You can use a maximum of five HPC Parametric Pack licenses per design study.

HPC Parametric Packs also work in conjunction with ANSYS HPC and ANSYS HPC Pack Licenses. Use theHPC licenses to enable multiple parallel processes to be used for each design point.

For more details on working with HPC Parametric Pack licenses in ANSYS Workbench, see Using HPCParametric Pack Licenses in the Workbench User's Guide.

Additional Restrictions HPC Parametric Pack licenses have the following additional restrictions:

• HPC Parametric Pack licenses apply to specific ANSYS, Inc. commercial licenses only; see your ANSYS, Inc.sales representative for a complete list of applicable licenses.

• HPC Parametric Pack licenses are supported only on platforms supported by ANSYS Workbench.

• HPC Parametric Pack licenses are not supported for Explicit Dynamics.

• HPC Parametric Pack licenses are not available for borrowing.

• HPC Parametric Pack licenses do not work with ANSYS Academic products.

• HPC Parametric Pack licenses do not interact with Ansoft licenses hosted in ANSYS Workbench.

4.3. Setting Up License Queuing

The License Queuing option allows an ANSYS process to wait (queue) for an available license in theevent all licenses are checked out. Activate this option by setting the environment variable ANSWAITto 1.

If the ANSWAIT environment variable is not set, then the ANSYS process will terminate with the followingmessage 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 and may not work as expected withjob scheduling software.


End-User Settings

4.4. Borrowing Application Licenses on Windows

License borrowing (available only on Windows machines) allows a user to take a license for use outsideof the company facility, such as for an engineer to take a license home on his laptop. Before users cantake advantage of license borrowing, the site administrator needs to set up the borrowing environment(see Run the ANSYS Borrow Utility (p. 63)).

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 li-censes is also a license server from which you could normally use licenses, you would be able to useonly the borrowed licenses. You can borrow only one task of any particular license.

This option is available only for the client version of ANSLIC_ADMIN.

1. Connect to the network where the license server machine is running.

2. Launch the client license borrowing utility: Start > All Programs > ANSYS 17.1 > ANSYS Client Licensing> Client ANSLIC_ADMIN Utility 17.1. Select Run the ANSYS Borrow Utility.

3. On the Borrow tab, specify the version number and return date. The return date defaults to the third dayfrom 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 thecorrect version.

5. Click Borrow.

6. Disconnect from the network. Note that even when you've disconnected from the network, you must stillrun the products from the same account you used to borrow the licenses. For example, if you use a networkaccount 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 machineAFTER you've disconnected from the network. If you encounter any difficulties, reconnect to thenetwork, 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. Yourborrowed license will simply expire at the end of the borrow period, and the license will be releasedinto the pool of available licenses.

To return a license early:

1. Reconnect to the same license server from which you borrowed the license(s).

2. Launch the client license borrowing utility: Start>All Programs> ANSYS 17.1> ANSYS Client Licensing>Client ANSLIC_ADMIN Utility 17.1. Select Run the ANSYS Borrow Utility.

3. Select the Return tab. Click Return all. If you want to keep some but not all of the licenses you borrowed,you will need to re-borrow them.



Borrowing Application Licenses on Windows

4. 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 licensesoriginally.

Some multi-feature products include other products and/or add-on features. The utility will automaticallycheck out any such included products or add-on features. If you borrow one of these multi-featureproducts and then click on the Return tab, you will see the product you selected, as well as any otherproducts and add-ons that it includes. If you return a multi-feature product early, these products andadd-on features will also be returned.


End-User Settings

Chapter 5: License Administration Using ANSLIC_ADMIN

For basic license administration, use the ANSYS License Management Center (LM Center). (See LicenseServer Administration Using ANSYS License Management Center (p. 31) for more information). Someof the more advanced options have not yet been migrated. This chapter explains how to use the AN-SLIC_ADMIN utility to perform many of the advanced procedures necessary to administer licenses.

On Windows license server machines, you will have access to a server (full) version of the ANSLIC_ADMINutility and an additional client version. The option descriptions below note which options are availableon 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 directorythat resides at <os drive>\Program Files\ANSYS Inc\Shared Files\Licensing bydefault. The Server ANSLIC_ADMIN offers access to all options and should be used to administer all li-censes across a site that use that machine as a license server machine. Changes made using the ServerANSLIC_ADMIN utility will affect all users who use that machine as a license server machine, whereappropriate. Note that settings such as Specifying the License Server Machine are always local settingsand 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 17.1 > ANSYS ClientLicensing > Client ANSLIC_ADMIN Utility 17.1 and updates the ansyslmd.ini file in the licensingdirectory that resides with the product installation. The Client ANSLIC_ADMIN utility should be usedonly to make changes to that local machine's configuration. Changes made using the Client ANSLIC_AD-MIN utility will affect only this machine and will not affect other users.

On Linux machines, you can access only the full version of ANSLIC_ADMIN; no client version is available.

Some options may apply to Linux or Windows systems only and are so noted.

See Advanced Licensing Configuration Options (p. 19) for details on configuring your license server touse LMTOOLS or FLEXNet Manager to manage FlexNet. For more information on advanced FlexNetoperations, open the ANSYS License Management Center and select View FlexNet Licensing Guide.

5.1. Using the ANSLIC_ADMIN Utility

To run ANSLIC_ADMIN on Windows, choose Start> All Programs> ANSYS License Manager> ServerANSLIC_ADMIN Utility (for the server version) or Start > All Programs > ANSYS 17.1 > ANSYS ClientLicensing > Client ANSLIC_ADMIN Utility 17.1 (for the client version). To run the utility on Linux, typethe following:

/ansys_inc/shared_files/licensing/lic_admin/anslic_admin

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



On 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 ANSYSLicensing Interconnect log file. Use the language directory name in the language subdirectory of thelicensing directory (en-us, fr, de, etc.) as the language value. This option is valid only with theserver 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 ANSYSLicensing Interconnect. Verify with your licensing system administrator before making thischange.

To change the language setting locally for only the current session of the server or client ANSLIC_ADMINutility, 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

Windows 7 Administrator Privileges On Windows 7 machines, you need to always run these AN-SLIC_ADMIN options as an administrator, preferably with UAC turned off. If UAC is on, even as admin-istrator, you must right-mouse click on the ANSLIC_ADMIN selection from the Start menu and chooseRun as administrator.

Windows 8.1 Administrator Privileges On Windows 8.1 machines, you need to always run theseANSLIC_ADMIN options as an administrator. Additionally, you should right-mouse click on the AN-SLIC_ADMIN selection from the Start menu and choose Run as administrator.

See the User Account Control (UAC) section of the ANSYS, Inc. Windows Installation Guide for moredetails on working with Windows and UAC.

We do not recommend running the ANSLIC_ADMIN on Windows machines by double-clicking the ex-ecutable directly, especially on Windows 7 or 8 systems. Doing so could launch the utility with unexpectedpermission levels.

To use the utility, select an action from the list of buttons on the left.

The ANSLIC_ADMIN utility consists of the following options:

• Launch the ANSYS License Management Center (p. 59) (Server Option)

• Specify the License Server Machine (p. 59)

• Set License Preferences for User (p. 62)

• Run the ANSYS Borrow Utility (p. 63) (Windows only) (Client Option)

• Set Site Preferences (p. 65) -- includes the following options:

– Specify Product Order (p. 65) (Server Option)


License Administration Using ANSLIC_ADMIN

– Modify Startup Options (p. 66) (Server Option)

– Specify License Servers to Cache (p. 67) (Server Option)

• View Status/Diagnostic Options (p. 68) -- includes the following options:

– Display the License Status (p. 68)

– Display Queued Licenses (p. 68)

– Display the Customer Number (p. 69)

– View the ANSYS Licensing Interconnect Debug Log File (p. 69) (Server Option)

– View the ANSYS FlexNet Debug Log File (p. 69) (Server Option)

– Gather Client Diagnostic Information (p. 69) (Client Option)

From the Tools menu, you can select Set Language Options (server only) and then choose a differentlanguage in which to view the server ANSLIC_ADMIN utility and the ANSYS Licensing Interconnect logfile. You must close and reopen the ANSLIC_ADMIN utility for this setting to take effect. This option isvalid only with the server ANSLIC_ADMIN.

From the Help menu, you can select:

• View the ANSLIC_ADMIN Help

• About ANSYS, Inc. Licensing

• About ANSLIC_ADMIN

To exit the ANSLIC_ADMIN utility, choose File>Exit.

5.1.1. Launch the ANSYS License Management Center

Use this option to launch the ANSYS License Management Center (LM Center). The ANSYS LicenseManagement Center is a browser-based user interface that centralizes many of the ANSYS licensingadministrative functions. For more information, see License Server Administration Using ANSYS LicenseManagement Center.

5.1.2. Specify the License Server Machine

Use this option to set the ANSYS Licensing Interconnect and ANSYS FlexNet servers. Using this optioncreates or updates (lists, adds, modifies, deletes, or reorders) entries in the ansyslmd.ini file in thelicensing directory for the local machine. With this option, you can specify single servers, multiple singleservers, or redundant triad servers. You also use this option to specify the Licensing Interconnect andANSYS FlexNet 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 ofwhere you have installed the product. You should use the server version of this option only to specifythe license server machines for Release 11.0 and lower versions. You can also use the server version tospecify 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.



Using the ANSLIC_ADMIN Utility

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 arerunning on a Windows 7 machine, you must run as an administrator, preferably with UAC turned off.If you are running with UAC turned on, you must launch ANSLIC_ADMIN using the Run as adminis-trator option. If you are running on a Windows 8.1 machine, you must run as an administrator. Addi-tionally, you must launch ANSLIC_ADMIN using the Run as administrator option. For more information,see the User Account Control (UAC) section of the ANSYS, Inc. Windows Installation Guide for moredetails on working with Windows and UAC.

To add a server:

1. Click Specify the License Server Machine.

2. Click Add Server Machine Specification.

3. Enter the ANSYS Licensing Interconnect and FlexNet 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 apath or a filename in place of the hostname.

To specify multiple single servers, click OK on this screen after adding the first server. Then clickthe Add Server Machine Specification button again and add information for the next server. Repeatthis process for each single server.

To specify redundant triad servers, click the 3-server (redundant triad) option and enter thehostname for each of the three servers in the spaces available.

4. Click OK.

To delete a server, highlight the server in the list and click Delete Selected Server Machine.

To edit a server, click on one of the listed servers and click Edit Selected Server Machine. You canthen change the ANSYS Licensing Interconnect and the FlexNet port numbers, the number of licenseservers, or the hostname(s).

The ansyslmd.ini File The Specify the License Server Machine option creates or updates the an-syslmd.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 usersat your site to use this setting without having to individually set the ANSYSLMD_LICENSE_FILE orANSYSLI_SERVERS environment variables to specify the license server machine(s). It also eliminatesthe 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 thelicense request is granted. To reorder the entries in the list, highlight a server and use the Move up orMove down buttons.

You are not limited to designating one set of license server machines for your network. You can havemultiple 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 specificationentry in this file will typically begin with ANSYSLI_SERVERS= and SERVER= to specify the Licensing In-terconnect and FlexNet port numbers, respectively.

On a single server:



ANSYSLI_SERVERS=<ansysliport>@<host>SERVER=<flexnetport>@<host>

For multiple single servers, each server should have its own ANSYSLI_SERVERS= and SERVER= lines.

On redundant (triad) servers on Linux platforms:

ANSYSLI_SERVERS=<ansysliport>@<host1>:<ansysliport>@<host2>:<ansysliport>@<host3>SERVER=<flexnetport>@<host1>:<flexnetport>@<host2>:<flexnetport>@<host3>

Windows platforms use semicolons (;) instead of colons:

ANSYSLI_SERVERS=<ansysliport>@<host1>;<ansysliport>@<host2>;<ansysliport>@<host3>SERVER=<flexnetport>@<host1>;<flexnetport>@<host2>;<flexnetport>@<host3>

Do not use commas as separators; use colons (:) on Linux machines and semicolons (;) on Windowsmachines.

The ANSYS Licensing Interconnect default port number is 2325 and the ANSYS FlexNet default portnumber is 1055. The host is the license server hostname. For example, if the license server name is alpha1:

ANSYSLI_SERVERS=2325@alpha1SERVER=1055@alpha1

The order of the ANSYSLI_SERVERS and the SERVER lines in the ansyslmd.ini file specifies the orderin 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 an-syslmd.ini file, you can do so by setting the ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERSenvironment variables on individual machines. These environment variables are useful if you want totemporarily 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 FlexNet port number.

If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environmentvariable is not set, the same server machines will be used to specify the Licensing Interconnect but theport number will be replaced by the Licensing Interconnect default port of 2325. When both variablesare set, ANSYSLMD_LICENSE_FILE explicitly defines the FlexNet servers while ANSYSLI_SERVERS ex-plicitly defines the Licensing Interconnect servers.

If you set the ANSYSLMD_LICENSE_FILE or ANSYSLI_SERVERS environment variables on a three-server (redundant) system, specify all three systems, in the same order as the SERVER lines are listed inthe 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 singleserver systems by separating the system names with colons on Linux systems and semicolons on Windowssystems.

To have your license server preference known each time you log in, set the environment variables AN-SYSLMD_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).

5.1.2.1. Sample Scenario

Suppose that you have a company with two departments, Design and Engineering. The Design Depart-ment has one license of ANSYS Mechanical and one license of DesignSpace with the server DES1, andall 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 DesignDepartment, and ANSYSLI_SERVERS=2325@ENG1 and SERVER=1055@ENG1 for the Engineering Depart-ment. These settings limit users in each department to work only on their own server. If individual usersin the Design Department need to run on the engineering server, ENG1, they could set the followingenvironment variable:

setenv ANSYSLMD_LICENSE_FILE 1055@ENG1

This example would automatically use 2325@ENG1 for the Licensing Interconnect license path. For thisexample, you would need to set ANSYSLI_SERVERS only if you were not using the default LicensingInterconnect port number.

5.1.3. Set License Preferences for User

Use this option to review the licenses available and prioritize the licenses. Settings specified here applyonly to the username shown in the button title. When you select this option, you will first choose therelease for which you want to set preferences. Select the release and click OK. All licenses available toyou 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 upand down in the list using the Move Up or Move Down buttons. When you open an application, thelicense 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 theapplication. The license manager will continue through the list until an available license is found. Ifnone are found, a message displays.

By default, all licenses available from your license server are shown and marked as available for use. Ifyou do not want a particular license to be available for your use, select the license in the list, and setthe 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 yourlicense 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 stateby selecting the Reset to Default button.

When you have completed your changes, click OK to make the changes and close the dialog box. ClickApply to make the changes without closing the dialog box. Selections you make here will take effectwith 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 Work-bench and specifying HPC licensing settings, see Establishing User Licensing Preferences in the End-User Settings section.



5.1.4. Run the ANSYS Borrow Utility

License borrowing (available only on Windows machines) allows a user to take a license for use outsideof the company facility, such as for an engineer to take a license home on his laptop. Before users cantake 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 li-censes is also a license server from which you could normally use licenses, you would be able to useonly the borrowed licenses.

This option is available only for the client version of ANSLIC_ADMIN.

5.1.4.1. Setting up License Borrowing

To use license borrowing, you must have license keys that specify borrowable licenses. License featuresthat can be borrowed will contain the keyword BORROW.

You can use the optional FlexNet options file settings to further control borrowing at your site. To usethese settings, you must first specify which users are allowed to borrow licenses by adding an IN-CLUDE_BORROW group to the options file. Any user not in the INCLUDE_BORROW group will not beallowed to borrow licenses. You may also want to set up an EXCLUDE_BORROW group to prevent spe-cific users from borrowing licenses.

You can also limit the number of licenses that can be borrowed from your total pool of borrowable li-censes. Set the BORROW_LOWWATER option in the options file to the number of licenses that cannotbe borrowed. For example, if you have 15 licenses total and want to limit the number that can be bor-rowed to 5, set BORROW_LOWWATER=10.

The maximum number of hours a license can be borrowed at any one time is defined by your licensefile. You can set that limit lower for your users by setting the MAX_BORROW_HOURS option in the optionsfile. MAX_BORROW_HOURS cannot exceed the limit specified in your license file. The total maximumnumber of borrowable hours is defined by your license agreement.

Compatibility between versions Flexera Software has created an incompatibility in license borrowingbetween FlexNet releases. Since different versions of FlexNet are used at most releases, the borrowedlicenses are not compatible between different ANSYS releases. The ANSBORROW utility includes a selectionfor 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.

The ANSBORROW utility allows you to borrow either initial release or service pack (SP) versions. The SPversions for a given platform use the same FlexNet version as the initial release; therefore, licenses se-lected for an SP should work for the initial release.

5.1.4.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, contact yourANSYS sales representative.

1. Connect to the network where the license server machine is running.





3. On the Borrow tab, specify the version number and return date. The return date defaults to the third dayfrom 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 thecorrect version.

5. Click Borrow.

6. Disconnect from the network. Note that even when you've disconnected from the network, you must stillrun the products from the same account you used to borrow the licenses. For example, if you use a networkaccount 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 machineAFTER you've disconnected from the network. If you encounter any difficulties, reconnect to thenetwork, 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. Yourborrowed license will simply expire at the end of the borrow period, and the license will be releasedinto the pool of available licenses.

To return a license early:

1. Reconnect to the same license server from which you borrowed the license(s).


3. Select the Return tab. Click Return all. If you want to keep some but not all of the licenses you borrowed,you will need to re-borrow them.

4. 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 licensesoriginally.

Some multi-feature products include other products and/or add-on features. The utility will automaticallycheck out any such included products or add-on features. If you borrow one of these multi-featureproducts and then click on the Return tab, you will see the product you selected, as well as any otherproducts and add-ons that it includes. If you return a multi-feature product early, these products andadd-on features will also be returned.



5.1.5. Set Site Preferences

This option is used for license server machines only.

The following site preference settings are available:

• Specify Product Order (p. 65)

• Modify Startup Options (p. 66)

• Specify License Servers to Cache (p. 67)

5.1.5.1. Specify Product Order

This option launches a utility that allows you to designate the order that the licensed products are listedin the Mechanical APDL launcher and the order in which licenses are tried in all applications. You firstwill 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 (includingall 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 isapplicable ONLY if this machine is a license server machine. The product ordering you select with this optionwill 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 (Release11.0 only), product category (Solver, PrepPost, Geometry, or HPC). To re-order the products, select aproduct and click the Move up or Move down button. When you have finished reordering all productsthat you want to reorder, click Save and then Close.

All products available in a given category are shown, regardless of whether you have licenses for them.

If you have made changes to your product ordering, you can return the settings to the default state byselecting the Reset to Default button.

For Release 12.0 and higher, after making changes to the product order (including resetting to the de-fault), you will need reread the license file or restart the license manager for the changes to take effect.

Only those logged in as root or superuser (Linux) or with administrative privileges (Windows) can usethis utility. You should set the product order before any of the users at your site run; once a user setshis preferences, the user preferences will take precedence.

Note

When installing the License Manager, if you have modified the product order in a previousrelease, the installation process will automatically update the product order to reflect anychanges you made as well as any changes (such as naming conventions) that may have oc-curred between releases.




5.1.5.2. Modify Startup Options

Note

Only those users who are logged in as root or superuser (Linux) or with administrative priv-ileges (Windows) can use this utility.

Use this option to modify your license manager startup options. License manager startup options thatyou can modify include:

ANSYS Licensing Interconnect Debug Log FileYou can specify the path to the ANSYS Licensing Interconnect debug log file (ansysli_server.log,by default), the detail level of the file (standard, connections, or verbose), the size limit of the file (defaultis 10MB; minimum is 1MB), and the number of log files to save (default is 10; minimum is 1).

ANSYS Licensing Interconnect Debug Log File Detail Descriptions

• STANDARD level logs ansysli_server STARTUP options, license cache information (such as fea-tures/counts and FlexNet options file content), CHECKOUT, CHECKIN, RESERVE, and RETURN_RESERVE.It also logs CLIENT_SHUTDOWN for all but ansysli_monitor.

• CONNECTIONS level logs everything that STANDARD logs, and CLIENT_ACCEPT and CLIENT_SHUTDOWNfor the monitor.

• VERBOSE level logs STANDARD plus CONNECTIONS, and ADD (product definitions and shared capabilities)and REMOVE (shared capabilities).

FlexNet OptionsYou can specify the path to the FlexNet debug log file (license.log, by default). By default, a new li-cense.log file is created each time you start the license manager; you can choose to have new inform-ation appended to the existing file instead.

You can also set the -local setting (Linux only).

The -local option restricts the ability to shut down the FlexNet components of the license managerto only an administrator running on the same machine where the FlexNet components of the licensemanager was started. This option is off by default. See the FlexNet License Administration Guide formore information on using this option.

The -local option is not recommended if you will be using license borrowing.

Miscellaneous OptionsYou 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 sameport number. If you change the Licensing Interconnect port number here, and other machines usethis machine's Licensing Interconnect, then on each of those machines, you must change the Licens-ing Interconnect port number by one or both of the following options, as appropriate for yourconfiguration:

• Specify the License Server Machine option of the ANSLIC_ADMIN utility

• Specify License Servers to Cache option of the ANSLIC_ADMIN utility



You can also disable the ability to reserve licenses for a design point study in ANSYS Workbenchand/or the users' ability to track licenses used by ANSYS Workbench. For more information on re-serving licenses for design point studies in ANSYS Workbench, see Reserving Licenses for Design PointStudies in the ANSYS Workbench documentation.

On Linux machines only, you can also specify who can shut down the ANSYS License Manager. Bydefault, anyone can stop the license manager. You can restrict shutdown capabilities to only theuser who started it, or to a group, such as lmadmin. If you choose group, you will need to specifythe name of the group. If you specify a group restriction, any users in that group who want to stopthe license manager must have the specified group as their primary group. Note that the user whostarted the license manager will still be able to shut it down, even if he is not part of a group withshutdown capabilities.

Warning

The license.log file and the ansysli_server.log file for each server should belocated on a local disk. Writing to an NFS-mounted disk or remote file server creates a situ-ation 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 afatal error condition.

5.1.5.3. Specify License Servers to Cache

When the Licensing Interconnect starts, it caches the licenses for any ANSYSLI_SERVERS lines that arein the ansyslmd.ini file in addition to its own licenses. As you run ANSYS applications and theyconnect with the Licensing Interconnect, it caches the licenses for any servers in your ANSYSLI_SERVERSpath that have not yet been cached. Sometimes, especially due to network traffic, this caching processcan impact the time it takes to check out a license. Use this option to cache your servers when youstart the ANSYS License Manager, rather than at the point that you request individual licenses.

Note

Only those users who are logged in as root or superuser (Linux) or with administrative priv-ileges (Windows) can use this utility.

When you select this option:

1. On the Specify License Servers to Cache dialog, click Add Server Machine Specification.

2. On the Specify License Servers to Cache - Edit Selected Server Machine dialog box, enter the LicensingInterconnect port number. The default Licensing Interconnect port number is 2325.

3. Enter the hostname of the server.

4. Click OK.

5. Repeat steps 1 - 4 for any additional servers that you want to cache.

6. 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 Machine.




To edit a cached server, click on one of the listed servers and click Edit Selected Server Machine. Youcan then change the ANSYS Licensing Interconnect port number or the hostname(s).

5.1.6. View Status/Diagnostic Options

The following reporting options are available:

• Display the License Status (p. 68)

• Display Queued Licenses (p. 68)

• Display the Customer Number (p. 69)

• View the ANSYS Licensing Interconnect Debug Log File (p. 69)

(Server Only)

• View the ANSYS FlexNet Debug Log File (p. 69)

(Server Only)

• Gather Client Diagnostic Information (p. 69)

(Server Only)

When you select one of these options, the data will appear in the log area on the right side of theutility. Display the Customer Number appends the customer number to the session log itself; theother options create their own display in the log area. Each option is explained in the following sections.

5.1.6.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 itdirectly to a file using the buttons at the bottom of the window. This option displays information basedon the same license path rules as ANSYS, Inc. products, taking into account the settings in the AN-SYSLMD_LICENSE_FILE environment variable and the ansyslmd.ini and license files. Setting theANS_FLEXLM_DISABLE_DEFLICPATH environment variable will affect the information displayed bythis option.

5.1.6.2. Display Queued Licenses

Use this option to see a list of capabilities that are queued and awaiting availability, and the applicablelicenses that are being used. The report will have the following format:

Capability Timestamp User Count Host PID Platform Product1 Count Timestamp User1 Count Host PID Platform Timestamp User2 Count Host PID Platform Timestamp Usern Count Host PID Platform Product2 Count Timestamp User1 Count Host PID Platform Timestamp User2 Count Host PID Platform Timestamp Usern Count Host PID Platform

Where the first line shows information for the requesting user, and subsequent lines under that capab-ility show information for the users who are currently using the licenses for each of the licensed productsthat satisfy the requested capability.



An example report is shown below. Each line is numbered for reference in the discussion following theexample. Note that the actual report does not contain line numbers.

Capability Product Timestamp User Count Host PID Platform1 ANS_SOLVER 2010/04/27 09:39:27 JQD 1 mach1.win.acme.com 1234 winx642 ane3fl 33 2010/04/27 08:01:10 JXS 1 mach2.win.acme.com 5678 winx644 2010/04/27 07:29:13 MQD 2 mach3.win.acme.com 8765 winx64

Line 1: User JQD is running a process, 1234, on the machine mach1.win.acme.com, which has requestedone license with the ANS_SOLVER capability.

Line 2: Based on the site/user preferences, the ane3fl product can satisfy the requested capability, andthis 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 machinemach2.win.acme.com, running process number 5678.

Line 4: User MQD has been using 2 of the available licenses since 7:29:13, from machinemach3.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 forone 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_ADMINutility. 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 shortcutusing the above command.

Run the following command on Linux systems:

/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -queueinfo

5.1.6.3. Display the Customer Number

Use this option to display your customer number (necessary when requesting customer support). Thelicense manager must be running for you to obtain your customer number.

5.1.6.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 In-terconnect debug log file (named ansysli_server.log by default).

5.1.6.5. View the ANSYS FlexNet Debug Log File

This option is available only on the license server machine(s). Use this option to view the license logfile (named license.log by default).

5.1.6.6. Gather Client Diagnostic Information

When you choose this option, ANSLIC_ADMIN gathers various licensing-related files, logs and relatedinformation about your license client system and places them in a single directory.




This feature is useful if you want to easily review the files from a single location, or if you need tocompress the files and send them to a technical support representative. Every time you choose togather these files, you are prompted to specify the path of the diagnostics directory or to accept thedefault location. If you do not define the path of the diagnostics directory, the log and error files willbe copied into a new, date-stamped subdirectory in your $HOME/.ansys directory on Linux or in thedirectory specified by the TEMP environment variable on Windows. Be aware when choosing this optionthat some of these files can be large and could require significant disk space. You may want to deletethese directories when you are finished reviewing them because of the disk space usage.

Using the ansys_pid utility:

After all relevant files are gathered (if selected), this option runs the ansys_pid utility, which queries thesystem for information that may be useful for troubleshooting certain problems. This operation maytake a few minutes. You can append this information to the session log, or you can write it out directlyto a file using the buttons at the bottom of the window.

When you run this ansys_pid utility, information about your licensing information is displayed in theANSLIC_ADMIN log area. Information displayed may include:

• operating system info

• environment information, including environment variable settings

• firewall information

• available license information

The contents of specific log and error files will not be displayed in the ANSLIC_ADMIN log area. Youwill 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 inform-ation 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.



Chapter 6: Using Dongles with the ANSYS License Manager

Important

Only the dongle driver that is included as part of our installation files is fully supported byANSYS, Inc. The driver version required for Release 17.1 is detailed in the File Information andSupported Dongle Driver Versions (p. 72) section below. We strongly recommend that you usethis version of the driver. If you use any other version, including older versions that weprovided, ANSYS, Inc. can provide only limited support if you encounter problems. Flexerahas stated that they will not provide any support for drivers other than the version that weinclude with our installation.

Due to requirements of non-ANSYS products that are installed on the machine or becauseof operating system levels that ANSYS, Inc. supports but the driver included in the ANSYSinstallation does not, you may need to use a version of the driver other than the one thatwe provide. You will need to choose which driver to use based on your individual businessneeds. Unfortunately, we cannot ensure that our license manager will work with that driver.

This section explains dongle and dongle driver support and usage with ANSYS, Inc. products at Release17.1. The information applies to the ANSYS License Manager only and does not apply to any other licensemanagers that you may be using. The following procedures assume that you have some familiarity withdongles, their usage, and their advantages and disadvantages.

6.1. Assumptions, Restrictions, and Notes

The ANSYS License Manager supports limited dongle usage:

• ANSYS, Inc. supports only FLEXID9 (Sentinel/Aladdin USB) dongles and their Flexera-provided drivers.

• ANSYS does not support license borrowing for any license features tied to a dongle.

When we refer to dongles, we are specifically referring to FLEXID9 (Sentinel/Aladdin USB) dongles.

Every machine from which you are serving licenses tied to a dongle requires the following:

• ANSYS License Manager is installed on the machine.

• Dongle is inserted in an appropriate USB slot.

• Required version of the dongle driver is installed on the machine. This manual step is described in detailbelow.

• Flexera-provided FLEXID9 library is in the correct location on the machine. The ANSYS License Manager in-stallation's licensing configuration process handles this step for Windows machines. On Linux, copying thisfile to the correct location is a manual step included in the Linux Procedures (p. 75) section below.



The dongle driver version required for Release 17.1 is detailed in the File Information and SupportedDongle Driver Versions (p. 72) section below. If the specified version of the dongle driver is already installedon your machine, no additional action should be required to use dongles with this release of the ANSYSLicense Manager. However, if you encounter problems, we recommend that you refer to DongleTroubleshooting (p. 77) at the end of this section and that you go through the steps below for yourmachine’s platform.

All ANSYS paths shown in this document show the default installation directory. If your installationdirectory is not the default location, replace all ANSYS paths with your installation directory. The defaultinstallation directories are as follows:

Windows: C:\Program Files\ANSYS IncLinux: /ansys_inc

You must have administrator/root privileges to install or remove a dongle driver.

6.2. File Information and Supported Dongle Driver Versions

The following tables provide platform-specific information about the supported dongle driver versionand the files that will be used as part of the driver installation process:

Table 6.1: 64-bit Windows File Information and Supported Dongle Driver Version

FlexNet VersionFlexNet FLEXID9 SharedLibrary

Driver Version andInstallation File

Zip File

11.13.1.2haspsrm_win64.dll, version 7.1haspdinst.exe, version6.65

11_13_1_1.zip

Note

The compressed file and directory names may not match the FlextNet version.

Table 6.2: 64-bit Linux File Information and Supported Dongle Driver Version

FlexNet VersionFlexNet FLEXID9 SharedLibrary

Driver Version andInstallation File

Zip File

11.13.1.2libhasp_linux_x86_64.so, version7.1

aksusbd-2.5-1.i386.rpm,version 2.5.1

11_13_1_1.tar

Note

The compressed file and directory names may not match the FlextNet version.


Using Dongles with the ANSYS License Manager

6.3. Supported Platforms

The following operating system (OS) levels are supported for dongle usage with ANSYS 17.1:

Table 6.3: 64-bit Windows Support

Driver OS Level Support

Windows 7, Windows 8.1, Windows 10 (Seethe Note below for the Windows 10

Operating System)

Note

The dongle driver supplied in the 11_13_1_1.zip file does not officially support Windows10. If problems are encountered when using it on a Windows 10 machine, only limitedsupport will be available.

Table 6.4: 64-bit Linux Support

Driver OS Level SupportLinux Operating System

RHEL 5.10, 6.5, 7.0Red Hat

openSUSE 12.3SUSE

6.4. Windows Procedures

Caution

Do not allow Windows Update to install later versions of the dongle driver as this is notthe Flexera-provided version. Automatic updates can cause unpredictable behavior withdongles, such as:

• Features that require the dongle cannot be checked out.

• The dongle FLEXID (hostid) is not returned correctly.

• The dongle driver cannot be removed using the methods described in this document.

6.4.1. Installing/Updating the Dongle Driver on Windows

Caution

Removing a dongle or its driver may seriously disrupt your ability to run any productthat uses it. Therefore, do not remove a dongle or its driver until you determine that allproducts that might be using it have been closed. Always stop all license managers thatuse the dongle and remove the dongle from the system before removing any existingdriver. (These steps are detailed below for the ANSYS License Manager.)

To install the ANSYS-supplied driver on Windows systems, follow the steps below. You must have systemadministrator privileges to install this driver.



Windows Procedures

1. Install the Release 17.1 ANSYS License Manager.

2. Confirm that the license manager is stopped by verifying that the 'ANSYS License Manager' service is notrunning.

3. Remove all FLEXID9 dongles attached to your machine. Do not attach any dongles to the system againuntil told to do so in this document; if a dongle is plugged in before you have completed the driver install-ation, the Windows operating system could automatically install a non-Flexera driver.

4. In Windows Explorer, navigate to the following directory:

C:\Program Files\ANSYS Inc\Shared Files\bin\winx64\drivers\flexnet

5. Extract the contents of the 11_13_1_1.zip file into C:\Program Files\ANSYS Inc\SharedFiles\bin\winx64\drivers\flexnet. You will need to remove 11_13_1_1 from the end of the default directoryshown, if it is included.

6. Open an administrator command prompt window and perform the following steps:

a. Remove any existing driver on your system. See the Removing an Existing Dongle Driver on Win-dows (p. 74) section below for more information.

b. Navigate to the following directory:

C:\Program Files\ANSYS Inc\SharedFiles\bin\winx64\drivers\flexnet\11_13_1_1

c. Issue the following command:

haspdinst.exe -install

7. When the installation completes, restart the machine.

Note

You may not see the new driver until the dongle has been inserted into the machine.However, do not insert the dongle until the next step.

8. After the machine has restarted, insert the dongle.

9. To see if the dongle is being recognized, open the ANSYS License Management Center and click the GetSystem Hostid Information link. If the dongle is recognized, you will see a FLEXID9 Dongle ID (F) entryunder the IDTYPE column. (You can open the ANSYS License Management Center by clicking the ANSYS,Inc. License Manager > ANSYS License Management Center item on the Windows Start menu/Appspage.)

6.4.2. Removing an Existing Dongle Driver on Windows

Caution

Removing a dongle or dongle driver may seriously disrupt your ability to run any productthat uses the dongle. Therefore, do not remove a dongle or dongle driver until you de-



termine that it is safe to do so for all products using the dongle. Always stop all licensemanagers that use the dongle and remove the dongle from the system before removingany existing driver.

Before installing the ANSYS-supplied driver, you must remove any existing dongle driver from yoursystem. You will need to use the installer or removal utilities provided with that driver to remove it.See the documentation provided with that driver for specific commands or procedures, or if you en-counter problems.

Copies of the FLEXID_Dongle_Driver_installer.exe and FLEXIDCleanUtility.exe files discussed in thissection are included in the following file's contents, which must be extracted to use either of these files:

C:\Program Files\ANSYS Inc\SharedFiles\bin\winx64\drivers\flexnet\11.9.1.0.zip

1. Uninstall the appropriate driver as described below.

• To remove a dongle driver supplied at ANSYS Release 16.0 or higher, run the following command whilein the 11_13_1_1 subdirectory:

haspdinst.exe -remove

• If the dongle driver has been updated through a Windows Update, it must be removed using the toolsprovided by SafeNet, Inc. See SafeNet’s documentation for details.

• The FLEXID_Dongle_Driver_Installer.exe file was the driver installation file that ANSYS, Inc. providedprior to Release 16.0. If you used it to install an earlier version of the ANSYS-supplied dongle driver,perform the following steps to remove it.

– Run the following command while in the 11.9.1.0 subdirectory:

FLEXID_Dongle_Driver_Installer.exe /remove

– Select the driver to uninstall and click Next.

• If you used the FLEXIDInstaller.exe file to install an earlier version of the dongle driver, you can use eitherthe cleanup utility provided for use with the FLEXIDInstaller utility or use the Programs and Featuresoption from the Windows Control Panel. To use the cleanup utility, run the following command whilein the 11.9.1.0 subdirectory:

FLEXIDCleanUtility.exe

2. Restart the machine.

6.5. Linux Procedures

6.5.1. Installing/Updating the Dongle Driver on Linux

Caution

Removing a dongle or a dongle driver may seriously disrupt your ability to run anyproduct that uses the dongle. Therefore, do not remove a dongle or dongle driver until



Linux Procedures

you determine that it is safe to do so for all products using the dongle. Always stop alllicense managers that use the dongle and remove the dongle from the system beforeremoving any existing driver. (These steps are detailed below for the ANSYS LicenseManager.)

To install the ANSYS-supplied driver on Linux systems, follow the steps below. You must have rootpermissions to install this driver.

1. Install the Release 17.1 ANSYS License Manager.

2. Confirm that the license manager is not running.

3. Remove all FLEXID9 dongles attached to your machine. Do not attach any dongles to the system againuntil told to do so in this document.

4. Remove any existing driver on your system, if necessary. See the Removing an Existing Dongle Driver onLinux (p. 77) section below to determine if you must remove an existing driver.

5. Navigate to the directory:

/ansys_inc/shared_files/bin/linx64/drivers/flexnet

6. Extract the 11_13_1_1.tar file.

7. Go to the subdirectory containing the 11_13_1_1.tar file's contents, and do the following:

a. Copy the libhasp_linux_x86_64.so file to the /usr/lib directory.

Note

If this file already exists in the /usr/lib directory, rename it before copying thefile. If the files are identical, no action is required.

b. Run the following command:

rpm -i ./aksusbd-2.5-1.i386.rpm

8. Reboot the machine.

9. Attach the dongle to the system.

10. To see if the dongle is recognized, open the ANSYS License Management Center and click the Get SystemHostid Information link. If the dongle is recognized, you will see a FLEXID9 Dongle ID (F) entry under theIDTYPE column. You can bring up the ANSYS License Management Center by running the followingscript:

/ansys_inc/shared_files/licensing/start_lmcenter



6.5.2. Removing an Existing Dongle Driver on Linux

Caution

Removing a dongle or dongle driver may seriously disrupt your ability to run any productthat uses the dongle. Therefore, do not remove a dongle or dongle driver until you de-termine that it is safe to do so for all products using the dongle. Always stop all licensemanagers that use the dongle and remove the dongle from the system before removingany existing driver.

1. Before installing the new driver, you must determine whether an existing driver must first be uninstalled.

• If the existing driver was installed via the script method (i.e., using the dinst script provided with thedriver) rather than by using the rpm method, you may not need to remove the currently installed driverbefore installing the new driver. The rpm installation method that will be used to install the new drivershould replace the existing driver with the new driver. If you decide to uninstall this driver, you mustuse the dinst script that you used to install it.

• If the existing driver was installed via the rpm method, you must uninstall this driver before installingthe ANSYS-supplied driver. (As of ANSYS Release 16.0, the only FlexNet-provided driver installationmethod has been the rpm method.)

2. If you uninstalled a driver, reboot the machine.

6.6. Dongle Troubleshooting

• On Linux systems, if you encounter “transaction lock” error messages, you may not have root privileges. Login as root and retry the operation.

• If you have installed the new driver, rebooted the machine, and attached the dongle to the system, but thedongle is not recognized, confirm that the following file exists in the location below:

Windows: <OS drive>\Windows\System32\haspsrm_win64.dll

Linux: /usr/lib/libhasp_linux_x86_64.so

If the file is missing, copy the installation's file with that name from the ANSYS FlexNet driver directoryto the required location for your machine's platform. Additional details are available in the appropriateplatform section above.



Dongle Troubleshooting


Chapter 7: Troubleshooting

This chapter lists problems and error messages that you may encounter while setting up licensing. Aftereach situation description or error message is the user action required to correct the problem.

For more troubleshooting information, see the FlexNet License Administration Guide (accessible from theANSYS License Management Center).

The following troubleshooting topics are available:7.1. Getting Additional License Debug Information7.2. Gathering Diagnostic Information7.3. Problem Situations7.4. Licensing Error Messages7.5. License Manager Installation Directory Errors7.6. ANSYS License Borrowing Errors7.7. FlexNet License Log File Errors

7.1. Getting Additional License Debug Information

Use the following suggestions to display or generate additional error messages and debugging inform-ation.

• View the licdebug file. The licdebug file is generated when you run an ANSYS, Inc. application andresides in the .ansys subdirectory under the directory specified by the TEMP environment variable (Win-dows) or in the $HOME directory (Linux). The licdebug filename will vary depending on the product butwill follow the format licdebug.<product>.171.out. For example:

If a licdebug file already exists and is dated today, the information is appended. If it is dated beforetoday, the existing file will be renamed with a .old extension and a new file will be started.

– Mechanical APDL (ANSYS):licdebug.ANS_SOLVER.171.out

– ANSYS Workbench:licdebug.ANS_WB.171.out

– Mechanical:licdebug.MECH.171.out

– ANSYS Fluent:licdebug.FLUENT_SOLVER.171.out

– ANSYS Polyflow:licdebug.POLYFLOW.171.out

– ANSYS CFX-Pre:licdebug.CFX_PRE.171.out

– ANSYS CFX Solver:licdebug.CFX_SOLVER.171.out

– ANSYS CFD-Post:licdebug.CFD_POST.171.out.

– ANSYS ICEM CFD (includes AI*Environment):licdebug.ICEM_AM.171.out

– ANSYS Icepak:licdebug.ICE_PAK.171.out



– ANSYS LS-DYNA:licdebug.DYNA_SOLVER.171.out

– Connection functionality:licdebug.ANS_PM.171.out

Note

The license debug file names include the current release of the application. Because notall applications are updated with each release, it is possible to have licedebug file namesthat are appended with older release numbers. For example, it is possible to be runningANSYS Release 16.1 but still have a product license debug log file name include 160 as inlicedebug.POLYFLOW.160.out.

The directory specified by the TEMP environment variable may be hidden on your system. To viewthe directory and file, click on My Computer. Choose Tools from the menu, and then click on Folderoptions. 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 thesesuggestions:

• Confirm that the license manager was restarted or the license file was reread after any changes weremade to the license file. If you did not make any changes to the license file for the server, check thedate/time that it was last changed. Get the relevant path information from the debug output. Also,confirm that the same path is being used.

• Try restarting the license manager and then attempt to run again. See if the same situation occurs.

• If you installed a new license file but are not seeing it even after restarting the license manager, confirmthat the correct license file is being used to start the license manager. In this case, neither the clientapplication nor the license manager is using the changed file. Also confirm that if site or user licensepreferences were set, the preferences were updated with the new license information.

• If the ansyslmd.lic file is at the end of the path and it is a license file that uses the license managerdaemon/service, then confirm that the license manager is started with the same path as the an-syslmd.lic file's path. The license manager could be looking at one file in the client application butthe license manager daemon/service was started with another file.

7.2. Gathering Diagnostic Information

There are situations which require licensing-related information to be gathered for diagnostic andtroubleshooting purposes. At times it may be necessary to provide this information to technical support.

The client-related diagnostic information can be gathered by using the Client ANSLIC_ADMIN utility.For more information, see, Gather Client Diagnostic Information in the License Administration UsingANSLIC_ADMIN section of the ANSYS Licensing Guide.

The server-related diagnostic information can be gathered by using ANSYS License ManagementCenter or by using the standalone gatherdiagnostics script. For more information, see, GatheringDiagnostic Information in the License Server Administration Using ANSYS License ManagementCenter section of the ANSYS Licensing Guide.


Troubleshooting

7.3. Problem Situations

This section describes problems you may encounter when setting up licensing or running an ANSYSproduct, as well as actions you can take to correct the problems.

7.3.1. License Manager Will Not Start

If the license manager will not start, perform the tests below in the order they are listed:

1. Check the license.log file in the licensing directory on the license server for errors. See the re-mainder of this chapter for a list of possible errors and their resolutions.

2. Check the ansysli_server.log file in the licensing directory on the license server for errors.

3. Verify that TCP/IP is installed and configured correctly. Verify that the IP address is static. See Commu-nications Requirements (p. 12) for information about configuring TCP/IP.

4. Verify that the hostid has not changed. If the hostid has changed, you must obtain a new license.

Linux x64 Systems:

Linux x64 systems running the ANSYS 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 attemptsto 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 see the following message when you start the first server:

***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 otherservers, or verify that they are already started. When at least two of the three servers are started,you will see the ANSYS License Management Center of this server change to reflect that it is nowrunning. Do NOT attempt to stop the license manager by clicking the Stop button in the ANSYSLicense Management Center.



Problem Situations

If you verify that at least two servers are started and the ANSYS License Management Center doesnot update to running in a reasonable time, follow the three steps noted in License Manager WillNot Start (p. 81).

Caution

When you see this message, do NOT click the Start button again.

7.3.1.1. License Manager Will Not Start After Adding a License File

In cases where License Management Center is used to add a UTF-8 formatted license file on a Linuxor SuSE system, license manager will not start if the LANG settings are not configured for UTF-8. In thiscase, you will need modify the LANG settings to accept UTF-8, delete and re-add the license file byfollowing the steps below.

1. Verify that the license file is UTF-8 formatted by opening the file in a text editor. If the file starts with threequestion marks (???) then the file is UTF-8 formatted.

2. If the license file is UTF-8 formatted, modify the LANG settings to accept UTF-8.

Red Hat

/etc/sysconfig/i18n

LANG="en_US.UTF-8"

LC_COLLATE="C"

SuSE

/etc/sysconfig/language

RC_LANG="en_US.UTF-8"

RC_LC_COLLATE="C"

3. Exit out of your current terminal.

4. Restart Tomcat by performing the following steps:

a. Stop the Tomcat server process by executing the stop_lmcenter script.

b. Start the Tomcat server process with the new port number by executing the start_lmcenter script.

These scripts can be found in the following directory:

/ansys_inc/shared_files/licensing

Note

Starting the Tomcat server process with the start_lmcenter script will also openANSYS License Management Center.


Troubleshooting

5. From the license_files directory, delete the UTF-8 formatted license file that was just added.

6. Open License Management Center and re-add the UTF-8 formatted license file.

7.3.2. License Manager Will Not Stop

When you attempt to stop the license manager, it may not stop immediately. You should use the Stopthe ANSYS, Inc. License Manager option of the ANSYS License Management Center to stop the licensemanager. For more information, see Stopping the ANSYS License Manager (p. 34). We do not recommendstopping the license manager manually; however, if you choose to do so, you must stop the componentsin the following order:

1. ansysli_monitor

2. Licensing Interconnect (ansysli_server)

3. FlexNet components (lmgrd first, followed by ansyslmd)

7.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 managerdoes not stop immediately. You will see a message stating that the currently-installed license file is athree-server license file. With three-server license files, the license manager could take 60 seconds orlonger to successfully stop. Wait at least 60 seconds. When the license manager has successfully stopped,the ANSYS License Management Center will show that it is stopped. For more information, see SettingUp Redundant (Triad) Servers (p. 27).

7.3.4. License Manager Installation's Licensing Configuration Step to UpdateSite Preferences (Product Order) Fails

Note

This step is only required if the license server's site preferences have been customizedvia the ANSLIC_ADMIN Utility's Set Site Preferences > Specify Product Order option. However,it is safe to follow the procedure below even if the site preferences have not been cus-tomized. Therefore, if you don't know if the server has customized site preferences, itis recommended that you follow this procedure.

If the ANSYS License Manager's licensing configuration log file (install_licconfig.log) indicates that thestep to automatically update any existing site preferences (product order) failed, the following procedurecan be used to manually update your modified product order file to include any product changes thathave occurred in the most recently installed release of the ANSYS License Manager.

1. Examine the section of the licensing configuration log that contains the error message to see if any detailswere provided describing why the automatic processing failed. If so, this issue will need to be resolvedbefore continuing.

2. Follow the section below for your operating system. <install_dir> is the directory in which the ANSYS LicenseManager is installed.

Windows:



Problem Situations

Open an administrator command prompt window and issue the following command:

"<install_dir>\Shared Files\Licensing\winx64\ansysli_util.exe" -updatesiteprefs

Linux:

Open a command line window and issue the following command:

"<install_dir>/shared_files/licensing/linx64/ansysli_util" -updatesiteprefs

3. A message should be displayed after the ansysli_util command is run. (If not, there is a problem.) Examinethe message to determine if the command completed successfully. If not, resolve any issues and run thecommand again. If you are unable to resolve the issues, contact ANSYS Technical Support.

4. Once the command completes successfully, examine the message to see if site preferences were updatedor removed. If so, either reread the license manager settings or restart the license manager so the changesare recognized by the ANSYS License Manager.

7.3.5. The Application Does Not Show the Correct License(s)

If you do not see the correct licenses in your application, in Client ANSLIC_ADMIN's Set License Pref-erences 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 pref-erences. If you had previously set your license preferences, select Set License Preferences for User fromthe ANSLIC_ADMIN utility and add the new license to your list in the desired order.

2. If you had previously defined your preferences and have since installed the license manager to a differentlocation, you may need to reset your preferences.

3. If you do not see the correct licenses in the Client ANSLIC_ADMIN's Set License Preferences for Useroption or in the Mechanical APDL Product Launcher, and you updated your product order at a previousrelease, you may need to update your product order again. Use the Specify Product Order option underServer ANSLIC_ADMIN's Set Site Preferences.

On the license server machine:

1. Select the Reset to Default button to see the current release's default product order.

2. Reorder the products as you want, including any new products.

For more information , see Specify Product Order (p. 65) and Establishing User Licensing Prefer-ences (p. 48).

7.3.6. FlexNet Log File Shows Unexpected Messages When the License ManagerIs Stopped

On Windows systems, you may see unexpected error messages in the FlexNet licensing log file whenyou 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.


Troubleshooting

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 an-syslmd 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

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\ApplicationData\Macrovision\FlexNet\lmgrd.620: errno No such file or directory

These or similar messages in the FlexNet log file can be safely ignored in most cases. You can verifythat the service is shown as stopped, and that the ansysli_server, ansysli_monitor, lmgrd,and ansyslmd processes are stopped via Task Manager.

7.3.7. Unable to Check Out Licenses

If the license manager appears to start but you cannot check out any licenses, perform the tests belowin the order they are listed:

1. Review the Licensing Interconnect debug log file for more information. Use the View Licensing InterconnectLog option of ANSYS License Management Center to view the file.

2. On the license server machine(s), review the FlexNet license.log file for error messages. Use the ViewFlexNet Debug Log option of ANSYS License Management Center to view the file.

3. If neither log file exists or has a zero length, verify that you have write permissions on the files and on thedirectory containing the files (the licensing directory by default).

4. 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 untilyou have returned all borrowed licenses. For more information, see Borrowing Application Licenses onWindows (p. 55)

You could also encounter problems with obtaining a license if the Licensing Interconnect is still attempt-ing to restart the FlexNet server. Check the FlexNet license.log file. If you see the following linesmultiple times, try rebooting your license server machine:

(lmgrd) ansyslmd exited with status 28 (Communications error)(lmgrd) Since this is an unknown status, license server (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.(lmgrd) REStarted ansyslmd (pid 103864)

7.3.8. Entries in the FlexNet Options File Are Ignored

If you are using a FlexNet 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 ofthe system on which the Licensing Interconnect is running.



Problem Situations

7.3.9. Jobs Abort When a License Manager Goes Down in Three-Server Envir-onment

If you are running in a three-server environment and ANSYS program jobs abort when one of the licensemanagers goes down, perform the tests below in the order they are listed:

Note

1. If this problem persists after you perform the steps below, you may want to consider switchingto a single-server environment.

2. When using a three-server environment, we strongly recommend that all three servers be onthe same subnet. If this is not the case, you should consider using three machines which are inthe same physical location and are on the same subnet.

1. Verify that two of the three license managers are still running. Use the ANSLIC_ADMIN utility (Displaythe License Status). If the license manager is not already running on all servers, start it on all of them.

2. Check the ansyslmd.ini file in the licensing directory to make sure the server specification is correct.

3. Check to see whether the ANSYSLI_SERVERS or ANSYSLMD_LICENSE_FILE environment variable is set.If it is, verify that the settings are correct.

4. Verify that the same license file exists on all three license servers in the licensing directory. The hostnamesof all three servers must appear in these files and in the same order. If the license files are not the same onall three servers, make corrections as necessary and restart the license manager.

5. Verify that the date and time on all license servers are consistent and correct. Make corrections as necessaryand restart the license manager.

6. Verify that the hostid has not changed on any of the license servers. If any hostid has changed, you needto obtain and install new licenses on all license servers.

7. Verify that the license manager and utilities are installed locally on each license server. If not, run the in-stallation from the installation media and choose to install the license server only. See the installationmanual for your product and platform for more information.

8. Verify that the ansyslmd.opt files match exactly on all three license servers.

9. Check the FlexNet license.log and the licensing interconnect ansysli_server.log files for errormessages. See the remainder of this chapter for a list of possible errors and their resolutions.

7.3.10. Licensing Log File Not Created

On Windows, if the license manager starts and licenses can be taken from the license server, but theFlexNet licensing log file and the ansysli_server.log file are not written, check the Administratoraccount. Verify that the Administrator (as well as the individual user) has write privileges to the directorywhere the log files are to be written.

7.3.11. Queuing Does Not Work

If queuing does not work, refer to the following list of possible causes and corrections:


Troubleshooting

• Verify that the environment variable ANSWAIT is set to 1.

• The license manager is down. In this case, use ANSYS License Management Center to start the licensemanager.

• The hostname is mistyped in the ansyslmd.ini file or the ANSYSLMD_LICENSE_FILE environmentvariable. If so, correct the name and retry.

• You are not licensed for the requested product. In this case, request a product for which you are licensed.

• All licenses for the requested feature are reserved in the license options file. If so, have the license ad-ministrator correct the license options file.

• The user is excluded via the license options file from using the licenses for the feature(s) that are installedon this machine.

• You are running an application that does not support queuing.

7.3.12. No Licensing Interconnect or FlexNet Path Available from Display theLicense Status Option

If you select the Display the License Status option from the ANSLIC_ADMIN utility and see a messagestating that the Licensing Interconnect or FlexNet path is empty, try the following:

1. Use the Specify the License Server Machine option of the ANSLIC_ADMIN utility to specify the missingLicensing Interconnect or FlexNet port number. (On Windows, use the Client ANSLIC_ADMIN utility.) Ifthe machine is already specified but the error message states that no FlexNet path has been specified, theFlexNet port number may be missing from the license server specification shown in the Specify the LicenseServer window. Add the machine's FlexNet port number using the Specify the License Server Machineoption to add this machine to your FlexNet license path.

Note

This particular machine may have been configured to run the ANSYS Licensing Interconnectwithout starting FlexNet. Verify that FlexNet is running on this machine before changingthis setting.

See Specify the License Server Machine (p. 59) for more information on specifying license servermachines.

2. Check the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable setting. If this environment variableis set, the ANSYS License Manager will not use the license server machine specifications in the an-syslmd.ini file. In this case, only the ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS environmentvariable settings will be used.

7.3.13. Cannot Enter Data in Text Fields

On some Linux systems (for example Red Hat 7 systems), if you cannot enter data in text fields whenusing the ANSLIC_ADMIN utility, you may be encountering a Tcl incompatibility. To correct the problem,unset the following environment variables before running the ANSLIC_ADMIN utility:

QT_IM_MODULEXMODIFIERS



Problem Situations

GTK_IM_MODULE

You should reset these environment variables when you are finished using ANSLIC_ADMIN. Do notpermanently unset these environment variables as doing so could affect other applications.

Note

Other ANSYS utilities that have interfaces written in the Tcl scripting language couldencounter the same issue. (e.g., the Mechanical APDL Product Launcher.)

7.3.14. Design Point Project Locks Reserved Licenses During a Hang

If you are running a design point study in ANSYS Workbench and are using reserved licenses, you mayneed to free licenses if one or more design points hang or do not complete successfully. To do so, youwill need to free the entire reserve. When a user reserves a group of licenses, the group is given a reserveID. To free a reserved license without shutting down the license manager, you can use a specific ID,you can return licenses reserved by a specific user, or you can return all reserved licenses.

If you want to return a license associated with a specific reserve ID, issue the following ansysli_utilcommand option to find the reserve ID of the reserved licenses:

ansysli_util -reserve_list

The list of reserve IDs will be displayed. For example, issuing the above command might return outputsimilar to the following (your output will appear on a single line):

USER LABEL/RESERVE-ID jqd MyProject(###)(###)634710595285628367 licabc.acme.com--7782-6343374 PRODUCT TASK HOST FlexNet_SERVER ANSYS Dynamics <dynamics> 19 jqd.win.acme.com--7782-6343374 1055@licabc RESERVED_DATE 2012/05/01 14:51:43 ANSYS Academic Mechanical HPC 3

Using the reserve ID from the previous command output, issue the following command to remove aspecific reserve:

ansysli_util -return_reserve_by_id id

If you want to return licenses reserved by a specific user, issue the following command:

ansysli_util -return_reserve_by_user username

If you want the ability to return all reserved licenses, use one of the following Licensing Interconnectstartup options:

1. Start the License Interconnect under your user ID.

OR

2. Start the Licensing Interconnect, using the ansyslmd.ini keyword (RETURN_RESERVE=USER) or LicensingInterconnect command option (-reserveuser) to specify the users who are able to return reserved licenses.Note that you can also specify by group on Linux, using the Licensing Interconnect command option-re-servegroup or the ansyslmd.ini keyword RETURN_RESERVE=GROUP. See keyword and command optionsin the Reference Section for more information.

Once you are permitted to return reserved licenses, issue the following command to return all reservedlicenses:


Troubleshooting

ansysli_util -return_reserve_all

This command removes any free or hung licenses in the reserve; if any of the reserved licenses are stillin use, those running jobs will continue to completion. Any licenses checked out by those running jobswill remain checked out until the jobs complete. The design point study will not start new jobs, sincethe reserves have been removed.

7.3.15. See a “File Not Found” Message When Running a Licensing Utility

Linux x64 System: Linux x64 systems running the ANSYS License Manager require the Linux StandardBase (LSB) package. If this package is missing, you will see a message similar to one of the followingerrors when the license manager attempts to run, or when you attempt to run a licensing utility, suchas ANSLIC_ADMIN, getFLEXid, or lmutil.

/lmgrd -h./lmgrd: No such file or directory

If you have confirmed that the file listed does exist, try installing the LSB package from the Linux install-ation media.

7.3.16. Cannot See Attached Dongle

There are a number of reasons why you may not be able to see an attached dongle. Review the listbelow to troubleshoot the issue.

• Occasionally, dongles may work loose. Verify that the dongle is fully inserted in the appropriate USBport.

• The required dongle driver must be manually installed on the machine. To determine which version ofthe driver is required for this release of the ANSYS License Manager and for information on installingthe driver, see Using Dongles with the ANSYS License Manager (p. 71).

• Additional dongle-specific troubleshooting information can be found in Dongle Troubleshooting at theend of the Using Dongles with the ANSYS License Manager (p. 71) section of this guide.

7.3.17. Unable to Run a Bookmarked Version ANSYS License ManagementCenter

To run the ANSYS License Management Center, Tomcat must be running. Start Tomcat prior tostarting the ANSYS License Management Center from a bookmark.

7.3.18. Unable to View PDF Files in ANSYS License Management Center

To view PDF files in the ANSYS License Management Center the appropriate PDF plugin for yourbrowser must be enabled.

For Internet Explorer and Firefox: Enable the Adobe PDF plugin.

For Chrome: Enable the Chrome PDF Viewer plugin.

7.3.19. Unable to Search PDF Files in ANSYS License Management Center

To perform searches of PDF files displayed in the ANSYS License Management Center the appropriatePDF plugin for your browser must be enabled.



Problem Situations

For Internet Explorer and Firefox: Enable the Adobe PDF plugin.

For Chrome: Enable the Chrome PDF Viewer plugin.

7.3.20. Starting ANSYS License Management Center Causes Error Messages(Linux Only)

Installing the ANSYS License Manager as root and subsequently attempting to run ANSYS LicenseManagement Center as a non-root user may display one of the following permission issues:

• ANSYS License Management Center hangs up, displaying the message,“Determining license managerstatus...”

• ERROR: In attempting to write to /ansys_inc/shared_files/licensing/tools/tomcat/logs/catalina.out,Tomcat will not be able to start successfully. Please check the file permissions.

/bin/sh: /var/tmp/cmd.out: Permission denied

• ERROR: Attempt to delete file "/ansys_inc/shared_files/licensing/tools/tomcat/bin/setenv.sh.old"failed.

• ERROR: Attempt to rename file " /ansys_inc/shared_files/licensing/tools/tomcat/bin/setenv.sh" to "/ansys_inc/shared_files/licensing/tools/tomcat/bin/setenv.sh.old" failed.

• ERROR: The new value of export ANSYSLM_ROOT_DIR=/ansys_inc/shared_files/licensing/../.. was notupdated in the Tomcat/ansys_inc/shared_files/licensing/tools/tomcat/bin/setenv.sh file.

Existing PID file found during start.

Removing/clearing stale PID file.

Unable to remove or clear stale PID file. Start aborted.

These permission issues may be resolved by running the following commands:

chmod 777 -R /ansys_inc/shared_files/licensing/tools/tomcat/binchmod 777 -R /ansys_inc/shared_files/licensing/tools/tomcat/logs

7.3.21. Manually Changing the Tomcat Port Number

During the default ANSYS License Manager installation, the Tomcat port number is set to 1084. Tochange this port number, see, Modifying the Tomcat Port Number (p. 23)

7.4. 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 taskhas been freed up and try again. If this error occurs on a regular basis, you may want to talk to yourANSYS sales representative about obtaining additional licenses.


Troubleshooting

This error may also occur when licenses have been reserved for certain users, or when certain usershave 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 versionfield), and licenses have been reserved for this feature. In this situation, the number of reserved li-censes is reserved out of each INCREMENT, rather than the sum total of both.

*** Cannot connect to license server.

or

***Unable to connect to FlexNet license server

The license manager is currently not running. Use ANSYS License Management Center to startthe license manager. Your license must exist on the license server prior to starting the licensemanager.

If you install the license manager and a license file, and it appears that the server is running, butyou cannot connect to your license server, try rebooting.

If you think the license manager should already be running, check the FlexNet license log file andthe 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 an-sysli_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 licensekeys 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 licensekeys were created with the wrong ID). The license manager could not be started.

• The wrong license file is on the system AND the user changed the server line to have the machine'shostid 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 settingof 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 becauseit was not able to start the FlexNet server or may have exited after failing to restart the FlexNetserver. Check the FlexNet license log file (license.log). If you see the following lines multipletimes, try rebooting your license server machine:

(lmgrd) ansyslmd exited with status 28 (Communications error)(lmgrd) Since this is an unknown status, license server (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.(lmgrd) REStarted ansyslmd (pid 103864)

*** Feature removed during lmreread, or wrong SERVER line hostid



Licensing Error Messages

Some possible causes of this message include:

• There is a typographical error in the license file's SERVER line. Typically, the machine ID was mistypedwhen manually entering the license file on a machine.

• You tried to install another machine's license file on a machine and changed the SERVER line in thefile 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 stationand 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 filethat 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 beset 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, orthe version is greater than the highest supported version, or the license file has been edited whilethe license server is running and the license file is not reread. Additional causes for this messageinclude:

• If you are trying to install another machine's license file on a machine AND changes both the host-name and the machine ID information on the SERVER line to be this machine's information. TheINCREMENT 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 lmrereadwas 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 theproblem). Such an attempt will not succeed because the INCREMENT lines were created using thedocking station's Ethernet address, which in this situation can no longer be seen on this machine.

• If one or more INCREMENT lines that were made for machine A were installed in machine B's licensefile and those features were trying to be checked out from machine B.

*** Feature has expired.

Your license has expired; 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 environmentvariable 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 ofthe 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.


Troubleshooting

• If you are licensed to run this product, install the license from the license supplied by ANSYS, Inc. or yourANSYS sales representative using ANSYS License Management Center. If you have already created thelicense, use ANSYS License Management Center 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.For the current version of FlexNet, see Compatibility with Other FlexNet-Licensed Software (p. 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 lineoption on the Mechanical APDL (ANSYS) product) and no license for that product is currentlyavailable 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 forUser in the ANSLIC_ADMIN utility.

• Your Technology Enhancements and Customer Support (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 authorizedto run a new release or you may not have installed your new license. If this is the case, install thelicense using the ANSYS License Management Center. If you have installed the new license, usethe ANSYS License Management Center to reread the license file. To view the build date inMechanical APDL (ANSYS), use the -v command line option.

*** Invalid (inconsistent) license key

For the current version of FlexNet, see Compatibility with Other FlexNet-Licensed Software (p. 1).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 causedby transferring the file).

Invalid license file: None of the hostnames in the license file match the system hostname.

This message occurs when you install the license file if the hostname of the system you are runningon does not match any of the hostnames in your license file. Some possible reasons why this canhappen 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 thelicense 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/hostsfile. When you run the Get System Hostid Information option of the ANSYS License Management




Center, the utility uses the localhost information instead of the correct system hostname. An exampleof 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 abclinux510.99.9.99 abclinux5 abclinux5[root@abclinux5 ~]$ hostname abclinux5[root@abclinux5 ~]$ hostname -slocalhost[root@abclinux5 ~]$

In this example, the Get System Hostid Information option would incorrectly use the localhostinformation.

To correct the problem, you need to edit the /etc/hosts file and change the order of thehostname 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 abclinux5127.0.0.1 localhost.localdomain localhost abclinux5[root@abclinux5 ~]$ hostname abclinux5[root@abclinux5 ~]$ hostname -sabclinux5[root@abclinux5 ~]$

In the corrected example, the Get System Hostid Information option would correctly use theabclinux5 hostname.

*** Local checkout filter rejected request.

View the license debug log files (FlexNet license.log and the Licensing Interconnect an-sysli_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 clientcomputer's /etc/hosts file (Linux) or the services file (Windows).

***The ANSYS license manager server is down. Unless a connection is reestablished, ANSYS willexit in nn minutes.

A message similar to this one occurs in a one-server license environment if your license managerhas quit running. In a three-license server environment, the ANSYS license manager must be runningon at least two of the three license server machines at all times. If two of the license server machinesgo down, or two of the machines are not running the license manager, this error message will appearin the program output or in a message box. The program will continue to run for nn minutes toallow the license manager to be restarted or to be started on a second machine if using redundantservers. When this error message appears, start the license manager on the other machines designatedas license servers.

If you get this message and determine that the license manager is still running, and you are runningin a one-server environment, then the IP address of the license server machine was changed whilethe ANSYS product was running (this is usually caused by connecting to or disconnecting from anInternet Service Provider (ISP) that dynamically allocates IP addresses). To correct this situation, youmust return the IP address to the same address that the license server had when the ANSYS productwas started.


Troubleshooting

If the IP address changes after you start the ANSYS product (either because you connected to ordisconnected from your ISP), you can correct the error by restarting the ANSYS product. You shouldnot need to restart the license manager.

You can avoid this problem by remaining connected to or disconnected from the ISP the entiretime you are running the application.

*** version of vendor daemon is too old.

For the current version of FlexNet, see Compatibility with Other FlexNet-Licensed Software (p. 1).Verify that you are not using the license manager daemons supplied with a previous release.

Your version of the ANSYS license client software is out of date. Refer to Licensing Error Messagesin the Troubleshooting section of the ANSYS Licensing Guide.

The version of the license client ansysli_client [version] must be greater or equal to theclient ANSYS application [version].

This message indicates that you are attempting to start an ANSYS, Inc. application with an out-of-date version of the license client.

If you are using different installation directories for the current and prior versions, you need to ensurethat each version is running from the appropriate installation directory.

If you are using the same installation directory for the current version as you used for the priorversion, try the following solutions:

• The license client was running during the installation process and was not replaced. In this case, closeall ANSYS, Inc. applications, making sure that the license client closes, and then run the Complete Un-finished Licensing Installation Configuration option from the Client ANSLIC_ADMIN’s Tools menu.

• The license client was running during the installation process and was replaced, but the application isnot reading the new client. In this case, close all ANSYS, Inc. applications, making sure that the licenseclient closes, and restart the ANSYS, Inc. application.

Your version of the ANSYS license manager software is out of date. Download and install thecurrent ANSYS license manager from the ANSYS Customer Portal.

The version of the license server ansysli_server [version] must be greater or equal to theclient ANSYS application [version].

This message indicates that you are attempting to start an ANSYS, Inc. product with an out-of-dateversion of the license server. You need to update to the latest version of the license manager.

***Cannot read data from license server.

The server and the client are having difficulties communicating. This error is usually caused by thenetwork 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 theserver.

• 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 areply. The license server may be experiencing a high demand or a temporary outage. Try againlater.

In rare occasions, your site could be submitting too many requests too quickly (simultaneously ornearly simultaneously) to the ANSYS License Manager. In this case, you will also see that the licenseserver machine in question is averaging 85% CPU usage or higher. In this scenario, we recommendthat you either point some of the clients to a different license server or install one or more standalonelicensing interconnects for some of the clients to use. For instructions on installing a standalone li-censing interconnect, see Run the ANSYS Licensing Interconnect without FlexNet (p. 19).

***Connection to the license server closed unexpectedly.

If you see the above message and the server is not experiencing any demand, a virus scanner maybe blocking connections to your license server. Rebooting your license server may also resolve theissue.

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 freea port before the timeout period expired. This situation could happen if the port is being used bysome other application, or after you shut down a server if you did not wait long enough for theports to free before restarting it.

Consult your system administrator before making changes to your default operating system settingsor to determine which command is appropriate for your operating system level.

***Failed to retrieve license preferences. Be sure that you are able to connect to the licenseserver.

If you attempt to set your license preferences and the client information is at a higher release thanthe server information, you may see this message. To verify, see the getuserprefs.log file (onLinux machines, in .ansys in your home directory; on Windows, in %TEMP%\.ansys). Note thelast lines in the example below:

2012/08/24 17:18:00 INFO Not connected to a local port.2012/08/24 17:18:00 NEW_CONNECTION Connected to license server: [email protected]. ANSYSLI_SERVERS: [email protected] Servers: [email protected]/08/24 17:18:01 SITE_PREFS 2012.0806 0/1/0/3 4679:ALI_UTIL:[email protected]:lin32:linux10 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 [email protected] [1.1.2] must be greater or equal to the client ALI_UTIL version [1.3.0].

***License File filename has changed. Please do a reread to update the server.

The license file or the FlexNet options file has been changed since the last restart of the licensemanager or reread of the license file. The changes will not be available until you restart the licensemanager or reread the license file. If you are running the ANSYS Licensing Interconnect and FlexNet


Troubleshooting

independently and have cached the license file, the cached license file may be out of date. RestartFlexNet or reread the license file to update the cached license file. If you make changes to the licensefile, in addition to rereading the license file in FlexNet, you must also recache the license file in theLicensing Interconnect by restarting the Licensing Interconnect or by using the Reread LicenseManager Settings option in the ANSYS License Management Center.

7.5. License Manager Installation Directory Errors

The directory you specified is not valid for one of the following reasons:

• Must not be a UNC path

• Must not contain a symbolic link or junction

• Must not be a filename

• Must be an absolute path

• Must be in long file name format (not 8.3 format)

• Must contain a valid, existing local, fixed-media drive

Please check your path, correct the problem, and retry.

If you see this message or one that is similar, you may need to correct the path to the licensemanager. The message will display a particular error code (listed below). The -100 series numbersindicate errors associated with the path you entered; the -200 series numbers indicate errors asso-ciated with the path specified in the service.

• -108 / -208: path is a UNC path; UNC paths are not permitted.

• -109 / -209: path contains a remote (network) drive; remote drives are not permitted.

• -110 / -210: path does not contain a valid drive letter from a to z.

• -111 / -211: path points to a file rather than to a directory.

• -113 / -213: path is a relative path, which is not permitted.

• -114 / -214: root path is invalid. (Example: The drive specified in the path doesn’t exist.)

• -115 / -215: path’s root path isn’t a local fixed-media drive path.

• -116 / -216: path contains either a symbolic link or a junction, neither of which is permitted.

• -117 / -217: path is a short (8.3) file name format path, which is not permitted.

7.6. ANSYS License Borrowing Errors

***Unable to return <Product>, encountered “feature not found” attempting to return licensefeature <Product.>

If you see the above message when attempting to return a borrowed license before the expirationdate, the -2 -p license manager startup option might have been set. The -2 -p option is not



ANSYS License Borrowing Errors

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 machinefrom which the license was borrowed. To correct the problem, add the machine to the server spe-cification. If the ANSYS Borrow Utility is open when the server specification is changed to containthis server, you must close and restart the utility after changing the license server specification andbefore returning the borrowed license.

7.7. FlexNet 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. Inthis 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, thehostname is not correct.

• The hostname of the license server changed. Change the hostname on the SERVER line of the licensefile to correct this problem. REMEMBER to send ANSYS the new hostname so that future licensefiles 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 userchanged the machine's ID on the SERVER line but did not change the hostname. If the machine IDis also wrong, you will also see a message about the wrong hostid on SERVER line after correctingthe hostname.

• The wrong hostname was used to create the license file. As long as the correct machine ID wasused, you should be able to change the hostname on the SERVER line of the license file to fix thisproblem. REMEMBER to send ANSYS the correct hostname so that future license files are made withthe correct hostname.

***Invalid license key (inconsistent authentication code)

The INCREMENT lines in the license file are not valid for this system (Hostid mismatch). This errorwill 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 thehostname and the machine ID to machine B's in the SERVER line.

• If INCREMENT lines created for machine A are appended to an existing ansyslmd.lic file onmachine 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 theproblem). Such an attempt will not succeed because the INCREMENT lines were created using thedocking 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 forone of the license servers, this message will appear and will prohibit an ANSYS product from running


Troubleshooting

on any machine. Verify that the hostid in the license file matches the hostid on all three licenseservers. If it does not, the license file must be created using the correct hostid for all license servermachines.

***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 havebeen incorrectly typed in the SERVER line.

• The user installed a license file created for machine A on machine B and changed the hostname inthe 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 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 ansyslmd.lic (YYY) file does not match the hostname of the system(XXX).



FlexNet License Log File Errors


Chapter 8: Product Variable Table

The following table shows each ANSYS, Inc. product and its associated feature name as used in the IN-CREMENT lines.

This table is provided as a reference for both current and legacy products. Not all products listed aregenerally available but are included here for customers running an older release. Contact your ANSYSsales representative or technical support representative for details regarding product availability.

Table 8.1: Product/Feature Names for Licensed Products

Feature NamesProduct

ANSYS Multiphysics Products

aim_mp1ANSYS AIM Pro

ancfx*ANSYS Mechanical CFD-Flo

ane3*ANSYS Mechanical Emag

ane3fl*ANSYS Multiphysics

mpba*ANSYS Multiphysics Solver

ANSYS nCode DesignLife Products

ancode_standardANSYS nCode DesignLife Standard

ancode_vibrationANSYS nCode DesignLife Vibration

ancode_acc_testingANSYS nCode DesignLife Accelerated Testing

ancode_weldsANSYS nCode DesignLife Welds

ancode_hpc ANSYS nCode DesignLife Parallel

ancode_thermo_mechANSYS nCode DesignLife Thermo-MechanicalModule

ancode_compositeANSYS nCode DesignLife Composites

ANSYS Structural Mechanics Products

a_lmatANSYS Composite Cure Simulation

ans_actANSYS Customization Suite

caewbpl3ANSYS DesignSpace

dsdxmANSYS DesignXplorer

dfatigueANSYS Fatigue Module

mech_1*ANSYS Mechanical Pro

mech_2*ANSYS Mechanical Premium

ansys*ANSYS Mechanical Enterprise

meba*ANSYS Mechanical Enterprise Solver

prfnlsANSYS Professional NLS

prf*ANSYS Professional NLT




dynardo_osl, dynardo_ospANSYS optiSLang

kinemat, dynamicsANSYS Rigid Body Dynamics

struct*ANSYS Structural

stba*ANSYS Structural Solver

ANSYS Explicit Dynamics Products

acdi_ad3dfull, acdi_adhpc, acdi_adprepost,int4nas

ANSYS Autodyn

acdi_explprofANSYS Explicit STR

dyna*ANSYS LS-DYNA

ANSYS Fluid Dynamics Products

acfx_bldmdlrANSYS BladeModeler

acfdANSYS CFD

acfd_mhdANSYS CFD MHD

acfd_solverANSYS CFD Solver

acfd_floANSYS CFD-Flo

acfx_pre, acfx_solver, acfx_nolimit,acfx_parallel

ANSYS CFD-Flo Solver

acfd_cfxANSYS CFX

acfx_advanced_turbulence,acfx_turbulence_transition

ANSYS CFX Advanced Turbulence Models

acfx_mfrANSYS CFX Multiple Frames of Reference

acfx_multiphaseANSYS CFX Multi-Phase Flows

acfx_radiationANSYS CFX Radiation Models

acfx_combustionANSYS CFX Reacting and Combusting Species

acfd_cfx_solver, acfx_preANSYS CFX Solver

acfd_rifANSYS CFX-RIF Flamelet Library Generator

acfd_fluentANSYS Fluent

acfd_ibANSYS Fluent Immersed Boundary Module

acfd_fcellANSYS Fluent PEM Fuel Cell Module

acfd_fcellANSYS Fluent SOFC Fuell Cell Module

acfd_fluent_solverANSYS Fluent Solver

acfd_v2fANSYS Fluent V2F Module

acfd_ffc, acfd_ffc_preANSYS Fluent for CATIA V5

acfd_ffc_preANSYS Fluent for CATIA V5 Pre

acfd_ffc, acfd_ffc_pre, acfd_fluent_solverANSYS Fluent for CATIA V5 Analyst

acfd_polyflowANSYS Polyflow

acfd_polyflow_blowmoldingANSYS Polyflow BlowMolding

acfd_polyflow_extrusionANSYS Polyflow Extrusion

acfd_polyflow_solverANSYS Polyflow Solver


Product Variable Table


acfx_turbogridANSYS TurboGrid

acfd_cfx_turboANSYS CFX Turbo

acfd_vista_tfANSYS Vista TF

Combustion and Chemical Reactions Products

rd_ckgraph, rd_ckpost, rd_ckpreproc,rd_ckui, rd_ckcompute

ANSYS CHEMKIN-PRO

rd_ckcomputeANSYS CHEMKIM-PRO HPC

rd_ckgraph, rd_ckpost, rd_ckpreproc,rd_ckui, rd_ckcompute

ANSYS Collaborator License

rd_ckgraph, rd_ckpost, rd_ckpreproc,rd_ckui, rd_ckcompute, rd_energico,rd_kineticsapi

ANSYS ENERGICO

rd_energico, rd_kineticsapiANSYS ENERGICO Add-on

rd_fortejob, rd_forteui, rd_forteviz,rd_fortemesh, rd_mechforte, rd_mechsoot

ANSYS Forte CFD

rd_mechmfcANSYS MFL Encrypted Member

rd_mechmfcANSYS MFL Encrypted Non-Member

rd_mechwb, rd_reactionwbuiANSYS Reaction Workbench Add-on

ANSYS HPC Products

anshpcANSYS HPC

anshpc_packANSYS HPC Pack

ans_dp_packANSYS HPC Parametric Pack

dysmpANSYS LS-DYNA HPC

ANSYS Pre/Post Processing and Geometry Interface Products

acdi_adprepostANSYS Autodyn PrepPost

a_dynamics_4_scdmANSYS Dynamics for SpaceClaim by Algoryx

a_catv6_readerANSYS Geometry Interface for CATIA V6

acfx_postANSYS CFD-Post

acfd_preppostANSYS CFD PrepPost

acpreppostANSYS Composite PrepPost

agppiANSYS DesignModeler

amesh_extendedANSYS Extended Meshing

a_geometryANSYS Geometry Interfaces

aimed, aihexa, aimshcrt, aibfcart, aiiges,aiacis, aioutput, aioutcfd, aidxf, aiquad,aimshcrt

ANSYS ICEM CFD Hexa

aimed, aitetra, aiprism, aiiges, aiacis,aioutput, aioutcfd, aidxf, aiquad

ANSYS ICEM CFD Tetra/Prism

pdmimanANSYS Interface for Team Center Engineering

a_jt_readerANSYS Geometry Interface for JT




dynapp*ANSYS LS-DYNA PrepPost

preppost*ANSYS Mechanical Enterprise PrepPost

ameshANSYS Meshing

parameshANSYS Mesh Morpher

rbfmorphANSYS RBF Morph Module

a_spaceclaim_catv5ANSYS SpaceClaim CATIA V5 Interface

a_spaceclaim_dirmodANSYS SpaceClaim Direct Modeler

a_spaceclaim_gdtGD&T Module for SpaceClaim

a_spaceclaim_jtJT Open Reader for SpaceClaim

a_spaceclaim_faceteddataFaceted Data Toolkit for SpaceClaim

a_spaceclaim_3dpdf3D PDF Reader for SpaceClaim

capricatv5CADNexus/CAPRI CAE Gateway for CATIA V5

piautoinGeometry Interface for Autodesk

picatv5Geometry Interface for CATIA V5

linux_catiav5Geometry Interface for CATIA V5 Linux

1spacdesGeometry Interface for Creo Elements/DirectModeling

piproeGeometry Interface for Creo Parametric

piugGeometry Interface for NX

rdparaGeometry Interface for Parasolid

rdacisGeometry Interface for SAT

pisoledgGeometry Interface for Solid Edge

pisolworGeometry Interface for SolidWorks

ANSYS Academic Products

aa_a*, aa_mcadANSYS Academic Associate Mechanical andCFD

aa_a_cfd, aa_mcadANSYS Academic Associate CFD

anshpc, rd_ckcompute, rd_ckgraph,rd_ckpost, rd_ckpreproc, rd_ckui,

ANSYS Academic Associate Chemical Kinetics

rd_fortejob, rd_fortemesh, rd_forteui,rd_forteviz, rd_mechforte

aa_a_hpcANSYS Academic Associate HPC

aa_fcellANSYS Academic Fuel Cell Tools

aa_mesh, aa_mcadANSYS Academic Meshing Tools

aa_r*, aa_mcadANSYS Academic Research Mechanical andCFD

aa_r_cfd, aa_mcadANSYS Academic Research CFD


ANSYS Academic Research Chemical Kinetics





aa_r_et, aa_mcadANSYS Academic Research ElectronicsThermal

aa_r_hpcANSYS Academic Research HPC

aa_r_dy*, aa_mcadANSYS Academic Research LS-DYNA

aa_dy_pANSYS Academic Research LS-DYNA HPC

aa_r_me, aa_mcadANSYS Academic Research Mechanical

aa_r_pf, aa_mcadANSYS Academic Research Polyflow

aa_t_cfd, aa_mcadANSYS Academic Teaching CFD


ANSYS Academic Teaching Chemical Kinetics


aa_t_me*, aa_mcad, aa_dsANSYS Academic Teaching Mechanical

aa_t_i*, aa_mcad, aa_dsANSYS Academic Student

aa_s_aimANSYS AIM Student

ANSYS EKM Products

ekm_desktop, ekm_mdANSYS EKM Analyst

ekm_basicANSYS EKM Basic

ekm_user, ekm_mdANSYS EKM Shared

ANSYS Offshore Products

acdi_aqwags, acdi_aqwaline,acdi_aqwawave, acdi_hydrodiff

ANSYS AQWA DIFFRACTION

acdi_aqwadrft, acdi_aqwafer, acdi_aqwags,acdi_aqwalbrm, acdi_aqwaline,

ANSYS AQWA SUITE

acdi_aqwanaut, acdi_aqwawave,acdi_hydrodiff

acdi_aqwaline, acdi_aqwawave, acdi_cd-ags,acdi_cd-drift, acdi_cd-fer, acdi_cd-libr,acdi_cd-naut, acdi_hydrodiff

ANSYS AQWA SUITE with Coupled CableDynamics

acdi_asas, acdi_asaslink, acdi_asasnl,acdi_asas-vis, acdi_beamst, acdi_comped,

ANSYS ASAS-OFFSHORE

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_asas-vis, acdi_beamstANSYS BEAMCHECK

acdi_fatjackANSYS FATJACK

ANSYS Electronic Thermal Management Products

si2d_gui, si2d_solveANSYS 2D Extractor Option

aice_optANSYS Iceopt

aice_pak, aiiges, aice_mesher, aice_solvANSYS Icepak




aice_solvANSYS Icepak Solver

ANSYS Electromagnetics Products

al4allegro, al4ansoft, al4apd,al4boardstation, al4encore, al4expedition,

ANSYS ALinks for EDA

al4generic, al4powerpcb, al4virtuoso,al4zuken, alinks_gui (2 per seat),al4cadvance, al4cds, al4gem, al4first,al4odb++

xlate_iges, xlate_proe, xlate_step,xlate_inventor, xlate_solidworks

ANSYS ALinks for MCAD

xlate_catia4, xlate_catia5ANSYS ALinks for MCAD CATIA

xlate_unigraphicsANSYS ALinks for MCAD NX

xlate_parasolidANSYS ALinks for MCAD Parasolid

al4ansoft, al4generic, designer_desktop,ensemble_gui, nexxim_gui, nexxim_netlist,

ANSYS Designer Pre/Post Processor

serenade_gui, symphony_gui, nexxim_dc,serenade_linear

ansoft_distrib, ansoft_distrib_engine,ansoft_distrib_engine_mp

ANSYS Distributed Solve (DSO)

electronics_desktop, electronics3d_gui,electronics2d_gui, electronicsckt_gui,emit_legacy_gui, savant_legacy_gui

ANSYS Electronics Desktop

electronics_desktop, electronics2d_gui,electronicsckt_gui, emit_legacy_gui

ANSYS Electronics Desktop Core

hfsshpcANSYS Electronics HPC

hfsshpc_packANSYS Electronics HPC Pack

emit_legacy_gui, emit_solve,emit_legacy_hpc

ANSYS Emit

ensemble_gui, hfss_desktop, hfss_gui,hfss_solve, nexxim_gui

ANSYS HFSS

ensemble_gui, hfss_desktop, hfss_gui,nexxim_gui

ANSYS HFSS Pre/Post Processor

hfss_solveANSYS HFSS Solver

hfssie_solve, hfssie_guiANSYS HFSS-IE Solver

hfsssbr_solveANSYS HFSS SBR + Solver

hfss_transient_solveANSYS HFSS-TR Solver

m2dfs_ac, m2dfs_ax, m2dfs_ckt, m2dfs_cn,m2dfs_ed, m2dfs_es, m2dfs_gui (5 per seat),

ANSYS Maxwell 2D

m2dfs_ms, m2dfs_par, m2dfs_post (2 perseat), m2dfs_solve, maxwell_desktop (5 perseat), maxwlspc, schem_gui, m2dfs_th,m2dfs_tran, m2dfs_qs_solve (5 per seat)

m2dfs_ac, m2dfs_ax, m2dfs_ckt, m2dfs_cn,m2dfs_ed, m2dfs_es, m2dfs_gui' m2dfs_ms,

ANSYS Maxwell 3D




m2dfs_par, m2dfs_post (2 per seat),m2dfs_solve, m3dfs_gui (5 per seat),m3dfs_solve, maxwell_desktop (5 per seat),maxwlspc, schem_gui, m2dfs_th,m2dfs_tran, m2dfs_qs_solve (5 per seat),m3dfs_qs_solve

m2dfs_gui (5 per seat), m3dfs_gui,maxwell_desktop (5 per seat)

ANSYS Maxwell 3D Pre/Post Processor

m2dfs_gui (5 per seat), m3dfs_gui,maxwell_desktop (5 per seat),m2dfs_qs_solve (5 per seat), m3dfs_qs_solve

ANSYS Maxwell 3D QS

optimetrics, ansoft_distrib_engine (2 perseat)

ANSYS Optimetrics (For HFSS, Q3D Extractor,Maxwell)

m2dfs_gui, maxwell_desktop, maxwlspc,pemag, pexprt, m2dfs_qs_solve

ANSYS PExprt

q3d_desktop, si2d_gui, si2d_solve, si3d_gui,si3d_solve

ANSYS Q3D Extractor

si3d_solveANSYS Q3D Extractor 3D Solver

q3d_desktop, si2d_gui, si3d_guiANSYS Q3D Extractor Pre/Post Processor

ensemble_25_sim, symphony_dt_sim,symphony_fd_sim, nexxim_dc, nexxim_tran,

ANSYS RF Option

nexxim_hb, nexxim_osc, nexxim_tvnoise,filter_synthesis, emit_solve

maxwell_desktop, rmxprt_bcm, rmxprt_ecm,rmxprt_gui, rmxprt_im, rmxprt_sym

ANSYS RMxprt

savant_legacy_gui, hfsssbr_solve,savant_legacy_hpc

ANSYS Savant

savant_legacy_datANSYS Savant HPC

nexxim_dc, nexxim_eye, nexxim_tran,nexxim_ami, hfss_transient_solve,designer_hspice, si2d_gui, si3d_gui

ANSYS SI Option

simplorer_desktop, simplorer_gui,simplorer_sim, mspc_fws, DayBasic,

ANSYS Simplorer

DayIEEEDataInterface, SimplorerBasic,SimplorerKernel, SimplorerSchematic,SimplorerLibPower, SimplorerLibMechanics,SimplorerLibAutomotive,SimplorerLibHydraulic, SimplorerLibSensor

simplorer_advanced,simplorer_CProgrInterface,

ANSYS Simplorer Advanced

simplorer_desktop, simplorer_gui,simplorer_sim, mspc_fws, DayBasic,DayIEEEDataInterface, SimplorerBasic.SimplorerCProgrInterface,SimplorerFrequencyStepResp,SimplorerKernel, SimplorerMaxwellTr2D,




SimplorerOptimizer, SimplorerSchematic,SimplorerSIMULINK, SimplorerLibPower,SimplorerLibMechanics,SimplorerLibAutomotive,SimplorerLibHydraulic, SimplorerLibSensor,simplorer_vhdlams, simplorer_control

simplorer_CProgrInterface,simplorer_desktop, simplorer_gui,

ANSYS Simplorer Basic

simplorer_sim, mspc_fws, DayBasic,DayIEEEDataInterface, SimplorerBasic,SimplorerKernel, SimplorerSchematic

simplorer_controlANSYS Simplorer Control Option

simplorer_CProgrInterface,simplorer_desktop, simplorer_gui,

ANSYS Simplorer ML

simplorer_sim, mspc_fws, DayBasic,DayIEEEDataInterface, SimplorerBasic,SimplorerKernel, SimplorerSchematic,simplorer_vhdlams

al4generic, designer_desktop, ensemble_gui,nexxim_gui, nexxim_netlist, siwave_gui,

ANSYS SIwave

siwave_reporter, siwave_solver, nexxim_dc,nexxim_eye, nexxim_tran, nexxim_ami,designer_hspice, siwave_level1,siwave_level2, siwave_level3, al4generic

siwave_gui, siwave_level1ANSYS SIwave - DC

designer_desktop, ensemble_gui,nexxim_gui, nexxim_netlist, siwave_gui,

ANSYS SIwave PI

siwave_reporter, designer_hspice,siwave_pi_adv, siwave_level1, siwave_level2

siwave_gui, siwave_reporter, siwave_pi_advANSYS SIwave PI Advisor Suite

al4generic, siwave_gui, siwave_reporterANSYS SIwave Pre/Post Processor

siwave_psi_ac_solveANSYS SIwave PSI Solver

simplorer_LibSMPSANSYS SMPS Power Package

An * after a feature name indicates that an item is a product variable and can be used on a stand-alonebasis to start a product run in the Mechanical APDL (ANSYS) application.

Products listed here use the ANSYS license manager (ansyslmd vendor daemon). ANSYS, Inc. doessupply licenses for products that use other license managers, such as the Fluent product which is notlisted above; however, those products will use their respective license managers. To determine the licensemanager to which the license applies, see Recognizing an ANSYS, Inc. License File (p. 7)



GlossaryANSLIC_ADMIN A utility that centralizes the various ANSYS product licensing administrat-

ive functions. See also, License Server Administration Using ANSYS LicenseManagement Center (p. 31).

ANSWAIT An environment variable that will allow you to queue your ANSYS job inthe event that all ANSYS licenses are in use. Once a license becomesavailable and you are next on the queue, your ANSYS job will automatic-ally start.

ANSYS License Manager The ANSYS License Manager consists of three components. The first twoare FlexNet components; the last one is an ANSYS component. See thedefinitions of each for more information.

• lmgrd

• ansyslmd

• ansysli_server

ansysli see Licensing Interconnect

ANSYS License Manage-ment Center

The ANSYS License Management Center is a browser-based user inter-face that centralizes many of the ANSYS licensing administrative functions.

ansysli_client A component of the Licensing Interconnect that is run by ANSYSapplications on client systems. No user configuration or administra-tion is required or associated with this component.

ansysli_monitor The ansysli_monitor runs on the same machine where the an-sysli_server is running and ensures that the Licensing Interconnectis functioning correctly. If the Licensing Interconnect is not running,ansysli_monitor can restart it. If the Licensing Interconnect is runningbut is not responsive, ansysli_monitor can kill and restart it.

ansysli_server A component of the Licensing Interconnect that is run on the licenseserver systems. Use ANSLIC_ADMIN to manage (start, stop, etc.).

ansysli_server.log The Licensing Interconnect log file, it provides a chronicle of Licens-ing Interconnect licensing activity, including problems. The LicensingInterconnect log file is located in the licensing directory by default.

ansysli port number Communication channel by which the ANSYS, Inc. applications commu-nicate with the Licensing Interconnect. The default ansysli port numberis 2325.

ANSYSLMD_LICENSE_FILE An environment variable that may be used to specify the license servermachine from which you want to check out a license.

ansyslmd This is one of the FlexNet components of the ANSYS license managerused to process ANSYS product licensing requests, including issuing andreturning licenses. ansyslmd, often referred to as the vendor daemon,



is started by lmgrd and must be running to perform the aforementionedtasks.

ansyslmd.ini File that resides in the licensing directory. It is created by ANSLIC_ADMINutility options Specify the license server machine and Modify licensemanager startup options.

backup server In a three-server (redundant triad) network, the two servers not chosento be the master are the backup servers. If the master server goes down,the backup server listed next in the license file automatically assumesthe role of master. (A backup server is also known as a shadow server.)

borrowable license A borrowable license is a license that you can use temporarily outsideof the company facility (such as at home on a laptop). A special licensekey is required before any license can be borrowed.

build date The build date is the year, month, and date the ANSYS application wasbuilt. The version field in the license file specifies the latest build datethat can be run using that license. It may also appear as 9999.9999 if amaintenance agreement is not applicable.

Capability ANSYS, Inc. has assigned identifiers to each of the specific areas of func-tionality in the software. We refer to these identifiers as capabilities, whichyou may see in ANSYS, Inc. licensing displays and logs. Each capabilitycan be satisfied by at least one license feature; often, multiple licensefeatures can satisfy a particular capability.

client A client is a machine that requests licenses but is not a license servermachine (i.e., does not have licenses installed on it).

feature The word feature, when used in the descriptions of the licensing utilities,refers to the ANSYS product. See Product Variable Table (p. 101) for thelist of ANSYS products and their corresponding license features.

FlexNet A component of the ANSYS license manager used for all ANSYS products.Also called FlexNet License Manager. The FlexNet component authentic-ates and processes all license requests.

FlexNet license log file Typically referred to as the FlexNet Debug Log File, it contains informationrelevant to licensing activity. This file provides a way of tracking licensingproblems that may occur. The licensing log file, license.log, is locatedin the licensing directory by default.

FlexNet port number Communication channel by which the license manager communicateswith the client (Licensing Interconnect). The default FlexNet port numberis 1055.

floating license Anyone on the network can run a licensed ANSYS product, up to thelimit specified in the license file. Floating licenses require the licensemanager daemon (lmgrd) and the vendor daemon (ansyslmd) to berunning to count the concurrent usage of the licenses.

license See license task.


Glossary

license borrowing License borrowing allows a user to take a license for use outside of thecompany facility, such as for an engineer to take a license home on hislaptop.

license file A license file grants access to run specified products. Each licensedproduct will have an entry in the license file, ansyslmd.lic or an-soft.lic, which will reside in the license_files directory. Proper install-ation of a license file grants access to ANSYS products. Install the licensefile using the ANSYS License Management Center or during the install-ation process.

license key The actual full license for the product.

license.log Typically referred to as the FlexNet Debug Log File, it contains informationrelevant to licensing activity. This file provides a way of tracking licensingproblems that may occur. The licensing log file is located in the licensingdirectory by default.

license manager Software used for licensing ANSYS, Inc. products. The ANSYS LicenseManager has two components: the FlexNet software and the LicensingInterconnect.

license options file A FlexNet file containing license manager-related resource information.By default, the file is named ansyslmd.opt and resides in the li-cense_files directory. You may specify the following information in theoptions file:

• Licenses that are reserved for individuals, groups, or machines

• Those individuals, groups, or machines that are denied access to licenses

license server machine A license server machine is a computer that you have designated to bethe administrator of ANSYS product licenses; the licenses are installedon the server machine(s). One or three systems (redundant triad) can beused to administer any particular set of ANSYS product licenses.

license task Each concurrent use of an ANSYS product is a license task. Each use ofan ANSYS product will take a number of license tasks from the totalnumber available.

licensing directory The default location for the licensing files. On Linux systems, the licensingdirectory is /ansys_inc/shared_files/licensing. On Windowssystems, the default licensing directory is <OS_Drive>\ProgramFiles\ANSYS Inc\Shared Files\Licensing, located in thesame drive as the operating system.

Licensing Interconnect Communications between the ANSYS applications, lmgrd, and an-syslmd are handled by an intermediary process called the ANSYS Licens-ing Interconnect. The ANSYS Licensing Interconnect communicates withthe FlexNet license manager to authenticate and process all license re-quests.



Licensing Interconnect LogFile

Provides a chronicle of Licensing Interconnect licensing activity, includingproblems. The Licensing Interconnect log file, ansysli_server.log,is located in the licensing directory by default.

lmadmin A group of users that you designate to have the ability to perform licenseadministrative tasks that are considered disruptive.

lmgrd One of the FlexNet components of the ANSYS License Manager, used toprocess ANSYS product licensing requests, including issuing and returninglicenses.

LMTOOLS LMTOOLS is a Windows-only utility that will perform various license ad-ministrator functions, such as listing the users of licensed products.LMTOOLS is no longer sufficient to manage the ANSYS License Managerand the Licensing Interconnect. You should use the ANSYS LicenseManagement Center to start or stop the license manager and use theANSLIC_ADMIN utility to check the license status, etc. However, if youhave well-established processes to manage FlexNet, you can continueto use LMTOOLS (see Advanced Licensing Configuration Options (p. 19)).

lmutil lmutil is a FlexNet-supplied utility that will perform various licenseadministrator functions including: rereading the license file, shuttingdown the license manager, starting the license manager, and listing theusers of licensed products. lmutil is the underlying process in severalof the ANSYS License Management Center and ANSLIC_ADMIN options.

master server In a three-server (redundant triad) network, one of the servers must bethe master server. The server listed first in the license file automaticallyassumes the role of master. The other two license servers machines areshadow servers (or backup servers). In a one-server network, that serveris automatically the master.

options file See license options file.

path When used in the context of a license file path, the list of places that aresearched in order to locate a valid license file. The path is built fromvalues in the ANSYSLMD_LICENSE_FILE environment variable, settingsin the ansyslmd.ini file, or an actual license file.

product variable Some ANSYS products have been assigned a specific product variablevalue. Use this product variable value when starting a job to specifywhich ANSYS product is to be run. For Mechanical APDL, the productvariable may be set by using the -p command line option, the AN-SYS171_PRODUCT environment variable, or the Mechanical APDLlauncher. See Product Variable Table (p. 101) for a list of ANSYS productsand their associated product variables/feature names.

quorum You may designate either one or three machines to be license servers.In a three-server (redundant triad) network, license manager daemonsmust be running on the majority (2) of the server machines (a quorum)before requests for licenses will be processed.

redundant (triad) servers Having multiple machines designated as license servers for an ANSYSproduct. Redundancy can be achieved either by having three license


Glossary

server machines working together in tandem, where two of the threemust be running at all times but serving from a single set of licenses, orby having any number of license server machines running independently,each serving from different license files.

server See license server.

shadow server See backup server.

Tamper Resistant License A sixty character encryption used in the licensing file.

task See license task.

TRL Tamper Resistant License

vendor daemon FlexNet terminology used to refer to the vendor-specific component ofthe FlexNet license manager. The ANSYS vendor daemon is ansyslmd.




IndexSymbols

AA FlexNet License Status

display, 38Academic licenses, 48, 62Agreement number, 69All licenses reserved, 91ANS_FLEXLM_DISABLE_DEFLICPATH, 47ANSLIC_ADMIN utility, 57

debug log, 37definition, 109display customer number, 69display queued licenses, 68display the license status, 68gather diagnostic information, 39, 69modify startup options, 66run the ANSYS borrow utility, 63set license preferences, 62set site preferences, 65specify product order, 65specifying the license server, 59using its options (Linux), 57view FlexNet debug log file, 69View status/diagnostic options, 68view the ansysli debug log file, 69

ANSWAIT environment variable, 54definition, 109

ANSYSlicenses, 8

ANSYS License Management Center, 32display FlexNet license status, 38display license server hostid, 36functionality, 32install license, 32License Manager run mode, 40log, 38requirements, 31, 71rereading license manager settings, 35shutdown the license manager, 34start the license manager, 34update license, 32using its options , 32

ANSYS Licensing Guideviewing, 41

ansys_pid utility, 80ansysli, 2

definition, 109port number, 13

ansysli port numberdefinition, 109

ansysli_clientdefinition, 109

ansysli_monitordefinition, 109

ansysli_server, 3definition, 109

ansysli_server log filedefinition, 109

ANSYSLI_SERVERS, 47ANSYSLI_TIMEOUT_CONNECT, 47ANSYSLI_TIMEOUT_TCP, 47ansyslmd, 2-5

definition, 109ansyslmd.ini

definition, 110ansyslmd.ini file, 24, 48, 59ansyslmd.lic file, 2-3, 24, 32, 48ansyslmd.opt file, 26, 61ANSYSLMD_LICENSE_FILE, 3, 47ANSYSLMD_LICENSE_FILE environment variable

definition, 109

BBackup server

definition, 110boot_ansflex file, 20Borrowable license

definition, 110Borrowing

licenses, 55, 63Build date

definition, 110

CCaching FlexNet licenses, 19, 66Caching license servers, 67Capability

definition, 110Changing Java Version, 44Client configuration, 47Clients

definition, 110Commands (Linux)

ps, 20, 22Commercial licenses, 48, 62Communications requirements, 12Complete unfinished client licensing installation config-uration, 57Configuring redundant (triad) servers, 27Configuring TCP/IP, 12



Configuring the license server machine, 24.cshrc file, 59customer number, 69

Ddaemon

vendor, 4-5Daemons

starting at system boot time, 20, 22starting manually, 34vendor (ansyslmd), 3

Debugging, 79design points

licensing, 54Diagnostic information

gathering, 69Diagnostic log files, 39Display customer number, 69Display FlexNet License Status, 38Display license server hostid, 36Display license status, 68Display queued licenses, 68Dongles

using, 71

EEnabling Secure Connections, 41Environment variables

ANS_FLEXLM_DISABLE_DEFLICPATH, 47ANSWAIT, 54ANSYSLI_SERVERS, 47ANSYSLI_TIMEOUT_CONNECT, 47ANSYSLI_TIMEOUT_TCP, 47ANSYSLMD_LICENSE_FILE, 3, 47

Error messages, 79license borrowing, 97license log file, 98licensing, 20, 90

Establishing user licensing preferences, 48Expired license, 92

FFeature

definition, 110Feature names, 101Files

ansyslmd.ini, 24, 48, 59ansyslmd.lic, 32, 48ansyslmd.opt, 26, 61boot_ansflex

init_ansysli, 20.cshrc, 59

init_ansysli, 20init_ansyslm_tomcat, 22license, 2-3

installing, 24license (ansyslmd.lic), 24license files format, 3license.log, 20, 22

viewing, 37-38, 69sample license files, 6

Firewall settings, 27FlexNet

compatibility with other software, 1definition, 110license, 36port number, 13

FlexNet debug log (license.log)viewing, 37

FlexNet debug log file (license.log)viewing, 38, 69

FlexNet icensing Guideviewing, 41

FlexNet license options file (ansyslmd.opt)editing, 26

FlexNet Licensesviewing, 36

FLEXNet Manager, 19, 57FlexNet Manager, 31FlexNet port number

definition, 110floating license

definition, 110Floating licenses, 1, 8Format of license files, 3Freeing a license, 57Functions requiring lmadmin group privileges, 25

GGather diagnostic information, 69Group

creating, 25Group restrictions

defining, 25

Hhigh performance computing

licensing, 51hostid, 4, 8hostname, 4, 8HPC licensing, 51HPC Parametric Pack licensing, 54HTTPS

configuring, 41


Index

IINCREMENT lines, 5, 101init_ansysli, 20init_ansyslm_tomcat, 22Installation

license, 32uninstalling the license manager, 28

Installing license files, 24Installing the license manager, 11

Linux, 16post-installation instructions, 20Windows, 14

installing the license manager, 13Complete unfinished client licensing installationconfiguration, 57

Interconnectdebug log , 37

Interconnect debug log (license.log)viewing, 37

is down error message, 91

JJava

version, 44

LLicense

error message: has expired, 92installing, 32updating, 32

License administration, 31, 57creating lmadmin group, 57

License borrowing, 55, 63definition, 111running, 55running the borrow utility, 63setup, 63

License borrowing error messages, 97License file installation, 24License files, 2-3

definition, 111example, 6format, 3INCREMENT lines, 5recognizing, 7SERVER lines, 4settings precedence, 48specifying the location, 24VENDOR lines, 4

License keydefinition, 111

License log file (license.log)

definition, 110-111error messages, 98

License log file error messages, 98License Management Center, 31, 59

launching, 59License manager

advanced configuration, 19compatibility with other software, 1Complete unfinished licensing client installationconfiguration, 57Complete unfinished licensing installation configur-ation, 32components, 2daemon, 112defined, 1definition, 111installation prerequisites, 14installing, 11, 13installing on Linux, 16installing on Windows, 14modifying startup command options, 24modifying startup options, 66post-installation instructions, 20shutting down, 34shutting down with ANSLIC_ADMIN, 34starting at system boot time, 20starting manually, 34starting with ANSYS License Management Center,34uninstalling, 28

License Managerrereading settings, 35

License Manager Run Mode, 40License methods

sharing vs. separate, 62License options file (ansyslmd.opt)

definition, 111License preferences

academic vs. commercial, 48, 62License queuing, 54, 57License server

error message: is down, 91specifying, 26

license server machines, 2License server machines

definition, 7, 111display FlexNet license status, 38display hostid, 36master, 7selecting, 8three-server network, 7

License server manager, 2



License serverscaching, 67configuring, 24designating for license checkout, 57, 59error messages, 20network licensing , 2redundancy, 9shutting down the license manager daemon, 34specifying, 59

License statusdisplay, 68

License taskdefinition, 111

license.logviewing, 37

license.log file, 20, 22viewing, 38, 69

Licensescustomer number, 69floating, 8freeing, 57installing/updating, 32waiting for available, 54

Licensingdebugging, 79error messages, 79problem situations, 81process, 1sample scenario, 61selecting server machines, 8separate method, 62sharing method, 62tasks, 8three-server license network, 7

Licensing Configuration Detailsviewing, 41

Licensing directory, 1Licensing environment

setting up, 31, 57Licensing error messages, 90Licensing Interconnect, 2

defining group restrictions, 25port number, 13running independently of FlexNet, 19running without FlexNet, 19

Licensing Interconnect (ansysli_server), 3Licensing preferences

establishing for users, 48lmadmin group, 25, 57lmdown, 25lmgrd, 2

utility definition, 112

lmhostid, 36lmremove, 25lmreread, 25LMTOOLS, 19, 57lmutil

utility definition, 112Log file, 112

(see also license log file)

MMaster server, 7, 20, 22

definition, 112

NNetwork File System

licensing failures on, 24Network licensing

network licensing considerations, 8queuing facility, 54shutting down the license manager, 34starting license manager at system boot time, 20starting license manager manually, 34

No license file found for feature error message, 93No licenses are currently available error message, 90

PPath

definition, 112Pool of available tasks, 8Port number

FlexNet, 4Port Number

changing Tomcat port number, 23Port numbers

changing, 13FlexNet, 13Licensing Interconnect, 13

Preferencessetting, 48, 62

Product list, 101Product order

specifying , 65Product variable

definition, 112PS command, 20, 22

QQueued licenses

display, 68Queuing, 54, 57Quorum

definition, 112


Index

RRedundant (triad) servers

setting up, 27Redundant server options, 9Redundant servers

definition, 112Requirements

ANSYS License Management Center, 31, 71Reread License Manager Settings, 35root login, 28, 57Running the Licensing Interconnect and FlexNet inde-pendently, 19-20Running the Licensing Interconnect without FlexNet,19

SSample license files, 6Sample licensing scenario, 61SERVER lines, 4Set site preferences, 65Shadow server

definition, 113Shutting down the license manager, 34Site preferences

setting , 65Specify product order, 65Specifying firewall settings, 27Specifying the license server, 26, 59Starting the license manager, 34Starting the license manager at system boot time, 20Startup options for license manager

modifying, 66Status

viewing, 68superuser login, 28, 57Symbolic links, 1

TTasks, 8TCP/IP

dial-up connection, 12testing whether TCP/IP is installed, 12

TCP/IP requirements, 12Three-server network, 7Tomcat

changing port number, 23starting at system boot time, 22

Troubleshootingansys_pid utility, 80getting additional debugging information, 79license borrowing errors, 97license log file errors, 98

licensing error messages, 90problem situations, 81

Troubleshooting ANSYS error messages, 79

UUnavailable licenses, 90Uninstalling the license manager, 28Updating license, 32User privileges, 57

Using the FlexNet options file, 26Using Dongles, 71

VVendor daemon, 2-3, 5vendor daemon

definition, 113Vendor daemon (ansyslmd), 4VENDOR lines, 4View status/diagnostic options, 68View the ansysli debug log file, 69Viewing FlexNet Licenses, 36Viewing the FlexNet debug log, 37Viewing the FlexNet debug log file, 38, 69Viewing the interconnect debug log, 37

WWANs, 8Wide area networks, 8




Installation Guide for Linux


2600 ANSYS Drive 000408Canonsburg, PA 15317 ANSYS, Inc. is

certified to ISO9001:2008.

[email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494


The information in this guide applies to all ANSYS, Inc. products released on or after this date, until supersededby 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1. System Prerequisites .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1. CAD Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2. Disk Space and Memory Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3. Requirements for the GPU Accelerator in Mechanical APDL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4. Additional Hardware and Software Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.5. Third-Party Software and Other Security Considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2. Platform Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1. Utilizing CPU Hyperthreading Technology with ANSYS CFD Solvers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2. Compiler Requirements for Linux Systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3. Select Your Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3. Installing the ANSYS Software for a Stand-alone Linux System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1. Pre-Installation Instructions for Download Installations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2. Product Download Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3. Installing from a USB Drive .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.4. Mounting the DVD Instructions for DVD Installations (Linux x64 Only) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.5. Product Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.5.1. Specifying CAD Configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.5.2. ANSYS License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.5.2.1. Registering the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214. Installing the ANSYS Products and the License Server on Different Linux Machines . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.1. Pre-Installation Instructions for Download Installations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2. Product Download Instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3. Installing from a USB Drive .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.4. Mounting the DVD Instructions for DVD Installations (Linux x64 Only) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.5. Product Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.5.1. Specifying CAD Configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.5.2. ANSYS License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.5.2.1. Registering the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.5.3. Network Installation and Product Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.5.3.1. Export the /ansys_inc Directory .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.5.3.2. Run the Product Configuration Utility on All Client Machines .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5. Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.1. Post-Installation Procedures for Mechanical APDL and ANSYS Workbench Products .... . . . . . . . . . . . . . . . . . . . . . 36

5.1.1. Post-Installation Procedures for ANSYS CFX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.1.1.1. Setting up CFX-RIF .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.1.1.2. Setting up ANSYS TurboGrid Release 17.1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.1.1.3. Using the ANSYS CFX Launcher to Set Up Users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.1.2. Post-Installation Procedures for ANSYS Fluent .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1.3. Post-Installation Procedures for ANSYS Polyflow .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1.4. Post-Installation Procedures for ANSYS ICEM CFD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1.5. Post-Installation Procedures for ANSYS Autodyn .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1.6. Post-Installation Procedures for Other Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.2. Product Localization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425.2.1. Translated Message File Installation for Mechanical APDL ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.3. Launching ANSYS, Inc. Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436. Installing the ANSYS, Inc. Product Help Documentation Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457. Silent Mode Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7.1. Silent Product and License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.2. Silent Product Configuration/Unconfiguration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50



7.3. Silent Media Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.3.1. Silent Uninstall .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8. Configuring CAD Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.1. Using the CAD Configuration Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

8.1.1. Unconfiguring .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548.1.2. Running the CAD Configuration Manager in Batch Mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.1.3. NX Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

8.2. Configuring the Geometry Interface for NX for ANSYS Workbench Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569. Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5710. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

10.1. Installation Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5910.1.1. Gathering Diagnostic Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5910.1.2.The GUI Installation Process Hangs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5910.1.3.The Target Machine Does Not Have a DVD Drive .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5910.1.4. CAD Configuration Manager Help Does Not Load .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6010.1.5. Cannot Enter Data in Text Fields .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6010.1.6. Download and Installation Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6010.1.7. System-related Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.1.8. High Performance Computing Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

10.2. Installation Troubleshooting - Mechanical APDL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.2.1.Your batch jobs terminate when you log out of a session .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.2.2. Mechanical APDL Documentation File for User Interface Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.2.3. Launcher Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6210.2.4. FORTRAN Runtime Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

10.2.4.1. Intel Linux 64 Systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6210.2.4.2. Intel EM64T Linux x64 Systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6210.2.4.3. AMD Opteron Linux x64 Systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

10.3. Installation Troubleshooting - ANSYS Workbench .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6210.3.1. Startup or Graphics Problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

10.4. Installation Troubleshooting - ANSYS CFX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6310.4.1. CFX Distributed Parallel Runs Fail .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10.5. Contacting Technical Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6311. Applications Included with Each Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


Linux Installation Guide

List of Tables

1.1. Supported Linux Platforms .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2. CAD Support by Platform ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1. OpenMotif Versions for SUSE Linux Enterprise .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2. Compiler Requirements for All Linux Versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.1. Startup Commands .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43




Chapter 1: Installation Prerequisites for Linux

This document describes the steps necessary to correctly install and configure all ANSYS, Inc. productson Linux platforms for Release 17.1. These products include:

• ANSYS Structural Mechanics

– ANSYS Mechanical Products (includes Mechanical APDL and Mechanical, where supported)

– ANSYS Customization Files for User Programmable Features

• ANSYS Explicit Dynamics

– ANSYS Autodyn

– ANSYS LS-DYNA

• ANSYS Fluid Dynamics

– 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 Additional Tools

– ANSYS Composite PrepPost

– ANSYS Icepak (includes ANSYS CFD-Post)

– Remote Solve Manager Standalone Services

• ANSYS Geometry Interfaces

– ACIS

– CATIA, Version 4


– NX

– Parasolid



Notes Not all products may be available on all Linux platforms. Please see the remainder of thisdocument for detailed information on which products are available on which platforms.

At Release 17.1, ANSYS BladeGen, Vista CCD, Vista CPD, Vista RTD, and Vista AFD are not supported onLinux platforms.

ANSYS Workbench and ANSYS EKM Desktop are installed by default as product components to mostANSYS, Inc. products. ANSYS Workbench is not installed as part of the products under ANSYS AdditionalTools. ANSYS Workbench includes the following applications:

• DesignModeler

• Design Exploration

• Meshing

• Remote Solve Manager

• Fluent Meshing

• FE Modeler

• EKM Client

Important Notice

If you wish to run multiple releases of ANSYS, Inc. software, you MUST install them chronologically (i.e.,Release 16.0 followed by Release 17.1). If you install an earlier release after installing Release 17.1, youwill encounter licensing issues that may prevent you from running any products/releases. If you needto install an earlier release after you have already installed Release 17.1, you MUST uninstall Release17.1, then re-install the releases in order.


The following features are new or changed at Release 17.1. Please review these items carefully.

• ANSYS Reaction Design Products (Chemkin) are now included in the product installation and can be selectedon the product selection menu for installation.

1.1. System Prerequisites

ANSYS, Inc. Release 17.1 products are supported on the Linux platforms and operating system levelslisted in the following tables. Patches listed may be superseded by newer versions; see your vendor forthe most current version. See the individual Platform Certification Specifics in this guide for more in-formation on specific platform requirements. For up-to-date information on hardware platforms or op-


Installation Prerequisites for Linux

erating systems that have been certified, go to http://www.ansys.com/Support/Platform+Support. (ThisURL is case-sensitive.)

Table 1.1: Supported Linux Platforms

AvailabilityPlatformarchitecture(directory name)

Operating SystemProcessorPlatform

Download/ USB

linx64Red Hat Enterprise Linux 6.5through 6.7, Red Hat Enterprise

EM64T/Opteron 64Linux x64

Linux 7.0 through 7.1, SUSELinux Enterprise 11 SP3 andSP4, SUSE Linux Enterprise 12SP0 and SP1

Supported Platforms for High Performance Computing Please see the discussions on ConfiguringDistributed ANSYS and Configuring ANSYS CFX Parallel for detailed information on supported platformsfor distributed computing.

1.1.1. CAD Support

The following CAD and auxiliary programs are supported on the indicated products and platforms.Products are:

A = Mechanical APDLW = ANSYS WorkbenchI = ANSYS ICEM CFD standalone (some CAD systems may require the integrated ANSYS Work-bench Reader)

Table 1.2: CAD Support by Platform

Linux x64

A , ICATIA 4.2.4

W, ICATIA V5–6R2015

W, IGAMBIT 2.4

A, W, IParasolid 27.0

A, W, IACIS 2016 1.0 1

A, W, INX 8.5

A, W, INX 9.0

A, W, INX 10.0

W,STEP AP203, AP214

A 2, W, I 3IGES

IGEMS

I4Rhinoceros

1. For ANSYS ICEM CFD standalone, ACIS 18.0.1 is the supported version for all platforms.

2. MAPDL supports 5.1 by default, but 5.2 is also supported if the IOPTN command is used.

3. IGES Versions 4.0, 5.2, and 5.3 are supported.



System Prerequisites


4. Support limited to Rhinoceros 3 and earlier.

1.2. Disk Space and Memory Requirements

You will need the disk space shown here for each product for installation and proper functioning. Thenumbers listed here are the maximum amount of disk space you will need. Depending on the optionsselected for each product, you may require less.

Disk SpaceProduct

11.7 GBANSYS Mechanical APDL

8.2 GBANSYS Autodyn

9.4 GBANSYS LS-DYNA

9.6 GBANSYS CFX

8.4 GBANSYS TurboGrid

10.6 GBANSYS Fluent

8.9 GBANSYS Polyflow

8.8 GBANSYS ICEM CFD

10.3 GBANSYS Icepak

8.3 GBANSYS CFD Post only

8.2 GBANSYS Forte

4.0 GBANSYS Geometry Interfaces

4.2 GBANSYS Composite PrepPost

Memory Requirements You must have a minimum of 8 GB of memory to run product installations;16 or 32 GB of memory is recommended.

1.3. Requirements for the GPU Accelerator in Mechanical APDL

Your system must meet the following requirements to use the GPU accelerator capability in MechanicalAPDL:

• The machine(s) being used for the simulation must contain at least one supported NVIDIA GPU card or oneIntel Xeon Phi coprocessor. The following cards are supported:

NVIDIA Tesla K20c (both workstation and server)NVIDIA Tesla K40c (both workstation and server)NVIDIA Tesla K80 (server with GPU cooling solution only, 2 GPUs consume 2 ANSYS HPC licenses)NVIDIA Quadro K5000NVIDIA Quadro K5200NVIDIA Quadro K6000NVIDIA Quadro M6000Intel Xeon Phi 7120Intel Xeon Phi 5110Intel Xeon Phi 3120

• For NVIDIA GPU cards, the driver version must be 346.59 or newer.



• For Intel Xeon Phi coprocessors, the driver version must be “MPSS 3.5” or newer.

Note

Mechanical APDL assumes that the Intel Xeon Phi coprocessor driver is installed in /opt/in-tel/mic/coi. If the installation is located in a different folder, set the ANS_MIC_LIB_PATHenvironment variable to the path where the Xeon Phi driver is installed (for example,/mypath/mic/coi).

1.4. Additional Hardware and Software Requirements

• Intel 64 / AMD64 system with a supported operating system version installed

• 8 GB of RAM

• 128 GB free on the hard drive is recommended

• TCP/IP for the license manager (see the ANSYS Licensing Guide for more information on TCP/IP)

• Approximately twice as much swap space as memory. The amount of memory swap space on the systemmay limit the size of the model that can be created and/or solved.

• Discrete graphics card with the latest drivers and compatible with the supported operating systems. Whenworking with large 3D models, use of a recent NVIDIA Quadro, AMD FirePro or similar card is recommended.

For information on the most recently tested NVIDIA and AMD graphics cards, see ANSYS.com>Support> Platform Support and view the Graphics Cards Tested PDF for your release.

A minimum screen resolution of: 1024 x 768 (4:3 aspect ratio), 1366 x 768 (16:9 aspect ratio) or 1280x 800 (16:10 aspect ratio) with minimum 24 bit color. A higher screen resolution such as 1920x1080(16:9) or 1920x1200 (16:10) is strongly recommended for most applications.

Note

– A number of cosmetic display issues have been reported when running the installationprogram on Linux platforms using AMD graphics cards. These issues do not affect theinstallation functionality.

– Use of Ultra High Definition (4K) graphics cards may cause a number of cosmetic displayissues (including enlarged or reduced text and incorrect positioning of option labels).These issues do not affect the installation functionality.

• X11, OpenGL graphics libraries

• Mesa-libGL (OpenGL) is required to run data-integrated ANSYS Workbench applications such as Mechanical.

• For most applications, a three-button mouse is required to access all available functionality.

• PDF reader software is required to read the installation guides and other user documentation.

• CFX-RIF requires 32-bit libraries (even when running on a 64-bit machine). For details, see Setting up CFX-RIF (p. 38).



Additional Hardware and Software Requirements

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 installationto work properly, you must allow access to these products.

Executable NameProduct Name

tclshTcl

wishTk

perlPerl

gzipGNU gzip

tarGNU tar

ANSYS, Inc. products may have softlinks that require 777 permissions. In addition, the following third-party products are known to contain softlinks that require 777 permissions:

• CPython

• GCC

• HPMPI

• IMPI

• INTELMPI

• MainWin

• Mono

• MPICH

• OPENMPI

• PCMPI

• Perl

• Python

• Qt

• Qwt



Chapter 2: Platform Details

Linux

For ALL 64-bit Linux platforms, OpenMotif, and Mesa libraries should be installed. These libraries aretypically installed during a normal Linux installation. You will also need the xpdf package to view theonline help.

ANSYS products require OpenMotif. After installing SuSe Linux Enterprise, review the table below andinstall the appropriate version of OpenMotif. (You may need to use "rpm -iv -force" to install these.)

Table 2.1: OpenMotif Versions for SUSE Linux Enterprise

OpenMotif Zypper PackageOpenMotif VersionSUSE Linux Enterprise Release

openmotif22-libs oropenmotif22-libs-32bit

openmotif22-libs-2.2.4-139.1 oropenmotif22-libs-32bit-2.2.4-139.1.x86_64

SUSE Linux Enterprise 11 SP 3

motifSLES 11 SP4: motif-2.3.4-1SUSE Linux Enterprise 11 SP 4

motifSLES 11 SP4: motif-2.3.4-1SUSE Linux Enterprise 12 SP 0

motifSLES 12 SP1:motif-2.3.4-4.15.x86_64

SUSE Linux Enterprise 12 SP 1

For more information on OpenMotif libraries for your platform, see http://www.motifzone.net.

Red Hat Enterprise Linux 6.5 through 6.7 and 7.0 through 7.1 You need to install the followinglibraries:

• libXp.x86_64

• xorg-x11-fonts-cyrillic.noarch

• xterm.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



http://www.motifzone.net.

• compat-gcc-34.x86_64

• gtk2.i686

• libXxf86vm.i686

• libSM.i686

• libXt.i686

• xorg-x11-fonts-ISO8859-1-75dpi.noarch

Red Hat no longer includes the 32-bit libraries in the base configuration so you must install those sep-arately.

Additional requirements for Intel, AMD Opteron, and EM64T Linux systems are detailed below.

ANSYS, Inc. License Manager Linux x64 systems running the ANSYS, Inc. License Manager requirethe 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 If you are running ANSYS Workbench using the KDE desktop environment, setthe focus stealing prevention level to "None" to prevent the project save dialog boxes from appearingbehind the application window:

1. Use the kcontrol command to launch the KDE Control Center.

2. In the Control Center window, select Desktop> Window Behavior> Advanced.

3. Change Focus Stealing Prevention Level to None.

4. Click Apply.

If you are running on KDE 4 or if the kcontrol command does not exist, use System Settings to setthe focus stealing prevention setting level to "None":

1. Use the systemsettings command to launch the System Settings.

2. In the System Settings window, select General> Window Behavior> Focus.

3. Change Focus Stealing Prevention Level to None.

4. Click Apply.

Semaphore Limit On some Linux systems, ANSYS Workbench reaches a system limit on the numberof semaphores in the Linux configuration. In this case, you will see a message similar to the following:

sem_lock->semop->op_op: Invalid argument


Platform Details

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 limitwhen rebooting, add the above command to one of your system’s startup scripts by copying the com-mand into a file called mod_sem and then setting up the following links to execute the file each timeyou restart your system:

cp mod_sem /etc/init.dln -s /etc/init.d/mod_sem /etc/rc3.d/S61mod_semln -s /etc/init.d/mod_sem /etc/rc5.d/S61mod_sem

Mechanical, Meshing, DesignModeler, and FE Modeler Applications If you are using a localizedoperating system (such as French or German), you must set the mwcontrol VisualMainWin control onany machines running these applications in order for these applications to recognize the correct numer-ical format. ANSYS Workbench must already be installed before setting this control.

First, you need to ensure that the /v171/aisol/WBMWRegistry/ directory has write permissions.From the /v171/aisol/ directory, issue the following command:

chmod -R 777 WBMWRegistry/

Then, use the following procedure to set mwcontrol for your locale:

1. cd to <wb_install directory>/v171/aisol

2. Issue the following command:

./.workbench -cmd mwcontrol

3. On the MainWin Control Panel, select Regional Settings.

4. Select the Regional Settings tab.

5. Change the language in the dropdown to match the language you want to use.

6. Check the Set as system default locale option.

7. 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 memorythat 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, the following should be addedto the /etc/security/limits.conf file:

* hard memlock unlimited* soft memlock unlimited

The need for increasing the limits may be indicated by the following error message with Platform MPI:

fluent_mpi.16.0.0: Rank 0:1: MPI_Init: ibv_create_cq() failedfluent_mpi.16.0.0: Rank 0:1: MPI_Init: Can't initialize RDMA devicefluent_mpi.16.0.0: Rank 0:1: MPI_Init: MPI BUG: Cannot initialize RDMA protocollibibverbs: Warning: RLIMIT_MEMLOCK is 32768 bytes.This will severely limit memory registrations



When Fluent is launched by a scheduler (like PBSPro, SGE, etc.), these limits may be reset by thescheduler. You may check running the “limit” command within and without the scheduler to compare.Any differences indicate the issue above.

If you use PBSPro, add ulimit -l unlimited directly in the pbs_mom startup script, and let PBSreload the pbs_mom.

If you use SGE, you must change the startup script /etc/init.d/sgeexecd to include the ulimit-l unlimited command as shown in the following example:

-- BEGIN --if [ "$startup" = true ]; then# execution daemon is started on this host!echo " starting SGE_execd"exec 1>/dev/null 2>&1ulimit -l unlimited$bin_dir/SGE_execdelse-- END --

Once this modification is in place, restart SGE to set the correct memory limits on the SGE daemon andany invoked processes.

Using Mechanical APDL with Infiniband On some operating systems, the default amount of physicalmemory that can be pinned/locked by a user application is set to a low value and must be explicitlyincreased. A value recommended by Intel is 90% of the physical memory. Therefore, the followingshould be added to the /etc/security/limits.conf file:

* hard memlock unlimited* soft memlock unlimited

This behavior has been observed on Intel MPI 4.1.3, but might also occur on Platform MPI 9.1.2.1.

Using the Fluent Launcher On Linux systems, you must have the following package (as appropriatefor your platform) installed in order to use the Fluent launcher:

SUSE 11 pr 12: libstdc++33

Using ANSCUSTOM If you use ANSCUSTOM to link your own version of ANSYS Release 17.1 on aSUSE SLES 11.x or 12.x computer, you may see two unsatisfied externals that are system, not ANSYSfiles, due to the linker looking for some system files in a Red Hat directory on a SUSE computer.

To work around this problem, run the following as root:

mkdir –p /usr/lib/gcc/x86_64-redhat-linux/3.4.6ln -sf /usr/lib/gcc/i586-suse-linux/2.95.3/crtbegin.o /usr/lib/gcc/x86_64-redhat-linux/ 3.4.6/crtbegin.oln -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. Thelinker will specify where it is trying to find the crtbegin.o and crtend.o files; that location will bethe last part of the above commands. You can use the Linux locate command to find the existingcrtbegin.o and crtend.o files; that location would be the first part of the above commands.

System Libraries On 64-bit Linux linx64 systems, the ANSYS Release 17.1 executable is looking forsystem libraries that do not have revision numbers appended to the end of their file names. On someSUSE systems, the graphics libraries all have revision numbers appended to the end of the library file-names. In these cases, ANSYS quits because the loader cannot find all of the libraries that it is lookingfor. When running ANSYS Release 17.1, the loader will inform you that it is unable to locate a specific


Platform Details

library (for example, libXm.so). Using the Linux locate command, find the library (libXm.so inthis example) on your system and add the appropriate symbolic link as seen below.

To overcome this possible problem, run the following as root:

ln -sf /usr/lib64/libGLU.so.1.3.060402 /usr/lib64/libGLU.soln -sf /usr/X11R6/lib64/libXm.so.3.0.3 /usr/X11R6/lib64/libXm.soln -sf /usr/X11R6/lib64/libXp.so.6.2 /usr/X11R6/lib64/libXp.soln -sf /usr/X11R6/lib64/libXt.so.6.0 /usr/X11R6/lib64/libXt.soln -sf /usr/X11R6/lib64/libXext.so.6.4 /usr/X11R6/lib64/libXext.soln -sf /usr/X11R6/lib64/libXi.so.6.0 /usr/X11R6/lib64/libXi.soln -sf /usr/X11R6/lib64/libX11.so.6.2 /usr/X11R6/lib64/libX11.soln -sf /usr/X11R6/lib64/libSM.so.6.0 /usr/X11R6/lib64/libSM.soln -sf /usr/X11R6/lib64/libICE.so.6.4 /usr/X11R6/lib64/libICE.soln -sf /lib64/libgcc_s.so.1 /lib64/libgcc.so

For Linux, you may need the following:

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 LinuxANSYS was built and tested on Red Hat using the compilers as noted in Table 2.2: Compiler Requirementsfor All Linux Versions (p. 12). The ANSYS solver is built on Red Hat Enterprise Linux AS release 4 (Update5).

For ANSYS Workbench and ANSYS Autodyn, you may need to increase the stack size; we recommendsetting it to 1 GB. Add the following to your configuration file:

For the Bourne (bash) shell:

ulimit -s 1024000

For the C (csh) shell:

limit stacksize 1024000

Other shells may have different settings; please refer to your shell documentation for specific details.

Intel Xeon EM64TANSYS was built and tested on a generic Intel EM64T system running Red Hat Enterprise Linux AS release5.3.

If you are running on Intel's Xeon EM64T system, we recommend that you turn CPU hyperthreadingoff (default is on). A system administrator needs to reboot the system and enter the BIOS to turnthe hyperthreading option off.

2.1. Utilizing CPU Hyperthreading Technology with ANSYS CFD Solvers

Hyperthreading technology uses one processor core to run more than one task at a time. ANSYS doesnot recommend using hyperthreading technology in conjunction with ANSYS CFD Solvers (Fluent, CFXand AIM Fluids). We recommend that you turn CPU hyperthreading off (default is on). A system admin-istrator needs to reboot the system and enter the BIOS to turn the hyperthreading option off.



Utilizing CPU Hyperthreading Technology with ANSYS CFD Solvers

2.2. Compiler Requirements for Linux Systems

Table 2.2: Compiler Requirements for All Linux Versions

AUTODYNCompilers*

Fluent Compilers*CFXCompilers*

Mechanical APDL,ANSYS WorkbenchCompilers*

Intel 15.0.2(FORTRAN, C,C++)

GCC 4.8.3 (typicallyinstalled as part of theoperating system)

Intel 15.0.2FORTRAN (forcustom solver

Intel 15.0.2 (FORTRAN,C, C++)

modeling usingUser Fortran)and GCC 4.8.4(for custommeshimport/exportexecutables)

* Compilers are required only if you will be using User Programmable Features (UPF), User DefinedFunctions (UDF), or other customization options.

2.3. Select Your Installation

The next step is to select your installation type. Please select the option below that matches your install-ation.

• Installing the ANSYS Software for a Stand-alone Linux System (p. 13)

• Installing the ANSYS Products and the License Server on Different Linux Machines (p. 23)


Platform Details

Chapter 3: Installing the ANSYS Software for a Stand-alone LinuxSystem

This section explains how to install ANSYS, Inc. products, including ANSYS client licensing, as well asthe ANSYS, Inc. License Manager.

The default installation expects you to be logged in as root. You can install as non-root; however, if youare not logged in as root, you will not be able to set the /ansys_inc symbolic link and may potentiallyexperience permission problems. The inability to set the /ansys_inc symbolic link will in no way in-hibit 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 directoryto ensure license manager compatibility and availability among releases and products.

If you did not use the /ansys_inc symbolic link, you must replace all references to /ansys_inc/v171or <install_dir> with the actual installation path you used.

Before You Begin

We recommend that you have the following information available before you begin this installation:

• An account on the ANSYS Customer Portal. If you do not have an account, you may register at https://sup-port.ansys.com/portal/site/AnsysCustomerPortal to receive your own account.

• Your license file from ANSYS, Inc., saved to a temporary directory. For more information, see Registering theLicense Server (p. 21).

• Open port numbers for both the FLEXlm and ANSYS Licensing Interconnect. Defaults are 1055 and 2325,respectively. To verify that these port numbers are available, open a command line and enter the followingcommand:

netstat -a -t

You will see a list of active ports. If 1055 and 2325 are listed, they are already in use and cannot beused for ANSYS, Inc. licensing. In this case, you will need to specify different port numbers where in-dicated later in this installation.

• Your local machine's name, to specify as the license server.

You should also verify that you are running on a supported platform. ANSYS, Inc. products support 64-bit Linux systems running Red Hat 6 (6.5, 6.6 or 6.7), SUSE Linux Enterprise 11 (SP3 or SP4) and SUSELinux Enterprise 12 (SP0 or SP1).

Verify that you have sufficient disk space to download, uncompress, and install the products you willbe installing. Approximate disk space requirements for each product are shown in Disk Space andMemory Requirements (p. 4).

If you have any problems with--or questions about--the installation process, log a Service Request onthe ANSYS Customer Portal to have a Systems Support Specialist assist you.



https://support.ansys.com/portal/site/AnsysCustomerPortal


This section is divided into four sets of instructions:

• Product Download Instructions: This set of instructions describes the download and extraction process.

• Product Installation with Client Licensing: This set of instructions describes the product installation, includingthe client licensing portion.

• License Manager Installation: This set of instructions describes the license manager installation.

• Post-Installation Procedures for All Products: This is a set of instructions that describes any configurationsteps that may be required for the various products.

Both the product and the license manager will be installed on the same machine. You must completeboth the client licensing portion and the license manager installation in order to run ANSYS, Inc. products.

3.1. Pre-Installation Instructions for Download Installations

Before downloading the installation files, you need to accurately determine your platform type. Versionsthat are optimized for different chip sets from the same vendor can have similar names, causing confu-sion. We strongly recommend that you run the getFLEXid script on each machine first. This scriptwill output the correct platform name for each machine on which it is run. This script can be obtainedfrom the ANSYS website, by clicking Support>Licensing>Capture License Server Info.

3.2. Product Download Instructions

To download the installation files from our website, you will need to have a current technical supportagreement.

Depending on the product/platform combination(s) you choose, you may need to download multiplefiles.

1. From the Customer Portal, https://support.ansys.com/portal/site/AnsysCustomerPortal, click Downloads> Current Release.

2. Select your installation operating system (Windows x64 or Linux x64).

3. Select the type of files you wish to download:

• Primary Packages: Individual full packages for the primary ANSYS products.

• ISO Images: ISO images for the DVD installation.

4. Click the appropriate download option.

5. Select your desired download directory and click Save.

6. Repeat this process for each download file.

7. To download Add-On Packages, Tools or Academic Packages, click the + to the right of the appropriateproduct group title to display the download options and download as required.

8. After all downloads have been completed, uncompress each package using standard uncompressionutilities for your specific platform. We strongly recommend that you extract the files into new, temporarydirectories.


Installing the ANSYS Software for a Stand-alone Linux System


• Continue with the steps described in Product Installation (p. 16).

3.3. Installing from a USB Drive

Red Hat Entreprise 6.5 through 6.7 and SUSE Linux Enterprise 11 SP3 and SP4

Insert the USB drive into an appropriate USB slot on your computer. Navigate to the root directory ofthe USB drive and Run ./INSTALL. Continue with the steps described in Product Installation (p. 16).


For these versions, the default auto-mount function permission shows read-only which does not allowyou to install the ANSYS products. To address this issue, manually mount the USB by following the stepsbelow.

1. Open the auto-mount location, right-click the ANSYS170 USB and click Eject.

2. In a root shell, run the following command to determine the usb drive location:

fdisk -l

From the results of the fdisk -l coomand, locate the Device Boot data. The device boot datashould be in a format similar to /dev/sbd1, where sbd1 is the USB location. You will use thedevice boot data when editing the fstab below.

3. Create a mounting point by running the following command:

mkdir /run/media/<username>/ANSYS170

4. Edit the fstab to mount the USB with read/execute permissions.

vi /etc/fstab

Inserting the following line:

/dev/sdb1 /run/media/<username>/ANSYS170 auto users,defaults 0 0

Note the use of the device boot data used in the line.

5. Run the following command to execute the fstab:

mount -a

6. Continue with the steps described in Product Installation (p. 16).

3.4. 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 installationprocedure using either a locally- or remotely-mounted DVD, depending on your site's system.

Note

Typically, a Linux system will mount a local DVD for you under /media/ANSYS171.



Mounting the DVD Instructions for DVD Installations (Linux x64 Only)

For a locally-mounted DVD installation, issue the following commands:

mkdir dvdrom_dirmount -t iso9660 /dev/cdrom dvdrom_dir

If the target machine does not have a DVD reader, first follow the steps for locally-mounted DVD, andthen 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. Asample /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 havedifferent syntax.

3. Log on to the machine where you wish to install ANSYS, Inc. products and issue the following commands:

mkdir dvdrom_dir2mount -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.

3.5. Product Installation

1. Navigate to the directory where you extracted the files. Run ./INSTALL. If you downloaded the install-ation package, this file will reside in the directory where you untarred the downloaded files. If you arerunning from a DVD, this file will reside in the top level of the DVD.

2. The ANSYS, Inc. Installation Launcher appears.



From the options along the left side of the launcher you can install ANSYS products, DocumentationOnly, ANSYS EKM Server, and the ANSYS License Manager. You can access the installation guidefor the ANSYS EKM Server from the Downloads page on the Customer Portal.

The ANSYS, Inc. Quick Start Installation Guide, ANSYS, Inc. Quick Start Licensing Guide, System Re-quirements Guide and complete Installation Help Guide can be accessed through the options locatedalong the bottom of the launcher.

Select the language you want to use from the drop-down menu in the upper right corner. Englishis the default.

3. Click the Install ANSYS Products option.

4. The license agreement appears. Read the agreement, and if you agree to the terms and conditions, selectI Agree. Click the Next arrow, located on the right side of the screen.

5. The directory where you wish to install the ANSYS, Inc. products is shown in the Install Directory field.You can install the products into any directory you wish, but you must have write permissions to the dir-ectory you choose. The default is /ansys_inc. We recommend using the default directory.

The Symbolic Link option is available only if you are installing as root and is enabled (checked)by default. If you choose to disable (uncheck) the symbolic link or are installing as a non-root user,substitute the directory path where you installed the product for all subsequent occurrences of/ansys_inc in this guide.

We strongly recommend that you use the Symbolic Link option. If you do not use this option, youmust install all releases into a common directory to ensure license manager compatibility andavailability among releases and products.

If you have already installed the ANSYS Workbench Framework for Ansoft, you must install anyadditional ANSYS, Inc. products into the same directory.

On Linux, you can choose Disable RSS to disable automatic internet feeds to ANSYS, Inc. products.



Product Installation

Click the Next arrow.

6. If this is a first time installation, you are prompted to enter your license server specification. If you alreadyhave an existing license server specification file, you will not see this window and proceed directly to thenext step.

Enter your ANSYS Licensing Interconnect port number and your ANSYS FlexNet port number. Defaultsare provided and will work in most cases. You may need to check with your IT department toconfirm that the default port numbers are valid or to get different port numbers if necessary.

Specify the hostname for your license server machine(s).


7. All products available in the installation package(s) you downloaded are listed.

The installation program attempts to query your license server to pre-select your installation options.If the query is successful, the following message is displayed:

Your installation options were pre-selected based upon information from your license server.

You can select or deselect any combination of products. ANSYS Workbench is automatically installedwith most ANSYS, Inc. products; there is no individual product selection for ANSYS Workbench.

If you select Catia V5 or NX, you will have additional installation steps. These steps are completedon the CAD Configuration screen which is displayed when you click the Next arrow. For additionalinformation on completing these steps, see Specifying CAD Configurations (p. 19).

By default, the Install Documentation option is enabled (checked). When enabled, help document-ation is included as part of the installation process for all products selected. No help documentationis included with the installation if this box is disabled (unchecked).

You will also see an estimate of the disk space required to install all of the selected components,and the disk space you have available. The actual amount of disk space required may be less, butif you choose to run the installation with insufficient disk space available, we strongly recommendthat you review the log files at the end of the installation to verify that all products were installedcorrectly. Installation log files are written to the installation directory.

Note

On a first time installation, if you chose to install any ANSYS Geometry Interfaces, en-sure that you have also selected at least one ANSYS, Inc. product as part of the in-stallation. Installing an ANSYS Geometry Interface without an underlying ANSYS,Inc. product on a first time installation may cause installation errors.

Select the products you want to install and click the Next arrow.

The dates on the licensing files being installed are compared to any that may already exist on yourmachine. (This may take a few moments.)

8. A summary screen appears listing your installation selections. Please review this list carefully to verify thatit is correct. When you are sure all selections are correct, click the Next arrow to begin the installation.



9. The installation progress screen displays a status bar towards the bottom of the installation window. Thisstatus bar tracks the percentage of packages that have been installed on your computer. Depending onthe number of products you have selected, the installation time required could be lengthy. You will notbe able to interrupt the installation process. Please be patient while the installation completes.

Note

Clicking the View Details Progress Log button opens a second window that displaysthe name of each product package as it is uncompressed and installed.

Click the Next arrow to continue the installation.

10. The product installation window reappears with a message noting that the installation is complete. ALaunch Survey Upon Exiting option is included here. Clicking Exit while the Launch Survey Upon Ex-iting is enabled causes your default browser to open, displaying the product survey. Disabling (un-checking) the Launch Survey Upon Exiting option and then clicking Exit skips the survey.

The ANSYS, Inc. Installation Launcher appears. For this stand-alone installation, you must completethe License Manager installation (next) to run ANSYS, Inc. products.

3.5.1. Specifying CAD Configurations

Selecting Catia V5 or NX from the product selection screen and clicking the Next arrow displays theCAD Configuration screen. This screen contains the configuration properties for each CAD product thatyou have selected in an expanded "accordion" view.

You can use the following instructions to configure the appropriate CAD properties. After configuringyour CAD products or deciding to perform the configuration at a later time, click the Next arrow.

If you have not yet installed the related CAD programs, or do not know the requested information, youcan choose to skip these configuration steps by selecting the Skip all and configure later using CADConfiguration Manager option located on the lower left-hand portion of the screen. If you skip thesesteps, you will need to manually configure these CAD interfaces using the CAD Configuration Manager.See Configuring CAD Products (p. 53) for more information on using the CAD Configuration Manager.

CATIA V5

• If you selected CATIA V5 and any product that includes ANSYS Workbench, you will be required to selectthe appropriate CAD reader/plugin for ANSYS Workbench. You can choose to configure the Reader,CADNexus CAPRI CAE Gateway, or skip and configure later (using the CAD Configuration Manager).

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 skipand configure later (using the CAD Configuration Manager).

2. If you choose the Workbench Associative Interface and the UGII environment variables were not set, youmay need to specify the NX installation path for an existing NX installation. If you are an administrativeuser, a file required to load the NX plug-in is placed in the administrative user's Application Data folderby default, which may not be accessible by other, non-administrative users. To allow non-administrativeusers to run, you will need to define the environment variable UGII_CUSTOM_DIRECTORY_FILE priorto 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 CustomDirectory File Path under the NX tab.

3. If you selected the ANSYS ICEM CFD NX Interface product but not the NX Geometry Interface product onthe product selection screen, you may need to specify the NX installation path or choose to skip config-uring NX and use the CAD Configuration Manager to configure later.

3.5.2. ANSYS License Manager Installation

Follow the instructions below to install the ANSYS, Inc. License Manager on your Linux machine. Becauseyou will not be using a network server, you must install and configure the ANSYS, Inc. License Manageron your machine. The License Manager controls access to the ANSYS, Inc. products you have purchased.

1. Navigate to the directory where you extracted the files. Run ./INSTALL.LM. If you downloaded the licensemanager installation package, this file will reside in the directory where you untarred the downloadedfiles. If you are running from a DVD, this file will reside in the top level of the DVD.

2. You may see a warning stating that if the license manager is currently running, it will be shut down. Thisinstallation assumes that you have not previously installed the products or the licensing on this machine,and you are not pointing to a network license server machine. You may safely ignore this message andclick OK.

3. Select the language you want to use. English is the default.


5. The directory where you wish to install the ANSYS, Inc. License Manager is shown in the Install Directoryfield. You can install the License Manager into any directory you wish, but you must have write permissionsto the directory you choose. The default is /ansys_inc. We recommend using the default directory.You must use the same directory where the products were installed.

Note

You are unable to change the installation directory for a computer that currently containsan instance of the ANSYS, Inc. License Manager or ANSYS Electromagnetics LicenseManager. To change the installation directory location, you must first uninstall any pre-vious versions of both products.

6. The ANSYS, Inc. License Manager is selected as the only product available to install. As with the productinstallation, the required and available disk space numbers are shown. Click the Next arrow.

7. A summary screen appears that lists the products to be installed. Because this is a license manager install-ation, the ANSYS, Inc. License Manager is the only product listed.

Click the Next arrow. The license manager installation begins.

The ANSYS, Inc. License Manager is now being installed and configured on your system. After theLicense Manager installation has been completed, the Launch License Management Center uponexiting option is included on the screen. The ANSYS License Management Center is a browser-based user interface that centralizes many of the ANSYS product licensing administrative functions.



If you do not wish to launch the License Management Center, uncheck the Launch License Man-agement Center upon exiting option.

8. Click Exit to close the License Manager Installation screen.

9. Click Exit to close the ANSYS, Inc. Installation Manager.

10. Open a terminal window and navigate to your ANSYS installation. The following table lists the defaultpaths to start the ANSYS products you have installed.

Application Locations

How to LaunchApplication

/ansys_inc/v171/ACP.shACP

/ansys_inc/v171/cfdpostCFD Post

/ansys_inc/v171/CFX/bin/<productname>CFX

Where <productname> can be cfx5, cfx5launch, cfx5pre, cfx-solve, or cfx5post.

/ansys_inc/v171/fluent/bin/fluentFLUENT

/ansys_inc/v171/icemcfd/icemcfdICEM CFD

/ansys_inc/v171/icepak/icepakICEPAK

/ansys_inc/v171/polyflow/bin/polyflowPolyFlow

/ansys_inc/v171TurboGrid/bin/cfxtgTurbogrid

/ansys_inc/v171/Framework/bin/Linux64/runwb2Workbench

3.5.2.1. Registering the License Server

If you are a new user who has not received a license file for your server or if you add or change a licenseserver machine, follow this procedure to register your license server information. See the ANSYS LicensingGuide for more information on selecting license servers (Selecting License Server Machines) and onusing the ANSYS License Management Center (License Server Administration Using ANSYS LicenseManagement Center).

1. Open the ANSYS License Management Center. To run the ANSYS License Management Center on Linuxrun the following script:

/shared_files/licensing/start_lmcenter

2. Click the Get System Hostid Information option to display your system ID code(s).

3. Select the system ID you wish to use and click SAVE TO FILE.


4. Forward this text file to your ANSYS sales representative so that a license file can be created for you.

5. Add your license files though the ANSYS License Management Center. For these steps, see Adding a Li-cense.

After completing the installation process, please refer to Post-Installation Instructions (p. 35).





Chapter 4: Installing the ANSYS Products and the License Server onDifferent Linux Machines

This section explains how to install ANSYS, Inc. products, including ANSYS client licensing, as well asthe ANSYS, Inc. License Manager.

The default installation expects you to be logged in as root. You can install as non-root; however, youwill not be able to set the /ansys_inc symbolic link and may potentially experience permissionproblems. The inability to set the /ansys_inc symbolic link will in no way inhibit your ability to runANSYS, Inc. products; it is provided as a convenience when navigating to the /ansys_inc directory.


If you did not use the /ansys_inc symbolic link, you must replace all references to /ansys_inc/v171or <install_dir> with the actual installation path you used.

Before You Begin




• Open port numbers for both the FLEXlm and ANSYS Licensing Interconnect. Defaults are 1055 and 2325,respectively. To verify that these port numbers are available, open a command line and enter the followingcommand:

netstat -a -t


• Your local machine's name, to specify as the license server.

You should also verify that you are running on a supported platform. ANSYS, Inc. products support 64-bit Linux systems running Red Hat 6 (6.5, 6.6 or 6.7), SUSE Linux Enterprise 11 (SP3 or SP4) and SUSELinux Enterprise 12 (SP0 or SP1).

Verify that you have sufficient disk space to download, uncompress, and install the products you willbe installing. Approximate disk space requirements for each product are shown in Disk Space andMemory Requirements (p. 4).






This section is divided into four sets of instructions:

• Product Download Instructions: This set of instructions describes the download and extraction process.




For this procedure, the product and the license manager will be installed on separate machines. Youmust complete both the client licensing portion and the license manager installation in order to run ANSYS,Inc. products.

4.1. Pre-Installation Instructions for Download Installations

Before downloading the installation files, you need to accurately determine your platform type. Versionsthat are optimized for different chip sets from the same vendor can have similar names, causing confu-sion. We strongly recommend that you run the getFLEXid script on each machine first. This scriptwill output the correct platform name for each machine on which it is run. This script can be obtainedfrom the ANSYS website, in the Licensing Support area under “Capture License Server Info”.

4.2. Product Download Instructions













Installing the ANSYS Products and the License Server on Different Linux Machines



• Continue with the steps described in Product Installation (p. 26).

4.3. Installing from a USB Drive


Insert the USB drive into an appropriate USB slot on your computer. Navigate to the root directory ofthe USB drive and Run ./INSTALL. Continue with the steps described in Product Installation (p. 26).


For these versions, the default auto-mount function permission shows read-only which does not allowyou to install the ANSYS products. To address this issue, manually mount the USB by following the stepsbelow.

1. Open the auto-mount location, right-click the ANSYS170 USB and click Eject.

2. In a root shell, run the following command to determine the usb drive location:

fdisk -l

From the results of the fdisk -l coomand, locate the Device Boot data. The device boot datashould be in a format similar to /dev/sbd1, where sbd1 is the USB location. You will use thedevice boot data when editing the fstab below.

3. Create a mounting point by running the following command:

mkdir /run/media/<username>/ANSYS170

4. Edit the fstab to mount the USB with read/execute permissions.

vi /etc/fstab

Inserting the following line:

/dev/sdb1 /run/media/<username>/ANSYS170 auto users,defaults 0 0

Note the use of the device boot data used in the line.

5. Run the following command to execute the fstab:

mount -a

6. Continue with the steps described in Product Installation (p. 26).



Installing from a USB Drive

4.4. 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 installationprocedure using either a locally- or remotely-mounted DVD, depending on your site's system.

Note

Typically, a Linux system will mount a local DVD for you under /media/ANSYS171.

For a locally-mounted DVD installation, issue the following commands:

mkdir dvdrom_dirmount -t iso9660 /dev/cdrom dvdrom_dir

If the target machine does not have a DVD reader, first follow the steps for locally-mounted DVD, andthen 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. Asample /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 havedifferent syntax.

3. Log on to the machine where you want to install ANSYS, Inc. products and issue the following commands:

mkdir dvdrom_dir2mount -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.

4.5. Product Installation

1. Navigate to the directory where you extracted the files. Run ./INSTALL. If you downloaded the install-ation package, this file will reside in the directory where you untarred the downloaded files. If you arerunning from a DVD, this file will reside in the top level of the DVD.

2. The ANSYS, Inc. Installation Launcher appears.



From the options along the left side of the launcher you can install ANSYS products, DocumentationOnly, ANSYS EKM Server, and the ANSYS License Manager. You can access the installation guidefor the ANSYS EKM Server from the Downloads page on the Customer Portal.


Select the language you want to use from the drop-down menu in the upper right corner. Englishis the default.



When installing more than one platform or if you are installing a platform other than your currentmachine 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 isshown at the bottom of the window. You can choose as many platforms as you want; however,you must run the platform configuration procedure (see Run the Product Configuration Utility inNetwork Installation and Product Configuration (p. 32)) for each platform other than your currentmachine type. See Network Installation and Product Configuration (p. 32) for specific instructionson how to configure a shared installation directory across multiple machines using a commonnetwork file system.

5. The directory where you want to install the ANSYS, Inc. products is shown in the Install Directory field.You can install the products into any directory you want, but you must have write permissions to thedirectory you choose. The default is /ansys_inc. We recommend using the default directory.

The Symbolic Link option is available only if you are installing as root and is enabled (checked)by default. If you choose to disable (uncheck) the symbolic link or are installing as a non-root user,




substitute the directory path where you installed the product for all subsequent occurrences of/ansys_inc in this guide.

We strongly recommend that you use the Symbolic Link option. If you do not use this option, youmust install all releases into a common directory to ensure license manager compatibility andavailability among releases and products.

If you have already installed the ANSYS Workbench Framework for Ansoft, you must install anyadditional ANSYS, Inc. products into the same directory.

On Linux, you can choose Disable RSS to disable automatic internet feeds to ANSYS, Inc. products.










If you select Catia V5 or NX, you will have additional installation steps. These steps are completedon the CAD Configuration screen which is displayed when you click the Next arrow. For additionalinformation on completing these steps, see Specifying CAD Configurations (p. 29).



Note

On a first time installation, if you chose to install any ANSYS Geometry Interfaces, en-sure that you have also selected at least one ANSYS, Inc. product as part of the in-



stallation. Installing an ANSYS Geometry Interface without an underlying ANSYS,Inc. product on a first time installation may cause installation errors.

Select the products you want to install and click the Next arrow. The dates on the licensing filesbeing installed are compared to any that may already exist on your machine. (This may take a fewmoments.)

8. A summary screen appears listing your installation selections. Please review this list carefully to verify thatit is correct. When you are sure all selections are correct, click the Next arrow to begin the installation.


Note




11. If you have installed ANSYS, Inc. products on a file server, follow the instructions under Network Installationand Product Configuration (p. 32).

4.5.1. Specifying CAD Configurations

Selecting Catia V5 or NX from the product selection screen and clicking the Next arrow displays theCAD Configuration screen. This screen contains the configuration properties for each CAD product thatyou have selected in an expanded "accordion" view.


If you have not yet installed the related CAD programs, or do not know the requested information, youcan choose to skip these configuration steps by selecting the Skip all and configure later using CADConfiguration Manager option located on the lower left-hand portion of the screen. If you skip thesesteps, you will need to manually configure these CAD interfaces using the CAD Configuration Manager.See Configuring CAD Products (p. 53) for more information on using the CAD Configuration Manager.

CATIA V5





NX


2. If you choose the Workbench Associative Interface and the UGII environment variables were not set, youmay need to specify the NX installation path for an existing NX installation. If you are an administrativeuser, a file required to load the NX plug-in is placed in the administrative user's Application Data folderby default, which may not be accessible by other, non-administrative users. To allow non-administrativeusers to run, you will need to define the environment variable UGII_CUSTOM_DIRECTORY_FILE priorto installation and specify a location where other users have read access. Alternatively, you can run theCAD Configuration Manager after the installation and provide an updated location for the NX CustomDirectory File Path under the NX tab.



After you have installed the ANSYS products on your client machines, follow the instructions below toinstall the ANSYS, Inc. License Manager on your license server machine. The License Manager controlsaccess to the ANSYS, Inc. products you have purchased.

1. Navigate to the directory where you extracted the files. Run ./INSTALL.LM. If you downloaded the licensemanager installation package, this file will reside in the directory where you untarred the downloadedfiles. If you are running from a DVD, this file will reside in the top level of the DVD.

2. You may see a warning stating that if the license manager is currently running, it will be shut down. Ifyou have not previously installed the products or the licensing on this machine, and you are not pointingto a network license server machine, you may safely ignore this message and click OK.

3. Select the language you want to use. English is the default.


5. The directory where you want to install the ANSYS, Inc. License Manager is shown in the Install Directoryfield. You can install the License Manager into any directory you want, but you must have write permissionsto the directory you choose. The default is /ansys_inc. We recommend using the default directory.You must use the same directory where the products were installed.

Note






Click the Next arrow. The license manager installation begins.

The ANSYS, Inc. License Manager is now being installed and configured on your system. After theLicense Manager installation has been completed, the Launch License Management Center uponexiting option is included on the screen. The ANSYS License Management Center is a browser-based user interface that centralizes many of the ANSYS product licensing administrative functions.If you do not want to launch the License Management Center, uncheck the Launch License Man-agement Center upon exiting option.


9. Click Exit to close the ANSYS, Inc. Installation Manager.

10. Open a terminal window and navigate to your ANSYS installation. The following table lists the defaultpaths to start the ANSYS products you have installed.

Application Locations

How to LaunchApplication

/ansys_inc/v171/ACP.shACP

/ansys_inc/v171/cfdpostCFD Post

/ansys_inc/v171/CFX/bin/<productname>CFX

Where <productname> can be cfx5, cfx5launch, cfx5pre, cfx-solve, or cfx5post.

/ansys_inc/v171/fluent/bin/fluentFLUENT

/ansys_inc/v171/icemcfd/icemcfdICEM CFD

/ansys_inc/v171/icepak/icepakICEPAK

/ansys_inc/v171/polyflow/bin/polyflowPolyFlow

/ansys_inc/v171TurboGrid/bin/cfxtgTurbogrid

/ansys_inc/v171/Framework/bin/Linux64/runwb2Workbench



1. Open the ANSYS License Management Center. To run the ANSYS License Management Center on Linuxrun the following script:

/shared_files/licensing/start_lmcenter









4.5.3. Network Installation and Product Configuration

To complete a network installation (where the product is installed on one machine and one or moreclients access that installation to run the product) to a file server machine, follow the steps below. Thesesteps apply to the following products: Mechanical APDL, ANSYS Workbench, ANSYS CFX, ANSYS ICEMCFD, ANSYS Fluent, ANSYS Polyflow, ANSYS Icepak, NX, and Remote Solve Manager (RSM).

A network installation must be homogeneous, although you can install on different operating systems.

You must complete the following steps to run products across a network:4.5.3.1. Export the /ansys_inc Directory4.5.3.2. Run the Product Configuration Utility on All Client Machines

We strongly recommend that these steps be performed by the same non-root user. Installing and con-figuring as different users may create permissions problems. Likewise, installing and/or configuring asa root user may also result in permissions problems.

4.5.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 dir-ectory to all client machines so that all users can access the program. You will also need to share theANSYS directory if the machine you are installing on does not have a DVD/USB drive or an internetconnection for downloading files and you need to share files with a machine that does have a DVD/USBdrive or internet connection.

The instructions below assume ANSYS, Inc. products were installed in the specified directory.

1. Install the ANSYS, Inc. products. The following example uses /usr/ansys_inc.

2. 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/writepermission from all clients, use *(rw):

/usr/ansys_inc *(rw)

Alternatively, if the installing user is root, use:

/usr/ansys_inc *(rw,no_root_squash)

3. Run

exportfs -a

4. On all client computers, mount the ansys_inc directory.



If you perform a network install where you want the clients to be able to modify the licensing configur-ation, you need to consider the NFS write options for the exported file system as shown in the aboveexamples. You also need local permissions to the licensing directory (/shared_files/licensing/)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 withoutone, copy the DVD contents using a Samba mount or some other transfer method that is safe to usebetween Windows and Linux.

If sharing the ANSYS directory between Linux machines, you must use the same mount point for boththe client and server. For example, if you installed to a file server in a directory named /apps/an-sys_inc and you did not choose the symbolic link to /ansys_inc, then you must mount this directoryon the client machine using /apps/ansys_inc as the mount point. If you did choose the symboliclink to /ansys_inc during installation on the file server, you must either use /ansys_inc as themount 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.5.3.2. Run the Product Configuration Utility on All Client Machines

For network installations, you must run this step on every client machine.

Note

The username and user ID utilized when running the Product Configuration Utility must bethe same as the installing server user.

1. On each client machine, issue the following command to run the Product Configuration utility:

/ansys_inc/v171/ProductConfig.sh

2. Select Configure Products.

3. Select the products you want to configure and click Configure.

Note

ANSYS Workbench is configured when Mechanical APDL, ANSYS CFX, ANSYS Fluent,ANSYS Polyflow, or Remote Solve Manager Standalone Services is selected. CFD-Post isconfigured when either ANSYS CFX, ANSYS Fluent, ANSYS Polyflow or ANSYS Icepak isconfigured.

4. On the Configuration Complete dialog box, click Finish.

After completing the installation process, please refer to Post-Installation Instructions (p. 35).

Important

If you use network installation and wish to disable the ANSYS Product Improvement Program(APIP) for all clients from a central location, perform the following steps on the file server:




1. Navigate to the installation directory:[Drive:]\v170\commonfiles\globalset-tings

2. Open the file ANSYSProductImprovementProgram.txt.

3. Change the value to from "on" to "off" and save the file.



Chapter 5: Post-Installation Instructions

The following post-installation procedures apply to all ANSYS, Inc. products. Individual products mayhave additional post-installation procedures; please refer to the following sections for each product.

5.1. Post-Installation Procedures for Mechanical APDL and ANSYS Workbench Products5.2. Product Localization5.3. Launching ANSYS, Inc. Products

Note

If the installation program reported any errors, please review the installation error file (in-stall.err) located in the ANSYS Inc directory. Contact your ANSYS Support representative ifyou have any questions.

After the product is installed, you need to establish some system settings, including path names andenvironment variables. See your shell documentation or man pages file for the shell being used forspecific 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).

(or appropriate path to theindividual products'executables)

/ansys_inc/v171/ansys/bin

(contains ANSLIC_ADMINutility)

/ansys_inc/shared_files/licensing/lic_admin

2. Set the following environment variables based on the behavior you want. Set the environment variablesfollowing 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 theworkstation 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 willoutput their analysis results. Note that the X server must have permission to connect to thehost machine.

If you will be using connection functionality, you may have additional environment variables toset. See the section Configuring CAD Products (p. 53) later in this guide for more information.

3. Set the license manager to start automatically at boot time. For platform-specific instructions, see LicenseManager Automatic Startup Instructions in the ANSYS Licensing Guide.



4. Designate server(s) for license checkout and establish necessary user privileges (recommended but notrequired). For information on these tasks, see Post-Installation Instructions for the License Manager in theANSYS Licensing Guide.

5. Make a backup copy of the /ansys_inc directory using a tape backup command such as tar.

6. Verify the installation by logging out as root (if you installed as root) and logging back in as a regular userand then starting the product to verify that it starts and runs correctly.

Quality Assurance Services: If you require verification of Mechanical APDL, the Mechanical Application,Fluent, or CFX, ANSYS, Inc. offers Quality Assurance services. If you are interested in this service, go tohttp://www.ansys.com/Support/Quality+Assurance/Quality+Services or call the ANSYS, Inc. CorporateQuality Group at (724) 746-3304.

5.1. Post-Installation Procedures for Mechanical APDL and ANSYSWorkbench Products

The following post-installation procedures apply only to the Mechanical APDL and ANSYS Workbenchproducts. These are in addition to the post-installation procedures in the previous section.

1. Set the following environment variables based on the behavior you want. Set the environment variablesfollowing the conventions of your shell. Not all of these are required for all integrated ANSYS Workbenchproducts (such as ANSYS Autodyn), but setting them correctly for ANSYS Workbench will in no way hinderthe performance of the other products.

The ANSYS171_DIR environment variable sets the location of the ANSYS directory hierarchy.The default value is /ansys_inc/v171/ansys. You probably will not need to reset thisvariable, unless you change the location of the installed files.The ANSYSLIC_DIR environment variable sets the location of the ANSYS licensing directoryhierarchy. The default value is /ansys_inc/shared_files/licensing . You probablywill not need to reset this variable, unless you change the location of the licensing files.ANSYS171_PRODUCT - set this to the correct product variable to run Mechanical APDL tostart with the correct product without specifying the -p command modifier each time. See theProduct Variable Table in the ANSYS 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 newjob with the same name and in the same directory as the current job.ANSYS171_WORKING_DIRECTORY - set this variable to the directory you want designated asyour working directory. The working directory setting in the launcher will reflect this setting.ANSYS171_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).ANSYS171_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 fullpath) if the automatic browser detection fails. A browser is needed to view HTML reports andhelp for the ANS_ADMIN utility and the Mechanical APDL launcher. By default, ANSBROWSERpoints 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 toset. See the section Configuring CAD Products (p. 53) 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 torun batch jobs; the at.deny file should contain the username of users who are not permitted to run



http://www.ansys.com/Support/Quality+Assurance/Quality+Services

batch jobs. The files consist of one username per line and can be modified only by the superuser. If neitherfile exists, only root will be able to run batch jobs.

The at. files are located in the /etc directory on Linux machines.

3. Run the ANS_ADMIN utility to properly configure ANSYS (depending on the products you are running)or relink ANSYS.

4. Specify the product order as it will appear in the Mechanical APDL launcher (optional). If you want tospecify product order, use the ANSLIC_ADMIN utility. See the ANSYS Licensing Guide for more information.

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, Back-ground’ Solve Process Settings will likely not function as expected due to write permissions for RSMworking 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 doc-umentation for more information.

5.1.1. 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 RuntimeEnvironment in the /ansys_inc/v171/commonfiles/jre directory. Regardless of whether youhave modified your setup files, you can still run ANSYS CFX commands by specifying the full pathnameof the commands you want to run. This procedure may be useful if you have several releases of ANSYSCFX 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 cfx-root/bin/cfx5 (where cfxroot is the directory in which ANSYS CFX is installed), your commandsearch paths must be modified to search the directory cfxroot/bin. This can be done by one of thefollowing methods:

Modification of individual user setup files You can select Tools> Configure User Startup Filesfrom the ANSYS CFX Launcher to modify your own setup files: .login for the C shell, .profile forthe 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 byrunning the ANSYS CFX commands by name. This method has the advantage that it need not be doneby the system administrator, but has the disadvantage that it must be done by each user.

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 havebeen changed. You will then need to log out and log in again or source your setup files before you canuse the software.

Manual execution of a setup script each time the software is used You can also use the Toolsmenu of the launcher to launch an editor to create new setup scripts which need to be run each timeyou want to use the ANSYS CFX software. This method has the advantage of not requiring changes toexisting setup files and allows you to use different versions of ANSYS CFX software by running different



Post-Installation Procedures for Mechanical APDL and ANSYS Workbench Products

setup files. The disadvantages are that all users must create their own setup files and run them manuallyin 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.logincfx5

Having created the setup files, users of the Bourne or Korn shell then need to do the following beforerunning ANSYS CFX:

.$HOME/cfx5.profilecfx5

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 inthe command search path. While this has the advantage of only one file needing to be modified in orderto 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.1.1. Setting up CFX-RIF

CFX-RIF is a flamelet-library generation tool. For details, see CFX-RIF in the CFX-Solver Modeling Guide.

In order to run CFX-RIF on Red Hat 7, you need to ensure that the following 32-bit libraries are installed:

libX11.so.6libpthread.so.0libdl.so.2libm.so.6libstdc++.so.6libgcc_s.so.1libc.so.6libxcb.so.1libXau.so.6

To locate and install the 32-bit libraries:

As root:

Add the following line to /etc/yum.conf:

multilib_policy=all

Edit /etc/yum/pluginconf.d/rhnplugin.conf and uncomment the lines that read:

[rhel-i386-server-5]

enabled = 1

yum whatprovides <library_name>

yum install <rpm>



5.1.1.2. Setting up ANSYS TurboGrid Release 17.1

Manual modification of individual user setup files To start ANSYS TurboGrid without using fullpathnames every time you want to run the ANSYS TurboGrid software, your path must be altered toinclude the ANSYS TurboGrid directory. This can be done by adding the following line to the .loginand .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:$PATHexport 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 bytyping cfxtg.

Modification of system setup files The system administrator modifies the setup files ( normallyetc/profile), which are run by all users during login, to include the directory cfxroot/bin in thecommand search path. While this method has the advantage that only one file needs to be modifiedto 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.1.3. 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

and select Tools> Configure User Startup Files. This option runs cfxroot/bin/cfx5setupuserthat modifies your setup files or writes the necessary commands to files, which you can merge manuallywith your existing setup files.

If you choose to modify your setup files, you will see a message indicating that your setup files havebeen changed. You will then need to log out and log in again or source your setup files before you canuse the software.

User setup can also be run from the command line by entering:

cfxroot/bin/cfx5setupuser

Enter the flag -h to view the optional commands.




5.1.2. 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 shelland its derivatives by entering:

set path = (/ansys_inc/v171/fluent/bin $path)

or in the Bourne/Korn shell or bash, by entering:

PATH=(/ansys_inc/v171/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 Fluentlauncher 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 haveadded it for previous versions. Verify that the environment variable is unset by typing:

printenv FLUENT_INC

This command should not return anything.

2. Add the following paths to all users' login startup files:

<install_dir>/ansys_inc/v171/fluent/bin

3. Run the following command:

<install_dir>/ansys_inc/v171/fluent/bin/fluent

4. Click Default.

5. Click Yes when asked if you want to discard the LAUNCHER history.

6. Click Cancel if you do not want 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.3. Post-Installation Procedures for ANSYS Polyflow

Polyflow no longer requires the FLUENT_INC environmental variable. It should be deleted as is recom-mended for Fluent:

• Remove the FLUENT_INC setting from your .cshrc,.profile, or .bashrc file if you have added itfor previous versions. Verify that the environment variable is unset by typing:

printenv FLUENT_INC

This command should not return anything.



5.1.4. 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/v171/icemcfd/linux64_amd/bin

2. Add the following environment variable to all users' login startup files.

ICEM_ACN - set to /ansys_inc/v171/icemcfd/linux64_amd

3. Start ANSYS ICEM CFD by typing icemcfd.

5.1.5. Post-Installation Procedures for ANSYS Autodyn

The following post-installation procedures apply only to the AUTODYN product.

Add the following paths to all users' login startup files (i.e., .cshrc or .login files).

/ansys_inc/v171/autodyn/bin

5.1.6. Post-Installation Procedures for Other Products

BladeEditor In order to use BladeEditor, you must set the Geometry license preference to ANSYSBladeModeler as follows:

1. In the ANSYS Workbench menu, select Tools> License Preferences.

2. In the License Preferences dialog box, click the Geometry tab.

3. If ANSYS BladeModeler is not the first license listed, then select it and click Move up as required to moveit to the top of the list. If ANSYS BladeModeler is not in the list, then you need to obtain an ANSYSBladeModeler license.

4. Select ANSYS DesignModeler in the list and set its value to 0 (which means “Don't Use”). This step preventsDesignModeler from using an ANSYS DesignModeler license when an ANSYS BladeModeler license is notavailable.

5. Click OK to close the dialog box.

You can inadvertently destroy your BladeEditor models by updating a project or otherwise processinga Geometry cell, depending on your license preference settings. This problem can affect you if you haveany ANSYS DesignModeler licenses. To avoid this problem, configure the license preferences as describedabove. For more details, please see Configuring the BladeModeler License in the ANSYS BladeEditordocumentation.

ACP When running ACP on Red Hat Enterprise Linux 7, the libpng12 and compat-libtiff3 libraries arerequired to be installed. You can install these by issuing the following commands with superuser priv-ileges:

yum install libpng12yum install compat-libtiff3




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 lan-guage. See your specific product documentation for instructions on choosing a localized version of theproduct.

All products that are localized define the language via the languagesettings.txt file. In mostcases, you will not have to manually edit this file. If you do need to edit it manually, you can use oneof 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, inorder:

1. $Home/.ansys/v171

2. <install_dir>/ansys_inc/v171/commonfiles/language

ANSYS, Inc. licensing also looks for the languagesettings.txt in the licensing languages subdir-ectories in order to display the ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnectmessage and log files in a different language.

Some products are not fully localized but offer only the messages in a translated version. See the fol-lowing section for instructions on translated message file installation.

5.2.1. Translated Message File Installation for Mechanical APDL

If your ANSYS sales representative has supplied you with message files in your local language, use thefollowing procedures to install and access these files. You must create new message files for each releasebecause 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/v171/ansys/docu/fr

2. Copy the message files msgcat.171,msgidx.171, and msgfnm.171 into that subdirectory.

3. Access these files from the Language Selection option of the launcher or via the -l command line option:

ansys171 -l fr



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 youdid not, substitute your installation path for the path given below.

Table 5.1: Startup Commands

NotesCommandProduct

For a complete list of command lineoptions, see Starting an ANSYS

/ansys_inc/v171/ansys/bin/an-sys171

MechanicalAPDL

Session from the Command Level inthe Operations Guide.

/ansys_inc/v171/Frame-work/bin/<platform>/runwb2

ANSYSWorkbench

/ansys_inc/v171/CFX/bin/cfx5ANSYS CFX

For a complete list of command lineand launcher options, see StartingANSYS Fluent in the Fluent Users Guide.

/ansys_inc/v171/fluent/bin/fluentANSYS Fluent

/ansys_inc/v171/icemcfd/<plat-form>/bin/icemcfd

ANSYS ICEM CFD

Starts the POLYFLOW MANager. Forany other tool, use /an-

/ansys_inc/v171/polyflow/bin/poly-man

ANSYS Polyflow

sys_inc/v171/poly-flow/bin/<tool>

/ansys_inc/v171/CFD-Post/bin/cfd-post

ANSYS CFD-Post

/ansys_inc/v171/Icepak/bin/icepakANSYS Icepak

/ansys_inc/v171/TurboGrid/bin/cfx-tg

ANSYSTurboGrid

solver only/ansys_inc/v171/autodyn/bin/auto-dyn171

ANSYS Autodyn

/ansys_inc/v171/ACP/ACP.shANSYS ACP



Launching ANSYS, Inc. Products


Chapter 6: Installing the ANSYS, Inc. Product Help DocumentationOnly

Performing the ANSYS product help documentation installation places the entire help library onto acomputer. The Documentation Only installation is intended to be used for installing documentation ona central server without any products.

To perform the installation:

1. Navigate to the directory where you extracted the installation files. Run ./INSTALL.

• If you downloaded the installation package, this file will reside in the directory where you untarred thedownloaded files.

• If you are running from a DVD or USB, this file will reside in the top level of the DVD or USB.

The ANSYS, Inc. Installation Launcher appears.

2. From the options along the left side of the launcher click Install ANSYS Documentation Only.

The license agreement appears.

3. Read the agreement, and if you agree to the terms and conditions, click I Agree. Click Next.

4. The directory where you want to install the ANSYS, Inc. help documentation is shown in the Install Direct-ory field. You can install the help documentation into any directory you want, but you must have writepermissions to the directory you choose. The default is /ansys_inc. We recommend using the default dir-ectory.

We strongly recommend that you also set the symbolic link /ansys_inc to the directory where theANSYS, Inc. product is installed. The symbolic link option is available only if you are installing asroot and is set by default. If you choose not to specify the symbolic link or are installing as a non-root user, substitute the directory path where you installed the product for all subsequent occurrencesof/ansys_inc in this guide.


Click Next.

5. A summary screen appears listing your help documentation installation. You will also see an estimate ofthe disk space required to install all of the selected components, and the disk space you have available.

Click Next to begin the installation.



6. When the help documentation installation has completed, click Exit. The product installation window re-appears. You can close this window at this time.

Note

Alternatively, you can run the document installation by running the INSTALL.DOCONLYinstallation file. This file is located in the linux directory on USB drives.

The ANSYS help documentation can be installed silently by running the INSTALL.DOCONLY installationfile with the –silent flag. For more information, see Silent Mode Operations (p. 47).


Installing the ANSYS, Inc. Product Help Documentation Only

Chapter 7: 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, becauseof the way the products are packaged, not all of these flags may be valid for a silent configuration/un-configuration, or uninstall.

Product Flags

product_flagProduct

-mechapdlMechanical APDL

-ansyscustANSYS Customization Files

-autodynANSYS Autodyn

-lsdynaANSYS LS-DYNA

-cfdpostANSYS CFD-Post

-cfxANSYS CFX

-turbogridANSYS TurboGrid

-fluentANSYS Fluent

-polyflowANSYS Polyflow

-aqwaANSYS Aqwa

-icemcfdANSYS ICEM CFD

-forteANSYS Forte

-chemkinproANSYS Chemkin

-energicoANSYS Energico

-reactionwbANSYS Reaction Workbench

-mflANSYS Model Fuel Library (Encrypted)

Note: Installing any of the above products will install ANSYS Workbench.

-acpANSYS Composite PrepPost

-rsmANSYS Remote Solve Manager Standalone Services

-catia4CATIA 4.x Geometry Interface

-parasolidParasolid Geometry Interface

-acisACIS Geometry Interface

-ug_pluginNX Geometry Interface Plugin

-icepakANSYS Icepak



For more information on which products are included with each installation, see Applications Includedwith Each Product (p. 67).

7.1. Silent Product and License Manager Installation

Caution

A silent license manager installation could shut down the ANSYS, Inc. License Manager, af-fecting other users who are using that license server machine.

You can deploy an ANSYS, Inc. product installation in silent mode. The general form to run a silentproduct installation, including the client licensing, is:

INSTALL -silent -install_dir path -product_flag

If no product flags from the list above are specified, all available products will be installed. To installspecific products, run the silent install with any combination of the product flags listed above (not allproducts are available on all platforms). For example, to install only TurboGrid and Icepak, issue thefollowing command:

INSTALL -silent —install_dir “/ansys_inc/” -turbogrid -icepak

Additional command line arguments are available; please see the list below.

To install the ANSYS, Inc. License Manager on Linux systems that will act as license servers, you mustrun the INSTALL.LM command:

INSTALL.LM -silent -install_dir path

The silent license manager installation is valid only for the default Licensing Configuration option "Runthe ANSYS Licensing Interconnect with FLEXlm." Please see the ANSYS Licensing Guide for more inform-ation.

You can use the following arguments when running a silent installation. Note that some options areavailable only for a silent license manager installation.


Displays a list of valid arguments for a silent installation.-help

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

-install_dirpath

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 validproduct_flags below.

-product_flag

You can specify an options file that lists the products you want to install. To doso, you must provide a full path to a file containing desired products. See SpecifyingProducts with an Options File (p. 50) below for more details.

-productfilepath

Disables automatic internet feeds to ANSYS, Inc. products (Linux only).-disablerss

Specifies the location of the license file to install. If the path is not specified or ifthe 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).

-licfilepathpath


Silent Mode Operations

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

-setliclanglanguage

subdirectory of the licensing directory (en-us, fr, de, etc.) as the languagevalue. This flag can be used during a GUI installation as well. Valid only whendoing a license manager installation (INSTALL.LM).

Specifies information to be used by the client for the license server. Valid only inconjunction with a silent installation (INSTALL). The format is:

Single license server:

-licserverinfo

LI_port_number:FLEXlm_port_number:hostname

Example:

2325:1055:abc

Three license servers:

LI_port_number:FLEXlm_port_number:hostname1,hostname2,host-name3

Example:

2325:1055:abc,def,xyz

The default values for the Licensing Interconnect and FlexNet port numbers(2325 and 1055, respectively) will be used if they are not specified. However,you do need to include the colons.

Example:

::abc

or

::abc,def,xyz

Information specified via -licserverinfo will be appended to existinginformation in the ansyslmd.ini file. To change information already inyour ansyslmd.ini file, you must use the ANSLIC_ADMIN utility.

By default, for the products that are being installed, all help documentation isincluded. The -nohelp argument removes all help from the installation.

-nohelp

Specifies a language to use for the products.-lang

Any messages will be written to the appropriate installation log files. Installation log files are locatedin the installation directory: install.log contains installation messages, and install_liccon-fig.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_in-stall_temp_licconfig_<user>_<index>.log file, located in $HOME/.ansys.

For more information on the silent license manager installation, see the ANSYS Licensing Guide.



Silent Product and License Manager Installation

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 optionsfile can contain all possible products, with the products you do not want to install commented out, orit can contain only the products you want to install. An example options file is shown below. In theexample, NX is commented out using an acceptable comment indicator. When using the options file,do not include the dash (-) before the product name.

mechapdlansyscustautodynlsdynacfdpostcfxturbogridfluentpolyflowicepak#ug

7.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/v171/ProductConfig.sh -silent

Use the -product_flag argument to specify which products should be configured. If you do notspecify one or more products, all products that have been installed will be configured. The validproduct_flags are:

product_flagProduct



-cfxANSYS CFX


-fluentANSYS Fluent


-icepakANSYS Icepak



Errors will be written to the ${HOME}/.ansys/v160/ directory on the client machine.

7.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 171-<number>.dvdfiles of each DVD are located in the same directory. You can then proceed with the silent installation as de-scribed earlier.



• Place all of the media in separate drives (any combination of virtual ISO mounts or hardware drives) so thatthey can be accessed simultaneously during the installation. Then run the silent installation as describedearlier, but include the additional -media_dir2 <path> and -media_dir3 <path> options as neededfor each drive:

INSTALL -silent -install_dir path -product_flag -media_dir2 <path -media_dir3 <path>

The installer uses the mount directory from which it was launched as the first media path; you needto specify only the location of the subsequent DVD(s) using the -media_dir2 and -media_dir3options shown in the example above.

7.3.1. Silent Uninstall

You can also run the uninstall silently by issuing the following command:

/ansys_inc/v171/ans_uninstall171 –silent

The silent uninstall will automatically uninstall all products for this release and delete the v171 directoryand all subdirectories. You will not be prompted for confirmation.

To uninstall individual products, use the following product options in conjunction with the -silentargument:


-cfxANSYS CFX


-fluentANSYS Fluent




-icepakANSYS Icepak


For example, to uninstall only TurboGrid and Icepak, issue the following command:

/ansys_inc/v171/ans_uninstall171 –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 error messageswill be written to ansys_inc/install.err.



Silent Media Installation


Chapter 8: 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, youneed to ensure that the product is properly licensed, and set any necessary environment variables orother configuration as appropriate. See the manuals for the individual CAD products for informationabout environment variables and other configuration requirements.

For complete information about the files you can import, see the Mechanical APDL ANSYS ConnectionUser's Guide.

Caution

Be sure to install Mechanical APDL and the connection functionality from the same release.If you attempt to run the latest connection functionality on a machine that is running anearlier 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 skipconfiguring these products during the installation process. The following sections describe any post-installation configuration procedures that are required and how to manually configure NX if you didnot configure NX during installation or if you are updating your CAD versions. These methods are alldescribed in the following sections.

8.1. Using the CAD Configuration Manager

The CAD Configuration Manager utility allows you to configure geometry interfaces for ANSYS Work-bench 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 Associative Interface mode for NX is supported on Linux. However, the ANSYS NX menuand the active connection for the Associative Interface is NOT available on Linux because the interfaceoperates in passive mode Linux.

The CAD Configuration Manager on Linux is organized into several tabs:

• CAD Selection

• Creo Parametric (options are active on Windows only)

• NX

• Teamcenter (options are active on Windows only)

• CAD Configuration

An administrative user has the option to configure or unconfigure any selected CAD systems either forthe 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 administrativeuser will only be allowed to configure or unconfigure for all users. In this situation, NX configure andunconfigure actions are skipped. Non-administrative users will only be allowed to configure for them-selves. Any user-specific configuration settings take precedence over global configuration settings.

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 configurationprocess. You can also manually select each tab to progress through the configuration process; bothmethods work the same. However, the applicable tabs will not be enabled until you choose the associatedproduct on the CAD Selection tab.

You can choose Help to view instructions on using the CAD Configuration Manager at any time. Ifthe help does not load into your default browser, set the BROWSER environment variable to the pathof 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 installationpath if different than /ansys_inc:

/ansys_inc/v171/aisol/.workbench -cmd -NoMW mono /ansys_inc/v170/commonfiles/CAD/bin/linx64/Ans.CadInt.CADConfigUtilityGUI.exe.

2. On the CAD Selection tab, choose the CAD products that you need to configure.

3. If you selected NX as one of your CAD products, the NX tab opens.

a. Enter or browse to the NX installation location.

b. The NX custom directory file is not applicable on Linux and can be ignored as it will be disabled.

c. Click Next.

4. The CAD Configuration tab opens.

a. Click the Configure Selected CAD Interfaces button.

b. When the configuration for all products is complete, log entries appear, listing those products thatwere successfully configured and those that were not. Address any errors and reconfigure.

c. 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 /an-sys_inc. If you do not have write permissions to the /ansys_inc directory, the log file will bewritten to $TEMP. If you have not defined $TEMP, the log file is written to /tmp. When /tmp is notaccessible, this file will be written to the current working directory.

8.1.1. Unconfiguring

If you need to unconfigure any of your CAD products, follow the steps above, but choose UnconfigureSelected CAD Interfaces on the CAD Configuration tab.


Configuring CAD Products

8.1.2. Running the CAD Configuration Manager in Batch Mode

You can configure ANSYS Geometry Interfaces by supplying the CAD Configuration Manager witharguments specific to the CAD sources you want to make available. The following table contains a listof supported arguments.

The command to run the CAD Configuration Manager in batch mode on Linux is:

/ansys_inc/v170/aisol/.workbench -cmd -NoMW mono /ansys_inc/v170/commonfiles/CAD/bin/linx64/ Ans.CadInt.CADConfigurationUtility.exe -arguments

CommentValueArgument

Results in any specified CAD sources beingunconfigured. When this flag is absent, the CAD

NoneUNCONFIGURE_SPECIFIED

Configuration Manager will attempt to unconfigureall designated CAD sources.

Results in all CAD sources being disabled alongwith prerequisite libraries.

NoneUNCONFIGURE

Configure/unconfigure NX Geometry Interface toWorkbench. The argument UGII_BASE_DIR must alsobe specified for the configure operation.

NoneUG_CONFIG_WB

This should agree with environment variableUGII_BASE_DIR. Not required with unconfigureoperation.

Full path to NXinstallation (quotationsare required if there

UGII_BASE_DIR

are spaces in thepath).

Configure/unconfigure CatiaV5 Reader.NoneCATIA_READER

Note

All arguments require a dash (-) before them in order to be properly recognized by the CADConfiguration Manager. Arguments' values should not have a dash preceding them.

For example, you can configure the NX Geometry Interface to ANSYS Workbench from the commandline by using the following:

/ansys_inc/v170/aisol/.workbench -cmd -NoMW mono /ansys_inc/v170/commonfiles/CAD/bin/linx64/Ans.CadInt.CADConfigurationUtility.exe -UG_CONFIG_WB -UGII_BASE_DIR "<pathtonx>"

where /ansys_inc/v171 is the installation directory you specified.

To unconfigure the same CAD Interface, the command would be:

/ansys_inc/v170/aisol/.workbench -cmd -NoMW mono /ansys_inc/v170/commonfiles/CAD/bin/linx64/Ans.CadInt.CADConfigurationUtility.exe -unconfigure_specified -UG_CONFIG_WB

Although the argument order does not matter, an argument value must immediately follow its argument.

8.1.3. NX Configuration

Running the CAD Configuration Manager for NX performs the following steps to activate the NXreader:



Using the CAD Configuration Manager

• Registers the NX Associative Geometry Interface for ANSYS Workbench by copying the file UGNX#.Compon-ent.XML from /ansys_inc/v171/aisol/CADIntegration/UG to either /ansys_inc/v171/com-monfiles/registry/linx64/append when the configuration manager is in administrative mode orto $HOME/.config/ANSYS/171/UserRegFiles_NNNN/append, when the CAD ConfigurationManager is run by a non-administrator. The CAD Configuration Manager ensures that only one versionof the file exists in the target location.

UGNX# is the NX version detected by the CAD Configuration Manager, and NNNN is a numericidentifier appended to the UserRegFiles directory.

• You must specify the environment variables UGII_BASE_DIR and UGII_ROOT_DIR. The UGII_BASE_DIR mustpoint to the install location supplied to the CAD Configuration Manager. The UGII_ROOT_DIR must pointto the /ugii or /bin subdirectory in the NX install location. The Workbench Associative Interface for NXwill not work without these two variables set properly, as these are required for proper startup of the CAD.

• Prior to configuring a client of a network install, the client system must have its UGII_BASE_DIR point tothe same version of NX as designated on the server system. This must be done before running CAD Config-uration Manager or the Product Configuration Tool. For more information, see Network Installation andProduct Configuration (p. 32).

8.2. Configuring the Geometry Interface for NX for ANSYS WorkbenchProducts

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 UGNX Reader for Workbench option.

1. Launch CAD Configuration Utility.

2. Select CAD Interface Configuration to continue.

3. Select Configure UG NX Reader for Workbench to continue.

4. Enter the directory path to the NX installation path. Select OK to continue.

5. Select EXIT to close CAD Configuration Utility.



Chapter 9: Uninstalling the Software

To uninstall a product, issue the following command:

/ansys_inc/v171/ans_uninstall171

Alternatively, if you are using the Mechanical APDL product, you can use the Uninstall option of theANS_ADMIN utility. To launch ANS_ADMIN, issue the following command:

/ansys_inc/v171/ansys/bin/ans_admin171

1. From the uninstall panel, click Select Products to Uninstall.

If you are not a superuser, you will see a warning message, and then the uninstall continues.

2. A list of products that are installed appears. Select those products you want to uninstall and click Continue.Then click OK to confirm the list of products to be uninstalled.

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) fromall of the Linux platforms.





10.1. Installation Troubleshooting

This section lists problems and error messages that you may encounter while installing and/or runningANSYS, Inc. products. After each situation description or error message is the user action required tocorrect the problem.

You can also find answers to commonly-asked questions on our customer portal. After you log in tothe customer portal, select Knowledge Resources> Solutions.

For information on licensing-related errors, see the Troubleshooting section of the ANSYS LicensingGuide.

10.1.1. Gathering Diagnostic Information




10.1.2. The GUI Installation Process Hangs

• If the GUI installation process appears to “hang” during file extraction, with no activity appearing in themessage window, press ENTER on the command window used to start the installation. When the installationis complete, check the message window carefully for any installation errors or warnings; however, this situationrarely 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 awarethat some components require a lengthy extraction time; we recommend allowing up to 30 minutes forthese 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 increasethe size of any disk quotas on your $TEMP directory.

10.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 installationfiles from the Customer Portal on www.ansys.com, use a USB Flash drive or follow the instructions in



http://www.ansys.com/

Mounting the DVD Instructions for DVD Installations (Linux x64 Only) (p. 15) to mount to a machinethat does have a DVD drive.

10.1.4. CAD Configuration Manager Help Does Not Load

If the help for the CAD Configuration Manager does not load into your default browser, set theBROWSER environment variable to the path of your HTML viewer (such as Mozilla or Firefox) and restartthe CAD Configuration Manager.

10.1.5. Cannot Enter Data in Text Fields

SUSE On some SUSE Linux systems, if you cannot enter data in text fields during the installation orwhen using the ANSLIC_ADMIN utility, you may be encountering a Tcl incompatibility. To correct theproblem, unset the following environment variables before running the installation or the ANSLIC_ADMINutility:

QT_IM_MODULEXMODIFIERSGTK_IM_MODULE

You should reset these environment variables when you are finished running the installation or usingANSLIC_ADMIN. Do not permanently unset these environment variables as doing so could affect otherapplications.

10.1.6. Download and Installation Error Messages

The current platform type is not selected and is not included in current download files. Pleasemake sure that you are using the correct media or downloaded file. Continuing with a platforminstallation may require additional post-install configuration.

Do you want to continue?

This message occurs if you have selected a platform for installation that does not match the filesyou are trying to install (either from the installation DVD, USB 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. 15) and enter thecorrect pathname for your platform.

Licensing files currently installed for <platform> are more recent than those on the installationmedia. The <platform> files will not be installed and will be deselected.

This message appears during an ANSYS, Inc. product installation if the installed license managerfiles are newer than the ones being installed. You should always use the newest files. However, dueto 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, re-gardless of the file dates, re-run the installation with the -nodatecheck option. We strongly re-


Troubleshooting

commend that you exercise caution when running the installation with the -nodatecheck option;installing older license files can result in licensing errors and the inability to run ANSYS, Inc. products.

10.1.7. System-related Error Messages

Error, could not open display.

Either the DISPLAY environment variable is not correct or the xhosts command was not properlyset. See the Mechanical APDL Basic Analysis Guide for specific graphics information.

***Error, ANSYS171_DIR environment variable is not set. This is a fatal error – exiting.

This message indicates that the ANSYS171_DIR environment variable was not set where necessaryfor licensing. This environment variable (which is set in the scripts that run ANSYS) should be setto the release-specific installation directory.

10.1.8. 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 17.1 with a differentversion of MPI than is supported. See the Parallel Processing Guide for a complete list of supportedMPI versions.

10.2. Installation Troubleshooting - Mechanical APDL

The items listed below apply only to the Mechanical APDL product.

10.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 runningafter you log out of a session. If you are running via the Launcher, select Options> Use ‘nohup’ ToStart Batch Runs With Output Sent to ‘File Only.’ We do not recommend using this setting on systemsthat automatically set ‘nohup.’

10.2.2. Mechanical APDL Documentation File for User Interface Error Messages

Missing or erroneous documentation files for user interface. Command ignored.

Verify that the documentation list file for the user interface exists in the /ansys_inc/v171/an-sys/gui/en-us/UIDL subdirectory.

ls -l /ansys_inc/v171/ansys/gui/en-us/UIDL/menulist.ans

The system should respond with:

-rw-r--r-- 1 root 23 Jan 8 11:50 /ansys_inc/v171/ansys/gui /en-us/UIDL/menulist.ans



Installation Troubleshooting - Mechanical APDL

Make sure that the pathnames in the menulist.ans file are correct.

10.2.3. Launcher Error Messages

Some of the more common error messages follow. See the ANSYS Licensing Guide for licensing-relatedlauncher messages.

***Cannot create required <profile> file. Therefore, cannot write to profile information duringthis 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, thisdirectory is C:\Documents and Settings\<user name>\Application Data\AN-SYS\v171\launcher on Windows or ~/.ansys/v171/launcher on Linux.

10.2.4. FORTRAN Runtime Error Messages

The following error messages occur if you are running Mechanical APDL in a directory in which the userdoes not have write permission, or if Mechanical APDL files (i.e., Jobname.RST, Jobname.DB) existin the current directory but you do not have write permissions to the files. The specific messages thatappear on each system are shown below.

10.2.4.1. Intel Linux 64 Systems

Input/Output Error 177: Create Failure

In Procedure: fappnd

At Line: 72

Statement: Formatted WRITE

Unit: 19

10.2.4.2. Intel EM64T Linux x64 Systems

forrtl: Permission denied

forrtl: severe (9): permission to access file denied, unit 19, file /build/v171/ansys/objs

10.2.4.3. AMD Opteron Linux x64 Systems

***ERROR

Unable to open file /build/v171/ansys/objs/file.err for WRITE. Check directory and file permissions.

10.3. Installation Troubleshooting - ANSYS Workbench

10.3.1. Startup or Graphics Problems

To minimize graphics problems, always verify that you are running the latest graphics drivers providedby your computer's hardware manufacturer.


Troubleshooting

If you are running ANSYS Workbench on Linux and experience problems at startup or with the GUI orgraphics displaying correctly, and you are running in accelerated graphics mode, you may need to re-launch 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 tosoftware rendering. ANSYS Workbench also will use software rending mode by default when runningon 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

10.4. Installation Troubleshooting - ANSYS CFX

10.4.1. CFX Distributed Parallel Runs Fail

On some SLES machines (typically ones with more than one network card), the default configurationof /etc/hosts will cause CFX distributed parallel runs to fail. In such cases, the problem might besolved 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.

10.5. Contacting Technical Support

Technical Support for ANSYS, Inc. products is provided either by ANSYS, Inc. directly or by one of ourcertified ANSYS Support Providers. Please check with the ANSYS Support Coordinator (ASC) at yourcompany to determine who provides support for your company, or go to www.ansys.com and selectContacts> Contacts and Locations.

If your support is provided by ANSYS, Inc. directly, Technical Support can be accessed quickly and effi-ciently from the ANSYS Customer Portal, which is available from the ANSYS Website (www.ansys.com)under Support > Customer Portal. The direct URL is: support.ansys.com.

One of the many useful features of the Customer Portal is the Knowledge Resources Search, which canbe found on the Home page of the Customer Portal. To use this feature, enter relevant text (errormessage, etc.) in the Knowledge Resources Search box and click the magnifying glass icon. TheseKnowledge Resources provide solutions and guidance on how to resolve installation and licensing issuesquickly.

NORTH AMERICA

All ANSYS Products except Esterel, Apache and Reaction Design products

Web: Go to the ANSYS Customer Portal (http://support.ansys.com) and select the appropriate option.

Toll-Free Telephone: 1.800.711.7199 (Please have your Customer or Contact ID ready.)

Support for University customers is provided only through the ANSYS Customer Portal.

GERMANY

ANSYS Mechanical Products

Telephone: +49 (0) 8092 7005-55 (CADFEM)

Email: [email protected]

All ANSYS Products



Contacting Technical Support



http://support.ansys.com



National Toll-Free Telephone: (Please have your Customer or Contact ID ready.)

German language: 0800 181 8499

English language: 0800 181 1565

Austria: 0800 297 835

Switzerland: 0800 564 318

International Telephone: (Please have your Customer or Contact ID ready.)

German language: +49 6151 152 9981

English language: +49 6151 152 9982


UNITED KINGDOM

All ANSYS Products


Telephone: Please have your Customer or Contact ID ready.

UK: 0800 048 0462

Republic of Ireland: 1800 065 6642

Outside UK: +44 1235 420130



JAPAN

CFX and Mechanical Products

Telephone: +81-3-5324-7305

Email:

Mechanical: [email protected]

Fluent: [email protected];

CFX: [email protected];

Polyflow: [email protected];

Icepak

Telephone: +81-3-5324-7444


Licensing and Installation


INDIA

All ANSYS Products


Telephone: +91 1 800 209 3475 (toll free) or +91 20 6654 3000 (toll) (Please have your Customer orContact ID ready.)


Troubleshooting




FRANCE

All ANSYS Products


Toll-Free Telephone: +33 (0) 800 919 225 Toll Number: +33 (0) 170 489 087 (Please have your Customeror Contact ID ready.)



BELGIUM

All ANSYS Products


Toll-Free Telephone: (0) 800 777 83 Toll Number: +32 2 620 0152 (Please have your Customer or ContactID ready.)



SWEDEN

All ANSYS Products


Telephone: +46 (0) 10 516 49 00



SPAIN and PORTUGAL

All ANSYS Products


Spain: Toll-Free Telephone: 900 933 407 Toll Number: +34 9178 78350 (Please have your Customer orContact ID ready.)

Portugal: Toll-Free Telephone: 800 880 513 (Portugal)

Email: [email protected], [email protected]


ITALY

All ANSYS Products


Toll-Free Telephone: 800 789 531 Toll Number: +39 02 00621386 (Please have your Customer or ContactID ready.)











TAIWAN, REPUBLIC OF CHINA

Telephone: 866 22725 5828

K0REA

Telephone: 82-2-3441-5000

CHINA

Toll-Free Telephone: 400 819 8999 Toll Number: +86 10 82861715


Troubleshooting

Chapter 11: Applications Included with Each Product

The following table displays which ANSYS, Inc. applications are included with each of the product in-stallation options.

What is Included?Silent InstallOption

Product Install Option

ANSYS, Inc. Products

ANSYS Structural Mechanics

Workbench [1], MechanicalAPDL, ECAD

-mechapdlANSYS Mechanical Products

Workbench [1], MechanicalAPDL User-ProgrammableFeature


ANSYS Explicit Dynamics

Workbench [1], Autodyn-autodynANSYS Autodyn

Workbench [1], ANSYS LS-DYNA-lsdynaANSYS LS-DYNA

ANSYS Fluid Dynamics

Workbench [1], CFX, CFD-Post-cfxANSYS CFX (includes ANSYSCFD-Post)

Workbench [1], Fluent, CFD-Post-fluentANSYS Fluent (includes ANSYSCFD-Post)

Workbench [1], TurboGrid-turbogridANSYS TurboGrid

Workbench [1], CFD-Post,Polyflow

-polyflowANSYS Polyflow (includes ANSYSCFD-Post)

Workbench [1], CFD-Post-cfdpostANSYS CFD-Post only

Workbench [1], Forte-forteANSYS Forte

Workbench [1], Chemkin-chemkinproANSYS Chemkin

Workbench [1], Chemkin,Energico


Workbench [1], Chemkin,Reaction Workbench


Workbench [1], Chemkin, ModelFuel Library (Encrypted)

-mflANSYS Model Fuel Library(Encrypted)

Workbench [1], ICEM CFD-icemcfdANSYS ICEM CFD

ANSYS Additional Tools

ACP Only-acpANSYS Composite PrepPost

CFD-Post, Icepak, ECAD-icepakANSYS Icepak (includes ANSYSCFD-Post)



What is Included?Silent InstallOption


Remote Solve Manager-rsmANSYS Remote Solve ManagerStand Alone Services

ANSYS Geometry Interfaces

Geometry Interface for ACIS-acisACIS

Geometry Interface for Catia,Version 4

-catia4Catia, Version 4

Geometry Interface for NX-ug_reader,-ug_plugin

NX

Geometry Interface for Parasolid-parasolidParasolid

1. Workbench includes the Workbench Framework, DesignModeler, DesignXplorer, and Remote Solve Manager.


Applications Included with Each Product

Installation Guide for Windows


2600 ANSYS Drive ANSYS, Inc. iscertified to ISO9001:2008.

Canonsburg, PA [email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494


The information in this guide applies to all ANSYS, Inc. products released on or after this date, until supersededby 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 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1. System Prerequisites .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1.1. CAD Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2. Disk Space and Memory Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3. Software Prerequisites .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4. Requirements for the GPU Accelerator in Mechanical APDL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5. Additional Hardware and Software Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.5.1. ANSYS AIM Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5.2. 3Dconnexion Product Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.6.Third-Party Software and other Security Considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102. Platform Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1. Utilizing CPU Hyperthreading Technology with ANSYS CFD Solvers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2. Compiler Requirements for Windows Systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3. Select Your Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3. Installing the ANSYS Software for a Stand-alone Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1. Downloading the Installation Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1.1. Installing from a USB Drive .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.2. Installing from a DVD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.2. Installing ANSYS, Inc. Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.1. Product Installation with Client Licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2.1.1. Specifying CAD Configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.2. ANSYS License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.2.2.1. Registering the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234. Installing the ANSYS Products and the License Manager on Different Windows Machines . . . . . . . . . . . . . . . . 25

4.1. Downloading the Installation Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.1.1. Installing from a USB Drive .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.1.2. Installing from a DVD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.2. Installing ANSYS, Inc. Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.2.1. Product Installation with Client Licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.2.1.1. Network Server and Product Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.2.1.2. Specifying CAD Configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.2.2. ANSYS License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.2.1. Registering the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5. Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.1. Post-Installation Procedures for Mechanical APDL and ANSYS Workbench Products .... . . . . . . . . . . . . . . . . . . . . . 39

5.1.1. Post-Installation Procedures for ANSYS Fluent .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1.2. Post-Installation Procedures for ANSYS Polyflow .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1.3. Post-Installation Procedures for ICEM CFD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1.4. Post-Installation Procedures for Other Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.2. Launching ANSYS, Inc. Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.3. Running the ANS_ADMIN Utility for Mechanical APDL /ANSYS Workbench Products .... . . . . . . . . . . . . . . . . . . . . 415.4. Product Localization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.4.1. Translated Message File Installation for Mechanical APDL /ANSYS Workbench Products .... . . . . . . . 426. Installing the ANSYS, Inc. Product Help Documentation Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437. Silent Mode Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.1. Installing ANSYS, Inc. Products .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.1.1. Silent Mode Operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.1.1.1. Silent Product and License Manager Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.1.1.2. Silent Product Configuration/Unconfiguration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.1.1.3. Silent Media Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50



7.1.1.4. Silent Uninstall .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518. Configuring CAD Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

8.1. Using the CAD Configuration Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.1.1. Unconfiguring .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568.1.2. Running the CAD Configuration Manager in Batch Mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568.1.3. Network Considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588.1.4. Uninstalling .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.1.5. Creo Parametric Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

8.1.5.1. Configuring the Connection for Creo Parametric ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608.1.5.1.1. The WBPlugInPE.dat File and config.pro File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.1.5.1.2.The config.pro File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618.1.5.1.3.The config.anscon.171 File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

8.1.5.2. Creo Parametric Environment Variables .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.1.6. NX Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

8.1.6.1. Configuring the Connection for NX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.1.6.2. Configuring for Teamcenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

8.2. Configuring CADNexus/CAPRI CAE Gateway for CATIA V5 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638.3. Configuring AutoCAD ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

9. Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679.1. Uninstalling Licensing Components .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

10. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.1. Installation Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

10.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.1.2. Uninstall Gives Access Denied Error Message .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.1.3. Uninstall on a Windows 7, Windows 8.1 or Windows 10 System Gives Compatibility ErrorMessage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.1.4. A .chm File Does Not Display Properly Across a Network .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.1.5. Products Crash with an Application Error ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.1.6. Product Installation Does Not Create Start Menu Item for ANSYS and CAD Plugins Do NotWork .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.1.7. Product Installation Displays Security Warning Dialogs or Silent Product Installation Hangson a Network Install .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.1.8. System-related Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7110.1.9. CasPol Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

10.2. Installation Troubleshooting - Mechanical APDL and ANSYS Workbench Products .... . . . . . . . . . . . . . . . . . . . . . . 7110.2.1. The Mechanical APDL Launcher is Excessively Slow to Start ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7110.2.2. Display Problems on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7110.2.3. ANS_ADMIN Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7210.2.4. Mechanical APDL Product Launcher Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7210.2.5. Distributed Mechanical APDL IBM Platform MPI Error Messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7210.2.6. ANSYS Workbench Products Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

10.3. Installation Troubleshooting - ANSYS CFX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7310.3.1. TurboGrid Mouse Behavior Problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

10.4. Contacting Technical Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7411. Applications Included with Each Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77


Windows Installation Guide

List of Tables

1.1. Supported Windows Platforms .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2. Supported Products by Platform ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3. CAD Support by Platform ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1. Compiler Requirements for All Windows Versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13




Chapter 1: Installation Prerequisites for Windows

This document describes the steps necessary to correctly install and configure all ANSYS, Inc. productson Windows platforms for Release 17.1. These products include:

• ANSYS Structural Mechanics

– ANSYS Mechanical Products (includes ANSYS Mechanical and Mechanical APDL)

– ANSYS Customization Files for User Programmable Features

• ANSYS Explicit Dynamics

– ANSYS Autodyn

– ANSYS LS-DYNA

• ANSYS Fluid Dynamics

– 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 Offshore

– ANSYS Aqwa

• ANSYS Additional Tools

– ANSYS Icepak (includes ANSYS CFD-Post)

– Remote Solve Manager Standalone Services

• ANSYS PDM Interfaces

– Teamcenter

• ANSYS Geometry Interfaces

– AutoCAD

– ACIS






– Creo Elements/Direct Modeling

– Autodesk Inventor

– JTOpen

– NX

– Parasolid

– Creo Parametric

– Solid Edge

– SolidWorks

Note

ANSYS Workbench and ANSYS EKM Desktop are installed by default as product componentsto most ANSYS, Inc. products. ANSYS Workbench is not installed as part of the products underANSYS Additional Tools, nor with the CFD-Post only option. ANSYS Workbench includes thefollowing applications:

• The Mechanical Application

• DesignModeler

• Design Exploration

• Meshing

• Remote Solve Manager

• Fluent Meshing

• FE Modeler

• EKM Client

Because some of these applications can be run as standalone applications without ANSYSWorkbench, you will see some but not all of these listed separately as options when youuninstall. In such cases, you will need to select those options in order to uninstall thosecomponents.

Where supported, IGES and STEP Geometry Interfaces will be installed.

Some procedures apply only to specific products and are so noted.


Installation Prerequisites for Windows

Important Notice

If you want to run multiple releases of ANSYS, Inc. software, you MUST install them chronologically (i.e.,Release 16.0 followed by Release 17.1). If you install an earlier release after installing Release 17.1, youwill encounter licensing issues that may prevent you from running any products/releases. If you needto install an earlier release after you have already installed Release 17.1, you MUST uninstall Release17.1, then re-install the releases in order.


The following features are new or changed at Release 17.1. Please review these items carefully.

• ANSYS Reaction Design Products (Chemkin) are now included in the product installation and can be selectedon the product selection menu for installation.

• The ANSYS SpaceClaim Direct Modeler product is now available as a stand-alone package. This product isa 3D direct modeling application that allows users to create, edit, and prepare geometry for engineeringsimulation.

1.1. System Prerequisites

ANSYS 17.1 is supported on the following Windows platforms and operating system levels. 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.)

Table 1.1: Supported Windows Platforms

AvailabilityPlatform architecture(directory name)

Operating SystemProcessor

Download, USBwinx64Windows 7 (Professional & Enterprise),Windows 8.1 (Professional &

x64 (64-bit)

Enterprise), Windows 10 (Professional,Enterprise & Education), MicrosoftWindows HPC Server 2008 R2 [1],Windows Server 2012 R2 [1]

1. Microsoft Windows HPC Server 2008 R2 and Windows Server 2012 R2 are supported only for selectsolvers for parallel high performance execution. Any users running on Microsoft Windows HPC Server2008 R2 or Windows Server 2012 R2 as non-admin should be a member of the HPC Users Group in theconfiguration panel of the HPC Cluster Manager.

For detailed and current support information, see the Platform Support section of the ANSYS, Inc.website (www.ansys.com).

Note

Home editions of Windows operating systems are not supported.







Supported Platforms for High Performance Computing Please see the discussions on ConfiguringDistributed ANSYS and Configuring ANSYS CFX Parallel for detailed information on supported platformsfor distributed computing.

Table 1.2: Supported Products by Platform

WindowsServer 2012

MicrosoftWindows

HPC Server2008

Windows64-bit

Product

√ANSYS Workbenchdata-integrated andnative applications

Standalone Solvers and Applications

22√Mechanical APDL

22√CFX

√TurboGrid

√ICEM CFD

√Autodyn

√LS-DYNA

22√Fluent

√Aqwa

√Polyflow

22√Icepak

√EKM Server

1. Supported as a 32-bit application

2. 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 APDLW = ANSYS WorkbenchI = ANSYS ICEM CFD standalone (some CAD systems may require the integrated ANSYS Work-bench Reader)

Table 1.3: CAD Support by Platform

Windows 10Windows 8.1 6Windows 7Product

A, W, IA, W, IA, W, ICATIA 4.2.4

A, W, IA, W, IA, W, ICATIA V5–6R2016

W, I10W, ICATIA V5 (CADNexus CAPRI CAE Gateway V3.21.0)V5–6R2013, V5–6R2014, V5–6R2015

W, IW, IW, ICATIA V6 R2015x



Windows 10Windows 8.1 6Windows 7Product

A, W, IA, W, IParasolid 27.09

A, W, ICreo Parametric Wildfire 5.0 2, 3

A, W, IA, W, IA, W, ICreo Parametric 2.0 11

A, W, IA , W, IA, W, ICreo Parametric 3.0

A, W, IA, W, IA, W, IACIS 2016 1.01

AA, W, IA, W, INX 8.5

AA, W, IA, W, INX 9.0

A, W, IA, W, IA, W, INX 10.0

W, IW, ISolidWorks 2015

W, IW, IW, ISolidWorks 2016

W, IW, ISolid Edge ST7

W, IW, ISolid Edge ST8

W, IW, IAutodesk Inventor 2015

W, IW, IW, IAutodesk Inventor 2016

W, IAutoCAD 2013

W, I 12W, IAutoCAD 2014

W, IW, IAutoCAD 2016

A, W, IA, W, IIGES

W, IW, IW, IJT 10.0

W, IW, ISTEP AP203, AP214

W, I 7W, ICreo Elements/Direct Modeling 18.1

W, IW, IW, ICreo Elements/Direct Modeling 19.0

W, ITeamcenter Unified Architecture 10.1.0.1 (2– &4–tier) with NX 8.5.2 MP1 & NX 9.0

W, IW, ITeamcenter Unified Architecture 11.2 (NX 10.0only)

IIGEMS

IIIDI MS8/9

W, IW, IRhinoceros

W, IW, ISketchUp

W, IW, IW, IGAMBIT 2.4

1. For ICEM CFD standalone, ACIS 18.0.1 is the supported version for all platforms.

2. Requires Pro/ENGINEER 5 Build Date M020 or higher for Windows 7.

3. Pro/ENGINEER Wildfire 5 is also named Creo Elements/Pro 5.0.

4. MAPDL supports 5.1 by default, but 5.2 is also supported if the IOPTN command is used.

5. IGES Versions 4.0, 5.2, and 5.3 are supported.

6. Professional and Enterprise




7. Requires CoCreate 18.1 M060 or later.

8. Requires AutoCAD 2013 SP2.

9. For ICEM CFD direct interface, Parasolid 24.0 is the supported version on all platforms.

10. Only versions V5–6R2014 and V5–6R2015 are supported on Windows 8.1.

11. Requires Creo Parametric 2.0 M100.

12. Requires Installation of Autodesk’s Model Documentation Hotfix.

Note

View the latest supported CAD packages at ansys.com> Solutions> Solutions by Role>IT Professionals> Platform Support> CAD Support.

1.2. Disk Space and Memory Requirements

You will need the disk space shown here for each product for installation and proper functioning. Thenumbers 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.

Disk SpaceProduct

12.4 GBANSYS Mechanical APDL

6.8 GBANSYS Autodyn

7.1 GBANSYS LS-DYNA

19.7 GBANSYS AIM

7.4 GBANSYS CFX

6.7 GBANSYS TurboGrid

8.9 GBANSYS Fluent

7.2 GBANSYS Polyflow

6.6 GBANSYS Aqwa

7.1 GBANSYS ICEM CFD

5.3 GBANSYS Icepak

6.7 GBANSYS CFD Post only

6.0 GBANSYS Forte

5.4 GBANSYS Geometry Interfaces

5.1 GBCATIA V5

1.8 GBCATIA v6

1.7 GBANSYS Remote Solve Manager Standalone Services

2.0 GBANSYS Composite PrepPost

Product installations also require an additional 500 MB of free disk space during an installation.

Memory Requirements You must have a minimum of 8 GB of memory to run product installations;16 or 32 GB of memory is recommended.



1.3. Software Prerequisites

You must have the following software installed on your system. Administrator privileges are requiredto install these files. These software prerequisites will be installed automatically when you launch theproduct installation. If you've completed an installation successfully, the executables are also locatedunder the \v171\prereq directory should you need to manually install them at a later date. Prior toinstalling, you can find them in the root \prereq directory of the media/download package.

• Microsoft .NET Framework 4.0

.NET Framework 4.0 is native on Windows 8.1 and Windows 10 and do not require any additionalpatches.

.NET Framework 4.0 is required for Windows 7.

• Microsoft Visual C++ 2005 SP1 Redistributable, 2.0.50727.762

• Microsoft Visual C++ 2008 SP1 ATL Redistributable Package

• Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update

• Microsoft Visual C++ 2010 SP1 ATL Redistributable Package

1.4. Requirements for the GPU Accelerator in Mechanical APDL

Your system must meet the following requirements to use the GPU accelerator capability in MechanicalAPDL:

• The machine(s) being used for the simulation must contain at least one supported NVIDIA GPU card or oneIntel Xeon Phi coprocessor. The following cards are supported:

NVIDIA Tesla K20c (both workstation and server)NVIDIA Tesla K40c (both workstation and server)NVIDIA Tesla K80 (server with GPU cooling solution only, 2 GPUs consume 2 ANSYS HPC licenses)NVIDIA Quadro K5000NVIDIA Quadro K5200NVIDIA Quadro K6000NVIDIA Quadro M6000Intel Xeon Phi 7120Intel Xeon Phi 5110Intel Xeon Phi 3120

• For NVIDIA GPU cards, the driver version must be 353.06 or newer. For optimal performance on Windows,the TCC (Tesla Compute Cluster) driver mode is recommended when using Tesla series GPU cards. Somelimitations exist when using this driver mode (e.g., no support for Windows XP). Check your GPU card doc-umentation for more details on how to set this driver mode and the existing limitations.

• For Intel Xeon Phi coprocessors, the driver version must be “MPSS 3.5” or newer.

Note

On Windows, the use of Remote Desktop may disable the use of a GPU device. LaunchingMechanical APDL through the ANSYS Remote Solve Manager (RSM) when RSM is installed



Requirements for the GPU Accelerator in Mechanical APDL

as a service may also disable the use of a GPU. In these two scenarios, the GPU acceleratorcapability cannot be used. Using the TCC (Tesla Compute Cluster) driver mode, if applicable,can circumvent this restriction.

1.5. Additional Hardware and Software Requirements

• Intel 64 / AMD64 system with the correct operating system version installed

• 8 GB of RAM

• 128 GB free on the hard drive is recommended

• Discrete graphics card with the latest drivers and compatible with the supported operating systems. Whenworking with large 3D models, use of a recent NVIDIA Quadro or AMD FirePro card is recommended. Forthe AIM product, see ANSYS AIM Requirements (p. 9).

For information on the most recently tested NVIDIA and AMD graphics cards, see ANSYS.com>Support> Platform Support and view the Graphics Cards Tested PDF for your release.

Note

Use of Ultra High Definition (4K) graphics cards may cause a number of cosmeticdisplay issues (including enlarged or reduced text and incorrect positioning of optionlabels). These issues do not affect the functionality of the installation program.

A minimum screen resolution of: 1024 x 768 (4:3 aspect ratio), 1366 x 768 (16:9 aspect ratio) or 1280x 800 (16:10 aspect ratio) with minimum 24 bit color. A higher screen resolution such as 1920x1080(16:9) or 1920x1200 (16:10) is strongly recommended for most applications.

Note

Some combinations of graphics card type, operating system, and MPEG resolution fail toplay MPEGs properly. You may be able to get normal playback results simply by changingthe MPEG settings. Alternatively, you can upgrade your graphics card.

• For laptop systems, ANSYS Workbench requires the latest graphics drivers.

• Microsoft Mouse or a mouse. Most applications require a three-button mouse.

• If you use a 3Dconnexion product, 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 systemmay limit the size of the ANSYS model that can be created and/or solved.

• TCP/IP for the license manager (see the ANSYS 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. WhenTCP/IP is installed, it must be bound to a network adapter. On machines that are connected to aninternal network, TCP/IP must be bound to a network card such as an Ethernet adapter. The vastmajority of systems using TCP/IP will fall into this category. On machines that connect to the internetor 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 attemptto connect to the Internet every time ANSYS is run. See the ANSYS Licensing Guide for more inform-ation.

• Microsoft Internet Explorer (IE) 11 or greater 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 install-ation, simply run your preferred browser and reestablish it as the default.

• PDF reader software is required to read the installation guides and other user documentation.

To access our help system videos, ANSYS recommends that you set Windows Media Player as yourdefault. Note--The default media player for Windows 8.1 is defined as Video; please change this settingto Windows Media Player.

1.5.1. ANSYS AIM Requirements

For basic usage and simple models, a workstation-class 3D-capable graphics card with at least 256 MBof memory that supports OpenGL version 3.3 or higher, as noted below, is needed to successfully runAIM.

To analyze larger models, use a recent NVIDIA Quadro or AMD FirePro card, including:

AMD MobileAMDNVIDIA MobileNVIDIA

FirePro Mx9xxFireProVx900

Quadro x700MQuadro FX 470x

FireProMx000

FirePro WxQuadro x800MQuadro FX x800

FireProWxxxxM

FirePro SxQuadro x000MQuadro x000

Quadro K Series MQuadro K Series

Quadro Maxwell SeriesM

Quadro MaxwellSeries

Note on Intel Graphics Cards: Use of integrated Intel graphics cards is not recommended. These cardsare typically found in lightweight laptops or notebooks, and are known to have OpenGL incompatibil-ities resulting in display issues in AIM. Examples are Intel HD 3000 and 4000 series cards.

Note on Hybrid Graphics: If your graphics system supports two graphics chips, one integrated andone dedicated (example is NVIDIA Optimus), ensure that the dedicated graphics chip is used whenlaunching AIM. Instructions on how to do this can typically be found on graphics card vendor's website.

Note on Vendor Legacy Support: To be compatible, legacy GL 3.3 compliant cards should still bewithin the official legacy support period of their respective graphics vendor, and must still be receivingregular driver updates. Visit the vendor websites (AMD and NVIDIA) to review legacy hardware lists.

1.5.2. 3Dconnexion Product Support

Only the Mechanical APDL, ANSYS Meshing, DesignModeler, Mechanical, ANSYS ICEM CFD, and CFD-Post applications have been tested for manipulating the model (turning, zooming, panning, etc.) withthe 3Dconnexion products. While these 3Dconnexion products do provide significantly enhanced 3D



Additional Hardware and Software Requirements

control over viewing the model, they do not function as a mouse replacement and selection operationsstill require a mouse.

To use a 3Dconnexion product with the listed products, you must download and install the appropriateMicrosoft Windows driver for your version of Windows. Please refer to http://www.3dconnexion.comfor more information on using Space products and to download the appropriate drivers.

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 installationto work properly, you must allow access to these products.

Executable NameProduct Name

tclsh.exeTcl

want.exeTk

perl.exePerl

7z.exe7zip

.netMicrosoft .NETFramework



http://www.3dconnexion.com

Chapter 2: Platform Details

Windows 7, Windows 8.1 and Windows 10 User Account Control (UAC)

Windows 7, Windows 8.1 and Windows 10 use a feature called User Account Control (UAC) to controlprivileges 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.

ANSYS, Inc. requires that you have full administrative privileges when installing any software on MicrosoftWindows 7, 8.1 and 10. Non-administrative accounts do not usually have the permissions required toaccess 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 administratorwith UAC turned on and Run as Administrator selected. Because of changes to the UAC functionality,it is necessary that you right-click and select Run as Administrator from the context menu when in-stalling to Windows 8.1 or Windows 10.

Recommended Installation Options for Windows 7:

• 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 contextmenu)

Note

If you are running with UAC on, even if you have administrative privileges, you will havelimited account control unless you specifically choose Run as Administrator.

Recommended Installation Options for Windows 8.1 and Windows 10:

• UAC turned off and install with full administrative privileges (using Run as Administrator from the contextmenu)

When installing ANSYS, Inc. products, we strongly recommend that you use the recommended optionsabove. 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 disableUAC.

Follow the instructions for your operating system for disabling UAC.

Once you have installed your applications, you can enable UAC again.

Installing with UAC On

If you cannot disable UAC and need to install with UAC on, you must run all applications, including theinstallation setup, as an administrator. Otherwise, the files may be written to AppData\Local\Vir-



tualStore\<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 perform the following functions:

For Windows 7:

• Always run ANSLIC_ADMIN, the File Association utility, and the CAD Configuration Manager by selectingthe 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. Right-click the shortcut you wish to modify and select Properties.

2. From the Properties dialog box, click Advanced on the Shortcut tab.

3. Select Run as administrator and click OK.

4. Click OK.

Refer to your operating system documentation or visit www.microsoft.com for more instructions onsetting Run as Administrator at various levels within the operating system.

For Windows 8.1 and Windows 10:

• Always run ANSLIC_ADMIN, the File Association utility, and the CAD Configuration Manager byselecting the utility or application from the Start menu and right-mouse clicking and selecting Run asAdministrator.

• Set your Start menu shortcuts to always run as administrator with the following procedure (or similar):

1. Right-click the shortcut you wish to modify and select Open File Location from the options locatedat the bottom of your screen.

2. Right-click the shortcut file that is displayed and click Properties from the menu.

3. From the Properties dialog box, click Advanced on the Shortcut tab.

4. Select Run as administrator and click OK.

5. Click OK.

Notes about UAC

When installing ANSYS, Inc. products, including the license manager, on Windows 7, Windows 8.1 orWindows 10 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 installthe product.

If you install both the product and the license manager with full administrative privileges, the productand licensing installation and configuration will proceed as normal.

If you install as an administrative user with UAC turned on, you may encounter unpredictable behaviorwith both the product and license manager installations and subsequent behavior. As an administrator,


Platform Details

you should choose to install and run applications with full administrative privileges to avoid any unpre-dictable situations. We strongly recommend against running with UAC on and not selecting Run asAdministrator. These situations are described below.

1. If you have UAC turned on and you do not install (and run) with full administrative privileges, be awarethat files may be written to and read from the %localappdata%\VirtualStore\ location (in the caseof licensing, to %localappdata%\VirtualStore\Program Files\ANSYS Inc\SharedFiles\Licensing) instead of to the <os drive>.

In this situation, ANSLIC_ADMIN settings, such as Specify the License Server Machine, will indicatethat files are being written to and read from <os drive>\Program Files\ANSYS Inc\SharedFiles\Licensing. Log files may behave in the same way. However, when you view the an-syslmd.ini file located in <os drive>\Program Files\ANSYS Inc\SharedFiles\Licensing, you will not see the ANSLIC_ADMIN settings you specified.

2. To ensure that files are correctly written to and read from <os drive>\Program Files\ANSYSInc\Shared Files\Licensing, you should always run with full administrative privileges by selectingRun as Administrator.

3. If you are not running with full administrative privileges, you will not be able to use those ANSLIC_ADMINoptions that require administrative privileges, such as starting and stopping the license manager.

2.1. Utilizing CPU Hyperthreading Technology with ANSYS CFD Solvers

Hyperthreading technology uses one processor core to run more than one task at a time. ANSYS doesnot recommend using hyperthreading technology in conjunction with ANSYS CFD Solvers (Fluent, CFXand AIM Fluids). We recommend that you turn CPU hyperthreading off (default is on). A system admin-istrator needs to reboot the system and enter the BIOS to turn the hyperthreading option off.

2.2. Compiler Requirements for Windows Systems

Table 2.1: Compiler Requirements for All Windows Versions

AUTODYNCompilers*

Fluent Compilers*CFX Compilers*Mechanical APDL,ANSYS WorkbenchCompilers*

Visual Studio 2012(including the MS

Visual Studio 2012,2013 and 2015

Visual Studio 2012(including the MS

Visual Studio 2012(including the MS C++

C++ compiler)compilers (includingC++ compiler) andcompiler) and Inteland Intelthe MS C++

compiler)Intel FORTRAN15.0.2 compilers

FORTRAN 15.0.2compilers FORTRAN 15.0.2

compilers

* Compilers are required only if you will be using User Programmable Features (UPF), User DefinedFunctions (UDF), or other customization options.

2.3. Select Your Installation

The next step is to select your installation type. Please select the option below that matches your install-ation.

• Installing the ANSYS Software for a Stand-alone Windows System (p. 15)



Select Your Installation

• Installing the ANSYS Products and the License Manager on Different Windows Machines (p. 25)


Platform Details

Chapter 3: Installing the ANSYS Software for a Stand-alone WindowsSystem

This section includes the steps required for installing ANSYS, Inc. products and licensing configurationon one Windows machine.

You can follow these instructions while actually installing the products and setting up the licenseserver. To do so, simply use the selections that are pertinent to you and insert your specific informationwhere noted.

Before You Begin




• Open port numbers forFlexNet and ANSYS Licensing Interconnect. Defaults are 1055 and 2325, respectively.To verify that these port numbers are available, open a command line and enter the following command:

netstat -a -p tcp


• Your local machine's hostname, to specify as the license server.

You should also verify that you are running on a supported platform. ANSYS, Inc. supports 64-bit systemsrunning Windows 7, 8.1 and 10.

Verify that you have sufficient disk space to download, uncompress, and install the products you willbe installing.


These instructions are divided into four sections:

• Product Download/DVD Instructions: This set of instructions describes the download and extraction process.








For this installation, both the product and the license manager will be installed on the same machine.You must complete both the client licensing portion and the license manager installation in order to runANSYS, Inc. products.

3.1. Downloading the Installation Files













9. Begin the product installation as described in Installing ANSYS, Inc. Products (p. 17).

3.1.1. Installing from a USB Drive

To install ANSYS, Inc. products from a USB drive, insert the USB drive into a USB slot on your computer.Locate and right-click the setup.exe file stored at the root level of the USB and select Run as adminis-trator. Continue with the steps described in Installing ANSYS, Inc. Products (p. 17).

3.1.2. Installing from a DVD

To install ANSYS, Inc. products from a DVD, place the DVD in your DVD drive. If autorun is enabled, theinstallation will begin automatically. If autorun is disabled, locate and right-click the setup.exe filecontained on the DVD and select Run as administrator. Continue with the steps described in InstallingANSYS, Inc. Products (p. 17).


Installing the ANSYS Software for a Stand-alone Windows System


You will be prompted to change DVDs during the installation. Please make sure you have all installationDVDs before beginning the installation.

3.2. Installing ANSYS, Inc. Products

This section explains how to install ANSYS, Inc. products.

Note

ANSYS requires users to install all products by using the right-click option Run as ad-ministrator.

.

3.2.1. Product Installation with Client Licensing

To install ANSYS, Inc. products with client licensing, follow the steps below.

Note

You must also install the ANSYS, Inc. License Manager on at least one server machine in orderto run ANSYS, Inc. products. See ANSYS License Manager Installation (p. 22) for licensemanager installation instructions.

1. Save all data and close all Windows applications before continuing.

2. If you downloaded the installation files or if you are installing from a DVD or USB with autorun disabled,browse to the location of the setup.exe file. Right-click the setup.exe file and select Run as admin-istrator.




Installing ANSYS, Inc. Products

From the options on the left side of the launcher you can install ANSYS products, ANSYS EKMServer, MPI for ANSYS Parallel Processing, and the ANSYS License Manager. You can access the in-stallation guide for the ANSYS EKM Server from the Downloads page on the Customer Portal. TheMPI for ANSYS Parallel Processing installation steps are displayed when you click the Install MPIfor ANSYS Parallel Processing link.


3. Select the language you want to use from the drop-down menu in the upper right corner. English is thedefault.



5. Read the agreement, and if you agree to the terms and conditions, select I Agree. Click the Next arrow,located on the right side of the screen.

6. The directory where you want to install the ANSYS, Inc. products is shown in the Install Directory field.You can install the products into any directory you want, but you must have write permissions to thedirectory you choose. The default is C:\Program Files\ANSYS Inc. We recommend using the defaultdirectory.

Note

You must install all ANSYS, Inc. products into the same location. Installing productsinto different locations can cause product components to fail. If you choose an installdirectory via the Browse feature, the installation will automatically append \ANSYSInc\ to the chosen directory. The installation path can have a maximum of 100characters, except on AUTODYN, which has a maximum of 40 characters.

• Leave the Associate file extensions with ANSYS products checkbox marked. This allows you todouble-click files from Windows Explorer to launch the various products.

• Choose Disable ANSYS RSS Feed to disable automatic internet feeds to ANSYS, Inc. products.











If the installation program was unable to query your license server, this message is not displayedand the default installation options are selected.


If you select AutoCAD, Catia V5, Inventor, NX, Creo Parametric, Solid Edge, or SolidWorks, you willhave additional installation steps. These steps are completed on the CAD Configuration screenwhich is displayed when you click the Next arrow. For additional information on completing thesesteps, see Specifying CAD Configurations (p. 20).

Note

As of Release 17.0 the MechASAS package is no longer installed with the ANSYSMechanical Products. This package is required when using BEAMCHECK and FAT-JACK assessment types with Design Assessment. If you need the MechASASpackage, please download it from the ANSYS Customer Portal.



Note


Select/deselect the products you want to install and click the Next arrow.


9. A summary of the selected installation data appears. Review the information carefully, and if correct, clickthe Next arrow to continue the installation.

10. The installation progress screen displays a status bar towards the bottom of the installation window. Thisstatus bar tracks the percentage of packages that have been installed on your computer. Depending on




the number of products you have selected, the installation time required could be lengthy. You will notbe able to interrupt the installation process. Please be patient while the installation completes.

Note


The installation program will first check your system to determine if you have the necessary pre-requisites. If the prerequisites are not already on your system, the prerequisites will be installedautomatically. You may be asked to run the necessary files (such as the .NET exe), or to reboot yourmachine, depending on your existing machine configuration. If you are asked, you will need toreboot in order to complete the prerequisite installation successfully.



Note

If prerequisite components necessary for the installation of the ANSYS productswere installed, the following message may be displayed:

A system restart is required before using any ANSYS Products.

The ANSYS, Inc. Installation Launcher appears. For this stand-alone installation, you must completethe License Manager installation (next) to run ANSYS, Inc. products.

3.2.1.1. Specifying CAD Configurations

Selecting AutoCAD, Catia V5, Inventor, NX, Creo Parametric, Solid Edge, or SolidWorks from the productselection screen and clicking the Next arrow displays the CAD Configuration screen. This screen containsthe configuration properties for each CAD product that you have selected in an expanded "accordion"view.


If you have not yet installed the related CAD programs, or do not know the requested information, youcan choose to skip these configuration steps by selecting the Skip all and configure later using CADConfiguration Manager option located on the lower left-hand portion of the screen. If you skip thesesteps, you will need to manually configure these CAD interfaces using the CAD Configuration Managerbefore you can successfully import models into Mechanical APDL, ANSYS Workbench, or ICEM CFD. Youcan access the CAD Configuration Manager in Windows 7 (Start > All Programs > ANSYS 17.1 >Utilities > CAD Configuration Manager 17.1), Windows 8.1 (Right-click the Start Screen> All apps>ANSYS 17.1 > CAD Configuration Manager 17.1) and in Windows 10 (Start > All apps> ANSYS 17.1> CAD Configuration Manager 17.1). See Configuring CAD Products (p. 53) for more information onusing the CAD Configuration Manager.



AutoCAD

• If you selected AutoCAD as one of your CAD products, you will have to choose which AutoCAD productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).

CATIA V5


Autodesk Inventor

• If you selected Inventor as one of your CAD products, you will have to choose which Inventor product toconfigure. You can choose the Reader (non-associative), Workbench Associative Interface (requires thatthe CAD product be installed), or skip and configure later (using the CAD Configuration Manager).

NX




Creo Parametric

1. If you selected Creo Parametric, you will have to choose which Creo Parametric product to configure. Youcan choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD productbe installed), or skip and configure later (using the CAD Configuration Manager).

2. 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:\ProgramFiles\PTC\Creo 1.0\Parametric by default) for an existing Creo Parametric installation.

SolidWorks

• If you selected SolidWorks as one of your CAD products, you will have to choose which SolidWorks productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).




Solid Edge

• If you selected Solid Edge as one of your CAD products, you will have to choose which Solid Edge productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).


Follow the instructions below to install and configure the ANSYS License Manager on your local Windowsmachine. You must be an administrative user to install the ANSYS License Manager on Windows. TheLicense Manager controls access to the ANSYS, Inc. products you have purchased. You must completethe License Manager installation to run ANSYS, Inc. products.

1. If the Installation Launcher is not open, right-click the setup.exe file and select Run as administrator.

2. Select Install ANSYS License Manager.

If you downloaded only the license manager installation, right-click setupLM.exe and select Runas administrator.

3. The installation launcher appears.

4. You will be notified that the license manager, if running, will be shut down. Click OK.

5. The License Agreement screen appears. Read the license agreement, and if you agree, click I Agree toaccept the terms and click the Next arrow, located on the right side of the screen.. You must select I Agreeto continue with the installation.

6. Specify the installation directory and click the Next arrow to continue.. You can accept the default orspecify an alternate path and the directory name where the license manager is to be installed. The install-ation directory is set to <OS_Drive>\Program Files\ANSYS Inc by default. You must have ad-ministrative privileges for the directory you specify. In addition, the directory:

• must be a local directory

• must be a local, fixed-media drive

• cannot be a UNC or relative path

• cannot be a short (8.3) file name format path

• cannot be a symbolic link or junction

• cannot use wide character names/paths

Note




The ANSYS, Inc. License Manager is the only component available and is selected to be installed.The amount of disk space required and the disk space available appear at the bottom of the window.Be sure that you have sufficient space before continuing.

7. Click the Next arrow to continue.


The ANSYS License Manager is now being installed and configured on your system. After the LicenseManager installation has been completed, the Launch License Management Center upon exitingoption is included on the screen. The ANSYS License Management Center is a browser-baseduser interface that centralizes many of the ANSYS product licensing administrative functions. If youdo not want to launch the License Management Center, uncheck the Launch License ManagementCenter upon exiting option.


10. When the license manager installation is complete, click Exit. A new Start Menu item named ANSYS, Inc.License Manager will be created automatically. It will include selections for the License ManagementCenter, the ANSYS, Inc. Licensing Guide, the FlexNet License Administration Guide and the ANSLIC_ADMINutility.









After completing the installation process, please refer to Post-Installation Instructions (p. 37)





Chapter 4: Installing the ANSYS Products and the License Manageron Different Windows Machines

This section describes installing ANSYS, Inc. products on one Windows machine and installing the ANSYS,Inc. License Manager on a different Windows machine that will act as a license server.

You can follow these instructions while actually installing the products and setting up the licenseserver. To do so, simply use the selections that are pertinent to you and insert your specific informationwhere noted.

Before You Begin




• Open port numbers for FlexNet and ANSYS Licensing Interconnect on your license server machine. Defaultsare 1055 and 2325, respectively. To verify that these port numbers are available, open a command line onthe server machine and enter the following command:

netstat -a -p tcp

You will see a list of active ports. If 1055 and 2325 are listed, they are already in use and cannot beused for ANSYS, Inc. licensing. In this case, you will need to specify different port numbers where in-dicated later in this tutorial.

• The hostname of the machine that will act as a license server.

You should also verify that you are running on a supported platform. ANSYS, Inc. supports 64-bit systemsrunning Windows 7, Windows 8.1 and Windows 10.

Verify that you have sufficient disk space to download, uncompress, and install the products you willbe installing.

For network installations, the same UNC paths or mapped drive letters must be used on the server andall client computers. Failure to use matching UNC paths or mapped letter drives can cause servercommunication issues or loss of product functionality.


This installation is divided into four sets of instructions:

• Product Download/DVD Instructions: This set of instructions describes the download and extraction process.








For this procedure, the product and the license manager will be installed on separate Windows machines.You must complete both the client licensing portion and the license manager installation in order to runANSYS, Inc. products.

4.1. Downloading the Installation Files













9. Begin the product installation as described in Installing ANSYS, Inc. Products (p. 27)

4.1.1. Installing from a USB Drive

To install ANSYS, Inc. products from a USB drive, insert the USB drive into a USB slot on your computer.Locate and right-click the setup.exe file stored at the root level of the USB and select Run as adminis-trator. Continue with the steps described in Installing ANSYS, Inc. Products (p. 27).


Installing the ANSYS Products and the License Manager on Different Windows Ma-chines


4.1.2. Installing from a DVD

To install ANSYS, Inc. products from a DVD, place the DVD in your DVD drive. If autorun is enabled, theinstallation will begin automatically. If autorun is disabled, locate and right-click the setup.exe filecontained on the DVD and select Run as administrator. Continue with the steps in Installing ANSYS,Inc. Products (p. 27).

If you are installing from media, you will be prompted to change DVDs during the installation. Pleasemake sure you have all installation DVDs before beginning the installation.



Note

ANSYS requires users to install all products by using the right-click option Run as ad-ministrator.

4.2.1. Product Installation with Client Licensing

To install ANSYS, Inc. products, including client licensing, follow the steps below.

Note

You must also install the ANSYS, Inc. License Manager on at least one server machine in orderto run ANSYS, Inc. products. See ANSYS License Manager Installation (p. 35) for licensemanager installation instructions.


2. If you downloaded the installation files or if you are installing from a DVD or USB with autorun disabled,navigate to the location of the setup.exe file. Right-click the setup.exe file and select Run as admin-istrator.





From the options on the left side of the launcher you can install ANSYS products, ANSYS EKMServer, MPI for ANSYS Parallel Processing, and the ANSYS License Manager. You can access the in-stallation guide for the ANSYS EKM Server from the Downloads page on the Customer Portal. TheMPI for ANSYS Parallel Processing installation steps are displayed when you click the Install MPIfor ANSYS Parallel Processing link.


3. Select the language you want to use from the drop-down menu in the upper right corner. English is thedefault.



5. Read the agreement, and if you agree to the terms and conditions, click I Agree. Click the Next arrow,located on the right side of the screen..

6. The directory where you want to install the ANSYS, Inc. products is shown in the Install Directory field.You can install the products into any directory you want, but you must have write permissions to thedirectory you choose. The default is C:\Program Files\ANSYS Inc. We recommend using the defaultdirectory.

Note

You must install all ANSYS, Inc. products into the same location. Installing products intodifferent locations can cause product components to fail. If you choose an install directoryvia the Browse feature, the installation will automatically append \ANSYS Inc\ to thechosen directory. The installation path can have a maximum of 100 characters, excepton AUTODYN, which has a maximum of 40 characters. For a network installation, the



same UNC paths or mapped drive letters must be used on the server and all clientcomputers.

• Leave the Associate file extensions with ANSYS products checkbox marked. This allows you todouble-click files from Windows Explorer to launch the various products.

• If you specify a network location as the installation directory, you should select the Add .NET securityexceptions on the above install directory option. This option allows the .NET binaries that are locatedunder the \ANSYS Inc directory on the shared machine to be run from the network. To understandthe implications of this security exception for .NET, please contact your system administrator or seeMicrosoft’s website http://msdn.microsoft.com/en-us/library/7c9c2y1w(v=vs.80).aspx.

• Choose Disable ANSYS RSS Feed to disable automatic internet feeds to ANSYS, Inc. products.

• Used with network installations, this option allows the .NET binaries that are located under the \ANSYSInc directory on the shared machine to be run from the network.






8. All products available in the installation package(s) you downloaded are listed. The installation programattempts to query your license server to pre-select your installation options. If the query is successful, thefollowing message is displayed:


If the installation program was unable to query your license server, this message is not displayedand the default installation options are selected.


If you select AutoCAD, Catia V5, Inventor, NX, Creo Parametric, Solid Edge, or SolidWorks, you willhave additional installation steps. These steps are completed on the CAD Configuration screenwhich is displayed when you click the Next arrow. For additional information on completing thesesteps, please see Specifying CAD Configurations (p. 33).

Note

As of Release 17.0 the MechASAS package is no longer installed with the ANSYSMechanical Products. This package is required when using BEAMCHECK and FAT-




http://msdn.microsoft.com/en-us/library/7c9c2y1w(v=vs.80).aspx

JACK assessment types with Design Assessment. If you need the MechASASpackage, please download it from the ANSYS Customer Portal.



Note


Select/deselect the products you want to install and click the Next arrow.




Note


The installation program will first check your system to determine if you have the necessary pre-requisites. If the prerequisites are not already on your system, the prerequisites will be installedautomatically. You may be asked to run the necessary files (such as the .NET exe), or to reboot yourmachine, depending on your existing machine configuration. If you are asked, you will need toreboot in order to complete the prerequisite installation successfully.


11. The product installation window reappears with a message noting that the installation is complete. ALaunch Survey Upon Exiting option is included here. Clicking Exit while the Launch Survey Upon Ex-



iting is enabled causes your default browser to open, displaying the product survey. Disabling (un-checking) the Launch Survey Upon Exiting option and then clicking Exit skips the survey.

Note

If prerequisite components necessary for the installation of the ANSYS productswere installed, the following message may be displayed:

A system restart is required before using any ANSYS Products.

4.2.1.1. Network Server and Product Configuration

To complete a network installation (where the product is installed on one machine and multiple clientsaccess that installation to run the product) to a file server machine, follow the steps below. A networkinstallation must be homogeneous, although you can install on different operating systems.

1. Install the product(s) to be shared in a location that all clients can access. Install all platforms that thismachine will host as described in Product Installation with Client Licensing (p. 27).

You must share the entire \ANSYS Inc directory, not just the \v171 directory. If mapping adrive to the shared location, it must be mapped to the \ANSYS Inc folder.

2. Open the Product Configuration Manager (\\fileservermachine\ANSYS Inc\v171\Product-Config.exe). Select Install Required Prerequisites. You must be logged in as an administrative userto install the prerequisites. This step must be completed on all client Windows systems.

3. A configuration status screen appears. This screen displays the required prerequisite installation process.Once the process is complete, click Exit. The Product Configuration Manager remains open.

4. On each Windows client, update the .NET security settings. By default, the .NET 3.5 Framework preventsapplications from being run over a network. In order to install over a network, each Windows client thataccesses 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 fromthe network. To make this modification from the Product Configuration Manager, select Add .NET securityexception for ANSYS, Inc. products. You must have administrative privileges to modify the securitypolicy.

To understand the implications of this security exception for .NET, please contact your system ad-ministrator or see Microsoft’s website http://msdn.microsoft.com/en-us/library/7c9c2y1w(v=vs.80).aspx.

Alternatively, you can allow network execution manually rather than using the Add .NET securityexception for ANSYS, Inc. products option of the Product Configuration Manager. The Add .NETsecurity exception for ANSYS, Inc. products option runs the Caspol utility, which is located underthe .NET Framework installation, in C:\Windows\Microsoft.NET\Framework64\v2.0.50727for a 64-bit machine. You can run this utility manually in a command prompt window to open fulltrust to files on the shared drive.

On a 64-bit machine, run the following command:

<os drive>\Windows\Microsoft.NET\Framework64\v2.0.50727\Caspol.exe -m -ag <CodeGroup> -url file://x:/* FullTrust






where x is the mapped drive or UNC path where the product is installed, and CodeGroup is theappropriate Caspol permissions level. We recommend a CodeGroup setting of 1.2. If that settingdoes not work or is not appropriate for your environment, please see the Caspol documentationavailable from Microsoft or contact your system administrator.

You must install Caspol as an administrative user. If running this from the command line on Windows7, Windows 8.1 or Windows 10, you must start the command prompt as Administrator, or thecommand will fail.

5. If you are sharing the Mechanical APDL product, edit the tlbrlist171.ans file, located in\v171\ansys\gui\en-us\toolbars on the Windows file server. The file should read as follows:

\\fileservermachine\ANSYS Inc\v171\ansys\gui\en-us\toolbars\ANSYSSTANDARD.TLB\\fileservermachine\ANSYS Inc\v171\ansys\gui\en-us\toolbars\ANSYSABBR.TLB\\fileservermachine\ANSYS Inc\v171\ansys\gui\en-us\toolbars\ANSYSGRAPHICAL.TLB

6. For all types of network installations, from each client Windows machine, you will need to run Product-Config.exe. If the Product Configuration Manager has been closed, please reopen it as described above.

7. Select Configure Products.

8. 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.

9. An informational message box appears as each product is configured.

All operations and error messages that are encountered while using the product configuration (orunconfiguration) option are written to the productConfig.txt file in the %TEMP% directory ofthe client machine. No log files are written to the machine that is hosting ProductConfig.exe.

Note

ProductConfig.exe can also be run in batch mode using the ‘-silent' flag, which maybe useful for automating configuration for multiple systems or across a MicrosoftWindows HPC cluster. For more information see Silent Mode Operations (p. 45).

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 (p. 53) for detailed instructions on running this utility, or selectHelp from the menu bar in the CAD Configuration Manager.

12. When the configuration is completed, you will see shortcuts to each product in Windows 7 under Start> All Programs > ANSYS 17.1 and in Windows 8.1 and 10 under All apps> ANSYS 17.1.

Unconfigure To unconfigure products that have previously been shared, use the following procedure:



1. From each client machine, in Windows 7, select Start > All Programs > ANSYS 17.1 > Utilities> ProductConfiguration 17.1, Windows 8.1, right-click the Start Screen> All apps> ANSYS 17.1> Product Con-figuration 17.1 and in Windows 10 (Start > All apps> ANSYS 17.1 > CAD Configuration Manager 17.1).

2. Select Unconfigure Products.

3. Select the products you want to unconfigure. Click Unconfigure. When unconfiguring products, be awarethat WB/Common should be unconfigured last, after all other products are unconfigured. If you are un-configuring some but not all products, do NOT unconfigure WB/Common, or your remaining productswill not run correctly.

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, youmust 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 willnot be able to proceed with the unconfigure. You will need to revise your selections before continuing.

• 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. The user interface billboard displays the status of each product as it is unconfigured. The shortcuts toeach product are now removed.

4.2.1.2. Specifying CAD Configurations

Selecting AutoCAD, Catia V5, Inventor, NX, Creo Parametric, Solid Edge, or SolidWorks from the productselection screen and clicking the Next arrow displays the CAD Configuration screen. This screen containsthe configuration properties for each CAD product that you have selected in an expanded "accordion"view.


If you have not yet installed the related CAD programs, or do not know the requested information, youcan choose to skip these configuration steps by selecting the Skip all and configure later using CADConfiguration Manager option located on the lower left-had portion of the screen. If you skip thesesteps, you will need to manually configure these CAD interfaces using the CAD Configuration Managerbefore you can successfully import models into Mechanical APDL, ANSYS Workbench, or ICEM CFD. Youcan access the CAD Configuration Manager in Windows 7 (Start > All Programs > ANSYS 17.1 >Utilities > CAD Configuration Manager 17.1), Windows 8.1 (Right-click the Start Screen> All apps>ANSYS 17.1 > CAD Configuration Manager 17.1) and in Windows 10 (Start > All apps> ANSYS 17.1> CAD Configuration Manager 17.1). See Configuring CAD Products (p. 53) for more information onusing the CAD Configuration Manager.

AutoCAD

• If you selected AutoCAD as one of your CAD products, you will have to choose which AutoCAD productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).




CATIA V5


Autodesk Inventor

• If you selected Inventor as one of your CAD products, you will have to choose which Inventor product toconfigure. You can choose the Reader (non-associative), Workbench Associative Interface (requires thatthe CAD product be installed), or skip and configure later (using the CAD Configuration Manager).

NX




Creo Parametric

1. If you selected Creo Parametric, you will have to choose which Creo Parametric product to configure. Youcan choose the Reader (non-associative), Workbench Associative Interface (requires that the CAD productbe installed), or skip and configure later (using the CAD Configuration Manager).

2. 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:\ProgramFiles\PTC\Creo 1.0\Parametric by default) for an existing Creo Parametric installation.

SolidWorks

• If you selected SolidWorks as one of your CAD products, you will have to choose which SolidWorks productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).

Solid Edge

• If you selected Solid Edge as one of your CAD products, you will have to choose which Solid Edge productto configure. You can choose the Reader (non-associative), Workbench Associative Interface (requiresthat the CAD product be installed), or skip and configure later (using the CAD Configuration Manager).




Because you will be using a network server, you must install and configure the ANSYS, Inc. LicenseManager on the server machine. The License Manager controls access to the ANSYS, Inc. products youhave purchased.

1. On the server machine, navigate to the directory where the installation packages reside. Right-click thesetup.exe file and select Run as administrator. The ANSYS, Inc. Installation Launcher appears. ClickInstall ANSYS License Manager.

2. You will see a warning stating that if the license manager is currently running, it will be shut down. Youmay safely ignore this message and click OK.

3. The license agreement appears. Read the agreement, and if you agree to the terms and conditions, clickI Agree. Click the Next arrow, located on the right side of the screen.

4. The directory where the license manager will be installed is shown in the Install Directory field. Acceptthe default directory and click the Next arrow.

Note




Click Next. The license manager installation begins.

After the License Manager installation has been completed, the Launch License ManagementCenter upon exiting option is included on the screen. The ANSYS License Management Centeris a browser-based user interface that centralizes many of the ANSYS product licensing administrativefunctions. If you do not want to launch the License Management Center, uncheck the Launch Li-cense Management Center upon exiting option.


8. Click Exit to close the ANSYS, Inc. Installation Launcher.

9. From the machine on which the products were installed, choose Start> Programs> ANSYS 17.1><product> to launch the ANSYS, Inc. products that you have installed.


If you are a new user who has not received a license file for your server or if you add or change a licenseserver machine, follow this procedure to register your license server information. See the ANSYS LicensingGuide for more information on selecting license servers (Selecting License Server Machines) and on




using the ANSYS License Management Center (License Server Administration Using ANSYS LicenseManagement Center).







After completing the installation process, please refer to Post-Installation Instructions (p. 37)



Chapter 5: Post-Installation Instructions

The following post-installation procedures apply to all ANSYS, Inc. products. Individual products mayhave additional post-installation procedures; please refer to the following sections for each product:

5.1. Post-Installation Procedures for Mechanical APDL and ANSYS Workbench Products5.2. Launching ANSYS, Inc. Products5.3. Running the ANS_ADMIN Utility for Mechanical APDL /ANSYS Workbench Products5.4. Product Localization

Note

If the installation program reported any errors, please review the installation error file (in-stall.err) located in the ANSYS Inc directory. Contact your ANSYS Support representative ifyou have any questions.

It may also be necessary to establish some system settings, including path names and environmentvariables. See your operating system documentation for specific instructions on setting paths and en-vironment 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 probablywill not need to reset this variable, unless you change the location of the licensing files.

To set environment variables:

Windows 7: Right-click Computer and choose Properties. Click Advanced System Settings, andclick Environment Variables. Click New. Type the name in the Variable Name field and the desiredsetting in the Variable Value field. Click OK on all dialog boxes.

Windows 8.1: From the Start Screen, right-click, select All apps and then click the File Explorericon. On the left side of the File Explorer, right-click Computer and choose Properties. Click Ad-vanced System Settings, and click Environment Variables. Click New. Type the name in theVariable Name field and the desired setting in the Variable Value field. Click OK on all dialog boxes.

Windows 10: Right-click Start and choose Control Panel. Click Advanced System Settings>Sys-tem>Advanced System Settings>Environment Variables.. Click New. Type the name in theVariable 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 environmentvariables, 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 environmentvariable to the desired drive letter (including the colon) and a HOMEPATH environment variable to thedesired path. For example:



HOMEDRIVE=C:HOMEPATH=\Users\Mine

3. Set the license manager to start automatically at boot time. For platform-specific instructions, see LicenseManager Automatic Startup Instructions in the ANSYS Licensing Guide.

4. Designate server(s) for license checkout and establish necessary user privileges (recommended but notrequired). For information on these tasks, see Post-Installation Instructions for the License Manager in theANSYS Licensing Guide.

5. Make a backup copy of the \ANSYS Inc directory.

6. Verify the product installation by selecting each product from the Start menu to verify that they eachstart and run correctly. You must be pointing to a valid license server machine before you can verify theinstallation.

7. If you chose not to set file associations during the installation, you may want to run the File Associationutility now to configure the ANSYS file types. Administrative privileges are required to run this utility

For Windows 7, select Start> All Programs> ANSYS 17.1> Utilities> File Association 17.1 andfor Windows 8.1 and 10, right-click the Start Screen> All apps> ANSYS 17.1> File Association17.1.

For network installations, run the File Association utility on each client computer.

You can also run the File Association utility in silent mode:

<install_dir>\v171\commonfiles\tools\<platform>\fileassoc.exe -silent

You can see help on the fileassoc.exe by issuing -help. File associations are as follows:

File ExtensionANSYS, Inc. Product

.db, .dbb, .grphMechanical APDL

.mres, .resANSYS CFD-Post

.cfx, .cvf, .def, .mdefANSYS CFX

.acpANSYS Composite PrepPost

.casANSYS Fluent

.prj, .tin, .unsANSYS ICEM CFD

.scdoc, .scjournalANSYS Space Claim DirectModeler

.ad, .agdb, .aqdb, .bgd, .cmdb, .dsdb, .engd, .fedb,

.mechdat, .meshdat, .wbdb, .wbpj, .wbpzANSYS Workbench

Quality Assurance Services: If you require verification of Mechanical APDL, the Mechanical Application,Fluent, or CFX, ANSYS, Inc. offers Quality Assurance services. If you are interested in this service, go tohttp://www.ansys.com/Support/Quality+Assurance/Quality+Services or call the ANSYS, Inc. CorporateQuality Group at (724) 746-3304.



http://www.ansys.com/Support/Quality+Assurance/Quality+Services

5.1. Post-Installation Procedures for Mechanical APDL and ANSYSWorkbench Products

The following post-installation procedures apply only to the Mechanical APDL and ANSYS Workbenchproducts. These are in addition to the post-installation procedures noted above for all products.

• Set the following environment variables based on the behavior you want. Set the environment variablesfollowing the conventions of your operating system. Not all of these are required for all integrated ANSYSWorkbench products (such as ANSYS Autodyn), but setting them correctly for ANSYS Workbench will inno way hinder the performance of the other products.

• The ANSYS171_DIR environment variable sets the location of the ANSYS directory hierarchy. The defaultvalue is c:\Program Files\ANSYS Inc\V171\ANSYS. You probably will not need to reset thisvariable, unless you change the location of the installed files.

• ANSYS171_PRODUCT - set this to the correct product variable to run Mechanical APDL to start withthe correct Mechanical APDL product without specifying the -p command modifier each time.

• ANS_CONSEC - set this to YES to disable Mechanical APDL dialog boxes and allow multiple jobs to runconsecutively without waiting for user input. Settings for ANS_CONSEC are:

GPF Dialog Box onError

Batch DialogBox

Value ofANS_CONSEC

YesNoNot defined/default

NoNoYES

YesYesNO

• ANSYS_LOCK - set to ON (default) to create file locks to prevent users from opening a new job withthe same name and in the same directory as the current job.

• ANSYS171_MAT161 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOS-ITE_MSC material (requires an LS-DYNA MAT_161 license).

• ANSYS171_MAT162 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOS-ITE_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 usedby the LS-DYNA executable. It is set to ANSYS during installation; changing this environment variablewill prevent ANSYS LS-DYNA from using your ANSYS licenses when running the executable.

Note

As of Release 17.0 the MechASAS package is no longer installed with the ANSYSMechanical Products. This package is required when using BEAMCHECK and FATJACKassessment types with Design Assessment. If you need the MechASAS package, pleasedownload it from the ANSYS Customer Portal.




5.1.1. Post-Installation Procedures for ANSYS Fluent

After installing the ANSYS Fluent software, you will need to reset the default values in the ANSYS Fluentlauncher as follows:

1. Verify that the FLUENT_INC environment variable is not set. From the Control Panel, select System andclick the Advanced tab. Click Environment Variables. Find and delete the FLUENT_INC variable.

2. In Windows 7, select Start> All Programs> ANSYS 17.1> Fluid Dynamics> Fluent 17.1. In Windows 8.1,right-click theStart Screen> All apps> ANSYS 17.1> FLUENT 17.1. In Windows 10, Start > All apps>ANSYS 17.1> FLUENT 17.1.

3. Click Default.

4. Click Yes when asked if you want to discard the LAUNCHER history.

5. Click Cancel if you do not want 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.2. Post-Installation Procedures for ANSYS Polyflow

Polyflow no longer requires the FLUENT_INC environmental variable. It should be deleted as is recom-mended for Fluent:

• From the Control Panel, select System and click the Advanced tab. Click Environment Variables. Find anddelete the FLUENT_INC variable.

5.1.3. Post-Installation Procedures for ICEM CFD

If you are running ICEM CFD over the network, you may not be able to access ICEM CFD Help usingthe Help menu. To access ICEM CFD Help, navigate to commonfiles\help\en-us in the installationdirectory on the server machine and copy the file icemcfd_help.chm to your local machine. Double-click the local copy to view the help.

5.1.4. Post-Installation Procedures for Other Products

BladeGen If you are running BladeGen on Windows 7, in order to access the BladeGen online help,you need to install WinHlp32.exe, which is available from Microsoft.

BladeEditor In order to use BladeEditor, you must set the Geometry license preference to ANSYSBladeModeler as follows:

1. In the ANSYS Workbench menu, select Tools> License Preferences.

2. In the License Preferences dialog box, click the Geometry tab.

3. If ANSYS BladeModeler is not the first license listed, then select it and click Move up as required to moveit to the top of the list. If ANSYS BladeModeler is not in the list, then you need to obtain an ANSYSBladeModeler license.

4. Select ANSYS DesignModeler in the list and set its value to 0 (which means “Don't Use”). This step preventsDesignModeler from using an ANSYS DesignModeler license when an ANSYS BladeModeler license is notavailable.



5. Click OK to close the dialog box.

FEMGV For ANSYS Aqwa customers, FEMGV is also available as a separate, standalone installation,available via media or the ANSYS Customer Download Center.

5.2. Launching ANSYS, Inc. Products

To launch ANSYS, Inc. products on Windows 7 platforms, choose the product from the ANSYS 17.1program group under the Start menu (Start> All Programs> ANSYS 17.1) and on Windows 8.1 and10, under All apps.

For Mechanical APDL, you can also use the launcher:

Windows 7: Start> All Programs> ANSYS 17.1> Mechanical APDL Product Launcher 17.1.

Windows 8.1: Start Screen> All apps> ANSYS 17.1> Mechanical APDL Product Launcher 17.1.

Windows 10: Start> All apps> ANSYS 17.1> Mechanical APDL Product Launcher 17.1.

5.3. Running the ANS_ADMIN Utility for Mechanical APDL /ANSYSWorkbench Products

You may need to run the ANS_ADMIN utility to relink Mechanical APDL if you use the customizationtools. For more information on individual options available with this utility, see the online help accessiblefrom Help buttons on the utility dialog boxes. You can launch ANS_ADMIN without administrativeprivileges, 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 corres-ponding product may not be installed.

To run the ANS_ADMIN utility from Windows 7, choose Start> All Programs> ANSYS 17.1> Utilities>ANS_ADMIN 17.1. To run the ANS_ADMIN utility from Windows 8.1 and 10, right-click the All apps>ANSYS 17.1> ANS_ADMIN 17.1.

5.4. Product Localization

Many ANSYS, Inc. products are available in multiple languages, including English, German, French, andJapanese. For those products that are localized, you are able to view the GUI and messages in thespecified language. See your specific product documentation for instructions on choosing a localizedversion of the product.

All products that are localized define the language via the languagesettings.txt file. In mostcases, you will not have to manually edit this file. If you do need to edit it manually, you can use oneof 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, inorder:

1. %appdata%\ANSYS\v171



Product Localization

2. <install_dir>\ANSYS Inc\v171\commonfiles\Language

ANSYS, Inc. licensing also looks for the languagesettings.txt in the licensing languages subdir-ectories in order to display the server ANSLIC_ADMIN utility and the ANSYS, Inc. Licensing Interconnectmessage and log files in a different language.

Some products are not fully localized but offer only the messages in a translated version. See the fol-lowing section for instructions on translated message file installation.

5.4.1. Translated Message File Installation for Mechanical APDL /ANSYSWorkbench Products

If your ANSYS, Inc. sales representative has supplied you with message files translated into your locallanguage, use the following procedure to install and access these files from within Mechanical APDL:

1. Create an appropriately named subdirectory to hold the message files. For example, if your local languageis French, create a directory in the following location:

<os drive>\Program Files\ANSYS Inc\V171\ANSYS\docu\fr

2. Copy the message files (msgcat.171,msgidx.171, and msgfnm.171) into the newly created subdir-ectory.

3. Access these message files by using the -l command line option. For example:

ansys171 -l fr

Or, when you are running Mechanical APDL from the Mechanical APDL launcher, choose the Lan-guage Selection option and then pick the desired language.

You must create a newly translated message file for each release of Mechanical APDL because errormessages may occur in a different order for each release.



Chapter 6: Installing the ANSYS, Inc. Product Help DocumentationOnly

Performing the ANSYS product help documentation installation places the entire help library onto acomputer. The Documentation Only installation is intended to be used for installing documentation ona central server without any products.

To perform the installation:


2. If you downloaded the installation files or if you are installing from a DVD/USB with autorun disabled,navigate to the location of the setup.exe file. Right-click the setup.exe file and select Run as administrator.


3. From the options along the left side of the launcher click Install ANSYS Documentation Only.


4. Read the agreement, and if you agree to the terms and conditions, click I Agree. Click Next.

5. The directory where you want to install the ANSYS, Inc. help documentation is shown in the Install Direct-ory field. You can install the products into any directory you want, but you must have write permissionsto the directory you choose. The default is C:\Program Files\ANSYS Inc. We recommend using the defaultdirectory.

Click Next.

6. A summary screen appears listing your help documentation installation. You will also see an estimate ofthe disk space required to install all of the selected components, and the disk space you have available.

Click Next to begin the installation.

7. When the help documentation installation has completed, click Exit. The product installation window re-appears. You can close this window at this time.

Note

Alternatively, you can run the document installation by running the SetupDocOnly.exeinstallation file. This file is located in the windows directory on USB drives.

The ANSYS help documentation can be installed silently by running the SetupDocOnly.exe installationfile with the –silent flag. For more information, see Silent Mode Operations (p. 45).




Chapter 7: Silent Mode Operations



ANSYS, Inc. requires that you have full administrative privileges when installing any software on MicrosoftWindows 7,Windows 8.1 or Windows 10. Non-administrative accounts do not usually have the permissionsrequired to access system areas that installation programs often need to modify. “Full administrativeprivileges” means that you are running as administrator with UAC turned off, or you are running asadministrator with UAC turned on and Run as Administrator selected. Because of changes to the UACfunctionality, it is necessary that you right-click and select Run as Administrator from the contextmenu when installing to Windows 8.1.

Windows 7, Windows 8.1 and Windows 10 use a feature called User Account Control (UAC) to controlprivileges 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.

7.1.1. Silent Mode Operations

ANSYS, Inc. supports silent mode operations, including installation, configuring/unconfiguring, anduninstalling.

You can specify the following product flags. These flags are all valid for a silent install. However, becauseof the way the products are packaged, not all of these flags may be valid for a silent configuration/un-configuration 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 beinstalled, configured, or uninstalled.

Product Flags

product_flagProduct



-autodynANSYS Autodyn

-lsdynaANSYS LS-DYNA


-cfxANSYS CFX


-fluentANSYS Fluent


-aqwaANSYS Aqwa



product_flagProduct


-aimANSYS AIM

-forteANSYS Forte

-chemkinproANSYS Chemkin



-mflANSYS Model Fuel Library (Encrypted)

Note: Installing any of the above products will install ANSYS Workbench.

-acpANSYS Composite PrepPost

-icepakANSYS Icepak

-aviewANSYS Viewer

-rsmRemote Solve Manager Standalone Services

-tcengANSYS TeamCenter Engineering

-catia4CATIA 4.x

-catia6CATIA V6

-parasolidParasolid

-acisACIS

-cocreateCreo Elements/Direct Modeling

-jtopenJTOpen

-solidworks_readerSolidWorks Reader

-solidworks_pluginSolidWorks Plugin

-catia5_readerCATIA 5 Reader

-catia5_pluginCATIA 5 Plugin

-adinventor_readerAutodesk Inventor Reader

-adinventor_pluginAutodesk Inventor Plugin

-proe_readerCreo Parametric Reader

-proe_pluginCreo Parametric Plugin

-ug_readerNX Reader

-ug_pluginNX Plugin

-acad_readerAutoCAD Reader

-acad_pluginAutoCAD Plugin

-solidedge_readerSolid Edge Reader

-solidedge_pluginSolid Edge Plugin

For more information on which products are included with each installation, see Applications Includedwith Each Product (p. 77).



7.1.1.1. Silent Product and License Manager Installation

Caution

A silent license manager installation could shut down the ANSYS, Inc. License Manager, af-fecting other users who are using that license server machine.

You can deploy an ANSYS, Inc. product installation in silent mode. The general form to run a silentproduct installation, including the client licensing, from the Start>Run menu is:

setup.exe -silent -product_flag

Note

In Windows 8.1 and 10 it is necessary to run silent commands from an administratorprompt. To access a Run as Administrator command prompt, click Start Screen> Allapps> right-click the Command Prompt Icon> select Run as Administrator.

The above form will install the products specified (see the list of product_flags above). Additionalcommand line arguments are available; please see the list below.

For example, to install TurboGrid and Icepak to the default installation directory, issue the followingcommand:

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 mustrun the setupLM.exe:

setupLM.exe -silent

The silent license manager installation is valid only for the default Licensing Configuration option "Runthe ANSYS Licensing Interconnect with FLEXlm." Please see Installing the ANSYS License Manager ofthe ANSYS Licensing Guide for more information.

If you are installing the license manager to a non-default installation directory, you can use the silentinstallation method, but only for the initial installation. To change the license manager installation dir-ectory for future installations, you will need to uninstall the license manager before reinstalling to adifferent directory.

You can use the following arguments when running a silent installation:


Specifies the directory to which the product is to be installed. For the installationdirectory, you must enclose the path in quotes if you have spaces in the pathname.

-install_dir"path"

If you want the product to install to the default location, you can omit the -in-stall_dir argument. The default location is <os drive>:\ProgramFiles\ANSYS Inc\.

Specifies one or more products to install. If you omit the -product_flagargument, all products will be installed. See the list of valid product_flagsabove.

-product_flag




You can specify an options file that lists the products you want to install. To doso, you must provide a full path to a file containing desired products. See SpecifyingProducts with an Options File (p. 49) for more details.

-productfile"path"

Disables automatic internet feeds to ANSYS, Inc. products.-disablerss

Allows the .NET binaries that are located under the \ANSYS Inc directory onthe shared machine to be run from the network. You must have administrative

-caspol

privileges to modify the security policy. Use this option when you specify a networklocation as the installation directory. To understand the implications of this securityexception for .NET, please contact your system administrator or see Microsoft’swebsite http://msdn.microsoft.com/en-us/library/7c9c2y1w(v=vs.80).aspx.

Displays a list of valid arguments for a silent installation.-help

Specifies the location of the license file to install. If the path is not specified or ifthe 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).

-licfilepath"path"

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

-setliclanglanguage

language subdirectory of the licensing directory (en-us, fr, de, etc.) as thelanguage value. This flag can be used during a GUI installation as well. Validonly when doing a license manager installation (setupLM.exe).

Specifies information to be used by the client for the license server. Valid only inconjunction with a silent installation (setup.exe). The format is:

Single license server:

-licserverinfo

LI port number:FLEXlm port number:hostname

Example:

2325:1055:abc

Three license servers:

LI port number:FLEXlm port number:hostname1,hostname2,host-name3

Example:

“2325:1055:abc,def,xyz”

The default values for the Licensing Interconnect and FlexNet 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 alsoneed to enclose the values in quotes (Windows only).

Example:

::abc

or

“::abc,def,xyz”




Information specified via -licserverinfo will be appended to existinginformation in the ansyslmd.ini file. To change information already inyour ansyslmd.ini file, you must use the ANSLIC_ADMIN utility.

By default, for the products that are being installed, all help documentation isincluded. The -nohelp argument removes all help from the installation.

-nohelp

Specifies a language to use for the products.-lang

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 anynecessary 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 andwrite 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 witha silent licensing installation, the licensing installation messages may not be written to the install_lic-config.log (for example, if the silent licensing installation aborts); in these cases, you may find errormessages in the .ansys_install_temp_licconfig_<user>_<index>.log file, located in%TEMP%.

For more information on the silent license manager installation, see Installing the ANSYS License Managerof the ANSYS 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 possibleproducts, with the products you do not want to install commented out, or it can contain only theproducts you want to install. An example options file is shown below. In the example, Creo Parametricand NX are commented out using the acceptable comment indicators. When using the options file, donot include the dash (-) before the product name.

mechapdlansyscustautodyncfdpostcfxturbogridfluentpolyflowicepak::proeREM 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_CMD171=C:\Program Files\PTC\Creo 1.0\Parametric\bin\para-metric1.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 requireadministrative permissions to install. If you want to install as a non-administrative user but requireprerequisites, you can install the prerequisites separately by running InstallPreReqs.exe fromthe top level directory as an administrator. You can also install the prerequisites silently using the fol-lowing command:

InstallPreReqs.exe -silent

7.1.1.2. Silent Product Configuration/Unconfiguration

You can also run the ProductConfig.exe via command line (i.e., silent mode) to configure or un-configure products.

From each client machine, run the ProductConfig.exe -silent with the following options:-config, -unconfig, -prereqs, -caspol, and -product_flag. These options are describedbelow.

• -config/-unconfig -- Use with the -silent option to indicate that products should be configured/un-configured.

• -prereqs -- Required to install the necessary prerequisites on your system. Prerequisites must be installedonce on each machine.

• -caspol -- Required to modify the necessary .NET security settings to allow the product to run across thenetwork. This option needs to be run once on each machine.

• -product_flag -- Use to specify which products should be configured; see the above list ofproduct_flags. If you do not specify one or more products, all products that have been installed will beconfigured.

• Use the -help option for a list of commands available for use with ProductConfig.exe.

An example command for silent configuration is:

"\\machineabc\Program Files\ANSYS Inc\v171\ProductConfig.exe" -silent -prereqs"\\machineabc\Program Files\ANSYS Inc\v171\ProductConfig.exe" -silent -caspol"\\machineabc\Program Files\ANSYS Inc\v171\ProductConfig.exe" -silent -config

All operations and error messages that are encountered while using the silent product configuration/un-configuration option are written to the productConfig.txt file in the %TEMP% directory of the clientmachine. No log files are written to the machine that is hosting ProductConfig.exe.

7.1.1.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 171-<number>.dvdfiles of each DVD are located in the same directory. You can then proceed with the silent installation as de-scribed earlier.

• Place all of the media in separate drives (any combination of virtual ISO mounts or hardware drives) so thatthey can be accessed simultaneously during the installation. Then run the silent installation as describedearlier, but include the additional -media_dir2 <path> option for each drive:



setup.exe -silent -product_flag -media_dir2 <path>

The installer uses the mount directory from which it was launched as the first media path; you needto specify only the location of the subsequent DVD(s) using the -media_dir2 option shown in theexample above.

7.1.1.4. Silent Uninstall

To run a silent uninstall, run the following from some location other than the \v171 directory:

C:\> <installation path>\v171\Uninstall.exe -silent

The silent uninstall will unconfigure and remove all products and remove the entire \v171 directory,including any user files or subdirectories that you have added to the \v171 directory.

Because of the way ANSYS, Inc. products are packaged, not all of the product_flags shown aboveare valid. To uninstall individual products, use the following product options in conjunction with the-silent argument:


-aqwaANSYS Aqwa

-cfxANSYS CFX


-fluentANSYS Fluent




-icepakANSYS Icepak

-rsmRemote Solve Manager StandaloneServices

For example, to uninstall only TurboGrid and Icepak, issue the following command:

C:\> <installation path>\v171\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 versionof CFD-Post, you must specify -cfdpost as well as all of the above products that you have installed.

Note that CFD-Post is also installed with CFX; however, you do not need to uninstall CFX to uninstallthe standalone version of CFD-Post, and uninstalling the standalone version of CFD-Post will not removethe CFD-Post capability from CFX.





Chapter 8: Configuring CAD Products

The connection, geometry interface, and other CAD functionality for all supported CAD products is in-cluded with the ANSYS release media. Select the CAD systems you want to install during the installationprocess. If you choose not to install CAD systems during the installation, you can install them at a laterdate.

To run the connection or geometry interface functionality, you need to:

1. Ensure that the CAD product is correctly installed and licensed.

2. Ensure that you have the correct ANSYS, Inc. license(s).

3. Run the installation setup.

For complete information about the files you can import and the platforms supported by the connectioncapability, see the ANSYS Connection User's Guide. For more information about geometry interface in-formation in ANSYS Workbench, see the topics Attach to Active CAD Geometry and Import ExternalGeometry File in the ANSYS DesignModeler help.

Caution

Be sure to install Mechanical APDL and the connection functionality from the same release.If you attempt to run the latest connection functionality on a machine that is running anearlier release of Mechanical APDL, or vice versa, the connection may fail.

The connection for Creo Parametric requires you to run Mechanical APDL, Creo Parametric and theconnection for Creo Parametric on the same machine. The connection for NX requires you to runMechanical 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.

8.1. Using the CAD Configuration Manager

The CAD Configuration Manager allows you to configure geometry interfaces for Mechanical APDLand ANSYS Workbench. 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 thisutility.

The CAD Configuration Manager is organized into several tabs:

• CAD Selection

• Creo Parametric

• NX

• Teamcenter (active on Windows only)



• CAD Configuration

This document describes how to use the CAD Configuration Manager as a wizard, beginning with theCAD Selection tab and using the Next button to progress through the configuration process. You canalso manually select each tab to progress through the configuration process; both methods work thesame. However, the applicable tabs will not be enabled until you choose the associated product on theCAD Selection tab.

1. From Windows 7, click Start > All Programs > ANSYS 17.1 > Utilities > CAD Configuration Manager17.1. From Windows 8.1, right-click the Start Screen> All apps> ANSYS 17.1> CAD ConfigurationManager 17.1. From Windows 10, right-click the Start > All apps> ANSYS 17.1> CAD ConfigurationManager 17.1.

2. On the CAD Selection tab, choose the CAD products that you need to configure. Click Next.

3. If you did not select any CAD interfaces the necessary prerequisites will be registered, enabling Geometry(DesignModeler). You must run the CAD Configuration Manager as an administrative user for someCAD registrations to take place. Select the CAD Configuration tab and click Configure Selected CADInterfaces to register the prerequisites.

4. If you selected Creo Parametric as one of your CAD products, you will have to choose which Creo Para-metric product to configure:

a. The Reader option specifies the non-associative source and doesn't require a Creo Parametric install-ation. (This reader does not support CAD associativity or parameters.)

b. The Workbench Associative Plug-In option requires Creo Parametric to be installed. When youchoose this option, the Creo Parametric tab opens.

i. Enter or browse to the Creo Parametric installation location (for example,C:\ProgramFiles\PTC\Creo 3.0\F000\Parametric).

ii. Enter or browse to the Creo Parametric start command (for example,C:\ProgramFiles\PTC\Creo 3.0\F000\Parametric\bin\parametric.bat). Include the com-plete path if entering the command manually.

iii. Click Next.

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 CreoParametric installations are present on the system, the plug-in should only be configuredfor a single installation of Creo Parametric; otherwise unconfiguring the plug-in willcause 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. The Reader option specifies the non-associative source and doesn't require an NX installation. (Thisreader does not support CAD associativity or parameters.)



b. The Workbench Associative Plug-In option requires NX to be installed. When you choose this option,the NX tab opens.

i. Enter or browse to the NX installation location (for example,C:\ProgramFiles\Siemens\NX 10.0).

ii. Enter or browse to the NX custom directory file path (for example,C:\Documents andSettings\UserName\Application Data\ANSYS\v171\Unigraphics).

Note

If you are installing as an administrator, this file path will be defined in youradministrator's user space by default and non-administrative users will not beable to run. Use this setting to specify a new location for the custom directoryfile path that is accessible by all users.

iii. Click Next.

6. If you selected Inventor, AutoCAD, SolidWorks or SolidEdge as one of your CAD products, you will haveto choose which product to configure:

a. The Reader option specifies the non-associative source and doesn't require an Inventor, AutoCAD,SolidWorks or SolidEdge installation. (This reader does not support CAD associativity or parameters.)

b. The Workbench Associative Plug-In option requires Inventor, AutoCAD, SolidWorks or SolidEdgeto be installed.

7. If SpaceClaim Engineer is installed, you will have to choose to configure the ANSYS Workbench Plug-In for either SpaceClaim Direct Modeler or SpaceClaim Engineer. Otherwise you are limited to config-uring the SpaceClaim Direct Modeler Plug-In.

8. If you selected Teamcenter as one of your CAD products, the Teamcenter tab opens:

a. Enter or browse to the Teamcenter installation location (for example,C:\SIEMENS\Teamcen-ter2011).

b. Discriminator is a client-defined identifier for a session. For example, ANSYSWBPlugInTC.

c. Choose Next.

9. If you selected Catia V5 as one of your CAD products, you will have the option to choose which CATIA V5product to configure.

a. Select the Reader option to configure the CATIA V5 standalone reader that does not require an in-stallation of the CATIA V5 CAD program. (This reader does not support CAD associativity or parameters.)

b. Select the CADNexus/CAPRI CAE Gateway option to configure the CATIA V5 associative reader thatdoes 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).




c. Click Next.

10. The CAD Configuration tab opens.

a. Click the Configure Selected CAD Interfaces button.

b. When the configuration for all products is complete, log entries appear, listing those products thatwere successfully configured and those that were not. Address any errors and reconfigure.

c. For more details, click the Display Configuration Log File button to see a detailed log file.

11. When all of your CAD products have been successfully configured, click Exit.

You can review the CAD Configuration Manager log file, CADConfigurationMgr.log, in \ANSYSInc.

Important

If you change your source from reader to associative plug-in or vice-versa (Creo Parametric,NX, SolidWorks, Autodesk Inventor, SolidEdge, AutoCAD or Catia V5), you must first uncon-figure the existing source and then configure using the new source.

8.1.1. Unconfiguring

If you need to unconfigure any of your CAD products, follow the steps above, but choose UnconfigureSelected CAD Interfaces on the CAD Configuration tab.

8.1.2. Running the CAD Configuration Manager in Batch Mode

You can configure ANSYS Geometry Interfaces by supplying the CAD Configuration Manager witharguments specific to the CAD sources you want to make available. The following table contains a listof supported arguments.

The command to run the CAD Configuration Manager in batch mode on Windows is:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" -arguments


Results in any specified CAD sources beingunconfigured. When this flag is absent, the CAD

NoneUNCONFIGURE_SPECIFIED

Configuration Manager will attempt to configureall designated CAD sources.

Results in all CAD sources being disabled alongwith prerequisite libraries.

NoneUNCONFIGURE

Specify Creo Parametric source as either theassociative plug-in or the reader (Spatial, no Creo

NoneEither: PE_CONFIG_WB orPE_CONFIG_WBSPATIAL

Parametric install required). When the plug-in isspecified, additional arguments PROELOADPOINTand PROE_START_CMD are required.




Not required with unconfigure operation.Full path to CreoParametric

PROELOADPOINT

installation (quotesrequired onWindows).

Not required with unconfigure operation.Full path tocommand used to

PROE_START_CMD

launch CreoParametric (quotesrequired onWindows)

Specify NX source as either the associative plug-inor the reader (Spatial, no NX install required).

NoneEither: UG_CONFIG_WB orUG_CONFIG_WBSPATIAL

When the plug-in is specified, the argumentUGII_BASE_DIR must also be specified.

This should agree with environment variableUGII_BASE_DIR. Not required with unconfigureoperation.

Full path to NXinstallation

UGII_BASE_DIR

Specify Catia V5 source as either the Reader(Spatial, no Catia install required) or CAPRI(CADNexus install required).

NoneEither: CATIA_SPATIAL orCATIA_CAPRI

Configure/unconfigure Creo Elements/DirectModeling.

NoneOSDM_CONFIG

Specify Inventor source as either the associativeplug-in or the reader (Spatial, no Inventor installrequired).

NoneEither: INVENTOR_CONFIG orINVENTOR_CONFIG_WBSPATIAL

Specify SolidWorks source as either the associativeplug-in or the reader (Spatial, no SolidWorksinstall required).

NoneEither: SOLIDWORKS_CONFIGor SW_CONFIG_WBSPATIAL

Specify Solid Edge source as either the associativeplug-in or the reader (Spatial, no Solid Edge installrequired).

NoneEither: SOLIDEDGE_CONFIG orSOLIDEDGE_CONFIG_SPATIAL

Specify AutoCAD source as either the plug-in orthe reader (Spatial, no AutoCAD install required).

NoneEither: ACAD_CONFIG orACAD_CONFIG_SPATIAL

Configure/unconfigure Teamcenter; forconfiguration requiresTC_ROOT flag.

NoneTEAMCENTER_CONFIG

Not required with unconfiguration operation.Path to Teamcenterinstallation.

TC_ROOT

Configure/unconfigure JT.NoneJTOPEN_CONFIG

Configure/unconfigure CATIA v4.NoneCATIA4_CONFIG

Configure/unconfigure CATIA v6.NoneCATIA6_CONFIG





Not required with unconfigure operation.An identifier for theANSYS TeamcenterPlug-In

TC_DISCRIMINATOR

Note

All arguments require a dash (-) before them in order to be properly recognized by the CADConfiguration Manager. Arguments' values should not have a dash preceding them.

For example, you can configure Creo Parametric and SolidWorks Geometry Interfaces to ANSYS Workbenchfrom the command line by using the following:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" -SW_CONFIG -PE_CONFIG_WB -PROELOADPOINT "C:\Program Files\PTC\Creo 2.0\Parametric" -PROE_START_CMD "C:\Program Files\PTC\Creo 2.0\Parametric\bin\parametric.bat"

where installpath is the same as the value of environment variable %AWP_ROOT171%, platformis the value of environment variable %ANSYS_SYSDIR%, and Creo Parametric is installed to C:\ProgramFiles\PTC\Creo 2.0\Parametric.

To unconfigure the same CAD Interfaces, the command would be:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" -unconfigure_specified -SW_CONFIG -PE_CONFIG_WB

Although the argument order does not matter, an argument value must immediately follow its argument.

8.1.3. Network Considerations

When Workbench is installed to a network location (made available from a mapped network drive), anyconfiguration actions will make the selected geometry interfaces available/unavailable only to the userwho is currently logged in. To make changes that apply to all users, the configure/unconfigure actionmust be run as an administrator logged into the system hosting the Workbench installation. Configur-ation actions performed as an administrator on this server machine will impact all users on all machinesreferencing that install, except for users who have overridden the server configuration by configuringfor themselves.

Prior to running the CAD Configuration Manager from a network location, the product configurationtool must be executed. This process will result in the client system being configured to match thegeometry interface selections on the server. Products requiring additional information such as interfacesto Creo Parametric, NX and Teamcenter may fail to configure. This can be remedied either by manuallyrunning CAD Configuration Manager following Product Configuration, or by setting appropriate envir-onment variables prior to execution of Product Configuration such as UGII_CUSTOM_DIRECTORY_FILE,PROE_START_CMD171 and TC_ROOT. TC_ROOT can be set to the path of your Teamcenter installation.Further details regarding environment variables pertaining to Creo Parameteric and NX are offered inthe interface specific help sections below. For more information on using the Product Configurationmanager, please see Network Server and Product Configuration (p. 31).

For loading associative geometry interfaces into their respective CAD environments, when the Workbenchinstallation is referenced from a network location:



• A local administrator’s configuration changes will set up associative CAD interfaces to load into the CADenvironment of all local users, when that scope is selected (applicable to AutoCAD, Inventor, SolidWorks,Solid Edge, Creo Elements/Direct and NX).

• The associative geometry interface for Creo Parametric will load into the CAD environment of all users whenthe CAD installation is writable for that administrative user. Otherwise, it will load only into the CAD envir-onment of the administrator who is currently logged in, and each additional user must be configured indi-vidually.

CAD Readers for JT, Creo Parametric, Inventor, NX, CatiaV5, CatiaV6, AutoCAD, Solid Edge and SolidWorksmay not fully unconfigure on a client of a network installation, even when this action is attempted bya client's administrator. An administrative user on the server must execute an unconfigure action, usingCAD Configuration Manager, in order for these interfaces to be fully deactivated on the client.

8.1.4. Uninstalling

Warning

Do not proceed with an uninstall for CAD-specific unconfigure actions or you will leave someANSYS Workbench products unusable.

8.1.5. Creo Parametric Configuration

Running the CAD Configuration Manager for Creo Parametric performs the following steps to activatethe Creo Parametric plug-in:

• Sets the environment variable PROE_START_CMD171 to the file used to launch Creo Parametric (for exampleC:\Program Files\PTC\Creo 3.0\F000\Parametric\bin\parametric.bat).

• For administrative installations, adds the ANSYS 17.1 entry to the config.pro file located in<creo_path>\text. An example for Creo Parametric would be:

PROTKDAT C:\Program Files\PTC\Creo 3.0\F000\Common Files\text

An example for Wildfire 5.0 would be:

PROTKDAT C:\Program Files\proeWildfire 5.0\text

• Updates the WBPlugInPE.dat file referenced in the config.pro file, so that it contains information forloading the WorkBench Plug-In and the ANSYS Connection product.

• Registers the Plug-In file WBPlugInCreo3COM.dll (Creo Parametric 3.0),WBPlugInPECOM.dll (CreoParametric 2.0) or DSPlugInPEWF5COM.dll (Wildfire 5.0) referenced in the WBPlugInPE.dat file.

• When Workbench is installed on a network location and the local administrator has write permissions to<creo_path>\text, a version-specific WBPlugInPE171.dat file will be created and placed in thatfolder. However, when <creo_path>\text is unwriteable, both the config.pro and the WBPlugIn-PE171.dat will be placed in either %HOME% or %HOMEDRIVE%%HOMEPATH%.

If you do not have write access to your ANSYS Workbench installation, you may encounter the followingerror when attempting to import Creo Parametric models without an active CAD session:

No write access, please choose another startup directory for trail filecreation.




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 WB171PluginProWFEXEC_FILE E:\Program Files\ANSYS Inc\V171\AISOL\CADIntegration\ProE\ winx64\WBPlugInPECOM.dllTEXT_DIR E:\Program Files\ANSYS Inc\V171\AISOL\CADIntegration\ProE\ ProEPages\Language\<locale>STARTUP dlldelay_start FALSEallow_stop TRUEunicode_encoding FALSEREVISION ProEWildfireEND

NAME ac4pro171dllexec_path E:\Program Files\ANSYS Inc\V171\ANSYS\ac4\bin\pro\winx64\ac4pro.exetext_path E:\Program Files\ANSYS Inc\V171\ANSYS\ac4\data\pro\textSTARTUP dlldelay_start FALSEallow_stop TRUEunicode_encoding FALSEunicode_encoding FALSErevision 24.0end

Note

When configuring the plug-in to run with Wildfire 5.0, the reference to WBPlugInPECOM.dllwill instead be DSPlugInPEWF5COM.dll and ac4pro.exe should be ac4pro_wf5.exe.

<locale> should be "en-us" for English, "de" for German, "fr" for French, or "ja" for Japanese.

Do not delete any of these lines. If you modify this file, do NOT enter a carriage return after the ENDline. The file may be customized with other information. If these lines are deleted, or if the WBPlugIn-PE.dat file is not present in any of the directories in the search path, Creo Parametric will not loadANSYS-related CAD interfaces. You should typically never have to edit these files for path informationcontained within them. Paths are determined by environment variable settings, which are set automat-ically during installation. If you encounter problems when attempting to run Creo Parametric, use theCAD Configuration Manager to reconfigure rather than attempting to edit files directly.

Following an update of an existing Creo Parametric 2.0 or 3.0 installation to a different maintenancerelease (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 CADConfiguration Manager (p. 53). This situation does not apply to Pro/ENGINEER Wildfire 5.0, or CreoElements/Pro 5.0.

In order for CAD Configuration Manager to successfully perform configuration of the Creo ParametricAssociative Geometry Interface it is required that the Windows Operating System's decimal separatorbe the same symbol when running configuration as it was when the original Creo Parametric installationwas performed.

8.1.5.1. Configuring the Connection for Creo Parametric

All Creo Parametric users must have copies of the WBPlugInPE.dat file and the config.anscon.171(connection for Creo Parametric) files. The config.anscon.171 file is placed in the Program



Files\ANSYS Inc\V171\ansys\ac4\data\winx64 directory. config.anscon.171 must becopied into the user's working directory at the time Creo Parametric is started. The WBPlugInPE.datfile is placed in the Program Files\ANSYS Inc\V171\AISOL\CADIntegration\%AN-SYS_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 con-fig.anscon.171 file into your working directory and restart Creo Parametric.

8.1.5.1.1. The WBPlugInPE.dat File and config.pro File

Creo Parametric uses the WBPlugInPE.dat file to locate related executables such as the connectionfor Creo Parametric.

Mechanical APDL/ANSYS Workbench also requires a config.pro file.

• 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 inthe Creo Parametric installation log, which can be found in <path-to-creo-paramet-ric>\bin\pim\xml\creobase.xml. In the cases that the crebase.xml file is missing, the ship codecan be determined by looking in the Windows Registry using regedit. For Creo 2.0, that value is located inSOFTWARE\Wow6432Node\PTC\Creo Parametric\2.0\<DateCode>\Shipcode. For Creo 3.0 the value is locatedin HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PTC\PTC Creo Parametric\3.0\<DateCode>. <Date-code> is a integer reflecting the date of the Creo build.

The config.pro file contains a PROTKDAT line that points to the WBPlugInPE.dat file. This file isgenerated either during the product install or by running the CAD Configuration Manager to configurethe Mechanical APDL /ANSYS Workbench products for Creo Parametric.

The <proe_platform> variable is the name that Creo Parametric gives to its platform directories:

WBPlugInPECOM

Creo ParametricPlatform

ANSYS Platform<platform>

HardwarePlatform

<proe_plat-form>

x86e_win64winx64Win 7 and Win8.1 x64

8.1.5.1.2. The config.pro File

A typical config.pro file might look like the following example. This example has an entry for ANSYSWorkbench. You may have other Creo Parametric specific customizations.

PROTKDAT E:\Program Files\ANSYS Inc\V171\AISOL\CADIntegration\$ANSYS_PROEWF_VER\ ProEPages\config\WBPlugInPE.dat




8.1.5.1.3. The config.anscon.171 File

Users who launch Mechanical APDL from Creo Parametric will need the information from the con-fig.anscon.171 file. This file is installed for all users in the \ac4\data\winx64 subdirectory. Youtypically do not need to edit this file. Here is a sample config.anscon.171 file:

ANSYS_CMD %AWP_ROOT171%\ANSYS\bin\%ANSYS_SYSDIR%\ansys171.exeANSYS_GRAPHIC_DEVICE WIN32ANSYS_SOLVER Sparse**ANSYS_SELECTED_LAYERS 1-256**ANSYS_GEOMETRY_TYPE Solids Only**ANSYS_NEUTRAL_FORMAT Yes**ANSYS_PRODUCT_NAME ANE3FL

**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 aboutthe config.anscon.171 file.

8.1.5.2. Creo Parametric Environment Variables

Most environment variables are set during product installation. In general, you will not need to resetthese variables. Check the manuals for the individual CAD products for information about environmentvariables and their settings.

PROE_START_CMD171Specifies the name of the .bat file which launches Creo Parametric on the system. The path to the execut-able should be already set if the Creo Parametric installation path has been defined for the PATH environ-ment setting.

PROE_START_CMD171 Default = C:\Program Files\PTC\Creo 2.0\Paramet-ric\bin\parametric.bat

8.1.6. NX Configuration

Running the CAD Configuration Manager for NX performs the following steps to activate the NX plug-in:

• If not already existing, sets the environment variable UGII_CUSTOM_DIRECTORY_FILE to %APPDATA%\AN-SYS\v171\Unigraphics\custom_dirs.dat.

• If not already present, adds an entry to the custom_dirs.dat file specifying the location of the Plug-In,e.g.,C:\Program Files\ANSYS Inc\V171\AISOL\CADIntegration\UnigraphicsNX\winx64.

• Registers the Plug-In file (DSPlugInUGCOM.dll). For the previous example, these files would be locatedin C:\Program Files\ANSYS Inc\V171\AISOL\CADIntegration\Unigraphic-sNX\winx64\startup.

8.1.6.1. Configuring the Connection for NX

User-Defined Environment Variables You will need to have the following environment variable setif you will be running the connection for NX product from inside NX.

UGII_VENDOR_DIR for Mechanical APDLThis environment variable is not set during the installation process and can only be set in a user's start-upfile 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 insideNX. This environment variable tells NX where to find the ANSYS program, for example:C:\ProgramFiles\ANSYS Inc\V171\ANSYS\ac4\bin\ug50\winx64.

UGII_BASE_DIR and UGII_ROOT_DIRThe environment variables UGII_BASE_DIR and UGII_ROOT_DIR must be defined for proper operationof NX and the ANSYS Workbench Plug-In to NX. These environment variables are typically created by theNX installer; however, in rare cases, you may have to create/update these two variables. 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 variablemust be set to the install path of the NX version to be launched, prior to starting that version ofthe CAD. Otherwise errors will be encountered during CAD startup and the plug-in will not load.For example, if switching from NX 8.5 to run NX 9.0, you must update UGII_BASE_DIR to the NX9.0 path before starting NX 9.0. Similarly, the UGII_ROOT_DIR environment variable must be set tothe ugii subdirectory in the install path of the NX version to be launched.

8.1.6.2. Configuring for Teamcenter

Running the CAD Configuration Manager for Teamcenter performs the following step to activate theTeamcenter plug-in:

• When Teamcenter Unified is detected, the environment variable TC_ROOT is set to the Teamcenter Unifiedinstallation path.

8.2. Configuring CADNexus/CAPRI CAE Gateway for CATIA V5

The CADNexus/CAPRI CAE Gateway for CATIA V5 product is available for ANSYS Workbench. The ANSYSWorkbench-specific portions are included in the installation. However, to run this product, you mustcomplete the configuration as follows:

1. Install ANSYS Workbench according to the instructions in this guide.

2. Install CATIA V5 and LUM licensing (requires a CATIAV5 license key MD2, HD2 or ME2).

3. From the ANSYS, Inc. Customer Portal, download the CADNexus/CAPRI CAE Gateway for CATIA V5 foryour platform to a temporary folder. (Do not download to a folder containing blank spaces in the foldername, e.g., Program Files). Follow the download procedures described in Downloading the InstallationFiles (p. 16).

4. Extract the contents of the zip file using your standard zip utility.

5. Install CADNexus/CAPRI CAE Gateway for CATIA V5 using the appropriate exe for your platform.

6. Follow the instructions on the CAPRI installation screens to complete the installation. When specifyingthe 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.



Configuring CADNexus/CAPRI CAE Gateway for CATIA V5

7. Run the CAD Configuration Manager and select the Catia V5: CADNexus/CAPRI CAE Gateway optionto complete the configuration as described in Using the CAD Configuration Manager (p. 53).

Note

Using the CAD Configuration Manager to set up the CADNexus/CAPRI CAE Gatewaydoes not require administrative rights, although installing that product (step 5) requiresthese rights. However, if you want to reconfigure to use the ANSYS Workbench Readerfor Catia V5, administrative rights are required.

If you want to revert to the standard CATIA V5 interface, run the CAD Configuration Manager andselect the Catia V5: Standard Interface option to complete the configuration as described in Usingthe CAD Configuration Manager (p. 53).

You cannot run the standard CATIA V5 interface simultaneously with the CADNexus/CAPRI CAE Gatewayfor CATIA V5 interface.

8.3. Configuring AutoCAD

Running the CAD Configuration Manager for AutoCAD performs the following steps to active the plug-in:

1. Creates the folders %PROGRAMDATA%\AnsysWB.bundle and %PROGRAMDATA%\Autodesk\Application-Plugins\AnsysWB.bundle\Contents\v171\Winx64\AutoCAD

2. Copies the following folders from the Workbench installation into the bundle's AutoCAD sub-folders:

• All files within <ANSYS 16.0 Install Path>\aisol\CADIntegration\DWG\winx64 are copied to %PROGRAM-DATA%\ApplicationPlugins\AnsysWB.bundle\Contents\v171\winx64\AutoCAD\2013

• All files within <ANSYS 16.0 Install Path>\aisol\CADIntegration\DWG\images are copied to %PROGRAM-DATA%\Autodesk\ApplicationPlugins\AnsysWB.bundle\Contents\v171\winx64\AutoCAD\Resources

• All folders within <ANSYS 16.0 Install Path>aisol\CADIntegration\DWG\Language are copied to %PRO-GRAMDATA%\Autodesk\ApplicationPlugins\AnsysWB.bundle\Contents\v171\winx64\AutoCAD\Re-sources\Language

3. Finally a %PROGRAMDATA%\Autodesk\ApplicationPlugins\AnsysWB.bundle\PackageContents.XML file iscreated with the following contents:

<?xml version="1.0" encoding="utf-8"?>

<ApplicationPackage ProductCode="{6C6B872A-2ECF-4272-B7B7-1CA69B1EAD08}" HelpFile="./Contents/v171/

Winx64/AutoCAD/Resources/cadAutoCAD.html" Icon="./Contents/v171/Winx64/AutoCAD/Resources/ansys70.bmp"

Description="ANSYS Workbench Geometry Interface 17.1" AppVersion="17.1" Name="AnsysWB171

" ProductType="Application" SchemaVersion="1.0" AutodeskProduct="AutoCAD" FriendlyVersion="15.0

" SupportedLocales="Enu" OnlineDocumentation="www.ansys.com

" Author="ANSYS, Inc." UpgradeCode="{12D6EF98-CEE6-431E-B699-DE9DE4F32B7E}">

<CompanyDetails Name="ANSYS, Inc." Email=" " Url="www.ansys.com" Phone=" " />

<RuntimeRequirements SeriesMax="R19.1" SeriesMin="R19.0" Platform="AutoCAD" OS="Win64" />





<Components Description="64bit Component">

<RuntimeRequirements SeriesMax="R19.1" SeriesMin="R19.0" Platform="AutoCAD" OS="Win64" />

<ComponentEntry AppName="WB150PlugInDWG" ModuleNameWin64="./Contents/v171/Winx64/AutoCAD/2013/

WB150PlugInDWG.arx" AppDescription="Windows 64bit support" LoadOnCommandInvocation="True"

LoadOnRequest="True">

<Commands GroupName="ANSYS_Workbench_Geometry_Interface">

<Command Local="WB150STARTWB" Global="WB150STARTWB" />

<Command Local="WB150STARTASIM" Global="WB150STARTASIM" />

<Command Local="WB150HELP" Global="WB150HELP" />

<Command Local="WB150ABOUT" Global="WB150ABOUT" />

</Commands>

</ComponentEntry>

<ComponentEntry AppName="AnsysWB150" ModuleName="./Contents/v171/Winx64/

AutoCAD/Resources/Language/

en-us/Workbench150.cuix" />

</Components>

</ApplicationPackage>



Configuring AutoCAD


Chapter 9: Uninstalling the Software

Use this process to uninstall any ANSYS, Inc. product that was installed using the Unified Installationprocess.

Note to CFX Users The provided uninstall tool cannot uninstall MPI services. If you have CFX productsinstalled that you are uninstalling, you must stop the MPI services before continuing with the uninstall:

1. As an administrator, go to the Run window and type Services.msc.

2. Search for "IBM Platform MPI Remote Launch" and if found, click Stop.

3. Search for "Intel(R) MPI Library Process Manager" and if found, click Stop.

4. Continue with the uninstallation procedure, below.

Uninstall Procedure for All Users All users should use the following procedure to uninstall ANSYS,Inc. products.

1. Close down all applications that are currently running.

2. From Windows 7, select Start > All Programs > ANSYS 17.1 > Uninstall 17.1. From Windows 8.1, right-click the Start Screen> All apps> ANSYS 17.1> Uninstall 17.1. From Windows 10, right-click the Start> All apps> ANSYS 17.1> Uninstall 17.1. You must uninstall with the same or higher privileges thanwere used to install the product, and we strongly recommend uninstalling as the same user who installedthe product originally.

3. Select the product(s) to be uninstalled and unconfigured and click Uninstall Selected Item(s). Not allproducts and product components may be listed individually.

4. You will be asked to save all data and close all Windows applications before continuing. Click OK.

5. You will be asked if you are sure you want to uninstall the selected products. Click Yes.

6. A message appears indicating that the uninstallation is complete. Click OK.

Note

After all the desired products are uninstalled, you are presented with a messagestating that any files or directories that were not recognized by our uninstall programremain. These remaining files typically include such things as .udf files, user custom-ized documentation, and various routines. If these files are no longer required,please remove them manually.

CFD-Post CFD-Post can be installed as a standalone product; however, as a standalone product, it isalso automatically installed with Fluent, Polyflow, and Icepak. To uninstall CFD-Post, you must uninstallall of the above products that you have installed.



• If you choose to uninstall standalone CFD-Post without uninstalling the other products, the uninstall programwill not uninstall CFD-Post.

• If you choose to uninstall all of the other products that include standalone CFD-Post but you do not selectCFD-Post, then CFD-Post will not be removed.

Individual product directories may not be removed if they contain components that are shared withother 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) fromall of the Windows platforms.

This procedure removes the specified ANSYS, Inc. program from your system but will not remove theANSYS licensing components. Follow the steps in Uninstalling Licensing Components (p. 68) to uninstallthe licensing components.

9.1. Uninstalling Licensing Components

Before proceeding with the following steps to remove the ANSYS licensing components from yoursystem, make certain that there are no ANSYS, Inc. products on this machine or any other machines onthe network that rely on these ANSYS licensing components.

License Servers Follow these steps on a license server machine:

1. Stop the ANSYS, Inc. License Manager via the ANSYS License Management Center.

2. 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. Delete the Licensing subdirectory.

4. Remove the ANSYS, Inc. License Manager folder from the Start menu.

5. Remove the ANSYSLIC_DIR and the ANSYSLIC_SYSDIR environment variables, if set.

Clients Follow these steps on client machines:

1. Delete the Licensing subdirectory.

2. Remove the ANSYS 17.1> ANSYS Client Licensing folder from the Start menu or from the Apps screen.


Uninstalling the Software


10.1. Installation Troubleshooting

This section lists problems and error messages that you may encounter while installing and/or runningANSYS, Inc. products. After each situation description or error message is the user action required tocorrect the problem.

You can also find answers to commonly-asked questions on our customer portal. After you log in tothe customer portal, select Knowledge Resources> Solutions.

For information on licensing-related errors, see the Troubleshooting section of the ANSYS LicensingGuide.

10.1.1. Using ANSLIC_ADMIN to Gather Diagnostic Information




You can also use the AnsysInstallationDiagnostics.exe, in the \v171\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 temporarydirectory, depending on directory permissions. The log files are intended to help ANSYS, Inc. technicalsupport personnel expedite any technical issues. It would be useful to have the files ready to providebefore contacting Technical Support.

10.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 messageswhen removing product components. Run the uninstall as an administrative user, and close all applica-tions before running the uninstall.

10.1.3. Uninstall on a Windows 7, Windows 8.1 or Windows 10 System GivesCompatibility Error Message

If you uninstall an ANSYS, Inc. product on a Windows 7, Windows 8.1 or Windows 10 system using theANSYS, Inc. Uninstall utility, you may see the following error message:



This program might not have installed correctly.

If this program didn't install correctly, try reinstalling using settings that are compatible with thisversion of Windows.

This message is caused by the Windows Program Compatibility Assistant and can safely be ignored.Click Cancel and continue with the uninstall.

10.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 Con-vention (UNC) path to open the file on a network shared folder, typical with a Network Configurationinstall. This is a known issue with security update 896358, security update 840315, or Microsoft WindowsServer 2003 Service Pack 1 (SP1). Please go to http://support.microsoft.com/kb/896358 and http://sup-port.microsoft.com/kb/896054 for more information on this problem and Microsoft's recommended fix.

If you are running ICEM CFD over the network and you have applied this security update, you may notbe able to access ICEM CFD Help using the Help menu. To access ICEM CFD Help, navigate to common-files\help\en-us in the installation directory on the server machine and copy the file icem-cfd_help.chm to your local machine. Double-click the local copy to view the help.

10.1.5. Products Crash with an Application Error

On Windows Server 2008 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 selectthe Data Execution Prevention tab.

If DEP is set, you will need to add ANSYS to the list of exceptions. For more information on DEP andhow to change the settings, see http://support.microsoft.com/kb/875351.

10.1.6. Product Installation Does Not Create Start Menu Item for ANSYS andCAD Plugins Do Not Work

On a Windows 7, Windows 8.1 or Windows 10 system, if you install ANSYS, Inc. products but do notsee a Start Menu/Apps item and your CAD plugins do not work, the TEMP environment variable maybe pointing to an inaccessible location. For example, it may point to a location such as %USERPRO-FILE%\Local Settings\Temp. As a result, the product installation could end without configuringthe product correctly. You should ensure that the TEMP variable points to a valid location, such as%USERPROFILE%\AppData\Local\Temp.

10.1.7. Product Installation Displays Security Warning Dialogs or Silent ProductInstallation Hangs on a Network Install

If you see a security warning dialog box during a GUI installation/product configuration, or if your in-stallation hangs during a silent installation, you may need to modify your security settings. Set themachine you are installing from as a trusted site and allow launching of unsafe applications so that theprerequisite installation can complete. Then re-run the installation. Contact your system administratoror 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:


Troubleshooting

http://support.microsoft.com/kb/896358




1. Run PreReqCheck.exe from the top level directory.

2. Install any missing prerequisites by running InstallPreReqs.exe from the top level directory as anadministrator.

3. When the prerequisites have finished installing, run the installation as you normally would (GUI or silently).

10.1.8. System-related Error Messages

***Error, ANSYS171_DIR environment variable is not set. This is a fatal error – exiting.

This message indicates that the ANSYS171_DIR environment variable was not set where necessaryfor 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 machineas a trusted site. On a Windows 7, Windows 8.1 or Windows 10 machine, in the Control Panel, selectNetwork and Internet, select Internet Options, and select Security. Click on Trusted Sites andclick Sites. Add the machine as file://servername.

10.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 putquotes around your server specification as shown in the following example:

C:\Users\>C:\Windows\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -m -ag 1.2 -url file://"\\machineabc\ANSYS Inc\*" FullTrust

10.2. Installation Troubleshooting - Mechanical APDL and ANSYS Work-bench Products

The items listed below apply only to the Mechanical APDL and/or ANSYS Workbench products.

10.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 surethe hostnames in the ansyslmd.ini file and in the ANSYSLMD_LICENSE_FILE and the ANSYSLI_SERV-ERS 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 numberis correct.

10.2.2. Display Problems on Windows

This situation applies only to Windows systems running Mechanical APDL.

Windows includes a function called Aero that may cause Mechanical APDL graphing or plotting problemsin 3-D mode on some systems. If this problem occurs, disable the Windows Aero theme in Windows 7when running Mechanical APDL. If you are using Windows 8.1, please follow the steps below to correctthis issue.

Disabling Aero in Windows 8.1



Installation Troubleshooting - Mechanical APDL and ANSYS Workbench Products

1. Open the Windows Control Panel.

2. Click Ease of Access.

3. Click Optimize Visual Display.

The Make the computer easier to see window opens. Please note that you can access this windowin a number of ways.

4. Enable the Turn off all unnecessary animations (when possible) option.

5. Click Ok.

6. Close the Windows Control Panel.

10.2.3. ANS_ADMIN Error Messages

Grayed out options

If certain options are grayed out, your account may not have the necessary system administratorprivileges necessary to run those options.

10.2.4. Mechanical APDL Product Launcher Error Messages

Some of the more common error messages follow. See the ANSYS Licensing Guide for licensing-relatedlauncher messages.

***Cannot create required <profile> file. Therefore, cannot write to profile information duringthis 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, thisdirectory is C:\Documents and Settings\<user name>\Application Data\AN-SYS\v171\launcher on Windows or ~/.ansys/v171/launcher/ on UNIX.

***No ANSYS product installations found.

Verify your Mechanical APDL product installation. If the desired product was not installed, install it.

10.2.5. Distributed Mechanical APDL IBM Platform MPI Error Messages

You may encounter the following message when setting up IBM Platform MPI or running DistributedANSYS using IBM Platform MPI.

Error executing Mechanical APDL. Refer to System-related Error Messages in the Mechanical APDLonline help. If this was a Distributed Mechanical APDL job, verify that your MPI software is installedcorrectly, 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 completedthis item according to the IBM Platform MPI installation readme instructions.

You may also see this error if ANSYS Inc\v171\ansys\bin\<winx64> is not in your PATH.

If you need more detailed debugging information, use the following:


Troubleshooting

1. Open a Command Prompt window and set the following:

SET ANS_SEE_RUN=TRUESET ANS_CMD_NODIAG=TRUE

2. Run the following command line:ansys171 -b -dis -i myinput.inp -o myoutput.out.

10.2.6. ANSYS Workbench Products Troubleshooting

This section lists problems and error messages that you may encounter while installing and/or runningANSYS Workbench. After each situation description or error message is the user action required tocorrect the problem. Always try the suggested user action before contacting your technical supportrepresentative.

Problem Situations

CAD System Plug-In Menus Do Not Appear for NX or Creo Parametric ANSYS Workbench onWindows platforms will append its information to an existing customization file for NX and/or CreoParametric. If no customization file exists, ANSYS Workbench will create a file. For NX, ANSYS Workbenchlooks for the custom_dirs.dat file in the directory specified via the UGII_CUSTOM_DIRECTORY_FILEenvironment 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 In-terface, ANSYS Workbench will also append its information to the config.pro file located in the CreoParametric 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 informationto the file. In this case, you will need to revise the permissions on the file and manually add the appro-priate ANSYS Workbench-specific information in order for the ANSYS menu to appear in NX or CreoParametric.

Script Errors When Running ANSYS Workbench If you encounter script errors such as "Error: Unableto 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=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en for more information on downloading and installingMSXML.

ANSYS Workbench Error Messages

***Unable to connect to Solver Manager.

Another application might be using the Solver Manager port (10002 by default). Try changing theport number by editing the Ansys.SolverManager.exe.config file located in the installationdirectory at \AISOL\Bin\<platform>.

If you are getting the "Unable to connect to Solver Manager" error message or are having difficultylaunching 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\sys-tem32\drivers\etc\hosts file.

10.3. Installation Troubleshooting - ANSYS CFX

The items listed below apply only to the ANSYS CFX products.



Installation Troubleshooting - ANSYS CFX

http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en

10.3.1. TurboGrid Mouse Behavior Problems

Depending on the graphics card and driver version, you may experience problems with the accuracyof mouse clicks in the 3D Viewer. For example, you may try to insert a control point at a given locationby 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.

10.4. Contacting Technical Support

Technical Support for ANSYS, Inc. products is provided either by ANSYS, Inc. directly or by one of ourcertified ANSYS Support Providers. Please check with the ANSYS Support Coordinator (ASC) at yourcompany to determine who provides support for your company, or go to www.ansys.com and selectContacts> Contacts and Locations.

If your support is provided by ANSYS, Inc. directly, Technical Support can be accessed quickly and effi-ciently from the ANSYS Customer Portal, which is available from the ANSYS Website (www.ansys.com)under Support > Customer Portal. The direct URL is: support.ansys.com.

One of the many useful features of the Customer Portal is the Knowledge Resources Search, which canbe found on the Home page of the Customer Portal. To use this feature, enter relevant text (errormessage, etc.) in the Knowledge Resources Search box and click the magnifying glass icon. TheseKnowledge Resources provide solutions and guidance on how to resolve installation and licensing issuesquickly.

NORTH AMERICA

All ANSYS Products except Esterel, Apache and Reaction Design products


Toll-Free Telephone: 1.800.711.7199 (Please have your Customer or Contact ID ready.)


GERMANY

ANSYS Mechanical Products

Telephone: +49 (0) 8092 7005-55 (CADFEM)


All ANSYS Products


National Toll-Free Telephone: (Please have your Customer or Contact ID ready.)

German language: 0800 181 8499

English language: 0800 181 1565

Austria: 0800 297 835

Switzerland: 0800 564 318

International Telephone: (Please have your Customer or Contact ID ready.)

German language: +49 6151 152 9981

English language: +49 6151 152 9982



Troubleshooting






UNITED KINGDOM

All ANSYS Products


Telephone: Please have your Customer or Contact ID ready.

UK: 0800 048 0462

Republic of Ireland: 1800 065 6642

Outside UK: +44 1235 420130



JAPAN

CFX and Mechanical Products

Telephone: +81-3-5324-7305

Email:

Mechanical: [email protected]

Fluent: [email protected];

CFX: [email protected];

Polyflow: [email protected];

Icepak

Telephone: +81-3-5324-7444


Licensing and Installation


INDIA

All ANSYS Products


Telephone: +91 1 800 209 3475 (toll free) or +91 20 6654 3000 (toll) (Please have your Customer orContact ID ready.)

FRANCE

All ANSYS Products


Toll-Free Telephone: +33 (0) 800 919 225 Toll Number: +33 (0) 170 489 087 (Please have your Customeror Contact ID ready.)



BELGIUM

All ANSYS Products









Toll-Free Telephone: (0) 800 777 83 Toll Number: +32 2 620 0152 (Please have your Customer or ContactID ready.)



SWEDEN

All ANSYS Products


Telephone: +46 (0) 10 516 49 00



SPAIN and PORTUGAL

All ANSYS Products


Spain: Toll-Free Telephone: 900 933 407 Toll Number: +34 9178 78350 (Please have your Customer orContact ID ready.)

Portugal: Toll-Free Telephone: 800 880 513 (Portugal)

Email: [email protected], [email protected]


ITALY

All ANSYS Products


Toll-Free Telephone: 800 789 531 Toll Number: +39 02 00621386 (Please have your Customer or ContactID ready.)



TAIWAN, REPUBLIC OF CHINA

Telephone: 866 22725 5828

K0REA

Telephone: 82-2-3441-5000

CHINA

Toll-Free Telephone: 400 819 8999 Toll Number: +86 10 82861715


Troubleshooting




Chapter 11: Applications Included with Each Product

The following table displays which ANSYS, Inc. applications are included with each of the product in-stallation options.

What is Included?SilentInstallOption


ANSYS, Inc. Products

ANSYS Structural Mechanics

Workbench [1], Mechanical APDL2-mechapdlANSYS Mechanical Products

Workbench [1], Mechanical APDLUser-Programmable Feature


ANSYS Explicit Dynamics

Workbench [1], Autodyn-autodynANSYS Autodyn

Workbench [1], ANSYS AIM-lsdynaANSYS LS-DYNA

Workbench [1], ANSYS AIM, ANSYS Polyflow(without ANSYS CFD-Post)

-aimANSYS AIM

ANSYS Fluid Dynamics

Workbench [1], CFX, CFD-Post-cfxANSYS CFX (includes ANSYSCFD-Post)

Workbench [1], Fluent, CFD-Post-fluentANSYS Fluent (includes ANSYSCFD-Post)

Workbench [1], TurboGrid-turbogridANSYS TurboGrid

Workbench [1], CFD-Post, Polyflow-polyflowANSYS Polyflow (includesANSYS CFD-Post)

Workbench [1], CFD-Post-cfdpostANSYS CFD-Post only

Workbench [1], Forte-forteANSYS Forte

Workbench [1], Chemkin-chemkinproANSYS Chemkin

Workbench [1], Chemkin, Energico-energicoANSYS Energico

Workbench [1], Chemkin, Reaction Workbench-reactionwbANSYS Reaction Workbench

Workbench [1], Chemkin, Model Fuel Library(Encrypted)

-mflANSYS Model Fuel Library(Encrypted)

Workbench [1], ICEM CFD-icemcfdANSYS ICEM CFD

ANSYS Offshore

Workbench [1], Aqwa-aqwaANSYS Aqwa

ANSYS Additional Tools

ACP Only-acpANSYS Composite PrepPost



What is Included?SilentInstallOption


CFD-Post, Icepak-icepakANSYS Icepak (includes ANSYSCFD-Post)

Remote Solve Manager-rsmANSYS Remote Solve ManagerStand Alone Services

ANSYS Viewer-aviewANSYS Viewer

ANSYS PDM Interface

TeamCenter Integration for NX-tcentTeamCenter Engineering

ANSYS Geometry Interfaces

Geometry Interface for AutoCAD-acadAutoCAD

Geometry Interface for ACIS-acisACIS

Geometry Interface for Catia, Version 4-catia4Catia, Version 4



Geometry Interface for Creo Elements/DirectModeling

-cocreateCreo Elements/Direct Modeling

Geometry Interface for Inventor-adinventorInventor

Geometry Interface for JTOpen-jtopenJTOpen

Geometry Interface for NX-ug_reader,-ug_plugin

NX

Geometry Interface for Parasolid-parasolidParasolid

Geometry Interface for Creo Parametric (formerlyPro/ENGINEER)

-proe_reader,-proe_plugin

Creo Parametric (formerlyPro/ENGINEER)

Geometry Interface for Solid Edge-solidedgeSolid Edge

Geometry Interface for SolidWorks-solidworksSolidWorks

1. Workbench includes the Workbench Framework, DesignModeler, DesignXplorer, SpaceClaim DirectModeler, SpaceClaim Catia V5 Interface, ECAD and Remote Solve Manager.

2. As of Release 17.0 the MechASAS package is no longer installed with the ANSYS Mechanical Products.This package is required when using BEAMCHECK and FATJACK assessment types with Design Assessment.If you need the MechASAS package, please download it from the ANSYS Customer Portal.


Applications Included with Each Product

Configuring High Performance Computing


2600 ANSYS Drive ANSYS, Inc. iscertified to ISO9001:2008.

Canonsburg, PA [email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494


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




Disclaimer Notice








Table of Contents

Configuring Distributed ANSYS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11. Setting up Distributed ANSYS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1. Prerequisites for Running Distributed ANSYS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1. MPI Software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2. Installing the Software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2. Setting Up the Cluster Environment for Distributed ANSYS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.1. Optional Setup Tasks .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.2. Using the mpitest Program ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.3. Interconnect Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2. Running a Distributed Job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Configuring ANSYS CFX Parallel ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1. ANSYS CFX Linux Parallel Setup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1. Setting Up Remote Access on Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1.1. Testing Remote Access .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1.2. Set Up of ssh .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1.3. Global Set Up of rsh .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1.4. Individual User Set Up for rsh .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2. hostinfo.ccl File ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3. Using Intel MPI (Message Passing Interface Library) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.1. Environment Variables .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.2. Network Fabrics Selection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.4. Using IBM Platform MPI (Message Passing Interface Library) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.1. Environment Variables .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.2. Interconnect Selection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.5. Using Cray MPI (Message Passing Interface Library) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.5.1. Cray MPI Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2. ANSYS CFX Windows Parallel Setup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1. Parallel Setup for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.1. hostinfo.ccl file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.1.1. Adding Hosts for Parallel Processing with the cfx5parhosts Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.2. Setting Up Intel MPI for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.1. Setting Up Intel MPI Authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2.1.1. Password Authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.1.2. Delegated Authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.1.3. Impersonated Authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2.2. Enabling Intel MPI Parallel Through a Windows Firewall ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3. Setting Up IBM Platform MPI for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.3.1. Enabling IBM Platform MPI Parallel Through a Windows Firewall ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.4. Setting up and Running Microsoft Windows HPC 2008 or HPC 2012 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

IBM Platform MPI with High (>4096) Process Count .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27




List of Tables

1. Products with Limited HPC Functionality .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. Platforms and MPI Software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23. LS-DYNA MPP MPI Support on Windows and Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3




Configuring Distributed ANSYS

This section explains how to configure your network/cluster to run Distributed ANSYS. It is importantthat you follow these steps in order to run successfully in a distributed environment.

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 HPCfunctionality, as noted in the following table.

Table 1: Products with Limited HPC Functionality

VT AcceleratorCapability

SMP CapabilityDistributedANSYS

Capability

Product

Yes4 processorsdefault limit

YesANSYS AcademicTeaching Products

NoNoNoANSYS LS-DYNA

No2 processorsmax

NoANSYS DesignSpace

1. Setting up Distributed ANSYS

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

The following topics are available:1.1. Prerequisites for Running Distributed ANSYS1.2. Setting Up the Cluster 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 beneeded to run a distributed solution 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 a distributedsolution.

If you are running across multiple machines (for example, a cluster), your system must meet these ad-ditional requirements to run a distributed solution.

• Homogeneous network: All machines in the cluster must be the same type, OS level, chip set, and intercon-nects.



• You must be able to remotely log in to all machines, and all machines in the cluster must have identicaldirectory structures (including the ANSYS 17.1 installation, MPI installation, and working directories). Do notchange or rename directories after you've launched ANSYS. For more information on files that are writtenand their location, see Controlling Files that Distributed ANSYS Writes in the Parallel Processing Guide.

• All machines in the cluster must have ANSYS 17.1 installed, or must have an NFS mount to the ANSYS 17.1installation. If not installed on a shared file system, ANSYS 17.1 must be installed in the same directory pathon all systems.

• All machines must have the same version of MPI software installed and running. The table below shows theMPI software and version level supported for each platform.

1.1.1. MPI Software

The MPI software supported by Distributed ANSYS depends on the platform (see the table below).

The files needed to run Distributed ANSYS using IBM Platform MPI or Intel MPI are included on the in-stallation media and are installed automatically when you install ANSYS 17.1. Therefore, when runningon a single machine (for example, a laptop, a workstation, or a single compute node of a cluster) onWindows or Linux, or when running on a Linux cluster, no additional software is needed. However,when running on multiple Windows machines (a cluster), you must install the MPI software separately(see Installing the Software later in this section).

Distributed ANSYS runs on the following platforms:

Intel Xeon EM64T 64-bit Linux (Platform MPI, Intel MPI)AMD Opteron 64-bit Linux (Platform MPI, Intel MPI)Windows 64-bit (Platform MPI, MS MPI, Intel MPI)Windows HPC Server 2008 / 2012 x64 (Microsoft HPC Pack (MS MPI))

Table 2: Platforms and MPI Software

More InformationMPI SoftwarePlatform

Linux, Intel XeonEM64T and AMDOpteron 64-bit

Platform MPI: http://www-03.ibm.com/systems/technicalcomputing/

PlatformMPI9.1.3.1

platformcomputing/products/mpi/index.html

Intel MPI5.0.3

Intel MPI: http://software.intel.com/en-us/articles/intel-mpi-library-documentation/

Windows 64-bitWindows 7 x64 /

Platform MPI: http://www-03.ibm.com/systems/

PlatformMPI9.1.3.1Windows 8.1 x64

/ Windows 10 x64technicalcomputing/platformcomputing/products/mpi/index.html

Intel MPI5.0.3

Intel MPI: http://software.intel.com/en-us/articles/intel-mpi-library-documentation/

http://www.microsoft.com/hpc/Microsoft HPCPack (MS MPI)

Windows HPC Server2008 / 2012 x64



http://www-03.ibm.com/systems/technicalcomputing/platformcomputing/products/mpi/index.html





http://software.intel.com/en-us/articles/intel-mpi-library-documentation/











http://www.microsoft.com/hpc/

ANSYS LS-DYNA If you are running ANSYS LS-DYNA, you can use LS-DYNA's parallel processing (MPPor SMP) capabilities. Use the launcher or the command line method as described in Activating DistributedANSYS in the Parallel Processing Guide to run LS-DYNA MPP. For Windows and Linux systems, please seethe following table for LS-DYNA MPP MPI support. For more information on using in ANSYS LS-DYNAgeneral, 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

64-bitLinux

64-bitWindows

MPI version for DYNA MPP

XXPlatform MPI

n/aXMS MPI

1.1.2. Installing the Software

To run Distributed ANSYS on a cluster, you must install ANSYS 17.1 on all machines in the cluster, orhave an NFS mount to the ANSYS 17.1 installation. Install ANSYS 17.1 following the instructions in theANSYS, Inc. Installation Guide for your platform. Be sure to complete the installation, including all requiredpost-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 installationprogram will start. A Platform MPI installation README file will open simultaneously. Follow the instruc-tions in the README file as you complete the Platform MPI installation.

The instructions for installing Platform MPI are also found in the installation directory in the followingREADME files:

Program Files\ANSYS Inc\V171\commonfiles\MPI\Platform\9.1.3.1\Windows\IN-STALL_PLATFORM-MPI_README.mht

or

Program Files\ANSYS Inc\V171\commonfiles\MPI\Platform\9.1.3.1\Windows\IN-STALL_PLATFORM-MPI_README.docx

Installing Intel MPI on Windows

You can install Intel MPI from the Installation launcher by choosing Install MPI for ANSYS, Inc. ParallelProcessing. On the following screen, choose to install Intel MPI. The Intel MPI installation program willstart. An Intel MPI installation README file will open simultaneously. Follow the instructions in theREADME file as you complete the Intel MPI installation.

The instructions for installing Intel MPI are also found in the installation directory in the followingREADME files:

Program Files\ANSYS Inc\V171\commonfiles\MPI\Intel\5.0.3\Windows\INSTALL_IN-TEL-MPI_README.mht

or



Setting up Distributed ANSYS

Program Files\ANSYS Inc\V171\commonfiles\MPI\Intel\5.0.3\Windows\INSTALL_IN-TEL-MPI_README.docx

Microsoft HPC Pack (Windows HPC Server 2008 / 2012)

You must complete certain post-installation steps before running Distributed ANSYS on a MicrosoftHPC Server 2008 or 2012 system. The post-installation instructions provided below assume that MicrosoftHPC Server 2008 / 2012 and Microsoft HPC Pack (which includes MS MPI) are already installed on yoursystem. The post-installation instructions can be found in the following README files:

Program Files\ANSYS Inc\V171\commonfiles\MPI\WindowsHPC\README.mht

or

Program Files\ANSYS Inc\V171\commonfiles\MPI\WindowsHPC\README.docx

Microsoft HPC Pack examples are also located in Program Files\ANSYS Inc\V171\common-files\MPI\WindowsHPC. Jobs are submitted to the Microsoft HPC Job Manager either from thecommand 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 17.1 and the correctversion of MPI installed, you need to configure your distributed environment using the following pro-cedure.

1. Obtain the machine name for each machine on the cluster.

Windows 7:From the Start menu, click on Computer, then click on System properties. The full computer nameis listed. Note the name of each machine (not including the domain).

Windows 8.1:From the All apps screen, open the Control Panel. Click System and Security> System. The fullcomputer name is listed. Note the name of each machine (not including the domain).

Windows 10:From the Start menu, pick Settings >System >About. The full computer name is listed under PCName. 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 thisname 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 jqdgolinux2 jqd



Change/verify .rhosts file permissions on all machines by issuing:

chmod 600 .rhosts

Verify communication between machines via rsh or ssh (e.g., rsh golinux2 ls). You shouldnot be prompted for a password. If you are, check the .rhosts permissions and machine namesfor 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 toconfigure the hosts171.ans file. You can use the ANS_ADMIN utility to configure this file. You canmanually modify the file later, but we strongly recommend that you use ANS_ADMIN to create this fileinitially to ensure that you establish the correct format.

Windows 7:Start >All Programs >ANSYS 17.1 >Utilities >ANS_ADMIN 17.1

Windows 8.1:All apps >ANSYS 17.1 > ANS_ADMIN 17.1

Windows 10:Start >All apps >ANSYS 17.1 > ANS_ADMIN 17.1

Linux:/ansys_inc/v171/ansys/bin/ans_admin171

The ANS_ADMIN interface is similar for Windows and Linux:

• Choose ANSYS/Workbench Configure Cluster to configure the hosts171.ans file.

• Under Select file to configure, choose the hosts171.ans file to be configured and chooseConfigure for Distributed ANSYS. Click OK.

• Enter the system name (from Step 1) in the Machine hostname field and click Add. On the nextdialog box, enter the system type in the Machine type drop-down, and the number of cores inthe Max number of jobs/processors field. Click Add. Repeat this step for each machine in thecluster.

• When you are finished adding machines, click Close then File > Exit.

The hosts171.ans file should be located in your current working directory, your home directory,or the apdl directory. All three locations are equally valid; the location should be chosen basedon user preference.

4. Windows only: Verify that all required environment variables are properly set. If you followed the post-installation instructions described above for Microsoft HPC Pack (Windows HPC Server 2008 / 2012), thesevariable should be set automatically.

On the head node, where ANSYS 17.1 is installed, check these variables:

ANSYS171_DIR=C:\Program Files\ANSYS Inc\v171\ansys

ANSYSLIC_DIR=C:\Program Files\ANSYS Inc\Shared Files\Licensing

where C:\Program Files\ANSYS Inc is the location of the product install and C:\ProgramFiles\ANSYS Inc\Shared Files\Licensing is the location of the licensing install. If yourinstallation locations are different than these, specify those paths instead.




On Windows systems, you must use the Universal Naming Convention (UNC) for all ANSYS, Inc.environment variables on the compute nodes for Distributed ANSYS to work correctly.

On the compute nodes, check these variables:

ANSYS171_DIR=\\head_node_machine_name\ANSYS Inc\v171\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-DYNAexecutable to use ANSYS, Inc. licensing.

Since the LS-DYNA run will use ANSYS, Inc. licensing for LS-DYNA, you do not need to setLSTC_LICENSE_SERVER.

5. Windows only: Share out the ANSYS Inc directory on the head node with full permissions so that thecompute 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 runcorrectly, but they may be useful for achieving the most usability and efficiency, depending on yoursystem 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 ofthe client (default is 15 seconds).

• ANSYS_NETWORK_COMM - This is the time to wait, in seconds, before timing out while communicatingwith the client machine (default is 5 seconds).

• ANS_SEE_RUN_COMMAND - Set this environment variable to 1 to display the actual mpirun commandissued 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 specifya full path to a remote shell. For example, setting MPI_REMSH = /usr/bin/ssh will use ssh insteadof the default remote shell (rsh). Note that selecting the Use Secure Shell instead of Remote Shelloption 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 lineoption will override the environment variable setting as well.

• MPI_IC_ORDER - Set this environment variable to specify the order in which the interconnects on thesystem are to be used. The interconnects will be tried in the order listed from left to right. If an inter-connect is listed in uppercase, no interconnects listed after that one will be tried. If MPI_IC_ORDER isnot set, the fastest interconnect available on the system is used. See the Platform MPI documentationfor more details.

• MPIRUN_OPTIONS - Set this environment variable to -prot to display a grid of interconnects amongthe 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 environmentvariables 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 mpiruncommand 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 upcorrectly. The mpitest program should start without errors. If it does not, check your paths, .rhostsfile, and permissions; correct any errors, and rerun.

When running the mpitest program, you must use an even number of nodes.

On Linux:

For Intel MPI (default), issue the following command:

mpitest171 -machines machine1:2

For Platform MPI, issue the following command:

mpitest171 -mpi pcmpi -machines machine1:2

You can use any of the same command line arguments (such as -machines) with the mpitest programas you can with Distributed ANSYS.

On Windows:

Issue the following command to run a local test on Windows using Intel MPI:

ansys171 -np 2 -mpitest

Use the following procedure to run a distributed test on Windows using Intel MPI:

1. Create a file named machines in your local/home directory. Open the machines file in an editor.

2. Add your master and slave machines in your cluster. For example, in this cluster of two machines, themaster machine is gowindows1. List the machine name separately for each core on that machine. Forexample, if gowindows1 has four cores and gowindows2 has two, the machines file would look likethis:

gowindows1gowindows1gowindows1gowindows1





gowindows2gowindows2

3. From a command prompt, navigate to your working directory. Run the following:

ansys171 -mpifile machines -mpitest

1.2.3. Interconnect Configuration

Low-end hardware, such as slow interconnects, will reduce the speed improvements you see in a dis-tributed analysis. For optimal performance, we typically recommend that you use an interconnect witha communication speed of 1000 megabytes/second or higher.

Distributed ANSYS supports the following interconnects. Not all interconnects are available on all plat-forms; see http://www.ansys.com/Support/Platform+Support for a current list of supported interconnects.Other interconnects may work but have not been tested.

• InfiniBand (recommended)

• 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 accommodatethe higher speeds.

Hardware for specific types of interconnects is generally incompatible with other proprietary interconnecttypes (except Ethernet and GiGE).

Systems can have a network of several different types of interconnects. Each interconnect must be as-signed a unique hostname and IP address.

On Windows x64 systems, use the Network Wizard in the Compute Cluster Administrator to configureyour interconnects. See the Compute Cluster Pack documentation for specific details on setting up theinterconnects. You may need to ensure that Windows Firewall is disabled for Distributed ANSYS to workcorrectly.

2. Running a Distributed Job

For information on running Distributed ANSYS after you have your environment configured, see theParallel Processing Guide.

For more information on using Distributed ANSYS, 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 inthis chapter to ensure that users can execute ANSYS CFX jobs in parallel. Parallel communicationmethods are available that use MPI (Message Passing Interface). Platform-specific versions of MPI areavailable in some instances.

The ANSYS CFX-Solver parallel option is supported on all platforms that support the CFX-Solver.

1. ANSYS CFX Linux 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 orsecure 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 Accesson 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 Linux

Each system that will be used as a slave node must be configured to allow access via remote shellcommands from the master node. This can be done globally for all users or on a per-user basis.

Often, networks where ssh, rsh or rlogin are used frequently will already be configured to allow remoteaccess to all users. If this is the case, nothing more needs to be done.

The CFX5RSH environment variable is used to select the remote shell protocol. By default, CFX5RSH=sshis set. If you want to use rsh, then set CFX5RSH=rsh either in the environment or in the cfx5rc file(see Resources Set in cfx5rc Files in the CFX Introduction).

In either case, ssh or rsh, the remote machine must not prompt for a password when you run remotecommands.

1.1.1. Testing Remote Access

You can test remote access using ssh using the command:

ssh unixhost echo working

You can test remote access using rsh for a Linux slave node using the command:

rsh unixhost echo working



1.1.2. Set Up of ssh

If you use ssh for remote access, consult your system documentation on how to set up ssh betweenmachines so that it does not require the user to enter a password.

1.1.3. Global Set Up of rsh

This method, which is used to allow remote access for all users, depends on whether NIS is used tomaintain netgroups, as well as common password and group databases. If this is not the case, then youshould log in to each slave node as root and create a file called /etc/hosts.equiv containing aline:

<master>

where <master> is the hostname of the master node. See your system documentation for more in-formation 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 theroot user on the NIS master server, and a line such as the one below added to /etc/hosts.equivon 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 descrip-tion of how to configure NIS is beyond the scope of this manual. Please see your system documentationfor more information about NIS.

1.1.4. Individual User Set Up for rsh

Individual users can create a file called .rhosts in their home directory on each slave containing aline:

<master> <user>

where <master> is the hostname of the master and <user> is their username on the master. Thisfile should be made readable only by the user, for example, by running:

chmod 600 ~/.rhosts

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 madereadable by all users of the software. This file is a database containing information about the availablehosts and where ANSYS CFX has been installed on each of them. The file is used by the ANSYS CFX-Solver when constructing a parallel run.

This file is written using the CFX Command Language. It defines a set of HOST DEFINITION objects, onefor each available node. For example:

SIMULATION CONTROL: EXECUTION CONTROL: PARALLEL HOST LIBRARY: HOST DEFINITION: kangaroo Installation Root = /ansys_inc/v%v/CFX END 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 ENDEND

Note

If you manually create your hostinfo.ccl file, you must ensure that the SIMULATIONCONTROL...END wrapper is present.

None of the values for each host are mandatory, and the following empty host definition is perfectlyvalid:

HOST DEFINITION: parakeetEND

Host names are limited to the set of valid CCL object names. In particular, they must not contain fullstops (.) 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 con-taining the installation host. You can add hosts to the hostinfo.ccl file using the cfx5parhostsutility, or by modifying the file using a text editor. Individual users may also create their own versionsof 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 shouldpoint to the <CFXROOT> directory in which ANSYS CFX is installed. On mixed architectures, you mayfind it useful to supply the Number of Processors and/or Relative Speed parameters. A little time maybe saved at startup by giving the Host Architecture String parameter explicitly, for example, using thecfx5parhosts utility.

Tip

If an individual user wants to use a host that is not present in either the hostinfo.cclin the installation config directory or the user's own version of this file, then the user canadd this host to the list for a particular run by using the CFX-Solver Manager. However, thiswould have to be done each time a run is started.

The available parameters for the hostinfo.ccl file are as follows:

Installation RootThis is set to the <CFXROOT> installation directory on this host. If it is set to the special string none, thisindicates that there is no ANSYS CFX installation on the remote host, which can sometimes be useful ifonly the solver binary is available.

Host Architecture StringANSYS CFX will use this value to select the most appropriate solver executable for this node. These stringscan be obtained by giving the command <CFXROOT>/bin/cfx5info -os on the node in question.



ANSYS CFX Linux Parallel Setup

When these short os values (for example, linux-amd64) are given in this position, the generic solver ex-ecutable will always be used for this host. The string can also be set to the actual architecture of the remotehost (for example, intel_xeon64.sse2_linux2.3.4), which is determined by giving the command <CFX-ROOT>/bin/cfx5info -arch. If these longer strings are used then CFX could use this information toselect between solvers optimized for specific architectures. However, since there are currently no solversoptimized for specific architectures, this extra information is currently unused.

Number of ProcessorsAs implied, this is the number of processors on the machine. It is used for display purposes only and canbe safely omitted.

Relative SpeedThe 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 relativespeed of 1.0. The faster machine would work on a partition size twice as large as the slower machine inthis case.

The numbers themselves are arbitrary; as a guide you may want to set 1.0 for a 1 GHz processor,0.75 for a 750 MHz processor, and so on. If a relative speed entry is not entered, a default of 1.0 isassumed for that host.

You can obtain relative speed values using the cfx5parhosts utility.

Remote Host NameTo include hosts in the parallel run with names that contain, for example, underscore characters, you canadd the “Remote Host Name” parameter to the HOST DEFINITION with the correct network name for thehost and use a readable alias as the name of the object.

Solver ExecutableA solver executable may be explicitly supplied, if necessary. This is usually only required when using Install-ation Root = none, and is recommended for advanced users only. The following substitutions are madeon the string:

root directory of the installation%r

parallel suffix for the executable%p

version of ANSYS CFX being run%v

operating system string%o

architecture subdirectory specification; for example,linux/double

%a

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:



DescriptionArgument

Add information about the named hosts to the file. This assumes thatANSYS CFX is installed in the same directory on each listed host as on thehost on which you are running.

-add host[,host,...]

host may be specified as [user@]hostname[:cfx-5 root] if the user nameor the ANSYS CFX installation root directory differs from the local host.

Runs a standard benchmark case, and fills in the Relative Speed for thelocal host. The benchmark case will usually take less than 5 minutes torun.

-benchmark

Use the specified file as the hostinfo.ccl file.-file file

Merge host information from the named file.-merge file

After modifying the file, write back the information available without attemptingto fill in any missing pieces.

-no-update

Used with -update. Normally, hosts which exist on the network but cannotbe connected to with rsh or ssh are included in the resulting file with acomment. This switch will exclude these hosts.

-strict

Use the system host file. This is the default.-system

Updates the specified host information file. If any hosts do not have anarchitecture specified in the existing hostinfo.ccl file (for example, because

-update

it was added via the -add switch), it will connect to the host and query it tofill in the Host Architecture String parameter. This is the default behavior. Notethat if the Installation Root parameter is incorrect for the host, it will use thestandard system commands to guess a generic architecture string. This canhappen if you use -add to include a host with a different installation directorythan the local one.

Use the per-user host file.-user

1.3. Using Intel MPI (Message Passing Interface Library)

Most Linux systems support two parallel run modes: Intel MPI and IBM Platform MPI. Intel MPI is thepreferred parallel run mode on most of the supported ANSYS CFX platforms.

Intel MPI supports several network fabrics including:

• Shared memory, typically used for intra-host communication.

• DAPL-capable network fabrics, such as Infiniband, iWarp, Dolphin and XPMEM (through DAPL).

• TCP/IP-capable network fabrics, such as Ethernet and InfiniBand (through IPoIB).

• TMI-capable network fabrics including Qlogic and Myrianet (through Tag Matching Interface).

• OFA-capable network fabrics including InfiniBand (through OFED verbs).

Intel MPI is automatically installed with ANSYS CFX in the<CFXROOT>/../commonfiles/ directory.You do not need a license from Intel to run the ANSYS CFX-Solver using Intel MPI.




Intel 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 “Intel MPI Local Parallel” or “Intel MPI Distributed Parallel”start method options.

1.3.1. Environment Variables

In most cases, the default settings are sufficient and it may not be necessary to set any environmentvariables.

ANSYS CFX uses the environment variable CFX5_IMPI_DIR to select which Intel MPI installation is used.The default setting points to the version that is automatically installed by ANSYS CFX in the<CFX-ROOT>/../commonfiles/MPI/Intel directory. You can use cfx5info -v to find the current settingsfor CFX5_IMPI_DIR and other environment variables. If you want to use a different Intel MPI version,you can install that version in an alternative location and set CFX5_IMPI_DIR to that location.

There are several environment variables that can be used to control Intel MPI that may provide addi-tional flexibility that is not directly accessible through the ANSYS CFX start-up scripts. For example,environment variables are available for network fabric selection (discussed briefly below), process pinningcontrol, and collective operation control.

Any of these environment variables can be set by modifying the start command in the etc/start-methods.ccl file and using the Intel MPI options -env and/or -genv (an example of this usage isgiven in the section on network fabric selection). More detail on all options and environment variablesis available in the Intel MPI documentation.

Some useful environment variables include those described below. If these environment variables areset the start-up scripts automatically set them for your ANSYS CFX runs.

I_MPI_MPD_REMSHSpecifies which method is used by Intel MPI to spawn jobs on remote machines. The Intel MPI default isssh. However, by default the ANSYS 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.

I_MPI_FABRICS and I_MPI_FABRICS_LISTSpecifies the networks fabrics to be used and the order in which Intel MPI searches for them.

1.3.2. Network Fabrics Selection

Intel MPI start methods use the default network fabrics selection built into Intel MPI. The default orderin which Intel MPI checks for fabrics is DAPL, OFA, TCP, TMI. The environment variable I_MPI_FABRICS_LISTcontrols the search order used by Intel MPI.

If you want to force selection of a specific network fabric, then you can either set the I_MPI_FABRICSenvironment variable or modify the start command in the etc/start-methods.ccl file and addthe necessary command line flags (for example: -env IMPI_FABRICS shm:dapl to select the combinationof shared memory and DAPL fabrics) .

The following table shows how Intel MPI searches for drivers for the various network fabrics:

2nd attempt1st attemptInterconnect

N/AN/Ashm



2nd attempt1st attemptInterconnect

libdat.so or libdat.so.1 for DAPL 1.2 providersand libdat2.so or libdat2.so.1 for DAPL 1.2providers

Environment variableI_MPI_DAT_LIBRARY

DAPL

N/AN/ATCP

libtmi.soEnvironment variable I_MPI_TMI_LIBRARYTMI

libibverbs.soEnvironment variableI_MPI_OFA_LIBRARY

OFA

For example, Intel MPI expects that the DAT shared library for the DAPL network fabric is located eitherin the default library search path or in a specific location if a full path is specified. If the shared librarycannot be found, Intel MPI will not take advantage of the DAPL network fabric. To fix this, you will haveto install the shared libraries into the correct location or set the environment variable I_MPI_DAT_LIBRARYto point to the correct DAT shared library.

There are other environment variables not documented here which provide further control over networkfabrics selection. These are described in the Intel MPI documentation.

1.4. Using IBM Platform MPI (Message Passing Interface Library)

IBM Platform MPI is available as an alternative parallel run mode on all the supported ANSYS CFX plat-forms.

IBM Platform MPI supports several communication modes including shared memory and networkedTCP/IP (Ethernet), luDAPL, VAPI, OpenFabrics (IB), GM-2, MX (Myrinet), Elan4 (Quadrics), QLogic InfiniPath,and EtherFabric (Level 5 Networks).

IBM Platform MPI is automatically installed with ANSYS CFX in the <CFXROOT>/tools directory. Youdo not need a license from Platform to run the ANSYS CFX-Solver using IBM Platform MPI.

IBM 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 “PlatformMPI Distributed Parallel” start method options.

For IBM Platform MPI, the –cpu_bind option is used by default and binds processes to cores using acyclic order. This leads to better performance but, on multi-user clusters having scheduling systemsthat do not enforce exclusive use of cluster nodes, may cause problems because multiple jobs may bebound to the same CPU on the same node. In this case, the –cpu_bind argument to mpirun shouldbe removed from the IBM Platform MPI start methods in the <CFXROOT>/etc/start_methods.cclfile.

1.4.1. Environment Variables

In most cases, the default settings are sufficient and it may not be necessary to set any environmentvariables.

ANSYS CFX uses the environment variable CFX5_PCMPI_DIR to select which IBM Platform MPI installationis used. The default setting points to the version that is automatically installed with ANSYS CFX in the<CFXROOT>/../commonfiles/MPI/Platform directory. You can use cfx5info -v to find the currentsettings for CFX5_PCMPI_DIR and other environment variables. If you want to use a different IBM PlatformMPI version, you can install that version in an alternative location and set CFX5_PCMPI_DIR to thatlocation. For distributed parallel runs, IBM Platform MPI must be present at the same location (same




absolute path) on all hosts. Typically, this is achieved by using a central ANSYS CFX installation, accessibleby all hosts. In order to run a CFX job in distributed parallel using IBM Platform MPI on hosts with dif-ferent CFX installation locations, you must first install IBM Platform MPI under the same location (sameabsolute path) on each host, then set the environment variable CFX5_PCMPI_DIR to the location underwhich IBM Platform MPI was installed.

There are several environment variables that can be used to control IBM Platform MPI (documented inthe IBM Platform MPI documentation) that may provide additional flexibility not directly accessiblethrough the ANSYS CFX startup scripts. If these environment variables are set the startup scripts auto-matically set them for your ANSYS CFX runs. Some useful environment variables include:

MPI_REMSHEnables you to change which method is used by IBM Platform MPI to spawn jobs on remote machines.The IBM Platform MPI default is ssh. However, by default the ANSYS CFX software sets this to be the sameas the setting used for CFX5RSH, and rsh if CFX5RSH is not set. This variable is applicable only to Linux andHP-UX.

MPI_IC_ORDEREnables you to change the default order in which IBM Platform MPI searches for interconnects.

1.4.2. Interconnect Selection

IBM Platform MPI start methods use the default communication mode selection built into IBM PlatformMPI. The default order in which IBM 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 theetc/start-methods.ccl file and add the necessary command line flags (for example: -GM to forceselection of the Myrinet interconnect) or use the appropriate IBM 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) andsetting the subnet you want to use (-subnet, sometimes useful for selecting particular interconnects aswell if your system is configured that way).

For some Linux-based cluster environments not supported by IBM Platform MPI, it is possible that theMyrinet, Infiniband or Quadrics hardware drivers are not located where IBM Platform MPI expects. IfIBM Platform MPI cannot detect the drivers for fast interconnects, it will generally default back to thelowest speed connection that it can detect (usually TCP/IP socket communication).

The following table gives information on the default search path IBM Platform MPI uses to find driversfor the various communication interfaces:

3rd attempt2nd attempt1st attemptInterconnect

/usr/voltaire/lib/libitapi.solibitapi.soEnvironment variableMPI_ICLIB_ITAPI

Infiniband(IB)

/opt/gm/lib/libgm.so OR/opt/gm/lib/libgm32.so

libgm.so OR libgm32.soEnvironment variableMPI_ICLIB_GM

Myrinet(GM)

nonelibelan.soEnvironment variableMPI_ICLIB_ELAN

ELAN

nonelibdat.soEnvironment variableMPI_ICLIB_UDAPL

UDAPL



3rd attempt2nd attempt1st attemptInterconnect

libmtl_common.so,libmpga.so, libmosal.so,libvapi.so

Environment variableMPI_ICLIB_VAPIDIR

Environment variableMPI_ICLIB_VAPI

VAPI

/usr/lib64/libpsm_infinipath.so.1

libpsm_infinipath.so.1Environment variableMPI_ICLIB_PSM

Infinipath

For example, IBM Platform MPI expects that GM stack shared libraries for Myrinet interconnects arelocated either in the default library search path or in the /opt/gm/lib64 (64 bit x86) directories. If theshared libraries are not in either location, IBM Platform MPI will not take advantage of the high-speedinterconnects. To fix this, you will have to copy the shared libraries into the correct location or set theenvironment variable MPI_ICLIB_GM to point to the correct GM stack shared library.

1.5. Using Cray MPI (Message Passing Interface Library)

The ANSYS CFX-Solver supports Cray’s native implementation of MPI on the Cray Linux Environment(CLE) using the start method ‘Cray MPI Distributed Parallel’.

Cray MPI is closely integrated with the batch queuing system and interconnects used on Cray systems.

Cray MPI is the recommended method of running on Cray systems, as opposed to using Cluster Com-patibility Mode (CCM) with a different MPI.

When starting a solver run, the Cray MPI start method may be specified on the command line usingthe option: -start-method “Cray MPI Distributed Parallel”, having reserved the requiredprocessing elements via the built-in batch queuing system.

1.5.1. Cray MPI Options

The aprun command, which can be modified, is used by the start method to launch the job. Otheroptions available from Cray are described in the documentation for aprun.

Note that numa node memory containment is enforced, using the -ss option. The default methodused by Cray MPI to allocate processes to CPU cores is appropriate when all cores are used. However,if it is intended that each host is only partly utilized (for example, because of the memory requirementsof the run), this can result in asymmetric utilization. In such cases, the -S option can be used to limitthe number of processes per numa node. For example, -S 4 would limit the number of processes pernuma node to 4.

2. ANSYS CFX Windows Parallel Setup

ANSYS CFX-Solver must be installed on all hosts that are to be used for a parallel run.

Local parallel runs use Intel MPI (default) or IBM Platform MPI for communication.

To run distributed parallel (where slave processes run on hosts other than the host with the masterprocess), the desired MPI service must be installed, configured, and started on all involved hosts. Inaddition, you must make host information available to the master host. These tasks are discussed inSetting Up IBM Platform MPI for Windows (p. 22) or Setting Up Intel MPI for Windows (p. 21).



ANSYS CFX Windows Parallel Setup

2.1. Parallel Setup for Windows

When the ANSYS CFX distributed parallel starts, it needs to know where to find the CFX-Solver executableon every host. You must make host information available to the master host by one of these mechanisms:

• (Preferred mechanism) The hostinfo.ccl file on the master host is configured with any required inform-ation about slave hosts.

The hostinfo.ccl file registers information such as the Installation Root and Host Ar-chitecture String parameters for hosts used for distributed parallel runs. The hostinfo.cclfile is created automatically when installing ANSYS CFX. By default, it contains details of the host onwhich it is installed.

For hosts that have the same architecture as the machine that runs the master process, registrationin the hostinfo.ccl file is optional; if a particular host is not specified then all of its propertiesare assumed to be the same as those of the machine that runs the master process.

For machines that have a machine architecture different from the machine that runs the masterprocess, the hostinfo.ccl file must include information about the properties that differ fromthose of the machine that runs the master process.

See hostinfo.ccl file (p. 18) for more information.

If your machine previously had ANSYS CFX installed, then ensure that remote host interrogation isdisabled either by deleting the environment variable CFX_SOLVE_DISABLE_REMOTE_CHECKS or(equivalently) by setting that environment variable to a value of 1. This environment variable can bespecified in your Windows environment or your user cfx5rc.txt file or site cfx5rc.txt file. SeeResources Set in cfx5rc Files in the CFX Introduction for details.

• Have ANSYS CFX determine the required information for itself.

If ANSYS CFX is to determine the required information for itself, then remote- or secure-shell accessmust be available from the master host (the system on which parallel runs will be started) to slavehosts (systems on which the ANSYS CFX-Solver will actually run). You must be able to execute an rshor ssh command on the remote host without typing in your password. Unless you already have yourWindows systems set up to allow this type of access, this method of setting up distributed parallelis not recommended.

You will also have to set the environment variable CFX_SOLVE_DISABLE_REMOTE_CHECKS to avalue of 0; this enables remote host interrogation. This environment variable can be specified in yourWindows environment or your user cfx5rc.txt file or site cfx5rc.txt file. See Resources Setin cfx5rc Files in the CFX Introduction for details.

2.1.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 host and be madereadable by all users of the software. This file is a database containing information about the availablehosts and where ANSYS CFX has been installed on each of them. The file is used by the ANSYS CFX-Solver when constructing a parallel run.

The hostinfo.ccl file is written using the CFX Command Language. It defines a set of HOSTDEFINITION objects, one for each available host. 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 CONTROLEND # SIMULATION CONTROL

Note

If you manually create your hostinfo.ccl file, you must ensure that the SIMULATIONCONTROL...END wrapper is present.

None of the values for each host are mandatory. For example, the following empty host definition isperfectly valid:

HOST DEFINITION: hostname1END

Host names are limited to the set of valid CCL object names. In particular, they must not contain fullstops (.) 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 con-taining the installation host. You can add hosts to the hostinfo.ccl file using the cfx5parhostsutility, or by modifying the file using a text editor.

For most installations, it will be necessary only to supply the Installation Root parameter, which shouldpoint to the <CFXROOT> directory in which ANSYS CFX is installed. On mixed networks, you may findit useful to supply the Number of Processors and/or Relative Speed parameters. A little time may besaved at startup by giving the Host Architecture String parameter explicitly, for example, using thecfx5parhosts utility.

The available parameters are as follows:

Installation RootThis is set to the <CFXROOT> installation directory on this host. If it is set to the special string none, thisindicates that there is no ANSYS CFX installation on the remote host, which can sometimes be useful ifonly the solver binary is available.

Host Architecture StringThis should be set to the actual architecture <arch> of the remote host. ANSYS CFX will use this value toselect the most appropriate solver executable for this host. These strings can be obtained by giving thecommand <CFXROOT>/bin/cfx5info -os on the host in question. If the shorter <os> values aregiven in this position, the generic solver executable will always be used for this host.

Number of ProcessorsAs implied, this is the number of processors on the machine. It is used for display purposes only and canbe safely omitted.

Relative SpeedThe 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 inthis case.

The numbers themselves are arbitrary; as a guide you may want to set 1.0 for a 1 GHz processor,0.75 for a 750 MHz processor, and so on. If a relative speed entry is not entered, a default of 1.0 isassumed for that host.

You can obtain relative speed values using the cfx5parhosts utility.

Remote Host NameTo include hosts in the parallel run with names that contain, for example, underscore characters, you canadd the “Remote Host Name” parameter to the HOST DEFINITION with the correct network name for thehost and use a readable alias as the name of the object.

Solver ExecutableA solver executable may be explicitly supplied, if necessary. This is usually only required when using Install-ation Root = none, and is recommended for advanced users only. The following substitutions are madeon the string:

root directory of the installation%r

parallel suffix for the executable%p

version of ANSYS CFX being run%v

operating system string%o

architecture subdirectory specification, for example,linux/double

%a

If it is not supplied, this parameter has the default value %r/bin/%a/solver%p.exe

2.1.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 isdone by running:

CFXROOT\bin\cfx5parhosts argument list

where argument list corresponds to one or more of the arguments listed below.

DescriptionArgument

Add information about the named host(s) to the file. This assumes thatANSYS CFX is installed in the same directory on each listed host as on thehost on which you are running.

-add host[,host,...]

host may be specified as [user@]hostname[:cfx-5 root] if the user nameor the ANSYS CFX installation root directory differs from the local host.

To add a set of separately-installed Windows hosts to the hostinfo.cclfile, where the installation may be in a different place on each host, therecommended method is to gather the hostinfo.ccl files created oneach host by the installation process, and merge them together using the-merge switch.

Runs a standard benchmark case, and fills in the Relative Speed for the localhost. The benchmark case will usually take less than 5 minutes to run.

-benchmark



DescriptionArgument

Use the specified file as the hostinfo.ccl file.-file file

Merge host information from the named file.-merge file

After modifying the file, write back the information available without attemptingto fill in any missing pieces.

-no-update

Used with -update. Normally, hosts that exist on the network but cannot beconnected to with rsh or ssh are included in the resulting file with a comment.This switch will exclude these hosts.

-strict

Use the system host file. This is the default.-system

Updates the specified host information file. If any hosts do not have anarchitecture specified in the existing hostinfo.ccl file (for example, because

-update

it was added via the -add switch), it will connect to the host and query it tofill in the Host Architecture String parameter. This is the default behavior. Notethat if the Installation Root parameter is incorrect for the host, it will use thestandard system commands to guess a generic architecture string. This canhappen if you use -add to include a host with a different installation directorythan the local one.

Use the per-user host file.-user

2.2. Setting Up Intel MPI for Windows

To install, configure, and start the Intel MPI service on a given host, install Intel MPI using the installationlauncher. After installing Intel MPI in this way, the software is configured and started. For more inform-ation, see Product Installation with Client Licensing.

2.2.1. Setting Up Intel MPI Authentication

Intel MPI can operate under three levels of authentication. Each method requires some setup.

2.2.1.1. Password Authentication

1. From the launcher, select Tools > Command Line.

2. Enter:

cfx5parallel -register-impi-user

A prompt will appear asking for a user name which is valid on all machines. This must include adomain where needed. For example, DOMAIN\User.

A prompt will then appear asking for a password. This must be then entered again for confirmation.

2.2.1.2. Delegated Authentication

This is a domain based authorization with delegation ability.

Create an environment variable I_MPI_AUTH_METHOD=delegate.

2.2.1.3. Impersonated Authentication

This is a domain based authorization with delegation ability.




Create an environment variable I_MPI_AUTH_METHOD=impersonate.

2.2.2. Enabling Intel MPI Parallel Through a Windows Firewall

To enable Intel MPI parallel processing through a Windows firewall:

1. Click Start and select Control Panel.

2. On the Control Panel dialog box, double-click Security Center.

3. Click Windows Firewall.

4. On the Windows Firewall dialog box, click the Exceptions tab and then click Add Program.

5. Browse to the following programs:

• For Intel MPI:

– <CFXROOT>\bin\<CFX5OS>\solver-impi.exe

– <CFXROOT>\bin\<CFX5OS>\double\solver-impi.exe

– <CFXROOT>\..\commonfiles\MPI\Intel\<version number>\winx64\bin\smpd.exe

– <CFXROOT>\..\commonfiles\MPI\Intel\<version number>\winx64\bin\mpiexec.exe

After each selection, click OK to add that program to the list of programs that are permitted topass through the Windows firewall.

6. When you are finished, click OK to close the Windows Firewall dialog box, then close the Windows Se-curity Center and the Control Panel.

2.3. Setting Up IBM Platform MPI for Windows

To install, configure, and start the IBM Platform MPI service on a given host, install Platform-MPI usingthe installation launcher. After installing IBM Platform MPI in this way, the software is configured andstarted. For more information, see Product Installation with Client Licensing.

Note

• IBM Platform MPI service requires that all hosts are on the same domain and that the user hasan account for that domain.

• IBM Platform MPI service requires that all machines in the cluster have identical MPI installationdirectory paths.

• IBM Platform MPI uses the –cpu_bind option by default and binds processes to cores using acyclic order. This leads to better performance but, on multi-user clusters having scheduling systemsthat do not enforce exclusive use of cluster nodes, this may cause problems because multiplejobs may be bound to the same CPU on the same node. In this case, the –cpu_bind argumentto mpirun should be removed from the IBM Platform MPI start methods in the start_meth-ods.ccl file in the <CFXROOT>/etc directory.



2.3.1. Enabling IBM Platform MPI Parallel Through a Windows Firewall

To enable IBM Platform MPI parallel processing through a Windows firewall:

1. Click Start and select Control Panel.

2. On the Control Panel dialog box, double-click Security Center.

3. Click Windows Firewall.

4. On the Windows Firewall dialog box, click the Exceptions tab and then click Add Program.

5. Browse to the following programs:

• For IBM Platform MPI:

– <ANSYS Inc installation path>\v160\CFX\bin\<CFX5OS>\solver-pcmpi.exe

– <ANSYS Inc installation path>\v160\CFX\bin\<CFX5OS>\double\solver-pcmpi.exe

– <ANSYS Inc installation path>\v160\commonfiles\MPI\Platform\<version number>\winx64\sbin\pcmpi-win32service.exe

– <ANSYS Inc installation path>\v160\commonfiles\MPI\Platform\<version num-ber>\winx64\bin\mpirun.exe

– <ANSYS Inc installation path>\v160\commonfiles\MPI\Platform\<version number>\winx64\bin\mp-id.exe

The IBM Platform MPI service listens to port 8636 by default. This can be changed during installationof IBM Platform MPI from the product installer or using the following command:

cfx5parallel -setportkey-pcmpi-service

In all cases, you must ensure the chosen port is accessible.

After each selection, click OK to add that program to the list of programs that are permitted topass through the Windows firewall.

6. When you are finished, click OK to close the Windows Firewall dialog box, then close the Windows Se-curity Center and the Control Panel.

2.4. Setting up and Running Microsoft Windows HPC 2008 or HPC 2012

To set up running Microsoft Windows HPC 2008 or Microsoft Windows HPC 2012, steps must be takenso 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.

To prepare for running ANSYS CFX with Microsoft Windows HPC 2008 or Microsoft Windows HPC 2012,you can follow the steps below (terms in angle brackets < > should be replaced with the required entry):




1. Install ANSYS Licensing, ANSYS Workbench and ANSYS CFX on the head node.

2. Share the installation directory. For example, on a typical installation share C:\Program Files\ANSYSInc as \\<HeadNodeName>\ANSYS Inc where <HeadNodeName> is the name of the head node.

3. 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\v171\prereq\2008MFCvcredist_x64.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\2008vcredist_x64.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\2008vcredist_x86.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\2010vcredist_x64.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\2010vcredist_x86.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\2012vcredist_x64.exe /quiet\\<HeadNodeName>\ANSYS Inc\v171\prereq\2012vcredist_x86.exe /quiet\\<HeadNodeName>\ANSYS Inc\v171\prereq\dotNetFx40.exe /q\\<HeadNodeName>\ANSYS Inc\v171\prereq\vcredist_x64_SP1.exe /Q\\<HeadNodeName>\ANSYS Inc\v171\prereq\vcredist_x86_SP1.exe /Q

• or by using the clusrun command on the headnode to execute these commands on all the nodes(refer to your Microsoft Windows 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 shareC:\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 2008R2 Client Utilities’ on the submitting machine. This is available for download from Microsoft. This sets theCCP_HOME environment variable, enabling the ‘Submit to Windows CCS or HPC Queue’ start method inthe CFX-Solver Manager.

6. On the submitting machine, create %USERPROFILE%\.cfx\cfxccs_options.txt with the followingcontent to define the required CCS options:

PATHMAP=C:\Program Files\ANSYS Inc;\\<HeadNodeName>\ANSYS IncPATHMAP= C:\Users\<UserName>;\\<HeadNodeName>\<UserName> orPATHMAP=C:\Users\<UserName>;\\<SubmitHostName>\<UserName> if the workingdirectory has been shared from the submitting machine.CLUSTERHOST=<HeadNodeName> to be used when submitting jobs from machines otherthan the headnode.ACCOUNT=<OtherUserDomain>\<OtherUserName> to be used when submitting jobsusing different credentials, where <OtherUserDomain> and <OtherUserName> are thedomain and user names of another user, respectively.PROCESSORSPERSOLVER=2 an optional setting (default setting is 1) that allocates the numberof cores per partition. This is typically used on hosts that are limited by memory bandwidthsuch as Xeon-based machines.

7. Set up ANSYS Workbench for a network as described in Network Installation and Product Configuration.

To submit a job:



1. Start the CFX-Solver Manager (either using CFX standalone or from ANSYS Workbench) on the submittingmachine using the software installed on the headnode.

2. Ensure that the Run Mode on the Run Definition tab of the CFX-Solver Manager is set to Submit toWindows CCS or HPC Queue. Otherwise, set up the CFX-Solver Manager as normal.

3. 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 Managerwindow). You may elect to have these credentials saved to avoid repeated prompting of these credentials.

Note

1. For simulations making use of User Fortran, you must ensure that the Fortran is linked againstthe solver-msmpi.lib. This is done by making the appropriate changes to cfx5mkext.ccl.

2. %USERPROFILE% is typically C:\Users\<UserName> on Microsoft Windows HPC Server2008.

3. To use on ANSYS Workbench with Parameters and Design Points, start the CFX-Solver Managerensure that the Run Mode on the Run Definition tab of the CFX-Solver Manager is set toSubmit to Windows CCS or HPC Queue, set the number of processes, then click SaveSettings. When the user clicks Update all Design Points each parameter or design point willbe solved on the cluster.





IBM Platform MPI with High (>4096) Process Count

The Platform MPI software included with ANSYS products allows for a maximum of 4096 processes tobe included in a single parallel calculation. You will need to obtain an additional license from Interna-tional Business Machines Corp. (IBM) for higher process counts. Alternatively, you can use the "IntelMPI" option in the settings for your parallel calculation.


