When configuring access for a host that uses both iSCSI and Fibre Channel, what step ensures proper access?

When configuring access for a host that uses both iSCSI and Fibre Channel, what step ensures proper access?

• A. Add both protocols to the same igroup
• B. Enable mixed-protocol access in ONTAP System Manager
• C. Assign the host to an NVMe subsystem instead
• D. Create separate igroups for each protocol

Answer: (D)

When a single host uses both iSCSI and Fibre Channel, keep the initiators for each transport in their own dedicated igroups. This ensures each protocol’s initiators are mapped precisely to the correct targets and zoning, preventing cross-protocol confusion and access issues. By creating one igroup for the Fibre Channel WWPNs and another for the iSCSI IQNs, ONTAP can present the same storage to the host over both protocols in a clean, controlled way. This separation also aligns with fabric zoning and security requirements, and you can still enable multiprotocol access on the SVM so the host can reach the same LUNs via both paths. Mixing protocols in a single igroup or trying to enable a non-existent mixed-protocol toggle isn’t appropriate, and assigning the host to an NVMe subsystem does not address iSCSI/FC access.

When a single host uses both iSCSI and Fibre Channel, keep the initiators for each transport in their own dedicated igroups. This ensures each protocol’s initiators are mapped precisely to the correct targets and zoning, preventing cross-protocol confusion and access issues. By creating one igroup for the Fibre Channel WWPNs and another for the iSCSI IQNs, ONTAP can present the same storage to the host over both protocols in a clean, controlled way. This separation also aligns with fabric zoning and security requirements, and you can still enable multiprotocol access on the SVM so the host can reach the same LUNs via both paths. Mixing protocols in a single igroup or trying to enable a non-existent mixed-protocol toggle isn’t appropriate, and assigning the host to an NVMe subsystem does not address iSCSI/FC access.