Autodiscovered CPU resources incorrect - Win32 Agent

[sfuller_hyperic]

I am looking at the autodiscovered CPU resources on one of my servers, which is a dual quad core Xeon running Windows.

For the first 4 cores, I see something like the following listed:

server1 Win32 CPU 1 (1863Mhz Intel Xeon)

For cores 5 - 8 I see the following:

server1 Win32 CPU 5 (1863Mhz

‘

x V Xeon)
server1 Win32 CPU 5 (1863Mhz M

˜

¸u Xeon)
server1 Win32 CPU 5 (1863Mhz Xeon)
server1 Win32 CPU 5 (1863Mhz Intel Xeon)
server1 Win32 CPU 5 (1863Mhz U x V Xeon)
server1 Win32 CPU 5 (1863Mhz ¸kÒ x V Xeon)
server1 Win32 CPU 5 (1863Mhz è8W x V Xeon)

We're running agent version 3.2.0 EE on these servers. Does anyone have any idea why the agent is detecting these "other" CPUs?

[BradFelmey]

I don't offhand have an answer, but since the agents are the same between EE and OSS versions, try grabbing the latest OSS agent (3.2.1 as of this writing). It can't hurt to try.

[bclark_hyperic]

I have the same issue--even when using the 3.2.2 version of the OSS agent.

http://communities.vmware.com/thread/350958?tstart=0

Brian

[BradFelmey]

Sounds like a bugamundo. Please file: http://jira.hyperic.com

[dougm_hyperic]

(pasting reply from a related thread, feel free to pass around to any others I missed)
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.

[bclark_hyperic]

Thanks!

Just to confirm, after installing the new DLL, I would manually delete the incorrect CPU resources, and then manually kick-off an auto-discovery on the platform to get things into a correct state?

Brian