vxfentsthdw options describes three methods the utility provides to test storage devices.
Use the vxfentsthdw utility to verify disks are configured to support I/O fencing. In this procedure, the vxfentsthdw utility tests the three disks one disk at a time from each node.
From the node galaxy, the disks are /dev/rdsk/c1t1d0, /dev/rdsk/c2t1d0, and /dev/rdsk/c3t1d0.
From the node nebula, the same disks are seen as /dev/rdsk/c4t1d0, /dev/rdsk/c5t1d0, and /dev/rdsk/c6t1d0.
Note To test the coordinator disk group using the vxfentsthdw utility, the utility requires that the coordinator disk group, vxfencoorddg, be accessible from two nodes.
To test the coordinator disk group using vxfentsthdw -c
vxfentsthdw
command with the -c
option. For example:
Enter the first node of the cluster:
ALL tests on the disk /dev/rdsk/c1t1d0 have PASSED.
The disk is now ready to be configured for I/O Fencing on node galaxy as a COORDINATOR DISK.
ALL tests on the disk /dev/rdsk/c4t1d0 have PASSED.
The disk is now ready to be configured for I/O Fencing on node nebula as a COORDINATOR DISK.
Removing and replacing a failed disk
If a disk in the coordinator disk group fails verification, remove the failed disk or LUN from the vxfencoorddg disk group, replace it with another, and retest the disk group.
If you need to replace a disk in an active coordinator disk group, refer to the troubleshooting procedure.
See Adding or removing coordinator disks
To remove and replace a failed disk
To test disk devices containing data you want to preserve, you can use the -r option with the -m, -f, or -g options, which are described in the following sections. For example, to use the -m option and the -r option, you can run the utility by entering:
# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -rm
When invoked with the -r option, the utility does not use tests that write to the disks. Therefore, it does not test the disks for all of the usual conditions of use.
Review the procedure to test the shared disks. The utility uses the -m option.
See Testing the shared disks for SCSI-3
Use the -f option to test disks that are listed in a text file. For example, you can create a file to test two disks shared by systems galaxy and nebula that might resemble:
galaxy /dev/rdsk/c2t2d1 nebula /dev/rdsk/c3t2d1
galaxy /dev/rdsk/c2t2d1 nebula /dev/rdsk/c3t2d1
where the first disk is listed in the first line and is seen by galaxy as /dev/rdsk/c2t2d1 and by nebula as /dev/rdsk/c3t2d1. The other disk, in the second line, is seen as /dev/rdsk/c2t2d2 from galaxy and /dev/rdsk/c3t2d2 from nebula. Typically, the list of disks could be extensive.
Suppose you created the file named disks_blue. To test the disks, you would enter:
# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -f disks_blue
The utility reports the test results one disk at a time, just as for the -m option.
You can redirect the test results to a text file. Precede the command with "yes" to acknowledge that the testing destroys any data on the disks to be tested.
Caution Be advised that by redirecting the command's output to a file, a warning that the testing destroys data on the disks cannot be seen until the testing is done.
# yes | /opt/VRTSvcs/vxfen/bin/vxfentsthdw -f disks_blue > blue_test.txt
Use the -g option to test all disks within a disk group. For example, you create a temporary disk group consisting of all disks in a disk array and test the group.
Note Do not import the test disk group as shared; that is, do not use the -s option.
The utility reports the test results one disk at a time. You can redirect the test results to a text file for review.
# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -g red_disks_dg > redtest.txt
After testing, destroy the disk group and put the disks into disk groups as you need.
If the utility detects that a coordinator disk has existing keys, you see a message that resembles:
There are Veritas I/O Fencing keys on the disk. Please make sure
that I/O Fencing is shut down on all nodes of the cluster before
******** WARNING!!!!!!!! ********
THIS SCRIPT CAN ONLY BE USED IF THERE ARE NO OTHER ACTIVE NODES IN THE CLUSTER! VERIFY ALL OTHER NODES ARE POWERED OFF OR INCAPABLE OF ACCESSING SHARED STORAGE.
If this is not the case, data corruption will result.
Do you still want to continue : [y/n] (default: n) y
The utility prompts you with a warning before proceeding. You may continue as long as I/O fencing is not yet configured.