Difference in the LSOM.lsomComponentDedupScanType setting between upgraded and newly built hosts in the vSAN hybrid cluster.
search cancel

Difference in the LSOM.lsomComponentDedupScanType setting between upgraded and newly built hosts in the vSAN hybrid cluster.

book

Article ID: 390318

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

  • The purpose of the article is to rectify settings of the vSAN advance parameter  LSOM.lsomComponentDedupScanType 

Symptoms :

  • While adding a newly built host to a vSAN hybrid cluster, a discrepancy in the configuration of the LSOM.lsomComponentDedupScanType parameter was observed. On the new host, the value of this parameter is set to 2, whereas on the existing hosts in the vSAN hybrid cluster, it may be set to 0.

Environment

VMware vSAN

Cause

  • The value of LSOM.lsomComponentDedupScanType parameter by default is 2
     
  • The LSOM.lsomComponentDedupScanType parameter may have been set to 0 to fix a known performance issue in the vSAN 6.0 hybrid cluster.

  • The value of LSOM.lsomComponentDedupScanType may differ while introducing newly built host in vSAN hybrid cluster.

Resolution

The hybrid vSAN cluster can continue to operate with the default value of LSOM.lsomComponentDedupScanType as 2 

The difference between the existing value 0  and the default value 2 does not impact performance.

Additional Information

The command to check LSOM.lsomComponentDedupScanType :

esxcfg-advcfg -g /LSOM/lsomComponentDedupScanType

Powered by Wolken Software