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

[Michael Markstaller]

Dontknow if got this right but we're pulling up all links, backups and IPSec SA's with appropriate "ntp server x.x.x.x source Fax/y" commands. 
I cannot guarantee this pulls it up instantly as I also have IPSec & syslogging which micht cause it, but one of these ntp/syslog will help. the real problem begins when you want the dialer to *not* go up at any time..
another idea: have another ip sla monitor with source-address/interface..
On the other hand, dialer-watch should pull the backup-dialer up as soon as the route disappears but it requires to have a route to watch and makes things more complicated..

Besides the "ip sla monitor" config disappering on reboot I wrote earlier,
the following works like a charm here (12.3(14)T or 12.4):

omit the "delay down 120" should make dialbackup to come up faster
Di11 is the primary link (PPPoE)
Di25 is the Dialbackup
1.2.3.4 is one "near" IP which disappears when the link goes down (like PtP)
--- cut ---
ip sla monitor 10
 type echo protocol ipIcmpEcho 1.2.3.4 source-interface Dialer11
 frequency 30
ip sla monitor schedule 10 life forever start-time now
track 10 rtr 10 reachability
 delay down 120
!
ip route 0.0.0.0 0.0.0.0 Dialer11 track 10
ip route 0.0.0.0 0.0.0.0 Dialer25 200
--- cut ---

Michael

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of 
> Sascha E. Pollok
> Sent: Thursday, May 19, 2005 3:44 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] IP SLA, Object Tracking, Dial Backup
> 
> Good day,
> 
> I am currently looking at IP SLA w/ object tracking and it's 
> benefits for
> detecting e.g. non directly-connected links failures. Surfing the web,
> I find several examples (especially on Cisco's website) using floating
> default routes for bringing up BRI backup-interfaces and 
> stuff like this.
> For me, these solutions only bring up the backup-link when there is
> actually traffic flowing from the local network to the outside world
> (0.0.0.0).
> 
> What I would like to do is e.g. to bring up a 
> Dialer-Interface as soon as
> a tracked object fails. I thought I might be able to do this 
> by using a
> dialer watch-list and watching some route that disappears when the
> tracked object fails but I am not too sure about this. It would be
> best if I could cause the default-route to disappear (ok this works
> already), to float in a 2nd default route (no problem) and to bring
> up the Dialer-interface instantly (problem!). I could use 
> dialer-persist
> on the Dialer-interface but since it's "up/up spoofing) all the time
> it would come up even without a failure of the main-link or tracked
> object. I am looking for a command like "dialer persist track xxx".
> 
> Does anyone have a nice hint here?
> 
> Thanks!
> Sascha
> _______________________________________________
> 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/
>