<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic APIC-EM EasyQOS on VSS in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/apic-em-easyqos-on-vss/m-p/3526531#M2256</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to use APIC-EM 1.4 to configure QoS on our new LanEdge/Core-devices that consist of Cat6840 in VSS. Those VSS'es use a dedicated port as dual-active detection with Fast-Hello. The network is not in production yet so I can play with as much as I like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to deploy an EasyQoS-policy it fails and looking at the "Preview Policy" I can see that APIC-EM is trying to configure the service-policy on the dual-active-detection-interface. When an interface is set as DAD it doesn't accept any other interface-config.&lt;/P&gt;&lt;P&gt;I thought that APIC-EM was smart enough to exclude the interface from EasyQOS since it does exclude the VSL-interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway to manually exclude an interface from an EasyQOS-deployment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Tobias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 12:38:47 GMT</pubDate>
    <dc:creator>tlr</dc:creator>
    <dc:date>2019-03-01T12:38:47Z</dc:date>
    <item>
      <title>APIC-EM EasyQOS on VSS</title>
      <link>https://community.cisco.com/t5/controllers/apic-em-easyqos-on-vss/m-p/3526531#M2256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to use APIC-EM 1.4 to configure QoS on our new LanEdge/Core-devices that consist of Cat6840 in VSS. Those VSS'es use a dedicated port as dual-active detection with Fast-Hello. The network is not in production yet so I can play with as much as I like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to deploy an EasyQoS-policy it fails and looking at the "Preview Policy" I can see that APIC-EM is trying to configure the service-policy on the dual-active-detection-interface. When an interface is set as DAD it doesn't accept any other interface-config.&lt;/P&gt;&lt;P&gt;I thought that APIC-EM was smart enough to exclude the interface from EasyQOS since it does exclude the VSL-interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway to manually exclude an interface from an EasyQOS-deployment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Tobias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:38:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/apic-em-easyqos-on-vss/m-p/3526531#M2256</guid>
      <dc:creator>tlr</dc:creator>
      <dc:date>2019-03-01T12:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: APIC-EM EasyQOS on VSS</title>
      <link>https://community.cisco.com/t5/controllers/apic-em-easyqos-on-vss/m-p/3526532#M2257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;as of today, there is a way to exclude an interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.5 EasyQoS release notes&lt;/P&gt;&lt;H2 class="topictitle2" style="margin-top: 18px; margin-bottom: 10px; font-style: inherit; font-size: 16px; font-family: Arial, Helvetica, sans-serif; color: #444444;"&gt;What’s New in Cisco EasyQoS for APIC-EM, Release 1.5.0.x&lt;/H2&gt;&lt;P style="margin-top: 1px; margin-bottom: 0.5em; font-size: 14px; color: #58585b;"&gt;&lt;/P&gt;&lt;P style="margin-top: 1px; margin-bottom: 0.5em; font-size: 14px; color: #58585b;"&gt;The &lt;SPAN style="font-style: inherit;"&gt;Cisco APIC-EM&lt;/SPAN&gt; software release provides the following new EasyQoS app features and functions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A name="concept_yvz_1r3_cz__li_341056F9E96646B594E8B79C213EED7D" style="font-style: inherit; font-size: inherit; color: #007fab;"&gt;&lt;/A&gt;&lt;SPAN style="margin-top: 1px; margin-bottom: 0.5em; font-style: inherit; font-size: 14px;"&gt;Provides for the traffic class to be modified for NBAR apps.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="margin-top: 1px; margin-bottom: 0.5em; font-style: inherit; font-size: 14px;"&gt;Permits device interfaces to be excluded from QoS policy provisioning.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="margin-top: 1px; margin-bottom: 0.5em; font-style: inherit; font-size: 14px;"&gt;Adds support for new monitoring functionality to assist in troubleshooting EasyQoS app (beta feature).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="margin-top: 1px; margin-bottom: 0.5em; font-style: inherit; font-size: 14px;"&gt;Permits the user to change the DSCP value for each traffic class per scope/policy.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="margin-top: 1px; margin-bottom: 0.5em; font-style: inherit; font-size: 14px;"&gt;Support for the Fastlane QoS feature on wireless LAN controllers (WLCs).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jun 2017 03:09:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/apic-em-easyqos-on-vss/m-p/3526532#M2257</guid>
      <dc:creator>aradford</dc:creator>
      <dc:date>2017-06-28T03:09:27Z</dc:date>
    </item>
  </channel>
</rss>

