Comments on: VMware: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 2 http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/#utm_source=feed&utm_medium=feed&utm_campaign=feed It's all about virtualization... Tue, 07 Feb 2012 10:38:16 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Pedro http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/comment-page-1/#comment-4033 Pedro Fri, 11 Nov 2011 13:11:02 +0000 http://blog.vmpros.nl/2009/11/18/test-post-part-2/#comment-4033 Hi, I have a problem when I run jointool, then I think roles and permissions as Node 1 to Node 2 change not see, he could do? Thanks. Hi,
I have a problem when I run jointool, then I think roles and permissions as Node 1 to Node 2 change not see, he could do?

Thanks.

]]> By: Sander Daems http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/comment-page-1/#comment-2113 Sander Daems Sun, 17 Jan 2010 16:14:24 +0000 http://blog.vmpros.nl/2009/11/18/test-post-part-2/#comment-2113 Windows Server 2008 64bit Enterprise editions are supported for VC 4.0 (KB Article: 1009080) You installed your cluster with this article? When (in my case) cluster node1 is down, he move the groups, my VC client also disconnect.. but with a reconnect everything is still online and can manage my vCenter (node2) again. Maybe your timeout for reconnect is too low, or it takes too much time for moving the groups or starting the services? Reconnection is a normal procedure. Make sure you got your "vCenter Server Name" (one of the last screenshots) in your DNS server added and your vCenter settings. Make sure your "vCenter Managed IP" is correct, thats your cluster ip.. I hope you can solve your problem with one of these solutions Windows Server 2008 64bit Enterprise editions are supported for VC 4.0 (KB Article: 1009080)

You installed your cluster with this article? When (in my case) cluster node1 is down, he move the groups, my VC client also disconnect.. but with a reconnect everything is still online and can manage my vCenter (node2) again.

Maybe your timeout for reconnect is too low, or it takes too much time for moving the groups or starting the services? Reconnection is a normal procedure.

Make sure you got your “vCenter Server Name” (one of the last screenshots) in your DNS server added and your vCenter settings.

Make sure your “vCenter Managed IP” is correct, thats your cluster ip..

I hope you can solve your problem with one of these solutions

]]> By: vCenterCluster http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/comment-page-1/#comment-2112 vCenterCluster Sun, 17 Jan 2010 02:25:01 +0000 http://blog.vmpros.nl/2009/11/18/test-post-part-2/#comment-2112 Quick question, was the failover seamless? I lose the connection to the VI client and then all the hosts show disconnected on the 2nd node in the windows cluster and I must click the "connect" button from within the VI client. Is this the expected vCenter 4.0 behavior? I am using Windows 2008 64-bit Enterprise Edition and vCenter 4.0 Update 1 in a 2 node MSCS Failover cluster configuration. Is this suppossed to work seamlessly? I am using two physical machines for this. Quick question, was the failover seamless?
I lose the connection to the VI client and then all the hosts show disconnected on the 2nd node in the windows cluster and I must click the “connect” button from within the VI client. Is this the expected vCenter 4.0 behavior?

I am using Windows 2008 64-bit Enterprise Edition and vCenter 4.0 Update 1 in a 2 node MSCS Failover cluster configuration.

Is this suppossed to work seamlessly?
I am using two physical machines for this.

]]> By: Sander Daems http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/comment-page-1/#comment-2077 Sander Daems Fri, 20 Nov 2009 07:39:11 +0000 http://blog.vmpros.nl/2009/11/18/test-post-part-2/#comment-2077 See also Update 1 vSphere: Enhanced Clustering Support for Microsoft Windows – Microsoft Cluster Server (MSCS) for Windows 2000 and 2003 and Windows Server 2008 Failover Clustering is now supported on an VMware High Availability (HA) and Dynamic Resource Scheduler (DRS) cluster in a limited configuration. HA and DRS functionality can be effectively disabled for individual MSCS virtual machines as opposed to disabling HA and DRS on the entire ESX/ESXi host. Refer to the Setup for Failover Clustering and Microsoft Cluster Service guide for additional configuration guidelines See also Update 1 vSphere:

Enhanced Clustering Support for Microsoft Windows – Microsoft Cluster Server (MSCS) for Windows 2000 and 2003 and Windows Server 2008 Failover Clustering is now supported on an VMware High Availability (HA) and Dynamic Resource Scheduler (DRS) cluster in a limited configuration. HA and DRS functionality can be effectively disabled for individual MSCS virtual machines as opposed to disabling HA and DRS on the entire ESX/ESXi host. Refer to the Setup for Failover Clustering and Microsoft Cluster Service guide for additional configuration guidelines

]]> By: VMware: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 1 | VMpros.nl http://blog.vmpros.nl/2009/11/18/clustering-vcenter-server-40-using-microsoft-cluster-services-part-2/comment-page-1/#comment-2074 VMware: Clustering vCenter Server 4.0 Using Microsoft Cluster Services Part: 1 | VMpros.nl Wed, 18 Nov 2009 16:39:11 +0000 http://blog.vmpros.nl/2009/11/18/test-post-part-2/#comment-2074 [...] Check Part 2 [...] [...] Check Part 2 [...]

]]>