Important Update: Cohesity Products Knowledge Base Articles
All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.
CVM: VMWare CFS clustered configuration is showing additional disk entries as disk.EnableUUID is not set to TRUE
Problem
The environment consists of a 4-node CVM/CFS VMWare cluster configuration. The server named "node-04" is showing additional disk entries for the same disks compared to the other clustered nodes.
In addition, VxVM disk flags 'lmissing' and 'udid_mismatch' are also shown.
node-04 # vxdisk listDEVICE TYPE DISK GROUP STATUS
sba-emm-app-pro_vmdk0_0 auto:sliced sba-emm-app-pro_vmdk0_0 mmdbdg20 online shared lmissing
sba-emm-app-pro_vmdk0_1 auto:sliced sba-emm-app-pro_vmdk0_1 mmdata1dg20 online shared lmissing
sba-emm-app-pro_vmdk0_2 auto:sliced sba-emm-app-pro_vmdk0_2 mmdatadg20 online shared lmissing
sda auto:LVM - - LVM
sdb auto:sliced - (mmdatadg20) online shared udid_mismatch
sdc auto:sliced - (mmdbdg20) online shared udid_mismatch
sdd auto:sliced - (mmdata1dg20) online shared udid_mismatch
Error Message
node-01 is showing less devices like node-02 and node-03:
# vxdisk -eo alldgs listDEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
sba-emm-app-pro_vmdk0_0 auto:LVM - - LVM sda -
sba-emm-app-pro_vmdk0_1 auto:sliced sba-emm-app-pro_vmdk0_0 mmdbdg20 online shared sdc -
sba-emm-app-pro_vmdk0_2 auto:sliced sba-emm-app-pro_vmdk0_1 mmdata1dg20 online shared sdd -
sba-emm-app-pro_vmdk0_3 auto:sliced sba-emm-app-pro_vmdk0_2 mmdatadg20 online shared sdb -
Cause
As this is a VMWare environment, is the 'disk.EnableUUID' parameter set to TRUE in the VMware Virtual Machine Properties for the disks?
In this instance, the 'disk.EnableUUID' is NOT set for node-04, hence the additional DMPNODE entries shown by vxdisk list.
In VMWare environment it is essential to set the disk.EnableUUID parameter for each VM to "TRUE".
This step is necessary so that the VMDK always presents a consistent UUID to the VM (Virtual Machine), thus allowing the disk to be correctly presented to VxVM and Veritas DMP.
Solution
For each of the virtual machine nodes (VMs) that will be participating in the cluster, follow the steps below from the vSphere client, to enable UUIDs for disks on a virtual machine
1. Power off the guest.
2. Select the guest and select Edit Settings.
3. Select the Options tab on top.
4. Select General under the Advanced section.
5. Select the Configuration Parameters... on right hand side.
6. Check to see if the parameter disk.EnableUUID is set, if it is there then make sure it is set to TRUE.
If the parameter is not there, select Add Row and add it.
7. Power on the guest.
With the VMWare disk.EnableUUID paramater set for node-04, disk groups import successfully once the GUEST is booted.
node-04 # vxdisk listDEVICE TYPE DISK GROUP STATUS
sba-emm-app-pro_vmdk0_0 auto:LVM - - LVM
sba-emm-app-pro_vmdk0_1 auto:sliced sba-emm-app-pro_vmdk0_0 mmdbdg20 online shared
sba-emm-app-pro_vmdk0_2 auto:sliced sba-emm-app-pro_vmdk0_1 mmdata1dg20 online shared
sba-emm-app-pro_vmdk0_3 auto:sliced sba-emm-app-pro_vmdk0_2 mmdatadg20 online shared
NOTE: No additional dmpnodes are visible by the "vxdisk list" output