[c-nsp] IP SLA, Object Tracking, Dial Backup

[Michael Markstaller]

> -----Original Message-----
> From: Luan Nguyen [mailto:luan.nguyen at mci.com] 
> Sent: Friday, May 20, 2005 5:03 AM
> To: Michael Markstaller; 'Sascha E. Pollok'; cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] IP SLA, Object Tracking, Dial Backup
> 
> I'll buy the "have another ip sla monitor" for bringing the 
> dialer interface
> sooner.  

Now, as always it depends but this might be the "cleanest" way, my problem is mostly keeping the dialbackup down, therefore I use the 120secs delay to prevent kicking dialbackup for short outages as many cheaper ADSL do a disconnect every 24h..

> We do managed VPN 
so do we ;)

> so bringing up the dialer interface instantly
> never a problem since like said before...eigrp hellos, gre 
> keepalives, ike
> keepalives...etc will do the job fine.  Dialer watch works 
> great too since
> we advertise a route through eigrp through gre tunnel to the 

as I don't have gre in most cases for complexity/security/paranoia/bug-reasons it wasn't that easy sometimes before to have a reliable dial-backup..
the ip sla monitor *with* configurable source if and track on routes is really a great thing as it gives me the first time a reliable and common dialbackup-setup, regardless of what line-type, eigrp, bgp, Dialers, routes, dynamic IP's etc.. 

> cpe.  I have a
> static ip as well as a cisco router at home, so if you are 
> really desperate
> I could do ebgp with you and send you a route so you could watch :)
might depend on who you ask and where, it took me sometimes quite a while to get some route announced from your employer ;) 
as we do all this stuff also with foreign lines and varying technologies occasionally, there were many cases in the past where I simply don't had a route to watch for..

I guess one of the biggest challenges with Cisco & VPN is to choose which technologie to use under which circumstances..

Michael