Greetings community,
I've been a big fan of IP SLA since its inception, I think in 2006, and use it in my own data center operations as well as my clients. I use it for PBR but it's a static fixed config.
The question is: can I have a PBR route-map on an interface that reroutes traffic based _ONLY_ on the IP SLA failing? Not when track is successful, but when track fails?
The reason is that I have a small customer whom has (don't laugh too hard) a cable modem provider that's flakier that corn flakes, and uses three AT&T xDSL 8 meg lines as backup. The need is that, in the event of the primary cable modem provider failing, the outbound traffic needs to be split up between the DSL lines to avoid a degree of overloading of traffic suddenly having to switch from high speed cable to slow speed DSL.
The route-map is below, nothing private to have to worry about:
! Match to send out Corp01
!
route-map reroute-internet-traffic permit 10
match ip address 131
set ip next-hop verify-availability 192.168.255.16 1 track 1
!
! Match to send out Corp02
!
route-map reroute-internet-traffic permit 15
match ip address 132
set ip next-hop verify-availability 192.168.255.17 2 track 1
!
! Match to send out Corp03
!
route-map reroute-internet-traffic permit 20
match ip address 133
set ip next-hop verify-availability 192.168.255.18 3 track 1
!
!-------------------------------------------------------------------------------
!
int gi0/0
ip policy route-map reroute-internet-traffic
exit
!
end
-------------------------
each access list 131 thru 133 states what traffic should route thru which DSL. In a normal PBR operation, this works perfectly fine, but we want this to kick in _ONLY_ if the track fails.
Ideas and comments are appreciated.
-Jeff
