Bug 679024 - Can't load bonding module without set the miimon value using network script method .
Summary: Can't load bonding module without set the miimon value using network script m...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts
Version: 6.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.1
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-21 10:24 UTC by Hangbin Liu
Modified: 2011-02-21 17:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-21 17:07:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.