iSCSI max-iscsi-sessions tunable in Nimble OS 5.0 and session termination behavior

Nimble OS 5.0 introduces a configurable max-iscsi-sessions parameter under iscsi settings to cap concurrent iSCSI sessions per node, replacing the previous hard-coded limit. Pool utilization can be observed as a Current/Max ratio, with values approaching 100% indicating impending exhaustion.

The change creates a configuration transition where the limit can be raised or lowered on a running system. The documented feature describes the parameter and monitoring, but does not specify the enforcement semantics when the configured maximum is reduced below the number of active sessions.

For planning safe adjustments and understanding compatibility with workloads that rely on persistent sessions, the session termination policy needs clarification.

Does lowering max-iscsi-sessions below the current session count immediately terminate excess sessions, or is the new limit enforced only for new connection attempts? Is there a defined grace or drain behavior for existing sessions when the limit is reduced? How is the enforcement boundary documented for versions prior to Nimble OS 5.0 versus 5.0 and later?