SNDPTFORD Download Failover process

1.	HTTP/HTTPS is attempted first. o The download limit defaults to 100 MB.
2.	If the HTTP/HTTPS connection fails, we failover to the Universal Connection setup, which is the PTP. o The download limit now fails over to 35 MB.
3.	If the Universal Connection connection fails, we failover to SDLC, which is the old external modem method. o For all SDLC connections the download limit is 10 MB.

Failover for a VPN Configuration

The failover process for a VPN configuration follows:

1.	HTTP/HTTPS is attempted first. o The download limit defaults to *NOMAX.
2.	If the HTTP/HTTPS connection fails, we failover to the Universal Connection setup, which is VPN. o The download limit now fails over to 100 MB.
3.	If the Universal Connection connection fails, we failover to SDLC, which is the old external modem method. o For all SDLC connections the download limit is 10 MB.

Note: Multihop does not utilize the HTTP/HTTPS connectivity; thus, the largest download limit is 100 MB.

V5R4 and i 6.1 and i 7.1

In V5R4 and above, a user can set up a *primary, as well as a *backup, connection with *LCLDIAL, *RMTDIAL, or *DIRECT to name a few.
The *DIAL types take the place of the V5R3 *PTP, and the *DIRECT takes the place of *VPN. We call this the Universal Connection.

Note: *OTHERISP and *MULTIHOP are also available, although *MULTIHOP has a different failover scenario.

If local point-to-point was configured, the user will see the following in WRKTCPPTP:

QLCLDIAL01
QVPN01IBM1
QVPN01IBM2

Note: If the connection is using a remote modem, the profile found would be QRMTDIAL01.

If VPN was configured, the user will see the following in WRKTCPPTP:

QVPN01IBM1
QVPN01IBM2

Failover for a Point-to-Point Configuration

The failover process for a point-to-point configuration follows:

1.	HTTP/HTTPS is attempted first. o The download limit defaults to 100 MB.
2.	If the HTTP/HTTPS connection fails, we failover to the Universal Connection setup, which is the PTP. o The download limit now fails over to 35 MB.
3.	If the Universal Connection connection fails, we failover to SDLC, which is the old external modem method. o For all SDLC connections the download limit is 10 MB.

Failover for a VPN Configuration

The failover process for a VPN configuration follows:

1.	HTTP/HTTPS is attempted first. o The download limit defaults to *NOMAX.
2.	If the HTTP/HTTPS connection fails, we failover to the Universal Connection setup, which is VPN. o The download limit now fails over to 100 MB.
3.	If the Universal Connection connection fails, we failover to SDLC, which is the old external modem method. o For all SDLC connections the download limit is 10 MB.

Notes:

1.	Multihop does not utilize the HTTP/HTTPS connectivity; thus, the largest download limit is 100 MB.
2.	HTTP Proxy connections have a size limit of 100 MB.
3.	HTTP Proxy connections with NTLM authentication are not supported.
4.	V5R4 also allows backup connections. These profiles will have 02 rather than 01, for example: *primary configured as a direct connection has QVPN01IBM1 and QVPN01IBM2 profiles configured. *backup configured as a local modem has QLCLDIAL02, QVPN02IBM1, and QVPN02IBM2 profiles configured.

Summary

The failover process follows:

1.	HTTP/HTTPS is attempted first. o If the configuration was set up as Direct/VPN, then the download limit defaults to *NOMAX. o If the configuration was set up for PTP, then the download limit defaults to 100 MB.
2.	If the HTTP/HTTPS connection fails, we failover to the Universal Connection setup, which is VPN/Direct or PTP. o If the configuration was set up as Direct/VPN, then the download limit now fails over to 100 MB. o If the configuration was set up for PTP, then the download limit now fails over to 35 MB.
3.	If the Universal Connection connection fails, we failover to SDLC, which is the old external modem method. o For all SDLC connections the download limit is 10 MB.

Notes:

1.	HTTP/HTTPS/HTTP Proxy connections allow a larger size limit and image orders.
2.	If the HTTP/HTTPS/HTTP Proxy connection fails, the larger size limit and image order options will also fail. Failover to save file orders will occur.
3.	HTTP proxy connections with NTLM authentication are not supported.

Related Documents

For additional information, refer to the following Rochester Support Center knowledgebase documents:

New, Configuration for ECS / ESA Using a Character-Based Screen- V5R4:
New, Ordering PTFs Using the SNDPTFORD Command at V5R3 and Above:
New, General Information on Setting Up ECS and Electronic Service Agent for V5R3 and V5R4 and Above:
New, Point-to-Point Profile Changes in V5R3 and V5R4:
New, SNDPTFORD Image Orders at V5R3, V5R4, and V6R1: