# Bandwidth vs Bandwidth Remaining **URL:** https://forum.networklessons.com/t/bandwidth-vs-bandwidth-remaining/26597 **Category:** Lessons Discussion **Created:** [May 4, 2022, 7:07pm UTC](https://forum.networklessons.com/t/bandwidth-vs-bandwidth-remaining/26597 "2022-05-04T19:07:45Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![lagapidis](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/lagapidis/32/4949_2.png) [@lagapidis](https://forum.networklessons.com/u/lagapidis) #### Post date: [May 30, 2022, 4:50am UTC](https://forum.networklessons.com/t/bandwidth-vs-bandwidth-remaining/26597/3 "2022-05-30T04:50:45Z")
Hello Sandeep Remember, that these values are referring to **bandwidth guarantees** that exist **during congestion**. In other words, this is **reserved bandwidth for that particular type of traffic**. Now if there is no AF11, AF21, and AF31 traffic at a particular time, then all other configured traffic types (EF and class-default) will share the full bandwidth of the interface as needed. But such traffic will be served in a best-effort manner, no guaranteed bandwidth is provided beyond what has been configured. So if you were to examine the results of such a situation in the lab, you would see that any additional bandwidth available would show up under the class-default. But be aware that this is not guaranteed bandwidth that you are seeing, but best effort. I hope this has been helpful! Laz Remember, when configuring these values (whether percentage or percentage remaining) they define the minimum guaranteed bandwidth --- _[View the full topic](https://forum.networklessons.com/t/bandwidth-vs-bandwidth-remaining/26597)._