Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Packet drops observed on vmxnet3 when packet length greater than vNIC's MTU (75213)

Last Updated: 8/20/2021Categories: TroubleshootingTotal Views: 34361Language:
English

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Symptoms

Packet drops increase when vmxnet3 is used on vsphere67u2 or later.

To get vmxnet3 stats, run the following command in an SSH session to the ESXi host managing the VM in question:

net-stats -l

From the output of the above command, note the PortNum and SwitchName values that correlate with your VM, and substitute their values in the below command:

vsish -e cat /net/portsets/<SwitchName>/ports/<PortNum>/vmxnet3/rxSummary

Example:

vsish -e cat /net/portsets/DvsPortset-0/ports/67108902/vmxnet3/rxSummary
stats of a vmxnet3 vNIC rx queue {
...
number of packets dropped due to pkt length exceeds vNic mtu:462727 <=== this counter increases
...

Cause

This issue occurs because in vSphere 6.7 Update 2, MTU check was enforced on packets on receive path to not allow non-LRO (Large Receive Offload) packets greater than vNIC MTU. This limit was not enforced in previous releases.

Resolution

To resolve this issue, config options are provided in vSphere 6.7 P01 at two different granularities.
Note: The default will still be to enforce a stricter MTU check.

Use one of these options to re-enable the previous behavior (that is, to avoid the MTU check):

Host-wide config option:

esxcli system settings advanced set -o "/Net/Vmxnet3NonTsoPacketGtMtuAllowed" -i 1
Note: This configuration is applicable over all vmxnet3 vNICs (host wide). This setting will be then applied to each VM that will be powered on after making this change

OR

vNIC specific config option:

Use ethernet0.rxAllowPktGtMtu = "1" in the .vmx file:

Where, "ethernet0" should be replaced by the specific vNIC on which the configuration is to be applied.
Please use the VMware KB article below to follow steps on how to:

Modifying advanced virtual machine settings using vSphere Client (1016098)
https://kb.vmware.com/s/article/1016098

Workaround

To work around this issue on vSphere 6.7 Update 2 and later versions, change the receiving vNIC's MTU (inside the VM) as per the packet lengths expected.

Example:
If vSwitch MTU is 9000, then packets up to 9000 bytes in length can be delivered as non-LRO packets. In this case, increase the vNIC's MTU to 9000.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
NSX ID 対応ファイアウォールが断続的に動作する。ESXi ホストで NSX コンテキスト エンジンが実行しない (76518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 6.7.x

Take Our Survey

Support Assistant