Skip to main content
NetApp Knowledge Base

Cluster Ports Degraded after NX3232C upgrade

Views:
240
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • Cisco NX3232 cluster switch
  • NX-OS 9.3(7)
  • RCF 1.6

Issue

During upgrade of Cluster Interconnect switches to NX3232, multiple connectivity issues seen including the following errors:


Sat Mar 05 08:30:33 -0800 [node1: nphmd: hm.alert.raised:alert]: Alert Id = NodeIfInErrorsWarnAlert , Alerting Resource = node1/e3b raised by monitor controller
Sat Mar 05 08:35:33 -0800 [node1: nphmd: hm.alert.cleared:notice]: Alert Id = NodeIfInErrorsWarnAlert , Alerting Resource = node1/e3b cleared by monitor controller
 
 
vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif .. <many-to-many/all-to-all>
vifmgr.cluscheck.droppedlarge:alert]: Partial packet loss when pinging from cluster lif .. <many-to-many/all-to-all>
callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss
vifmgr.cluscheck.hwerrors:alert]: Port e3b on node node2 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors

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.