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

VMs lose network connectivity after vMotion in an NSX-T environment (74767)

Last Updated: 9/27/2019Categories: InformationalTotal Views: 4699Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Virtual Machines permanently lose network connectivity after a vMotion

On the vSphere Client the vNIC of the VM shows "Connected" to a Logical Switch

The issue is temporarily resolved if the vNIC is disconnected and reconnected however the issue recurs on the next vmotion

The issue is permanently resolved if the VM is added to and removed from the DFW Exclusion List

At the time of the vmotion, the ESXi host contains logging similar to this

/var/log/vmkernel.log

2019-08-29T14:51:08.163Z cpu53:3795337)NetX Classifier: need to register a classifier without a vif ID
2019-08-29T14:51:08.163Z cpu53:3795337)NetX DVF: error while refreshing SI filter: Bad parameter
2019-08-29T14:51:08.163Z cpu53:3795337)Failed to read config of filter nic-3798473-eth3-vmware-si.12: Bad parameter
2019-08-29T14:51:08.163Z cpu53:3795337)Failed to update vif id for filter () : Bad parameter

/var/log/cfgAgent.log

2019-08-29T14:51:08.163Z NSX 3795320 - [nsx@6876 comp="nsx-controller" subcomp="cfgAgent" tid="F93B2700" level="panic"] vsipfw: VsipFWIoctl.cpp:sendIoctl():67 ioctl cmd 30 on device /dev/nsx-vsip failed: Invalid argument
2019-08-29T14:51:08.163Z NSX 3795320 - [nsx@6876 comp="nsx-controller" subcomp="cfgAgent" tid="F93B2700" level="error" errorCode="DFWERR_FILTER_UPDATE_CONFIG"] dfw: Failed to update filter config: Invalid argument

Cause

This problem occurs due to a failure to handle dvfilter processing correctly and has been observed following NSX-T upgrade.

Resolution

This issue is resolved in VMware NSX-T Data Center 2.5, available at VMware Downloads.

Workaround

The issue can be permanently resolved by deleting and recreating the dvfilters associated with the VM vNICs.

To resolve individual VMs:
- Power off and power back on the VM (not a reboot)
or
- Add the VM to and remove from the DFW Exclusion List

To resolve all VMs:
Disable and re-enable the DFW
Note, enabling DFW may result in some TCP sessions being dropped and restarted where stateful rules apply.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
应用热修补程序后，Usage Meter 无法导出日志包并发送未加密的报告 (74693)

KB
•
ホット パッチを適用した後、使用量メーターがログ バンドルのエクスポートに失敗し、暗号化されていないレポートを送信する (74693)

Results 1-2 of 2

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