Hardware information data is not available

[vertices]

I have Free Veeam One 7 running and I'm trying to monitor a couple of ESXi servers over the public internet. Some are free standalone ESXi, and other are paid and on a vCenter. I am unable to look at hardware info by selecting the host in Veeam one, and then going to the hardware tab on any host that doesn't have a full tunnel.

Now I have a couple of other hosts with full tunnel access. Those work fine. So I can only assume I have some ports wrong. However I reviewed the documentation and it appears that 443 and 5989 are required. For good measure, I have also allowed 80 and 5988. However no matter what I do, Veeam One works fine in all respects except for the hardware tab. If I have a full tunnel and using private IPs, it also works fine.

Looking that the firewalls in front of those hosts, I don't see anything being blocked. So nothing jumps out at me.

I even tried simply allowing all ports and it still didn't work.

Any ideas?





Also, if you are monitoring a vCenter, but then select a host off of that vCenter in Veeam Monitor, does Veeam One then communicate directly with the host? Or does it pull the CIM information via the vCenter it's configured with?

[veremin]

Are there any similarities between affected hosts, apart from absence of tunnel access (trying to limit the scope of potential issues)? They all are free ones, standalone, etc.? Thanks.

[veremin]

As to your question, even if the hosts are added as a part of vCenter, we still need to communicate with them directly, as it's not possible to collect some counters through VC. Thanks.

[Vitaliy S.]

Looks like a firewall issue to me... btw do you use admin or read only account to connect to these hosts?

[macgyver]

Hello anything new on this issue ?

We have a support ticket open - veeam support is perfectly taking care - but no solution yet

Veeam One works perfect except for the hardware tab.

We installed Veeam One Version 7.0R2 no more updates available (7.0.0.876)

Even in fresh test setup with esxi 5.5 / vcsa ( VMware-vCenter-Server-Appliance-5.5.0.10300-1945271_OVF10.ova) / all admin accounts in a local network

no firewall all software components fully licensed Versions >

vcenter shows all affected hosts fine with hardware Information

in Veeam One still no hardware tab / empty window


it seems to be a vmware issue ( cim communication / sfcb-watchdog ) but we are not 100 % sure

maybe there are more ideas to look at ?

we are clueless

[Vitaliy S.]

Can you please tell me your case ID, so I could take a look at this with our dev team?

[macgyver]

Hello,

here is our Case ID :

Case 00520564

[macgyver]

we now have installed

R2a Update (build 7.0.0.919)

still same issue

[Vitaliy S.]

Yes, I don't believe it has something to do with Veeam ONE version. Given that you have required permissions in-place and CIM server is up and running, then the reason for this should be easily detected after reviewing debug logs.

BTW, can you navigate to the "problematic" host -> Configuration -> Security profile -> Service properties -> CIM Server? Is it running?

[macgyver]

all necessary services up & running

network test :

veeamone server > telnet > esxi host

port 80
port 443
port 5989
port 5988

all ports open and reachable

even if we put the esxi host standalone to veeam one with full root credentials

> no hardware tab / empty window

[macgyver]

veeamdcs.log

i readded this host standalone to veeam one ( root account )
here are the results

[Vitaliy S.]

Macgyver, please avoid posting log snippets as it is advised by our forum rules. I have already asked your engineer to give our dev team your debug logs for review. Let's see what they can find out.

[macgyver]

ok sorry

[macgyver]

anything new ?

mac

[Vitaliy S.]

Hi Mac, your engineer says he cannot reach you via email. Let me follow up your case one more time.

[hux]

Did this issue ever get resolved? I'm having the same kind of problem with several of my ESXi servers (the majority in fact): I get either the "Host hardware status" error or the "hardware sensors collection failure" error.

[Vitaliy S.]

Hi hux,

There was a patch released for host hardware monitoring, though I'm not sure it applies to your situation, as debug logs review is needed here. Do you have a support case opened?

Thanks!

[hux]

I opened support case #00719966 just now. However, I was unable to attach any logs. (each time, I get a response that my file was not attached).

[Vitaliy S.]

Do you mean you cannot upload logs to the FTP server provided by our support team?

[dcrudo]

we had the same issue...thanks to another post we managed to solve it!
The issue was related to a different way to collect the information in V8 than V7.

Now it seems the DNS configuration in ESXi plays a role... i got almost crazy, but once fixed the DNS in ESXi and rebooted everything is now working.

1) give a full host/domain name to the ESXi under configuration > DNS settings
2) make sure the DNS record exists in the DNS server used by ESXi and Veeam

The information given by the alarm should include that it might come from a DNS misconfiguration or missing record.

Dave

[Vitaliy S.]

Yes, we will update the KB for this alarm. Thanks for the heads up.

[Vitaliy S.]

For future readers - DNS configuration will no longer be required for hardware sensors monitoring, as we are working on a different method of obtaining this data.