It is best practice to keep all your nodes up to date with the
latest version of IBM Aspera Enterprise Server, IBM Aspera Connect Server, or IBM Aspera Point-to-Point Client
To verify your node machine's product version, run the following command on your node
machine:
$ ascp -A
If you have an older version, you can download the latest from
http://asperasoft.com/downloads.
-
Go to Nodes and click New Managed
Node.
-
Enter your managed node's IP Address,
Name, SSH Port, and
Node API Port.
Important: When adding the Console server itself as a managed
node, don't enter 127.0.0.1 as the IP address unless it is the
only node you are planning to add to the console. Even then
it is not recommended. Do this only if your network or firewall
configuration interferes with Console communicating with its own
external address.
-
Select an algorithm for SSH Encryption.
-
Add the node to a failover group.
Select
Enable failover and load balancing for Console-initiated
transfers on this node. Add the node to an existing group or
select enter new name from the Failover Group Name drop-down menu to create a new
group. If you select enter new name, enter a new failover group name in the
prompt. For more information on failover groups, see
Configure Failover Groups.
- Optional:
Create the three default Console groups. Select Create default Console
groups.
The default transfer Console groups have the following permissions:
- Transfer Admin: Users in this group can manage transfers on this
node. This includes initiating, canceling, and deleting transfers.
- Transfer Initiator: Users in this group can only initiate
transfers.
- Transfer Monitor: Users in this group can only monitor
transfers.
For
more information on Console groups, see
Creating Console Groups
-
When finished, click Create.