OMIVV 5 not connecting to ESXi 6.7 U3

Do you have updated OMSA as well? For U3 there is a new one needed

https://downloads.dell.com/FOLDER05847739M/1/OM-SrvAdmin-Dell-Web-9.3.1-3684.VIB-ESX67i_A00.zip

Maybe it helps to run from ESXi commandline

esxcli system wbem set --enable true
/etc/init.d/sfcbd-watchdog stop
/etc/init.d/sfcbd-watchdog start

Regards,
Joerg

Hi Joerg,

OMSA is already installed in this version. I also uninstalled OMSA on one host, because in other communitys is was suggested to unistall it. But no success.

Your commands on ESXi commandline brought no success.

Regards,

Magnus

Hi Magnus,
 Is the issue is observed with ESXi 6.7 U3 alone, or same is seen with other versions of ESXi as well (If you have any in your environment) .

Can you try triggering below WSMAN query to ESXi .
Query (From a Windows Machine) :
winrm e cimv2/CIM_IPProtocolEndpoint -u:ESXi_Username -p:ESXi_Password -r:https://Esxi_Host_IP:443/wsman -skipCNCheck -SkipCACheck -auth:basic -encoding:utf-8 -SkipRevocationCheck -f:pretty
 
Thank You,
Vineeth

Hi Vineeth,

Connection to ESXi 6.7 EP 05 and ESXi 6.5 EP 13 works as expected, both connection tests (iDRAC and Host) pass.

The result of the WSMAN query to ESXi 6.7 U3 is an error.

error number: -2144108327 0x803380D9

Running this query to ESXi 6.7 EP 05 and ESXi 6.5 EP 13 brings an expected XML answer

Hi Magnus,
 Thank you for the details.
 The error code indicates invalid connection string, presume target name and credentials are right.

 Can you check the wbem status at ESXi host after triggering above mention winrm query (winrm e cimv2/CIM_IPProtocolEndpoint….)
 wbem status can be seen by ‘esxcli system wbem get’ command, ‘WSManagement Service’ indicates the wbem current status.

 Another query :  Does any of the vm-kernel adapter added to ESXi has IP address 128.x.x.x or above ?

Regards,
Vineeth

Hi Vineeth,

esxcli system wbem get befor and after the query returns:

Authorization Model: password
CIMObject Manager PID: 3146219
Enabled: true
Enabled Running SSLProtocols: tlsv1.2
Enabled SSLProtocols:
Enabled System SSLProtocols: tlsv1.2
Loglevel: warning
Port: 5989
Service Location Protocol PID: 2103061
WSManagement PID: 2103357
WSManagement Service: true

Result on ESXi 6.7 EP 05 is the same.

No there is no VMkernel adapter with IP address 128.x.x.x, but because i used Dell EMC customized ESXi 6.7 U3 Image, i have a VMkernel Adapter named iDRAC Network, vSwitchiDRACvusb, ip address 169.254.02

Hi Magnus,
 OMIVV will depend on ESXi to provide iDRAC details for management.
 If wsamn query CIM_IPProtocolEndpoint on ESXi does not respond, OMIVV fails to perform Test Connectivity and Inventory.
 Cab you please log a support ticket for team to take a closer look at the problem.

Thank You,
Vineeth

Do you happen to have the iDRAC service module installed? I found that having the iDRAC service module installed causes the hosts to not connect. Once I removed it I was able to add the hosts to OMIVV. (Interestingly once I'd done an initial inventory, I was able to re-add the iDRAC service module and things kept working.)

thanks for the advice.

following vib was installed:

dellemc-osname-idrac 6.7-0A03 DellEMC PartnerSupported 2019-10-31

I removed the vib and reboot the esxi, but no success in connecting to the server via OMIVV

There is another vib:

OpenManage 9.3.1.ESXi670-3684 Dell VMwareAccepted 2019-11-05

Should i removed this as well?

The VIB that was causing me problems is dcism. (https://www.dell.com/support/contents/us/en/04/article/product-support/self-support-knowledgebase/enterprise-resource-center/systemsmanagement/eism)

Unfortunately it did not fix my problem. I have opened a ticket at Dell Support and will post the results here