IBM Connect:Direct FASP scenarios
The use of FASP protocol by IBM® Sterling Secure Proxy depends on the presence of a High-Speed Add-on (HSAO) license and the FASP setting used on the sending and receiving Connect:Direct® nodes.
Connect:Direct nodes without Secure Proxy
The following table shows when IBM Connect:Direct FASP protocol is used between two Connect:Direct nodes with no Secure Proxy involved, based on the type of license.
| PNODE FASP= | Protocol | SNODE FASP= |
|---|---|---|
| N | TCP | N |
| N | TCP | Y |
| N | TCP | SSP |
| Y | TCP | N |
| Y | CD: FASP | Y |
| Y | TCP | SSP |
| SSP | TCP | N |
| SSP | TCP | Y |
| SSP | TCP | SSP |
Connect:Direct nodes with a single instance of Secure Proxy
The following table shows when Connect:Direct FASP protocol is used when the twoConnect:Direct nodes are using a single instance of Secure Proxy, based on the type of license.
| 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 |
Connect:Direct nodes with two instances of Secure Proxy
The following table shows when Connect:Direct FASP protocol is used when the two Connect:Direct nodes are using two instances of Secure Proxy, based on the type of license.
| 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 |