ESXi 6.0 on MGMT LAN Couldn't resolve host name

[denbei]

Hellow all.
plz help me.

I found some error in zabbix_server.log.

error reason for "esxi1:vmware.hv.vm.num[{$URL},{HOST.HOST}]" changed: Couldn't resolve host name

This ESXi on MGMT LAN (no DNS),but I writen /etc/hosts.
I tried culr & ping by hostname, was good results.

my zabbix version is 3.0.1 and vShpere is 6.0

Tell me,what is problem?
where I must detect?

[frankwangzc]

I have the same issue when monitoring ESXi system.
Anyone know?
Thanks in advance.

[emz]

Same issue here. Can somebody help?

[Ruddimaster]

I have also this issue...

[ebonweaver]

Naming issues...

I'm guessing you all may have hit the same issue I did. Finally in searching for answers and re-re-reading the documentation for 3.2 I noticed this line:

"Note that “Template Virt VMware” template should be used for VMware vCenter and ESX hypervisor monitoring. The “Template Virt VMware Hypervisor” and “Template Virt VMware Guest” templates are used by discovery and normally should not be manually linked to a host."

And there suddenly I had my answer, because I was using the template that is named in a way that indicates it's the template that should be used. I'm trying to monitor a hypervisor, so I use the hypervisor template, right? Apparently not, they have named the templates poorly, and you have to RTFM to figure that out. Unfortunately since I upgraded from past versions, I don't have all these templates built in, and it's impossible to import them in many cases because of complex dependencies on other things that are not in the older version configurations, and they don't add in the upgrades, and provide no way to add later.

So seems we're on our own to try to create things from scratch based on the item documentation unless we start over with a brand new server to get the defaults. For the rest of you, if you started with 3.0 or higher just make sure you are using the right template.