Connecting
Connecting for the first time
All connections to the NOAA RDHPCS enclave are done via Secure Shell (SSH) in a terminal session to a Bastion, or via a web browser to ParallelWorks. See our ParallelWorks guide.
Note
For access to the MSU HPC systems Orion and Hercules, please review the MSU-HPC user guide.
Authentication is via a CAC/PIV card or RSA SecurID token.
Internal to the enclave, X509 certificates are used to authenticate between resources. At first login, and at yearly intervals, a master certificate valid for one year is created (SSH Bastion login required) with a user-defined pass-phrase. At each successive log in, a thirty-day proxy certificate is created and used for resource access and data transfers.
Attention
You must have access to an RDHPCS resource (system) in order to log into it! Visit the Account Information Management website to view your RDHPCS profile and system access.
Access to most RDHPCS systems require a signed x.509 certificate. The first login attempt will generate a master certificate request. You will experience a short (less than 5 minute) delay while the request is signed. Users cannot fully log on to a system until that certificate is signed.
The prompt will ask you to create a passphrase. Create a passphrase with a minimum of three words.
Note
Do not worry if you forget your passphrase – just continue to try. On the 4th attempt the system will prompt you to recreate your master certificate.
Secure Shell (SSH) Access
Access to on premise RDHPCS compute resources is done using the Secure Shell (SSH) protocol to one of the system’s bastions, or via ParallelWorks.
MSU systems (Orion, Hercules) are accessed via SSH or OpenOnDemand. See MSU-HPC Logging In for instructions.
SSH clients are available for Windows-based systems, such as published by VanDyke software. For recent SecureCRT versions, the preferred authentication setting shown above
For Windows systems, PuTTY, SecureCRT, or MobaXterm can also be used to provide SSH capability. Recent updates to Windows 10 and Windows 11 have added built-in support for SSH. If it is not installed on your version of Windows, please refer to Microsoft’s documentation on OpenSSH.
Bastion Hostnames
RDHPCS System |
CAC Bastion hostnames |
RSA Bastion hostnames |
Gaea |
gaea.princeton.rdhpcs.noaa.gov gaea.boulder.rdhpcs.noaa.gov |
gaea-rsa.princeton.rdhpcs.noaa.gov gaea-rsa.boulder.rdhpcs.noaa.gov |
Hera |
hera.boulder.rdhpcs.noaa.gov hera.princeton.rdhpcs.noaa.gov |
hera-rsa.boulder.rdhpcs.noaa.gov hera-rsa.princeton.rdhpcs.noaa.gov |
Jet |
jet.boulder.rdhpcs.noaa.gov jet.princeton.rdhpcs.noaa.gov |
jet-rsa.boulder.rdhpcs.noaa.gov jet-rsa.princeton.rdhpcs.noaa.gov |
Niagara |
niagara.boulder.rdhpcs.noaa.gov niagara.princeton.rdhpcs.noaa.gov |
niagara-rsa.boulder.rdhpcs.noaa.gov niagara-rsa.princeton.rdhpcs.noaa.gov |
PPAN |
bastion-analysis.princeton.rdhpcs.noaa.gov bastion-analysis.boulder.rdhpcs.noaa.gov |
analysis-rsa.princeton.rdhpcs.noaa.gov analysis-rsa.boulder.rdhpcs.noaa.gov |
Cloud |
Unavailable |
|
MSU-HPC Orion |
Unavailable |
Common Access Card (CAC) SSH Login
RDHPCS users with a CAC who are logging in from a Windows, Mac, or Linux system are recommended to use a CAC login. This requires a CAC reader and software from Tectia. If you recently were issued a new CAC or renewed CAC, please log into the Account Information Management website to update the CAC information.
Reference the Tectia pages for complete information on how to configure Tectia initially for login using SSH with your CAC.
sshg3 CAC-BASTION-HOSTNAME
Reference the table above for the appropriate CAC Bastion to use.
When prompted, enter your CAC PIN.
RSA SSH Login
RDHPCS users who do not have a CAC, or lack the required hardware or software, are welcome to use an RSA login.
ssh RSA-BASTION-HOSTNAME
Reference the table above for the appropriate RSA Bastion to use.
When prompted, enter your PASSCODE which consists of your PIN+RSA_CODE. The RSA_CODE is the 6-8 digit code from the RSA fob or RSA app.
Selecting a Node
RDHPCS systems accessed via SSH allow users to select a specific head node at login. After successful authentication at the bastion host, a list of available nodes will be displayed with a 5 second delay to choose a specific destination. To select a specific host, press Control+C (^C) and enter the desired node.
Here is an example of what the display looks like for the Gaea system mid 2024:
Welcome to the NOAA RDHPCS.
Attempting to renew your proxy certificate...Proxy certificate has 720:00:00 (30.0 days) left.
Welcome to gaea.rdhpcs.noaa.gov
Gateway to gaea-c5.ncrc.gov and other points beyond
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! RDHPCS Policy states that all user login sessions shall be terminated !!
!! after a maximum duration of seven (7) days. ALL user login sessions will !!
!! be dropped from the Princeton Bastions at 4AM ET / 2AM MT each Monday !!
!! morning, regardless of the duration. Please note: This will NOT impact !!
!! batch jobs, cron scripts, screen sessions, remote desktop, or data !!
!! transfers. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hostname Description
gaea C5 head nodes
gaea51 C5 head node
gaea52 C5 head node
gaea53 C5 head node
gaea54 C5 head node
gaea55 C5 head node
gaea56 C5 head node
gaea57 C5 head node
gaea58 C5 head node
gaea60 T6 Test access only
gaea61 C6 head node
gaea62 C6 head node
gaea63 C6 head node
gaea64 C6 head node
gaea65 C6 head node
gaea66 C6 head node
gaea67 C6 head node
gaea68 C6 head node
You will now be connected to NOAA RDHPCS: Gaea (CMRS/NCRC) C5 system.
To select a specific host, hit ^C within 5 seconds.
Note
After the 5 second wait, the bastion node will use a load balancer to select a node.
X11 Graphics
Users can use SSH X11 forwarding to open GUI-based applications (e.g., xterm,
ARM Forge). This is typically done using an SSH option. For the TECTIA client
sshg3
or OpenSSH-based clients, use the -X
option:
gsissh -X host.url
or
ssh -X host.url
Other clients, like PuTTY, will have an option when configuring the host.
The base SSH X11 forwarding is typically slow. RDHPCS systems use X2Go for improved X11 performance. Some users have found it difficult to use X2Go. Please submit a support issue if you have issues using X2Go.
Note
Microsoft Windows users can use any of the X11 servers available for Windows. The SSH client will need to be configured to use the X11 server for forwarding X11.
SSH Port Tunnels
To allow users to easily transfer small files to and from the RDHPCS systems, the bastion configures SSH port-forwarding tunnels. To use these tunnels, the user must configure their local SSH client to create tunnels to/from the bastion.
See the Port Tunnel section of the Tectia page for details.
Web based ParallelWorks Access
See the RDHPCS Cloud Computing for details on using ParallelWorks in a web browser to access on-premise and cloud HPCS.