<?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: Regarding the selection of the MU-SPN connection destination in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1232867#M1175</link>
    <description>&lt;P&gt;Outside of that you can see&amp;nbsp;Best Gateway Selection Criteria&amp;nbsp;as nowadays the gateway location is selected by response time but you can also include the gateway load as a criteria. After the location is selected the user session will persist on the SPN-MU even when there are multiple of them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/gateway-priority-in-a-multiple-gateway-configuration/best-gateway-selection-criteria" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/gateway-priority-in-a-multiple-gateway-configuration/best-gateway-selection-criteria&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Only gateways for mobile users scale in a horizontal way while SC and RN scale only vertically without making extra instances.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/pancast-episodes/pancast-episode-41-scaling-on-prisma-access/ta-p/584437" target="_blank"&gt;https://live.paloaltonetworks.com/t5/pancast-episodes/pancast-episode-41-scaling-on-prisma-access/ta-p/584437&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jun 2025 08:01:33 GMT</pubDate>
    <dc:creator>nikoolayy1</dc:creator>
    <dc:date>2025-06-30T08:01:33Z</dc:date>
    <item>
      <title>Regarding the selection of the MU-SPN connection destination</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1232826#M1174</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Attention: JAPAC TPM team&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello Team,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When IP Optimization is disabled and there are multiple MU-SPNs in a single compute location,&lt;BR /&gt;how is the MU-SPN to be connected to selected?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand that it connects to the one that is physically close and has the fastest response,&lt;BR /&gt;but is load balancing performed?&lt;/P&gt;
&lt;P&gt;If load balancing is performed, what method is used?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the information is not public, I would appreciate it if you could let me know.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 02:18:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1232826#M1174</guid>
      <dc:creator>y.saitou</dc:creator>
      <dc:date>2025-06-30T02:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding the selection of the MU-SPN connection destination</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1232867#M1175</link>
      <description>&lt;P&gt;Outside of that you can see&amp;nbsp;Best Gateway Selection Criteria&amp;nbsp;as nowadays the gateway location is selected by response time but you can also include the gateway load as a criteria. After the location is selected the user session will persist on the SPN-MU even when there are multiple of them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/gateway-priority-in-a-multiple-gateway-configuration/best-gateway-selection-criteria" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-gateways/gateway-priority-in-a-multiple-gateway-configuration/best-gateway-selection-criteria&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Only gateways for mobile users scale in a horizontal way while SC and RN scale only vertically without making extra instances.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/pancast-episodes/pancast-episode-41-scaling-on-prisma-access/ta-p/584437" target="_blank"&gt;https://live.paloaltonetworks.com/t5/pancast-episodes/pancast-episode-41-scaling-on-prisma-access/ta-p/584437&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 08:01:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1232867#M1175</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2025-06-30T08:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding the selection of the MU-SPN connection destination</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1233014#M1176</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/153031"&gt;@nikoolayy1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for your reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem has been solved.&lt;BR /&gt;Thank you for your help.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 08:17:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/regarding-the-selection-of-the-mu-spn-connection-destination/m-p/1233014#M1176</guid>
      <dc:creator>y.saitou</dc:creator>
      <dc:date>2025-07-02T08:17:44Z</dc:date>
    </item>
  </channel>
</rss>

