Skip to main content
NetApp Knowledge Base

FAS8300 NodeIfInErrorsWarnAlert Received

Views:
551
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:
12/26/2024, 9:21:30 AM

Applies to

  • FAS8300/FAS8700/AFFA400
  • ONTAP 9
  • Cluster Switch

Issue

  • Cluster alerts with NodeIfInErrorsWarnAlert  are shown in EMS log file: 
[vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif lif-name (node01) to cluster lif lif-name (node02).
 
Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between Cluster01 (IP ADD) on Node01 and Cluster02 (IP ADD) on Node02
  •  This error can also be observed in SYSTEM-HEALTH-ALERT.XML

The percentage of inbound packet errors of node "Node01" on interface "xxx" is above the warning threshold.

  • Review cluster ports and switch logs to determine which ports are connected:

CLUSTER01::> network port show
Node: NODE01
                                           Speed(Mbps)        Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- ---------
xxx       Default      Default          up   9000  auto/-     healthy

  • Switch logs show switch side MTU size is incorrectly set:
Ethernetx/x is up
admin state is up, Dedicated Interface
  Hardware: 40000 Ethernet, address: xxxx.xxxx.xxxx (bia xxxx.xxxx.xxxx)
  MTU 1500 bytes, BW 40000000 Kbit , DLY 10 usec
  • Running ifstat -z  on the affected node check the related ports shows high CRC errors:

-- interface  xxx  
RECEIVE
Total frames:      468m | Frames/second:     227  | Total bytes:       114g
Bytes/second:    55454  | Total errors:      556k | Errors/minute:      16
Total discards:      0  | Discards/minute:     0  | Multi/broadcast:  2369k
Non-primary u/c:     0  | Errored frames:      0  | Unsupported Op:      0
CRC errors:        556k | Runt frames:         0  | Fragment:            0

 

 

 

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.