[ovirt-users] Issue with a LACP bond interface.

[CRiMSON]

What is the *proper* way. Cause I've come across quite a few different ways
reading on this how to get it done. Some say do it by hand, others say
never do it by hand use the vdsClient, others say do it this way. I mean
between forum posts, blogs, it seems there are multiple ways to do this.
With no concrete "This is how you should do it"



On 2 November 2017 at 04:19, Yaniv Kaul <ykaul at redhat.com> wrote:

>
>
> On Thu, Nov 2, 2017 at 3:06 AM, CRiMSON <crimson at unspeakable.org> wrote:
>
>> The config details:
>>
>> root at lv426 network-scripts]# cat ifcfg-bond0
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=bond0
>>
>> BONDING_OPTS='mode=4 lacp_rate=1 miimon=100 xmit_hash_policy=2'
>>
>> BRIDGE=ovirtmgmt
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> DEFROUTE=no
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> [root at lv426 network-scripts]# cat ifcfg-eno1
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=eno1
>>
>> MASTER=bond0
>>
>> SLAVE=yes
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> DEFROUTE=no
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> [root at lv426 network-scripts]# cat ifcfg-enp11s0
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=enp11s0
>>
>> MASTER=bond0
>>
>> SLAVE=yes
>>
>> ONBOOT=yes
>>
>> DEFROUTE=no
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> [root at lv426 network-scripts]# cat ifcfg-enp2s0f0
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=enp2s0f0
>>
>> MASTER=bond0
>>
>> SLAVE=yes
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> DEFROUTE=no
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> [root at lv426 network-scripts]# cat ifcfg-enp2s0f1
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=enp2s0f1
>>
>> MASTER=bond0
>>
>> SLAVE=yes
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> DEFROUTE=no
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> [root at lv426 network-scripts]# cat ifcfg-ovirtmgmt
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=ovirtmgmt
>>
>> TYPE=Bridge
>>
>> DELAY=0
>>
>> STP=off
>>
>> ONBOOT=yes
>>
>> BOOTPROTO=dhcp
>>
>> MTU=1500
>>
>> DEFROUTE=yes
>>
>> NM_CONTROLLED=no
>>
>> IPV6INIT=no
>>
>> DNS1=10.100.100.1
>>
>> DNS2=10.1.2.2
>>
>> [root at lv426 network-scripts]# cat /proc/net/bonding/bond0 |grep Slave
>>
>> *Slave* Interface: eno1
>>
>> *Slave* queue ID: 0
>>
>> *Slave* Interface: enp2s0f0
>>
>> *Slave* queue ID: 0
>>
>> *Slave* Interface: enp2s0f1
>>
>> *Slave* queue ID: 0
>>
>> *Slave* Interface: enp11s0
>>
>> *Slave* queue ID: 0
>>
>> As you can see by the above all 4 interfaces are configured and up
>> properly and working.
>>
>> I've configured them using the command:
>>
>>  vdsClient -s 0 setupNetworks bondings='{bond0:{nics:eno1+en
>> p11s0+enp2s0f0+enp2s0f1,options:mode=4 lacp_rate=1 miimon=100
>> xmit_hash_policy=2}}'
>>
>>
> Why are you using vdsClient to configure the network?
> Y.
>
>
>> It's all good.
>>
>> But when I reboot interface3 enp11s0 is not part of the bond,
>>
>> [root at lv426 ~]# cat /proc/net/bonding/bond0 |grep Slave
>>
>> *Slave* Interface: eno1
>>
>> *Slave* queue ID: 0
>>
>> *Slave* Interface: enp2s0f0
>>
>> *Slave* queue ID: 0
>>
>> *Slave* Interface: enp2s0f1
>>
>> *Slave* queue ID: 0
>>
>> And looks like it's had it's bonding config removed b y VDSM.
>>
>> [root at lv426 network-scripts]# cat ifcfg-enp11s0
>>
>> # Generated by VDSM version 4.19.31-1.el7.centos
>>
>> DEVICE=enp11s0
>>
>> ONBOOT=yes
>>
>> MTU=1500
>>
>> NM_CONTROLLED=no
>>
>> If I re-=run the vdsClient command and if down/ifup the interface it
>> happily rejoins the bond and carries on working perfectly.
>>
>> For the life of me I can't figure out what I'm missing / done wrong.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20171102/c02ea398/attachment.html>