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

NSX DFW System Events triggered by vmotion in NSX 6.4.2 and 6.4.3 environments (60435)

Last Updated: 8/5/2021Categories: AlertsTotal Views: 1501Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following System Events are raised on the NSX Manager

Major - Failed to apply firewall rule to vnic.
Critical - Failed to apply Firewall rules to host.

NSX Manager log:
2018-10-29 08:14:45.945 GMT INFO messagingTaskExecutor-8 EventServiceImpl:119 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] [SystemEvent] Time:'Thu Nov 29 08:14:45.941 GMT 2018', Severity:'Major', Event Source:'host-64', Code:'301032', Event Message:'Failed to apply firewall rule to vnic.', Module:'vShield Firewall', Universal Object:'false'
2018-10-29 08:14:45.953 GMT INFO messagingTaskExecutor-9 EventServiceImpl:119 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] [SystemEvent] Time:'Thu Nov 29 08:14:45.951 GMT 2018', Severity:'Critical', Event Source:'host-64', Code:'301034', Event Message:'Failed to apply Firewall rules to host.', Module:'vShield Firewall', Universal Object:'false'

ESX vsfwd.log:
2018-10-29T08:14:45Z vsfwd: [WARN] cannot update rule hit count due to mismatch gennum 1542927847105 <> 0.
2018-10-29T08:14:45Z vsfwd: [ERROR] failed to initialize rule hit count of filter nic-28903582-eth1-vmware-sfw.2: mismatching ruleset
2018-10-29T08:14:45Z vsfwd: [WARN] failed to update rule hit count of filter nic-28903582-eth1-vmware-sfw.2

These events correspond to the time a VM was vmotion'd.

Cause

On NSX 6.4.2 and NSX 6.4.3 these errors are triggered on vmotion of a VM.
The problem is due to a sequencing issue related to the VMs DFW filter.
This causes vsfwd on the destination host to program DFW rules on the VMs filters before vmotion has completely finished.
This results in the filters generation number being set to 0.
vsfwd processing of stats is impacted for this filter.
DFW core functionality is not impacted

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.4

Workaround

The issue can be worked around by performing any publish operation on the DFW post vmotion.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant