Hi Paul,
This is the most simple and straight forward example, no need to use PBR or 
anything else.
I use this for routing traffic through management tunnels based on reachability 
of the next hop.

ip sla monitor 1
 type echo protocol ipIcmpEcho 1.1.1.1
  timeout 3000

 track 1 rtr 1 reachability

 ip route 2.2.2.2 255.255.255.0 1.1.1.1 track 1

Hope this helps
Ziv




-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Riemer
Sent: Thursday, September 18, 2008 5:40 AM
To: Paul Stewart; [email protected]
Subject: Re: [c-nsp] Static Route based on next hop reachable

Hi Paul,

Take a look at Policy based routing with object tracking.

http://www.cisco.com/en/US/tech/tk364/technologies_configuration_example
09186a0080211f5c.shtml

Cheers,

Aaron
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Stewart
Sent: Thursday, 18 September 2008 10:25 AM
To: [email protected]
Subject: [c-nsp] Static Route based on next hop reachable

Hi there..



This is a bit of a long story .. But what we are looking for is to
create a
static route only if the next hop is reachable and directly connected.
is
this possible?



I seem to remember there is a way to do this via IP SLA statements where
if
a condition is met then do X



Can anyone enlighten me on this?  We have some clients connecting via
PPPOE
to a 7206VXR but now want to move towards load balancing where the
client
could connect to multiple devices in a round robin format.  The more
obvious
answer would be to create the routes via Radius but this has proven
difficult due to a proprietary system in use to create the radius users
file.



Thanks,



Paul







_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

LEGAL DISCLAIMER: This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************






 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************



_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to