Not connecting to nearest gateway


ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

L2 Linker

Not connecting to nearest gateway

Hi All,

We are testing Prisma access and user is not connecting to nearest gateway. We have selected 3 locations India west east and south, user is close to south region but always connect to India west. When I check the GPA logs it shows priority for India west has priority 5 but in the portal configuration portal>agent>external we have set source region any and priority as highest ( admin guide asks to keep it none but that option not available)

I know that gateway select is based on ssl response time but how to find which is lowest response time from the logs??

L1 Bithead

In your PanGPS.log, filter off the following:



The response times it will list are the tcp connection time and ssl handshake time.

L2 Linker


The response time is what we need to check, but for India West location there is a hard code set for high priority hence, it will always get elected. We tried with India south and Singapore, it is working as expected.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!