Collector Gives Inaccurate CPU Count When Environment Includes Servers Using Hyperthreading
search cancel

Collector Gives Inaccurate CPU Count When Environment Includes Servers Using Hyperthreading

book

Article ID: 341423

calendar_today

Updated On:

Products

VMware

Issue/Introduction

When Capacity Planner Collector collects inventory data in an environment that includes servers using hyperthreading, the Collector occasionally does not get an accurate CPU count.

Environment

VMware Capacity Planner 2.1.x
VMware Capacity Planner 2.5.x
VMware Capacity Planner 2.6.x

Resolution

This problem can occur if you have a server that includes one or more physical processors, but because of hyperthreading, you have double the number of logical processors. For example, the CPU count for a server reads as 4 instead of 2. This situation occurs if you have not enabled Windows Management Instrumentation (WMI ) for the Collector and target machines. It can also occur if you select the Only Use Registry option on the Collect tab of the Inventory Options dialog box (Admin > Options > Module Settings > Inventory), or if a firewall blocks your access to the servers to be assessed. Other conditions might cause an inaccurate count as well.

The workaround, in most cases, is to use a WMI-compliant host for the collection. Use the default setting on the Collect tab of the Inventory Options dialog box - Automatic Detection of Method (WMI then Registry), and resolve the firewall issues if possible. If the firewall is your issue, you have to open a port to allow WMI traffic to pass through to the remote systems.