vSAN and vMotion Ping Health Check alarms in L3 networks

Products

• VMware vSAN

Issue/Introduction

Symptoms:
The following circumstances may cause vSAN and the vMotion ping health check to report errors even if the gateway is set on these vmknics for vSAN and vMotion traffic as described in Overriding the Default Gateway of a VMkernel Adapter:

• If there are multiple vmknics on cluster hosts. 
• vSAN and/or vMotion traffic are in separated L3 networks other than Management traffic.
• The default gateway is set on vmknic for the Management traffic.
• If the user doesn't set static routes on hosts for vSAN networks and vMotion networks as described in administrative manual.

Environment

VMware vSAN 6.6.x
VMware vSAN 6.7.x
VMware vSAN 6.2.x

Cause

This causes the vSAN ping health check not to bind to vmknic per its traffic tag.

Resolution

To resolve this issue, set static routes for vSAN networks and vMotion networks. 

To set static routes for vSAN networks and vMotion networks, see administrative manual.