similar to: Configuring bonding in domU

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

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

*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

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

I''m having some trouble getting bridging and bonding working in Ubuntu Hardy. This is with the Xen kernel (appears to be happening with both, however.) I''ve tried about 10 different configurations, and posted below is the latest. auto br0 iface br0 inet static address 10.0.1.27 gateway 10.0.1.1 network 10.0.0.0 netmask 255.255.0.0 pre-up /sbin/ifconfig eth0 up pre-up

On 20/09/2019 04:55, Carlos A. Carnero Delgado wrote: > 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 >

Hi *, I'm running into a problem configuring bonding on an HP DL 360 G4p, running 4.3 + tg3 driver version 3.43f. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes, including balance-rr (0), active-backup (1), and balance-alb (6). All have the

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

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

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

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

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