Vitaliy S. wrote: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!
Users browsing this forum: No registered users and 7 guests