Skip to main content
NetApp Knowledge Base

Intermittent severe latency spikes occur between E-Series NVMe controller and ESXi hosts

Views:
32
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • E-Series using NVMe over RoCE (EF300 / EF600)
  • VMware ESXi hosts

Issue

  • Latency measured via VeeamOne shows random spikes
  • No internal latency found on server/storage sides.
  • Firmware/driver updates on ESXi hosts did not help.
  • Nexus switch logs show packet drops, likely due to QoS misconfiguration.
  • NVMe controller stats report frequent KeepAliveTimeout (KAT) events.
    • E-Series support data log -> NVMEOF-STATISTICS.CSV
      "NVMe Controller Statistics (Raw)"

 "NVMe Controllers","TCC","KAT","MQCF","MCCF","CR","CS"

"Controller A, HIC 2, port 2a","4","69","0","0","0","0"
"Controller A, HIC 2, port 2b","4","54","0","0","0","0"
"Controller B, HIC 2, port 2a","4","65","0","0","0","0"
"Controller B, HIC 2, port 2b","4","57","0","0","0","0"


"NVMe controller statistics legend"

"TCC = Total Controller Count"
"KAT = Keep Alive Timeouts"
"MQCF = Max Queue Connection Failures"
"MCCF = Max Controller Connection Failures"
"CR = NVMe Controller Resets"
"CS = NVMe Controller Shutdowns"

  • No physical layer errors; the issue is at the NVMe protocol layer.

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.