what is impact of correcting LUN HLU conflicts/ mismatch in Hyper-V environment?
We have a 18 node cluster environment Cisco UCS Blades where each blade installed with Windows 2012 r2 and Hyper-V enabled.
Initially multiple luns were mapped to these 18 node cluster as shared luns. Later we faced VM reboots which were running on blade servers. Later we found out, all the shared luns mapped to 18 node cluster had HLU mismatch, which may possibly the issue behind VM/Host reboots.
Now as a first method to correct he HLU mismatch, we are planning to remove each lun from storage group and remap and correct/assign HLU IDs of the luns, which is a disruptive procedure and time consuming.
As a second method, creating a new storage group and add required luns to storage groups correcting HLU IDs without adding any host to storage group. Once HLU ID correction is done and ready we can add remove the host from old SG and add to newly created SG with HLU ID corrected.
If there is a change in HLU IDs, What will be the impact on Hyper-V cluster nodes? While the system boots whether it rescan same luns and cluster will be up or any re-config of disks to cluster required>>