Server Load Balancing

Hosting multiple servers to share the traffic load for the same service is common. It can avoid excessive load on a single server by distributing the load, optimizing resource usage, and preventing a single server failure. Vigor3912/3910 support the Server Load Balance function. With Server Load Balance, when massive connections enter the router, the router will distribute the inbound NAT sessions among the servers with the configured load balance weight.

  • Supported Model and Firmware version:
  • Vigor3912/Vigor3912S fw 4.3.5
  • Vigor3910/Vigor2962 fw 4.4.3*
  • Vigor3912/3910 Setup

    Go to NAT >> Server Load Balance. Click an index to configure the settings.

  • Check Enable
  • Give a profile name for identification
  • Select the protocol of the service (TCP for web service)
  • Select WAN interface as where the Internet clients can access the server
  • Enter the Public Port number which will open to the local server
  • Select a scheduler type (Learn more in the following section)
  • Enter the IPs, ports, and weights of local servers. Note that the session will not forward to a server when its weight is set to 0.
  • Scheduler

    We offer two options for scheduler configuration to meet different needs of server type.

  • Source IP Based: The same source IP will always connect to the same server.
  • Least Connected: The same source IP may connect to a different server every time. If you connect to server A this time, when the session terminated, you might connect to server B next time.
  • With the configuration above, when there are 30 Internet clients connecting to port 80 on WAN5, the router will redirect 10 of them to Server A (10.10.1.1), 10 of them to Server B (10.10.1.100), and 10 of them to Server C (10.10.1.200).

    Vigor3900/2960 Setup

    Go to NAT >> Server Load Balance. Click Add to create a new profile.

  • Give a profile name for identification
  • Check Enable
  • Select the protocol of the service (TCP for web service)
  • Select WAN interface as where the Internet clients can access the server
  • Enter the port number which will open to the local server
  • Select a scheduler type (Learn more in the following section)
  • Click Add at Real Server to set the Ips, ports, and weights of local servers
  • Scheduler

    We offer two options for scheduler configuration to meet different needs of server type.

  • Least Connected: The same source IP may connect to a different server every time. If you connect to server A this time, when the session terminated, you might connect to server B next time.
  • Source IP Based: The same source IP will always connect to the same server.
  • With the configuration below, when there are 10 Internet clients connecting to port 80 on WAN 1, the router will redirect 3 of them to Server A (192.168.239.2), 1 of them to Server B, and 6 of them to Server C.

    With the configuration below, when there are 10 connection requests to port 80 on WAN 1, the router will redirect 3 of them to Server A (192.168.239.2), 1 of them to Server B and 6 of them to Server C.

    Published On:2024-01-24 

    Was this helpful?