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

Guest Introspection VM disconnect on VDI infrastructure (67264)

Last Updated: 5/10/2019Categories: TroubleshootingTotal Views: 5650Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After upgrading NSX from 6.4.0 to 6.4.1, 6.4.2 or 6.4.3, you may encounter issues with Guest Introspection deployment status and VM connectivity with AV.
Intermittent Errors message may be seen on ESXi hosts "Guest Introspection Host Status".
If you have not recently upgraded, these errors may occur if there are a large number of VMs are on each host and if DRS is enabled.

Cause

The NSX Manager has a timeout of 30 seconds to get the update from MUX process on the ESXi host, when a configuration update has been applied.
The configuration update is applied to the namespace database, each VM has these since NSX 6.4.1, these updates are taking a large amount of time around 45 seconds or more to update all the VMs on that host.
Since this time is more than 30 seconds, the NSX Manager will reschedule the same update.
The ESXi host MUX process has no way of knowing that this is the same update, therefore it will push the update to all the VMs once again.
This means there will be another time out, lasting more than 30 seconds (NSX manager time limit) and it then goes into a loop.

This issue is dependent on the load and activity on the hosts, which means it is not consistent.
When this loop occurs, the MUX process is always busy and therefore unable to process events from VMs and that is why we are seeing the random disconnects.

Impact / Risks

The affected VMs were may not be getting scanned with AV.
This can be checked using the Eicar test on the affected VMs: http://2016.eicar.org/86-0-Intended-use.html
Remote may be unable to login to VDI desktops.
Slower VM connectivity may be observed from remote users.
There are usually more than 120 VMs per affected host. Please note, this figure includes powered off VMs.

Note: In NSX 6.4.4 and ESXi 6.5 P03 and 6.7,
- Max Powered on Virtual Machines per Host = 150
- Max Concurrent vMotions to or from a Host = 50
- Max Concurrent Virtual Machines Booting on a Host = 50
- Co-existence of powered off /on VMs: 250 (out of which 150 in powered on state (when there is no boot storm, bulk power-on recommended in batched of 50)

Resolution

This issue has been resolved in NSX 6.4.4.

Also improvements were made to ESXi 6.5 P03 and 6.7, therefore to gain the full benefit, it is recommended to upgrade to these ESXi versions also.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

NSX-V GI 6.4.4 Improvements

Additional Resources

KB
•
VCHA 环境中 VCSA 时间同步配置的注意事项 (68030)

Result 1 of 1

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

Take Our Survey

Support Assistant