Bug 185730
| Summary: | Only one bonding device bond0 possible | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Rene Zbinden <rene.zbinden> |
| Component: | iputils | Assignee: | Radek Vokál <rvokal> |
| Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | baif |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-10-19 18:46:01 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: | |||
can I also have ifcfg-* files from /etc/sysconfig/network-scripts Which version of iputils exactly are you using? Had the problem been solved? This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |
Description of problem: I need two bonding devices bond0 and bond1. I followed the procedure described in /usr/share/doc/iputils-20020927/README.bonding and made the following lines in /etc/modprobe.conf alias bond0 bonding alias bond1 bonding options bond0 miimon=100 options bond1 -o bonding1 arp_interval=200 arp_ip_target=10.0.0.1 When I start the network I get the following messages: Bringing up loopback interface: ip_tables: (C) 2000-2002 Netfilter core team [ OK ] Bringing up interface bond0: ip_tables: (C) 2000-2002 Netfilter core team bonding: Warning: failed to get speed/duplex from eth2, speed forced to 100Mbps, duplex forced to Full. [ OK ] Bringing up interface bond1: bonding device bond1 does not seem to be present, delaying initialization. [FAILED] And when I have a look at /proc/net/bonding there is only bond0 visible. Version-Release number of selected component (if applicable): How reproducible: As described above Steps to Reproduce: 1./etc/init.d/network stop 2.rmmod bonding 3./etc/init.d/network start Actual results: No bond1 device available Expected results: bond1 device should be available Additional info: