Specifications

Table 3‑1. Choosing a vCenter Single Sign-On Deployment Mode (Continued)
vCenter Server Deployment Single Sign-On Deployment Mode
Multiple vCenter Servers in Linked Mode Multisite vCenter Single Sign-On
vCenter Servers with high availability Basic vCenter Single Sign-On with VMware vSphere HA
(provides high availability for vCenter Server and vCenter
Single Sign-On )
Basic vCenter Single Sign-On with vCenter Server
Heartbeat (provides high availability for vCenter Server
and vCenter Single Sign-On )
See “vCenter Single Sign-On and High Availability,” on
page 35.
Basic
Basic vCenter Single Sign-On is the most common deployment mode, and
meets the requirements of most vSphere 5.1 and 5.5 users. Typically, this
deployment mode maintains the same architecture as previous vCenter
Server environments. In most cases, you can use vCenter Simple Install to
deploy vCenter Server with vCenter Single Sign-On in basic mode.
In Basic deployment mode, a single standalone instance of the vCenter Single
Sign-On server supports the connectivity of Active Directory, OpenLDAP,
Local Operating System, and vCenter Single Sign-On embedded users and
groups. In most cases, the vCenter Single Sign-On instance is installed on the
same host machine as vCenter Server, as with the vCenter Server Simple
Install option, or the vCenter Server Appliance.
The Basic vCenter Single Sign-On deployment is appropriate in the following
circumstances:
n
If you have a single vCenter Server of any supported inventory size: up
to 1,000 hosts or 10,000 virtual machines.
n
If you have multiple geographically dispersed locations, each with a
local vCenter Server and you do not require a single-pane-of-glass view
as provided by vCenter Linked Mode.
Multiple Single Sign-On
instances in the same
location
For this deployment mode, you install a vCenter Single Sign-On primary
instance and one or more additional vCenter Single Sign-On nodes. Both the
primary and high availability instances are placed behind a third-party
network load balancer (for example, Apache HTTPD or vCNS). Each vCenter
Single Sign-On has its own VMware Directory Service that replicates
information with other vCenter Single Sign-On servers. vCenter Single Sign-
On administrator users, when connected to vCenter Server through the
vSphere Web Client, will see the primary vCenter Single Sign-On instance.
This deployment mode has the following limitations:
n
It provides failover only for the vCenter Single Sign-On service. It does
not provide failover for the vCenter Single Sign-On host machine.
n
It supports the connectivity of Active Directory, OpenLDAP and
vCenter Single Sign-On embedded users and groups, but does not
support the use of local operating system user accounts.
vSphere Upgrade
34 VMware, Inc.