After a network port failure, iSCSI LUNs became inaccessible until LIFs were manually migrated. Which explains this behavior?

After a network port failure, iSCSI LUNs became inaccessible until LIFs were manually migrated. Which explains this behavior?

• A. The SVM was stopped, preventing LIF failover.
• B. NVMe subsystem misconfigured.
• C. SAN data LIFs cannot fail over automatically; they must be migrated manually.
• D. iSCSI uses multi-protocol LIFs that require failover configuration.

Answer: (C)

When iSCSI uses LIFs for SAN traffic, not all SAN data LIFs participate in automatic failover. In many ONTAP configurations, SAN data LIFs must be migrated manually to a healthy port or node after a failure. If the LIF is not migrated, the iSCSI path remains bound to the failed interface, so the LUNs become inaccessible until you move the LIF to a functioning path. That’s why, after the port failure, the LUNs were unavailable until you performed a manual LIF migration. The other options don’t fit the scenario as directly: stopping the SVM would affect more than just SAN failover; an NVMe subsystem misconfiguration isn’t related to iSCSI LIF failover; and multi-protocol LIFs don’t inherently require manual failover for iSCSI access.

When iSCSI uses LIFs for SAN traffic, not all SAN data LIFs participate in automatic failover. In many ONTAP configurations, SAN data LIFs must be migrated manually to a healthy port or node after a failure. If the LIF is not migrated, the iSCSI path remains bound to the failed interface, so the LUNs become inaccessible until you move the LIF to a functioning path. That’s why, after the port failure, the LUNs were unavailable until you performed a manual LIF migration.

The other options don’t fit the scenario as directly: stopping the SVM would affect more than just SAN failover; an NVMe subsystem misconfiguration isn’t related to iSCSI LIF failover; and multi-protocol LIFs don’t inherently require manual failover for iSCSI access.