Node-to-node transfer issues

Edit online

A node-to-node transfer (also called a share-to-share transfer) moves files from one transfer node or cloud storage location to another, as opposed to a transfer between a user desktop and a transfer node.

This is as opposed to uploading files from a user desktop or remote storage to a transfer node or cloud storage (or downloading files from the cloud to a user desktop or remote storage).

Folders in a user's Files app may be in any number of storage locations, including in different buckets or different cloud providers. When a user moves files from one folder in the Files app to another, a node-to-node transfer occurs.

Likewise, in the Packages app, sending a digital package that includes files or folders from the Files app ("Upload from Files" in the Send files panel) also results in a node-to-node transfer. And if a digital package includes files or folders already in cloud storage along with files and folders from the user desktop or remote storage, the AoC transfer monitor displays the package transfer on two separate transfer records: one transfer for the upload and a separate transfer for the node-to-node transfer.

For example, the screenshot below shows two transfer reports for a single transfer. The package contains one file ("byok_architecture copy.png") on the user's desktop and one folder ("AoC Self-Packed Onboarding") in the user's Files app.

The AoC transfer monitor showing two transfer records for the transfers associated with a single package transfer. One transfer moves a folder from one storage location to another; this is a node-to-node transfer. The other transfer is a typical file upload from the user desktop.

There may be times when the error message "Unable to start node-to-node transfer" displays.

If you are the user attempting the transfer, try the transfer again because the issue may be ephemeral.

To contact your local tech support administrator, click in the banner and select "Technical support".

If you are the local tech support administrator, do the following:
  1. The security token may have expired. Check configurations in Organization > Security. See Configuring Organization Security Settings.
  2. If the transfer is to or from a tethered node, check the transfer logs on the node; see Where are the IBM Aspera client and server logs?
  3. Work with the user to collect web browser network traces; see How to collect network traces for troubleshooting.