01-11-2022 12:33 PM
What is the difference between 'real-time' and 'high' priority than? Will there be any difference under similar circumstances when you have 100 Mbit/s MAX egress and 50 Mbit/s guarantee, while actual traffic matching this class exceeding 100 Mbit/s? Previously I was under impression that real-time one will just drop traffic exceeding queue limit and anything else will just reclassify everything above to default class 4 as bandwith is available there.
But after checking https://live.paloaltonetworks.com/t5/general-topics/qos-is-quot-real-time-quot-priority-a-strict-pri... and doing my test it seems like no reclassification is happening in both cases - doesn't matter which priority you use (except maybe low) - once all bandwith is used for a traffic within this class, it will just drop assigned kind of traffic.
Maybe @michaelmertens can share results of his QoS implementation?
What is a correct assumption?
01-13-2022 04:18 AM
the real-time classes have a dedicated hardware queue that bypasses the regular queue when resources are depleted (and packets need to fight for resources), all the other priorities are 1 shared resource pool with higher priority packets getting accepted and forwarded first and low priority packets getting discarded first/forwarded last.
Priorities only come into play when resources are depleted/interface congested, not when limits are being enforced
01-14-2022 12:04 PM - edited 01-14-2022 12:10 PM
That's what I am alluding to really. If link is congested - what happens to a traffic in a class with a real-time priority, where volume of traffic egressing interface for this class higher than egress value mentioned in a profile for this class? Can PaloAlto reclassify it to best-effort class 4 or will just drop it?
Also another question - what happens if we have more than 1 real-time class in a profile?
PS: Actually Steve Cantwell in this thread says something different about whether queues are been enforced same time as qos profile applied: https://live.paloaltonetworks.com/t5/general-topics/qos-is-quot-real-time-quot-priority-a-strict-pri...
Q: Does QoS queuing ONLY get engage when the interface is congested?
A: the answer is NO
01-17-2022 12:48 AM
Real-time queueing has priority over all other priorities, lower priorities will always be dropped before real-time
you can put more classes into real-time priority, but putting too much of your mean traffic in this priority will simply create a FiFo queue, defeating the purpose of real-time over lower priorities
The queue would indeed also be used if you run into a limitation for the class, but it would be a bit odd to have a limit _and_ real-time queueing in the same class i think?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!