VCS service group shows as autodisabled even after it is autoenabled

book

Article ID: 100008322

calendar_today

Updated On:

Description

Error Message

# hagrp -online DB01 -sys clds012
VCS WARNING V-16-1-10159 Group XXXX is auto-disabled in cluster. This can happen if group is not probed on all alive nodes in group's SystemList or VCS engine is not running on all alive nodes in group's SystemList

# hares -online MaestroVol -sys clds012
VCS WARNING V-16-1-10282 Group XXXX for resource MaestroVol is auto-disabled in cluster

Cause

The reason for this error is that HAD on the active node is showing that the service group on NodeA is auto disabled. Even though VCS is not running on NodeA, the Had daemon on Node B sees an auto enable state from Node A.

Resolution

To resolve this issue, run an hagrp autoenable on NodeA from NodeB:

# hagrp -autoenable XXXX -sys NodeA

This will now allow the XXXX service group to be onlined successfully on Node B.

 

Applies To

This issue pertains to a two node or multi-node VCS cluster. Node B is running Had, but node Node A is not. Both nodes are in gab membership.

The first step is to attempt to autoenable the service group on Node B:

# hagrp -autoenable XXXX -sys NodeB

Then run an hastatus -sum to determine the status:

# hastatus -sum

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State         

B  ClusterService  clds011              Y          N               OFFLINE       
B  ClusterService  clds012              Y          N               ONLINE        
B  XXXX            NodeA              Y          Y               OFFLINE       
B  XXXX            NodeB              Y          N               OFFLINE

It is shown that the service group is enabled on Node A, but not on Node B.

Issue/Introduction

When trying to either online a VCS service group or a VCS resource, the command output is returning an error: