"VCS WARNING V-16-1-50832 Cluster <node> is not in RUNNING state" appears when attempting to perform a switch

book

Article ID: 100011514

calendar_today

Updated On:

Cause

This message may appear in a global cluster if there is a problem with network connectivity between the sites.

Resolution

1) Make sure that each cluster has valid a ClusterAddress:
haclus -display | grep ClusterAddress 
If a valid ClusterAddress is not present, use haclus to configure one:
haclus -modify ClusterAddress "10.12.240.109" 

 
2) If you have not already done so, run /opt/VRTSvcs/bin/gcoconfig on each cluster. This will add a WAC resource on each cluster and bring it online. 

 
3) If you have not already done so, a dd an ICMP Heartbeat to each cluster.

For example: 
 
Cluster 1 
hahb -add Icmp 
hahb -modify Icmp ClusterList -add london_clus 
hahb -modify Icmp Arguments "10.12.252.105" -clus london_clus 

Cluster 2
hahb -add Icmp 
hahb -modify Icmp ClusterList -add frankfurt_clus 
hahb -modify Icmp Arguments "10.12.240.109" -clus frankfurt_clus 

 


Issue/Introduction

# ./hagrp -switch oragrp -any -clus vvr2_cluster
VCS WARNING V-16-1-50832 Cluster vvr2_cluster is not in RUNNING state

Powered by Wolken Software