VCF 5.0 On VxRail 8.0.100 – Walkthrough (Part 2: Isolated SSO WLD)

Note: this is an example for reference only please use the VxRail installation procedures & services provided by Dell.

PART 1

This is the 2nd in a series of posts covering VCF 5.0 On VxRail 8.0.100. The following post provides an example walkthrough covering the process of deploying a VI Workload Domain using the UI for Workflow Optimization method.

In this example we will showcase the new VCF 5.0 feature: Isolated WLD with individual SSO. In previous releases VCF imposed certain restrictions on the configuration of identity domains – the Management vCenter and the vCenters of each Workload Domain (WLD) had to be members of a single vSphere SSO domain. To improve the flexibility and overcome the limitations, customers can now choose how to configure the SSO for every WLD vCenter that they deploy. This allows VCF users to achieve the needed isolation between Workload Domains and increases the number of supported Workload Domains above 15. This increases the number of supported WLDs in a single VCF instance from 15 to 25. The possible SSO domain options when creating a new WLD in VCF 5.0 are:

Join the default SSO domain created by the Management vCenter
Create a new SSO domain

In this example I chose to create a new SSO domain ‘ring.local’ leveraging the new Isolated SSO WLD feature in VCF 5.0:

You can view a list of prerequisites and an overview of the procedure on the VMware site here.

Note: this is an example for reference only please use the VxRail Solve installation procedures provided by Dell.

SDDC Manager – Pre-Reqs

Ensure to complete the following from within SDDC Manager UI:

Licensing details entered correctly
Repository logins authenticated successfully
Download NSX-T Manager bundle

Deploy VI WLD Using WFO UI Method

The following input values are required as per the process of creating a VI WLD from the SDDC Manager UI:

VI WLD Name
SSO Domain Name
DC Name
vCenter Fully Qualified Domain Name (FQDN)
ESXi hosts, VxRail Manager, and NSX Manager instances (IP & FQDN resolvable)
vCenter IP address, netmask and gateway
Root Password
NSX Host Overlay Network (DHCP server if using)

Change the VxRail Manger IP address & confirm discovery of hosts:

Update VxRail Manager Certificate with the correct Hostname by logging into VxRail Manager via ssh with mystic followed by su. cd /mystic dir and run the following script:

./generate_ssl.sh hostname.domain.local