FlexCache origin write failures caused by IPFW state exhaustion on port 11105
Applies to
- NetApp ONTAP 9
- FlexCache
- WAN
- NFS
Issue
- FlexCache origin write operations can fail or appear hung even though the origin volume remains online.
- Clients can report write failures, hangs, or intermittent access problems while using FlexCache.
- EMS may report `ipfw.ReachedMaxStates` when the node cannot allocate additional firewall keep-state entries.
[node-##: OscHighPriThreadPoo: ipfw.ReachedMaxStates:notice]: The ipfw firewall failed to create dynamic "keep-state" entry. Reason: Dynamic entries for 'keep-state' rules allocation failure, current # of entries: 31446. Recent connections reaching this limit: [intercluster_lif]:47238->[intercluster_lif]:11105 (TCP):32272
- In some environments, `Nblade.dBladeNoResponse` and `csm_createSessionFailed` can also appear once new intercluster connections can no longer be created.
- The problem is typically associated with a large number of persistent FlexCache / CSM connections on TCP port
11105. - The issue can become more visible after topology growth, peer changes, or node reboots when large numbers of sessions are re-established.
