VMware Cloud Community
ManivelR
Hot Shot
Hot Shot
Jump to solution

vsan health alarm 'host maintenance mode and decommission state'

Hi All,

I have a 6 node VSAN cluster.During maintenance,I have taken only one ESXi host reboot(before that,I enabled the ESXi host in to maintenance with the below command line).

esxcli system maintenanceMode set -e true -m ensureObjectAccessibility

Now Im seeing "Host maintenance mode warning" alert and when we try to put the ESXi host in to maintenance again via vCenter server,Im seeing VSAN data migration option as "cannot be completed.Taken esxi reboot as well but no luck.

rest all other 5 nodes are running good.

What actions we need to take to fix this warning issue ?

pastedImage_0.png

pastedImage_1.png

1 Solution

Accepted Solutions
TheBobkin
Champion
Champion
Jump to solution

Hello Manivel,

This is not just a warning, that node is not providing and storage or data to the cluster and this should be resolved.

This issue can be resolved with one line from the CLI:

# localcli vsan maintenancemode cancel  

(MUST be localcli - not esxcli)

Bob

View solution in original post

3 Replies
TheBobkin
Champion
Champion
Jump to solution

Hello Manivel,

This is not just a warning, that node is not providing and storage or data to the cluster and this should be resolved.

This issue can be resolved with one line from the CLI:

# localcli vsan maintenancemode cancel  

(MUST be localcli - not esxcli)

Bob

ManivelR
Hot Shot
Hot Shot
Jump to solution

Great Bob.

It has been fixed.Thanks for your prompt response.

Thank you,

Manivel RR

0 Kudos
TheBobkin
Champion
Champion
Jump to solution

Necroing my own post here with some more updated information (as folks are still referencing it, noted from @Dieter-VKGroup kudoing it today).

 

Just a small update: while running 'localcli vsan maintenancemode cancel' will still clear a vSAN Decom state it isn't actually the advisable option - what I have noted in the field is that often there is some process from vCenter still trying to put the node in MM and it can actually go back into vSAN Decom state after some time by itself again.

So in order to properly clear this (for good) is to just give it what it wants, while the node is still in vSAN Decom state, migrate any powered-on VMs off the node then place it in MM with 'No Action' option then immediately take it out of MM, this will ensure it won't try to proceed and be back in vSAN Decom state.

0 Kudos