Veritas Storage Foundation 5.1 SP1 Cluster File System Administrator"s Guide (5900-1738, April 2011)
before the private interconnect cables are fixed and Node 1 rejoins the cluster,
Node 0 panics due to hardware failure and cannot come back up, Node 1 cannot
rejoin.
Suggested solution: Shut down Node 1, reconnect the cables, restart the node.
You must then clear the registration of Node 0 from the coordinator disks.
To fix scenario III
1
On Node 1, type the following command:
# /opt/VRTSvcs/vxfen/bin/vxfenclearpre
2
Restart the node.
Troubleshooting I/O fencing
The following sections discuss troubleshooting the I/O fencing problems. Review
the symptoms and recommended solutions.
SCSI reservation errors during bootup
When restarting a node of an SFCFS cluster, SCSI reservation errors may be
observed such as:
date system name kernel: scsi3 (0,0,6) : RESERVATION CONFLICT
This message is printed for each disk that is a member of any shared disk group
which is protected by SCSI-3 PR I/O fencing. This message may be safely ignored.
The vxfentsthdw utility fails when SCSI TEST UNIT READY command
fails
While running the vxfentsthdw utility, you may see a message that resembles as
follows:
Issuing SCSI TEST UNIT READY to disk reserved by other node
FAILED.
Contact the storage provider to have the hardware configuration
fixed.
The disk array does not support returning success for a SCSI TEST UNIT READY
command when another host has the disk reserved using SCSI-3 persistent
reservations. This happens with the Hitachi Data Systems 99XX arrays if bit 186
of the system mode option is not enabled.
Troubleshooting SFCFS
Troubleshooting I/O fencing
178