William Stuart wrote:
Hello everyone,
I am sorry for not mentioning it was a vmWare instance. The packet
replay seemed to be the culprit.
This occured when we moved the image to a vmWare host running vmWare ESX
3.5 from 3.0. Our working theory is that under 3.5 pernicious mode
works
We have also experienced problems with CARP when moving ESX from 3.0i to
3.5. No solution yet.
Have tried to tweak the vSwitch settings ? I remember I made CARP work
with 2 OpenBSD 4.2 VM on ESX 3.5 after changing some settings in the
networking properties... (I know I should document what
Hello everyone,
I am sorry for not mentioning it was a vmWare instance. The packet
replay seemed to be the culprit.
This occured when we moved the image to a vmWare host running vmWare ESX
3.5 from 3.0. Our working theory is that under 3.5 pernicious mode
works differently than under 3.0
On 2008-07-21, William Stuart [EMAIL PROTECTED] wrote:
I am sorry for not mentioning it was a vmWare instance. The packet
replay seemed to be the culprit.
This occured when we moved the image to a vmWare host running vmWare ESX
3.5 from 3.0. Our working theory is that under 3.5 pernicious
On 2008-07-19, William Stuart [EMAIL PROTECTED] wrote:
Thanks everyone I figured it out!
19:13:46.334037 CARPv2-advertise 36: vhid=50 advbase=1 advskew=0
demote=0 (DF) [tos 0x10]
19:13:46.334299 CARPv2-advertise 36: vhid=50 advbase=1 advskew=0
demote=0 (DF) [tos 0x10]
Something is
Thank you for the idea. I did try that, but it still did not become MASTER.
I had to give up on carp (and redundancy altogether) and run with
aliases for now.
Vinicius Vianna wrote:
Hi William,
I don't know for sure, but I remember dealing with this kind of
problem and setting preempt did
Hi
Are you sure that all the interfaces you have configured carp on have
link and can connect to each other? (I've seen similar behaviour caused
by defective NICs: receive buffer not receiving while send buffer still
sending - try ping on all interfaces) Is lo up? Is there any other
router
Markus Wernig wrote:
Hi
Are you sure that all the interfaces you have configured carp on have
link and can connect to each other? (I've seen similar behaviour
caused by defective NICs: receive buffer not receiving while send
buffer still sending - try ping on all interfaces) Is lo up? Is
If you tcpdump do you see any carp traffic at all (ip proto 112)? Upon
reboot? And you did enable carp preemption on both hosts (sysctl
net.inet.carp.preempt=1)?
On Fri, Jul 18, 2008 at 01:26:07PM -0700, William Stuart wrote:
Markus Wernig wrote:
Hi
Are you sure that all the interfaces you have configured carp on have
link and can connect to each other? (I've seen similar behaviour
caused by defective NICs: receive buffer not receiving while send
Thanks everyone I figured it out!
19:13:46.334037 CARPv2-advertise 36: vhid=50 advbase=1 advskew=0
demote=0 (DF) [tos 0x10]
19:13:46.334299 CARPv2-advertise 36: vhid=50 advbase=1 advskew=0
demote=0 (DF) [tos 0x10]
Something is mirroring and replaying all the packets back.
Grrr. Must be a
(Sorry if this is a dupe, not sure if you had to be a subscriber to send
to the list)
Hello all,
I am a new to OpenBSD but not *nix in general...
I have two systems running OpenBSD 4.2. It has 9 carp interfaces, and
has been running fine for months. All of a sudden, both systems are in
Hello all,
I am a new to OpenBSD but not *nix in general...
I have two systems running OpenBSD 4.2. It has 9 carp interfaces, and
has been running fine for months. All of a sudden, both systems are in
BACKUP state.
I have rebooted, shut down and restarted, run ifconfig carp1 state
Hi William,
I don't know for sure, but I remember dealing with this kind of problem
and setting preempt did work, maybe worth a try:
/etc/sysctl.conf:
net.inet.carp.preempt=1
Anyone else?
HTH,
Vinicius
William Stuart escreveu:
(Sorry if this is a dupe, not sure if you had to be a
14 matches
Mail list logo
