<?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 DiffServ incorrectly handles Express Forwarded traffic, with B2 f/w 4.00.26 in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/diffserv-incorrectly-handles-express-forwarded-traffic-with-b2-f/m-p/46652#M409</link>
    <description>Article ID: 5859 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack B2&lt;BR /&gt;
Firmware 4.00.26 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Protocols/Features&lt;/B&gt;&lt;BR /&gt;
DiffServ &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Express Forwarded traffic is not transmitted from high priority hardware queue &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
If DiffServ is used to mark the DSCP value of a frame based on a keyword of "ef" or a value of 46 (with either of these yielding L3 Express Forwarding), as a side-function the outgoing L2 frame should be placed into the highest priority hardware queue (Queue 5) for transmission (&lt;A href="http://bit.ly/18F0WPL" target="_blank" rel="nofollow noreferrer noopener"&gt;5848&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
This side-functionality is broken, with the above-stated product and firmware. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 4.00.60 or higher.</description>
    <pubDate>Wed, 27 Nov 2013 03:31:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-27T03:31:00Z</dc:date>
    <item>
      <title>DiffServ incorrectly handles Express Forwarded traffic, with B2 f/w 4.00.26</title>
      <link>https://community.extremenetworks.com/t5/faqs/diffserv-incorrectly-handles-express-forwarded-traffic-with-b2-f/m-p/46652#M409</link>
      <description>Article ID: 5859 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack B2&lt;BR /&gt;
Firmware 4.00.26 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Protocols/Features&lt;/B&gt;&lt;BR /&gt;
DiffServ &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Express Forwarded traffic is not transmitted from high priority hardware queue &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
If DiffServ is used to mark the DSCP value of a frame based on a keyword of "ef" or a value of 46 (with either of these yielding L3 Express Forwarding), as a side-function the outgoing L2 frame should be placed into the highest priority hardware queue (Queue 5) for transmission (&lt;A href="http://bit.ly/18F0WPL" target="_blank" rel="nofollow noreferrer noopener"&gt;5848&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
This side-functionality is broken, with the above-stated product and firmware. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 4.00.60 or higher.</description>
      <pubDate>Wed, 27 Nov 2013 03:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/diffserv-incorrectly-handles-express-forwarded-traffic-with-b2-f/m-p/46652#M409</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-27T03:31:00Z</dc:date>
    </item>
  </channel>
</rss>

