Configuring a JNI or AMCC HBA for SAN boot

To take advantage of the SAN boot feature on an Oracle SPARC host, you must appropriately configure the HBA.

Before you configure the HBA, ensure that you already completed the following actions:

Configured the HBA for static port binding.
Configured and mapped the volume that serves as the SAN boot disk.
Configured the LUNs for use with VERITAS Volume Manager with DMP.
Mirrored the boot volume onto the discovered LUNs.
Installed the correct level of FCode on your HBA. To find the correct level, see the supported hardware list at the following website:
https://datacentersupport.lenovo.com/

To configure the HBA for SAN boot, use the following steps:

Change to the OpenBoot prompt.
For example, you might type in a command similar to the following command: shutdown -i0 -g0 -y
At the OK prompt, type setenv auto-boot? false.
This command specifies that the system does not restart after a power failure or after you use the reset command.
Type setenv use-nvramrc? true to enable script interpretation.
Type reset-all to clear the system's registers.
Type devalias to identify the device aliases and the associated paths of devices that are connected to the system. Note the device alias of the HBA, which presents your SAN boot volume.
Select the HBA device by typing " /devicestring" select-dev, where /devicestring is the device alias string that you wrote down.
The following command is an example: " /pci@1f,2000/JNI,FCR@1" select-dev
Note: There is a space between the opening quotation mark and the forward slash.
Type set-pconfig.
Type set-speed.
Run probe-scsi-all and note the WWPN associated with the boot volume.
Type set-bootp-wwn and enter the WWPN found in the previous step.
Type set-nvp-valid and type FF as the offset when prompted.
Type reset-all.
Type boot vx-disk –rv, where disk is the name of your boot disk.