I have 2 VM servers on an ESX VMWare server, and these 2 servers fail the agent monitoring constantly. This was an issue withh more servers, but we have moved them to another ESX server ad the issue for 1 resolved instantly the second required a reinstall of the agent.
The servers are both up and running and are always reachable as when I see the alert I can reach the server. Also in hosts it shows green for the agent and it is receiving data from the agent about services as far as I can tell as the graphs are there. 1 is a SQL server and the other is a secondary DC.
I have reinstalled the agent on both with the same results. Currently I have disabled the agent monitor to stop the actions, but I really need this to work. Does anyone have some ideas as to the problem?
From my troubleshooting we are thinking it might be something with the ESX server except when we moved 1 server the problem followed until a reinstall of the agent was done. THe problems really started when we moved all of our production VM's to this particular ESX to rebuild the other ESX server. I have slowly fixed it for all other servers but these 2. Moving most back to the second server helped a lot, but this server shoul dnot have the issues with just 2 VM's being hosted currently. It is speced out for about 5-8 VM's
The servers are both up and running and are always reachable as when I see the alert I can reach the server. Also in hosts it shows green for the agent and it is receiving data from the agent about services as far as I can tell as the graphs are there. 1 is a SQL server and the other is a secondary DC.
I have reinstalled the agent on both with the same results. Currently I have disabled the agent monitor to stop the actions, but I really need this to work. Does anyone have some ideas as to the problem?
From my troubleshooting we are thinking it might be something with the ESX server except when we moved 1 server the problem followed until a reinstall of the agent was done. THe problems really started when we moved all of our production VM's to this particular ESX to rebuild the other ESX server. I have slowly fixed it for all other servers but these 2. Moving most back to the second server helped a lot, but this server shoul dnot have the issues with just 2 VM's being hosted currently. It is speced out for about 5-8 VM's