hsukirman
Contributor
Contributor

ESX & HP Management Agents 8.1.0 = No WBEM

Hi there,

I have an ESX 3.5 server with the latest HP Management Agents installed (hpmgmt-8.1.0-vmware3x). I use HP SIM to monitor my ESX servers.

I saw that HP SIM is able to collect information about VMs on an ESX host when the WBEM protocol in configured. Now with other ESX servers running older HP agents (I have currently 7.8.0 & 7.9.1 running and tried it too with 8.0.0) this works just fine. However on my host with the 8.1.0 agents I get error messages during the system's identification process.

It says for example:

"Running VM Identification

The system is not a VMware ESX Host, or WBEM credentials may not be specified, skipping VM Identification"

"[WBEM] System identified as WBEM instrumented but no usable WBEM credentials available. Check configuration and rerun Identification.

Root Cause: Identification failed to generate relevant WBEM credentials for target system.

Corrective Action: Check network and configuration of target system. Check the following pages to ensure appropriate WBEM credentials and port number data are provided: Global Protocol Settings, System Protocol Settings. Rerun Identification and Data Collection."

I checked some other protocols like SNMP & System Management Homepage and they all work fine. Just the WBEM seems to have some problems. (I use HP SIM's global protocol settings to configure WBEM. This way the same credentials are used for all my ESX hosts)

Has anyone seen this before? Do you have an idea what I could to to get WBEM running?

Thank you in advance for your comments!

0 Kudos
7 Replies
Texiwill
Leadership
Leadership

Hello,

A better location for this question would be the HP Technical forums as it is HP specific.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
hsukirman
Contributor
Contributor

Yes there I posted already. I have two ESX 3.5 U1 (with patches) and old HP management agents running that are working just fine. Then I have one ESX 3.5 U1 (same patchlevel) with the latest HP agents installed and I get the WBEM error described above. So today I set up a test ESX 3.5 Update 2 with the latest HP agents and that one is working fine too.

So I am wondering where this WBEM comes from. Is it something that the HP agents install, or is something that comes with a standard ESX installation? (That is why I am posting in both forums)

Greetings,

HSukirman

0 Kudos
nomadnate
Contributor
Contributor

Hi, this is related to the HP Proliant Support Pack install.

Check Add/Remove programs - you should see the following -- HP Insight Agent WBEM providers.

This was new to the 7.9 or 8.0 Support Pack, I believe.

0 Kudos
JRink
Enthusiast
Enthusiast

Earlier today I just added a ESX 3.5 U2 host to my HP-SIM server. The only thing I did was install the Insight Agent (latest version available) on my ESX host. Add my root username and password to the WBEM information under global protocol settings, and do a manual discovery of the ESX host ip address. Seemed to work fine.

Here's the stderr output from my latest Indentify task of the esx host:

Starting identification process...

Checking for known running web servers.

Checking for System Management Home Page and other HP web agents.

Received a response from the system management homepage, this system supports SM

H.

Checking for WBEM support on system.

This system has WBEM protocol support

This system has at least one SMI-S CIMOM installed

This system doesn´t have a server CIMOM installed locally, or cannot connect to

it using all credentials specified

Running WBEM rules based identification.

Cannot get ComputerSystem WBEM/WMI data from the system

Running VM Identification

The system is a VMware ESX Host and has guests running on it

Running WS-Man identification.

The system did not respond to WS-Management, verify credentials.

Checking for SNMP support on system.

The system responded to a SNMP request, it supports SNMP.

Running SNMP base Cluster identification using common cluster MIB.

This was not a system with the common cluster MIBs supported.

Running HP ProLiant management agent identification

System has the SNMP ProLiant server (foundation) agents installed, adding system

type.

Running HP NetServer identification.

System supports the NetServer SNMP agent, adding system type

Running HP-UX SNMP identification.

System does not have the HPUX SNMP agents installed.

Running SNMP System Type Manager identification.

Found matching SNMP System Type Manager rule, added as possible system type

Checking for DMI protocol support.

The Windows CMS cannot communicate with HP-UX or other DMI, skipping.

Running DMI System Type Manager identification.

The system does not have Windows DMI support.

Running HP-UX DMI identification.

The system does not have HP-UX DMI support.

Running HP/Compaq Desktop identification.

The system does not have Windows DMI support.

Running HP DMI Desktop identification.

The system does not have HP DMI Desktop support.

Running Generic DMI identification.

The system does not have Generic DMI support.

Checking for SSH protocol support.

The system supports SSH protocol

Running Storage identification.

There were no storage profiles found on this system.

Storage identification completed.

Running HP Service Guard Identification.

The system is not part of HP Service Guard cluster

Checking if this system is supported by Insight Power Manager.

Insight Power Manager is not supported.

Running VM identification.

VMM is installed, but the system is not a VM Host or may not be configured in VM

M

Building system relationships.

Running limited data collection for common attribute.

Done with limited data collection, checking retrieved data.

The SSH is not configured on this system

SMH trust status is false.

Running node communication diagnosis

System identification done with this system.

edit - sorry for the formatting.... the copy/paste didnt seem to work quite right.

0 Kudos
IBMVM
Contributor
Contributor

try enablling snmp and cimd services in esx firewall ..

Looks like HP SIM server can't communicate to some of the running services on ESX firewall. IF you want to really brave then go ahead and stop firewall complete to see if all of your error is gone and then you can do selective opening of ports on firewall Smiley Happy

0 Kudos
mkats
Contributor
Contributor

esxcfg-firewall -q

Opened ports:

hp-sim : port 2301 tcp.in tcp.out

sim-cert : port 280 tcp.out

cimserver : port 5989 tcp.in tcp.out

hpim : port 2381 tcp.in

cimserver (wbem) : port 5988 tcp.in tcp.out

0 Kudos
Texiwill
Leadership
Leadership

Hello,

Check out http://www.astroarch.com/wiki/index.php/HPSIM_and_ESX for some assistance on this.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos