An administrator enabled the iSCSI protocol on an SVM and created a LUN for a Windows 2012 server. When the administrator uses Windows Disk Management, the LUN cannot be found. What are two solutions

The Windows 2012 server acts as an iSCSI initiator in this architecture, not a target - configuring it as a target is architecturally incorrect for a host connecting to a NetApp SAN.

iSCSI Send Targets is a target discovery mechanism configured on the initiator side during portal discovery, not a configuration step performed within an igroup on ONTAP.

The Windows initiator's IQN (iSCSI Qualified Name) must be added to an igroup on the ONTAP SVM, and that igroup must be mapped to the LUN - without this authorization, the storage array will not present the LUN to the host. This igroup-to-LUN mapping is the access control mechanism that determines which initiators can see a given LUN.

The Microsoft iSCSI Initiator service must be running on the Windows 2012 server to enable the host to establish iSCSI sessions and discover targets - without the service active, no iSCSI traffic originates from the host side at all.