For ALL 64-bit Linux platforms, OpenMotif, and Mesa libraries should be installed. These libraries are typically installed during a normal Linux installation. You will also need the xpdf package to view the online help.
ANSYS products require OpenMotif. After installing SuSe Linux Enterprise, review the table below and install the appropriate version of OpenMotif. (You may need to use "rpm -iv -force" to install these.)
Table 2.1: OpenMotif Versions for SUSE Linux Enterprise
| SUSE Linux Enterprise Release | OpenMotif Version | OpenMotif Zypper Package |
|---|---|---|
| SUSE Linux Enterprise 11 SP 3 | openmotif22-libs-2.2.4-139.1 or openmotif22-libs-32bit-2.2.4-139.1.x86_64 | openmotif22-libs or openmotif22-libs-32bit |
| SUSE Linux Enterprise 11 SP 4 | SLES 11 SP4: motif-2.3.4-1 | motif |
| SUSE Linux Enterprise 12 SP 0 | SLES 11 SP4: motif-2.3.4-1 | motif |
| SUSE Linux Enterprise 12 SP 1 | SLES 12 SP1: motif-2.3.4-4.15.x86_64 | motif |
For More information on OpenMotif libraries for your platform, see http://www.motifzone.net.
Red Hat Enterprise Linux 6.7 through 6.9 and 7.1 through 7.3 You need to install the following libraries:
libXp.x86_64
xorg-x11-fonts-cyrillic.noarch
xterm.x86_64
openmotif.x86_64
compat-libstdc++-33.x86_64
libstdc++.x86_64
libstdc++.i686
gcc-c++.x86_64
compat-libstdc++-33.i686
libstdc++-devel.x86_64
libstdc++-devel.i686
compat-gcc-34.x86_64
gtk2.i686
libXxf86vm.i686
libSM.i686
libXt.i686
xorg-x11-fonts-ISO8859-1-75dpi.noarch
glibc-2.12-1.166.el6_7.1 (or greater)
Red Hat no longer includes the 32-bit libraries in the base configuration so you must install those separately.
Additional requirements for Intel, AMD Opteron, and EM64T Linux systems are detailed below.
ANSYS, Inc. License Manager Linux x64 systems running the ANSYS, Inc. License Manager require the Linux Standard Base (LSB) 3.0 package.
CATIA V4 with Mechanical APDL To run CATIA V4 with Mechanical APDL on Linux 64-bit platforms, you must have the following Linux 32-bit i686 libraries:
glibc
libstdc++
ANSYS Workbench If you are running ANSYS Workbench using the KDE desktop environment, set the focus stealing prevention level to "None" to prevent the project save dialog boxes from appearing behind the application window:
Use the kcontrol command to launch the KDE Control
Center.
In the Control Center window, select .
Change Focus Stealing Prevention Level to None.
Click .
If you are running on KDE 4 or if the kcontrol command does not
exist, use System Settings to set the focus stealing prevention setting level to
"None":
Use the systemsettings command to launch the System
Settings.
In the System Settings window, select .
Change Focus Stealing Prevention Level to None.
Click .
Semaphore Limit On some Linux systems, ANSYS Workbench reaches a system limit on the number of semaphores in the Linux configuration. In this case, you will see a message similar to the following:
sem_lock->semop->op_op: Invalid argument
sem_unlock->semctl: Invalid argument
To increase the number of semaphores, run the following command as owner or root:
% echo 256 40000 32 32000 > /proc/sys/kernel/sem
This modification takes effect immediately, but is reset at the next reboot. To avoid resetting the limit when rebooting, add the above command to one of your system’s startup scripts by copying the command into a file called mod_sem and then setting up the following links to execute the file each time you restart your system:
cp mod_sem /etc/init.d ln -s /etc/init.d/mod_sem /etc/rc3.d/S61mod_sem ln -s /etc/init.d/mod_sem /etc/rc5.d/S61mod_sem
Mechanical, Meshing, DesignModeler, and FE Modeler Applications If you are using a localized operating system (such as French or German), you must set
the mwcontrol VisualMainWin control on any machines running these
applications in order for these applications to recognize the correct numerical format.
ANSYS Workbench must already be installed before setting this control.
First, you need to ensure that the /v182/aisol/WBMWRegistry/ directory has write permissions. From the /v182/aisol/ directory, issue the following command:
chmod -R 777 WBMWRegistry/
Then, use the following procedure to set mwcontrol for your
locale:
cd to <wb_install
directory>/v182/aisol
Issue the following command:
./.workbench -cmd mwcontrol
On the MainWin Control Panel, select .
Select the Regional Settings tab.
Change the language in the dropdown to match the language you want to use.
Check the Set as system default locale option.
Click to accept the changes, and then click to dismiss the Change Regional Settings notification.
Using Fluent with Infiniband On some operating systems, the default amount of physical memory that can be pinned/locked by a user application is set to a low value and must be explicitly increased. A value recommended by Intel is 90% of the physical memory. Therefore, the following should be added to the /etc/security/limits.conf file:
* hard memlock unlimited * soft memlock unlimited
The need for increasing the limits may be indicated by the following error message with Platform MPI:
fluent_mpi.16.0.0: Rank 0:1: MPI_Init: ibv_create_cq() failed fluent_mpi.16.0.0: Rank 0:1: MPI_Init: Can't initialize RDMA device fluent_mpi.16.0.0: Rank 0:1: MPI_Init: MPI BUG: Cannot initialize RDMA protocol libibverbs: Warning: RLIMIT_MEMLOCK is 32768 bytes. This will severely limit memory registrations
When Fluent is launched by a scheduler (like PBSPro, SGE, etc.), these limits may be reset by the scheduler. You may check running the “limit” command within and without the scheduler to compare. Any differences indicate the issue above.
If you use PBSPro, add ulimit -l unlimited directly in the
pbs_mom startup script, and let PBS reload the
pbs_mom.
If you use SGE, you must change the startup script
/etc/init.d/sgeexecd to include the ulimit -l
unlimited command as shown in the following example:
-- BEGIN -- if [ "$startup" = true ]; then # execution daemon is started on this host! echo " starting SGE_execd" exec 1>/dev/null 2>&1 ulimit -l unlimited $bin_dir/SGE_execd else -- END --
Once this modification is in place, restart SGE to set the correct memory limits on the SGE daemon and any invoked processes.
Using Mechanical APDL with Infiniband On some operating systems, the default amount of physical memory that can be pinned/locked by a user application is set to a low value and must be explicitly increased. A value recommended by Intel is 90% of the physical memory. Therefore, the following should be added to the /etc/security/limits.conf file:
* hard memlock unlimited * soft memlock unlimited
This behavior has been observed on Intel MPI 4.1.3, but might also occur on Platform MPI 9.1.4.2.
Using the Fluent Launcher On Linux systems, you must have the following package (as appropriate for your platform) installed in order to use the Fluent launcher:
| SUSE 11 pr 12: libstdc++33 |
Using ANSCUSTOM If you use ANSCUSTOM to link your own version of ANSYS Release 18.2 on a SUSE SLES 11.x or 12.x computer, you may see two unsatisfied externals that are system, not ANSYS files, due to the linker looking for some system files in a Red Hat directory on a SUSE computer.
To work around this problem, run the following as root:
mkdir –p /usr/lib/gcc/x86_64-redhat-linux/3.4.6
ln -sf /usr/lib/gcc/i586-suse-linux/2.95.3/crtbegin.o /usr/lib/gcc/x86_64-redhat-linux/
3.4.6/crtbegin.o
ln -sf /usr/lib/gcc/i586-suse-linux/2.95.3/crtend.o /usr/lib/gcc/x86_64-redhat-linux/
3.4.6/crtend.o
The revision numbers shown in the examples (2.95.3 and 3.4.6) may be different on your
system. The linker will specify where it is trying to find the
crtbegin.o and crtend.o files; that location
will be the last part of the above commands. You can use the Linux
locate command to find the existing
crtbegin.o and crtend.o files; that location
would be the first part of the above commands.
System Libraries On 64-bit Linux (linx64) systems, the ANSYS Release 18.2 executable is looking for system
libraries that do not have revision numbers appended to the end of their file names. On
some SUSE systems, the graphics libraries all have revision numbers appended to the end
of the library filenames. In these cases, ANSYS quits because the loader cannot find all
of the libraries that it is looking for. When running ANSYS Release 18.2, the loader will
inform you that it is unable to locate a specific library (for example,
libXm.so). Using the Linux locate
command, find the library (libXm.so in this example) on your system
and add the appropriate symbolic link as seen below.
To overcome this possible problem, run the following as root:
ln -sf /usr/lib64/libGLU.so.1.3.060402 /usr/lib64/libGLU.so ln -sf /usr/X11R6/lib64/libXm.so.3.0.3 /usr/X11R6/lib64/libXm.so ln -sf /usr/X11R6/lib64/libXp.so.6.2 /usr/X11R6/lib64/libXp.so ln -sf /usr/X11R6/lib64/libXt.so.6.0 /usr/X11R6/lib64/libXt.so ln -sf /usr/X11R6/lib64/libXext.so.6.4 /usr/X11R6/lib64/libXext.so ln -sf /usr/X11R6/lib64/libXi.so.6.0 /usr/X11R6/lib64/libXi.so ln -sf /usr/X11R6/lib64/libX11.so.6.2 /usr/X11R6/lib64/libX11.so ln -sf /usr/X11R6/lib64/libSM.so.6.0 /usr/X11R6/lib64/libSM.so ln -sf /usr/X11R6/lib64/libICE.so.6.4 /usr/X11R6/lib64/libICE.so ln -sf /lib64/libgcc_s.so.1 /lib64/libgcc.so
For Linux, you may need the following:
ln -sf /usr/lib64/libXm.so.4.0.0 /usr/lib64/libXm.so.3
The revision numbers appended to the filenames on the left may be different on your system.
ANSYS was built and tested on Red Hat using the compilers as noted in Table 2.2: Compiler Requirements for All Linux Versions. The ANSYS solver is built on Red Hat Enterprise Linux AS release 4 (Update 5).
For ANSYS Workbench and ANSYS Autodyn, you may need to increase the stack size; we recommend setting it to 1 GB. Add the following to your configuration file:
For the Bourne (bash) shell:
ulimit -s 1024000
For the C (csh) shell:
limit stacksize 1024000
Other shells may have different settings; refer to your shell documentation for specific details.
ANSYS was built and tested on a generic Intel EM64T system running Red Hat Enterprise Linux AS release 5.3.
If you are running on Intel's Xeon EM64T system, we recommend that you turn CPU hyperthreading off (default is on). A system administrator needs to reboot the system and enter the BIOS to turn the hyperthreading option off.