Common services design

Microsoft Active Directory

By default, a single Active Directory VSI is deployed onto the IBM Cloud® infrastructure.

The design also provides the option to deploy two highly available MSAD servers as dedicated Microsoft Windows® Server VMs in the management cluster.

If you choose the option with two highly available MSAD servers, you're responsible to provide Microsoft licensing and activation.

Active Directory serves to authenticate accesses to manage the VMware® instance only and not to house users of the workloads in the deployed instances. The forest root domain name of the Active Directory server equals to the Domain Name Services (DNS) domain name that you specify. This domain name is specified only for the primary VMware Cloud Foundation for Classic - Automated instance if multiple instances are linked. For linked instances, each instance contains an Active Directory server that sits in the forest root replica ring. The DNS zone files are also replicated on the Active Directory servers.

vSphere Single Sign On (SSO) domain

The vSphere Single Sign On (SSO) domain is used as the initial authentication mechanism for a single instance or multiple linked instances. The SSO domain also serves to connect a VMware instance or multiple linked instances to the MSAD server. The following SSO configuration is applied:

• The SSO domain of vsphere.local is always used.
• For VMware instances that are tied to an existing instance, the vCenter Server appliance is joined to the existing instance’s SSO domain.
• The SSO site name is the root domain that was chosen when you deployed your instance.

Integration with existing forest

Merging of Active Directory forests is a complex process. If you want to integrate your instance with an existing Active Directory forest, IBM Cloud recommends that you add your existing Active Directory infrastructure as an extra identity source to VMware vCenter Server® rather than attempting to merge forests. IBM Cloud automation requires that you choose a root domain for your instance with at least three qualifiers to reduce the likelihood of conflict with your existing domain.

You have several options for reference to your existing domain as an identity source:

• If you have connectivity to your domain controllers in or from IBM Cloud, you can reference them directly.
• You can deploy read-only replica controllers in IBM Cloud.
• You can add one-way trust from the domain controllers that are deployed by IBM Cloud to your domain controllers.

Primary VMware Cloud Foundation for Classic - Automated instance

The VMware Cloud Foundation for Classic - Automated deployment uses the deployed AD VSIs or VMs as DNS servers for the instance. All deployed components (vCenter, NSX, ESXi hosts) are configured to point to the AD as their default DNS. You can customize the DNS zone configuration if it does not interfere with the configuration of the deployed components.

This design integrates DNS services on the AD VMs in the following configuration:

• The domain structure is specified by the user.
• The domain name can be any number of levels up to the maximum that all VMware Cloud Foundation for Classic - Automated components handle.
• The domain name must be at least three levels. This guideline enforces the best practice that the top-level domain delegates responsibility to the instance for the instance domain.
• The AD/DNS servers are configured to be authoritative for the DNS domain.
• The AD/DNS servers are configured to point to the IBM Cloud DNS servers for all other zones.
• Any secondary cloud regions that are integrated to the first cloud region or target-deployed cloud region must use the same DNS name structure with unique host prefixes.
• Optionally, you can deploy redundant DNS servers within the vSphere cluster. Two AD/DNS servers are configured unlicensed. It is your responsibility to provide licenses for the Windows operating systems for these servers.
• If a single site is provisioned with only one AD/DNS server, then all configured VMware Cloud Foundation for Classic - Automated components must have only that single IP address as a DNS entry.

Secondary VMware Cloud Foundation for Classic - Automated instances

For cross-instance redundancy, when the first secondary VMware Cloud Foundation for Classic - Automated instance is added to an existing primary or stand-alone VMware Cloud Foundation for Classic - Automated instance, that primary instance AD DNS server IP address is used in the secondary VMware Cloud Foundation for Classic - Automated instance and in any subsequent secondary instance “secondary DNS” entry for all components that require a DNS server entry.

For example, ESXi, vCenter, and NSX Manager, and also add-on components, such as, HCX, Zerto, and Veeam. The primary site secondary DNS entry is then changed to the AD/DNS IP address of the first secondary VMware Cloud Foundation for Classic - Automated instance.