<?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>article Nominated Discussion: Understanding QoS in General Articles</title>
    <link>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-understanding-qos/ta-p/561124</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;SPAN&gt;tags: next-generation firewall, network security, routing, QoS, advanced administration&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This Nominated Discussion Article is based on the post "&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/confused-about-qos-on-palo-need-some-assistance/m-p/559217" target="_blank" rel="noopener"&gt; Confused about QoS on Palo, need some assistance&lt;/A&gt;&lt;SPAN&gt;" by&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/317939"&gt;@latechguy&lt;/a&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;and&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;answered by Cyber Elite&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/77347"&gt;@TomYoung&lt;/a&gt;&amp;nbsp;&amp;nbsp;Read on to see his response!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;My understanding is that QoS only really applies to egress.&lt;/P&gt;
&lt;P&gt;The issue I faced this week was with Apple updates killing the ingress and impacting sip trunks.&lt;/P&gt;
&lt;P&gt;Egress didn't appear to be an issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now with that said, would applying QoS within our Palos help in any way when it comes to the sip trunks if the issue is with ingress being saturated?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What could you possibly do in this case?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes!&amp;nbsp; This can be done.&amp;nbsp; See the 2nd paragraph in this article.&amp;nbsp; &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClS0CAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClS0CAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;" &lt;EM&gt;An important concept to keep in mind is that a QoS profile is applied on the&amp;nbsp;egress&amp;nbsp;interface of a packet that is traveling through the firewall. This would mean, for example, that to limit upload, a QoS profile needs to be enabled on the untrust interface and to limit download, a QoS profile needs to be enabled on the trust interface.&lt;/EM&gt; "&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can limit your untrust ingress by applying policy to your trust egress, especially with TCP-based traffic, which will decrease the sliding window based upon packet loss.&amp;nbsp; The article also has good stuff for your SIP trunks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 11 Oct 2023 15:35:18 GMT</pubDate>
    <dc:creator>JayGolf</dc:creator>
    <dc:date>2023-10-11T15:35:18Z</dc:date>
    <item>
      <title>Nominated Discussion: Understanding QoS</title>
      <link>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-understanding-qos/ta-p/561124</link>
      <description>&lt;P&gt;This Nominated Discussion Article is based on the post " Confused about QoS on Palo, need some assistance".&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2023 15:35:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-articles/nominated-discussion-understanding-qos/ta-p/561124</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2023-10-11T15:35:18Z</dc:date>
    </item>
  </channel>
</rss>

