Subscribe
Accepted Solution

Cannot deploy ontap select

I am currently installing ONTAP Select Version: 2.1 VM Version: 2.1  on VMware ESXi, 6.0.0, 3073146

 

When the cluster is created I get the following error

ClusterCreateFailed :  NodeStartErr: Node ontapcluster-1 failed to start: (Cannot 'start' VM ontapcluster-1: NoCompatibleHost).

 

 

 

 

Can anyone advise what the issue is?

Re: Cannot deploy ontap select

Hi,

 

Can you let us know which version of ONTAP Select you are trying to install

 

 

Thanks

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Cannot deploy ontap select

Here's the info for the data node that the ontap deploy utility created :

 

Product: Data ONTAP-v

Version : 2.0.0 (9,0P1)

 

I assume that based on the versioning it is 9.0P1.  The one node cluster is created successfuly but when the data VM tries to power up I get the original error message and I get  two cryptic messages in Vmware. 

"Failed to find a host for powering on the virtual machine. The following faults explain why the registered host is not compatible."

"The operation is not allowed in the current state of the host."

 

Thanks for your assistance.

Re: Cannot deploy ontap select

[ Edited ]

@

 
Thanks for the detailed error.
 

 

"The operation is not allowed in the current state of the host."

 

Here is the KB which mentions the same error and resolution

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2069496

 

Please try this

To work around this issue, disconnect and reconnect the ESXi host that is running the virtual machine to force vCenter Server to retrieve an updated set of data relating to the objects registered to the host.

 

google search showed me this link too.

https://www.vmadmin.co.uk/resources/36-virtualcenter/362-the-operation-is-not-allowed-in-the-current-connection-state-of-the-host-vcenter-5-5

 

is the VC 5.5?

 

regards

SR

Re: Cannot deploy ontap select

Thanks for the reply.  That was indeed the issue.