IBM Aspera Console 3.1.0 Release Notes

Product Release: September 30, 2016

Release Notes Updated: September 30, 2016

This release of IBM Aspera Console 3.1.0 provides the new features, fixes, and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.


  • Managed Clusters
    • You can now add IBM Aspera Transfer Clusters to your Console as managed clusters.
    • Managed clusters must be clusters built with IBM Aspera Enterprise Server 3.7.1+.
    • Console now monitors transfers running on managed clusters using access key authentication for each node.
    • Cluster nodes can have multiple access keys.
    • Console reports now support reporting on and filtering reports by cluster node access keys.
    Note: Console does not currently support using managed clusters as endpoints for simple and smart transfers.
  • Managed Nodes
    • Admins are no longer required to provide SSH credentials when adding managed nodes. Admins must still provide SSH credentials if they want to configure the node through Console.
  • System
    • (Linux) OpenSSL has been upgraded to version 1.0.1j.
      Note: Console 3.1.0 for Windows does not include the latest OpenSSL 1.0.1u update. Aspera will release a new package with the update next month.


AC-102 - Console basic reports suffer performance issues due to MySQL misoptimizes query.


Windows:  2008r2, 2012

Linux 64-bit:  RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.16

Browsers:  Internet Explorer 8-11, Firefox 27-45, Safari 6-9, Google Chrome 32-48


Linux 64-bit (rpm): aspera-console-
md5: d235771fa8b0e1ce37d1578ada925fc7
sha1: 6dbd9c1f1178c836d113e4cc2968085474c3eed0
Windows: AsperaConsole-
md5: 2fffb2714f707c20d46734de5c6594f8
sha1: 7c838424efb6d320968312e9c7587998bc2bd5e4


Note: This release contains tickets created from different tracking systems. For this reason, the ticket IDs may reflect different numbering formats.

NODE-137 - The Node API reports an incorrect count of failed files.

NODE-133 - The Node API reports the incorrect completion time for a transfer.

NODE-123 - If a transfer is canceled or it errors out, and it is retried before Console has a chance to poll the node, Console fails to mark the file as errored and instead adds a new file record when resuming the transfer. Both the original and new record appear in the Session Files table on the Session Details page, but the original record remains a normal, green bar and is never updated.

ES-53 - Cluster to cluster transfers are not supported.

#31098 - (Linux Only) Upgrading the common components from version 1.2.9 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Console or Orchestrator after upgrading the common components will recreate the missing link during the installation process.

#27236 - Console generates reports of the type XLSX (rather than XLS). Any reports completed before upgrading from a version of Console prior to 2.5 are no longer accessible through the web link. However, any reports that were not completed before the upgrade (such as scheduled reports) are unaffected: a report configured to generate XLS generates XLSX when it next runs. Workaround: Click Rerun on a completed report.

#22396 - If upgrading from a version of Console prior to 2.0.1, email notifications are configured for specific transfer paths on a user’s Preferences > Email Notifications page, these settings are not honored when the user clicks the Rerun link on the Activity page on a transfer that started before the upgraded.

#22303 - If upgrading from a version of Console prior to 2.0.1, scheduled smart transfers that were created before upgrading continue to use the old behavior, displaying dates/times using the timezone of the transfer requester, rather than trying to look up the recipient's time zone.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Powered by Zendesk