Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

Detecting accidental SCSI-3 PR key removal from coordinator LUNs
The keys currently installed on the coordinator disks can be read using the
following command:
# vxfenadm -s all -f /etc/vxfentab
There should be a key for each node in the operating cluster on each of the
coordinator disks for normal cluster operation. There will be two keys for every
node if you have a two-path DMP configuration.
Identifying a faulty coordinator LUN
The utility vxfentsthdw (1M) provided with I/O fencing can be used to identify
faulty coordinator LUNs. This utility must be run from any node in the cluster.
The coordinator LUN, which needs to be checked, should be supplied to the utility.
See “About the vxfentsthdw utility” on page 106.
Starting shared volumes manually
Following a manual CVM shared disk group import, the volumes in the disk group
need to be started manually, as follows:
# vxvol -g dg_name startall
To verify that the volumes are started, run the following command:
# vxprint -htrg dg_name | grep ^v
Listing all the CVM shared disks
You can use the following command to list all the CVM shared disks:
# vxdisk -o alldgs list |grep shared
Failure scenarios and recovery strategies for CP
server setup
Table 4-1 describes the various failure scenarios and recovery strategies that
should be considered when setting up and maintaining I/O fencing using CP
servers.
241Prevention and recovery strategies
Identifying a faulty coordinator LUN