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,
Ben if you could suggest how I can assist you in reproduction of the
unusual behavior I’d be happy to share anything I can with you or help out
in any way that I can.
On Thu, Mar 8, 2018 at 9:17 PM Ben Pfaff wrote:
> On Thu, Mar 08, 2018 at 08:57:45PM -0500, Chris Boley wrote:
> >
It should work. How are you setting it?
--Justin
> On Mar 8, 2018, at 5:57 PM, Chris Boley wrote:
>
> bond-rebalance-interval=1
>
> If I set this option to any other setting such as 5000 for example it always
> shows 1 on the output of an sudo ovs-vsctl list
bond-rebalance-interval=1
If I set this option to any other setting such as 5000 for example it
always shows 1 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