You can fine tune EIGRP using offset-lists and adjusting the delay on various interfaces. If you make your adjustments such that your backup path becomes a feasible successor, you can achieve sub-second convergence when you primary path fails. If EIGRP has to query for a route, you are dead in the water.
Doing this gives you the benefits of a dynamic routing protocol, while keeping things very deterministic in the case of failure (you know exactly which secondary path is going to pick up the traffic) and making failover as fast as possible.
Figuring out what to use for your offset and delay values takes a little bit of calculating (depending how complex your topology is), but nothing too hard (you just have to make sure your primary path wins by at least 1).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...