vMotion network configuration finding for vSphere Distributed Switch is listed in Skyline Health findings.
Expanding this finding shows the following information:
A mismatch between the MTU settings of a vMotion vmkernel adapter and a vMotion Ditributed Switch connected to it might lead to a failure in vMotion operations. Both MTU settings must match so that vMotion Operations can execute successfully. Click the Ask VMware link above for more details and a resolution.
VMware vCenter Server
VMware vSphere ESX
Skyline Health will report an MTU mismatch when the configured MTU of a vMotion VMkernel adapter differs from that of its connected vSphere Distributed Switch (VDS).
There are two scenarios where this finding can be reported:
In this situation, change the MTU on the vMotion VMkernel adapter to 9000. Ensure that Physical Switchports connected to the Physical Network adapters [vmnicX] attached to this VDS can support 9000 MTU.
In this situation, change the MTU on vMotion VMkernel adapter to 1500.
Initiate a RETEST of Skyline Health by Clicking on vCenter Server -> Monitor -> Skyline Health -> RETEST.
If the MTU on the vSphere Distributed Switch has to be changed, please refer to Enabling Jumbo Frames on virtual switches
To change the MTU on a VMkernel adapter, following steps can be performed:
*NOTE: Ensure that no vMotion operation is in progress before changing the MTU.
'⋮' for the vMotion VMkernel adapter and click on Edit.esxcli network ip interface set --mtu=<mtu_value> --interface-name=vmk<#>