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

vNICs are disconnected after NSX is uninstalled from ESXi (74556)

Last Updated: 5/6/2021Categories: AlertsTotal Views: 4793Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

After NSX 6.4 is uninstalled from an ESXi host, you see the following symptoms.

vNICs are disconnected on the host.

vNICs cannot be manually connected.

NSX VIBs have been successfully uninstalled from the host.

In vmkernel.log, you see entries similar to:

2019-08-26T12:59:05.858Z cpu0:497596)Net: 2524: connected Win2012R2-2.eth0 eth0 to vDS, portID 0x7000014
2019-08-26T12:59:05.858Z cpu0:497596)Net: 3215: associated dvPort 0 with portID 0x7000014
2019-08-26T12:59:05.858Z cpu0:497596)DVFilter: 3595: Could not find filter 'vmware-sfw'
2019-08-26T12:59:05.858Z cpu0:497596)DVFilter: 5605: Failed to add filter vmware-sfw on vNic 0 slot 2: Not found
2019-08-26T12:59:05.858Z cpu0:497596)WARNING: Net: 3261: DVFilterActivateCommon failed for port 0x7000014: Failure
2019-08-26T12:59:05.858Z cpu0:497596)Net: 3734: dissociate dvPort 0 from port 0x7000014
2019-08-26T12:59:05.858Z cpu0:497596)Net: 3740: disconnected client from port 0x7000014

Cause

The symptom occurs because dvfiltertable entries are not removed from a host which NSX VIBs are uninstalled from.

Impact / Risks

VMs lose network connectivity.

Resolution

Currently, there is no resolution.

Workaround

Before moving the ESXi out of NSX clusters, run the following command on the ESXi host.

vsipioctl clearallfilters -Override -a vmware-sfw

Note:
The command disables DFW. Do not run the command while VMs with DFW attached is running.
The command must be run before uninstalling NSX because the command is only available when NSX is installed.

If you have moved the ESXi out of NSX cluster without running the command, reboot the ESXi host to recover from the symptom.

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

VMware NSX Data Center for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX Data Center for vSphere 6.4.x

Take Our Survey

Support Assistant