Is it worth implementing IP SLAs to track WAN interfaces in this scenario? I want to load-balance, host-dependent, when all WAN interfaces are up. When all three WAN interfaces go down, I want to switch the ACTIVE GLBP Router to BLUE-MPLS-CE. I plan to use ip sla tracking to track these 3 objects, and write a boolean OR statement. when this boolean OR goes down, i want to decrement RED-SW GLBP priority and make BLUE-SW the ACTIVE GLBP Router.
RED-MPLS-CE
Gi0/1, Gi0/2 are L2 shared broadcast domains
Gi0/3 is a preferred WAN connection
BLUE-MPLS-CE
Gi0/1, Gi0/2 are L2 shared broadcast domains
Gi0/3 is a preferred WAN connection
Any help or input is appreciated.
Thanks!
Incase you have trouble reading the text on the side, here it is:
IP SLA config
ip sla 1
icmp-echo 192.168.3.2 source-ip 10.1.1.6
timeout 2000
frequency 2
ip sla 2
icmp-echo 192.168.1.2 source-ip 10.1.1.6
timeout 2000
frequency 2
ip sla 3
icmp-echo 192.168.2.2 source-ip 10.1.1.6
timeout 2000
frequency 2
track 1 ip sla 1 reachability
track 2 ip sla 2 reachability
track 3 ip sla 3 reachability
track 202 list boolean or
object 1
object 2
object 3
ip sla schedule 1 start-time now life forever
ip sla schedule 2 start-time now life forever
ip sla schedule 3 start-time now life forever
interface Vlan10
ip address 10.1.10.2 255.255.255.0
ip ospf network point-to-point
ip ospf hello-interval 1
ip ospf retransmit-interval 2
glbp 71 ip 10.146.71.1
glbp 10 timers msec 200 msec 750
glbp 10 priority 105
glbp 10 preempt
glbp 10 load-balancing host-dependent
glbp 10 name
glbp71 
glbp 10 weighting track 202 decrement 30
