ansys licensing guide

ANSYS, Inc. LicensingGuide9.0 Release

002092November 2004

ANSYS, Inc. is aUL registeredISO 9001: 2000Company.

ANSYS, Inc. LicensingGuide

9.0 Release

ANSYS, Inc.Southpointe275 Technology DriveCanonsburg, PA [email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494

Revision HistoryDateNumberMay 2003001791October 2003001904April 2004001977November 2004002092

*The information in this guide applies to all ANSYS, Inc. products (including the ANSYS and ANSYS Workbench Products)released on or after this date, until superceded by a newer version of this guide.

Copyright and Trademark InformationCopyright © 2004 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.

ANSYS, DesignSpace, CFX, DesignModeler, DesignXplorer, ANSYS Workbench environment, AI*Environment, CADOE andany and all ANSYS, Inc. product names referenced on any media, manual or the like, are registered trademarks or trademarksof subsidiaries of ANSYS, Inc. located in the United States or other countries. ICEM CFD is a trademark licensed by ANSYS,Inc. All other trademarks and registered trademarks are property of their respective owners.

ANSYS, Inc. is a UL registered ISO 9001: 2000 Company.

ANSYS Inc. products may contain U.S. Patent No. 6,055,541.

Microsoft, Windows, Windows 2000 and Windows XP are registered trademarks of Microsoft Corporation.Inventor and Mechanical Desktop are registered trademarks of Autodesk, Inc.SolidWorks is a registered trademark of SolidWorks Corporation.Pro/ENGINEER is a registered trademark of Parametric Technology Corporation.Unigraphics, Solid Edge and Parasolid are registered trademarks of Electronic Data Systems Corporation (EDS).ACIS and ACIS Geometric Modeler are registered trademarks of Spatial Technology, Inc.

ACIS® Geometric Modeler and ACIS InterOp from Spatial Technology, Inc.Parasolid and Parasolid IGES from EDS.Parasolid Bodyshop from Unigraphics Solutions2D DCM from D-Cubed Ltd.GHS3D meshing technology by P. L. George, INRIA, France.Visual MainWin®Copyright 2002 Mainsoft Corporation. All rights reserved. Mainsoft, Mainwin, the software porting company, e-porting,the e-porting company, and Visual MainWin are trademarks or registered trademarks of Mainsoft Corporation in theUnited States and/or foreign countries.ZLIB 1.1.3 Copyright (C) 1995-1998 Jean-loup Gailly and Mark AdlerMeschach Library Copyright (C) 1993 David E. Steward & Zbigniew Leyk, all rights reserved.DesignSpace contains Simulation Wizard, Patent Pending.

FLEXlm License Manager is a trademark of Macrovision Corporation.

This ANSYS, Inc. software product and program documentation is ANSYS Confidential Information and are furnished byANSYS, Inc. under an ANSYS software license agreement that contains provisions concerning non-disclosure, copying,length and nature of use, warranties, disclaimers and remedies, and other provisions. The Program and Documentationmay be used or copied only in accordance with the terms of that license agreement.

Printed in the U.S.A.

Table of ContentsPreface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

1. Supported Products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

1.1. ANSYS and FLEXlm .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11.1.1. The Licensing Process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–21.1.2. Compatibility with Other FLEXlm-Licensed Software ... . . . . . . . . . . . . . . . . . . . . . . 1–21.1.3. Links to FLEXlm .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2

1.2. Communications Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–31.2.1. Configuring TCP/IP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3

1.2.1.1. Determining Whether TCP/IP Is Installed on a Microsoft WindowsSystem .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

1.2.2. Changing the Default Port Number ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–41.3. Explanation of Licensing Terms ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

1.3.1. The License Manager Daemon (lmgrd) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–51.3.2. The Vendor Daemon (ansyslmd) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–51.3.3. The License File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–51.3.4. The Application Programs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6

2. License Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.1. What Are License Servers? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.2. Selecting License Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1

2.2.1. Redundant Server Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–22.2.2. Registering License Server Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3

3. License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13.1. Installing License Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13.2. Specifying the License Server and License Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1

3.2.1. Setting the Path with an Environment Variable ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33.2.2. License Files Settings Precedence ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4

3.3. License Files Format ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43.3.1. SERVER Lines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43.3.2. VENDOR Lines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–53.3.3. INCREMENT Lines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63.3.4. Sample License Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–73.3.5. Recognizing an ANSYS License File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8

3.4. Product Variable Table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94. The ANSYS License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1

4.1. License Manager Daemon ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14.1.1. Modifying License Manager Startup Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14.1.2. Starting the License Manager Manually .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24.1.3. Starting the License Manager at System Boot Time ... . . . . . . . . . . . . . . . . . . . . . . . . 4–2

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

4.1.4. Shutting Down the License Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–45. The Licensing Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

5.1. Designating Server(s) for License Check-out ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15.1.1. Sample Scenario ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2

5.2. Establishing User Privileges ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–25.2.1. Editing the Licensing Options File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–35.2.2. Sample Options File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6

5.3. Other Environment Variable Settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–65.4. Creating the lmadmin Group ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8

5.4.1. HP AlphaServer (Compaq), HP, SGI, Sun, Linux ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–85.4.2. IBM RS/6000 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8

5.5. Setting Up License Queuing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–95.6. Using License Borrowing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10

5.6.1. Setting up License Borrowing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–105.6.2. Running the License Borrowing Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10

6. License Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16.1. Using the ANSLIC_ADMIN Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1

6.1.1. Register License Server Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26.1.2. Display the License Server Hostid ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–36.1.3. Run the License Wizard ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–36.1.4. Install the License File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–36.1.5. Start the License Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46.1.6. Stop the License Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46.1.7. Reread the License File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56.1.8. Specify the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56.1.9. Edit the FLEXlm Options File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56.1.10. Modify Startup Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66.1.11. Remove a Client License ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66.1.12. Run the ANSYS Borrow Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76.1.13. View Status/Diagnostic Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7

6.1.13.1. Display the License Status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76.1.13.2. Display the Customer Number ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76.1.13.3. View the License File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86.1.13.4. View the License Log File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86.1.13.5. Gather Diagnostic Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8

6.1.14. Uninstall the License Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86.2. Using the LMTOOLS Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9

7. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17.1. Getting Additional License Debug Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17.2. Using the ansys_pid Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–37.3. Problem Situations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3

ANSYS, Inc. Licensing Guide

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.vi

7.3.1. License Manager Will Not Start .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–37.3.2. License Manager Will Not Stop in a Three-Server Environment ... . . . . . . . 7–57.3.3. Unable to Check Out Licenses ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–57.3.4. Jobs Abort When License Manager Goes Down in Three-Server Envir-onment ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–57.3.5. Ethernet Address Shows All Zeroes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–67.3.6. Licensing Log File Not Created ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–67.3.7. Queuing Does Not Work ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–77.3.8. The FLEXlm Utility lmcksum May Give Misleading Information ... . . . . . . . 7–77.3.9. The Launcher is Excessively Slow to Start .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7

7.4. Licensing-Related Launcher Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–77.5. Licensing Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–97.6. ANSYS License Borrowing Errors .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–167.7. ANSYS License Log File Errors .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17

Glossary ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G–21Index ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index–1

List of Tables1.1. Configuring TCP/IP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–33.1. Product/Feature Names for Licensed Products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94.1. License Manager Automatic Startup Instructions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37.1. ANS_FLEXLM_DEBUG Output Locations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2

viiANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

ANSYS, Inc. Licensing Guide

Preface

1. Supported Products

This document contains information for running the FLEXlm License Manager with allANSYS, Inc. products, including ANSYS, ANSYS Workbench, ANSYS ICEM CFD, and ANSYSCFX products. However, some information may pertain only to specific products/licensinglevels, such as ANSYS or DesignSpace.

Supported Hardware Platforms

This document details information about licensing ANSYS, Inc. products on the hardwareplatforms listed below. Not all products support all platforms listed below. Please referto the installation documentation for the platforms on which your specific product runs.The name in parenthesis indicates the directory name for each platform (referred to as<platform> throughout this document).

• HP AlphaServer (alpha)

• HP PA8000 64-bit (hp64)

• HP Itanium2 64-bit (hpia64)

• IBM RS/6000 AIX 5L (aix64)

• SGI 64-bit (sgi64)

• Sun UltraSPARC 64-bit (sun64)

• Sun UltraSPARC III+ 64-bit (usIII)

• Fujitsu SPARC64 IV 64-bit (fjpp)

• Intel IA-32 Linux (linia32) (RH AS 2.1, Kernel 2.4.9)

• Intel IA-64 Linux (linia64) (RH AS 2.1, Kernel 2.4.18)

• AMD Opteron Linux 64-bit (linop64)

• Windows XP 64-bit (win64)

• Windows XP (intel)

• Windows 2000 (intel)

For specific operating system requirements, refer to the installation guide for the productand platform you are running.


Intended Audience

The ANSYS Licensing Guide is intended for the person responsible for licensing adminis-tration of all ANSYS, Inc. products at a site. This person is typically the system administrator.

Product Definitions

This guide applies to all licensed ANSYS, Inc. products, including ANSYS, ANSYS Work-bench, ANSYS ICEM CFD, and ANSYS CFX products, unless otherwise noted.

Summary of New and Changed Features

Listed below is a summary of those licensing items that are either new or have beenchanged since the last release. For a list of all major new and changed features of anyproduct, see the Release Notes document for that product.

• The ANSLIC_ADMIN utility has been updated and reorganized for easier use.

• A license borrowing capability has been added.

Conventions Used in This Document

Computer prompts and responses and user input are printed using this font:

/ansys_inc/shared_files/licensing/lic_admin/anslic_admin

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

exec_path <drive>:\Program Files\Ansys Inc\ansys90\ac4 \bin\pro\<platform>\ac4pro90.exe

Wild card arguments and variables are italicized.

Commands appear in bold face.

Note — Note paragraphs are introduced by the text Note. A note contains inform-ation that supplements the main topic being discussed.

Caution: Paragraphs that begin with the word “Caution” in bold, with the restof the text in normal type, warn you about actions or situations that potentiallymay cause problems or unexpected behavior or results in ANSYS, Inc. products.

Preface

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.x

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

xiANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Section 1: Supported Products

Chapter 1: Introduction

1.1. ANSYS and FLEXlm

ANSYS, Inc. uses the FLEXlm (FLEXnet Publisher Licensing Module) license manager forall of its licensed products. FLEXlm, the most popular license manager used in the softwareindustry, is best known for its ability to allow software licenses to be available (or float)anywhere on a network. Floating licensing benefits both users and license administrators.Users can make more efficient use of fewer licenses by sharing them on the network. Li-cense administrators can control who uses the licensed application and the machine(s)where the licenses will be available. The format of the traffic between the ANSYSproduct(s) and the license manager is machine independent, allowing for heterogeneousnetworks. This means the license server and the computer running an application canbe either different hardware platforms or even different operating systems (Windowsand UNIX, for example).

The license manager, daemons or services, and license utility files are installed duringthe installation process.

A typical installation on a Unix machine allows you to install the product anywhere onthe system. The installation then creates a symbolic link from the installation directoryto /ansys_inc. All licensing files and utilities are provided in the /ansys_inc/shared_files/li-censing subdirectory.

If you installed the product elsewhere on your system, replace all references to /ansys_incin this guide with the name of the installation directory you used. Any referencethroughout this manual to the licensing directory on Unix platforms means /an-sys_inc/shared_files/licensing.

A typical installation on a Windows machine (choosing the default installation directory)installs the products in the product subdirectory in \Program Files\Ansys Inc, locatedon the same drive as the operating system. The \Shared Files\Licensing subdirectoryis also created in this installation directory. If you installed the product in a different dir-ectory, replace all references to \Program Files\ANSYS Inc\<product> in this guidewith the name of the installation directory you used. However, the licensing directorywill still remain in the default location; you cannot change this location. The licensingcomponents are shared across all ANSYS, Inc. products and need to reside in a fixedlocation.


Any reference throughout this manual to the licensing directory on Windows platformsmeans \Program Files\Ansys Inc\Shared Files\Licensing, located on the same driveas the operating system.

1.1.1. The Licensing Process

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

1. Select the license server(s). See Section 2.2: Selecting License Servers.

2. Install and configure TCP/IP. See Section 1.2: Communications Requirements forinformation on configuring TCP/IP.

3. Install the software. See the appropriate installation manual for your productand platforms.

4. Register the license server(s). See Section 2.2.2: Registering License Server Inform-ation.

5. Run the License Wizard. See Section 6.1.3: Run the License Wizard

6. Set up the licensing environment. See Chapter 5, “The Licensing Environment”.

1.1.2. Compatibility with Other FLEXlm-Licensed Software

Because of FLEXlm's popularity, you may have FLEXlm licenses from more than onevendor.

The ANSYS License Manager uses FLEXlm 9.2. If you do have other FLEXlm-licensedproducts running FLEXlm 9.2 or higher, you can run them in conjunction with ANSYSproducts with no intervention or special configuration requirements.

However, if you want to combine ANSYS, Inc. license files with other license files and useone lmgrd license manager, please refer to the FLEXlm End Users Guide for informationon how to administer multiple products using the FLEXlm license manager. If you needtechnical assistance when running multiple products under the same license manager,please contact Macrovision Corporation for technical support.

1.1.3. Links to FLEXlm

For more information on using FLEXlm, please visit the FLEXlm web site at http://www.mac-rovision.com/products/flexnet_publisher/licensing_module.shtml. You can refer to theFLEXlm End Users Guide for the most current information on all FLEXlm features. Youcan also access this document from the ANSLIC_ADMIN Help menu option View theFLEXlm End Users Guide.


ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.1–2

http://www.macrovision.com/services/support/enduser/TOC.htm

http://www.macrovision.com/products/flexnet_publisher/licensing_module.shtml

http://www.macrovision.com/products/flexnet_publisher/licensing_module.shtml


1.2. Communications Requirements

1.2.1. Configuring TCP/IP

TCP/IP needs to be configured and started for any ANSYS, Inc. product and the licensemanager to be able to run. You should consult your network administrator for assistancewith this configuration. The TCP/IP protocol must be installed on any machine on whichyou want to run an ANSYS product.

TCP/IP is supplied as part of the UNIX operating system. Table 1.1: “Configuring TCP/IP”specifies the system utility used to configure TCP/IP on the various hardware platforms.You should consult your network administrator for assistance with this configuration.

Note — HP AlphaServer and Intel Linux systems require an Ethernet card.

Table 1.1 Configuring TCP/IP

TCP/IP Configuration UtilityHardware Platform

sysman net_wizardHP AlphaServer (Compaq)

samHP

smit tcpipIBM

From the desktop icon, choose this path: System>SystemManager>Network Setup

SGI

/etc/rc2.d/S69inetSun, Fujitsu

linuxconfIntel Linux

yastOpteron Linux

For Windows systems, the TCP/IP protocol is included as part of the operating systemand is typically installed by default. If you do need to install TCP/IP, remember that itmust be bound to a network adapter.

On machines that are connected to an internal network, TCP/IP must be bound to anetwork card such as an Ethernet adapter. The vast majority of systems using TCP/IP willfall into this category.

On machines that connect to the Internet or corporate intranet through a modem, TCP/IPcan be bound to a dial-up connection.

1–3ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Section 1.2: Communications Requirements

1.2.1.1. Determining Whether TCP/IP Is Installed on a MicrosoftWindows System

To determine if TCP/IP is installed on your system, open the Control Panel. Continue asfollows based upon the machine's operating system:

• Windows XP -- Open Network Connections, highlight Local Area Connection andright-mouse click. Select Properties. Internet Protocol (TCP/IP) should be listed.

• Windows 2000--Open Network and Dial-Up Connections, open Local Area Network,and then click on the Properties button. Internet Protocol (TCP/IP) should be listed.

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

Caution: If your computer is connected to a network, it is highly recommendedthat you contact your Information Technology Department before installing ormodifying TCP/IP on your machine.

1.2.2. Changing the Default Port Number

A port number specifies the communications channel by which two or more processescan communicate. ANSYS uses 1055 as the default port number for the ANSYS FLEXlmlicense manager. If you encounter a conflict in port numbers, you can change the defaultby modifying all of the following files:

• On the server machine(s): the port number listed on the SERVER line in the licensefile (license.dat) on the license server(s).

• On the client machine(s): the port number listed in the ansyslmd.ini file or theport number specified in the LM_LICENSE_FILE or the ANSYSLMD_LICENSE_FILEenvironment variables, if set.

1.3. Explanation of Licensing Terms

The four main components of FLEXlm are:

• License manager daemon (lmgrd)

• Vendor daemon (ansyslmd)

• License files



• Application program (e.g., ANSYS)

These components are explained in more detail in the following sections. Note that theterm daemon is used throughout this document. A daemon on Unix systems is the sameas a service on Windows systems.

1.3.1. The License Manager Daemon (lmgrd)

The license manager daemon (lmgrd) handles the initial contact with the client applica-tion programs (ANSYS, etc.), passing the connection on to the appropriate vendor daemon(ansyslmd for ANSYS products). It also starts and restarts ansyslmd. Although not re-commended, FLEXlm permits redundant license manager daemons on three servermachines, allowing you to make your license available if any two of the three servermachines is running. Redundancy can be achieved with three-server redundant serversor by using multiple single-license servers. See Section 2.2.1: Redundant Server Optionsfor more information.

1.3.2. The Vendor Daemon (ansyslmd)

In FLEXlm, licenses are granted by running processes. There is one process for eachvendor who has a FLEXlm-licensed product on the network. This process is called thevendor daemon. The vendor daemon keeps track of how many licenses are checked out,and who has them. If the vendor daemon terminates for any reason, all users lose theirlicenses. The ANSYS vendor daemon is ansyslmd.

Client programs communicate with ansyslmd, usually through TCP/IP network commu-nications. The vendor daemon (ansyslmd) is started by the license manager daemon(lmgrd).

1.3.3. The License File

Licensing data is stored in a text file called the license file. The license file is created byANSYS, Inc. and is installed by the license administrator. It contains information aboutthe server machines and vendor daemon, and at least one line of data (called INCREMENTlines) for each licensed product. Each INCREMENT line contains a license key based onthe data in that line, the hostids specified in the SERVER line(s), and other vendor-specificdata.

The default location for the ANSYS license file (license.dat) is in the licensing directory.End users can override this location by setting the environment variable ANSYSLMD_LI-CENSE_FILE to point elsewhere. License files need to reside only on license servers.


Section 1.3: Explanation of Licensing Terms

1.3.4. The Application Programs

Application programs are software programs such as ANSYS, CFX, etc. ANSYS applicationprograms containing FLEXlm need to be able to communicate with the ANSYS licensemanager. All ANSYS, Inc. products use the same license manager.



Chapter 2: License Servers

2.1. What Are License Servers?

License administration is controlled by specific computers on the network called licenseservers. License servers monitor what products are being run, who is running them, andfrom what computer system. They grant or deny permission to run products. When anANSYS product begins, it requests permission to execute from a server. The server checksthe pool of available license tasks and grants the request only if the required tasks areavailable. For each request that is granted, the required license tasks are removed fromthe pool. As each ANSYS product execution ends, these license tasks are returned to thepool of available tasks.

The server machine or machines are designated by you--the end user. You have the optionof designating one server or three servers. In a one-server network, if the server machinegoes down, the licenses are no longer available for use until the server machine is backin service. In a three-server 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 oneserver, then that server is automatically the master server. In a three server environment,the order of the SERVER lines in the license file determines which server is the master.The order of the servers must match on all machines in a three server environment. The firstis the master, the second is the first backup, etc. If the order of the SERVER lines does notmatch on the three servers, then the servers will attempt to determine the master server;however, this attempt may not be successful. In a three-server network, if the masterserver is unavailable, then the first backup acts as the master.

You must make sure the order of the SERVER lines is consistent between redundantservers; otherwise, reconnections may fail.

2.2. Selecting License Servers

Before running any FLEXlm-licensed program using floating licenses, you will need toset up your license server machine (or machines). You must select which machine(s) willbe license servers, and provide the hostid and hostname of those machines to ANSYS,Inc. Use the Register License Server Information option of the ANSLIC_ADMIN utilityto generate the licserver.info file, which then needs to be forwarded to your ANSYSsales representative.


You need to select the computer systems that will act as servers before we can supplyyou with the licenses that are required to activate your licensed product(s). Informationabout the servers is used to generate the necessary license key(s).

Consider the following points when deciding which computer(s) will be used as server(s):

• All files used in conjunction with the license software must be located on a diskthat is physically local to the server computer(s).

• Computers must have a high-speed, reliable Ethernet connection.

• Computers that experience extremely high levels of network traffic or processinglags due to high CPU and/or I/O usage are poor candidates for servers.

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

• The license server must have a static IP address.

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

• You cannot use DHCP for license servers.

• If using a three-server network, we recommend that you choose three machinesthat are of the same platform type (that is, three HPs, three SGIs, etc.).

• If using a three-server network, we highly recommend that all three servers be onthe same subnet in the same physical location.

If these guidelines are not followed, the ability of the license software to perform consist-ently will be compromised.

Caution: Do not change the date on the license server machine. Doing so willprohibit the ANSYS product from running. Restoring the system to its originalstate prior to the date change may require significant effort.

2.2.1. Redundant Server Options

Throughout this document, we use the term “three-server network” when referring toredundant servers. Redundant server setup is a network configuration where multiplesystems are designated as license servers. Redundancy can be achieved in two ways:

• Three different systems can be selected to work together in tandem, wherebytwo of the three must be running at all times. These three license servers workfrom a single set of licenses.

Chapter 2: License Servers


• Any number of license servers can be running independently. The total numberof licenses is split between each license server. For example, if you are licensedfor 20 tasks of a certain product, and you have two license servers, each licenseserver will serve ten licenses. In this example, if one of these systems fails, onlyten licenses will be available.

We recommend the second option if your site requires redundancy. Be sure to reviewSection 2.2: Selecting License Servers for guidelines and special considerations whenchoosing license servers. Single license server networks are usually sufficient for mostsites.

2.2.2. Registering License Server Information

The Register License Server Information option of the ANSLIC_ADMIN utility createsa file named licserver.info in the licensing directory. The content of this file is generatedby prompting you for information about your company and you (the person runningthe utility). This is important so that we know to which of our customers this informationbelongs and to whom we may speak if we have questions about the data. The optionalso pulls necessary information from your license server (such as computer type, oper-ating system level, and hostid) and places it in the file. Create this file on each systemthat will be a license server. Return the licserver.info file(s) to your ANSYS sales repres-entative so that licenses can be supplied to you.


Section 2.2: Selecting License Servers

Chapter 3: License FilesAll ANSYS, Inc. programs use a single, common license file. The license file contains allsite-specific information required by FLEXlm. This information includes:

• Server names and hostids

• Vendor daemon name

• Feature information

In general, the license file must exist on every machine designated as a license server. Ifthe license file contains counted (also called "floating") licenses, you have to start the li-cense manager daemon (lmgrd) before you can use the application on Unix systems.On Windows systems, the license manager daemon is installed as a service named ANSYSFLEXlm License Manager.

You can use the License Wizard available from the ANSLIC_ADMIN utility to install orupdate a license file, specify the license server, and start or reread the license file. Thewizard will prompt you for the necessary information at each step.

3.1. Installing License Files

Use the Install the License File option of the ANSLIC_ADMIN utility to install the licensefile. The license file will be named license.dat and will be created in the licensing directory.If this file does not exist in the licensing directory or does not have the expected name,ANSYS products may not run.

If you are running in a three-server environment, the license file must reside on all threeservers and must match on all three servers.

If you make any changes to the license file, you must either restart the license manageror reread the license file. You can accomplish both tasks by using the ANSLIC_ADMINutility. Note that Install the License File is also the first step of the Run the LicenseWizard option.

3.2. Specifying the License Server and License Files

ANSYS products expect the license file to be named license.dat and reside in the licensingdirectory.The license file must reside on the license servers but does not have to be onthe machines where the ANSYS product is run. If you are running ANSYS products on


multiple machines, you have these options for making your license available on all theclient machines:

• Choose the Specify the License Server option of the ANSLIC_ADMIN utility tocreate a file named ansyslmd.ini in the licensing directory. Each server's specific-ation entry in this file must begin with SERVER=. This option is highly recommen-ded. The format of the ansyslmd.ini file created by ANSLIC_ADMIN follow.

On a single server:

SERVER=<port>@<host>

On redundant or multiple single servers on UNIX platforms:

SERVER=<port>@<host1>:<port>@<host2>:<port>@<host3>

Windows platforms use semicolons (;) instead of colons:

SERVER=<port>@<host1>;<port>@<host2>;<port>@<host3>

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

SERVER=1055@alpha1

This specification can also be set to the path and filename of a valid license file:

SERVER=<full path to the license file>

The order of the SERVER lines in the ansyslmd.ini file specifies the order in whichthe requested license will be granted.

• Set the ANSYSLMD_LICENSE_FILE environment variable to port@host, wherehost and port come from the SERVER line in the license file. The ANSYS defaultport number is 1055. This environment variable can also be set to the path andfilename of a valid license file. This option is NOT recommended.

• Set the LM_LICENSE_FILE environment variable to port@host. This environmentvariable can also be set to the path and filename of a valid license file. Be awarethat setting this environment variable can be disruptive to other software com-panies' products that use FLEXlm as their license manager. This option is NOT re-commended.

The license file path specified in the ANSYSLMD_LICENSE_FILE or the LM_LICENSE_FILEenvironment variables can be port@host, a directory name, a file, or a list of files separ-ated by colons on UNIX or semi-colons on Windows. If there is a directory name in thislist, all files named *.lic in that directory are used.

Chapter 3: License Files


You can only start the license manager on the server machine specified in the licensefile.

Note — If you are running redundant servers, you should have the license file(as well as the entire licensing directory) installed locally on each license server.If you do not, you lose all the advantages of having redundant servers, since thefile server holding these files becomes a single point of failure.

3.2.1. Setting the Path with an Environment Variable

ANSYS products expect the license file to reside in the licensing directory and be namedlicense.dat. You should rarely, if ever, want to specify where the license file is locatedwith an environment variable. However, you can change the license file location withthe ANSYSLMD_LICENSE_FILE or the LM_LICENSE_FILE environment variables.

Use the environment variable ANSYSLMD_LICENSE_FILE to set the location of the licensefile. For example, in the UNIX C shell:

% setenv ANSYSLMD_LICENSE_FILE license_file_path

Using the earlier example of a license server named alpha1, the line would look like this:

setenv ANSYSLMD_LICENSE_FILE 1055@alpha1

or

setenv ANSYSLMD_LICENSE_FILE /ansys_inc/shared_files/licensing/license.dat

The second example above would look only in the specified directory on the local ma-chine.

In the UNIX Korn and Bourne shells:

# ANSYSLMD_LICENSE_FILE=license_file_path# export ANSYSLMD_LICENSE_FILE

On Windows, use the Control Panel to change the system environment, setting AN-SYSLMD_LICENSE_FILE to license_file_path, where license_file_path is thefull path to the license file. This can also be a port@host setting, where port and hostare the port number and host name from the SERVER line in the license file. The ANSYSdefault port number is 1055.

With lmgrd and lmutil (lmstat, lmdown, etc.), the -c option overrides the setting of theANSYSLMD_LICENSE_FILE environment variable (UNIX only).


Section 3.2: Specifying the License Server and License Files

3.2.2. License Files Settings Precedence

License file settings have precedence in the following order:

1. ANSYSLMD_LICENSE_FILE environment variable

2. The FLEXlm resource file: ~/.flexlmrc (UNIX) or the Windows registry

3. LM_LICENSE_FILE environment variable

4. Settings in the ansyslmd.ini file in the licensing directory

5. The license file license.dat. Be aware that the license.dat file is not always used.If you have an ansyslmd.ini file with at least one SERVER line in it, the license.datfile will not be used.

3.3. License Files Format

License files usually begin with a SERVER line (or three SERVER lines for redundant servers)followed by a VENDOR line, followed by one or more INCREMENT lines.

You can modify only these data items in the license file:

• system host names on the SERVER line(s)

• Port numbers on the SERVER line(s)

• Vendor daemon file paths on the VENDOR line(s)

• Options file paths on the VENDOR line(s)

• Optional port numbers on the VENDOR line(s) (for firewall support only)

Long lines normally use the "\" line-continuation character to break up long lines. A spacecharacter must precede the line-continuation character.

Note — Everything else is used to compute the license key and should be enteredexactly as supplied. All data in the license file is case sensitive, unless otherwiseindicated.

3.3.1. SERVER Lines

The SERVER line specifies the hostname and hostid of the license server and the portnumber of the license manager daemon (lmgrd). Normally a license file has one SERVERline. Three SERVER lines mean that you are using redundant servers. License administrators



do not have the option of deleting SERVER lines from a license file because the hostidsfrom the SERVER lines are computed into the license keys on every INCREMENT line.

The format of the SERVER line is:

SERVER host hostid 1055

where:

host is the license server host name or IP address; a string returned by the UNIX hostnameor uname -n command. On Windows systems, ipconfig /all returns the host name. Thiscan also be an IP address (nnn.nnn.nnn.nnn format).

hostid is usually the string returned by the Display the License Server Hostid option ofthe ANSLIC_ADMIN utility.

1055 is the TCP port number to use. ANSYS' port number is 1055. This can be changed ifport 1055 is already in use on your system.

Example:

SERVER enterprise 0122345 1055

Note — If you change the port number, then you must also change the portnumber that is specified in the ansyslmd.ini file, or in the ANSYSLMD_LI-CENSE_FILE or the LM_LICENSE_FILE environment variables to match the portnumber specified in the SERVER line.

3.3.2. VENDOR Lines

The VENDOR line specifies the vendor daemon's name and path. lmgrd uses this line tostart the vendor daemon, and the vendor daemon reads it to find its options file. Theformat of the VENDOR line is shown below.

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

where:

ansyslmd is the name of the ANSYS vendor daemon.

vendor_daemon_path is the path to the executable for this daemon. This path is optional.ANSYS, Inc. does not supply this field because lmgrd will look for the vendor daemonansyslmd executable in the directory where lmgrd is located and all ANSYS productsinstall both of these daemons into the same directory.


Section 3.3: License Files Format

Note — If you do supply this path and the path includes spaces, enclose the entiredirectory path in double quotes, as in the following example:

VENDOR ansyslmd "c:\program files\ansys inc\Shared Files\Licensing \Intel"

options_file_ path is the full path to the end-user options file for this daemon. FLEXlmdoes not require an options file. The options file need not be specified on this line. Aslong as the options file ansyslmd.opt is located in the same directory as the license file(the licensing directory), the vendor daemon will automatically find and use it. The Editthe FLEXlm Options File option of the ANSLIC_ADMIN utility will put the options filein the correct directory location.

If the directory path includes spaces, enclose the entire directory path in double quotes,as in the following example:

VENDOR ansyslmd options="c:\program files\ansys inc\Shared Files\ Licensing\ansyslmd.opt"

port is the vendor daemon port number. Note: This is for firewall support only and isotherwise not recommended. In the following example, #### would be replaced withthe port number you choose:

VENDOR ansyslmd options=/ansys_inc/shared_files/licensing /ansyslmd.opt port=####

3.3.3. INCREMENT Lines

An INCREMENT line describes the license to use a product. The syntax of the INCREMENTline is:

INCREMENT feature ansyslmd feat_version exp_date #lic key [HOSTID=feat_hostid] [VENDOR_STRING="vendor_str"] [BORROW=n] [PLATFORMS="..."] [SUPERCEDE="..."] [ISSUED="..."] [START="..."] [ISSUER="..."] [NOTICE="..."] [OVERDRAFT=nnn] [DUP_GROUP=NONE|SITE|[UHDV]] [TS_OK]

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. Thespecified daemon serves this feature.



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

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

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

key is the encryption key for this INCREMENT line.

Many optional fields may follow. For example, the BORROW field indicates that borrowingis enabled for that license feature. n is the maximum number of hours that a license canbe borrowed. The maximum is 336 hours (two weeks).

See the FLEXlm End Users Guide for more information.

3.3.4. Sample License Files

A sample license file is shown here. This file is for 15 ANSYS Mechanical tasks and 12ANSYS DesignSpace tasks.

SERVER gagh 690daec6 1055VENDOR ansyslmdINCREMENT ansys ansyslmd 9999.9999 30-sep-2004 15 8C59A481BA50 \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2003 \ START=10-sep-2003INCREMENT dspi ansyslmd 9999.9999 30-sep-2004 12 424290D68B3D \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2003 \ START=10-sep-2003INCREMENT caewbpl3 ansyslmd 9999.9999 30-sep-2004 12 535301E79C4E \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2003 \ START=10-sep-2003INCREMENT deba ansyslmd 9999.9999 30-sep-2004 12 646412F80D5F \ VENDOR_STRING=customer:00012345 ISSUED=10-sep-2003 \ START=10-sep-2003

where:

• gagh is the hostname of the license server

• 690daec6 is the hostid

• 1055 is the port number

• ansyslmd is the vendor daemon

• ansys, dspi, caewbpl3, and deba are the features representing ANSYS Mechanicaland ANSYS DesignSpace.


Section 3.3: License Files Format

http://www.globetrotter.com/TOC.htm

• 9999.9999 indicates that the maintenance agreement is not applicable. Otherwise,this the highest supported build date for the product. For ANSYS only, you canview the build date by running ANSYS with the -v command option.

• 30-sep-2004 is the expiration date

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

• 8C59A481BA50, 424290D68B3D, 535301E79C4E, and 646412F80D5F, are encryptionkeys for ANSYS Mechanical and ANSYS DesignSpace, respectively

• customer:00012345 is the customer number

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

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

3.3.5. Recognizing an ANSYS License File

If you receive a license file and are not sure if it is an ANSYS license file, you can determineif it is by looking at the contents of the license file. If it is an ANSYS 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.

ANSYS, Inc. supplies some licenses for CFX products that use the CFX license manager.Those CFX license files are not compatible with the ANSYS license manager. You can re-cognize CFX license files in two ways:

• In the line beginning with the word DAEMON, the second field/item is CFDS.

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

Please use the CFX license manager utility to administer CFX licenses.

ANSYS, Inc. also supplies some licenses for ICEM CFD products that use the ICEM licensemanager. Those ICEM license files are not compatible with the ANSYS license manager.You can recognize ICEM license files in two ways:

• In the line beginning with the word VENDOR, the second field/item is ICEM_CFD.

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

Please use the ICEM license manager tools to administer ICEM licenses.



3.4. Product Variable Table

The following table shows all ANSYS, Inc. products and their associated feature name asused in the INCREMENT lines.

Table 3.1 Product/Feature Names for Licensed Products

Feature NamesProduct

ane3fl*ANSYS Multiphysics

ane3flds*ANSYS Multiphysics/LS-DYNA

ane3fl1*ANSYS Multiphysics 1



ane3fldp*ANSYS Multiphysics/DYNAPrepPost

ane3fl*, acfx_flotran_up-grade

ANSYS Multiphysics/CFX-Flo

ane3flds*, acfx_flotran_up-grade

ANSYS Multiphysics/CFX-Flo/LS-DYNA

ane3fldp*, acfx_flotran_up-grade

ANSYS Multiphysics/CFX-Flo/DYNAPrepPost

ansys*ANSYS Mechanical U

ane3*ANSYS Mechanical/Emag

anfl*ANSYS Mechanical/FLOTRAN

ansysds*ANSYS Mechanical/LS-DYNA

ane3ds*ANSYS Mechanical/Emag/LS-DYNA

anflds*ANSYS Mechanical/FLOTRAN/LS-DYNA

ansysdp*ANSYS Mechanical/DYNAPrepPost

ane3dp*ANSYS Mechanical/Emag/DYNAPrepPost

anfldp*ANSYS Mechanical/FLOTRAN/DYNAPrepPost

anfl*, acfx_flotran_upgradeANSYS Mechanical/CFX-Flo

anflds*, acfx_flotran_up-grade

ANSYS Mechanical/CFX-Flo/LS-DYNA

anfldp*, acfx_flotran_up-grade

ANSYS Mechanical/CFX-Flo/DYNAPrepPost

struct*ANSYS Structural U

struct1*ANSYS Structural1


Section 3.4: Product Variable Table




ste3*ANSYS Structural/Emag

stfl*ANSYS Structural/FLOTRAN

ste3fl*ANSYS Structural/Emag/FLOTRAN

structds*ANSYS Structural/LS-DYNA

ste3ds*ANSYS Structural/Emag/LS-DYNA

stflds*ANSYS Structural/FLOTRAN/LS-DYNA

ste3flds*ANSYS Structural/Emag/FLOTRAN/LS-DYNA

structdp*ANSYS Structural/DYNAPrepPost

ste3dp*ANSYS Structural/Emag/DYNAPrepPost

stfldp*ANSYS Structural/FLOTRAN/DYNAPrepPost

ste3fldp*ANSYS Structural/Emag/FLOTRAN/DYNAPrepPost

stfl*, acfx_flotran_upgradeANSYS Structural/CFX-Flo

ste3fl*, acfx_flotran_up-grade

ANSYS Structural/Emag/CFX-Flo

stflds*, acfx_flotran_up-grade

ANSYS Structural/CFX-Flo/LS-DYNA

ste3flds*, acfx_flotran_up-grade

ANSYS Structural/Emag/CFX-Flo/LS-DYNA

stfldp*, acfx_flotran_up-grade

ANSYS Structural/CFX-Flo/DYNAPrepPost

ste3fldp*, acfx_flotran_up-grade

ANSYS Structural/Emag/CFX-Flo/DYNAPrepPost

prf*ANSYS Professional

prfe3*ANSYS Professional/Emag

prffl*ANSYS Professional/FLOTRAN

prfe3fl*ANSYS Professional/Emag/FLOTRAN

emag*ANSYS Emag

emaghf*ANSYS Emag HF

emagfl*ANSYS Emag/FLOTRAN

flotran*ANSYS FLOTRAN

preppost*ANSYS PrepPost




prpostdy*ANSYS PrepPost/DYNAPrepPost

ansysul*ANSYS University Introductory

ansysuh*ANSYS University Intermediate

ansysrf*ANSYS University Advanced

aunivres*ANSYS University Research

dyna*ANSYS LS-DYNA

dynapp*ANSYS DYNAPrepPost

dynapc*ANSYS LS-DYNA PC

mpba*ANSYS Multiphysics Batch

meba*ANSYS Mechanical Batch

prba*ANSYS Professional Batch

stba*ANSYS Structural Batch

flba*ANSYS FLOTRAN Batch

e3ba*ANSYS Emag Batch

debachANSYS DesignSpace Batch Child

e3bachANSYS Emag Batch Child

flbachANSYS FLOTRAN Batch Child

mebachANSYS Mechanical Batch Child

mpbachANSYS Multiphysics Batch Child

prbachANSYS Professional Batch Child

stbachANSYS Structural Batch Child

caewbpl1, dspi, debaANSYS DesignSpace Entra

dsstruct, debaANSYS DesignSpace Structural

caewbpl3, dspi, debaANSYS DesignSpace

caewbplh, caetmpl, custg-ate

ANSYS Workbench SDK

cad2mesh, aimed, aiout-put, aiprism, aitetra, agppi

CFX-CAD2Mesh

cad2meshANSYS CFX-Mesh

acfx_flotran_upgradeANSYS CFX FLOTRAN Upgrade

acfx_anymoduleANSYS CFX Flo

acfx_anymoduleANSYS CFX-5 PrepPost




acfx_pre, acfx_solver,acfx_nolimit, acfx_parallel

ANSYS CFX-5 Basic Capability Solver

acfx_mfrANSYS CFX-5 Multiple Frames of Reference

acfx_multiphaseANSYS CFX-5 Multi-Phase Flows

acfx_combustionANSYS CFX-5 Reacting and Combusting Species

acfx_radiationANSYS CFX-5 Radiation Models

acfx_advanced_turbu-lence, acfx_turbu-lence_transition

ANSYS CFX-5 Advanced Turbulence Models

acfx_par_procANSYS CFX-5 Parallel Computing

acfx_pre, acfx_solveracfx_nolimit, acfx_mfr,acfx_multiphase,acfx_combustion, acfx_ra-diation, acfx_parallel,acfx_advanced_turbu-lence, acfx_turbu-lence_transition

ANSYS CFX-5 Full Capability Solver

acfx_postANSYS CFX-Post

acfx_turbogridANSYS CFX-TurboGrid

acfx_pre, acfx_solver,acfx_nolimit, acfx_mfr,acfx_multiphase,acfx_combustion, acfx_ra-diation, acfx_advanced_tur-bulence, acfx_turbu-lence_transition, acfx_par-allel, acfx_post

ANSYS CFX Academic Research

acfx_pre, acfx_solver,acfx_mfr, acfx_multiphase,acfx_combustion, acfx_ra-diation, acfx_advanced_tur-bulence, acfx_turbu-lence_transition, acfx_post

ANSYS CFX Academic Teaching Kit

aihexaICEM Hexahedral Mesher

aienv, aienvsubANSYS AI*Environment

aipicatANSYS ICEM CFD Direct Interface for CATIA V4

aipiideaANSYS ICEM CFD Direct Interface for I-DEAS




aipipsANSYS ICEM CFD Reader for Parasolid

aipiproANSYS ICEM CFD Direct Interface for Pro/ENGINEER

aipiseANSYS ICEM CFD Direct Interface for Solid Edge

aipiswANSYS ICEM CFD Direct Interface for SolidWorks

aipiugANSYS ICEM CFD Direct Interface for UG

batmesh, bmeshsubBatch Meshing Module

aiprism, aioutput, aioutcfdCFD Utilities Add-on for AI*Environment

concatiaANSYS Connection for CATIA V4

concatv5ANSYS Connection for CATIA V5

conparaANSYS Connection for Parasolid

conproeANSYS Connection for Pro/ENGINEER

consatANSYS Connection for SAT

conugANSYS Connection for Unigraphics

advmeshANSYS Advanced Structural Meshing Module

agppiANSYS DesignModeler

dsdxmANSYS DesignXplorer

femxstrANSYS DesignXplorer VT (-FXS)

caetmplCAE Templates

collengCollaboration Engine

dfatigueFatigue Module

wbunixWorkbench Interface for UNIX

int4nasInterface for Nastran

wbframeANSYS Workbench Framework

motionbANSYS Motion Basic

motionfANSYS Motion Full

aiemax, emaghf, freqsw,aiautmdl, aiautmsh, aiiges,aioutans, aitetra, aivis3

ANSYS Emax

aiemax, aiautmdl, aiautm-sh, aiiges, aioutans, aitetra,aivis3

ANSYS Emax PrepPost

emaxupp, aiautmdl, aiautm-sh, aiiges, aioutans, aitetra,aivis3

ANSYS University Emax PrepPost




emaxuppr, emaghf, aiautm-dl, aiautmsh, aiiges,aioutans, aitetra, aivis3

ANSYS University Emax PrepPost Research

solveugANSYS Solver for Unigraphics

dysmpANSYS LS-DYNA SMP

dydtmDrop Test Module for ANSYS LS-DYNA (-DTM)

freqswANSYS Frequency Sweep VT (-FS)

lsmat161LS-DYNA MAT_161

perfparParallel Performance for ANSYS ( -PP )

piautoinGeometry Interface for Autodesk Inventor

picatiaGeometry Interface for CATIA V4

picatv5Geometry Interface for CATIA V5

pimedeskGeometry Interface for Mechanical Desktop

rdparaGeometry Interface for Parasolid

piproeGeometry Interface for Pro/ENGINEER

rdacisGeometry Interface for SAT

pisoledgGeometry Interface for SolidEdge

pisolworGeometry Interface for SolidWorks

piugGeometry Interface for Unigraphics

pdmimaniMan PDM System

parameshANSYS ParaMesh

pmeshuniANSYS ParaMesh University

pmeshgeoANSYS ParaMesh Geometry Add-on

aioutput, aiiges, aiacis,aiedgeom, aioutcfd

ANSYS ICEM CFD Basic with Advanced GeometrySupport

aioutput, aiiges, aiacis,aipiug, aioutcfd

ANSYS ICEM CFD Basic with Unigraphics Direct Inter-face

aioutput, aiiges, aiacis,aipicat, aioutcfd

ANSYS ICEM CFD Basic with CATIA V4 Direct Interface

aioutput, aiiges, aiacis,aipipro, aioutcfd

ANSYS ICEM CFD Basic with Pro/Engineer Direct Inter-face

aioutput, aiiges, aiacis,aipiidea, aioutcfd

ANSYS ICEM CFD Basic with SDRC-IDEAS Direct Inter-face




aioutput, aiiges, aiacis, aip-isw, aioutcfd

ANSYS ICEM CFD Basic with SolidWorks Direct Inter-face

aioutput, aiiges, aiacis, aip-ise, aioutcfd

ANSYS ICEM CFD Basic with SolidEdge Direct Interface

aimed, aihexaANSYS ICEM CFD Hexa

aimed, aitetra, aiprism,ANSYS ICEM CFD Tetra/Prism

aimed, aiquadANSYS ICEM CFD Quad

aimed, aiglobalANSYS ICEM CFD Global

aimed, aiautmdl, aiautmshANSYS ICEM CFD Autohexa

aihexct5, aihexct5eANSYS ICEM CFD Hexa CAA V5 Based (for CATIA V5)

aiiges, aiacis, aimed, aitetra,aimshprt

ANSYS ICEM CFD Mesh Prototyper

aivis3, aiiges, aiacisANSYS ICEM CFD Environment for CART3D

aimed, aimshcrt, aiflowcrt,aiflowcrtp

ANSYS ICEM CFD Cart3D Product

aicabinANSYS ICEM CFD Cabin Modeler Add-on

aimed, aitetra, aiprism,aicabin

ANSYS ICEM CFD Cabin Modeler Stand-alone

aiic3m, aiic3msbANSYS ICEM CFD IC3M Add-on

aimed, aitetra, aihexa,aiic3m, aiic3msb,

ANSYS ICEM CFD IC3M Stand-alone

aimed, aicomakANSYS ICEM CFD Comak

aivis3ANSYS ICEM CFD Visula3 / PV3

aioptmshANSYS ICEM CFD OptiMesh

An * after a feature name indicates that an item is a product variable and can be usedon a stand-alone basis to start a product run.

Products listed here use the ANSYS license manager. ANSYS, Inc. does supply licensesfor ICEM CFD and CFX products not listed above; however, those licenses will use theICEM or CFX license manager. To determine if the license is for the ANSYS, ICEM, or CFXlicense manager, see Section 3.3.5: Recognizing an ANSYS License File.



3–16

Chapter 4: The ANSYS LicenseManagerIn order to run ANSYS products and then perform standard administration/operationtasks, you must make sure that the license manager is running.

4.1. License Manager Daemon

Most ANSYS products use a small program that runs in the background on the servermachine(s) to perform standard licensing operations. This program is called a daemon.The license manager daemon lmgrd and the vendor daemon ansyslmd perform licensemanager functions such as processing requests for clients. Both of these daemons mustbe running on the license server. On Windows systems, the license manager daemon isinstalled as a service named ANSYS FLEXlm License Manager.

4.1.1. Modifying License Manager Startup Options

Although we do recommend using the default settings when starting the license manager,you may find the need to change one of the options.

On UNIX systems, use the Modify Startup Options option of the ANSLIC_ADMIN utilityto modify the directory path to the license file and the directory path to the license.logfile.

You can also set FLEXlm's -2 -p or -local options. The -2 -p restricts the ability toshut down the license manager, reread the license file, or remove a client to a FLEXlmadministrator (who is by default root) or a member of the lmadmin group, if one exists.If the root administrator is not a member of this group, then he does not have permissionto use any of the above utilities. The -local option further restricts the ability to shutdown the license manager to only an administrator running on the same machine wherethe license manager was started. Both options are off by default. See the FLEXlm EndUsers Guide for more information on using these options.

This ANSLIC_ADMIN utility option writes an ansyslmd.ini file in the licensing directory.This file contains modified settings. If the file does not exist, the defaults are used. Thisoption will also update boot_ansflex with any changes. Follow the procedure inTable 4.1: “License Manager Automatic Startup Instructions” to make sure these newoptions are used at system boot.




Warning: The license.log file for each server should be located ona local disk. Writing to an NFS-mounted disk or remote file servercreates a situation where the license server(s) may fail. If the remotesystem containing the license.log file crashes, the license managerwould be unable to log license transaction data. This would createa fatal error condition.

On Windows systems, run the FLEXlm LMTOOLS utility in the ANSYS FLEXlm LicenseManager folder to configure the service. See the documentation provided with LMTOOLSfor more information.

4.1.2. Starting the License Manager Manually

The lmgrd program must be running on a quorum of systems designated to be servers.In a one-license server system, lmgrd must be started on that server and in a threeserver system, lmgrd must be started on at least two of the three servers before an ANSYSproduct can be run.

You can start the license manager manually via the Start the License Manager optionof the ANSLIC_ADMIN utility. This option starts the lmgrd license manager daemon,which in turn will automatically start the ansyslmd vendor daemon.

4.1.3. Starting the License Manager at System Boot Time

Table 4.1: “License Manager Automatic Startup Instructions” details the steps for eachUNIX hardware platform that must be performed on each license server to start the licensemanager automatically when the system is rebooted. You should substitute your platformname (see Supported Hardware Platforms) wherever you see <platform>. On Windowssystems, the license manager is set to start up automatically at system reboot.

Note — The procedure described in this section starts the license manager atboot time as root. It is not essential that the license manager be started by theroot 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, you need tomanually start the license manager by a non-privileged user each time the systemis rebooted.

Chapter 4: The ANSYS License Manager


Table 4.1 License Manager Automatic Startup Instructions

InstructionsPlatform

cd /ansys_inc/shared_files/licensing/<platform>cp boot_ansflex /sbin/init.dchmod 750 /sbin/init.d/boot_ansflexln -s /sbin/init.d/boot_ansflex /sbin/rc3.d/S90ansysflex

HP Alpha

cd /ansys_inc/shared_files/licensing/<platform>cp boot_ansflex /sbin/init.dchmod 750 /sbin/init.d/boot_ansflexln -s /sbin/init.d/boot_ansflex /sbin/rc2.d/S900FLEX

HP

cd /ansys_inc/shared_files/licensing/<platform>cat boot_ansflex >> /etc/inittab

IBM RS/6000

cd /ansys_inc/shared_files/licensing/<platform>cat boot_ansflex >> /etc/rc2.d/S40FLEXchmod 750 /etc/rc2.d/S40FLEX

SGI

cd /ansys_inc/shared_files/licensing/<platform>cat boot_ansflex >> /etc/rc3.d/S40FLEXchmod 750 /etc/rc3.d/S40FLEX

Sun, Fujitsu

cd /ansys_inc/shared_files/licensing/<platform>cat boot_ansflex >>/etc/rc.d/rc.local

Intel Linux

cd /ansys_inc/shared_files/licensing/<platform>cat boot_ansflex >>/etc/rc.d/boot.local

AMD OpteronLinux

Once the procedure is in place for starting the license manager automatically at boottime, reboot the system.

When the system comes back up, check to see that the license manager is running bytyping the appropriate ps command and looking for ansyslmd in the resulting displayunder the column labeled COMMAND.

For SYS V UNIX systems:

ps -ef

Next, check the license.log file in the licensing directory for error messages. This filecontains a history of ANSYS product activity across the network when this computer ischosen as the master license server by the licensing software. It will also contain start-up messages and possibly error messages.


Section 4.1: License Manager Daemon

4.1.4. Shutting Down the License Manager

You can shut down the license manager via the Shutdown the License Manager optionof the ANSLIC_ADMIN utility (see Chapter 6, “License Administration”). This option willshut down all three servers of a redundant setup, unless the license manager was storedwith the -local option.

The license manager must be running to be able to run ANSYS products.

Warning: Do not use kill -9 (on UNIX systems) to shut down the li-cense manager. Use the ANSLIC_ADMIN utility option or lmdown.

Chapter 4: The ANSYS License Manager


Chapter 5: The LicensingEnvironmentWe recommend that you set up your licensing environment after installing an ANSYSproduct. The tasks that we recommend performing include:

• Designating Server(s) for License Check-out

• Establishing User Privileges

• Creating the lmadmin Group

• Setting Up License Queuing

These tasks are described in the following sections.

5.1. Designating Server(s) for License Check-out

You are not limited to designating one set of license server machines for your network.You can have multiple single-server or three-server 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 servermachines (one or three) on the network.

To designate license servers, run the Specify the License Server option of the ANSLIC_AD-MIN utility on every machine where you installed an ANSYS product. With this option,you can specify single servers, multiple single servers, or redundant servers. Using thisoption creates or updates the ansyslmd.ini file in the licensing directory. We recommendusing this method for specifying your license server preference.

If you want to override the settings in the ansyslmd.ini file, you can do so by setting theANSYSLMD_LICENSE_FILE environment variable. This environment variable is usefulif you want to temporarily point to a different license server without disrupting the ma-chine's configuration.

If you set the ANSYSLMD_LICENSE_FILE environment variable on a three-server (re-dundant) system, specify all three systems, in the same order as the SERVER lines are listedin the license file. If you specify only the master and it is down, you could see a “LicenseServer Down” or “No License Found” message and the search for a license could fail. Joinredundant or multiple single server systems by separating the system names with colonson Unix and semicolons on Windows systems.


To have your license server preference known each time you log in, set the environmentvariable ANSYSLMD_LICENSE_FILE (both Windows and Unix systems). On Unix systems,place this environment variable in your login startup file (i.e., .cshrc file).

5.1.1. Sample Scenario

Suppose that you have a company with two departments, Design and Engineering. TheDesign Department has one license of ANSYS Mechanical and one license of DesignSpacewith the server DES1, and all users in the Design Department run on DES1. The seconddepartment, 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 statesSERVER=1055@DES1 for the Design Department and SERVER=1055@ENG1 for the Engin-eering Department, limiting users in each department to work only on their own server.If individual users in the Design Department need to run on the engineering server, ENG1,they could set the following environment variable:

setenv ANSYSLMD_LICENSE_FILE 1055@ENG1

For more information on using the license options file, please see Section 5.2: EstablishingUser Privileges.

5.2. Establishing User Privileges

To set specific user privileges with FLEXlm, you need to use the options file. The optionsfile allows you, the license administrator, to control various operating parameters ofFLEXlm:

• Allow or deny the use of features based on user, hostname, display name, group,etc.

• Reserve licenses based on user, hostname, display name, group, etc.

• Control the amount of information logged about license usage.

By using the options file, you can be as secure or as open with licenses as you like.

The default location of the options file, ansyslmd.opt, is in the licensing directory. If youhave a three-server system, the options file must match exactly on all three servers.

If you are using an options file, you must specify the pathname to the file on the VENDORline in the license file, unless it resides in the same directory as the license file, which isthe default when using the ANSLIC_ADMIN utility. On UNIX systems, the VENDOR linewould look like this for an options file named my.opt:

VENDOR ansyslmd options=/ansys_inc/shared_files/licensing/my.opt

Chapter 5: The Licensing Environment


On Windows systems, if the path has spaces in it, you must enclose it in quotes:

VENDOR ansyslmd options="c:\Program Files\Ansys Inc\Shared Files\Licensing\my.opt"

5.2.1. Editing the Licensing Options File

Use the Edit the FLEXlm Options File option of the ANSLIC_ADMIN utility to edit thelicense options file.

The maximum line length is 2048 characters. FLEXlm allows the "\" character as a continu-ation character in options file lines. You can include comments in your options file bystarting each comment line with a pound sign "#." Everything in an options file is casesensitive. Be sure that user names and feature names, for example, are entered correctly.

Some commonly used lines in the options file are shown below. See the FLEXlm EndUsers Guide for information on additional options.

Deny a user access to a feature.EXCLUDE

Deny a user access to all features served by this vendor daemon.EXCLUDEALL

Define a group of users for use with any options.GROUP

Define a group of hosts for use with any options.HOST_GROUP

Allow a user to use a feature.INCLUDE

Allow a user to use all features served by this vendor daemon.INCLUDEALL

Reserve licenses for a user.RESERVE

Sets the number of licenses for a BORROW feature that cannot beborrowed.

BORROW_LOWWATER

Excludes a user or predefined group of users from the list of whois allowed to borrow licenses for a BORROW feature.

EXCLUDE_BORROW

Includes a user or predefined group of users in the list of who isallowed to borrow a BORROW feature.

INCLUDE_BORROW

Changes the maximum period for which a license can be bor-rowed. The new period must be less than that specified in the li-cense file. If multiple MAX_BORROW_HOURS keywords appear inthe options file, only the last one is applied to the license feature.

MAX_BORROW_HOURS

When creating an options file, you must understand the options file precedence. INCLUDEand EXCLUDE statements can be combined in the same options file and control accessto the same features. When doing so, keep in mind the following:

• If there is only an EXCLUDE list, everyone who is not on the list will be allowed touse the feature.


Section 5.2: Establishing User Privileges



• If there is only an INCLUDE list, only those users on the list will be allowed to usethe feature.

• If neither list exists, everyone is allowed to use the feature.

• The EXCLUDE list is checked before the INCLUDE list; someone who is on bothlists will not be allowed to use the feature.

• EXCLUDE_BORROW supersedes INCLUDE_BORROW.

• Anyone not in an INCLUDE_BORROW statement is not allowed to borrow licenses.

Once you create an INCLUDE or EXCLUDE list, everyone else is implicitly "outside" thegroup. This feature allows you, as an administrator, the ability to control licenses withouthaving to explicitly list each user that you wish to allow or deny access to. In other words,there are two approaches; you can either give most users access and list only the excep-tions, or you can severely limit access and list only the those users that have accessprivileges.

The format for these keywords follow:

RESERVE number feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

INCLUDE feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

EXCLUDE feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

GROUP name list_of_users

INCLUDEALL {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

EXCLUDEALL {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

HOST_GROUP name host_list

BORROW_LOWWATER feature number

EXCLUDE_BORROW feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

INCLUDE_BORROW feature {USER | HOST | DISPLAY | PROJECT | GROUP | HOST_GROUP | INTERNET} name

MAX_BORROW_HOURS feature num_hours

Above, number is the number of tasks; feature is the license feature name (see Sec-tion 3.4: Product Variable Table for a list of license feature names for all ANSYS products);name is the user's login name or group; list_of_users is a blank-separated list of groupmember's login names; host_list is a blank-separated list of host names; and



num_hours is the number of hours for which a license can be borrowed, up to the limitspecified in the license file. On UNIX systems, DISPLAY requires the tty device name, andnot the DISPLAY environment variable name. Also, PROJECT refers to the LM_PROJECTenvironment variable.

Note — You can make groups arbitrarily large by listing the GROUP more thanonce; FLEXlm concatenates such entries.

You can also specify feature as follows:

feature:name=value

You can specify a feature by any of the following fields, found in the license file INCRE-MENT lines:

VERSION HOSTID EXPDATE KEY VENDOR_STRING ISSUER NOTICE dist_info user_info asset_info

If your license file has multiple INCREMENT lines of the same feature and any of thesefields (such as VENDOR_STRING and VERSION) differ between the INCREMENT lines, andyou are reserving licenses for this feature, FLEXlm will reserve the same number of licensesfrom each INCREMENT line. This can result in more licenses being reserved than expected.Specify the differing field to reserve licenses from a single INCREMENT line.

For example, the following license contains two INCREMENT lines that differ only by theversion date:

INCREMENT struct ansyslmd 2001.0331 permanent 1 AA1DE4A0E7BB \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2001 START=01-Jan-2001

INCREMENT struct ansyslmd 2001.0430 permanent 1 3D967A3ECF4E \ VENDOR_STRING=customer:12345678 \ ISSUED=01-Jan-2001 START=01-Jan-2001

If you create the following entry in the options file:

RESERVE 1 struct USER smith

then you will reserve two licenses, one from each INCREMENT line, for user smith.

To reserve only one license, create an entry that contains the differing information:

RESERVE 1 struct:VERSION=2001.0430 USER smith

For a complete list of license features, see Section 3.4: Product Variable Table.

For more information on the options file, see the FLEXlm End Users Guide.


Section 5.2: Establishing User Privileges


Note — The TIMEOUT and TIMEOUTALL options are not available with ANSYSproducts.

5.2.2. Sample Options File

In the following example options file, one license to execute ANSYS Mechanical is reservedfor user pat, three licenses for user lee, and one license for anyone on the computer withthe hostname of client3. In addition, user joe is not allowed to use the ANSYS Mechanicalprogram.

RESERVE 1 ansys USER patRESERVE 3 ansys USER leeRESERVE 1 ansys HOST client3EXCLUDE ansys USER joe

Note — In a three license server environment, the same options file must beplaced on all three systems. The options specified will not take effect until thelicense manager has been shut down and restarted or the license file has beenreread.

5.3. Other Environment Variable Settings

You can also use the following environment variables.

ANSYSLMD_LICENSE_FILECan be used to identify a license server or license file. If set, this specification is usedbefore any other license path information. See Section 3.2.2: License Files SettingsPrecedence for precedence information. The default port number assigned to ANSYS,Inc. is 1055. Therefore, if your server has the hostname alpha1 and the IP address of10.3.1.69, you can identify the server to use as 1055@alpha1 or [email protected].

LM_LICENSE_FILEAlso identifies the license server or license file. If set, this specification is used afterANSYSLMD_LICENSE_FILE setting. See Section 3.2.2: License Files Settings Preced-ence for precedence information. Unlike ANSYSLMD_LICENSE_FILE, this environ-ment variable is used for all FLEXlm licensed products and can be disruptive to othernon-ANSYS software.

ANS_FLEXLM_DISABLE_ENVUse this environment variable to exclude both the LM_LICENSE_FILE and AN-SYSLMD_LICENSE_FILE environment variable settings from the licensing path. Setto 1 to use this environment variable. Note that use of the ANS_FLEXLM_DIS-ABLE_DEFLICPATH environment variable overrides ANS_FLEXLM_DISABLE_ENV.



ANS_FLEXLM_DEBUGIf set, provides licensing debugging information. Possible settings are:

• 0 or not set: Indicates that no licensing debug information should be displayed.

• 1: Indicates that basic licensing debug information should be displayed.

• 2: Indicates that all licensing debug information should be displayed.

You will not want to keep this environment variable set all of the time because it willgenerate a large quantity of information.

For some ANSYS products, this information is sent to the file licdebug.out, whichresides in the directory specified by the TEMP environment variable, and is not dis-played on the screen. The directory specified by the TEMP environment variablemay be hidden on your system. To view the directory and file, click on My Computer.Choose Tools from the menu, and then click on Folder options. Click on the Viewtab and select Show hidden files and folders. Click OK.

ANS_FLEXLM_ENABLE_FLEX_DIAGEnables the use of FLEXLM_DIAGNOSTICS for ANSYS, Inc. products. See Chapter 7,“Troubleshooting” for more information on using this and the FLEXLM_DIAGNOSTICSenvironment variable.

FLEXLM_DIAGNOSTICSProvides additional levels of debugging information. You should set this environmentvariable only under the direction of Macrovision or ANSYS technical support. Formore information on this environment variable, see the FLEXlm End Users Guide.

ANS_FLEXLM_DISABLE_DEFLICPATHIndicates that the default license path should not be searched when determiningthe licensing path in the ANSYS product:

• Only ANSYSLMD_LICENSE_FILE environment variable setting is used.

• Settings in the ansyslmd.ini file and the license file in the licensing directorywill NOT be used.

ANS_FLEXLM_HBEATIdentifies the number of seconds between the FLEXlm heartbeats sent to the FLEXlmserver from an ANSYS product (Windows systems only).

• Minimum Value: 30 seconds (values between 0 and 30 are set to 30)

• Maximum Value: 120 seconds (values above 120 are set to 120)

• Default Value: 60 seconds


Section 5.3: Other Environment Variable Settings


ANS_FLEXLM_LMSGSIf set to a value other than 0 (zero), this environment variable indicates that all FLEXlmmessages should be returned in FLEXlm's long format rather than ANSYS, Inc.'s defaultshort. In some cases, this may provide more information to support staff. Long mes-sages are automatically displayed if the ANS_FLEXLM_DEBUG environment variableis set to 1 or 2 (even if the ANS_FLEXLM_LMSGS environment variable is not set).

ANS_FLEXLM_EXPWARN_DAYSBy default, you will be notified of the upcoming expiration of your license beginning30 days prior to the expiration date. Use this environment variable to change thenumber of days to any number between 7 and 90.

5.4. Creating the lmadmin Group

By default, root (on Unix) or administrator (Windows) has access to the options below.To allow other users to access these options, you need to create an lmadmin group oncomputers 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 func-tions.

Those functions requiring root or lmadmin group privilege include the following. Usethe utility shown in parentheses.

• Remove a Client (lmremove or ANSLIC_ADMIN)

• Stop the License Manager (lmdown or ANSLIC_ADMIN)

• Reread the License File (lmreread or ANSLIC_ADMIN)

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

5.4.1. HP AlphaServer (Compaq), HP, SGI, Sun, Linux

Add a line to the file /etc/group as follows:

lmadmin:*:nn:root,user1,user2,user3...usern

where nn represents any unique group number and user1, user2, user3, ..., usernrepresent a list of n users in the group.

5.4.2. IBM RS/6000

Use smit to create an lmadmin group and add users to this group.



5.5. Setting Up License Queuing

The License Queuing option allows an ANSYS process to wait (queue) for an available li-cense in the event all licenses are checked out. Activate this option by setting the envir-onment variable ANSWAIT to one of the following values:

1 - queue everything2 - queue only primary configured tasks (interactive or batch)3 - queue only interactive runs (including Connection product features)4 - queue only primary configured tasks in interactive runs

A primary configured task is required to run a product and is the very first license checkedout, such as ANSYS Multiphysics, ANSYS Structural, etc. Advanced or transient tasks, suchas Performance Parallel for ANSYS or the Geometry Interface products are not consideredprimary configured tasks.

The example here will queue licenses for all products in both interactive and batch mode:

UNIX csh (C) Shell

setenv ANSWAIT 1

UNIX ksh (Korn) or sh (Bourne) Shells

ANSWAIT=1;export ANSWAIT

On Windows systems, use the Control Panel to set the ANSWAIT environment variable.

The following message will appear in the output if your process is waiting (queued) foran available ANSYS license:

Maximum number of licenses already checked out for feature name.Server host1: Queuing for 1 license(s) of feature name

If the ANSWAIT environment variable is not set, then the ANSYS process will terminatewith the following message in the event all ANSYS licenses are checked out. This is thedefault condition.

Licensed number of users already reached (-4,132)

The License Queuing option may not be available on all products.


Section 5.5: Setting Up License Queuing

5.6. Using License Borrowing

License borrowing allows a user to take a license for use outside of the company facility,such as for an engineer to take a license home on his laptop. Before users can take ad-vantage of license borrowing, you need to set up the borrowing environment.

License borrowing is available only on Windows systems.

5.6.1. Setting up License Borrowing

To use license borrowing, you must have license keys that specify borrowable licenses.

You can use the optional BORROW options file settings to further control borrowing atyour site. To use these settings, you must first specify which users are allowed to borrowlicenses by adding an INCLUDE_BORROW group to the options file. Any user not in theINCLUDE_BORROW group will not be allowed to borrow licenses. You may also wish toset up an EXCLUDE_BORROW group to prevent specific users from borrowing licenses.

You can also limit the number of licenses that can be borrowed from your total pool ofborrowable licenses. Set the BORROW_LOWWATER option in the options file to thenumber of licenses that cannot be borrowed. For example, if you have 15 licenses totaland want to limit the number that can be borrowed to 5, set BORROW_LOWWATER=10.

The maximum number of hours a license can be borrowed is defined in your license file(default is 336 hours, or two weeks). You can set that limit lower for your users by settingthe MAX_BORROW_HOURS option in the options file. MAX_BORROW_HOURS cannotexceed the limit specified in your license file.

In addition, we recommend that you not use the -2 -p option, available via the ModifyStartup Options selection of the ANSLIC_ADMIN utility. Doing so will prevent usersfrom returning borrowed licenses early.

5.6.2. Running the License Borrowing Utility

To run the license borrowing utility, you must be running on a Windows system connectedto a network, and you must have borrowable licenses. For more information about bor-rowable licenses, please contact your ANSYS sales representative.

1. Launch the license borrowing utility: Start>Programs>ANSYS FLEXlm LicenseManager>ANSLIC_ADMIN. Select Run the ANSYS Borrow Utility.

2. Select the product(s) you want to borrow, including any add-on features orgeometry interfaces.



3. Specify the return date (defaults to 72 hours or 3 days).

4. Click Borrow.

5. Disconnect from the network. Note that even when you've disconnected fromthe network, you must still run the products from the same account you used toborrow the licenses. For example, if you use a network account to borrow the li-censes, you cannot then run from a local account.

If you keep a license for the full amount of time, there is no need to check the licenseback in. Your borrowed license will simply expire at the end of the borrow period, andthe license will be released into 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 license borrowing utility: Start>Programs>ANSYS FLEXlm LicenseManager>ANSLIC_ADMIN. Select Run the ANSYS Borrow Utility.

3. Select the Return tab. Indicate which license(s) you are returning and click Return.

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 toborrow the licenses originally.

Some multi-feature products include other products and/or add-on features. The utilitywill automatically check out any such included products or add-on features. If you borrowone of these multi-feature products and then click on the Return tab, you will see theproduct you selected, as well as any other products and add-ons that it includes. If youreturn a multi-feature product early, these products and add-on features will also be re-turned.


Section 5.6: Using License Borrowing

5–12

Chapter 6: License Administration

6.1. Using the ANSLIC_ADMIN Utility

This chapter explains some procedures that you need to perform to administer licenses.You can use the ANSLIC_ADMIN utility to perform most day-to-day licensing procedures.The functionality offered by ANSLIC_ADMIN is discussed in this section. Some optionsmay apply to only UNIX or to Windows systems. For advanced operations, please see theFLEXlm End Users Guide.

To run ANSLIC_ADMIN on Windows, choose Start>Programs>ANSYS FLEXlm LicenseManager>ANSLIC_ADMIN utility. To run the utility on UNIX, type the following:

/ansys_inc/shared_files/licensing/lic_admin/anslic_admin

You do not need system administrator privileges to run the ANSLIC_ADMIN utility;however, you must have system administrator privileges to run certain options. To usethe utility, select an action from the list of buttons on the left.

The status of your machine appears on the bottom left-hand side of the screen, in theMachine Name status area. The machine can be a client (any machine with no valid li-cense file installed is considered a client) or a license server. If a license server, the statuscan be running or not running. The status will update automatically when the machine'sstatus changes. On Windows systems, if the machine is a client and you want to convertit to a server, you will need to use the installation media and install the license managerfollowing the instructions in the ANSYS Installation and Configuration Guide for Windows.

The right side of the utility usually displays a log of your session activities (the sessionlog). The reporting options will also display information in this area. Use the buttons atthe bottom to clear the session log or to write the log out to a file. If you need to contactTechnical Support, you will need to send them this log file.

For some items, such as Display the License Status, the right-hand window convertsto a status window showing the requested information. Use the buttons underneaththis status area to return to the session log, to write the status information to the sessionlog, or to write the status information directly to a file.

The ANSLIC_ADMIN utility consists of the following options:

• Register License Server Information

• Display the License Server Hostid



• Run the License Wizard

• Install the License File

• Start the License Manager

• Stop the License Manager

• Reread the License File

• Specify the License Server

• Edit the FLEXlm Options File

• Modify Startup Options (UNIX only)

• Remove a Client License

• Run the ANSYS Borrow Utility (Windows only)

• View Status/Diagnostic Options -- includes the following options:

– Display the License Status

– Display the Customer Number

– View the License File

– View the License Log File

– Gather Diagnostic Information

From the Uninstall menu (UNIX only), you can select Uninstall the License Manager.See Section 6.1.14: Uninstall the License Manager for more details on uninstalling the li-cense manager.

From the Help menu, you can select:

• View the ANSLIC_ADMIN Help

• View the FLEXlm End Users Guide

• About

To exit the ANSLIC_ADMIN utility, choose File>Exit.

6.1.1. Register License Server Information

Use this option to register your license server information with ANSYS, Inc. When youchoose this option, you will be prompted to supply your customer number (optional),



company name, your name, e-mail address, etc. This utility also obtains informationabout your system, such as hostname, hostid, hardware platform, operating system level,and current date. In addition, this utility requires information about the type of licenseserver machine. In the case of a three-server system, you must supply the server inform-ation on each server.

The utility places the information it gathers into a file named licserver.info. By default,this file is written to the home directory; it will also create it in the licensing directory.You can browse to a directory other than the home directory. You must forward the file,created on each license server, to your ANSYS sales representative.

If you are running this utility on a Windows laptop system, you should disconnect fromthe docking station before running this option so that the laptop's hostid informationis used and not the docking station's.

6.1.2. Display the License Server Hostid

Use this option to obtain and display the hostid of the system on which you are currentlyrunning. Selecting this option runs the FLEXlm utility lmhostid. To write this informationout to a file, click the Create File button. By default, the file is named ansysid.machine-name.txt, although you can change the filename if you wish.

6.1.3. Run the License Wizard

This option is used for license server machines only.

This wizard walks you through the process of installing or updating a license file, specifyingthe license server(s) (which updates the ansyslmd.ini file), and starting the licensemanager or rereading the license file. The wizard will prompt you for the necessary in-formation at each step. You should use this option when you receive a new license fileas it will walk you through the necessary steps to activate the new license.

You can perform each of these steps individually using the separate options on the AN-SLIC_ADMIN utility.

6.1.4. Install the License File

Use this option if you received a new license. This utility creates the license file, calledlicense.dat by default, in the licensing directory. The license file contains your licensinginformation and allows you to run ANSYS, Inc. products.


Section 6.1: Using the ANSLIC_ADMIN Utility

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

2. Select this option from the ANSLIC_ADMIN utility.

3. Browse to the file. If you do not already have a license file, the information fromthis temporary file will be used to create the license file. If you do have an existinglicense file, the existing file will be renamed to license.dat.old.

In a three-server setup, you must use this option on each license server.

Warning: Do not save license files in Microsoft Word format.

If the license manager is running when you add or update a license, you must restart thelicense manager or reread the license file for the new file to take effect.

6.1.5. Start the License Manager

Use this option to start the license manager. The license file must exist prior to startingthe license manager. The license manager must be running to run an ANSYS, Inc. product.

The file license.log in the licensing directory contains a history of licensing activity acrossyour network since the last time the license manager was started. It also contains startupmessages and possibly error messages. This option will save any existing license.log fileto license.log.old prior to starting the license manager.

Note — In a three-server environment, you may see a delay in starting the licensemanager until two of the three servers are running. Do not press the Start theLicense Manager button more than once for the same server.

6.1.6. Stop the License Manager

Use this option to shut down the license manager. This option will shut down the licensemanager on all machines listed in the license file. You will be asked to confirm that themachine(s) should be shut down. Remember that the license manager must be runningin order to run an ANSYS, Inc. product. Before shutting down the license manager, checkthat no ANSYS, Inc. product processes are currently running. Any processes that arerunning will be terminated when you shut down the license manager.

Warning: Do not use kill -9 (on UNIX systems) to shut down the li-cense manager. Use the ANSLIC_ADMIN utility option or lmdown.



Note — In a three-server environment, you may see a delay in stopping the licensemanager. Do not press the Stop the License Manager button more than oncefor the same server.

6.1.7. Reread the License File

Use this option when the license manager is already running and you have updated thelicense file or the license options file. If you update the license file or the license optionsfile, you must run this option for the changes to take effect. Otherwise, the license man-ager will not be aware of the changes until it is stopped and restarted.

6.1.8. Specify the License Server

Use this option to set the license server(s). This option lists, adds, deletes, or reordersentries in the ansyslmd.ini file with the server specification.

To add a server:

1. Click Add Server Specification.

2. Enter the host name(s) of your license server(s) and the TCP/IP port number. TheANSYS, Inc. default port number is 1055.

3. Click OK.

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

Entries in this file tell ANSYS, Inc. products which license server(s) to query to find a validlicense. Using this option allows all users at your site to use this setting without havingto individually set environment variables (ANSYSLMD_LICENSE_FILE and/or LM_LI-CENSE_FILE) to find the license file. It also eliminates the need to have a copy of the li-cense file on every system at your site.

Set the license server on all systems running an ANSYS, Inc. product.

The order that the SERVER lines are listed in the ansyslmd.ini file dictates the order inwhich the license request is granted. To reorder the entries in the list, highlight a serverand use the Move up or Move down buttons.

6.1.9. Edit the FLEXlm Options File

Use this option to edit the license options file ansyslmd.opt, which resides in the licensingdirectory. The license options files must match on all three systems if you are using re-



dundant systems. The options file allows you, the license administrator, to control variousoperating parameters of FLEXlm. For more information on using the license options file,see Section 5.2: Establishing User Privileges. Restart the license manager or reread thelicense file for changes to take effect.

6.1.10. Modify Startup Options

Use this UNIX-only option to modify your license manager startup options. Licensemanager startup options that you can modify include the license file path and the licenselog file path. You can also specify the -2 -p or -local options (not recommended ifyou will be using license borrowing). See Section 4.1.1: Modifying License ManagerStartup Options for more information on modifying these license manager startup options,or see the FLEXlm End Users Guide.

6.1.11. Remove a Client License

You may need to free a license when a licensed user was running an ANSYS, Inc. producton a node that subsequently crashed. This situation will sometimes cause the license tobecome unusable. Free the license to allow the license to return to the pool of availablelicenses. Only those with FLEXlm administrative privileges (UNIX) or administrative priv-ileges (Windows) can use this procedure because removing a user's license can be dis-ruptive.

You will be prompted for the following information:

• feature name

• user name

• host name

• display

If you are not sure of any of the above items, run the Display the license status optionto obtain the correct information. This option allows you to remove a client only fromthe license server machine on which the license is checked out.

A client must be running at least two minutes before you can remove it. If you attemptto remove a client in less than two minutes, you will get an error.

The license removal is not immediate.




6.1.12. Run the ANSYS Borrow Utility

This Windows-only option launches the ANSYS License Borrowing utility. From there,you can select licenses for use outside of the company facility. This feature is useful forsituations such as allowing an engineer to take a license home on his laptop. This optionis available only on Windows, and only if you have borrowable licenses. For more inform-ation on license borrowing, see Section 5.6: Using License Borrowing. For more informa-tion on borrowable licenses, contact your ANSYS sales representative.

6.1.13. View Status/Diagnostic Options

The following reporting options are available:

• Display the License Status

• Display the Customer Number

• View the License File

• View the License Log File

• Gather Diagnostic Information

When you select one of these options, the data will appear in the log area on the rightside of the utility. Display the Customer Number appends the customer number to thesession log itself; the other options create their own display in the log area. Each optionis explained in the following sections.

6.1.13.1. Display the License Status

Use this option to see the status of licensing activity. All features are displayed in thestatus window, along with the users of those features. You can append this informationto the session log or write it directly to a file. This option displays information based onthe same license path rules as ANSYS, Inc. products, taking into account the settings inthe ANSYSLMD_LICENSE_FILE and LM_LICENSE_FILE environment variables and theansyslmd.ini and license files. Setting the ANS_FLEXLM_DISABLE_ENV orANS_FLEXLM_DISABLE_DEFLICPATH environment variables will affect the informationdisplayed by this option.

6.1.13.2. Display the Customer Number

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



6.1.13.3. View the License File

This option displays the contents of your current license file in the reporting area. Youcan append this information to the session log or write it out to a separate file. Do notuse this option to create a new license file. The Write to File option here will create atext file that includes extraneous information that is not valid in a license file, and shouldbe used only to create a file for reference purposes.

6.1.13.4. View the License Log File

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

6.1.13.5. Gather Diagnostic Information

Use this option to run the ansys_pid utility, which queries the system for informationthat may be useful for troubleshooting certain problems. This operation may take a fewminutes. You can append this information to the session log, or you can write it out dir-ectly to a file.

6.1.14. Uninstall the License Manager

Use this UNIX-only menu option to remove the entire ANSYS, Inc. license manager install-ation from your system. To use this option, you must be logged in as root or superuser.

You will be asked to verify that the license manager should be uninstalled from this sys-tem.

The contents of the licensing directory will be deleted. Also, if the license manager isrunning, it will be shut down.

On Windows systems, you can uninstall the license manager using the LMTOOLS utility.Before proceeding with the following steps, make certain that there are no ANSYS, Inc.products on this machine or any other machines on the network that rely on these ANSYSlicensing components.

Skip these steps if the machine does not have the ANSYS FLEXlm License Manager in-stalled. Perform these steps ONLY if this is a Windows system and is an ANSYS FLEXlmLicense Manager server machine:

1. Use the ANSLIC_ADMIN to stop the license manager.



2. In the ANSYS FLEXlm License Manager program folder, click on the FLEXlmLMTOOLS utility.

3. Select the Configure Services tab and highlight ANSYS FLEXlm License Manager.Click on the Remove Service button.

4. Exit the LMTOOLS utility.

On all Windows systems, follow these steps. For more information on performing any ofthe following tasks, please refer to your Windows system documentation.

1. Delete the \Licensing subdirectory located under \Program Files\ANSYSInc\Shared Files.

2. Remove the ANSYS FLEXlm License Manager program folder from the Startmenu.

3. Remove the ANSYSLIC_DIR environment variable.

6.2. Using the LMTOOLS Utility

The LMTOOLS utility is a Windows-only license administration tool. With the LMTOOLSutility, you can start, stop, and reconfigure the license manager, get information such ashostids, get server status, and more. To run this utility, click on FLEXlm LMTOOLS Utilityin the ANSYS FLEXlm License Manager program folder. For more information on theoptions available, please refer to the online help provided with the LMTOOLS utility.

Note — Do not change the license file or the license log file path via the LMTOOLSutility on 64-bit Windows system. Doing so will result in unexpected licensingbehavior.


Section 6.2: Using the LMTOOLS Utility

6–10

Chapter 7: TroubleshootingThis chapter lists problems and error messages that you may encounter while settingup licensing. After each situation description or error message is the user action requiredto correct the problem.

For more troubleshooting information, see the FLEXlm End Users Guide.

7.1. Getting Additional License Debug Information

Use the following suggestions to display or generate additional error messages and de-bugging information.

• Set the ANS_FLEXLM_DEBUG environment variable to display debugging inform-ation. You can choose from two levels of detail: 1: basic licensing debugging in-formation is displayed and 2: All licensing debugging information is displayed.The default is to show no licensing debugging information. You will not want tokeep this environment variable set all the time because it will generate a largequantity of information.

This information is sent to different locations, depending on the product. Possiblelocations are:

– The licdebug file in the directory specified by the TEMP environment variable.In this case, the information is not displayed on the screen. The licdebug file-name will vary depending on the product:

→ ANSYS CFX: licdebug.cfx.90.out

→ ANSYS ICEM (includes AI*Environment and ANSYS Emax): licde-bug.icem.90.out

→ ANSYS Workbench: licdebug.wb.90.out

→ ANSYS DesignModeler: licdebug.dm.90.out

→ ANSYS Part Manager (used for ANSYS Workbench Geometry Interfaces):licdebug.pm.90.out

The directory specified by the TEMP environment variable may be hidden onyour system. To view the directory and file, click on My Computer. ChooseTools from the menu, and then click on Folder options. Click on the View taband select Show hidden files and folders. Click OK.



– The current working directory

– Standard ANSYS output

Table 7.1 ANS_FLEXLM_DEBUG Output Locations

Standard AN-SYS output

Current Work-ing Directory

TEMP locationProduct

XANSYS

XANSYS Workbench

XANSYS DesignModeler

XANSYS Part Manager

XANSYS CFX (Windows)

XANSYS CFX (UNIX)

XAI*Environment (Windows)

XAI*Environment (UNIX)

XANSYS Emax (Windows)

XANSYS Emax (UNIX)

• Set the ANS_FLEXLM_LMSGS environment variable to control whether errormessages appear in long or short format. By default, when theANS_FLEXLM_DEBUG environment variable is NOT set, ANSYS, Inc. displays errormessages in short format. Set this environment variable to a value other than 0(zero) to display the long format. Long messages are automatically displayedwhen the ANS_FLEXLM_DEBUG environment variable is set, even ifANS_FLEXLM_LMSGS is not set.

• Set the ANS_FLEXLM_ENABLE_FLEX_DIAG environment variable to 1 to enablethe use of FLEXLM_DIAGNOSTICS for ANSYS, Inc. products.

• Set the FLEXLM_DIAGNOSTICS environment variable to a value of 1, 2, or 3,where 3 provides the most debugging information. You should set this environ-ment variable only under the direction of Macrovision's technical support. Formore information on this environment variable, see the FLEXlm End Users Guide.

If after following these suggestions, the resulting debug information does not makesense, try these suggestions:

• Confirm that the license manager was restarted or the license file was reread afterany changes were made to the license file. If the user did not make any changesto the license file for the server, check the date/time that it was last changed. Get

Chapter 7: Troubleshooting



the relevant path information from the debug output. Also, confirm that the samepath is being used.

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

• If the user put a license key in a license file but is not seeing it even after restartingthe license manager, confirm that the correct license file is being used to start thedaemon/service. In this case, neither the client application nor the daemon/serviceis using the changed file.

• If the license.dat file is at the end of the path and it is a license file that uses thelicense manager daemon/service, then confirm that the license manager is startedwith the same path as the license.dat file's path. The license manager could belooking at one file in the client application but the license manager daemon/servicewas started with another file.

7.2. Using the ansys_pid Utility

You can use the Gather Diagnostic Information option of the ANSLIC_ADMIN utilityto query the system for various pieces of information that may be needed fortroubleshooting certain problems. The underlying utility, ansys_pid, collects informationabout the system as well as about ANSYS licenses.

ansys_pid sends all of the information that it collects to the log area. At times it may benecessary to provide the information for technical support. Use the Write to File buttonat the bottom of the ANSLIC_ADMIN to write a file. Then forward the file to the appro-priate person.

7.3. Problem Situations

This section describes problems you may encounter when setting up licensing or runningan ANSYS product, 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 that are listed below. Perform thetests in the order that they are listed.

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


Section 7.3: Problem Situations

2. Verify that TCP/IP is installed and configured correctly. Verify that the IP addressis static. See Section 1.2: Communications Requirements for information aboutconfiguring TCP/IP.

3. Verify that the hostid has not changed. If the hostid has changed, you must obtaina new license.

In a three-server environment, you could also see the following message when you startthe first of the three servers:

***Attempting to start the license manager...

Start the License Manager status:

The license manager failed to start.

You may examine the license log file for more information or possible errors (byclicking the 'View Status/Diagnostic Options' button). Additionally, you can referencethe Troubleshooting section in the ANSYS Licensing Guide for more details.

NOTE: The currently-installed license file is a three-server license file. With three-server license files, the license manager will not fully start until at least two of thethree license servers are running.

This message results when a quorum of servers (2 of the 3) are not yet started. Startthe other servers, or verify that they are already started. When at least two of thethree servers are started, you will see the status window of this server change to reflectthat it is now running. Do NOT attempt to stop the license manager by pressing theStop the License Manager button.

If you verify that at least two servers are started and you still see this message, andthe status window does not update to running in a reasonable time, follow the threesteps noted above in Section 7.3.1: License Manager Will Not Start.

Caution: When you see this message, do NOT press the Start the LicenseManager button again. Doing so will cause another copy of the lmgrd licensemanager daemon/service to start without the corresponding ansyslmdvendor daemon/service and will require you to carefully remove the extraANSYS lmgrd manually.



7.3.2. License Manager Will Not Stop in a Three-Server Envir-onment

When you attempt to stop the license manager in a three-server environment, the licensemanager does not stop immediately. You will see a message stating that the currently-installed license file is a three-server license file. With three-server license files, the licensemanager could take 60 seconds or longer to successfully stop. Wait at least 60 seconds.When the license manager has successfully stopped, the status window will show thatit is stopped.

7.3.3. Unable to Check Out Licenses

If the license manager appears to start but you cannot check out any licenses, performthe tests that are listed below. Perform the tests in the order that they are listed.

1. Verify that the license.log file exists in the licensing directory on the licenseserver machine(s). Note that license.log in the licensing directory is the defaultlocation of this file. To see whether the file's location has been changed, chooseModify Startup Options on the ANSLIC_ADMIN utility on UNIX. On Windows,run the FLEXlm LMTOOLS utility in the ANSYS FLEXlm License Manager folderand choose the Configure Services tab. Check the name in the "License log file"field. If the license.log file does not exist or has zero length, verify the writepermissions on the directory and file.

2. On the license server machine(s), review the license.log file for error messages.See the remainder of this chapter for a list of possible errors and their resolutions.

7.3.4. Jobs Abort When License Manager Goes Down in Three-Server Environment

If you are running in a three-server environment and ANSYS program jobs abort whenone of the license managers goes down, perform the tests that are listed below. Performthe tests in the order that they are listed.

Note — If this problem persists after you perform the steps below, you may wantto consider switching to a single-server environment.

Note — When using a three-server environment, we strongly recommend thatall three servers be on the same subnet. If this is not the case, you should considerusing three machines which are in the same physical location and are on thesame subnet.


Section 7.3: Problem Situations

1. Verify that two of the three license managers are still running. Use the ANSLIC_AD-MIN utility (Display the License Status). If the license manager is not alreadyrunning on all servers, start it on all of them.

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

3. Check to see whether the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILEenvironment 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 licensingdirectory. The hostnames of all three servers must appear in these files and inthe same order. If the license files are not the same on all three servers, makecorrections 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 necessary and restart the license manager.

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

7. Verify that the license manager and utilities are installed locally on each licenseserver. If not, run the installation from the product CD and choose to install thelicense server only. See the installation manual for your product and platformfor more information.

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

9. Check the license.log file for error messages. See the remainder of this chapterfor a list of possible errors and their resolutions.

7.3.5. Ethernet Address Shows All Zeroes

On Windows 2000 systems only, if the ethernet address shows 12 zeroes when you viewit (using the FLEXlm LMTOOLS utility in the ANSYS FLEXlm License Manager folder onWindows), the network cable has been removed. To correct, re-connect the networkcable.

7.3.6. Licensing Log File Not Created

On Windows, if the license manager starts and licenses can be taken from the licenseserver, but the licensing log file is not written, check the Administrator account. Verifythat the Administrator (as well as the individual user) has write privileges to the directorywhere the log file is to be written.



7.3.7. Queuing Does Not Work

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

• The license manager is down. In this case, use ANSLIC_ADMIN to start the licensemanager.

• The hostname is mistyped in the ansyslmd.ini file or the ANSYSLMD_LI-CENSE_FILE or LM_LICENSE_FILE environment variables. If so, correct the nameand retry.

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

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

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

• The License Queuing option may not be available on all products.

7.3.8. The FLEXlm Utility lmcksum May Give Misleading In-formation

The FLEXlm utility lmcksum may give misleading information. Do not rely on its resultsto verify the accuracy of your license file.

7.3.9. The Launcher is Excessively Slow to Start

If the launcher takes an excessively long time to startup (Windows only), make sure thehostnames in the ansyslmd.ini file and in the ANSYSLMD_LICENSE_FILE and theLM_LICENSE_FILE environment variables are typed correctly and that the hosts specifiedby the hostnames exist. Also verify that the port number is correct.

7.4. Licensing-Related Launcher Error Messages

Some messages that you see from the launcher are related to product licensing. Thesemessages follow. For additional launcher error messages, see the Troubleshooting sectionof the ANSYS Installation and Configuration Guide for your platform.


Section 7.4: Licensing-Related Launcher Error Messages

***Unable to retrieve any valid licenses for <simulation environment.> Pleasesee the ANSYS, Inc. Licensing Guide's Troubleshooting section for more information.

***Required <Product> license was not found. Therefore, simulation environmentsimulation environment will not be available.

***Could not initialize FLEXlm licensing.

***Error: No license path found.

***No licensed products found.

***No products available for this simulation environment.

***Unable to load profile <name> because license <product> is not available.However, simulation environment <simulation environment> was selected.

***License list unavailable. [ANSYS Workbench Products Only]

If you see any of the above messages (or any similar licensing error messages), thelauncher has encountered an error while trying to find or retrieve a license. Possiblecauses are the license manager is not running, no licenses were found, or the existinglicenses have expired. Also check the license manager log file in the licensing direct-ory. If any of these messages appear, perform the tests that are listed below in theorder presented:

1. Use the ANSLIC_ADMIN utility to verify that the license manager is running.Choose Display the License Status. If you are running in a three-server en-vironment, verify that two of the three servers are running.

2. Verify that the license manager is running. If the license manager is not run-ning, start it on the license server machine(s). Check the license.log file oneach license server for errors.

3. Run ANSYS from a command prompt to check for additional error messages.(Use the -p command modifier to specify the correct product name. SeeSection 3.4: Product Variable Table for details.)

Example (Windows):

"C:\Program Files\Ansys Inc\V90\ANSYS\bin\intel\ansys90" -p ane3

Check the ANSYS Output window for error messages and additional inform-ation about the failure.



4. Use the ping command to test communication between the client machineand the license server.

If the ping command does not work, modify the hosts file or the DNS serverto contain the correct host names and IP addresses. Verify that the licenseserver and the client machines have unique IP addresses.

5. Verify that the ansyslmd.ini file exists in the licensing directory and that itcontains the correct hostname of the license server. If this file does not exist,see Section 5.1: Designating Server(s) for License Check-out of the ANSYS,Inc. Licensing Guide to specify the license server. If the ANSYSLMD_LI-CENSE_FILE or LM_LICENSE_FILE variable is used to specify the licenseserver, verify that the hostname of the license server is correct.

6. Verify that the port number used on the license server and the client machinematch.

7. Verify that the correct version of the license manager daemons (lmgrd andansyslmd) is being used. The current version is FLEXlm 9.2.

***Unable to load profile <name> because simulation environment <simulationenvironment> is not available.

If you see this message, the simulation environment specified in the named profilewas uninstalled since the profile was created. You will need to specify a new simula-tion environment and re-specify any launcher settings to continue. To avoid seeingthis message in subsequent launcher sessions, update and resave the profile, or re-install the desired simulation environment.

7.5. Licensing Error Messages

*** Licensed number of users already reached.

You may have reached the number of ANSYS product tasks that you have licensed.Wait until a task has been freed up and try again. If this error occurs on a regularbasis, you may want to talk to your ANSYS sales representative about obtaining ad-ditional licenses.

This error may also occur when licenses have been reserved for certain users, or whencertain users have been excluded from licenses via the license options file.


Section 7.5: Licensing Error Messages

*** All licenses are reserved for others.

This error may occur if you have multiple INCREMENT lines for the same feature inthe license file, and there are differing fields on each INCREMENT line (such asVENDOR_STRING and the version field), and licenses have been reserved for thisfeature. In this situation, the number of reserved licenses is reserved out of each IN-CREMENT, rather than the sum total of both.

*** Cannot connect to license server.

The license manager is currently not running. Use the ANSLIC_ADMIN utility to startthe license manager. Your license must exist on the license server prior to startingthe license manager.

If you think the license manager should already be running, check the license logfile for errors.

Some other possible causes for this error include:

• The wrong hostname is in the license file (machine ID is correct in the file andwhen the license keys were generated). The license manager could not bestarted.

• The wrong license file is on the system (both hostname and machine ID areincorrect and the license keys were created with the wrong ID). The licensemanager could not be started.

• The wrong license file is on the system AND the user changed the server lineto have the machine's hostid but not the hostname. The license managercould not be started.

• An incorrect port number was used on the SERVER line(s) in the ansyslmd.inifile or in the setting of the licensing path environment variables (AN-SYSLMD_LICENSE_FILE or LM_LICENSE_FILE)



*** Feature removed during lmreread, or wrong SERVER line hostid

Some possible causes of this message include:

• There is a typographical error in the license file's SERVER line. Typically, themachine ID was mistyped when manually entering the license file on a ma-chine.

• The user tried to install another machine's license file on a machine andchanged the SERVER line in the file to have this machine's hostname but notthe machine ID.

• A laptop with a docking station (with an Ethernet card in it) is removed fromthe docking station and the license file was made using this card's Ethernetaddress.

• The feature was removed during lmreread but the client is reading an oldcopy of the license file that still contains the removed feature.

*** Clock difference too large between client and server.

This message will appear if the date on the machine has changed. The date shouldnever be set ahead or behind the actual date.



*** License server does not support this feature.

This message can be generated if the feature has expired (on the server), or has notyet started, or the version is greater than the highest supported version, or the licensefile has been edited while the license server is running and the license file is not reread.Additional causes for this message include:

• If the user is trying to install another machine's license file on a machine ANDchanges both the hostname and the machine ID information on the SERVERline to be this machine's information. The INCREMENT lines contained in thelicense file are still invalid for this machine.

• If new information for the requested feature was added to the license file butneither an lmreread was issued nor was the license manager restarted.

• If a laptop with a docking station (with an Ethernet card in it) is removed fromthe docking station, and the license was made using this card's Ethernet ad-dress, AND the user edited the SERVER line, replacing the Ethernet addresswith the disk signature of the machine (in an attempt to fix the problem). Suchan attempt will not succeed because the INCREMENT lines were created usingthe docking station's Ethernet address, which in this situation can no longerbe seen on this machine.

• If one or more INCREMENT lines that were made for machine A were installedin machine B's license file and those features were trying to be checked outfrom machine B.

*** Feature has expired.

Your license has expired; please contact your ANSYS sales representative for a renewal.



*** No such feature exists.

A license does not exist for the requested product. Verify that the ANSYSLMD_LI-CENSE_FILE and the LM_LICENSE_FILE environment variables and the ansyslmd.inifile are pointing to the correct license server.

Verify that you are running the correct product. Use the ANSYS90_PRODUCT envir-onment variable (for ANSYS), the -p command line option, or the Product selectionbox from the launcher to select the product that you are licensed to run. If you arenot licensed to run this product, contact your ANSYS sales representative to obtaina license. If you are licensed to run this product, install the license from the licensesupplied by ANSYS, Inc. or your ANSYS sales representative using the ANSLIC_ADMINutility. If you have already created the license, use ANSLIC_ADMIN to reread the li-cense file.

You could also see this message if you are trying to use a license manager daemonfrom a previous release. The license manager daemons (lmgrd and ansyslmd) atthis release are FLEXlm 9.2.

If you are an ANSYS Workbench customer, you could see these messages if onlyANSYS Workbench is installed (no ANSYS installation) but the required WorkbenchInterface for UNIX license is not found. The “No ANSYS product installations found”message is a result of the first error and is not a separate situation. To correct thisproblem, you need a valid Workbench Interface for UNIX license. If you do not haveone, contact your ANSYS sales representative.

The Workbench Interface for UNIX licenses enable you to run the Workbench userinterface and are a no charge product that you can request from your ANSYS salesrepresentative. Because ANSYS licenses are designed to “float” on a network, youwill need to request a quantity of Workbench Interface for UNIX licenses equal tothe smaller of the two following scenarios:

• The number of Sun, HP, or Linux clients that may be running one of theseANSYS Workbench products

• The number of ANSYS product licenses (DesignSpace, Professional, Structural,Mechanical, Multiphysics, or Prep/Post) that your HP, Sun, or Linux clientshave access to run with in the ANSYS Workbench environment.

For example, if you have 20 users sharing 10 ANSYS licenses, and 4 of these users areoperating a Sun, HP, or Linux client in the ANSYS Workbench environment, you needonly 4 Workbench Interface for UNIX licenses. If all 20 users are operating Sun, HP,



or Linux clients in the ANSYS Workbench environment and sharing 10 ANSYS licenses,then you need 10 Workbench Interface for UNIX licenses.

*** License file does not support this version.

The build date in the program is newer than the version in the license file. You maynot be authorized to run a new release or you may not have installed your new license.If this is the case, install the license using the ANSLIC_ADMIN utility. If you have in-stalled the new license, use ANSLIC_ADMIN to reread the license file. To view thebuild date in ANSYS, use the -v command line option.

*** Licensing files currently installed are more recent than those on the CD. Do youwant to load the older licensing files?

You will get this message if you install an earlier version of the product after a laterversion. In almost all cases, you should answer no to preserve the most current copyof the licensing files. If you answer yes, any changes you made to the licensing fileswill be lost.

*** Invalid (inconsistent) license key

The license manager daemons for this release are FLEXlm 9.2 (lmgrd and ansyslmd).Verify that you are not using the license manager daemons supplied with a previousrelease.

*** Local checkout filter rejected request.

Set the ANS_FLEXLM_DEBUG environment variable to 2 to find the specific causeof this message.

*** Cannot find server hostname in network database.

This message will appear if one or more of the SERVER computer names do not appearin the client computer's /etc/hosts file (UNIX) or the services file (Windows).

On SGI systems, if running under NIS, see the resolver man page for more information.



*** The License Manager is currently running and failed to shutdown. There maybe some remaining processes that need to be killed manually.

If you attempt to uninstall the license manager without first successfully shutting itdown, you may inadvertently leave an ansyslmd and an lmgrd process running onyour system. These processes will be stopped when you reboot your system. Youcan stop these processes manually, but use extreme caution, because other productsthat use the FLEXlm license manager will also have lmgrd processes running. If youdo want to stop an lmgrd process, use the ps command to find the ANSYS lmgrdprocess.

***The ANSYS license manager server is down. Unless a connection is reestablished,ANSYS will exit in nn minutes.

This message occurs in a one-server license environment if your license managerhas quit running. In a three-license server environment, the ANSYS license managermust be running on at least two of the three license server machines at all times. Iftwo of the license server machines go down, or two of the machines are not runningthe license manager, this error message will appear in the program output or in amessage box. The program will continue to run for nn minutes to allow the licensemanager 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 othermachines designated as license servers.

If you get this message and determine that the license manager is still running, andyou are running in a one-server environment, then the IP address of the licenseserver machine was changed while the ANSYS product was running (this is usuallycaused by connecting to or disconnecting from an Internet Service Provider (ISP)that dynamically allocates IP addresses). To correct this situation, you must returnthe IP address to the same address that the license server had when the ANSYSproduct was started.

If the IP address changes after you start the ANSYS product (either because youconnected to or disconnected from your ISP), you can correct the error by restartingthe ANSYS product. You should not need to restart the license manager.

You can avoid this problem by remaining connected to or disconnected from theISP the entire time you are running the application.



***FLEXlm version of vendor daemon is too old.

The license manager daemons at this release are FLEXlm 9.2 (lmgrd and ansyslmd).Verify that you are not using the license manager daemons supplied with a previousrelease.

***Cannot read data from license server.

The server and the client are having difficulties communicating. This error is usuallycaused by the network setup or by the network data being different from the datain the license file (for example, the server name, machine ID, port number, or vendordaemon).

• Confirm that the information on the SERVER line of the license file is the correctinformation for the server.

• Confirm that the syntax of the SERVER and VENDOR lines of the license file iscorrect.

• Verify that TCP/IP is enabled correctly.

• Check that the hosts file on the client machine contains the license server.

• Try using <port>@<host> when specifying the server.

7.6. ANSYS License Borrowing Errors

***Unable to return <Product>, encountered “feature not found” attempting toreturn license feature <Product.>

or the following will appear in the log file:

UNAUTHORIZED lmremove request from <user> at node <host>.

If you see the above message when attempting to return a borrowed license beforethe expiration date, the -2 -p license manager startup option was set. Unset theoption. See Section 4.1.1: Modifying License Manager Startup Options for more in-formation on using the license manager startup options.



7.7. ANSYS 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 ofthe system. In this case, change the hostname in the license file. Other possible causesinclude:

• The license file was put on a machine other than the one for which it wascreated; therefore, the hostname is not correct.

• The hostname of the license server changed. Change the hostname on theSERVER line of the license file to correct this problem. REMEMBER to sendANSYS the new hostname so that future license files are made with the correcthostname.

• The license file was put on a machine other than the one for which it wascreated AND the user changed the machine's ID on the SERVER line but didnot change the hostname. If the machine ID is also wrong, you will also see amessage about the wrong hostid on SERVER line after correcting the hostname.

• The wrong hostname was used to create the license file. As long as the correctmachine ID was used, you should be able to change the hostname on theSERVER line of the license file to fix this problem. REMEMBER to send ANSYSthe correct hostname so that future license files are made with the correcthostname.


Section 7.7: ANSYS License Log File Errors

***Invalid license key (inconsistent authentication code)

The INCREMENT lines in the license file are not valid for this system (HostID mismatch).This error will also occur if the license file was typed incorrectly. Additional causesfor this message include:

• If a license file created for machine A is being installed on machine B AND theuser changed the hostname and the machine ID to machine B's in the SERVERline.

• If INCREMENT lines created for machine A are appended to an existing li-cense.dat file on machine B.

• If a laptop with a docking station (with an Ethernet card in it) is removed fromthe docking station, and the license was made using this card's Ethernet ad-dress, AND the user edited the SERVER line, replacing the Ethernet addresswith the disk signature of the machine (in an attempt to fix the problem). Suchan attempt will not succeed because the INCREMENT lines were created usingthe docking station's Ethernet address, which in this situation can no longerbe seen on this machine.

• In a three-server license environment, if the license file was created using anincorrect hostid for one of the license servers, this message will appear andwill prohibit an ANSYS product from running on any machine. Verify that thehostid in the license file matches the hostid on all three license servers. If itdoes not, the license file must be created using the correct hostid for all licenseserver machines.



***Wrong HostID on SERVER line for license file: <path to license file>

License file is not valid for this machine. Possible causes include:

• There is a typographical error. If the license file was entered manually, themachine ID may have been incorrectly typed in the SERVER line.

• The user installed a license file created for machine A on machine B andchanged the hostname in the SERVER line but did not change the machineID.

• 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 fromthe docking station, and the license file was made using this card's Ethernetaddress.

• A license file was made for a Pentium III CPU ID and the hyphen was not putafter the first four characters of the ID (e.g., ABCDEF01 was entered as the IDrather than ABCD-EF01). Ethernet address would be expected.

• A license file was made using the Windows disk signature but the keyword'DISK_SERIAL_NUM=' was not put before the ID. Ethernet address would beexpected.

*** “XXX” : Not a valid server hostname, exiting. Valid server hosts are: “YYY”.

The hostname listed in the license.dat (YYY) file does not match the hostname ofthe system (XXX).


Section 7.7: ANSYS License Log File Errors

7–20

GlossaryANSLIC_ADMIN A utility that centralizes the various ANSYS product licens-

ing administrative functions. Tasks include, but are notlimited to:

• starting and stopping the license manager

• installing licenses

• displaying license status

ANSWAIT An environment variable that will allow you to queueyour ANSYS job in the event that all ANSYS licenses arein use. Once a license becomes available and you arenext on the queue, your ANSYS job will automaticallystart.

This option is not available for some products.

ANSYSLMD_LICENSE_FILE An environment variable that may be used to specify thelicense server from which you want to check out a license.

ansyslmd This is the ANSYS, Inc. vendor daemon used to processANSYS product licensing requests, including issuing andreturning licenses. The vendor daemon is started by thelicense manager daemon (lmgrd) and must be runningto perform the aforementioned tasks.

ansyslmd.ini File that resides in the licensing directory. It is createdby ANSLIC_ADMIN utility options Specify the licenseserver (UNIX and Windows) and Modify license man-ager startup options (UNIX only).

ASD ANSYS Support Distributor.

build date The build date is the year, month, and date the ANSYSproduct was built. The version field in the license filespecifies the latest build date that can be run using thatlicense. It may also appear as 9999.9999 if a maintenanceagreement is not applicable.


backup server In a three-server network, the two servers not chosen tobe the master are the backup servers. If the master servergoes down, the backup server listed next in the licensefile automatically assumes the role of master. (A backupserver is also known as a shadow server.)

borrowable license A borrowable license is a license that you can use tem-porarily outside of the company facility (such as at homeon a laptop). A special license key is required before anylicense can be borrowed.

client A client is a machine that requests licenses but is not alicense server (i.e., does not have licenses installed on it).

daemon A process that typically runs in the background. In thecase of ANSYS licensing, the license manager daemon(lmgrd) and the vendor daemon (ansyslmd) are usedto process client requests, including issuing and returninglicenses. Windows systems refer to this process as a ser-vice.

feature The word feature, when used in the descriptions of thelicensing utilities, refers to the ANSYS product. See Sec-tion 3.4: Product Variable Table for the list of ANSYSproducts and their corresponding license features.

FLEXlm License manager used for all ANSYS products.

floating license Anyone on the network can run a licensed ANSYSproduct, up to the limit specified in the license file.Floating licenses require the license manager daemon(lmgrd) and the vendor daemon (ansyslmd) to be run-ning to count the concurrent usage of the licenses.

getcn Getcn is a utility that will display your customer number,which is contained in your license. Getcn may be runfrom the ANSLIC_ADMIN utility by choosing Displaycustomer number.

IA-32 IA-32 refers to the Intel architecture, 32-bit processor.

IA-64 IA-64 refers to the Intel architecture, 64-bit processor.

Glossary

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.G–22

license See license task.

license borrowing License borrowing allows a user to take a license for useoutside of the company facility, such as for an engineerto take a license home on his laptop.

license file A file generated by the Licensing Wizard or the Install/up-date the license options of the ANSLIC_ADMIN utilityor during the installation process. Each licensed productwill have an entry in the license file, license.dat, whichwill reside in the licensing directory. Proper installationof a license file grants access to ANSYS products.

license key The actual full license for the product.

license log file A file containing information relevant to licensing activity.This file provides a way of tracking licensing problemsthat may occur. The licensing log file, license.log, is loc-ated in the licensing directory by default.

license manager Software used for licensing ANSYS, Inc. products. ANSYSuses the FLEXlm software.

license manager daemon A program generally run in the background that is usedto process client requests, including issuing and returninglicenses. The license manager daemon (lmgrd) starts thevendor daemon (ansyslmd) and is typically started whenthe system is booted and must be running to performthe aforementioned tasks. Windows systems refer to thisprocess as a service.

license options file A file containing license manager-related resource inform-ation. This file is created on license server systems, bythe ANSLIC_ADMIN utility. By default, the file is namedansyslmd.opt and resides in the licensing directory. Youmay specify the following information in the resourcefile:

• Licenses that are reserved for individuals, groups,or machines

• Those individuals, groups, or machines that aredenied access to licenses

G–23ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Glossary

license server A license server is a system that you have designated tobe the administrator of ANSYS product licenses; the li-censes are installed on the server machine(s). One orthree systems can be used to administer any particularset of ANSYS product licenses.

license task Each concurrent use of an ANSYS product is a licensetask. Each use of an ANSYS product will take a numberof license tasks from the total number available.

licensing directory The default location for the licensing files. On Unix sys-tems, the licensing directory is /an-sys_inc/shared_files/licensing. On Windows systems,the licensing directory is \Program Files\AnsysInc\Shared Files\Licensing, located in the same driveas the operating system. The licensing directory cannotbe changed from the default directory on Windows sys-tems.

lmadmin A group of users that you designate to have the abilityto perform license administrative tasks that are con-sidered disruptive.

lmgrd A program generally run in the background that is usedto process ANSYS product licensing requests, includingissuing and returning licenses. The license managerdaemon starts the vendor daemon (ansyslmd) and istypically started when the system is booted and mustbe running to perform the aforementioned tasks. The li-cense manager daemon is lmgrd.

lmtools LMTOOLS is a Windows-only utility that will performvarious license administrator functions, such as listingthe users of licensed products. See the LMTOOLS helpfor more information on using this utility.

lmutil Lmutil is a utility that will perform various license admin-istrator functions including: rereading the license file,shutting down the license manager, starting the licensemanager, and listing the users of licensed products.lmutil is the underlying process in several of the AN-SLIC_ADMIN options.

Glossary


log file See license log file.

master server In a three-server network, one of the servers must be themaster server. The server listed first in the license fileautomatically assumes the role of master. The other twolicense servers are shadow servers (or backup servers).In a one-server network, that server is automatically themaster.

options file See license options file.

port number Communication channel by which the license managercommunicates with the client. The ANSYS default portnumber is 1055.

product variable Each ANSYS product has been assigned a specific productvariable value. Use this product variable value whenstarting a job to specify which ANSYS product is to berun. The product variable may be set by using the -pcommand line option, the ANSYS90_PRODUCT envir-onment variable (for ANSYS), or the launcher. See Sec-tion 3.4: Product Variable Table for a list of ANSYSproducts and their associated product variables/featurenames.

quorum You may designate either one or three systems to be li-cense servers. In a three server network, license managerdaemons must be running on the majority (2) of theservers before requests for licenses will be processed.

redundant servers Having multiple systems designated as license serversfor an ANSYS product. Redundancy can be achievedeither by having three license servers working togetherin tandem, whereby two of the three must be runningat all times, serving from a single set of licenses, or byhaving any number of license servers running independ-ently, each serving from different license files.

server See license server.

session log In the ANSLIC_ADMIN utility, all licensing activity iswritten to an area on the right-hand side of the utility,called the session log area. The session log maintains a

G–25ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Glossary

running tabulation of all activity (starting or stoppingthe license manager, rereading the license file, errors,etc.). The session log can also be written to a file that canbe used for troubleshooting.

service A process on a Windows machine that typically runs inthe background. UNIX systems refer to this process as adaemon. In the case of ANSYS licensing, the licensemanager daemon (lmgrd) and the vendor daemon (an-syslmd) are services used to process client requests, in-cluding issuing and returning licenses.

shadow server In a three-server network, the two servers not chosen tobe the master are the shadow servers. If the masterserver goes down, the shadow server listed next in thelicense file automatically assumes the role of master. (Ashadow server is also known as a backup server.)

task See license task.

vendor daemon The ANSYS vendor daemon is ansyslmd. It is used toprocess ANSYS licensing requests, including issuing andreturning licenses. The vendor daemon is started by thelicense manager daemon (lmgrd).

Glossary


IndexAAgreement number, 6–7All licenses reserved, 7–10ANSLIC_ADMIN utility

definition, G–21display customer number, 6–7display license server hostid, 6–3editing the license options file, 6–5install license, 6–3register license server information, 6–2reread the license file, 6–5shutdown the license manager, 6–4specifying the license server, 6–5start the license manager, 6–4uninstall the license manager, 6–8update license, 6–3using its options (UNIX), 6–1view license log file, 6–8

ANSWAIT environment variable, 5–9definition, G–21

ANSYSlicenses, 2–1

ansyslmd, 1–4, 1–5, 3–5, 3–6, 4–1definition, G–21

ansyslmd.inidefinition, G–21

ansyslmd.ini file, 3–1, 3–4, 5–1, 6–5ansyslmd.opt file, 5–2, 5–2, 6–5ANSYSLMD_LICENSE_FILE, 1–5, 3–1,3–3, 3–3, 5–6ANSYSLMD_LICENSE_FILE environmentvariable

definition, G–21ansys_pid utility, 7–3ANS_FLEXLM_DEBUG, 5–6, 7–1ANS_FLEXLM_DISABLE_DEFLICPATH, 5–6ANS_FLEXLM_DISABLE_ENV, 5–6

ANS_FLEXLM_ENABLE_FLEX_DIAG, 5–6,7–1ANS_FLEXLM_EXPWARN_DAYS, 5–6ANS_FLEXLM_HBEAT, 5–6ANS_FLEXLM_LMSGS, 5–6, 7–1ASD

definition, G–21autoexec.bat file, 5–9

BBackup server

definition, G–22boot_ansflex file, 4–1Borrowable license

definition, G–22Borrowing

licenses, 5–10, 6–7Build date

definition, G–21

CClients

definition, G–22Commands (UNIX)

PS, 4–2.cshrc file, 5–1customer number, 6–7

Ddaemon

vendor, 3–5, 3–6Daemons

definition, G–22license manager (lmgrd), 4–1starting at system boot time, 4–2starting manually, 4–2vendor (ansyslmd), 4–1

Debugging, 7–1Display customer number, 6–7Display license server hostid, 6–3Display license status, 6–7


EEnvironment variables

ANSWAIT, 5–9ANSYSLMD_LICENSE_FILE, 1–5, 3–1,5–6ANS_FLEXLM_DEBUG, 5–6, 7–1ANS_FLEXLM_DISABLE_DEFLICPATH,5–6ANS_FLEXLM_DISABLE_ENV, 5–6ANS_FLEXLM_ENABLE_FLEX_DIAG, 5–6,7–1ANS_FLEXLM_EXPWARN_DAYS, 5–6ANS_FLEXLM_HBEAT, 5–6ANS_FLEXLM_LMSGS, 5–6, 7–1FLEXLM_DIAGNOSTICS, 5–6, 7–1LM_LICENSE_FILE, 3–1, 3–3, 5–6setting the path to the license files, 3–3

Error messages, 7–1launcher , 7–7license borrowing, 7–16license log file, 7–17licensing, 4–2, 7–9

Expired license, 7–12

FFeature

definition, G–22Feature names, 3–9Files

ansyslmd.ini, 3–1, 3–4, 5–1, 6–5ansyslmd.opt, 5–2, 5–2, 6–5autoexec.bat, 5–9boot_ansflex, 4–1.cshrc, 5–1license, 1–4, 1–5license (license.dat), 3–1, 3–1license files format, 3–4license.dat, 3–3, 3–4, 6–3license.log, 4–2, 6–4, 6–8

viewing, 6–8licserver.info, 2–3, 6–2

sample license files, 3–7FLEXlm

compatibility with other software, 1–2definition, G–22

FLEXLM_DIAGNOSTICS, 5–6, 7–1floating license

definition, G–22Floating licenses, 1–1, 2–1, 3–1Format of license files, 3–4Freeing a license, 5–1, 6–6Functions requiring lmadmin group priv-ileges, 5–8

Ggetcn utility

definition, G–22

Hhostid, 2–1, 3–4, 6–2hostname, 2–1, 3–4, 6–2

IIA-32, G–22IA-64, G–22INCREMENT lines, 3–6, 3–9Installation

license, 6–3uninstalling the license manager, 6–8

LLauncher

error messages, 7–7License

error message: has expired, 7–12installing, 6–3updating, 6–3

License administrationcreating lmadmin group, 5–1

License borrowing, 5–10, 6–7definition, G–23

License borrowing error messages, 7–16

Index

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.Index–2

License files, 1–4, 1–5, 3–1definition, G–23example, 3–7format, 3–4INCREMENT lines, 3–6recognizing, 3–8reread, 6–5SERVER lines, 3–4settings precedence, 3–4specifying the location, 3–1VENDOR lines, 3–5

License keydefinition, G–23

License log file (license.log)definition, G–23error messages, 7–17viewing, 6–8

License log file error messages, 7–17License manager, 4–1, 6–6

compatibility with other software, 1–2daemon, 1–4, 1–5, G–24defined, 1–1definition, G–23modifying startup command options,4–1modifying startup options, 6–6shutting down, 4–4, 6–4shutting down with ANSLIC_ADMIN,6–4starting at system boot time, 4–2starting manually, 4–2starting with ANSLIC_ADMIN, 6–4uninstalling, 6–8

License manager daemondefinition, G–23

License options file (ansyslmd.opt), 5–2editing, 5–3, 6–5sample, 5–6

License options file (ansyslmd.opt),definition, G–23

License queuing, 5–1, 5–9License server

error message: is down, 7–10License servers

definition, 2–1, G–24designating for license checkout, 5–1,5–1display hostid, 6–3error messages, 4–2master, 2–1network licensing daemons, 4–1redundancy, 2–2registering, 2–3, 6–2selecting, 2–1shutting down the license managerdaemon, 6–4specifying, 6–5three-server network, 2–1

License statusdisplay, 6–7

License taskdefinition, G–24

License wizard, 6–3License.dat file, 1–4license.dat file, 1–5, 3–1, 3–1, 3–3,3–4, 6–3license.log file, 4–2, 6–4

viewing, 6–8Licenses

customer number, 6–7floating, 2–1, 3–1freeing, 5–1, 6–6installing/updating, 6–3waiting for available, 5–9

Licensingdebugging, 7–1error messages, 7–1problem situations, 7–3process, 1–2sample scenario, 5–2selecting servers, 2–1setting the path to the license files, 3–3tasks, 2–1three-server license network, 2–1

Index–3ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Index

Licensing directoryUNIX platforms, 1–1Windows platforms, 1–1

Licensing environmentsetting up, 5–1

Licensing error messages, 7–9licserver.info file, 2–3, 6–2lmadmin group, 5–1, 5–8lmdown, 5–8lmgrd, 1–4, 1–5, 4–1, 4–2

utility definition, G–24lmhostid, 6–3lmremove, 5–8lmreread, 5–8LMTOOLS, 6–9lmutil

utility definition, G–24LM_LICENSE_FILE, 3–1, 5–6Log file

(see also license log file)

MMaster server, 2–1, 4–2

definition, G–25

NNetwork File System

licensing failures on, 4–1Network licensing

network licensing considerations, 2–1network licensing daemons, 4–1queuing facility, 5–9shutting down the license manager,4–4starting license manager at system boottime, 4–2starting license manager manually, 4–2

No license file found for feature error mes-sage, 7–13No licenses are currently available errormessage, 7–9

PPool of available tasks, 2–1Port number, 3–4

definition, G–25Product list, 3–9Product variable

definition, G–25PS command, 4–2

QQueuing, 5–1, 5–9Quorum

definition, G–25

RRedundant servers

definition, G–25Registering license server information,2–3, 6–2Reread the license file, 6–5root login, 6–1, 6–8

SSample license files, 3–7Sample licensing scenario, 5–2SERVER lines, 3–4Service

definition, G–26Session log

definition, G–25Shadow server

definition, G–26Shutting down the license manager, 4–4Specifying the license server, 6–5Starting the license manager, 6–4Startup options for license manager

modifying, 6–6superuser login, 6–1, 6–8Symbolic links, 1–1

Index

ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.Index–4

TTasks, 2–1TCP/IP, 1–2

dial-up connection, 1–3testing whether TCP/IP is installed, 1–4

Three-server network, 2–1Troubleshooting

ansys_pid utility, 7–3getting additional debugging informa-tion, 7–1license borrowing errors, 7–16license log file errors, 7–17licensing error messages, 7–9problem situations, 7–3

Troubleshooting ANSYS error messages,7–1

UUnavailable licenses, 7–9Uninstalling the license manager, 6–8Updating license, 6–3User privileges, 5–1

Using the options file, 5–2

VVendor daemon, 1–4, 1–5, 3–5, 3–6,4–1vendor daemon

definition, G–26VENDOR lines, 3–5Viewing license log file, 6–8

WWANs, 2–1Wide area networks, 2–1

Index–5ANSYS, Inc. Licensing Guide . 9.0 Release . 002092 . © SAS IP, Inc.

Index

ansys licensing guide

Documents

ansys workbench environment

ansys confidential information

ul registered iso

software porting company

eporting company

trademark informationcopyright

software product

flexlmlicensed software