| Note |
|---|
FastX2 is now supported on the Neon HPC system. Benefits of FastX2 over FastX1
We encourage everyone to migrate to FastX2. |
Installing FastX2
Installing FastX1
Configuring FastX Clients to connect to HPC Systems
Resuming Sessions
FastX is a program for connecting to the HPC systems with a GUI desktop environment. It is similar to /wiki/spaces/hpcdocs/pages/76514725 connections but is newer and a little more robust when using Duo 2 factor authentication. Please see the FastX documentation site for detailed information on how to use FastX. FastX will send an automatic authentication request to your registered device if using the Duo app. Otherwise it will make a phone call to your registered number. Unlike No Machine though there is a much longer time out so it is more forgiving of slow push response times or the latency of a phone call for authentication. Another benefit that FastX has over No Machine is that you can close a remote desktop session but as long as the FastX program and the connection to the server was not disconnected the underlying ssh session is still active. This means that sessions can be started and stopped on the same server without triggering additional authentication requests from Duo.
| Anchor | ||||
|---|---|---|---|---|
|
You can download the FastX FastX2 client from the ITS software download page. After signing in with your HawkID find the FastX link and click on it. On the next page that opens up you will see buttons to download a client. Select the one that is appropriate for your system.
| Anchor | ||||
|---|---|---|---|---|
|
| Note |
|---|
HPC Systems recommends installing FastX2 instead of FastX1. |
You can download the FastX2 client from the ITS software download page. After signing in with your HawkID find the FastX link and click on it. On the next page that opens up you will see buttons to download a client. Select the one that is appropriate for your system.
Notice that there is also a listing of the license server and port. Take note of these as they will have to be entered after the FastX1 program is installed. The license information is not needed for FastX2. The installation procedures are fairly standard but for more details see the FastX page on the Engineering Wiki. Note that those instructions are for the FastX1 client. You will need to connect to a VPN for off-campus access if using FastX1. Since FastX2 is licensed on the server side the client does not require the VPN. However, if off-campus be sure to use port 40 in the connection settings. Unless you already have access to the Engineering VPN use the the UI Anywhere VPN service service.
...
Register license for FastX1
Once the program is installed you should be able to launch it in the way other programs are run on your system. Once the FastX1 client has launched you will need to enter the license information. To do that click on the Help menu and select Register. In the resulting dialog select License Server for the Activation Method. Enter the license server and port from the download page and enter into the respective boxes and click on the Okay button.Before you run FastX, you need to select the license server. From the Help menu, select Register. The License Activation dialogue box asks for the Activation Key. Use the arrow to the right of Activation Key to select License Server. Complete the License Server information as shown. Hostname: itsnt1396.iowa.uiowa.edu and Port: 5053. Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
To connect to the HPC systems, you will need to create entries for the hosts. To create a new entry click on the green + button of the FastX toolbar. This will open up a connection editor.
...
Select the one that you would like to use and it will start up in a new window. When you are finished with a session you can log out of it as normal. This will leave an ssh session open to the server so that any further sessions on that server will not need to go through the Duo authentication. To disconnect from the server completely, either exit FastX or right-click on the server name and select Disconnect.
| Anchor | ||||
|---|---|---|---|---|
|
Sessions can be resumed if they are not terminated when the FastX program is closed. Note that FastX sessions are dependent on an ssh connection to the server but are actually distinct. This means that you can disconnect from a server but leave the session running and reconnect to it later. In this scenario, the backend ssh connection to the server has to be established new so this will require Duo authentication. But once the ssh connection is up FastX will find any existing connections on the server. What is important to keep in mind here is that there are more than one login node per HPC system. Neon has 2 login nodes and Helium has 3. In each case they are round robin resolved so that a connection to neon.hpc.uiowa.edu will resolve to either neon-login-1.hpc.uiowa.edu or neon-login-2.hpc.edu. This is important to remember when trying to reconnect to sessions as your new connection will need to land on the same host as the session that you want. If you do this frequently you may want to create explicit connections for each login node.
...