HP 3PAR Solaris Implementation Guide

The hardware path for the second path must be derived and passed to OpenBoot when the
host server needs to boot from the second path. The second path can be deduced and
constructed using the information from the Solaris luxadm display command:
# luxadm display /dev/rdsk/c7t50002AC000300040d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c7t50002AC000300040d0s2
.
.
.
State ONLINE
Controller /devices/pci@8,700000/SUNW,qlc@3,1/fp@0,0
Device Address 21520002ac000040,a
Host controller port WWN 210100e08b275ab5
Class primary
State ONLINE
.
9. For SPARC, create aliases for the alternative hardware paths to the boot-disk. The host server
console must be taken down to the OpenBoot ok prompt:
# init 0
#
INIT: New run level: 0
The system is coming down. Please wait.
System services are now being stopped.
Print services stopped.
May 23 16:51:46 sunb1k-01 syslogd: going down on signal 15
The system is down.
syncing file systems... done
Program terminated
{1} ok
ok nvalias path1 /pci@8,700000/pci@1/SUNW,qlc@5/fp@0,0/disk@w20520002ac000040,a:a
ok nvalias path2 /pci@8,700000/SUNW,qlc@3,1/fp@0,0/disk@w21520002ac000040,a:a
Configuration for Multiple Path Booting
A Solaris host can boot from multiple paths to the boot LUN and this should be done to give
redundancy in the event of failure of the primary boot path. Follow the examples below for SPARC
and x86 platforms on how to configure multipath booting.
SPARC
Set both paths as aliases in the PROM and set the boot-device parameter to both these aliases.
For example:
ok nvalias sanboot1 /pci@1e,600000/pci@0/pci@2/emlx@0/fp@0,0/disk@w20340002ac000120,a
ok nvalias sanboot2 /pci@1e,600000/pci@0/pci@2/emlx@0,1/fp@0,0/disk@w21540002ac000120,a
ok setenv boot-device sanboot1 sanboot2
With these settings and the host server set to auto-boot on power up, the server should boot from
the second path automatically in the event of a failure on the first path.
Configuration for Multiple Path Booting 67