We should get something like this on 3850 (off course by changing numbers inside):
queue-limit cos 2 percent 50 queue-limit cos 3 percent 50 queue-limit cos 6 percent 70 queue-limit cos 7 percent 70
but I am completely lost on how I can translate threshold I had previously to something similar into the new syntax. Cisco documentation is not very clear to me on how to adapt queues and buffers policy to 3850.
Is the logic different, with calculation or else to do ?
tough one, this has come up quite a bit in the past. There is not really a 1 to 1 conversion as far as I recall. It is mostly class-based, and you need to decide which traffic you want to prioritize, and assign that traffic to classes...
The 3850's QoS architecture is both similar and in some ways "improved/better" than the 3750's.
As, at least in my approach, platform QoS implementations are often just a "subset" of what my logical QoS model/policy is. For any new or different platform, rather than just trying to "replicate" one platform's QoS implementation to another (different) platform, I try to get the new/different platform to best implement my logical QoS model/policy.
Might this be possible for you too?
One reason I ask, you seem to be asking (mostly) about replication of WTD, which, can be a bit more advanced part of a QoS model/policy. If you don't really have your own logical QoS model/policy dealing with WTD, and/or early dropping, you might be better off just using the 3850's defaults or set WTD to all be max.
I have used enabling Auto QoS on a single port on a new platform to get some of the basic stuff created. If the values from Auto QoS meet your needs, great! If not, you can use the platform specific entries created by Auto QoS as a template.
GoalDocumentationDefineAdd Device to Smart AccountSync Smart Account via vManage1.1 VNF package for vBranchDesignDeployOperate
To successfully provision a ENCS device in remote site with internet connection.
Minimum software relea...
はじめに確認方法Version による Application name の変更について備考参考情報 はじめに本ドキュメントでは Cisco SD-WAN における Policy 上で設定可能な Application を確認する方法について記載しています。 確認方法サポートされている Application name についてはご使用されている vManage へ API を呼び出して確認することが可能です。https://<IP or FQDN>/...
DMVPN (Dynamic Multipoint VPN) Introduced by Cisco in late 2000 is a routing technology you can use to build a VPN network with multiple sites (spokes) without having to statically configure all devices. It’s a “hub and spoke” network, where the spok...
On 24th August 2021, Cisco announced the latest IOS XE release - Cisco IOS XE Bengaluru 17.6.1a
IOS XE 17.6.1a unlocks various routing features and enhancements comprehensively covering different technology segments such as voice, security,...
DMVPN (Dynamic Multipoint VPN) Introduced by Cisco in late 2000 is a routing technology you can use to build a VPN network with multiple sites (spokes) without having to statically configure all devices. It’s a “hub and spoke” network, where th...