VMware Cloud Community
bclark_hyperic
Enthusiast
Enthusiast
‎04-11-2008 10:47 AM
Jump to solution

Issue with number of CPU's discovered by Hyperic

Hello,

I found something a little confusing and inconsistent. When looking at one Windows 2003 platform in Hyperic, I noticed that it showed the CPU speed in the main platform view as "8 @ 1995 MHz". This looks correct to me, as this is a two CPU system, with each CPU having four cores.

However, on another Windows 2003 platform that I have, that I know has a single quad-core CPU, Hyperic shows the CPU Speed as "2793 MHz". I would think it should show it as "4 @ 2793 MHz".

Under the "Platform Services Health" section of the main platform view, on the server that shows as having 8 CPU's, it shows a group of CPU's. On the platform that Hyperic believes has only one CPU, it shows only one CPU, not a group.

I have looked through a number of my platforms, and some show correctly and some do not. I haven't been able to figure out a pattern.

This is more than a cosmetic issue, as it appears that Hyperic is unaware of the other CPU's, and they cannot be monitored, etc.

Adding...
It seems that Hyperic has a problem with Windows Systems with more than 4 CPU's. On my dual processor quad-core systems (8 CPU's), the discovery process seems to have gone awry.

Each CPU Core in the Services inventory (and the CPU "auto-group" for that platform) after the fourth CPU will actually show up as 12 CPU's, as shown below. I don't know where the weird characters come from. That is straight from Hyperic.

Win32 CPU 8 (1995Mhz 
”
 Xeon)
Win32 CPU 8 (1995Mhz Ð# x 2 Xeon)
Win32 CPU 8 (1995Mhz p
š
x Xeon)
Win32 CPU 8 (1995Mhz @
Ę
x 2 Xeon)
Win32 CPU 8 (1995Mhz 0¡ Xeon)
Win32 CPU 8 (1995Mhz Ð ç x 2 Xeon)
Win32 CPU 8 (1995Mhz  Xeon)
Win32 CPU 8 (1995Mhz è
‹
Xeon)
Win32 CPU 8 (1995Mhz ¨ Xeon)
Win32 CPU 8 (1995Mhz 
Ш
2 Xeon)
Win32 CPU 8 (1995Mhz H Xeon)
Win32 CPU 8 (1995Mhz Intel Xeon)

Anyone else have this issue? Anyone know how to fix it?

Thanks,
Brian

Message was edited by: bclark
0 Kudos
1 Solution

Accepted Solutions
dougm_hyperic
VMware Employee
VMware Employee
‎05-01-2008 06:06 PM
Jump to solution

Hey Guys,
The name issue has been fixed for 3.2.4, ticket contains a link to the sigar .dll with the fix:
http://jira.hyperic.com/browse/HHQ-2040

You'll have to manually delete the CPU services with the bogus names.
As for the number of CPUs, the physical number is what should be displayed.
There's some fixes underway in the 1.5.1 version of sigar for that.

View solution in original post

0 Kudos
7 Replies
excowboy
Virtuoso
Virtuoso
‎04-13-2008 08:09 AM
Jump to solution

Hi Brian,

I remember another user with the same issue:
http://communities.vmware.com/message/1925960#1925960

Looks like the latest HQ Agent doesn't fix the issue and looks like only Quad Core CPUs are affected. I think the problem is SIGAR related.
If I understand this posting correctly, informations about are gathered from Windows Registry:
http://communities.vmware.com/message/1925009#1925009

Maybe you can have a look at the registry:
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0

or run

java -jar hq-product.jar -m discover

again to see the output of the autodiscovery and especially of the CPU information.

Mirko
0 Kudos
bclark_hyperic
Enthusiast
Enthusiast
‎04-15-2008 12:04 PM
Jump to solution

Ok. I ran java -jar hq-product.jar -m discover on one of my platforms that has a quad-core Xeon processor.

The output is below. Nothing jumped out at me. It does get the correct CPU speed, it just doesn't recognize the four cores. Windows certainly recognizes the four cores, or at least Task Manager does.

Anyone else see anything?

Thanks,
Brian


C:\Program Files\hyperic-hq-agent-3.2.2-noJRE\pdk\lib>java -jar hq-product.jar -m discover
7 servers detected

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER Win32 WindowsServer [/]
AIID.....localhost Win32 WindowsServer
config...
product..{}
metric...{}
control..{}

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
[No services discovered]

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER Win32 ProcessServer [/]
AIID.....localhost Win32 ProcessServer
config...
product..{}
metric...{}
control..{}

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
WINDOWSERVER Win32 ProcessServer services:
WINDOWSERVER Win32 CPU 1 (3192Mhz Intel Xeon)
config...
product..{cpu=0}
metric...{}
control..null
rt.......null

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER Win32 NetworkServer [/]
AIID.....localhost Win32 NetworkServer
config...
product..{}
metric...{}
control..{}

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
WINDOWSERVER Win32 NetworkServer services:
WINDOWSERVER Win32 Network Interface eth0 (ethernet) (BASP Virtual Adapter)
config...
product..{interface=eth0}
metric...{}
control..null
cprops...{mtu=1500, flags=UP BROADCAST RUNNING MULTICAST, address=10.xxx.xxx.xxx
, broadcast=10.xxx.xxx.xxx, mac=xxxxxxxx, netmask=255.255.255.0}
rt.......null
WINDOWSERVER Win32 Network Interface lo0 (loopback) (MS TCP Loopback interface)
config...
product..{interface=lo0}
metric...{}
control..null
cprops...{mtu=1520, flags=UP LOOPBACK RUNNING, address=127.0.0.1, netmask=2
55.0.0.0}
rt.......null

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER Win32 FileServer [/]
AIID.....localhost Win32 FileServer
config...
product..{}
metric...{}
control..{}

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
WINDOWSERVER Win32 FileServer services:
WINDOWSERVER Win32 File System C:\ (local/NTFS)
config...
product..{mount=C:\}
metric...{}
control..null
rt.......null
WINDOWSERVER Win32 File System D:\ (local/NTFS)
config...
product..{mount=D:\}
metric...{}
control..null
rt.......null

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: localhost Net Services [C:\]
AIID.....localhost Net Services
config...
product..{}
metric...{}
control..null

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
[No services discovered]

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER HQ Agent 3.2.2 [C:\Program Files\hyperic-hq-agent-3.2.2-noJRE\pd
k\lib] (Hyperic HQ monitor Agent)
AIID.....CAM Agent Server
config...
product..{}
metric...{}
control..null
cprops...{JavaVersion=10.0-b19, JavaVendor=Sun Microsystems Inc., UserHome=C:\D
ocuments and Settings\bclark, SigarVersion=1.5.0.1, version=3.2.2, SigarNativeVe
rsion=1.5.0.1}

Runtime Resource Report...none

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Server: WINDOWSERVER .NET 2.0 [C:\WINDOWS\Microsoft.NET\Framework]
AIID.....C:\WINDOWS\Microsoft.NET\Framework
config...
product..{}
metric...{}
control..null

Runtime Resource Report...
Platform=Win32, fqdn=WINDOWSERVER.* (Microsoft Windows 2003)
config...
product..null
metric...{platform.log_track.level=Warn, platform.log_track.eventlogs=System, pl
atform.log_track.enable=true, platform.config_track.enable=true}
control..null
cprops...{cpuSpeed=3192 MHz, secondaryDNS=10.xxx.xxx.xxx, defaultGateway=10.xxx.xxx.xxx, a
rch=x86, ram=4096 MB, vendor=Microsoft, vendorVersion=2003, primaryDNS=10.xxx.xxx.xxx
6, ip=10.xxx.xxx.xxx, version=5.2}
[No services discovered]
0 Kudos
dougm_hyperic
VMware Employee
VMware Employee
‎05-01-2008 06:06 PM
Jump to solution

Hey Guys,
The name issue has been fixed for 3.2.4, ticket contains a link to the sigar .dll with the fix:
http://jira.hyperic.com/browse/HHQ-2040

You'll have to manually delete the CPU services with the bogus names.
As for the number of CPUs, the physical number is what should be displayed.
There's some fixes underway in the 1.5.1 version of sigar for that.
0 Kudos
bclark_hyperic
Enthusiast
Enthusiast
‎05-02-2008 02:07 PM
Jump to solution

To clarify, when you say the "physical number of cpu's", do you mean cpu sockets or cpu cores?

Brian
0 Kudos
kparikh
Enthusiast
Enthusiast
‎08-13-2008 12:23 PM
Jump to solution

Hi Brian,

Can you confirm if the patch worked for you.

Thanks
Kashyap
0 Kudos
bclark_hyperic
Enthusiast
Enthusiast
‎08-19-2008 01:39 PM
Jump to solution

It has almost resolved my issue. I installed the 3.2.4 version of the agent and started it up. Then I deleted the 44 "bad" CPU Services associated with the Platform. Then I ran an auto-discovery from the command line (as suggested earlier in this thread) and it correctly shows my 8 CPU's.

However, I now can't figure out how to get my Hyperic HQ Server to recognize the CPU's on this Platform at all. the auto-discovery didn't automatically repopulate the CPU Services.

Anyone know how I can have my CPU's rediscovered by Hyperic?

Brian
0 Kudos
kparikh
Enthusiast
Enthusiast
‎08-20-2008 04:55 PM
Jump to solution

Hi Brian,

Thanks for confirming that the fix works on command line. To get the CPU services back in HQ you can restart the agent, it should reappear under the platform health services within few minutes after agent restart.

Kashyap