Translations:Ansys/17/en: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Importing a new version from external source)
(Importing a new version from external source)
Line 1: Line 1:
Before a local institutional Ansys license server can be reached from our systems, firewall configuration changes will need to be made on both the institution side and on our side.  To start this process, contact your local Ansys license server administrator and obtain the following information: 1) fully qualified hostname of the local Ansys license server; 2) Ansys flex port (commonly 1055); 3) Ansys licensing interconnect port (commonly 2325); and 4) Ansys static vendor port (site specific). In the case of license3.sharcnet.ca the static port is 1793. Ensure the administrator is willing to open the firewall on these three ports to accept license checkout requests from your Ansys jobs running on our systems.  Contact our [[technical support]] and send us the four pieces of information and indicate which system(s) you want to run Ansys on Beluga, Cedar, Graham/gra-vdi, Narval or Niagara.
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 2425 (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 setup for use on the particular Alliance system(s) 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.  Once you have all the information together send it to [[technical support]] and mention which system(s) you want to run Ansys jobs on ie) Beluga, Cedar, Graham/Gra-vdi, Narval or Niagara.  The Alliance support analyst assigned to your ticket will then arrange for the Alliance firewall to be opened so outbound license connections from the Ansys software can reach your license server.  The Analyst will also send you a range(s) 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 system(s).

Revision as of 00:16, 11 May 2023

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Ansys)
Before a local Ansys license server can be reached from an Alliance cluster, firewall changes will need to be done on both the server side and the Alliance side.  For many local 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 submitting jobs.

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 2425 (INTEPORT). With this information you can then immediately configure your ansys.lic file as described above and theoretically begin using the software. If however the license server has never been setup for use on the particular Alliance system(s) 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. Once you have all the information together send it to technical support and mention which system(s) you want to run Ansys jobs on ie) Beluga, Cedar, Graham/Gra-vdi, Narval or Niagara. The Alliance support analyst assigned to your ticket will then arrange for the Alliance firewall to be opened so outbound license connections from the Ansys software can reach your license server. The Analyst will also send you a range(s) 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 system(s).

Retrieved from "https://docs.alliancecan.ca/mediawiki/index.php?title=Translations:Ansys/17/en&oldid=135929"