titan

Up since 11/8/17 02:45 pm

eos

Up since 11/14/17 11:20 pm

rhea

Up since 10/17/17 05:40 pm

hpss

Up since 11/20/17 09:15 am

atlas1

Up since 11/15/17 07:25 am

atlas2

Up since 11/27/17 10:45 am
OLCF User Assistance Center

Can't find the information you need below? Need advice from a real person? We're here to help.

OLCF support consultants are available to respond to your emails and phone calls from 9:00 a.m. to 5:00 p.m. EST, Monday through Friday, exclusive of holidays. Emails received outside of regular support hours will be addressed the next business day.

GridFTP with SSH Authentication

See this article in context within the following user guides: Data

Configuring GridFTP with SSH Authentication

    No setup is required if you will be using SSH for authentication. However, to use this for remote transfers, the remote facility must also accept SSH for authentication.

Transferring Data

    Files are transferred using the globus-url-copy command. The arguments to that command will differ based on your authentication method.
    To use globus-url-copy with SSH authentication load the globus module:

      $ module load globus

    Then run the globus-url-copy command:

    For example, while on an OLCF resource, you can transfer file1 in your OLCF User Work area to file2 on a remote system:

     $ globus-url-copy -tcp-bs 12M -bs 12M -p 4 -v -vb file:/lustre/atlas/scratch/$USER/file1 sshftp://user@remote.system/remote/dir/file2

    From the OLCF, transfer file1 on a remote system to file2 in your User Work area:

     $ globus-url-copy -tcp-bs 12M -bs 12M -p 4 -v -vb sshftp://remote.system/remote/dir/file1 file:/lustre/atlas/scratch/$USER/file2

    From remote system, transfer file1 on a remote system to file2 in your User Work area:

     $ globus-url-copy -tcp-bs 12M -bs 12M -p 4 -v -vb file:/remote/dir/file1 sshftp://userid@dtn.ccs.ornl.gov/lustre/atlas/scratch/$USER/file2

SSH Keys

    SSH keys can not be used to grant passwordless access to OLCF resources. However, SSH keys can be created for OLCF systems to use for access to remote resources that support ssh keys.
    To create an SSH key pair for dtn.ccs.ornl.gov:
    Log in to dtn.ccs.ornl.gov and go to your .ssh directory or create a .ssh directory if you do not have one.
    $ssh-keygen -t dsa
    Enter passphrase (empty for no passphrase): 
    Enter same passphrase again: 
    Your identification has been saved in /ccs/home/$USER/.ssh/id_dsa.
    Your public key has been saved in /ccs/home/$USER/.ssh/id_dsa.pub.
    
    This will generate a ssh key pair consisting of id_dsa.pub and id_dsa. If you choose not to enter a passphrase, anyone who gains access to your private key file will then be able to assume your identity.
    To cash the private key and passphrase so that you do not need to enter it for every ssh operation in your session:
    $ ssh-agent
    $ ssh-add
    Identity added: /ccs/home/$USER/.ssh/id_rsa (/ccs/home/$USER/.ssh/id_rsa)
    Enter passphrase for /ccs/home/$USER/.ssh/id_dsa: 
    Identity added: /ccs/home/$USER/.ssh/id_dsa (/ccs/home/$USER/.ssh/id_dsa)
    Copy your id_dsa.pub to the remote resource’s .ssh directory and copy the contents into a file called “authorized_keys”.
    To test if this was successful, ssh to the remote resource from dtn.ccs.ornl.gov. If your ssh key works you will not need to enter your password for the remote resource.