Start a Conversation

Solved!

Go to Solution

1388

March 31st, 2021 03:00

OME 2.5 Unclassified discovery ESXi .

HI everyone, we are having trouble discovering the ESXi with the OME 2.5 mounted under W2016.

Apparently the SNMP and WSMAN communication is correct, but only the ESXi nodes appear like this.

Someone can contribute / help Thank you.

19 Posts

April 8th, 2021 03:00

Thanks for the answers,

We have finally detected that it must be a problem with Windows 2016 and OME, since under W2012 it works without problems.

 

THANKS 

4 Operator

 • 

3.7K Posts

March 31st, 2021 07:00

Hi,

 

there is no screenshot published with your post, could you detail the status of your ESXi nodes into OME?

At a starting point please read this documentation : https://www.dell.com/support/kbdoc/en-us/000178332/how-to-troubleshoot-unknown-device-status-in-dell-openmanage-essentials

I remain at your disposal.

 

Regards,

19 Posts

March 31st, 2021 09:00

Thanks for your answer !!

As you can see in the attached files the esxi discovered appear as unknown.

Captura2.PNG

Captura1.PNG

In the discover,  you can see that the WSman dont work fine, not collect WSMAN profile Data.. THANKS

Moderator

 • 

8.4K Posts

March 31st, 2021 13:00

Just to confirm, did you install the OMSA VIB prior to using WSMAN? If not then I would recommend doing so, then retry.


Also, if you run this command (change x.x.x.x to your IPs) from the OME server, it will let you see the error on why it's not discovering.

 

winrm e cimv2/CIM_IPProtocolEndpoint -u: root -r:https:// X.X.X.X:443/wsman -SkipCNCheck -SkipCACheck -auth:basic -encoding:utf-8 –SkipRevocationCheck

Let me know what you see. 
 
 
 
No Events found!

Top