跳转到主内容

EMS事件netif.tcp.conn.bad.checksum"

Views:
59
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

适用场景

9.11.1 9.11.1及更高版本

问题描述

  • 此时将显示以下EMS消息:
Mon Sep 26 02:09:05 +0900 [node01: kernel: netif.tcp.conn.bad.checksum:error]: TCP packet with bad checksum detected on port e0c. The packet arrived on connection with source address xx.xx.xx.xx and destination_address xx.xx.x.xx.
  • 错误的TCP ksum也在 ::> system node run -node node_name -command ifstat port_name 中的端口上增加:

-- interface  e0c  (40 days, 5 hours, 34 minutes, 37 seconds) --
RECEIVE
Total frames:     2047m | Frames/second:     589  | Total bytes:      2625g
Bytes/second:      755k | Total errors:        0  | Errors/minute:       0
...
LRO bytes:        2527g | LRO6 segments:       0  | LRO6 bytes:          0
 Bad UDP cksum:       0  | Bad UDP6 cksum:      0  | Bad TCP cksum:      21
 Bad TCP6 cksum:      0  | Mcast v6 solicit:    0  | Lagg errors:         0
...

  • 在继续使用解决方案之前、可以执行以下故障排除步骤:
    • 验证 “ifstat端口)”下的所有CRC错误 ,如果可以 看到CRC错误,则对连接到端口的电缆/SFP进行故障诊断。
    • 如果ifstat 中未报告CRC错误:
      • 如果EMS消息中报告单个客户端、请调查该 客户端。
      • 否则、如果客户端中没有趋势、请调查EMS消息中提及的客户端IP与SIF之间的设备。
      • 确保在所有接口(存储、交换机、主机)上设置正确的MTU
  • 注意:从存储、连接的交换机端口和客户端上的受影响端口同时收集tcpDump或数据包跟踪,以确认TCP错误校验和。目前尚无其他已知方法可排除贡献者或确定发生原因。

 

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.