Skip to content

Commit c4e2c45

Browse files
authored
Merge pull request #92939 from AnejaAmit/patch-7
Update vmware-software-update-frequency.md
2 parents e40fdeb + 2ca568f commit c4e2c45

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ One benefit of Azure VMware Solution private clouds is the platform is maintaine
1414

1515
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter, vSAN, and NSX-T in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter, and NSX-T is different.
1616

17-
- **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter and NSX-T 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, and so on, in your private cloud.
17+
- **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter and NSX-T 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.
1818

19-
- **vCenter** - There's no impact to workloads running in your private cloud. During this time, vCenter 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.
19+
- **vCenter** - There's no impact to workloads running in your private cloud. During this time, vCenter 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 are using SRM or vSphere replication user interfaces, it is recommended to not configure vSphere replications and configure or execute site recovery plans during the vCenter upgrade.
2020

2121
- **NSX-T** - 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 and all of the following symptoms:
2222

0 commit comments

Comments
 (0)