A simple note to delete vSAN datastore from ESXi host while it’s not parts of the cluster. The error “Found host(s) esxi.mydomain.lab participating in the vSAN service which is not a member of this host’s vCenter cluster“, indicates that the host is still a member of vCenter cluster.

The issue comes out when I was playing with vSAN configuration on vShpere 7. I’ve deleted the cluster without removing the cluster hosts properly.

Delete vSAN Datastore in ESXi Host

It’s not possible to delete a vSAN datastore from Datastore section of ESXi host. I’ve tried but the Delete button was false.

But we can remove the ESXi host from vSAN cluster then the vSAN datastore will be removed automatically.

Let’s delete vSAN Datastore using the following steps.

Enable SSH on ESXi host where you deploy VCSA

1. Log in ESXi host suing IP address and root and password.
2. Click Manage on Navigator part.
3. Select the Services tab.
4. Select TSM-SSH service from the list.
5. Push Start button on top.

Make sure the SSH is enabled and you are able to connect to ESXi host via SSH.

Related Article: How To Fix No Healthy Upstream VCenter 7 Issue?

You can enable ESXi SSH through vCenter as well.

Connect with root user to ESXi host using PuTTy, command prompt, Terminal, PowerShell, Chrome SSH or whatever you have.

 ssh root@192.168.20.101

Now, type the following command to check out the vSAN Datastore.

esxcli vsan storage list

If you have any storage linked to vSAN, delete it with the following command. Make sure you select the right UUID of the vSAN Datastore.

esxcli vsan storage remove -u "UUID"

The command will list all the vSAN mounted storage on ESXi host. If you don’t have any mounted datastore like my lab, just type the following command to remove the host from vSAN cluster.

esxcli vsan cluster leave

The task has been completed. Now you should have a healthy ESXi host with any notifications or the “Found host(s) esxi.mydomain.lab participating in the vSAN service which is not a member of this host’s vCenter cluster” error.

I hope this has been informative and solved the issue you have with your VMWare vSphere Lab. If you want more about vSAN Datastore and Disk group.

The post How to Delete vSAN Datastore Correctly appeared first on TECHNIG.

When you encounter no healthy upstream error, it means that the vCenter is not up and ready yet. Just wait a few minutes before connecting to vCenter via a web browser.

But every no healthy upstream error is because of an unprepared vCenter. There might be some issue that does not allow the services of vCenter to be running properly.

Fix vCenter 7 no healthy upstream error?

There is another guide to help you fix no healthy upstream error of vCenter 7. It might be occurred after upgrading vCenter 6.7 to vCenter 7.

1. Shutdown the vCenter
2. Upgrade the VM hardware version
3. Edit settings > VM Options > General Options > Select VMware Photon OS

Note: make sure you have allocated enough memory and CPU for the vCenter 7 virtual machine. The vCenter 7 is CPU and memory hungry.

Read the related community post on vMware forum.

Related article: Setup a Penetration Testing Lab.

Hardware Requirements for the vCenter Server Appliance

When you deploy the vCenter Server appliance, you can select to deploy an appliance that is suitable for the size of your vSphere environment. The option that you select determines the number of CPUs and the amount of memory for the appliance. The hardware requirements for a vCenter Server appliance depend on the size of your vSphere inventory.

The upgrade of the appliance is a migration of the old version to the new version, which includes deploying a new appliance of version 7.0. You can deploy the new vCenter Server appliance on an ESXi host 6.5 or later, or on a vCenter Server instance 6.5 or later. Your system must also meet specific software and hardware requirements.

Hardware Requirements for a vCenter Server Appliance

Note: If you want to add an ESXi host with more than 512 LUNs and 2,048 paths to the vCenter Server inventory, you must deploy a vCenter Server appliance for a large or x-large environment.

Let us know if you still have issues with vCenter no healthy upstream.

The post How to Fix no healthy upstream vCenter 7 Issue? appeared first on TECHNIG.