clomd value change in all hosts


CLOMD value can be changed in multiple ways, here I am showing two ways i.e., powershell or cli



Take ssh to hosts in cluster and use below commands (6.x version) to fetch the clomd values and change the values:


           esxcfg-advcfg --get /VSAN/ClomRepairDelay

           esxcfg-advcfg --set <value in minutes> /VSAN/ClomRepairDelay   Ex: esxcfg-advcfg --set 240 /VSAN/ClomRepairDelay



  • Below command is used to get the current clomd values in hosts of the cluster: By default it is 60 mins, after any host that is placed in maintenance mode with ensure accessibility cross 60 mins, resync gets triggered and objects gets rebuild into other hosts of same vsan cluster.

          get-cluster clustername | Get-VMHost | Get-AdvancedSetting | ?{$_.Name -match "Repairdelay"} | Select-Object Entity,Name,Value | Sort-Object Entity

  • If there is a planned maintenance and you suspect the host doesn't come back within 60 mins, then you can change the value to more than 60 mins, in below example I have used 240 mins.

          get-cluster clustername | Get-VMHost | Get-AdvancedSetting | ?{$_.Name -match "Repairdelay"} | Set-AdvancedSetting -Value 240 -Confirm:$false

  • Below command can be used to reset the clomd value back to default i.e., 60 mins.

          get-cluster clustername | Get-VMHost | Get-AdvancedSetting | ?{$_.Name -match "Repairdelay"} | Set-AdvancedSetting -Value 60 -Confirm:$false


Replace the clustername mentioned in above commands with the cluster name you are using.


Note: CLOMD values take affect only after restarting the clomd service in all hosts of a specific vsan cluster, command as below:

 /etc/init.d/clomd restart

Leave a Reply