2012/3/2 PP;Q Q P(P8P?P8QP8P= <chipits...@gmail.com>: > hello! > > we are running CARP-ed load balancers (carp over different vlans). > it was running just great with 6 carp addresses. > > when we added 7th, randomly we get MASTERs on both server for certain carp > interface. After reboot we can get different carp interface on dual MASTER > state, and so on. > carp negotiations are ok, tcpdump shows them all. both peers see each other. > > if I put one interface to BACKUP state, it goes to mASTER soon. > > we are runnung 5.0/amd64
I'm seeing this too. The current work-around is to set the carp to announce to a carppeer to the other box so it doesn't multicast but rather uses unicasts. In my case, the to-be-slave machine doesn't see all the carp announcements from the master, but rather one per minute or so. I have this on Dell amd64 openbsds ranging from 4.8 to 5.0, in all my cases when running on top of vlans (just because that is how we set these up) and running on Extreme Switches. The ips on the vlan interfaces can talk fine, the master hears all carp packets, the slave misses most or all carps from the other. This means that tcpdump on the master shows the higher-skewed carps from the slave also. The odd thing is that its not consistent on all carps either, but rather a few out of many. If I set just those to use carppeer, it sometimes moves over to other carps, but it could have been moving around for a long time, haven't had time to fully investigate this. I have a few non-critical pairs on which to test stuff, it needed. -- B To our sweethearts and wives.B May they never meet. -- 19th century toast
