To change the Cluster Name and the Cluster ID, follow the below procedure:

1. Stop the Veritas Cluster Server (VCS) engine on all nodes in the cluster leaving the services it manages up and running by executing the following command from a Windows command prompt on one node in the cluster:
hastop -all -force

2. Stop the VCS communications on all nodes in the cluster by executing the following command from a Windows command prompt on all nodes in the cluster:
net stop llt
When prompted to stop VCSComm and GAB, answer Y

3. Modify the %vcs_root%\comms\llt\llttab.txt file in a text editor on all nodes to replace the cluster ID. Replace the existing cluster ID on the set-cluster line with the new, unique cluster ID.

4. On one node, modify the %vcs_home%\conf\config\main.cf file in a text editor to replace the old cluster name with the new, unique cluster name. This only need to be done on one server and the file can be copied to all remaining nodes of the cluster.

5. Verify that the syntax of the %vcs_home%\conf\config\main.cf file is correct by executing the following command in a Windows command prompt:
hacf -verify "%vcs_home%\conf\config"
When the syntax of the file is correct, there is no output from the above command.

6. Edit the registry location HKEY_LOCAL_MACHINE\Software\Veritas\VCS\Base to change the ClusterName and the ClusterID values. These values should be the same as the new values created above.

7. Restart VCS on the node where the %vcs_home%\conf\config\main.cf file edited by executing the following command from a Windows command prompt:
hastart

8. Check the status of VCS by executing the following command from a Windows command prompt:
hasys -state

The above command may need to be executed several times before the status will show that the node is in a running state.

9. Once the command from step 8 shows that the node is in a running state, start VCS on the rest of the nodes by executing the following command in a Windows command prompt:
hastart -all

10. Check the status of VCS on all nodes by executing the following command from a Windows command prompt:
hasys -state

The above command may need to be executed several times before the status will show that all nodes are in a running state.