vSAN Cluster hosts not communicating with vCenter 6.5

[cru306]

vSAN Cluster hosts not communicating with vCenter 6.5 and this issue resolved after vCenter reboot only ,

I am using the vSAN cluster with following combination and continuously facing issue

vCenter 6.5

Esxi 6.5

Horizon view 7.8

[TheBobkin]

Hello cru306​,

I would advise when posting here (or anywhere really) to start by providing a lot more information - vague questions tend to get ignored or relatively useless responses (as there is no context):

- What exact build of vCenter and ESXi are in use?(e.g. ESXi 6.5 P04, build:15256549 as opposed to "Esxi 6.5")

- You stated this issue is recurring

          - Is it the same host every time?

          - Is it all hosts in the cluster or just one?

          - Is this occurring for other hosts managed by this vCenter that are not in this vSAN cluster?

- When did this start occurring and what changes preceded this?

- Is there any pattern to the occurrence that you can determine? (e.g. every time you do back-ups or deploy a large pool of VMs)

- Have you opened a Support Request with VMware GSS in relation to this? If no, why not and if yes, what were their findings?

Bob

[cru306]

Hi Bob,

Thanks for your reply .. Below my inputs.

What exact build of vCenter and ESXi are in use?(e.g. ESXi 6.5 P04, build:15256549 as opposed to "Esxi 6.5")

vCenter 6.5 - 8024368

ESXi, 6.5.0 - 7388607

- Is it the same host every time?

Random not single host , but in another non vSAN cluster will be fine,

Is it all hosts in the cluster or just one?

all host

- When did this start occurring and what changes preceded this?

I am try to create the new VM but it is stuck in 5% so I am restarting the vCenter services first, then incase any issue rebooting the vCenter,

Is there any pattern to the occurrence that you can determine? (e.g. every time you do back-ups or deploy a large pool of VMs)

We are using linked clone so we just disable the provisioning only,

Have you opened a Support Request with VMware GSS in relation to this? If no, why not and if yes, what were their findings?

Yes, they also recommended to reboot the vCenter only,

Note :we have storage controller firmware outdated alert only

We are using two 10GB NIC , One for VDI , another one for vMoteion & vSAN (50% 50% network resource share)

I am suspecting the network but network utilization not full load.

Regrdsa

Chandru GR.

[TheBobkin]

Hello Chandru,

Thanks for that clarifying information.

I took a look at the notes on the Support Request and based on those + the information above this doesn't appear to be a vSAN-specific issue - that being said, there are no logs attached to that case so it's not currently possible to check whether the cluster is configured correctly etc. .

Thus I would advise moving this question to vSphere/vCenter sub-forum (or asking a Mod to if unable) and following my colleagues advice of opening a Support Request with the relevant team (vCenter - System Management) should this issue re-occur.

Bob

[scott28tt]

I have already suggested he keep everything into a single thread - there were 3 separate threads opened across the vSphere and vSAN forum areas.

This is the active thread in the vSphere forum: During the DRS Fully automated state getting multiple alert in vCenter 6.5