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
marwanshawi wrote:
How the policy knows the interface congested ? This through tow waysReferencing the interface bandwidth ( u can change it using bandwidth command )
Just wanted to clarify, the bandwidth statement, correctly set, can be used to determine interface/policy load but a QoS service policy will not queue packets (unless using percent based shapers) based on the bandwidth statement. (NB: the bandwidth statement can also influence class weights which can be important if your mixing absolute and relative bandwidth statements in CBWFQ class statements.)
If for example, you set the bandwidth statement to 10x actual physical interface bandwidth, 100% actual interface usage will only show as 10% usage but a CBWFQ service policy will queue and treat packets as the policy defines.
Conversely, if bandwidth statement is set to 1/10 of actual interface bandwidth, 50% actual interface usage may show as 500% usage but a CBWFQ policy will not resequence packets (again w/o a shaper).
