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

High CPU Utilization in NSX Controllers (52581)

Last Updated: 11/16/2018Categories: TroubleshootingTotal Views: 4913Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

NSX Controllers show high CPU Utilization.

CPU Utilization Graphs on the vCenter for the Controller Appliance show a linear increase up to the current Value.

vRealize Network Insight might be used in the environment.

The top command (with option 'R' to sort for Utilization), executed on the NSX Controller root shell, shows that the CPU is consumed almost entirely by various logrotate processes.

The command strace -p <logrotate-pid> -f -o /var/tmp/strace_out on the NSX Controller root shell shows that logrotate is working on files located in /var/log/nvpcli.

Cause:

vRealize Network Insight uses a CLI method to pull relevant Network Information from the NSX Controllers. For example, it logs in to the NSX Controller, runs and parses a cli command, logs off again.
This procedure creates a new log file per action on the NSX Controller, up to one new log file per second. The logrotate process is unable to cope with the large amount of individual log files created.

Note: vRNI is just an example for a software triggering this issue; other VMware or third party software, or simple scripts used to log in to the NSX Controllers in short intervals, would trigger the same behavior.

Solution

This issue is resolved in:
VMware NSX for vSphere 6.4.1, available at VMware Downloads.
VMware NSX for vSphere 6.3.7, available at VMware Downloads.

To work around this issue if you do not want to upgrade:

Disable the vRNI Controller polling (or other Software / Scripts using the CLI method to fetch Information from the Controllers); this should prevent the creation of the large volume of log files.

Delete the log files from /var/log/nvpcli periodically. CPU Utilization should go back to normal levels after a few minutes. Controller reboot or redeployment is not required.

Polling Information from the NSX Controllers can be disabled on vRNI with the following steps:

Navigate to Accounts and Data Sources page on Settings.

Click on the Edit data source icon on right side of the NSX Manager.

Unselect the Enable NSX Controller.

Click on Submit button.

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)

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.3.x

Take Our Survey

Support Assistant