Configuring FASP
FASP configuration settings are not added to the Connect:Direct configuration files during
install. To enable IBM Aspera High-Speed Add-on for Connect:Direct, you must manually configure the
initparm.cfg and netmap.cfg files to run FASP.
-
Do one of the following steps:
- If you installed Connect:Direct® for UNIX V4.2.0.4 as a new installation (you did not upgrade from a previous version), go to Step 2. The initparm.cfg file is already configured for FASP listen ports.
- If you upgraded from a previous version of Connect:Direct for UNIX to V4.2.0.4, you must configure the initparm.cfg file by specifying a FASP listen port or port ranges.
Format is
listen.ports=(nnnnn, nnnnn-nnnnn)
.Example:# FASP listen ports fasp:\ :listen.ports=(44001, 33002-33005):
Note: The number of concurrent FASP processes is limited to the number of ports designated in this file. If you attempt to use more concurrent FASP processes than there are ports available fails, FASP fails. -
Configure the netmap.cfg file by specifying FASP values for the local node record. Use the
following chart.
Example:
local.node:\
… :fasp=yes:\ :fasp.policy=fair:\ :fasp.bandwidth=500MB:\ :fasp.filesize.threshold=2GB:\Parameter Value fasp Optional. Default is no if the parameter is not present. Enables FASP. - If set to no, FASP is disabled.
- If set to yes, yes, FASP is enabled. This sets the default for all Connect:Direct file transfers. fasp=(pnode value, snode value), for example, fasp=(yes, ssp)
- This setting can be overridden by the remote node record or process parameters.
- The remote server must have FASP enabled.
fasp.filesize.threshhold 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.
fasp.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.
fasp.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.
-
(Optional) Configure the netmap.cfg file by specifying FASP values for the remote node record.
Use 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.
Example:
myRmtNodePartner:\
… :fasp=yes:\ :fasp.policy=fair:\ :fasp.bandwidth=1GB:\ :fasp.filesize.threshold=1GB:\Parameter Value fasp Optional. Valid values are yes and no. Enables FASP. - If set to no, files sent to this remote node will not use FASP.
- If set to yes, files sent to this remote node will default to use FASP instead of TCP/IP.
- This setting can be overridden by the process parameters.
- The remote server must have FASP enabled.
fasp.filesize.threshhold 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.
fasp.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.
fasp.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.