<?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 Palo Alto QOS - WRED drops in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-qos-wred-drops/m-p/384996#M90108</link>
    <description>&lt;P&gt;In Palo Alto firewall, &amp;nbsp;we observed WRED drops on QOS (150Mbps) &amp;nbsp;applied egress interface eth 1/11 – due to which DB sync/mirroring is randomly getting failed/dropped between DC &amp;amp; DR. Please let me know for any configuration changes/workarounds to avoid this WRED drops.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 10 Feb 2021 09:41:08 GMT</pubDate>
    <dc:creator>preetpk</dc:creator>
    <dc:date>2021-02-10T09:41:08Z</dc:date>
    <item>
      <title>Palo Alto QOS - WRED drops</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-qos-wred-drops/m-p/384996#M90108</link>
      <description>&lt;P&gt;In Palo Alto firewall, &amp;nbsp;we observed WRED drops on QOS (150Mbps) &amp;nbsp;applied egress interface eth 1/11 – due to which DB sync/mirroring is randomly getting failed/dropped between DC &amp;amp; DR. Please let me know for any configuration changes/workarounds to avoid this WRED drops.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 09:41:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-qos-wred-drops/m-p/384996#M90108</guid>
      <dc:creator>preetpk</dc:creator>
      <dc:date>2021-02-10T09:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto QOS - WRED drops</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-qos-wred-drops/m-p/385253#M90123</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71795"&gt;@preetpk&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Why are you classifying SQL traffic as low priority traffic? In the vast majority of environments you would be giving SQL a higher priority over other traffic, not setting it as low priority traffic. With how you have things configured, your QoS is performing exactly what you are telling it to. Traffic starts queuing, WRED kicks in and will start dropping packets from lower priority queues to preserve high priority traffic.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to look at how you've actually configured QoS and what your organizations actual goal is with this traffic. From the look of things and how you have it configured at the moment, it appears like you want to treat SQL traffic as low priority. If that's the case and it meets your business use-case that's all fine and well, but you will run into DB replication issues.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 22:47:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-qos-wred-drops/m-p/385253#M90123</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-02-10T22:47:29Z</dc:date>
    </item>
  </channel>
</rss>

