Hello RonDebbs,
The process has a few steps
Insure the PATH to the symcli is set. This will tell you where it is.
# find / -name symcli -type file -print 2>/dev/null
symcfg list
above will list serial # , if you have more than one symmetrix use the -sid option in your command, to prevent sorting through lots of output.
use this to determine what is currently masked
symmaskdb -sid 0123 list -wwn 10000000C93725b4 devs
the 2 variables are the -sid which is the last 3 or 4 digits of the symmetrix serial # and the wwn .
To obtain the wwn with AIX this might work.
#!/bin/ksh
# to grab the hba wwns out of a aix node
for fc in `lsdev -C | grep ^fcs | awk '{print$ 1}'`
{
wwn=`lscfg -vl $fc | grep 'Network Address' | cut -c 37-`
echo "$fc\t$wwn"
}
So now that you have the output from
symmaskdb -sid 0123 list -wwn 10000000C93725b4 devs
compaire it to what is mounted or in your volume groups.
The output of a inq command might be helpful, or not.
In a change window. Unmask the devices you want to free up
symmask -sid 0123 -wwn 10000000C93725b4 remove devs 111,112
in the above command you can list as many characters as your OS will allow on one command line.
To promptly put the devices back
symmask -sid 0123 -wwn 10000000C93725b4 add devs 111,112
symmask -sid 0123 refresh -noprompt
symcfg discover
I suggest using the unmask command first becuase if you inadverently pull the device out of a voulme group, and need to put it back in it can be done so quickly.
After the devices are unmasked, and you can still use the production file systems, proceed to the not_ready or write_protect phase.
Devices must be write disabled prior to unmapping
from the commad line this will do that
symdev -sid 0123 write_disable XXX -sa ALL -p 1 -noprompt
symdev -sid 0123 write_disable XXX -sa ALL -p 0 -noprompt
I usually do a symdev show on the device and get specific, on the sa I am pulling it from.
After the device is write_disabled it can be unmaped with
unmap dev xxx from dir all:all;
which is usually put in a text file and run through symconfigure. Something like
symconfigure -sid 0123 -f unamp_devs preview -noprompt
symconfigure -sid 0123 -f unmap_devs prepair -noprompt
symconfigure -sid 0123 -f unmap_devs commit -noprompt
After all of that the devices will be free and be able to be redeployed on another System.
Pulling disk can cause applications to crash. Be careful !
If the devices are just going to be used on the same system but in a different volume group, all of the above in unnecessary just use LVM to manage the volume groups.
Good Luck,