- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-24-2020 05:00 AM
Hello!
I was wondering if anyone could shed some light on what exactly is meant by pre-tunnel and post-tunnel latency, which can be found under the GlobalProtect monitor.
Is it latency before the tunnel was created, and then after the tunnel was created?
Or does pre-tunnel latency + post-tunnel latency = tunnel latency?
What can it tell me about a clients connection? Low latency is obviously good, but when I see a pre-tunnel latency of 1200, can I point blame on the clients local internet connection, or elsewhere?
I can't find anything clear from Palo Alto on these terms, so any ideas on the subject would be very much appreciated!
12-02-2020 06:24 AM
I would suggest that a pre-tunnel latency of 1200 is really quite bad and could lead to end user experience issues, the tunnel latency in my understanding is the latency to the endpoint when it logs onto the portal (pre-tunnel) and once the tunnel comes up (post-tunnel) the paths that the packets take across the internet will have a big bearing on the latency stats.
I would say the best use for this information would be with distributed gateways, for instance if you have a portal in the UK and a gateway in the US and the UK, a user in the US should use the gateway that is closest (least latency) and then use a faster connection through MPLS or SD-WAN back to corporate resources.
12-02-2020 06:24 AM
I would suggest that a pre-tunnel latency of 1200 is really quite bad and could lead to end user experience issues, the tunnel latency in my understanding is the latency to the endpoint when it logs onto the portal (pre-tunnel) and once the tunnel comes up (post-tunnel) the paths that the packets take across the internet will have a big bearing on the latency stats.
I would say the best use for this information would be with distributed gateways, for instance if you have a portal in the UK and a gateway in the US and the UK, a user in the US should use the gateway that is closest (least latency) and then use a faster connection through MPLS or SD-WAN back to corporate resources.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!