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 Publish tasks fail with "Firewall provisioning failed on Host host-XXXX for reason XXXXXX:failed to parse config" (57194)

Last Updated: 8/5/2021Categories: Total Views: 4474Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

You have DFW rules created on the "Partner Services" section which contain multiple services under a single rule.

You restart the the vShield-Stateful-Firewall service, and now firewall publish tasks succeed.

You see error messages similar to the following:

vmkernel.log

2018-04-12T18:39:14.262Z cpu4:8432502)WARNING: Heap: 3867: Could not allocate 299008 bytes for dynamic heap vsiHeap.8432502. Request returned Admission check failed for memory resource
2018-04-12T18:39:34.282Z cpu4:8498110)WARNING: Heap: 3867: Could not allocate 4096 bytes for dynamic heap worldGroup.8498111. Request returned Admission check failed for memory resource
2018-04-12T18:39:34.282Z cpu4:8498110)WARNING: Heap: 3867: Could not allocate 4096 bytes for dynamic heap worldGroup.8498111. Request returned Admission check failed for memory resource

vsm.log

2018-06-07 16:08:51.859 CDT INFO taskScheduler-10 EventBsdFtrMgrImpl:284 - Transactionally updated resource: host-XXXXX, with feature status: [resourceId : null, featureId : com.vmware.vshield.firewall, featureVersion : 5.5, status : YELLOW, installed : true, errorStatus : ]
2018-06-07 16:08:51.893 CDT INFO taskScheduler-10 EventBsdFtrMgrImpl:284 - Transactionally updated resource: host-XXXXX, with feature status: [resourceId : null, featureId : com.vmware.vshield.firewall, featureVersion : 5.5, status : YELLOW, installed : true, errorStatus : ]

Solution

This issue occurs when there are multiple services defined in a single Partner Services Distributed Firewall rule AND the rule has multiple security groups in its source or destination. If a publish task is attempted, the new ruleset will be pushed, however the overall memory consumption of vsfwd on esxi will increase. The memory steadily increases with each subsequent firewall publish task until the memory cannot be increased, thus resulting in a publish failure.

This is caused by a small memory leak which will increase the overall memory consumption of the vsfwd process on the ESXi host. Restarting the Firewall service on ESXi will clear vsfwd process memory and set the overall consumption back to a stable level.

This issue will be resolved with the release of NSX 6.4.2

Workarounds:

Restart the firewall service on esxi when a firewall publish failure is observed.
# /etc/init.d/vShield-Stateful-Firewall restart

Redesign the Partner Services firewall rules so that no single rule has multiple services configured.

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
•
在 VCSA 6.5.x 升级后部署 OVF 期间出现“此版本的 vCenter Server 不支持部署 OVF 模板 (This version of vCenter Server does not support Deploy OVF Template)”错误 (2151085)

Results 1-2 of 2

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.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

VMware NSX for vSphere 6.0.x

Take Our Survey

Support Assistant