Which host information is required to map new iSCSI LUNs for a Hyper-V cluster and make them visible to the Hyper-V cluster?

Which host information is required to map new iSCSI LUNs for a Hyper-V cluster and make them visible to the Hyper-V cluster?

• A. IQNs
• B. WWNs
• C. IP addresses
• D. Hostnames

Answer: (A)

The initiator’s identity used by iSCSI, the IQN, is what matters when mapping LUNs for a Hyper-V cluster. The storage array presents or hides LUNs based on which iSCSI initiators (identified by their IQNs) are allowed access. In a Hyper-V cluster, each node’s iSCSI initiator has a unique IQN, and you map the new LUNs to that IQN so all cluster nodes can see and use them. IP addresses simply locate the target, but the actual access control and visibility of the LUN depend on the IQN. WWNs pertain to Fibre Channel, not iSCSI, and hostnames don’t determine LUN access. So, the required host information to map new iSCSI LUNs for visibility to the Hyper-V cluster is the IQN.

The initiator’s identity used by iSCSI, the IQN, is what matters when mapping LUNs for a Hyper-V cluster. The storage array presents or hides LUNs based on which iSCSI initiators (identified by their IQNs) are allowed access. In a Hyper-V cluster, each node’s iSCSI initiator has a unique IQN, and you map the new LUNs to that IQN so all cluster nodes can see and use them. IP addresses simply locate the target, but the actual access control and visibility of the LUN depend on the IQN. WWNs pertain to Fibre Channel, not iSCSI, and hostnames don’t determine LUN access. So, the required host information to map new iSCSI LUNs for visibility to the Hyper-V cluster is the IQN.