On Tue, Sep 8, 2020 at 11:27 AM Han Zhou wrote:
>
>
>
> On Tue, Sep 8, 2020 at 5:29 AM Numan Siddique wrote:
> >
> > On Thu, Sep 3, 2020 at 7:44 AM Han Zhou wrote:
> > >
> > > The checking of lsp "up" status before adding ARP responder flows was
> > > added to avoid confusion in cases when a net
On Tue, Sep 8, 2020 at 5:29 AM Numan Siddique wrote:
>
> On Thu, Sep 3, 2020 at 7:44 AM Han Zhou wrote:
> >
> > The checking of lsp "up" status before adding ARP responder flows was
> > added to avoid confusion in cases when a network admin sees ARP response
> > for VM/containers that is not up o
On Thu, Sep 3, 2020 at 7:44 AM Han Zhou wrote:
>
> The checking of lsp "up" status before adding ARP responder flows was
> added to avoid confusion in cases when a network admin sees ARP response
> for VM/containers that is not up on chassis yet. However, this check
> introduces an extra round of
The checking of lsp "up" status before adding ARP responder flows was
added to avoid confusion in cases when a network admin sees ARP response
for VM/containers that is not up on chassis yet. However, this check
introduces an extra round of flow change in SB and triggers computes
on hypervisors whi
