Hi Amit,

Thanks for the quick response. What I mean is that we do not have administrative access to their router in our WAN. We give them an IP address on our WAN segment and then they NAT that to their internal network. The router sits in our data center. The CSU/DSU has a T1 back to their data center and the Eth interface connects to our WAN switch. We then have static routes on our WAN router to point traffic for their IP addresses to the WAN address that we give them (and they NAT). I'll see if I can draw something up real quick.

Thanks!

Jake

I am not clear from your description whether you are routing the same prefix for the customer via the "preferred" link and via the "backup" link. I assume that this is the case and if so there are a couple of solutions that might work. I would suggest first considering floating static routes. You would keep the existing static routes and you would configure the new backup static routes with an administrative distance higher than the default (of 1) so that if the primary static route is available it is used and if it is withdrawn from the routing table then the floating static route gets inserted into the routing table and could be redistributed. I would suggest that you make the administrative distance greater then the AD of EIGRP redistributed routes.

A second alternative would be closer to what your question is asking and would manipulate the metric of the backup static route. One version of the alternative would be to have the primary static route and the backup static route on the same router. You would then control redistribution of static routes with a route map. The route map would have one instance which would match the primary static routes and would set the default metric to some value of delay and would have a second instance which would match the backup static routes and would set the delay metric to some higher value. This would result in the primary static routes having a better metric and the backup static routes having a worse metric. The other version of this option is to configure primary static routes on one router and to configure the backup static routes on another router. On the router doing backup static routes you set a default metric for the static route redistribution that is worse than the default metric of the primary static routes.

HTH

Rick

"On the router doing backup static routes you set a default metric for the static route redistribution that is worse than the default metric of the primary static routes. "

Hi Rick,

This is what I was looking for and as I stated before, I do modify the metrics for WAN sites where I have access to both routers. I set a delay on the Serial Interfaces pointed to the backup site so that it has a worse metric than my primary site. However, since I could only set the delay on the interface of the router I control, would it still make it a backup route?

Jake

It might be sufficient to just set the delay on the interface higher. My thought had been to explicitly configure default metric under router eigrp (or to explicitly code the metrics on the redistribute statement so that you had manual control.

HTH

Rick

It was my understanding that to modify metrics using the delay commmand, you had to set delay on both ends of the WAN link. Is that not the case? Just setting it on my end should work?

that's what I needed. Thanks Rick

Jake

I am glad that my answers were helpful to you. Thanks for using the rating system to indicate that your issue was resolved (and thanks for the rating). It makes the forum more useful when people can read about an issue and can know that they will read something that resolved the issue. I encourage you to continue your participation in the forum.

HTH

Rick