similar to: Error: dev_set_mac_address of dev

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into

Hi, Fedora got a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1401612 In qemu with two virtio-net interfaces: $ ip l ... 5: ens14: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:e9:64:41 brd ff:ff:ff:ff:ff:ff 6: ens15: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

Hi, Fedora got a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1401612 In qemu with two virtio-net interfaces: $ ip l ... 5: ens14: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:e9:64:41 brd ff:ff:ff:ff:ff:ff 6: ens15: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

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! Is it HTB fully compatible with BOND interface? I have this setup (mode= fault tolerance) : BOND0 -> ETH0 + ETH1 BOND1 -> ETH2 + ETH3 ( http://www.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Documentation/networking/bonding.txt ) HTB work very well with Class over BOND0. If I add Class for BOND1 it generate balance errors. Also with HTB.init

Hai, That bond0 interface, you might want to change that the interface name to bond1 Depending on the bonding settings, you might have hit a reserved name. I lots my docu on that but i know i configured a bond1 because bond0 didn work right. And then check these. wbinfo -pPt ( or wbinfo -p && wbinfo -P && wbinfo -t ) wbinfo --sids-to-unix-ids S-1-22-2-10513 wbinfo -D

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 CentOS, I think i found a "bug" in the /etc/sysconfig/network-scripts/ifup-eth script of CentOS 5.2. i can post the my changed ifup-eth script if you want. Am I the first one with this problem? Situation: - eth2 and eth3 should be in bond1 interface - bond1 should be an interface of bridge named "iscsi" the problem is that the brctl addif command in ifup-eth gets

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

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,

Hi, In one of our xen server, I am using two bonding. bond0 : Is for trunk, where the vlans are attached , port eth0 & eth1 is attached to bond0 bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the

Hi List, We're using bonding to create bond0 with 2 NICs, and noticing that CentOS 5 2.6.18-8.1.14.el5 (and presumably older) creates bond1 as well. I'd like to remove bond1 from the system, so that our monitoring scripts don't pick it up, except for those machines that actually do have a bond1. So... how does one remove bond1? Thanks! Misc info below of configuration and

Hello, Where can I find a link (or docs) to *working* network config for xen 4.1.2? My tests (s. below) were not successful. Thank you in advance for any hints. Regards, Mark # --- root@xen411dom0:~# cat /etc/network/interfaces # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback auto bond0

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox

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 and an independent, non-bonded network device. Also the bonding device

OK, at least its not an *issue* with Gluster. I didn't expect any but you never know. I have been amused at the 'lack' of discussion on Teaming performance found on Google searches. There are lots of 'here it is and here is how to set it up' articles/posts, but no 'ooh-wee-wow it is awesome' comments. It seems that for most people Bonding has worked it kinks out

Hi, Sorry of this is the wrong list, trying to find some help. I am trying to set up 2 KVM hosts using Debian 9 (connecting to a 3 node Centos 7.4 gluster cluster) To get the bandwidth I have bonded 2 NICS each end. However while the network works fine for the Debian VM host the VM guests cannot connect/get an IP using DHCP connecting to br0. (Same setup on the Centos end works fine however)

Hi, we are trying to switch our bonding modes from 1 (active-backup) to 6 (balance-alb). However it seems, that these bond devices are not always getting the MAC address from the same slave. Sometimes the device gets the MAC address of the first and sometimes of the second slave. Since only the MAC address of the first slave device is (can be) registered in DHCP, this breaks connectivity

# modinfo ixgbe filename: /lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/net/ixgbe/ixgbe.ko version: 3.15.1-k license: GPL description: Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, <linux.nics at intel.com> srcversion: B390E9D9904338B52C2E361 I have updated this to 3.18.7-1 as well, same results # ifconfig bond1 |grep error

With kernel 2.6.13.4 linux bridge with traffic management for 4000users and 20.4 MB/s(tx)/22.4 MB/s(rx) data load of CPU is max 50% With kernel 2.6.15.1 the same linux bridge with the same traffic has 100% CPU load and in top I have ksoftirqd proccess. The machine is P4 3.2 GHz with 1GB of ram and 4 NetGear 620 cards The config is: /sbin/modprobe acenic link=0x0100,0x0100,0x0100,0x0100