Skip to main content
NetApp Knowledge Base

Cisco Nexus C3132Q ALERT vifmgr.cluscheck.ctdpktloss after fw. upgrade

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

Applies to

  • Cisco Nexus C3132Q-V
  • RCF version 1.1
  • NX-OS version 7.0(3)I7(8)

Issue

  • NX-OS updated to 7.0(3)I7(8)
  • All the nodes in the cluster have ping issues. Example:
 
Sun Feb 28 18:08:32 +0100 [node_name_1: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_1_clus1 ( 169.254.59.251 ) on node_name_1_clus1 and node_name_6_clus2 ( 169.254.20.249 ) on node_name_6
Sun Feb 28 17:27:38 +0100 [node_name_2: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_2_clus1 ( 169.254.78.72 ) on node_name_2_clus1 and node_name_6_clus2 ( 169.254.20.249 ) on node_name_6
Sun Feb 28 18:31:29 +0100 [node_name_3: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_3_clus1 ( 169.254.159.111 ) on node_name_3_clus1 and node_name_6_clus2 ( 169.254.20.249 ) on node_name_6
Sun Feb 28 18:27:32 +0100 [node_name_4: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_4_clus1 ( 169.254.54.33 ) on node_name_4_clus1 and node_name_6_clus2 ( 169.254.107.101 ) on node_name_6
Sun Feb 28 15:02:02 +0100 [node_name_5: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_5_clus1 ( 169.254.133.220 ) on node_name_5_clus1 and node_name_6_clus2 ( 169.254.20.249 ) on node_name_6
Sun Feb 28 14:38:17 +0100 [node_name_6: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Total Packet Loss - Ping failures detected between node_name_6_clus1 ( 169.254.107.101 ) on node_name_6_clus1 and node_name_6_clus2 ( 169.254.62.17 ) on node_name_6
 

 

 
 
 

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.