Just a question, being that I'm tucked away in a corner these days and not on the keyboards much at all, is there any routing protocol involved we're not seeing on your config? Additionally, you're just after having one of the ISP's as a backup, correct?
You could "possibly" use "IP SLA Tracking" as a means of establishing your primary and backup routes:
»
www.firewall.cx/cisco-te ··· sic.htmlI've configured this in a test environment on occasions and it's still cool watching it work
Just Yahoo or Google "IP SLA Tracking" or "IP SLA Monitoring" and you'll find more information should this be an approach you want to take.
The second thing to consider is "policy-based routing." I noticed you have set an ip address as your "next hop" in your route-map statement, but I don't see a policy configured on an interface that would tell the router to send traffic in "that" particular direction (unless I overlooked something):
»
www.cisco.com/en/US/docs ··· icy.htmlPerhaps a different approach may be in order?
Regardless, see if any of the above information may be of use to you...
Jay