[ovs-discuss] Bonding slave disabled

Neelakantam Gaddam neelugaddam at gmail.com
Wed Feb 15 05:37:57 UTC 2017


Hi Nick,

When I do "ifconfig br0 up", interestingly the bond slave ports are getting
enabled including may_enable.

This means that, port_run is not running before bond_run. port_run function
runs when there is a change in the dpif port. The port link changes are
received through netlink sockets. If these messages are missing, no one is
there to update may_enable the ports.

This is the exact behaviour, I am observing right now.
Any help to debug it further is greatly appreciated.






On Mon, Feb 13, 2017 at 10:31 PM, Neelakantam Gaddam <neelugaddam at gmail.com>
wrote:

> Hi,
>
> Thanks for the help.
>
> Bonding tap or internal devices are not my use case.
>
> I saw the interface status was UP and RUNNING (for both eth0 and eth1) in
> my setup and still did not get the enabled state in bond show.
> This is the exact issue I am observing.
>
>
>
>
>
>
> On Mon, 13 Feb 2017 at 4:45 PM, nickcooper-zhangtonghao <nic at opencloud.tech>
> wrote:
>
>>
>>
>> On Feb 12, 2017, at 1:05 PM, nickcooper-zhangtonghao <nic at opencloud.tech>
>> wrote:
>>
>> If you use the virtual ethernet driver, you should set the type of net
>> device. If not, the “system” will be used.
>>
>> For example, tap device
>>
>> ovs-vsctl add-br br0
>> ifconfig tap1 up
>> ifconfig tap2 up
>> ovs-vsctl add-bond br0 bond0 tap1 tap2 bond_mode=active-backup
>> ovs-vsctl set interface tap1 type=tap
>> ovs-vsctl set interface tap2 type=tap
>> ovs-appctl bond/show bond0
>>
>> Thanks.
>> Nick
>>
>> On Feb 11, 2017, at 2:02 PM, Neelakantam Gaddam <neelugaddam at gmail.com>
>> wrote:
>>
>> Hi,
>> When one interface is down, the interface showing may_enable to false.
>> But the up interface becoming active slave and is enabled.
>>
>> I am using virtual ethernet driver which doesn't have mii tool support.
>> The carrier link is up always , but still may_enable set to false. Is there
>> any other criteria for may_enable becoming false.
>>
>> Thanks
>> Neelakantam
>>
>>
>>
>>
>> Hi,
>> The example I given, should be described as below:
>>
>> ovs-vsctl add-br br0
>> ovs-vsctl add-bond br0 bond0 tap1 tap2 bond_mode=active-backup
>> ovs-vsctl set interface tap1 type=tap
>> ovs-vsctl set interface tap2 type=tap
>> ovs-appctl bond/show bond0
>>
>> More information about tap on OvS:
>> https://github.com/openvswitch/ovs/blob/c431227e33503421d3412bd3341575
>> 0b6010730d/Documentation/faq/issues.rst
>>
>> Section: “I created a tap device tap0, configured an IP address on it,
>> and added it to a bridge”.
>>
>>
>> It is not you case, sorry. I don’t really understand your case yesterday.
>> But I may try to explain it for you again. If you want to bond the net
>> devices. You should make sure that at least one bonded interface is
>> IFF_RUNNING. For example:
>>
>> ip link add name  vm1-lpeer2 type veth peer name  vm1-rpeer2
>> ip link add name  vm2-lpeer2 type veth peer name  vm2-rpeer2
>>
>> ifconfig vm1-lpeer up
>> ifconfig vm2-lpeer up
>> ovs-vsctl add-bond br0 bond2 vm1-lpeer vm2-lpeer bond_mode=active-backup
>>
>>
>> You should set the vm1-rpeer2 and vm2-rpeer2 UP using ifconfig command(if
>> you don’t do that, vm1-lpeer andvm2-lpeer are IFF_UP not IFF_RUNNING).
>>
>> ovs-appctl bond/show bond2
>> ---- bond2 ----
>> bond_mode: active-backup
>> bond may use recirculation: no, Recirc-ID : -1
>> bond-hash-basis: 0
>> updelay: 0 ms
>> downdelay: 0 ms
>> lacp_status: off
>> active slave mac: c6:42:c6:6d:9a:93(vm1-lpeer)
>>
>> slave vm1-lpeer: enabled
>> active slave
>> may_enable: true
>>
>> slave vm2-lpeer: enabled
>> may_enable: true
>>
>>
>>
>> I don’t know about the difference between 2.4 and 2.6 because I submitted
>> patches from 2.5. I hope the tips above can help you.
>>
>>
>>
>>
>> --
> Thanks & Regards
> Neelakantam Gaddam
>



-- 
Thanks & Regards
Neelakantam Gaddam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170215/fc24948a/attachment.html>


More information about the discuss mailing list