You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/azure-vmware-solution-platform-updates.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn about the platform updates to Azure VMware Solution.
4
4
ms.topic: reference
5
5
ms.custom: "references_regions, engagement-fy23"
6
6
ms.service: azure-vmware
7
-
ms.date: 4/20/2023
7
+
ms.date: 4/24/2023
8
8
---
9
9
10
10
# 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
21
21
22
22
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.
23
23
24
-
**HCX Enterprise Edition - Default**
24
+
**VMware HCX Enterprise Edition - Default**
25
25
26
26
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).
The data in Azure Log Analytics offer insights into issues by searching using Kusto Query Language.
31
31
@@ -131,7 +131,7 @@ All new Azure VMware Solution private clouds are now deployed with NSX-T Data Ce
131
131
132
132
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.
133
133
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).
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.
4
4
ms.topic: include
5
5
ms.service: azure-vmware
6
-
ms.date: 07/16/2021
6
+
ms.date: 4/22/2023
7
7
author: suzizuber
8
8
ms.author: v-szuber
9
9
---
@@ -12,25 +12,25 @@ ms.author: v-szuber
12
12
13
13
14
14
>[!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.
16
16
17
17
1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **Segments** > **Add**.
18
18
19
19
2. Provide the details for the new logical segment and select **OK**.
20
20
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.":::
22
22
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.
24
24
25
25
-**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.
26
26
27
27
-**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.
28
28
29
29
>[!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.
31
31
>
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.
33
33
>
34
34
>-**Type** - Overlay segment supported by Azure VMware Solution.
35
35
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