Stale health check warnings persist in the vCenter Server UI and cannot be cleared when the associated uplinks have been removed from the VDS.
search cancel

Stale health check warnings persist in the vCenter Server UI and cannot be cleared when the associated uplinks have been removed from the VDS.

book

Article ID: 449260

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The vSphere Client UI displays a general health check warning, but all granular health status details indicate a "Normal" state. There is no functional impact on the environment or data path. The issue is purely cosmetic, resulting in uncleared stale warnings in the UI.

Steps to reproduce the issue:

  1. A host is configured with four uplinks: two for general traffic (Management/vMotion/VM Network/Backups) trunking multiple VLANs, and two exclusively for vSAN traffic utilizing a single VLAN.
  2. All four uplinks are initially connected to a single VDS.
  3. VDS Health Check is enabled, which immediately and correctly triggers warnings regarding asymmetric VLAN availability across the four uplinks.
  4. The two vSAN uplinks are subsequently migrated to another VDS.
  5. VDS Health Check is re-enabled on the original VDS.
  6. The original VLAN warnings of the migrated uplinks persist in the vCenter UI for these hosts, despite all health check details reporting a clean status.

Environment

VMware vCenter Server

Cause

The original design of the VDS health check feature did not account for the specific use case where uplinks are removed, causing the system to retain and display orphaned health check data. 

Resolution

The fix will be released in a upcoming patch versions of 8.0 and 9.1. If you experience this issue, please open a support case with Broadcom: Contact Broadcom support