Monday, June 27, 2016

Repointing the VMware vCenter Server 6.0 between External Platform Services Controllers within a Site in a vSphere Domain (2113917)

Repointing a vCenter Server Appliance to another external Platform Service Controller in the same Site

  1. Log in to the vCenter Server Appliance Linux console as the root user.
  2. Run this command:

    shell.set --enabled true

  3. Run the shell command.
  4. Run this command to repoint the vCenter Server Appliance to Platform Services Controller (PSC) appliance:

    /usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-namesystemname_of_second_PSC

    Where, systemname_of_second_PSC is the system name used to identify the second Platform Services Controller.

    Notes
    :
    • The system name must be an FQDN or a static IP address and FQDN is case sensitive.
    • If the second Platform Services Controller runs on an HTTPS port that is different from the HTTPS port of the first Platform Services Controller, update the port number using this command:

      /usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-port --server-name localhost --dc-port https_port_of_second_PSC
  5. Run this command to stop the services in the vCenter Server Appliance:

    service-control --stop --all
  6. Run this command to start the services in the vCenter Server Appliance:

    service-control --start --all 
  7. Using the vSphere Web Client, log in to the vCenter Server instance in the vCenter Server Appliance to verify that the vCenter Server is up and running and manageable.

Repointing a Windows vCenter Server to another External Platform Service Controller

  1. Log in as an Administrator to the virtual machine or physical server on which you installed vCenter Server.
  2. Click Start > Run, type cmd and press Enter.
  3. Run this command to repoint the vCenter Server instance to the second Platform Services Controller:

    C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli set-dc-name --server-name localhost --dc-name system_name_of_second_PSC

    Where, system_name_of_second_PSC is the system name used to identify the second Platform Services Controller.

    Notes:
    • The system name must be an FQDN or a static IP address and FQDN is case sensitive.
    • If the second Platform Services Controller runs on an HTTPS port that is different from the HTTPS port of the first Platform Services Controller, update the port number using this command:

      C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli set-dc-port --server-name localhost --dc-port https_port_of_second_PSC
  4. Run this command to change to vCenter Server and/or Platform Services Controller installation directory:

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

    Note: This command uses the default installation path. If you have installed vCenter Server and/or Platform Services controller to another location, modify this command to reflect the correct install location.
  5. Run this command to stop the vCenter Server services:

    service-control --stop --all
  6. Run this command to start the vCenter Server services:

    service-control --start --all
  7. Using the vSphere Web Client, log in to the vCenter Server instance to verify that the vCenter Server is active.

No comments:

Post a Comment

Vmware NSX SSL creation 

Using OpenSSL for NSX Manager SSL import: Creates CSR and 4096 bit KEY Creating NSX 6.4.2 SSL    openssl req -out nsxcert.csr -newkey rsa:40...