Unable to connect to ESXi 6.7 - Verifying credentials

Hello RobCTL,

Have you tried uninstall, reboot and reinstall?

https://dell.to/3KQD6rr

Hello RobCTL,

What model server?

Have you reboot host after OMSA install? You may give that a try.

Typically you would use a windows client and check the box Ignore certificate warning.

I think you are doing that. Can you confirm?

Clear browser cache?

Try a different browser?

What do you get if you try, in a browser:

[actual Server IP]:1311  (instead of host name)

The restart command should be

/opt/dell/srvadmin/sbin/srvadmin-services.sh restart

but  it may be possible that the commands may be in a different path other than /opt/dell/srvadmin/sbin/ depending on how it was installed I think.

Hi Charles,

Thanks for the reply.

Yes I've ticked the "ignore certificate" and I've also tried it off as well.  I've tried a different browser and again the result is the same, as mentioned in my opening post I am not seeing any traffic coming back from the ESXi IP address.

What do you get if you try, in a browser:

[actual Server IP]:1311  (instead of host name)

If I insert the Windows server name in here I get the login screen, and I can also login to the web interface on this server so that bit is working.  As the ESXi OM component doesn't have a native web interface this doesn't work for the ESXi

On the ESXi server I've performed a "Find" for anything starting with srvadmin-services but nothing is found, this I suspect is the problem as although the application appears to be installed, and I can see it in the ESXi web portal I am not sure it actually is.

The server is a PowerEdge R530.

Thanks!

Heads up!  OMSA on ESXi works totally different than OMSA on Windows/Linux.  A Linux/Windows has to be used as a proxy to pull the infos from OMSA for ESXi. There is no :1311 in an ESXi... at least no OMSA will listen there.

Try the following:

esxcli system wbem set --enable true
/etc/init.d/sfcbd-watchdog restart
/etc/init.d/wsman restart

Open your https://windowsORlinux:1311  and choose "remote node" at the bottom.

Edit: Maybe the previous admin have "closed" an security whole by disabling a service. Check https://kb.vmware.com/s/article/1025757

Another note.... ESXi went out of support in 10/2022

Regards.
Joerg

Thanks @Origin3k for the tips, I've run through them and sadly it's still not playing ball.  I've checked the CIM service is running also. 

The plan is to migrate everything over to Hyper-V but that is a future project, at the moment I just need to get some visibility on the server/hardware.

Ok.. i spend some time to find an old 6.7.

[root@esx-node-14:~] esxcli software vib list | grep -i Open
OpenManage 10.1.0.0.ESXi670-4634 Dell VMwareAccepted 2021-10-30

[root@esx-node-14:/opt/dell] du -sh *
2.5M    bin
156.0K  pciconfig
2.8M    racadm
14.7M   srvadmin

Please take notice that also iDRAC Tools (racadm) are installed. These are not a requirement to get OMSA on ESXi working.

The OMSA Proxy have to be the same or higher version as the ESXi one.  To avoid FW Issues we access the OMSA within the same subnet.

The usage of this "remote managed node" feature needs to be anabled by clicking Managed System Login preference in Preferences->General Settings->Webserver-> Properties->Managed System Login. If not you will see a message which points the Admin into the right direction.

We dont have ESXi Lockdown enabled.. because of OMSA logins as OS user "root" iam not sure how this can be effect OMSA.

After a susscessfull login as "root" you will see in your Windows OMSA the content of the ESXi OMSA.

Because we have diskless servers we have limited use of OMSA on ESXi.  For HW alerting we use the iDRAC Enterprise (Syslog, SMTP, SNMP) and the Dell OMIVV Appliance to display Server HW into the vSphere Client.

OMIVV will be replaced by OME (OpenManageEnterprise) Appliance + Plugins which is available as a OVF for vSphere, Hyper-V, KVM.

Regards,
Joerg

"cd /opt/dell" first.

Yes, i printed the output because it was mentioned in earlier posts but there is nothing to start (at least for me).

The Problem youre facing i also seen earlier.   Can you try to restart the following

/etc/init.d/rhttpproxy restart
/etc/init.d/sfcbd-watchdog restart

and than try again.

Regards,
Joerg

@Origin3k thanks for your time on this.

Output of esxcli software vib list | grep -i Open command:

OpenManage 10.3.0.0.ESXi670-5081 Dell VMwareAccepted 2023-04-20

However the output of du -sh * is telling as I can't see srvadmin:

124.6M bin
4.0K bootbank
520.0K bootpart.gz
408.0K bootpart4kn.gz
30.1T dev
25.0M etc
40.1M lib
169.1M lib64
16.0K local.tgz
4.0K locker
116.0K mbr
15.0M opt
128.0K proc
4.0K productLocker
4.0K sbin
4.0K scratch
4.0K store
618.7M tardisks
4.0K tardisks.noauto
7.1M tmp
232.8M usr
18.8M var
2.8T vmfs
12.0K vmimages
4.0K vmupgrade

I can confirm that OM on the Windows server is the same version as the ESXi one.

Thanks

@Origin3k thanks for that, command ran and it ran successfully but still unable to get past the verify credentials.  I did notice that I was also not able to login to the local web instance on the Windows box to check the "remote managed node" feature but a quick restart of the DSM service fixed that.  Again checking the firewall I am not seeing any traffic coming back from the ESXi server, I can see the requests going out from the Windows server but they are just not getting any replies.

There is a weird looking log section under /etc/cim/dell/srvadmin/var/log/openmanage but i poke around and didnt find any usefull entries. I can see when login was successfull but trying it with a wrong username or password doesnt bring usefull hints.

I took notice that my OMSA was an older version than yours. Maybe you can give it a try and downgrade your OMSA on ESXi.

Regards
Joerg

@Origin3k good idea, I've downgraded the ESXi software but I am still getting the same issue.  I think I'll ponder if over the weekend and start afresh on Monday.  Thanks for the help