vrrp_instance VI_1 { state MASTER ### BACKUP on the backup ### interface eth0 lvs_sync_daemon_interface eth1 virtual_router_id 51 priority 100 ### 99 on the backup ### advert_int 1 smtp_alert virtual_ipaddress { 192.168.16.123 } }

Suddenly, I went a bit further... I saw a different (from the outdated doc) config on the web and tried it succesfully:

virtual_ipaddress { 192.168.16.123/32 brd 192.168.31.255 scope global }

And get these extra bits:

Feb 20 16:19:56 lvs1 Keepalived_vrrp: VRRP_Instance(VI_1) Transition to MASTER STATE Feb 20 16:19:57 lvs1 Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE Feb 20 16:19:57 lvs1 Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs. Feb 20 16:19:57 lvs1 Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 192.168.16.123 Feb 20 16:19:57 lvs1 Keepalived_vrrp: Remote SMTP server [127.0.0.1:25] connected. Feb 20 16:19:57 lvs1 Keepalived_vrrp: SMTP alert successfully sent.

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:04:23:9e:f3:74 brd ff:ff:ff:ff:ff:ff inet 192.168.28.226/20 brd 192.168.31.255 scope global eth0 inet 192.168.16.123/32 brd 192.168.31.255 scope global eth0 inet6 fe80::204:23ff:fe9e:f374/64 scope link valid_lft forever preferred_lft forever

But not sure both lvs are talking vrrp to each other; tcpdump does not intercept anything...

JD