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 loss while using cSwitch and etherchannel (IP HASH and Source MAC Hash) (59800)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 5055Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

On ESXi hosts where:

The system is on ESXi 6.7

Using DVS 6.6  and using etherchannel

Standard Switch and etherchannel

Packet loss is observed when using multiple uplinks to many destination IP addresses

pktcap-uw --trace shows packets being dropped after

EtherswitchDispath

pktfree  <----

Cause

There is a problem with the teaming algorithm when queuing multiple packets at the same time. The drop happens when more than 1 packet at the same time attempts to communicate with multiple destinations over multiple network adapters. This mainly effects vSAN heartbeating UDP traffic. This can effect VMs that attempt the same kind of traffic pattern.

Note: This only effects ESXi 6.7 when using cSwitch teaming policy IP HASH or Source MAC Hash. cSwitch is used by default in 6.7 for standard switches and VDS 6.6

Impact / Risks

Packet loss when using this configuration

Resolution

Fix in 6.7 U2 or the patch referenced in PR 2221818

Workaround

There are two different workarounds available:

a) Remove etherchannel and use teaming policy "route based on source port"

b) Revert to etherswitch:

Put host to maintenance

Enable etherswitch - Disable cswitch

esxcli system settings kernel set -s "netVSSUseEtherswitch" -v true

Reboot host

Verify that etherswitch is enabled

esxcli system settings kernel list -o "netVSSUseEtherswitch"
Name Type Configured Runtime Default Description
-------------------- ---- ---------- ------- ------- --------------------------------------------------------------------------
netVSSUseEtherswitch Bool true TRUE FALSE Use etherswitch instead of cswitch to back the virtual standard switch.

Move host out of maintenance

Note: This issue should be resolved in 6.7 U2. Please see PR 2221818

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
•
使用 Blast 连接到 Horizon View 虚拟机时报错：SSL 会话无效 (2088354)

KB
•
SSL セッションが無効になる - Blast を使用して Horizon View 仮想マシンに接続している場合 (2088354)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSAN 运行状况服务 - 容错域数量异常 (2130581)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant