Skip to main content
NetApp Knowledge Base

The number of bad checksum observed in IFSTAT does not match alerts in EMS logs?

  1. Last updated
  2. Save as PDF
Views:
435
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP
  • TCP

Issue

  • EMS event logs reporting netif.tcp.conn.bad.checksum since ONTAP upgrade 9.12.1

netif.tcp.conn.bad.checksum:error]: TCP packet with bad checksum detected on port a1a. The packet arrived on connection with source address 10.1.1.2 and destination_address 10.1.1.1

  • IFSTAT also shows bad checksum but at a much larger scale
  • Should this not be a 1 to 1 mapping of IFSTAT output to EMS alert ?

Bad UDP cksum:       0  | Bad UDP6 cksum:      0  | Bad TCP cksum:   18104

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.