HP Solution Required - SIM Reporting Errors with volume space 100% with WBEM enabled

[Mark_575]

HP,

I've asked about this problem before, but it's causing me real problems now.

If WBEM is enabled and after a data collection task has run, if I run volume space reports, many of my servers report volumes as 100% full, see attached.

This makes the report useless unless I dump the contents into excel are recalculate the results.

If I disable WBEM then results return to normal, but I can't gather parameters from many of my non HP servers.

Is HP looking into this or is there a patch available?
I have SIM 5.1 with SP1

Many Thanks
Mark.

[Rob Buxton]

I'd also be keen to hear, especially from anyone that's gone to 5.2.

There have been no fixes I'm aware of for HPSIM 5.1.

It's definitely a pain I use a perl script to report and for all our virtual servers I have to extract the used and size and calculate the space used.

[Mark_575]

I've tried v5.2 but no change.

Is there a way to escalate this problem to HP for resolution?

Thanks
Mark.

[Blazhev_1]

Hi

check this advisory:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01091885&prodTypeId=15351&prodSeriesId=1842838

This is a workaround of course, but will maybe help you to resolve the problem :)

Regards,
Pac

[Mark_575]

Hi Pac,

Yes, I have been using this Fix for the last few months, but it's very time consuming to wait 30 Plus mins every time you enable or disable WBEM and then re-run the reports.

Interesting it says on that link you sent:

"A future version of HP SIM will allow the correct disk drive usage percentage to be reported."

Are we able to press HP for a date when this will be available?

Cheers
Mark.

[Lucky Luciano]

Hi there

just to confirm that Mark is not making this experience alone

I used 5.1 and noticed the same, now I am on 5.2 and no change at all.

Would appreciate if this is corrected

[Mark_575]

Sorry to keep harping on about this one.

But is there any more of you out there experiencing this, who don't mind adding their comments here.

Also how can I go about getting a solution rather than the annoying workaround?

Thanks
Mark.