Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

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

Views:
144
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

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

Issue

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.

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support