During a node replacement, NFS clients remain online while iSCSI clients drop. Which explanation best fits this behavior?

During a node replacement, NFS clients remain online while iSCSI clients drop. Which explanation best fits this behavior?

• A. iSCSI requires multipathing
• B. iSCSI LIFs fail over automatically
• C. NFS LIFs cannot migrate
• D. SLM was disabled

Answer: (B)

During a node replacement, the system performs LIF failover to keep services reachable. The key difference between the two protocols is that iSCSI relies on stateful sessions, while NFS is largely stateless. iSCSI LIFs are configured to fail over automatically to another node when the owning node goes offline, which causes the iSCSI sessions to drop as the initiator must re-login to the target on the new path. NFS, being stateless, can continue to function across the new path without requiring a session re-establishment, so NFS clients stay online. This combination explains why iSCSI clients drop while NFS clients remain available during the node replacement.

During a node replacement, the system performs LIF failover to keep services reachable. The key difference between the two protocols is that iSCSI relies on stateful sessions, while NFS is largely stateless. iSCSI LIFs are configured to fail over automatically to another node when the owning node goes offline, which causes the iSCSI sessions to drop as the initiator must re-login to the target on the new path. NFS, being stateless, can continue to function across the new path without requiring a session re-establishment, so NFS clients stay online. This combination explains why iSCSI clients drop while NFS clients remain available during the node replacement.