CMK version: Checkmk Enterprise Edition 2.2.0
OS version: Debian 11
I just updated from 2.1.0p28cee to 2.2.0cee. After the update, vSphere integration from all vSphere servers no longer works. All services of the vSphere Server are set to Unknown, and the individual servers report that they no longer receive piggyback data. Under 2.1.0 it worked without problems with the same settings
For your ESX or vSphere server you can check the special agent call with.
cmk -D hostname
in the line agent you find the command line for your special agent. This you can execute manually to check if it works or not.
I just implemented the vsphere monitoring on 2.2.0 with esxi being created as piggyback hosts at a customer site and that worked out pretty fine.
What does the Check_MK Service tell you for the vsphere server host?
And please do as well what Andreas said, you can then see directly more details.
I found the solution, it was a layer 8 problem … To prevent errors with other devices in the same folder (which are ping-only), I’ve set the integration to “No API integrations, no Checkmk agent”. But that disabled the vSphere check too. After enabling it again for the specific hosts it works!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.