Migrating existing SAN boot images

If you have an HP host and existing SAN boot images that are controlled by storage controllers, you can migrate these images to image-mode virtual disks (VDisks) that are controlled by the SAN Volume Controller.

1. Shut down the host.
2. Perform the following configuration changes on the storage controller:
   1. Remove all the image-to-host mappings from the storage controller.
   2. Map the existing SAN boot image and any other disks being migrated to SAN Volume Controller control.
3. Zone one port of each host bus adapter (HBA) to one of the SAN Volume Controller ports that is associated with the I/O group for the target image-mode VDisk.
4. Perform the following configuration changes on the SAN Volume Controller:
   1. Create an image-mode VDisk for the managed disk (MDisk) that contains the SAN boot image. Use the MDisk unique identifier to specify the correct MDisk.
   2. Create a host object and assign it to the HBA port that you zoned to the SAN Volume Controller port in step 3.
   3. Map the image mode VDisk to the host. For example, you could map the boot disk to the host with SCSI LUN ID 0.
   4. Map the swap disk to the host, if required. For example, you could map the swap disk to the host with SCSI LUN ID 1.
5. Change the boot address of the host by using the following steps:
   1. Restart the host and open the BIOS utility of the host during the booting process.
   2. Set the primary boot path to the hardware path of the LUN mapped from the SAN Volume Controller.
6. Boot the host in single-path mode.
7. Uninstall any multipathing driver that is unsupported for the HP host using the SAN Volume Controller.
8. Install subsystem device driver (SDD) if required.
9. If you installed SDD, restart the host in single-path mode to ensure that the SDD was properly installed.
10. Zone each HBA port to one port on each SAN Volume Controller node.
11. Add HBA ports to the host object that you created in step 4.b.
12. Configure the HBA settings on the host by using the following steps:
    1. Restart the host and open the BIOS utility of the host during the booting process.
    2. Set the alternate boot path to the hardware path of the boot disk using the HBA and SAN Volume Controller node that is not used by the primary boot path.
    3. Exit the BIOS utility and finish booting the host.
13. Map any further VDisks to the host, as required.