We've encountered an issue in our VMware ESXi 5.5 environment where VMs that have been moved using vMotion from one host to another are never discovered again. I've also noticed this happen if a VM is powered off, removed from the host's inventory, added to another host's inventory, and then powered on.
We're monitoring each host individually since vCenter 5.5 doesn't seem to like to communicate with Zabbix and using the default discovery rules.
Any help you can provide would be appreciated, last time this happened I had to delete all the hypervisors and let everything discover from scratch at the cost of a lot of historical data.
We're monitoring each host individually since vCenter 5.5 doesn't seem to like to communicate with Zabbix and using the default discovery rules.
Any help you can provide would be appreciated, last time this happened I had to delete all the hypervisors and let everything discover from scratch at the cost of a lot of historical data.
Comment