From 50a6907018c809526ae085f6a21eb44661e18117 Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Sat, 9 Dec 2023 07:06:57 -0800 Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md --- ...LAB_05-Implement_Intersite_Connectivity.md | 22 ++++++++++++++----- 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md index 3f8f6404..eef3b5b1 100644 --- a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md +++ b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md @@ -79,7 +79,9 @@ In this task, we create a core services virtual network with a virtual machine. 1. Select **Review + Create**, and then select **Create**. -1. You do not need to wait for the virtual machine to be created. Continue on to the next task. +1. You do not need to wait for the resources to be created. Continue on to the next task. + + >**Note:** Did you notice in this task you created the virtual network when you created the virtual machine? ## Task 2: Create a manufacturing services virtual machine and virtual network. @@ -121,6 +123,7 @@ In this task, we create a manufacturing services virtual network with a virtual 1. Select **Review + Create**, and then select **Create**. ## Task 3: Test the connection between the virtual machines. + In this task, you test the connection between the virtual machines in different virtual networks. ### Verify the private IP address fo the CoreServicesVM @@ -129,7 +132,7 @@ In this task, you test the connection between the virtual machines in different 1. On the **Overview** blade, in the **Networking** section, record the **Private IP address** of the machine. You need this information to test the connection. -### Connect to the **ManufacturingVM**. +### Test the connection to the CoreServicesVM from the **ManufacturingVM**. 1. In the portal, select for and select the `**ManufacturingVM**` virtual machine. @@ -137,8 +140,10 @@ In this task, you test the connection between the virtual machines in different 1. Select **RunPowerShellScript** and run the **Test-NetConnection** command. Be sure to use the private IP address of the **CoreServicesVM**. - ```Test-NetConnection -port 3389``` - + ```Powershell + Test-NetConnection -port 3389``` + ``` + 1. It may take a couple of minutes for the script to run. The top of the page shows an informational message *Script execution in progress.* 1. The test connection should fail. Virtual machines in different virtual networks should, by default, not be able to communicate. @@ -169,7 +174,7 @@ In this task, you create virtual network peerings to enable communications betwe | | Peering link name | `ManufacturingVnet-to-CoreServicesVnet` | | | Virtual network deployment model | **Resource manager** | | | I know my resource ID | Not selected | - | | Subscription | | + | | Subscription | *your subscription* | | | Virtual network | **ManufacturingVnet** | | | Traffic to remote virtual network | Allow (default) | | | Traffic forwarded from remote virtual network | **Allow** | @@ -206,7 +211,12 @@ In this task, you verify the virtual machines in different virtual networks can Congratulations on completing the lab. Here are the main takeaways for this lab. ++ By default, resources in different virtual networks cannot communicate with other. ++ Virtual network peering enables you to seamlessly connect two or more virtual networks in Azure. ++ Peered virtual networks appear as one for connectivity purposes. ++ The traffic between virtual machines in peered virtual networks uses the Microsoft backbone infrastructure. + ## Cleanup your resources -If you are working with your own subscription take a minute to delete the lab resource. This will ensure resourcess are freed up and cost is minimized. +If you are working with your own subscription take a minute to delete the lab resource group. This will ensure resources are freed up and cost is minimized.