vSphere 5.x Tip To Toe: Installing vCenter Server Heartbeat v6.6
This is a product that really is not given its proper credits, by customers at least whom do not see paying a bunch of k$s to protect their vCenter server properly, any way we had a bid and this product was included so usually when going through an RFP and there is something that I do not grasp from tip to toe then its lab time and afterwards its notes, notes and some ore notes.
Off to arms then!
What I didn’t know about vCenter Server Heartbeat that it was powered by Neverfail and I’ve worked with this product a couple of times for customers who demanded high availability for their SQL and ORACLE servers, in hereunder notes I will be covering the virtual to virtual scenario because from my humble point of prospective this will be the most used.
- 1 IP address which will represent the service hosted by the vCenter server so if your current vCenter server is named vCenterServer and its IP address is 192.168.1.10 then the service name which will be high available will be vCenterServer and its IP address will be 192.168.1.10.
- 2 IP addresses for Primary and Secondary servers management.
- An additional NIC which will be used for heartbeat communication and data transfer.
- I am using Windows Server 2012 with the latest updates for this test.
- Don’t create a new server and presume that you’ll be installing vCenter server on it and then it will be configured as a secondary node, this doesn’t work this way :).
- On the original vCenter server
- Add a second vNIC.
- Edit both network interfaces and disable DNS registration.
- Rename the interface with the original IP address (192.168.1.10) to Public and add a new IP address to it which will be the management IP i.e 192.168.1.11
- Rename the second interface to VMware Channel and assign it with only an IP address and subnet mask i.e 220.127.116.11, no gateway and no DNS is needed, again make sure DNS registration is disabled also disable NETBIOS on TCI/IP.
- Open services.msc and change the startup type of these services to manual (VMware VirtualCenter Server, VMware vSphere Profile-Drive Storage, vCenter Inventory Service and VMware VirtualCenter Management Webservices).
- Rename it to vCenterServer2 and don’t do a sysprep because both the primary and secondary machine SID’s must be identical.
- Configure the Primary network interface with the management IP address (192.168.1.12) and the service IP address (192.168.1.10).
- Configure the VMware channel network interface with only an IP address and netmark i.e 18.104.22.168.
- Again make sure that on both interfaces DNS registration is disabled and NETBIOS is disabled on the VMware Channel interface.
- Now edit the virtual machine settings and connect both network interfaces.
Installation – Primary Node:
- As of this post the latest build is vCSHB-v6-6-13406.exe.
- Start the executable, and you’ll find the nifty powered by Neverfail in the spalsh.
- Click next and chose “Install Primary VMware vCenter Server Heartbeat“.
- Accept the license agreement, next.
- Add your key, next.
- Here we’re going for LAN high availability, next.
- Secondary node is virtual, next.
- Select the destination installation path, next.
- For the VMware Channel configuration, chose the interface which we’ve named earlier VMware Channel, next.
- Add the primary vmware channel IP address which will be shown as the IP address of the VMware Channel interface and then you have to manually type in the IP address of the secondary server VMware Channel IP address i.e. 22.214.171.124 also if you have a specific requirement you can change the communication ports, next.
- Select the public channel interface, named Public earlier and click next.
- Add the public IP address of the service where here it will be i.e 192.168.1.10 which is the original IP address of the vCenter server and retain the user same IP address for secondary configuration, next.
- Add the IP addresses that will be used for management for both servers i.e 192.168.1.11 and 192.168.1.12, next.
- Now you’ll notice that the FQDN of the protected service will take the same FQDN of the original computer name, this is because the vCenter Server services are dependent on this FQDN name and it can’t be changed, as such you’ll have to rename the original vCenter server in such a way that you’ll end up with this:
- vCenterServer < Service name.
- vCenterHost1 < Primary node name.
- vCenter Host2 < Secondary node name.
- Now you select what are the features you want to be protected, usually defaults will be sufficient and if you can VMware Hoirzon View Composer installed you can protect that as well, in the same dialogue a username and password will be required and these are used to register the vCenter Heartbeat plugin to the vCenter server, next.
- Put the UNC path of the shared network folder that we’ve created earlier, next.
- Review the summary, next.
- Wait for Pre-Install checks to finish, next.
- Wait for the Install phase to finish, next.
- Wait for the Packet filter installation to finish, next.
- Here before you click finish you must head to you DNS server and you need to remove all automatic registration entries from your forward and reverse lookup zones and then what you will need to do it create 3 new static entries.
- vCenterServer pointing to 192.168.1.10
- vCenterBox1 pointing to 192.168.1.11
- vCenterBox2 pointing to 192.168.1.12
- Now you can click finish and your vCenter Server will reboot.
- Once the server is up, sign-in and in the system tray you’ll find the vCenter Server Hearbeat icon.
- Right click on it and click on Manage Server.
- If the group doesn’t show up automatically, click on add and type the name of the service i.e vCenterServer and put your credentials where you’ll notice that this node is the primary node and the secondary node is waiting.
Installation – Secondary Node:
- Copy vCSHB-v6-6-13406.exe to the secondary server and start it.
- Click next and select Install Secondary VMware vCenter Server.
- Now put the UNC path which we used before to copy some installation configuration on the primary node, next.
- Wait for Pre-Install to finish, next.
- Wait for the Install to finish, next.
- Here is where we select the VMware Channel adapter (should be selected by default), next.
- Here is where we select the Public adapter (also selected by default), next.
- Wait for the node configuration to finish, next and finish.
Give a couple of seconds and the primary server will detect the secondary server and it will start communicating where first network connectivity is checked and the system registry is replicated and finally data will be replicated.
Now you have a vCenter server with proper protection against failure =).