SVM STMS
SVM STMS
(OP)
Hello Forumers,
any thoughts on this:
Assume someone took the disks / LUNs under control of SVM. STMS is not active therefore the boot volume might be called: /dev/(r)dsk/c1t0d0 and some FC attached LUN (2 paths) may appear as: /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0.
The file /etc/vfstab would of course refer to objects such as /dev/md/(r)dsk/d20 or similar. Using command metastat would allow to show the association between /dev/md/(r)dsk/dN and /dev/(r)dsk/c1t0d0 and /dev/(r)dsk/c2t5WWNNd0 or /dev/(r)dsk/c3t5WWNNd0, respectively.
Now the admin would decide to enable STMS, so the boot volume might suddenly appear as: /dev/(r)dsk/c4t2000000....d0 and instead of two the two /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0 (from above) one would only see a STMS metadevice , i.e. c4t6.....d0.
Would SVM recognize this modification automatically (as the respective device / metadevice association from above would cease to exist)? Or is there the need for explicit activity, and if so: what?
Thanks. Cheers dj600stoxx
any thoughts on this:
Assume someone took the disks / LUNs under control of SVM. STMS is not active therefore the boot volume might be called: /dev/(r)dsk/c1t0d0 and some FC attached LUN (2 paths) may appear as: /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0.
The file /etc/vfstab would of course refer to objects such as /dev/md/(r)dsk/d20 or similar. Using command metastat would allow to show the association between /dev/md/(r)dsk/dN and /dev/(r)dsk/c1t0d0 and /dev/(r)dsk/c2t5WWNNd0 or /dev/(r)dsk/c3t5WWNNd0, respectively.
Now the admin would decide to enable STMS, so the boot volume might suddenly appear as: /dev/(r)dsk/c4t2000000....d0 and instead of two the two /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0 (from above) one would only see a STMS metadevice , i.e. c4t6.....d0.
Would SVM recognize this modification automatically (as the respective device / metadevice association from above would cease to exist)? Or is there the need for explicit activity, and if so: what?
Thanks. Cheers dj600stoxx
Talk To Other Members
RE: SVM STMS
example:
mirror d10
c0t0d0s0 d11
c0t1d0s0 d12
you run stmsboot -e (sparc only)
for x64/x86, you modify the file /kernel/drv/fp.conf, you don't use stmsboot command.
it will become:
mirror d10
WWNd0 d11
WWNd0 d12
You can after that fact (after you complete the stms reboot as required) run the following command to see the correlation between the need id and the old.
stmsboot -L
non-STMS device name STMS device name
----------------------------------------------------------------
/dev/rdsk/c0t0d0 /dev/rdsk/c4t500000E06745DEE0d0
/dev/rdsk/c0t1d0 /dev/rdsk/c4t500000E07868A070d0
RE: SVM STMS
Seems that with SAN 4.4 there is a need for special handling but maybe in Solaris 10 this is also done automatically?
RE: SVM STMS