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


VMware Host Hardware Status (SOAP) Sensor returns warnings after Update to VMware 6.7

Votes:

1

Your Vote:

Up

Down

Hi,

We have an issue with the VMware Host Hardware Status (SOAP) sensor.

After we updated our VMware infrastructure and the Esxi Hosts to VMware ESXi, 6.7.0 these sensors return some warnings.

We are currently using PRTG version 18.4.45.1898. I guessed that the VMware Host Hardware Status (SOAP) sensor will be working fine since there was an update on the VMware Host Performance (SOAP) sensor so it will work with VMware 6.7 Update 1.

The warnings mentioned are depending on the Hardware that is asked for its status. Meaning with similar hardware the warnings PRTG shows are the same. As Example [Warning. 42 elements return a warning state…] from 200 States this sensor gets.

We checked the Hardware and the vcenter for errors and warnings but they aren’t showing any warnings at all. And since the Sensor gets its data from the vcenter they should show the same warnings and errors. Even when I’m creating a new VMware Host Hardware Status asking the vcenter about the esxi Hardware Status the warnings shown are the same.

Does this sensor need an update and when can I get it? Or is there something else wrong?

Sadly we can’t use this sensor like this anymore.

Many thanks in advance.

esxi hardware-status soap update vmware vmware-host-hardware-status--soap- vmwaresensor

Created on Nov 12, 2018 12:58:02 PM by  Jacqueline Weigel (11) 2



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello Jaqueline,

Thank you for your reply. I discussed this issue with our VMware administrators and I need to correct my previous reply.

Some updates of the vCenter change the internal way how the vendor specific drivers (Dell, HP...) communicate with the vCenter via CIM. These specific drivers need to be adjusted after an update so that they do not throw a warning via the API calls.

Based on our own experience, this takes about six to eight weeks until new packages get available after an update of the vCenter.

I'm afraid that this is something that we cannot fix ourselves.


Kind regards,
Felix Saure, Tech Support Team

Created on Nov 16, 2018 8:49:56 AM by  Felix Saure [Paessler Support]



15 Replies

Votes:

0

Your Vote:

Up

Down

Hi Jacqueline,

I agree, the API should indeed return the exact same values as displayed in your vCenter. Unfortunately, this appears to be an issue with VMware 6.7, we have other customers reporting the same findings so we need to wait for a fix from VMware here.

As we cannot change the API output of the vCenter, you can enter the settings of the sensor and enter the warning string into the Known Warnings. You can get the string by enabling the sensor setting Write Result to Disk.


Kind regards,
Felix Saure, Tech Support Team

Created on Nov 13, 2018 12:17:28 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Felix,

according to our observation this is not an issue directly related to vCenter. In our case the problem showed up after we updated the first esxi host to 6.7.0 Update 1. At this point of time the vCenter itself had been running on 6.7.0 Update 1 for about a week without any occurrences.

In my understanding this could be a change of VMware, which Paessler has to adopt the behavior of the appropriate sensor to.

But I understand that Paessler themselves are in close communication with VMware to get a short time fix resolving this issue.

Is this correct and is there any idea when this will happen?

Many thanks in advance.

Created on Nov 13, 2018 1:00:34 PM by  Jacqueline Weigel (11) 2



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello Jaqueline,

Thank you for your reply. I discussed this issue with our VMware administrators and I need to correct my previous reply.

Some updates of the vCenter change the internal way how the vendor specific drivers (Dell, HP...) communicate with the vCenter via CIM. These specific drivers need to be adjusted after an update so that they do not throw a warning via the API calls.

Based on our own experience, this takes about six to eight weeks until new packages get available after an update of the vCenter.

I'm afraid that this is something that we cannot fix ourselves.


Kind regards,
Felix Saure, Tech Support Team

Created on Nov 16, 2018 8:49:56 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi.

What is the fix for this? To wait for PRTG and vCenter to work it out? And then what? Update PRTG or vCenter? Will anyone update this thread when it is fixed? We are hesitant to update our PRTG in case if it breaks a service we use to read web/API calls.

Aidan

Created on Jan 24, 2019 6:49:59 PM by  amaher (0)



Votes:

0

Your Vote:

Up

Down

Hi there,

Updates of PRTG won't help here since the changes need to be deployed in the CIM extensions of VMware. PRTG can just work with the information provided by the API.


Kind regards,
Felix Saure, Tech Support Team

Created on Jan 25, 2019 12:38:36 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

We are currently "accepting" the warnings within the sensor under "Known Warnings" so we can separate the this warnings from real ones. That is not satisfactory, I know.

But how about a small change from prtg on this topic?

I think it is possible to check/filter the values without real value ("Unknown") and report them back into a separate channel (like Returning Unknown or something like that) not the warning channel?

In my opinion this would be a nice solution on part of prtg, even if it doesn’t fix the error.

I hope you consider my idea.

Jacqueline

Created on Jan 25, 2019 1:46:31 PM by  Jacqueline Weigel (11) 2



Votes:

1

Your Vote:

Up

Down

Hi Jaqueline,

I get your point, unfortunately I cannot think of way to get this working with the current concept of PRTG just storing numerical value except for the sensor message. What would be possible (please don't see this as promise) is to store the number of filtered warnings in a channel. I'll forward this to our Product Owners for consideration.


Kind regards,
Felix Saure, Tech Support Team

Created on Jan 28, 2019 7:50:17 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Felix, we have this issue as well in our vSphere 6.7 Update 1 environment. All of our vCenters and ESXi hosts are at the latest available patch, I hope you have an idea for this issue, since otherwise this sensor is useless.

Created on Feb 7, 2019 2:38:00 PM by  stiwa_schd (67) 1



Votes:

0

Your Vote:

Up

Down

What particular error do you get?


PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Feb 8, 2019 12:38:01 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

That issue is definitely VMWare related as in "The hardware requires newer drivers". Did you check if any updates are available? There's not much we can do to fix this :/


PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Feb 11, 2019 10:32:01 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We already used the latest customized installation .iso from Dell, so there are no newer drivers available..

Created on Feb 12, 2019 3:41:52 PM by  stiwa_schd (67) 1



Votes:

0

Your Vote:

Up

Down

We do have some customers with that issue; you'll need to contact VMWare regarding that I'm afraid :( We're just returning what we get from the Managed Object Browser API endpoint here.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Feb 13, 2019 10:44:53 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

We have the sames issue with Dell ESXi host on 6.7 VMware version. Any update for this issue ?

Thank's in advance.

Best regards,

Created on Apr 15, 2019 9:02:24 AM by  extdsmi (0)



Votes:

0

Your Vote:

Up

Down

There's nothing we can do in this regard. I discussed this issue with our VMware administrators and I need to correct my previous reply.Some updates of the vCenter change the internal way how the vendor specific drivers (Dell, HP...) communicate with the vCenter via CIM. These specific drivers need to be adjusted after an update so that they do not throw a warning via the API calls.Based on our own experience, this takes about six to eight weeks until new packages get available after an update of the vCenter. I'm afraid that this is something that we cannot fix ourselves.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Apr 15, 2019 9:29:26 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

My solution to this was eventually to create a script to bypass this. I accomplished this with PowerCLI from VMware - the PowerShell extensions to communicate with VMware.

For details I would like to refer here - cause it is easier for me to maintain the script there - assuming it would need adjustments:

https://www.it-admins.com/prtg-and-vmware-6-7-vcenter-host-hardware-status/

PS: This is a user-script and not officially supported by PRTG - just thought it might help some others with the same issue...

Regards

Florian Rossmark

www.it-admins.com

Created on Aug 8, 2019 8:19:02 PM by  Florian Rossmark (4,187) 3 2



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.