Skip to content

Commit a9c96e8

Browse files
authored
Update vmware-software-update-frequency.md
Fixed grammar.
1 parent d9c10e4 commit a9c96e8

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/azure-vmware/includes/vmware-software-update-frequency.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: VMware software update frequency
33
description: Supported VMware software update frequency for Azure VMware Solution.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 12/12/2022
6+
ms.date: 2/7/2023
77
author: suzizuber
88
ms.author: v-szuber
99
---
@@ -15,13 +15,13 @@ One benefit of Azure VMware Solution private clouds is that the platform is main
1515
> [!NOTE]
1616
> A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud and should be avoided.
1717
18-
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center is different.
18+
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center has the following considerations:
1919

2020
- **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter Server and NSX-T Data Center isn't blocked during this time. It's recommended that, during this time, you don't plan any other activities like: scaling up private cloud, scheduling or initiating active HCX migrations, making HCX configuration changes, and so on, in your private cloud.
2121

2222
- **vCenter Server** - There's no impact to workloads running in your private cloud. During this time, vCenter Server will be unavailable and you won't be able to manage VMs (stop, start, create, or delete). It's recommended that, during this time, you don't plan any other activities like scaling up private cloud, creating new networks, and so on, in your private cloud. If you're using VMware Site Recovery Manager or vSphere Replication user interfaces, it's recommended to not configure vSphere Replication, and configure or execute site recovery plans during the vCenter Server upgrade.
2323

24-
- **NSX-T Data Center** - There's workload impact and when a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to maximum 1 minute with any of the following symptoms:
24+
- **NSX-T Data Center** - There's workload impact and when a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to 1 minute with any of the following symptoms:
2525

2626
- Ping errors
2727

@@ -35,7 +35,6 @@ Microsoft is responsible for applying any patches, updates, or upgrades to ESXi,
3535

3636
You'll be notified through Azure Service Health that includes the timeline of the upgrade. This notification also provides details on the upgraded component, its effect on workloads, private cloud access, and other Azure services. You can reschedule an upgrade as needed.
3737

38-
3938
Software updates include:
4039

4140
- **Patches** - Security patches or bug fixes released by VMware
@@ -45,6 +44,6 @@ Software updates include:
4544
- **Upgrades** - Major version change of a VMware stack component
4645

4746
>[!NOTE]
48-
>Microsoft tests a critical security patch as soon as it becomes available from VMware.
47+
> Microsoft tests a critical security patch as soon as it becomes available from VMware.
4948
5049
Documented VMware workarounds are implemented in lieu of installing a corresponding patch until the next scheduled updates are deployed.

0 commit comments

Comments
 (0)