docker keepalived vip 不通怎么绑定
点击联系发帖人
时间：2016-10-13 09:42
Keepalived无法绑定VIP故障排查经历_词汇网
Keepalived无法绑定VIP故障排查经历
责任编辑：词汇网 发表时间： 13:29:41
一&故障描述我在台湾合作方给定的两台虚拟机上部署HAProxy+Keepalived负载均衡高可用方案。在配置完Keepalived后，重新启动Keepalived，Keepalived没有绑定VIP。Keepalived执行程序路径为/data/app_platform/keepalived/sbin/keepalived配置文件路径为/data/app_platform/keepalived/conf/keepalived.conf&&Keepalived的启动脚本为/etc/init.d/keepalivedkeepalived.conf的内容LB1&Master!&Configuration&File&for&keepalived&&&global_defs&{&&¬ification_email&{&&&&&&&&}&&¬ification_email_from&&&&smtp_server&127.0.0.1&&&smtp_connect_timeout&30&&&router_id&LB1_MASTER&}&&&&vrrp_script&chk_haproxy&{&&&&&&&&&script&"killall&-0&haproxy"&&&&&&&&&interval&2&&&&&weight&2&&&&&}&&&&&&&&&vrrp_instance&VI_1&{&&&&&state&MASTER&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&virtual_ipaddress&{&&&&&&&10.1.1.200/24&&&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}重新启动Keepalived查看日志Mar&&3&18:09:00&cv-1&Keepalived[20138]:&Stopping&Keepalived&v1.2.15&(02/28,2015)&Mar&&3&18:09:00&cv-1&Keepalived[20259]:&Starting&Keepalived&v1.2.15&(02/28,2015)&Mar&&3&18:09:00&cv-1&Keepalived[20260]:&Starting&Healthcheck&child&process,&pid=20261&Mar&&3&18:09:00&cv-1&Keepalived[20260]:&Starting&VRRP&child&process,&pid=20262&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&Kernel&netlink&reflector&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&Kernel&netlink&command&channel&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&gratuitous&ARP&shared&channel&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Registering&Kernel&netlink&reflector&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Registering&Kernel&netlink&command&channel&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Configuration&is&using&:&3924&Bytes&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Configuration&is&using&:&55712&Bytes&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&3&18:09:18&cv-1&kernel:&__ratelimit:&1964&callbacks&suppressed&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.查看VIP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13没有VIP绑定二&排查过程1）检查VIP的配置情况向合作方确认提供的VIP的详细情况IPADDR&&10.1.1.200NETMASK&&255.255.255.0GATEWAY&&10.1.1.1Brodcast&&10.1.1.255&&这里设置的是10.1.1.200/24&&&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip2）检查iptables和selinux的设置情况$&sudo&service&iptables&stop&$&sudo&setenforce&0&setenforce:&SELinux&is&disabled如果非要开启iptables的话，需要作些设定iptables&-I&INPUT&-ið1&-d&224.0.0.0/8&-j&ACCEPT&service&iptables&savekeepalived使用224.0.0.18作为Master和Backup健康检查的通信IP3）检查相关的内核参数HAProxy+Keepalived架构需要注意的内核参数有：#&Controls&IP&packet&forwardingnet.ipv4.ip_forward&=&1开启IP转发功能net.ipv4.ip_nonlocal_bind&=&1开启允许绑定非本机的IP如果使用LVS的DR或者TUN模式结合Keepalived需要在后端真实服务器上特别设置两个arp相关的参数。这里也设置好。net.ipv4.conf.lo.arp_ignore&=&1net.ipv4.conf.lo.arp_announce&=&2net.ipv4.conf.all.arp_ignore&=&1net.ipv4.conf.all.arp_announce&=&24）检查VRRP的设置情况LB1&Masterstate&MASTER&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&100LB2&Backupstate&BACKUP&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&99Master和Backup的virtual_router_id需要一样，priority需要不一样，数字越大，优先级越高5）怀疑是编译安装Keepalived版本出现了问题重新下载并编译2.1.13的版本，并重新启动keepalived，VIP仍然没有被绑定。线上有个平台的keepalived是通过yum安装的，于是打算先用yum安装keepalived后将配置文件复制过去看看是否可以绑定VIPrpm&-ivh&http://ftp.linux.ncsu.edu/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm&yum&-y&install&keepalivedcp&/data/app_platform/keepalived/conf/keepalived.conf&&/etc/keepalived/keepalived.conf重新启动keepalived然后查看日志Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Registering&Kernel&netlink&reflector&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Registering&Kernel&netlink&command&channel&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Opening&file&"/etc/keepalived/keepalived.conf".&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Configuration&is&using&:&65250&Bytes&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Opening&file&"/etc/keepalived/keepalived.conf".&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Configuration&is&using&:&7557&Bytes&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&VRRP_Script(chk_haproxy)&succeeded&Mar&&4&16:42:47&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&4&16:42:48&xxxxx&Keepalived_healthcheckers[17332]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&4&16:42:53&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200再查看IP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13再通过yum将keepalived卸载掉yum&remove&keepalived恢复到原来的启动脚本/etc/init.d/keepalived重新启动keepalived后还是无法绑定VIP怀疑是keepalived启动脚本/etc/init.d/keepalived的问题检查/etc/init.d/keepalived#&Source&function&library.&.&/etc/rc.d/init.d/functions&&&exec="/data/app_platform/keepalived/sbin/keepalived"&prog="keepalived"&config="/data/app_platform/keepalived/conf/keepalived.conf"&&&[&-e&/etc/sysconfig/$prog&]&&&&.&/etc/sysconfig/$prog&&&lockfile=/var/lock/subsys/keepalived&&&start()&{&&&&&[&-x&$exec&]&||&exit&5&&&&&[&-e&$config&]&||&exit&6&&&&&echo&-n&$"Starting&$prog:&"&&&&&daemon&$exec&$KEEPALIVED_OPTIONS&&&&&retval=$?&&&&&echo&&&&&[&$retval&-eq&0&]&&&&touch&$lockfile&&&&&return&$retval&}关键是这一行daemon&$exec&$KEEPALIVED_OPTIONS由于没有复制/etc/sysconfig/keepalived,所以将直接执行damon&/data/app_platform/keepalived/sbin/keepalived由于keepalived默认使用的是/etc/keepalived/keepalived.conf作为配置文件，而这里指定了不同的配置文件，所以要修改成为daemon&$exec&-D&-f&$config重新启动keepalived，查看日志和VIP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:136）将LB2&Backup的keepalived启动脚本也修改一下，观察VIP接管情况查看LB1&Master$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13查看LB2&Backup$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13问题出现了，LB1&Master和LB2&Backup都绑定了VIP&10.1.1.200，这是不正常的！！！！在LB1和LB2上登录10.1.1.200看看[lb1&~]$&ssh&10.1.1.200&&Last&login:&Wed&Mar&&4&17:31:33&2015&from&10.1.1.200&[lb1&~]$[lb2&~]$&ssh&10.1.1.200&Last&login:&Wed&Mar&&4&17:54:57&2015&from&101.95.153.246&[b2&&~]$在LB1上停掉keepalived，ping下10.1.1.200这个IP，发现无法ping通在LB2上停掉keepalived，ping下10.1.1.200这个IP，发现也无法ping通然后开启LB1上的keepalived，LB1上可以ping通10.1.1.200,LB2上不行开启LB2上的keepalived，LB2上可以ping通10.1.1.200由此得出，LB1和LB2各自都将VIP&10.1.1.200绑定到本机的eth1网卡上。两台主机并没有VRRP通信，没有VRRP的优先级比较。7)排查影响VRRP通信的原因重新启动LB1&Master的Keepalived查看日志Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&Configuration&is&using&:&65410&Bytes&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Script(chk_haproxy)&succeeded&Mar&&5&15:45:37&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_healthcheckers[32302]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&5&15:45:43&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200发现LB1&Master上的Keepalived直接进入Master状态，然后接管VIP再重新启动LB2&Backup上的Keepalived，查看日志Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&Configuration&is&using&:&65408&Bytes&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Entering&BACKUP&STATE&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&5&15:47:46&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_healthcheckers[30618]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&5&15:47:52&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200可以看到LB2上的Keepalived先进入BACKUP状态，然后又转为MASTER状态，然后接管VIP这样就说明VRRP组播有问题。既然VRRP组播有问题，就尝试使用单播发送VRRP报文。修改LB1和LB2的配置LB1添加以下配置unicast_src_ip&&10.1.1.12&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.17&&&&&&&&&&&&&&&&&}LB2添加以下配置unicast_src_ip&&10.1.1.17&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.12&&&&&&&&&&&&&&&&&}unicast_src_ip&表示发送VRRP单播报文使用的源IP地址unicast_peer&表示对端接收VRRP单播报文的IP地址然后各自重新加载keepalived，观察日志LB1Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Script(chk_haproxy)&considered&successful&on&reload&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&Configuration&is&using&:&65579&Bytes&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(1),&fd(10,11)]&Mar&&5&16:13:36&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Received&lower&prio&advert,&forcing&new&election&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Received&lower&prio&advert,&forcing&new&election&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200LB2Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&Received&higher&prio&advert&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&Entering&BACKUP&STATE&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&removing&protocol&VIPs.&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_healthcheckers[452]:&Netlink&reflector&reports&IP&10.1.1.200&removed查看VIP绑定情况，发现LB2上的VIP已经移除在LB1上LB2上执行ping&10.1.1.200这个VIP[lb1&~]$&ping&-c&5&10.1.1.200&PING&10.1.1.200&(10.1.1.200)&56(84)&bytes&of&data.&64&bytes&from&10.1.1.200:&icmp_seq=1&ttl=64&time=0.028&ms&64&bytes&from&10.1.1.200:&icmp_seq=2&ttl=64&time=0.020&ms&64&bytes&from&10.1.1.200:&icmp_seq=3&ttl=64&time=0.020&ms&64&bytes&from&10.1.1.200:&icmp_seq=4&ttl=64&time=0.021&ms&64&bytes&from&10.1.1.200:&icmp_seq=5&ttl=64&time=0.027&ms&&&---&10.1.1.200&ping&statistics&---&5&packets&transmitted,&5&received,&0%&packet&loss,&time&3999ms&rtt&min/avg/max/mdev&=&0.020/0.023/0.028/0.004&ms[lb2&~]$&ping&-c&5&10.1.1.200&&PING&10.1.1.200&(10.1.1.200)&56(84)&bytes&of&data.&&&---&10.1.1.200&ping&statistics&---&5&packets&transmitted,&0&received,&100%&packet&loss,&time&14000ms当LB1接管VIP的时候LB2居然无法ping通VIP，同样将LB1的Keepalived停掉，LB2可以接管VIP，但是在LB1上无法ping通这个VIP在LB1和LB2上进行抓包lb1&~]$&sudo&tcpdump&-vvv&&-ið1&host&10.1.1.17&tcpdump:&listening&onð1,&link-type&EN10MB&(Ethernet),&capture&size&65535&bytes&16:46:04.827357&IP&(tos&0xc0,&ttl&255,&id&328,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:05.827459&IP&(tos&0xc0,&ttl&255,&id&329,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:06.828234&IP&(tos&0xc0,&ttl&255,&id&330,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:07.828338&IP&(tos&0xc0,&ttl&255,&id&331,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&lb2&~]$&sudo&tcpdump&-vvv&-ið1&host&10.1.1.12&tcpdump:&listening&onð1,&link-type&EN10MB&(Ethernet),&capture&size&65535&bytes&16:48:07.000029&IP&(tos&0xc0,&ttl&255,&id&450,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:07.999539&IP&(tos&0xc0,&ttl&255,&id&451,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:08.999252&IP&(tos&0xc0,&ttl&255,&id&452,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:09.999560&IP&(tos&0xc0,&ttl&255,&id&453,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"在LB1和LB2所在物理机上的其他虚拟机进行VIP&ping测试，同样只能是LB1上绑定的VIP只能是LB1所在的物理机上的虚拟机可以ping通，LB2所在的物理机上的虚拟机无法ping通，反之也是一样有同行建议说VRRP和DHCP也有关系，经过查看对方提供的VM的IP地址居然是DHCP分配的，但是经过测试，VRRP和DHCP没有关系。线上环境最好不要使用DHCP来获取IP地址。8）请对方技术人员配合检查VIP无法ping通的问题最终查明对方的内网居然使用的虚拟网络，网关是没有实际作用的。所以部分虚拟机无法通过10.1.1.1这个网关去访问VIP。让对方虚拟机提供方的技术人员到服务器调试HAProxy+Keepalived，他们通过网络设置使得10.1.1.200这个VIP可以通过内网访问。但是当我测试时，发现当HAProxy挂掉后，Keepalived无法作VIP的切换。9）解决当HAProxy挂掉后，Keepalived无法对VIP切换的问题。经过反复测试，发现当Keepalived挂掉后，VIP可以切换。但是当HAProxy挂掉后，VIP无法切换。仔细检查配置文件和查阅相关资料，最终确定是Keepalived的weight和priority两个参数的大小设置问题。原来的配置文件中我设置LB1的weight为2，priority为100。LB2的weight为2，priority为99对方在调试的时候将LB1的priority更改为160.这样反复测试当LB1的HAProxy挂掉后，VIP都无法迁移到LB2上。将LB1上的priority更改为100就可以了。这里需要注意的是：主keepalived的priority值与vrrp_script的weight值相减的数字小于备用keepalived的priority&值即可！vrrp_script&里的script返回值为0时认为检测成功，其它值都会当成检测失败*&weight&为正时，脚本检测成功时此weight会加到priority上，检测失败时不加。主失败:&&&&&&&&&&&&主&priority&&从&priority&+&weight&时，主依然为主*&weight&为负时，脚本检测成功时此weight不影响priority，检测失败时priority&-&abs(weight)主失败:&&&&&&&&&&主&priority&-&abs(weight)&&从priority&主依然为主。最终的配置文件为：!&Configuration&File&for&keepalived&&&global_defs&{&&¬ification_email&{&&&&&&&&}&&¬ification_email_from&&&&smtp_server&127.0.0.1&&&smtp_connect_timeout&30&&&router_id&LB1_MASTER&}&&&&vrrp_script&chk_haproxy&{&&&&&script&"killall&-0&haproxy"&&&&&interval&2&&&&&weight&2&&&&&}&&&&&&&&&#设置外网的VIP&vrrp_instanceð0_VIP&{&&&&&state&MASTER&&&&&interfaceð0&&&&&virtual_router_id&51&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&unicast_src_ip&&8.8.8.6&&&&&&&&#使用VRRP的单播&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&8.8.8.7&&&&&&&&&&&&&&&&&}&&&&&virtual_ipaddress&{&&&&&8.8.8.8/25&&brd&8.8.8.255&&devð0&labelð0:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}&&&&&#设置内网的VIP&vrrp_instanceð1_VIP&{&&&&&state&MASTER&&&&&interfaceð1&&&&&virtual_router_id&52&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&unicast_src_ip&&10.1.1.12&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.17&&&&&&&&&&&&&&&&&}&&&&&virtual_ipaddress&{&&&&&10.1.1.200/24&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}&三&排查总结在配置Keepalived的时候，需要注意以下几点：A.内核开启IP转发和允许非本地IP绑定功能，如果是使用LVS的DR模式还需设置两个arp相关的参数。B.如果Keepalived所在网络不允许使用组播，可以使用VRRP单播C.需要注意主备的weight和priority的值，这两个值如果设置不合理可能会影响VIP的切换。D.如果使用的配置文件不是默认的配置文件，在启动Keepalived的时候需要使用&-f&参数指定配置文件。原地址：&&&&/Linux/981.htm 词汇网声明本文技术文章来自：51cto
上一集:没有了 下一集:
相关文章：&&&&
最新添加资讯
24小时热门资讯
附近好友搜索Ubuntu14.04&+&Keepalived1.2.13
172.18.8.74&(master，vip:172.18.8.100)
172.18.8.73&(slave,vip:172.18.8.100)
通过keepalived&实现redis主从备份零切换
keepalived.conf配置文件，如下：
!&Configuration&File&for&keepalived
global_defs&{
&&&router_id&ubuntu-lvs-74
vrrp_script&chk_redis&{
&&&&script&&/etc/keepalived/scripts/redis_check.sh&
&&&&interval&2
vrrp_instance&VI_1&{
&&&&state&MASTER
&&&&interfaceð0
&&&&virtual_router_id&51
&&&&priority&101&#&&备机&优先级为100
&&&&authentication&{
&&&&&&&&auth_type&PASS
&&&&&&&&auth_pass&redis
&&&&track_script&{
&&&&&&&chk_redis
&&&&virtual_ipaddress&{
&&&&&&&172.18.8.100/32
&&&¬ify_master&/etc/keepalived/scripts/redis_master.sh
&&&¬ify_backup&/etc/keepalived/scripts/redis_backup.sh
&&&¬ify_fault&&/etc/keepalived/scripts/redis_fault.sh
&&&¬ify_stop&&&/etc/keepalived/scripts/redis_stop.sh
virtual_server&172.18.8.100&6379&{
&&&&delay_loop&1
&&&&lb_algo&rr
&&&&lb_kind&DR&#NAT
&&&&#nat_mask&255.255.255.255
&&&&persistence_timeout&50
&&&&protocol&TCP
&&&&real_server&172.18.8.74&6379&{
&&&&&&&&weight&1
&&&&&&&&TCP_CHECK&{
&&&&&&&&&&connect_timeout&3
&&&&&&&&&&nb_get_retry&3
&&&&&&&&&&delay_before_retry&3
&&&&&&&&&&connect_port&6379
&&&&real_server&172.18.8.73&6379&{
&&&&&&&&weight&1
&&&&&&&&TCP_CHECK&{
&&&&&&&&&&connect_timeout&3
&&&&&&&&&&nb_get_retry&3
&&&&&&&&&&delay_before_retry&3
&&&&&&&&&&connect_port&6379
正确的结果应该是：
当前启动主keepalived时候，虚拟主机IP应该被主机监听绑定，备机不绑定虚拟IP；当主机keepalived宕掉时，备机进行绑定VIP
1、为什么我keepalived主备都会监听虚拟IP？
#sudo&ip&a
都是输出：[code]root@ubuntu-lvs-74:/opt/lvs#&ip&a
1:&lo:&&LOOPBACK,UP,LOWER_UP&&mtu&65536&qdisc&noqueue&state&UNKNOWN&group&default&
&&&&link/loopback&00:00:00:00:00:00&brd&00:00:00:00:00:00
&&&&inet&127.0.0.1/8&scope&host&lo
&&&&&&&valid_lft&forever&preferred_lft&forever
&&&inet&172.18.8.100/32&brd&172.18.8.100&scope&global&lo:0
&&&&&&&valid_lft&forever&preferred_lft&forever
&&&&inet6&::1/128&scope&host&[/code]/etc/sysctl.conf&设置了：
net.ipv4.ip_nonlocal_bind&=&1
VIP设置如下,ifconfig：
root@ubuntu-lvs-74:/opt/lvs#&ifconfig
eth0&&&&&&Link&encap:Ethernet&&HWaddr&52:54:00:ee:21:49&&
&&&&&&&&&&inet&addr:172.18.8.74&&Bcast:172.18.8.127&&Mask:255.255.255.128
&&&&&&&&&&inet6&addr:&fe80::5054:ff:feee:2149/64&Scope:Link
&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1
&&&&&&&&&&RX&packets:3038779&errors:0&dropped:1356&overruns:0&frame:0
&&&&&&&&&&TX&packets:564682&errors:0&dropped:0&overruns:0&carrier:0
&&&&&&&&&&collisions:0&txqueuelen:1000&
&&&&&&&&&&RX&bytes:&(155.4&MB)&&TX&bytes:.2&MB)
lo&&&&&&&&Link&encap:Local&Loopback&&
&&&&&&&&&&inet&addr:127.0.0.1&&Mask:255.0.0.0
&&&&&&&&&&inet6&addr:&::1/128&Scope:Host
&&&&&&&&&&UP&LOOPBACK&RUNNING&&MTU:65536&&Metric:1
&&&&&&&&&&RX&packets:703904&errors:0&dropped:0&overruns:0&frame:0
&&&&&&&&&&TX&packets:703904&errors:0&dropped:0&overruns:0&carrier:0
&&&&&&&&&&collisions:0&txqueuelen:0&
&&&&&&&&&&RX&bytes:.4&MB)&&TX&bytes:.4&MB)
lo:0&&&&&&Link&encap:Local&Loopback&&
&&&&&&&&&&inet&addr:172.18.8.100&&Mask:255.255.255.255
&&&&&&&&&&UP&LOOPBACK&RUNNING&&MTU:65536&&Metric:1请教，这是哪里出了问题了？
2、keepalived启动后，出现VRRP_Instance(VI_1)&Now&in&FAULT&state
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Netlink&reflector&reports&IP&fe80::5054:ff:feee:2149&added
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Registering&Kernel&netlink&reflector
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Registering&Kernel&netlink&command&channel
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Opening&file&'/etc/keepalived/keepalived.conf'.
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Configuration&is&using&:&13613&Bytes
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Using&LinkWatch&kernel&netlink&reflector...
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Activating&healthchecker&for&service&[172.18.8.74]:6379
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Activating&healthchecker&for&service&[172.18.8.73]:6379
Dec&&6&21:01:44&ubuntu-lvs-74&Keepalived_vrrp[9802]:&VRRP_Instance(VI_1)&Now&in&FAULT&state
Dec&&6&21:01:44&ubuntu-lvs-74&Keepalived_vrrp[9802]:&Opening&script&file&/etc/keepalived/scripts/redis_fault.sh
Destination&&&&&Gateway&&&&&&&&&Genmask&&&&&&&&&&&&&&Flags&&Metric&Ref&&&&Use&Iface
default&&&&&&&&&&&&172.18.8.1&&&&&&0.0.0.0&&&&&&&&&&&&&&&&UG&&&&&0&&&&&&0&&&&&&&&0&&&ð0
172.18.8.0&&&&&&*&&&&&&&&&&&&&&&&&&&&255.255.255.128&U&&&&&&&0&&&&&&0&&&&&&&&0&&&ð0
172.18.8.100&&*&&&&&&&&&&&&&&&&&&&&255.255.255.255&UH&&&&&0&&&&&&0&&&&&&&&0&&&&&lo
root@ubuntu-lvs-74:/opt/lvs#&ipvsadm&-ln
IP&Virtual&Server&version&1.2.1&(size=4096)
Prot&LocalAddress:Port&Scheduler&Flags
&&-&&RemoteAddress:Port&&&&&&&&&&&Forward&Weight&ActiveConn&InActConn
TCP&&172.18.8.100:80&rr
&&-&&172.18.8.73:80&&&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
&&-&&172.18.8.74:80&&&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
TCP&&172.18.8.100:6379&rr&persistent&50
&&-&&172.18.8.73:6379&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
&&-&&172.18.8.74:6379&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0
VIP:172.18.8.100&，在73,74之间可以互相ping通
请教，VRRP_Instance(VI_1)&Now&in&FAULT&state&可能是哪方面原因造成的？
回复讨论(解决方案)
1、router_id&别重复
2、主机&state&MASTER&&&备机&state&BACKUP
3、lo0上的那个VIP是做心跳的，eth0上的VIP才是宕机之后做切换的}
Keepalived无法绑定VIP故障排查经历
责任编辑：词汇网 发表时间： 13:29:41
一&故障描述我在台湾合作方给定的两台虚拟机上部署HAProxy+Keepalived负载均衡高可用方案。在配置完Keepalived后，重新启动Keepalived，Keepalived没有绑定VIP。Keepalived执行程序路径为/data/app_platform/keepalived/sbin/keepalived配置文件路径为/data/app_platform/keepalived/conf/keepalived.conf&&Keepalived的启动脚本为/etc/init.d/keepalivedkeepalived.conf的内容LB1&Master!&Configuration&File&for&keepalived&&&global_defs&{&&¬ification_email&{&&&&&&&&}&&¬ification_email_from&&&&smtp_server&127.0.0.1&&&smtp_connect_timeout&30&&&router_id&LB1_MASTER&}&&&&vrrp_script&chk_haproxy&{&&&&&&&&&script&"killall&-0&haproxy"&&&&&&&&&interval&2&&&&&weight&2&&&&&}&&&&&&&&&vrrp_instance&VI_1&{&&&&&state&MASTER&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&virtual_ipaddress&{&&&&&&&10.1.1.200/24&&&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}重新启动Keepalived查看日志Mar&&3&18:09:00&cv-1&Keepalived[20138]:&Stopping&Keepalived&v1.2.15&(02/28,2015)&Mar&&3&18:09:00&cv-1&Keepalived[20259]:&Starting&Keepalived&v1.2.15&(02/28,2015)&Mar&&3&18:09:00&cv-1&Keepalived[20260]:&Starting&Healthcheck&child&process,&pid=20261&Mar&&3&18:09:00&cv-1&Keepalived[20260]:&Starting&VRRP&child&process,&pid=20262&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&Kernel&netlink&reflector&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&Kernel&netlink&command&channel&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Registering&gratuitous&ARP&shared&channel&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Registering&Kernel&netlink&reflector&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Registering&Kernel&netlink&command&channel&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Configuration&is&using&:&3924&Bytes&Mar&&3&18:09:00&cv-1&Keepalived_healthcheckers[20261]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Configuration&is&using&:&55712&Bytes&Mar&&3&18:09:00&cv-1&Keepalived_vrrp[20262]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&3&18:09:18&cv-1&kernel:&__ratelimit:&1964&callbacks&suppressed&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.&Mar&&3&18:09:18&cv-1&kernel:&Neighbour&table&overflow.查看VIP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13没有VIP绑定二&排查过程1）检查VIP的配置情况向合作方确认提供的VIP的详细情况IPADDR&&10.1.1.200NETMASK&&255.255.255.0GATEWAY&&10.1.1.1Brodcast&&10.1.1.255&&这里设置的是10.1.1.200/24&&&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip2）检查iptables和selinux的设置情况$&sudo&service&iptables&stop&$&sudo&setenforce&0&setenforce:&SELinux&is&disabled如果非要开启iptables的话，需要作些设定iptables&-I&INPUT&-ið1&-d&224.0.0.0/8&-j&ACCEPT&service&iptables&savekeepalived使用224.0.0.18作为Master和Backup健康检查的通信IP3）检查相关的内核参数HAProxy+Keepalived架构需要注意的内核参数有：#&Controls&IP&packet&forwardingnet.ipv4.ip_forward&=&1开启IP转发功能net.ipv4.ip_nonlocal_bind&=&1开启允许绑定非本机的IP如果使用LVS的DR或者TUN模式结合Keepalived需要在后端真实服务器上特别设置两个arp相关的参数。这里也设置好。net.ipv4.conf.lo.arp_ignore&=&1net.ipv4.conf.lo.arp_announce&=&2net.ipv4.conf.all.arp_ignore&=&1net.ipv4.conf.all.arp_announce&=&24）检查VRRP的设置情况LB1&Masterstate&MASTER&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&100LB2&Backupstate&BACKUP&&&&&interfaceð1&&&&&virtual_router_id&51&&&&&priority&99Master和Backup的virtual_router_id需要一样，priority需要不一样，数字越大，优先级越高5）怀疑是编译安装Keepalived版本出现了问题重新下载并编译2.1.13的版本，并重新启动keepalived，VIP仍然没有被绑定。线上有个平台的keepalived是通过yum安装的，于是打算先用yum安装keepalived后将配置文件复制过去看看是否可以绑定VIPrpm&-ivh&http://ftp.linux.ncsu.edu/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm&yum&-y&install&keepalivedcp&/data/app_platform/keepalived/conf/keepalived.conf&&/etc/keepalived/keepalived.conf重新启动keepalived然后查看日志Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Registering&Kernel&netlink&reflector&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Registering&Kernel&netlink&command&channel&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Opening&file&"/etc/keepalived/keepalived.conf".&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Configuration&is&using&:&65250&Bytes&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Opening&file&"/etc/keepalived/keepalived.conf".&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Configuration&is&using&:&7557&Bytes&Mar&&4&16:42:46&xxxxx&Keepalived_healthcheckers[17332]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&4&16:42:46&xxxxx&Keepalived_vrrp[17333]:&VRRP_Script(chk_haproxy)&succeeded&Mar&&4&16:42:47&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&4&16:42:48&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&4&16:42:48&xxxxx&Keepalived_healthcheckers[17332]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&4&16:42:53&xxxxx&Keepalived_vrrp[17333]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200再查看IP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13再通过yum将keepalived卸载掉yum&remove&keepalived恢复到原来的启动脚本/etc/init.d/keepalived重新启动keepalived后还是无法绑定VIP怀疑是keepalived启动脚本/etc/init.d/keepalived的问题检查/etc/init.d/keepalived#&Source&function&library.&.&/etc/rc.d/init.d/functions&&&exec="/data/app_platform/keepalived/sbin/keepalived"&prog="keepalived"&config="/data/app_platform/keepalived/conf/keepalived.conf"&&&[&-e&/etc/sysconfig/$prog&]&&&&.&/etc/sysconfig/$prog&&&lockfile=/var/lock/subsys/keepalived&&&start()&{&&&&&[&-x&$exec&]&||&exit&5&&&&&[&-e&$config&]&||&exit&6&&&&&echo&-n&$"Starting&$prog:&"&&&&&daemon&$exec&$KEEPALIVED_OPTIONS&&&&&retval=$?&&&&&echo&&&&&[&$retval&-eq&0&]&&&&touch&$lockfile&&&&&return&$retval&}关键是这一行daemon&$exec&$KEEPALIVED_OPTIONS由于没有复制/etc/sysconfig/keepalived,所以将直接执行damon&/data/app_platform/keepalived/sbin/keepalived由于keepalived默认使用的是/etc/keepalived/keepalived.conf作为配置文件，而这里指定了不同的配置文件，所以要修改成为daemon&$exec&-D&-f&$config重新启动keepalived，查看日志和VIP绑定情况$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:136）将LB2&Backup的keepalived启动脚本也修改一下，观察VIP接管情况查看LB1&Master$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13查看LB2&Backup$&ifconfigð1:vipð1:vip&&Link&encap:Ethernet&&HWaddr&00:16:3E:F2:37:6B&&&&&&&&&&&&inet&addr:10.1.1.200&&Bcast:10.1.1.255&&Mask:255.255.255.0&&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1&&&&&&&&&&&Interrupt:13问题出现了，LB1&Master和LB2&Backup都绑定了VIP&10.1.1.200，这是不正常的！！！！在LB1和LB2上登录10.1.1.200看看[lb1&~]$&ssh&10.1.1.200&&Last&login:&Wed&Mar&&4&17:31:33&2015&from&10.1.1.200&[lb1&~]$[lb2&~]$&ssh&10.1.1.200&Last&login:&Wed&Mar&&4&17:54:57&2015&from&101.95.153.246&[b2&&~]$在LB1上停掉keepalived，ping下10.1.1.200这个IP，发现无法ping通在LB2上停掉keepalived，ping下10.1.1.200这个IP，发现也无法ping通然后开启LB1上的keepalived，LB1上可以ping通10.1.1.200,LB2上不行开启LB2上的keepalived，LB2上可以ping通10.1.1.200由此得出，LB1和LB2各自都将VIP&10.1.1.200绑定到本机的eth1网卡上。两台主机并没有VRRP通信，没有VRRP的优先级比较。7)排查影响VRRP通信的原因重新启动LB1&Master的Keepalived查看日志Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&Configuration&is&using&:&65410&Bytes&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&5&15:45:36&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Script(chk_haproxy)&succeeded&Mar&&5&15:45:37&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&15:45:38&gintama-taiwan-lb1&Keepalived_healthcheckers[32302]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&5&15:45:43&gintama-taiwan-lb1&Keepalived_vrrp[32303]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200发现LB1&Master上的Keepalived直接进入Master状态，然后接管VIP再重新启动LB2&Backup上的Keepalived，查看日志Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&Configuration&is&using&:&65408&Bytes&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Entering&BACKUP&STATE&Mar&&5&15:47:42&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(0),&fd(10,11)]&Mar&&5&15:47:46&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Entering&MASTER&STATE&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&15:47:47&gintama-taiwan-lb2&Keepalived_healthcheckers[30618]:&Netlink&reflector&reports&IP&10.1.1.200&added&Mar&&5&15:47:52&gintama-taiwan-lb2&Keepalived_vrrp[30619]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200可以看到LB2上的Keepalived先进入BACKUP状态，然后又转为MASTER状态，然后接管VIP这样就说明VRRP组播有问题。既然VRRP组播有问题，就尝试使用单播发送VRRP报文。修改LB1和LB2的配置LB1添加以下配置unicast_src_ip&&10.1.1.12&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.17&&&&&&&&&&&&&&&&&}LB2添加以下配置unicast_src_ip&&10.1.1.17&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.12&&&&&&&&&&&&&&&&&}unicast_src_ip&表示发送VRRP单播报文使用的源IP地址unicast_peer&表示对端接收VRRP单播报文的IP地址然后各自重新加载keepalived，观察日志LB1Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&setting&protocol&VIPs.&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Script(chk_haproxy)&considered&successful&on&reload&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&Configuration&is&using&:&65579&Bytes&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&Using&LinkWatch&kernel&netlink&reflector...&Mar&&5&16:13:35&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP&sockpool:&[ifindex(3),&proto(112),&unicast(1),&fd(10,11)]&Mar&&5&16:13:36&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Transition&to&MASTER&STATE&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Received&lower&prio&advert,&forcing&new&election&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Received&lower&prio&advert,&forcing&new&election&Mar&&5&16:13:48&gintama-taiwan-lb1&Keepalived_vrrp[2551]:&VRRP_Instance(VI_1)&Sending&gratuitous&ARPs&onð1&for&10.1.1.200LB2Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&Received&higher&prio&advert&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&Entering&BACKUP&STATE&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_vrrp[453]:&VRRP_Instance(VI_1)&removing&protocol&VIPs.&Mar&&5&16:13:48&gintama-taiwan-lb2&Keepalived_healthcheckers[452]:&Netlink&reflector&reports&IP&10.1.1.200&removed查看VIP绑定情况，发现LB2上的VIP已经移除在LB1上LB2上执行ping&10.1.1.200这个VIP[lb1&~]$&ping&-c&5&10.1.1.200&PING&10.1.1.200&(10.1.1.200)&56(84)&bytes&of&data.&64&bytes&from&10.1.1.200:&icmp_seq=1&ttl=64&time=0.028&ms&64&bytes&from&10.1.1.200:&icmp_seq=2&ttl=64&time=0.020&ms&64&bytes&from&10.1.1.200:&icmp_seq=3&ttl=64&time=0.020&ms&64&bytes&from&10.1.1.200:&icmp_seq=4&ttl=64&time=0.021&ms&64&bytes&from&10.1.1.200:&icmp_seq=5&ttl=64&time=0.027&ms&&&---&10.1.1.200&ping&statistics&---&5&packets&transmitted,&5&received,&0%&packet&loss,&time&3999ms&rtt&min/avg/max/mdev&=&0.020/0.023/0.028/0.004&ms[lb2&~]$&ping&-c&5&10.1.1.200&&PING&10.1.1.200&(10.1.1.200)&56(84)&bytes&of&data.&&&---&10.1.1.200&ping&statistics&---&5&packets&transmitted,&0&received,&100%&packet&loss,&time&14000ms当LB1接管VIP的时候LB2居然无法ping通VIP，同样将LB1的Keepalived停掉，LB2可以接管VIP，但是在LB1上无法ping通这个VIP在LB1和LB2上进行抓包lb1&~]$&sudo&tcpdump&-vvv&&-ið1&host&10.1.1.17&tcpdump:&listening&onð1,&link-type&EN10MB&(Ethernet),&capture&size&65535&bytes&16:46:04.827357&IP&(tos&0xc0,&ttl&255,&id&328,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:05.827459&IP&(tos&0xc0,&ttl&255,&id&329,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:06.828234&IP&(tos&0xc0,&ttl&255,&id&330,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:46:07.828338&IP&(tos&0xc0,&ttl&255,&id&331,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&lb2&~]$&sudo&tcpdump&-vvv&-ið1&host&10.1.1.12&tcpdump:&listening&onð1,&link-type&EN10MB&(Ethernet),&capture&size&65535&bytes&16:48:07.000029&IP&(tos&0xc0,&ttl&255,&id&450,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:07.999539&IP&(tos&0xc0,&ttl&255,&id&451,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:08.999252&IP&(tos&0xc0,&ttl&255,&id&452,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"&16:48:09.999560&IP&(tos&0xc0,&ttl&255,&id&453,&offset&0,&flags&[none],&proto&VRRP&(112),&length&40)&&&&&10.1.1.12&>&10.1.1.17:&VRRPv2,&Advertisement,&vrid&51,&prio&102,&authtype&simple,&intvl&1s,&length&20,&addrs:&10.1.1.200&auth&"1111^@^@^@^@"在LB1和LB2所在物理机上的其他虚拟机进行VIP&ping测试，同样只能是LB1上绑定的VIP只能是LB1所在的物理机上的虚拟机可以ping通，LB2所在的物理机上的虚拟机无法ping通，反之也是一样有同行建议说VRRP和DHCP也有关系，经过查看对方提供的VM的IP地址居然是DHCP分配的，但是经过测试，VRRP和DHCP没有关系。线上环境最好不要使用DHCP来获取IP地址。8）请对方技术人员配合检查VIP无法ping通的问题最终查明对方的内网居然使用的虚拟网络，网关是没有实际作用的。所以部分虚拟机无法通过10.1.1.1这个网关去访问VIP。让对方虚拟机提供方的技术人员到服务器调试HAProxy+Keepalived，他们通过网络设置使得10.1.1.200这个VIP可以通过内网访问。但是当我测试时，发现当HAProxy挂掉后，Keepalived无法作VIP的切换。9）解决当HAProxy挂掉后，Keepalived无法对VIP切换的问题。经过反复测试，发现当Keepalived挂掉后，VIP可以切换。但是当HAProxy挂掉后，VIP无法切换。仔细检查配置文件和查阅相关资料，最终确定是Keepalived的weight和priority两个参数的大小设置问题。原来的配置文件中我设置LB1的weight为2，priority为100。LB2的weight为2，priority为99对方在调试的时候将LB1的priority更改为160.这样反复测试当LB1的HAProxy挂掉后，VIP都无法迁移到LB2上。将LB1上的priority更改为100就可以了。这里需要注意的是：主keepalived的priority值与vrrp_script的weight值相减的数字小于备用keepalived的priority&值即可！vrrp_script&里的script返回值为0时认为检测成功，其它值都会当成检测失败*&weight&为正时，脚本检测成功时此weight会加到priority上，检测失败时不加。主失败:&&&&&&&&&&&&主&priority&&从&priority&+&weight&时，主依然为主*&weight&为负时，脚本检测成功时此weight不影响priority，检测失败时priority&-&abs(weight)主失败:&&&&&&&&&&主&priority&-&abs(weight)&&从priority&主依然为主。最终的配置文件为：!&Configuration&File&for&keepalived&&&global_defs&{&&¬ification_email&{&&&&&&&&}&&¬ification_email_from&&&&smtp_server&127.0.0.1&&&smtp_connect_timeout&30&&&router_id&LB1_MASTER&}&&&&vrrp_script&chk_haproxy&{&&&&&script&"killall&-0&haproxy"&&&&&interval&2&&&&&weight&2&&&&&}&&&&&&&&&#设置外网的VIP&vrrp_instanceð0_VIP&{&&&&&state&MASTER&&&&&interfaceð0&&&&&virtual_router_id&51&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&unicast_src_ip&&8.8.8.6&&&&&&&&#使用VRRP的单播&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&8.8.8.7&&&&&&&&&&&&&&&&&}&&&&&virtual_ipaddress&{&&&&&8.8.8.8/25&&brd&8.8.8.255&&devð0&labelð0:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}&&&&&#设置内网的VIP&vrrp_instanceð1_VIP&{&&&&&state&MASTER&&&&&interfaceð1&&&&&virtual_router_id&52&&&&&priority&100&&&&&advert_int&1&&&&&authentication&{&&&&&&&&&auth_type&PASS&&&&&&&&&auth_pass&1111&&&&&}&&&&&unicast_src_ip&&10.1.1.12&&&&&unicast_peer&{&&&&&&&&&&&&&&&&&&&10.1.1.17&&&&&&&&&&&&&&&&&}&&&&&virtual_ipaddress&{&&&&&10.1.1.200/24&&&&brd&10.1.1.255&&&&&&devð1&labelð1:vip&&&&&&&}&&&&&&&track_script&{&&&&&&&&&chk_haproxy&&&&&&&&&&&&&&&&&}&}&三&排查总结在配置Keepalived的时候，需要注意以下几点：A.内核开启IP转发和允许非本地IP绑定功能，如果是使用LVS的DR模式还需设置两个arp相关的参数。B.如果Keepalived所在网络不允许使用组播，可以使用VRRP单播C.需要注意主备的weight和priority的值，这两个值如果设置不合理可能会影响VIP的切换。D.如果使用的配置文件不是默认的配置文件，在启动Keepalived的时候需要使用&-f&参数指定配置文件。原地址：&&&&/Linux/981.htm 词汇网声明本文技术文章来自：51cto
上一集:没有了 下一集:
相关文章：&&&&
最新添加资讯
24小时热门资讯
附近好友搜索Ubuntu14.04&+&Keepalived1.2.13
172.18.8.74&(master，vip:172.18.8.100)
172.18.8.73&(slave,vip:172.18.8.100)
通过keepalived&实现redis主从备份零切换
keepalived.conf配置文件，如下：
!&Configuration&File&for&keepalived
global_defs&{
&&&router_id&ubuntu-lvs-74
vrrp_script&chk_redis&{
&&&&script&&/etc/keepalived/scripts/redis_check.sh&
&&&&interval&2
vrrp_instance&VI_1&{
&&&&state&MASTER
&&&&interfaceð0
&&&&virtual_router_id&51
&&&&priority&101&#&&备机&优先级为100
&&&&authentication&{
&&&&&&&&auth_type&PASS
&&&&&&&&auth_pass&redis
&&&&track_script&{
&&&&&&&chk_redis
&&&&virtual_ipaddress&{
&&&&&&&172.18.8.100/32
&&&¬ify_master&/etc/keepalived/scripts/redis_master.sh
&&&¬ify_backup&/etc/keepalived/scripts/redis_backup.sh
&&&¬ify_fault&&/etc/keepalived/scripts/redis_fault.sh
&&&¬ify_stop&&&/etc/keepalived/scripts/redis_stop.sh
virtual_server&172.18.8.100&6379&{
&&&&delay_loop&1
&&&&lb_algo&rr
&&&&lb_kind&DR&#NAT
&&&&#nat_mask&255.255.255.255
&&&&persistence_timeout&50
&&&&protocol&TCP
&&&&real_server&172.18.8.74&6379&{
&&&&&&&&weight&1
&&&&&&&&TCP_CHECK&{
&&&&&&&&&&connect_timeout&3
&&&&&&&&&&nb_get_retry&3
&&&&&&&&&&delay_before_retry&3
&&&&&&&&&&connect_port&6379
&&&&real_server&172.18.8.73&6379&{
&&&&&&&&weight&1
&&&&&&&&TCP_CHECK&{
&&&&&&&&&&connect_timeout&3
&&&&&&&&&&nb_get_retry&3
&&&&&&&&&&delay_before_retry&3
&&&&&&&&&&connect_port&6379
正确的结果应该是：
当前启动主keepalived时候，虚拟主机IP应该被主机监听绑定，备机不绑定虚拟IP；当主机keepalived宕掉时，备机进行绑定VIP
1、为什么我keepalived主备都会监听虚拟IP？
#sudo&ip&a
都是输出：[code]root@ubuntu-lvs-74:/opt/lvs#&ip&a
1:&lo:&&LOOPBACK,UP,LOWER_UP&&mtu&65536&qdisc&noqueue&state&UNKNOWN&group&default&
&&&&link/loopback&00:00:00:00:00:00&brd&00:00:00:00:00:00
&&&&inet&127.0.0.1/8&scope&host&lo
&&&&&&&valid_lft&forever&preferred_lft&forever
&&&inet&172.18.8.100/32&brd&172.18.8.100&scope&global&lo:0
&&&&&&&valid_lft&forever&preferred_lft&forever
&&&&inet6&::1/128&scope&host&[/code]/etc/sysctl.conf&设置了：
net.ipv4.ip_nonlocal_bind&=&1
VIP设置如下,ifconfig：
root@ubuntu-lvs-74:/opt/lvs#&ifconfig
eth0&&&&&&Link&encap:Ethernet&&HWaddr&52:54:00:ee:21:49&&
&&&&&&&&&&inet&addr:172.18.8.74&&Bcast:172.18.8.127&&Mask:255.255.255.128
&&&&&&&&&&inet6&addr:&fe80::5054:ff:feee:2149/64&Scope:Link
&&&&&&&&&&UP&BROADCAST&RUNNING&MULTICAST&&MTU:1500&&Metric:1
&&&&&&&&&&RX&packets:3038779&errors:0&dropped:1356&overruns:0&frame:0
&&&&&&&&&&TX&packets:564682&errors:0&dropped:0&overruns:0&carrier:0
&&&&&&&&&&collisions:0&txqueuelen:1000&
&&&&&&&&&&RX&bytes:&(155.4&MB)&&TX&bytes:.2&MB)
lo&&&&&&&&Link&encap:Local&Loopback&&
&&&&&&&&&&inet&addr:127.0.0.1&&Mask:255.0.0.0
&&&&&&&&&&inet6&addr:&::1/128&Scope:Host
&&&&&&&&&&UP&LOOPBACK&RUNNING&&MTU:65536&&Metric:1
&&&&&&&&&&RX&packets:703904&errors:0&dropped:0&overruns:0&frame:0
&&&&&&&&&&TX&packets:703904&errors:0&dropped:0&overruns:0&carrier:0
&&&&&&&&&&collisions:0&txqueuelen:0&
&&&&&&&&&&RX&bytes:.4&MB)&&TX&bytes:.4&MB)
lo:0&&&&&&Link&encap:Local&Loopback&&
&&&&&&&&&&inet&addr:172.18.8.100&&Mask:255.255.255.255
&&&&&&&&&&UP&LOOPBACK&RUNNING&&MTU:65536&&Metric:1请教，这是哪里出了问题了？
2、keepalived启动后，出现VRRP_Instance(VI_1)&Now&in&FAULT&state
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Netlink&reflector&reports&IP&fe80::5054:ff:feee:2149&added
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Registering&Kernel&netlink&reflector
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Registering&Kernel&netlink&command&channel
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Opening&file&'/etc/keepalived/keepalived.conf'.
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Configuration&is&using&:&13613&Bytes
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Using&LinkWatch&kernel&netlink&reflector...
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Activating&healthchecker&for&service&[172.18.8.74]:6379
Dec&&6&21:01:43&ubuntu-lvs-74&Keepalived_healthcheckers[9801]:&Activating&healthchecker&for&service&[172.18.8.73]:6379
Dec&&6&21:01:44&ubuntu-lvs-74&Keepalived_vrrp[9802]:&VRRP_Instance(VI_1)&Now&in&FAULT&state
Dec&&6&21:01:44&ubuntu-lvs-74&Keepalived_vrrp[9802]:&Opening&script&file&/etc/keepalived/scripts/redis_fault.sh
Destination&&&&&Gateway&&&&&&&&&Genmask&&&&&&&&&&&&&&Flags&&Metric&Ref&&&&Use&Iface
default&&&&&&&&&&&&172.18.8.1&&&&&&0.0.0.0&&&&&&&&&&&&&&&&UG&&&&&0&&&&&&0&&&&&&&&0&&&ð0
172.18.8.0&&&&&&*&&&&&&&&&&&&&&&&&&&&255.255.255.128&U&&&&&&&0&&&&&&0&&&&&&&&0&&&ð0
172.18.8.100&&*&&&&&&&&&&&&&&&&&&&&255.255.255.255&UH&&&&&0&&&&&&0&&&&&&&&0&&&&&lo
root@ubuntu-lvs-74:/opt/lvs#&ipvsadm&-ln
IP&Virtual&Server&version&1.2.1&(size=4096)
Prot&LocalAddress:Port&Scheduler&Flags
&&-&&RemoteAddress:Port&&&&&&&&&&&Forward&Weight&ActiveConn&InActConn
TCP&&172.18.8.100:80&rr
&&-&&172.18.8.73:80&&&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
&&-&&172.18.8.74:80&&&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
TCP&&172.18.8.100:6379&rr&persistent&50
&&-&&172.18.8.73:6379&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0&&&&&&&&&
&&-&&172.18.8.74:6379&&&&&&&&&&&&&Route&&&1&&&&&&0&&&&&&&&&&0
VIP:172.18.8.100&，在73,74之间可以互相ping通
请教，VRRP_Instance(VI_1)&Now&in&FAULT&state&可能是哪方面原因造成的？
回复讨论(解决方案)
1、router_id&别重复
2、主机&state&MASTER&&&备机&state&BACKUP
3、lo0上的那个VIP是做心跳的，eth0上的VIP才是宕机之后做切换的}
我要回帖
更多关于 keepalived 配置vip 的文章
更多推荐
- ·wps中切换工作簿的办公软件快捷键大全表能不能自定更换？
- ·认观世认观音菩萨做干娘有什么说法为干妈，会有功德吗？
- ·从负极到正极，电源的正极电势高还是负极电视高内部的电势是怎么升高的？必须有个电场的环境，被移动的正电荷移动时电势才能提升啊？
- ·打算想开一家女装二三线品牌加盟实体店店，请问哪个品牌有个性？
- ·2019年“大国工匠2023年度人物发布仪式人物年度人物”揭晓,他们在各自领域是怎样的人物?_百度...
- ·河南焦作市单光黑纸哪里有？
- ·有点闲置的资金可以在东方金钰股份有限公司投资吗？
- ·定州市昌二十二冶润达物业业
- ·河南温县康乐机械厂兴华和港温机械厂哪个好
- ·在深圳买4000的社保15年了,2016年60岁退休社保不够15年能领多少工资
- ·小城镇规划那种餐饮更受喜爱
- ·2010部门中期财政规划报告告
- ·安徽黄山胶囊有限公司没有上新三板
- ·芝麻642，来个借贷宝押金放米的，无前期无押金的我们再谈别的，都不是傻子，
- ·求大神们推荐一个天津做网站公司靠谱的公司？
- ·销售这么赚，大学生怎么不愿做 帅小伙卖房未满两年卖房自己买豪车
- ·河南火车罐体东莞废钢材回收收
- ·1800/50利用商的按不变价格计算计算
- ·docker keepalived vip 不通怎么绑定
- ·快手解封申诉直播被永久封了，可以解开吗，需要多久。已经在申请解封当中了
- ·中山装口袋做法图片下口袋做法
- ·乱轰三国志10突骑兵 给骑兵加护甲给武将加吗
- ·nevergone天梯属性多少层有剑灵
- ·为什么下载了应用宝还是不能玩天天酷跑下载安装
- ·奥秘角子机游戏娱 乐 场怎么无法显示?有什么更新
- ·命运冠位指定新手首抽攻略 fgo命运冠位指定怎么玩
- ·s6世界s6总决赛rng tsm rng vs tsm为什么不用加赛
- ·天使之剑动漫全集山洞通行证在那里?
- ·攻城掠地珍宝介绍三珍宝比二珍宝提升大不大
- ·大话手游转生修正西游手游敏系单位和血系单位该如何选择前世修正？
- ·黑魂3打了不死队还会在法兰要塞被黑魂3隆道尔的白影影入侵吗
- ·如果你下辈子有两种选择让你选你会选哪个?a德古拉 b狼人杀女巫自救 c女巫
- ·葡萄牙自由行攻略，奥比杜斯小镇的特色是什么，求详细攻略？
- ·九十月份去沈阳南湖玩有沈阳海盗船银饰之类的吗
