similar to: bogus bond0 device showing up in /proc/net/dev

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

I have a machine I just deployed w/ tg3 interfaces, I have setup bonding on this same line of server (HP DL380 G4) a million times. I saw there were changes recently to how you configure a bond and have my setup configured according to: http://kbase.redhat.com/faq/docs/DOC-7431 The HP switch has a LACP trunk defined on the two ports. Problem is, when rebooting, I need to issue a `service network

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

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

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

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

Hi, last weekend I've updated samba and ctdb on my 2-node cluster. Samba is now on 3.5.6 (from 3.3.4), ctdb on 1.0.114 (from 1.0.84). Both installed from repo via yum and ctdb-packages. After restarting both nodes everything was fine, we could access files on the cluster. On monday I noticed that the nodes didn't had their initial adresses: Node 1: hostname dscln01, public IP

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

Hi all, I've got two gigabit ethernet interfaces bonded in CentOS 5.6. I've set "miimode=1000" and I've tried "mode=" 0, 4 and 6. I've not been able to get better than 112MB/sec, which is the same as the non-bonded interfaces. My config files are: === cat /etc/sysconfig/network-scripts/ifcfg-{eth1,eth2,bond0} # SN1 HWADDR=00:30:48:fd:26:71

Anyone know how to get statistics on bonded interfaces? I have a system that does not use eth0-3, rather we have bond0, bond1, bond2. The members of each bond are not eth0-3, rather they are eth6, eth7, etc. I didn't see anything in the man page about forcing sar to collect data on specific network interfaces.

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

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

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 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 try to get working together vlan and bonding both for dom0 and domU. I lost packets sent to dom0 while domU is OK. Nightly stats for dom0: 52879 packets transmitted, 45293 received, 14% packet loss, time 52879599ms rtt min/avg/max/mdev = 0.144/0.224/717.306/5.129 ms Nightly stats for domU: 52952 packets transmitted, 52952 received, 0% packet loss, time 52952554ms rtt min/avg/max/mdev =

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