Linux high-Availability load Balancing cluster understanding

HA implementation in highly available clusters heartbeat of course there are others like keeplive

How the load-balanced cluster LB is implemented.

(1). Hardware lb (more famous) F5; The big-IP series, Citri, the company's NetScaler series, the A10 Company's AX-series

(2). Software lb Four layer: LVS (Linux virtualserver)

Note: Chinese developed, seven-storey: nginx,haproxy

High-availability Load balancing

When configuring Ha, the server's VIP does not need to set sub-interfaces in Setup, Heartbeat creates

When you configure LB server's VIP at setup, you need to configure the ETH0:0 sub-interface Separately, the DR model needs to create a manual create lo:0 sub-interface configuration VIP on the real server, and configure the route, ignoring the ARP request.

When configuring ha+lb, two lb does not need to manually create the configuration eth0:0 subinterface, the DR model needs to create a manually created lo:0 subinterface configuration VIP on the real server and configure the route, ignoring the ARP request.

This article from "Sleep" blog, declined reprint!

Linux high-Availability load Balancing cluster understanding