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

Disabling firewall on a cluster fails in NSX (52902)

Last Updated: 3/30/2018Categories: TroubleshootingTotal Views: 2607Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Disabling firewall on a cluster fails.

The GUI does not show any errors.

The vsm.log file contains entries similar to:

018-02-05 15:03:27.201 UTC INFO http-nio-127.0.0.1-7441-exec-33504 FirewallUIFacade:877 - Calling enable[false] cluster API...
2018-02-05 15:03:27.203 UTC INFO http-nio-127.0.0.1-7441-exec-33504 FirewallServiceImpl:2764 - Enable firewall[false] called for cluster[domain-c40]
2018-02-05 15:03:27.206 UTC INFO http-nio-127.0.0.1-7441-exec-33504 FirewallServiceImpl:2777 - Firewall is already disabled on {

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This is a design issue where the interaction between network fabric and firewall module was purely based on per host basis.

The only message forwarded from network fabric module was that host has been prepared (vibs installed and messaging completed).

The firewall module was always making the assumption, to enable firewall for the given host by default. If the user has disabled firewall on cluster, new host added to the cluster get the firewall enabled by default. There is no straight forward way via UI to disable firewall on newly added host.

Impact / Risks

Disabling the firewall fails.

Resolution

This issue is resolved in VMware NSX for vSphere 6.3.6, available at VMware Downloads.

Workaround

To work around this issue, use REST API to enable then disable the firewall on the cluster:

For example:

[root@DEVLGRE3NSX001 ~]# curl -k -H "X-NSX-Username:admin" -X PUT "http://localhost:7441/api/4.0/firewall/domain-c40/enable/true";
ENABLED_INSYNC
[root@DEVLGRE3NSX001 ~]# curl -k -H "X-NSX-Username:admin" -X PUT "http://localhost:7441/api/4.0/firewall/domain-c40/enable/false";
INSTALLED_DISABLED

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
确定 ESXi 主机关闭电源或重新启动的原因 (1019238)

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

KB
•
在客户连接中对许可证密钥管理进行故障排除 (2143936)

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 NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant