rsnt_translations
56,573
edits
Ansys: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Marked this version for translation) |
No edit summary |
||
| Line 90: | Line 90: | ||
<!--T:17--> | <!--T:17--> | ||
Before a local Ansys license server can be reached from an Alliance system, firewall changes will need to be done on both the server side and the Alliance side. For many institutional servers this work has already been done. In such cases you simply need to contact your local Ansys license server administrator and request 1) the fully qualified hostname (LICSERVER) of the server; 2) the Ansys flex port commonly 1055 (FLEXPORT); and 3) the Ansys licensing interconnect port commonly 2325 (INTEPORT). With this information you can then immediately configure your <code>ansys.lic</code> file as described above and theoretically begin using the software. If however the license server has never been | Before a local Ansys license server can be reached from an Alliance system, firewall changes will need to be done on both the server side and the Alliance side. For many institutional servers this work has already been done. In such cases you simply need to contact your local Ansys license server administrator and request 1) the fully qualified hostname (LICSERVER) of the server; 2) the Ansys flex port commonly 1055 (FLEXPORT); and 3) the Ansys licensing interconnect port commonly 2325 (INTEPORT). With this information you can then immediately configure your <code>ansys.lic</code> file as described above and theoretically begin using the software. If however the license server has never been set up for use on the Alliance systems that you want to use it on, then you will also need to request the 4) static vendor port number (VENDPORT) number from your administrator. <br> | ||
Once you have all the information together, send it to [[technical support]] and mention which systems you want to use to run Ansys jobs. We will then arrange for the Alliance firewall to be opened so outbound license connections from the Ansys software can reach your license server. You will also be sent a range of IP addresses so that your server administrator can likewise open the local firewall to allow inbound license connections to your server on the required ports (FLEXPORT, INTEPORT, VENDPORT) from the requested Alliance systems. | Once you have all the information together, send it to [[technical support]] and mention which systems you want to use to run Ansys jobs. We will then arrange for the Alliance firewall to be opened so outbound license connections from the Ansys software can reach your license server. You will also be sent a range of IP addresses so that your server administrator can likewise open the local firewall to allow inbound license connections to your server on the required ports (FLEXPORT, INTEPORT, VENDPORT) from the requested Alliance systems. | ||
| Line 96: | Line 96: | ||
<!--T:2830--> | <!--T:2830--> | ||
Ansys comes with an <code>lmutil</code> tool that can be used to check your license usage. Before using it verify your <code>ansys.lic</code> is configured. Then run the following two commands on a cluster that you are | Ansys comes with an <code>lmutil</code> tool that can be used to check your license usage. Before using it verify your <code>ansys.lic</code> is configured. Then run the following two commands on a cluster that you are set up to use: </translate> | ||
{{Commands2 | {{Commands2 | ||
|module load ansys | |module load ansys | ||
| Line 120: | Line 120: | ||
# Now you need to create a "journal" file. It's purpose is to load the case file (and optionally the data file), run the solver and finally write the results. See examples below and remember to adjust the filenames and desired number of iterations. | # Now you need to create a "journal" file. It's purpose is to load the case file (and optionally the data file), run the solver and finally write the results. See examples below and remember to adjust the filenames and desired number of iterations. | ||
# If jobs frequently fail to start due to license shortages and manual resubmission of failed jobs is not convenient, consider modifying your script to requeue your job (up to 4 times) as shown under the <i>by node + requeue</i> tab further below. Be aware that doing this will also requeue simulations that fail due to non-license related issues (such as divergence), resulting in lost compute time. Therefore it is strongly recommended to monitor and inspect each Slurm output file to confirm each requeue attempt is license related. When it is determined that a job is requeued due to a simulation issue, immediately manually kill the job progression with <code>scancel jobid</code> and correct the problem. | # If jobs frequently fail to start due to license shortages and manual resubmission of failed jobs is not convenient, consider modifying your script to requeue your job (up to 4 times) as shown under the <i>by node + requeue</i> tab further below. Be aware that doing this will also requeue simulations that fail due to non-license related issues (such as divergence), resulting in lost compute time. Therefore it is strongly recommended to monitor and inspect each Slurm output file to confirm each requeue attempt is license related. When it is determined that a job is requeued due to a simulation issue, immediately manually kill the job progression with <code>scancel jobid</code> and correct the problem. | ||
# After [[Running_jobs|running the job]] you can download the data file and import it back into Fluent with <i>File > Import > Data…</i>. | # After [[Running_jobs|running the job]], you can download the data file and import it back into Fluent with <i>File > Import > Data…</i>. | ||
=== Slurm scripts === <!--T:220--> | === Slurm scripts === <!--T:220--> | ||