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

Drop counters in DFW for packets increments in presence of fragmented packets in NSX-v (67214)

Last Updated: 2/22/2019Categories: TroubleshootingTotal Views: 3491Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The packet drop counters are incrementing.

Running the getfilterstat -f nic-73312875-eth0-vmware-sfw.2 command displays output similar to:

For example:

/bin/vsipioctl getfilterstat -f nic-73312875-eth0-vmware-sfw.2
PACKETS IN OUT
------- -- ---
v4 pass: 1741866240 2246525043
v4 drop: 258604075 68962297 <<<<< Drops are incrementing and REASON for Drops does not account for the drop packets

v6 pass: 62677697 42678808
v6 drop: 0 36
v6 reject: 3 0

BYTES IN OUT
----- -- ---
v4 pass: 602021574988 3301412816442
v4 drop: 0 0  <<<<<<<  Byte Drops are not incrementing

v6 pass: 6145541059 3204135532
v6 drop: 0 0
v6 reject: 240 0

Cause

This issue occurs because when a fragmented packet is received, a copy of the packet is queued and original packet is dropped.

Note: This is where the drop counter increases.

When all the fragmented packets have been received, the fragmented packets are reassembled and run through the firewall. After the firewall result on this packet, the packet is re-fragmented as it was initially received and all the fragmented packets are sent on their way, hence you see that nothing was dropped.

Resolution

This is a known issue affecting VMware NSX for vSphere 6.3.6.

Currently, there is no resolution.

Workaround

To work around this issue, upgrade to NSX for vSphere 6.4.0 or later.

Note: Starting in NSX for vSphere 6.4.0 release, a counter is introduced which tracks these drops so that they can be accounted for.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant