Bug 679024

Summary:	Can't load bonding module without set the miimon value using network script method .
Product:	Red Hat Enterprise Linux 6	Reporter:	Hangbin Liu <haliu>
Component:	initscripts	Assignee:	initscripts Maintenance Team <initscripts-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	notting
Target Milestone:	rc
Target Release:	6.1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-21 17:07:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Hangbin Liu 2011-02-21 10:24:46 UTC

Description of problem:

miimon specifies the MII link monitoring frequency in milliseconds , the default value is 0 . I just want to load the bonding module ,so using the network script method whithout setting the BONDING_OPTS option , but failed .

Version-Release number of selected component (if applicable):

# uname -ri
2.6.32-117.el6.i686 i386

How reproducible:

Everytime

Steps to Reproduce:
1.
# service network stop
2.
# cat /etc/modprobe.d/bonding.conf
alias bond0 binding
# cat /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
3. 
#service network restart
  
Actual results:

Bringing up interface bond0:  binding device bond0 does not seem to be present, delaying initialization.
[FAILED]

Expected results:

Bringing up interface bond0:  [  OK  ] 

Additional info:

I can bring up bond0 on RHEL5 successfully with this way .

Comment 2 Bill Nottingham 2011-02-21 17:07:48 UTC

You need to set the parameters either in modprobe.conf, or in BONDING_OPTS; you can't leave both blank.