From 7e8c5434b57ac836e0805e7270f3306ad9e56be7 Mon Sep 17 00:00:00 2001 From: awillslo Date: Tue, 13 May 2025 16:36:16 -0400 Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md minor changes to match UI navigation and selection --- .../LAB_05-Implement_Intersite_Connectivity.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index cac333c4..4014d89a 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -181,6 +181,8 @@ In this task, you create a virtual network peering to enable communications betw | Allow CoreServicesVnet to access the peered virtual network | selected (default) | | Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network | selected | +1. Click **Add**. + 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. @@ -221,7 +223,7 @@ In this task, you want to control network traffic between the perimeter subnet a 1. Search for select the `CoreServicesVnet`. -1. Select **Subnets** and then **+ Create**. Be sure to **Save** your changes. +1. Select **Subnets** and then **+ Subnet**. Be sure to select **Add** to save your changes. | Setting | Value | | --- | --- | @@ -239,9 +241,11 @@ In this task, you want to control network traffic between the perimeter subnet a | Name | `rt-CoreServices` | | Propagate gateway routes | **No** | -1. After the route table deploys, select **Go to resource**. +1. After the route table deploys, Search for and select the **Route Tables**. + +1. Select the resource (not the checkbox) **rt-CoreServices** -1. Select **Routes** and then **+ Add**. Create a route from a future Network Virtual Appliance (NVA) to the CoreServices virtual network. +1. Expand **Settings** then select **Routes** and then **+ Add**. Create a route from a future Network Virtual Appliance (NVA) to the CoreServices virtual network. | Setting | Value | | --- | --- | @@ -251,9 +255,9 @@ In this task, you want to control network traffic between the perimeter subnet a | Next hop type | **Virtual appliance** (notice your other choices) | | Next hop address | `10.0.1.7` (future NVA) | -1. Select **+ Add** when the route is completed. The last thing to do is associate the route with the subnet. +1. Select **+ Add**. The last thing to do is associate the route with the subnet. -1. Select **Subnets** and then **Associate**. Complete the configuration. +1. Select **Subnets** and then **+ Associate**. Complete the configuration. | Setting | Value | | --- | --- |