<?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 Internal Gateway Selection in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/internal-gateway-selection/m-p/554286#M4296</link>
    <description>&lt;P&gt;I'm wondering where I can find official documentation about process of Internal Gateway Selection. There is only a broad documentation how does the external process looks like. Right now I'm testing a setup to have a redundant Internal Gateways to avoid single point of failure, and what I can see in my observation is that GP is connecting to every Internal Gateway on the list.&lt;/P&gt;
&lt;P&gt;Further more depending on a dice roll I think, user-id to ip mapping is created on some of them. I saw already few situation:&lt;/P&gt;
&lt;P&gt;- mapping created only on one gateway further away in terms of latency, redistributed to others&lt;/P&gt;
&lt;P&gt;- mapping created on two gateways, one with low latency, one with high, redistributed to others&lt;/P&gt;
&lt;P&gt;- mapping created on all four gateways&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm just wondering how it was designed by Palo Alto, and if that's an expected result.&lt;/P&gt;</description>
    <pubDate>Fri, 18 Aug 2023 10:40:19 GMT</pubDate>
    <dc:creator>Wojciech_Rogala</dc:creator>
    <dc:date>2023-08-18T10:40:19Z</dc:date>
    <item>
      <title>Internal Gateway Selection</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/internal-gateway-selection/m-p/554286#M4296</link>
      <description>&lt;P&gt;I'm wondering where I can find official documentation about process of Internal Gateway Selection. There is only a broad documentation how does the external process looks like. Right now I'm testing a setup to have a redundant Internal Gateways to avoid single point of failure, and what I can see in my observation is that GP is connecting to every Internal Gateway on the list.&lt;/P&gt;
&lt;P&gt;Further more depending on a dice roll I think, user-id to ip mapping is created on some of them. I saw already few situation:&lt;/P&gt;
&lt;P&gt;- mapping created only on one gateway further away in terms of latency, redistributed to others&lt;/P&gt;
&lt;P&gt;- mapping created on two gateways, one with low latency, one with high, redistributed to others&lt;/P&gt;
&lt;P&gt;- mapping created on all four gateways&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm just wondering how it was designed by Palo Alto, and if that's an expected result.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Aug 2023 10:40:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/internal-gateway-selection/m-p/554286#M4296</guid>
      <dc:creator>Wojciech_Rogala</dc:creator>
      <dc:date>2023-08-18T10:40:19Z</dc:date>
    </item>
  </channel>
</rss>

