Oracle Enterprise Linux 5.3 NIC bonding on a Dell PE2950/PER 900
Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
/etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias scsi_hostadapter megaraid_sas
alias scsi_hostadapter1 ata_piix
alias scsi_hostadapter2 qla2xxx
alias peth0 bnx2
alias bond0 bonding
options bonding miimon=100 mode=0
after the configuration, when I restart the Network service, the following Messages are displays
service network restart
Shutting down interface bond0: bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:24:E8:5E:8F:F3 - is still in use by bond0. Set the HWaddr of eth0 to
a different address to avoid conflicts.
[ OK ]
Shutting down interface eth0: bonding: bond0: Unable to update slaves because interface is down.
[ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0
[ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
[ OK ]
please give me a solution how to solve this issue;
I seem to remember that things worked better when we ending ethernet bonding before restarting the network. I am looking for those notes and will update later.
After restarting networking with the warnings you posted, what do you see in the routing table? What do you see with the command `ethtool bond0`?
Correct me if I'm wrong, but it looks like bonding has failed when you restart, is that true? 'bond0' should be your operational interface, and it doesn't seem to be working, here.
I remember testing ethernet bonding on Cyclades devices. Our programmers, as I remember, put in a fix which either spoofed the MAC (I think they took the MAC of eth0 and make it the default machine address regardless of the active interface's real address).
There are issues with this. Not sure what to tell you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.