ESXi 4.1 / OME - Discovery / Inventory won't work anymore

Sorry, I have to correct, since I can't change an existing pos:

The ESXi-hosts that won't inventorize are in a seperate configured IP-range as my other ESXi-hosts, except for one machine that inventorizes just fine. After some googling and the realisation of the simple truth that I am not able to fix this, maybe the smart guys from Dell can get me a hint?

Hi Chris and thanks for the post.

Can you compare the WSMan settings in your discover wizard and confirm that the setup in the ranges is correct?

It seems like one range is working ok, but one is not.  Can you check the screen below?

Thanks,

Rob

Thanks for the updates Chris. When you say the ESXi hosts are not getting inventory data, are you seeing an entry for ESXi CIM provider in the agent table for those hosts? It will be called VMWare ESXi under Software Agent information table as part of host inventory.

Regards

Abhijit

Hi Rob,

I am sure WS-MAN is configured correctly, since it worked for several weeks with this configuration, but I already checked the WS-MAN config too, since it was my first guess. Also I deleted the range, configured it again with WS-MAN, with no effect.

The screenshot is showing an alternative possible configuration of WS-MAN? Then I would try that tomorrow, for I am leaving the office now and head home.

Hi Abhijit,

The host-OS don't get recognized, in contrast to the ESXi-hosts that do get inventorized and properly recognized.

To my surprise, now the second of three scopes with ESXi-Hosts refuse to get inventorized, which worked yesterday. Any ideas?

EDIT: Now I read over my first post again, and I have to make clear: the hosts _are_ found by OME and are showing in the OME webUI, but no Details about firmwarelevel, hardwarestatus etc are available. English is not my primary language, so you have to bear with me :-)

Thanks for the updates Chris.

You are saying that the entries for the hosts are present in the device tree but detailed inventory data is not being shown. I'm not sure but from your post, it looks like you are not seeing the entry for VMWare ESXi in the Software Agent information table.

You can try using the troubleshooting tool and type in the address for one of the ESXi hosts and try connecting using WS-MAN. That will tell if the connectivity and credentials are still working for that host for WS-MAN protocol. If the connectivity is good, you can try increasing the timeout in the WS-MAN page on the discovery wizard to 10.

Regards

Abhijit

Hi Abhijit,

yes, I can't see the entry for VMware ESXi in the software agent section.

I installed the troubleshooting tool on the machine that hosts OME and tested WS-MAN, looks ok to me. The output is identical on every host.

I am quoting the output:

Also, I set the timeout to 10 and even to 20, with no effect.

Thanks for the updates. The connectivity looks good. Since you have already tried deleting and re-discovering the ESXi hosts, I would recommend to open a trouble ticket with support and they can gather additional information. Here is the number: 800-945-3355

Hi Abhijit,

thanks so far. I'll let you know if I / we find a solution.

You should be able to contact German Tech support. Let us know how it goes.

Regards

Abhijit