Skip to main content
NetApp Knowledge Base

NFS write latency after LACP reconfiguration

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

Applies to

  • ONTAP 9
  • NFS
  • LACP

Issue

  • Increased write latency after LACP (Link Aggregation Control Protocol) was reconfigured from single to multimode
  • Latency spikes up to 10ms, mainly affecting NFS workloads
  • QoS statistics and performance metrics show latency at the N-blade (protocol processing) layer
  • NFS clients (ESXi hosts) exceed 128-slot per TCP connection limit, triggering ONTAP NAS flow control, pausing client operations until resources are freed
  • EMS logs show recurring 'nblade_execsOverLimit_1' events:
Tue Sep 01 00:19:56+0300 [cluster_A-01:kernel:nblade_execsOverLimit_1:notice]: params:{'clientIpAddress':'x.x.x.x','clientPort':'xxx','lifIpAddress':'x.x.x.x','vserverId':'1','execsLimit':'128'}

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.