Pinging with jumbo frames fail even with correct configuration in ESXi 5.5 and reports the error: sendto() failed (Message too long)
search cancel

Pinging with jumbo frames fail even with correct configuration in ESXi 5.5 and reports the error: sendto() failed (Message too long)


Article ID: 343871


Updated On:


VMware vCenter Server VMware vSphere ESXi


  • When using the vmkping command to test jumbo frame connectivity, it fails with an error similar to:

    sendto() failed (Message too long)

  • The vmkping command includes the do not fragment flag and the maximum test size of 8972 bytes. The sytax is similar to:

    # vmkping -s 8972 -d x.x.x.x

    Where x.x.x.x is the IP address of a device on the network that supports an MTU of 9000.

  • All network devices in the layer-2 path is configured correctly for MTU 9000
  • More than one VMkernel port exists with an IP address in the same subnet as the destination that is being pinged
  • This behavior does not occur in ESXi 5.1 and earlier releases
  • When conducting a packet capture on the VMkernel interface that is used to ping, attempted ICMP ECHO requests are not sent out of the VMkernel interface, (nor are they making it to physical network adapter to pass to the physical network.)


VMware vCenter Server 4.1.x
VMware vCenter Server 5.1.x
VMware ESX Server 3.0.x
VMware VirtualCenter 2.5.x
VMware vSphere ESXi 6.0
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Embedded
VMware vCenter Server 4.0.x
VMware vCenter Server 5.5.x
VMware ESX 4.0.x
VMware vCenter Server 6.0.x
VMware vCenter Server 5.0.x
VMware ESXi 4.0.x Installable
VMware ESXi 4.0.x Embedded
VMware ESXi 4.1.x Installable
VMware ESXi 3.5.x Embedded
VMware ESX Server 3.5.x
VMware vSphere ESXi 5.1
VMware vSphere ESXi 6.5
VMware vSphere ESXi 5.5
VMware VirtualCenter 2.0.x
VMware ESX 4.1.x
VMware vCenter Server 6.5.x
VMware ESXi 3.5.x Installable


In some situations, MTU 9000 traffic may fail out one or more VMkernel interfaces when multiple VMkernel ports exist in the same subnet as the destination device that is being communicated with. This can occur if MTU is changed multiple times.

Note: This KB article refers to a specific defect where all physical networking and vSphere configuration is correctly configured for Jumbo Frames. The sendto() failed (Message too long) message can be an indication of a genuine configuration problem and all components along the network path must be thoroughly checked.


This is a known issue affecting ESXi 5.5.

Note: Be cautious when working with VMkernel ports used for iSCSI or NFS traffic. Ensure that the virtual machines are migrated, or powered off prior to deleting VMkernel ports.

To work around this issue, delete the VMkernel interfaces and then re-create without changing the MTU more than once.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
Testing VMkernel network connectivity with the vmkping command
Enabling Jumbo Frames on virtual distributed switches
vmkping コマンドを使用した VMkernel ネットワーク接続のテスト