Appendix A. CLI setup and SAN Boot 815
Enabling SAN Boot for Windows
Complete the following procedure if you want to install a Windows host by using SAN Boot:
1. Configure the IBM Storwize V5000 Gen2 system so that only the boot volume is mapped
to the host.
2. Configure the Fibre Channel storage area network (SAN) so that the host sees only one
IBM Storwize V5000 Gen2 system node port. Multiple paths during installation are not
supported.
3. Configure and enable the host bus adapter (HBA) BIOS.
4. Install the operating system by using the normal procedure, selecting the volume as the
partition on which to install.
5. Install Subsystem Device Driver Device Specific Module (SDDDSM) after the installation
completes.
6. Modify your SAN zoning to allow multiple paths.
7. Check your host to see whether all paths are available.
8. Set redundant boot devices in the HBA BIOS to enable the host to boot when its original
path fails.
Enabling SAN Boot for VMware
Complete the following steps if you want to install a VMware ESX host by using SAN Boot:
1. Configure the IBM Storwize V5000 Gen2 system so that only the boot volume is mapped
to the host.
2. Configure the Fibre Channel SAN so that the host sees only one IBM Storwize V5000
Gen2 system node port. Multiple paths during installation are not supported.
3. Configure and enable the HBA BIOS.
4. Install the operating system by using the normal procedure, selecting the volume as the
partition on which to install.
5. Modify your SAN zoning to allow multiple paths.
6. Check your host to see whether all paths are available and modify the multipath policy, if
required.
Windows SAN Boot migration
If your host runs Windows Server 2008, Windows 2012 or Windows 2016 operating system
and uses existing SAN Boot images that are controlled by storage controllers, you can
migrate these images to image-mode volumes that are controlled by the IBM Storwize V5000
Gen2 system.
HBAs: You might need to load an additional HBA device driver during installation,
depending on your Windows version and the HBA type.
HBAs: You might need to load an additional HBA device driver during installation,
depending on your ESX level and the HBA type.
To Next Page
Loading...
Need help?
General