What kind of nics are you using? Try using miimon instead of carrier for failure detection. See the ovs-vswitchd.conf.db man page.
Darragh. From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Neelakantam Gaddam Sent: 10 February 2017 07:58 To: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] Bonding slave disabled One more observation is that if any of the interface link status is down, then the add-bond operation is showing the down interface as disabled and up interface as enabled with proper mac address. On Fri, Feb 10, 2017 at 1:25 PM, Neelakantam Gaddam <neelugad...@gmail.com<mailto:neelugad...@gmail.com>> wrote: Hi all, I am observing strange issue while configuring bonding in ovs 2.6.1. Configuration: ovs-vsctl add-br br0 ifconfig eth0 up ifconfig eth1 up ovs-vsctl add-bond br0 bond0 eth0 eth1 bond_mode=active-backup ovs-appctl bond/show bond0 ---- bond0 ---- 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: 00:00:00:00:00:00(none) slave eth0: disabled may_enable: false slave eth1: disabled may_enable: false Even though, interfaces eth0 and eth1 having the link status showing UP, the bond show command always showing the eth0/eth1 as disabled. What are the possible reasons for slave interface displaying as disabled? When I debug further, I observed that may_enable is 0 always. What are the possibilities of this variable becoming zero? -- Thanks & Regards Neelakantam Gaddam -- Thanks & Regards Neelakantam Gaddam
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
