From Jon's reference "The sum of all bandwidth allocation on an interface cannot exceed 75 percent of the total available interface bandwidth. The remaining 25 percent is used for other overhead, including Layer 2 overhead, routing traffic, and best-effort traffic. Bandwidth for the CBWFQ class-default class, for instance, is taken from the remaining 25 percent."
What's not clear is how an explicitly defined class-default interacts with the reserved 25%. I've believed the class-default had always shared its bandwidth with both user traffic and overhead traffic. (For instance, your usage of RED might show counts for IP Prec 6/7, if you're doing routing across the interface.) What might be the issue here is your explicitly defined 25% within class-default.
Try class-default without the explicit bandwidth setting. If you can load down the interface with traffic, examine the queues and see if the queue weights correspond to expected ratios (e.g. class-default weight being half of class CBS_TRAFFIC_SERIAL weight).
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...