Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Migrating vCenter Server Heartbeat 6.3 Update 1 and later from identical nodes to non-identical (Updates MS DNS) nodes (2002117)

Purpose

This article provides steps to migrate vCenter Server Heartbeat 6.3 Update 1 and later from an identical nodes configuration to a non-identical (Updates MS DNS) nodes configuration.

Note: This procedure reconfigures vCenter Server Heartbeat 6.3 Update 1 and later installed in a LAN environment where vCenter Server and SQL Server are protected but not installed on the same machine (remote SQL Server).

Resolution

Before starting this process, shutdown vCenter Server Heartbeat on both servers leaving the protected applications running.

On the Secondary Server:
  1. Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual.
  2. Open the Configure Server wizard, click the Public tab, and select Non-identical (Updates MS DNS).
  3. Provide the Service Name for vCenter Server.

    Note: This is typically the current name of vCenter Server.

  4. In the NIC dropdown, select the Principal (Public) NIC.
  5. In the Public IP dropdown, select the Principal (Public) IP address assigned to the Principal (Public) NIC.
  6. In the first Mask field, enter the Subnet Mask of the Principal (Public) IP address.
  7. In the Passive IP field, enter a reserved Management IP address for the Secondary server.
  8. In the second Mask field, enter the Subnet Mask of the Management IP address.
  9. Click Finish.
  10. Right-click the Secondary server image and choose Edit Settings.
  11. Disable the network adapters for both the VMware Channel and Principal (Public) NICs.
  12. Navigate to the Network Connections, right-click the Principal (Public) network connection and choose Properties. Select Internet Protocol (TCP/IP) and click Properties.
  13. Change the IP address to match that of the Secondary Management IP address previously entered in the Configure Server wizard.
  14. Click Advanced, select the DNS tab, and deselect Register this connection’s addresses in DNS. Click OK three times to close the dialogs.
  15. Right-click the Channel network connection and choose Properties. Select Internet Protocol (TCP/IP) and click Properties.
  16. Click Advanced, select the DNS tab, and deselect Register this connection’s addresses in DNS. On the WINS tab, select Disable NetBIOS over TCP/IP. Click OK three times to close the dialogs.
  17. Navigate to the server’s System Properties, click the Computer Name tab, and click Change to rename the Secondary server and join a Workgroup. When requested, restart the server.
  18. Right-click the Secondary server image and choose Edit Settings.
  19. Re-enable the virtual network adapters for both the VMware Channel and Principal (Public) NICs.
  20. Navigate to the server’s System Properties, click the Computer Name tab, and click Change to join the domain. When requested, restart the server.
On the Primary Server
  1. Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual, Stopped, and close the dialog.
  2. Open the Configure Server wizard, click the Public tab, and select Non-identical (Updates MS DNS).
  3. Provide the Service Name for vCenter Server.

    Note: The Service Name is the same as current name of the Primary server.

  4. In the NIC dropdown, select the Principal (Public) NIC.
  5. In the Public IP dropdown, select the Principal (Public) IP address assigned to the Principal (Public) NIC.
  6. In the first Mask field, enter the Subnet Mask of the Principal (Public) IP address.
  7. In the Passive IP field, enter a reserved Management IP address for the Primary server.
  8. In the second Mask field, enter the Subnet Mask of the Management IP address.
  9. Click Finish.
  10. Navigate to Network Connections, right-click the Principal (Public) network connection and choose Properties. Select Internet Protocol (TCP/IP) and click Properties.
  11. Click Advanced, click the DNS tab, and deselect Register this connection’s addresses in DNS. Click OK three times to close the dialogs.
  12. Right-click the Channel network connection and choose Properties. Select Internet Protocol (TCP/IP) and click Properties.
  13. Click Advanced, click the DNS tab, and deselect Register this connection’s addresses in DNS.
  14. Navigate to the server’s System Properties, click the Computer Name tab, and click Change to rename the Primary server. When requested, restart the server.
  15. On both the Primary and Secondary servers, navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Automatic, and close the dialog.
After you complete the preceding steps, you must ensure that vCenter Server Heartbeat is configured correctly.
 
To check the vCenter Server Heartbeat configuration:
  1. Before starting vCenter Server Heartbeat, verify the time synchronization between the Primary and Secondary servers. When a difference exists, synchronize the Secondary (passive) server to the Primary (active) server across the VMware Channel. To synchronize the time, run this command:

    net time \\<Primary_Channel_IP_address> /set

  2. Start vCenter Server Heartbeat on both Primary and Secondary servers.
  3. Allow the Primary and Secondary servers to establish a handshake and commence replication.
  4. Launch the vCenter Server Heartbeat Console and navigate to the Applications: Tasks page.

    Note: If the user account under which you have installed vCenter Server Heartbeat is a member of the Domain
    Admins group, Enterprise Admins group, or has been delegated Administrator rights, proceed to Step 4d.

    1. Click User Accounts >Add
    2. Enter the credentials of a domain account that is a member of the Domain Admins group, Enterprise Admins group, or one that has been delegated Administrator rights and click OK
    3. When the account has been successfully added to the list, click Close
    4. Click Add to create a new task.
    5. In the Add Task dialog, enter this name for the Name of the task:

      DNSUpdate (Primary)

       
    6. Choose Network configuration for the Task Type. 
    7. For Runs on, select Primary.
    8. In the Command field, enter:

      dnsconftool.exe –auto 

    9. From the Run As: dropdown, select an account with appropriate rights (the account previously added).
    10. Click OK
    11. Repeat the procedure creating the Network Configuration task DNSUpdate (Secondary). 

  5. Manually run the Network task corresponding to the currently active server. Normally this is the Primary server (for example, DNSUpdate (Primary)) and verify that the task completes with exit code 0.
  6. Verify that Nslookup resolves as shown below:

    Nslookup resolves Service Name to Public IP
    Nslookup resolves Primary Name to Public IP
    Nslookup resolves Secondary Name to Secondary Passive IP

Additional Information

vCSHB-Ref-2209

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: