I have a situation where an entire MLPPP bundle goes down because of a single T1 taking errors. My thought is that when the errors are severe enough, the result is lost mlppp 'control' packets that cause the whole bundle to crash. Obviously, when this occurs, the normal course is to shut the offending T-1, troubleshoot with the LEC and bring it back up only when it's fixed. However, I'm not always available and I would prefer if there was a way for the router to sense that a T-1 is taking too many CRC, input errors, (via a threshold?) and automatically put the interface into a down/down state. Then, the rest of the bundle would survive until I had time to fix.
Has anyone tried this before? Is there any ability to do it?
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...