1. For both CAR and CB-Policing is it true that...
If Bc = Be, excess burst is disabled. Be must be greater than Bc for excess bursting capability.
2. If so, I'm missing why we can't use the Be if it's the same as Bc.
If Bc = 4K, and Be = 4K, in time interval 1 (t1) if I send 4K conforming, the Be should allow me to burst another 4K as excess. But I can send no excess if I'm reading it right. If that's just the way it is I can live with it.
3. If Bc = 4K, and Be = 6K, in time interval 1 (t1) if I send 4K conforming, does the Be allow me to burst another 6K (10K total in t1) or another 2K (6K in total) as excess?
4. In CAR the max-burst (Be) is configured, but no violate action is possible. Is there a second (excess) bucket used for regulating max-burst?
The recommendations you have stated seem to be for the older implementation of CB-Policing, where it was modeled on CAR. The current implementation is based on the following RFCs: RFC2697 & RFC2698
In answer to your questions:
1. For CAR, Be is inclusive of Bc. Therefore, if Bc = Be, there is no excess burst capability. For CB-Policing, Be does not include Bc, therefore, there is no excess burst capability when Be = 0. If Be > 0, then you have excess burst.
2. My respose to 1 answers this question, I hope.
3. See response to 1. For Car, you will get 2k of excess burst. For CB-Policing, you will get 6k of excess burst.
4. Wtih CAR, you only get a single bucket policer, so it's either conforming or exceeding. With CB-Policing, you have the option of a two-bucket policer, which allows you the additional violate-action.
Good luck getting a design recommendation from TAC !
My thinking of the disparity between CAR and CB-Policing recommendations is that CAR, being an older technology, was used in the days when it was likely that shapers were not very granular. Therefore, you had to have a course measurement interval. These days, shapers are more accurate so you can use a smaller measurement interval.
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...