From a08354702a0f1ebcee1cf06e91086cb5bf3f3e97 Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Mon, 24 Jun 2024 07:23:18 -0700 Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md --- ...LAB_05-Implement_Intersite_Connectivity.md | 29 ++++--------------- 1 file changed, 6 insertions(+), 23 deletions(-) diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index 3eecb421d..f94a0202c 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -169,39 +169,22 @@ In this task, you create a virtual network peering to enable communications betw 1. In CoreServicesVnet, under **Settings**, select **Peerings**. -1. On CoreServicesVnet | Peerings, select **+ Add**. - -1. Use the information in the following table to create the peering. +1. On CoreServicesVnet | Peerings, select **+ Add**. If not specified, take the default. | **Parameter** | **Value** | -| --------------------------------------------- | ------------------------------------- | -| **This virtual network** | | +| --------------------------------------------- | ------------------------------------- | | Peering link name | `CoreServicesVnet-to-ManufacturingVnet` | -| Allow CoreServicesVnet to access the peered virtual network | selected (default) | -| Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network | selected | -| Allow gateway in CoreServicesVnet to forward traffic to the peered virtual network | Not selected (default) | -| Enable CoreServicesVnt to use the peered virtual networks' remote gateway | Not selected (default) | -| **Remote virtual network** | | -| Peering link name | `ManufacturingVnet-to-CoreServicesVnet` | -| Virtual network deployment model | **Resource manager** | -| I know my resource ID | Not selected | -| Subscription | *your subscription* | -| Virtual network | **ManufacturingVnet** | +| Virtual network | **ManufacturingVM-net (az104-rg5)** | | Allow ManufacturingVnet to access CoreServicesVnet | selected (default) | | Allow ManufacturingVnet to receive forwarded traffic from CoreServicesVnet | selected | -| Allow gateway in CoreServicesVnet to forward traffic to the peered virtual network | Not selected (default) | -| Enable ManufacturingVnet to use CoreServicesVnet's remote gateway | Not selected (default) | - -1. Review your settings and select **Add**. - -![Screenshot of peering page.](../media/az104-lab05-peering.png) +| Peering link name | `ManufacturingVnet-to-CoreServicesVnet` | +| Allow CoreServicesVnet to access the peered virtual network | selected (default) | +| Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network | selected | - 1. In CoreServicesVnet | Peerings, verify that the **CoreServicesVnet-to-ManufacturingVnet** peering is listed. Refresh the page to ensure the **Peering status** is **Connected**. 1. Switch to the **ManufacturingVnet** and verify the **ManufacturingVnet-to-CoreServicesVnet** peering is listed. Ensure the **Peering status** is **Connected**. You may need to **Refresh** the page. - ## Task 5: Use Azure PowerShell to test the connection between virtual machines In this task, you retest the connection between the virtual machines in different virtual networks.