Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 04 Apr 2009 10:20:52 +0200
From:      Sebastiaan van Erk <sebster@sebster.com>
To:        freebsd-cluster@freebsd.org
Subject:   CARP and NIC-teaming on ESXi
Message-ID:  <49D71864.3010403@sebster.com>

next in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Hi all,

I have a problem using CARP for IP failover on a FreeBSD 7.1-amd64 
virtual machine on ESXi 3.5. The problem can be reproduced using a 
single FreeBSD virtual mmachine.

When I put the FreeBSD VM on a virtual switch on ESXi with one physical 
network card associated to it, CARP works fine, the carp interface 
becomes MASTER.

However, as soon as I associate 2 physical network cards with the 
virtual switch so that I have NIC failover, the FreeBSD machine 
continuously becomes the BACKUP even though there are no other machines 
with the same vhid. In the logs I get this message repeated ad infinitum:

carp0: MASTER -> BACKUP (more frequent advertisement received)
arp_rtrequest: bad gateway 192.168.1.1 (!AF_LINK)
carp0: MASTER -> BACKUP (more frequent advertisement received)
arp_rtrequest: bad gateway 192.168.1.1 (!AF_LINK)

When I ping the shared IP addres 192.168.1.1 it replies VERY 
infrequently (a few times ever 50000 pings).

When I do a tcpdump to see the carp advertisements then when it is 
working (only one network card), I see something like this (with carp 
advertisements approximately every second):

10:08:11.241213 00:00:5e:00:01:4a > 01:00:5e:00:00:12, ethertype IPv4 
(0x0800), length 70: (tos 0x10, ttl 255, id 28744, offset 0, flags [DF], 
proto VRRP (112), length 56) 192.168.1.2 > 224.0.0.18: VRRPv2, 
Advertisement, vrid 74, prio 100, authtype none, intvl 1s, length 36, 
addrs(7): 
156.231.51.105,143.57.8.21,37.96.2.205,99.70.81.166,146.170.184.206,103.60.18.123,240.32.224.52
10:08:12.651052 00:00:5e:00:01:4a > 01:00:5e:00:00:12, ethertype IPv4 
(0x0800), length 70: (tos 0x10, ttl 255, id 28757, offset 0, flags [DF], 
proto VRRP (112), length 56) 192.168.1.2 > 224.0.0.18: VRRPv2, 
Advertisement, vrid 74, prio 100, authtype none, intvl 1s, length 36, 
addrs(7): 
156.231.51.105,143.57.8.22,34.65.134.219,132.160.185.229,103.202.156.249,174.25.227.190,231.95.30.57
10:08:14.061257 00:00:5e:00:01:4a > 01:00:5e:00:00:12, ethertype IPv4 
(0x0800), length 70: (tos 0x10, ttl 255, id 28769, offset 0, flags [DF], 
proto VRRP (112), length 56) 192.168.1.2 > 224.0.0.18: VRRPv2, 
Advertisement, vrid 74, prio 100, authtype none, intvl 1s, length 36, 
addrs(7): 
156.231.51.105,143.57.8.23,91.0.105.24,240.239.51.204,21.9.216.6,232.26.58.127,73.8.235.226

However, when I do the NIC teaming on ESXi, I constantly see 2 packets 
arrive at the same time and I get the 'more frequent advertisement 
received' message in the logs:

10:10:47.527982 00:00:5e:00:01:4a > 01:00:5e:00:00:12, ethertype IPv4 
(0x0800), length 70: (tos 0x10, ttl 255, id 30136, offset 0, flags [DF], 
proto VRRP (112), length 56) 192.168.1.2 > 224.0.0.18: VRRPv2, 
Advertisement, vrid 74, prio 100, authtype none, intvl 1s, length 36, 
addrs(7): 
156.231.51.105,143.57.8.129,248.175.196.213,178.47.150.234,200.203.153.156,219.129.15.78,19.136.6.207
10:10:47.529163 00:00:5e:00:01:4a > 01:00:5e:00:00:12, ethertype IPv4 
(0x0800), length 70: (tos 0x10, ttl 255, id 30136, offset 0, flags [DF], 
proto VRRP (112), length 56) 192.168.1.2 > 224.0.0.18: VRRPv2, 
Advertisement, vrid 74, prio 100, authtype none, intvl 1s, length 36, 
addrs(7): 
156.231.51.105,143.57.8.129,248.175.196.213,178.47.150.234,200.203.153.156,219.129.15.78,19.136.6.207

Does anybody know what could be going on, and whether it's possible to 
get this working?

Thanks in advance,
Sebastiaan


[-- Attachment #2 --]
0	*H
010	+0	*H
	Q00lS|
6$1-~j0
	*H
0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
080630135157Z
090630135157Z0h10Uvan Erk10U*
Sebastiaan10USebastiaan van Erk1"0 	*H
	sebster@sebster.com0"0
	*H
0
Va\bEnݚa<M8ʄ^tv>x73bohi2oqS_¶Bm^p*I	x"9pt!jar#)n)^?'z<).+Ѐ4igR'UP*\Ւ,?.;?fBܯTzM IDվCK*3Yŧ
mcaztxʐsq/00.0U0sebster@sebster.com0U00
	*H
KT4W6ӽq]
tS` %f1G:HbzJj$EjE'JV~-VbVnJZE/`@@04!+T:c	پf`$Z=1#|oG[OBRG00lS|
6$1-~j0
	*H
0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
080630135157Z
090630135157Z0h10Uvan Erk10U*
Sebastiaan10USebastiaan van Erk1"0 	*H
	sebster@sebster.com0"0
	*H
0
Va\bEnݚa<M8ʄ^tv>x73bohi2oqS_¶Bm^p*I	x"9pt!jar#)n)^?'z<).+Ѐ4igR'UP*\Ւ,?.;?fBܯTzM IDվCK*3Yŧ
mcaztxʐsq/00.0U0sebster@sebster.com0U00
	*H
KT4W6ӽq]
tS` %f1G:HbzJj$EjE'JV~-VbVnJZE/`@@04!+T:c	پf`$Z=1#|oG[OBRG0?0
0
	*H
010	UZA10UWestern Cape10U	Cape Town10U
Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0)	*H
	personal-freemail@thawte.com0
030717000000Z
130716235959Z0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00
	*H
0Ħ<UsUNʙZhup[v:aQP
0cZ,p+Z?qV˯<6$*+w=+>@dקe*TH<a@dr`00U00CU<0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0U0)U"0 010UPrivateLabel2-1380
	*H
HP.
fgCL!6-6/P p<ab:~t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$F]_eO1q0m0v0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAS|
6$1-~j0	+0	*H
	1	*H
0	*H
	1
090404082052Z0#	*H
	1:[/1r:a7C+0_	*H
	1R0P0	`He0
*H
0*H
0
*H
@0+0
*H
(0	+71x0v0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAS|
6$1-~j0*H
	1xv0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAS|
6$1-~j0
	*H
YоG._,))0+3ܳ5[5;muf.fȮ"͏#n+#@ 'yh:WoJ]#)ݗKUMP2̯J8B]t+]7y&jNAd,KX~Hsҷd\w4ytY~|w5#Ws72L-_m&Z+Ms,+?,iguD\`5(ہꚺ

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49D71864.3010403>