Skip to content

Commit 1088433

Browse files
authored
Merge pull request #235611 from rvandenbedem/patch-1
Update create-nsxt-segment-azure-portal-steps.md
2 parents 1abbd3d + 51268c7 commit 1088433

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

articles/azure-vmware/azure-vmware-solution-platform-updates.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about the platform updates to Azure VMware Solution.
44
ms.topic: reference
55
ms.custom: "references_regions, engagement-fy23"
66
ms.service: azure-vmware
7-
ms.date: 4/20/2023
7+
ms.date: 4/24/2023
88
---
99

1010
# What's new in Azure VMware Solution
@@ -21,11 +21,11 @@ Introducing Run Commands for VMware HCX on Azure VMware Solution. You can use th
2121

2222
All new Azure VMware Solution private clouds are being deployed with VMware NSX-T Data Center version 3.2.2. NSX-T Data Center versions in existing private clouds will be upgraded to NSX-T Data Center version 3.2.2 through April 2023.
2323

24-
**HCX Enterprise Edition - Default**
24+
**VMware HCX Enterprise Edition - Default**
2525

2626
VMware HCX Enterprise is now available and supported on Azure VMware Solution at no extra cost. VMware HCX Enterprise brings valuable [services](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html), like Replicated Assisted vMotion (RAV) and Mobility Optimized Networking (MON). VMware HCX Enterprise is now automatically installed for all new VMware HCX add-on requests, and existing VMware HCX Advanced customers can upgrade to VMware HCX Enterprise using the Azure portal. Learn more on how to [Install and activate VMware HCX in Azure VMware Solution](install-vmware-hcx.md).
2727

28-
**Log analytics - monitor Azure VMware Solution**
28+
**Azure Log analytics - monitor Azure VMware Solution**
2929

3030
The data in Azure Log Analytics offer insights into issues by searching using Kusto Query Language.
3131

@@ -131,7 +131,7 @@ All new Azure VMware Solution private clouds are now deployed with NSX-T Data Ce
131131

132132
You'll receive an email with the planned maintenance date and time. You can reschedule an upgrade. The email also provides details on the upgraded component, its effect on workloads, private cloud access, and other Azure services.
133133

134-
For more information on this NSX-T Data Center version, see [VMware NSX-T Data Center [!INCLUDE [nsxt-version](includes/nsxt-version.md)] Release Notes](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/rn/VMware-NSX-T-Data-Center-312-Release-Notes.html).
134+
For more information on this NSX-T Data Center version, see [VMware NSX-T Data Center 3.1.1 Release Notes](https://docs.vmware.com/en/VMware-NSX/3.1/rn/VMware-NSX-T-Data-Center-311-Release-Notes.html).
135135

136136
## May 2021
137137

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: Add an NSX-T network segment using Azure VMware Solution
3-
description: Steps to add an NSX-T network segment for Azure VMware Solution in the Azure portal.
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.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 07/16/2021
6+
ms.date: 4/22/2023
77
author: suzizuber
88
ms.author: v-szuber
99
---
@@ -12,25 +12,25 @@ ms.author: v-szuber
1212

1313

1414
>[!NOTE]
15-
>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 network segment.
15+
>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.
1616
1717
1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **Segments** > **Add**.
1818

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

21-
:::image type="content" source="../media/networking/add-new-nsxt-segment.png" alt-text="Screenshot showing how to add a new NSX-T segment in the Azure portal.":::
21+
:::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.":::
2222

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

2525
- **Subnet gateway** - Gateway IP address for the segment's subnet with a subnet mask. VMs are attached to a logical segment, and all VMs connecting to this segment belong to the same subnet. Also, all VMs attached to this logical segment must carry an IP address from the same segment.
2626

2727
- **DHCP** (optional) - DHCP ranges for a logical segment. You must configure a [DHCP server or DHCP relay](../configure-dhcp-azure-vmware-solution.md) to consume DHCP on Segments.
2828

2929
>[!NOTE]
30-
>The **Connected gateway** is selected by default and is read-only. It shows Tier-1 gateway and type of segment information.
30+
>The **Connected gateway** is selected by default and is read-only. It shows Tier-1 Gateway and type of segment information.
3131
>
32-
>- **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.
32+
>- **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.
3333
>
3434
>- **Type** - Overlay segment supported by Azure VMware Solution.
3535
36-
The segment is now visible in Azure VMware Solution, NSX-T Manger, and vCenter.
36+
The segment is now visible in Azure VMware Solution, NSX-T Manager, and vCenter Server.

0 commit comments

Comments
 (0)