A media editor mounts a datastore with NFS. The storage admin adds the editor host bus adapter to a Fibre Channel zoneset and also requests an iSCSI IQN. The mount still succeeds or fails with the export. What actually admits this host?
Select an answer to reveal the explanation.
Short Explanation
You are checking a passport for a visitor who walked in the side gate. NFS is a file share over IP, and the export plus the client IP decide whether this editor mounts it.
Full Explanation
NFS grants access at the file level. The storage system exports a path and allows clients by IP address, and sometimes by a stronger authentication method on that same IP service. That export is what admits or refuses the editor. An iSCSI target portal and an initiator IQN admit a block initiator that logs in with iSCSI. This datastore is NFS, so there is no IQN in the path. A Fibre Channel zoneset controls which Fibre Channel port names may talk inside a VSAN. The editor's NFS client is not logging in with a host bus adapter for this mount. A device alias is a fabric-wide name for a Fibre Channel PWWN. Distributing it does not create an NFS permission. Caveat: if the same array also presents a LUN by Fibre Channel, that LUN still needs zoning. The NFS mount in this question does not. Operational check: read the export's allowed clients and confirm the editor's IP is listed, then mount again without changing the zoneset. If a firewall sits between the editor and the NFS server, that filter can still block the mount after the export is correct. The zone and the IQN remain the wrong tools.