"Error: VMDg:online:GetDgGuid failed" reported when attempting to online VMDg resource in Veritas Cluster
Article ID: 100050769
Updated On:
Description
Error Message
The VMDg_A.log available at %VCS_HOME%/log would report errors below:
VMDg::online:GetDgGuid failed. Error: 40
VMDg::online:Init diskgroup : Unrecognized error code. 00000028
Cause
The above errors indicate an issue with the configuration for the VMDg resource. The possible cause for the issue being that the DiskGroup has disk(s) that are shared across the cluster nodes and the DG is imported as a Dynamic DG (Secondary),
Hence, the DG is not recognized by the VMDg agent for VCS
NOTE: VMDg resources are designed to recognize DGs that are imported only as Dynamic (Cluster)
Resolution
1) Run vxdg list on the node where the disk group is imported. The output as below will show the details of the Diskgroup type.
Perform the below steps to change it to a Cluster Diskgroup
a) Deport the Disk Group:
b) Import the Disk Group as Dynamic (Cluster)
OR
Run the below command to change the DG type using command line:
vxdg -g import -s
Sample output
3) Run the vxdg list command to ensure that the Disk Group type is changed to Dynamic (cluster)
4) Now probe the VMDg resource in VCS and it should now come online.
Note: If this is a Campus Cluster or a GCO (Global Cluster Option) where each node/site is utilizing replication between storage, it will be necessary to ensure the Diskgroup on both nodes (Campus Cluster) or all sites (GCO) show as Dynamic (Cluster) when running the vxdg list command and verifying the Disk Group Type value.
Issue/Introduction
At times, when attempting to online a Volume Manager Diskgroup (VMDg) resource in Veritas Cluster (VCS) on Windows platform, it would fail to come online and also report a red question for the problem VMDg resource. This does not apply for VMNSDg resources, only VMDg resources.
