Overview: Remote Nodes
Importance of Creating Remote Nodes
A remote node consists of the information needed to connect from a FASP Session, ASCMD, SSH, or TCP to a remote server. All plugins provide a dropdown arrow option to select a remote node for their plugin operations.
Without a remote node, you must input an IP address or host names, user ID, and password at multiple places in your workflows. If this information changes, your must change the information in multiple places. If you use a remote node and populate the information there instead, the only place the information changes in that node.
Types of Remote Nodes:
There are four types of remote nodes. The table below describes the circumstances under which
each type should be used.
| Node type | Conditions for use |
|---|---|
| Aspera FASP |
The remote node has one of the following installed:
|
| SSH | The remote node accepts SSH connections. Note: Unix (*nix) machines accept SSH
connections by default on Windows machines, usually when software like Open SSH is
installed.
|
| IP | The remote node does not have the characteristics of either an Aspera FASP node or an SSH node (for example, a transcoding server or a quality check server). |
| Aspera Orchestrator | The remote node is also an Orchestrator server. |