First run this command to dump the instance names for all instances in the system: and now just execute the command (replace ‘lsi_mr3-544a842043a54a00/LSI Incorporation’ with the Key Value Instance you received as the output of previous command) : That’s it 🙂 Any questions, comments? Just ping me.
One of the many steps performed when you try to unstretch vSAN cluster is disabling stretch cluster mode in all ESXi hosts. It’s done automatically so you don’t need to worry about that but in my case I needed to do that manually. When you run into an below error during ova deployment, definitely it’s […]
In this blog post i will describe what is going on in the background when ‘./sos –stretch-vsan’ command is initiated. It’s not a rocket science because all these steps are done when you stretch cluster manually but i thought it can be helpful for someone who never did that. Some tasks are described as ‘all […]
This time very short and quick post:) If you see such error message (as below) in vCenter when adding or replacing VMware vSAN 6.7 Witness Appliance, just remember: CHECK YOUR vSAN Witness Appliance VERSION AND BUILD. The witness host must be capable of running the same version of ESXi as vSAN data nodes. 2019-11-08T18:24:31.613Z info […]
vSAN Health Check plug-in is not available and displays an error: “The vCenter server is not responding, please check your setup (status code 503)” Starting vsan-health service manually ended with general error: “An error occured while starting service” Group permission on /etc/vmware-vpx/ssl is correct. This issue is not related with Dell OMI in this version of […]
Next book to the virtualization’s required reading list added: VMware vSphere 6.5 Host Resources Deep Dive