Windows 2016 Boot For San
Before you begin. Your system must support SAN boot LUNs. Check the Interoperability Matrix for the latest SAN booting requirements for your operating system version. For Windows 2003 configurations, store the pagefile.sys file on the local disk if you suspect pagefile latency issues. See the Microsoft Knowledge Base article Support for booting from a Storage Area Network (SAN) for more information about pagefiles. For Fibre Channel HBAs, specific queue depths provide best results. It is best to tune the queue depths on the server-side HBA for Windows hosts to 254 for Emulex HBAs or 256 for QLogic HBAs.
Steps. Enable BootBIOS on the HBA.BootBIOS firmware is installed on your HBA, but it is disabled by default. For information about how to enable BootBIOS on the HBA, see your HBA vendor-specific documentation.
San Boot Windows Server 2016
Windows 2016 Boot For San Antonio
Windows 2016 Trial
Add the HBA initiator to an igroup.You use this igroup to specify the host that can access the boot LUN. To add the initiator to the igroup, you can enter the WWPN for Fibre Channel HBAs or the iSCSI node name for iSCSI HBAs. For information about creating and managing igroups, see the SAN Administration Guide (formerly the Block Access Management Guide for iSCSI and FC) for your version of Data ONTAP. Restrict the HBA to a single path to the boot LUN. You can add additional paths after Windows is installed and you have a multipathing solution in place.To limit a single path to the boot LUN, you can use a Data ONTAP feature called port sets. You create a port set, add the port (or LIF) to the port set, and then bind the port set to an igroup. Port sets are supported for Fibre Channel (Data ONTAP operating in 7-Mode and clustered Data ONTAP) and for iSCSI (clustered Data ONTAP only).