File Transfer
From an NRAO Host
The hosts on either correlator can be reached via the NRAO DNS, file transfer can be initiated from an
NRAO host in a pretty straight-foward manner (assuming the access is to one of the three DNS accessible hosts:
- At the DC correlator
- server-1 (usno-server-1p-ext), server-2 (usno-server-2p-ext) and swc-001 (usno-server-swc-001p)
- At the SOC correlator
- server-1 (usno-server-1t-ext), server-2 (usno-server-2t-ext) and swc-001 (usno-server-swc-001t)
For example:
- scp user@theHost:thatFile localFile
- rsync localDirectory/ user@theHost:thatDirectory <-- The slash is required to prevent making localDirectory a subdirectory
At the remote usename can be
root
which allows reading and writing of any file on the remote host. If that policy gets
proscribed, then the remote user will have to be
admin
which may require some work since many files are accessible by root.
From a USNO DC Host
Initiating the transfer from a DC host is more complicated because entry into an NRAO host requires logging into
gygax
as one step.
This requires providing the user's NRAO password. If the target machine is the test cluster, then it may also be necessary to provide a password
to get into the cluster from
gygax
. Some
ssh
configuration files are provided in
/root/.ssh
which have the name =nraoUsername-s1t.config=—
these handle the hopping to get to
server-1t
by specifying the remote host as
server-1t
.
--
JimJacobs - 2020-08-04