CPU value different in 720x and 721x for Windows sensor

Technote (troubleshooting)


Problem(Abstract)

CPU value differ in TADDM version 720x and 721x when running the Windows sensor

Symptom

During a CCMDB CI audit it showed that the CPU counts different between Actual and Authorized CI in TSRM. When compared to the actual TADDM values, found that different versions of the TADDM showed different counts for the same ComputerSystem

For example, according to the system itself, when checking the server has 8 CPUs.

TADDM scan in 721FP3 reports 8 CPU, but TADDM scan in 720FP6 for example only reports 2 CPUs.


Cause

This has been identified as a product defect under APAR IV01439


Diagnosing the problem

Test case scenario when issue could be found:

Run a discovery against a Windows 2008/Vista machine that has CPU(s) with several cores. After the discovery you should now see the correct number of the CPU's in the Product Console in the "Number of Logical CPUs" property (e.g. if the machine has 2 CPUs with 4 cores each, then the value should be equal to 8). You may also do a discovery of an already discovered target that shows the wrong value for CPU as in the above scenario (target has 8, but only 2 are shown by scan) to see if the value now is assigns correctly after the fix (migrating to TADDM version 721 or above)


Resolving the problem


We have fixed this in taddm 7.2.1.


According to apar:

APAR NAME: IV01439
For the below operating system levels, when the number of physical and logical
processors is not the same, TADDM is reporting the physical number as number of
CPUs. This is due to the fact that, starting from Windows Vista and Windows 2008,
Microsoft has introduced the NumberOfLogicalProcessors attribute in the WMI
Win32_ComputerSystem class. In Windows 2003 and Windows XP this same change was
introduced with hot fixes 932370 and 936235 respectively. The existing WMI
attribute NumberOfProcessors, which contained the number of logical processors,
changed its meaning starting from the above levels of Windows Operating system.
It now contains the number of physical processors. The new attribute,
NumberOfLogicalProcessors, in the WMI Win32_ComputerSystem class, must be used
instead to retrieve the previous available information. TADDM will accommodate
this change and ensure to display the number of logical processors according to
the information available. In this way the NumCPUs will consistently contain the
number of logical CPUs.


Product Alias/Synonym

TADDM

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Application Dependency Discovery Manager

Software version:

7.2.1

Operating system(s):

AIX, Linux, Windows

Reference #:

1625494

Modified date:

2014-01-21

Translate my page

Machine Translation

Content navigation