I ran Update Manager on my ESXi host yesterday and updated to VMWare ESXi, 6.5.0, 8935087. Now my VMWare Hardware Status says Warning. the details show 36 elements return a warning state. THe server also has an iDRAC and It will no longer read the CPU Load. I've tried running all the firmware updates today, but same resluts.
Dell R320 - Hardware Status -Warning After VMWare Upgrade
Votes:
0
12 Replies
Votes:
0
Mike,
Are you monitoring the host directly or through your vCenter server?
If you are monitoring through your vCenter server, please switch to monitoring directly.
Benjamin Day
Paessler Support
Created on Aug 14, 2018 10:00:43 PM by
Votes:
0
I know there are some issues with the VMWare 6.5 release, and SOAP not entirely working correctly. We are waiting on VMWare to patch this and correct the issue.
Can you confirm through the vSphere client that there exist no Hardware Warnings for the host itself? All our System Health sensor does is report that information. Does the System Performance sensor still work OK?
As for the Dell iDRAC and CPU, were you doing that with an SNMP CPU Load sensor?
Benjamin Day
Paessler Support
Created on Aug 15, 2018 4:57:11 PM by
Votes:
0
That is very odd behavior from the Dell iDRAC for SNMP CPU Load. Dell must have changed their OID structure in iDRAC 7. Do you have any other SNMP sensors talking to the iDRAC that aren't working?
As for the VMWare issue, try monitoring it from vCenter. You can do this by adding a Host Hardware Health sensor to the vCenter, and it will return all the ESX hosts it can see. Add this one in question, and let's see what happens.
Benjamin Day
Paessler Support
Created on Aug 15, 2018 10:27:11 PM by
Votes:
0
CPU sensor was fine until I did the VMWare update. I've updated to the most recent firmware of the iDRAC and still no luck with CPU.
I added it in through vCenter and it's still showing Warning for Hardware Status of the Dell R320 host.
New Status at 8/16/2018 12:00:00 PM (Eastern Standard Time): Warning Last Message:
Warning. 36 elements return a warning state: Add-in Card 3 SD1 0 --- 0.11.3.244; Add-in Card 3 SD2 0 --- 0.11.3.245; BIOS 1 ECC Corr Err 65 --- 0.34.1.1; BIOS 1 ECC Uncorr Err 65 --- 0.34.1.2; BIOS 1 I/O Channel Chk 65 --- 0.34.1.3; BIOS 1 PCI Parity Err 65 --- 0.34.1.4; BIOS 1 PCI System Err 65 --- 0.34.1.5; BIOS 1 SBE Log Disabled 65 --- 0.34.1.6; BIOS 1 Logging Disabled 65 --- 0.34.1.7; BIOS 1 Unknown 65 --- 0.34.1.8; BIOS 1 CPU Protocol Err 65 --- 0.34.1.10; BIOS 1 CPU Bus PERR 65 --- 0.34.1.11; BIOS 1 CPU Init Err 65 --- 0.34.1.12; BIOS 1 CPU Machine Chk 65 --- 0.34.1.13; BIOS 1 Memory Spared 65 --- 0.34.1.17; BIOS 1 Memory Mirrored 65 --- 0.34.1.18; BIOS 1 Memory RAID 65 --- 0.34.1.19; BIOS 1 Memory Added 65 --- 0.34.1.20; BIOS 1 Memory Removed 65 --- 0.34.1.21; BIOS 1 Memory Cfg Err 65 --- 0.34.1.22; BIOS 1 Mem Redun Gain 65 --- 0.34.1.23; BIOS 1 PCIE Fatal Err 65 --- 0.34.1.24; BIOS 1 Chipset Err 65 --- 0.34.1.25; BIOS 1 Err Reg Pointer 65 --- 0.34.1.26; BIOS 1 Mem ECC Warning 65 --- 0.34.1.27; BIOS 1 Mem CRC Err 65 --- 0.34.1.28; BIOS 1 USB Over-current 65 --- 0.34.1.29; BIOS 1 POST Err 65 --- 0.34.1.30; BIOS 1 Hdwr version err 65 --- 0.34.1.31; BIOS 1 Mem Overtemp 65 --- 0.34.1.32; BIOS 1 Mem Fatal SB CRC 65 --- 0.34.1.33; BIOS 1 Mem Fatal NB CRC 65 --- 0.34.1.34; BIOS 1 OS Watchdog Time 65 --- 0.34.1.113; BIOS 1 Non Fatal PCI Er 65 --- 0.34.1.38; BIOS 1 Fatal IO Error 65 --- 0.34.1.39; BIOS 1 MSR Info Log 65 --- 0.34.1.40 Last Scan: Last Up: Last Down: Uptime: Downtime: Coverage: Sensor Type: Interval: 84 s 84 s 100.0000% 0.0000% 100% VMware Host Hardware Status (SOAP) 5 m
Last change on Aug 17, 2018 5:41:44 AM by
Votes:
0
Mike,
It looks like we will have to wait on VMWare to fix this bug they have on their end with the code.
As for the CPU from the iDRAC, I've compiled an OIDLib for the Dell iDRAC, and even that MIB file from Dell doesn't have "CPU Utilization". So they never had it to begin with, and they had the standard OID for CPU that our SNMP CPU sensor could read. But apparently, that was changed in iDRAC 7. I'm happy to send you the OIDLib, and you can check it out. It does have things like Processor Current Speed, Max Speed, Cores, Threads, etc. It also has a large amount of data for everything else on the host.
Benjamin Day
Paessler Support
Created on Aug 17, 2018 9:01:19 PM by
Votes:
0
Arount,
Our sensor hasn't changed. We know VMWare is still trying to get the SOAP working right. Until they correct this, our sensors will behave incorrectly.
Benjamin Day
Paessler Support
Created on Aug 31, 2018 10:30:15 PM by
Votes:
0
If neither VMWare nor dell provided an Update in the meantime, you might want to check out the following alternative approach:
https://www.it-admins.com/prtg-and-vmware-6-7-vcenter-host-hardware-status/
Created on Dec 26, 2019 9:32:54 AM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment