Skip to main content
NetApp Knowledge Base

Failed hardware upgrade leads to multiple stale cluster table entries

  1. Last updated
  2. Save as PDF
Views:
173
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • Hardware upgrade (head upgrade)

Issue

After any problems when executing procedures that introduce new nodes, like:
  • problematic hardware upgrade
  • failed or partial node-join attempts with subsequent fore removal
  • human mistakes like re-joining a wiped node that was never unjoined from the cluster before but only halted

there may be stale entries left behind in various cluster configuration tables.

Such stale table entries referring orphaned nodes can block different operations like metrocluster configure or node rename with errors similar to
entry not found or duplicate entry or Invalid DR group ID, or others:

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.