Skip to main content
NetApp Knowledge Base

Cluster network port does not return home after upgrading one C3132Q switch

  1. Last updated
  2. Save as PDF
Views:
668
Visibility:
Public
Votes:
2
Category:
fabric-interconnect-and-management-switches
Specialty:
hw
Last Updated:

Applies to

  • Cisco N3K-C3132Q-V Cluster Network Switches (CNS) / Nexus 3132Q-V / NX3132V
  • Cisco Nexus Operating System (NX-OS)  upgrade along with Reference Config File (RCF) update to Cluster-HA-Breakout RCF v1.8 or later
  • Two cluster LIFs/ports per node cabling with two cluster switches

Issue

  • One cluster network port does not return home after upgrading one CNS
  • Total packet loss when pinging from cluster lif
    vifmgr: vifmgr.cluscheck.droppedall:alert]: Total packet loss when pinging from cluster lif Node1_clus1 (node Node1) to cluster lif Node2clus2 (node Node2).
  • Followed by VIFMgr errors
    vifmgr: vifmgr.dbase.checkerror:alert]: VIFMgr experienced an error verifying cluster database consistency. Some LIFs might not be hosted properly as a result.
    vifmgr: vifmgr.startup.failover.err:alert]: VIFMgr encountered errors during startup.
  • When just one cluster network port in one node is online, multiple rings in that node are offline (vifmgr, vldb and mgwd) with CLUSTER NETWORK DEGRADED errors.
  • No more errors when that port is manually offlined and the cluster LIF changes the home port. 
  • Cable re-seat/replace/swap doesn't fix the issue.
  • Controller port is properly detected on the switch side.
  • All cluster network pings fail between LIFs on both switches but work for LIFs connected to the same switch.

 

 

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.