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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey guys, i'm a newbie to the forum so go easy on me. I am trying to bond IP Addresses on dual nic'd HP Proliant Blade servers. Anyone know the easiest way to go about this? The servers are running red hat 8.0. Also, if anyone has experience w/ red hat and proliant servers, have you installed insight agent and if so any good sources for that? thanks all!!!
I have never come across this before... I would guess do:
ifconfig eth0 < IP Addreess> broadcast < Broadcast Address > netmask < Subnet Mask >
ifconfig eth0 < IP Addreess> broadcast < Broadcast Address > netmask < Subnet Mask >
with the same IP address... How are you routing this though... You cant set a router to have the same IP address on two different interfaces... At least as far as I know...
You will need to add at least the following line to /etc/modprobe.conf
so the bonding driver will automatically load when the bond0 interface is
configured. Refer to the modprobe.conf manual page for specific modprobe.conf
syntax details. The Module Parameters section of this document describes each
bonding driver parameter.
alias bond0 bonding
Next you need to configure the contents of /etc/sysconfig/network-scripts/
ifcfg-bond0 should contain the following: (customize for your network)
All interfaces that are part of a bond should have SLAVE and MASTER
definitions. For example, in the case of Red Hat, if you wish to make eth0 and
eth1 a part of the bonding interface bond0, their config files (ifcfg-eth0 and
ifcfg-eth1) should resemble the following:
Use DEVICE=eth1 in the ifcfg-eth1 config file. If you configure a second
bonding interface (bond1), use MASTER=bond1 in the config file to make the
network interface be a slave of bond1.
then commit the bond:
modprobe bonding mode=1 miimon=500
now perform:
service network restart
to restart the interfaces and ensure that the bond is complete
to test the bond, unplug one cable, and see if you can still ping, btw the above config is for fault tolerance teaming, not etherchannel or round robin, to do etherchannel or round robing you need to modify your parameters when you modprobe bonding.
Hello I have successfully bonded many nics on various machines with HP's bonding driver .. please make sure you read the bonding mini how to and have the pre-requsite drivers ie .. e1000 and bcm5700 .. it should all work .. but I have recently run into a conflict with the HP Insite Agent (healt manager ) breaking my bonding driver .. Any one else ?? thanks !!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.