- Red Hat Linux 6 or 7
- CentOS 6 or 7
- SUSE 11
|Minimum Hardware Requirement
- 2 GHz dual-core CPU (or better)
- 4 GB of RAM
- 2 GB of disk space
|Data Storage Requirement
In terms of planning for the size growth of the database, the per file
records generate 1-2KB per file transfer, and the session records generate
8-12KB per session. For some size estimates, here are a few examples:
- 100 sessions per day of 1000 files each, all external transfers between
managed and unmanaged nodes = approx 2 MB per day db growth, 60 MB per
month, 700 MB per year.
- 1000 sessions per day of 1 file each, all internal between managed nodes
= approx 14 MB per day, 420 MB per month, 5 GB per year.
- 1000 sessions per day, 10,000 files each, 50% internal between managed
nodes, 50% external with unmanaged node = approx 15 GB per day, 450 GB
per month, 5.4 TB per year.
- Aspera Common Components
- MySQL Database
- Apache HTTP Server
Note: If there is an existing installation, shut down the MySQL database and the
Apache HTTP server during installation.
- In order to work with Console, node machines must have an Aspera transfer product
installed (IBM Aspera Enterprise Server, IBM Aspera Connect Server, or IBM Aspera Point-to-Point Client).
- To use the new Console architecture implemented in Console version 3.0
and on, the Aspera transfer products on existing node machines must be
upgraded to at least version 3.4.6 and ideally to the latest version.
These legacy nodes must be converted to use Node API using the built-in
convert option in the Console 3.0 Node edit screens. If a node is not
converted to use Node API, the legacy node will continue to report to
Console using the existing mechanism. For more information on node
conversion, see Converting Legacy Nodes.
|Firewall (on the Console Machine)
Open the following ports on the Console machine:
- For the Web UI, allow inbound connections for HTTP or HTTPS Web access (for example,
- Allow outbound connections for SSH (to be used for node administration) on a non-default,
configurable TCP port (for example, . TCP/33001).
- Allow an outbound connection for Aspera Central (for example, . TCP/40001).
- Allow an inbound connection for MySQL (for example, . TCP/4406).
|Firewall (on the Node Machines)
- To ensure that your server is secure, Aspera strongly recommends allowing inbound
connections for SSH on TCP/33001 (or on another non-default,
configurable TCP port), and disallowing inbound connections on TCP/22.
If you have a legacy customer base using TCP/22, you can allow inbound
connections on both ports. For details on securing your individual
Aspera transfer server product, review the corresponding user
- Allow inbound connections for FASP transfers, which use UDP/33001 by
default, although the server may also choose to run FASP transfers on
- For current nodes and legacy nodes that have been converted to current nodes, allow an
inbound connection on TCP 9092.
- For legacy nodes (unconverted), allow an inbound connection for Aspera Central (for
- For legacy nodes (unconverted), allow an outbound connection for logging to Console on
Note: No servers are listening on UDP ports.
When an Aspera client
initiates a transfer, the client opens an SSH session to the SSH server on
the designated TCP port and negotiates the UDP port over which the data
transfer will occur.