In this post, we are going to see How to clear UDID mismatch in VCS Cluster(online thinrclm udid_mismatch)?
We are doing this activity in VCS 3 node cluster with Linux environment.
In VCS Cluster udid_mismtach might lead to disk failures.
Error:
#vxdisk -l alldgs list | grep udid emc4_184a auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch emc4_184b auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch emc4_184c auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch
Resolution:
Verify the fencing disks using “vxdisk -l alldgs list | grep udid” command to know whether it’s having udid_mismatch or not. Using that command we came to know all the three fencing disks has udid_mismatch.
#vxdisk -l alldgs list | grep udid emc4_184a auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch emc4_184b auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch emc4_184c auto:cdsdisk - (vxfendg) online thinrclm udid_mismatch
Verify the all 3 disks udid and udid_asl values are different or not.
Using below command we found that, udid & udid_mismatch values are different.
#vxdisk -v list emc4_184a | grep -i udid flags: online ready private autoconfig udid_mismatch coordinator thinrclm udid: EMC%5FSYMMETRIX%5FF000197500111%5F110184A008 tag: udid_asl=EMC%5FSYNNETRIX%5F000195702690%5F9002F64000
Like the above use the same command to check udid & udid_mismatch values for another two disks(emc4_184b, emc4_184c)
Then check whether the fencing keys on the coordinator disks are fine using below command
#vxfenadm -s /dev/vx/rdmp/emc4_184a
All the fencing keys are looking good on the coordinator disks.
Finally, command to clear the udid_mismatch flag from all 3 fencing disks.
#vxdisk updateudid emc4_184a #vxdisk updateudid emc4_184b #vxdisk updateudid emc4_184c
Confirm udid_mismatch has been cleared or not using the below command.
#vxdisk -o alldgs list | grep -i udid
