Dear All,
We have installed and have been running vCenter Heartbeat for a while now but we have a problem that I'd appreicate some advice on.
It appears that after a while the computer account password get's changed on the primary node, and the secondary node is effectively kicked off the domain - can't log on, can't start the vCenter services...
Are we doing something wrong here??!
Thanks
That sounds as if both nodes have the same ID in AD (SID, NetBIOS name). Where they cloned?
AWo
VCP 3 & 4
Author @ vmwire.net
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
That's correct, the secondary is a direct clone of the primary and as such they share the same computer account. I thought this was how it was meant to be configured?
Regardless of the VMware stuff or what you running on any Windows box, as soon as two machines are member of an AD they must have a different identity. That means a different NetBIOS name and SID. What has happend is that one host changed the secure channel password between DC and member server and the other one didn't (can't) know about that and lost the connection thereby.
Having two vCenter server doesn't mean you have to clone the base OS. Only vCenter gets installed twise and the second installation becomes themirror of the first one.
Ever read this http://pubs.vmware.com/vsp40/install/c_install_vc_client.html ?
AWo
VCP 3 & 4
Author @ vmwire.net
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
I understand that AWo, but in the case of Heartbeat, the machines are never on the network or domain at the same time anyway (packet filter comes in to play).
In the Heartbeat doco (http://www.vmware.com/pdf/heartbeat_55_reference_guide.pdf) it states "The clone must be 100% with no changes to the Name, SID, or domain membership."
But if that's the case, I can't understand how it will ever work, unless it syncs the computer account passwords between the two nodes?
All very confusing.
rsandlan schrieb:In the Heartbeat doco (http://www.vmware.com/pdf/heartbeat_55_reference_guide.pdf) it states +"The clone must be 100% with no
changes to the Name, SID, or domain membership."+
Ah, O.K., didn't know that....but it seems that both were online once. That might have caused this.
AWo
VCP 3 & 4
Author @ vmwire.net
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
Ok, answer...!
Heartbeat changes the following registry key to "1" to prevent the password from being changed and becoming out of sync with the secondary node.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange
Group Policy changed this setting back to "0" - thereby causing our problem.
Hope this helps anyone else with the same problem,
Richard
Thanks! Good to know.
AWo
VCP 3 & 4
Author @ vmwire.net
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
What did you do to recover from this issue?
did you have to rebuild the heart beat cluster?