SolarWinds | Serv-U
Contact Support: 866-530-8040 | Contact Sales: 855-498-4154 or email | Show Flags | Login
Serv-U FTP Server Home Page
The Best for Less
Secure file transfer & share files
from anywhere - affordably

BUY NOW
FREE for 14 Days
Full featured trial with secure
FTP, file sharing & web transfer

DOWNLOAD FREE TRIAL


How to Deploy Serv-U Gateway in a Cluster  -  KB Article #2103

Related Articles -- 2077, 2076, 2075

When you deploy a cluster of Serv-U Gateways, you need to:

  1. Define each Gateway on each Serv-U server (at the Server level)
  2. Define listeners on BOTH Gateways (at the Domain level)

Serv-U does not currently load-balance ports on the Gateway itself, so you need to declare different ports on each Serv-U Gateway listener and then use your load balancer to address the entire pool.

For example, to set up SFTP in this configuration:

...you would use a configuration like the following.

  1. Add Gateway#1 and Gateway#2 on Serv-U#1
  2. Add Gateway#1 and Gateway#2 on Serv-U#2
  3. Go into your domain on Serv-U#1 and add TWO new listeners:
    • SFTP on Gateway#1 on port 10022 (or any other port)
    • SFTP on Gateway#2 on port 10022
  4. Go into your domain on Serv-U#2 and add TWO more new listeners:
    • SFTP on Gateway#1 on port 20022
    • SFTP on Gateway#2 on port 20022
  5. Go into your load balancer and configure the following round-robin pool to handle incoming connections on port 22:
    • Port 10022 on Gateway#1
    • Port 20022 on Gateway#1
    • Port 10022 on Gateway#2
    • Port 20022 on Gateway#2

Recommended Configuration

We recommend adding the server number to the port numbers assigned to listeners. The following recommended configuration uses this convention. (All leading numbers are TCP/IP ports.)

Serv-U Server #1 - define these listeners on EACH Serv-U Gateway:

  • 10021: FTP and explicit SSL/TLS
  • 10022: SFTP using SSH
  • 10080: HTTP
  • 10443: HTTPS (SSL encrypted HTTP)
  • 10990: Implicit FTPS (SSL/TLS)
  • ALSO: Set your FTP passive port range to 10500-10509 (on "Server Settings | Network Settings")

Serv-U Server #2 - define these listeners on EACH Serv-U Gateway:

  • 20021: FTP and explicit SSL/TLS
  • 20022: SFTP using SSH
  • 20080: HTTP
  • 20443: HTTPS (SSL encrypted HTTP)
  • 20990: Implicit FTPS (SSL/TLS)
  • ALSO: Set your FTP passive port range to 20500-20509

Load Balancer - define the following service pools:

  • 21 (FTP and explicit SSL/TLS): Assign to ports 10021 and 20021 on each Gateway (4 ports in all)
  • 22 (SFTP using SSH): Assign to ports 10022 and 20022 on each Gateway
  • 80 (HTTP): Assign to ports 10080 and 20080 on each Gateway
  • 443 (HTTPS (SSL encrypted HTTP)): Assign to ports 10443 and 20443 on each Gateway
  • 990 (Implicit FTPS (SSL/TLS)): Assign to ports 10990 and 20990 on each Gateway
  • 10500-10509 (Serv-U #1's passive FTP ports): Assign to ports 10500-10509 on each Gateway (requires "sticky sessions" as described below)
  • 20500-20509 (Serv-U #2's passive FTP ports): Assign to ports 20500-20509 on each Gateway
  • Also set "sticky sessions" (all connections from the same IP source address will be sent to the same destination) on 21 (FTP and explicit SSL/TLS) and 990 (Implicit FTPS (SSL/TLS)).

Component Failure Scenarios

With this configuration, service loss is only possible if both Gateway nodes or both Serv-U nodes cease to function. Three possible failures are briefly considered below.

One Gateway Fails

In this scenario one of the Serv-U Gateways fails. The load balancer notices the two missing ports from the dead gateway and withdraws them from the load balancing pool. From the perspective of end users, service continues.

One Server Fails

In this scenario one of the Serv-U servers fails. This causes the Serv-U Gateways to shut down their related ports. Then, the load balancer notices the missing port from the each gateway and withdraws them from the load balancing pool. From the perspective of end users, service continues.

One Server and One Gateway Fail

In this scenario one of the Serv-U servers fails and one of the Serv-U Gateways fails. This loss of the Serv-U server causes the surviving Serv-U Gateway to shut down its related ports. Now, the load balancer notices that all ports are inactive except one and begins to send all traffic to the single surviving port. From the perspective of end users, service continues.



Login to Customer Service Center

Please enter your e-mail address and password in the fields below.

Email Address:

Password: