Release Notes: IBM Aspera Transfer Cluster Manager 1.2.5 for AWS and IBM Cloud
Release Notes: IBM Aspera Transfer Cluster Manager 1.2.5 for AWS and IBM Cloud

Release Notes: IBM Aspera Transfer Cluster Manager 1.2.5 for AWS and IBM Cloud

Product Release: April 5, 2018
Release Notes Updated: April 18, 2018

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

NEW FEATURES

Cluster manager and cluster node images are upgraded to IBM Aspera Enterprise Server 3.8.1, which improves performance and security, including remediation for the Spectre and Meltdown security vulnerabilities.

Cluster Manager

Improved health-status reporting for ScaleKV activity.

Cluster Nodes

Cluster templates are now set by default to have ATC Manager and cluster nodes communicate over private networks.

ISSUES FIXED IN THIS RELEASE

ATC-433 - [EC2] The DNS templates include an extra line that causes the hosted zone and hosted zone ID to not populate when launching a cluster.

ATC-293 - Transfers intiated using the Aspera RPC-style API fail.

AMAZON MACHINE IMAGE (AMI) INFORMATION

Cluster Manager Image

Name: atc-manager-1.2.5.7022b7-20180323T185305Z-507

Region Registered Image
us-east-1 ami-425f8f3f
us-west-1 ami-45746225
us-west-2 ami-8aed73f2
ap-south-1 ami-516c373e
ap-northeast-1 ami-a7ecbfc1
ap-northeast-2 ami-a6ef40c8
ap-southeast-1 ami-03e3bf7f
ap-southeast-2 ami-fe428f9c
eu-central-1 ami-4f6a39a4
eu-west-1 ami-39431540
sa-east-1 ami-02b7e36e
Transfer Node Image

Name: atc-node-1.2.5.7022b7-es3.8.1.155196-20180323T191255Z-507

Region Registered Image
us-east-1 ami-c47babb9
us-west-1 ami-e9706689
us-west-2 ami-729e000a
ap-south-1 ami-59603b36
ap-northeast-1 ami-503b6936
ap-northeast-2 ami-5aed4234
ap-southeast-1 ami-d4104fa8
ap-southeast-2 ami-a15c91c3
eu-central-1 ami-f992c112
eu-west-1 ami-f0702689
sa-east-1 ami-2fb1e543

IBM CLOUD (SOFTLAYER) MACHINE IMAGE INFORMATION

Cluster Manager Image

Name: atc-manager-1.2.5.7022b7-20180323T185305Z-507

Data Center Registered Image
ams01, ams03, che01, dal01, dal05, dal06, dal09, dal10, dal12, dal13, fra02, hkg02, hou02, lon02, lon04, lon06, mel01, mex01, mil01, mon01, osl01, par01, sao01, sea01, seo01, sjc01, sjc03, sjc04,sng01, syd01, syd04, tok02, tor01, wdc01, wdc04, wdc06, wdc07 1284cdf9-8287-4382-ae88-d3ef8106dd9f

Transfer Node Image

Name: atc-node-1.2.5.7022b7-es3.8.1.155196-20180323T191255Z-507

Data Center Registered Image
ams01, ams03, che01, dal01, dal05, dal06, dal09, dal10, dal12, dal13, fra02, hkg02, hou02, lon02, lon04, lon06, mel01, mex01, mil01, mon01, osl01, par01, sao01, sea01, seo01, sjc01, sjc03, sjc04, sng01, syd01, syd04, tok02, tor01, wdc01, wdc04, wdc06, wdc07 54920a9f-3f77-4cb2-a10a-60c6211b18f6

PACKAGE INFORMATION

Cluster Manager
aspera-atcm-1.2.5.7022b7.100-linux-64.tar.gz
clusterconsole.2.20180206112920.9e96063.tar.gz
clusterconsole-ui.7.20180219040613.ec6bbcd.tar.gz
aspera-entsrv-3.8.1.155196-linux-64-release.rpm
aspera-stats-collector-2.0.0.154757-linux-64.tar.gz
aspera-ruby-rbenv-centos-7.rpm
aspera-ruby-2.2.4-centos-7-x86_64.rpm

Transfer Nodes
aspera-entsrv-3.8.1.155196-linux-64-release.rpm
aspera-atcm-1.2.5.7022b7.100-linux-64.tar.gz

KNOWN ISSUES

ATC-327 - [AWS] Route 53 DNS updates fail intermittently with the error, "com.amazonaws.services.route53.model.InvalidInputException".

ATC-322 - Syncing Console 3.2.0 access keys from the ATC Manager UI deletes sub-access keys. (CIM-543)

ATC-320 - Trapd can take up to 5 minutes to timeout when attempting to browse an unreachable IP address.

ATC-292 - ATC Manager does not support multiple ascp sessions that upload the same files to the same destination.

ATC-207 - The ATC Manager UI displays a maximum of ten access keys in the access keys table and in the transfer statistics drop-down menu.

PRODUCT SUPPORT

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.