This bug has been copied from bug #516569 and has been proposed to be backported to 5.5 z-stream (EUS).
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Due to an incorrect loading of the bonding driver module, certain systems may not have been able to activate a bonding interface. This error has been fixed, and the bonding driver is now correctly loaded when an ifcfg script contains the "BONDING_OPTS" option.
we successfully tested initscripts-8.45.30-3.el5_5.1 on RHEL5.5 on Linux ibm-x3650m3-02.lab.eng.brq.redhat.com 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux When adding: BONDING_OPTS=" miimon=100 mode=4 lacp_rate=1 " into /etc/sysconfig/network-scripst/ifcfg-bond0 bonding driver is successfully loaded withou affecting /etc/modprobe.conf. We tested bonding driver against Cisco c3560e both with two and four interfaces in port-channel and only two cables connected to server. In both cases bond0 remains in bridge after reboot. Closing with verified status
Reproducer used for verification: 1. show the switch ports configuration, to declare how did we configure the ports, four in one bond or two in one bond. 2. to check whether the bonding work without modprobe.conf alias setup 3. to confirm whether the bonding work with BONDING_OPT setup in ifcfg-bond0
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0885.html