Removing preexisting keys


Removing preexisting keys
Prev	About the vxfenclearpre utility	Next

If you encountered a split-brain condition, use the vxfenclearpre utility to remove CP Servers, SCSI-3 registrations, and reservations on the coordinator disks, Coordination Point servers, 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 of another node or other nodes on shared disks or CP server.

To clear keys after split-brain

Stop VCS on all nodes.
```
# hastop -all
```
Make sure that the port h is closed on all the nodes. Run the following command on each node to verify that the port h is closed:
```
# gabconfig -a
```
Port h must not appear in the output.
Stop I/O fencing on all nodes. Enter the following command on each node:
```
# /etc/init.d/vxfen.rc stop
```
If you have any applications that run outside of VCS control that have access to the shared storage, then shut down all other nodes in the cluster that have access to the shared storage. This prevents data corruption.
Start the vxfenclearpre script:
```
# /opt/VRTSvcs/vxfen/bin/vxfenclearpre
```

Read the script's introduction and warning. Then, you can choose to let the script run.

Do you still want to continue: [y/n] (default : n) y

The script cleans up the disks and displays the following status messages.

Cleaning up the coordinator disks...

Cleared keys from n out of n disks, 
where n is the total number of disks.

Successfully removed SCSI-3 persistent registrations
from the coordinator disks.

Cleaning up the Coordination Point Servers...

...................
[10.209.80.194]:50001: Cleared all registrations
[10.209.75.118]:443: Cleared all registrations

Successfully removed registrations from the Coordination Point Servers.

Cleaning up the data disks for all shared disk groups ...

Successfully removed SCSI-3 persistent registration and
reservations from the shared data disks.

See the log file /var/VRTSvcs/log/vxfen/vxfen.log

You can retry starting fencing module. In order to restart the whole 
product, you might want to reboot the system.

Start the fencing module on all the nodes.
```
# /etc/init.d/vxfen.rc start
```
Start VCS on all nodes.
```
# hastart
```