Skip to content

Commit ad6ece0

Browse files
Refine alert codes and remediation details
Updated error messages and recommendations in the Alert Codes and Remediation Table for clarity and consistency.
1 parent 13da99c commit ad6ece0

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,16 +61,16 @@ The following actions are always recommended for ensuring host maintenance opera
6161
## Alert Codes and Remediation Table
6262
| Error Code | Error Details | Recommended Action |
6363
|--------------------|---------------------------------|---------------------|
64-
| 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's recommended to use "Passthrough mode" for mounting any CD-ROM. |
64+
| 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's recommended to use "Passthrough mode" for mounting any CD-ROM. |
6565
| 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. |
66-
| 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. |
67-
| 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 |
68-
| 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. |
66+
| EPC_SCSIDEVICE_SHARINGMODE | This error is encountered when a Virtual Machine is configured to use SCSI controller with bus-sharing in "virtual" mode. | Follow [this KB article](https://knowledge.broadcom.com/external/article?legacyId=79910) for the removal of any SCSI controller engaged in bus-sharing in virtual mode is attached to VMs. |
67+
| 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 |
68+
| 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. |
6969
| 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 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. |
7070
| 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. |
71-
| 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. |
71+
| EPC_INVALIDVM / EPC_ORPHANVM | This error is encountered when there's an orphaned or Invalid VM is present 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. |
7272
| 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. |
73-
| 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. |
73+
| 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. |
7474
| 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. |
7575
| 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. |
7676
| 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. |

0 commit comments

Comments
 (0)