On 2/9/06, Graeme Fowler <graeme@xxxxxxxxxxx> wrote:
>
> In your case, substitute eth0 and eth1 for bond0.99 and bond0.500.
I added the track interface into my conf, but there was a never ending loop
that occurred when restarting keepalived:
Feb 9 09:52:44 testd2 Keepalived_vrrp: Registering Kernel netlink reflector
Feb 9 09:52:44 testd2 Keepalived_vrrp: Registering Kernel netlink command
channel
Feb 9 09:52:44 testd2 Keepalived_vrrp: Registering gratutious ARP shared
channel
Feb 9 09:52:44 testd2 Keepalived_vrrp: VRRP_Instance(VI_1{) the virtual id
must be set!
Feb 9 09:52:44 testd2 Keepalived: Starting VRRP child process, pid=10645
Feb 9 09:52:44 testd2 Keepalived: VRRP child process(10645) died:
Respawning
Feb 9 09:52:44 testd2 Keepalived_vrrp: Using MII-BMSR NIC polling thread...
The entry:
vrrp_instance VI_1{
state MASTER
interface eth1
#lvs_sync_daemon_interface eth0
track_interface{
eth1
}
virtual_router_id 51
priority 100
smtp_alert
advert_int 1
virtual_ipaddress{
x.x.x.208/32 dev eth1
}
notify_master "/sbin/masterState.sh"
notify_backup "/sbin/backupState.sh"
notify_fault "/sbin/backupState.sh"
}
I also tried with the lvs_sync uncommented as eth0 and as eth1
> If you really want to find out more about this (which is *not* related
> to LVS in any way, shape or form) then your distribution probably comes
> with a file like the following:
>
/usr/share/doc/iputils-20020927/README.bonding
>
Running debian, pretty stock 2.6.8-2-686-smp...I dont have it. Any ideas why
the notify scripts wont run?
-Matt
|