similar to: Channel bonding on Guest VM being slow

I don''t know if there was a problem in the archive or not, I just wanted to link to this post of mine, but I could not find it in the archive. So here''s a re-post. -------- Original-Nachricht -------- Betreff: [Xen-users] Xen, NIC bonding, ARP problem Datum: Fri, 30 Mar 2007 10:05:45 +0200 Von: Dominik Klein <dk@in-telegence.net> An: xen-users@lists.xensource.com Hi

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

Hello, I have a server with 4 NICS running CentOS 5.2. I have bonded the interfaces together such that 'bond0' consists of eth0-3. This is not a problem, and works fine. However, I now need to create a virtual interface. In a non-bonded server I would just create something like eth0:1, but with a bonded interface I am a bit confused. I have created bond0:1 simple by copying the

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It''s always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the

I have the following networking setup: - eth0 and eth1 corresponding to the physical ports on the host NIC - bond0 which enslaves eth0 + eth1 - br0 which attaches bond0 - xenbr0 - xenbr5 all of which are internal only networks (10.0.0.0; 10.1.1.0; etc) Br0 is used both for the host to access the outside world as well as DomUs acting as gateway machines for each xenbr network. For example the

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.

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

Greetings all. This has been an ongoing issue for me for a few months, and I''ve been trying to get an answer. My server has two NICs, and I want to set up the following: NICs (x2) -> bond (mode 5) -> Xen Bridge -> Doms ...however, trying to configure this doesn''t seem to work: network-bridge steals eth0 instead of bond0, which breaks the bond AND my networking. The

Hi everyone After configuring bonding eth0 and eth1 in domU, "cat /proc/net/bonding/bond0" showed it was configured correctly. ----------------------------------------------------------------------------------------- Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth1 Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms):

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

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

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, I''m not quiet sure the most reasonable way to dealing with bonding on xenserver. My configuration is as follow. It was ok if i do nothing, but When I tried to ''service network restart'', the bond is break. Then, /proc/net/bonding/pbond: Slave Interface: eth0 eth1 was down bonding MII status: down My questions are: how to deal with this situation? how to avoid

Hi all, i recently found that some frontend servers (Centos6) show: kernel: bonding: bond0: link status definitely up for interface eth2. kernel: bonding: bond0: link status definitely down for interface eth2, disabling it kernel: bonding: bond0: link status definitely up for interface eth2. On some days frequently and on others none. But there is no hw failure or similar. $ cat

Hello! I would like to use the new bonding feature of kickstart in release 6.4. My setup is one bonding interface (bond0) with two (eth0, eth1) ethernet cards. I am using two VLANs on bonding interface so I have no IP for bond0 but have IPs for bond0.1 and bond0.2. If I create config by hand it works. Now I would like to convert my kickstart file using the new bonding feature. The kickstart

I am able to bring up a bonded NIC in Centos4 without requiring to bring up the bond0 with an ip address, but with CentOS-3 I must assign the NIC an address or eth0 and eth1 will not slave. I need to bring bond0 up without an ip address becuase I will be using tagged VLANs. ie. <snip /etc/sysconfig/network-scripts/ifcfg-bond0> DEVICE=bond0 BOOTPROTO=none ONBOOT=yes IPADDR=169.254.0.1

Hi Gerhard; I'm pretty new to this list too but I think this may be a bonding issue. What bonding mode are you using in /etc/modprobe.conf? You should have a couple of lines in there: alias bond0 bonding options bond0 miimon=x mode=x What kind of switch are you connecting to and have you done any specific configuration to the switch to support your bonding mode? (depends on the mode).

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

On 18/04/2017 15:54, Frank Thommen wrote: > 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