Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-06 00:29:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_06-Implement_Network_Traffic_Management.md

Browse Source
This commit is contained in:
Clifford Brent Smith 2021-02-10 21:03:31 -07:00 committed by GitHub
parent 990187bb85
commit 48443927dc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 44 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
View File

@ -97,7 +97,7 @@ In this task, you will deploy four virtual machines into the same Azure region.
-nameSuffix 3 `
-AsJob
```
>**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 5 minutes.
>**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 5 - 15 minutes.
>**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task.
@ -117,7 +117,7 @@ In this task, you will configure local peering between the virtual networks you
1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**.
1. Add a peering with the following settings (leave others with their default values):
1. Add a peering with the following settings (leave others with their default values) and click Add:
| Setting | Value |
| --- | --- |
@ -141,7 +141,7 @@ In this task, you will configure local peering between the virtual networks you
1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**.
1. Add a peering with the following settings (leave others with their default values):
1. Add a peering with the following settings (leave others with their default values) and click Add:
| Setting | Value |
| --- | --- |
@ -280,17 +280,19 @@ In this task, you will configure and test routing between the two spoke virtual
| Setting | Value |
| --- | --- |
| Name | **az104-06-rt23** |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg2** |
| Location | the name of the Azure region in which you created the virtual networks |
| Name | **az104-06-rt23** |
| Propagate gateway routes | **No** |
1. Click **Review and Create**. Let validation occur, and click **Create** to submit your deployment.
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt23**.
1. On the **az104-06-rt23** route table blade, click **Routes** and then click **+ Add**.
1. On the **az104-06-rt23** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**.
1. Add a new route with the following settings (leave others with their default values):
@ -300,8 +302,10 @@ In this task, you will configure and test routing between the two spoke virtual
| Address prefix | **10.63.0.0/20** |
| Next hop type | **Virtual appliance** |
| Next hop address | **10.60.0.4** |
1. Click **OK**
1. Back on the **az104-06-rt23** route table blade, click **Subnets** and then click **+ Associate**.
1. Back on the **az104-06-rt23** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**.
1. Associate the route table **az104-06-rt23** with the following subnet:
@ -309,6 +313,8 @@ In this task, you will configure and test routing between the two spoke virtual
| --- | --- |
| Virtual network | **az104-06-vnet2** |
| Subnet | **subnet0** |
1. Click **OK**
1. Navigate back to **Route tables** blade and click **+ Add**.
@ -316,19 +322,21 @@ In this task, you will configure and test routing between the two spoke virtual
| Setting | Value |
| --- | --- |
| Name | **az104-06-rt32** |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg3** |
| Location | the name of the Azure region in which you created the virtual networks |
| Region | the name of the Azure region in which you created the virtual networks |
| Name | **az104-06-rt32** |
| Propagate gateway routes | **No** |
1. Click Review and Create. Let validation occur, and hit Create to submit your deployment.
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt32**.
1. On the **az104-06-rt32** route table blade, click **Routes** and then click **+ Add**.
1. On the **az104-06-rt32** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**.
1. Add a new route with the following settings (leave others with their default values):
1. Add a new route with the following settings:
| Setting | Value |
| --- | --- |
@ -336,8 +344,10 @@ In this task, you will configure and test routing between the two spoke virtual
| Address prefix | **10.62.0.0/20** |
| Next hop type | **Virtual appliance** |
| Next hop address | **10.60.0.4** |
1. Click **OK**
1. Back on the **az104-06-rt32** route table blade, click **Subnets** and then click **+ Associate**.
1. Back on the **az104-06-rt32** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**.
1. Associate the route table **az104-06-rt32** with the following subnet:
@ -345,6 +355,8 @@ In this task, you will configure and test routing between the two spoke virtual
| --- | --- |
| Virtual network | **az104-06-vnet3** |
| Subnet | **subnet0** |
1.Click **OK**
1. In the Azure portal, navigate back to the **Network Watcher - Connection troubleshoot** blade.
@ -386,14 +398,15 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| SKU | **Standard** |
| Public IP address | **Create new** |
| Public IP address name | **az104-06-pip4** |
| Availability zone | **Zone-redundant** |
| Add a public IPv6 address | **No** |
1. Click Review and Create. Let validation occur, and hit Create to submit your deployment.
> **Note**: Wait for the Azure load balancer to be provisioned. This should take about 2 minutes.
1. On the deployment blade, click **Go to resource**.
1. On the **az104-06-lb4** load balancer blade, click **Backend pools** and click **+ Add**.
1. On the **az104-06-lb4** load balancer blade, in the **Settings** section, click **Backend pools**, and click **+ Add**.
1. Add a backend pool with the following settings (leave others with their default values):
@ -406,10 +419,12 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Virtual machine IP address | **ipconfig1 (10.60.0.4)** |
| Virtual machine | **az104-06-vm1** |
| Virtual machine IP address | **ipconfig1 (10.60.1.4)** |
1. Click **Add**
1. Wait for the backend pool to be created, click **Health probes**, and then click **+ Add**.
1. Wait for the backend pool to be created, in the **Settings** section, click **Health probes**, and then click **+ Add**.
1. Add a health probe with the following settings (leave others with their default values):
1. Add a health probe with the following settings:
| Setting | Value |
| --- | --- |
@ -418,8 +433,10 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Port | **80** |
| Interval | **5** |
| Unhealthy threshold | **2** |
1. Click **OK**
1. Wait for the health probe to be created, click **Load balancing rules**, and then click **+ Add**.
1. Wait for the health probe to be created, in the **Settings** section, click **Load balancing rules**, and then click **+ Add**.
1. Add a load balancing rule with the following settings (leave others with their default values):
@ -436,7 +453,8 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Idle timeout (minutes) | **4** |
| TCP reset | **Disabled** |
| Floating IP (direct server return) | **Disabled** |
| Use outbound rules to provide backend pool members access to the internet. | **Enabled** |
1. Click **OK**
1. Wait for the load balancing rule to be created, click **Overview**, and note the value of the **Public IP address**.
@ -463,9 +481,9 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Setting | Value |
| --- | --- |
| Name | **subnet-appgw** |
| Address range (CIDR block) | **10.60.3.224/27** |
| Network security group | **None** |
| Route table | **None** |
| Subnet address range | **10.60.3.224/27** |
1. Click **Save**
> **Note**: This subnet will be used by the Azure Application Gateway instances, which you will deploy later in this task. The Application Gateway requires a dedicated subnet of /27 or larger size.
@ -481,8 +499,6 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Region | name of the Azure region into which you deployed all other resources in this lab |
| Tier | **Standard V2** |
| Enable autoscaling | **No** |
| Scale units | **1** |
| Availability zone | **1, 2, 3** |
| HTTP2 | **Disabled** |
| Virtual network | **az104-06-vnet01** |
| Subnet | **subnet-appgw** |
@ -509,7 +525,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
1. Click **Add**, click **Next: Configuration >** and, on the **Configuration** tab of the **Create an application gateway** blade, click **+ Add a routing rule**.
1. On the **Add a routing rule** blade, on the **Listener** tab, specify the following settings (leave others with their default values):
1. On the **Add a routing rule** blade, on the **Listener** tab, specify the following settings:
| Setting | Value |
| --- | --- |
@ -520,7 +536,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Port | **80** |
| Listener type | **Basic** |
| Error page url | **No** |
1. Switch to the **Backend targets** tab of the **Add a routing rule** blade and specify the following settings (leave others with their default values):
| Setting | Value |
@ -528,11 +544,11 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Target type | **Backend pool** |
| Backend target | **az104-06-appgw5-be1** |
1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Add new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values):
1. Click **Add new** under to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values):
| Setting | Value |
| --- | --- |
| HTTP setting name | **az104-06-appgw5-http1** |
| HTTP setting | **az104-06-appgw5-http1** |
| Backend protocol | **HTTP** |
| Backend port | **80** |
| Cookie-based affinity | **Disable** |