VMware DRS moves VMs to other hosts creating errors

[huskgrah]

I have tried to use ESX3 and it starts to go "silly" when DRS moves virtual machines for better performance. Is there a solution to this or do I absolutely need to dedicate a license seat to monitor that node?

[rkennedy]

Can you provide more information about the error you're seeing? What's the error? Where is it appearing? Any screenshots will help as well.

[huskgrah]

When I first set up monitoring of my 4 VMware hosts, I asked the ESX3 agent to also monitor the VMs. One of many VMs originally was running on vmware-cstm1. DRS has since migrated the following VM to vmware-cstm3. Since that migration I am receiving the error:
ESX3 CRITICAL - VMware machine "Echo2003-v" does not exist

I believe I did see a note online saying that this was a problem, but I want to confirm.

[huskgrah]

VM-errors.rtf

[Box293]

The problem exists because you are monitoring the guests via the ESXi host, so once they move they can no longer be monitored as that ESXi host does not know about that guest.

I am unsure if the plugin you are using supports monitoring the guests through the vCenter server. When you do it this way, it works regardless of which ESXi host the guest is running on, as vCenter knows where the guests are.

My plugin box293_check_vmware was designed with this in mind. box293_check_vmware can be downloaded here:
http://exchange.nagios.org/directory/Pl ... re/details

There is also a wizard for it:
http://exchange.nagios.org/directory/Ad ... rd/details

I recommend checking it out, it might offer you better VMware monitoring than you currently have. It will resolve the issue you have.