Date: Wed, 18 Apr 2007 11:50:36 -0400 From: Sven Willenberger <sven@dmv.com> To: freebsd-stable@freebsd.org Subject: CARP and em0 timeout watchdog Message-ID: <1176911436.7416.8.camel@lanshark.dmv.com>
next in thread | raw e-mail | index | archive | help
I currently have a FreeBSD 6.2-RELEASE-p3 SMP with dual intel PRO/1000PM
nics configured as follows:
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 192.168.0.18 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:30:48:8d:5c:0a
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 4096
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 10.10.0.18 netmask 0xfffffff8 broadcast 10.10.0.23
ether 00:30:48:8d:5c:0b
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
the em0 interface connects to the LAN while the em1 interface is
connected to an identical box via CAT6 crossover cable (for
ggate/gmirror).
Now, I have also configured a carp interface:
carp0: flags=49<UP,LOOPBACK,RUNNING> mtu 1500
inet 192.168.0.20 netmask 0xffffffff
carp: MASTER vhid 1 advbase 1 advskew 0
There are twin boxes here and I am running Samba. The problem is that
with transfers across the carp IP (192.168.0.20) I end up with em0
resetting after a watchdog timeout error. This occurs whether I transfer
files from a windows box using a share (samba) or via ftp. This problem
does *not* occur if I ftp to the 192.168.0.19 interface (non-virtual). I
suspected cabling at first so had all the cabling in question replaced
with fresh CAT6 to no avail. Several gigs of data can be transferred to
the real interface (em0) without any issue at all; a max of maybe 1 - 2
Gig can be transferred connected to the carp'ed IP before the em0 reset.
Any ideas here?
Sven
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1176911436.7416.8.camel>