tone correction

jobingeorge-microsoft · jobingeorge-microsoft · commit 613f6c1f16d5 · 2025-03-28T18:29:43.000+05:30
diff --git a/articles/azure-vmware/azure-vmware-solution-host-remediation.md b/articles/azure-vmware/azure-vmware-solution-host-remediation.md
@@ -6,7 +6,7 @@ ms.service: azure-vmware
 ms.date: 03/25/2025
 ---
 
-# Azure VMware Solution SDDC maintenance best practices
+# Azure VMware Solution Sofware-Defined Data Center (SDDC) maintenance best practices
 
 ## Host maintenance and lifecycle management
 
@@ -21,21 +21,21 @@ Host remediation involves replacing the faulty node with a new healthy node in t
 > [!TIP]
 > **Customer communication:** An email is sent to the customer's email address before the replacement is initiated and again after the replacement is successful. 
 > 
-> To receive emails related to host replacement, you need to be added to any of the following Azure RBAC roles in the subscription: 'ServiceAdmin', 'CoAdmin', 'Owner', 'Contributor'.
+> To receive emails related to host replacement, you need to be added to any of the following Azure Role-Based Access Control (RBAC) roles in the subscription: 'ServiceAdmin', 'CoAdmin', 'Owner', 'Contributor'.
 
 ## Maintenance Operations Best Practices
-AVS undertakes periodic maintenance of the private cloud and this includes security patches, minor & major updates to VMware software stack.
+Azure VMware Solution undertakes periodic maintenance of the private cloud and this includes security patches, minor & major updates to VMware software stack.
 
 The following actions are always recommended for ensuring host maintenance operations are carried out successfully:
 1.	**vSAN storage utilization:** To maintain Service Level Agreement (SLA), ensure that your vSphere cluster's storage space utilization remains below 75%. If the utilization exceeds 75%, upgrades may take longer than expected or fail entirely. If your storage utilization exceeds 75%, consider adding a node to expand the cluster and prevent potential downtime during upgrades.
 2.	**Distributed Resource Scheduler (DRS) rules:** DRS VM-VM anti-affinity rules must be configured in a way to have at least (N+1) hosts in the cluster, where N is the number of VMs part of DRS rule.
 3.	**Failures To Tolerate (FTT) violation:** To prevent data loss, change VMs configured with a vSAN storage policy for Failures to Tolerate (FTT) of 0 to a vSAN storage policy compliant with [Microsoft SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) (FTT=1 for up to 5 hosts in a cluster and FTT=2 for 6 or more hosts in a cluster) and ensure host maintenance operations can carried out seamlessly.
-4.	**Remove VM CD-ROM mounts:** VMs mounted with “Emulate mode” CD-ROMs will block host maintenance. Ensure CD-ROMs are mounted in “Passthrough mode”.
-5.	**Serial/parallel port or external device:** If you are using an image file (ISO, FLP, etc), ensure that it is accessible from all ESXi hosts in the cluster. Store the files on a datastore that are shared between all ESXi Servers that will participate in the vMotion of the virtual machine. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) for more information.
-6.	**Orphaned VMs:** In the case of an orphaned virtual machine, the VM needs to be either re-registered if possible (if it has not been deleted) or removed from inventory. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information.
+4.	**Remove VM CD-ROM mounts:** VMs mounted with “Emulate mode” CD-ROMs block host maintenance. Ensure CD-ROMs are mounted in “Passthrough mode”.
+5.	**Serial/parallel port or external device:** If you are using an image file (ISO, FLP, etc), ensure that it is accessible from all ESXi hosts in the cluster. Store the files on a datastore that are shared between all ESXi Servers that participate in the vMotion of the virtual machine. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) for more information.
+6.	**Orphaned VMs:** In the case of an orphaned virtual machine, the Virtual Machine (VM) needs to be either re-registered if possible (if it hasn't been deleted) or removed from inventory. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information.
 7.	**SCSI shared controller:** When using SCSI bus sharing use with bus type as “Physical” for VMs. VMs connected to Virtual SCSCI controllers will be powered-off. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article?legacyId=2147661) for more information.
 8.	**Third-party VMs & applications:** For third-party VMs & applications:
-    1. Ensure that third-party solutions deployed on AVS are compliant and do not interfere with maintenance operations.   
+    1. Ensure that third-party solutions deployed on AVS are compliant and don't interfere with maintenance operations.   
     2. Ensure that the VM isn’t installed with a VM-Host “Must run” DRS rule. Additionally, verify that these applications are compatible with upcoming versions of the VMware stack.
     3. Consult with your solution vendor and update in advance if necessary to maintain compatibility post-upgrade.
 
@@ -59,18 +59,18 @@ Azure VMware Solution monitors the following conditions on the host:
 ## Alert Codes and Remediation Table
 |  Error Code         |        Error Details              |  Recommended Action     |
 |--------------------|---------------------------------|---------------------|
-|  EPC_CDROM_EMULATEMODE |  This error is encountered when CD-ROM on the Virtual Machine uses emulate mode, whose ISO image is not accessible  | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79306) for the removal of any CDROM mounted on customer's workload Virtual Machines in emulate mode or detach ISO. It is recommended to use "Passthrough mode" for mounting any CD-ROM. |
-| EPC_DRSOVERRIDERULE | This error is encountered when there is a Virtual Machine with DRS Override set to “Disabled” mode. | VM should not block vMotion while putting host into maintenance. Set Partially Automated DRS rules for the VM. Refer to [this document](/azure/azure-vmware/create-placement-policy#enable-restrict-vm-movement-for-specific-vms) to know more about VM placement policies. |
+|  EPC_CDROM_EMULATEMODE |  This error is encountered when CD-ROM on the Virtual Machine uses emulate mode, whose ISO image isn't accessible  | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79306) for the removal of any CDROM mounted on customer's workload Virtual Machines in emulate mode or detach ISO. It is recommended to use "Passthrough mode" for mounting any CD-ROM. |
+| EPC_DRSOVERRIDERULE | This error is encountered when there's a Virtual Machine with DRS Override set to “Disabled” mode. | VM shouldn't block vMotion while putting host into maintenance. Set Partially Automated DRS rules for the VM. Refer to [this document](/azure/azure-vmware/create-placement-policy#enable-restrict-vm-movement-for-specific-vms) to know more about VM placement policies. |
 |  EPC_SCSIDEVICE_SHARINGMODE  | This error is encountered when a Virtual Machine is configured to use a device that prevents a maintenance operation: A device that is a SCSI controller which is engaged in bus-sharing   | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79910) for the removal of any SCSI controller engaged in bus-sharing attached to VMs   |
 |  EPC_DATASTORE_INACCESSIBLE  |  This error is encountered when any external Datastore attached to AVS Private Cloud becomes inaccessible  | Follow [this article](/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts?tabs=azure-portal#performance-best-practices) for the removal of any stale Datastore attached to cluster  |
 |  EPC_NWADAPTER_STALE | This error is encountered when connected Network interface on the Virtual Machine uses network adapter which becomes inaccessible | Follow [this KB article](https://knowledge.broadcom.com/external/article/318738/troubleshooting-the-migration-compatibil.html) for the removal of any stale N/W adapters attached to Virtual Machines   |
-| EPC_SERIAL_PORT | This error is encountered when a Virtual Machine’s serial port is connected to a device that cannot be accessed on the destination host. | If you are using an image file (ISO, FLP, and so on), ensure that it is accessible from all ESXi servers on the cluster. Store the files on a data store that is shared between all ESXi servers that will participate in vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
-| EPC_HARDWARE_DEVICE | This error is encountered when a Virtual Machine’s parallel Port/USB Device is connected to a device cannot be accessed on the destination host. | If you are using an image file (ISO, FLP, and so on), ensure that it is accessible from all ESXi servers of the cluster. Store the files on a data store that is shared between all ESXi servers that will participate in the vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
-| EPC_INVALIDVM / EPC_ORPHANVM | This error is encountered when there is an orphaned or Invalid VM in the inventory | Ensure all your Virtual Machines are accessible to the vCenter. Refer to [this KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information |
+| EPC_SERIAL_PORT | This error is encountered when a Virtual Machine’s serial port is connected to a device that can't be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers on the cluster. Store the files on a data store that is shared between all ESXi servers that will participate in vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
+| EPC_HARDWARE_DEVICE | This error is encountered when a Virtual Machine’s parallel Port/USB Device is connected to a device cannot be accessed on the destination host. | If you're using an image file (ISO, FLP, and so on), ensure that it's accessible from all ESXi servers of the cluster. Store the files on a data store that is shared between all ESXi servers that will participate in the vMotion of the virtual machine. Refer to [this KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) from Broadcom for more information. |
+| EPC_INVALIDVM / EPC_ORPHANVM | This error is encountered when there's an orphaned or Invalid VM in the inventory | Ensure all your Virtual Machines are accessible to the vCenter. Refer to [this KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information |
 
 
 > [!NOTE]
-> Azure VMware Solution tenant admins must not edit or delete the previously defined VMware vCenter Server alarms because they are 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.
+> 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.
 
 
 
