- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Inconsistent data collection (Processor informatio...
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
Forums
Discussions
Discussions
Discussions
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
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-25-2011 07:36 AM
10-25-2011 07:36 AM
Inconsistent data collection (Processor information) for WBEM/WMI
I use WBEM/WMI for virtual machines for data collection in HP SIM (6.2). After some random time, the data collection jobs stop collecting CPU inventory data. This is evident in the canned reports. For example if I open a data collection report for a given VM, the far right column of the very top table is called "Number of CPU". This will be populated for a while and then randomly become blank after several data collection jobs have run. Additionally, farther down in the report should be a table called "CPU" with detailed processor inventory data in it. This whole table is missing.
If I reboot the server (and this does not always work), the data collection jobs will work for a few iterations and then eventually fail again. And then, they never work until I reboot again. And, as I mentioned, sometimes the reboot does not work either. I have also tried using the mxstop and mxstart commands to avoid a full reboot, but that has the same results (works sometimes and not others).
I guess I am hoping someone out there knows of a work-around for this. If it is a bug, I can live with that as long as I have a work-around. Since reboots works inconsistently, I am guessing the answer is no...but I thought I would ask.
Thanks
Nelson