Problems with WBEM & reporting data

[Dave Behler]

We've been using HPSIM for quite some time with few problems. Recently I just enabled the use of the WBEM protocol in order to retrieve data from our virtual machines.

In doing so, it seems that the data being collect via WBEM has a higher priority then that through the HP Mgmt Agents (example now when I run the canned report "Operating System Information - Servers" I only get the brief OS description of Microsoft(R) Windows(R) Server 2003, Standard Edition and no info in the additional description column and now neither column lists the Service Pack version.)

As a test I disabled WBEM, removed & rediscovered a server and the all of the data that I'm use to was back in the report for that single server.

Is there a way to fix this? I like collecting the data through WBEM on the VM, but now the data in the reports for the majority of my servers has been seriously degraded.

[Dave Behler]

Forgot to mention that we are running SIM 5.0 with SP4 and all Mgmt agents are at least at v7.40

[NJK-Work]

Hi David,

I dont have a great solution for you, but what I do is just set a WBEM password for the VMs and thus WBEM fails for all other physical machines (leaving the normal SIM data collection to work for those).

We have a custom server database that pulls in hardware information from SIM. As soon as I enabled WBEM (when we rolled out VMware) it blew up all the data (like you are seeing). The only solution I could find was to enable WBEM, but only set passwords for the VMs. Its ugly, but it does work.

Hope this helps
Nelson

[Dave Behler]

Nelson,

Your suggestion worked perfectly. I agree this solution isn't ideal, at least the data that I need for my reports is as expected.

Now my only problem is that the devices (VM's and non-HP servers) that I discover with WBEM change status to unknown every night. If I recycle the wmi mapper and re-identify these systems they report correctly. I found some other posts with similar issues, but no definitive solution. Any idea?

Thanks,
Dave

[Rob Buxton · Accepted solution]

One of the issues I had seemed to be related to the Daily Device Identification task.
I found that when I stopped this task running I didn't lose servers to the Unknown status.

Since I went to SP5 I've not seen the problem, but I also made sure that I didn't have any tasks that might conflict with each other running at the same time.

I also spent time looking at the HPSIM logs as I could generally find the approximate time that the server seemed to change its status.

[Dave Behler]

I've actually been thinking about applying SP5, but haven't had a compelling reason. I'll give that a try and see how it goes.

[fishmn]

I can tell that the problem still exists with SP5. Disabling the daily device ID will help but only up until your next discovery runs. If you have both turned off you will not lose your VM id's.

I have ongoing ticket with HP on troubleshooting the pegasus wmi mapper which is the component service that WBEM uses. I have also been bit by using "overwrite" when performing Data Collection's against servers. If the job fails you lose all your report data on the server.. not a feature.

Ron

[Rob Buxton]

Ron,
I've reduced the frequency of the Discovery task and again made sure there's no conflict.

I'm not losing the VM's so my guess is still that it is a combination of things rather than an individual issue.

I've made sure that things like Discovery and Daily Device ID etc. were scheduled for quite different times of the day.

[Dave Behler]

I've upgraded to SP5 and things are somewhat better. I also spread out the discovery process and the daily device identification process. Like I said things are better, but not perfect. Now after discovery runs I lose only some of my vm's and it is always the same ones. After they change to unknown, I reidentify just these and they go back into known server status.

As I posted in another thread, I've found that I must use an account (either domain or local) with admin access in my wbem/wmi protocol settings in order to get wbem to work at all. Several HP docs that I found state that the wbem account shouldn't need any special priviledges. Could this have something to do with my problems?

[dospavlos]

I've also found that the only solution is a local admin user specified in the wbem protocol settings. Can anyone link me to the docs describing the priviledges that wbem needs/doesn't need.