ESXi Maintenance Mode stuck at 32%: InsufficientAgentVmsDeployed
search cancel

ESXi Maintenance Mode stuck at 32%: InsufficientAgentVmsDeployed

book

Article ID: 428260

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi host getting stuck at 32% while entering maintenance mode.
  • /var/log/vmware/vpxd/vpxd.log in vCenter server reports the below error stack 
    YYYY-MM-DDTHH:MM:SS.338Z info vpxd[#####] [Originator@6876 sub=cdrsPlmt opID=mkpvo6c1-#####-auto-56hp-h5:########-##] Vm [vim.VirtualMachine:vm-#####,EXAMPLE_VM] failed constraint check false on host [vim.HostSystem:host-##,HOST.EXAMPLE.COM] with <obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:vim25" versionId="8.0.3.0" xsi:type="LocalizedMethodFault"><fault xsi:type="InsufficientAgentVmsDeployed"><hostName>lHOST.EXAMPLE.COM</hostName><requiredNumAgentVms>1</requiredNumAgentVms><currentNumAgentVms>0</currentNumAgentVms></fault><localizedMessage></localizedMessage></obj>

 

Environment

  • VMware vCenter Server
  • VMware vSphere ESXi

Cause

Due to Insufficient Malware Prevention SVM VMs deployed on a cluster.

Resolution

When Malware Prevention SVM is deployed on a cluster, the ESX Agent Manager (EAM) of the vCenter server manages the deployment of one MPS SVM on each host.

  1. Please ensure that the MPS SVM VM is powered on on each ESXi host within the cluster. 

      Note: MPS SVM VMs are typically identified by the naming convention "VMWare_MPS-SVM".

     2. If the MPS SVM VMs is powered off, power it on.

     3. Retry task.