Our Storageboxes are able to setup ALUA. If your work with GAD over WDM it could be an good idea to work with it. But there are one problem. Solaris need an entry/change into the scsi_vhci.conf. Pls be carefull. Im only on a testsystem but it work.
Setup ALUA as described in my previous article. Now ALAU is, seen from storage, enabled. If you check your LUN into solaris with „mpathadm show lu /dev/rdsk/……“ you should see „Asymmetric: no“. Whatever you do. Reboot. reconfigure, nothing changes that state. Its active/active. You have to edit your „/etc/driver/drv/scsi_vhci.conf“ (not a beginner guide, you have to know how that file comes there)
from
# „misc/scsi_vhci/scsi_vhci_<failover-module-name>“ in ‚ddi-forceload‘ above.
#
# “ 111111″
# „012345670123456789012345“, „failover-module-name“ or „NONE“
# „|-VID–||—–PID——|“,
# scsi-vhci-failover-override =
# „STK FLEXLINE 400“, „f_asym_lsi“,
# „SUN T4“, „f_tpgs“,
# „CME XIRTEMMYS“, „NONE“;
#to
# „misc/scsi_vhci/scsi_vhci_<failover-module-name>“ in ‚ddi-forceload‘ above.
#
# “ 111111″
# „012345670123456789012345“, „failover-module-name“ or „NONE“
# „|-VID–||—–PID——|“,
scsi-vhci-failover-override =
„HITACHI OPEN“,“f_tpgs“;
# „STK FLEXLINE 400“, „f_asym_lsi“,
# „SUN T4“, „f_tpgs“,
# „CME XIRTEMMYS“, „NONE“;
#
#END: FAILOVER_MODULE_BLOCK (DO NOT MOVE OR DELETE)REBOOT
After that your „mpathadm show lu /dev/rdsk/……“ shoud show your device with „Asymmetric: yes“. Thats it.
Be aware!!! After that you CANT see any Non-ALUA Lun from an HDS Device who are identified with „HITACHI OPEN“ in „format“. The system dosent show them. As an example. If you have two G1000 with an GAD Setup and 10GAD Luns – you can setup one or more LUNS without GAD but with an enabled ALUA (look at your GUI or set it with the CLI) to this Server. But you CANT set an VSP (Raid7000) Lun to this host. Solaris dosent recognize it. This is not an „Solaris-Problem“. Some guys tell me that this is standard behavior in Linux/some Windows…depend on the MPXIO Standards.