# Do not multiply NFSv4.1 session concurrency by the connection count

> Will adding nconnect connections raise an Azure NetApp Files session's negotiated request limit?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-400-do-not-multiply-nfsv4-1-session-concurrency-by-the-connection-count/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:25:16+00:00
- Modified: 2026-09-10T02:01:57+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Will adding nconnect connections raise an Azure NetApp Files session's negotiated request limit?

## Potentially affected

Use this check for Linux clients mounting Azure NetApp Files over NFSv4.1. Record the actual protocol, session-slot setting, and connection count; do not apply the source's separate NFSv3 tuning model to this calculation.

## DSE recommendation

Write down the desired outstanding-request budget before changing mount options.

## Article

## Source facts

For NFSv4.1, Azure NetApp Files and the client negotiate a session request limit using the lower supported value. That session limit applies across its connections; extra connections do not each receive a fresh session allowance. Microsoft’s example with 64 session slots and two connections still permits 64 outstanding requests in total. Changes to the Linux max_session_slots setting require a reboot. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-linux-concurrency-session-slots).

## Applicability

Use this check for Linux clients mounting Azure NetApp Files over NFSv4.1. Record the actual protocol, session-slot setting, and connection count; do not apply the source’s separate NFSv3 tuning model to this calculation.

## DSE recommendation

Write down the desired outstanding-request budget before changing mount options. Distinguish session capacity from how that capacity is spread over network connections. Review the source’s server and per-connection limits alongside the measured workload, and schedule any required reboot through the client owner’s maintenance process. Avoid multiplying a session limit by the number of connections in a sizing spreadsheet.

## Verification

Inspect the negotiated session information using the documented mount-trace approach, then measure the intended workload before and after a controlled change. Compare outstanding requests and latency rather than promising a throughput increase from a setting alone. Keep packet traces restricted and sanitize them for ordinary review. If the negotiated allowance is unchanged, investigate that fact before increasing concurrency elsewhere.

## Official references

[Microsoft Learn: Linux concurrency best practices for Azure NetApp Files – Session slots and slot table entries](https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-linux-concurrency-session-slots).

## Primary reference

- Name: Linux concurrency best practices for Azure NetApp Files - Session slots and slot table entries | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-linux-concurrency-session-slots
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Do not multiply NFSv4.1 session concurrency by the connection count,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-400-do-not-multiply-nfsv4-1-session-concurrency-by-the-connection-count/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.