keepalived双主配置

最新推荐文章于 2024-04-18 04:29:05 发布
最新推荐文章于 2024-04-18 04:29:05 发布
阅读量484 收藏
点赞数
分类专栏： linux 文章标签： keepalived
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_39567748/article/details/100181095
版权

基础的已经在前一篇文章介绍过，链接如下：
https://blog.csdn.net/qq_39567748/article/details/100180809

服务器名称IP地址VIP网卡名称备注
local-100-101172.20.100.101172.20.100.250eth0主
docker-100-108172.20.100.108172.20.100.251eth0主

1、配置如下：

双主模式
[root@localhost-100-101 keepalived]# cat keepalived.conf 
! Configuration File for keepalived

global_defs {
   notification_email {
   15321375963@139.com
   }
   notification_email_from 15321375963@189.cn 
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id 172.20.100.101
   #vrrp_skip_check_adv_addr
   #vrrp_strict
   #vrrp_garp_interval 0
   #vrrp_gna_interval 0
}

vrrp_instance VI_1 {
    state MASTER
    interface eth0
    lvs_sync_daemon_inteface eth0
    virtual_router_id 51
    nopreempt
    preempt delay 60
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass rongkang
    }
    virtual_ipaddress {
        172.20.100.250/24
    }
}

vrrp_instance VI_2 {
    state BACKUP
    interface eth0
    lvs_sync_daemon_inteface eth0
    virtual_router_id 52
    nopreempt
    preempt delay 60
    priority 90
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass rongkang
    }
    virtual_ipaddress {
        172.20.100.251/24
    }
}




[root@docker-100-108 ~]# cat /etc/keepalived/keepalived.conf 
! Configuration File for keepalived

global_defs {
   notification_email {
   15321375963@139.com
   }
   notification_email_from 15321375963@189.cn
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id 172.20.100.108
   #vrrp_skip_check_adv_addr
   #vrrp_strict
   #vrrp_garp_interval 0
   #vrrp_gna_interval 0
}

vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    lvs_sync_daemon_inteface eth0
    virtual_router_id 51
    nopreempt
    preempt delay 60
    priority 90
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass rongkang
    }
    virtual_ipaddress {
        172.20.100.250/24
    }
}

vrrp_instance VI_2 {
    state MASTER
    interface eth0
    lvs_sync_daemon_inteface eth0
    virtual_router_id 52
    nopreempt
    preempt delay 60
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass rongkang
    }
    virtual_ipaddress {
        172.20.100.251/24
    }
}
[root@docker-100-108 ~]#

2、启动服务

systemctl start keepalived
systemctl enable keepalived

3、查看网卡
localhost-100-101

[root@localhost-100-101 ~]# ip add
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:c6:4d:82:b3:00 brd ff:ff:ff:ff:ff:ff
    inet 172.20.100.101/24 brd 172.20.100.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet 172.20.100.250/24 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::c14a:4493:465b:199b/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

docker-100-108

eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether fa:ca:f2:59:ee:00 brd ff:ff:ff:ff:ff:ff
    inet 172.20.100.108/24 brd 172.20.100.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 172.20.100.251/24 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a21e:eb94:4c03:739f/64 scope link 
       valid_lft forever preferred_lft forever
    inet6 fe80::c14a:4493:465b:199b/64 scope link tentative dadfailed 
       valid_lft forever preferred_lft forever

4、抓包查看

[root@localhost-100-101 ~]# tcpdump -i eth0 vrrp -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
10:56:06.681265 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:06.683314 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:07.682486 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:07.684963 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:08.683899 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:08.685145 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:09.685109 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:09.687187 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:10.686365 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:10.687348 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:11.687684 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:11.690099 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:12.688996 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:12.690150 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:13.690279 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:13.692694 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
10:56:14.691574 IP 172.20.100.101 > 224.0.0.18: VRRPv2, Advertisement, vrid 51, prio 100, authtype simple, intvl 1s, length 20
10:56:14.693902 IP 172.20.100.108 > 224.0.0.18: VRRPv2, Advertisement, vrid 52, prio 100, authtype simple, intvl 1s, length 20
搬砖小胖子
关注
专栏目录
KeepAlived双主配置
studywinwin的博客
02-05 489
文章目录环境规划配置说明keepalived 配置RS的配置Client 测试解决了什么问题 环境规划 配置说明 Client的网关指向 192.168.1.4 RS，keepalived 网关指向 192.168.43.17 RS上安装 httpd服务，RS1，RS2的vip为 192.168.43.100，RS3，RS4的vip为 192.168.43.200 keepalived服务器上...
keepalived主从配置
qaz13468559745的博客
05-17 665
keepalived主从配置 master 192.168.146.130 backup 192.168.146.131 master yum install keepalived vim keepalived.conf ! Configuration File for keepalived global_defs { notification_email { acassen@firewall.l...
keepalived：双主配置
focus_lyh的博客
08-09 244
双主配置
keepalived双主双从配置
weixin_55223769的博客
03-12 179
双主双从配置： 配置环境： keepalived1：192.66.66.101 keepalived2：192.66.66.102 web1：192.66.66.103 web2：192.66.66.104 vip1：192.66.66.106 vip2：192.66.66.107 在keepalived1上安装配置Keepalived: yum install keepalived ipvsadm -y vim /etc/keepalived/keepalived.conf ! Configuratio
MySQL高可用之KeepAlived+双主
flynetcn的专栏
03-29 989
用KeepAlived实现mysql双主互备
Nginx笔记(四)----Nginx+keepalived双主配置(双机双主热备)_keepalived 配置多个nginx
最新发布
2401_83739951的博客
04-18 309
chk_nginx.sh脚本也不用改，然后重启keepalived。然后修改两台机器上的nginx首页。
【lvs】LVS+Keepalived双主配置
H2K1R～ACE
08-31 140
【lvs】LVS+Keepalived双主配置
双主+Keepalived
y1035793317的博客
11-08 492
目录 思路： 环境： 主从同步 Mysql-master1配置（/etc/my.cnf） Mysql-master2配置（/etc/my.cnf） 授权 Mysql-master1配置 Mysql-master2配置 测试主主同步 keepalived的安装配置 1、在master1和master2上安装软件包keepalived 2、修改Keepalived的配置文件 master1配置 master2配置 3、启动Keepalived（两台机器） 4、测试 思路： K
mysql双主多从高可用配置_双主MySQL+keepalived高可用配置
weixin_36182029的博客
01-19 240
部署双节点双主数据库服务器MySQL分别在二台服务器上安装mysql，要求同版本或主服务器比从服务器版本高。主机mysql配置：Vi /etc/my.cnf[mysqld]Log-bin=mysql-binServer-id=1Service mysqld restartMysql –uroot –p从mysql配置：Vi /etc/my.cnf[mysqld]Log-bin=mysql-binS...
linux keepalived双主模式,keepalived 双主模式详解
weixin_36477469的博客
05-12 886
1·VRRP协议基本原理介绍Keepalived实现的基础是VRRP协议，我们将会在这一节中简要介绍VRRP协议的基本原理1.1 协议vRRP协议是为消除在静态缺省路由环境下的缺省路由器单点故障引起的网络失效而设计的主备模式的协议，使得在发生故障而进行设备功能切换时可以不影响内外数据通信，不需要再修改内部网络的网络参数。VRRP协议具有IP地址备份，优先路由选择，减少不必要的路由器间通信等功能。V...
配置nginx + keepalived双主模式（双机互为主备）
MassiveStars的博客
01-09 9309
前言 此前已经写过一篇使用keepalived实现nginx的高可用 这种方式有一台机器一直作backup使用，比较浪费资源 使用keepalived来实现nginx的高可用 下面来配置nginx+keepalived的双主机双机热备，这种配置下有两个Virtual IP，两个机器互为主备，最后我们把域名DNS服务器解析至两个Virtual IP即可。 环境介绍 两
LVS+keepalived双主配置
Blue summer的博客
07-01 971
keepalived双主配置 既然说双主，那么也就是要有两个对外提供服务的VIP了，所以双主模式也可以理解为两个单主共用同一批后端RS。因此，我们要新增对另一个VIP的定义，包括vrrp实例和后端实例。 环境准备 机器 作用 192.168.0.100 LVS调度器对外服务IP，VIP1 192.168.0.110 LVS调度器对外服务IP，VIP2 192.168.0.2...
实现keepalived双主热备配置
weixin_45445879的博客
10-07 241
实现keepalived双主热备 1.双热主备：给两台nginx配上虚拟IP，用户请求通过DNS轮询方式分发请求到不同的虚拟IP，不同的虚拟IP绑定不同的Nginx服务器，161虚拟IP和nginx的ip171绑定，172位备用机，162虚拟IP和172绑定，171位备用机，现在就是不存在主备关系了，每台都是主节点也是备用机 规则：以一个虚拟IP分组归为同一个路由 主节点配置： global_defs { # 路由id：当前安装keepalived的节点主机标识符，保证全局唯一 route
keepalived 双主模式
weixin_42494845的博客
10-26 785
keepalived 双主配置使用两个vip地址，前端使用2台机器，互为主备，同时有两台机器工作，当其中一台机器出现故障，两台机器的请求转移到一台机器负担，非常适合于当前架构环境。 架构： 服务器 ip 主vip 备vip mycentos7_1 192.168.130.128 192.168.130.140 192.168.130.141 mycentos7_2 192.168.130.128 192.168.130.141 192.168.130.140 mycentos7_1
Keepalived 双主模式
小楼一夜听春雨，深巷明朝卖杏花
11-21 744
双机双主 正常情况下nginx是一台提供服务，另外一条备份， 互为主备要引入两个VIP，如mysql双主，nginx双主，这样要引入两个VIP，也就是还需要引入 virtual_ipaddress { 192.168.179.199 192.1681.79.188 } 只是代表这个实例有两个VIP 192.168.179.102 [root@localhost ~]# cat /etc/keepalived/keepalived.conf global_defs { .
nginx+keepalived集群-双主
看到代码头都是大的~
04-10 384
单机部署可参考：https://blog.csdn.net/ym5209999/article/details/119897237主备模式可参考：https://blog.csdn.net/ym5209999/article/details/132983080。
Nginx与Keepalived双主配置详解及示例
总结来说，本文档提供了一个基础的Nginx和Keepalived双主配置案例，用于实现高可用的Web服务环境。通过合理的网络和软件配置，可以确保当一台Nginx服务器故障时，另一台能够自动接管，从而保障服务的连续性。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值