Closed fvb-sb closed 2 years ago
This sounds like a DELL OMSA issue. Please check the FAQ: https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions. You need to upgrade the OpenManage VIB.
Sorry, I may have closed the issue too quickly.
pywbem._exceptions.AuthError: WBEM server returned HTTP status 401 (Unauthorized). This is most likely an issue with userid/password, but for servers that implement resource access control it might also be an issue with the permissions of the userid.
So this would indicate wrong credentials. But nevertheless, check the OpenManage status.
Thanks for your swift reply Claudio.
I've checked the installed VIBs on the 7.0.3 and 6.7 hosts. It seems that there are no OpenManage VIBs at all:
7.0.3:
esxcli software vib list | grep -iE 'del|open|manag' dell-shared-perc8 06.806.92.00-1OEM.700.1.0.15843807 BCM VMwareCertified 2021-10-14 dell-configuration-vib 7.0.0-A00 DEL PartnerSupported 2021-10-14 dellemc-osname-idrac 7.0.0-A00 DEL PartnerSupported 2021-10-14 lsuv2-oem-dell-plugin 1.0.0-1vmw.703.0.0.18644231 VMware VMwareCertified 2021-10-14
6.7:
esxcli software vib list | grep -iE 'del|open|manag' dell-shared-perc8 06.806.90.00-1OEM.650.0.0.4598673 Avago VMwareCertified 2018-12-28 dell-configuration-vib 6.7-1A02 DellEMC PartnerSupported 2018-12-28 dellemc-osname-idrac 6.7-0A01 DellEMC PartnerSupported 2018-12-28
The credentials seem to be fine - the user is still present on the affected ESXi hosts and login through WebUI works well.
For the ESXi upgrade I've used a custom OEM ISO (downloaded on my.vmware.com: VMware-VMvisor-Installer-7.0.0.update03-18644231.x86_64-DellEMC_Customized-A00.iso) - may this be a problem when using this instead of the 'pure' ISO provided by VMware?
Kind regards Sebastian
Strange, I always thought the Dell Customized ISO contains the OpenManage VIB. I suggest to try two things:
Manually download and install the OpenManage VIB on your already installed Dell custom ESXi. If this doesn't work, install the normal ESXi and see if the CIM elements works (you can use the plugin to test this).
On Dell servers the OpenManage VIB is recommended, as it adds additional CIM/hardware elements to the list.
Yes, try it with the normal ESXi ISO.
It turned out that the permission of the monitoring user on the ESXi hosts were changed somehow due to the upgrade from ESXi 6.7 to 7.0. After applying administrative rights to the monitoring user the check_esxi_hardware.py script works as before/expected.
Hi is there any way that we check with no ssl certificate
tcp/5989 is the CIM server with SSL/TLS certificate (wbem-https). The alternative is tcp/5988 which is the CIM server without encryption (wbem-http). But I'm not sure if this is enabled or can be enabled on ESXi side. And even if it were possible, I strongly advise against using it, as your login credentials would be transmitted in plain text.
yes i disabled on esxi CIM secure server, i.e 5989, but still i am having issues UNKNOWN: 'Connection to "IP" timed out. (connect timeout=9.99)'
^CTraceback (most recent call last):
File "/usr/lib/nagios/plugins/check_esxi.py", line 804, in
Dear community
After upgrading my ESXi hosts from 6.7.0, 17700523 to 7.0.3, 18644231 the check_esxi_hardware script doesn't work anymore. CLI output is:
I've tried updating pywbem as well. Since then CLI output has changed but still no success:
I've one ESXi node left running on 6.7. For this node the script still works like a charm. Any ideas what could do the trick?
OS: CentOS7 pywbem: 0.7.0 / 1.2.0 Version of check_esxi_hardware.py: 20210809 Executed command: check_esxi_hardware.py -H HOSTNAME -U USERNAME -P PASSWORD -V dell -v
Any help appreciated. Thanks in advance. Sebastian