Incorrect OSType from Discovery Process

[pedro-chicago]

I hope I am able to explain this clearly. I have tried to reverse engineer the discovery process for servers in an attempt to figure this out.

Currently running HP SIM 5.2 with SP2 (Hotfixes - HOTFIX52_002.jar, HOTFIX52_003.jar; MIB Update Kit 8.10; VCRM 2.1.10.800 with Windows 2000 and Windows Server 2003 PSPs) on Windows Server 2003 SP2 using local SQL 2005 SP2 database. Currently only have a few HP servers (DL3x0 G3/G4/G5 or BL460c1) discoverd - Windows Server 2003, Windows 2000, and VMware ESX 3.5, all with the latest PSPs.

When discovering HP servers running Windows Server 2003 SP2 with PSP 8.11, everything appears to work correctly. The problem is that when I try to do an advanced search based on software/firmware and component type individual components, the only options for operating system are Linux - VMware ESX Server, Other, and Windows NT.

Looking at the database tables mibOSToVCOS and swVersionWeights and the SNMP OID .1.3.6.1.4.1.232.11.2.2.4 (.iso.org.dod.internet.private.enterprises.compaq.cpqHostOs.cpqHoComponent.cpqHoInfo.cpqHoOsType) for Windows Server 2003 (result is windowsdotNet), then the Windows Server 2003 servers should map to swVersionWeights.osKey = 69.

But looking at the database tables (CIM_OperatingSystem and CIM_SoftwareIdentity) and some of the files in the config\* directories (config\datacol\dcEnumMappings.xml and config\datacol\collector-wmi.xml), the WMI query for Win32_OperatingSystem.OSType is 18 for Windows Server 2003 servers. This ends up being mapped to Windows NT and the CIM_OperatingSystem.OSType value is 18. Also, the CIM_OperatingSystem.dc_OSType value is Windows NT and the CIM_OperatingSystem.dc_PrimaryOS value is 1. This is also true for Windows 2000 servers where the WMI query for Win32_OperatingSystem.OSType is 18.

So when I look at the CIM_SoftwareIdentity table for a Windows Server 2003 server, the CIM_SoftwareIdentity.TargetOperatingSytem values are 1 for all of the software elements. Going back to the advanced search, if I choose Windows NT for the OS, I actaully see all of the Windows 2000 and Windows 2003 software/firmware elements. Given that I will need to add Windows Server 2003 x64 and Windows Server 2008 servers to HP SIM, along with their associated PSPs, there doesn't seem to be any way to keep all of these seperate.

It seems like there is some incorrect or inconsistent logic being used in the discovery process for mapping the server OS information, either via SNMP or WMI, to the various table.column values. I don't know if anyone else has observed this or if there is any fix. If I didn't explain this well or anyone wants any more detailed information or logs, please let me know.

Thanks.