https:\/\/azure.microsoft.com\/en-us\/regions\/offers\/<\/strong><\/a><\/p>\n\n\n\nNote<\/strong>: To identify the names of the Azure regions to use when setting the value of the LOCATION<\/strong> variable, run az account list-locations –query “[].{name:name}” -o table. Make sure to use the notation which does not include a space, e.g. eastus<\/strong> rather than US East<\/strong>.<\/p>\n\n\n\nFrom the Cloud Shell pane, run the following to create an instance of Network Watcher in preparation for the upcoming exercises in this lab:<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
az network watcher configure --resource-group NetworkWatcherRG --locations $LOCATION --enabled -o table<\/code><\/pre>\n\n\n\nNote<\/strong>: If you receive an error indicating there is no \u201cNetworkWatcherRG\u201d resource group, create a resource group from the portal named NetworkWatcherRG and rerun the command.<\/p>\n\n\n\nFrom the Cloud Shell pane, run the following to create a resource group in the designated Azure region.<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
az deployment sub create --location $LOCATION --template-file azuredeployexceed30305suba.json --parameters rgName=exceed05a-labRG rgLocation=$LOCATION\n\n<\/code><\/pre>\n\n\n\nFrom the Cloud Shell pane, upload the Azure Resource Manager template \\Azurelabs03\\azuredeployexceed30305rga.json<\/strong>.<\/li>From the Cloud Shell pane, upload the Azure Resource Manager parameter file \\Azurelabs03\\azuredeployexceed30305rga.parameters.json<\/strong>.<\/li>From the Cloud Shell pane, run the following to deploy an Azure Load Balancer Basic with its backend pool consisting of a pair of Azure VMs hosting Windows Server 2019 Datacenter Core into the same availability set (replace the <vm_Size> placeholder with the size of the Azure VM you intend to use for this deployment, such as Standard_D2s_v3):<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
az deployment group create --resource-group exceed05a-labRG --template-file azuredeployexceed30305rga.json --parameters @azuredeployexceed30305rga.parameters.json vmSize=Standard_D2s_v3<\/code><\/pre>\n\n\n\nNote<\/strong>: Wait for the deployment to complete before proceeding to the next task. This should take about 10 minutes.<\/p>\n\n\n\nIn the Azure portal, close the Cloud Shell<\/strong> pane.<\/li><\/ol>\n\n\n\nTask 2: Analyze highly available Azure VMs deployed into an availability set behind an Azure Load Balancer Basic<\/strong><\/p>\n\n\n\nIn the Azure portal, search for and select Network Watcher<\/strong> and, on the Network Watcher<\/strong> blade, select Topology<\/strong>.<\/li>On the Network Watcher | Topology<\/strong> blade, specify the following settings:<\/li><\/ul>\n\n\n\nSetting<\/td> Value<\/td><\/tr><\/thead> Subscription<\/td> the name of the Azure subscription you are using in this lab<\/td><\/tr> Resource Group<\/td> exceed05a-labRG<\/strong><\/td><\/tr>Virtual Network<\/td> exceed05a-vnet<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nReview the resulting topology diagram, noting the connections between the public IP address, load balancer, and the network adapters of Azure VMs in its backend pool.<\/li><\/ul>\n\n\n\nOn the Network Watcher<\/strong> blade, select Effective security rules<\/strong>.<\/li>On the Network Watcher | Effective security rules<\/strong> blade, specify the following settings:<\/li><\/ul>\n\n\n\nSetting<\/td> Value<\/td><\/tr><\/thead> Subscription<\/td> the name of the Azure subscription you are using in this lab<\/td><\/tr> Resource group<\/td> exceed05a-labRG<\/strong><\/td><\/tr>Virtual machine<\/td> exceed05a-vm0<\/strong><\/td><\/tr>Network interface<\/td> exceed05a-nic0<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nReview the associated network security group and the effective security rules, including two custom rules that allow inbound connectivity via RDP and HTTP.<\/li><\/ul>\n\n\n\nNote<\/strong>: Alternatively, you can view Effective security rules<\/strong> from:<\/p>\n\n\n\nthe exceed05a-nic0<\/strong> network interface blade.the exceed05a-web-nsg<\/strong> network security group blade<\/li><\/ul><\/li><\/ul>\n\n\n\nOn the Network Watcher<\/strong> blade, select Connection troubleshoot<\/strong>.<\/li><\/ul>\n\n\n\nNote<\/strong>: The intention is to verify the proximity (in the networking terms) of the two Azure VMs in the same availability set.<\/p>\n\n\n\nOn the Network Watcher | Connection troubleshoot<\/strong> blade, specify the following settings and select Check<\/strong> :<\/li><\/ul>\n\n\n\nSetting<\/td> Value<\/td><\/tr><\/thead> Subscription<\/td> the name of the Azure subscription you are using in this lab<\/td><\/tr> Resource group<\/td> exceed05a-labRG<\/strong><\/td><\/tr>Source type<\/td> Virtual machine<\/strong><\/td><\/tr>Virtual machine<\/td> exceed05a-vm0<\/strong><\/td><\/tr>Destination<\/td> Select a virtual machine<\/strong><\/td><\/tr>Resource group<\/td> exceed05a-labRG<\/strong><\/td><\/tr>Virtual machine<\/td> exceed05a-vm1<\/strong><\/td><\/tr>Protocol<\/td> TCP<\/strong><\/td><\/tr>Destination port<\/td> 80<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nNote<\/strong>: You will need to wait a few minutes for the results in order for the Azure Network Watcher Agent<\/strong> VM extension to be installed on the Azure VMs.<\/li><\/ul>\n\n\n\nReview the results and note the latency of the network connection between the Azure VMs.<\/li><\/ol>\n\n\n\nNote<\/strong>: The latency should be about 1 millisecond, since both VMs are in the same availability set (within the same Azure datacenter).<\/p>\n\n\n\nIn the Azure portal, navigate to the exceed05a-labRG<\/strong> resource group blade, in the list of resources, select the exceed05a-avset<\/strong> availability set entry, and on the exceed05a-avset<\/strong> blade, note the fault domain and update domain values assigned the two Azure VMs.<\/p>\n\n\n\nIn the Azure portal, navigate back to the exceed05a-labRG<\/strong> resource group blade, in the list of resources, select the exceed05a-lb<\/strong> load balancer entry, and on the exceed05a-lb<\/strong> blade, note the public IP address entry.<\/li>In the Azure portal, start a Bash<\/strong> session in the Cloud Shell pane.<\/li>From the Cloud Shell pane, run the following to test load balancing of HTTP traffic to the Azure VMs in the backend pool of the Azure load balancer (replace the <lb_IP_address> placeholder with the IP address of the front end of the load balancer you identified earlier):<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
for i in {1..4}; do curl 40.71.66.236; done<\/code><\/pre>\n\n\n\nNote<\/strong>: Verify that the returned messages indicate that the requests are being delivered in the round robin manner to the backend Azure VMs<\/p>\n\n\n\nOn the exceed05a-lb<\/strong> blade, select the Load balancing rules<\/strong> entry and, on the exceed05a-lb | Load balancing rules<\/strong> blade, select the exceed05a-lbruletcp80<\/strong> entry representing the load balancing rule handling HTTP traffic.<\/li>On the exceed05a-lbruletcp80<\/strong> blade, in the Session persistence<\/strong> drop-down list, select Client IP<\/strong> and then select Save<\/strong>.<\/li><\/ul>\n\n\n\nWait for the update to complete and, from the Cloud Shell pane, re-run the following to test load balancing of HTTP traffic to the Azure VMs in the backend pool of the Azure load balancer with session persistence (replace the <lb_IP_address> placeholder with the IP address of the front end of the load balancer you identified earlier):<\/li><\/ol>\n\n\n\nCode<\/p>\n\n\n\n
for i in {1..4}; do curl 40.71.66.236; done<\/code><\/pre>\n\n\n\nNote<\/strong>: Verify that the returned messages indicate that the requests are being delivered to the same backend Azure VMs<\/p>\n\n\n\nIn the Azure portal, navigate back to the exceed05a-lb<\/strong> blade, select the Inbound NAT rules<\/strong> entry and note the two rules that allow for connecting to the first and the second of the backend pool VMs via Remote Desktop over TCP ports 33890 and 33891, respectively.<\/p>\n\n\n\nFrom the Cloud Shell pane, run the following to test Remote Desktop connectivity via NAT to the first Azure VM in the backend pool of the Azure load balancer (replace the <lb_IP_address> placeholder with the IP address of the front end of the load balancer you identified earlier):<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
curl -v telnet:\/\/40.71.66.236:33890<\/code><\/pre>\n\n\n\nNote<\/strong>: Verify that the returned message indicates that you are successfully connected.<\/p>\n\n\n\nPress the Ctrl+C<\/strong> key combination to return to the Bash shell prompt and run the following to test Remote Desktop connectivity via NAT to the second Azure VM in the backend pool of the Azure load balancer (replace the <lb_IP_address> placeholder with the IP address of the front end of the load balancer you identified earlier):<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
curl -v telnet:\/\/40.71.66.236:33891<\/code><\/pre>\n\n\n\nNote<\/strong>: Verify that the returned message indicates that you are successfully connected.<\/p>\n\n\n\nPress the Ctrl+C<\/strong> key combination to return to the Bash shell prompt.<\/p>\n\n\n\n<\/p>\n\n\n\n
Task 3: Remove Azure resources deployed in the exercise<\/strong><\/p>\n\n\n\nFrom the Cloud Shell pane, run the following to list the resource group you created in this exercise:<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
az group list --query \"[?starts_with(name,'exceed05a-')]\".name --output tsv<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
Note<\/strong>: Verify that the output contains only the resource group you created in this lab. This group will be deleted in this task.<\/p>\n\n\n\nFrom the Cloud Shell pane, run the following to delete the resource group you created in this lab<\/li><\/ul>\n\n\n\nCode<\/p>\n\n\n\n
az group list --query \"[?starts_with(name,'exceed05a-')]\".name --output tsv | xargs -L1 bash -c 'az group delete --name $0 --no-wait --yes'<\/code><\/pre>\n\n\n\nClose the Cloud Shell pane.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Lab 2: Implement and analyze highly available Azure VM deployments using availability zones and Azure Load Balancer Standard<\/strong><\/p>\n\n\n\nThe main tasks for this lab are as follows:<\/p>\n\n\n\n
Deploy highly available Azure VMs into availability zones behind an Azure Load Balancer Standard by using Azure Resource Manager templates<\/li> Analyze highly available Azure VMs deployed across availability zones behind an Azure Load Balancer Standard<\/li> Remove Azure resources deployed in the exercise<\/li><\/ul>\n\n\n\nTask 1: Deploy highly available Azure VMs into availability zones behind an Azure Load Balancer Standard by using Azure Resource Manager templates<\/strong><\/p>\n\n\n\nIf needed, in the Azure portal, open Cloud Shell<\/strong> pane by selecting on the toolbar icon directly to the right of the search textbox.<\/li>If prompted to select either Bash<\/strong> or PowerShell<\/strong>, select Bash<\/strong>.<\/li>In the toolbar of the Cloud Shell pane, select the Upload\/Download files<\/strong> icon, in the drop-down menu select
![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img1-11-1024x134.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img2-11-1024x372.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img3-10-1024x413.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img4-10.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img5-10-1024x455.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img6-9.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img7-9-1024x341.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img8-9-1024x119.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img9-9-1024x432.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img10-3-6-1024x141.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img11-3-6-1024x232.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img12-3-3-1024x151.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img13-3-3-1024x152.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/02\/img14-8-1024x78.png\")
<\/figure>\n\n\n\n