Search the VMware Knowledge Base (KB)
Products:
View by Article ID

Repointing vCenter Server 6.0 between sites in a vSphere Domain (2131191)

  • 24 Ratings
Language Editions

Purpose

Caution: This operation is no longer supported in vSphere 6.5 and running these steps can cause permanent damage.

This article provides steps to repoint vCenter Server 6.0 Update 1 and later between Platform Service Controllers (PSC) in different sites within your vSphere domain. 

For guidance on the different types of repointing within a vSphere domain, see the table below. Currently, repointing can only be done with Platform Service Controller nodes within the same vSphere domain.

Repoint Type Article
Repointing within a Site Repointing the VMware vCenter Server 6.0 between External Platform Services Controllers within a Site in a vSphere Domain (2113917)
Repointing between Sites * This Article
Repointing from Embedded PSC to External PSC ** The Reconfigure vCenter Server with Embedded Platform Services Controller to vCenter Server with External Platform Services Controller section in the vSphere 6.0 Upgrade guide.

* Introduced in vSphere 6.0 Update 1, you can now move vCenter Server between sites within the vSphere domain. You must upgrade the vCenter Server and Platform Services Controllers to Update 1 in order to use this process.
 
** Introduced in vSphere 6.0 Update 1, you can decommission the Embedded Platform Services Controller on the vCenter Server and repoint the vCenter Server to an External Platform Service Controller. You must upgrade the vCenter Server and Platform Services Controllers to Update 1 in order to use this process.

Cause

When vCenter Server is installed, it creates services registrations that it issues to start the vCenter Server services. These service registrations are written to a specific site of the Platform Services Controller (PSC) that was used during install time. When attempting to move the vCenter Server's affinity to a new Platform Services Controller in a new site, the vCenter Server will fail to start its services due to not having the proper service registrations in the new site.

Resolution

To move your vCenter Server between external Platform Services Controllers located in different sites:

Replace the cmsso-util

Download and extract the 2131191_cmsso-util.zip file attached to this article to replace the cmsso-util file on the vCenter Server(s) you intend to move. 

For the vCenter Server Appliance:
  1. Connect to vCenter Server Appliance using an SSH session.
  2. Provide the root user name and password when prompted.
  3. Run this command to enable the Bash shell:

    shell.set --enable True

  4. Run this command to access the Bash shell:

    shell

  5. Back up the current cmsso-util file on vCenter Server using this command:

    mv /bin/cmsso-util /bin/cmsso-util.bak

  6. Configure the vCenter Server to allow file transfer with WinSCP.

    For more information, see Error when uploading files to vCenter Server Appliance using WinSCP (2107727).

  7. Upload the previously extracted cmsso-util file into the /bin/ directory.
  8. Run this command to make the cmsso-util file executable:

    chmod +x /bin/cmsso-util

  9. Remain in the SSH session.
For vCenter Server for Windows:
  1. Connect to the host that is running vCenter Server using Remote Desktop.
  2. Open an administrative command prompt.
  3. Run these commands to backup the cmsso-util file:

    cd "C:\Program Files\VMware\vCenter Server\bin"

    ren cmsso-util cmsso-util.bak


  4. Upload the previously extracted cmsso-util file into the C:\Program Files\VMware\vCenter Server\bin directory.
  5. Remain in the Command Prompt.
Before moving vCenter Server between Sites

On vCenter Server you intend to move:
  1. Determine the current site using the VMAFD-CLI command:

    For the vCenter Server Appliance: /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name --server-name localhost

    For a Windows installed vCenter: C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli get-site-name --server-name localhost

  2. This will output the vCenter Server site in the session window.

    For example:

    /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name --server-name localhost
    East

  3. Determine your vSphere domain using the VMAFD-CLI command:

    For the vCenter Server Appliance: /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name localhost

    For a Windows installed vCenter: C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli get-domain-name --server-name localhost

  4. This will output the vCenter Server's current vSphere Domain in the session window.

    For example:

    /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name localhost
    vsphere.local

On the Platform Services Controller you intend to move vCenter Server to:
  1. Determine the current site using the VMAFD-CLI command:

    For the vCenter Server Appliance: /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name --server-name localhost

    For a Windows installed vCenter: C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli get-site-name --server-name localhost

  2. This will output the vCenter Server site in the session window.

    For example:

    /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name --server-name localhost
    West

Moving the vCenter Server between Sites

Note: Moving vCenter Server between sites requires a restart of the vCenter Server services.

For the vCenter Server Appliance:
  1. Connect to vCenter Server Appliance using an SSH session.
  2. Provide the root user user name and password when prompted.
  3. Run this command to enable the Bash shell:

    shell.set --enable True

  4. Run this command to access the Bash shell:

    shell

  5. Repoint vCenter Server to the Platform Services Controller in the separate site by running this command:

    /bin/cmsso-util repoint --repoint-psc FQDN_of_PSC_New_Site

    For example:

    /bin/cmsso-util repoint --repoint-psc PSC4.vmware.Local

    This restarts the services of the vCenter Server Appliance.

  6. Run the move-services option on cmsso-util on vCenter Server using this command:

    /bin/cmsso-util move-services

  7. You can either allow the cmsso-util binary to prompt you or you can manually specify the switches.

    Note: This moves the current service registrations from the vCenter Server's current site (East) to the new site (West). While the service registrations are being moved, the vCenter Server services is restarted.
    • If using the prompt, enter:
Domain:
Username:
Password:
PSC Node:
Old Site Name:
New Site Name:

For example: using the information from section Before Moving the vCenter Server between Sites:

Domain: vsphere.local
Username: Administrator
Password: VMw@re123
PSC Node: psc4.vmware.local
Old Site Name: East
New Site Name: West

    • If manually specifying the switches run this command:
cmsso-util move-services --psc-node <PSC_FQDN_from_Step_5> --domain-name <vSphere Domain Name> --username Administrator --passwd Administrator_Password --oldsite-name <vCenter Server's Original Site> --newsite-name <vCenter Server's New Site>

For example using the information from section Before Moving the vCenter Server between Sites:

cmsso-util move-services --psc-node psc4.vmware.local --domain-name vsphere.local --username Administrator --passwd VMw@re123 --oldsite-name East --newsite-name West


For the vCenter Server for Windows:
  1. Connect to the host that is running vCenter Server using Remote Desktop.
  2. Open an administrative command prompt.
  3. Execute the following:

    cd "C:\Program Files\VMware\vCenter Server\bin"

  4. Repoint the vCenter Server to the Platform Services Controller in the separate site by running this command:

    "%VMWARE_PYTHON_BIN%" cmsso-util repoint --repoint-psc FQDN_of_PSC_New_Site

    For example:

    "%VMWARE_PYTHON_BIN%" cmsso-util repoint --repoint-psc PSC4.vmware.Local

  5. Run the move-services option of cmsso-util on to move the vCenter Server's service registration using this command:

    "%VMWARE_PYTHON_BIN%" cmsso-util move-services

  6. You can either allow the cmsso-util binary to prompt you or you can manually specify the switches.

    Note: This moves the current service registrations from the vCenter Server's current site (East) to the new site (West). While the service registrations are being moved, the vCenter Server services is restarted.

    • If using the prompt, enter:

      Domain:
      Username:
      Password:
      PSC Node:
      Old Site Name:
      New Site Name:

      For example using the information from section Before Moving the vCenter Server between Sites

      Domain: vsphere.local
      Username: Administrator
      Password: VMw@re123
      PSC Node: psc4.vmware.local
      Old Site Name: East
      New Site Name: West


    • If manually specifying the switches, use the following syntax:

      cmsso-util move-services --psc-node <PSC_FQDN_from_Step_5> --domain-name <vSphere Domain Name> --username Administrator --passwd Administrator_Password --oldsite-name <vCenter Server's Original Site> --newsite-name <vCenter Server's New Site>

      For example using the information from section Before Moving the vCenter Server between Sites:

      cmsso-util move-services
      --psc-node psc4.vmware.local --domain-name vsphere.local --username Administrator --passwd VMw@re123 --oldsite-name East --newsite-name West

See Also

Attachments

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

  • 24 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)




Please enter the Captcha code before clicking Submit.
  • 24 Ratings
Actions
KB: