Skip to content

Commit b4909a5

Browse files
Adding error & recommended action for maintenance
1 parent f84ebfd commit b4909a5

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,8 @@ The following actions are always recommended for ensuring host maintenance opera
6868
| EPC_HARDWARE_DEVICE | This error is encountered when a Virtual Machine’s parallel Port/USB Device is connected to a device 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 of the cluster. Store the files on a data store that is shared between all ESXi servers that 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. |
6969
| 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. |
7070
| EPC_VMHOSTDRSRULE | This error is encountered when there's a Virtual Machine with Host affinity/anti-affinity DRS rule. | VM shouldn't block VMware vMotion while putting a host into maintenance mode. Set "should rules" for VM-Host affinity. Refer to [this document](/azure/azure-vmware/create-placement-policy#what-is-the-difference-between-the-vm-host-affinity-policy-and-restrict-vm-movement) for more information. |
71-
| EPC_FTTVIOLATION | This error is encountered when a virtual machine has "Failures to Tolerate" as 0 or "No data redundancy" | Follow [this KB article](https://knowledge.broadcom.com/external/article/391522/the-esxi-host-takes-very-long-time-enter.html) to configure FTT as 1 or 2 for the Virtual Machine. |
71+
| EPC_FTT_ZERO | This error is encountered when a virtual machine has "Failures to Tolerate" as 0 or "No data redundancy" | Follow [this KB article](https://knowledge.broadcom.com/external/article/391522/the-esxi-host-takes-very-long-time-enter.html) to configure FTT as 1 or 2 for the Virtual Machine. |
72+
| 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. |
7273

7374
> [!NOTE]
7475
> 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.

0 commit comments

Comments
 (0)