Adding Nodes

Transfer servers must be configured as nodes before they can be added to IBM Aspera Shares. For more information, see Configuring Nodes for Use with Shares. When adding a node, have the following information available:
Note: You can add one machine as a node multiple times to create nodes with different access credentials to different areas of the system defined by the node users' docroot settings.
  1. From the Shares home page, click the button next to Nodes.


  2. Complete the New Node configuration form.


    Field Description
    Name A description of the node.
    Host Hostname or IP address: The node's hostname or IP address. For remote nodes, use the IP address or resolvable host name. For a local host (Shares and Enterprise Server are installed on the same machine), the hostname is localhost.
    Note: When adding a local node multiple times, you must ensure each node uses localhost as the host.

    Port: The node's HTTPS port (as configured in aspera.conf). The port field represents the port on which the node service is running. The default is 9092.

    Path: The path field is an advanced feature used for URL Proxy operations. In nearly all cases, you may leave this field blank.

    API Username The node API username associated with the transfer user on the node machine.
    API Password The node API password associated with the transfer user on the node machine.
    Use SSL Shares requires SSL to be enabled, so this must be selected. Nodes may use an Aspera pre-installed and self-signed certificate (/opt/aspera/etc/aspera_server_cert.pem), or your own certificate. To generate a new certificate, see IBM Aspera Enterprise Server Admin Guide: Installing SSL Certificates.
    Note: After generating a new certificate, you must create a cert.pem file that contains the private key and the certificate. To do so, copy and paste the entire body of the key and cert files into a single text file. Then save the file as filename_cert.pem.
    Verify SSL Certificate

    To verify the SSL certificate, select this checkbox.

    If the node's SSL certificate is not recognized by the Certifcate Authority (CA), Shares displays the following error message at the top of the page when you try to add the node: "Status: Not pingable. Internal error. (Error-35)".

    If the node is using the default self-signed SSL certificate provided by Aspera, the certificate is not recognized by any CA. You must clear the Verify SSL Certificate option.

    Timeout Sets the number of seconds Shares will wait for this node to respond to a request.
    Open Timeout Sets the number of seconds Shares will wait for the connection to this node to open.
    Bytes free - warn Issues a warning message when the node has equal to or less than a specified number of storage bytes free. You can enter the number as G, MB, terrabytes, and bytes.
    Percent free - warn Issues a warning message when the node has equal to or less than a specified percent of its storage free.
    Bytes free - error Issues an error message when the node has equal to or less than a specified number of storage bytes free. You can input the number as G, MB, terrabytes, and bytes.
    Percent free - error Issues an error message when the node has equal to or less than a specified percent of its storage free.
  3. Click Create Node to create the node.
    After the node is created, Shares redircts you to the node Detail page. A status message at the top of the page reads, "Stats collector issue. Node disabled. Configuration changes have not had time to propagate to the stats collector or node configuration incorrect." This is normal and indicates that the Shares server dateabase has not yet been updated.

    The node now appears on your Home page under Nodes

    .