Configuring Electronics Installation for HPC
In HPC applications, Ansys Electromagnetics Suite must be available on each cluster host where jobs may be run.
- On the Linux platform, Ansys EM may be installed on a shared drive that is accessible to all machines in the cluster.
- On the Windows platform, Ansys EM must be installed separately on each host of the cluster.
Ansys EM must be accessible using the same path on each host. All cluster users running Ansys EM jobs must have permission to read and execute the files in the installation directory and its subdirectories.
The temp directory selected during installation must be readable and writable by all user accounts used to run the Ansys Electromagnetics Suite. This temp directory path should be the same on all machines of the cluster and should be local to every machine. For example, C:\temp on Windows, /tmp on Linux.
Because HPC is offered as a direct integration, you need only install the Ansys EM software. No additional configuration is required.
Firewall Configuration
If firewall is turned off between the machines of the cluster, there is no need for any configuration.
If firewall is turned on:
- For a Windows cluster: Configure firewall by adding exceptions that allow Ansys EM programs and services to communicate with each other. If you are using a standard Windows Firewall, this is automatically done for you by the installation program. If you are using a third-party firewall software, it needs to be configured in a similar manner.
- For a Linux cluster: Open up the firewall for range of ports denoting ephemeral (or dynamic) ports. Check with your system administrator on how this can be done on each machine of cluster.
Installation Directory Examples
Microsoft Windows
Install the Ansys Electromagnetics Suite in directory C:\Program Files\AnsysEM\v242\win64 on each node of the cluster. The same directory pathname must be used on all hosts.
Linux
Install the Ansys Electromagnetics Suite in a common directory that is accessible using the path /opt/AnsysEM/v242 on each execution node of the cluster.