keepalived主要用作RealServer的健康状态检查以及LoadBalance主机和BackUP主机之间failover的实现。keepalived主要目的在于，其自身启动一个服务，能够实现工作在双节点或多个节点上，并且可以在内核生效的ipvs规则其中当前持有资源的节点被称为活跃节点，另外的节点被称为备节点被称为 Master/Backup。

VRRP（如果有学习过TCP\IP，这一块很好理解）：

虚拟路由器冗余协议（VRRP）是一种选择协议，它可以把一个虚拟路由器的责任动态分配到局域网上的 VRRP 路由器中的一台。控制虚拟路由器 IP 地址的 VRRP 路由器称为主路由器，它负责转发数据包到这些虚拟 IP 地址。一旦主路由器不可用，这种选择过程就提供了动态的故障转移机制，这就允许虚拟路由器的 IP 地址可以作为终端主机的默认第一跳路由器。使用 VRRP 的好处是有更高的默认路径的可用性而无需在每个终端主机上配置动态路由或路由发现协议。 VRRP 包封装在 IP 包中发送。

VRRP优先级别：

VRRP每个节点是有自己的优先级的，一般优先级是从0-255，数字越大优先级越高因此可以这么定义：假如要有一初始化的状态，其中一节点优先级100另一节点优先级99，那么毫无疑问，谁的优先级高谁就是主节点所有的节点刚启动后上线都是backup状态，需通过选举的方式选择master，如果其他节点没有响应则将自己提升为master

通告机制：如果节点之间master出现故障，其会自动转移当前角色，这时我们的管理员应该知道其已切换角色keepalived支持邮件发送机制，如果其状态发生改变的话可以通过邮件方式发送给管理员，使管理员第一时间可以查看其活动状态，方便之后的运维工作

keepalived核心组成部分

1.vrrp的实现

2.virtual_server：基于vrrp作为所谓通告机制之上的

3.vrrp_script:以外部脚本方式进行检测

KeepAlived的安装：

[root@Nginx-one ~]# tar zxf keepalived-1.2.13.tar.gz [root@Nginx-one ~]# cd keepalived-1.2.13[root@Nginx-one keepalived-1.2.13]# yum install kernel-devel openssl-devel libnl-devel[root@Nginx-one keepalived-1.2.13]#./configure --prefix=/ --mandir=/usr/local/share/man/--with-kernel-dir=/usr/src/kernels/2.6.32-431.el6.x86_64/[root@Nginx-one keepalived-1.2.13]# make && make installKeepalived configuration------------------------Keepalived version       :1.2.13        ##version##Compiler: gcc				##编译工具##Compiler flags           :-g -O2	##参数##ExtraLib:-lssl -lcrypto -lcrypt 	##扩展库##Use IPVS Framework:Yes                  ##LVS核心代码框架，不使用LVS可以编译时disable-lvs##IPVS sync daemon support :Yes           ##IPVS同步进程，是否开启取决于 IPVS FRAMEWORK###IPVS use libnl           :Yes           ##是否使用libnl库##fwmark socket support    :Yes           ##套接字框架##Use VRRP Framework:Yes                  ##VRRP框架，keepalived的核心进程vrrpd##Use VRRP VMAC            :Yes           ##VRRP Virtual mac##SNMP support             :NoSHA1 support             :NoUseDebug flags           :No[root@Nginx-one keepalived-1.2.13]# make && make install

KeepAlived的所有配置都在一个配置文件里设置，支持的配置可分为以下三类：

1、全局配置（global configure）

2、VRRPD配置

3、LVS配置

很明显，全局配置就是对整个keepalived生效的配置，不管是否使用LVS，VRRPD是keepalived的核心，LVS配置只在要使用keepalived来配置和管理LVS时使用，如果仅使用keepalived来做HA，LVS不需要配置。

配置文件都是以块（block）形式组织的，每个块都在{}范围内，#和!表示注释。

全局定义（global definition）

global_defs {   notification_email {##指定keepalived在发生事件（如切换）需要发送Email的对象，多个写多行##     itchenyi@gmail.com   }   notification_email_from itchenyi@gmail.com   smtp_server 127.0.0.1##SMTP服务器##   smtp_connect_timeout 30##链接超时时间##   router_id Nginx-one			##路由标识，这里用主机名##}

VRRPD配置（VRRP同步组（syncchroization group） 和 VRRP实例 （VRRP instance））

不 使用SYNC Group的话，如果路由有2个网段，一个内网，一个外网，每个网段开启一个VRRP实例，假设VRRP配置为检查内网，那么当外网出现问题 时，VRRPD会认为自己是健康的，则不会发送Master和Backup的切换，从而导致问题，Sync Group可以把两个实例都放入Sync Group，这样的话，Group 里任何一个实例出现问题都会发生切换。

vrrp_instance VI_1 {   ##虚拟路由标识##state MASTER           ##初始状态，默认，选举产生后才可以升级为Master ，这里明确定义其为Master##interface eth1         ##选举通过那个网卡接口##virtual_router_id 10   ##虚拟路由的ID号，一般不大于255，可选IP最后一段使用##priority 100           ##初始优先级，选举过程中判断的依据，和路由的概念一样##advert_int 1           ##检查间隔，默认1s##authentication {       ##认证机制##auth_type PASS         ##认证方式，PASS为明文##auth_pass ipython      ##认证密码##}virtual_ipaddress {    ##虚拟地址池##1.1.1.100}}

配置Backup 配置如下：

[root@nginx-two keepalived-1.2.13]# cat /software/keepalived/etc/keepalived/keepalived.conf 2.! Configuration File for keepalived3. 4.global_defs {5.   notification_email {6.     itchenyi@gmail.com7.   }8.   notification_email_from itchenyi@gmail.com9.   smtp_server 127.0.0.110.   smtp_connect_timeout 3011.   router_id nginx-two12.}13. 14.vrrp_instance VI_1 {15.    state BACKUP16.    interface eth117.    virtual_router_id 2018.    priority 5019.    advert_int 120.    authentication {21.        auth_type PASS22.        auth_pass ipython23.    }24.    virtual_ipaddress {25.        1.1.1.10026.    }27.}28. 29.###其他配置：####30.	nopreempt 设置为不抢占，这个配置只能设置在state为BACKUP的节点上，并且这个机器的优先级必须比另一台高31.	preempt_delay 抢占延迟，默认5分钟32.	debug debug级别33.	notify_master 切换到Master时执行的脚本34. 35.##start##36.[root@Nginx-one keepalived-1.2.13]# service keepalived start37.Starting keepalived:   [  OK  ]38. 39.###观察其日志文件###40.[root@Nginx-one keepalived-1.2.13]# tail -f /var/log/messages 41.Aug  3 00:02:12 Nginx-one Keepalived[8177]: Starting Keepalived v1.2.13 (08/03,2014)42.Aug  3 00:02:12 Nginx-one Keepalived[8178]: Starting Healthcheck child process, pid=818043.Aug  3 00:02:12 Nginx-one Keepalived[8178]: Starting VRRP child process, pid=818144.####当前的IP地址####45.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Netlink reflector reports IP 1.1.1.10 added46.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Netlink reflector reports IP fe80::20c:29ff:fecb:90a2 added47.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Registering Kernel netlink reflector48.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Registering Kernel netlink command channel49.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Netlink reflector reports IP 1.1.1.10 added50.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Netlink reflector reports IP fe80::20c:29ff:fecb:90a2 added51.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Registering Kernel netlink reflector52.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Registering gratuitous ARP shared channel53.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Registering Kernel netlink command channel54.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Opening file '/etc/keepalived/keepalived.conf'.55.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Configuration is using : 62834 Bytes56.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: Using LinkWatch kernel netlink reflector...57.Aug  3 00:02:13 Nginx-one Keepalived_vrrp[8181]: VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]58.###打开并加载配置文件####59.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Opening file '/etc/keepalived/keepalived.conf'.60.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Configuration is using : 7377 Bytes61.Aug  3 00:02:13 Nginx-one Keepalived_healthcheckers[8180]: Using LinkWatch kernel netlink reflector...62.####切换为Master 状态####63.Aug  3 00:02:14 Nginx-one Keepalived_vrrp[8181]: VRRP_Instance(VI_1) Transition to MASTER STATE64.Aug  3 00:02:15 Nginx-one Keepalived_vrrp[8181]: VRRP_Instance(VI_1) Entering MASTER STATE65.Aug  3 00:02:15 Nginx-one Keepalived_vrrp[8181]: VRRP_Instance(VI_1) setting protocol VIPs.66.####在接口上添加VIP###67.Aug  3 00:02:15 Nginx-one Keepalived_vrrp[8181]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 1.1.1.10068.Aug  3 00:02:15 Nginx-one Keepalived_healthcheckers[8180]: Netlink reflector reports IP 1.1.1.100 added69.Aug  3 00:02:20 Nginx-one Keepalived_vrrp[8181]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 1.1.1.10070. 71. 72.###查看是否添加VIP###73.[root@Nginx-one keepalived-1.2.13]# ip a show|awk '/inet\ /'74.    inet 127.0.0.1/8 scope host lo75.    inet 1.1.1.10/8 brd 1.255.255.255 scope global eth176.    inet 1.1.1.100/32 scope global eth177. 78.停止MASTER，查看BACKUP的状态转移79.[root@Nginx-one keepalived-1.2.13]# service keepalived stop80.Stopping keepalived:                                       [  OK  ]81. 82. 83.[root@nginx-two keepalived-1.2.13]# tail -f /var/log/messages 84.Aug  3 00:05:01 nginx-two Keepalived_vrrp[5148]: Using LinkWatch kernel netlink reflector...85.Aug  3 00:05:01 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) Entering BACKUP STATE86.Aug  3 00:05:01 nginx-two Keepalived_healthcheckers[5147]: Using LinkWatch kernel netlink reflector...87.Aug  3 00:05:01 nginx-two Keepalived_vrrp[5148]: VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]88.Aug  3 00:05:40 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) Transition to MASTER STATE89.Aug  3 00:05:41 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) Entering MASTER STATE90.Aug  3 00:05:41 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) setting protocol VIPs.91.Aug  3 00:05:41 nginx-two Keepalived_healthcheckers[5147]: Netlink reflector reports IP 1.1.1.100 added92.Aug  3 00:05:41 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 1.1.1.10093.Aug  3 00:05:46 nginx-two Keepalived_vrrp[5148]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 1.1.1.10094. 95.####和路由协议一样，当MASTER上线被检测到会抢占VIP，可以想象的到，Keepalived也支持非抢占模式，只有BACKUP在变成MASTER后宕机了，才会转移VIP，说起来怎么这么绕口####

定义Keepalived的检测机制

###一只简单的脚本判断nginx 是否在工作###[root@nginx-two ~]# cat nginx_check.sh #!/bin/bashalive=`netstat -pant|awk '/0.0.0.0:80/&&/LISTEN/'|wc -l`if[ $alive -eq 1];then   exit 0else   exit 1 fi###增加keepalived配置###vrrp_script nginx_check{    script "/root/nginx_check.sh"    interval 1      ###检测时间间隔 1s###    weigh -60      ###如果条件成立，权重-60###}####将track_script块加入instance 配置块####    track_script    {        nginx_check    }[root@Nginx-one ~]# service keepalived restartStopping keepalived:[  OK  ]Starting keepalived:[  OK  ]###无须质疑，只要nginx 的80端口是正常监听的，主就还是主###[root@Nginx-one ~]# ip a show|awk '/inet\ /'    inet 127.0.0.1/8 scope host lo    inet 1.1.1.10/8 brd 1.255.255.255 scope global eth1    inet 1.1.1.100/32 scope global eth1###停止Nginx服务###[root@Nginx-one ~]# service nginx stopStopping nginx:[  OK  ]###看看日志###Aug300:52:13Nginx-one Keepalived_vrrp[8490]: VRRP_Script(nginx_check) failedAug300:52:14Nginx-one Keepalived_vrrp[8490]: VRRP_Instance(VI_1)Entering FAULT STATEAug300:52:14Nginx-one Keepalived_vrrp[8490]: VRRP_Instance(VI_1) removing protocol VIPs.Aug300:52:14Nginx-one Keepalived_vrrp[8490]: VRRP_Instance(VI_1)Nowin FAULT stateAug300:52:14Nginx-one Keepalived_healthcheckers[8489]:Netlink reflector reports IP 1.1.1.100 removed###Backup机器变成Master了###[root@nginx-two ~]# ip a show|awk '/inet\ /'    inet 127.0.0.1/8 scope host lo    inet 1.1.1.20/8 brd 1.255.255.255 scope global eth1    inet 1.1.1.100/32 scope global eth1

本文原创地址：