vCenter - Showing a VMware ESX server not responding
Environment
Content
We received these alarms after enabled the firewall of the vCenter workstation.
Therefore, we compared those with the reference from VMware to update, and solved the host connection problem.
Reference
Update
- Vmware vCenter 4.x
Content
We received these alarms after enabled the firewall of the vCenter workstation.
Alarm 'Host connection and power state' on 10.0.0.1 sent email to it@office.local;info 11/22/2012 12:55:19 PM 10.0.0.1From the logs of the firewall, it showed some blocked connection.
Alarm 'Host connection failure' on 10.0.0.1 changed from Gray to Gray info 11/22/2012 12:55:15 PM 10.0.0.1
Alarm 'Host connection and power state' on 10.0.0.1 triggered an action info 11/22/2012 12:55:15 PM 10.0.0.1
2012-11-22 15:19:29 OPEN UDP 10.0.0.2 10.0.0.3 4306 161 - - - - - - - - -It might be some policies missed, although those would be set when installing vCenter.
2012-11-22 15:19:20 DROP UDP 10.0.0.1 10.0.0.2 54940 902 94 - - - - - - - RECEIVE
2012-11-22 15:19:30 DROP UDP 10.0.0.1 10.0.0.2 37919 902 94 - - - - - - - RECEIVE
2012-11-22 15:19:31 CLOSE TCP 10.0.0.2 10.0.0.4 4225 2222 - - - - - - - - -
2012-11-22 15:19:40 DROP UDP 10.0.0.1 10.0.0.2 55512 902 94 - - - - - - - RECEIVE
2012-11-22 15:19:49 OPEN UDP 10.0.0.2 10.0.0.3 4321 161 - - - - - - - - -
2012-11-22 15:19:50 DROP UDP 10.0.0.1 10.0.0.2 42030 902 94 - - - - - - - RECEIVE
Therefore, we compared those with the reference from VMware to update, and solved the host connection problem.
Reference
- Alarms about the host connection state changing from green to red frequently occur
- Collecting diagnostic information for VMware products
Update