The CVM service group goes in to faulted state after you restart the management console node
When the Cluster> reboot command is run, sometimes the CVM service group goes into faulted state on the node that was restarted. This issue is usually caused by a minor number conflict between the CVM shared disk group objects, such as volumes, volume sets or Replicated Volume Groups (RVGs) and the private disk group objects. Confirm that the minor numbers of the private disk group objects do not overlap with the CVM disk group objects on the joining CVM slave node.
https://www.veritas.com/support/en_US/article.000107801
Workaround:
To bring the CVM service group online
- Run the following command on the node where CVM service group is in faulted state
# hastop -local
- Offline all the file systems. Run the following command from another node where the management console is online.
Storage> fs offline <file system name>
- Deport all the disk groups using the following command:
# vxdg -s deport <disk_group>
- Import all the disk groups using the following command:
# vxdg -s import <disk_group>
- Start Veritas Cluster Server (VCS).
# hastart
If the file system does not come online, then run the following command to make all the file systems online:
Storage> fs online <file system name>