Storage Foundation for Oracle® RAC 7.3.1 Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- About Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Testing the shared disks using the vxfentsthdw -m option
Review the procedure to test the shared disks. By default, the utility uses the -m option.
This procedure uses the /dev/sdx disk in the steps.
If the utility does not show a message stating a disk is ready, verification has failed. Failure of verification can be the result of an improperly configured disk array. It can also be caused by a bad disk.
If the failure is due to a bad disk, remove and replace it. The vxfentsthdw utility indicates a disk can be used for I/O fencing with a message resembling:
The disk /dev/sdx is ready to be configured for I/O Fencing on node sys1
Note:
For A/P arrays, run the vxfentsthdw command only on active enabled paths.
To test disks using the vxfentsthdw script
- Make sure system-to-system communication is functioning properly.
- From one node, start the utility.
# vxfentsthdw [-n]
- After reviewing the overview and warning that the tests overwrite data on the disks, confirm to continue the process and enter the node names.
******** WARNING!!!!!!!! ******** THIS UTILITY WILL DESTROY THE DATA ON THE DISK!! Do you still want to continue : [y/n] (default: n) y Enter the first node of the cluster: sys1 Enter the second node of the cluster: sys2
Enter the names of the disks you are checking. For each node, the disk may be known by the same name:
Enter the disk name to be checked for SCSI-3 PGR on node sys1 in the format: for dmp: /dev/vx/rdmp/sdx for raw: /dev/sdx Make sure it's the same disk as seen by nodes sys1 and sys2 /dev/sdr Enter the disk name to be checked for SCSI-3 PGR on node sys2 in the format: for dmp: /dev/vx/rdmp/sdx for raw: /dev/sdx Make sure it's the same disk as seen by nodes sys1 and sys2 /dev/sdr
If the serial numbers of the disks are not identical, then the test terminates.
- Review the output as the utility performs the checks and report its activities.
- If a disk is ready for I/O fencing on each node, the utility reports success:
ALL tests on the disk /dev/sdx have PASSED The disk is now ready to be configured for I/O Fencing on node sys1 ... Removing test keys and temporary files, if any ... . .
- Run the vxfentsthdw utility for each disk you intend to verify.