Filtering through my e-mail after a short, one week, holiday I ran into an e-mail from one of my colleagues pointing me to VMware KB Article 1013013. This KB article describes one of the first patches for vCenter Server 4.

The problem is that High Availability in a vSphere 4 virtual environment may not work when a host failure occurs and the node failure detection algorithm fails when using certain IP addresses. VMware found out that this is due to the fact that all of the Service Console Port(s) or Management Network IP address(s) on an ESX host fall within the following range:

3.x.x.x – 9.x.x.x
26.x.x.x – 99.x.x.x

Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.

The problem can obviously be solved by changing (one of the) Service Console Port(s) or Management Network IP address(s) or install vCenter Server 4.0 Patch 1.

More information can be found here.

Related posts:

1. ESXi bug when changing IP address
2. vSphere network troubleshooting
3. vSphere Licensing and Options Overview
4. VMware vSphere clustering Q&A (VSP1682)
5. Upgrading VMware ESX 3.5 to ESX 4.0 (vSphere)

Tags: VMware

This entry was posted on Monday, August 24th, 2009 at 11:06 and is filed under ESX/ESXi, vCenter Server, vCenter Site Recovery Manager/High Availability, VMware. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.