Storage not displaying correctly on host connected to vCent

[Fiskepudding]

Hello

I am using v 6.0.

If I look at vCenter (with vSphere) I see this (all individual disks showing):


If i look at it veeam one i see this. individual disks not showing:


So I added a this particular host as a standalone host on veeam one and it shows the disks:


So it seems to have something to do with the vCenter. But what?...

We have installed the LSI controller VIB files on the host.
Have also restarted vCenter server.

[Vitaliy S.]

Hello Espen,

You're spot on! The list of hardware sensors available through Managed Object Browser in vCenter Server and ESX(i) is a bit different. You can check that using these instructions.

Currently Veeam ONE v6 is relying on the data available through MOB, however in our next version which is coming this year we will be using CIM over XML protocol to obtain hardware data directly from ESX(i) hosts. With this approach you will have a complete view of ALL hardware sensors of the ESX(i) hosts.

Thank you!

[Fiskepudding]

Ok, sounds good.
But the strange thing is that we have 2 other identical hosts, witch shows fine in veeam one, even when listed under vCenter.
I find it strange they dont behave the same way.

[Vitaliy S.]

Most likely these hosts have a different set of hardware sensors in Managed Object Browser, even though they have the identical hardware.

[Fiskepudding]

Interesting, the sensor cout on the 3 idnentical servers are:

ESX1: 193 -This shows the disks in Veeam one
ESX2: 191 - This is the one that does NOT show disks in veeam one (but in vCenter/vSphere)
ESX3: 191 - This also shows the disk in Veeam one

Oh well, I just migt wait for the new version and se if that helps.

[Fiskepudding]

ehhm..
actually ESX1 has two more disks then 2 and 3. So that could make up for the different numbers.

That leaves esx2 and 3 as identical. But differnet behaviour when displaying HW in Veeam one.

[Vitaliy S.]

We have investigated this behavior with VMware and their support engineers have confirmed that the list of MOB hardware sensors might be different to what you see in vCenter Server/ESX(i) server GUI. That is why have decided to address this issue in our next update.