Hi Zahid,
dgdisabled flag can occur due to any error that prevents further configuration changes on the disk group. For example, this can occur if no good disks are found during the disk group import operation, if no valid configuration copies are found on the disks in the disk group, or if writes to all configuration copies fail during an update to the disk group configuration
The dgdisabled error flag indicates that configuration changes on a disk group are disabled
The dgdisabled error flag displays when the Veritas Volume Manager configuration daemon, vxconfigd loses access to all enabled configuration copies for the disk group. Configuration copies let you back up and restore all configuration data for disk groups, and for objects such as volumes that are configured within the disk groups. Loss of access can occur if power is disrupted or a network cable is disconnected. To recover from loss of access, fix any disk connectivity issues, then deport and re-import the disk group.
Now from VCS prospective, a diskgroup resource can fault because of multiple reasons, can list couple of them here
1. dg unable to import (while onlining)
2. dg deported while VCS was running (manual deport or storage access is lost while dg was imported)
3. resource contention when dg agent is unable to monitor diskgroup resource
Beginning with the Storage Foundation and High Availability (SFHA) Solaris 6.0 release, a node can join the cluster even if there is a shared disk group that is in the DGDISABLED state. In earlier releases the node failed to join the cluster.
G
