How to configure the VCS cluster UUID manually

book

Article ID: 100007990

calendar_today

Updated On:

Description

Error Message

2009/12/15 17:46:51 VCS ERROR V-16-1-10614 Cluster UUID is not configured or it is empty,  on system - VCS Stopping. Manually Restart VCS after configuring Cluster UUID.
2009/12/15 17:46:51 VCS ERROR V-16-1-10651 Cluster UUID received from snapshot is not matching with one existing on HOSTNAME. VCS Stopping. Manually restart VCS after configuring correct CID in the cluster.

 

Resolution

The error messages are caused by the VCS UUID not matching between different servers in the cluster:

To configure the cluster UUID manually, the following command needs to be executed to copy the cluster UUID from the existing VCS cluster system node/(s) to the required nodes which encounter the issue of UUID not matching.

 
# /opt/VRTSvcs/bin/uuidconfig.pl [-rsh] -clus -copy -from_sys sys -to_sys sys1 sys2 [sys3...]
 
The uuidconfig.pl utility copies the cluster UUID from a system that is specified following the "-from_sys" option to all the systems that are specified following the "-to_sys" option in the above command.
 

You can then verify the existence of the valid cluster UUID and compare it to the existing cluster system nodes:

uuidconfig.pl [-rsh] -clus -display -use_llthost | sys1 [sys2 sys3...

OR manually

# cat /etc/vx/.uuids/clusuuid

 
ssh or rsh connectivity is required between the cluster nodes for the uuidconfig.pl command to be able to copy the file between the Cluster systems. However, if there is any problem with ssh or rsh connectivity between the cluster nodes, then it is possible to manually copy the file /etc/vx/.uuids/clusuuid from the server which is part of the VCS cluster, to other servers which are not able to join into the cluster.
 
If the file containing the VCS cluster UUID (/etc/vx/.uuids/clusuuid) does not exist on any of the systems in the cluster, then use the uuidconfig.pl Perl script to configure the cluster UUID correctly using the -configure option.
 
# uuidconfig.pl [-rsh] -clus -configure [-force] [-use_llthost | sys1 [sys2...]

 

For the exact usage and further options please see the man page for "uuidconfig".

 

 

 

Applies To

Veritas Cluster Server version 5.1 or later

Issue/Introduction

Veritas Cluster Server (VCS) 5.1 onwards has introduced a new feature of cluster UUID (Universally Unique ID) . If a Cluster UUID is not present or does not match with that of other system nodes in the
VCS cluster, then VCS services will not be able to start on that system node. This feature is introduced to prevent system nodes from different clusters to mistakenly join into incorrect VCS clusters that they do not belong to.  If a cluster is being manually configured or a new node is being joined into an existing cluster, then it may be required to configure the VCS cluster UUID manually, else that particular system node will not be able to join into the cluster by starting the VCS cluster services. An error will be encountered in the VCS engine_A.log (/opt/VRTSvcs/log/engine_A.log) upon issuing the VCS 'hastart' command to start the VCS cluster services.  
Powered by Wolken Software