Hey,
Welcome to the OpenBSD community mailing list. I'm also using CARP for
lots of HA-setups and yes, I will be gentle. I have never had issues
like yours but my setup seems very different. The virtual host id (vhid)
and its ip adress becomes a carp-group, so changing the vhid back and
forth is not something I understand why you are doing.
- Try to isolate this to 2 simple test machines with as simple setup
as possible. Be simple.
- Make those machines either run the release version or current. State
which.
- Then continue;
- Post your interfaces configurations.
- Post your dmesg
- Post your pf.conf
- Post your tcpdump (where you observed this, make it as small as
possible)
- Also some information about why you are changing vhid would be
interesting.
- vhid needs to be the same on all hosts participating in the same
carp interface.
- if you change vhid, the other host(s) on the other side also needs
to change.
- Are you using a carp on top of any other non-hardware interface?
Like a vlan, with carpdev?
- Also, many people forget this, but if you type "man 4 carp" you
will find a lot of good stuff to be read about carp, vhids, carpdev and
such.
Best of luck,
Alexander
On 01/21/2016 11:02 PM, rizz2pro . wrote:
Hello,
This is my first time posting here so be gentle.
It seems that random CARP interfaces on our systems will just die, stop
replying to any requests OR only 1 request out of ~50 will make it through,
slowly.
tcpdump also shows no traffic reach the interface. Only when that 1 request
makes it through, we will see traffic arrive to the system.
We've tried everything we could think of to bring the carp interface back
to life such as reboot, run sh /etc/netstart and even going as far as
rebuilding the system server from scratch with maven and dropping the
site55.tgz file in there but none of these things fix the issue.
When we change the VHID to anything else and restart the interface, it
fixes everything and the interface is smoking fast again. When we change
the VHID back to what it originally was, we're dead in the water. Again,
change it back to any random VHID and the issue goes away. So I have
narrowed it down to VHID. Whenever we run into this problem I just tell
people to change it to anything else.
I know the CARP interface's MAC address is generated by the VHID so I am
sort of leaning towards it be an ARP issue and possibly not an issue with
the OBSD system. But I am hoping for some hints or ideas from you guys.
Thanks in advance for any help!
RZ
