1.6. LVS — A Block Diagram
LVS routers use a collection of programs to monitor cluster members and cluster services. Figure 1.5, “LVS Components” illustrates how these various programs on both the active and backup LVS routers work together to manage the cluster.
Figure 1.5. LVS Components
pulsedaemon runs on both the active and passive LVS routers. On the backup router,
pulsesends a heartbeat to the public interface of the active router to make sure the active router is still properly functioning. On the active router,
lvsdaemon and responds to heartbeat queries from the backup LVS router.
Once started, the
lvsdaemon calls the
ipvsadmutility to configure and maintain the IPVS routing table in the kernel and starts a
nannyprocess for each configured virtual server on each real server. Each
nannyprocess checks the state of one configured service on one real server, and tells the
lvsdaemon if the service on that real server is malfunctioning. If a malfunction is detected, the
ipvsadmto remove that real server from the IPVS routing table.
If the backup router does not receive a response from the active router, it initiates failover by calling
send_arpto reassign all virtual IP addresses to the NIC hardware addresses (MAC address) of the backup node, sends a command to the active router via both the public and private network interfaces to shut down the
lvsdaemon on the active router, and starts the
lvsdaemon on the backup node to accept requests for the configured virtual servers.
1.6.1. LVS Components
Section 126.96.36.199, “
pulse” shows a detailed list of each software component in an LVS router.
This is the controlling process which starts all other daemons related to LVS routers. At boot time, the daemon is started by the
/etc/rc.d/init.d/pulsescript. It then reads the configuration file
/etc/sysconfig/ha/lvs.cf. On the active router,
pulsestarts the LVS daemon. On the backup router,
pulsedetermines the health of the active router by executing a simple heartbeat at a user-configurable interval. If the active router fails to respond after a user-configurable interval, it initiates failover. During failover,
pulseon the backup router instructs the
pulsedaemon on the active router to shut down all LVS services, starts the
send_arpprogram to reassign the floating IP addresses to the backup router's MAC address, and starts the
lvsdaemon runs on the active LVS router once called by
pulse. It reads the configuration file
/etc/sysconfig/ha/lvs.cf, calls the
ipvsadmutility to build and maintain the IPVS routing table, and assigns a
nannyprocess for each configured LVS service. If
nannyreports a real server is down,
ipvsadmutility to remove the real server from the IPVS routing table.
This service updates the IPVS routing table in the kernel. The
lvsdaemon sets up and administers LVS by calling
ipvsadmto add, change, or delete entries in the IPVS routing table.
nannymonitoring daemon runs on the active LVS router. Through this daemon, the active router determines the health of each real server and, optionally, monitors its workload. A separate process runs for each service defined on each real server.
This is the LVS configuration file. Directly or indirectly, all daemons get their configuration information from this file.
188.8.131.52. Piranha Configuration Tool
This is the Web-based tool for monitoring, configuring, and administering LVS. This is the default tool to maintain the
/etc/sysconfig/ha/lvs.cfLVS configuration file.
This program sends out ARP broadcasts when the floating IP address changes from one node to another during failover.
Chapter 2, Initial LVS Configuration reviews important post-installation configuration steps you should take before configuring Red Hat Enterprise Linux to be an LVS router.