- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Problems with WBEM & reporting data
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2006 05:43 AM
тАО10-12-2006 05:43 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2006 05:57 AM
тАО10-12-2006 05:57 AM
Re: Problems with WBEM & reporting data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 09:56 AM
тАО10-13-2006 09:56 AM
Re: Problems with WBEM & reporting data
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 05:20 AM
тАО11-16-2006 05:20 AM
Re: Problems with WBEM & reporting data
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 11:31 AM
тАО11-16-2006 11:31 AM
SolutionI 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2006 12:48 AM
тАО11-17-2006 12:48 AM
Re: Problems with WBEM & reporting data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2006 03:39 AM
тАО11-17-2006 03:39 AM
Re: Problems with WBEM & reporting data
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2006 06:02 AM
тАО11-19-2006 06:02 AM
Re: Problems with WBEM & reporting data
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-22-2006 12:04 AM
тАО11-22-2006 12:04 AM
Re: Problems with WBEM & reporting data
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 03:04 AM
тАО11-28-2006 03:04 AM