Skip to content

Commit 2a701fb

Browse files
authored
Update create-nsxt-segment-azure-portal-steps.md
1 parent 1ebe530 commit 2a701fb

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: Add an NSX-T Data Center network segment using Azure VMware Solution
3-
description: Steps to add an NSX-T Data Center network segment for Azure VMware Solution in the Azure portal.
2+
title: Add an NSX network segment using Azure VMware Solution
3+
description: Steps to add an NSX network segment for Azure VMware Solution in the Azure portal.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 1/03/2024
6+
ms.date: 6/12/2024
77
author: suzizuber
88
ms.author: v-szuber
99
ms.custom: engagement-fy23
@@ -13,13 +13,13 @@ ms.custom: engagement-fy23
1313

1414

1515
>[!NOTE]
16-
>If you plan to use DHCP, you'll need to [configure a DHCP server or DHCP relay](../configure-dhcp-azure-vmware-solution.md) before you can configure an NSX-T Data Center network segment.
16+
>If you plan to use DHCP, you'll need to [configure a DHCP server or DHCP relay](../configure-dhcp-azure-vmware-solution.md) before you can configure an NSX network segment.
1717
1818
1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **Segments** > **Add**.
1919

2020
2. Provide the details for the new logical segment and select **OK**.
2121

22-
:::image type="content" source="../media/networking/add-new-nsxt-segment.png" alt-text="Screenshot showing how to add a new NSX-T Data Center segment in the Azure portal.":::
22+
:::image type="content" source="../media/networking/add-new-nsxt-segment.png" alt-text="Screenshot showing how to add a new NSX segment in the Azure portal.":::
2323

2424
- **Segment name** - Name of the segment that is visible in vCenter Server.
2525

@@ -30,8 +30,8 @@ ms.custom: engagement-fy23
3030
>[!NOTE]
3131
>The **Connected gateway** is selected by default and is read-only. It shows Tier-1 Gateway and type of segment information.
3232
>
33-
>- **T1** - Name of the Tier-1 Gateway in NSX-T Manager. A private cloud comes with an NSX-T Tier-0 Gateway in Active/Active mode and a default NSX-T Tier-1 Gateway in Active/Standby mode. Segments created through the Azure VMware Solution console only connect to the default Tier-1 Gateway, and the workloads of these segments get East-West and North-South connectivity. You can only create more Tier-1 Gateways through NSX-T Manager. Tier-1 Gateways created from the NSX-T Manager console are not visible in the Azure VMware Solution console.
33+
>- **T1** - Name of the Tier-1 Gateway in NSX Manager. A private cloud comes with an NSX Tier-0 Gateway in Active/Active mode and a default NSX Tier-1 Gateway in Active/Standby mode. Segments created through the Azure VMware Solution console only connect to the default Tier-1 Gateway, and the workloads of these segments get East-West and North-South connectivity. You can only create more Tier-1 Gateways through NSX Manager. Tier-1 Gateways created from the NSX Manager console are not visible in the Azure VMware Solution console.
3434
>
3535
>- **Type** - Overlay segment supported by Azure VMware Solution.
3636
37-
The segment is now visible in Azure VMware Solution, NSX-T Manager, and vCenter Server.
37+
The segment is now visible in Azure VMware Solution, NSX Manager, and vCenter Server.

0 commit comments

Comments
 (0)