<?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 QoS tag VLAN or Port in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/qos-tag-vlan-or-port/m-p/8699#M280</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I have a VSP4450 with a connected IPTV server. We have problem with TVs lagging and I would like to add a QoS tag either on the ingress traffic on the port or on the VLAN (52) to see if it resolves the issue?&lt;BR /&gt;&lt;BR /&gt;Is it this easy or am I missing something?&lt;BR /&gt;&lt;BR /&gt;VLAN config:&lt;BR /&gt;interface vlan 52&lt;BR /&gt;qos ingressmap 1p 6&lt;BR /&gt;qos ingressmap ds 46&lt;BR /&gt;qos egressmap 1p 6&lt;BR /&gt;qos egressmap ds 46&lt;BR /&gt;&lt;BR /&gt;Port config:&lt;BR /&gt;interface gig 1/13&lt;BR /&gt;qos level port 1/13 6&lt;BR /&gt;(No DSCP tag that I can find)&lt;/P&gt;</description>
    <pubDate>Wed, 03 Nov 2021 18:10:00 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2021-11-03T18:10:00Z</dc:date>
    <item>
      <title>QoS tag VLAN or Port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/qos-tag-vlan-or-port/m-p/8699#M280</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I have a VSP4450 with a connected IPTV server. We have problem with TVs lagging and I would like to add a QoS tag either on the ingress traffic on the port or on the VLAN (52) to see if it resolves the issue?&lt;BR /&gt;&lt;BR /&gt;Is it this easy or am I missing something?&lt;BR /&gt;&lt;BR /&gt;VLAN config:&lt;BR /&gt;interface vlan 52&lt;BR /&gt;qos ingressmap 1p 6&lt;BR /&gt;qos ingressmap ds 46&lt;BR /&gt;qos egressmap 1p 6&lt;BR /&gt;qos egressmap ds 46&lt;BR /&gt;&lt;BR /&gt;Port config:&lt;BR /&gt;interface gig 1/13&lt;BR /&gt;qos level port 1/13 6&lt;BR /&gt;(No DSCP tag that I can find)&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 18:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/qos-tag-vlan-or-port/m-p/8699#M280</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2021-11-03T18:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: QoS tag VLAN or Port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/qos-tag-vlan-or-port/m-p/8700#M281</link>
      <description>&lt;P&gt;All ports have default qos set to 1. All ports on VSP by default set to L2+L3 trusted i.e Diff-Serve enable and Diff-serv type as Core. For this default config, port level qos&amp;nbsp; would have no impact. VSP would use ingress DSCP mapping&amp;nbsp; for both tagged or untagged packets. If packets ingressing with DSCP value as 0, packets would get QoS level of 1. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;In order for packets to be assigned qos level based on port, a port should be configured as L2Untrusted+L3Untrusted (no enable-diffserv enable / access-diffserv enable). DSCP would be remarked based on QoS to DSCP egress map.&lt;/P&gt;
&lt;P&gt;A better approach would be to use ACL to remark DSCP for traffic sourced from IPTV server given there are indeed packet losses occurring in the network for qos Queue 1. Else, remarking DSCP would have no impact.&lt;/P&gt;
&lt;P&gt;I would suggest to open a case with support to let someone look into complete path from IPTV server to Clients and confirm if there any indeed any packet losses for the IPTV stream and on which node in the network and why and then go for a solution from there.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 23:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/qos-tag-vlan-or-port/m-p/8700#M281</guid>
      <dc:creator>Ron_Huygens</dc:creator>
      <dc:date>2021-11-04T23:00:00Z</dc:date>
    </item>
  </channel>
</rss>

