Hardware sensors collection failure after V8 upgrade

Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Tue Nov 11, 2014 11:12 am

In the case from Iain, the issue seems to be related to names resolution (our support team has find out it after reviewing job logs). Let's see what our dev team can say after looking through your debug information.
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby mcwill » Tue Nov 11, 2014 12:03 pm 3 people like this post

Yes, on our system the cause was the affected vSphere hosts; Configuration -> DNS and Routing -> Host Identification -> Name = localhost

Changing the above so it matched the DNS entry solved the problem.

Regards,
Iain
mcwill
Enthusiast
 
Posts: 64
Liked: 10 times
Joined: Sat Jan 16, 2010 9:47 am
Full Name: Iain McWilliams

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby macgyver » Tue Nov 11, 2014 12:10 pm

Hi,

issue resolved with veeam Support

thanks

Regards

Mac
macgyver
Influencer
 
Posts: 15
Liked: 2 times
Joined: Thu Jan 20, 2011 6:03 pm

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby northrundicandus » Wed Nov 12, 2014 3:44 pm 1 person likes this post

It appears that the new CIM-SMASH protocol method of Hardware Sensors collection now requires DNS resolution of the individual ESX hosts to work correctly. Previously with v7 I only needed the vCenter server to be resolvable, and not for the individual ESX hosts managed by that vCenter.

Does this mean that customers who add their ESX servers to vCenter by IP address are out of luck when it comes to this kind of monitoring?
northrundicandus
Service Provider
 
Posts: 14
Liked: 3 times
Joined: Thu Aug 11, 2011 9:01 pm
Full Name: Joe Ross

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby macgyver » Wed Nov 12, 2014 6:22 pm

hello,

no your are not out of luck,

we have the same setup ( IP )

just make sure the veeamone server is able to resolve ( reverse lookup ) the dns names ( FQDN ) of the esxi host(s) in your vcenter(s) !

you can do this by static dns entries in your dns server ( more flexible ) or just use your local hosts file on the veeam one server = manual adding ip addresses and FQDN,
if later IP addresses or names change please don't forget to change them here as well.

This solved our problems with the hardware tab / display in Veeam One 8 ( and Veeam One 7 as well )

Regards

Mac
macgyver
Influencer
 
Posts: 15
Liked: 2 times
Joined: Thu Jan 20, 2011 6:03 pm

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Wed Nov 12, 2014 10:20 pm

northrundicandus wrote:Previously with v7 I only needed the vCenter server to be resolvable, and not for the individual ESX hosts managed by that vCenter.

Does this mean that customers who add their ESX servers to vCenter by IP address are out of luck when it comes to this kind of monitoring?

Previously we were using vSphere API to monitor hardware sensors, but when we have raised one issue with VMware regarding this method, they have advised us not to use this method and use CIM-SMASH.

The case with ESXi servers added by IP address, should not be an issue. Let me check it with the dev team tomorrow.
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby northrundicandus » Wed Nov 12, 2014 10:25 pm 1 person likes this post

Vitaliy S. wrote:The case with ESXi servers added by IP address, should not be an issue. Let me check it with the dev team tomorrow.


I determined this is an issue if the customer defined a hostname and DNS domain in the ESX install, but added the ESX server to vCenter with an IP address instead. Adding a hosts file entry on the Veeam Monitor server is a quick fix for this until the customer can remove and add the server back to vCenter using a hostname instead.
northrundicandus
Service Provider
 
Posts: 14
Liked: 3 times
Joined: Thu Aug 11, 2011 9:01 pm
Full Name: Joe Ross

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Wed Nov 12, 2014 10:27 pm

Is there any reason to add ESXi host via IP address instead of its hostname? Just trying to confirm that I didn't miss any use case.
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby northrundicandus » Wed Nov 12, 2014 10:32 pm

I've seen this a lot in the field with small vSphere deployoments. Customers don't know they need to add a DNS record for their ESX hosts to their AD integrated DNS servers, so they end up adding their ESX hosts to vCenter by IP address instead.
northrundicandus
Service Provider
 
Posts: 14
Liked: 3 times
Joined: Thu Aug 11, 2011 9:01 pm
Full Name: Joe Ross

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Wed Nov 12, 2014 10:35 pm

I never remember my host IP address, but I do know its hostname all the time. :)

Ok, we will discuss this scenario internally and I will update the thread with the requirements for CIM-smash monitoring feature.
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby macgyver » Thu Nov 13, 2014 8:04 am

Hi Vitaliy,

this would be great !

i never thought of the solution veeamsupport came up with.

on the one hand Veeamone/CIM-Smash can use ip-addresses for all servers but on the other hand for backwards communication to the infrastructure it must be able to resolve the fqdn of the esxi servers for hardware monitoring

no chance of working with ip addresses !

maybe you can explain this to me ;-)

it's by design ? :-)

Regards

Mac
macgyver
Influencer
 
Posts: 15
Liked: 2 times
Joined: Thu Jan 20, 2011 6:03 pm

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby firmdale » Thu Nov 13, 2014 8:29 am

Case # 00675767

Same issue here. Adding DNS records resolved issue with ONE connecting to hosts but still seeing below:

Description
Sensor "Memory" equal Warning
Sensor "PROC 2 DIMM 4: Physical Memory Module Socket=04 on ProcessorBoard=2" equal Warning
Sensor "System Board 8 Memory: Uncorrectable ECC" equal Alert
Sensor "System Chassis 1 UID Light" equal Unknown
Sensor "System Chassis 2 Sys. 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 "Disk or Disk Bay 1 C1 P1I Bay 1: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 1 C1 P1I Bay 1: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 2 C1 P1I Bay 2: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 2 C1 P1I Bay 2: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 3 C1 P1I Bay 3: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 3 C1 P1I Bay 3: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 4 C1 P1I Bay 4: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 4 C1 P1I Bay 4: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 5 C1 P2I Bay 5: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 5 C1 P2I Bay 5: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 6 C1 P2I Bay 6: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 6 C1 P2I Bay 6: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 7 C1 P2I Bay 7: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 7 C1 P2I Bay 7: Hot Spare" equal Unknown
Sensor "Disk or Disk Bay 8 C1 P2I Bay 8: Drive Present" equal Unknown
Sensor "Disk or Disk Bay 8 C1 P2I Bay 8: Hot Spare" equal Unknown
Sensor "Power Supply 1 Power Supply 1: Presence detected" equal Unknown
Sensor "Power Supply 2 Power Supply 2: Presence detected" equal Unknown
firmdale
Novice
 
Posts: 9
Liked: 1 time
Joined: Thu Sep 09, 2010 3:32 pm
Full Name: Firmdale Hotels IT Department

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Thu Nov 13, 2014 9:31 am

These sensors do not health state in the vSphere Client (this column) for them is empty, that is why they are reported as unknown. We are working on the workaround for this behavior. Thanks!
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby Vitaliy S. » Thu Nov 13, 2014 10:40 am 1 person likes this post

macgyver wrote:i never thought of the solution veeamsupport came up with.

on the one hand Veeamone/CIM-Smash can use ip-addresses for all servers but on the other hand for backwards communication to the infrastructure it must be able to resolve the fqdn of the esxi servers for hardware monitoring

no chance of working with ip addresses !

maybe you can explain this to me ;-)

it's by design ? :-)


If you have ESXi hosts added by IP address, you can still make it work by following either of these ways:

1. adjust "hosts" files on the Veeam ONE server in order to resolve host name
2. do the required changes in the vCenter Server config (Configuration -> DNS and Routing -> Host Identification)

The explanation of this requirement is pretty straight forward. When the API call is sent to the host to get the data for hardware sensors, ESXi host returns it's name (configured in the option 2 above) and then this name is used to establish the connection tunnel for data retrieval. If Veeam ONE cannot resolve the name of the host, then it cannot connect to it, thus hardware sensors data is not available.

In version 7 we were using different mechanism of getting this data, and when we have discovered an issue with the API, have decided to switch to a more reliable way of monitoring hardware senors.

Hope this makes sense!
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Hardware sensors collection failure after V8 upgrade

Veeam Logoby macgyver » Thu Nov 13, 2014 5:14 pm

Hi Vitaliy,

all clear as day ;-)
If I'd known about this earlier ;-)

Thanks

Regards

Mac
macgyver
Influencer
 
Posts: 15
Liked: 2 times
Joined: Thu Jan 20, 2011 6:03 pm

PreviousNext

Return to Veeam ONE



Who is online

Users browsing this forum: No registered users and 2 guests