Definitive recommendation for bonding Broadcom NICS?
andrew at aei.on.ca
Wed Oct 13 12:45:01 CDT 2004
There shouldn't be a need to recompile the bcm5700 kernel driver
as the tg3 driver should get the job done. I have 4 PE 2650's running
Red Hat ES 3 Update 2 and the tg3 driver works just fine under a
bonded configuration (active-standby mode) using the bonding driver.
And it actually works just fine! The bonded configuration using the
tg3 driver also works without issues under heavy loads (since I perform
remote backups over the Gibabit network to a Tape Library).
There were issues with the tg3 driver (not being able to set speed
and duplex) and bonding (ARP issues) on Red Hat ES, the original.
These issues disappeared after Update 2.
Hope that helps.
On Wed, 2004-10-13 at 13:06, Kevin M. Myer wrote:
> I have a rack of 2650's that I want to use a NIC bonding driver with (failover
> and loadbalance mode). I'm finding it extremely cumbersome to have to
> recompile the bcm5700 and basp drivers for every kernel upgrade. And with RHEL
> 3, Update 3, I find I have to restart the network after initial boot for the
> default route to get set properly. But I'm also seeing posts from folks that
> tg3 doesn't handle well under high loads so using that and the bonding driver
> thats include with Red Hat EL might not work either.
> What is the definitive recommendation for a bonding driver for Broadcom NICS?
> Or isn't there one?
> Kevin M. Myer
> Senior Systems Administrator
> Lancaster-Lebanon Intermediate Unit 13
> (717) 560-6140
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> Please read the FAQ at http://lists.us.dell.com/faq
More information about the Linux-PowerEdge