Skip to main content
NetApp Knowledge Base

ONTAP Select VM Not Recognized After Unsupported Clone

  1. Last updated
  2. Save as PDF
Views:
10
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • NetApp ONTAP Select (OTS)
  • VMware vSphere environments
  • Cloned Virtual Machine (VM)

Issue

After performing an unsupported cold clone of an ONTAP Select (OTS) VM node (for snapshot consolidation), the following issues were observed:
  • The cloned VM runs and ONTAP System Manager may show the cluster as healthy initially. 
  • ONTAP Deploy cannot discover or manage the cloned VM node.
  • Cluster refresh in Deploy shows node state changes such as "powered_on" to "powered_off".
  • Deploy continues referencing the original VM name even after it is renamed or powered off.  

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.