vMotion Network is not pingable from the jump server and vice versa

Products

• VMware vSphere ESXi

Issue/Introduction

• The vMotion network is unable to ping the Jump server and default gateway.
• The vMkernel is not able to send the traffic to the upstream.

Environment

VMware vSphere ESXi

VMware vSphere vCenter

Cause

This issue can occur if the static routes are not configured for the vMotion network in ESXi host.

Resolution

To configure a static route to a  gateway/router for the vMotion network:

1. Open a console to the ESXi or ESX host. For more information, see Using ESXi Shell in ESXi
2. In ESXi 7.0, and ESXi 8.0:
    
   • To add a static route, run the command:
     esxcli network ip route ipv4 add --gateway xx.xx.xx.xx -n 0.0.0.0/0 -N vmotion
        
   • To list the route, run the command:
     esxcli network ip route ipv4 list
     
     
     
3. When finished, check the host's current routing table with the esxcfg-route -l -N vmotion command,  the vMotion static routes display in the output.

Note :  xx Represents the default gateway ipv4 address.

Additional Information

For more information : Configuring static routes for vmkernel ports on an ESXi host