cc_staff
1,894
edits
Ansys: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(Marked this version for translation) |
mNo edit summary |
||
| Line 87: | Line 87: | ||
Researchers who purchase a CMC license subscription must send their Alliance account username to <cmcsupport@cmc.ca> otherwise license checkouts will fail. The number of cores that can be used with a CMC license is described in the <i>Other Tricks and Tips</i> sections of the [https://www.cmc.ca/?s=Other+Tricks+and+Tips&lang=en/ Ansys Electronics Desktop and Ansys Mechanical/Fluids quick start guides]. | Researchers who purchase a CMC license subscription must send their Alliance account username to <cmcsupport@cmc.ca> otherwise license checkouts will fail. The number of cores that can be used with a CMC license is described in the <i>Other Tricks and Tips</i> sections of the [https://www.cmc.ca/?s=Other+Tricks+and+Tips&lang=en/ Ansys Electronics Desktop and Ansys Mechanical/Fluids quick start guides]. | ||
=== Local license servers === <!--T:16--> | === Local license servers ===<!--T:16--> | ||
<!--T: | <!--T:160--> | ||
Before a local Ansys license server can be | Before a local institutional Ansys license server can be used on the Alliance, firewall changes will need to be done on both the server and cluster side. For many Ansys servers this work has already been done and they can be used by following the steps in the "Ready To Use" section below. For Ansys servers that have never used on the Alliance, two additional steps must be done as shown in the "Setup Required" section also below. | ||
<!--T:18--> | ==== Ready To Use ====<!--T:17--> | ||
If | |||
<!--T:170--> | |||
To use an ANSYS License server that has already been setup for use on the cluster where you will be submitting jobs, contact your local Ansys license server administrator and get the following three pieces (1->3) of information: | |||
1) the fully qualified hostname (LICSERVER) of the server | |||
2) the Ansys flex port (FLEXPORT) number commonly 1055 | |||
3) the Ansys licensing interconnect port (INTEPORT) number commonly 2325 | |||
Once the three pieces of information are collected, configure your <code>~/.licenses/ansys.lic</code> file by plugging the values for LICSERVER, FLEXPORT and INTEPORT into the <code>FILE: ansys.lic</code> template above. | |||
==== Setup Required ====<!--T:18--> | |||
<!--T:180--> | |||
If your local Ansys license server has never been setup for use on the Alliance cluster(s) where you will be submitting jobs, then in addition to (1->3) above, you will ALSO need to get the following item (4,5) from the administrator: | |||
4) the static vendor port (VENDPORT) number from your local Ansys server administrator | |||
5) confirmation that <servername> will resolve to the same IP as LICSERVER on Alliance clusters | |||
where the <servername> can be found in the first line of the license file with format "SERVER <servername> <host id> <lmgrd port>". Item (5) is required otherwise Ansys license checkouts will not work on any remote cluster at the Alliance. If it turns out <servername> does not meet this requirement then request your license administrator to change <servername> to either the same fully qualified hostname as LICSERVER or at least to a hostname that will resolve to the same IP address as LICSERVER remotely. | |||
<!--T:181--> | |||
Finally send (1->4) by email to [[technical support]] being sure to mention which Alliance cluster(s) you want to run Ansys jobs on. Alliance system administrators will then proceed to open the firewall so license checkout requests can reach your license server from the specified cluster(s) compute nodes. In return you will then receive a range of IP addresses to forward to your server administrator can then open the local firewall to permit inbound Ansys license connections from the cluster(s) on EACH of the ports defined by FLEXPORT, INTEPORT and VENDPORT. | |||
== Checking license usage == <!--T:283--> | == Checking license usage == <!--T:283--> | ||