RE: IP SLA preempt after a switchover

Use track to trigger an eem script which removes the route or sets the track
object to down. When the sla comes back, fire off another eem script that
starts a kron job to fire off a third eem script that restores the route or
enables the track object.

David

--
http://dcp.dcptech.com
> -----Original Message-----
> From: PhiL [mailto:theccie_at_gmail.com]
> Sent: Wednesday, December 22, 2010 3:15 PM
> To: David Prall
> Cc: groupstudy
> Subject: Re: IP SLA preempt after a switchover
> 
> Thanks David,
> 
> I found that but I need it to be delayed for at least 6 hours.
> --
> Regards,
> 
> PhiL
> 
> 
> 
> On Wed, Dec 22, 2010 at 2:41 PM, David Prall <dcp_at_dcptech.com> wrote:
> 
> 
> 	With newer code you can for up to 180 seconds.
> 
> 	Track 200 ip sla 1
> 	 Delay up 180
> 
> 	David
> 
> 	--
> 	http://dcp.dcptech.com
> 
> 
> 
> 	> -----Original Message-----
> 	> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On
> Behalf Of
> 	> PhiL
> 	> Sent: Wednesday, December 22, 2010 2:35 PM
> 	> To: groupstudy
> 	> Subject: IP SLA preempt after a switchover
> 	>
> 	> Hi there,
> 	>
> 	> I am trying to configure IP SLA to monitor an upstream IP and
> remove
> 	> the
> 	> default route from the routing table so a floating static is
> inserted.
> 	> Everything is working fine but I wonder if there is a way of
> delaying
> 	> for
> 	> several hours the re-insertion of the original default route
> once
> 	> tracking
> 	> is reestablished. Right now as soon as the ping to the
> <upstream IP
> 	> within
> 	> ISP1> is replied the route is reinserted.
> 	>
> 	> This is my scenario:
> 	>
> 	> ISP1 ------ R1 --------|
> 	>                             switch ------ userPC
> 	> ISP2 ------ R2 --------|
> 	>
> 	>
> 	> R1 config:
> 	> router eigrp 10
> 	>  redistribute static
> 	>  passive-interface FastEthernet0/1.1
> 	>  network 192.168.1.0
> 	>  network 192.168.2.0 0.0.0.3
> 	>  no auto-summary
> 	> !
> 	> ip route 0.0.0.0 0.0.0.0 <ISP1 next-hop IP> track 200
> 	> !
> 	> ip sla monitor 1
> 	>  type echo protocol ipIcmpEcho <upsteam IP within ISP1>
> 	>  request-data-size 64
> 	>  threshold 10000
> 	> ip sla monitor schedule 1 life forever start-time now ageout
> 1800
> 	> ip sla monitor 2
> 	>  type echo protocol ipIcmpEcho 10.1.1.1
> 	> !
> 	> track 200 rtr 1 reachability
> 	> !
> 	>
> 	>
> 	> R2 is also running EIGRP and has a default route with a worse
> metric
> 	> than
> 	> R1's default route.
> 	>
> 	> --
> 	> Regards,
> 	>
> 	> PhiL
> 	>
> 	>
> 
> 	> Blogs and organic groups at http://www.ccie.net
> 	>
> 	>
> _______________________________________________________________________
> 	> Subscription information may be found at:
> 	> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net