There are three common ways to attack this challenge: defining longer prefix routes favoring the preferred routes, weighting the routes advertised based on the advertised prefix, and using policy routing to override the routing tables. Since you are using OSPF, the first option won't work and the second is tricky to set up correctly, so your only real choice is probably policy routing.
In most cases, you will need to use policy routing anyway for the return traffic, unless the source of the traffic can also be distinguished by IP address. When setting up the policy routing, don't forget to provide for fallback to the alternate link in case of primary link failure.
Hint: remember that you need to detect link failure before you can react to it, this is automatic as long as all routing decisions are based on IP addresses learned via OSPF.
thank you for reply, i manged to configure the routers to auto detect & fallback to the alternate available link but the traffic that originally traversed through the failed link blocked by the access-list.
Would appreciate if somebody could enlighten me by providing some samples.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...