vSphere 6 Deployment Topologies

vCenter Server with Embedded PSC and Database

The embedded PSC is meant for standalone sites where vCenter Server will be the only SSO integrated solution. In this case replication to another PSC should not be required and is not possible.

  • Device is a single point of failure.
  • Supports Windows and VCSA (vCenter Server Appliance) based deployments
  • Replication between PSCs not required
  • Multiple standalone instances supported
  • Sufficient for small scale deployments
  • Not suitable for use with other VMware products (vRA, NSX etc.)
  • Easy to deploy and maintain

design1

vCenter Server with Embedded Database and External PSC

In this configuration the PSC is external from the vCenter Server. Multiple vCenter Servers can share the same external PSC.

  • PSC and vCenter servers are single points of failure
  • Reduces footprint by sharing Platform Service Controllers across several vCenter Servers.
  • PSC is a single point of failure throughout the infrastructure
  • Supports Windows and VCSA (vCenter Server Appliance) based deployments
  • Easy to deploy
  • Not suitable for use with other VMware products (vRA, NSX etc.)
  • Sufficient for small scale deployments

design2

vCenter Server with External Database, PSC and VUM with External Database

In this configuration each site is independent with PSC replication between sites. The vCenter Server is aware of the site topologies and use the local PSC under normal circumstances. Administrators are able to seamlessly move the vCenter Servers between PSCs when necessary.

design3

This topology allows for Enhanced Linked Mode (ELM) which is facilitated by the PSC. Enhanced Linked Mode provides for a single point of management for all vCenter Servers in the same vSphere domain. In vSphere 6 the Windows-based and Virtual Appliance-based vCenter Servers have the same operational maximums and can belong to the same linked mode configuration. The configuration replicates all license, global permissions, tags and roles across all sites.

  • PSC/vCenter/Database are a single points of failure throughout the infrastructure
  • Supports Windows based deployments only
  • Suitable for Medium and Large scale deployments
  • Suitable for use with other VMware Products (vRA/NSX/VSAN)

Each site would have the following deployment topology:

design4

Highly Available Architecture for Multi-Site vCenter and PSC

This topology combines the high availability configuration in a local site with a multi-site configuration. Each site is populated with at least two PSCs for high availability. vCenter Server nodes are individually clustered with MSCS for HA.

design5

This model protects the platform service controller service by having multiple instances of PSC locally behind a load balancer. Failure of a PSC does not impact the usage of the infrastructure. The PSCs should also be separated from each other physically using anti-affinity rules. The vCenter Server nodes are individually clustered with MSCS for HA. The vCenter Servers interact with the PSCs through a load balancer.

  • Supports Windows based deployments only
  • Suitable for Medium and Large scale deployments
  • Suitable for use with other VMware Products (vRA/NSX/VSAN)

Each site would have the following deployment topology:

design6

Leave a Reply

Your email address will not be published. Required fields are marked *