vSAN Proactive Network Performance Test reporting Health Status as Failed
search cancel

vSAN Proactive Network Performance Test reporting Health Status as Failed

book

Article ID: 447345

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

Details of this Proactive test are documented in KB 326905

vSAN Proactive Network Performance Test reporting Health Status as Failed and reports 0 Received Bandwidth (Mb/s) between different hosts.

Environment

vSAN (all versions)

Cause

This issue can occur due to vMotion / Management and vSAN VMkernel adapters being configured to use the same IP subnet and TCP/IP stack (multihoming), which is an unsupported configuration on ESXi.

Multi-homing resulting in asymmetric routing has also been reported to cause VM snapshot stuns and quiesce timeouts on vSAN as per KB 437724.

Resolution

To resolve this issue, reconfigure the VMkernel adapters so that vMotion, Management and vSAN reside on different IP subnets.

Identify the overlapping subnets using esxcfg-vmknic -l.

Modify the IP address or Netmask of the vMotion, Management or vSAN interfaces to ensure they are on unique subnets.

Rerun the vSAN Proactive Network Performance Test to verify connectivity.

Note: Refer to KB 318546 for detailed information on why multihoming is unsupported on ESXi.