Release Notes: IBM Aspera On Demand 3.6.0 Release Notes
Release Notes: IBM Aspera On Demand 3.6.0

Release Notes: IBM Aspera On Demand 3.6.0

  • Product Release: June 7, 2017
  • Release Notes Updated: October 3, 2017

WHAT'S NEW

This release of IBM Aspera On Demand provides the following new features:

  • Automatic adaptive and dynamic determination of proper cloud storage part size to allow arbitrarily large files without special configuration.
  • Preservation of file creation and modification times on uploads to cloud storage.
  • New Clustered Transfer Capability: New asperanoded command line and API to invoke transfersthat use all nodes in a cluster (static or autoscale) for 10 Gbps scale out of transfer speed.
  • New Autoscale Cluster Manager: The new Autoscale capability in Enterprise Server 3.6 allows Aspera transfer nodes to self-scale in today's dynamic cloud environments. The core capabilities are an autoscale cluster manager service for elastic auto scaling of transfer hosts and client load balancing and automatic cluster configuration, the new node/v4 multi-tenant secure access key system, and a new cluster management UI for managing policies and reporting on transfers across the cluster. See the Autoscale Cluster Manager.
  • (AWS Only) FCP FOD, FOD 20 MBPS, and FOD-100 MBPS root partitions have been increased to 800 GB.
  • Support for IBM Aspera Enterprise Server 3.6.0.
  • Support for IBM Aspera Connect Browser Plug-In 3.6.1.

AWS Image Requirements

At this time, On Demand only supports 'EBS-only' instance types, which include: c4, g3, m4, p2, r4, and t2. Aspera highly recomends using the c4 and m4 types, which are the only instances with enhanced networking enabled. If you need to use instance types with instance-store devices, you must delete ephemeral devices first, before creating the new instances.

Application Platform On Demand (APOD) / Server On Demand (SOD)

New Features

  • Aspera AWS AMIs now support enhanced networking if created with the following AWS instances: C3 C4 D2 I2 M4 R3.
IBM Aspera Enterprise Server product version updated to 3.6.0 with the following new features:
  • Aspera introduces access key authentication for Ascp and Async. Access keys provide an alternative to the security credentials of a node user or system user. Because an access key is restricted to its own storage (local or cloud), it allows access control and usage reporting to be segregated by storage. This offers significant benefits to multi-tenant service providers and enterprise installations with multiple departments. Access key authentication supports Aspera client products, such as Desktop Client, Point-to-Point Client, Enterprise Server, Connect, and Drive. It also supports Faspex, Shares, and Aspera Files. For details, see your product documentation for these products.
  • A new watchfolder feature automates file transfers from a source to a destination system. Files placed into a designated source folder are automatically transferred to the destination. Watchfolder transfers are run from the source machine only and do not require any additional software on the destination system.
  • Server-side encryption-at-rest (EAR): EAR encryption and decryption can now be done from the server. The passphrase is set in aspera.conf. Client-side EAR is still available as before.
  • File links are now supported for cloud storage. The "links" are small text files have the following naming convention:
    .name.asp-trapd-lnk
    Limitations: The current implementation (of uploads) does not check whether a file with a -lnk name already exists at the destination, and pvcl_trap does not handle the symlink type, hence the "symbolic link" symbol is not displayed in the UI.
  • License support is now available for multiple entitlements per computer.
  • Added support for storage to blob pages in Azure.Docroots can now be configured using $(home) for a user's home directory. This is also supported by asconfigurator.
Note: For the full release notes, see IBM Aspera Enterprise Server 3.6.0 Release Notes.
IBM Aspera Shares product version updated to 1.9.3 with the following new features:
  • IBM Aspera Connect Browser Plug-In: Shares 1.9.3 requires Connect 3.6.1. You are required to install or upgrade to Connect 3.6.1 for all browsers.
  • SAML: Shares now supports OAuth 2 tokens with SAML API requests.
  • SAML: You can now configure the fingerprint algorithm for the SAML Identity Provider Configuration page (Admin > Accounts > Directories and click Edit for SAML Identity Provider).
  • SAML: Improved SAML functionality for logging in with usernames containing special characters.
  • SAML: SAML users are now affected by session timeouts configured in Shares.
  • Home Shares: Admins can disable home shares for individual users.
  • Email Templates: The Transfer Completed email template now supports the share_path and node_path variables to list the full path of the destination directory relative to share or node docroots.
  • Rake Tasks: Improved performance for certain rake tasks.
  • Rake Tasks: New rake tasks to fetch LDAP user and group data. UI: The total count of entries (files and folders) is displayed when browsing the current directory in a share.
  • Nginx: Updated Nginx for better SSL support. Nginx: Nginx now supports IPv6. You can access the Shares server by entering an IPv6 address in a browser.
  • Security: Upgrades to Ruby 2.0.0, Java 8, and OpenSSL 1.0.1p.
Note: For the full release notes, see IBM Aspera Shares 1.9.3 Release Notes.
Known Issues

#33734 - Accessing https://shares_hostname/node_api/ping should not require authentication.

#29891 - Sometimes restoring Console's configuration file deletes the home folder of users in aspusers group, except aspadmin. Workaround: Before restoring your configuration file, follow the steps in this article: https://support.asperasoft.com/entries/90334347.

#29858 - Sometimes Console's database is left empty after restoring a configuration file and users not allowed to log back into Console. Workaround: Before restoring your configuration file, follow the steps in this article: https://support.asperasoft.com/entries/90334347.

#29649 - Restoring one SHOD Shares instance's database onto another SHOD Shares instance causes instance to not be browsable, with perpetual license error. Workaround: Use Rake task to disable and re-enable entitlement mode for the Shares application: https://support.asperasoft.com/entries/76203557-Web-application-entitlement-feature.

IBM Aspera Shares On Demand (SHOD)

New Features

IBM Aspera Shares product version updated to 1.9.3 with the following new features:
  • IBM Aspera Connect Browser Plug-In: Shares 1.9.3 requires Connect 3.6.1. You are required to install or upgrade to Connect 3.6.1 for all browsers.
  • SAML: Shares now supports OAuth 2 tokens with SAML API requests.
  • SAML: You can now configure the fingerprint algorithm for the SAML Identity Provider Configuration page (Admin > Accounts > Directories and click Edit for SAML Identity Provider).
  • SAML: Improved SAML functionality for logging in with usernames containing special characters.
  • SAML: SAML users are now affected by session timeouts configured in Shares.
  • Home Shares: Admins can disable home shares for individual users.
  • Email Templates: The Transfer Completed email template now supports the share_path and node_path variables to list the full path of the destination directory relative to share or node docroots.
  • Rake Tasks: Improved performance for certain rake tasks.
  • Rake Tasks: New rake tasks to fetch LDAP user and group data. UI: The total count of entries (files and folders) is displayed when browsing the current directory in a share.
  • Nginx: Updated Nginx for better SSL support. Nginx: Nginx now supports IPv6. You can access the Shares server by entering an IPv6 address in a browser.
  • Security: Upgrades to Ruby 2.0.0, Java 8, and OpenSSL 1.0.1p.
Note: For the full release notes, see IBM Aspera Shares 1.9.3 Release Notes.
Known Issues

#33734 - Accessing https://shares_hostname/node_api/ping should not require authentication.

#29891 - Sometimes restoring Console's configuration file deletes the home folder of users in aspusers group, except aspadmin. Workaround: Before restoring your configuration file, follow the steps in this article: https://support.asperasoft.com/entries/90334347.

#29858 - Sometimes Console's database is left empty after restoring a configuration file and users not allowed to log back into Console. Workaround: Before restoring your configuration file, follow the steps in this article: https://support.asperasoft.com/entries/90334347.

#29651 - On AWS Console, simple/smart transfers with a SOFTLAYER node as the source will fail. The reverse also fails: on SOFTLAYER Console, simple/smart transfers with an AWS node as the source will fail.

#29649 - Restoring one SHOD Shares instance's database onto another SHOD Shares instance causes instance to not be browsable, with perpetual license error. Workaround: Use Rake task to disable and re-enable entitlement mode for the Shares application: https://support.asperasoft.com/entries/76203557-Web-application-entitlement-feature.

IBM Aspera Faspex Application On Demand (FOD)

IBM Aspera Faspex product version updated to 3.9.3 with the following new features:

  • IBM Aspera Connect Browser Plug-In: Faspex 3.9.3 requires Connect 3.6.1. You are required to install or upgrade to Connect 3.6.1 for all browsers.
  • Drag-and-Drop for Google Chrome: The drag-and-drop functionality on the New Package page is now supported in Chrome. Users must use Connect version 3.6.1 or higher to use drag-and-drop in Chrome.
  • Direct Upload to Custom Inbox: For dropboxes, there is now an option to upload packages directly to a custom inbox without going to the default inbox first.
  • Cloud Referencing: When the source and destination of a package are in the same cloud storage, package files will link to the source files instead of making copies of the source files. This feature supports any cloud service that supports trap links.Note: The cloud referencing feature requires cloud storages that use IBM Aspera Enterprise Server 3.6.0+ to work.
  • Rake Tasks: The rake packages:clean_deleted command now cleans deleted packages in batches, instead of as a single query.
  • Security: Aspera common components (including OpenSSL and Apache) are now updated to increase security and protect against the logjam threat.
Note: For the full release notes, see the IBM Aspera Faspex 3.9.3 Release Notes.

Known Issues

#29653 - Restoring configuration to a FOD instance replaces the apache hostname with the backup FOD's hostname. Workaround: Reset the Apache hostname to that of the current FOD using the command: asctl apache:hostname <current FOD IP address>.

#29652 - Backing up and restoring Faspex on a SoftLayer FOD changes the server's name from its real IP to "localhost". (Observed by navigating to Server > Configuration > Web Server)

IBM Aspera Console On Demand (COD)

New Features

IBM Aspera Console product version updated to 3.0.3 with a new internal architecture and many new features.

The new architecture queries data from managed nodes using the Aspera Node API, rather than pushing data to the Console via the Aspera Central service. This new architecture has many advantages for scalability and robustness. Important details include the following:

  • Managed nodes added to a Console version prior to 3.0 still continue to use this legacy method with the database logger to report to Console 3.0, and they are annotated as “Legacy Nodes” in the nodes list.
  • These existing managed nodes running version 3.4.6 or higher of Enterprise Server or Point-to-Point can be converted to use the new Aspera Node API with the Convert to use Node API option in the Node edit screens. If converted, these nodes will be queried by Console using the new Node API method.
  • This means you will want to upgrade your nodes to at least version 3.4.6 and ideally to version 3.6.0 in order to take advantage of the scalability this new Console architecture offers.
For more information on the architecture change and relevant new features list, see IBM Aspera Console 3.0.1 Release Notes.
  • Watchfolders: A watchfolder is an automation of file transfers from a source to a destination system. Files placed into a source folder are automatically transferred to the destination. It runs on the client side only and does not require any additional software on the destination system. Adding a watchfolder-enabled node and the watchfolder instance to Console enables Console to monitor and report transfers initiated by the service.
    Note: Watchfolder requires Enterprise Server 3.6.0+ with a watchfolder-enabled license. To enable watchfolder functionality in Console 3.0.3 for APOD/SOD, APOD/SOD-WS, or SHOD contact Aspera for watchfolder-enabled entitlement keys.
  • Transfers: Console now allows configuration per node of the file suffix for partially downloaded files. The current default suffix is .aspx, but this can be changed by going toNodes, editing the desired node, and going to Configuration > Advanced File Handling.
  • Graph: If enabled, Console tracks the total bandwidth usage across all nodes on the Dashboard graph. Enable by going to Configuration > Defaults.
  • License: Console now stores license information in the database, rather than in a file located at /opt/aspera/console/config/ (Linux) and C:\Program File (x86)\Aspera\Management Console\config (Windows). If a license is added to the directory before the upgrade script is run, the script migrates the license information from the file into the database and deletes the file.
  • Reports: Time information ("Actual start", "Finished", and "Total run time") now display at the bottom of the report screen.
  • Security: Upgrades to Ruby 2.0.0, Java 8, and OpenSSL 1.0.1p.

AMAZON MACHINE IMAGE (AMI) INFORMATION

Aspera Platform On Demand / Server On Demand (APOD / SOD)
Region Registered AMI
us-west-2 ami-ac7e60d5
ap-northeast-1 ami-ddb5b0b3
ap-northeast-2 ami-8ff638e1
ap-south-1 ami-45d1a62a
ap-southeast-1 ami-56c40a35
ap-southeast-2 ami-a77d5ac4
ca-central-1 ami-3fd46b5b
eu-central-1 ami-49706b25
eu-west-1 ami-4104b532
eu-west-2 ami-c06473a4
sa-east-1 ami-36d3505a
us-east-1 ami-1c8ca476
us-east-2 ami-56fadf33
us-west-1 ami-45b3c525
Aspera Platform On Demand / Server On Demand without Console (APOD / SOD WOC)
Region Registered AMIc
us-west-2 ami-52b65632
ap-northeast-1 ami-40787f2e
ap-northeast-2 ami-de01cfb0
ap-south-1 ami-bbdfa8d4
ap-southeast-1 ami-1f2fe17c
ap-southeast-2 ami-1c1f387f
ca-central-1 ami-bcd46bd8
eu-central-1 ami-c5ced5a9
eu-west-1 ami-fdfc4f8e
sa-east-1 ami-df8d0eb3
us-east-1 ami-153f0a7f
us-west-1 ami-75ea9c15
Aspera Platform On Demand / Server On Demand with Shares (APOD / SOD WS)
Region Registered AMI
us-west-2 ami-d58263b5
ap-northeast-1 ami-6fabae01
ap-northeast-2 ami-a7f03ec9
ap-south-1 ami-46d1a629
ap-southeast-1 ami-98c907fb
ap-southeast-2 ami-b87c5bdb
ca-central-1 ami-4cd66928
eu-central-1 ami-15736879
eu-west-1 ami-9b05b4e8
sa-east-1 ami-d2cc4fbe
us-east-1 ami-b081a9da
us-west-1 ami-52b0c632
Faspex On Demand (FOD)
Region Registered AMI
us-west-2 ami-24846544
ap-northeast-1 ami-2cb5b042
ap-northeast-2 ami-79f43a17
ap-south-1 ami-c2a2dfad
ap-southeast-1 ami-57c40a34
ap-southeast-2 ami-fd7d5a9e
ca-central-1 ami-edd56a89
eu-central-1 ami-5b716a37
eu-west-1 ami-d803b2ab
sa-east-1 ami-4fcc4f23
us-east-1 ami-508fa73a
us-west-1 ami-c2b0c6a2
Faspex On Demand 20Mbps for Marketplace (FOD 20MBPS)
Region Registered AMI
us-west-2 ami-51977431
ap-northeast-1 ami-03efee6d
ap-northeast-2 ami-5a28e634
ap-south-1 ami-f49ce19b
ap-southeast-1 ami-9db871fe
ap-southeast-2 ami-e06b4d83
ca-central-1 ami-fdd76899
eu-central-1 ami-14170d78
eu-west-1 ami-d101b3a2
sa-east-1 ami-1a1a9976
us-east-1 ami-9c1726f6
us-west-1 ami-da96e7ba
Faspex On Demand 100Mbps for Marketplace (FOD 100MBPS)
Region Registered AMI
us-west-2 ami-b79370d7
ap-northeast-1 ami-8ff0f1e1
ap-northeast-2 ami-922de3fc
ap-south-1 ami-f89de097
ap-southeast-1 ami-4bbc7528
ap-southeast-2 ami-976046f4
ca-central-1 ami-bad966de
eu-central-1 ami-45160c29
eu-west-1 ami-c1ff42b2
sa-east-1 ami-11189b7d
us-east-1 ami-e11b2a8b
us-west-1 ami-e99bea89
Faspex On Demand FCP
Region Registered AMI
us-east-1 ami-f9a09893
Shares On Demand (SHOD)
Region Registered AMI
us-west-2 ami-71856411
ap-northeast-1 ami-d8b5b0b6
ap-northeast-2 ami-f2f6389c
ap-south-1 ami-5e9de031
ap-southeast-1 ami-dac40ab9
ap-southeast-2 ami-357c5b56
ca-central-1 ami-bbd966df
eu-central-1 ami-4c706b20
eu-west-1 ami-ab07b6d8
sa-east-1 ami-37d3505b
us-east-1 ami-3a81a950
us-west-1 ami-dfb3c5bf

SOFTLAYER IMAGE INFORMATION

Product Image ID
Aspera Platform On Demand / Server On Demand (APOD / SOD) APOD-SOD 3.6.0 - February 2016 Release
Aspera Platform On Demand / Server On Demand without Console (APOD / SOD WOC) APOD-SOD-WOC 3.6.0 - February 2016 Release
Aspera Platform On Demand / Server On Demand with Shares (APOD / SOD WS) APOD-SOD-WS 3.6.0 - February 2016 Release
Faspex On Demand (FOD) FOD 3.6.0 - February 2016 Release
Faspex On Demand 20Mbps for Marketplace (FOD 20MBPS) FOD-20MBPS 3.6.0 - February 2016 Release
Faspex On Demand 100Mbps for Marketplace (FOD 100MBPS) FOD-100MBPS 3.6.0 - February 2016 Release
Shares On Demand (SHOD) SHOD 3.6.0 - February 2016 Release

SOFTWARE COMPONENTS

Application Platform On Demand / Server On Demand (APOD / SOD)

  • IBM Aspera Enterprise Server 3.6.0
  • IBM Aspera Console 3.0.3
Shares On Demand (SHOD)
  • IBM Aspera Shares 1.9.3
  • IBM Aspera Enterprise Server 3.6.0
  • IBM Aspera Console 3.0.3
Faspex On Demand (FOD)
  • IBM Aspera Faspex 3.9.3
  • IBM Aspera Enterprise Server 3.6.0
Console On Demand (COD)
  • IBM Aspera Enterprise Server 3.6.0
  • IBM Aspera Console 3.0.3

AMI PACKAGE INFORMATION

APOD / SOD

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

APOD / SOD w/o Console

aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-woc-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

APOD / SOD w/ Shares

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-ws-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

FOD

aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

FOD 20Mbps for Marketplace

"aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-20mbps-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

FOD 100Mbps for Marketplace

aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-100mbps-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

FCP-FOD

aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119431-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fcp-fod-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-100mbps-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

SHOD

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-shod-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

SOFTLAYER PACKAGE INFORMATION

APOD / SOD

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

APOD / SOD w/o Console

aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-woc-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

APOD / SOD w/ Shares

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-apod-sod-ws-3.6.0-119289.noarch.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

FOD

aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

FOD 20Mbps for Marketplace

"aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-20mbps-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

FOD 100Mbps for Marketplace

aspera-common-1.1.22.117256-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-faspex-3.9.3.110840-0.x86_64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-fod-100mbps-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm

SHOD

aspera-common-1.2.15.115916-0.x86_64.rpm
aspera-console-3.0.5.119278-0.x86_64.rpm
aspera-entsrv-3.6.0.119278-linux-64.rpm
aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
aspera-ondemand-init-shod-3.6.0-119289.noarch.rpm
aspera-ondemand-tools-3.6.0-119289.noarch.rpm
aspera-shares-1.9.3.118993-1.x86_64.rpm

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.