Here is one interesting scenario.SRDF setup with R1 and R2,ClonesC1,C2 on each side.Planning to use the host on C2-side to access the data on a dial basis to perform backups or to do some tests.
Since the LUN ID are more than 255 allocated on the FAs,Solaris host want to install the ssd drivers. Initial plan was to use sd.conf file to control which devices can be accessed by the servers(Either clones or Primary volumes).In this case since ssd driver discovers the storage dynamically,how would i be able to control,which device need to be accessed?Is there any static method?
Reason for doing that way is,If i mask primary and Clone volumes to FA then ssd will discover both but while importing the volume groups to solaris,it would get confused to which disks to use since both of them will have same Private regions.
This isn't really Solaris specific, but our solution for our DR environment (where we need to access R2s or Clones) involves scripts to change the masking from the Clones to the R2s and back again.
We normally leave our R2s masked for DR activation. If we run a DR test we switch to masking the Clones. Once the test is completed we revert back to the R2s mapped. It's a bit of a pain to set up, but once it is it just needs to be maintained.
SSD driver can't be "tweeked" via sd.conf file .. thus if you have more then 255 devices, you have to either
1) map on more ports .. (map half of the devices on a couple of FA ports and another half on another pair of FA ports. If possible bring FA ports online/offline to filter devices. Otherwise change masking (!!!!) to filter devices.
2) map all devices on a single pair of port and use lun offsett to filter devices
3) map all devices on a single pair of ports and use masking to filter devices
Leave the thread here. Not sure on yout second point. 2) map all devices on a single pair of port and use lun offsett to filter devices. BY Lun off set,Can i tell scan only 1-10 LUNs or 11-20.So that it will scan only those?