similar to: Bonding mode balance-alb (6): How to control the assigned MAC address?

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

Since I upgraded from 4.4 to 4.5 my system which has 2 sets of ALB bonded interfaces hangs on shutdown while doing an ifdown on these interfaces. Has anyone else seen this issue with 4.5 and bonding? Ross S. W. Walker Information Systems Manager Medallion Financial, Corp. 437 Madison Avenue 38th Floor New York, NY 10022 Tel: (212) 328-2165 Fax: (212) 328-2125 WWW: http://www.medallion.com

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

With the current talk on bonding, I have a few questions of my own. I'm setting up a KVM host with CentOS 6.3 x86_64 on which I'd like to attach the VMs to a bonded interface. My target setup is one where two GigE NICs are bonded and then the KVM bridge interface is attached to the bonded interface. Initially I tried to use the balance-alb mode (mode6), but had little luck (receiving

I haven't done any testing of performance differences, but on my oVirt/rhev i use standard bonding as that's that it supports. On the stand along gluster nodes I use teaming for bonding. Teaming may be slightly easier to manage, but not by much if you are already used to bond setups. I haven't noticed any bugs or issues using teaming. *David Gossage* *Carousel Checks Inc. | System

I'm looking at tuning up a new site and the bonding issue came up A google search reveals that the gluster docs (and Lindsay) recommend balance-alb bonding. However, "team"ing came up which I wasn't familiar with. Its already in RH6/7 and Ubuntu and their Github page implies its stable. The libteam.org people seem to feel their solution is more lightweight and it seems easy

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 am working on setting up an NFS server, which will mainly serve files to web servers, and I want to setup two bonds. I have a question regarding *which* bonding mode to use. None of the documentation I have read suggests any mode is "better" than other with the exception of specific use cases (e.g. switch does not support 802.3ad, active-backup). Since my switch *does* support

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

On 07/07/16 05:36 PM, Digimer wrote: > On 07/07/16 05:21 PM, Joe Smithian wrote: >> Hi All, >> >> I see an unexpected beahviour from NetworkManager on CentOS 7.1. >> Using nmcli tool, I create a bond with two slaves as explained in the Red >> Hat 7.1 Networking guide. I enable slaves and master; bond works as >> expected. >> When I restart

Hi All, I see an unexpected beahviour from NetworkManager on CentOS 7.1. Using nmcli tool, I create a bond with two slaves as explained in the Red Hat 7.1 Networking guide. I enable slaves and master; bond works as expected. When I restart NetworkManager, it creates a new bond with the same name but not connected to any device. Two bonds with the same name is confusing for my other monitoring

Hi, ------- ------- | B |eth0---------eth0| C | | |eth1---------eth1| | ------- ------- In an attempt to have the install setup to increase speed and/or reliability of a link between two linux machines (for example in case of a wireless connection), I read that there were more than one solution, for example the old eql driver, bonding

Hi, I install a new 4 Port GBit Server with centos 6.3 and I'd like to use nic bonding. Searching for a good how to pinted to this page: http://www.how2centos.com/centos-6-channel-bonding/ My question: Is this the current, good way to bond the 4 ports? The other question: What should I set on the cisco switch for the Port-channel options? As far as I understand for performance and

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

Greetings- I'd like to configure multiple copper NICs on a server running CentOS 6.2 in a LAGG configuration for better throughput to the core switch. After quite a bit of searching, I'm not seeing anything of the sort. Is LAGG specific to the BSD world and the HP switches I'm running? Or, does it go by a different name? Bonding perhaps? If so, is bonding compatible with LAGG? --Tim

Hi, I do have one iscsi storage with 4 GBit nics of which currently only one is configured with an ip and which is in productive use by one cent os 6.3 server. Doing some research brought me to the idea to use some nic bonding or multipathing for that storage, but multipathing I did about four or five years ago only once :) Furthormore I can't find the ultimate answer (may be there is not

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

Hi, I have a dataset called 'fish'. fish$Species returns extract 1. When I use fish$Species != c("CRA","PHC"), i.e. I want all species except "CRA" and "PHC", I get extract 2 which is blatantly wrong. Can anyone see what I'm doing wrong? Regards, James EXTRACT 1 > fish$Species [1] ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB

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