Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
On many devices, peak just appears to double the effective transfer rate of average.
Your thinking about Be being set to zero, for peak making it the same at average, is logically correct, but I would say you need to try in on the device under question.
If you review peak shaping, Cisco, I recall, has some documentation Be only refills with unused Bc, but on many devices, Be seems to refill on every Tc.
Traditionally, QoS features don't usually get "wrung out" as often in the field, so in my experience, they are more likely not to work exactly as documented. (BTW, if you find a clear case of this, and bring it to Cisco's attention, the "fix" might be a revision to the documentation - laugh.)
