similar to: bonding

Hi, I've using linux bonding in active-backup mode to combine two pairs of GigE NICs (eth0/eth1, eth2/eth3) into two logical bonds (bond0/bond1). All is working fine. However, I would like to specify a primary interface for each bond. This means I need to specify different options to the bonding module for each bond. I have tried every conceivable incantation of options and cannot get the

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in

I four nodes setup to do active-backup bonding and the drivers loaded for the bonded network interfaces vary between tg3 and e100. All interfaces with the e100 driver loaded report errors much like what you see here: bonding: bond0: link status definitely down for interface eth2, disabling it e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex bonding: bond0: link status definitely up for

HI All. I have a linux box connected to a switch network with 2 network interfaces, how would I able to ''trunk'' these 2 interfaces? options I can see are: - ethernet bonding - iproute2? - teql Which one are the best to use? I''m curretly having problem with ethernet bonding, my setup are as follow: ip add: 192.168.10.30/24 I do: # modprobe bonding # ip addr add

Dear All, Please ignore my previous mail I have using CentOS 4.4 Linux and Kernel Version is 2.6.9-42.EL I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server) I have configured Ethernet Channel Bonding in

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Hi list How is ether bonding handled with Xen? Is it possible to use bonding inside a xen virtual server by bonding dom0s eth0 and eth1 or should a domU connect to dom0s "bond0" (eth0-eth1)? Is there any xen configuration examples using bonding somewhere? Thanks :) -- Med venlig hilsen / Best regards Lars E. D. Jensen - DCmedia ledj@dcmedia.biz - http://dcmedia.biz PGP PUBLIC KEY:

With the current talk on bonding, I have a few questions of my own. I'm setting up a KVM host with CentOS 6.3 x86_64 on which I'd like to attach the VMs to a bonded interface. My target setup is one where two GigE NICs are bonded and then the KVM bridge interface is attached to the bonded interface. Initially I tried to use the balance-alb mode (mode6), but had little luck (receiving

Hi, I'm trying to configure a network bridge over a bonding without any success. Here is my configuration: ifcfg-eth0: DEVICE=eth0 HWADDR=00:1E:C9:E8:3F:E5 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-eth1: DEVICE=eth1 HWADDR=00:1E:C9:E8:3F:E7 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-bond0: DEVICE=bond0 ONBOOT=yes BRIDGE=br0 USERCTL=no ifcfg-bridge0: DEVICE=br0

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

I've just setup nic bonding on our server (DL585-G7 running Centos 5.5 x86_64) as detailed on the wiki: http://wiki.centos.org/TipsAndTricks/BondingInterfaces and all seems fine but from other "howto's" I've seen on the web, they're should be a /proc/net/bond0/info As far as I can see, I don't have one and I'm not sure if it should be there or its absence is a

Hi guys, I am trying to get bonding work on a debian etch system. I searched already in the mailing list but unfortunately I couldnt find a proper solution. This is what i did so far. - Installed Debian Etch on my server - Installed the following packages for using Xen from the Debian repository: xen-hypervisor-3.0.3-1-i386-pae linux-image-2.6.18-5-xen-686 linux-image-2.6.18-5-xen-686 xen-tools

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [

Hello I have two linux machines connected via 2 dsl lines (bonded) 192.168.0.1-eth0-dsl---2Mbit---dsl-eth0-192.168.0.2 ^-eth1-dsl---2Mbit---dsl-eth1-^ so the final figure is something like this: 192.168.0.1-bond0---4Mbit---bond0-192.168.0.2 I can only use arp monitoring for fail checking - if one dsl line fails - automatically use only the other one. I set up everything correctly (i

Hello list, Please don''t shoot me. I know I''m doing something with bonding that bonding wasn''t made for. I just want to give it a try. I want a simple mechanism to have a failover on a 24Mbit line to a 2Mbit line in case the 24Mbit line goes down. Between A and B there are two lines: a 24Mbit and a 2Mbit. I use two OpenVPN tunnels with tap devices: +-- tap0 (A)---

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

Setting up bonding in active-backup mode 1 (using ARP monitoring) on a server, it looked OK, but pulling the active link cable didn't actually work, it didn't fail over. Eventually with manual playing around with modprobe, ifconfig, ifenslave, etc., a solution was stumbled upon: enslave the eth1 device before eth0, and all is good. Why this should matter is a puzzle - I could not find

Trying to think this through, hope someone can lend a hand. I have 3 eths I want to bond together and that seems simple enough. eth0,1,2 <-> bond0 , though not sure how this would be for multiple ip addresses needed for the virtual machines... perhaps eth:0, eth:1 etc....to bond0:1, bond0:2 ? then I want to bridge to my virtual machines.... I am going to be using virtual machines, each

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

Guys, good afternoon I'm using in my bond interfaces as active backup, in theory, should assume an interface (or work) only when another interface is down. But I'm just lost packets on the interface that is not being used and is generating packet loss on bond. What can that be? Follow my settings bond [root at xxxxx ~]# ifconfig bond0 ; ifconfig eth0 ; ifconfig eth1 bond0