Skip to main content
NetApp Knowledge Base

Switches (re)configuration after MCCIP configuration is applied might result in lack of communication between the nodes

Last Updated:

Applies to

  • MetroCluster IP
  • Broadcom BES-53248 Switches
  • Initial install


As per installation documentation the switches have to be set to factory default, updated, and configured (RCFs applied) followed by switch reboot before the MetroCluster IP configuration is started. 

If for any reason the switches are to be configured after the MetroCluster IP configuration is completed this might result in a lack of NV Memory communication. The following symptoms are to be observed:

  • Storage failover interconnect error
  • NVRAM log not synchronized
  • Disk inventory not exchanged
  • Messages like: nvmm.mirror.abortingcf.takeover.disabled etc.


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.