This should happen automatically, since in the absence of policy routing, the standard routing tables will be consulted. Make sure you have two routes to the remote subnet and it'll work.
However, please allow me to suggest an alternative to what you're doing. I believe your goal is to have a GOLD and a STANDARD path for providing better service to certain protocols or applications. Creating multiple FR paths may not actually work as well as you think, especially if your/your customer want to add more classes in the future. Chances are you may have routing protocols enabled. If you want the failover you mentioned to work, that means running the routing protocol on all paths. That's wasted bandwidth.
Second, what happens when the FR path gets congested and has to start discarding? You have no guarantee that it'll discard data over routing protocol information, and that could lead to flapping.
Also, I've tested this type of setup in a lab environment to prove a point. The FR infrastructure vendor used a common input buffer at the remote end. That means that all your PVCs come into one buffer, so your ftp could still have negative impact over your higher grade traffic.
Have a look at Cisco's CBWFQ (Class Based Weighted Fair Queueing). With this you can match traffic to access lists (which can match source IP/port), IP precedence and other sources of info. You can then guarantee minimum bandwidths for each class of traffic, on a per-interface basis.
This is cleaner, faster and much more versatile than using multiple FR paths.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.