ansys 8.1 installation guide

ANSYS Installation andConfiguration Guide forUNIXANSYS Release 8.1

001978April 2004

ANSYS, Inc. is aUL registeredISO 9001: 2000Company

ANSYS Installation andConfiguration Guide forUNIX

ANSYS Release 8.1

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

Revision HistoryDateReleaseNumberApril 2002ANSYS 6.1001602October 2002ANSYS 7.0001685May 2003ANSYS 7.1001789October 2003ANSYS 8.0001902April 2004ANSYS 8.1001978

Trademark InformationANSYS, DesignSpace, DesignModeler, ANSYS DesignXplorer VT, ANSYS DesignXplorer, ANSYS Emax, ANSYS Workbenchenvironment, CFX, AI*Environment, CADOE and any and all ANSYS, Inc. product names referenced on any media, manualor the like, are registered trademarks or trademarks of subsidiaries of ANSYS, Inc. located in the United States or othercountries.

Copyright © 2004 SAS IP, Inc. All rights reserved. Unpublished rights reserved under the Copyright Laws of the UnitedStates.

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.

"FLEXlm License Manager" is a trademark of Macrovision Corporation.

Other product and company names mentioned herein are the trademarks or registered trademarks of their respectiveowners.

HP Fortran RTL #385 for Tru64 UNIX AlphaCopyright Hewlett-Packard Company 2002. All rights reservedRestricted Rights: Use, duplication, or disclosure by the U.S. Governmentis subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable.HP C++ Shared RTL for Tru64 UNIX AlphaCopyright Hewlett-Packard Company 2002. All rights reserved.Restricted Rights: Use, duplication, or disclosure by the U.S. Governmentis subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable.Contains IBM XL Fortran for AIX Version 7.1 Release 1.1 Runtime ModulesCopyright IBM Corporation 1990, 1997. All Rights Reserved

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.

Table of ContentsANSYS Installation and Configuration Guide for UNIX ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1. Installation Prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1. Additional Hardware and Software Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2. Platform Certification Specifics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1. HP AlphaServer (Compaq) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.2. Hewlett Packard (HP-UX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2.3. IBM Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.4. Sun ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.5. Silicon Graphics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.6. Intel Linux ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2. ANSYS Installation Instructions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1. Mounting the CD ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2. Running a Typical Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3. Running a Custom Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4. Exporting the ANSYS Directory ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5. Registering the License Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3. Post-Installation Procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154. Running the ANS_ADMIN Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185. Translated Message File Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186. Connection Product Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1. Setting Environment Variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.1.1. Environment Variable for Pro/ENGINEER ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.1.2. Environment Variables for Unigraphics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.2. Configuring ANSYS Connection for Pro/ENGINEER ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2.1. The protk.dat File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.2.2. Configuring Connection for Pro/ENGINEER and Unigraphics - theconfig.anscon File .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7. Installing the Healing Module ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238. Parallel Performance Configuration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

8.1. Message Passing Interface (MPI) Software ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249. Installation Troubleshooting ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.1. Using the ansys_pid Utility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279.2. The Online Help System Does Not Run Properly ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279.3. The Launcher is Excessively Slow to Start .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299.4. System-related Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9.4.1. SGI Platform Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309.4.2. Linux 32-bit Platform Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

9.5. ANSYS Documentation File for User Interface Error Messages ... . . . . . . . . . . . . . 319.6. Launcher Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

ANSYS Installation and Configuration Guide for UNIX .ANSYS Release 8.1 . 001978 . © SAS IP, Inc.

9.7. ANSYS Parallel Performance Error Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329.8. FORTRAN Runtime Error Messages .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

9.8.1. HP AlphaServer (Compaq) Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329.8.2. HP Series Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.8.3. IBM RS/6000 Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.8.4. SGI Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.8.5. Sun UltraSPARC Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.8.6. Intel IA-32 and IA-64 Linux Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

List of Tables1. Operating System Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. Product Support .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23. Locally-Mounted CD-ROM Procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84. Remotely-Mounted CD-ROM Procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95. Names for ANSYS and Pro/ENGINEER Platform Directories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226. Platforms and MPI Software ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

ANSYS Installation and Configuration Guide for UNIX .ANSYS Release 8.1 . 001978 . © SAS IP, Inc.vi

ANSYS Installation and Configuration Guide for UNIX

ANSYS Installation and ConfigurationGuide for UNIX1. Installation Prerequisites

ANSYS 8.1 is supported on the following UNIX platforms and operating system levels.See the individual Platform Certification Specifics in this guide for more information. Forup-to-date information on hardware platforms or operating systems that have beencertified, go to http://www.ansys.com/services/hardware_support/. (This URL is case-sensitive.)

Table 1 Operating System Requirements

Compilers*Platform/Operating System

Compaq FORTRAN V5.5Compaq C V6.4-216 (dtk)Compaq C++ V6.5-028

HP AlphaServer / Tru64 UNIX 64-bit V5.1 (Com-paq)

F90 B.11.01.72F90 patch PHSS-29512HP C B.11.11.08HP aC++ A.03.50

HP PA8000 64-bit / HP-UX 11.0 (64-bit)

QPK1100 B.11.00.62.4 Quality Pack, Sept. 2003B6268AA B.11.00.11.02 graphics and TechComputing softwareB6061AA B.11.08.05.01 HP-MLIB math softwareB6060BA B.11.00.16 HP-MPI (if running MPI)

HP F90 V2.6.5HP aC++/C A.05.41

HP Itanium2 IA64 / HP-UX 11.22 (This versionmay also run on Itanium** platforms, but theperformance is not as good.)

B6836AA B.11.22.01 HP-UX graphics API runtimeB6060BA B.11.22.08 HP-MPI (if running MPI)

XL 8.1.1.3VAC C 6.0.0.6VAC C++ 6.0.0.6

IBM AIX64 64-bit / AIX 5.1 Update 4

MIPS F90 7.3.1.3mMIPS C 7.3.1.3mC++ 7.3.1.3m

SGI 64-bit /IRIX64 6.5.17m

ANSYS Installation and Configuration Guide for UNIX .ANSYS Release 8.1 . 001978 . © SAS IP, Inc.

http://www.ansys.com/services/hardware_support/

Compilers*Platform/Operating System

SunOne Studio 8

Compiler PatchesC Patch 112760-06F95 Patch 112762-09Common Patch 112763-08C++ Patch 113817-02Mathlib Patch 113820-02F95 Patch 114801-02Common Patch 114803-01C++ Patch 108434-14C++ Patch 108435-14libsunperf Patches:114806-01114807-01114808-01114809-01115108-01115109-01115110-01115111-01115112-01115113-01

Sun UltraSPARC 64-bit / Solaris 8, UltraSPARC III64-bit / Solaris 8

Kernel Patch 108528-20X11 Patch 108652-66X11 Patch 111741-02ELITE 3-D Patch 108604-31EXPERT 3-D, XVR-500 Patch 108576-40CREATOR 3–D Patch 108605-32OpenGL 1.3Threads patch 108993-31

Intel Compiler Version 7.1Intel IA-32 Linux / RedHat 7.3 Kernel 2.4.18

Intel Compiler Version 7.1Intel IA-64 Linux / RedHat 7.2 Kernel 2.4.9

* Compilers are required only if you will be using User Programmable Features.

** A firmware upgrade is also required for HP-UX 11.22 on Itanium systems. Contact yourHP representative for more information on the firmware upgrade.

Table 2 Product Support

LinuxSunSGIIBM AIX5L

HP-UX11.22

(Itanium)

HP-UX11.0

HP AlphaServer

XXXXCatia 4.x

XCATIA V5 R2-12

XXXXXXParasolid 15.1

XXXXPro/ENGINEER 2001

X*XXXPro/E Wildfire**

ANSYS Installation and Configuration Guide for UNIX .ANSYS Release 8.1 . 001978 . © SAS IP, Inc.2


LinuxSunSGIIBM AIX5L

HP-UX11.22

(Itanium)

HP-UX11.0

HP AlphaServer

XXXXXSAT ACIS 12

XXXXXUnigraphics NX 2.0

X*XXXHealing CADFix v5.2OEM

XXXXXXXLS- DYNA

XXXXXXXParallel Perf.

XXXXXXXDXVT

* Linux 32-bit only

** Pro/E Wildfire Connection may require manually editing the protk.dat file on SGI andHP platforms.

1.1. Additional Hardware and Software Requirements

• X11, OpenGL graphics libraries

• 890 MB of disk space for installation; some platforms and configurations may re-quire less

• If installing CATIA V5, an additional 570 MB of disk space; 1 GB memory recom-mended.

• A minimum of 512 MB of real memory is required. Some systems may performbetter with 1 GB of memory.

• Approximately twice as much swap space as memory. SGI and HP AlphaServer(Compaq) machines may require more swap space, especially if you use the /SYS,/SYP, or HardCopy commands. The amount of memory swap space on the systemmay limit the size of the ANSYS model that can be created and/or solved.

• TCP/IP for the license manager (see the ANSYS, Inc. Licensing Guide for more inform-ation on TCP/IP)

• On HP AlphaServer (Compaq) systems, if you are using the OpenGL graphics driver,you will need the PowerStorm 3x0 v2.2 for V5.0A or V5.1 OpenGL runtime librariesloaded on your system. 3-D is supported under the PowerStorm graphics hardwareoptions.

Section 1: Installation Prerequisites

3ANSYS Installation and Configuration Guide for UNIX .ANSYS Release 8.1 . 001978 . © SAS IP, Inc.

• For SGI systems, ANSYS requires that the SGI Extended Math Libraries (BLAS) beinstalled on the system. ANSYS cannot run unless these libraries are installed. Seethe section Installing the BLAS Libraries later in this guide for more information.

• For Sun systems, OpenGL 1.3 must be installed.

Note to Exceed Users

If you run ANSYS through Hummingbird, Communications Ltd.'s ExceedTM product, werecommend that you adjust the Window Manager settings in order for the online helpsystem to work properly. The setting varies depending on the version of Exceed you arerunning. Note that changing this setting may affect other applications that you runthrough Exceed; please check with your system administrator before making any changes.

1. Right-click on the Exceed icon in the Windows Task Bar.

2. Select Tools> Configuration.

3. Double-click on the Screen Definition icon.

4. Change the Window Manager to Native (for Exceed 6.2) or Default to Native(for Exceed 7.0).

5. Double-click the Performance icon.

6. Select Draft Mode, Batch Requests, and Save Unders.

7. Set Maximum Backing Store to Always.

8. Set Default and Minimum Backing Store to When Mapped.

9. Click OK. Exceed will now ask if you want to perform a server reset. Click Yes.

1.2. Platform Certification Specifics

1.2.1. HP AlphaServer (Compaq)

If you are using a large -m value, the system kernel parameters must be modified usingsysconfigdb -m -f (see man sysconfigdb) as shown below. An example of the /etc/sy-sconfigtab entry is shown below. For more information, see the HP AlphaServer (Compaq)system documentation.

vm:swap device = /dev/disk/dsk0bvm_swap_eager = 0ubc_maxpercent = 80ubc_minpercent = 2



proc:max_per_proc_stack_size = 1073741824per_proc_stack_size = 67108864max_per_proc_address_space = 8589934592per_proc_address_space = 8589934592max_per_proc_data_size = 8589934592per_proc_data_size = 8589934592

ipc:shm_seg = 1024shm_mni = 2048shm_max = 0x100000000sem_mni = 512sem_msl = 128

1.2.2. Hewlett Packard (HP-UX)

Setting the Maximum Data Segment Size Increase the operating system parametermaxdsiz, which defines the maximum data segment size of an executing process to atleast 528 MB to execute the ANSYS program with the default (512 MB) amount of workspace. If you are using the -m command line option, set maxdsize equal to or larger thanthe -m value plus the data space size of the ANSYS executable (approximately 16 MB).For example, if you set -m to 700, set maxdsiz to at least 716 MB. In general, you shouldset the maxdsiz parameter as large as the system will allow. For more information onincreasing maxdsiz, see “Changing Kernel Parameters” in the HP 9000 Computers SystemAdministration Tasks Manual. For performance tuning, see the following HP Web page:http://www.hp-partners.com/edaweb_public/html/technical_support/tuning.html.

Any kernel parameters that are specific to the HP 64-bit operating system are appendedwith the suffix _64bit (for example, maxdsiz_64bit). If you should run into memory al-location problems, set the suffix _64bit parameters as large as the system will allow.

HP Graphics Requirements

• Non-Itanium2 HP-UX 11.x systems require ACE 9911 or later.

• When running the ANSYS program using Motif, the following options must be setin the .Xdefaults file:

Mwm*FocusAutoRaise: FalseMwm*KeyboardFocusPolicy:PointerMwm*KeyBindings: Motif

• When using the 3-D driver (OpenGL), we recommend using graphics boardsgreater than 8-plane.

• HP Itanium2 systems do not support spaceball devices.

Section 1: Installation Prerequisites


http://www.hp-partners.com/edaweb_public/html/technical_support/tuning.html

To use the HP OpenGL graphics driver, you must have a graphics device and a machinethat are both capable of supporting OpenGL. This list changes often; we recommendthat you verify with HP that your hardware meets the requirements. Once these require-ments have been established, install the OpenGL software onto the HP system. Typically,OpenGL software is installed into the /opt/graphics/OpenGL directory.

1.2.3. IBM Systems

Increase the data segment size to unlimited to allow for the maximum possible wavefront.This can be done via smit for each ANSYS user or globally by changing the default in the/etc/security/limits file.

1.2.4. Sun

Modify the Sun CDE window settings so that “Auto Raise Window” and “Allow ParentWindow on Child” are both set to Off.

1.2.5. Silicon Graphics

Maintaining user Placement of ANSYS Windows For the window manager to re-member the user's placement of the ANSYS windows, you must use an editor to modifythe following line in the /usr/lib/X11/app-defaults/4DWm file to be:

*positionIsFrame: true

Then restart the window manager.

Installing the BLAS Libraries ANSYS requires that the SGI Extended Math Libraries(BLAS) be installed on the system. ANSYS cannot run unless these libraries are installed.The IRIX Foundation CD contains the BLAS libraries. They are located under the product“Standard Execution Environment” subproduct of libblas standard execution libraries.The libraries are part of the ftn_eoe.sw64.lib (SGI64 systems) subproducts.

If you use the inst program or the swmgr program to install the operating system, theBLAS libraries are not installed along with it unless they already appear on the systemfrom a previous release. (The inst and swmgr programs update only what they find inexistence on the system.)

To install:

• If using the inst program, install the BLAS libraries manually.

• If using the swmgr program, open the ftn_eoe.swNN.lib folder, and click thecheck box for the BLAS library subproduct.



Note — If you install the libraries from a maintenance level CD (such as IRIX6.5.17m) and receive a conflict message, install the libraries from the IRIXFoundation CD for the base level of the operating system (such as IRIX 6.5).

Setting Parameter Values for SGI Systems To run ANSYS with a large -m value, setthe vmemoryuse and datasize parameters to unlimited. These parameters cannot exceedthe hard limits. To check the actual hard limits set in the kernel, type:

limit -h

To set the kernel parameters to unlimited, use systune to change the kernel and thenrebuild and reboot. Then switch user to root and type:

systune -iresource

Type the following (you can cut and paste this number from one of the other settings):

rlimit_vmem_max = 0x7fffffffffffffff rlimit_data_max = 0x7fffffffffffffff

Reboot the system, log in, and in a new shell type:

unlimit

To show new unlimited settings, type:

limit

1.2.6. Intel Linux

For the 32 and 64-bit versions, you will need the following OpenGL libraries. These librariesare typically installed during a normal Linux installation.

64-bit Linux32-bit Linux

XFree86-devel-4.1.0-8XFree86-devel-4.2.0-8

Mesa-devel-3.4.2-9

ANSYS was built and tested on the Red Hat distribution as noted in Table 1: “OperatingSystem Requirements”.

ANSYS, Inc. has not certified 3-D on Linux.

2. ANSYS Installation Instructions

You must log in as root or superuser to install ANSYS.

Section 2: ANSYS Installation Instructions


2.1. Mounting the CD

Depending on your site's system, you will need to run the installation procedure usingeither a locally- or remotely-mounted CD.

For a locally-mounted CD-ROM installation, issue the commands from Table 3: “Locally-Mounted CD-ROM Procedures” for your specific platform. For a remotely-mounted CD-ROM installation, first follow the steps for locally-mounted CD-ROM, and then follow theappropriate procedure for your platform as shown in Table 4: “Remotely-Mounted CD-ROM Procedures”.

Table 3 Locally-Mounted CD-ROM Procedures

ProcedurePlatform

mkdir cdrom_dirmount /dev/disk/cdrom0c cdrom_dir

HP AlphaServer(Compaq)

mkdir cdrom_dirmount -r -o cdcase /dev/dsk/c#t2d0 cdrom_dir

HP

mkdir cdrom_dirmount -v cdrfs -r /dev/cd0 cdrom_dir

IBM

Insert CD into CD-ROM drive. The mount is done automatically by themediad daemon to /CDROM or /cdrom on SGI systems.

SGI

mkdir cdrom_dirmount -F hsfs -r /dev/sr0 cdrom_dir

Sun

mkdir cdrom_dirmount -t iso9660 /dev/cdrom cdrom_dir

Intel Linux

On HP machines, the # symbol must be replaced with the SCSI ID of the CD device.



Table 4 Remotely-Mounted CD-ROM Procedures

ProcedurePlatform

1. Add the cdrom_dir directory to the /etc/exports file on the ma-chine with the CD-ROM device. A sample /etc/exports entry is:

/cdrom_dir -ro

2. Log on to the machine where you wish to install ANSYS and issuethe following commands:

mkdir cdrom_dir2mount -r Host:cdrom_dir cdrom_dir2

where Host is the hostname of the machine where the CD device islocated.

HP AlphaServer(Compaq)

1. Add the cdrom_dir directory to the /etc/exports file on the ma-chine with the CD-ROM device. A sample /etc/exports entry for SGIis:

/cdrom_dir -ro,anon=65534

A sample entry for HP is:

/cdrom_dir -ro,anon=0

2. Run exportfs to export the cdrom_dir directory:

exportfs cdrom_dir




HP, SGI

1. Use the smit utility to export the cdrom_dir directory.

2. Log on to the machine where you wish to install ANSYS and issuethe following command:

mkdir cdrom_dir2mount -v cdrfs -r /dev/cd0 cdrom_dir2

3. Use the smit utility to mount the remote cdrom_dir directory tocdrom_dir2.

IBM



ProcedurePlatform

1. Add the cdrom_dir directory to the /etc/dfs/dfstab file. Run/etc/init.d/nfs.server start.

2. Run shareall to export the cdrom_dir directory.




Sun

1. Add the cdrom_dir directory to the /etc/exports file on the ma-chine with the CD-ROM device. A sample /etc/exports entry is:

/cdrom_dir -ro

2. Run exportfs to export the cdrom_dir directory:

exportfs cdrom_dir


mkdir cdrom_dir2mount -t nfs Host:cdrom_dir cdrom_dir2


Intel Linux

2.2. Running a Typical Installation

This section explains a typical ANSYS installation, including the license manager, as wellas a license manager-only installation. A typical installation installs ANSYS, ANSYS LS-DYNA, DDS, the Healing Module, and the Connection products (except CATIA V5). It doesNOT install the customization tools or Connection for CATIA V5. You will need to performa custom installation for those options. See the README file on the installation CD for alist of platform directory names.

1. For a single-platform install, type ./INSTALL.

To install multiple platform versions of ANSYS on a single machine (file server),type ./INSTALL -PLATFORM. Click the platform you want to install and continuewith the installation. Repeat this process for every platform you want to install.You will have to exit and re-enter the installation procedure between each plat-



form installation. You can install all platforms into one directory; the ANSYSstartup script will automatically determine the correct platform executable.

To invoke the text-based installation procedure, type ./INSTALL -NOGUI.

2. The ANSYS 8.1 Installation screen appears. Click Install ANSYS 8.1 to begin theinstallation (products and license manager). You can also click Install LicenseManager ONLY and proceed directly to Step 6. Remember for a license manager-only installation, all systems designated as license servers must use FLEXlm 9.2(included with this release). Because this is an upgraded version at this release,you will need to run the license manager installation on all of your license servermachines.

Note — You can also type ./INSTALL.LM and then proceed to step 6.

3. Read the license agreement, and if you agree, click I Agree to accept the terms.

4. Accept the default or specify an alternate path where the CD is mounted andthe directory name where ANSYS is to be installed.

Default platform-specific directories:

HP AlphaServer (Compaq), SGI, Sun, Intel Linux: /usr/ansys_incIBM: /usr/lpp/ansys_incHP: /users/ansys_inc

5. Choose an installation option and click Install ANSYS 8.1.

Choose Typical or Custom. Typical installs all components except the custom-ization tools and Connection for CATIA V5, and sets the symbolic link /ansys_incto the directory where ANSYS is installed. Custom requires that you select thespecific components to be installed and allows you to specify the symbolic link.You must select Custom in order to use the customization tools and Connectionfor CATIA V5.

In some cases, you may see a dialog listing products not supported on yourplatform. Review the list, and click OK. You will then see a dialog listing installationdata including platform, installation directory, products, and size of the installa-tion. Review the information, and if correct, click Install ANSYS 8.1 to continuethe installation.

6. Specify if this machine is a license server or a client machine. If a client machine,continue with step 8. If a license server and the license manager is currentlyrunning, you need to shut it down to continue the installation. Click Yes to shut



it down, No to end the installation. If you choose No, you will exit the installationat this point and need to complete it at a later time.

If you already have a version of ANSYS installed, the installation compares thelicense manager files to ensure that the most recent files are installed.

7. If this is a server machine, you can enter your license now or choose to create itlater using ANSLIC_ADMIN. Click on Create License. Enter either the filenameof the license or enter an editor to cut and paste the license.

If a license file exists, the installation will automatically create an ansyslmd.inifile.

New licenses for existing customers may not be supplied with the ANSYS 8.1package. They will be supplied when the current licenses expire or when TECSexpires. If your license is current, it will still work for this release, so you can clickon Create License Later.

8. If this is a client machine, you must enter the port number (1055) and the licenseserver host name.

9. If this is a license server machine, click Yes to start the license manager. If the li-cense files were not yet created, the license manager will not be started.

If you start the license manager now, it will run as root. If you want to run it as anon-privileged user, run ANSLIC_ADMIN as root to shut down the licensemanager and then run ANSLIC_ADMIN again as a non-priviliged user and startthe license manager.

10. Click OK to end the installation. You will be asked to complete a Hardware andOperating System Survey at this point. Click Yes to take the survey or No to bypassit. Although the survey is optional, ANSYS, Inc. will use the information collectedto better meet our customers' computing needs. If you are installing multipleplatforms, you only need to fill out the survey once. The survey requires theNetscape browser.

To install ANSYS on other license servers, repeat these steps on those systems.

11. Run ANSYS using the supplied scripts (ansys81 and launcher81). User-writtenscripts for running ANSYS are not supported.

If you have installed ANSYS on a file server, follow the instructions under Section 2.4:Exporting the ANSYS Directory.



Warning: If you have a three-license server network, we do not re-commend that you load ANSYS on a single file server; doing soeliminates the inherent safety of a redundant setup.

You must choose a custom installation to install the customization tools or Connectionfor CATIA v5. The other items are all included by default during a typical installation.

2.3. Running a Custom Installation

Use a custom installation to select specific components to install. The procedure for acustom installation is almost the same as described in for a typical installation. However,when you are prompted to choose an installation option, click Custom installation. Alist of components appears:

ANSYSANSYS LS-DYNAConnection for CATIAConnection for ParasolidConnection for Pro/ENGINEERConnection for SATConnection for UnigraphicsConnection for CATIA V5Distributed SolversCustomization tools

Click the box next to the components that you want to install, and click Next. You canselect as many components as you wish to install.

During a custom installation, you will also be asked whether you want the/ansys_incsymbolic link to be used. We strongly recommend that this link be used. If you do notspecify the symbolic link, substitute the directory path where you installed ANSYS for allsubsequent occurrences of /ansys_inc in this guide.

2.4. Exporting the ANSYS Directory

If you are installing ANSYS on a file server, you need to export the /ansys_inc directoryto all client machines so that all users can access the program.

You must use the same mount point for both the client and server. For example, if youinstalled ANSYS on a file server in a directory named /apps/ansys_inc and you did notchoose the symbolic link to /ansys_inc, then you must mount this directory on the clientmachine using /apps/ansys_inc as the mount point. If you did choose the symbolic link



to /ansys_inc during installation on the file server, you must either use /ansys_inc asthe mount point on the client or you must create a symbolic link to /ansys_inc on theclient machine. (If you performed a typical installation, you did not have to choose tocreate the symbolic link; it is created automatically during a typical installation).

The instructions below assume ANSYS was installed in the specified directory and thata typical installation was performed, which creates a symbolic link to /ansys_inc.

HP AlphaServer (Compaq), HP-UX, HP Itanium2, SGI, Linux

1. Install ANSYS into the default directory (/usr/ansys_inc, or /users/ansys_inc onHP-UX and Itanium2).

2. Export the /ansys_inc directory by adding the following line to the /etc/exportsfile:

/usr/ansys_inc

or

/users/ansys_inc -anon=0

for HP-UX and Itanium2

3. On HP-UX or HP-Itanium2, SGI, and Linux systems, run

exportfs -a

4. On all client computers, mount the /ansys_inc directory.

IBM

1. Install ANSYS into the default directory (/usr/lpp/ansys_inc).

2. Export the /ansys_inc directory by using smit:

smitty nfsNetwork File System (NFS)Add a directory to Exports List (complete the exports menu)

3. Mount the /ansys_inc directory on the client machine using smit:

smitty nfsNetwork File System (NFS)Add a file system for mounting (complete the mounts menu)

Sun



1. Install ANSYS into the default directory (/usr/ansys_inc).

2. Designate the /ansys_inc directory to be exported by adding the following lineto the /etc/dfs/dfstab file:

share -f nfs /usr/ansys_inc

3. Issue the following commands:

cd /etc/rc3.d S15nfs.server start

4. Export the /ansys_inc directory to all client computers:

shareall

2.5. Registering the License Server

Follow this procedure to register your license server information if you are a new useror if you are adding or changing a license server machine. See the ANSYS, Inc. LicensingGuide for more information on selecting license servers and on using the ANSLIC_ADMINutility.

1. Select the machines that will be your license servers and install ANSYS 8.1.

2. Use the ANSLIC_ADMIN utility to register license server information on each li-cense server.

3. Return the resulting file to your ANSYS sales representative. ANSYS, Inc. or yoursales representative will then supply you with your license keys. This file is locatedin /ansys_inc/shared_files/licensing/licserver.info by default.

4. Use the ANSLIC_ADMIN utility to enter your license key and start the licensemanager.

If during the installation process you did not create/install a license and the installationprocedure did not detect an existing license, ANSYS creates a licserver.info file in thelicensing directory. In this situation, send this licserver.info file to your sales represent-ative. When you receive your license key, use ANSLIC_ADMIN to enter your license keyand start the license manager.

3. Post-Installation Procedures

After ANSYS is installed, you need to establish some system settings, including pathnamesand environment variables. See your shell documentation or man pages file for the shellbeing used for specific instructions on setting paths and environment variables.

Section 3: Post-Installation Procedures


1. Add the following paths to all ANSYS users' .cshrc or .login files.

(or appropriate path to the ANSYSexecutables)

/ansys_inc/v81/ansys/bin

(contains ANSLIC_ADMIN utility)/ansys_inc/shared_files/licensing/lic_admin

(HP AlphaServer (Compaq), HP,IBM, SGI)

/usr/bin/x11

(Sun)/usr/openwin/bin

(Intel Linux)/usr/X11R6/bin

2. Set the following ANSYS environment variables based on the behavior you want.Set the environment variables following the conventions of your shell. For ex-ample, to set an environment variable in the C shell, type:

setenv environment_variable value

So, to set the DISPLAY environment variable, you type the following, where devis the workstation hostname or IP address on which to display graphics:

setenv DISPLAY dev:0.0

DISPLAY - set this to the IP address or hostname of the workstation to whichthe users will output their analysis results. Note that the X server must havepermission to connect to the host machine.ANSYS81_PRODUCT - set this to the correct product variable to run ANSYSto start with the correct ANSYS product without specifying the -p commandmodifier each time. See Section 3.4: Product Variable Table in the ANSYS, Inc.Licensing Guide for a list of valid product variables.ANSYS81_ALTPRODS - set this to specify alternate product choices withthe priority you wish. If no licenses are available for your first product choice,the ANSYS program will automatically cascade through the specified altern-ative until it finds an available license. Use only in conjunction with the AN-SYS81_PRODUCT environment variable. Separate each product with a colon(:) on UNIX platforms or with a semicolon (;) on Windows platforms. For ex-ample (UNIX): setenv ANSYS81_ALTPRODS product_vari-able1:product_variable2...

ANSYS_LOCK - set to ON (default) to create file locks to prevent users fromopening a new job with the same name and in the same directory as thecurrent job.ANSYS81_DTM - set to ON to automatically activate the ANSYS LS-DYNADrop Test Module (default = OFF).



ANSYS81_PPFA - set to ON to automatically activate the Parallel Performancefor ANSYS product (default = OFF).OPENWINHOME - set this variable to path/openwin for the X11 and OpenGLgraphics drivers on Sun UltraSPARC systems only.ANSYS81_WORKING_DIRECTORY - set this variable to the directory youwant designated as your working directory. Note that setting this environmentvariable does NOT change the working directory setting in the launcher.SPACEBALL2 - set this environment variable to 1 to use a spaceball withANSYS.ANSYS81_MAT161 - set this environment variable to 1 to enable use of theLS-DYNA *MAT_COMPOSITE_MSC material (requires an LS-DYNA MAT_161license).LD_ASSUME_KERNEL - set this environment variable to 2.2.5 for Linux 32-bit Redhat 9.0 or Redhat Advanced Server 3.0 systems only.

If you are installing Connection products, you may have additional environmentvariables to set. See the section Connection Product Installation later in this guidefor more information.

3. Set the license manager to start automatically at boot time. For platform-specificinstructions, see Table 4.1: “License Manager Automatic Startup Instructions” inthe ANSYS, Inc. Licensing Guide.

4. Designate server(s) for license checkout and establish necessary user privileges(recommended but not required). For information on these tasks, see Chapter 5,“The Licensing Environment” in the ANSYS, Inc. Licensing Guide.

5. Make a backup copy of the /ansys_inc directory using a tape backup commandsuch as tar.

6. Verify the ANSYS installation by logging out as root and logging back in as aregular user and then selecting each option from the launcher (launcher81) toverify that they each start and run correctly.

7. Create or update the at. files. The at.allow file should contain the username ofall users allowed to run batch jobs; the at.deny file should contain the usernameof users who are not permitted to run batch jobs. The files consist of one user-name per line and can be modified only by the superuser. If neither file exists,only root will be able to run batch jobs.

The at. files are located in the /usr/lib/cron directory on HP AlphaServer (Com-paq), SGI, HP, and Sun machines, in the /var/adm/cron directory on IBM machines,and in the /etc directory on Linux machines.

Section 3: Post-Installation Procedures


8. Run the ANS_ADMIN utility to properly configure ANSYS (depending on theproducts you are running) or relink ANSYS.

If you require verification of the ANSYS program, ANSYS, Inc. offers Quality Assuranceprograms for some ANSYS products. If you are interested in this service, go to ht-tp://www.ansys.com/services/quality_assurance/quality_services.htm or call the ANSYS,Inc. Quality Assurance Group at (724) 746-3304.

4. Running the ANS_ADMIN Utility

You can run the ANS_ADMIN utility in either GUI or text mode. For more informationon individual options available with this utility, see the online help accessible from Helpbuttons on the utility dialog boxes. You do not need system administrator privileges torun ANS_ADMIN, but you will need them to run some options.

GUI Version

1. Type the following:

/ansys_inc/v81/ansys/bin/ans_admin81

2. Select ANSYS-specific administrative options and click OK.

Text Version

1. Type the following:

/ansys_inc/v81/ansys/bin/ans_admin81 -NOGUI

2. To access an option, type the number of the option you want and press ENTER.

5. Translated Message File Installation

If your ANSYS sales representative has supplied you with message files in your local lan-guage, use the following procedures to install and access these files. You must createnew message files for each release because error messages may occur in a different orderfor each release.

1. Create a language-named subdirectory (for example, fr for French) under the/docu directory:

mkdir /ansys_inc/v81/ansys/docu/fr



http://www.ansys.com/services/quality_assurance/quality_services.htm

http://www.ansys.com/services/quality_assurance/quality_services.htm

2. Copy the message files msgcat.81, msgidx.81, and msgfnm.81 into that sub-directory.

3. Access these files from the Language Selection option of the launcher or via the-l command line option:

ansys81 -l fr

6. Connection Product Installation

All ANSYS Connection products are included with the ANSYS release media and all exceptCATIA v5 are installed with a typical installation. The Connection for CATIA v5 requiresa custom installation. To run an ANSYS Connection product, you need to:

1. Ensure that the product is properly licensed.

2. Set the necessary environment variables as discussed in the next section.

3. Run the ANS_ADMIN utility if using Connection for Pro/ENGINEER or CATIA V5.

For complete information about the files you can import, see Introduction to Import ofthe ANSYS Connection User's Guide.

Caution: Be sure to install ANSYS and the Connection products from the sameCD release. If you attempt to run the latest ANSYS Connection product on a ma-chine that is running an earlier release of ANSYS, the Connection may fail, or viceversa.

6.1. Setting Environment Variables

Most environment variables are set during product installation. In general, you will notneed to reset these variables. Check the manuals for the individual CAD products for in-formation about environment variables and their settings.

6.1.1. Environment Variable for Pro/ENGINEER

ANSYS_PROE_CMDSpecifies the name of the command which launches Pro/ENGINEER on the system.The command name cannot exceed eight characters in length. Do not use an aliasto the Pro/ENGINEER executable. The path to the executable should be already setif the Pro/ENGINEER installation path has been defined for the PATH environmentsetting.

Default = proe2001

Section 6: Connection Product Installation


6.1.2. Environment Variables for Unigraphics

ANSCON_CONFIG_DIRSets the location of the config.anscon configuration file. If ANSYS81_DIR has beenset, you may not need to set this variable.

Default = /ansys_inc/v81/ansys/ac4/data

The next variable is not defined by the Unigraphics installation script. It can only be setin a user's start-up file or at command level before running Unigraphics. You must setthis environment variable if you will be running the Connection for Unigraphics productfrom inside Unigraphics. This environment variable tells Unigraphics where to find theANSYS program.

UGII_VENDOR_DIRDefines the ANSYS menu for Unigraphics.

setenv UGII_VENDOR_DIR /ansys_inc/v81/ansys/ac4/bin/ug20/<platform>

If the directory names in this environment variable or in ANSCON_CONFIG_DIR containuppercase characters, the user must set the following environment variable:

UGII_OPTIONSets the case of characters in directory names on the current system. Possible optionsare MIXED, LOWER or UPPER. We recommend the following setting:

setenv UGII_OPTION MIXED

6.2. Configuring ANSYS Connection for Pro/ENGINEER

The config.anscon and protk.dat files are required for the ANSYS Connection forPro/ENGINEER. The config.anscon file is placed in the /ansys_inc/v81/ansys/ac4/datadirectory during the ANSYS installation. The protk.dat file is placed in the Pro/ENGINEERinstallation directory when you run the ANS_ADMIN utility's Configuration options >Configure Connection for Pro/E option. This file defines:

• The name of the executable for Connection for Pro/ENGINEER

• The path to the executable

• The path to the message file

• The current revision of Pro/ENGINEER



Before using ANSYS Connection for Pro/ENGINEER, you must run the ANS_ADMIN utility'sConfiguration options>Configure Connection for Pro/E.

1. Launch ANS_ADMIN.

2. Select Configuration options to continue.

3. Select Configure Connection for Pro/E to continue.

4. Enter the name of the language (character set) used with Pro/ENGINEER (usasciiis the default) and the Pro/ENGINEER installation path. Select OK to continue.

Note — You must have permissions to create/update the protk.dat filein the Pro/ENGINEER installation directory when choosing this option.

Caution: Check the protk.dat file for duplicate definitions. If you haveinstalled other Pro/ENGINEER products before, you may have duplicateentries for the name of the executable and the revision. The ANS_ADMINutility's Configuration options>Configure Connection for Pro/E createsthe protk.dat file in the Pro/ENGINEER installation directory as listed inSection 6.2.1: The protk.dat File, below. If a protk.dat file already exists,the information is appended. Edit the protk.dat file and delete any du-plicate definitions. The new file should have the following entries for thecurrent release of this product, but may contain additional definitions ifother Pro/ENGINEER products are in use:

name ac4pro81exec_path /ansys_inc/v81/ansys/ac4/bin/pro/<platform>/ac4protext_path /ansys_inc/v81/ansys/ac4/data/pro/textrevision 2001STARTUP dllend

5. Select EXIT to close ANS_ADMIN.

See Section 6.2.1: The protk.dat File for more information about the protk.dat file. Theconfig.anscon file is documented in Section 6.2.2: Configuring Connection for Pro/EN-GINEER and Unigraphics - the config.anscon File.

6.2.1. The protk.dat File

The protk.dat file defines the name of the executable for Pro/ENGINEER, the path to theexecutable, the path to the message file, and the current revision of the installedPro/ENGINEER. Pro/ENGINEER 2001 with a date code of 2001240 or higher must alreadybe installed before configuring Pro/ENGINEER.

Section 6: Connection Product Installation


The protk.dat file may be stored in one of these directories.

1. Pro/ENGINEER working directory (directory from which Pro/E was launched)

2. /<ProE_install_dir>/<proe_platform>/text/usascii/

3. <ProE_install_dir>/<proe_platform>/text

usascii is the default language (character set). You may have specified a different languageduring installation.

The <proe_platform> variable is the name that Pro/ENGINEER gives to its platformdirectories. Pro/ENGINEER platform names are similar, but not identical, to the ANSYSplatform names:

Table 5 Names for ANSYS and Pro/ENGINEER Platform Directories

Pro/ENGINEER PlatformName <PROE_PLATFORM>

ANSYS Platform Name<PLATFORM>

Hardware Platform

hp8k, hpux11_pa32, orhpux_pa64

hppa8000-64HP PA8000 64-bit

ibm_rs6000aix64IBM RS/6000 64-bit (AIX5.1)

sgi_mips4 or sgi_elf4sgi64SGI 64-bit

sun4_solaris or sun4_solar-is_64

sun64Sun UltraSPARC 64-bit

sun4_solaris or sun4_solar-is_64

usIIISun UltraSPARC III+ 64-bit

i486_linuxlinuxia32Linux IA-32

6.2.2. Configuring Connection for Pro/ENGINEER and Unigraphics- the config.anscon File

Users who launch ANSYS from Pro/ENGINEER or Unigraphics will need the informationfrom the config.anscon file. This file is installed for all users in /ansys_inc/v81/an-sys/ac4/data/. Here is a sample config.anscon file:

ANSYS_CMD /ansys_inc/v81/ansys/bin/ansys81ANSYS_GRAPHIC_DEVICE x11-statANSYS_SOLVER Frontal**ANSYS_SELECTED_LAYERS 1-256**ANSYS_GEOMETRY_TYPE Solids Only**ANSYS_NEUTRAL_FORMAT YesANSYS_PRODUCT_NAME ANSYS



**These variables are not supported by Pro/ENGINEER and are ignored by Pro/ENGINEER.They appear for compatibility with Unigraphics.

You can modify the config.anscon file to set information for all ANSYS Connection forPro/ENGINEER and Unigraphics users. Pro/ENGINEER and Unigraphics users can copythis file to their working directory and configure it for their own projects by using theconfiguration editor. Unigraphics users should see Using the Configuration Editor andPro/ENGINEER users should see Using the Configuration Editor in the ANSYS ConnectionUser's Guide for more information. See Setting ANSYS Configuration Parameters in theANSYS Connection User's Guide for more information about the config.anscon file.

7. Installing the Healing Module

Follow the steps below to install the Healing Module (AGHM). You must install ANSYSbefore installing AGHM.

1. Mount the CD as explained in Section 2.1: Mounting the CD.

2. Type ./INSTALL.

3. Enter a mount directory or type Y to accept the default.

4. Enter an installation directory, or type Y to accept the default.

5. Verify the installation information and type Y to install.

Mount the CD as explained in Section 2.1: Mounting the CD.

8. Parallel Performance Configuration

Parallel Performance for ANSYS, which turns on the AMG and distributed (DDS, DPCG,DJCG) solvers, requires the installation of ANSYS 8.1. The system must be on a networkor have multiple processors on a single machine to run the distributed solvers. MPIsoftware is required for the distributed solvers and must be installed, configured andrunning before you run the distributed solvers. MPI and ANSYS 8.1 must be installed onthe master machine, and MPI software and the distributed solvers must be installed oneach machine. If MPI is not installed, use the table below to find out what type of MPIsoftware to install. Be sure to follow the configuration instructions accompanying thatsoftware carefully to ensure that the distributed solvers will run correctly.

MPI software is not required for the AMG solver. If you are only using the AMG solver,you can go directly to Using the Parallel Performance for ANSYS Add-On in the ANSYSAdvanced Analysis Techniques Guide.

Section 8: Parallel Performance Configuration


Parallel Performance for ANSYS cannot be added onto the following products:

• University and ANSYS ED

• Prep/Post products

• ANSYS LS-DYNA

• ESP products

• Batch children

8.1. Message Passing Interface (MPI) Software

The MPI software you use depends on the platform. The following table lists the platformsthat support the Parallel Performance for ANSYS solvers and the type of MPI software toinstall. For questions regarding the installation and configuration of the MPI software,please contact your MPI vendor.

Table 6 Platforms and MPI Software

More InformationMPI SoftwarePlatform

http://www.sgi.com/software/mpt/overview.htmlMPI 3.2.0 with array ser-vices 3.2

SGI

http://www.sun.com/hpc/communitysource/HPC CLUSTERTOOLS 5.0Sun

http://www.austin.ibm.com/support/sp/ sp_se-

cure/readme/pssp3.1/poe.html[1]

Parallel Environment forAIX Version 3.2.0.14

IBM

http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDe-tailPage_IDX/1,1703,3438,00.html

HP MPI B.01.08.03.00, HP-MPI for HP-UX 11.22

HP PA 800064-bit, Itani-um2 IA64

http://www.compaq.com/hpc/software/cmpi.htmlCompaq MPI 1.96 (Patch

2)[2]

HP Al-phaServer(Compaq)

http://mpi-softtech.comMPIPro 1.6.5Intel IA-32Linux

/ansys_inc/v81/ansys/mpichMPICH-1.2.5Intel LinuxIA-32 and64

[1] Not downloadable -- this is an informational file only.

[2] This version of MPI is for Compaq TruCluster Server systems only.



http://www.sgi.com/software/mpt/overview.html

http://www.sun.com/hpc/communitysource/

http://www.austin.ibm.com/support/sp/sp_secure/readme/pssp3.1/poe.html

http://www.austin.ibm.com/support/sp/sp_secure/readme/pssp3.1/poe.html

http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,3438,00.html



http://www.compaq.com/hpc/software/cmpi.html

http://mpi-softtech.com

Using the mpitest Program

The mpitest program is a simple ping program to verify that MPI is set up correctly. OnUNIX, run:

/ansys_inc/v81/ansys/bin/mpitest81

Note — If you are using MPICH, run mpitestmpich81 instead.

The preceding example used two nodes. To change the number of nodes, edit the scripts.You must use an even number of nodes.

Configuring Parallel Performance

You must be able to log in and rsh (for MPICH) to all machines where you plan to run thedistributed solvers. We highly recommend that you establish an identical directorystructure for the executable location on all machines; an identical directory structure isrequired for some MPI installations.

The ANSYS working directory used on the machine from which ANSYS is started (mastermachine) must also exist locally on each remote machine that will use the distributedsolution. Working directories should not be NFS mounted to all machines.

For example, if you start ANSYS in a directory named /home/staff/jo (or you specify thisworking directory in the launcher), then a directory named /home/staff/jo must existlocally on each remote machine.

Accessing Remote Hosts

Each UNIX platform has a file to define the remote systems accessible from that system.Typically, it's called the .rhosts file and resides in the user's home directory. Since thethe distributed solvers rely upon accessing the processors of solvers on remote machines,you must ensure the following before trying to run the distributed solvers:

• You must be able to log in to all machines on which you plan to run the distributedsolver. To test that the .rhosts file is working correctly, perform a remote login(rlogin) from one host to another. You should not be prompted for a password.If you are, check the .rhosts permissions and machine names for correctness.

• Your .rhosts file must list all systems on which you plan to run the the distributedsolver.

Section 8: Parallel Performance Configuration


If you plan to run the distributed solvers on one machine with multiple processors in ashared memory environment, you need to have the MPI software installed, but you donot need the .rhosts file. See the DSOPT, Local command for more information.

Once you have updated the .rhosts file, type:

chmod 600 .rhosts

Setting Environment Variables

You may want to set the following environment variables.

• ANSYS_RSH - This is the remote shell command to use in place of the default rsh.

• ANSYS_NETWORK_START - This is the time, in seconds, to wait before timing outon the start-up of the client (default is 15 seconds).

• ANSYS_NETWORK_COMM - This is the time to wait, in seconds, before timing outwhile communicating with the client machine (default is 5 seconds).

SGI Configuration Issues

When you install the SGI MPI software, you must also install the array 3.2 software(available from the Message Passing Toolkit 1.3 distribution). The array daemon must berunning on each system you plan to use for the distributed solvers. Update the/usr/lib/arrayd.conf file to list each system on which you plan to run the distributedsolvers. The local hostname of the machine must be listed first in this file.

Using MpCCI

MpCCI, a message passing interface designed specifically for FSI problems, is a codecoupling interface that couples ANSYS with a third party CFD code. For more informationon using MpCCI with ANSYS, see the ANSYS Coupled-Field Analysis Guide. For more inform-ation on MpCCI in general, see http://www.scai.fraunhofer.de.

ANSYS supports MpCCI on the HP PA8000 64-bit, SGI 64-bit IRIX, and Linux 32-bit platformsonly. On Linux, you must run MPICH as your MPI software.

The MpCCI software is included on the ANSYS media. However, you will need to obtaina license from Fraunhofer SCAI (http://www.scai.fraunhofer.de/index.php?id=222&L=1).To use MpCCI:

1. Install the software following the instructions found in the README file in thempcci/<platform> directory on the CD. The compressed tar files are found in



http://www.scai.fraunhofer.de

http://www.scai.fraunhofer.de/index.php?id=222&L=1

HP64.Z, SGI64.Z, and LINUX32.Z. You will need the compilers listed inTable 1: “Operating System Requirements” to complete this installation correctly.

You also need Perl 5 or later. You can download Perl from ht-tp://www.perl.com/pub/a/language/info/software.html.

2. After installing MpCCI, you will need to generate a system ID and return thatvalue to Fraunhofer SCAI, who will then issue you an appropriate license key.

9. Installation Troubleshooting

This section lists problems and error messages that you may encounter while installingand/or running the ANSYS program. After each situation description or error messageis the user action required to correct the problem.

For information on licensing-related errors, see the Chapter 7, “Troubleshooting” sectionof the ANSYS, Inc. Licensing Guide.

In addition, this appendix describes the ansys_pid utility, which is useful fortroubleshooting some problems.

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

By default, ansys_pid sends all of the information that it collects to the screen. At timesit may be necessary to provide the information for technical support. You will be givenan option to save the data to a file. This option allows you to specify a filename for theoutput. Then forward the file to the appropriate person.

9.2. The Online Help System Does Not Run Properly

The online documentation for ANSYS uses the Oracle Help browser. Several unusualbehaviors and their cause and resolution are listed.

If you request help and nothing happens:

• On a few machine configurations, the online help system can take up to 60 secondslonger than ANSYS to initialize, due to the large amount of documentation avail-

Section 9: Installation Troubleshooting


http://www.perl.com/pub/a/language/info/software.html

http://www.perl.com/pub/a/language/info/software.html

able. If you request help within 60 seconds of running ANSYS, you may simplyneed to wait a few more seconds for help to start.

• If you have minimized the help windows, activating help will not restore them totheir original size. Instead of minimizing help, you can close the help windowswhen you are done using help. This does not exit the help, so the help system willstill be available quickly next time you request help.

• The help system may have aborted due to a system error. You cannot restart thehelp system from your current ANSYS session. You can save your work and restarta new ANSYS session.

If the text in the online help is unclear (the fonts are too small, too large, or rough aroundthe edges):

• Use the [+] or [-] keys to enlarge or reduce the fonts. Depending on your system'sconfiguration and installed fonts, you may need to experiment with the [+] and[-] keys to adjust your font size. Typically, the [+] will increase the font size, andthe [-] will decrease it.

• If the [+] and [-] keys do not improve the font, you may need to use a differentstyle sheet. The online help system uses a Cascading Style Sheet (CSS) to controlthe appearance of the help. The default CSS, ansys.css, is encapsulated with therest of the help content in /ansys_inc/v81/commonfiles/help/en-us/ansys.jar.

To modify the CSS:

1. Extract the files ansys.css and ansys2.css from the .JAR file using a PKZIPcompatible compression / decompression utility (e.g., gunzip)

2. Overwrite ansys.css with ansys2.css

3. Using the same utility you used in step 1, place the new ansys.css back intothe .JAR file

If the results of the provided backup style sheet are still inadequate, you may haveto customize the stylesheet yourself. To do this, follow the procedure above, butsubstitute step 2 with editing ansys.css. If you are unfamiliar with Cascading StyleSheets, see www.w3schools.com for a tutorial to CSS.

If clicking on the scroll bar in the help system results in the screen scrolling for more thanone page, we recommend that you try one of these scrolling methods instead:

• Use the Page Up and Page Down keys.



http://www.w3schools.com/css

• Click the arrows at either end of the scroll bar, rather than clicking on the scrollbar itself.

• Use the mouse to drag the scroll bar to the desired location.

When starting ANSYS over Exceed, all of the UNIX window controls (borders, close buttons,etc.) disappear, or the help windows appear but are small and in the top left corner ofthe screen.

• You need to change your window manager settings in Exceed. See the sectionNote to Exceed Users earlier in this guide for information on changing your windowmanager settings.

• If changing the window manager settings does not correct the problem, we re-commend upgrading to Exceed 7.0 or higher.

• If the problem still occurs, change the Window Manager to X. You must start anX Windows manager like mwm before running ANSYS.

Mouse clicks are slow to initiate an action.

• This is a result of the mouse click signals traveling over the network via an Exceedconnection. Try adjusting the Exceed Performance settings. See the section Noteto Exceed Users earlier in this guide for information on specific changes we suggest.

9.3. The Launcher is Excessively Slow to Start

If the launcher is excessively slow to start (more than 60 seconds), AND you have LSF in-stalled, you may not have an LSF license. In this case, set the ANS_LAUNCH_IGNORELSFenvironment variable to 1 to bypass the LSF check. To resume the LSF check once youhave an LSF license, set ANS_LAUNCH_IGNORELSF to 0 (or unset it).

9.4. System-related Error Messages

Cannot find file <product>.tar in directory <cdrom_dir>

This error may appear during the ANSYS installation if you have entered the wrongCD pathname. Check Table 3: “Locally-Mounted CD-ROM Procedures” and enter thecorrect pathname for your platform.

Error, could not open display.

Either the DISPLAY environment variable is not correct or the xhosts command wasnot properly set. See the ANSYS Basic Analysis Guide for specific graphics information.



***Error, ANSYS81_DIR environment variable is not set. This is a fatal error – exiting.

This message indicates that the ANSYS81_DIR environment variable was not setwhere necessary for licensing. This environment variable (which is set in the scriptsthat run ANSYS) should be set to the release-specific installation directory.

9.4.1. SGI Platform Messages

/ansys_inc/v81/ansys/bin/sgi64/ansys.e81: rdl : Fatal Error : Cannot SuccessfullyMap soname 'libblas.so' under any of the filenames

/ansys_inc/v81/ansys/lib/sgi64/libblas.so : /usr/lib64/libblas.so :

/usr/lib64/internal/libblas.so : /lib64/libblas.so :

/opt/lib64/libblas.so : /ansys_inc/v81/ansys/lib/sgi64/libblas.so.1 :

/usr/lib64/libblas.so.1 : /usr/lib64/internal/libblas.so.1 :

/lib64/libblas.so.1 : /opt/lib64/libblas.so.1

ANSYS requires that the SGI Extended Math Libraries (BLAS) be installed on the system.The BLAS libraries are part of the ftn_eoe.sw64.lib and ftn_eoe_.sw32.lib sub-products. See the subsection on Silicon Graphics in the Platform Certification Specificssection for more information.

9.4.2. Linux 32-bit Platform Messages

/ansys_inc/v81/ansys/bin/linuxia32/ansys.e81: relocation error: /ansys_inc/v81/an-sys/lib/linuxia32/libansys2.so: symbol errno, version GLIBC_2.0 not defined in filelibc.so.6 with link time reference

This message occurs on Linux 32-bit Redhat 9.0 or Redhat Advanced Server 3.0 sys-tems only. To correct this error, set the LD_ASSUME_ KERNEL environment variableto 2.2.5.



9.5. ANSYS Documentation File for User Interface Error Mes-sages

Missing or erroneous documentation files for user interface. Command ignored.

Verify that the documentation list file for the user interface exists in the /an-sys_inc/v81/ansys/gui/en-us/UIDL subdirectory.

ls -l /ansys_inc/v81/ansys/gui/en-us/UIDL/menulist81.ans

The system should respond with:

-rw-r--r-- 1 root 23 Jan 8 11:50 /ansys_inc/v81/ansys/gui /en-us/UIDL/menulist81.ans

Make sure that the pathnames in the menulist81.ans file are correct.

9.6. Launcher Error Messages

Some of the more common error messages follow. See the ANSYS, Inc. Licensing Guidefor licensing-related launcher messages.

***Cannot create required <profile> file. Therefore, cannot write to profile inform-ation during this launcher session.

If you see this error, you cannot add or modify profile information during thislauncher session. Verify that you have write access to the directory and restart thelauncher session. Typically, this directory is C:\Documents and Settings\<username>\Application Data\Ansys\v81\launcher on Windows or ~/.ansys/v81/launch-er on UNIX.

***No ANSYS product installations found.

Verify your ANSYS product installation. If the desired ANSYS product was not installed,install it.

You could also see this message if only ANSYS Workbench is installed (no ANSYS in-stallation) but the required Workbench Interface for UNIX license is not found. Youwill first see a message “Required Workbench Interface for UNIX” license was notfound. Therefore, simulation environment ANSYS Workbench will not be available.”When you click OK on that message box, the “No ANSYS product installations found”box appears.



***LSF Submittal error. Job <name> could not be submitted.

Verify that you have LSF properly installed, configured, and running. For more inform-ation, please contact your LSF vendor or go to www.platform.com.

9.7. ANSYS Parallel Performance Error Messages

The following error messages are associated with the Parallel Performance for ANSYSsolvers on the HP platform.

mpid: Error: HP MPI version incompatibility detected

mpid: 1.7.2 runtime environment; 1.6 application

mpid: restart with the mpirun1.6 launch utility

This message occurs if you are attempting to use ANSYS 8.1 on an HP PA8000 systemwith MPI version 1.7.2. In order to run MPI 1.6, you must run the mpirun1.6 utility,included with the MPI 1.7.2 package from HP.

<HP-MPI>: MPI_Init: This MPI application must be started with mpirun.

mpirun: MPI application not responding: Connection timed out

This message occurs if you are attempting to use ANSYS 8.1 on an HP PA8000 systemwith MPI version 1.6. In order to run MPI 1.7.2, you must run the mpirun command.

9.8. FORTRAN Runtime Error Messages

The following error messages occur if the user is running ANSYS in a directory in whichthe user does not have write permission, or if ANSYS files (i.e., Jobname.RST, Job-name.DB) exist in the current directory but the user does not have write permissions tothe files. The specific messages that appear on each system are shown below.

9.8.1. HP AlphaServer (Compaq) Systems

forrtl: severe(9): info: Fortran error message number is 9.

forrtl: warning: Could not open message catalog: for_msg.cat.

forrtl: info: Check environment variable NLSPATH and protection of/usr/lib/nls/msg/en_US.88591/for_msg.cat.



www.platform.com

forrtl: severe(9): Message not found

This message occurs if the FORTRAN message catalog is not installed on the system.

forrtl: severe: permission to access file denied, unit 19, file fort.19

This message occurs if the FORTRAN message catalog is installed on the system.

9.8.2. HP Series Systems

** FORTRAN I/O ERROR 908: COULD NOT OPEN FILE SPECIFIED FILE: ftn19, UNIT:19

LAST FORMAT:

9.8.3. IBM RS/6000 Systems

1525-139 Unit 19 is not valid for the WRITE/PRINT statement since the ACTION=specifier for the unit has value READ. The program will stop.

9.8.4. SGI Systems

sfe: unit not connected

apparent state: unit 19 named fort.19

last format:

lately writing sequential formatted internal IO

*** Execution Terminated (114)

9.8.5. Sun UltraSPARC Systems

write sfe: [13] Permission denied

logical unit 19, named file.err

lately: writing sequential formatted external IO



9.8.6. Intel IA-32 and IA-64 Linux Systems

Input/Output Error 177: Creat Failure

In Procedure: fappnd

At Line: 72

Statement: Formatted WRITE

Unit: 19



ansys 8.1 installation guide

Documents

fortran message

message passing

directory

window manager

identical

run batch

configuration

irix foundation