WJPatton.com » vcenter

VMware KB1024051 – MSCS vCenter Clustering Unsupported

wjpatton — Mon, 19 Jul 2010 14:40:13 +0000

A newly published VMware KB1024051 article now states that “VMware does not support third party clustering products.”

This means that Microsoft Clustering Service or Veritas Cluster Services are not supported for vCenter 4.x.

Please take this into account when designing mission-critical vCenter deployments. These customers should be looking at VMware vCenter Server Heartbeat with VMware HA instead of third-party clustering products.

VMware vCenter Server Heartbeat

VMware Clustering vCenter Server 4 on MSCS

wjpatton — Tue, 26 Jan 2010 23:21:23 +0000

*NOTICE* As of July 16, 2010 – VMware KB1024051 – has been published stating that “VMware does not support third party clustering products.” The instructions below should not be used for any production or supported environment.

VIOPS has a good document on how to cluster the vCenter services on MSCS. Things have changed slightly from 2.5 and though most of the steps will be old news for some, there are a couple changes so be sure to review before proceeding with your Install/Upgrade projects. It does have a nice section on upgrading existing clusters as well.

Get the document here.

One special note I would point out is running the “jointool.bat” for replicating roles at the end of your cluster config.

VMware KB1016262 – vCenter Agent Install Fails on ESXi 4 Host

wjpatton — Thu, 10 Dec 2009 16:52:34 +0000

VMware just posted an alert on this for ESXi 4 Hosts managed by either vCenter 4 or 4 Update 1. If you remove and re-add the Host to vCenter, or upgrade vCenter to Update 1 you may experience this issue.

At this time, there is no official fix, however it appears a reboot should fix the issue but with the Host disconnected from vCenter; vMotion is not an option and the disconnect may trigger HA, but I would hope that you have placed this host into Maintenance Mode prior to disconnecting from vCenter…right? Also, HA should have been disabled prior to your Update 1 patch…you did that as well, right?

Read the official VMware Alert here.