This is looking better. Note in the previous post, the scsi_vhci.conf entry conforms to the scsi_inquiry format: that is, eight characters are used for the vendor ID (NEXSAN followed by two spaces), with the product ID appended.
Now the scsi devices appear under /devices/scsi_vhci. However, cfgadm still only shows the first path (ie, the first controller) as configured for each SATABeast; “cfgadm -c configure c4″ still fails.
Now the original devices (for each path) no longer show up under /devices/pci@0,0/pci10de,5d@d/pci1077,137@0/fp@0,0; and mpathadm gives:
# mpathadm show lu /dev/rdsk/c5t6000402001FC19CA6E9E7EB400000000d0p0
Logical Unit: /dev/rdsk/c5t6000402001FC19CA6E9E7EB400000000d0s2
mpath-support: libmpscsi_vhci.so
Vendor: NEXSAN
Product: SATABeast
Revision: Cg52
Name Type: unknown type
Name: 6000402001fc19ca6e9e7eb400000000
Asymmetric: no
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: off
Auto Probing: NA
Paths:
Initiator Port Name: 210000e08b9c88b1
Target Port Name: 5000402101fc19ca
Override Path: NA
Path State: OK
Disabled: no
Target Ports:
Name: 5000402101fc19ca
Relative ID: 0
So, not quite there yet.