(big hole in wall where I've been slamming my head into it)
I have two providers between site A and site B, each an MPLS network. We have a switch between each router, one at each site. EIGRP load balances most traffic for us. We prefer provider 1 for time sensitive traffic (voice and video) because they give us QOS in the cloud. This 'preference' is executed with a route map against the vlans on the switch.
Works fine if the provider (wan) link on a router goes away, doesn't work so well if the lan link goes down. The route-map doesn't know that the lan interface is down, and for a while anyway the routes are still in the table so the route map just keeps on prefering the router that is not home.
So, I tried to use set next-hop verify availability and, what I find is, with that command in the route map, I can not configure the vlan with the ip policy route-map blah and have it stay set. Take out the verify availability...works fine, policy applies to the interface just fine!
Thank you for any insight.
I have two providers between site A and site B, each an MPLS network. We have a switch between each router, one at each site. EIGRP load balances most traffic for us. We prefer provider 1 for time sensitive traffic (voice and video) because they give us QOS in the cloud. This 'preference' is executed with a route map against the vlans on the switch.
Works fine if the provider (wan) link on a router goes away, doesn't work so well if the lan link goes down. The route-map doesn't know that the lan interface is down, and for a while anyway the routes are still in the table so the route map just keeps on prefering the router that is not home.
So, I tried to use set next-hop verify availability and, what I find is, with that command in the route map, I can not configure the vlan with the ip policy route-map blah and have it stay set. Take out the verify availability...works fine, policy applies to the interface just fine!
Thank you for any insight.