A factory IoT network cannot boot a host from an iSCSI LUN. The initiator IQN and the target portal IP were never configured. An administrator instead added the host to a Fibre Channel zoneset. What will actually let the host reach the LUN?
Select an answer to reveal the explanation.
Short Explanation
iSCSI travels as IP, so you hand the initiator a portal address and a target name. You do not get there by putting the host in a Fibre Channel zoneset. That zoneset never sees this session.
Full Explanation
iSCSI carries SCSI over TCP. The initiator needs the target's portal IP and the target IQN, plus IP reachability, before it can open a session and see a LUN. A Fibre Channel zoneset does not authorize that session and activating it will not make the factory LUN appear. An FCID is the address a Fibre Channel device receives at FLOGI. iSCSI does not use an FCID as the target address. NPV is a Fibre Channel edge mode. An Ethernet access switch carrying an iSCSI VLAN is not an NPV Fibre Channel switch, and NPV would not create an iSCSI session. Caveat: the storage array still has to mask the LUN to this initiator IQN, and a firewall in the path has to permit the iSCSI session, or a perfect portal configuration still shows no disk. Operational check: configure the portal IP and IQN on the initiator, confirm the session reaches the logged-in state, and only then look at LUN masking if the disk is still missing. Record the before and after values in the change ticket so the next shift can see what changed.