Thought I would come back to this.
So it can only apply QOS to the egress interface.
so if you have a PA with eth1 -> internet and eth2 -> proxy server.
you apply QOS for internet download traffic to eth2
you can't apply QOS on eth1 for inbound.
Not exactly what I wanted but atleast now I know
The problem is QOS doesn't just work on sub interfaces it works on the whole interface.
I have a 80G LACP ae and QOS only works up to 40G from memory, so to turn on QOS I have seperarte out interface. I prefer a single trunk with sub int on it.
it would be nice if it slowed ACK's back to the web site for web site downloads.. like squid does
I thought they removed the artificial limits to QoS with 7.1.11? Meaning, that QoS would support whatever the physical interfaces could support.
7.1.10 and earlier were limited to 1 Gbps when QoS was enabled, regardless of what the physical / aggregate interfaces could handle.
Granted, we don't have access to any ports greater than 10 Gbps, and have no switches with 10 Gbps to test with, so ...
I would like to add that when employing Active-Active your throughput per chassis should be calculated to be less than half of the chassis maximum throughput, as the cluster is intended to be a fail-over redundancy and not a capacity increasing measure (if both systems are at 60% capacity and one fails, the remaining chassis will be at 120% and potentially also cause serious impact)
so for a cluster of PA-5280 you would ideally not exceed 34Gbps per chassis
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!