Hi there,

Couple of questions:

Are you referring to Vmware hosts in remote locations?

I assume the new Vmware hosts are local test boxes?

Have you tried increasing the WSMan timeout value?

Thanks,

Rob

Yes I'm trying to monitor the VMWare host in two differenct locations. We have a mixture of No VM/Test VM/Production VM but some hosts are sitting idle at this time.

This is one location which has a total of 4 VMware hosts which shows health status but connection status (On) with a mixture of M610/M620 blades

In my other location I have 4 VMware hosts but only two show up as I've deleted them previously and tried to rescan the IP range. When this range is scanned it only can see two of the 4.

Troubleshooting tool results:

The VMWare hosts that aren't showing up or bringing back value on WSMAN testing indicate a incorrect username and password.

The VMWare hosts that do show connected and all the profiles it can see.

So I figured out the issue... the version of the Offline Openmanage we had previously installed was OM-SrvAdmin-Dell-Web-7.1.0-5304.VIB-ESX50i_A00 and I found a newer version v2-OM-SrvAdmin-Dell-Web-7.1.0-6339.VIB-ESX51i_A00. Once this was installed OME found the server and Health Status is now green. So perhaps a note for incompatability there for other users.

Additional issue -- When a scheduled discovery and inventory runs automatically all my VM hosts cease to show any health status. I can manually run the discovery/inventory on the include  range and it detects them fine again... anyone seen this issue? I've reported it to Dell technicial support as well.

I presume you are referring to ESXi hypervisor as VM host. Typically OME does not retrieve health status for virtual machine (guest).

For ESXi hosts, can you try to increase the timeout value (may be 20 seconds) in discovery wizard for WSMAN protocol and check if scheduled discovery and inventory runs fine ? Both manual discovery and scheduled run the same task. Only difference being all discovery ranges will be run during scheduled v/s only the selected one in the manual process.

Thanks,

Raj Shresta

As in my picture above my value timeout is at 60 seconds. I have 26 ranges in which I poll.

I've built this box from the OME Open Eval to v1.0.1 to 1.1 to 1.1.1 so I think we may be looking at wiping it clean and starting over since we are having so many erratic behaviours.