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

Ben Pfaff blp at ovn.org
Fri Nov 9 23:21:20 UTC 2018

On Mon, Oct 29, 2018 at 05:21:13PM +0530, Numan Siddique wrote:
> On Mon, Oct 29, 2018 at 5:00 PM Daniel Alvarez Sanchez <dalvarez at redhat.com>
> wrote:
> > Hi,
> >
> > After digging further. The problem seems to be reduced to reusing an
> > old gateway IP address for a dnat_and_snat entry.
> > When a gateway port is bound to a chassis, its entry will show up in
> > the MAC_Binding table (at least when that Logical Switch is connected
> > to more than one Logical Router). After deleting the Logical Router
> > and all its ports, this entry will remain there. If a new Logical
> > Router is created and a Floating IP (dnat_and_snat) is assigned to a
> > VM with the old gw IP address, it will become unreachable.
> >
> > A workaround now from networking-ovn (OpenStack integration) is to
> > delete MAC_Binding entries for that IP address upon a FIP creation. I
> > think that this however should be done from OVN, what do you folks
> > think?
> >
> >
> Agree. Since the MAC_Binding table row is created by ovn-controller, it
> should
> be handled properly within OVN.

I see that this has been sitting here for a while.  The solution seems
reasonable to me.  Are either of you working on it?

More information about the discuss mailing list