Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

when backup route works


I have small query. I have routes like this in one router.

ip route (via Router2)

ip route 10 (via Router3)

Please look into the attached diagram.

My question is link between Router4 and Router6 is broken, then will it take backup route via (i.e, Router3)




Re: when backup route works

With the static routing as long as the link is up between Router 1 & 2, it will send packets that way regardless if the connection between 4 & 6 fails.

New Member

Re: when backup route works

If I enable SAA in between Router1 and Router8 in two directions that is via Router2 and Router3.

Router8 will not respond to Router1 via Router2.It will respond via Router3 only.

Using this technique we can delete route to via in Router1 routing table.

So there will be only one active route via via Router3.

So invoking backup route is possible in this way.

Is it right or wrong? Some one suggested me this.

I didn't check it practically.

Required your suggestions.



Re: when backup route works

SAA is nothing more than a service level / performance monitoring tool. It does not control your routing in any way.

The best option is to enable a dynamic routing protocol (OSPF, EIGRP, RIP, etc) to dynamically re-route traffic if a link were to fail.

Re: when backup route works

SAA is only part of the solution. SAA monitors some target (for example, ping some IP address not necessarily next-hop). The other part of the solution is to read status of that monitor object (this process is called tracking) and install a route if status is OK. In reverse that also means that if after route has been installed the check fails (e.g. SAA didn't receive reply) then the route will be removed. Cisco refers to this method as 'reliable static routing'. The solution is very simple and yet it's powerful. As a monitoring target it's better to specify not just next-hop router, but something more meaningful for determining whether link is usable.

There is one catch using reliable static routes, or routes with tracking - if the route is down, how does SAA reach target? Looks like it's gonna be down all the time unless route is installed. And if route is installed what's the point of tracking? Similar to chicken and egg issue. To resolve this loop, SAA tracking is often implemented together with policy-routing that will ensure that probe packets are always sent via particular interface.

We use 'reliable static routing' all the time when more than one link provisioned to a site, unless specific situation demands dynamically learn routing information. Only then we'll put a dynamic routing protocol. We use ordinary static routes only in situations where there is only one line to a site (what's point to monitor it - if it doesn't work we haven't got anything else anyway, so no complexety).

Here is document on CCO providing more information on how reliable static routing works and sample configurations -

Let me know if you need more help on this.


Re: when backup route works


in the diagram you have provided, if the link between rtr4 & rtr6 goes down, then the only path available to is via

the problem is that rtr1 still knows of via is a better cost then (this is due to your staticRoute via

this happens because rtr1 has no idea that is not reachable via even if the link between 4 & 6 goes down, rtr1 knows to get to it must send the packet to

if you used a routing protocol through 1, 2, 4 & 6 at least with a floatingStaticRoute pointing to, then you could acheive a link outage between 4 & 6 and the routers would adjust their tables via routingProtocol and the floatingStaticRoute (that has the higher cost) would be used.

it may be best to implement a basic eigrp or even rip to get basic link status/routing updates.

(of course, if you use a routing protocol such as eigrp or even rip throughout all routers, there should be no need for a floatingStaticRoute with your design)

see these links for more routing protocol info:

eigrp -

igrp -

rip -

CreatePlease to create content