Thanks for the hint. It seems that’s the culprit. Not sure why going to v2.0 became an issue all of a sudden, but I am considering to disable SNMP discovery on the ESXi hosts to fix it. Maybe there are two other better solutions:
1 - Create a rule to disable checks like: hr_cpu, hr_fs, hr_mem, if64 for SNMP (this one I know where it is);
2 - Better yet, how to create a rule that will disable the conflicting ones: esx_vsphere_hostsystem_cpu_usage, esx_vsphere_hostsystem_mem_usage, esx_vsphere_counters_uptime, esx_vsphere_counters_if?
Regards,