Contents
Connecting to the PMACS Cluster
Currently, secure shell (SSH) is the only supported method of connecting to the cluster. The login machine name is consign.pmacs.upenn.edu You should probably add "ServerKeepAliveInterval 60" to your SSH client's configuration. After your account is created, you can connect using your PMACS credentials.
VPN for Off-campus access
The PMACS Cluster is behind a firewall. All users authorized to use the PMACS cluster can use this VPN to establish secure connections to the PMACS cluster when trying to SSH from off-campus. This is a web based VPN that can be accessed here. Once a VPN tunnel has been setup, normal SSH connections to the cluster head node: consign.pmacs.upenn.edu can be established.
Note 1 There may be other VPNs managed by PMACS/UPHS. Please ensure that while connecting to the PMACS cluster, you are using this VPN only.
Note 2 The VPN link above may present you with a self-signed certificate ("Untrusted connection") message. It is good practice to always verify that you are connecting to the right server. The SHA1 fingerprint for the certificate is:
38:CF:5F:DC:08:08:CD:74:86:50:A2:C2:B5:78:99:8F:66:51:48:76
Note 3 The web-based VPN is known to work with browsers like Firefox, Internet Explorer (IE) and Safari. There are known issues with using Chrome.
Note 4 Note 3. above is outdated. Subsequent to a recent update to our firewall, the web-based based VPN plugin may no longer work. See updated VPN information below.
VPN Client for Mac OS X (outdated information)
There is a known issue that prevents laptops/desktops running Mac OS X Yosemite from being able to download the VPN client from our firewall appliance. The direct link to the client application is here
Mac OS X El Capitan (outdated information)
There is a known issue with Mac OS X El Capitan (10.11) that prevents SSH/SCP/SFTP/rsync connections to the PMACS HPC cluster after the VPN session has been established. The fix is to use the "internal" IP addresses of the head node, consign.pmacs.upenn.edu, and/or the file transfer node, mercury.pmacs.upenn.edu, after setting up the web-based VPN tunnel. The internal IP addresses of both these systems are:
- consign.pmacs.upenn.edu: 172.16.103.23
- mercury.pmacs.upenn.edu: 172.16.103.24
VPN Client for GNU/Linux
Download client from here
Please also see the section below for more information on how to run the VPN client on GNU/Linux systems.
If the above approach to downloading and installing the web-based PMACS VPN does not work, the alternate approach is to install the stand-alone VPN console.
First download the appropriate installer for
OR
Once the appropriate installer has been downloaded and installed, a reboot may be required to reboot. Subsequently, the stand-alone client console must be used, without needing to use a web browser (as described on our wiki).
See pictures below for details on how to configure the Standalone VPN client (works for Windows and MacOS). Separate information for GNU/Linux VPN clients is also below.
Important Host/Server Names
- consign.pmacs.upenn.edu : head node/login server ; Do NOT run jobs on consign
- mercury.pmacs.upenn.edu : file transfer server and the server where home directories are initailized on First Login; Do NOT run jobs on mercury either
- PMACS VPN For Off-Campus Access
- But first see note about the VPN (above).
First Login
Temporary Password Change
All PMACS accounts are provisioned with a temporary password. Before you can log into the PMACS cluster for the first time, you will need to change this temporary password. Change of the temporary password and enrollment into the PMACS password reset system can be done here
Enrollment into the PMACS Password Reset system
All PMACS account passwords are set to expire every 180 days. To avoid your password from expiring and possibly preventing access to the PMACS cluster, all cluster users are encouraged to enroll into the reset system. The password reset application can be access here. Once enrolled, this system will also allow you to recover forgotten PMACS passwords and reset known/expired PMACS passwords.
Initialize your home area
- With the newly changed password log into the file transfer host: mercury.pmacs.upenn.edu
ssh <your_user_name>@mercury.pmacs.upenn.edu
Remember to replace <your_user_name> above with your PennKey username
- Upon login, you will see a message similar to
Creating home directory for <user_name>
- You are now ready to start using the PMACS HPC cluster :
ssh <your_user_name>@consign.pmacs.upenn.edu
Remember to replace <your_user_name> above with your PennKey username.
Once your home area has been initialized, you are ready to use the PMACS cluster. Do NOT attempt to run jobs on mercury.pmacs.upenn.edu or submit jobs from mercury.pmacs.upenn.edu. Please look at the PMACS HPC Users Guide for information on how to run jobs on the PMACS cluster.
File transfer to and from the PMACS HPC Cluster
Transferring data to/from the PMACS HPC cluster is done with program that supports the SSH v2 protocol. Programs like SCP, sFTP, rsync, WinSCP, Filezilla etc. are all supported.
All file transfer operations to/from the PMACS HPC cluster must be done via the dedicated file transfer server: mercury.pmacs.upenn.edu
File transfer using command line tools
Poplar command line programs for file transfer include SCP, sFTP, rsync, PSCP etc.
The following examples show how to transfer data (in this case, a file named "test") from a laptop/desktop computer to the PMACS HPC using the rsync program via the file transfer server: mercury.pmacs.upenn.edu
Be sure to replace "PMACSUSER" in the command below with your PMACS userid
% rsync -av test PMACSUSER@mercury.pmacs.upenn.edu:~/
File transfer using graphical tools
Poplar command line programs for file transfer include WinSCP, FileZilla etc.
The image below shows the settings to use in FileZilla, for file transfer to the PMACS HPC via the file transfer server: mercury.pmacs.upenn.edu
Be sure to replace "PMACSUSER" in the image below with your PMACS userid
Optional Section: Instructions for generating Public-Private keypairs
For added convenience and security, Public-Private Keys may be used for SSH connections to the PMACS cluster.
On Mac OS X and GNU/Linux systems, run the following command from within a terminal and follow the on-screen instructions. Please DO NOT copy-paste. Read each command and run the command on your own:
$ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key ($HOME/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in $HOME/.ssh/id_rsa. Your public key has been saved in $HOME/.ssh/id_rsa.pub. The key fingerprint is: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx asrini@ The key's randomart image is: +--[ RSA 2048]----+ | . | | kjweo | | x B E x | | * B l + | | S +aser .| | + + | | . weq | | . x 12| | 45+ | +-----------------+
On Windows machines you can generate and use PublicKeys with Putty. Here is a link to a Youtube channel which has video tutorials for generating and using Public keys.
After generating a Public-Private keypair, copy the contents of the .ssh/id_rsa.pub file to a file named .ssh/authorized_keys in your home area on the PMACS cluster.
INSTRUCTIONS BELOW, TO COPY PUBLIC KEYS, INDICATE USING THE HEAD NODE. YOU CAN ALSO USE OUR DEDICATED FILE TRANSFER NODE: mercury.pmacs.upenn.edu
[$USER@consign ~]$ if [ ! -d $HOME/.ssh ]; then mkdir -m 700 $HOME/.ssh; fi [$USER@consign ~]$ vim .ssh/authorized_keys One SSH public key per line; save and close the file
Then change the permissions on the file:
[$USER@consign ~]$ chmod 600 .ssh/authorized_keys
INSTRUCTIONS ABOVE, TO COPY PUBLIC KEYS, INDICATE USING THE HEAD NODE. YOU CAN ALSO USE OUR DEDICATED FILE TRANSFER NODE: mercury.pmacs.upenn.edu
More VPN Info
Below are screenshots that describe how to use the PMACS VPN on Windows or MacOS systems:
Below are screenshots that describe how to use the PMACS VPN on GNU/Linux systems:
