09-25-2014 01:10 PM - edited 03-07-2019 08:53 PM
09-25-2014 02:24 PM
Hi,
QOS must be enable on all switches as a best practice, depending on the switch model that you have at the core/distribution layer you will need to enable it and trust the interfaces between the switches to maintain the QOS markings.
Yes, it is possible to configure QOS on trunks ports.
Hope this helps.
09-26-2014 08:15 AM
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
The defaults for switches (except for the pretty recent) is, if QoS isn't enabled, switch ignores any markings, it will forward them without change, and there's no different traffic treatment. With QoS enabled, switch will reset CoS/ToS (unless configured otherwise) and will provide some, default, different traffic treatment.
For your first question, whether you need to configure every switch, or even any, depends on your QoS goals.
For your second question, it's an "it depends" answer. Generally, for trunks, you trust whatever QoS marking are received, on ingress, and for egress, you prioritize and/or drop according to your QoS policy.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide