Hi
I have added this following to my modprobe.conf file:

install bonding /sbin/modprobe bnx2; /bin/sleep 4; /sbin/modprobe e1000;
/sbin/modprobe --ignore-install bonding

in the hope that it would force bnx2(eth0 eth1) to be the active slave
however it does not do the trick. Does anyone have any ideas on why
not... and how to get it working...

Regards

> -----Original Message-----
> From: rhelv5-list-bounces@(protected)-
> bounces@(protected)
> Sent: 02 April 2008 13:06
> To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
> Subject: RE: [rhelv5-list] bonding problems
>
> hi
> RTFM...
> I am reluctant to speak to soon but we seem to have solved the
problem.
>
> We ended up putting a laptop on each switch and then cloning traffic
to
> the laptop and capturing it with wireshark. We also did a tcpdump on
the
> server locally on each interface.
>
> Our conclusions from this test was that a gratuitous arp was send by
the
> bonding driver and is seen locally on the relevant interface but is
> never received/seen by the switch.
>
> This is actually mentioned in some way in the bonding documentation.
>
> The solution has been to set an updelay for the bond interface. That
way
> the switch gets a chance to get its ducks in a row before the
interface
> becomes active. We have found 250ms to be a good value for the
updelay.
> 100ms have been to quick...
>
> Btw,
> The documentation for bonding makes mentioning of specifying load
order
> of modules.
> Thus anyone know how to translate kernel 2.4 modules.conf
> to kernel 2.5 modprobe.conf settings?
> The command is :
> add above bonding e1000 bnx2
>
> Regards

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list