Professional Documents
Culture Documents
ANSYS, Inc. Southpointe 275 Technology Drive Canonsburg, PA 15317 ansysinfo@ansys.com http://www.ansys.com (T) 724-746-3304 (F) 724-514-9494
Revision History Number 001686 001790 001903 001979 002094 Release ANSYS 7.0 ANSYS 7.1 ANSYS 8.0 ANSYS 8.1 ANSYS 9.0 Date October 2002 May 2003 October 2003 April 2004 November 2004
Table of Contents
ANSYS Installation and Configuration Guide for Windows ......................................... 1 1. Installation Prerequisites ................................................................................. 1 1.1. Additional Hardware and Software Requirements ................................... 2 2. ANSYS Pre-Installation Instructions .................................................................. 2 2.1. Installing from the Media ........................................................................ 3 2.2. Downloading the Installation Files .......................................................... 3 3. Installing ANSYS ............................................................................................. 3 3.1. Exporting/Sharing the ANSYS Directory .................................................. 6 3.2. Using the Universal Naming Convention (UNC) to Avoid Problems in Your Network ............................................................................................... 6 3.3. Setting the /3GB Switch .......................................................................... 8 3.4. Registering the License Server ................................................................ 8 4. Post-Installation Procedures ............................................................................ 9 5. Running the ANS_ADMIN Utility .................................................................... 11 6. Translated Message File Installation ............................................................... 11 7. Uninstalling ANSYS ....................................................................................... 12 8. Connection Product Installation .................................................................... 13 8.1. Setting Environment Variables .............................................................. 14 8.1.1. Environment Variable for Pro/ENGINEER ....................................... 14 8.2. Configuring ANSYS Connection for Pro/ENGINEER ................................ 14 8.2.1. The protk.dat File ......................................................................... 16 8.2.2. Configuring Connection for Pro/ENGINEER - the config.anscon File ....................................................................................................... 17 8.3. Unigraphics Troubleshooting ............................................................... 17 9. Installation Troubleshooting .......................................................................... 18 9.1. Using the ansys_pid Utility .................................................................... 18 9.2. Dial-up Adapter .................................................................................... 18 9.3. The Launcher is Excessively Slow to Start .............................................. 19 9.4. Display Problems on Windows XP ......................................................... 19 9.5. System-related Error Messages ............................................................. 19 9.6. ANS_ADMIN Error Messages ................................................................. 20 9.7. Launcher Error Messages ...................................................................... 20 Configuring Distributed ANSYS and the Distributed Solvers ..................................... 21 1. Prerequisites for Running Distributed ANSYS or the Distributed Solvers .......... 21 1.1. MPI Software ........................................................................................ 22 1.2. Using MPICH ........................................................................................ 23 1.2.1. Configuration for Windows Systems Running MPICH .................... 24 1.2.2. Configuration for UNIX/Linux Systems Running MPICH ................. 24
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows 2. Setting Up the Environment for Distributed ANSYS or the Distributed Solvers .................................................................................................................... 2.1. Using the mpitest Program ................................................................... 2.1.1. Running a Local Test .................................................................... 2.1.2. Running a Distributed Test ........................................................... 2.2. Other Considerations ............................................................................ 3. Running a Distributed Job .............................................................................
24 28 28 28 31 32
List of Tables
1. Operating System Requirements ........................................................................... 1 2. Product Support ................................................................................................... 1 1. Platforms and MPI Software ................................................................................. 22
vi
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Intel IA-32 bit / Windows XP Home or Professional (Build 2600) Compaq Visual Version 5.1 FORTRAN 6.6 A Intel IA-32 bit / Windows 2000 Version 5.0 (Build 2195) MS VC++ 6.0 (Service Pack 5)
* Compilers are required only if you will be using User Programmable Features.
X X X X X
X X X X X
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 3: Installing ANSYS You must have an account with administrator privileges to install ANSYS.
5.
6.
7.
3. Installing ANSYS
This section explains how to install ANSYS and the license server. Installing ANSYS 1. Follow the steps below for an ANSYS product installation.
Choose an installation option. You can select ANSYS products or the license manager only. If you choose to install only the license manager, you can proceed
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows directly to the next section, Installing the License Manager. If you choose to install the products, continue with the next step. 2. 3. 4. A dialog box appears listing the hardware requirements. Click Next. The ANSYS License Agreement dialog box appears. After reading the license agreement, if you accept, click Yes. In the Choose Destination Location dialog box, you indicate the directory name where ANSYS 9.0 is to be installed. To choose the default, click Next. We recommend that you choose the default directory. The default installation assumes that the installation directory for ANSYS is \Program Files\Ansys Inc\V90\ANSYS, located on the drive in which the operating system resides. 5. Select the components to be installed. Click the box next to the components that you want to install, and click Next. You can select as many components as you wish to install. The default installation installs all components except the customization tools, Connection for Pro/ENGINEER, and Connection for CATIA V5. You must manually select customization tools, Connection for Pro/ENGINEER, and Connection for CATIA V5 to use those options. 6. 7. 8. 9. Select the ANSYS program folder. We recommend that you choose the default, ANSYS 9.0. A dialog box appears listing the installation option, directory, and the program folder name. Click Next to begin installing. The installation process begins. A message box appears reminding Connections users of additional setup or configuration tasks that must be completed. The option for running the license manager installation appears. Verify that the Run the Licensing setup box is checked and click Next. When you have completed the licensing setup, or if you elected not to install the license manager, you will be prompted to complete the Hardware and Operating System Survey. Verify that the Take the ANSYS Survey box is checked and click Next to complete the survey. Although the survey is optional, ANSYS, Inc. will use the information collected to better meet our customers' computing needs. If you are installing multiple platforms, you only need to fill out the survey once. You must run the licensing setup to complete the installation. Installing the License Manager 4 Follow the steps below.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 3: Installing ANSYS 1. Place the CD in your CD drive. If autorun is enabled, the installation will begin automatically. If autorun is disabled, choose Start>Run and type D:\autoexec (replace D with the letter of your CD drive). Note You can also run LicenseSetup.bat from the root of the CD and proceed directly to the section Installing the License Manager 2. Choose Install License Manager Only. A message box appears asking if this system is a license server machine. Answer Yes if this system if designated to be the administrator of ANSYS licenses. Answer No if this system is to be configured as a client system requesting ANSYS licenses from an ANSYS FLEXlm license server machine. 3. If you answered Yes to the previous step, then a message box appears indicating that you have chosen to install the ANSYS license manager. You will be asked whether you have your license file. - If you have your license file, you can continue with the installation. - If you do not have your license file, you can exit the installation or continue the installation without your license file. If you continue the installation without your license file, you will not be able to run ANSYS until you install the license file by using the ANSLIC_ADMIN utility. See Section 3.4: Registering the License Server later in this guide for more information about obtaining your license file. If you have a license file, enter it now. - If your license file already exists, select the "Browse for the location of an existing license file" option and click Next. Enter the location and name of your license file. You must enter the complete path where the license file is located. Click Next. - If you need to create your license file, select the "Create a license file with Notepad" option and click Next. You automatically enter Notepad, where you can type or copy/paste in your license file. When finished, choose File>Save and then File>Exit. The license manager will be started; a reboot is not necessary. 4. If you answered No to Step #2, then you will be asked whether you want to configure this system to be a client system.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows You may be asked to enter the port number. You may also be asked to choose the number of servers, followed by the hostname for each license server.
3.2. Using the Universal Naming Convention (UNC) to Avoid Problems in Your Network
After you install ANSYS on a file server, use the UNC path instead of a drive letter to identify the ANSYS installation directory. This will avoid problems for machines on the network configured to run ANSYS from the file server. Note UNC paths can be used in the protk.dat file. However, if you experience problems when using the UNC paths, replace the UNC paths with drive letters in the Pro/ENGINEER configuration files. See the section Section 8.2.1: The protk.dat File for more information. The ANSYS directory should first be shared out to allow access by other systems on the network. The ANSYS installation directory should be shared out at the \Program Files\Ansys Inc level and be given a share name. The UNC name consists of the machine name of the file server, preceded by two backslashes, followed by the share name. For example, a typical UNC name for an installation drive is:
\\<machine name>\<share name>\V90\Ansys
If you are not sure what the servers machine name is, follow this procedure:
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 3: Installing ANSYS 1. 2. In the Control Panel, double-click the Network icon. The Network window appears. Choose the Identification tab. The name that appears in the Computer Name field is the machine name of the server.
On the file server, edit the following files: menulist90.ans (located in the \gui\en-us\uidl subdirectory) ans_ext.tbl (located in the \lib\<platform> subdirectory) tlbrlist.ans (located in the \gui\en-us\toolbars subdirectory
Substitute the UNC name (\\<machine name>\<share name>) for any occurrence of C:\Program Files\Ansys Inc. The drive letter may vary depending on where the operating system resides. Note If the system that shares the ANSYS directory should go down, all systems that have connected to that directory will be unable to run ANSYS. The following example describes how to share the ANSYS installation directory, substitute the UNC name, and configure a machine over the network to run ANSYS. In this example, the file server machine is named ANSYSSERVER and the share name given to the ANSYS installation directory is ANSYS. 1. On the file server ANSYSSERVER, create a share for the directory C:\Program Files\Ansys Inc. In Windows Explorer, right click on the \ANSYS Inc folder. Select Sharing..., then select Shared As and type in a share name of ANSYS. 2. On the file server ANSYSSERVER, modify the menulist90.ans, tlbrlist.ans, and ans_ext.tbl files, replacing all occurrences of C:\Program Files\ANSYS Inc with \\ANSYSSERVER\ANSYS. Go to each machine on the network that will be running ANSYS from the file server ANSYSSERVER. On each machine, browse the network to find the machine ANSYSSERVER. Open that machine and navigate to \ANSYS\V90\bin\intel. Open ans_admin.exe to run the ANS_ADMIN utility. Choose the Configure machine option. When prompted for the ANSYS installation directory, enter:
\\ANSYSSERVER\ANSYS INC\V90\Ansys
3.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
4.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
4. Post-Installation Procedures
After ANSYS is installed, you need to establish some system settings, including pathnames and environment variables. See your operating system documentation for specific instructions on setting paths and environment variables. The pathname to the procedure files (which run the executables) is already set on each machine so the users can run ANSYS from the DOS command line. See the ANSYS Operations Guide for more information on running ANSYS from the command line. 1. Add the following path to all ANSYS users' User Paths (right click My Computer and choose Properties> Advanced> Environment Variables and add a new user variable):
C:\Program Files\ANSYS Inc\V90\ANSYS\bin\<platform>
2.
Set the following ANSYS environment variables based on the behavior you want. To set environment variables: Windows XP: Choose Start>System Tasks>View System Information. Select the Advanced tab and click on the Environment Variables button. Click New and enter the desired value in the value field. Windows 2000: Choose Start>Settings>Control Panel and select System. Click on the Advanced tab, then click the Environment Variables button. Select either New or Edit (first highlight the environment variable if it already exists). Type the name in the Variable Name field and the desired setting in the Variable Value field. Click OK. The ANSYS90_DIR environment variable sets the location of the ANSYS directory hierarchy. The default value is c:\Program Files\Ansys Inc\V90\ANSYS. You probably will not need to reset this variable, unless you change the location of the installed files. ANSYS90_PRODUCT - set this to the correct product variable to run ANSYS to start with the correct ANSYS product without specifying the -p command modifier each time. ANSYS90_ALTPRODS - set this to specify alternate product choices with the priority you wish. If no licenses are available for your first product choice, the ANSYS program will automatically cascade through the specified alternative until it finds an available license. Use only in conjunction with the ANSYS90_PRODUCT environment variable. Separate each product with a colon (:) on UNIX platforms or with a semicolon (;) on Windows platforms.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows ANS_CONSEC - set this to YES to disable ANSYS dialog boxes and allow multiple jobs to run consecutively without waiting for user input. Settings for ANS_CONSEC are:
Value of ANS_CONSEC Not defined/default YES NO Batch Dialog Box No No Yes GPF Dialog Box on Error Yes No Yes
If you will be running Parallel Performance for ANSYS and using the DDS solver, the ANS_CONSEC must NOT be set to NO. ANSYS_LOCK - set to ON (default) to create file locks to prevent users from opening a new job with the same name and in the same directory as the current job. ANSYS90_DTM - set to ON to automatically activate the ANSYS LS-DYNA Drop Test Module (default = OFF). ANSYS90_PPFA - set to ON to automatically activate the Parallel Performance for ANSYS product (default = OFF). UGII_ROOT_DIR - defines the Unigraphics root directory. If Unigraphics is installed after ANSYS, the root directory must be appended to the system PATH. You must do this manually prior to running the Connection for Unigraphics product. ANSYS90_MAT161 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_MSC material (requires an LS-DYNA MAT_161 license). ANSYS90_MAT162 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_DMG_MSG material (requires an LS-DYNA MAT_162 license).
3.
Set the license manager to start automatically at boot time. For platform-specific instructions, see Table 4.1: License Manager Automatic Startup Instructions in the ANSYS, Inc. Licensing Guide. Designate server(s) for license checkout and establish necessary user privileges (recommended but not required). For information on these tasks, see the ANSYS, Inc. Licensing Guide. Make a backup copy of the \Ansys Inc directory.
4.
5.
10
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 6: Translated Message File Installation 6. Verify the ANSYS installation by logging out as root and logging back in as a regular user and then selecting each option from the Start menu to verify that they each start and run correctly. The license manager must be started before you can verify the installation. Run the ANS_ADMIN utility (Start>Programs>ANSYS Release 9.0>Utilities>ANS_ADMIN Utility) to properly configure ANSYS (depending on the products you are running) or relink ANSYS. Set the home directory. To set a home directory in Windows, you need to set a HOMEDRIVE environment variable to the desired drive letter (including the colon) and a HOMEPATH environment variable to the desired path. For example:
HOMEDRIVE=C: HOMEPATH=\Users\Mine
7.
8.
If you require verification of the ANSYS program, ANSYS, Inc. offers Quality Assurance programs for some ANSYS products. If you are interested in this service, go to http://www.ansys.com/services/quality_assurance/quality_services.htm or call the ANSYS, Inc. Quality Assurance Group at (724) 746-3304
11
2. 3.
Copy the message files (msgcat.90, msgidx.90, and msgfnm.90) into the newly created subdirectory. Access these message files by using the -l command line option. For example:
ansys90 -l fr
Or, when you are running ANSYS from the ANSYS launcher, choose the Language Selection option and then pick the desired language. You must create a newly translated message file for each release of ANSYS because error messages may occur in a different order for each release.
7. Uninstalling ANSYS
You must have an account with administrator privileges to uninstall ANSYS. To remove ANSYS from your system, follow these steps: 1. 2. 3. 4. 5. Click on the Start menu. Select Settings and then click Control Panel. Double-click Add/Remove Programs. Select ANSYS 9.0. Click on the Add/Remove button.
This procedure removes the ANSYS program from your system but will not remove the ANSYS licensing components. Before proceeding with the following steps to remove the ANSYS licensing components from your system, make certain that there are no ANSYS, Inc. products on this machine or any other machines on the network that rely on these ANSYS licensing components. Perform these steps ONLY if this system is an ANSYS FLEXlm License Manager server machine: 1. 2. In the ANSYS FLEXlm License Manager program folder, click on the FLEXlm LMTOOLS utility. Once in the LMTOOLS utility, select Configure Using Services and highlight ANSYS FLEXlm License Manager, listed in the box.
12
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 8: Connection Product Installation 3. 4. 5. Select the Start/Stop/Reread tab. ANSYS FLEXlm License Manager should be highlighted. Click on the Stop Service button. Select the Configure Services tab and highlight ANSYS FLEXlm License Manager. Click on the Remove Service button. Exit the LMTOOLS utility.
On all systems, follow these steps: 1. 2. 3. Delete the \Licensing subdirectory located under \Program Files\ANSYS Inc\Shared Files. Remove the ANSYS FLEXlm License Manager program folder from the Start menu. Remove the ANSYSLIC_DIR environment variable.
For complete information about the files you can import and the platforms supported by ANSYS Connections, see Introduction to Import of the ANSYS Connection User's Guide. Caution: Be sure to install ANSYS and the Connection products from the same CD release. If you attempt to run the latest ANSYS Connection product on a machine that is running an earlier release of ANSYS, the Connection may fail, or vice versa. ANSYS Connection for Pro/ENGINEER requires you to run ANSYS, Pro/ENGINEER and Connection for Pro/ENGINEER on the same machine. ANSYS Connection for Unigraphics requires you to run ANSYS, Unigraphics, and Connection for Unigraphics on the same machine. ANSYS Connections for CATIA, SAT, and Parasolid do not require any additional CAD installation.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
13
14
Section 8: Connection Product Installation ANS_ADMIN displays a confirmation message that the config file was successfully created. 5. Select OK to continue. ANS_ADMIN displays the following dialog:
6.
Enter the name of the Pro/ENGINEER installation path and the language (character set) used with Pro/ENGINEER. Select OK to continue. If a protk.dat file already exists, ANS_ADMIN displays a message similar to the following:
SUCCESS Entries for Connection for Pro/E have been appended to \<ProE_install_dir>\<proe_platform>\text\usacii\protk.dat
Caution: Check the protk.dat file for duplicate definitions. If you have installed other Pro/ENGINEER products before, you may have duplicate entries for the name of the executable and the revision. During the installation, ANSYS copies the protk.dat file to the Pro/ENGINEER installation directory, or if a protk.dat file already exists, the information is appended. Edit the protk.dat file and delete any duplicate definitions. The new file should have the following entries for the current release of this product, but may contain additional definitions if other Pro/ENGINEER products are in use:
name ac4pro90 exec_path <drive>:\Program Files\Ansys Inc\V90\ANSYS\ac4 \bin\pro\<platform>\ac4pro.exe text_path <drive>:\Program Files\Ansys Inc\V90\ANSYS\ac4 \data\pro\text revision 24.0 STARTUP dll end
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
15
ANSYS Installation and Configuration Guide for Windows Note Pro/ENGINEER cannot process UNC paths. Always use drive letters rather than UNC paths in the Pro/ENGINEER configuration files. 7. Select EXIT to close ANS_ADMIN.
By default, the protk.dat file for Pro/ENGINEER 2001 contains the following information for Windows:
name ac4pro90dll exec_path C:\Program Files\Ansys Inc\v90\ANSYS\ac4\bin\pro\Intel\ac4pro.exe text_path C:\Program Files\Ansys Inc\v90\ANSYS\ac4\data\pro\text STARTUP dll delay_start FALSE allow_stop TRUE revision 24.0 end
If a protk.dat file exists in the Pro/ENGINEER working directory, this file must be updated to contain the information listed above. You may copy the protk.dat file into the Pro/ENGINEER working directory and should modify the file whenever Pro/ENGINEER is upgraded. Do not delete any of these lines. If you modify this file, do not enter a carriage return after the END line. The file may be customized with other information. If these lines are deleted, or if the protk.dat file is not present in any of the directories in the search path, Pro/ENGINEER will not load. Pro/ENGINEER searches for the protk.dat file in the following locations: 1. 2. Pro/ENGINEER working directory (directory from which Pro/E was launched)
<proe_install>\<proe_platform>\text\<LANG>
16
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
The <proe_platform> variable is the name that Pro/ENGINEER gives to its platform directories. Pro/ENGINEER platform names are similar, but not identical, to the ANSYS platform names:
Hardware Platform ANSYS Platform <platform> Intel Intel Pro/ENGINEER Platform <proe_platform> i486_nt
**These variables are not supported by Pro/ENGINEER and are ignored by Pro/ENGINEER. See Setting ANSYS Configuration Parameters in the ANSYS Connection User's Guide for more information about the config.anscon file.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
17
9. Installation Troubleshooting
This section lists problems and error messages that you may encounter while installing and/or running the ANSYS program. After each situation description or error message is the user action required to correct the problem. For information on licensing-related errors, see the Chapter 7, Troubleshooting section of the ANSYS, Inc. Licensing Guide. In addition, this appendix describes the ansys_pid utility, which is useful for troubleshooting some problems.
18
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
To reset Windows XP Windows Ghosting for ANSYS, follow the procedure below: 1. Open a DOS command prompt and type the following command:
sdbinst /U "%ANSYS90_DIR%\bin\intel\ansys90.sdb"
2.
A Compatibility Database Installer dialog box stating "Uninstallation of ANSYS90 complete" will be displayed. Click OK.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
19
20
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Configuring Distributed ANSYS and the Distributed Solvers You will need at minimum one PPFA license for each job. All machines must have the same version of MPI software installed and running. You can run the system's native MPI (typically installed with the OS), or MPICH (installed with an ANSYS installation, where supported). The table below shows the native MPI software and version level for each platform. If you plan to use only the AMG solver in shared-memory ANSYS, MPI software is not required. It is required only for the distributed solvers. If you are using only the AMG solver, skip the rest of this document and continue with Using the Parallel Performance for ANSYS Add-On in the ANSYS Advanced Analysis Techniques Guide.
22
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
SGI 64-bit MPI 4.3 (MPT 1.8) with http://www.sgi.com/software/mpt/overview.html /IRIX64 6.5.23m array services 3.5 Sun UltraSPARC HPC CLUSTERTOOLS 64-bit / Solaris 8, 5.0 UltraSPARC III and IV 64-bit / Solaris 8 Intel IA-32 Linux MPI/Pro 1.6.5 / RedHat AS 2.1 Kernel 2.4.9 Intel IA-64 Linux MPICH-1.2.5 / RedHat AS 2.1 Kernel 2.4.18 and AMD Opteron 64-bit Linux / SuSE Kernel 2.4.21 Fujitsu SPARC64 Parallelnavi 2.1 IV / Solaris 8 Intel IA-32 bit / MPI/Pro 1.6.5 Windows XP Home or Professional (Build 2600) Version 5.1, Windows 2000 Version 5.0 (Build 2195) http://www.sun.com/hpc/communitysource/
http://www.mpi-softtech.com
23
5. 6. 7. 8.
If you are using MPICH and running the distributed solvers in shared-memory ANSYS, you will need to use an alternate ANSYS script and executable when using the distributed solvers. For MPICH, use the ansddsmpich script and the ansddsmpich.exe executable. See the ANSYS Advanced Analysis Techniques Guide for more information.
Section 2: Setting Up the Environment for Distributed ANSYS or the Distributed using the following procedure. This procedure applies to both Distributed ANSYS (on supported platforms) and to the distributed solvers running under shared-memory ANSYS. 1. Obtain the machine name for each machine on the cluster. You will need this name to set up the Configure Cluster option of the ANS_ADMIN utility in Step 3. Windows: Right-click on My Computer, left-click on Properties, and select the Network Identification or Computer Name tab. The full computer name will be listed. Note the name of each machine (not including the domain). UNIX/Linux: Type hostname on each machine in the cluster. Note the name of each machine. You will need this name to set up the .rhosts file, as well as for the ANS_ADMIN utility. 2. (UNIX/Linux only) Set up the .rhosts file on each machine. The .rhosts file lists all machines in the cluster. The machines should be listed using their complete system name, as taken from uname. For example, an .rhosts file for a two-machine cluster might look like this:
golinux1.ansys.com jqd golinux2 jqd
Verify communication between machines via rsh (e.g., rsh golinux2 ls). You should not be prompted for a password. If you are, check the .rhosts permissions and machine names for correctness. If you plan to run the distributed solvers on one machine with multiple processors in a shared memory environment, you need to have the MPI software installed, but you do not need the .rhosts file. 3. Configure the hosts90.ans file. Use the ANS_ADMIN utility to configure this file. You can manually modify the file later, but we strongly recommend that you use ANS_ADMIN to create this file initially to ensure that you establish the correct format. Windows: Start >Programs >ANSYS 9.0 >Utilities >ANS_ADMIN
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
25
Choose Configuration options, and then click Configure Cluster. Choose the hosts90.ans file to be configured and click OK. Then enter the system name (from Step 1) in the Machine hostname field and click Add. On the next dialog box, enter the system type in the Machine type drop-down, and the number of processors in the Max number of jobs field for each machine in the cluster. The working directory field also requires an entry, but this entry is not used by Distributed ANSYS or the distributed solvers. The remaining fields do not require entries. The hosts90.ans should be located in your current working directory, your home directory, or the apdl directory. 4. For running Distributed ANSYS with MPICH: The ANSYS90_DIR and the dynamic load library path (e.g., LD_LIBRARY_PATH) must be set by the appropriate shell startup script in order to run Distributed ANSYS with MPICH. Use the following scripts (supplied with ANSYS) to configure the distributed environment correctly for MPICH. For csh or tcsh shells, add the following line to your .cshrc, .tcshrc, or equivalent shell startup file:
source /ansys_inc/v90/ansys/bin/confdismpich90.csh
For sh or bash shells, add the following line to your .login, .profile, or equivalent shell startup file:
. /ansys_inc/v90/ansys/bin/confdismpich90.sh
As a test, rsh into all machines in the cluster (including the master) and verify that the ANSYS90_DIR and the LD_LIBRARY_PATH are set correctly. For example:
rsh master1 env | grep ANSYS90_DIR
and
rsh master1 env | grep LD_LIBRARY
Note Adding these confdismpich90 lines to your shell startup file will place the required ANSYS load library path settings in front of any existing system load library settings and will likely affect other applications, including native MPI. If you have problems running other applications after including these scripts, you will need to comment out these lines to run the other applications. 5. On UNIX/Linux systems, you can also 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 out on the start-up of the client (default is 15 seconds). ANSYS_NETWORK_COMM - This is the time to wait, in seconds, before timing out while communicating with the client machine (default is 5 seconds).
ON IBM systems: LIBPATH - on IBM, if POE is installed in a directory other than the default (/usr/lpp/ppe.poe), you must supply the installed directory path via the LIBPATH environment variable:
export LIBPATH=nondefault-directory-path/lib
On SGI systems: On SGI, in some cases, the default settings for environment variables MPI_MSGS_PER_PROC and MPI_REQUEST_MAX may be too low and may need to be increased. See the MPI documentation for SGI for more information on settings for these and other environment variables. On SGI, 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 be running 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 distributed solvers. The local hostname of the machine must be listed first in this file.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
27
Configuring Distributed ANSYS and the Distributed Solvers To verify that these environment variables are set correctly on each machine, run:
rsh machine1 env
On Windows systems only (for running the distributed solvers): If Windows running MPICH: Add C:\Program Files\MPICH\mpd\bin to the PATH environmental variable on all Windows machines (assuming MPICH was installed on the C:\ drive). This line must be in your path for distributed processing to work correctly.
On UNIX:
/ansys_inc/v90/ansys/bin/mpitest90
28
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
Section 2: Setting Up the Environment for Distributed ANSYS or the Distributed has four processors and gowindows2 has two, the machines file would look like this: gowindows1 gowindows1 gowindows1 gowindows1 gowindows2 gowindows2 Note You can also simply list the number of processors on the same line: gowindows1 4. 3. From a command prompt, navigate to your working directory. Run the following:
mpirun -np x -mf machines "C:\Program Files\ANSYS Inc\V90\ANSYS\bin\platform\mpitest.exe"
where x is the number of processors in your machines file (6 in this example). On Windows running MPICH:: 1. 2. Create a file named machines in your local/home directory. Open the machines file in an editor. Add your master and slave machines in your cluster. For example, in this cluster of two machines, the master machine is gowindows1. List the machine name separately for each processor (CPU) on that machine. For example, if gowindows1 has four processors and gowindows2 has two, the machines file would look like this: gowindows1 gowindows1 gowindows1 gowindows1 gowindows2 gowindows2 Note You can also simply list the number of processors on the same line: gowindows1 4. 3. From a command prompt, navigate to your working directory. Run the following:
mpirun -np x -machinefile machines "C:\Program Files\ANSYS Inc\V90\ANSYS\bin\platform\mpitest.exe"
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
29
Configuring Distributed ANSYS and the Distributed Solvers where x is the number of processors in your machines file (6 in this example). On Linux running MPICH: Note These instructions are typically done one time by the system administrator. Individual users may not have the necessary privileges to complete all of these steps. 1. 2. Edit the machines file. Navigate to the /ansys_inc/v90/ansys/mpich/<platform>/share subdirectory. Open the file machines.LINUX in an editor. In the machines.LINUX file, change machine1 to the master machine in your Linux cluster. For example, in our cluster of two machines, the master machine is golinux1. List the machine name separately for each processor (CPU) on that machine. For example, if golinux1 has four processors and golinux2 has two, the machines.LINUX file would look like this: golinux1 golinux1 golinux1 golinux1 golinux2 golinux2 Delete any other machines listed. Note If you are running an SMP box, you will simply list the number of processors on the same line: golinux1 4. 3. 4. Edit the mpitestmpich90 script to read np = x where x is the number of processors in your machines.LINUX file. Navigate to your working directory. Run the following:
/ansys_inc/v90/ansys/bin/mpitestmpich90
On Linux running MPI/Pro: 1. 2. Edit the machines file in the /etc subdirectory. Open the machines file in an editor. In the machines file, change machine1 to the master machine in your Linux cluster. For example, in our cluster of two machines, the master machine is golinux1. List the machine name separately for each processor (CPU) on that
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
30
Section 2: Setting Up the Environment for Distributed ANSYS or the Distributed machine. For example, if golinux1 has four processors and golinux2 has two, the machines file would look like this: golinux1 golinux1 golinux1 golinux1 golinux2 golinux2 Delete any other machines listed. 3. 4. Edit the mpitest90 script to read np = x where x is the number of processors in your machines file. Navigate to your working directory. Run the following:
/ansys_inc/v90/ansys/bin/mpitest90
On UNIX machines running native MPI: The process is the same as described for running MPICH on Linux machines (above), but you will need to contact your MPI vendor to find out where the appropriate machines file resides and how to edit it. Once you have properly edited the machines file following your vendor's instructions, edit mpitest90 to read np = x where x is the number of processors in your machines file.
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.
31
Configuring Distributed ANSYS and the Distributed Solvers Deploy 64-bit platforms such as Linux on Itanium or AMD chips. Use the /3GB switch on 32-bit platforms on Windows systems. As a broad guideline, use the following formula to get a general idea of memory usage for the DPCG solver. In this formula, n is the total number of CPU processors used, and MDOF is million degrees of freedom. Master machine (Machine 0): MDOF(maximum) = Machine(0) Memory(GB) / (0.1 + 1.0/No. of machines) Slave machines (Machine 1 - n): MDOF(maximum) = Machines (1...n)Memory(GB)*
n
For example, if you have a master machine that is a 32-bit Windows machine with 2.2 GB available RAM, using the /3GB switch, and a total of four machines in the cluster, you could solve a problem up to 6.3 MDOF: MDOF = 2.2 GB / (0.1 + 1 / 4) = 6.3 MDOF In this scenario, the slave machines must have 6.3 / 4 or 1.575 GB of available memory.
32
ANSYS Installation and Configuration Guide for Windows . ANSYS Release 9.0 . 002094 . SAS IP, Inc.