keepalived实验总结

最新推荐文章于 2024-08-21 08:34:56 发布
最新推荐文章于 2024-08-21 08:34:56 发布
阅读量369 收藏 5
点赞数 4
文章标签： 运维 linux 服务器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_61179587/article/details/141308033
版权

一、实现master/slave的keepalived单主架构

1、实验环境准备： 

四台虚拟机：realserver1(172.25.254.110)、realserver2(172.25.254.120)、ka1(172.25.254.10)、ka2(172.25.254.20)（vip：172.25.254.100）

2、实验配置：

#realserver1
[root@realserver1 ~]# yum install httpd -y
[root@realserver1 ~]# echo 172.25.254.110 > /var/www/html/index.html
[root@realserver1 ~]# systemctl enabled --now httpd
#realserver2
[root@realserver2 ~]# yum install httpd -y
[root@realserver2 ~]# echo 172.25.254.120 > /var/www/html/index.html
[root@realserver2 ~]# systemctl enabled --now httpd
#ka1
[root@ka1 ~]# yum install keepalived -y
[root@ka1 ~]# rpm -ql keepalived
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf
global_defs {
   notification_email {
        1231234574@qq.com				
   }
   notification_email_from keepalived@company.org			
   smtp_server 127.0.0.1				
   smtp_connect_timeout 30				
   router_id ka1.company.org		
   vrrp_skip_check_adv_addr				
   vrrp_strict														
   vrrp_garp_interval 0					
   vrrp_gna_interval 0					
   vrrp_mcast_group4 224.0.0.18			
}

vrrp_instance VI_1 {
    state MASTER
    interface eth0						
    virtual_router_id 100																							
    priority 100						
    advert_int 1						
    authentication {					
        auth_type PASS					
        auth_pass 1111					
    }
    virtual_ipaddress {					
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
[root@ka1 ~]# systemctl enable --now keepalived.service
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ifconfig

[root@ka1 ~]# tcpdump -i eth0 -nn host 224.0.0.18
[root@ka1 ~]# systemctl stop keepalived.service 
[root@ka1 ~]# systemctl start keepalived.service

3、实验结果测试：

二、实现VIP访问 

1、实验配置：

#ka1
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka1 ~]# systemctl restart keepalived.service 
global_defs {
   notification_email {
        1231234574@qq.com
   }
   notification_email_from keepalived@company.org
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id ka1.company.org
   vrrp_skip_check_adv_addr
   vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
   vrrp_mcast_group4 224.0.0.18
   vrrp_iptables
}
#ka2
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# systemctl restart keepalived.service

2、实验结果测试：

三、启用keepalived日志功能 

#ka1
[root@ka1 ~]# vim /etc/sysconfig/keepalived
KEEPALIVED_OPTIONS="-D -S 6"
[root@ka1 ~]# vim /etc/rsyslog.conf
local6.*                                                /var/log/keepalived.log
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# systemctl restart rsyslog.service 
[root@ka1 ~]# ll /var/log/keepalived.log 
-rw------- 1 root root 601 Aug 12 13:51 /var/log/keepalived.log

四、独立子配置文件

[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
#vrrp_instance VI_1 {
#    state MASTER
#    interface eth0
#    virtual_router_id 100
#    priority 100
#    advert_int 1
#    authentication {
#        auth_type PASS
#        auth_pass 1111
#    }
#    virtual_ipaddress {
#        172.25.254.100/24 dev eth0 label eth0:1
#    }
#}
include "/etc/keepalived/conf.d/*.conf"
 
[root@ka1 ~]# mkdir -p /etc/keepalived/conf.d
[root@ka1 ~]# vim /etc/keepalived/conf.d/172.25.254.100.conf
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
 
[root@ka1 ~]# systemctl restart keepalived.service

五、抢占模式和非抢占模式

1、非抢占模式：

#ka1
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    nopreempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
[root@ka1 ~]# systemctl restart keepalived.service 		#先重启da1的服务
[root@ka1 ~]# ifconfig 

#ka2
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 80
    advert_int 1
    nopreempt
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# ifconfig

2、抢占延迟模式：

#ka1
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ifconfig 

#ka2 
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 80
    advert_int 1
    preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
}
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# ifconfig 
 
[root@ka1 ~]# systemctl stop keepalived.service 
[root@ka1 ~]# systemctl restart keepalived.service

六、VIP单播配置

1、实验配置：

#ka1
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ifconfig 
[root@ka1 ~]# tcpdump -i eth0 -nn src host 172.25.254.10 and dst 172.25.254.20
[root@ka1 ~]# systemctl stop keepalived.service 		
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# tcpdump -i eth0 -nn src host 172.25.254.10 and dst 172.25.254.20
 
#ka2
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# ifconfig 
[root@ka2 ~]# tcpdump -i eth0 -nn src host 172.25.254.20 and dst 172.25.254.10
#ka1(172.25.254.10):
global_defs {
   notification_email {
        1231234574@qq.com
   }
   notification_email_from keepalived@company.org
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id ka1.company.org
   vrrp_skip_check_adv_addr
   #vrrp_strict		
   vrrp_garp_interval 0
   vrrp_gna_interval 0
   vrrp_mcast_group4 224.0.0.18
   #vrrp_iptables	 
}
 
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.10
    unicast_peer {
        172.25.254.20
    }
}

#ka2(172.25.254.20):
global_defs {
   notification_email {
        1231234574@qq.com
   }
   notification_email_from keepalived@company.org
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id ka1.company.org
   vrrp_skip_check_adv_addr
   #vrrp_strict		 #注释此参数，与vip单播模式冲突
   vrrp_garp_interval 0
   vrrp_gna_interval 0
   vrrp_mcast_group4 224.0.0.18
   #vrrp_iptables	 #注释此参数，与vip单播模式冲突
}
 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 80
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.20
    unicast_peer {
        172.25.254.10
    }
}

2、实验结果测试：

七、 keepalived邮箱通知脚本

#ka1
[root@ka1 ~]# yum install mailx -y
[root@ka1 ~]# vim /etc/mail.rc 
set from=1231234574@qq.com        
set smtp=smtp.qq.com
set smtp-auth-user=1231234574@qq.com
set smtp-auth-password=ukjiwlpvufjtjj
set smtp-auth=login
set ssl-verify=ignore
[root@ka1 ~]# echo test| mail -s test 1231234574@qq.com
[root@ka1 ~]# vim /etc/keepalived/mail.sh
[root@ka1 ~]# chmod +x /etc/keepalived/mail.sh
[root@ka1 ~]# /etc/keepalived/mail.sh master

#!/bin/bash
mail_dst="1231234574@qq.com"
send_message()
{
  mail_sub="$HOSTNAME to be $1 vip move"
  mail_msg="`date +%F\ %T`: vrrp move $HOSTNAME chage $1"	
  echo $mail_msg | mail -s "$mail_sub" $mail_dst
}
 
case $1 in
  master)
  send_message master
  ;;
  backup)
  send_message backup
  ;;
  fault)
  send_message fault
  ;;
  *)
  ;;
esac
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.10
    unicast_peer {
        172.25.254.20
    }
    notify_master "/etc/keepalived/mail.sh master"
    notify_backup "/etc/keepalived/mail.sh backup"
    notify_fault "/etc/keepalived/mail.sh fault"
}
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# systemctl stop keepalived.service		
[root@ka1 ~]# systemctl restart keepalived.service		
 
 
#ka2
[root@ka2 ~]# yum install mailx -y
[root@ka2 ~]# vim /etc/mail.rc
set from=1231234574@qq.com
set smtp=smtp.qq.com
set smtp-auth-user=1231234574@qq.com
set smtp-auth-password=ukjiwlpvufjtjj
set smtp-auth=login
set ssl-verify=ignore
[root@ka2 ~]# echo test| mail -s test 1231234574@qq.com
[root@ka2 ~]# vim /etc/keepalived/mail.sh
[root@ka2 ~]# chmod +x /etc/keepalived/mail.sh
[root@ka2 ~]# /etc/keepalived/mail.sh master
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# systemctl restart keepalived.service
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 80
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.20
    unicast_peer {
        172.25.254.10
    }
    notify_master "/etc/keepalived/mail.sh master"
    notify_backup "/etc/keepalived/mail.sh backup"
    notify_fault "/etc/keepalived/mail.sh fault"
}

八、实现master/master的keepalived双主架构

1、实验配置：

#ka1
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ifconfig 
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.10
    unicast_peer {
        172.25.254.20
    }
}
 
vrrp_instance VI_2 {
    state BACKUP
    interface eth0
    virtual_router_id 200
    priority 80
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.200/24 dev eth0 label eth0:2
    }
    unicast_src_ip 172.25.254.10
    unicast_peer {
        172.25.254.20
    }
}
 
#ka2 
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# ifconfig 
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 80
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.20
    unicast_peer {
        172.25.254.10
    }
}
 
vrrp_instance VI_2 {
    state MASTER
    interface eth0
    virtual_router_id 200
    priority 100
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.200/24 dev eth0 label eth0:2
    }
    unicast_src_ip 172.25.254.20
    unicast_peer {
        172.25.254.10
    }
}

2、实验结果测试：

九、实现IPVS的高可用性

1、实验配置：

#realserver1
[root@realserver1 ~]# ip a a 172.25.254.100/32 dev lo
[root@realserver1 ~]# cd /etc/sysconfig/network-scripts/
[root@realserver1 network-scripts]# vim ifcfg-lo
DEVICE=lo
IPADDR0=127.0.0.1
NETMASK0=255.0.0.0
IPADDR1=172.25.254.100
NETMASK1=255.255.255.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback
[root@realserver1 ~]# sysctl -a | grep arp
  
#realserver2
[root@realserver2 ~]# ip a a 172.25.254.100/32 dev lo
[root@realserver2 ~]# vim /etc/sysctl.d/arp.conf
[root@realserver2 ~]# sysctl --system
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.lo.arp_ignore = 1
net.ipv4.conf.lo.arp_announce = 2
[root@realserver2 ~]# scp /etc/sysctl.d/arp.conf root@172.25.254.100:/etc/sysctl.d/arp.conf
 
#ka1
[root@ka1 ~]# yum install ipvsadm -y
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  172.25.254.100:80 wrr
  -> 172.25.254.110:80            Route   1      0          0         
  -> 172.25.254.120:80            Route   1      0          0   
 
#ka2 
[root@ka2 ~]# yum install ipvsadm -y
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# ipvsadm -Ln
virtual_server 172.25.254.100 80 {
    delay_loop 6
    lb_algo wrr
    lb_kind DR
    #persistence_timeout 50
    protocol TCP
    
    real_server 172.25.254.110 80 {
        weight 1
        HTTP_GET {
            url {
              path /
              status_code 200
            } 
            connect_timeout 3
            nb_get_retry 2
            delay_before_retry 2
        }   
    }   
    
    real_server 172.25.254.120 80 {
        weight 1
        HTTP_GET {
            url {
              path /
              status_code 200
            }
            connect_timeout 3
            nb_get_retry 2
            delay_before_retry 2
        }
    }
}

 2、实验结果测试：

十、实现HAProxy高可用

1、实验配置：

#realserver1
[root@realserver1 ~]# systemctl restart network
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[root@realserver1 ~]# nmcli connection show 
NAME    UUID                                  TYPE      DEVICE 
eth0    5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0   
virbr0  0675fa0c-3989-45c3-bdf8-014f2e31edaf  bridge    virbr0 
ens33   c96bc909-188e-ec64-3a96-6a90982b08ad  ethernet  --     
[root@realserver1 ~]# nmcli connection delete ens33			
Connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad) successfully deleted.
[root@realserver1 ~]# systemctl restart network
[root@realserver1 ~]# ip a		
[root@realserver1 ~]# ip a d 172.25.254.100/32 dev lo			
[root@realserver1 ~]# ip a
[root@realserver1 ~]# vim /etc/sysctl.d/arp.conf 
net.ipv4.conf.all.arp_ignore=0
net.ipv4.conf.all.arp_announce=0
net.ipv4.conf.lo.arp_ignore=0
net.ipv4.conf.lo.arp_announce=0
[root@realserver1 ~]# sysctl --system
[root@realserver1 ~]# while true; do curl 172.25.254.100;sleep 1; done

#realserver2
[root@realserver2 ~]# systemctl restart network
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[root@realserver2 ~]# nmcli connection show
NAME    UUID                                  TYPE      DEVICE 
eth0    5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0   
virbr0  6dd347bc-a380-4e1c-8272-86658279a412  bridge    virbr0 
ens33   c96bc909-188e-ec64-3a96-6a90982b08ad  ethernet  --     
[root@realserver2 ~]# nmcli connection delete ens33
Connection 'ens33' (c96bc909-188e-ec64-3a96-6a90982b08ad) successfully deleted.
[root@realserver2 ~]# systemctl restart network
[root@realserver2 ~]# ip a
[root@realserver2 ~]# ip a d 172.25.254.100/32 dev lo
[root@realserver2 ~]# ip a
[root@realserver2 ~]# vim /etc/sysctl.d/arp.conf 
#ka1
[root@ka1 ~]# vim /etc/sysctl.conf 
net.ipv4.ip_nonlocal_bind=1
[root@ka1 ~]# sysctl -p
net.ipv4.ip_nonlocal_bind = 1
[root@ka1 ~]# yum install haproxy -y
[root@ka1 ~]# vim /etc/haproxy/haproxy.cfg 
listen webcluster
    bind 172.25.254.100:80
    mode http
    balance roundrobin
    server web1 172.25.254.110:80 check inter 3 fall 2 rise 5
    server web2 172.25.254.120:80 check inter 3 fall 2 rise 5
[root@ka1 ~]# systemctl enable --now haproxy.service 
[root@ka1 ~]# netstat -antlupe | grep haproxy
[root@ka1 ~]# vim /etc/keepalived/test.sh 
#!/bin/bash
killall -0 haproxy
[root@ka1 ~]# vim /etc/keepalived/keepalived.conf 		
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# systemctl restart haproxy.service 
[root@ka1 ~]# systemctl stop keepalived.service 
[root@ka1 ~]# ifconfig 
[root@ka1 ~]# systemctl restart keepalived.service 
[root@ka1 ~]# ifconfig 

#ka2
[root@ka2 ~]# vim /etc/sysctl.conf 
[root@ka2 ~]# sysctl -p
net.ipv4.ip_nonlocal_bind = 1
[root@ka2 ~]# yum install haproxy -y
[root@ka2 ~]# vim /etc/haproxy/haproxy.cfg 
[root@ka2 ~]# systemctl enable --now haproxy.service 
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# vim /etc/keepalived/test.sh
[root@ka2 ~]# vim /etc/keepalived/keepalived.conf 
[root@ka2 ~]# systemctl restart keepalived.service 
[root@ka2 ~]# systemctl restart haproxy.service 
vrrp_script check_haproxy {
    script "/etc/keepalived/test.sh"
    interval 1
    weight -30
    fall 2
    rise 2
    timeout 2
}
vrrp_instance VI_1 {
    state BACKUP
    interface eth0
    virtual_router_id 100
    priority 100
    advert_int 1
    #preempt_delay 5s
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        172.25.254.100/24 dev eth0 label eth0:1
    }
    unicast_src_ip 172.25.254.10
    unicast_peer {
        172.25.254.20
    }
    track_script {
        check_haproxy
    }
}

2、实验结果测试：

强者自救,圣者渡人
关注
  • 4
    点赞
  • 踩
  • 5
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
mysql主从+keepalived实现高可用
10-11
#### 实验背景及目标 在当前互联网业务场景中，为了确保数据库服务的连续性和可靠性，采用 MySQL 的主从复制架构结合 Keepalived 来实现高可用性是非常常见的方案。本文档将详细介绍如何通过配置 MySQL 双主双从...
keepalived+rdis高可用方案
07-10
【keepalived+rdis高可用方案】 ...总结，通过这个方案，可以实现redis的高可用性，减少因服务器故障导致的服务中断。同时，利用keepalived的健康检查和VIP漂移机制，保证了数据的持续可用和系统的稳定性。
Linux高可用(HA)集群keepalived实验
第九系艾文
08-18 282
keepalived 高可用 lvs-dr测试, 高可用nginx
LVS-DR及keepalived实验
ruocheng6的博客
03-23 560
1、LVM概述 2、LVM的管理命令 3、LVM应用示例 4、磁盘配额概述 5、磁盘配额管理
Keepalived+Nginx双机热备实验
weixin_51369125的博客
03-24 385
Keepalived是一款高可用性的服务，它可以帮助您在云服务器上实现负载均衡和故障转移。该服务通过VRRP协议实现了主备节点之间的故障切换和负载均衡。
Keepalived 特性实验
LCK 博客
06-21 609
一、单主架构 架构拓扑 实验环境： keepalived服务器1：10.0.0.11 keepalived服务器2：10.0.0.12 keepalived服务器1配置 global_defs { router_id LVS_DEVEL vrrp_skip_check_adv_addr vrrp_strict vrrp_garp_interval 0 vrrp_gna_interval 0 } vrrp_instance ro...
lvs+keepalived实验
weixin_30478757的博客
06-13 114
一、VRRP协议与工作原理 　　在现实网络环境中，主机之间的通信都是通过配置静态路由或者(默认网关)来完成的，而主机之间的路由器一旦发生故障，通信就会失效，因此这种通信模式当中，路由器就成了一个单点瓶颈，为了解决这个问题，就引入了VRRP协议。熟悉网络的学员对VRRP协议应该不陌生，它是一种主备模式的协议，通过VRRP可以在网络发生故障时透明的进行设备切换而不影响主机之间的数据通信，这...
keepalived总结
qq_39677803的博客
05-24 2229
master（192.168.199.201）配置如下。backup（192.168.199.202）配置如下。结果如下：201上有VIP，202上则没有。下面列出主的配置，从的自行修改。检测Nginx的脚本。
keepalived高可用集群学习以及实验总结
weixin_34245169的博客
06-05 338
HA Cluster实现方案：vrrp协议的实现keepalivedais: 完备HA集群RHCS(cman)heartbeatcorosync + pacemaker :corosync是集群框架引擎程序，pacemaker是集群资源管理器，crmsh是pacemaker命令行管理工具 stonish : shooting the other node in the header 节点爆头，比...
KEEPALIVED总结
m0_70884519的博客
08-18 746
vrrp 协议的软件实现，原生设计目的为了高可用 ipvs服务官网：http://keepalived.org/功能：基于vrrp协议完成地址流动为vip地址所在的节点生成ipvs规则(在配置文件中预先定义)为ipvs集群的各RS做健康状态检测基于脚本调用接口完成脚本中定义的功能，进而影响集群事务，以此支持n ginx、haproxy等服务。
Nginx+keepalived实现高可用
Lzcsfg的博客
06-14 845
"Keepalived" 是一个用于 Linux 系统的高可用性和负载均衡解决方案。它主要通过提供虚拟路由器冗余协议 (VRRP) 和健康检查来实现高可用性。
基于MySQL Cluster和Keepalived实现数据同步和故障转移的实验研究.pdf
10-10
在实验研究中，作者通过部署MySQL Cluster和Keepalived的组合，验证了这种架构可以有效实现数据同步和故障转移。在设置合理的集群参数和Keepalived策略后，系统在主服务器故障时能快速恢复服务，同时保持数据的完整...
Nginx+keepalived+tomcat实现性负载均衡
03-04
本实验环境使用 Nginx、keepalived 和 Tomcat 实现了高可用性和负载均衡。Nginx 作为反向代理服务器，keepalived 实现了高可用性和负载均衡，Tomcat 作为 java 应用服务器。实验环境的拓扑结构和配置文件都可以满足...
Linux运维实战项目keepalived Web服务器双机热备
10-11
#### 实验总结 通过本次实验，我们不仅掌握了如何使用Keepalived搭建Web服务器的双机热备系统，还深入理解了Keepalived的工作原理及其在高可用集群中的应用。此外，通过实际操作，我们还学会了如何配置和测试...
K8S 版本发版
最新发布
mqiqe的专栏
08-21 849
K8S（Kubernetes）版本发版是一个涉及多个步骤的过程，旨在确保应用程序的顺利升级和部署。
【运维自动化-配置平台】如何查看运营数据和审计
腾讯蓝鲸智云官方博客
08-20 220
也可自定义新增视图，比如新增一个按云厂商统计主机的：可以点击上下箭头调整图表展示位置说明：适合产品版本 V6.1/V6.2/V7.0/V7.1。
01 SSH--
m0_46671240的博客
08-19 257
SSH
模拟两台计算机的通讯-启动虚拟机（brctl+qemu组网）
simulate_create的博客
08-20 474
我们本次的目标是：vm-交换-vm。
keepalived
09-08
总结起来，Keepalived是一个用于检测服务器状态并实现服务器冗余的工具，它可以通过VRRP协议来实现设备的高可用性和负载均衡。配置文件中的各个区域可以定义全局参数和具体的服务器配置。<span class="em">1</span>...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值