VCS ERROR V-16-1-52569 [Licensing] Unable to find a valid base VCS license key (Remote Build)

book

Article ID: 100021013

calendar_today

Updated On:

Resolution

Unable to join a new node to the existing cluster, because no valid base VCS license key found.
 

 

 
ISSUE AS REPORTED:
 

 
When starting the new node cluster, it will not join because of  no valid key found.
 

 
# /opt/VRTS/bin/hastart
 

 
# tail -f /var/VRTSvcs/log/engine_A.log
 
VCS NOTICE V-16-1-10467 Replaying broadcast queue. snapped_membership: 0x7 current_membership: 0x7 current_jeopardy_membership: 0x0
 
VCS NOTICE V-16-1-10322 System sys_name  (Node '2') changed state from REMOTE_BUILD to RUNNING
 
VCS ERROR V-16-1-52569 [Licensing] Unable to find a valid base VCS license key (Remote Build)
 

 

 

 
SOLUTION:
 

 
Create a backup folder for the current installed licenses on each cluster node.
 

 
# cp -pR /etc/vx/licenses/lic /etc/vx/licenses/lic_bkp
 

 
# cd /etc/vx/licenses/lic
 

 
# rm *.vxlic
 

 
# /opt/VRTS/bin/vxlicinst ( Install the license key )
 

 

 
To update volume manager
 

 
# vxdctl license init
 

 

 

 
To update licensing information in a running cluster
 
-------------------------------------------------------------------------------
 

 
a.) Update system-level licensing information on all nodes in the cluster:
 

 
# /opt/VRTS/bin/hasys -updatelic -all
 

 
You MUST update licensing information on ALL nodes before proceeding to the next step.
 

 
b.) Update cluster-level licensing information:
 

 
#  /opt/VRTS/bin/hastart
 

 
#  /opt/VRTS/bin/haclus -updatelic
 

 
# /opt/VRTS/bin/hastatus -sum
 

 
The above commands should show the expected output of the cluster.
 

 

Issue/Introduction

VCS ERROR V-16-1-52569 [Licensing] Unable to find a valid base VCS license key (Remote Build)
Powered by Wolken Software