similar to: Xen with NIC Bonding on Debian Etch ?

Hi all, i have a xen 4.3 installation and would like to have a bridge bond szenario: *** eth0 eth1 | | bond0 | br0 | vif = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ] *** With the network script in debian wheezy *** /etc/network/interfaces auto bond0 iface bond0 inet manual slaves eth0 eth1

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

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

Hi all, I've setup a ethernet bond on my centos 5.6 server , when i do a reboot the bond does come up but cleared all the slaves and i've to manually re-add them with ifenslave. does anyone know a solution to this? am i missing something? offcourse i can add it to my rc.local but there must be a more elegant way. please see my configs below Thanks, Wessel ifcfg-bond0: DEVICE=bond0

Hello all, I'm having unusual difficulty configuring teaming with Centos 4.2. The 2 NIC's are Broadcom. The HW is HP DL360 and there is no teaming driver for RHEL4 since it comes with package (says HP). Since there is no teaming driver from centos (as far as I know), I tried the Broadcom Driver, configured the team file, but the team just wont come up. A Virtual Interface should be up

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

took a couple months off due to road blocks, hoping a fresh look would allow me to use my server as desired. I have three ports, eth0-2 over two nics. I want to bond them, and then use a bridge to connect to virtual machines on the virtual host computer. Never having done this, I am confused on some parts. Here is where I am at now and any pointers helpful. Single server, centos 6.x My issue

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

Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup

I'm running into a situation where a bogus bonded interface named "bond0" is being created, in addition to the desired "bond2" interface. Can anyone confirm this? Anyone know why it's happening or what I do to get rid of it? I wanted to start my numbering scheme at 2 instead of 0, which I didn't think would be a problem. As you can see, I have no reference

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 just upgraded a machine to 7.7.1908 and the default route is not being set on boot. This particular server has a bonded interface, and the corresponding configuration for the master is ( /etc/sysconfig/network-scripts/ifcfg-bond0): TYPE=Bond BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes NAME=bond0 DEVICE=bond0 ONBOOT=yes IPADDR=10.3.20.131 PREFIX=24

I have two servers with identical hardware ... TYAN i3210w system boards with dual intel gigabit interfaces, and a PCI intel gigabit nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5 Every other time I reboot, the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However,

I was given the challenge recently of creating a LAN-LAN bridge between two buildings several hundred metres from each other, using only existing Cat 3 wiring and without having to resort to an expensive and finicky 5 Ghz wireless link. I was able to create a 90 megabit link for about $3,000 Cdn with new PC's, CentOS 4.1, and the newly avaliable Black Box VDSL Ethernet Extender, which

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

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

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 all, we are testing CentOS 7 in order to migrate from Scientific Linux 6 / CentOS 6 and we are facing an issue with the network. Trying to configure network with teaming in activebackup mode or also with bonding in mode=1 (active backup as well) we see many RX dropped packets in the bond0 interface (around 10% of the total), 100% RX drops in the backup interface and 0% in the active interface.

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found