Previous

Next

Exercise: Troubleshoot routing, traffic control and load balancing issues

Completed

You work as a support engineer supporting Azure infrastructure. You've been contacted by your web team about an issue with website performance. The web team has a pool of webservers behind a load balancer and public IP address.

The web team thinks that the internet traffic isn't being distributed equally between all the webservers.

In this exercise, you'll use what you've learned to go through steps to troubleshoot the performance issues with your organizations website.

Check that the issue still exists

1. Using the Cloud Shell to the right, run this command.

   az network public-ip show \
   --resource-group <rgn>[sandbox resource group name]</rgn> \
   --name webPublicIP \
   --query '[ipAddress]' \
   --output tsv
   

2. Paste the IP address returned into a new browser tab.

   

   Note

   Your IP address will be different to the one shown in the screenshot.

3. Hit refresh in your browser, or on Windows press the F5 ten or twenty times. Notice that you are getting a response from the same webserver every single time.

4. Leave this tab open to check you resolve the issue in the next exercise.

Check all the virtual machines are responding on port 80

1. Navigate to the Azure portal in another browser tab.

2. Select Virtual machines.

   

3. Select webVirtualMachine1.

4. Under Settings, select Networking.

   

5. Check that inbound traffic is allowed on port 80.

6. Repeat the above for webVirtualMachine2.

The current settings appear to be correct.

Check the Load Balancer settings

1. Select Home.

2. Search for Load balancers.

   

3. Under Services, select Load balancers.

   

4. Select webLoadBalancer.

5. Under Settings, Select the Frontend IP configuration.

   

   Note

   There is a correctly configured frontend IP address. Check that it matches the IP address you have in your other tab.

6. Under Settings, select Backend pools.

   

   Note

   The virtual machines are both running.

7. Under Settings, select Load balancing rules, then select webLoadBalancerRule.

   

8. Check all the settings for the load balancer rule.

   

You think you have identified the issue. At the moment once a user visits the website they are routed to one virtual machine. This will persist because of the Session persistence setting.

You'll resolve the issue in the next exercise.

Continue