Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Firewall rules are not removed from dvfilter after disconnecting the VM from a logical switch (59614)

Last Updated: 3/1/2019Categories: TroubleshootingTotal Views: 7463Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After disconnecting a VM from an NSX-T logical switch and moving it to a regular distributed port group, some of the DFW rules remain in the dvfilter of the VM, potentially causing unexpected traffic blocks depending on the rules.

From the ESXi the VM lives on, obtain the VM's filter name by running:

>summarize-dvfilter

Note* The VM's filter name should look something like: nic-679396-eth2-vmware-sfw.2

From the ESXi, run the command

>vsipioctl getrules -f nic-######-eth2-vmware-sfw.2

The output still shows rules attached the vNIC that is no longer connected to a NSX-T logical switch

Cause

When a VM is disconnected from a Logical Switch, the filters associated should be removed, but are not

Impact / Risks

Depending on the firewall rules still being applied to the virtual nic of the VM, the user could experience unexpected traffic blocks.

Resolution

Resolution for this issue is expected in a future release for ESXi 6.5 and 6.7.

Workaround

Add the VM in the NSX-T DFW exclusion list before disconnecting it from the logical switch.
This ensures that all filters are removed from the VM prior to the Logical Switch disconnect, preventing the issue from occuring

Related Information

When a VM is disconnected from an NSX-T logical switch, the firewall rules should be cleared from the dvFilter associated to the VMNIC. We have identified that this is not happening in some specific ESXi versions.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
在 vSphere 群集之间迁移 NSX 组件虚拟机的步骤 (2148350)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant