Unable to vMotion virtual machines between hosts with the alarm "vMotion: MTU check".
search cancel

Unable to vMotion virtual machines between hosts with the alarm "vMotion: MTU check".

book

Article ID: 415366

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  •  The vMotion ping test is unsuccessful between the source and destination hosts, using this command:
              vmkping -I <vmotion network vmk>  <destination vMotion IP>  
      If the vMotion vmk is configured with vmotion tcp/ip stack, use below command:
              vmkping -I <vmotion network vmk> <destination vMotion IP> -S vmotion         
         
  •  vMotion traffic is not passing one of the vmnics.
  •  vSAN network alarm 'vMotion: MTU check (ping with large packet size)' is seen on UI at cluster level.
  •  Network connectivity is restored after failover to unused vmnic on teaming for vMotion network.

Environment

  • VMware vSphere ESXi
  • VMware vCenter Server

Cause

The VLAN used for vMotion is missing on the switchport for the vmnic in active use.

Resolution

Trunk the VLAN used for vMotion on the switchport connecting to the vmnic

Additional Information

Powered by Wolken Software