Costing route statments

[don_donohue]

What is the way to associate a cost with route statments? Or define a prefered route and a secondary (back up route statment)?

3 Cisco 2600's fully meshed frame relay. NO DYNAMIC

routing protocols being used, no RIP, OSPF etc. All

routing being done via static routes. Intent here is

to build in redundancy in case one of the links in the frame relay cloud goes away. So there will be a need to have at least 2 route statments to the same

destination subnet (different gateway's) in each 2600. One route statment being the prefered path and

the second statment to be used if the first (preferd) path "goes away". Is the distance metric the way to cost these or is there another entry on the ip route statment that will get us there?

[MickPhelps]

The metric is easy:

ip route 192.168.1.0 255.255.255.0 serial0.1

ip route 192.168.1.0 255.255.255.0 serial0.2 100

Serial0.1 will be the prefered route. Serial0.2 will take over if the serial0.1 sub-interface goes down.

Note that you really need to use sub-interfaces when you using floating statics and frame relay since PVCs can go down, but the main serial interface may remain up. If a PVC fails on a sub-interface, the sub-interface goes down.

Mick.

[don_donohue]

Mick,

Many thanks for your response, I was not sure how without any dynamic routing protocols the router was

going to determine that the dlci (pvc) went away. Sub-interfaces are the key. Again many thanks.

DAD