Discovering standalone ESX servers

[ssuhail]

Hello!!

We are running discovery to populate our CMDB. We were able to discover ESX servers with vCenters. However the standalong ESX servers are not getting discovered. We have provided all credentials including root, but somehow the standalone ESX servers don't get discovered.

Has anyone faced and solved this problem?

regards,

Suhail

[VivekSattanatha]

Hi Suhail,

OOB we cannot discover ESX servers standalone. There are no separate ESX exploration probes available to discover so I think it will fail in the classification phase itself.

Btw why you are going for standalone ESX discovery? vCenter discovery itself will give you enough information about ESX servers and it's pretty good for creating relationships with Servers.

Regards,

Vivek

[ssuhail]

Hi Vivek,

Unfortunately, our environment is spread across the globe and 50% of the ESX servers are standalone and the remaining ones with vCenter. The vCenter discovery is giving us every detail that it could for those ESX servers, but the remaining ones are not discoverable. Also I noticed that some of them were giving a warning as "Invalid Namespace"

I read that we cannot discover standalone ESX servers, but was hoping someone would have found a workaround.

regards,

Suhail

[VivekSattanatha]

Hi Suhail,

Interesting!! I didn't know before that ESX server can run without vCenter. Custom probes and Sensors will help but ESX servers having their own command line interface so I guess it will be a lot of work. Maybe be there will be a possibility of getting ESX host information from CIM probes. Right now the CIM probes will only work for getting ESX servers serial number.   You can ask this question to ServiceNow if there is any other possibility.

Regards,

Vivek

[William44]

Starting in Quebec, ServiceNow supports Standalone ESXi discovery | ServiceNow Docs