|
Hi again
On Mon 06 Feb 2006 15:37:11 GMT , Matt Chan <engineuity@xxxxxxxxx> wrote:
Well, I am only bringing up/down eth1 where the VIP is:
backupState.sh
#!/bin/sh
/usr/bin/touch /<my_home_path>/this.is.not.cool
/sbin/ifconfig eth1 down > /<my_home_path>/outputBackup.txt
masterState.sh
#!/bin/sh
/usr/bin/touch /<my_home_directory/this.is.cool
/sbin/ifconfig eth1 x.x.x.208 broadcast x.x.x.223 netmask \
255.255.255.255 up > /<my_home_directory>/outputMaster.txt
Hrm, right...
Nothing at all happens, right? What version of keepalived is this?
Thinking a bit deeper about this, I can see one problem straight away
(probably unrelated actually, but go with me here): having all your
announcements on eth0, but your VIP on eth1, means that if eth1 goes
down (say a switch fails or someone trips over the cable) then there is
nothing in your config to monitor it. I use the "track_interface"
vrrp_instance option for this, as follows:
vrrp_instance DNS-FRONT01 {
state MASTER
interface bond0.500
track_interface {
bond0.99
}
...rest of config
}
In which case if *either* bond0.500 or bond0.99 go down, the state will
change. Maybe you also need something like that?
Graeme
|
