|Article Number: 504053||Article Version: 5||Article Type: Break Fix|
VxRail E Series Nodes,VxRail Appliance Series,VxRail Appliance Family
From cluster -> monitor -> vSAN ...
For stretched clusters, see https://support.emc.com/kb/487348.
The MTU Check (ping with large packet size) warning can be caused by mismatched MTU between the switch and the vSphere environment.
What can cause a failure is if the vmknic has an MTU of 9000 and then the physical switch enforces an MTU of 1500. This is because the source does not fragment the packet and the physical switch will drop the packet.
Faulty network hardware (node sfp, network card, cable, switch port/sfp, etc) have also been known to trigger the MTU Check (ping with large packet size) warning.
Troubleshooting steps: if no issues found with MTU size... 2. Check switch ports and/or esx hosts for crc errors. Reference https://kb.vmware.com/kb/2108285 for more information on this Health Check Test. Check MTU Settings: Check vSphere MTU settings: Check the MTU setting for the DVS: DVPort ID In Use Client Check the MTU on the vmnics: Check for crc errors: sw0# show int stats detail int Ten 2/0/34
1. Check MTU size on top-of-rack switch, and on all vsphere components; DVS, vmk(s), vmnics.
Check top-of-rack switch MTU settings per the switch vendor documentation.
Check MTU setting for the node/portgroup referenced in the MTU warning message:
[vxrail@vxnode03:~] esxcfg-vmknic -l | grep vmk2
vmk2 16384 IPv4 192.168.121.3 255.255.255.0 192.168.121.255 00:50:56:6f:e3:c9 1500 65535 true STATIC
vmk2 16384 IPv6 fe80::250:56ff:fe6f:e3c9 64 00:50:56:6f:e3:c9 1500 65535 true STATIC, PREFERRED
[vxrail@vxnode03:~] esxcfg-vswitch -l
DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
VMware HCIA Distributed Switch 4352 9 512 1500 vmnic1,vmnic0
0 1 vmnic0
1 1 vmnic1
4101 1 vmk1
8205 1 vmk0
16400 1 vmk2
8208 1 vmk3
[vxrail@vxnode03:~] esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:01:00.0 ixgbe Up 10000Mbps Full 2c:60:0c:af:ee:de 1500 Intel Corporation Ethernet Controller X540-AT2
vmnic1 0000:01:00.1 ixgbe Up 10000Mbps Full 2c:60:0c:af:ee:df 1500 Intel Corporation Ethernet Controller X540-AT2
If MTU config appears to be ok, check for crc errors.
For checking crc errors on a switch, refer to the switch vendor documentation for the appropriate command.
For Brocade for example:
Interface TenGigabitEthernet 2/0/34 statistics (ifindex 8993701921)
Packets 7165702349 4603884761
Bytes 8633656075975 2910244530614
Unicasts 7154910149 4565459180
Multicasts 10782937 24109494
Broadcasts 9263 14316087
Errors 0 0
Discards 691 643
Overruns 0 Underruns 0
64-byte pkts 0
Over 64-byte pkts 932783488
Over 127-byte pkts 587058087
Over 255-byte pkts 19035776
Over 511-byte pkts 93628206
Over 1023-byte pkts 631386310
Over 1518-byte pkts 4901810482
Mbits/Sec 0.000000 0.000456
Packet/Sec 0 0
Line-rate 0.00% 0.00%
Check for crc errors on esx host:[vxrail@vxnode03:~] esxcli network nic stats get -n vmnic1NIC statistics for vmnic1 Packets received: 135817879 Packets sent: 82253912 Bytes received: 156239259329 Bytes sent: 53856798358 Receive packets dropped: 0 Transmit packets dropped: 0 Multicast packets received: 637031 Broadcast packets received: 0 Multicast packets sent: 0 Broadcast packets sent: 0 Total receive errors: 32614 Receive length errors: 1866 Receive over errors: 0 Receive CRC errors: 32596 Receive frame errors: 0 Receive FIFO errors: 0 Receive missed errors: 0 Total transmit errors: 0 Transmit aborted errors: 0 Transmit carrier errors: 0 Transmit FIFO errors: 0 Transmit heartbeat errors: 0 Transmit window errors: 0If crc errors are found, refresh (rerun) the command every few seconds to see if the crc errors are incrementing. If they are, proceed to troubleshoot the network hardware (node sfp, network cable, switch sfp/port, etc) to isolate the issue to a specific component and replace the faulty component. Once the faulty component has been replaced, run the above command every few seconds to confirm that the crc errors are no longer incrementing. The crc error counter on esx is only cleared by a reboot, so although the existing errors may still be present, the important thing is that they stop incrementing.Once the issue has been determined and resolved, rerun the vsan Health Check tests to confirm that the MTU Check (ping with large packet size) warning is no longer present.
if no issues found with MTU size...
2. Check switch ports and/or esx hosts for crc errors.
Reference https://kb.vmware.com/kb/2108285 for more information on this Health Check Test.
Check MTU Settings:
Check vSphere MTU settings:
Check the MTU setting for the DVS:
DVPort ID In Use Client
Check the MTU on the vmnics:
Check for crc errors:
sw0# show int stats detail int Ten 2/0/34