Marco Pfatschbacher wrote:

quoted text
> On Tue, Oct 23, 2007 at 11:10:32AM +0200, Heinrich Rebehn wrote:

>> Googling showed up quite a few posts of people having problems with CARP

>> and the "incorrect hash" message, but none really helped me.

>

> the most common reason for "incorrect hash" messages is

> that your configuration isn't in sync. That includes all

> IP addresses and the password.

>

> Seems like that's the case in your setup:

>

>> carp0: flags=8843 mtu 1500

>> 	lladdr 00:00:5e:00:01:0a

>> 	carp: MASTER carpdev vlan0 vhid 10 advbase 1 advskew 0

>> 	groups: carp

>> 	inet6 fe80::200:5eff:fe00:10a%carp0 prefixlen 64 scopeid 0xa

>> 	inet 134.102.176.250 netmask 0xffffff00 broadcast 134.102.176.255

>> 	inet 134.102.176.202 netmask 0xffffff00 broadcast 134.102.176.255

>

> vs.

>

>> carp0: flags=8802 mtu 1500

>> 	lladdr 00:00:5e:00:01:0a

>> 	carp: INIT carpdev vlan0 vhid 10 advbase 1 advskew 100

>> 	groups: carp

>> 	inet6 fe80::200:5eff:fe00:10a%carp0 prefixlen 64 scopeid 0xb

>> 	inet 134.102.176.250 netmask 0xffffff00 broadcast 134.102.176.255

>

> dunno where you got 134.102.176.202 from, though...

>

>> hostname.carp0:

>> inet 134.102.176.250 255.255.255.0 134.102.176.255 vhid 10 pass xxx10 carpdev vlan0 advskew 100 state backup

>>

>

> You shouldn't use "state backup" here.  The higher advskew is sufficient.

> "state" is only needed for manual intervention.

>

Have removed "state backup", and it is still working. Also fixed my

hostname.carp0.

Thanks for your help
--Heinrich