Re: NIC Teaming
- From: "Michael Simpson" <mikie.simpson@xxxxxxxxx>
- Date: Mon, 31 Mar 2008 13:34:56 +0100
On 3/27/08, Gerrard Geldenhuis <Gerrard.Geldenhuis@xxxxxxxxxxxx> wrote:
Hi Vivek,
It is also called bonding which might yield better results in google.
It is actually very simple:
Create a new file called ifcfg-bond0 in /etc/sysconfig/network-scripts/
with the following data inside:
DEVICE=bond0
BOOTPROTO=static
ONBOOT=yes
IPADDR=Your ip here
NETMASK=Your netmask here
In the interface that you want as part of the bond edit the appropriate
file. For example ifcfg-eth0 and ifcfg-eth2 which can also be found in
/etc/sysconfig/network-scripts/
You should edit out the ip address and netmask. Make sure the bootproto
is none, keep the hardware address, add slave=yes and add master=bond0
DEVICE=eth0
BOOTPROTO=none
HWADDR=AA:AA:C4:BE:AA:AA
ONBOOT=yes
TYPE=Ethernet
SLAVE=yes
MASTER=bond0
Hi there
i thought that you were meant to remove the HWADDR= lines from
ifcfg-eth0 and ifcfg-eth1 as bonding manipulates these values to make
the necessary arp magic work.
the documentation seems to support this view.
mike
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- Follow-Ups:
- RE: NIC Teaming
- From: Gerrard Geldenhuis
- RE: NIC Teaming
- References:
- RE: NIC Teaming
- From: Aggarwal Vivek-Q4997C
- RE: NIC Teaming
- From: Gerrard Geldenhuis
- RE: NIC Teaming
- Prev by Date: Samba + CUPS high cpu usage and huge logfiles
- Next by Date: RE: NIC Teaming
- Previous by thread: RE: NIC Teaming
- Next by thread: RE: NIC Teaming
- Index(es):
Relevant Pages
|
|