vxfentsthdw - Test SCSI-3 persistent reservations on a disk.
vxfentsthdw [ -m | -f filename ] [ -r] [ -t] [ -n] [ -p utilpath ] [ -o]
vxfentsthdw -g diskgroup [ -d | -w ] [ -r] [ -t] [ -n] [ -p utilpath ] [ -o]
vxfentsthdw -c coordinator_dg [ -d | -w ] [ -n] [ -p utilpath ] [ -o]
The vxfentsthdw utility is provided to test disks for the minimum supported size and for support of SCSI-3 persistent reservations. It verifies that the shared storage intended for use is configured to support I/O fencing. The utility works on any two cluster systems that share disks. It checks whether the disk size is above the minimum required size, then issues a series of vxfenadm commands to set up SCSI-3 registrations on the disk, verifies the registrations on the disk, and removes the registrations from the disk. Note that the utility destroys data on the disks unless the -r option is used. The vxfentsthdw utility requires that a disk intended for use as a data disk have at least 256 MB capacity, else you may see size related errors because the disk size requirement was not met.
The -c option may be used to test disks intended for use as coordinator disks that are set up in a disk group. Because the testing done with the -c option verifies only coordinator disk functionality, but does not perform any read write tests or I/O operations. The disks must be at least 128 MB, else you may see size related errors because the disk size requirement was not met.
The errors introduced due to disks smaller than the required size can be overridden by using the -o (override flag). However, if you proceed to test the disk after overriding the size errors, the disk may not set up correctly as the disk size may be smaller than the supported size. Also, you can use the utility to test whether the disks can be used as data or coordinator disks even before installing the SFHA stack.
This utility makes use of ssh and scp to communicate with the nodes. Please make sure the communication is set up properly before using this utility. Instead of ssh and scp, rsh and rcp can be used for communication by specifying the -n option.
-r Non-destructive testing. Testing of the disks for SCSI-3 persistent reservations occurs in a non-destructive way; that is, there is only testing for reads, not writes. May be used with -m, -f, or -g options. -t Testing of the return value of SCSI TEST UNIT READY (TUR) command under SCSI-3 reservations. A warning is printed on failure of TUR testing. May be used with -m, -f, or -g options. -m Manual testing. This is the default option; that is, if no options are specified, the utility carries out the test suite in manual operation. The utility prompts for system names and device paths. -f filename Test the disks listed in filename. This is a batch test operation. All disks specified in the file are tested one by one. The format of the file is:
Node1Name DevicePath Node2Name DevicePath
EXAMPLES: (Note that the format of DevicePath varies by operating system.)
For Solaris, if node SYSA and node SYSB have two shared disks, and the disks are seen as having DevicePath /dev/rdsk/c2t2d1s2 and /dev/rdsk/c3t2d1s2 on SYSA, and /dev/rdsk/c3t2d1s2 and /dev/rdsk/c3t2d2s2 on SYSB, the file filename contains:
SYSA /dev/rdsk/c2t2d1s2 SYSB /dev/rdsk/c3t2d1s2
SYSA /dev/rdsk/c3t2d1s2 SYSB /dev/rdsk/c3t2d2s2
For HP-UX, if node SYSA and node SYSB have two shared disks, and the disks are seen as having DevicePath /dev/rdsk/c2t2d1 and /dev/rdsk/c3t2d1 on SYSA, and /dev/rdsk/c3t2d1 and /dev/rdsk/c3t2d2 on SYSB, the file filename contains:
SYSA /dev/rdsk/c2t2d1 SYSB /dev/rdsk/c3t2d1
SYSA /dev/rdsk/c3t2d1 SYSB /dev/rdsk/c3t2d2
For AIX, if node SYSA and node SYSB have two shared disks, and the disks are seen as having DevicePath /dev/rhdisk70 and /dev/rhdisk75 on SYSA, and /dev/rhdisk60 and /dev/rhdisk65 on SYSB, the file filename contains:
SYSA /dev/rhdisk70 SYSB /dev/rhdisk60
SYSA /dev/rhdisk75 SYSB /dev/rhdisk65
For Linux, if node SYSA and node SYSB have two shared disks, and the disks are seen as having DevicePath /dev/sdw and /dev/sdx on SYSA, and /dev/sdy and /dev/sdz on SYSB, the file filename contains:
SYSA /dev/sdw SYSB /dev/sdy
SYSA /dev/sdx SYSB /dev/sdz
-c coordinator_dg Tests disks in a disk group for coordinator disk functionality only. This option requires that Veritas Volume Manager is installed and running. Testing does not include read/write or I/O testing and is not suitable for disks to be used as data disks. -o Overrrides errors related to disk size. This flag is used if you want to override errors related to disk size, but you want the utility to test the SCSI-3 readiness of the disk. However, the override flag does not guarantee that the disks can be set up as coordinator or data disks as the size may be smaller than the supported size. -g diskgroup Test all disks in the diskgroup. This option requires that Veritas Volume Manager is installed and running. A test disk group needs to be set up, with all disks to be tested contained within that group. Dynamic Multipathing (DMP) is tested with this option; that is, disks contained in the test disk group configured with DMP are tested for SCSI-3 compatibility. -d Use DMP devices for testing. This option may be used with -g or -c options. With this option, the script picks the DMP paths for disks in the disk group. -w Use raw devices for testing. This option may be used with -g or -c options. With this option, the script picks the raw paths for disks in the disk group. -n Use non-secure communication. By default, vxfentsthdw makes use of ssh and scp to communicate with nodes. When this option is specified, vxfentsthdw will use rsh and rcp for communication. -p utilpath Use utilpath as the path for VxFEN utilities used by vxfentsthdw. By default, vxfentsthdw will attempt to use vxfenadm from /sbin and vxfendd from /opt/VRTSvcs/vxfen/bin directories. These paths can be overridden to the utilpath specified with this option. This is useful when vxfentsthdw is used to test hardware on nodes that do not have the VRTSvxfen package installed. vxfentsthdw checks if the necessary utilities are available at their default paths. If not, it attempts to copy these utilities from the path where vxfentsthdw is being run to the specified tools directory. If this option is not specified, vxfentsthdw will attempt to copy the utilities to their default paths if they are not found on the target nodes.
vxfenadm(1M), vxfendebug(1M), vxfenconfig(1M), vxfenmode(4M), vxfenclearpre(1M)