Link to home
Start Free TrialLog in
Avatar of SmudoCH
SmudoCH

asked on

Question regarding PBR and object tracking

Hi all,

To one remote office we're having two redundant paths from our headquarters. I configured PBR together with object tracking to route business critical traffic over PATH1 (leased line) and all other traffic over PATH2 (Internet VPN). This work quite good, also with failover when one of the connections break down, the traffic is automatically being sent over the other path.

There's just one problem: I happens some times that a single ping times out and causes the Cisco router to think that the tracked object is down, but it's not.

Is there a way I can configure rtr (ip sla) to try multiple pings before actually seeing a link down? Let's say only when 3 pings time out the tracking should switch to the other line.

Here's the current rtr config:

...
track 100 rtr 1 reachability
...
rtr 1
 type echo protocol ipIcmpEcho 10.20.x.x source-ipaddr 10.1.x.x
 frequency 15
rtr schedule 1 life forever start-time now

Thanks
Smudo
ASKER CERTIFIED SOLUTION
Avatar of billwharton
billwharton

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SmudoCH
SmudoCH

ASKER

Okay, I didn't tell the whole truth. The VPN tunnel is a bit unstable, so the problem is not only that one ping fails but maybe 10 or 15 pings. This causes a downtime of the tunnel for 10 seconds each half an hour or so. With this situation it wouldn't help to ping more than 1 address on the other side. Any suggestion?
Try the delay parameter and see if that helps
Avatar of SmudoCH

ASKER

Thanks. I'll try that delay parameter and will let you know when it worked. It may takes some time to get the result.
Avatar of SmudoCH

ASKER

Looks like this works. Thanks for your help!

track 30 rtr 30 reachability
!
track 31 rtr 31 reachability
!
track 130 list boolean or
 object 30
 object 31
 delay down 35
!
rtr 30
 type echo protocol ipIcmpEcho 10.20.1.1 source-ipaddr 10.1.1.1
 frequency 15
rtr schedule 30 life forever start-time now
rtr 31
 type echo protocol ipIcmpEcho 10.20.1.2 source-ipaddr 10.1.1.1
 frequency 15
rtr schedule 31 life forever start-time now

Logs:
Mar 11 19:17:57.627: Track: 30 Change #26 rtr 30, reachability Up->Down
Mar 11 19:17:57.627: Track: 31 Change #44 rtr 31, reachability Up->Down
Mar 11 19:17:58.555: Track: 130 Down change delayed for 35 secs
Mar 11 19:18:07.627: Track: 30 Change #27 rtr 30, reachability Down->Up
Mar 11 19:18:07.627: Track: 31 Change #45 rtr 31, reachability Down->Up
Mar 11 19:18:08.555: Track: 130 Down change delay cancelled