Re: [ovs-discuss] OVN: MAC_Binding entries not getting updated leads to unreachable destinations

On Tue, Nov 20, 2018 at 5:21 AM Mark Michelson wrote: > > Hi Daniel, > > I agree with Numan that this seems like a good approach to take. > > On 11/16/2018 12:41 PM, Daniel Alvarez Sanchez wrote: > > > > On Sat, Nov 10, 2018 at 12:21 AM Ben Pfaff > > wrote: > > > > > > On

[ovs-discuss] A coredump cause by the race condition by handler、upcall and revalidation thread

We've found a coredump in a daily testcase(ovs2.7.0+dpdk), After a deep analyze we found it coredumped after a ovs service restart(with birdges and ports), and the revalidator and upcall threads race at the ukey_state. However ,it seems hard to reproduce the coredump.We conclude a possiblity

[ovs-discuss] Reg. ofport set to -1

Hi, Currently in OVS we set "-1" for ofport field in interface table of OVS DB when we fail to initialize the interface. This means if we had allocated any ofport number earlier, it is released. When the above failed interface gets initialized successfully later it gets a "new" ofport number

[ovs-discuss] Issue when using bond command in OVS

Hi everyone, I'm having several troubles with *bonding* functionalities. I'm beginning in this world and I made a topology like this one on my virtual machine: ++ |ns1 |