Hardware sensors collection failure after V8 upgrade

[saeed_sqs_20]

Alarm details
Description
Fired by event: VeeamHardwareSensorsCollectionEvent
Event description: Unable to connect to 192.168.2.20. Failed to retrieve host hardware information.
Initiated by: Veeam ONE Monitor (IT)
Knowledge
Veeam ONE server failed to collect host hardware information
Cause
Host hardware sensors information is retrieved via CIM-SMASH protocol, sensors status is defined by the firmware of the host
Resolution
Verify that CIM server on the ESXi host is up and running and confirm that connection account has sufficient permissions on the host via the vSphere Client (Host -> CIM -> CIM interaction)

[Shestakov]

Hello Saeed,
You need to install a patch to resolve the issue. Please contact Veeam technical support to get it.
Thanks!

[albertwt]

Hello Saeed,
You need to install a patch to resolve the issue. Please contact Veeam technical support to get it.
Thanks!

I've been told not to install the Patch v1 by the support team, so in this case we are waiting for the patch no.2 to come and fix this issue.

[Shestakov]

Albert,
Right, patch 2 is already around the corner.
Veeam technical support team will provide it to you as soon as it is done.
Thanks.

[ddayton]

I also have the same problem, which started after upgrading my Veeam B&R + ONE server from version 7 to version 8.

I have not changed any hardware, only upgraded Veeam. I am running ESXi 5.1 on a standalone host ( no vSphere ). I have a second host, but no running VMs since it is only a target for replication. ONE is only running on the production host. The Veeam server is also a VM.

If I look at the VMware Client console under Configuration/Health Status it shows all status as normal. All of the temperatures, fans ,voltages, etc. have values. CIM is running and I am only using the root account on the server.

I do know that this was working under Version 7, so I am not sure what to do next. I was planning on monitoring this forum and see is a solution appears soon before I bother opening a case since it is not critical. I have the IPMI monitoring the server health and it will auto e-mail me if there is a problem.

I resorted by date descending and found the notes about DNS and host name verses IP. I updated the Veeam servers hosts file, but haven't seen the error clear. Can't restart now because backups are running, so I'll check it tomorrow and update the post.

So I opened up a ticket and received a patch, however the patch is simply to ignore the error for now. So hoping to see a fix in the next patch. It worked in Version 6 & 7.

[Benedict]

Hello.
Got a subj problem after updating v7 -> v8.
Can I get latest patch w/o ticket?

[albertwt]

Hello.
Got a subj problem after updating v7 -> v8.
Can I get latest patch w/o ticket?

Not possible at the moment Dmitry,

because the ptch number 2 is not released yet.

[Benedict]

Not possible at the moment Dmitry,

because the ptch number 2 is not released yet.

At this moment, not even patch1 installed on my VeaamONE. Maybe patch1 can resolve my sensors failure error.

[albertwt]

At this moment, not even patch1 installed on my VeaamONE. Maybe patch1 can resolve my sensors failure error.

No, it iwll not resolve your sensor false alarm Dmitriy. The work around so far is to disable the alarm and wait until the patch Number 2 is released, hopefully sometimes this week or next.

[Shestakov]

For now it`s not recommended to install the existing patch, since it can cause other issues, that`s why it`s so-called "a pilot version of patch 1". If you have already installed it, we recommend to install a private hot-fix which is to solve the additional issues. Having this patch your errors will be ignored.
The new patch (so-called patch 2) is going to be released soon. Here the sensors collection mechanism is redesigned and tends to solve the errors in contrast to ignoring it. We are currently working on the final stage of it and hope to release it soon.
Thanks!

[Shestakov]

Got a subj problem after updating v7 -> v8.
Can I get latest patch w/o ticket?

You can contact Veeam technical support to be notified and provided as soon as the patch is released. Same day we will make it available to download on this forum.
As I wrote before, you can ask the support team to give you a pilot version of the patch, but it`s not recommended.
Thanks.

[eijja]

Hi,

Just wondering if this patch is available. I am also experiencing this issue.

Thanks!

[Shestakov]

Hi Andreaa,
Still working on it. We will announce here as soon as the patch is done.
Thank you!

[Vitaliy S.]

Updated patch is in the pilot stage. You can contact our technical team to obtain it.

[albertwt]

Updated patch is in the pilot stage. You can contact our technical team to obtain it.

So when is it going to be finalised as GA ?

[Shestakov]

Albert,
Hopefully it will take 1-2 weeks, but might take longer.
Thanks.

[albertwt]

Albert,
Hopefully it will take 1-2 weeks, but might take longer.
Thanks.

Ok, it seems that thepatch has come out earlier than expected, today just now I've installed VeeamONE_8.0.0.1615_Patch#1.exe

it resolved all of my problem with:

1. hardware performance collection failure.
2. false alarm re-occurring after manually acknowledged.

Thakns Veeam Support & development team for the correct patch this time

[Vitaliy S.]

Yes, it is in the pilot stage, glad that all of your issues have been resolved!

[Benedict]

Hello.
Can I get patch download link?

[Shestakov]

Dmitriy,
Please contact Veeam technical support to get it.
Thank you!

[Benedict]

Thought I already did it, through this thread =)

[Shestakov]

It`s a community forums, not a technical support.
Support engineers don`t review the forums.
Link to the technical support is here.
Thanks.

[Vitaliy S.]

For all future readers - if you experience the same problem, please apply our latest patch which is now GA > http://www.veeam.com/kb1986

[weeyin]

We are running Veeam ONE v8 to monitor our Vmware estate (running that latest build of ESXi 5.5) and within Veeam ONE we are seeing hardware status alarms all the time. Things like this are displaying:

http://1drv.ms/1EPPgZ1

While our vSphere client is reporting things like:

http://1drv.ms/1EPPkYR

It looks like there is an inconsistency within the monitoring between the two. Is this a bug or am I missing something?

Support Case ID: 00910796

[Shestakov]

Hello Sarah,
What is the build number of your Veeam One version? The problem you`ve described was solved in the first patch(update), and since then another update(2) has been released. Please install it.
Thanks!

[weeyin]

Hello Sarah,
What is the build number of your Veeam One version? The problem you`ve described was solved in the first patch(update), and since then another update(2) has been released. Please install it.
Thanks!

We are running 8.0.0.1569, will look at installing update 2 asap, thanks for the help!

[Shestakov]

You are welcome Sarah,
Looks like the update will solve the problem, since it`s a known issue for your current product version.
Thanks!