<?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: Experience with GlobalProtect during Corona pandemic time in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318725#M81804</link>
    <description>&lt;P&gt;The majority of QoS rules ignore the application.&lt;/P&gt;&lt;P&gt;They simply match the destination server (which is used for software deployment only) and are put in class 7 (which has a max bandwidth configured).&lt;/P&gt;&lt;P&gt;The "normal" fileserver traffic is listed in the QoS policy, hence put in class 4.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Mar 2020 13:41:32 GMT</pubDate>
    <dc:creator>JoergSchuetter</dc:creator>
    <dc:date>2020-03-26T13:41:32Z</dc:date>
    <item>
      <title>Experience with GlobalProtect during Corona pandemic time</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318468#M81757</link>
      <description>&lt;P&gt;I would like to share issues with GlobalProtect, and what was done to fix it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;QoS with loopback interface&lt;/STRONG&gt;&lt;BR /&gt;Due to high network load on the Internet line, we wanted to priorize (or limit) some traffic. It took several hours (testing, reading documents, having a PA supporter analyzing the issue, ...) until the root cause was identified. Applying QoS on a loopback interface is simply not supported. So we had to migrate the GP gateway from a loopback to a secondary IP (you can have more than one secondary IP) on the physical interface. The secondary IP was added with netmask /32. We had to update our security policy due to the interface of the gateway is now part of a different zone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Limit bandwidth of SMB traffic&lt;/STRONG&gt;&lt;BR /&gt;A good amount of traffic sent to the clients is caused by our software deployment (and patch management). The files/packages are provided on SMB-fileshares. By limiting this traffic (QoS policy based on the servers, regardless of the application) we ran into unexpected side effects with our fileservices (which is served by other servers, not related to the ones limited). There is only one "SMB-process" on the client machine. If a SMB connection to server A (our software deployment server), then this process chokes on SMB connections with server B. Luckily we are able to shift software deployment from SMB to http(s).&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2020 11:50:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318468#M81757</guid>
      <dc:creator>JoergSchuetter</dc:creator>
      <dc:date>2020-03-25T11:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: Experience with GlobalProtect during Corona pandemic time</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318499#M81767</link>
      <description>&lt;P&gt;How are you identifying SMB traffic in your QoS rule? Is it blanket all SMB traffic, or from specific "servers/hosts"?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2020 14:18:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318499#M81767</guid>
      <dc:creator>ZachBiles</dc:creator>
      <dc:date>2020-03-25T14:18:47Z</dc:date>
    </item>
    <item>
      <title>Re: Experience with GlobalProtect during Corona pandemic time</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318725#M81804</link>
      <description>&lt;P&gt;The majority of QoS rules ignore the application.&lt;/P&gt;&lt;P&gt;They simply match the destination server (which is used for software deployment only) and are put in class 7 (which has a max bandwidth configured).&lt;/P&gt;&lt;P&gt;The "normal" fileserver traffic is listed in the QoS policy, hence put in class 4.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2020 13:41:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318725#M81804</guid>
      <dc:creator>JoergSchuetter</dc:creator>
      <dc:date>2020-03-26T13:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: Experience with GlobalProtect during Corona pandemic time</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318746#M81811</link>
      <description>&lt;P&gt;Maybe a dumb question, but are the "more specific" rules for your app deployment servers higher in your QoS ruleset? Those are processed in order and exit on first match.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, are your rules configured bi-directional? I found that I had to list source and destination zones and IP's in both the source and destination field for it to catch the traffic. I'm guessing since it's the clients that initiate the transfer after the server instructs the client to do so.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2020 14:38:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/experience-with-globalprotect-during-corona-pandemic-time/m-p/318746#M81811</guid>
      <dc:creator>ZachBiles</dc:creator>
      <dc:date>2020-03-26T14:38:38Z</dc:date>
    </item>
  </channel>
</rss>

