Re-pointing and re-registering VMware vCenter Server Appliance 5.5.x and components
search cancel

Re-pointing and re-registering VMware vCenter Server Appliance 5.5.x and components

book

Article ID: 332316

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

After certain changes to your VMware vSphere deployment topography, you may need to re-point or re-register vCenter Server Appliance components with the vCenter Inventory Service or vCenter Single Sign-On and the vCenter Lookup Service to ensure that the components can continue to communicate.
 
Note: This article is designed to assist technical support engineers and customers with repointing services internal to the vCenter Server Appliance. To re-point to an external vCenter Single Sign-On server on your vCenter Server Appliance, see the Change the vCenter Single Sign-On Mode in the VMware vCenter Server Appliance section of the ESXi and vSphere 5.5 Documentation Guide.


Resolution

Re-registering the vCenter Inventory Service

To re-register the vCenter Inventory Service:
  1. Un-register the vCenter Inventory Service.
  2. Re-register the vCenter Inventory Service to embedded SSO.
Un-registering the vCenter Inventory Service

To un-register the vCenter Inventory Service:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./02-inventoryservice --mode uninstall --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. If successful, this must generate an output similar to:
======
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA> :7444/lookupservice/sdk
Service with id "local:3576d0a7-e3db-4857-b0c1-9e289f95aa9c" is successfully unregistered
Return code is: Success
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA> :7444/lookupservice/sdk
Successfully deleted authenticated user
Return code is: Success
======
 
Re-registering the vCenter Inventory Service to embedded SSO

To re-register the vCenter Inventory Service to embedded SSO:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./02-inventoryservice --mode install --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. If successful, this must generate an output similar to and the Inventory Service must now be functional in the vSphere Web Client:
======
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Anonymous execution
Successfully saved SSO locations and certificates
Return code is: Success
Creating SSO principal for vCenter Server
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Solution user with id: {Name: inventory-service-3b48d115-4cbc-4504-9c45-2ebf2c6b08c4, Domain: vsphere.local} successfully registered
Successfully assigned role "RegularUser" to user "{Name: inventory-service-3b48d115-4cbc-4504-9c45-2ebf2c6b08c4, Domain: vsphere.local}"
Return code is: Success
Registering vCenter Server into the service catalog
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Service with name 'inventory-service-3b48d115-4cbc-4504-9c45-2ebf2c6b08c4' was registered with ID: 'local:c89635d7-3285-48b1-9e5e-1d80f5d2f81a'
Appending serviceId to file
Return code is: Success
Updating vCenter Server configuration
======
 

Re-registering vCenter Server

To re-register vCenter Server:
  1. Un-register vCenter Server.
  2. Re-register vCenter Server to embedded SSO.
Un-registering vCenter Server

To un-register vCenter Server:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./01-vcenter --mode uninstall --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. If successful, this must generate an output similar to, and the vCenter Server will no longer be present in the vSphere Web Client:
======
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA> :7444/lookupservice/sdk
Service with id "local:3576d0a7-e3db-4857-b0c1-9e289f95aa9c" is successfully unregistered
Return code is: Success
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA> :7444/lookupservice/sdk
Successfully deleted authenticated user
Return code is: Success
======
 
Re-registering vCenter Server to embedded SSO
 
To re-register vCenter Server to embedded SSO:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./01-vcenter --mode install --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password> --option vc-admin-principal=root --option sso-deployment-type=embedded
     
  4. This must generate this output, and the vCenter Server must now be present in the vSphere Web Client:
======
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Anonymous execution
Successfully saved SSO locations and certificates
Return code is: Success
Creating SSO principal for vCenter Server
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Solution user with id: {Name: vpxd-<FQDN of VCVA>-18992a4f-2a46-4a89-a72b-967e157ae2be, Domain: vsphere.local} successfully registered
Successfully assigned role "RegularUser" to user "{Name: vpxd-<FQDN of VCVA>-18992a4f-2a46-4a89-a72b-967e157ae2be, Domain: vsphere.local}"
Return code is: Success
Registering vCenter Server into the service catalog
Intializing registration provider...
Getting SSL certificates for <FQDN of VCVA>:7444/lookupservice/sdk
Service with name 'vpxd-<FQDN of VCVA>-18992a4f-2a46-4a89-a72b-967e157ae2be' was registered with ID: 'local:c89635d7-3285-48b1-9e5e-1d80f5d2f81a'
Appending serviceId to file
Return code is: Success
Updating vCenter Server configuration
======

 

Re-registering the vSphere Web Client

To register the vSphere Web Client:
  1. Un-register the vSphere Web Client.
  2. Re-register the vSphere Web Client to SSO.
Un-registering the vSphere Web Client
 
To un-register the vSphere Web Client:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this commands from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./10-vmware-vsphere-client --mode uninstall --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. If successful, this must provide this output:
======
Intializing registration provider...
Getting SSL certificates for https://<FQDN of VCVA>:7444/lookupservice/sdk
Service with id "Default-First-Site:039daf02-5a24-42d8-b5ec-198976e9924c" is successfully unregistered
Return code is: Success
Intializing registration provider...
Getting SSL certificates for https://<FQDN of VCVA>:7444/lookupservice/sdk
Successfully deleted authenticated user
Return code is: Success
======
 
Re-registering the vSphere Web Client to SSO
 
To re-register the vSphere Web Client to SSO:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the Appliance as well as the [email protected] password:

    ./10-vmware-vsphere-client --mode install --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. This generates an output similar to, and the vSphere Web Client will now be registered:
======
Creating SSO principal for vSphere Web Client
Registration of solution user information is:
[solutionUser]
name=vsphere-client- <FQDN of VCVA>-37d2be78-a120-4148-af11-4059f8fe8da8
cert=/usr/lib/vmware-vsphere-client/server/SerenityDB/keys/vsphere-client.crt
description=vSphere Web Client at <FQDN of VCVA>
Intializing registration provider...
Getting SSL certificates for https:// <FQDN of VCVA>:7444/lookupservice/sdk
Solution user with id: {Name: vsphere-client- <FQDN of VCVA>-37d2be78-a120-4148-af11-4059f8fe8da8, Domain: vsphere.local} successfully registered
Successfully assigned role "RegularUser" to user "{Name: vsphere-client- <FQDN of VCVA>-37d2be78-a120-4148-af11-4059f8fe8da8, Domain: vsphere.local} "
Return code is: Success
Registration of service information is:
[service]
friendlyName=vsphere-client
version=5.5.0
ownerId=vsphere-client- <FQDN of VCVA>[email protected]
type=urn:com.vmware.vsphere.client
description=vSphere Web Client
 
[endpoint0]
uri=https:// <FQDN of VCVA>:9443/vsphere-client
ssl=/etc/vmware-vpx/ssl/rui.crt
protocol=vmomi
Intializing registration provider...
Getting SSL certificates for https:// <FQDN of VCVA>:7444/lookupservice/sdk
Service with name 'vsphere-client' was registered with ID: 'Default-First-Site:763af5c4-780f-4a0a-99b0-599ece73f7ad'
Appending serviceId to file
Return code is: Success
Stopping VMware vSphere Web Client...
Stopped VMware vSphere Web Client.
Starting VMware vSphere Web Client...
Intializing registration provider...
Getting SSL certificates for https:// <FQDN of VCVA>:7444/lookupservice/sdk
Service with name 'vsphere-client- <FQDN of VCVA>-561b91ce-72be-4170-b17b-cbc301099c3c' and ID 'local:ada97ab6-611b-43a4-921e-a34780c9f85b' was updated.
Return code is: Success
Waiting for VMware vSphere Web Client......
running: PID:12751
======
 

Re-registering the VMware Log Browser

Note: Log Browser is not available from 5.5 Update 3e and above in vCenter Server 5.5 version.
 
To register the VMware Log Browser:
  1. Un-register the VMware Log Browser.
  2. Re-register the VMware Log Browser to SSO.
Un-registering the VMware Log Browser

To un-register the VMware Log Browser:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./09-vmware-logbrowser --mode uninstall --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. If successful, this must provide this output:
======
Intializing registration provider...
Getting SSL certificates for https://<FQDN of VCVA>:7444/lookupservice/sdk
Service with id "local:715c8945-5ec0-4615-86d9-e9c1273d8164" is successfully unregistered
Return code is: Success
Intializing registration provider...
Getting SSL certificates for https://<FQDN of VCVA>:7444/lookupservice/sdk
Successfully deleted authenticated user
Return code is: Success
Stopping VMware Log Browser: success
======
 
Re-registering the VMware Log Browser to SSO

To re-register the VMware Log Browser to SSO:
  1. Log in to the vCenter Server Appliance via SSH using the Root account.
  2. Change into the register-hooks directory on the appliance using this command:

    cd /etc/vmware-sso/register-hooks.d
     
  3. Run this command from this directory, filling in the appropriate FQDN of the appliance as well as the [email protected] password:

    ./09-vmware-logbrowser --mode install --ls-server https://<FQDN of VCVA>:7444/lookupservice/sdk --user [email protected] --password <Password>
     
  4. This generates an output similar to, and the Log Browser will now be accessible in the vSphere Web Client:
======
insserv: Service network is missed in the runlevels 4 to use service postgresql
insserv: Service syslog is missed in the runlevels 4 to use service postgresql
VMware Log Browser is not running
Starting VMware Log Browser: success
Intializing registration provider...
Getting SSL certificates for https:// <FQDN of VCVA>:7444/lookupservice/sdk
Solution user with id: {Name: logbrowser- <FQDN of VCVA>-5cc46597-619a-470f-b230-53643c1b7fc4, Domain: vsphere.local} successfully registered
Successfully assigned role "Administrator" to user "{Name: logbrowser- <FQDN of VCVA>-5cc46597-619a-470f-b230-53643c1b7fc4, Domain: vsphere.local}"
Return code is: Success
Intializing registration provider...
Getting SSL certificates for https:// <FQDN of VCVA>:7444/lookupservice/sdk
Service with name 'VMware Log Browser' was registered with ID: 'local:65c28b91-1618-4cc7-8268-c977a84932cf'
Appending serviceId to file
Return code is: Success
======


Additional Information


重新指向和重新注册 VMware vCenter Server Appliance 5.5.x 及组件

Powered by Wolken Software