You are on page 1of 46

STAR-CD INSTALLATION GUIDE

Version 4.08.009
(Updated: 2 January 2009)

CONFIDENTIAL FOR AUTHORISED USERS ONLY

Formatted for duplex A4 printing

1988-2008 CD-adapco

TABLE OF CONTENTS
1 SYSTEM REQUIREMENTS AND LIMITATIONS Supported Systems .................................................................................................... 1-1 End of Life Notices for STAR-CD ports .................................................................. 1-3 Graphics Support ...................................................................................................... 1-4 Disk Space Requirements ......................................................................................... 1-4 Paging/Swap Space Requirements ........................................................................... 1-4 System-specific Issues .............................................................................................. 1-5 STAR-CD INSTALLATION Introduction ............................................................................................................... 2-1 STAR-CD suite installation on UNIX. ..................................................................... 2-2 STAR-CD suite installation on Windows ................................................................. 2-7 LICENSING FLEXlm Version 10.8.0.7 ........................................................................................ 3-1 Vendor Daemon Name ............................................................................................. 3-1 Starting the License Daemon .................................................................................... 3-1 License File Location ............................................................................................... 3-2 Environmental Variables .......................................................................................... 3-2 Configuration of FLEXlm license manager on Windows ........................................ 3-3 TESTING THE INSTALLATION Setup User Environment to Run STAR .................................................................... 4-1 Create a Working Directory ...................................................................................... 4-1 Automatically Generate the Case Using Pre-processor ............................................ 4-2 Run the STAR solver ................................................................................................ 4-2

Appendix A hardware.ini (SITE SPECIFIC CONFIGURATION FILE) Default Settings ....................................................................................................... A-1 Platform Settings ..................................................................................................... A-1 Host Settings ............................................................................................................ A-2 Group Settings ......................................................................................................... A-3 Appendix B software.ini (SOFTWARE CONFIGURATION FILE) Default Settings ........................................................................................................B-1
Version 4.08 (Updated: 17 November 2008) 1

Platform Settings ......................................................................................................B-2 Group Settings ..........................................................................................................B-2 Example software.ini ................................................................................................B-3 Appendix C Microsoft Windows Compute Cluster Server Installing Windows CCS Environment ....................................................................C-1 Setting up a Cluster ...................................................................................................C-1 Configure the Cluster ................................................................................................C-2 Appendix D Compilers Used to Build the Software Porting Reference Platforms for the STAR Solver .................................................. D-1 Porting Reference Platforms for the Advanced Pre-/Post-processor ....................... D-2

Version 4.08 (Updated: 17 November 2008)

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS Supported Systems

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS


This document applies to STAR-CD version 4.08, the current release of the STAR-CD suite of simulation software for continuum mechanics. A separately installed FORTRAN 90 compiler is only required if the user wishes to implement User Coding (In Appendix D, Table D.1 outlines appropriate compilers for each machine type). Users who wish to use the non-default installations are directed to the appendices for information about different ways to configure the software.

Supported Systems

Table 1-1 Minimum System Requirements of STAR-CD STAR-CD Platform AIX Power (64bit) HP-UX PA-Risc (64bit) HP-UX Itanium (64bit) Operating System AIX 5.2 (64bit) HP-UX 11.11 (64bit) HP-UX 11.23 (64bit) CPU Type IBM POWER 3 (64bit) HP PA8000 (64bit) Intel Itanium 2 (64bit) AMD x86 and Intel x86 (32bit) AMD64 and Intel EM64T (64bit AMD64 and Intel EM64T (64bit) AMD64 and Intel EM64T (64bit) Intel Itanium 2 (64bit)

Linux x86 (32bit)

Linux 2.4, glibc 2.2.2 (32bit)

Linux 2.4, glibc 2.2.5 (64bit) Linux x86_64 (64bit) Linux Itanium (64bit) Linux 2.4, glibc 2.2.5 (64bit) Linux 2.4, glibc 2.2.4 (64bit)

Version 4.08 (Updated: 17 November 2008)

1-1

SYSTEM REQUIREMENTS AND LIMITATIONS Supported Systems

Section 1

Table 1-1 Minimum System Requirements of STAR-CD STAR-CD Platform SunOS UltraSPARC (64bit) Operating System SunOS 5.10 aka Solaris 10 (64bit) Windows XP SP2, Windows Server 2003 SP1 and Windows Vista SP1 (32bit) Windows x86 (32bit) Windows XP x64 SP2, Windows Server 2003 x64, Windows CCS and Windows Vista SP1 (64bit) Windows XP x64 SP2, Windows Server 2003 x64, Windows CCS and Windows Vista SP1 (64bit) CPU Type SUN UltraSPARC III (64bit) AMD x86 and Intel x86 (32bit) AMD64 and Intel EM64T (64bit AMD64 and Intel EM64T (64bit)

Windows x64 (64bit)

AMD64 and Intel EM64T (64bit)

Linux x86, x86_64 and Itanium are tested and supported on Red Hat Enterprise Linux (RHEL) and SuSE Linux Enterprise Server/Desktop (SLES/SLED). STAR-CD is known to run on RHEL 3/4/5 and SLES 8/9/10. Some of these versions may require OS patches to function properly. CD-adapco makes no claim for suitability of other Linux distributions not mentioned above. Please note that Windows Server 2008 and Windows HPC Server 2008 are not supported with the initial release, but will be supported as soon as possible thereafter.

1-2

Version 4.08 (Updated: 17 November 2008)

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS End of Life Notices for STAR-CD ports

HPC mode (parallel computation) will require implementations of MPI (Message Passing Interface) compiled for specific operating systems. Versions are available from several operating system vendors. Those MPI implementations are usually optimised by the operating system vendor for their platforms, and therefore often offer better performance than third party vendors MPI implementations. Alternative third party vendors MPI implementations (e.g. MPICH-GM, ScaMPI, LAM MPI and MPICH) can be used. HP MPI (an implementation of MPI developed by Hewlett Packard) is now supplied with the STAR-CD distribution. It is available for HP-UX, Linux and Windows only. On the UNIX platforms, the public domain LAM MPI and MPICH implementations of MPI are provided as pre-compiled libraries for some of the supported operating systems which are selectable during the installation process.

End of Life Notices for STAR-CD ports


STAR-CD version 4.08 will be the last STAR-CD version developed and bug fix patches issued for the following systems: HP-UX Itanium platform. SunOS UltraSPARC platform. AIX Power port on AIX 5.2. This will be replaced by a new port on a newer IBM AIX operating system. Linux Itanium support for RHEL 2.1. Newer Linux distributions will continue to be supported.

In addition, though a final decision has not been made, either the STAR-CD 4.08 or 4.10 release may be the final development version issued for the following systems: Linux x86 (32bit) platform. Linux x86_64 platform running RHEL 3 or SLES 8. Newer porting reference systems are currently being considered Linux x86_64 platform compiled with the Absoft Fortran compiler. The latest benchmark results show that STAR-CD typically run signicantly faster using the PGI Fortran compiler. While the actual speed up is case and system dependent, observed gains typically range from 15 to 23%. The PGI Fortran compiler port has been supported since STAR-CD 3.26 and was the default port for STAR-CD 4.06 release. In addition, ports of STAR using the Intel compiler are being considered as this has the potential for even better performance. The most likely scenario is that STAR will be supported for PGI and Intel compilers.

Version 4.08 (Updated: 17 November 2008)

1-3

SYSTEM REQUIREMENTS AND LIMITATIONS Graphics Support

Section 1

Graphics Support
The GUI for pro-STAR, the advanced pre- and post-processing tool, has been rewritten and now uses the Qt GUI toolkit. The Motif based version has been discontinued. On UNIX-type systems, the command-line-only pro-STAR X-Window system driver (prostar x) continues to remain available. On Windows systems, the X driver has been discontinued. OpenGL runtime libraries and appropriate hardware are required to run the default OpenGL graphics driver. These runtime libraries are usually available for free on most systems, but are not necessarily part of the default operating system installation. If the user does not have the appropriate OpenGL hardware or drivers, an alternate Mesa graphics driver can be used. Mesa provides a software based implementation of OpenGL. When activated, this software emulation of hardware will typically result in much slower plotting than a hardware based solution.

Disk Space Requirements


The disk space requirements varies considerably between each of the STAR-CD ports. Allow between 600MB and 1GB of free disk space for a single port full installation.

Paging/Swap Space Requirements


Most virtual memory computers will not run a program unless the operating system can pre-allocate swap space for the executable, irrespective of the available free memory. Thus the swap space should minimally equal the amount of installed memory and should typically be set to 2-4 times the system memory. This would allow users to run executables significantly larger than the available memory, or run a number of large executables simultaneously. However performance will be significantly degraded if the system is paging heavily.

1-4

Version 4.08 (Updated: 17 November 2008)

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

System-specic Issues
CSH/TCSH problems with MPI on clusters Users with either csh or tcsh as their default shell need to be aware of potential MPI problems caused by poorly written .cshrc files. This file is executed whenever a new shell is created and this can cause MPI jobs to fail. Examples of problems are setting TMPDIR or stty settings without checking whether a shell is running in batch mode or under remote shell session. If STAR fails to run on a cluster and renaming your .cshrc file fixes the problem then you have a poorly written .cshrc file. This problem can be avoided by setting TMPDIR to a local disk and protecting settings like stty with an if conditional to test for interactive sessions:
if ( $?TERM && "tty | \grep -v not a tty" != "" ) then

Most people dont need a .cshrc and renaming this file to .login will also work. Please note that the ksh and bash shells do not have any of these problems.

AIX Power (IBM) Kernel parameters Check that the user resource limits are set appropriately with the command smit users (MAX FILE size, MAX DATA segment, MAX STACK size, MAX physical MEMORY).

HP-UX PA-Risc

Kernel Parameters Depending on the size of the cases being run, some kernel parameters may need to be raised above their default settings. This can be done through the sam interface. Parameters which should be checked are: maxdsiz maxssiz shmmax (if running on a shared memory computer)

Version 4.08 (Updated: 17 November 2008)

1-5

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

Section 1

HP-UX Itanium HP recommend using HPUX11i v2 TCOE (Technical Computing Operating Environment).

Linux x86, x86_64 and Itanium

pro-STAR On 32bit Linux x86 systems there is pro-STAR available for operating systems with glibc 2.2 and a glibc 2.3.2 version. The entries in the software.ini file will ensure that the correct version of pro-STAR is set. A new port for Linux Itanium has been prepared to support older operating systems with glibc 2.2.4 and there is still a port to support more recent operating systems after glibc 2.3.2:

platform Linux_Itanium PROSTAR=$PROSTARTOP/linux64_2.4-itanium-glibc_2.2.4-icc_9.1 group Linux_Itanium-glibc_2.3.2 PROSTAR=$PROSTARTOP/linux64_2.4-itanium-glibc_2.3.2

The GUI for pro-STAR is built with XFree86 and works well with the Gnome and KDE desktop environments. There is an incompatibility between the extended mode (glm) driver in pro-STAR and certain NVIDIA drivers on Linux. Specifically, versions 1.0-5336 and 1.0-5328 of the NVIDIA drivers are known to cause the X server to crash upon exit from pro-STAR. The issue is being addressed, and we expect a patch for pro-STAR will be available to partially alleviate the problems. However, we believe that the basic problem is with these drivers. The NVIDIA 1.0-4436 drivers are known to be completely compatible with pro-STAR.

STAR Solver On some 32bit Linux x86 systems the matching GNU C++ 2.x run time library may be missing:
star: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory

Install the GNU C++ 2.x /usr/lib/libstdc++-libc6.2-2.so.3 run time library.

1-6

Version 4.08 (Updated: 17 November 2008)

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

SunOS UltraSPARC (Solaris) pro-STAR For the whole STAR-CD suite to work coherently on one computer system the minimum level for Solaris is 10 (i.e. SunOS 5.10), this is because the solver component does not work on the older version of the operating system. The build of pro-STAR now uses Sun Studio 10 and the following should be applied for the program to work on systems with other compilers installed. From /opt/SUNWspro/READMEs/c++:
5. C++ Shared Library Patch A SUNWlibC patch is provided for each version of the Solaris Operating Environment supported by this Sun Studio 10 release on each of the supported platforms. The patch should be installed not only on the systems used for compiling, but on all systems where the resulting programs are run. Without these patches, some programs fail to link and some programs terminate in unusual ways due to runtime errors.

http://developers.sun.com/prodtech/cc/downloads/patches/ss10_patches.html

MPI on Clusters In order to run the STAR solver with SUN MPI on two or more nodes they must be part of the same cluster. To change this, deactivate Sun HPC Cluster Tools in one of the machines and then reactivate it as part of the other machines cluster. For example, log in as root on suna and deactivate cluster tools:

root@suna # /opt/SUNWhpc/HPC5.0/bin/Install_Utilities/bin/ctdeact -l

Make sure that root can rsh from suna to sunb. Then activate Sun HPC ClusterTools on each node, as part of the same cluster:

root@suna # /opt/SUNWhpc/HPC5.0/bin/Install_Utilities/bin/ctact -m hostnameB l

Rerun part_initialize, in order to add sunb into sunas all partition:


root@suna # /opt/SUNWhpc/sbin/part_initialize

Run mpinfo -N and check if both nodes are now part of the same cluster:
root@suna # /opt/SUNWhpc/bin/mpinfo -N NAME UP PARTITION OS OSREL NCPU FMEM FSWP LOAD1 LOAD5 LOAD15 suna y all SunOS 5.8 4 2576 8414 0.04 0.06 0.05 sunb Y all SunOS 5.8 1 537.31 3195 0.02 0.04 0.02

Version 4.08 (Updated: 17 November 2008)

1-7

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

Section 1

Windows x86 & x64 Intel Compiler Installation STAR-CD for Windows requires Intel Fortran 10.1 only if user coding compilation is needed. The Intel Visual Fortran Compiler 10.1 is available for purchase from: http://www.intel.com. In addition to the Fortran compiler, the Microsoft Visual Studio 2005 and Microsoft Windows SDK for Windows Server 2003 are additional dependencies required. Please install Microsoft Visual Studio 2005, then the Intel Fortran compiler and finally the Windows Server 2003 R2 Platform SDK. If you do not own Microsoft Visual Studio 2005, perform a default install of Microsoft Visual C++ Express Edition 2005 which can be downloaded from: http://www.microsoft.com/express/2005/

Please perform a default install of the Windows SDK for Windows Server 2003 R2, which is available for download from:

http://www.microsoft.com/downloadS/details.aspx?FamilyID=0baf2b35-c656-49 69-ace8-e4c0c0716adb&displaylang=en

To reduce installation time, select headers and libraries only. The PATH, LIB, and INCLUDE environment variables now need to be set so that you can access these tools. The Intel Fortran compiler sets its environment using the ifortvars.bat, Visual studio uses vcvarsall.bat, and the Microsoft platform sdk uses setenv.cmd. The tools needed to compile user coding are configured when the star environment is started from the menu item using a configuration file called autoenv-intel101.bat. An example config file called autoenv-intel101.bat.example can be found in the <INSTALLED LOC>\STAR-CD\bin directory. This file must be renamed and modified as necessary

1-8

Version 4.08 (Updated: 17 November 2008)

Section 1

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

Running on clusters If you are using a third party firewall or have Microsoft Firewall switched on, you must add an exception for the star4.08.exe pro-gl.exe executables. If you are planning to run STAR-CD on Windows XP you must disable simple file sharing by selecting:

Control Panel > Appearance and Themes > Folder Options > View Tab

At the bottom of the Advanced Settings scroll box, unselect Use simple file sharing. STAR-CD runs require the user to have power user rights or higher on the local machine starting the run. Power user rights are not required for shared memory runs on the local machine. To configure this, login to node which will start the run with administrator privilege.

If you are not using a domain controller: Select Administrator Tools > Computer Management > Local Users and Groups > Users > Account Name of Users running STAR-CD Right click and select properties. Select the member of tab, click the advanced button, and then nd now button. Select Power User or Administrator and click ok.

If you are using a domain controller: Select Administrator Tools > Computer Management > Local Users and Groups > Groups > Power User or Administrator. Right click and select properties. Click add, then advanced button, and then nd now button. Select Domain Users and click ok.

Version 4.08 (Updated: 17 November 2008)

1-9

SYSTEM REQUIREMENTS AND LIMITATIONS System-specic Issues

Section 1

If your system administrator does not wish to add all Domain users as power users on the local machine, they can add individual users or create a STAR-CD users group. Privileges can also be added from the command line using the net local group "power user" "domain name\account name or group" /add command.

1-10

Version 4.08 (Updated: 17 November 2008)

Section 2

STAR-CD INSTALLATION Introduction

Section 2

STAR-CD INSTALLATION
This new version of STAR-CD is released primarily through FTP although DVD-ROMs will be made available for customers who need that format. The DVD-ROM is ISO 9660 level 3 format with Rock Ridge and Joliet extensions. No matter in which form the data is received, the following is the minimum that is required to be installed to run STAR-CD: pro-STAR (pre-processor and post-processor) STAR (the continuum mechanics solver) RUNTIME (to support the operation of pro-STAR and STAR) FLEXlm (can be omitted if FLEXlm is already available)

Introduction

The following optional components are available for unix in the same package: STAR-Launch (provides a GUI to launch all of the STAR-CD suite) STAR-NET (for running under LSF, OpenPBS, SGE and Torque) HP MPI 2.2.5.1 (for HPC operation on some systems) LAM MPI 7.0 (for HPC operation on some systems) MPICH 1.2.4 (for HPC operation on all the supported systems) Common (Contains the manuals and tutorials, it is recommended that these are installed. The source code for LAM and MPICH is also provided for users who wish to compile it for their own use). Additionally plugins are provided. Please check the installation messages for a full list of available software and versions. Several other software components are supplied and these are presented during the installation. Several of these were previously included as pre-installed plugins, but now they can be installed in a separate manner allowing users to try different versions of the additional software without disturbing existing installations, currently they include the following: DARSCFD, DOLFA and ICE.

The following optional components are available for Windows in the same package: HP MPI 1.1 .NET 1.1 Framework (for 32bit windows only) .NET 2.0 Framework MPICH2 (for parallel operation of the STAR solver) Intel Runtime Libraries 10.1 Microsoft Visual C++ 2005 Redistributable Package MSYS 1.0.11

Version 4.08 (Updated: 23 December 2008)

2-1

STAR-CD INSTALLATION STAR-CD suite installation on UNIX.

Section 2

STAR-CD suite installation on UNIX.


In these instructions it is assumed that you will install STAR-CD in a directory called /opt/starcd. If you wish to use another directory, replace /opt/starcd with the actual full path directory name. Installing from FTP Package Installing from the FTP package is very much the same as installing from the DVD-ROM. The tar files should be unpacked into a temporary directory (for example /tmp/star_pkg). The unpacked size will be the same as the download because it contains other compressed archive files (bzip2 and 7za tools are supplied to support installation). The components that are not critical to the workings of the software are contained in a separate package (usually with the reference string Common in the filename). Typically they will be platform independent and include manuals and tutorials. We recommend that you install these as some are accessible through the GUI and warnings are generated during the initialisation of pro-STAR. They also contain a copy of the release notes, although the most up-to-date versions can be downloaded from User Services. Follow the instructions in the Installing the Software section by substituting for the string /opt/starcd with the location of the distribution on your site. Mounting the Installation DVD-ROM Hardcopy versions of the software distributions are only available at special request. Previous versions of STAR-CD distributed by CD-ROM allowed users to install directly from a file-manager GUI. This is no longer available and data must be transferred from the DVD-ROM before it is possible to run the installation script. The content of the DVD-ROM is a mirror of the data on the User Services web site (https://support.cd-adapco.com). The DVD-ROM is written to the ISO9660 Level 3 standard with Rock Ridge and Joliet extensions so that it can be read on the seven major platforms including Microsoft Windows. If The DVD-ROM media is DVD+R, so the reading device must be compatible to access the data on the disk. If the DVD-ROM does not automatically mount please mount the disk manually as directed in the hardware user guide for your system. Installing the Software In this section the location /tmp/star_pkg can refer equally to the location of the tar files unpacked from DVD-ROM or the unpacked FTP download. It is assumed here (for example) that the destination is /opt/starcd. It is strongly recommended to run the installer as a normal user like starcd or software instead of using the root account. This is because the installation of process of STAR-CD does not require administrative permission.

2-2

Version 4.08 (Updated: 23 December 2008)

Section 2

STAR-CD INSTALLATION STAR-CD suite installation on UNIX.

Change directory to /tmp/star_pkg execute the setup script with the command sh ./setup. It is recommended not to run the installer as root as it is not necessary to have administrative permission to install STAR-CD. The script can be interrupted at any time before the final stage in which the actual installation of files is initiated (usually <CTRL>-C). This script lists the various required packages and optional packages available on the DVD-ROM and prompts the user to select a system for installation. It will also prompt the user for the installation directory, and create it if necessary. The installation process can be repeated for numerous product and platform combinations. The installation script makes no assumption about the intended target platform, so (except for the previously mentioned limitation of SunOS 5.10) all products may be installed on a central server or over a network if the target system has no DVD-ROM reader. After all the specified software has been installed, the Software Administrator should check that the following files are up-to-date: /opt/starcd/doc/install.pdf /opt/starcd/doc/prostar-error-report.pdf /opt/starcd/doc/star-error-report.pdf /opt/starcd/doc/star_rnotes.pdf These documents are occasionally updated after the creation of the archives supplied with the tar les or on DVD-ROM. Please check the copies on the User Services web site (https://support.cd-adapco.com) or contact your support representative. The PDF les are accessible to users through the pro-STAR help menu.

Initialising the Software The installation tool allows any number of platform specific software to be installed below the same STARDIR location. Subsequent installation processes will not affect any configuration files that are already in the $STARDIR/etc directory. Repeated installation action creates files with an extension -new (for example software.ini-new) that can be renamed as the Software Administrator wishes provided that the filename extension is retained as .ini. The new configuration file can be activated by issuing the command setstar after an initialisation of the default system. A menu is presented allowing the user to select the appropriate configuration file. Local copies of the software.ini file can be created to tailor the installation for variation of versions or non-default ports. For example, one might create a file named alternate.ini in the $STARDIR/etc directory that activates a non-default port of STAR solver. Or make a copy in ones home directory with different settings. To activate the alternative INI files, a repeated call to setstar offers a menu of options for different configuration files. If you choose the last option on the list, then the full path to the file must be specified.

Version 4.08 (Updated: 23 December 2008)

2-3

STAR-CD INSTALLATION STAR-CD suite installation on UNIX.

Section 2

Hardware and Software Conguration The installation directory will contain: bin/ doc/ etc/ PROSTAR/ RUNTIME/ STAR/ (Plus others) The etc directory contains three important conguration les. The hardware.ini le contains site hardware and license information. The software.ini le contains installation specic information. The setstar le congures the users environment to be able to run STAR. hardware.ini An example hardware.ini le is written with the installation. A full list of all options is given in Appendix A, and these can be optimised for each site. However, during the installation the Software Administrator answers two questions about licensing. The results are placed in the hardware.ini le. This is all that is required in order to test the software. software.ini Under normal circumstances, the software.ini should not need editing. However, there may be occasions where non-standard installation combinations are required, and Appendix B contains a list of options and instructions for these circumstance. setstar This le should not be edited. The end user simply executes the following shell dependent commands. For Bourne, Korn or Bash shells: . /opt/starcd/etc/setstar For C and Tcsh shells: source /opt/starcd/etc/setstar

2-4

Version 4.08 (Updated: 23 December 2008)

Section 2

STAR-CD INSTALLATION STAR-CD suite installation on UNIX.

STAR version information will be printed out in the terminal screen, for example, on a linux platform:
STARDIR: /opt/starcd STARINI: Default CDLMD_LICENSE_FILE: 19999@cstarlicenseserver LM_LICENSE_FILE: 12345@otherlicenseserver ABSOFT: LAMHOME: PROSTAR: RUNTIME: STAR: STARLAUNCH: STARNET: /opt/absoft $STARDIR/LAM/7.0/linux_2.4-gcc_2.95.3-glibc_2.2.2-dso $STARDIR/PROSTAR/4.06.*/linux_2.2-x86 $STARDIR/RUNTIME/1.04.006/linux_2.4-x86 $STARDIR/STAR/4.06.*/linux64_2.4-pgf90_6.2-glibc_2.2.5-dso $STARDIR/STARLAUNCH/2.*/linux_2.2-x86 $STARDIR/STARNET/3.00.014/generic

Activating Alternative Conguration In this example three additional INI files have been created by the local site Software Administrator: absoft_9.ini, aix_53.ini, pgi_6.ini that can be accessed through a subsequent call to setstar after the initialisation of the default installation. These give access to additional platforms where they are supplied. Their naming is arbitrary and down to a site policy:
user@host_$ setstar STAR-CD INITIALIZATION MENU --------------------------1 = Default preference (software.ini) 2 = User defined preference (absoft_9.ini) 3 = User defined preference (aix_53.ini) 4 = User defined preference (pgi_6.ini) 5 = User defined preference (software_32bit.ini) 6 = Specify other preference Please enter your choice (1-6): 2 STARDIR: STARINI: CDLMD_LICENSE_FILE: LM_LICENSE_FILE: /opt/starcd $STARDIR/etc/pgi_6.ini 19999@license_server 19999@license_server:7127@license_server02:7588@server03

ABSOFT: /opt/absoft FLEXLM: $STARDIR/FLEXLM/10.8.0.7/linux64_2.4-x86-glibc_2.2.5 HPMPI: $STARDIR/HPMPI/2.2.5.1/linux64_2.4-x86-glibc_2.2.5 LAMHOME: $STARDIR/LAM/7.0/linux64_2.4-gcc_3.2.2-glibc_2.2.5-dso MPICH: $STARDIR/MPICH/1.2.4/linux64_2.4-gcc_3.2.2-glibc_2.2.5-dso PGI: /opt/pgi PROSTAR: $STARDIR/PROSTAR/4.06.000/linux64_2.4-x86-glibc_2.2.5 RUNTIME: $STARDIR/RUNTIME/1.04.006/linux64_2.4-x86-glibc_2.2.5 STAR: $STARDIR/STAR/4.06.000/linux64_2.4-pgf90_6.2-gcc_4.1.1-glibc_2.2.5-dso STARLAUNCH: $STARDIR/STARLAUNCH/2.04.04/linux64_2.4-x86-glibc_2.2.5 STARNET: $STARDIR/STARNET/3.00.014/generic

Please refer to Appendices A and B about changes to .ini files. If you are not a Software Administrator you can make copies of the .ini files to edit and choose item 6 to specify the full path to the alternative .ini file.
Version 4.08 (Updated: 23 December 2008) 2-5

Section 2

STAR-CD INSTALLATION STAR-CD suite installation on UNIX.

Additional Software: es-solutions and plugins The functionality of STAR-CD software is often enhanced by users own coding, sometimes this is to achieve repetitive tasks other times it is to investigate new and different modelling strategies. At CD-adapco our engineers have developed extensions to STAR-CD referred to as es-solutions (for example es-ice, es-after and es-vtm) and other additional software plugins (wave, DARS-CFD, DOLFA). In previous versions of STAR-CD they were pre-installed in the solver directories, they now reside in individual directories and, thus, can be installed anywhere on the file system. However, we recommend that you keep to the original directory structure until you have gained some familiarity and confidence with the new installation. Some of these tools are not available for every platform but this will be shown during the installation stages and the automatic log of what has been installed. To view the available plugins for a particular platform after installation you can use the command star -showplugins.

Running STAR solver on clusters We strongly recommend the installation of resource manager such as LSF, PBSPro, Sun Grid Engine or Torque for managing batch jobs on your cluster. You will need to install STAR-NET which acts as an interface between the resource manager and STAR-CD. In order to get the best scalability of STAR-CD solver on large number of node it is important is use a high speed interconnect such as Inniband, Myrinet or Gigabit. We recommend HP MPI as it supports multiple interconnect types. It is important to provide sufcient I/O bandwidth to a large parallel application running on many compute nodes. Therefore we recommend a parallel le system with multiple I/O nodes. In a large compute cluster with multiple parallel jobs running it is important to provide enough disk bandwidth by using a cluster of I/O nodes. STAR-CD supports parallel I/O through the new "-pario" option. We also recommend all user coding compilations and geometry decomposition to be done on a head node. These should be done before submitting jobs to the batch system using the "-ule" and "-decomp" options. For large clusters you may wish to employ multiple head nodes. Please refer to documentation in directory associated with the version of STAR-NET
$STARNET/generic/doc/starnet.pdf

Version 4.08 (Updated: 23 December 2008)

2-6

Section 2

STAR-CD INSTALLATION STAR-CD suite installation on Windows

STAR-CD suite installation on Windows


This installation must be performed by the administrator or a user with administrator rights. If you wish to change the default installation directory please note that STAR-CD on Windows cannot be installed in the same directory as any previous versions. If you want to install both the Windows x86 and x64 ports on a Windows x64 system they cannot be installed in the same directory. The computer must be rebooted after the installer as exited. During installation the CD-adapco installer starts a number of third party installers interactively, such as the MPICH2 installers. If you are prompted to reboot by these third party installers, please select No. If any errors occur during installation, these are recorded in the file: %STARDIR%\setup\4.08.xxxlog.txt Any user who wishes to run STAR-CD in parallel using HP MPI, Microsoft MPI or MPICH2 must first store their password in the Windows registry. Please see Appendix E of the User Guide for details. It is also required to switch off User Access Control (UAC) in order for parallel runs to work properly. If you wish to run STAR-CD in distributed mode using HP MPI, you should installed HP MPI on the same drive with same path structure on all nodes. This can be done by selecting destination location during HP MPI installation. Installing from FTP Package Installing from the FTP package is very much the same as installing from the DVD-ROM. The zip files should be unpacked into a temporary directory (for example C:\tmp\star_pkg).Click the setupwin.exe icon found in the unpacked directory to begin the installation process then follow the on screen instructions

Installing from DVD-ROM Insert the STAR-CD installation DVD-ROM into the DVD-ROM drive. The installation setup program should auto-load. If auto-insert notification has been disabled in Windows, the DVD-ROM will not auto-load. Perform the following in this case: Double click the My Computer icon on the desktop Double click the icon that corresponds to your DVD-ROM drive Click the setupwin.exe icon to begin the installation process

Version 4.08 (Updated: 23 December 2008)

2-7

STAR-CD INSTALLATION STAR-CD suite installation on Windows

Section 2

Running STAR solver on clusters To Configure a Cluster for multiprocessors calculation. 1. Install STAR-CD on the head node only. Compute Nodes need to be installed with dependencies only. Perform a Cluster Node installation as shown below (Figure 2.1) on all Compute Nodes. 2. Please check that CDLMD_LICENCE_FILE environmental variables on the head node point to your FLEXlm server (which can either be on local or remote) machine. Also ensure all nodes in the cluster can see the FLEXlm server. Details of FLEXlm conguration on Section 4.

Figure 2.1: Cluster Node installation

If you would like to use a cluster with Microsoft Windows CCS please read Appendix C.

2-8

Version 4.08 (Updated: 23 December 2008)

Section 3

LICENSING FLEXlm Version 10.8.0.7

Section 3

LICENSING
This version of FLEXlm utilities is now known as FLEXnet Publisher
http://www.macrovision.com/products/flexnet_publisher

FLEXlm Version 10.8.0.7

For your convenience, CD-adapco provides a set of FLEXnet Publisher utilities. These are installed in the <STAR-CD location>/license directory. STAR-CD does not depend on this location. If it is necessary to use the FLEXnet 10.8.07 license daemon for a number of programs the license directory can be moved to a more convenient location. The FLEXnet operation and installation is standard and is covered in detail in FLEXnet document : http://www.macrovision.com/pdfs/flexnet_licensing_end_user_guide.pdf These notes pertain to CD-adapco specific modifications to FLEXnet.

Vendor Daemon Name


The FLEXlm documentation refers to the vendor daemon name. For CD-adapco this is called cdlmd (cdlmd.exe on Windows), it is in the license file and the environmental variable CDLMD_LICENSE_FILE is used to locate the license file if set.

Starting the License Daemon

UNIX Systems Once installed on the target system the FLEXlm daemon should be initialised as follows: nohup lmgrd_path -c license_file -l log_file & Where lmgrd_path points to the license daemon lmgrd (for example $STARDIR/license/lmgrd). All information relating to the license transactions will be written to log_file.

Version 4.08 (Updated: 30 October 2008)

3-1

LICENSING License File Location

Section 3

Windows Systems Use lmtools.exe to handle the management of FLEXlm licensing.

License File Location


FLEXlm uses a number of ways to locate the license file, either by pathname or by port@host syntax. FLEXlm standard behaviour is to use the following hints: CDLMD_LICENSE_FILE environmental variable LM_LICENSE_FILE environmental variable In order to avoid conflicts with other vendors license servers we strongly recommend that you use the CDLMD_LICENSE_FILE environmental variable.

UNIX Systems A personal configuration file is found at: ~/.flexlmrc

Windows Systems A configuration keyname is in the Windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager In addition, the file $STARDIR/license/license.dat will be used if present.

Environmental Variables
The following variables can be set to adjust the behaviour. Unless others stated, setting the variable to 1 will turn the behaviour on, setting it to 0 or not setting it at all will turn it off. STARLICENSELOG When the license routines run, they will write to the file this is pointing to as well as standard out. Can be useful if license messages dont appear etc. This has to be set to the file.

3-2

Version 4.08 (Updated: 30 October 2008)

Section 3

LICENSING Conguration of FLEXlm license manager on Windows

STARLICENSEVERBOSE Causes more verbose messages to be displayed to both screen and log file.

STARNOFLEXLMRC Causes FLEXlm not to write the ~/.flexlmrc file (UNIX) or registry key (Windows).

STARNOTIMEOUT FLEXlm normally times out after 2 hours of inactivity. This means that if a machine crashes with a license checked out, the license will return to the server after this time. In cases where no activity for two hours is normal (a queuing system which suspends a job during the day or a long radiation calculation in iteration 0) then this will cause a SIGPIPE error (the client tries to speak to the server down a closed pipe). STAR-CD handles this error and exits. If this variable is set FLEXlm will never time out and so avoid the SIGPIPE error but the user needs to be aware that this may cause licenses which would otherwise be returned to remain out and so lmremove needs to be used.

STARWAIT Normally, FLEXlm will return if a license is unavailable and the code will exit. If STARWAIT is set, then FLEXlm will wait until a license becomes available. This may be of use in queue or batch systems.

STARLOK STARLOK can be used instead of FLEXlm. Please contact agency for details of STARLOK usage.

Conguration of FLEXlm license manager on Windows


1. Copy the license le (license.dat) to the license directory, e.g. C:\Program Files\CD-adapco\license. 2. Edit the license.dat le supplied by CD-adapco to replace unknown with your computer hostname ie computername. 3. Make sure that you have Administrator rights on the computer. 4. Make sure to replace port@hostename to the correct value during installation.
Version 4.08 (Updated: 30 October 2008) 3-3

LICENSING Conguration of FLEXlm license manager on Windows

Section 3

5. Congure the FlexLM license manager with lmtools.exe (The icon for FlexLM Tools can normally be found in C:\Program Files\CD-adapco\STAR-CD\4.06\FLEXLM\10.8.0.7\*\bin). a. Select the tab Cong Services. i. Type Service Name, e.g. CD-adapco license manager. i. Browse Path the lmgrd.exe le. ii. Browse Path to the license le. iii. Type the Path to the debug log le (This le will be created when the license service start). iv. Tick Use Services. v. Tick Start Server at Power Up. vi. Save Service. b. Select the tab Start/Stop/Reread. Select the service CD-adapco license server and click Start Server. c. Select the tab Service/License File. i. Make sure that Configuration using Services is selected. d. Exit lmtools.exe (File -> Exit). 6. Make sure the environmental variable CDLMD_LICENSE_FILE is set correctly. e. Open the control panel and open the System panel.

f. Select the Advanced tab and select Environmental variables. g. Check that value of the CDLMD_LICENSE_FILE is set to port@hostname. h. Change or create this variable if necessary. 7. Reboot the computer.

3-4

Version 4.08 (Updated: 30 October 2008)

Section 4

TESTING THE INSTALLATION Setup User Environment to Run STAR

Section 4

TESTING THE INSTALLATION


A number of tutorials are included with the STAR-CD distribution that are optional at installation. To check that the code is correctly installed, run one of the tutorial cases as described below.start open a STAR-CD Command Prompt and follow the instructions below:

Setup User Environment to Run STAR


UNIX Systems For Bourne, Korn or Bash shells: . /opt/starcd/etc/setstar For C and Tcsh shells: source /opt/starcd/etc/setstar This should return STAR version information, for example, on a Linux platform:
STARDIR: /opt/starcd STARINI: Default CDLMD_LICENSE_FILE: 19999@starlicenseserver LM_LICENSE_FILE:12345@otherlicenseserver ABSOFT: LAMHOME: PROSTAR: RUNTIME: STAR: STARLAUNCH: STARNET: /opt/absoft $STARDIR/LAM/7.0/linux_2.4-gcc_2.95.3-glibc_2.2.2-dso $STARDIR/PROSTAR/4.08.000/linux_2.4-x86-glibc_2.3.2 $STARDIR/RUNTIME/1.04.007/linux_2.4-x86-glibc_2.2.2 $STARDIR/STAR/4.08.000/linux64_2.4-pgf90_6.2-gcc_4.1.1-glibc_2.2.5-dso $STARDIR/STARLAUNCH/2.10.002/linux_2.2-x86-glibc_2.2.0 $STARDIR/STARNET/3.00.014/generic

Windows Systems To open a STAR-CD Command Prompt and follow the instructions below: Start > All Programs > CD-adapco > STAR-CD 4.08 Command Prompt:

Create a Working Directory


Create a working directory:
mkdir starcd4 cd starcd4

Version 4.08 (Updated: 6 November 2008)

4-1

TESTING THE INSTALLATION Automatically Generate the Case Using Pre-processor

Section 4

UNIX Systems
cp $STARDIR/STARCDTUTS/4.08.*/generic/star/tut1.1/* .

Windows Systems
copy %STARDIR%\STARCDTUTS\4.08.*\generic\star\tut1.1\*.* .

Automatically Generate the Case Using Pre-processor


The following instructions process the prep.inp to provide a model file called tut.mdl and a geometry file tut.ccmg and as problem file tut.prob. For further information about running STAR-CD please consult the user guide. First use the advanced pre-/post-processor to generate geometry and problem files:
prostar x tut cursor file ifile prep quit save

Run the STAR solver


star

The above commands should have generated a basic geometry using the pro-STAR pre- and post-processor and then run the STAR code to solve the case. If the installation completed successfully, there should be no failures or error messages. Additional testing may be carried out in HPC-mode. To see other options use:
star -help

Run the STAR solver requesting a 4 domain decomposition on the local host:
star 4

Run the STAR solver requesting a 4 domain decomposition specifying the number of processes on each host:
star hostnameA,2 hostnameB,2

Again, if the installation completed successfully, there should have been no failures or error messages.

4-2

Version 4.08 (Updated: 6 November 2008)

APPENDICES

APPENDICES

STAR-CD Version 4.08

CONFIDENTIAL FOR AUTHORISED USERS ONLY

1988-2008 CD adapco

Appendix A

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Default Settings

Appendix A hardware.ini (SITE SPECIFIC CONFIGURATION FILE)


The hardware.ini file allows site specific configuration settings to be allocated by the Software Administrator without involving the end user. The hardware.ini file is kept in $STARDIR/etc (where $STARDIR is the installation directory). An example of the hardware.ini is installed at the final stage of installation. The structure of a line is: keyword name environment setting
where,

keyword is one from the following: default, platform, group or host; these are described below. name is a platform, group or host name, or left blank for the default keyword. environment setting is an environmental variable set using the Bourne shell syntax.

These keywords are explained further in the next sections.

Default Settings
The default keyword is used to set environmental settings across all platforms and all hosts. For example, the license le can be set once per site as:
default CDLMD_LICENSE_FILE=19999@starlicenseserver

Platform Settings
The platform keyword is used to set environmental settings on specic platforms. For example, it might be a desired to set the compiler location environmental variable differently on the Linux_x86 and Linux_x86_64 platforms as:
platform Linux_x86 ABSOFT=/opt/absoft platform Linux_x86_64 ABSOFT=/opt/absoft64/9.0

Version 4.08 (Updated: 5 November 2008)

A-1

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Host Settings

Appendix A

The only options for platform name currently in use are:


AIX_Power, HP-UX_PA-Risc, HP-UX_Itanium, Linux_x86, Linux_x86_64, Linux_Itanium and SunOS_UltraSPARC.

An example of two preferred compiler hosts for user coding (hostb will be used only when hosta is unavailable) is shown in the following statement:
platform Linux_x86 COMPILERHOST=hosta:hostb

where hosta and hostb are automatically detected as members of the platform Linux_x86.

Host Settings
The host keyword is used to set host specic settings. This is especially useful for load-balancing parallel jobs. For example,
host hosta host hostb HPC_SPEED=2400 HPC_SPEED=1000

indicates the relative speeds of the cpus. This can then be used to decompose the geometry to balance the load on each processor. HPC_MPPHOST can be used to inform MPI of the alternative host name for a machine with multiple network cards e.g. hostc is also known as mpphostc in the secondary network (although this is set by the Systems Administrator when setting up the subnetwork). To set the dedicated subnetwork names of machines hostc and hostd:
host hostc host hostd HPC_MPPHOST=mpphostc HPC_MPPHOST=mpphostd

In a similar manner to the platform keyword a compiler host can be specied:


host hostc COMPILERHOST=hosta:hostb

this sets two preferred compiler hosts for user coding (hostb will be used only when hosta is unavailable). So that it does not matter that there is no compiler installed on hostc.

A-2

Version 4.08 (Updated: 5 November 2008)

Appendix A

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Group Settings

Group Settings
Groups are automatically determined in the $STARDIR/etc/setgroup le. A number of groups have been pre-set by CD-adapco. Examine that script to see how to dene a group and if necessary the script can be modied by the site Software Administrator. The output of setgroup is a string that sets the group value for the current host. It is not usual to invoke this script directly, but its affect can be seen in the choice of port for the platform. Here is an excerpt from the setgroup script:
case $GLIBC_VER in 2.[1-3]|2.[1-2]*|2.3.1) ;; *) echo "Linux_x86-glibc_2.3.2";; esac

The important item in the above excerpt is that the group name is the output from the script so the string Linux_x86-glibc_2.3.2 is used in the hardware.ini and the software.ini file. A corresponding entry for the group determined in setgroup must be set for the environment setting to be activated.

Version 4.08 (Updated: 5 November 2008)

A-3

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Group Settings

Appendix A

A-4

Version 4.08 (Updated: 5 November 2008)

Appendix B

SOFTWARE.INI (SOFTWARE CONFIGURATION FILE) Default Settings

Appendix B software.ini (SOFTWARE CONFIGURATION FILE)


The software.ini file is created during, and is unique to, the installation. The Software Administrator and end user should not need to edit this file. However, non-standard installations may require that copies of the file have to be altered. The software.ini file is kept in $STARDIR/etc (where $STARDIR is the installation directory). The structure of a line is: keyword name environment setting
Where,

keyword is one from default, platform or group; their function is described below. name is a platform or group name, or it is left blank for the default keyword. It can be user-dened. environment setting is an environmental variable set using the syntax of: variable = value

The information in the les is structured as shown at the end of this appendix.

Default Settings
The default keyword is used to set the top level of each software component across all platforms and all hosts. For example:
default LAMTOP=$STARDIR/LAM/7.0 default PROSTARTOP=$STARDIR/PROSTAR/4.08.000 default STARTOP=$STARDIR/STAR/4.08.000

set the top level location of LAM MPI, pro-STAR and STAR solver respectively. If a component is installed different location (for example a different version of an es-product) then only top level reference in the etc directory needs to be changed. For example, if MPICH was previously installed at /opt/mpich/mpich1.2.4 and not installed during the current installation, then changing: default to default MPICHTOP=/opt/mpich/mpich-1.2.4 MPICHTOP=NOMPICH

sets the top level location of MPICH to the previous installation.


Version 4.08 (Updated: 12 November 2008) B-1

SOFTWARE.INI (SOFTWARE CONFIGURATION FILE) Platform Settings

Appendix B

Platform Settings
The platform settings match the STAR port naming convention and should not be changed. However, in some circumstances these will have to be changed to activate a non-default port such as versions of the STAR solver compiled with different compilers and different versions of pro-STAR that are provided to deal with different version of the platforms Operating System. The method of activating the non-default port is through modification of a copy of the software.ini file. For example, to activate a different compiled version of the STAR solver on the Linux_x86_64 platform (i.e. AMD64 or Intel EM64T):
platform Linux_x86_64 STAR=$STARTOP/linux64_2.4-pgf90_6.2-gcc_4.1.1-glibc_2.2.5-dso

becomes:
platform Linux_x86_64 STAR=$STARTOP/linux64_2.4-absoft_9.0a-gcc_4.1.1-glibc_2.2.5-dso

Group Settings
The groups are determined with the $STARDIR/etc/setgroup script. However, if you enhance the setgroup script then the setting for the new group must be included in the software.ini. The simplest method of setting a group is to provide an echo groupname to the case structure in setgroup, as illustrated in Appendix A. Here is an excerpt from the comment block of that script:

# # # # # # # # # #

The following groups are defined in the standard "setgroup" file: SunOS_UltraSPARC3 = SunOS systems with UltraSPARC III processor or higher Linux_Itanium-glibc_2.3.2 = Linux Itanium systems with glibc-2.3.2 or later Linux_x86-glibc_2.3.2 = Linux x86 systems with glibc-2.3.2 or later Linux_x86_64-glibc_2.3.2 = Linux x86_64 systems with glibc-2.3.2 or later This script can be customised to select a group name for machines based on versions of various components like Operating system versions, CPU type, C run time versions and Fortran compilers.

Notice the several pre-set group values can been seen in software.ini, here is an example how the Linux_x86-glibc_2.3.2 group value is interpreted:

group Linux_x86-glibc_2.3.2 PROSTAR=$PROSTARTOP/linux_2.4-x86-glibc_2.3.2

B-2

Version 4.08 (Updated: 12 November 2008)

Appendix B

SOFTWARE.INI (SOFTWARE CONFIGURATION FILE) Example software.ini

If the 32bit port for Linux systems is to be used on a 64bit Linux system (AMD64/Intel EM64T) an alternative .ini file has been supplied:

$STARDIR/etc/software_32bit.ini

it is activated by setting the environment variable STARINI to the full path location of the file before activating setstar.

Example software.ini
In the following listing you can see the top section of an example INI file. The definitions of the majority of the environment variables used by STAR-CD are defined there. If you need to access a product installed in a different location, for example, a different version of es-ice, then make a copy of this file (choose any name as long as you retain the .ini extension) and edit the definitions. The method for defining a different port has been described separately.

# # Default settings # default default default default default default default default default default default default # default default default default default default default default default # default

FLEXLMTOP=$STARDIR/FLEXLM/10.8.0.7 HPMPITOP=$STARDIR/HPMPI/2.2.5.1 ICE=$STARDIR/ICE/2.05.126 LAMTOP=$STARDIR/LAM/7.0 MPICHTOP=$STARDIR/MPICH/1.2.4 PEMFC=NOPEMFC PROSTARTOP=$STARDIR/PROSTAR/4.08.000 RUNTIMETOP=$STARDIR/RUNTIME/1.04.007 STARCDMAN=$STARDIR/STARCDMAN/4.08.000/generic STARTOP=$STARDIR/STAR/4.08.000 STARLAUNCHTOP=$STARDIR/STARLAUNCH/2.10.002 STARNET=$STARDIR/STARNET/3.00.014/generic STARPLUGIN_AERO=$STARDIR/AERO/4.03.003 STARPLUGIN_AFTER=$STARDIR/AFTER/4.06.004 STARPLUGIN_DARSCFD=$STARDIR/DARSCFD/2.01.005 STARPLUGIN_DARSTIF=NOSTARPLUGIN_DARSTIF STARPLUGIN_DEMCFD=$STARDIR/DEMCFD/1.00.010 STARPLUGIN_DOLFA=$STARDIR/DOLFA/1.01.000 STARPLUGIN_ICE=$STARDIR/ICE/2.05.126 STARPLUGIN_VTM=$STARDIR/VTM/4.04.000 STARPLUGIN_WAVE=$STARDIR/WAVE/2.02.000 STARFLAGS=

Version 4.08 (Updated: 12 November 2008)

B-3

Appendix C

MICROSOFT WINDOWS COMPUTE CLUSTER SERVER Installing Windows CCS Environment

Appendix C Microsoft Windows Compute Cluster Server


Installing Windows CCS Environment
Latest Information about Windows CCS can be found at: http://www.microsoft.com/hpc The head and compute nodes for Windows Compute Cluster Server 2003 can be any of the following operating systems: Microsoft Windows Server 2003, Compute Cluster Edition Microsoft Windows Server 2003, Standard x64 Edition Microsoft Windows Server 2003, Enterprise x64 Edition, The x64-based versions of Microsoft Windows Server 2003 R2

By default, the head node includes remote administration and job scheduling components. The head node must also be configured as a compute node which can be paused if you do not wish jobs to run on it. However, in the design of Microsoft Compute Cluster, administrators can also perform administration and job scheduling from a remote workstation. Supported operating systems for remote administration workstations include: Microsoft Windows Server2003 with Service Pack 1 (SP1) Microsoft Windows XP Professional Service Pack 2 (SP2) Microsoft Windows XP Professional, x64 Edition

In addition, Windows Compute Cluster Server 2003 requires the following: Microsoft .NET Framework 2.0 Microsoft Management Console (MMC) 3.0 Pre-Release to run the Compute Cluster Administrator snap-in Microsoft SQL Server 2000 Desktop Engine (MSDE) to store all job information

Setting up a Cluster
Setting up a computing cluster with Windows Compute Cluster Server 2003 begins with confirming that the operating system and prerequisite software above are installed, the Compute Cluster Pack (CCP) can then be installed. This installs the job scheduler and cluster administrator software on the head node. The Microsoft CCS scheduler employs a multi-threaded architecture powered by the Microsoft SQL Server database. If the performance of the job scheduler becomes important, scheduler scaling can be enhanced with the addition of Microsoft SQL Server 2005 Enterprise Edition.
Version 4.08 (Updated: 30 October 2008) C-1

MICROSOFT WINDOWS COMPUTE CLUSTER SERVER Congure the Cluster

Appendix C

The Winsock Direct (WSD) supports Remote Direct Memory Access on the Windows CCS platform, this provides a more efficient and direct way to connect to the network hardware, eliminating much of the overhead associated with a standard TCP/IP stack. This switches Microsoft MPI into no copy on send mode, giving significantly greater bandwidth at the expense of higher CPU utilization. If you require additional information about installing and configuring a Windows CCS cluster. Please download Microsofts white paper Compute Cluster Deployment Guide. If you require additional information about tuning a Windows CCS cluster. Please download Performance Tuning a Compute Cluster: http://www.microsoft.com/downloads/details.aspx?FamilyID=40cd8152-f89d-4ab f-ab1c-a467e180cce4&displaylang=en These documents also contains a number of links to additional sources of information on Windows CCS.

Congure the Cluster


Start the administrator tool then follow the To Do List: Define the cluster network topology, configuring the public, private, and MPI network interfaces of the head node as applicable to the chosen configuration. Configure RIS if applicable. Add compute nodes. To do this, use the Node Management tile to access the Add Nodes Wizard. This will require approval from the cluster administrator before the node can be added to the cluster. Compute nodes can be added by running the compute cluster pack and selecting the compute node option, or by using the To Do List to access the Add Nodes wizard, and then selecting Automated or adding a specified node. Configure cluster users and administrators. To do this, use the Cluster Security tile to access the Configure Users wizard. Disable the firewalls in the cluster Install the CCS software development kit (SDK) from the Microsoft CPP installation CD on all nodes in the cluster (required by STAR). From the CCP wizard select Install Client Utilities only, and then click Next, select
C-2 Version 4.08 (Updated: 30 October 2008)

Appendix C

MICROSOFT WINDOWS COMPUTE CLUSTER SERVER Congure the Cluster

install the software development kit (SDK). Alternatively the CCS SDK Installer is also available for download at: http://www.microsoft.com/downloads/details.aspx?FamilyID=d8462378-2f68-40 9d-9cb3-02312bc23bfd&displaylang=en In order for STAR-CD to function properly on your Compute Cluster Server, please Turn off the firewall on all nodes in your cluster. Alternatively, you many decide to keep the firewall turned on, and allow exception for STAR-CD programs. Please contact your local CD-adapco support office for further information regarding this.

Version 4.08 (Updated: 30 October 2008)

C-3

MICROSOFT WINDOWS COMPUTE CLUSTER SERVER Congure the Cluster

Appendix C

C-4

Version 4.08 (Updated: 30 October 2008)

Appendix D

COMPILERS USED TO BUILD THE SOFTWARE Porting Reference Platforms for the STAR Solver

Appendix D Compilers Used to Build the Software


In this appendix two tables are presented that detail the versions of Operating System, Compilers and CPU families that are used to create the libraries for the STAR-CD solver and the advanced pre- and post-processor (pro-STAR). For operating system level it is a general condition that libraries built on earlier levels will work on the newer levels. When there are exceptions, extra libraries are supplied (usually referred to as different ports). However, please refer to Section 1 of this document to see the supported platform level. For the product to work in the manner in which it has been tested, it is a requirement that the minimum specifications in Table 1-1 are met. The supplied RUNTIME package will support the matching compiler.

Porting Reference Platforms for the STAR Solver


Table D-1 provides the porting reference platform used for the compilation of the STAR-CD solver libraries, indicating the operating system level and compiler version versions used. For situations that require user coding with the solver it is important to match the level of Fortran 90 compiler. Novel architectures or new hardware platforms not listed below may be supported by specic arrangement with CD-adapco. Table D-1: Porting Reference Platforms used to build the STAR solver
STAR-CD Platform Operating System AIX 5.2 (64bit) HP-UX 11.11 (64bit) HP-UX 11.23 (64bit) Linux 2.4.4, glibc 2.2.2 (SuSE 7.2 32bit) Linux 2.4.21, glibc 2.2.5 (SLES 8.0 64bit) Linux 2.4.21, glibc 2.2.5 (SLES 8 64bit) Linux 2.4.18, glibc 2.2.4 (RHEL 2.1 64bit) CPU Type IBM POWER (64bit) HP PA-RISC (64bit) Intel Itanium (64bit) AMD x86 and Intel x86 (32bit) AMD64 and Intel EM64T (64bit) AMD64 and Intel EM64T (64bit) Intel Itanium (64bit) FORTRAN Compiler IBM xlf90 9.1 HP f90 B.11.11.92 B3907DB/ B3909DB HP f90 B.11.23.22 Absoft f90 9.0a C compiler IBM xlc 7.1 HP cc B.11.11.16 HP cc A.05.50 GNU gcc 2.95.3 C++ compiler IBM xlC 7.1 HP aCC A.03.70 HP aCC A.05.50 GNU g++ 4.1.1

AIX Power (64bit) HP-UX PA-Risc (64bit) HP-UX Itanium (64bit) Linux x86 (32bit) Linux x86_64 (64bit) Linux x86_64 (64bit) Linux Itanium (64bit)

Absoft f90 9.0a

GNU gcc 3.2.2

GNU g++ 4.1.1

PGI pgf90 6.2-4

GNU gcc 4.1.1

GNU g++ 4.1.1

Intel ifort 9.0.031

GNU gcc 4.1.1

GNU g++ 4.1.1

Version 4.08 (Updated: 16 December 2008)

D-1

COMPILERS USED TO BUILD THE SOFTWARE Porting Reference Platforms for the Advanced Pre-/Post-processor

Appendix D

Table D-1: Porting Reference Platforms used to build the STAR solver
STAR-CD Platform Operating System SunOS 5.10 (64bit) Windows Server 2003 x64 SP2 (64bit) Windows Server 2003 x64 SP2 (64bit) CPU Type SUN UltraSPARC (64bit) AMD x86 and Intel x86 (32bit) AMD64 and Intel EM64T (64bit) FORTRAN Compiler SUN f90 8.2 2005/10/13 Intel ifort 10.1.029 Intel ifort 10.1.029 C compiler C++ compiler

SunOS UltraSPARC (64bit)


Windows x86 (32bit) Windows x64 (64bit)

SUN cc 5.8 2005/10/13 Intel icl 10.1.029 Intel icl 10.1.029

SUN CC 5.8 2005/10/13 Intel icl 10.1.029 Intel icl 10.1.029

CD-adapco will continue to work with compiler vendors to review performance and reliability. Our aim is to provide one port that has a good combination of reliability and performance and to maintain some continuity for supported compiler environments. Therefore, CD-adapco cannot guarantee continued support for a particular compiler. CD-adapco welcomes and encourages users to report their experience about performance and reliability of these ports. (e-mail:performance@uk.cd-adapco.com).

Porting Reference Platforms for the Advanced Pre-/Post-processor


For situations that require user coding with the pre-/post-process it is important to match the level of C++ compiler. Users who are interested in coding pro-STAR user subroutines which call C++ routines must use the C++ compilers listed in the table 1-2. Matching the C++ compiler exactly is necessary since objects created by one C++ compiler are generally not portable to another C++ compiler. Even though the advanced pre- and post-processing software was compiled using the SunOS 5.8 environment it is recommended that SunOS 5.10 is used for the whole product to operate correctly.

Table D-2: Porting Reference Platforms used to build the advanced pre-/post-processor
STAR-CD Platform Operating System AIX 5.1.0.0 (64bit) HP-UX B.11.00 (64bit) CPU Type IBM POWER (64bit) HP PA-RISC (64bit) FORTRAN Compiler IBM xlf90 7.1.0.2 HP f90 B3907DB/ B3909DB C compiler IBM xlc 5.0.2.7 HP cc B.11.11.26792.GP C++ compiler IBM xlC 5.0.2.7 HP aCC B3910B A.03.55

AIX Power

HP-UX PA-Risc

D-2

Version 4.08 (Updated: 16 December 2008)

Appendix D

COMPILERS USED TO BUILD THE SOFTWARE Porting Reference Platforms for the Advanced Pre-/Post-processor

Table D-2: Porting Reference Platforms used to build the advanced pre-/post-processor
STAR-CD Platform Operating System HP-UX B.11.22 (64bit) Linux 2.2.18, glibc-2.2 (SuSE 7.1 32bit) Linux 2.4.21, glibc-2.3.2 (SuSE 9.0 32bit) Linux 2.4.19, glibc-2.2.5 (SLES 8.0 64bit) Linux 2.4.18, glibc-2.2.4 (RHEL 2.1 64bit) Linux 2.4.21, glibc-2.3.2 (RHEL 3.0u4 64bit) SunOS 5.81 (64bit) Windows Server 2003 R2 (64bit) Windows Server 2003 R2 (64bit) CPU Type Intel Itanium (64bit) AMD x86 and Intel x86 (32bit) FORTRAN Compiler HP f90 B.11.22.04 C compiler HP cc A.05.55 C++ compiler HP aCC A.05.55

HP-UX Itanium

Linux x86

Absoft f90 9.0a

GNU gcc 4.1.1

GNU g++ 4.1.1

Linux x86

AMD x86 and Intel x86 (32bit)

Absoft f90 9.0a

GNU gcc 4.1.1

GNU g++ 4.1.1

Linux x86 64

AMD64 and Intel EM64T (64bit)

Absoft f90 9.0a

GNU gcc 4.1.1

GNU g++ 4.1.1

Linux Itanium (64bit)

Intel Itanium (64bit)

Intel ifort 9.1.051

Intel icl 9.1.051

Intel icl 9.1.051

Linux Itanium (64bit) SunOS UltraSPARC (64bit) Windows x86 (32bit) Windows x64 (64bit)

Intel Itanium (64bit)

Intel ifort 10.0.025

Intel icl 10.0.025

Intel icl 10.0.025

SUN UltraSPARC (64bit) AMD x86 and Intel x86 (32bit) AMD64 and Intel EM64T (64bit)

SUN f90 8.1 2005/01/07 Intel ifort 10.1.029 Intel ifort 10.1.029

SUN cc 5.7 2005/01/07 Microsoft Visual C++ 2005 Microsoft Visual C++ 2005

SUN CC 5.7 2005/01/07 Microsoft Visual C++ 2005 Microsoft Visual C++ 2005

Version 4.08 (Updated: 16 December 2008)

D-3

COMPILERS USED TO BUILD THE SOFTWARE Porting Reference Platforms for the Advanced Pre-/Post-processor

Appendix D

D-4

Version 4.08 (Updated: 16 December 2008)