[c-nsp] Tracking state of non-directly connected link

[Vitkovský Adam]

For simple link availability check you don't need the SLA responder at the other end.
Just have the ping running and define how many failed pings result in positive action.

adam
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> redscorpion69
> Sent: Tuesday, April 29, 2014 11:33 PM
> To: Velimir Filipov
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Tracking state of non-directly connected link
> 
> Hello,
> 
> Yeah I forgot to mention ip sla, I had it in my head. But what if CE is a small
> non-cisco router that doesn't have ip sla/static bfd?
> 
> Regards
> 
> 
> On Tue, Apr 29, 2014 at 3:59 PM, Velimir Filipov
> <vfilipov at evolink.com>wrote:
> 
> >
> > Hello.
> >
> > You could use ip sla and object tracking to achieve that.
> >
> >
> > http://www.cisco.com/c/en/us/td/docs/ios/dial/configuration/guide/12_2
> > sr/dia_12_2sr_book/dia_rel_stc_rtg_bckup.html
> >
> >
> > > Hello,
> >
> >
> > > What would be the best method of actively/passively keeping track of
> > > validity of static route over GPON interfaces for example?
> >
> > > We want to give an option of backup floating static route over
> > > backup interface, but need to be aware of primary link failure.
> >
> > > I could think of something like static bfd, which isn't available on
> > > all platforms, or maybe GRE tunnel will keepalives?
> >
> > > Regards
> >
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/