Installation

ANSYS products may not be available by default in your HPCBOX cluster deployment. You may have to install them yourself or contact HPCBOX Support for assistance.

Installation procedure

If installing the applications yourself, please make sure you use the following installation and post-installation configuration.

tip

We recommend getting assistance from HPCBOX support at boxhelp[at]drizti.com for installing, fine-tuning and setting up ANSYS products on your HPCBOX cluster. We are here to help!

Directory

ANSYS Mechanical, Structural, Fluids et. al

ANSYS products must be installed under /opt/drz/apps/ansys/VERSION. VERSION must be the ANSYS release number of the binaries you are installing, for example 2024R1.

Example structure with various ANSYS versions installed:

$ ls /opt/drz/apps/ansys/
2021R2  2022R1  2023R2  2024R1

$ ls /opt/drz/apps/ansys/2024R1/
ansys_inc

Post-Installation Configuration

Microsoft Azure

After installing binaries, you must create/edit a post installation configuration modulefile to link your ANSYS installation with HPCBOX.

Create a modulefile (just a text file) under /opt/drz/modulefiles/ansys/ and the filename should be the same as the ANSYS release you are configuring. For example, 2024R1

$ ls /opt/drz/modulefiles/ansys/
19.0.0  19.2.0  2019R2  2020R1  2021R1  2022R1  2024R1
19.1.0  2019R1  2019R3  2020R2  2021R2  2023R2

Place the following contents in the modulefile

#%Module 1.0
#
#  ANSYS 2024R1 module file
#

set  ANSYSHOME       /opt/drz/apps/ansys/2024R1/ansys_inc
set  ANSYSVERSION    v241

prepend-path PATH $ANSYSHOME/$ANSYSVERSION/CFX/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/CFD-Post/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/Framework/bin/Linux64/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/fluent/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/ansys/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/RSM/Config/tools/linux/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/SystemCoupling/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/icemcfd/linux64_amd/bin
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/AnsysEM/Linux64/

setenv ANSYS_HOME $ANSYSHOME
setenv ANSYS_VERSION $ANSYSVERSION

# For Intel MPI runs
set I_MPI_OFI_PROVIDER mlx

# For fluent
setenv  USE_INTEL_MPI_2019 1
setenv  FLUENT_LM_CHECK_ENABLE 1
set DRZ_FLUENT_IMPI_INTEL_MPI_HOME /opt/intel/oneapi/mpi/latest
set DRZ_FLUENT_IMPI_I_MPI_FABRICS shm:ofi
set DRZ_FLUENT_IMPI_FI_PROVIDER_PATH /opt/intel/oneapi/mpi/latest/libfabric/lib/prov

setenv INTELMPI_ROOT $DRZ_FLUENT_IMPI_INTEL_MPI_HOME
setenv FLUENT_INTEL_MPI_VERSION 2021
setenv FS_MPIRUN_FLAGS  " -genv I_MPI_DEBUG 1 -genv I_MPI_OFI_PROVIDER $I_MPI_OFI_PROVIDER -genv I_MPI_FABRICS $DRZ_FLUENT_IMPI_I_MPI_FABRICS -genv FI_PROVIDER_PATH $DRZ_FLUENT_IMPI_FI_PROVIDER_PATH -rmk sge " 
setenv SCHEDULER_TIGHT_COUPLING 1

# For CFX
setenv DRZ_CFX_IMPI_INTEL_MPI_HOME /opt/intel/oneapi/mpi/latest
setenv DRZ_CFX_IMPI_I_MPI_FABRICS shm:ofi
setenv DRZ_CFX_IMPI_FI_PROVIDER_PATH /opt/intel/oneapi/mpi/latest/libfabric/lib/prov


#setenv I_MPI_DEBUG 1

Make sure, you change the values set for ANSYSHOME and ANSYSVERSION to match the ANSYS release you are configuring. The above example is for release 2024R1

Google Cloud

After installing binaries, you must create/edit a post installation configuration modulefile to link your ANSYS installation with HPCBOX.

Create a modulefile (just a text file) under /opt/drz/modulefiles/ansys/ and the filename should be the same as the ANSYS release you are configuring. For example, 2024R1

$ ls /opt/drz/modulefiles/ansys/
19.0.0  19.2.0  2019R2  2020R1  2021R1  2022R1  2024R1
19.1.0  2019R1  2019R3  2020R2  2021R2  2023R2

Place the following contents in the modulefile

#%Module 1.0
#
#  ANSYS 2024R1 module file
#

set  ANSYSHOME       /opt/drz/apps/ansys/2024R1/ansys_inc
set  ANSYSVERSION    v241

prepend-path PATH $ANSYSHOME/$ANSYSVERSION/CFX/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/CFD-Post/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/Framework/bin/Linux64/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/fluent/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/ansys/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/RSM/Config/tools/linux/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/SystemCoupling/bin/
prepend-path PATH $ANSYSHOME/$ANSYSVERSION/icemcfd/linux64_amd/bin

setenv ANSYS_HOME $ANSYSHOME
setenv ANSYS_VERSION $ANSYSVERSION

# For Intel MPI runs
#set I_MPI_OFI_PROVIDER mlx

# For fluent
setenv  USE_INTEL_MPI_2019 1
setenv  FLUENT_LM_CHECK_ENABLE 1
set DRZ_FLUENT_IMPI_INTEL_MPI_HOME /opt/intel/oneapi/mpi/2021.11
#set DRZ_FLUENT_I_MPI_FABRICS shm:ofi

setenv INTELMPI_ROOT $DRZ_FLUENT_IMPI_INTEL_MPI_HOME
setenv FLUENT_INTEL_MPI_VERSION 2021
# Update the flags below to include RDMA options, if any, in future
setenv FS_MPIRUN_FLAGS  " -genv I_MPI_DEBUG 1 -rmk sge "
setenv SCHEDULER_TIGHT_COUPLING 1

# For CFX
setenv DRZ_CFX_IMPI_INTEL_MPI_HOME /opt/intel/oneapi/mpi/2021.11
#setenv DRZ_CFX_I_MPI_FABRICS shm:ofi
setenv DRZ_CFX_IMPI_I_MPI_FABRICS shm:tcp

#setenv I_MPI_DEBUG 1

Dyna

For Dyna, please obtain the binaries suitable for your CPU architecture, for example, if your CPU has support for AVX512, then please obtain those binaries.

Place the binaries under /opt/drz/apps/dyna/VERSION where VERSION is something like R16.0. Additionally, create symbolic links lsdyna_s, lsdyna_d, mppdyna_s, mppdyna_d to point to the single and double precision versions of the binaries.

For example, something like this:

ls -l /opt/drz/apps/dyna/R16.0/ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018

-rwxrwxr-x. 1 drzadm drzadm  12950432 Mar 19 04:08 ansyscl
lrwxrwxrwx. 1 drzadm drzadm        68 Apr  8 19:47 l2a -> ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018.l2a
-rwxrwxr-x. 1 drzadm drzadm 375966432 Mar 19 04:18 ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018
-rwxrwxr-x. 1 drzadm drzadm    442112 Mar 19 04:18 ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018.l2a
lrwxrwxrwx. 1 drzadm drzadm        64 Apr  8 19:47 mppdyna_d -> ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018

Post Installation Configuration

Create a modulefile (just a text file) under /opt/drz/modulefiles/dyna/ and the filename should be the same as the Dyna release you are configuring. For example, R16.0

$ ls /opt/drz/modulefiles/dyna/
R16.0  R15.0

Dyna requires its own modulefile and it is placed under /opt/drz/apps/modulefiles/dyna/VERSION.
An example for R16.0 is provided below:

Module file sample for Dyna

#%Module 1.0
#
# Dyna R16.0

set  DYNAHOME       /opt/drz/apps/dyna/R16.0/ls-dyna_mpp_d_R16_0_0_x64_centos79_ifort190_avx512_intelmpi-2018


prepend-path PATH $DYNAHOME

# Set license setup 
setenv LSTC_LICENSE ansys
setenv ANSYSLMD_LICENSE_FILE 1055@anslic01

# Set Intel MPI configuration

setenv   DRZ_DYNA_IMPI_I_MPI_FABRICS  shm:ofi
setenv   DRZ_DYNA_IMPI_PATH  /opt/intel/oneapi/mpi/latest/bin
setenv   DRZ_DYNA_IMPI_FI_PROVIDER_PATH /opt/intel/oneapi/mpi/latest/libfabric/lib/prov
setenv   DRZ_DYNA_IMPI_LD_LIBRARY_PATH /opt/intel/oneapi/mpi/latest/lib
setenv   DRZ_DYNA_IMPI_INTEL_MPI_HOME /opt/intel/oneapi/mpi/latest


#setenv I_MPI_DEBUG 1

Missing ANSYS product integration?

Please contact HPCBOX support in case you do not find a pre-built integration for your ANSYS product.

Installation procedure​

Directory​

ANSYS Mechanical, Structural, Fluids et. al​

Post-Installation Configuration​

Microsoft Azure​

Google Cloud​

Dyna​

Post Installation Configuration​

Missing ANSYS product integration?​