Which host information is used to map iSCSI LUNs for a Hyper-V cluster?

Which host information is used to map iSCSI LUNs for a Hyper-V cluster?

• A. WWPNs
• B. DNS names
• C. MAC addresses
• D. IQNs

Answer: (D)

In iSCSI, the host is identified by its IQN, and this is what the storage target uses to map LUNs to a specific initiator. When a Hyper-V cluster connects to a iSCSI target, each host’s iSCSI initiator presents its own IQN to the target, and the target grants access to the LUNs based on that IQN. That makes IQNs the key piece of host information used to determine which host can access which LUN. WWPNs are associated with Fibre Channel storage, not iSCSI. DNS names relate to network naming and resolution, not the per-host mapping of iSCSI LUNs. MAC addresses identify network interfaces, not storage paths. So the identifier that ties LUN access to a particular host in iSCSI environments is the IQN.

In iSCSI, the host is identified by its IQN, and this is what the storage target uses to map LUNs to a specific initiator. When a Hyper-V cluster connects to a iSCSI target, each host’s iSCSI initiator presents its own IQN to the target, and the target grants access to the LUNs based on that IQN. That makes IQNs the key piece of host information used to determine which host can access which LUN.

WWPNs are associated with Fibre Channel storage, not iSCSI. DNS names relate to network naming and resolution, not the per-host mapping of iSCSI LUNs. MAC addresses identify network interfaces, not storage paths. So the identifier that ties LUN access to a particular host in iSCSI environments is the IQN.