I am trying to include trunk ports into an etherchannel with a QoS input and output policy. Every attempt to put it into the channel-group fails because the physical interface has a service-policy attached to it.
I've tried to put the input/output service policies on the Port Channel virtual interface, but it only allows me to put the input policy on, not an output policy.
If I have any service-policy defined on the physical interfaces, it will not join the channel-group.
The interfaces are Layer 2 trunk ports to a 6509 and the Etherchannel is Layer 2 only.
With QoS enabled on the switch, will all the QoS markings be trusted by default over these trunks and therefore don't need to have the policies defined?
Im no QoS guru, but I can tell you that you should identify your traffic, mark it, and then apply a policy to it as close to the origin as possible.
Then, at each successive hop (layer 2 or L3), you will want to use the "mls qos trust cos" command (switched ports) or the "mls qos trust dscp | ip precedence" command (routed ports) to extend the trust boundary. By default, a port does not trust the CoS/QoS markings of the packet it receives.
As far as why you cant apply a policy in the outbound direction or why you cant apply it t the port channel, I will have to investigate.
Qute frankly I have always wondered why certain switch platforms do not allow you to apply a QoS policy in the outbound direction....seems strange.
Hope I was of some help.
[EDIT] To the QoS expert who will answer the call for help, if I am incorrect about anything, please let me know. Thanks. [EDIT]
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...