112 lines
5.6 KiB
Markdown
112 lines
5.6 KiB
Markdown
# ANSYS - RSM
|
|
|
|
## ANSYS Remote Resolve Manager
|
|
|
|
**ANSYS Remote Solve Manager (RSM)** is used by ANSYS Workbench to submit
|
|
computational jobs to HPC clusters directly from Workbench on your desktop.
|
|
Therefore, PSI workstations ***with direct access to Merlin*** can submit jobs
|
|
by using RSM.
|
|
|
|
Users are responsible for requesting possible necessary network access and
|
|
debugging any possible connectivity problem with the cluster. In example, in
|
|
case that the workstation is behind a firewall, users would need to request a
|
|
**[firewall
|
|
rule](https://psi.service-now.com/psisp/?id=psi_new_sc_category&sys_id=6f07ab1e4f3913007f7660fe0310c7ba)**
|
|
to enable access to Merlin.
|
|
|
|
!!! warning
|
|
The Merlin6 administrators **are not responsible for connectivity problems** between users workstations and the Merlin6 cluster.
|
|
|
|
### The Merlin6 RSM service
|
|
|
|
A RSM service is running on each login node. This service will listen a
|
|
specific port and will process any request using RSM (in example, from ANSYS
|
|
users workstations). The following login nodes are configured with such
|
|
services:
|
|
|
|
* `merlin-l-01.psi.ch`
|
|
* `merlin-l-001.psi.ch`
|
|
* `merlin-l-002.psi.ch`
|
|
|
|
Each ANSYS release installed in `/data/software/pmodules/ANSYS` should have its
|
|
own RSM service running (the listening port is the default one set by that
|
|
ANSYS release). With the following command users can check which ANSYS releases
|
|
have an RSM instance running:
|
|
|
|
```bash
|
|
systemctl | grep pli-ansys-rsm-v[0-9][0-9][0-9].service
|
|
```
|
|
|
|
??? example "Listing RSM service running on merlin-l-001.psi.ch"
|
|
```console
|
|
# systemctl | grep pli-ansys-rsm-v[0-9][0-9][0-9].service
|
|
pli-ansys-rsm-v195.service loaded active exited PSI ANSYS RSM v195
|
|
pli-ansys-rsm-v202.service loaded active exited PSI ANSYS RSM v202
|
|
pli-ansys-rsm-v211.service loaded active exited PSI ANSYS RSM v211
|
|
pli-ansys-rsm-v212.service loaded active exited PSI ANSYS RSM v212
|
|
pli-ansys-rsm-v221.service loaded active exited PSI ANSYS RSM v221
|
|
```
|
|
|
|
## Configuring RSM client on Windows workstations
|
|
|
|
Users can setup ANSYS RSM in their workstations to connect to the Merlin6 cluster.
|
|
The different steps and settings required to make it work are that following:
|
|
|
|
1. Open the RSM Configuration service in Windows for the ANSYS release you want to configure.
|
|
2. Right-click the **HPC Resources** icon followed by **Add HPC Resource...**
|
|
|
|
3. In the **HPC Resource** tab, fill up the corresponding fields as follows:
|
|
|
|
* **"Name"**: Add here the preffered name for the cluster. In example: `Merlin6 cluster - merlin-l-001`
|
|
* **"HPC Type"**: Select `SLURM`
|
|
* **"Submit host"**: Add one of the login nodes. In example `merlin-l-001`.
|
|
* **"Slurm Job submission arguments (optional)"**: Add any required Slurm options for running your jobs.
|
|
* In general, `--hint=nomultithread` should be at least present.
|
|
* Check **"Use SSH protocol for inter and intra-node communication (Linux only)"**
|
|
* Select **"Able to directly submit and monitor HPC jobs"**.
|
|
* **"Apply"** changes.
|
|
4. In the **"File Management"** tab, fill up the corresponding fields as follows:
|
|
|
|
* Select **"RSM internal file transfer mechanism"** and add **`/shared-scratch`** as the **"Staging directory path on Cluster"**
|
|
* Select **"Scratch directory local to the execution node(s)"** and add **`/scratch`** as the **HPC scratch directory**.
|
|
* **Never check** the option "Keep job files in the staging directory when job is complete" if the previous
|
|
option "Scratch directory local to the execution node(s)" was set.
|
|
* **"Apply"** changes.
|
|
5. In the **"Queues"** tab, use the left button to auto-discover partitions
|
|
|
|
* If no authentication method was configured before, an authentication window will appear. Use your
|
|
PSI account to authenticate. Notice that the **`PSICH\`** prefix **must not be added**.
|
|
|
|
* From the partition list, select the ones you want to typically use.
|
|
* In general, standard Merlin users must use **`hourly`**, **`daily`** and **`general`** only.
|
|
* Other partitions are reserved for allowed users only.
|
|
* **"Apply"** changes.
|
|
|
|
6. *[Optional]* You can perform a test by submitting a test job on each partition by clicking on the **Submit** button
|
|
for each selected partition.
|
|
|
|
!!! tip
|
|
Repeat the process from for adding other login nodes if necessary. This
|
|
will give users the alternative of using another login node in case of
|
|
maintenance windows.
|
|
|
|
## Using RSM in ANSYS
|
|
|
|
Using the RSM service in ANSYS is slightly different depending on the ANSYS
|
|
software being used. Please follow the official ANSYS documentation for
|
|
details about how to use it for that specific software.
|
|
|
|
Alternativaly, please refer to some the examples showed in the following chapters (ANSYS specific software).
|
|
|
|
### Using RSM in ANSYS Fluent
|
|
|
|
For further information for using RSM with Fluent, please visit the **[ANSYS Fluent](ansys-fluent.md)** section.
|
|
|
|
### Using RSM in ANSYS CFX
|
|
|
|
For further information for using RSM with CFX, please visit the **[ANSYS CFX](ansys-cfx.md)** section.
|
|
|
|
### Using RSM in ANSYS MAPDL
|
|
|
|
For further information for using RSM with MAPDL, please visit the **[ANSYS mapdl](ansys-mapdl.md)** section.
|