Jeez, first thing in the morning and a having my eyes fresh I found it. I had copied and pasted my scripts back and forth so much and had and missed a "space" in the line of the command that I wrote. False alarm. I fixed that and rebooted. Problem solved!
On Thu, Mar 8, 2018 at 11:44 PM, Justin Pettit <jpet...@ovn.org> wrote: > Can you provide the command and options that you used? I assume it was > ovs-vsctl. > > --Justin > > > On Mar 8, 2018, at 8:11 PM, Chris Boley <ilgtec...@gmail.com> wrote: > > Justin I set the value at 5000 > I tried it via my interfaces file stanza and also by way of the > extra-options: in a live command. > It produced no errors in either method but when I look at the bridge, > there it is.. 10000 every time. > > On Thu, Mar 8, 2018 at 9:06 PM Justin Pettit <jpet...@ovn.org> wrote: > >> It should work. How are you setting it? >> >> --Justin >> >> >> > On Mar 8, 2018, at 5:57 PM, Chris Boley <ilgtec...@gmail.com> wrote: >> > >> > bond-rebalance-interval=10000 >> > >> > If I set this option to any other setting such as 5000 for example it >> always shows 10000 on the output of an sudo ovs-vsctl list port vbond0 >> command. >> > >> > My version is 2.5.2. Is this rebalance interval negotiated between the >> Cisco etherchannel that I am peering with happens to depend on what the >> peer is willing to do or am I missing something? >> > >> > Thank you, >> > CB >> > >> > _______________________________________________ >> > discuss mailing list >> > disc...@openvswitch.org >> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >> >>
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
