I'm not near the server for a while but network is set up

2x broadcom nic with whatever driver works out of the box.

Both set as slaves to bond0 which is in mode=4 with no explicit options.

Switch is a fairly basic tp-link but works almost identically to a Cisco. Has 
the 2 ports set up in a portchannel.

Short and long, this config works in earlier kernel, but not with kernel 
shipped in 7.2

Release notes for RH7.2 suggest some work on bonding has been done, wonder if 
default options (LACP speed?) have changed?


On 30 December 2015 09:44:02 GMT+00:00, Dan Kenigsberg <dan...@redhat.com> 
>On Tue, Dec 29, 2015 at 09:57:07PM +0000, Jon Archer wrote:
>> Hi Stefano,
>> It's definitely not the switch, it seems to be the latest kernel
>> (kernel-3.10.0-327.3.1.el7.x86_64) which stops bonding working
>> reverting back to the previous kernel brings the network up in
>802.3ad mode
>> (4).
>> I know, from reading the release notes of 7.2, that there were some
>> to the bonding bits in the kernel so i'm guessing maybe some defaults
>> changed.
>> I'll keep digging and post back as soon as i have something.
>> Jon
>> On 29/12/15 19:55, Stefano Danzi wrote:
>> >Hi! I didn't solve yet. I'm still using mode 2 on bond interface.
>> >your switch model and firmware version?
>Hi Jon and Stefano,
>We've been testing bond mode 4 with (an earlier)
>kernel-3.10.0-327.el7.x86_64 and experienced no such behaviour.
>However, to better identify the suspected kernel bug, could you provide
>more information regarding your network connectivity?
>What is the make of your NICs? Which driver do you use?
>Do you set special ethtool opts (LRO with bridge was broken in 7.2.0
>kernel if I am not mistaken)?
>You have the ovirtmgmt bridge on top of your bond, right?
>Can you share your ifcfg*?

Sent from my Android device with K-9 Mail. Please excuse my brevity.
Users mailing list

Reply via email to