Differences between LVS three scheduling Modes

Differences between LVS three scheduling Modes

NAT: Address Translation
DR: Direct routing

TUN: Tunnel

NAT:
The cluster node and director must be in the same IP network;
RIP is usually a private address and is only used for communication between nodes in each cluster;
Director is located between the client and the real server and is responsible for handling all incoming and outgoing communications;
Real server must direct the gateway to DIP;
Supports port ing;
Real Server can use any OS;
Director is prone to system bottlenecks in large-scale application scenarios;

DR:
The cluster node and director must be in the agreed physical network;
RIP can use public IP addresses for convenient remote management and monitoring;
Director is only responsible for processing inbound requests. The ctor directly sends the response to the client;
Real server cannot direct the gateway to DIP;
Port ing is not supported;
Do not change the destination address (because the real Server is already bound to a VIP)
Rewrite the mac address of the Request Message (change the MAC address of the VIP machine to the MAC address of the backend real server), for example:

TUN:

Cluster nodes can span the Internet;
RIP must be a public IP address;
Dirctor is only responsible for processing inbound requests, and the corresponding packets are directly sent from the real server to the client;
The real server Gateway cannot point to director;
Only the OS that supports tunneling can be used for realserver;
Port ing is not supported;

LVS/DR + Keepalived

LVS + Keepalived achieves layer-4 load and high availability

LVS + Keepalived high-availability server Load balancer cluster architecture Experiment

Heartbeat + LVS build a high-availability server Load balancer Cluster

Build an LVS load balancing test environment

A stress test report for LVS

This article permanently updates the link address: