Internal steps performed by the vxfen startup script in SF product stack

book

Article ID: 100002274

calendar_today

Updated On:

Resolution

In order to assist with the understanding of how vxfen driver is started, here is a breakdown of the steps taken in the vxfen startup script:

1) Check to see if /etc/vxfenmode file is valid:

Make sure that vxfen_mode is not customized or disabled.

/usr/bin/egrep -v "[\s\t]*\#" $VXFENMODE | /usr/bin/egrep-i  ".*[^#]*vxfen_mode=customized|disabled" > /dev/null

AND make sure that vxfen_mechanism is not set to sg.

/usr/bin/egrep -v"[\s\t]*\#" $VXFENMODE | /usr/bin/egrep -i  ".*[^#]*vxfen_mechanism=sg"> /dev/null

AND make sure that scsi3_disk_policy is set to DMP.

/usr/bin/egrep -v "[\s\t]*\#" $VXFENMODE | /usr/bin/egrep -i".*[^#]*scsi3_disk_policy=dmp" > /dev/null

2) Now check the contents of /etc/vxfendg:

Get the name of disk group from /etc/vxfendg if it exists. If it does not exist, don't recreate /etc/vxfentab.

VXFENCOORDDG=`cat $VXFENDG`

3) Now check the contents of/etc/vxfendg, and make sure that the name DG shows up in vxdisk -o alldgs list:
# This must work for A/A as well as A/P arrays.

disk_names =vxdisk -o alldgs list | grep -w "$VXFENCOORDDG" | awk '{print $1}'

4)Get the list of disks in the disk group as well as all paths to each disk.  This must work for active/active arrays as well as active/ passive arrays.

for i in$disk_names
do
     vxdisk list "$i" | grep"pubpaths:" | awk '{print $3}'  >>/tmp/file1.$$
done


4) Cut out everything after "char=" asDMP device name:

cut -b6- /tmp/file1.$$ > $VXFENTAB

5) Otherwise, get the list of disks in the disk group as well as all paths to each disk.  This must work for active/active arrays as well as active/ passive arrays.

for i in $disk_names
do
   vxdisk list "$i" | grep state | awk '{print $1}'  >>/tmp/file1.$$
done


6) Prepend the /dev/rdsk to each disk before moving it to /etc/vxfentab.

for i in `cat/tmp/file1.$$`
do
   echo "/dev/rdsk/$i" >>/tmp/file2.$$
done


7)  Move the file to vxfentab:

mv /tmp/file2.$$ $VXFENTAB
 
 

 

Issue/Introduction

Internal steps performed by the vxfen startup script in SF product stack