Using High-Speed Add-on (HSAO) for Connect:Direct
IBM Aspera High-Speed Add-on for Connect:Direct® for UNIX uses FASP (Fast and Secure Protocol) network transport to transfer files over high bandwidth and high latency network connections.
At low latency it performs similarly to TCP/IP. However, as latency and packet loss increase, unlike TCP/IP, its performance does not degrade, and FASP continues to take advantage of all the available bandwidth.
IBM Aspera High-Speed Add-on for Connect:Direct for UNIX supports interoperability with Connect:Direct for Microsoft Windows and Secure Proxy. Fore more information, refer to High-Speed Add-On Getting Started Guide.
Activating FASP
By default, IBM Aspera High-Speed Add-on for Connect:Direct is not enabled. To enable it, you must download a license key and install Connect:Direct for UNIX.
About this task
Procedure
Licensed bandwidth for FASP transactions
The bandwidth available to a file transfer is limited by, among other things, the bandwidths specified in the sender’s and receiver’s Aspera license keys.
- Datacenter licenses (available in 10gbps, 1gbps, 300mbps and 100mbps) - can send and receive files using FASP when connected to a node that has an Endpoint or DataCenter license.
- Endpoint license - can send and receive files using FASP when connected to a node that has a DataCenter license.
When both sender and receiver only have Endpoint licenses, file transfer over FASP is not supported. When either the sender or receiver has an Endpoint license and the other has a Datacenter license, the available bandwidth is limited to the value in the Datacenter license. When both sender and receiver have Datacenter licenses, the bandwidth is limited to the smaller of the two values in the Datacenter licenses.
FASP Process Language
Once the FASP parameters for both trading partners have been configured, you can override the default settings on a process by process basis to perform exception processing.
Optional Parameters
- FASP (Yes | No)
- FASP POLICY (Values are the same as the FASP Local and Remote node record parameters)
- FASP.FILESIZE.THRESHOLD (Values are the same as the FASP Local and Remote node record parameters)
- FASP.BANDWIDTH (Values are the same as the FASP Local and Remote node record parameters)
- COPY statement - The four FASP parameters may be used individually or as a group within a COPY statement. This will set FASP values for the duration of that COPY statement and will not have any effect on statements within the submitted Process
- PROCESS statement - The four FASP parameters may be used individually or as a group at the end of a PROCESS statement. This will set the FASP parameters for all of the COPY statements in the process
- SUBMIT command - The four FASP parameters may be set individually or as a group at the end of a SUBMIT command. This will set the FASP parameters for all COPY statements in the process being submitted These settings will set FASP information for their relevant part of the scope, potentially overriding the Local Node settings, Remote Node settings and each other.
Examples
|
|
Hierarchy Settings
- Remote node record overrides local node record.
- Process parameters override remote node record.
- Submit statement overrides the process parameters.
- Each Copy statement overrides the effective settings of the session established by the node settings, Process or Submit statements. The Copy statement override is effective only for the duration of the Copy step.
Using FASP with IBM Aspera High-Speed Add-on and Secure Proxy
You can send files using IBM Aspera High-Speed Add-on through Secure Proxy using Connect:Direct for UNIX.
If you send a file from your local Connect:Direct for UNIX node configured for FASP, it passes through your Secure Proxy instance using FASP, and is sent to the remote node.
fasp=(yes|no|ssp,yes|no|ssp)
The first parameter is the
default for Connect:Direct as the PNODE. The second parameter is the default for Connect:Direct as
the SNODE. This parameter can now be used in the netmap local node record and remote node trading partner record in Connect:Direct for UNIX.
The following table shows results when Connect:Direct FASP protocol is used between two Connect:Direct nodes with no Sterling Secure Proxy involved.
PNODE fasp= | Protocol | SNODE fasp= |
N | TCP | N |
N | TCP | Y |
N | TCP | SSP |
Y | TCP | N |
Y | C:D FASP | Y |
Y | TCP | SSP |
SSP | TCP | N |
SSP | TCP | Y |
SSP | TCP | SSP |
The following table shows results when Connect:Direct FASP protocol is used with two Connect:Direct nodes going through a single instance of Sterling Secure Proxy.
PNODE fasp= | Protocol | SSP | Protocol | SNODE fasp= |
N | TCP | SSP | TCP | N |
N | TCP | SSP | TCP | Y |
N | TCP | SSP | TCP | SSP |
Y | TCP | SSP | TCP | N |
Y | C:D FASP | SSP | C:D FASP | Y |
Y | C:D FASP | SSP | TCP | SSP |
SSP | TCP | SSP | TCP | N |
SSP | TCP | SSP | C:D FASP | Y |
SSP | TCP | SSP | TCP | SSP |
The following table shows results when Connect:Direct FASP protocol is used with two Connect:Direct nodes going through two instances of Sterling Secure Proxy.
PNODE fasp= | Protocol | SSP | Protocol | SSP | Protocol | SNODE fasp= |
N | TCP | SSP | TCP | SSP | TCP | N |
N | TCP | SSP | TCP | SSP | TCP | Y |
N | TCP | SSP | TCP | SSP | TCP | SSP |
Y | TCP | TCP | TCP | SSP | TCP | N |
Y | C:D FASP | SSP | C:D FASP | SSP | C:D FASP | Y |
Y | C:D FASP | SSP | C:D FASP | SSP | TCP | SSP |
SSP | TCP | SSP | TCP | SSP | TCP | N |
SSP | TCP | SSP | C:D FASP | SSP | C:D FASP | Y |
SSP | TCP | SSP | C:D FASP | SSP | TCP | SSP |
For more information on using IBM® Secure Proxy with FASP, see Using FASP with Sterling Secure Proxy .
Configuring FASP
About this task
Procedure
FASP Messages
Use the following table to obtain FASP error message information.
Non-Detailed Statistics Mode (Message ID only) | Detailed Statistics Mode |
---|---|
FASP001E | FASP001E: FASP server session creation failed. |
FASP002E | FASP002E: FASP client session creation failed. |
FASP003E | FASP003E: FASP could not be initialized. |
FASP004E | FASP004E: Lock timeout. |
FASP005E | FASP005E: Memory allocation failure. |
FASP006E | FASP006E: Condition wait timed out. |
FASP007E | FASP007E: No FASP listen ports available. |
FASP008E | FASP008E: FASP disabled due to file size &FILESIZE < threshold &THRESHOLD |
FASP009E | FASP009E: FASP session terminated unexpectedly. |
FASP010E | FASP010E: SNODE refused FASP, FASP disabled. |
FASP011E | FASP011E: FASP CRC verification failed. |
FASP020E | FASP020E: Session Manager received invalid FASP control message. |
FASP021E | FASP021E: FASP control message fragmented or invalid. |
FASP022E | FASP022E: Session Manager failed to receive FASP control message. |
FASP023E | FASP023E: The FASP control message to send exceeds the buffer size. |
FASP024E | FASP024E: Session Manager failed to send FASP control message. |
FASP030E | FASP030E: FASP license file not found. |
FASP031E | FASP031E: FASP license file expired. |
FASP032E | FASP032E: FASP license in error. |
FASP033E | FASP033E: FASP license is malformed. |
FASP034E | FASP034E: FASP license is malformed. |
FASP035E | FASP035E: FASP License file at &LOCATION will expire in &VALUE day(s). |
FASP040E | FASP040E: FASP initialization failed - remote &TYPE &NODE. Error=&ERROR. |
FASP041E | FASP041E: FASP initialization failed - local &TYPE &NODE. Error=&ERROR. |
FASP042E | FASP042E: FASP initialization failed. |
Monitoring FASP transactions
You can view the Copy Termination Record (CTRC) for detailed statistics. For example, you can verify FASP was used, what bandwidth was used, and which policy was used.
- FASP=>Y indicates that FASP was used to transfer this file. FASP=>N would indicate TCP/IP was used.
- FSPL=>FAIR is the policy negotiated for this file transfer.
- FSBW=>1000000000 is the bandwidth negotiated for this file transfer (in bits per second).
- FMBC =>2 is the high water mark for the number of FASP buffers used
- FBCS =>16777216 is the FASP buffer size
- FSTH =>1073741824 is filesize threshold
- FSLP =>23708 is listen port used for FASP
PROCESS RECORD Record Id => CTRC
Completion Code => 0
Message Id => SCPA000I
Short Text => Copy step successful.
Ckpt=>Y Lkfl=>N Rstr=>N Xlat=>N Scmp=>N Ecmp=>N CRC=>N
FASP=>Y FSPL=>FAIR FSBW=>10000000000 FMBC=>2 FBCS=>16777216 FSTH=>1073741824
FSLP=>23708
Limitations
The following features cannot be used with FASP and Connect:Direct for UNIX:
- Firewall navigation source ports should not be used with FASP
- Silent installation does not support the FASP configuration parameters