<?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 RE: QoS marking on CPU sourced packets in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35266#M7068</link>
    <description>That's excellent news, thank you very much.&lt;BR /&gt;
&lt;BR /&gt;
I'll stop worrying about this now.&lt;BR /&gt;
&lt;BR /&gt;
Paul.&lt;BR /&gt;</description>
    <pubDate>Tue, 05 Jan 2016 17:13:00 GMT</pubDate>
    <dc:creator>Paul_Thornton</dc:creator>
    <dc:date>2016-01-05T17:13:00Z</dc:date>
    <item>
      <title>QoS marking on CPU sourced packets</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35263#M7065</link>
      <description>Here's a scenario where I can't quite work out if what I'm trying to do is even possible, let alone how to do it...&lt;BR /&gt;
&lt;BR /&gt;
Imagine you have two switches (in this exact instance, I have an X460 at both ends) that are used to terminate a fibre link between two locations on a network. This link carries most of its traffic at layer 3 - so it is basically a /30 point-to-point subnet.  There are a couple of L2 VLANs, but ignore those for the purposes of this question.&lt;BR /&gt;
&lt;BR /&gt;
Now throw in a routing protocol (I'm using BGP, but OSPF or IS-IS would have the same problem) to announce routes in both directions.&lt;BR /&gt;
&lt;BR /&gt;
If there is a large flood of traffic - imagine a bit of a DoS against a server at the far end of the link - I want to ensure that the routing protocol packets are prioritized, so the routing doesn't fall over and everything stops.&lt;BR /&gt;
&lt;BR /&gt;
Now here's the tricky part - the BGP/OSPF/IS-IS/RIP(!) packets are originated from the CPU, so I can't just whack an ingress ACL on a port to match them and set a higher qosprofile for those packets.  Is there any way to set the qos profile (or alternatively, set the DSCP bits and then use diffserv replacement) in this instance?&lt;BR /&gt;
&lt;BR /&gt;
Or am in in a situation where the only way to do this is to stick a router at each end, so there is an ingress port to put the ACL on?&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
&lt;BR /&gt;
Paul.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Dec 2015 18:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35263#M7065</guid>
      <dc:creator>Paul_Thornton</dc:creator>
      <dc:date>2015-12-29T18:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: QoS marking on CPU sourced packets</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35264#M7066</link>
      <description>Obviously we're all very quite over Christmas and the New Year &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
Anyone have any ideas?&lt;BR /&gt;
&lt;BR /&gt;
Paul.&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Jan 2016 18:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35264#M7066</guid>
      <dc:creator>Paul_Thornton</dc:creator>
      <dc:date>2016-01-04T18:31:00Z</dc:date>
    </item>
    <item>
      <title>RE: QoS marking on CPU sourced packets</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35265#M7067</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    Sorry for the late response.&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    By default CPU originated  protocol packets are mapped to  qp8 at egress hardware port with dscp value marked as 48 .So control packets  never get drop due to congestion at egress port provided scheduling algorithm  used is strict priority for qp8 on that egress port.&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    Regards,&lt;BR /&gt;
&lt;BR /&gt;
    Prabhakar MV&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Jan 2016 13:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35265#M7067</guid>
      <dc:creator>Prabhakar_Rao_M</dc:creator>
      <dc:date>2016-01-05T13:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: QoS marking on CPU sourced packets</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35266#M7068</link>
      <description>That's excellent news, thank you very much.&lt;BR /&gt;
&lt;BR /&gt;
I'll stop worrying about this now.&lt;BR /&gt;
&lt;BR /&gt;
Paul.&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Jan 2016 17:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/qos-marking-on-cpu-sourced-packets/m-p/35266#M7068</guid>
      <dc:creator>Paul_Thornton</dc:creator>
      <dc:date>2016-01-05T17:13:00Z</dc:date>
    </item>
  </channel>
</rss>

