- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- The system is not a VMware ESX Host
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
03-26-2008 07:09 AM
03-26-2008 07:09 AM
Running VM Identification
The system is not a VMware ESX Host, or WBEM credentials may not be specified, skipping VM Identification
I already tried to set "System Properties" myself as follows:
type: server
sub type: virtual machine host
sub type: ESX server host
sub type: Blade
sub type: p-class blade
sub type: Proliant
I have this with our four ESX servers.
yesterday I configured a new setup with a customer of ours ( also with HPSIM v5.2 + hotfix ) and there it worked straight out of the box.
I also checked the WBEM credentials and made sure the domain administrator as the 'root' account was specified.
Anybody keen to help here? Looking already for 4 hours into this problem.
I even opened the ESX firewall by running esxcfg-firewall -acceptIncoming
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2008 12:21 PM
03-26-2008 12:21 PM
Re: The system is not a VMware ESX Host
SNMP is the first thing to check as this should be enough to enable identification. I'm assuming you've installed the HP Agents? They should be at least 7.91 if you're running 3.0.2 or 3.5.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2008 01:02 AM
03-28-2008 01:02 AM
Re: The system is not a VMware ESX Host
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 11:00 PM
04-03-2008 11:00 PM
Re: The system is not a VMware ESX Host
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 11:01 PM
04-03-2008 11:01 PM
Re: The system is not a VMware ESX Host
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2008 03:46 AM
04-15-2008 03:46 AM
Re: The system is not a VMware ESX Host
When I added the two ESX servers, the system immediately recognized all Virtual Machines so I even didn't need to add my Virtual Machines, it was done automatically.
However, in some installations with Blade servers this doesn't seem to work.
It seems that this only works with Proliant Servers as it was in my installation yesterday.
Anyone and idea how I can troubleshoot this further why it doesn't work with Blades?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2008 10:41 AM
06-04-2008 10:41 AM
Solutionhttp://communities.vmware.com/message/914939#914939