Skip to main content
NetApp Knowledge Base

Node Becomes Standalone After Boot Device Replacement in ONTAP

  1. Last updated
  2. Save as PDF
Views:
5
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ASA-A150
  • ONTAP 9

Issue

  • After replacing the boot device on node 2, the node does not rejoin the existing cluster and instead becomes a standalone node.
  • Attempts to restore the node configuration and rejoin the cluster fail.
  •  System checks error: joining a node that is not an ALL SAN array to an all san array cluster is not supported
  • Attempts to restore the var file system using system node restore-backup fail.   
  • Cluster configuration backup does not contain the correct information for node02.

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.