Blue banner vSAN notifications in vCenter seen on the vSAN hosts or cluster Summary tab

Products

• VMware vSAN

Issue/Introduction

vCenter is below version 8.0U1

vSAN Health Service is reporting all healthy for the vSAN cluster

One of the below blue banner vSAN notifications is seen in vCenter on either the vSAN hosts or cluster Summary tab

• Host is in VC cluster but not in vSAN cluster.
• Host is in vSAN cluster but not in VC cluster.
• vSAN host cannot communicate with other hosts in the cluster.
• Host observes a vSAN node which doesn't belong to VC cluster.
• vSAN network is not configured.
• No local disks or SSDs configured for vSAN.
• vSAN disks need to be upgraded.
• vSAN datastore XXXX in cluster YYYY in datacenter ZZZZ does not have capacity
• Host is in a vSAN cluster but does not have vSAN service enabled

Environment

VMware vSAN & vCenter below 8.0U1

Cause

These are the old deprecated vpxd check logic for potential vSAN Configuration issues pre 6.0U1 that didn't exist in vSAN Health service. All these vpxd checks are now and have been part of vSAN Health Service for some time.

Under rare conditions these old deprecated vpxd check logic alerts can be triggered due to ESXi and vCenter getting out of sync with each other regarding the vSAN cluster configuration. 

Resolution

Upgrade vCenter to 8.0U1 or higher as the vpxd check logic for these potential vSAN configuration issues has been dropped from vCenter as they're now monitored via vSAN Health Service.
Note: If the environment is VxRail or SDDC a full environment upgrade to 8.0U1 may be required. 

If a vCenter upgrade is not possible you can safely ignore the alerts or make a small vSAN cluster change like un-tagging/retagging the vmk for vSAN on one of the hosts in the cluster or a change in the fault domain to trigger vCenter to recalculate the vSAN configuration between vCenter and ESXi.