If you encountered a split-brain condition, use the vxfenclearpre utility to remove SCSI-3 registrations and reservations on the coordinator disks as well as on the data disks in all shared disk groups.
You can also use this procedure to remove the registration and reservation keys created by another node from a disk.
To clear keys after split-brain
# hastop -all
# gabconfig -a
Port h must not appear in the output.
# svcadm disable -t vxfen
Do you still want to continue: [y/n] (default : n) y
In some cases, informational messages resembling the following may appear on the console of one of the nodes in the cluster when a node is ejected from a disk/LUN. You can ignore these informational messages.
<date> <system name> scsi: WARNING: /sbus@3,0/lpfs@0,0/ sd@0,1(sd91): <date> <system name> Error for Command: <undecoded cmd 0x5f> Error Level: Informational <date> <system name> scsi: Requested Block: 0 Error Block 0 <date> <system name> scsi: Vendor: <vendor> Serial Number: 0400759B006E <date> <system name> scsi: Sense Key: Unit Attention <date> <system name> scsi: ASC: 0x2a (<vendor unique code 0x2a>), ASCQ: 0x4, FRU: 0x0
The script cleans up the disks and displays the following status messages.
Cleaning up the coordinator disks... Cleaning up the data disks for all shared disk groups... Successfully removed SCSI-3 persistent registration and reservations from the coordinator disks as well as the shared data disks. You can retry starting fencing module. In order to restart the whole product, you might want to reboot the system.
# svcadm enable vxfen