Dell OpenManage Essentials

Last reply by 04-08-2021 Solved
Start a Discussion
2 Bronze
2 Bronze
1030

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.

Labels (2)
Solution (1)

Accepted Solutions
830

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 

View solution in original post

Replies (4)
Moderator
Moderator
993

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...

I remain at your disposal.

 

Regards,


Stéphane Thiallier
Business Intelligence Advisor

To reach support please post a public message into
English Enterprise Community or French Enterprise Community
987

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

969

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. 
 
 
 

Chris Hawk
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#Iwork4Dell

Did I answer your query? Please click on ‘Accept as Solution’
‘Kudo’ the posts you like!
831

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 

Latest Solutions
Top Contributor