Skip to main content
NetApp Knowledge Base

MetroCluster IP node does not boot after running set-defaults

  1. Last updated
  2. Save as PDF
Views:
611
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9
  • set-defaults run on a configured system
  • Motherboard replacement

Issue

After running set-defaults on a node that is already configured as part of a MetroCluster IP solution, the node fails to boot with the following messages reported during the boot attempt:

Attempting to use existing varfs on /dev/nvrd1
                                           <<<< Missing configuration for the MetroCluster IP interfaces
iw_cxgbe: Chelsio T5/T6 RDMA driver loaded.

Jun 30 08:07:51 [ClusterA-01:config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.

Waiting for requisite number of local mailboxes... (Press Ctrl-C to abort wait)

 

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.