Configuring FASP

To enable IBM Aspera High-Speed Add-on for Connect:Direct® for Microsoft Windows, you must update the local node (initialization parameters) with FASP parameters.
  1. From the Admin Tool initialization parameters, click the TCP/IP tab.
  2. In the Configure FASP section, click Properties.
  3. Configure the values for the Local Node by completing the following fields:
    Field Value
    FASP Listen Ports Type the port numbers you want to use for FASP. Only valid for SNode configuration.
    PNode FASP Flag Use when this is PNode. Valid values are:
    • If set to Yes, use FASP on PNode
    • If set to No, don't use FASP
    • If set to SSP , use FASP with SSP bridging
    • If set to Blank, use the default value of No.
    SNode FASP Flag Use when this is SNode. Valid values are:
    • If set to Yes, use FASP on SNode
    • If set to No, don't use FASP
    • If set to SSP , use FASP with SSP bridging
    • If set to Blank, use the default value of No.
    File Size Threshold Optional. Used to restrict small files from being sent using FASP.
    • If the file is greater than or equal to the stated value, the Connect:Direct server sends the file using FASP. Otherwise, it is sent using TCP/IP.
    • Default is 1GB.
    • You can use KB, MB, or GB designators. If no designator is included, the system uses bits.
    • This setting can be overridden by the remote node record or process parameters.
    Target Bandwidth Optional. Default is as stipulated in the FASP license key. Specifies how much bandwidth each transfer can use.
    • Default value can be changed, but cannot exceed the bandwidth specified in the license key.
    • You can use KB, MB, or GB designators. If no designator is included, the system uses bits per second.
    • This setting can be overridden by the remote node record or process parameters, but cannot exceed the bandwidth specified in the license key.
    Policy Optional. Specifies the fairness of each transfer. Default is fair.
    • This setting can be overridden by the remote node record or process parameters.
    • Valid values are:
      • Fixed - FASP attempts to transfer at the specified target rate, regardless of the actual network capacity. This policy transfers at a constant rate and finishes in a guaranteed amount of time. This policy typically occupies a majority of the network's bandwidth, and is not recommended in most file transfer scenarios.
      • Fair - FASP monitors the network and adjusts the transfer rate to fully utilize the available bandwidth up to the maximum rate. When other types of traffic build up and congestion occurs, FASP shares bandwidth with other traffic fairly by transferring at an even rate. This is the best option for most file transfer scenarios.
      • High - FASP monitors the network and adjusts the transfer rate to fully utilize the available bandwidth up to the maximum rate. When congestion occurs, a FASP session with high policy transfers at a rate twice of a session with fair policy.
      • Low - Similar to Fair mode, the Low (or Trickle) policy uses the available bandwidth up to the maximum rate as set in the Aspera license file. When congestion occurs, the transfer rate is decreased all the way down to the minimum rate as set in the Aspera license file.
  4. (Optional) Using Connect:Direct Requester, select Netmap and specify the values for the remote node using the following chart. Configure the remote node if you need to override your local node settings. For example, if you want to exclude a trading partner from using FASP. You can also configure the remote node record later.
    Field Value
    Pnode FASP flag Use when this is PNode. Valid values are:
    • If set to Yes, use FASP on PNode
    • If set to No, don't use FASP
    • If set to SSP , use FASP with SSP bridging
    • If set to Blank, use the default value of No.
    SNode FASP Flag Use when this is SNode. Valid values are:
    • If set to Yes, use FASP on SNode
    • If set to No, don't use FASP
    • If set to SSP , use FASP with SSP bridging
    • If set to Blank, use the default value of No.
    File Size Threshold Optional. Used to restrict small files from being sent using FASP.
    • If the file is greater than or equal to the stated value, the Connect:Direct server sends the file using FASP. Otherwise, it is sent using TCP/IP.
    • Default is 1GB.
    • You can use KB, MB, or GB designators. If no designator is included, the system uses bits.
    • This setting can be overridden by the process parameters.
    Target Bandwidth Optional. Default is as stipulated in the FASP license key. Specifies how much bandwidth each transfer can use.
    • Default value can be changed, but cannot exceed the bandwidth specified in the license key.
    • You can use KB, MB, or GB designators. If no designator is included, the system uses bits per second.
    • This setting can be overridden by the process parameters, but cannot exceed the bandwidth specified in the license key.
    Policy Optional. Specifies the fairness of each transfer. Default is fair.
    • This setting can be overridden by the process parameters.
    • Valid values are:
      • Fixed - FASP attempts to transfer at the specified target rate, regardless of the actual network capacity. This policy transfers at a constant rate and finishes in a guaranteed amount of time. This policy typically occupies a majority of the network's bandwidth, and is not recommended in most file transfer scenarios.
      • Fair - FASP monitors the network and adjusts the transfer rate to fully utilize the available bandwidth up to the maximum rate. When other types of traffic build up and congestion occurs, FASP shares bandwidth with other traffic fairly by transferring at an even rate. This is the best option for most file transfer scenarios.
      • High - FASP monitors the network and adjusts the transfer rate to fully utilize the available bandwidth up to the maximum rate. When congestion occurs, a FASP session with high policy transfers at a rate twice of a session with fair policy.
      • Low - Similar to Fair mode, the Low (or Trickle) policy uses the available bandwidth up to the maximum rate as set in the Aspera license file. When congestion occurs, the transfer rate is decreased all the way down to the minimum rate as set in the Aspera license file.