HP Sim 6.2 not detecting VMWare Guests Correctly

[Andrew Hedges]

All,

I'm having a bit of a strange problem with HP SIM 6.2 and it not detecting my VMWare guests correctly.

I'm running a mixture of ESX3.5, ESX4 and ESXi4.1 at the moment. I have managed to detect all of the hardware correctly on the ESX Hosts, and when the identify is running, it does correctly count the number of virtual guests running on that host.

However, it only seems to detect the guests OS that are turned off on the ESX hosts - the only one that's detecting guests correctly is my ESXi 4.1 server. All of my other virtual guests are appearing as Unmanaged and are not associated with the ESX host that is running them.

I have tried running numerous discoveries and identifications, but I am not seeing their status change in HP SIM or their association being created with the ESX Host that's running them.

Does anyone have any suggestions before I contact HP Support?

Cheers,

Andrew

[David Claypool]

Use 'Manage Communications' to diagnose.

[Andrew Hedges]

Thanks for your quick response,

I have tried under Manage Communications and I see a Green Tick for Identification and Run Tools, but have a Red X for Events..

Unfortunatly I am still not able to discover any of the guests running on this ESX Host. I have tried removing and then re-discovering this resource, and while it flags up that there are virtual guests running on it, it still doesn't associate the servers with this ESX host and they are listed as unmanaged.

Cheers,

Andrew

[T Kristiansen]

I see you have HPSIM 6.2 successfully monitoring your ESXi4.1 Host. Could you tell me please how you did this? I have not been able to get the Host in to SIM. I have a ticket open with VMWare and its not going anywhere. One thing I do know is that Port 5989 is not listening if I do a netstat -an (HostIP) I don't see anything listening on 5988/9.

Any ideas?

[Rob Buxton]

Check that you have credentials that HPSIM can use to access the host.
I also have a set of credentials that HPSIM can use to access the guests.

There's also an option that lets you enable / disable whether the guests a host has will be discovered as well.

For the last poster, ESXi uses WBEM, if you have an HP Server built with the Vmware Image then you need to install the HP Offline Bundle and the re-ID and Subscribe to wbem events.

[Gary Cormack]

Hi

I am also having the problem that my VMware guests are no being discovered or identified correctly. I was wondering if you could tell me where the option mentioned in the above post is located.

"There's also an option that lets you enable / disable whether the guests a host has will be discovered as well."

Thanks

Gary

[T Kristiansen]

I think the problem is that my ESXi server is not listening on 5988 or 5989 (WbEM ports)and it should be. It is strange because the VCenter server can poll hardware specifics but not SIM 6.2. If I do a netstat -an against the ESXi 4.1 host I do not see 5988/9 listening. I opened a ticket with VM but no luck so far on a cause, asked to escalate. This is a fully patched ESXi 4.1 w/update 01 on a fully updated (fw/HP CIM provders for esxi, drivers) 380 G6 using latest Netextreme II drivers etc, it's all up to date. I've tried all the quirky rediscovery routines from SIM with no luck and accurate creds. Can someone out there please run a Netstat -an against their eSXi 4.1 host and let me know if they see port 5989 listening. Thanks!

[Rob Buxton]

OK, took me a while to get this but I used the esxcli command network connection list to get a list of the ports open on our ESXi 4.1 host.
And yes, 5989 is listed as listening.
There's also a listing for 5988 which I think is related.
As far as I can see you cannot execute netstat on the ESXi host and unless it's different from non windows clients it doesn't take a remote client parameter as was suggested above.

So, you may want to retry using the esxcli command, but you will need the vSphere CLI utility loaded.

[Rob Buxton]

Oops sorry, I see from re-reading theat ESXi 4.1 is okay.
From the main HPSIM page, click on the server name. Under Product Description you should see the protocols that HPSIM has id'd as being available.
Click Tools & Links and go to System Credentials. From there I have SNMP and Single Sign On as valid credentials for my ESX 3.5 hosts.
The ESX servers have the HP Agents installed, they are configured to allow the single sign-on access and I guess that's what's providing the VM details.

For a request above, Options ->Discovery -> Configure general Settings is where you can allow HPSIm to discover the guests from the host. With the check on, a Re-Identification of the Host should discover the VMs.

[T Kristiansen]

To Rob,

Thanks for verifying ports. Here is my the output on my esxi 4.1 host.. I see 5988 and 5989 in there listening on the loop-back and null IP (~not on the host IP). I think the problem may be that I setup HPSIM 6.2 on a 2008 guest which resides on the esxi 4.1 Host I am trying to poll over 5989/8. I am going to try to setup another 2003 server with a fresh HP SIM 6.2 install and see if polling the host works.

127.0.0.1:8307 0.0.0.0:0 LISTEN 5130
tcp 0 0 127.0.0.1:8309 0.0.0.0:0 LISTEN 5130
tcp 0 0 127.0.0.1:5988 0.0.0.0:0 LISTEN 0
tcp 0 0 0.0.0.0:5989 0.0.0.0:0 LISTEN 0
tcp 0 0 0.0.0.0:80 0.0.0.0:0 LISTEN 5130
tcp 0 0 0.0.0.0:443 0.0.0.0:0 LISTEN 5130
tcp 0 0 127.0.0.1:12001 0.0.0.0:0 LISTEN 5130
tcp 0 0 127.0.0.1:8089 0.0.0.0:0 LISTEN 5356
tcp 0 0 127.0.0.1:8889 0.0.0.0:0 LISTEN 5259
tcp 0 0 10.4.10.16:427 0.0.0.0:0 LISTEN 0
tcp 0 0 127.0.0.1:427 0.0.0.0:0 LISTEN 0
tcp 0 0 0.0.0.0:902 0.0.0.0:0 LISTEN 0
tcp 0 0 0.0.0.0:22 0.0.0.0:0 LISTEN 0
tcp 0 0 0.0.0.0:8000 0.0.0.0:0 LISTEN 4876
tcp 0 0 0.0.0.0:8100 0.0.0.0:0 LISTEN 4870