similar to: CentOS 6 - Ethernet Bond Errors, 1 per frame

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

I have shifted some VM's to a new server running Quantal and have had a world of trouble. The first one was caused by issues with an apparently compiled in path in their apparmor version which forced VM pools to be in /srv or similar rather than where I wanted them. For now this was not a big issue, and thankfully the server where it would be a big time problem (there are individual drives per

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

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

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

Version 6.6 ... On Wed, Feb 25, 2015 at 1:17 PM, Jim Perrin <jperrin at centos.org> wrote: > <overly trimmed> > > On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > > Ok, so some of this now works, but I'm still having problems. With the > > bootif option, the system now correctly configures and uses the same > > interface to get its kickstart file.

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

Thanks for that Jason but it didn't solve the problem. The system is still coming up with the interfaces shuffled. It seems to *always* want to use the added ethernet card as eth0. On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr <jason at warr.net> wrote: > Starting back in RHEL/Cent 5 I found that the only way to make sure your > interface enumeration was consistent after install

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

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

Ok, when I run that, it creates a now "custom" 70-persistent-net.rules, but the interfaces are still out of order, with the added one listed first, and the built-ins 2nd and 3rd. On Wed, Feb 25, 2015 at 2:00 PM, Jason Warr <jason at warr.net> wrote: > Here is my script for post install if you want to try it. > > In order for the shuffling to not occur you do need to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

Out of order meaning, it puts the additional ethernet card as eth0, with the built-in ports as eth1 and eth2 respectively. WITHOUT the additional card installed, it puts the built-in ports as eth0 and eth1, which is what I want it to do. The additional card should be eth2, at least that's what I want it to do. Looking at persistent-net.rules, it always puts the additional card first, both

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 All, I''m configuring my natting-firewall to do some tc shaping. Some traffic has to be shaped on 30mbit, some on 10mbit all the others are unlimited. The configuring and filtering works correctly. The traffic that is shaped at 30mbit is correct, but the traffic that is shapped at 10mbit only gets to 100KB/sec. It is on a device configured with bonding (both in and out interface).

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, Could someone tell me, how can I select from a dataframe only those columns whose names contain a certain text? For example, if the column names are "Bond1.Creditclass","Bond1.Price","Bond2.Creditclass","Bond2.Price", how do I select only the columns corresponding to Bond1? Thanks a lot, Mihai [[alternative HTML version deleted]]