有没有可能configurationkeepalived这种方式？
在正常状态下，VIP_1分配给SERVER_1和VIP_2分配给SERVER_2
在服务器发生故障时，所有的VIP服务器都会进入工作状态，服务器发生故障后，我们不会将他的VIP迁移回给他，但是由于某些内容复制的原因，我们需要手动执行它。
目前configuration：
#SERVER_1 vrrp_sync_group VG1 { group { content } } vrrp_instance content { state BACKUP interface eth1 virtual_router_id 1 priority 100 advert_int 1 authentication { auth_type PASS auth_pass 1212 } virtual_ipaddress { 192.168.100.111/24 } } # SERVER_2 vrrp_sync_group VG1 { group { content } } vrrp_instance content { state BACKUP interface eth1 virtual_router_id 1 priority 100 advert_int 1 authentication { auth_type PASS auth_pass 1212 } virtual_ipaddress { 192.168.100.111/24 } } 在主机1上：
vrrp_instance VI_1 { state MASTER interface eth0 dont_track_primary virtual_router_id 1 priority 150 advert_int 5 mcast_src_ip 172.16.40.1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 10.0.0.1/24 dev eth0 } } vrrp_instance VI_2 { state BACKUP interface eth0 dont_track_primary virtual_router_id 5 priority 100 advert_int 5 mcast_src_ip 172.16.40.1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 10.0.0.2/24 dev eth0 } }
在主机2上：
vrrp_instance VI_1 { state BACKUP interface eth0 dont_track_primary virtual_router_id 1 priority 100 advert_int 5 mcast_src_ip 172.16.40.2 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 10.0.0.1/24 dev eth0 } } vrpp_instance VI_2 { state MASTER interface eth0 dont_track_primary virtual_router_id 5 priority 150 advert_int 5 mcast_src_ip 172.16.40.2 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 10.0.0.2/24 dev eth0 } }
对于无自动故障回复，请参阅keepalived.conf手册页中的nopreempt，但也请参阅： http ://article.gmane.org/gmane.linux.keepalived.devel/1537%22