Specifications

Table Of Contents
12 Enter the information to register vCenter Server with vCenter Single Sign-On.
The vCenter Single Sign-On administrator user name is administrator@vsphere.local, and the password
must match the password you entered when you installed vCenter Single Sign-On. The Lookup Service
URL takes the form https://SSO_host_FQDN_or_IP:7444/lookupservice/sdk, where 7444 is the default
vCenter Single Sign-On HTTPS port number. Your entry should match the entry you made when you
installed vCenter Single Sign-On. If you entered a different port number when you installed vCenter
Single Sign-On, use that port number.
NOTE If you installed vCenter Single Sign-On in a vCenter Server Appliance, you can enter the vCenter
Single Sign-On administrator user as root@localos. In this case, the password is the root password of the
vCenter Server Appliance. The Lookup Service URL takes the form
https://vCenter_Appliance_IP_or_host_name:{7444}/lookupservice/sdk.
13 Enter the Inventory Service URL.
The Inventory Service URL takes the form https://Inventory_Service_host_FQDN_or_IP:10443. 10443 is
the default Inventory Service HTTPS port number. If you entered a different port number when you
installed Inventory Service, use that port number here.
14 Click Install.
Installation might take several minutes. Multiple progress bars appear during the installation of the
selected components.
What to do next
Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postupgrade
actions you might want to take.
Use Custom Install to Upgrade vCenter Server from a Version 5.1.x
High Availability vCenter Single Sign-On Deployment
In high availability mode, two vCenter Single Sign-On nodes work with the same database, data, and user
stores to ensure that vCenter Single Sign-On is not a single point of failure.
This procedure upgrades an existing vCenter Server that was installed with a high availability vCenter
Single Sign-On deployment.
You can upgrade vCenter Single Sign-On in a high availability installation without taking all vCenter Single
Sign-On nodes offline at the same time. While the first Single Sign-On node is being upgraded, the load
balancer will redirect all requests to the second node. After the first node is successfully upgraded, you can
upgrade the second node.
vCenter Server can continue running while you upgrade vCenter Single Sign-On. Logged in users can
continue accessing vCenter Server and related solutions that are connected to vCenter Single Sign-On
during the upgrade. However, vCenter Server, the vSphere Web Client, and vCenter Inventory Service
cannot be started while the first Single Sign-On node is offline.
NOTE vCenter Server 5.5 supports connection between vCenter Server and vCenter Server components by
IP address only if the IP address is IPv4-compliant. To connect to a vCenter Server system in an IPv6
environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server.
The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if
assigned by DHCP.
Prerequisites
n
Review the topics in Chapter 3, “Preparing for the Upgrade to vCenter Server,” on page 31.
n
See “Prerequisites for the vCenter Server Upgrade,” on page 48
vSphere Upgrade
84 VMware, Inc.