Search code examples
azureroutesazure-traffic-manager

Azure Traffic Manger Priority Routing is not working

I created an Azure Traffic manager and routing with Priority.As per this

The Traffic Manager profile contains a prioritized list of service endpoints. By default, Traffic Manager sends all traffic to the primary (highest-priority) endpoint. If the primary endpoint is not available, Traffic Manager routes the traffic to the second endpoint. If both the primary and secondary endpoints are not available, the traffic goes to the third, and so on

My Traffic Manager monitoring

Low Priority

enter image description here

High Priority enter image description here

I tried to increase the priority and decrease the priority but there is no change.

Still, you can see that traffic manager pointing towards the teststatic site alone

Another question from the above doc

If the primary endpoint is not available

Here what is mean by not available? As I'm using Azure Web Apps for my testing purpose, So I thought When Stopping my webapp could be not available. But I'm wrong, Even though I stop the web app, still, the traffic manager pointing the stopped web app. So I'm confused about what is mean by not available here?

Solution

  • In your screenshots, the test endpoint monitor status is always a Degraded status. This indicated that the endpoint is not included in DNS reponses and does not receive traffic. So the Traffic Manager is still pointing towards the teststatic site alone. Traffic Manager considers an endpoint to be ONLINE only when the probe receives an HTTP 200 response back from the probe path If the monitoring protocol is HTTP or HTTPS. Any other non-200 response is a failure.

    You need to troubleshoot degraded state on Azure Traffic Manager and see Traffic Manager shows monitor status is degraded – Resolution

    what is mean by not available here?

    The traffic manager chooses an endpoint based on the status of each endpoint (disabled endpoint are not returned), the current health of each endpoint and the chosen traffic-routing method. If the endpoint is not available, that is to say the endpoint is not included the DNS response or is an unhealthy endpoint. But an exception to this is if all endpoints are degraded, in which case all of them will be considered to be returned in the query response. You can get more details from endpoint monitor status.

    An endpoint is unhealthy when any of the following events occur: A non-200 response is received (including a different 2xx code, or a 301/302 redirect); Request for client authentication; Timeout (the timeout threshold is 10 seconds; Unable to connect.

    Besides, Type ipconfig /flushdns to flush the DNS resolver cache when you verity the Traffic Manager Settings.