Merge pull request #313130 from riperez123/main

Add recommendation for vCenter scale configuration

Author: prmerger-automator[bot]

articles/azure-vmware/azure-vmware-solution-private-cloud-maintenance.md

@@ -74,6 +74,7 @@ The following actions are necessary for ensuring host maintenance operations are
 | EPC_FTTVIOLATION | This error is encountered when a cluster does not have the minimum number of hosts that the storage policy needs. | Add hosts as needed by the storage policy or change the VM FTT policy to support putting the host into maintenance mode. Refer to [this KB article](https://knowledge.broadcom.com/external/article/326857/vsan-host-fails-to-enter-maintenance-mod.html) to know more about FTT policy. |
 | ERECOMMENDATION_CLUSTER_SIZE | This recommendation indicates a cluster in the private cloud has 14 or more hosts. AVS supports a maximum of 16 hosts in a cluster. | Create a new cluster for new any new hosts that may be required. |
 | ERECOMMENDATION_PRIVATECLOUD_SIZE | This recommendation indicates a private cloud has 90 or more hosts. AVS supports a maximum of 96 hosts in a private cloud. | Consider creating a new private cloud for any new hosts and distribute hosts across the private clouds as necessary. |
+| ERECOMMENDATION_VCENTER_SCALE | This recommendation identifies that the vCenter virtual machine is provisioned with fewer CPU cores or less memory than recommended for the current virtual machine count within the private cloud. | Open up a support request to have the vCenter memory and CPU increased. |
 
 > [!NOTE]
 > Azure VMware Solution tenant admins must not edit or delete the previously defined VMware vCenter Server alarms because they're managed by the Azure VMware Solution control plane on vCenter Server. These alarms are used by Azure VMware Solution monitoring to trigger the Azure VMware Solution host remediation process.