Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/VM_creation_fails_with_NodeCreateFailed
      2021-10-12 08:12:50,237|DEBUG| 1418|85207|rest.py|173|response body: {"code":13,"details":"<vmname> invalid - no vm named 'cluster01-01' on host 'xxx.xxx.xxx.xxx'","type":"InvalidArg"} 2021-10-12 08:1...2021-10-12 08:12:50,237|DEBUG| 1418|85207|rest.py|173|response body: {"code":13,"details":"<vmname> invalid - no vm named 'cluster01-01' on host 'xxx.xxx.xxx.xxx'","type":"InvalidArg"} 2021-10-12 08:12:50,243|ERROR| 1418|85207|logger.py|132|client_api_helper.py|184:vm_get| Unable to locate VM "cluster01-01" on host "xxx.xxx.xxx.xxx". Reason: <vmname> invalid - no vm named 'cluster01-01' on host 'xxx.xxx.xxx.xxx'
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Migration_of_vVol-based_VM_between_ESX_hosts_using_DRS_fails_and_VM_becomes_orphaned
      Applies to NetApp SolidFire NetApp Element software Hyperconverged infrastructure (HCI) with Virtual Volumes (vVols) Issue Migration/vMotion of vVol-based VM between ESX hosts using Distributed Resour...Applies to NetApp SolidFire NetApp Element software Hyperconverged infrastructure (HCI) with Virtual Volumes (vVols) Issue Migration/vMotion of vVol-based VM between ESX hosts using Distributed Resource Scheduler (DRS) fails VM gets orphaned
    • https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_Deploy_-_ONTAP_cluster_create_failed_during_cluster_join_operation
      Applies to ONTAP Select Deploy (Deploy) ONTAP Select (OTS) Running connectivity checker in Deploy fails due to cluster join error message. ONTAPClusterCreateJoinOperationFailed: ONTAP cluster create f...Applies to ONTAP Select Deploy (Deploy) ONTAP Select (OTS) Running connectivity checker in Deploy fails due to cluster join error message. ONTAPClusterCreateJoinOperationFailed: ONTAP cluster create failed during cluster join operation on cluster "mySelectCluster". Reason: Failed to start cluster join on node: 169.254.10.200: Setup failed between nodes node1 and node2 with :Could not retrieve partner SFO information: entry doesn't exist. Resolve the issue, then try the command again.