I don't think that's how bonding works when you set up an active-passive bond.
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html What will happen when you set up the bonded interface is that you assign an IP address to bond0; ethX and ethY will have no IP at all, and in fact one of their MACs will vanish from the system. When you start getting into active-active things my change a bit, but I've only used active-passive, and I know that there's only ever one IP, and that goes to the bond0 device. ---- Paul Krizak Staff IT Engineer, IAS Qualcomm, Inc -----Original Message----- From: rhelv5-list-boun...@redhat.com [mailto:rhelv5-list-boun...@redhat.com] On Behalf Of Marco Shaw Sent: Thursday, March 08, 2012 9:07 AM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: [rhelv5-list] NIC bonding I'm possibly looking at testing bonding in a "single network fabric" environment. I was thinking of giving NIC1 IP1, NIC2 IP2, and then creating BOND0 with IP3. Is this do-able? All of the IPs are going to be routed through the same networking device. I'm planning on an active-passive setup, so when I pull the network cable on NIC1, I'd expect IP3 to be service from NIC2. Marco _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
