OPERATIONAL DEFECT DATABASE
...
...
On the vCenter UI, you observe high CPU usage numbers from your NSX Controllers (80-100%)The folder /var/log/nvcpli located on the NSX Controllers contains a huge amount of small log files that contain the following entries: 2018-01-29 17:36:26,758 INFO CLI started for single command with -c option2018-01-29 17:36:26,764 INFO Executing command: show control-cluster logical-routers interface 0xaaaa xxxxxxxxxxxxxxa2018-01-29 17:36:27,251 INFO CLI exited with return code: 02018-01-29 17:36:27,326 INFO CLI started for single command with -c option2018-01-29 17:36:27,395 INFO Executing command: show control-cluster logical-routers interface-summary 0xaaaa2018-01-29 17:36:27,497 INFO CLI started for single command with -c option2018-01-29 17:36:27,499 INFO Executing command: show control-cluster logical-routers interface 0xaaaa xxxxxxxxxxxxxa2018-01-29 17:36:27,638 INFO CLI started for single command with -c option2018-01-29 17:36:27,646 INFO Executing command: show control-cluster logical-routers routes 0xaaaa2018-01-29 17:36:27,758 INFO CLI exited with return code: 02018-01-29 17:36:27,976 INFO CLI exited with return code: 02018-01-29 17:36:28,144 INFO CLI exited with return code: 0
This article addresses network stability issues that may occur due to high CPU utilization within environments where NSX and vRNI are used together for data collection and analysis.
The high CPU Utilization occurs within the logrotate process for the NSX controllers. The logrotate utilizes all the available CPU resources almost exclusively, affecting all other processes on the controllers.Logrotate addresses and works on log files found in /var/log/nvpcli. This directory contains numerous amount of files. vRNI uses a cli mechanism to pull network details and information from the NSX controllers, this creates a new small log file which is created almost every second.
Can affect network stability / connectivity in environments when the controllers fail.If connections to the controllers are lost, the production might go down due to controllers outage. Below are the following primary features that might get impacted by turning off NSX Controller, VM-VM path may not work for VMs which are behind the DLR which has learnt routes.Events related to NSX Controller and control plane won’t be opened/closed.NSX Controller runtime state w.r.t Join and Majority status.Primary owner of logical switch and DLR won’t be visible.
Upgrading to 3.8.0 release will fix the issue
简体中文：从 vRNI 代理查询 mac 表时 vRNI 3.x 导致 NSX Controller 的 CPU 利用率达到 100%
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
