There is a simple solution assuming that the serial links are strict point to point interfaces (such as HDLC or PPP). It may be more complex if they are something like Frame Relay.
I would suggest configuring a primary static route specifying the next hop of serial-1, configure a floating static specifying the next hop of serial-2, and another floating static (with even higher distance) specifying the next hop of the BRI. It might look something like this:
And if you configure as I suggest you will get the result that BRI only dials if both serial links are down.
In normal operation the static route with no weight is used. If serial-1 goes down then that static route is removed from the route table and the static route with weight 240 is used (traffic is on serial-2). If serial-1 is down and then serial-2 goes down then that static route with weight 240 is removed from the route table and the static route with weight 250 is used.
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...