New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Dell R320 - Hardware Status -Warning After VMWare Upgrade

Votes:

0

Your Vote:

Up

Down

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 esxi hardware-status

Created on Aug 14, 2018 7:01:10 PM by  Mike72677 (0) 1



9 Replies

Votes:

0

Your Vote:

Up

Down

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  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

It was auto detected under Virtual Systems - VMWare - VMWare Hosts. So I would assume it's being monitored directly.

I'm new to PRTG so I'm not familiar with it yet. It was fine until my upgrade to 6.5 U2b. I believe it may be an issue with the VMWare upgrade.

Created on Aug 15, 2018 12:06:04 AM by  Mike72677 (0) 1



Votes:

0

Your Vote:

Up

Down

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  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

For that host, vCenter shows "No alerts or warnings out of 115 sensors".

Host Performance sensor is "Up" and green.

Yes, I added the SNMP CPU Load sensor on the iDRAC IP. It's an iDRAC 7 with the latest firmware.

Created on Aug 15, 2018 6:15:22 PM by  Mike72677 (0) 1



Votes:

0

Your Vote:

Up

Down

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  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Aug 16, 2018 7:01:14 PM by  Mike72677 (0) 1

Last change on Aug 17, 2018 5:41:44 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We have the same issues here. Soap request to ESXi backend and frontend servers reports warnings like:

Warning. 205 elements return a warning state: CPU2 Level-3 Cache; CPU2 Level-2 Cache; CPU2 Level-1 Cache; CPU1 Level-3 Cache; CPU1 Level-2 Cache; CPU1 Level-1 Cache; Battery 7.1; Renesas Technology Corp. SH7758 PCIe Switch [PS] #0; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #31; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #31; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #30; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #30; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #30; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #30; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit #30; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 1 Error #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Error #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 1 Thermal Control #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control #23; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast #22; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast #22; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Channel Target Address Decoder #22; Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Channel Target Address Decoder #22; Intel Corporation Xeon E7 v4/Xeon E5 v4/X

This all started to happen after upgrading our Dell R630's to to 6.5.xxx. We are now running VMware ESXi, 6.7.0, 9484548. And the warning are still there.

Both Dell Open Manage as the vCenters doesn't report any warning. It doesn't has anything to do with mib's i think because these are soap request. Are you sure PRTG makes still the right SOAP request to ESXi

Created on Aug 31, 2018 11:32:29 AM by  Arnout (0) 1



Votes:

0

Your Vote:

Up

Down

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  Benjamin Day [Paessler Support]



Please log in or register to enter your reply.


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.