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
Ah, first version supporting HQF.
Ok, for egress prioritization, you could use something like:
policy Sample
class real-time
priority percent 33
class HiPriority
bandwidth remaining 81 percent
fair-queue
class LoPriority
bandwidth remaining 1 percent
fair-queue
class class-default
bandwidth remaining 9 percent
fair-queue
Then all you need to do is map your different traffic into a class with the priority it needs. Most traffic will work fairly well falling into the default class. So, you only need to worry about traffic that needs to be treated better or worse. Something like VoIP bearer traffic should be directed to the real-time class. Something like VoIP signalling traffic might be directed to the HiPriority class. Something like bittorrent could be directed to the LoPriority class. NBAR can be used for match, for example:
class-map match-any LoPriority
match protocol bittorrent
