After you configured an Aspera transfer user on HSTS, test that an Aspera client can successfully connect to
HSTS and upload a
file.
Prerequisites:
- Client: Install an Aspera client application, such as IBM Aspera Desktop Client or
IBM Aspera Command Line
Interface, on the client computer.
- Server:
HSTS must have at least
one Aspera transfer user that is configured on it. A system user account that is configured to
authenticate Aspera transfers is required.
If any of the following connection tests fail, see Clients cannot establish connection.
-
On the client, test that you can reach the IP address of your server.
Run the
ping
command:
# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: icmp_seq=0 ttl=64 time=8.432 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=7.121 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=5.116 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=4.421 ms
64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=3.050 ms
...
In the example, the address of HSTS is 10.0.0.2 and the output shows successful responses from the
host.
If the output returns Destination host unreachable
, review the firewall
configuration of the server.
-
On the client, try a transfer to HSTS by using ascp.
Use the following syntax on your client machine:
# ascp -P 33001 -l max_rateunit source_pathtransfer_username@ip_address:destination_dir
For
example,
# ascp -P 33001 -l 10M /client-dir/files xfer_user1@10.0.0.2:/users/xfer_user/tmp
For
more information about ascp, see Ascp command reference.