Warning - Sensor Proc 1 level 1 crache .. equal unknown

[geraldb]

Hi,

I've just installed VeaamONE (7.0.0.949) and added an ESXI-Standalone Server (5.1).
After I've added the server I recveived the following warning:

Description
Sensor "Proc 1 Level-1 Cache DeviceID:1041.01" equal Unknown
Sensor "Proc 1 Level-2 Cache DeviceID:1042.01" equal Unknown
Sensor "Proc 1 Level-3 Cache DeviceID:1043.01" equal Unknown
Sensor "Proc 2 Level-1 Cache DeviceID:1041.02" equal Unknown
Sensor "Proc 2 Level-2 Cache DeviceID:1042.02" equal Unknown
Sensor "Proc 2 Level-3 Cache DeviceID:1043.02" equal Unknown
Knowledge
One of the hosts' hardware sensors has changed its status.
Cause
Monitoring hardware sensor information allows tracking physical hardware status.
Sensor's status is automatically refreshed by vCenter Server's request.


in the vSphere client -> heath status everything seems fine ..
http://i.imgur.com/qw4XXHv.jpg

I've resolved it once because but it instantly re-appears as a warning ..

[geraldb]

VeeamONE health view ..
http://i.imgur.com/yw3TW0F.png

[Shestakov]

Hi Gerald,

The issue is known and was discussed in the forum.

The problem of the warning appearance (most likely) is that VMware reports "Read Policy: unknown" state for these sensors.
Our support team worked with a number of clients having the same problem and contacted VMware for a clarification. We`ve received an answer that the problem is caused by some hardware vendors and VMware has a KB article describing the situation.

So we`ve decided to revise sensors collection mechanism for our upcoming Veeam One v8 release, which is going to be on a shelf in November.
For now I can suggest you to contact our support team for having Webex and making sure the problem is "Read Policy: unknown" status. If so, it is just a warning which should not harm your infrastructure or cause any problems.

P.S. Once you contact Veeam support team, please provide a support case number.
Thank you!

[geraldb]

Hi Shestakov,

thanks for your answer.
I think we don't need the veeam support to have a look at it because we have on all 3 HP ML350G6 Servers the same problem... seems to be unlikely that it is a real hardware issue.
But i have another short questions.
If I add this Warning to an exlusion, all further "host hardware status" issue will be ignored ? (e.g. storage / power supply problems)
Is there a possiblity to just ingore THIS single host hardware status issue ?

thanks
gerald

[Shestakov]

Gerald,

You are correct, you can customize the warning in accordance to your needs.
For this purpose, go to Veeam Monitor > Alarm Management tab > among Host alarms pick Host hardware status and Edit it.
Go to Rules and set Rule Types/Parameters as you want.

Thank you.

[geraldb]

Hi Shestakov,

did i misunderstood you or should this problem be solved with Version 8 ?
We updated today and get this warning now: (in the vsphere client health status everything is fine)

Description
Sensor "System Chassis 1 UID Light" equal Unknown
Sensor "System Chassis 2 Int. Health LED" equal Unknown
Sensor "System Chassis 3 Ext. Health LED" equal Unknown
Sensor "Proc 1 Level-1 Cache" equal Unknown
Sensor "Proc 1 Level-2 Cache" equal Unknown
Sensor "Proc 1 Level-3 Cache" equal Unknown
Sensor "Proc 2 Level-1 Cache" equal Unknown
Sensor "Proc 2 Level-2 Cache" equal Unknown
Sensor "Proc 2 Level-3 Cache" equal Unknown
Sensor "Power Supply 1 Power Supply 1: Presence detected" equal Unknown
Sensor "Power Supply 2 Power Supply 2: Presence detected" equal Unknown
Knowledge
One of the hosts' hardware sensors has changed its status
Cause
Monitoring hardware sensor information allows tracking physical hardware status.
Sensor's status is automatically refreshed by vCenter Server's request
Resolution
For more information on the hardware sensor please navigate to Hardware tab in Veeam ONE Monitor. Also check the hardware on the host triggered the alarm
External
Refer to VMware's online documentation and to corresponding KB article for more information

[Vitaliy S.]

Please install our latest patch (available through support team) to resolve that. Thanks!

[geraldb]

Thanks, perfect.
The patch resolved the issue.

[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