Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
We have 2 NIC cards and we need to configure channel bonding. We have configured etho,eth1 and bond0 as mentioned in Deployment guide. Issue is after restarting "Network" only bond0 is comming up. eth0 and eth1 remains down.
I think the issue is with the bonding driver. But not able to find the error
Well I'd wipe NetworkManager from the server, removing the NM_MANAGED options for a start. TBH, I've no idea if they will stop the NIC's loading, but it would think it likely.
IN RHEL we need both NIC cards up but not assigning any ip address individually. IP is assigned to bond0 alone. Now the scenario is like when is use the commands
ifconfig bond0 ipaddr
ifenslave bond0 eth0 eth1
it works fine but its a temporary solution. because when we restart the network service only bond0 is coming up
it might be a long shot but is your network manager not expecting the two interfaces to have an IP address? Maybe assign them an IP in a different subnet each?
Distribution: Fedora, CentOS, Scientific Linux, Oracle Enterprise, and RHEL
Posts: 156
Rep:
Your config files look right the only thing that I see is a nitpick is BONDING_opts should be BONDING_OPTS for sake of uniformity. Unless there is something else that is keeping things from working.
Typically we either do mode 4, or mode 1 for our bonds here so I am not as familiar with mode 0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.