Forum Discussion

Copper Contributor

Sep 17, 2020

Meaning of GatewayRegion_s field in in WVDActivityV1_CL table in log analytics

I am trying to troubleshoot some disconnect issues with a customer in the Western Europe region. I used the following query to list all the connections (it's not the ARM release of WVD): WVDActi...

Soo Kuan Teo

Microsoft

Oct 06, 2020

Thansk for your feedback! Good observation! This is expected. WVD gateways are distributed geographically in multiple Azure regions. Our attempt is to load-balance the traffic across nearby regions as to offer the best performance and experience for all users of WVD. Towards that, we make use of Azure FrontDoor with latency based traffic routing (https://docs.microsoft.com/en-us/azure/frontdoor/front-door-routing-methods#lowest-latencies-based-traffic-routing) and route users to gateways that are in the relative vicinity (not necessarily the one closest to them) without any negative impact on their user experience.

YannickJanssens

Copper Contributor

Oct 07, 2020

Soo Kuan Teo

Thank you for the reply! That would explain the results.

So my understanding of how the gateway is chosen does seem to be a bit off (I based this on a blog post about this topic somewhere).

I assumed that running an nslookup of rdgateway.wvd.microsoft.com would correctly show the gateway that would be used if I was to start a WVD session. For example at the moment is shows me:

Name: waws-prod-am2-f32c0796.cloudapp.net
Address: 51.136.28.200
Aliases: rdgateway.wvd.microsoft.com
rdgateway-prod-geo.trafficmanager.net
mrs-weur1c100-rdgateway-prod.wvd-ase-weur1c100-prod.p.azurewebsites.net
waws-prod-am2-f32c0796.sip.p.azurewebsites.windows.net

But running a capture with Wireshark does indeed show DNS entries such as afd-rdgateway-r1.wvd.microsoft.com which does imply that a Frontdoor service is at work.

Thanks again for the explanation.