Merge pull request #530 from MOC-Labs-Review/MOC-Labs-Review-patch-15

Update LAB_06-Implement_Network_Traffic_Management.md
This commit is contained in:
staleycyn 2022-04-09 06:56:09 -07:00 committed by GitHub
commit 4bf6fb07b2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -56,10 +56,12 @@ In this task, you will deploy four virtual machines into the same Azure region.
```powershell
$location = '[Azure_region]'
```
Now the resource group name:
```powershell
$rgName = 'az104-06-rg1'
```
And finally create the resource group in your desired location:
```powershell
New-AzResourceGroup -Name $rgName -Location $location
@ -384,7 +386,7 @@ In this task, you will configure and test routing between the two spoke virtual
| Protocol | **TCP** |
| Destination Port | **3389** |
1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. If status is **Unreachable**, you should restart az104-06-vm0.
1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. If status is **Unreachable**, you should stop and then start az104-06-vm0.
> **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router.