A state university hypervisor reaches its datastore with iSCSI. An engineer edits a Fibre Channel zoneset, and the session still fails. The initiator has no HBA in this path. What identifies this host to the target?
Select an answer to reveal the explanation.
Short Explanation
iSCSI knocks on an IP door, not on a Fibre Channel guest list. You identify this host with its initiator IQN toward the target portal on TCP port 3260. A zoneset does not get a vote on that session, because the hypervisor is not logging in with an HBA.
Full Explanation
iSCSI is IP block storage. The host identifies itself with an initiator IQN, and it reaches the target at a portal address on TCP port 3260. The target ACL or initiator group then decides whether that IQN may see the LUN. The university hypervisor has no HBA on this path, so a Fibre Channel zoneset is not in the session and editing it cannot fix the failure. A WWPN matters for a Fibre Channel login. It is not how an iSCSI initiator is named. An FCID is assigned at FLOGI on a Fibre Channel fabric. An iSCSI initiator does not present an FCID to a target portal. NPV and a domain ID are Fibre Channel fabric concepts for an edge switch that does not join the fabric as a full switch. A hypervisor does not use an NPV domain ID to authorize iSCSI. Caveat: a correct IQN and a reachable portal can still be rejected by target-side access control or by CHAP, so the zoneset is the wrong layer even when the IP path is only half the problem. Operational check: confirm the hypervisor opens TCP port 3260 to the portal, confirm the target allows that IQN, and leave the Fibre Channel zoneset out of this path.