Re: [c-nsp] vs isis delay propagation of loopback interfec

2020-12-15 Thread Aaron
+1 overload bit.

On Tue, Dec 15, 2020 at 1:58 PM Saku Ytti  wrote:

> Hey,
>
> > Can someone help me out here? I'm trying to find a way to delay the
> > propagation of a loopback interface in isis.
> >
> > The problem is the border node in sd-access, which uses the loopback
> > interface for Lisp, and as soon the fabric sees the interface it sends
> > traffic to the address.
> >
> > But at this time bgp might not be ready out of the fabric.
>
> I assume this means you have multiple options in iBGP and you are
> redirecting it too early. Perhaps:
>
> set-overload-bit on-startup wait-for-bgp
>
> Or perhaps have another loopback for services which is iBGP only carried.
>
> --
>   ++ytti
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] vs isis delay propagation of loopback interfec

2020-12-15 Thread Saku Ytti
Hey,

> Can someone help me out here? I'm trying to find a way to delay the
> propagation of a loopback interface in isis.
>
> The problem is the border node in sd-access, which uses the loopback
> interface for Lisp, and as soon the fabric sees the interface it sends
> traffic to the address.
>
> But at this time bgp might not be ready out of the fabric.

I assume this means you have multiple options in iBGP and you are
redirecting it too early. Perhaps:

set-overload-bit on-startup wait-for-bgp

Or perhaps have another loopback for services which is iBGP only carried.

-- 
  ++ytti
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] vs isis delay propagation of loopback interfec

2020-12-15 Thread Arne Larsen

Hi all.

Can someone help me out here? I'm trying to find a way to delay the 
propagation of a loopback interface in isis.


The problem is the border node in sd-access, which uses the loopback 
interface for Lisp, and as soon the fabric sees the interface it sends 
traffic to the address.


But at this time bgp might not be ready out of the fabric.

Right now we are using a eem script to open and close the interface 
based on a static delay.


Hope someone has way to get around this.

/Arne

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/