Hi,
Hope you are good!!
We are trying to monitor our Vcenter server from Checkmk, followed this documentation:
But , in host properties, what should we give on the agent part , we have left default
and when I am trying to run the connection test getting this error, although my ping is responding perfectly
Also the rule is configured (VMWare ESX via Vsphere)
BR
//Prachi
Hi,
Well, the ping is working from checkmk to Vcenter server, also since vcenter is an appliance and we are managing it through VMware ESX rule from checkmk then what other port needs to be opened?
We are using root login credentials of Vcenter in the VMware ESX via vSphere.
BR
//Prachi
ping → ok…
the special agent use https/443
telnet 443?
in case of security, i would recommend you to create a “read only” user on your vcenter for using it in cmk.
Hi,
Lovely, thank you.
Yes telnet 443 is not working from checkmk to vcenter server and so I feel its giving api error…
One more thing, can we monitor Poweredge Dell chassis Mx7000 also by Vmware ESX via vSphere rule? At the moment we are monitoring the Dell chassi using SNMP v1/v2 without giving the credentials like below…is it fine?othewise will ask my network team to open port 443 for both Chassi and vcenter as they both are on different network
BR
//Prachi
you mean the hardware on which esx is installed? dell has an idrac-interface which could be monitored by snmp.
to answer you question: no, this special agent is only for the v-center api.
hope that helps…
Not via vSphere, you need to monitor the ESX host direct. For that you have an option in the VMware rule.
You will get then the check Hardware Sensors:
This check checks the state of all of a VMWare ESX host system's hardware sensors - including temperatures, fans, power supplies, memory DIMMS, hard disk, an others. In order to avoid network traffic the agent sends only information about sensors that are not in green state.
Note: Due to a caching problem on the ESX host system side, this check occasionally reports incorrect sensor data. This may mean that the sensor appears to be stuck in an unhealthy state. You can find more information here: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1037330
Basically its using IPMI locally in ESX OS.
General I recommend IPMI over LAN to monitor Server Hardware because it is vendor independent which SNMP is not. For newer servers the solution is redfish which is AFAIK currently only available as a community plugin from exchange.
Hi,
Thank you, my doubts are cleared.
BR
//Prachi
Hi,
Yes, absolutely…in few of our Dell esxi hosts which we are monitoring via Vmware ESX via Vsphere rule, could see Hardware sensors in services…that means this parameter hardware sensor is related to the hardware on which the esx is installed.
Good to know, I had put it in disabled service, will put this in monitored service now:)
BR
//Prachi
If you want you can test the actual version of my Redfish special agent for the iDRAC management interface. It should now work also with MX7000 bladecenters.
Pay attention that you need to install as a site user the Redfish libraries inside your monitoring instance, if you want to try it.
Thank you so much!!!
We test and let you know the results.
BR
//Prachi
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.
