关键词：
keepalived + lvs
172.16.30.31 master
172.16.30.32 backup
172.16.30.10 vip
故障：监控显示keepalived master主机故障；通过ping查看vip存在。master重启以后，VIP漂移回master.
偶然间，重启master网卡发现，vip漂移backup以后，无法漂移回master；需重启master-keealived服务，VIP才可漂移回master.
master:
message
May 9 10:47:06 sd3031 Keepalived_healthcheckers[31967]: Netlink reflector reports IP 172.16.30.31 removed
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: Netlink reflector reports IP 172.16.30.31 removed
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: Netlink reflector reports IP 172.16.30.10 removed
May 9 10:47:06 sd3031 Keepalived_healthcheckers[31967]: Netlink reflector reports IP 172.16.30.10 removed
May 9 10:47:06 sd3031 avahi-daemon[3924]: Withdrawing address record for 172.16.30.31 on eth0.
May 9 10:47:06 sd3031 avahi-daemon[3924]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.16.30.31.
May 9 10:47:06 sd3031 avahi-daemon[3924]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.30.10.
May 9 10:47:06 sd3031 avahi-daemon[3924]: IP_ADD_MEMBERSHIP failed: No such device
May 9 10:47:06 sd3031 avahi-daemon[3924]: Withdrawing address record for 172.16.30.10 on eth0.
May 9 10:47:06 sd3031 avahi-daemon[3924]: Interface eth0.IPv4 no longer relevant for mDNS.
May 9 10:47:06 sd3031 kernel: bnx2 0000:0b:00.0: eth0: using MSIX
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: Kernel is reporting: interface eth0 DOWN
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: VRRP_Instance(VI_1) Entering FAULT STATE
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: VRRP_Instance(VI_1) removing protocol VIPs.
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: Netlink: error: Cannot assign requested address, type=(21), seq=1494298005, pid=0
May 9 10:47:06 sd3031 Keepalived_vrrp[31968]: VRRP_Instance(VI_1) Now in FAULT state
May 9 10:47:07 sd3031 Keepalived_healthcheckers[31967]: TCP socket bind failed. Rescheduling.
May 9 10:47:09 sd3031 kernel: bnx2 0000:0b:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex
May 9 10:47:09 sd3031 Keepalived_healthcheckers[31967]: TCP socket bind failed. Rescheduling.
May 9 10:47:09 sd3031 last message repeated 2 times
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: Kernel is reporting: interface eth0 UP
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: cant do IP_ADD_MEMBERSHIP errno=No such device (19)
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: Netlink reflector reports IP 172.16.30.31 added
May 9 10:47:10 sd3031 Keepalived_healthcheckers[31967]: Netlink reflector reports IP 172.16.30.31 added
May 9 10:47:10 sd3031 avahi-daemon[3924]: New relevant interface eth0.IPv4 for mDNS.
May 9 10:47:10 sd3031 avahi-daemon[3924]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.30.31.
May 9 10:47:10 sd3031 avahi-daemon[3924]: Registering new address record for 172.16.30.31 on eth0.
master重启网卡以后，keepalived在eth0网卡up状态，但是未获取到ip地址的时候，无法进行组播。
出现异常
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: Kernel is reporting: interface eth0 UP
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: cant do IP_ADD_MEMBERSHIP errno=No such device (19)
May 9 10:47:10 sd3031 Keepalived_vrrp[31968]: Netlink reflector reports IP 172.16.30.31 added
keepalived进行服务之间内部通信，需要网卡IP做支撑，此出，网卡未有IP，keepalived之间通信失败。
master与backup之间通信失败，导致vip未进行漂移。
修改了keepalived.conf
vrrp_instance ** {
advert_int 2 #修改此项，为keepalived之间组播间隔时间。
}
将默认1修改为2
重启master网卡
master_message.log
May 9 11:03:30 sd3031 Keepalived_healthcheckers[5463]: Netlink reflector reports IP 172.16.30.31 removed
May 9 11:03:30 sd3031 avahi-daemon[3924]: Withdrawing address record for 172.16.30.31 on eth0.
May 9 11:03:30 sd3031 Keepalived_healthcheckers[5463]: Netlink reflector reports IP 172.16.30.10 removed
May 9 11:03:30 sd3031 avahi-daemon[3924]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.16.30.31.
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: Netlink reflector reports IP 172.16.30.31 removed
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: Netlink reflector reports IP 172.16.30.10 removed
May 9 11:03:30 sd3031 avahi-daemon[3924]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.30.10.
May 9 11:03:30 sd3031 avahi-daemon[3924]: IP_ADD_MEMBERSHIP failed: No such device
May 9 11:03:30 sd3031 avahi-daemon[3924]: Withdrawing address record for 172.16.30.10 on eth0.
May 9 11:03:30 sd3031 avahi-daemon[3924]: Interface eth0.IPv4 no longer relevant for mDNS.
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: Kernel is reporting: interface eth0 DOWN
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) Entering FAULT STATE
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) removing protocol VIPs.
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: Netlink: error: Cannot assign requested address, type=(21), seq=1494298989, pid=0
May 9 11:03:30 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) Now in FAULT state
May 9 11:03:30 sd3031 kernel: bnx2 0000:0b:00.0: eth0: using MSIX
May 9 11:03:32 sd3031 Keepalived_healthcheckers[5463]: TCP socket bind failed. Rescheduling.
May 9 11:03:33 sd3031 kernel: bnx2 0000:0b:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex
May 9 11:03:34 sd3031 Keepalived_healthcheckers[5463]: TCP socket bind failed. Rescheduling.
May 9 11:03:34 sd3031 Keepalived_healthcheckers[5463]: TCP socket bind failed. Rescheduling.
May 9 11:03:34 sd3031 Keepalived_healthcheckers[5463]: Netlink reflector reports IP 172.16.30.31 added
May 9 11:03:34 sd3031 Keepalived_vrrp[5464]: Netlink reflector reports IP 172.16.30.31 added
May 9 11:03:34 sd3031 avahi-daemon[3924]: New relevant interface eth0.IPv4 for mDNS.
May 9 11:03:34 sd3031 avahi-daemon[3924]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.30.31.
May 9 11:03:35 sd3031 avahi-daemon[3924]: Registering new address record for 172.16.30.31 on eth0.
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: Kernel is reporting: interface eth0 UP
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) Transition to MASTER STATE
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) Entering MASTER STATE
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) setting protocol VIPs.
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 172.16.30.10
May 9 11:03:37 sd3031 Keepalived_healthcheckers[5463]: Netlink reflector reports IP 172.16.30.10 added
May 9 11:03:37 sd3031 avahi-daemon[3924]: Registering new address record for 172.16.30.10 on eth0.
May 9 11:03:37 sd3031 Keepalived_vrrp[5464]: Netlink reflector reports IP 172.16.30.10 added
backup_message-log
May 9 11:03:35 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Transition to MASTER STATE
May 9 11:03:35 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Entering MASTER STATE
May 9 11:03:35 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) setting protocol VIPs.
May 9 11:03:35 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 172.16.30.10
May 9 11:03:35 sd3032 Keepalived_vrrp[26277]: Netlink reflector reports IP 172.16.30.10 added
May 9 11:03:35 sd3032 Keepalived_healthcheckers[26275]: Netlink reflector reports IP 172.16.30.10 added
May 9 11:03:35 sd3032 avahi-daemon[3963]: Registering new address record for 172.16.30.10 on eth0.
May 9 11:03:40 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 172.16.30.10
May 9 11:04:05 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Received higher prio advert
May 9 11:04:05 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) Entering BACKUP STATE
May 9 11:04:05 sd3032 Keepalived_vrrp[26277]: VRRP_Instance(VI_1) removing protocol VIPs.
May 9 11:04:05 sd3032 Keepalived_healthcheckers[26275]: Netlink reflector reports IP 172.16.30.10 removed
May 9 11:04:05 sd3032 Keepalived_vrrp[26277]: Netlink reflector reports IP 172.16.30.10 removed
May 9 11:04:05 sd3032 avahi-daemon[3963]: Withdrawing address record for 172.16.30.10 on eth0.
VIP正常漂移本文出自 “运维笔记” 博客，请务必保留此出处http://phospherus.blog.51cto.com/7824598/1923725
keepalived安装及配置vip漂移(代码片段)
环境：主机10.10.6.105备机10.10.6.106VIP 10.10.6.188一、安装yuminstallkeepalived-y二、配置文件（/etc/keepalived/keepalived.conf）主机配置global_defsnotification_email[email protected][email protected][email& 查看详情
keepalived安装配置（高可用vip）,双主模式
首先需要明白我们准备使用keepalived来做什么，今天这里只是给大家简单安装和配置下keepalived实现vip对外服务，防止单点故障。keepalived是高可用高可用高可用而非负载非负载非负载。 下面我将使用keepalived部署双主模模... 查看详情
工作随笔-centos7以及docker搭建keepalived实现浮动vip
参考技术A4.验证准备服务器VIP漂移4.1备服务器首先启动keepalived，然后抓包4.2主服务器启动keepalived，然后抓包4.3通过ipa命令确认VIP漂移成功 查看详情
小谈keepalivedvip漂移原理与vrrp协议
参考技术Ahttps://www.cnblogs.com/lixuwu/p/8476997.html什么是keepalived呢？keepalived是实现高可用的一种轻量级的技术手段，主要用来防止单点故障(单点故障是指一旦某一点出现故障就会导致整个系统架构的不可用)的发生。之所以说keepalived... 查看详情
keepalived常见故障
...200 10.0.0.201这个登录一下，帮我测试一下nginx那个keepalived的功能正常不系统是centos7keepalived和 nginx都可以重启测试：1、pkillnignx后，故障切换一切正常，恢复nginx后也可以抢占回VIP2、在修改nginx配置文件后，在pkilln... 查看详情
keepalivedvip漂移基本原理及选举算法(代码片段)
keepalived可以将多个无状态的单点通过虚拟IP(以下称为VIP)漂移的方式搭建成一个高可用服务，常用组合比如keepalived+nginx，lvs，haproxy和memcached等。它的实现基础是VRRP协议，包括核心的MASTER竞选机制都是在VRRP协议所约定的。一、配... 查看详情
keepalived设置master故障恢复后不重新抢回vip配置
.../iptables适当位置添加行：-AINPUT-d224.0.0.18-jACCEPT默认情况下keepalived有一台主服务器（master，以后称之为M服务器），一台备服务器（backup，以后称之为B服务器）。正常情况下M服务器接管VIP成为【主】 查看详情
keepalived常见问题
...统分裂为两个独立的结点，这时两个结点会争抢资源。（keepAlived中表现为两个结点同时拥有VIP） keepalived分为主备两台机器，但对外只提供一个VIP访问，只有主机down机VIP才会漂移到备机提供服务。脑裂会导致主备两台机器同... 查看详情
keepalived非抢占模式(代码片段)
keepalived非抢占模式抢占模式为当keepalived的某台机器挂了之后VIP漂移到了备节点，当主节点恢复后主动将VIP再次抢回，keepalived默认工作在抢占模式下，而非抢占模式则是当主节挂了再次起来后不再抢回VIP。此处需要注意非抢占模... 查看详情
keepalived组播故障排查
虚拟机无法接收keepalived的vrrp组播现象： 在Ubuntu1404的系统下安装了三台虚拟机，然后配置了一个简单的keepalived+haproxy服务。结果启动后发现三台虚拟机都配上vip，keepalived.log日志中也未看见error的报错信息。排... 查看详情
keepalivevip故障
前端环境如下：Nginx+Keepalived(MASTER)-->node*12||CiscoASA-->VIP1.18||Nginx+Keepalived(BACKUP)问题描述：客户端访问域名指向CiscoASA外网端口，通过NAT地址转换到内网的VIP1.18，到达Nginx负载均衡器，之后将请求转向节点服务器。故障时，客... 查看详情
【keepalived】keepalivedvrrp双实例
...主机上的监听的端口（此处为80）做健康检查，所以需要keepalived绑定vip结合检测脚本，实现高可用。nginx01+nginx02+keepalived---->vip01nginx03+nginx04+keepalived---->vip02将域名www.example.com解析在vip01vip02上，既实现了负载均衡，又实现了... 查看详情
keepalived
keepalived一、原理： 功能：能够自动实现将用户访问的ip转移的方法，故障重启，故障，恢复切换，故障报警 模型：Master/Backup 使用场景：节点少，没有共享存储等等。他只能有一个主活动，其他为从节点功能实现：Ma... 查看详情
keepalived设置master故障恢复后不重新抢回vip(解决nopreempt无效)(代码片段)
注意：一定先关闭防火墙测试，先能保证测试通过。如果服务器一定要用防火墙，那么在测试无误后，通过命令运行VRRP路由冗余协议。允许组播，两台设备上都需要执行iptables-AINPUT-d224.0.0.18-jACCEPT或修改：... 查看详情
rhel6搭建keepalived(ha)任意单故障节点的高可用集群
搭建keepalived(HA)任意单故障节点的高可用集群实验拓扑图：实验要求：使用Keepalived实现web服务器的高可用Web服务器IP地址分别为192.168.4.53和192.168.4.54Web服务器53为主服务器，Web服务器54为备服务器Web服务器的VIP地址为192.168.4.251客... 查看详情
keepalived双机热备实现故障时发送邮件通知
...241backup:192.168.1.242漂移IP：192.168.1.2431。主备调度器都安装keepalived软件安装步骤例如以下：./configure--p 查看详情
keepalived
1:HA集群架构与VIIP工作原理：Linux高可用集群：pacemaker、keepalivedkeepalived理论工作原理：keepalived是以VRRP协议为实现基础的，VRRP全称VirtualRouterRedundancyProtocol,即虚拟路由冗余协议。虚拟路由冗余协议是实现路由器高可用的协议，即... 查看详情
keepalived用脚本实现切换
参考技术A平时做好了keepalived单主或者双住架构后，我们在测试的时候经常需要手动去停止keepalived服务或者网卡服务。假设线上nginx挂了，如何实现自动停止keepalived服务，实现VIP飘逸呢？软件配置文件可以加入脚本功能来检测。... 查看详情