RHEL6 platform LVS implements Load Balancing LoadBalancer

The LVS (Linuxvirtualserver) Cluster type is usually described by LVSDirector's request to relay to the cluster node. Currently, there are three available methods: the number of nodes that can be owned when the network address translation (LVS-NAT) different network 10 ~ 20 direct routing (LVS-DR) (Scheduler) same network high (100) ip tunneling (LVS-TUN) Support WAN high (100) Basic LoadBalancer structure: Level 3

The LVS (Linux virtual server) Cluster type is usually described by LVS ctor relay requests to cluster nodes. Currently, there are three available methods:
Number of nodes available for MB Nic
Network Address Translation (LVS-NAT) different network 10 ~ 20
Direct routing (LVS-DR) (Scheduler) same network high (100)
Ip tunneling (LVS-TUN) supports Wan high (100)

Basic Load Balancer structure:

Three-Stage Load Balancer structure:

Routing rules:
1. NAT Routing

2. Direct route DR

LVS-DR Configuration:

Vip
|
Clients -- DR----RS -- clients
|
NoARP

 

DR: Direct Routing
RS: Real Server

The server Load balancer is only responsible for scheduling requests, and the server directly returns the response to the customer, which can greatly improve the throughput of the entire cluster system. Both the scheduler and the server group must physically have a network adapter connected through a non-disconnected LAN, such as through a switch or high-speed HUB. The VIP address is shared by the scheduler and the server group. The VIP address configured by the scheduler is externally visible and used to receive request packets from virtual services; all servers configure the VIP address on their Non-ARP network devices. It is invisible to the outside and is only used to process network requests whose target address is VIP.

For more details, refer to the highlights on the next page.: Http://www.linuxidc.com/Linux/2013-11/92794p2.htm

Reading:

LVS-DR mode configuration details http://www.linuxidc.com/Linux/2013-01/78679.htm

LVS-DR direct routing for Load Balancing example http://www.linuxidc.com/Linux/2012-12/77033.htm

LVS-DR + Heartbeat for High Availability load balancing service http://www.linuxidc.com/Linux/2012-10/73008.htm

Principle of LVS-DR mode and possible "False load balancing" http://www.linuxidc.com/Linux/2012-10/72892.htm

High-availability LVS-DR for http://www.linuxidc.com/Linux/2012-07/64736.htm Load balancer with heartbeat + ldirectory

Keepalived + LVS-DR mode configure High Availability Load Balancing cluster http://www.linuxidc.com/Linux/2012-06/63139.htm