Step by step guide on how to create a SDDC WLD – Work Load Domain using VCF 2.2 on VxRack SDDC. Here it is assumed that you have either a) spare nodes in your VxRack SDDC or b) have recently deleted a WLD and want to reuse these servers in a new WLD.
Step one login to your VxRack Manager VM. VxRack is part of the same SSO domain as your vCenter server so you can use the same account to login providing it has the correct rights attributed.
Here you can see I have only 1 WLD created and that is my MGMT domain. To add a new VI WLD – First, click on ADD Work Domain and then Configure VI (Virtual Infrastructure).
Complete this section with the relevant details, Infrastructure Name, Org Name.
On the workload section of the wizard, we configure both VSAN performance and availability settings.
The selected performance level determines the capacity related setting in the Workload domain vSan storage policy.
- Low option provides 1 disk stripe per object and 40% object reservation.
- Balance option provides 1 disk stripe per object and 70& object space reservation
- High option provides 4 disk stripes per object and 100% object space reservation
The selected availability level determines the number of drive failures the workload domains environment can tolerate. The system assigns physical storage to the workload domain according to the selected availability level, to accommodate the desired redundancy level. The levels are associated with the Virtual SAN Storage policy that the system applies to the workload domain.
None = FTT 0
Normal = FTT 1
High = FTT 2
The Virtual Infrastructure Resources setting (which has been changed to Number of Nodes in VCF 2.3) is a strange way to allocate rack resources as it merely rounds up to the closest number of total servers. I.E you cannot provision a fraction of a server. Never the less I have submitted my requirements. I have opted for the Default network options. These values are set during the creation of the MGMT WLD and system bring up.
Here we define a VM VLAN that will sit on the VDS that is created during WLD creation.
Hit Next review your configuration and click next.
Now the Automation Takes over and completes these 46 tasks to create your new WLD.
- VRM: Import Parameters
- ESX: Inital Backup of the ESXI Servers
- Network: Configure Vlans on Switches
- VRM: Configure DNS Host Name
- vCenter: Deploy vCenter
- PSC: Give vSphere Permissions to the Default Site
- vCenter: Apply vCenter License
- vCenter: Install RPM Agent
- vCenter: Create Cluster
- VRM: Update vCenter Status
- vCenter: Create Distributed Virtual Switch
- vCenter: Tag Vlan ID
- vCenter: Check Host Network Configuration
- vCenter: Configure Host
- Log Hosts vSan Network Config 1
- vCenter: Configure LACP on VDS
- Log Host vSan Network configure MLAG on Tor Switches
- vCenter: Wait until All ESXi Hosts Available
- Log Hosts vSan Netowrk Config 4
- Virtual San: Claim Host Disk
- Log Host vSan network config 5
- vCenter: Wait Virtual San to come up completely
- vCenter: Wait vCenter Ready after Virtual SAN
- Virtual SAN: Update Default Policy
- vCenter: Wait vCenter Ready after Virtual SAN Policy
- Vitual San: Post Check after Virtual Enabled
- NSX: Deploy NSX Manager
- NSX: Register vCenter
- NSX: Apply License
- NSX: Create Controller IP Pool
- MSX: Create Controller
- VRM: Save Controller Information to Database
- NSX: Create VXLAN IP Pool
- NSX: Configure VXLAN
- NSX: Create Segment Range
- NSX: Create Transport Zone
- NSX: Create Virtual Wire
- NSX: Configure Anti-Affinity Rule for NSX Controller
- NSX: Configure Backup and Restore settings for NSX Manager
- vCenter: Wait vCenter Ready after Vibs Installed
- vCenter: Wait Hosts Ready before Enabling Cluster
- vCenter: Enable Cluster Features
- vCenter: Wait Hosts Ready after Enabling Cluster
- vCenter: Clear Red Alarms on Hosts
- VRM: SOS Logs backup Task
- ESX: Final Backup of the ESXi Servers
Once Automation is is complete we can log into our vCenter and see or brand shiny new cluster.
You will spot that the NSX controllers reside on the new WLD and the rest of the MGMT components sit on the MGMT cluster.
When I sized this cluster I specifically wanted it to to be only 3 nodes. As I wanted to demo expanding a rack.
Notice I have a few vSan Errors – these are related to the vSan HCL DB – I will run a LCM UPgrade in a later vCenter post that will clear up this error as well as upgrading or vCenter Version.