Message-ID: Check for HBA with dual-ported disks from the boot prom: Note you should reset system before probing it ok> reset-all ok> probe-scsi-all For example: ok> probe-scsi-all /pci@6,4000/scsi@3,1 /pci@6,4000/scsi@3 Target 2 Unit 0 Disk Disk Vendor Target 3 Unit 0 Disk Disk Vendor /pci@6,4000/scsi@2,1 Target 2 Unit 0 Disk Disk Vendor Target 3 Unit 0 Disk Disk Vendor Identify which disks are the dual-hosted disk and note the SCSI adaptors they are attached to. Using the above example, one connection would be "/pci@6,4000/scsi@3" and the other "/pci@6,4000/scsi@2,1" 2) Update the nvramrc to set the scsi-initiator-id to 6 for these device. From the boot prom type: ok> nvedit 0: probe-all install-console banner 1: cd /pci@6,4000/scsi@3 2: 6 " scsi-initiator-id" integer-property 3: device-end 4: cd /pci@6,4000/scsi@2,1 5: 6 " scsi-initiator-id" integer-property 6: device-end 3) Store the nvramrc. From the boot prom type: ok>nvstore 4) Evaluate the nvramrc: From the boot prom type: ok>nvramrc evaluate 5) Set the system to use the nvramrc: From the boot prom type: ok>setenv use-nvramrc? true 6) Do a reset: From the boot prom type: ok>reset-all 7) Edit the /etc/system file (on both nodes) to set fast/wide SCSI (disable Ultra SCSI): set scsi_options=0x3f8 8) Boot both systems and verify that you can see the multi-hosted disks from both nodes. Message-ID: <1021590517.52281@nntp1.acecape.com> >Great but how about file locking ? >does it work automagically ? No file locking. You need to use disk suite disk sets or Veritas Volume Manager disk groups to control access if you want to try something like this (not that I would recommend it)