Preparing Your System for Installation

Before beginning the installation process for Faspex, you must be logged into your computer as an admin .
Warning: Due to incompatible common components, IBM Aspera Console and IBM Aspera Faspex cannot be installed on the same machine. Aspera does not support this combination. If you are running an older version of Faspex and Console on the same machine, contact Technical Support to move one of the applications to another system.
Make sure you have taken the following steps to prepare your system and to ensure that installation goes smoothly.
  1. Determine whether Faspex has a domain name.

    Aspera recommends creating a domain name for Faspex. If Faspex is configured to identify itself by IP address (rather than by domain name), then the URLs in your notification emails contain an IP address (for example, ""). Some Web-based email services (such as Yahoo or Ymail, and Hotmail) have been known to automatically flag emails containing IP address links as "Spam," and move them to your Junk/Spam folder. If you do not have a domain name immediately available, then you can first configure Faspex with an IP address and then change it to use a domain name later.

    If you know that you will not be setting up a domain name, make sure that users add your Faspex "From" email address (for example, to their address book or contact list. Doing so typically "white-lists" the address so that emails from Faspex are not automatically flagged and routed the Junk/Spam folder.

    Do not configure Faspex to use a domain name or hostname that contains underscore characters. Doing so could prevent you from logging into the server or cause other connectivity problems. Internet standards for domain names and hostnames do not support underscore characters.
  2. Download the latest Aspera installers.

    Download the latest version of IBM Aspera Enterprise Server,Common Components and IBM Aspera Faspex installers from the following locations:

    You are required to enter your organization's Aspera login credentials to gain access. If you need help determining your organization's access credentials, contact Technical Support.

  3. Install Enterprise Server with a Connect server license.

    For instructions on installing your software and license, follow the steps in the IBM Aspera Enterprise Server or IBM Aspera Connect Server Admin Guide.

    The transfer server can be set up in either of the following configurations:

    • locally, on the same host as Faspex
    • remotely, on a separate host
    In the aspera.conf file (/opt/aspera/etc/aspera.conf) check the following:
    • Look for <persistent_store> in the <central_server> section, and be sure that it is set to enable (default value). This setting allows the retention of historical transfer data used by the stats collector.
    • Look for the <dir_allowed> setting for the faspex user, and ensure that it's set to true (default value).
    If you change settings, you must restart asperacentral and asperanoded.
    # service asperacentral restart
    # service asperanoded restart
  4. Enable port 33001 for fasp transfers.
    Open your SSH configuration file in a text editor. The configuration file is located in the following directory: /etc/ssh/sshd_config.

    Add the line Port 33001 to the configuration file to enable access to port 33001. If you are also using port 22 for shell access to the server you also need to add or uncomment the line Port 22 in the config file.

    Restart the SSH server to apply your new settings:

    # service sshd restart
  5. If you installed Enterprise Server on a remote host, you must configure the remote host to work with Faspex. For more information, see Working With Remote Servers.
You are now ready to install Faspex on your server. For more information on installing Faspex, see Installing Faspex with a Local Node.