GP Client - Available Gateway selection process

[conor_obrien]

Numerous reports of users connecting to GPCS Gateways in different regions E.g. EMEA connecting to Japan, NA to APAC etc. Client recently upgraded to v6.2.5. Uptick in these cases reported.

User from hibernation signs into GPCS @ 09:52, user based in UK - Gets Japan Gateway 

Logs below show GPCS Client in background working through & ruling out gateways from "Available gateway" list in seemingly 10 minute intervals, log snippets below

Connection Method is Always-On

Client V6.2.5 

Is the below Gateway selection process expected & always been the case? Signing into GPCS at particular moment in time, when GPCS Client working through "Available Gateway" list in background without user manual login, which will interfere with logging into nearest gateway based on Weight etc?

(P5820-T31220)Debug(1374): 02/04/25 09:21:49:341 gateway US Northwest (us-northwest-g-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=289 ms, assign 200 as its weight
(P5820-T31220)Debug(1374): 02/04/25 09:21:49:341 gateway Japan Central (japan-central-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=491 ms, assign 300 as its weight
(P5820-T31220)Debug(1374): 02/04/25 09:21:49:341 gateway Hong Kong (hong-kong-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=439 ms, assign 274 as its weight
(P5820-T31220)Info (1413): 02/04/25 09:21:49:341 CPanGatewayList::PickGatewayBaseOnWeight, PAN_NEW_GATEWAY_SELECTOR, chose prefered gateway index =1, gateway is US Northwest 

(P5820-T31220)Debug(1374): 02/04/25 09:31:56:138 gateway Japan Central (japan-central-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=491 ms, assign 300 as its weight
(P5820-T31220)Debug(1374): 02/04/25 09:31:56:138 gateway Hong Kong (hong-kong-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=439 ms, assign 200 as its weight

(P5820-T31220)Debug(1374): 02/04/25 09:42:04:095 gateway Japan Central (japan-central-zurichno.9s9hytwbzt.gw.gpcloudservice.com), priority=5, duration=491 ms, assign 200 as its weight
(P5820-T31220)Info (1413): 02/04/25 09:42:04:095 CPanGatewayList::PickGatewayBaseOnWeight, PAN_NEW_GATEWAY_SELECTOR, chose prefered gateway index =7, gateway is Japan Central

(P5820-T31220)Debug(4154): 02/04/25 09:52:03:485 ----Gateway Login starts----
(P5820-T31220)Debug(14194): 02/04/25 09:52:03:485 Set to service bUseCCUserGateway 0 and ccUserNameGateway
(P5820-T31220)Debug(2188): 02/04/25 09:52:03:485 Update user name from <username> to <username>

Please help shine some light here 

[nikoolayy1]

The best gateway is selected based on response time or response time + load (CPU and memory on the gateway) Best Gateway Selection Criteria / Features Introduced. You can try changing the selection algorithm and going to 6.3.1. Other than that bad network conditions between the client and the closest gateway could also affect the selection also you could disable this feature if you want only geolocation selection . Also as mentioned in here How the GlobalProtect App Selects Prisma Access Locations for Mobile Users I suspect you have issues with users that do not have in country gateway that should be uses , so they have to go to the nearest one in the next country.

Keep in mind that with Prisma Access ADEM AI-Powered ADEM Demo you can ask as user to manually select a gateway they should use and see if the networking conditions are bad between the user and Prisma Access as maybe the reason for not auto selecting the gateway.