Skip to main content
NetApp Knowledge Base

ONTAP Select NVRAM log not synchronized for one node

  1. Last updated
  2. Save as PDF
Views:
586
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • ONTAP Select HA
  • Cyclic Redundancy Check (CRC)

Issue

  • ONTAP Select NVRAM log is not synchronized for one node

cluster::> storage failover show

                                Takeover
Node            Partner         Possible  State    Description
--------------  --------------  --------  -------------------------------------
cluster-01      cluster-02      false     Connected to cluster-02, Takeover is not possible: NVRAM log not synchronized
cluster-02      cluster-01      true      Connected to cluster-01
2 entries were displayed.

  • Cluster network degraded events with appear within EMS log:

[cluster-01: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between cluster-01_clus1 ( 169.254.x.x ) on cluster-01 and cluster-02_clus1 ( 169.254.x.x ) on cluster-02

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.