Hi Daniel, I believe the note you are referring to says the following: "The Catalyst 6500 Series with Sup2T, Catalyst 6880 Series, Catalyst 4000 Series, Catalyst 3850 Series, and Catalyst 3650 Series switches will only be supported as an access-layer switch or as a distribution-layer switch. Support of a single switch as both a distribution-layer switch and an access-layer switch simultaneously is not supported. Multiple switch platforms of the same model can of course individually be either distribution l ayer switches or access-layer switches within a single deployment." That note is meant to indicate that a switch cannot be both an access-layer switch and a distribution-layer switch at the same time - not that the Catalyst 6K, 6880, and 4K series can't be used as core switches. I think we need to make that more clear in that note in the next update. The QoS policy provisioned to the switch depends upon it's role in the network. The actual roles supported by each switch platform is discussed beginning at the end of page 143 in the following design guide: https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Aug2017/APIC-EM-EasyQoS-DesignGuide-Aug2017.pdf If Dynamic QoS (which is still in Beta) is not being deployed, the QoS policy provisioned to distribution layer and core layer switches is the same - just trust of DSCP inbound on switch ports and queuing policies. So a collapsed core/distribution design should work fine. If Dynamic QoS is/will be deployed, then the collapsed core/distribution switch should have a role of distribution-layer switch. Dynamic QoS is discussed beginning on page 314 of the design guide. There are some caveats regarding VSS and dual-active-fast-hello configurations discussed, beginning on page 199 of the design guide. Mostly that is due to the ASIC design of the ports on the Sup-2T of the Catalyst 6K. The Sup-6T is currently not supported by EasyQoS. You should be able to begin with a non-VSS configuration of a Catalyst 4K, 6880, or Catalyst 6K with Sup-2T, and then add the second switch in the future. Both configurations are supported by EasyQoS. Just be aware of ports that share a common ASIC with ports that are subsequently used for the VSL connecting the switches may not be able to support QoS configurations when you implement the VSS configuration. You will of course have to re-apply QoS policy when you add the second switch in a VSS configuration. I hope this helps.
... View more
Hi Arik, Is the behavior you are looking for something like the following: interface GigabitEthernet0/0/5 no ip address shutdown negotiation auto plim qos input map ip dscp-based plim qos input map ip dscp 32 40 queue strict-priority ! interface GigabitEthernet0/0/5.100 service-policy output prm-dscp#EQ_SPP1-4Class#shape#50.0 ! interface GigabitEthernet0/0/5.200 service-policy output prm-dscp#EQ_SPP1-4Class#shape#45.0 Here's an example of the top level of the policy-maps. policy-map prm-dscp#EQ_SPP1-4Class#shape#45.0 class class-default shape average 45000000 service-policy prm-dscp#EQ_SPP1-4Class policy-map prm-dscp#EQ_SPP1-4Class#shape#50.0 class class-default shape average 50000000 service-policy prm-dscp#EQ_SPP1-4Class Each sub-interface has a hierarchical policy with a shaper and a child policy (not shown). Let me know if that is the configuration you are trying to support.
... View more