Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-04 23:59: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:
staleycyn 2023-05-15 11:47:43 -07:00 committed by GitHub
parent 646287736c
commit 20ed91f32a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -214,7 +214,7 @@ In this task, you will test transitivity of virtual network peering by using Net
> **Note**: **10.62.0.4** represents the private IP address of **az104-06-vm2**
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 connection was direct, with no intermediate hops in between the VMs.
1. Click **Run diagnostic tests** and wait until results of the connectivity check are returned. Verify that the status is **Success**. Review the network path and note that the connection was direct, with no intermediate hops in between the VMs.
> **Note**: This is expected, since the hub virtual network is peered directly with the first spoke virtual network.
@ -233,7 +233,7 @@ In this task, you will test transitivity of virtual network peering by using Net
> **Note**: **10.63.0.4** represents the private IP address of **az104-06-vm3**
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 connection was direct, with no intermediate hops in between the VMs.
1. Click **Run diagnostic tests** and wait until results of the connectivity check are returned. Verify that the status is **Success**. Review the network path and note that the connection was direct, with no intermediate hops in between the VMs.
> **Note**: This is expected, since the hub virtual network is peered directly with the second spoke virtual network.
@ -250,7 +250,7 @@ In this task, you will test transitivity of virtual network peering by using Net
| Protocol | **TCP** |
| Destination Port | **3389** |
1. Click **Check** and wait until results of the connectivity check are returned. Note that the status is **Unreachable**.
1. Click **Run diagnostic tests** and wait until results of the connectivity check are returned. Note that the status is **Fail**.
> **Note**: This is expected, since the two spoke virtual networks are not peered with each other (virtual network peering is not transitive).
@ -388,7 +388,7 @@ In this task, you will configure and test routing between the two spoke virtual
1. In the Azure portal, navigate back to the **Network Watcher - Connection troubleshoot** blade.
1. On the **Network Watcher - Connection troubleshoot** blade, initiate a check with the following settings (leave others with their default values):
1. On the **Network Watcher - Connection troubleshoot** blade, use the following settings (leave others with their default values):
| Setting | Value |
| --- | --- |
@ -401,7 +401,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 stop and then start az104-06-vm0.
1. Click **Run diagnostic tests** and wait until results of the connectivity check are returned. Verify that the status is **Success**. 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 **Fail**, 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.