\uD83E\uDD14 Problem
VM start protection fails with timed out error
\uD83C\uDF31 Solution
The above error can happen if there is communication issue between DRVA and ESXi CIM daemon.
Verify if you see any CIM related error in protected domains tab and from MSA logs.
MSA logs - /var/log/vme2/logs/jss-cimclient.log
2022-03-31 06:19:43,226 ERROR [Thread-10] (CimClient.java:642) getHostRequestInfo: CIM remote method call failure: 10.40.3.104 javax.wbem.WBEMException: Unable to connect at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.transmitRequestWorker(WBEMClientCIMXML.java:1756) at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.transmitRequest(WBEMClientCIMXML.java:1687) at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.enumerateInstances(WBEMClientCIMXML.java:1004) at com.jetstream.jss.platform.client.cim.CimClient.cimEnumerateInstances(CimClient.java:468) at com.jetstream.jss.platform.client.cim.CimClient.cimEnumerateInstances(CimClient.java:447) at com.jetstream.jss.platform.client.cim.CimClient.getHostRequestInfo(CimClient.java:601) at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.collectHostRequestsAndUpdateCache(HostServiceRequestCollectionTask.java:150) at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.fetchHostServiceRequests(HostServiceRequestCollectionTask.java:109) at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.processNextStep(HostServiceRequestCollectionTask.java:68) at com.jetstream.jss.task.Executor$TransientTaskRunnable.run(Executor.java:419) Caused by: java.net.ConnectException: Connection refused (Connection refused)
We can see there is communication failure which needs to be corrected by restarting CIM services on ESXi hosts.
Restart CIM service from all ESXi hosts in cluster.
Start VM protection again.
ESXi 6.7 has CIM related issues and most of these are not seen in ESXi 7.0 & later.
\uD83D\uDCCE Related articles
Filter by label
There are no items with the selected labels at this time.