similar to: Pair-bonding on virtualized servers, particularly on CentOS 7

Silvertip257, when you did this CentOS 6/KVM/bonding/bridging, did you ever get all the parts playing together correctlhy? I'm facing a setup with only two NIC's, and need for multiple trunked VLAN access, and bonded pairs, and KVM based bridges to get the VM's with exposed IP addresses. I can get basically any 2 out of the 3 server network components working, binding, VLAN's, or

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):

hi, bonding does not work when booting kernel-PAE-2.6.18-164.el5 module load failed on unresolved symbols Sep 17 11:36:53 monitor kernel: bonding: Unknown symbol ndisc_build_skb Sep 17 11:36:53 monitor kernel: bonding: Unknown symbol in6_dev_finish_destroy Sep 17 11:36:53 monitor kernel: bonding: Unknown symbol ndisc_send_skb Sep 17 11:36:53 monitor kernel: bonding: Unknown symbol

*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

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

Dear All, 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 Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in

Dear All, I have configured RHEL 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) In am followed the RHEL Cluster Suite Configuration document "rh-cs-en-4.pdf" and I have configured Ethernet Channel Bonding in

Dear All, 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 Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in

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 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

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

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

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

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

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

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 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:

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 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

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