34.4.1. Starting Parallel ANSYS Fluent on a Linux System Using Command Line Options

To start the parallel version of ANSYS Fluent using command line options, you can use the following syntax in a command prompt window:

fluent version -t nprocs [-gpgpu= ngpgpus ] [-p interconnect ] [-mpi= mpi_type ] [-cnf= hosts ]

where

For example, to use the Infiniband interconnect, and to start the 3D solver with 4 compute nodes on the machines defined in the text file called fluent.hosts, you can enter the following in the command prompt:

fluent 3d -t4 -pinfiniband -cnf=fluent.hosts

Note that if the optional -cnf= hosts is specified, a compute node will be spawned on each machine listed in the file hosts.

Also, ANSYS Fluent provides a fault-tolerance feature on Infiniband Linux clusters running OFED. To invoke this feature, use the command line flag -pinfiniband.ofedft (or -pib.ofedft), which enables transparent port fail-over and high-availability features using the IBM MPI. Note that while the simulations proceed more robustly with this option, there may be some degradation in performance.

During startup, ANSYS Fluent will create very small text files in the /tmp area. If you would like to specify a different location for these files, set the following environment variable: export FL_TMPDIR= directory.

The supported interconnects for parallel Linux machines are listed below (Table 34.5: Supported Interconnects for Linux Platforms (Per Platform), Table 34.6: Available MPIs for Linux Platforms, and Table 34.7: Supported MPIs for Linux Architectures (Per Interconnect)), along with their associated communication libraries, the corresponding syntax,

Table 34.5:  Supported Interconnects for Linux Platforms (Per Platform)

Platform Processor Architecture Interconnects/Systems*
Linux 64-bit lnamd64 ethernet, infiniband, myrinet

(*) Node processes on the same machine communicate by shared memory. ANSYS Fluent lets the MPI autoselect the best interconnect available on the system. Users can specify an interconnect to override that selection. Ethernet is the fallback choice.

Table 34.6:  Available MPIs for Linux Platforms

MPI Syntax (flag) Communication Library Notes
ibmmpi -mpi=ibmmpi IBM MPI General purpose for SMPs and clusters

(1)

intel -mpi=intel Intel MPI General purpose for SMPs and clusters
openmpi -mpi=openmpi Open MPI Open source MPI-2 implementation. For both SMPs and clusters.
cray -mpi=cray Cray MPI (MPT)Only available on Cray systems.

(1) IBM Platform MPI Community Edition is installed with Fluent, which is limited to 4096 processes without an additional license. Refer to IBM Platform MPI with High (>4096) Process Count for details.

Table 34.7:  Supported MPIs for Linux Architectures (Per Interconnect)

Architecture Ethernet Myrinet* Infiniband Proprietary Systems Omni-Path****
lnamd64 ibmmpi (default), intel, and openmpi ibmmpi (default), openmpi** ibmmpi (default), intel, and openmpi Cray*** intel

(*) Both MX and GM Myrinet protocols are supported. ANSYS Fluent will automatically detect which type is running on the system and will use that particular protocol. You only have to supply the -pmyrinet option. If the hardware supports it, the installation and usage of Myrinet MX is recommended (consult your Myrinet vendor for applicability).

(**) The OpenMPI version packaged with ANSYS Fluent does not support Myrinet. However, you can use a local version of OpenMPI with Myrinet support.

(***) Using the Cray platform, the Extreme Scalability Mode (ESM) option is used by default, employing the native Cray MPI (MPT) library for parallel communication. Optionally, you can use the Cluster Compatibility Mode (CCM) mode, in which the standard IBM MPI library is used for parallel communication. For simulations with high core counts (for example, above 1000 cores), the ESM mode is recommended for better performance. Note that when using MPT version 5.0 and higher (up to, but not including 7.0), you must set the following environment variable: export FLUENT_USE_CRAY_MPT5=1.

(****) Omni-Path requires OFED driver version 10.2 or higher.

(Linux Only) To enable a job scheduler supported native remote node access mechanism, you can use the -scheduler_rsh command line flag or set the environment variable SCHEDULER_RSH=1. This tight integration is only supported for the MPI/Job scheduler combinations listed below:


Release 18.2 - © ANSYS, Inc. All rights reserved.