Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 498480

Summary: [RHEL4.6] bonding mode=802.3ad always boot with first slave down
Product: Red Hat Enterprise Linux 4 Reporter: Flavio Leitner <fleitner>
Component: kernelAssignee: Jiri Pirko <jpirko>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: agospoda, pbatkowski, rkhan, tao, vfalico
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-05 20:05:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log of bonding with debug enabled
none
patch fixing link partner none

Description Flavio Leitner 2009-04-30 17:01:14 UTC 
After a normal boot, the system always comes up with first slave down.
If you manually set slave iface up by doing 'ip link set dev up' it comes 
back online. If you restart the network service the problem reproduces 
and if you de-enslave eth0 (ifenslave -d bond0 eth0), eth1 goes down.

Module options:
install bond0 /sbin/modprobe bonding -o bond0 miimon=500 mode=4 lacp_rate=fast xmit_hash_policy=layer3+4 use_carrier=0

Changing use_carrier=1 (default) didn't help.
There is a log with debug output enabled from bonding driver but I couldn't
see anything odd there.

The message logs shows the interface detected, then enslaved, link up and
finally link down.

Additional info:
"I have the same configuration in a DL580 server where I don't have an issue.
Also I don't have an issue with the BL680c (Full height blades) in the same
enclosure. Only the half height blades (BL460c) in the enclosure have the
issue. Both BL680c and BL460c share the same switches in the enclosure."
Comment 1 Flavio Leitner 2009-04-30 17:02:30 UTC 
Created attachment 341962 [details]
log of bonding with debug  enabled
Comment 4 Flavio Leitner 2009-04-30 17:08:50 UTC 
Created attachment 341965 [details]
patch fixing link partner

This patch was applied when bonding driver debug output was taken but 
it didn't help.
Comment 7 Jiri Pirko 2009-05-11 14:11:14 UTC 
Marking this as a duplicate. This issue is resolved in RHEL4.7.

*** This bug has been marked as a duplicate of bug 437865 ***
Comment 10 Jiri Pirko 2009-05-12 14:19:33 UTC 
Can you please provide additional info?

What machine does this issue occur at? Only BL460c? Do we have one suitable for internal testing?
Does this issue occur also with RHEL5 and upstream kernel?
Comment 11 Jiri Pirko 2009-05-12 14:28:19 UTC 
I want to also ask what appears on the output of "mii-tool" command and "ethtool eth2" after line "Mar 18 16:56:22 pmtraams02 kernel: bonding: bond0: link status definitely down for interface eth2, disabling it".

Thanks
Comment 12 Jiri Pirko 2009-05-13 18:00:08 UTC 
I tried to reproduce the problem on the only machine we have in rhts: hp-bl460c-02.rhts.bos.redhat.com. No luck :/
Comment 24 Paul Batkowski 2009-11-05 20:05:13 UTC 
Closing as a dup of bz#432622

*** This bug has been marked as a duplicate of bug 432622 ***