04-16-2011 02:18 PM - edited 03-04-2019 12:05 PM
Hi,
I'm working on a pretty simple configuration; the main idea is to use IP SLA to fire a secondary default route in case the primary one fails. The problem is that some sessions get stuck. Lets say device one on the hq is pinging a device behind this branch 2800. The connection suddenly drops and no transfer between those two devices are possible for like 20-30minutes. But the rest of the system works fine. If we remove the IP SLA parts of the configuration, the system works just fine. But we need the ip sla to provide a backup route. (any other possible ways for that?)
First I though of a nat table problem ( saw a similar situation where a 880 couldn't cleat the nat table resulting in not buing able to use the backup connection for the sessions that are currently active)but there's no nat configuration on any device. Is there any other tables that might get in the way of communication in case the main connection drops?
The connection between the branch and the hq is a point-to-point dsl connection, and route bridge mode needs to be used for that(as far as I know). I'm adding the associated part of the configuration. Thanks to anyone who can offer some support in advance.
version 12.4
!
!
ip cef
!
!
no ipv6 cef
!
multilink bundle-name authenticated
04-16-2011 04:21 PM
Have you thought about using OSPF with the gateway router using "default- information originate" to hand out a default route. Then use a floating static route like you currently have but with a higher metric of 250. If the connection goes down the OSPF adjacency goes away along with the default route. Then floating static route will take over.
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide