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

When configuring an IPset as part of a Security Group in the NSX DFW, if the firewall rule is applied to the Security Group it is not published to designated hosts/virtual machines (51537)

Last Updated: 11/20/2019Categories: InformationalTotal Views: 4261Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

You have created an "IP Set" inside the NSX Manager. This "IP Set" is applied to a "Security Group" using the NSX Service Composer. In the DFW, this "Security Group" has been selected in the "Applied To" field. After publishing, you see these symptoms:

The firewall rules traffic that should be getting caught and processed by the DFW fails.

A search for the rules applied to an expected virtual machine through the vsipioctl getrules -f <nic_filter> command reveals the intended rule is missing from the virtual machine.

Purpose

This article is to document a frequently replicated symptom and explain why it happens.

Cause

IP Sets are not supported in the "Applied to" field of the DFW.

The "Applied to" field of the DFW supports only the following selected objects:

Cluster

Datacenter

Distributed Virtual Port Group

NSX Edge

Network

Virtual Machine

vNIC

Logical Switch

Security Group

Host System

For more information, see the NSX-v 6.3 Administration Guide.

While all of the above items are supported in the "Applied to" field, it is possible to configure unsupported items indirectly through the DFW interface. For instance, an IP or MAC set can be applied to a given Security Group, and then apply the DFW to that Security Group. This results in an unsupported configuration and NSX Manager does not push the firewall rules to the VMs/hosts.

Resolution

To resolve this issue, to keep the firewall rules applied to the selected IPs in the IP Set and ensure they are pushed to the hosts/VMs, ensure those rules are "Applied to" the Distributed Firewall as a whole or one of the listed supported values.

Identify the rule in the DFW list of the Web Client.

Click the pencil icon in the "Applied To" field.

Select the checkbox beside "Apply this rule on all clusters on which the Distributed Firewall is installed."

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
•
Download and Install VMware Fusion (2014097)

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

Take Our Survey

Support Assistant