Hello list
I'd like to configure the following scenario:
Master and Backup Director with 2 VIPs. VIP1 with MASTER state on
Director1 (D1), VIP2 with MASTER state on Director2 (D2).
So that in "OK"-state, traffic goes through to different hosts and only
both VIPs are on one host in case of an error.
So when I start keepalived on D1, it only brings up the second VIP, but
not the first one. And it only sends VRRP adverts for that
virtual_router_id.
When I start keepalived on D2, it takes over VIP2, as D2 is the MASTER
for VIP2.
VIP1 is on neither D1 or D2.
Any ideas? Is this something, keepalived is not designed for or is it a bug?
I am using keepalived 1.1.11 but from the release notes I did not see
that 1.1.12 would fix this
This is my keepalived.conf on D2.
Dr2 has the same config with prio and state changed in both vrrp_instances.
cat keepalived.conf
! Configuration File for keepalived
global_defs {
notification_email { dk@xxxxxxxxxxxxxxxx }
notification_email_from acddbtest@xxxxxxxxxxxxxxxx
smtp_server 10.2.20.6
smtp_connect_timeout 30
lvs_id TEST-ACD-1
}
vrrp_sync_group ACDDB_mysql_eins {
group { vip_mysql_eins }
}
vrrp_sync_group ACDDB_mysql_zwei {
group { vip_mysql_zwei }
}
vrrp_instance vip_mysql_eins {
state MASTER
interface eth0
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 12345
}
virtual_ipaddress {
10.6.10.24/24 dev eth0
}
}
vrrp_instance vip_mysql_zwei {
state BACKUP
interface eth0
virtual_router_id 52
priority 10
advert_int 1
authentication {
auth_type PASS
auth_pass 12345
}
virtual_ipaddress {
10.6.10.27/24 dev eth0
}
}
|