Academy/Holodeck Lab Setup & Operations/Deploy a VI Workload Domain on Holodeck
This lab targets VCF 9.0.2

Deploy a VI Workload Domain on Holodeck

VCF 9.0.2Advancedadminarchitectvcdx⏱ 180 min

Applies to VCF 9.0.0 through 9.0.2 on Holodeck 9.0.2. Two documented routes: a full-stack New-HoloDeckInstance (without -ManagementOnly) deploys the workload domain with three nested hosts automatically; or, on a management-only instance, add nested hosts with New-HoloDeckESXiNodes and create the workload domain in VCF Operations. Source-checked 1 Oct 2026 against the Holodeck 9.0.2 documentation at vmware.github.io/Holodeck/9.0.2/ (index: Holodeck Environment Overview, Holorouter Overview, Concepts, Pre-requisites, Deployment, Post Deployment, Day 2 Operations, How To; cmd_reference; FAQ) and, where VCF behaviour is described, the VCF 9.0.1 documentation. In Holodeck 9.x the toolkit is a PowerShell module built into the HoloRouter OVA (Photon OS): the operator SSHes to the HoloRouter, runs pwsh, and works under /holodeck-runtime. There is no Windows HoloConsole, no C:\Holodeck path, no -ConfigFile parameter and no separate Prepare phase. Rewritten for v8.2.2 after the 360-degree audit.

Objectives

  • Explain what a VCF 9.0 workload domain is: its own vCenter deployed into the management domain, an NSX Manager cluster that is new or shared with another workload domain (never the management domain's), one or more vSphere clusters of commissioned hosts, and principal storage
  • Provision three nested ESX hosts for the workload domain with New-HoloDeckESXiNodes and commission them into the VCF inventory with a network pool and the matching principal storage type
  • Create the workload domain from VCF Operations (Inventory > VCF Instance > Add Workload Domain > Create New) with a vSphere Lifecycle Manager cluster image, vSAN storage, and a new or shared NSX Manager
  • Validate the workload domain in its own vCenter (vc-wld01-a) and NSX Manager (nsx-wld01-a) and in the VCF Operations inventory
  • Deploy a test workload on an NSX segment in the workload domain and verify connectivity through the HoloRouter
  • Perform lifecycle operations with the documented limits: add hosts and clusters (Update-HoloDeckInstance -AdditionalCluster), respect the three-host minimum of a standard vSAN cluster, and remove the workload domain

Prerequisites

holodeck-02 complete: management-only VCF 9.0.2 instance healthy (SDDC Manager, vc-mgmt-a, nsx-mgmt-a, ops-a). Physical host capacity for three more nested hosts plus a workload vCenter and NSX Manager (see the full-stack row of the requirement tables).

Prior labs: holodeck-02

Required skills:

  • VCF 9.0 constructs (instance, management domain, workload domain)
  • VCF Operations and vSphere Client navigation
  • vSAN and vSphere Lifecycle Manager basics
  • NSX segments and gateways
📸 Starting State: S3-9x — Management Domain Deployed (VCF 9.x)

Lab Environment

Management domain (esx-01a..04a) as deployed in holodeck-02. The workload domain adds three nested hosts (esx-05a, esx-06a, esx-07a in the Holodeck naming), a workload vCenter vc-wld01-a deployed into the management domain, and a workload NSX Manager nsx-wld01-a (or a shared one with another workload domain). All on the Site A VLANs of 10.1.0.0/20 behind the HoloRouter.

Important

The workload domain's vCenter and NSX Manager are new appliances deployed into the management domain; the management vCenter and management NSX Manager are never shared with workload domains (VCF 9.0.1 documentation, Table 2 Types of VCF Domains).

Mermaid source
graph TB
  subgraph MGMT[Management domain]
    SM[SDDC Manager] --- VCM[vc-mgmt-a] --- NSXM[nsx-mgmt-a]
    VCW[vc-wld01-a: workload vCenter appliance runs here]
    NSXW[nsx-wld01-a: workload NSX Manager runs here]
    OPS[VCF Operations ops-a]
  end
  subgraph WLD[Workload domain wld01]
    E5[esx-05a] --- E6[esx-06a] --- E7[esx-07a]
  end
  VCW -->|manages| WLD
  NSXW -->|transport nodes| WLD
  OPS -->|Add Workload Domain| SM

IP Addressing

NetworkPurposeVLAN
10.1.0.0/20Default Holodeck Site A master CIDR, subdivided by New-HoloDeckNetworkConfig into the Site A subnets (management, vMotion, vSAN, host overlay, edge uplinks, and others)VLANs 0 and 10-25 (Site A default)
10.2.0.0/20Default Holodeck Site B master CIDR (dual-site only)VLANs 40-58 (Site B default)
<external management network>HoloRouter external management IP (DHCP or static, set at OVA deployment); the only external IP a Holodeck environment needsExternal port group

Credentials

SystemUsernamePassword
HoloRouter (SSH and pwsh)rootSet in the OVA Additional settings at deployment
HoloRouter webtop(no authentication in 9.0.2)http://<holorouter-ip>:30000; the docs warn not to expose it externally
VCF Installeradmin@localHolodeck documented default (Post Deployment table)
VCF OperationsadminHolodeck documented default (Post Deployment table)
Management vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
SDDC Manageradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Management NSXadminHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)
Workload vCenteradministrator@vsphere.local (or administrator@<sso-domain> with an isolated SSO domain)Set in the Add Workload Domain wizard, or auto-generated and retrieved via the SDDC Manager API
Workload NSXadminSet in the Add Workload Domain wizard

Tasks

Task 1 Provision and commission the workload hosts

Manageability

A workload domain needs commissioned hosts in the inventory before the wizard can use them. Holodeck provides the nested hosts; VCF commissions them with a network pool and a principal storage type that the cluster will have to match.

Step 1

Check capacity against the full-stack row of the requirement tables (VCF 9.0 with Automation: 24-32 CPU, 325 GB RAM, 1.1 TB single site). The workload domain adds three nested hosts plus the vc-wld01-a and nsx-wld01-a appliances in the management domain.

Capacity confirmed or the plan reduced (for example no edge cluster).
Step 2

On the HoloRouter in pwsh (config imported) create three nested hosts: New-HoloDeckESXiNodes -Nodes 3 -CPU <vCPU> -MemoryInGb <GB> -Site a -vSANMode OSA (match the vSAN mode of the management domain unless you deliberately want an ESA cluster). Holodeck builds them from the staged ESX ISO on the Site A networks with DNS records (esx-05a.., check with Get-HoloDeckAppNetwork -Site a).

New-HoloDeckESXiNodes -Nodes 3 -CPU 8 -MemoryInGb 64 -Site a -vSANMode OSA
Three new nested hosts reachable; forward and reverse DNS present.
Step 3

Review the documented commissioning criteria that matter in the nested lab: supported ESX version, management IP on a VMkernel adapter on a standard switch, forward and reverse DNS, host name equal to the FQDN, self-signed certificate regenerated on the FQDN, hardware health OK, no pre-existing partitions on the vSAN disks, a network pool that supports the storage type, and the gateway inside the management subnet. Holodeck prepares the hosts this way; verify one host's DNS and certificate.

One host checked against the criteria; the others assumed identical (same build).
Step 4

Create or confirm a network pool for the workload domain (vMotion and vSAN ranges from Get-HoloDeckSubnet -Site a) and then commission the hosts: in the vSphere Client of the management vCenter, Global Inventory Lists > Hosts > Unassigned Hosts > Commission Hosts; review the checklist (Select All, Proceed); add the three FQDNs with storage type vSAN, vSAN type vSAN HCI, ESA unticked for OSA; select the network pool; validate and commission. (The SDDC Manager UI is the documented alternative.)

Three hosts validated and commissioned into the free pool, listed under Unassigned Hosts.
The platform temporarily enables SSH on each host to retrieve its host key, then disables it (documented). Hosts commissioned for vSAN HCI without ESA can only be used for vSAN OSA clusters.
Step 5

Record the commissioning outcome: host FQDNs, storage type, network pool, and the fact that a standard vSAN cluster needs a minimum of three hosts (VCF 9.0.1 documentation, vSAN cluster requirements), so three is the smallest workload cluster you can build.

Commissioning record with the three-host minimum noted.

Validation Gate

Check: Three nested hosts created with New-HoloDeckESXiNodes, DNS present, commissioned with vSAN HCI (OSA) and a network pool; three-host minimum recorded.

Expected: Hosts available in the Unassigned Hosts inventory for the workload domain.

Common Errors

Commissioning fails on DNS
Cause: Missing forward or reverse record, or FQDN case mismatch.
Fix: Check Get-HoloDeckDNSConfig; the host FQDN must match the hostname exactly.
Hosts not selectable for the planned cluster
Cause: Storage type mismatch (ESA vs OSA) between commissioning and the cluster.
Fix: Commission with the storage type the cluster will use; re-commission if needed.
Only two hosts available
Cause: Capacity or a failed build.
Fix: A standard vSAN cluster needs three hosts; add a host before creating the domain.

Task 2 Create the workload domain in VCF Operations

Manageability

In VCF 9.0 the Add Workload Domain wizard lives in VCF Operations (Inventory > Detailed View > VCF Instance > Add Workload Domain > Create New). It deploys a new vCenter into the management domain and a new or shared NSX Manager, then builds the cluster from a vSphere Lifecycle Manager image.

Step 1

Confirm the general requirements: a vSphere Lifecycle Manager cluster image is available for the default cluster (Managing vSphere Lifecycle Manager Images), the hosts are commissioned with the target principal storage type, a network pool with free IPs exists, a static IP pool or DHCP exists for the host overlay (TEP) VLAN, and the vCenter and NSX Manager FQDNs resolve (add them with Set-HoloDeckDNSConfig if the Holodeck records do not already cover vc-wld01-a and nsx-wld01-a).

Requirements checked; FQDNs resolve.
Step 2

In VCF Operations select Inventory > Detailed View, expand VCF Instances, browse to your instance and click Add Workload Domain > Create New. Review the prerequisites, Select All, Proceed.

Wizard started.
Step 3

General Information: Workload Domain Name wld01 (3-20 characters; include location in production); Enable vSphere Supervisor: deactivate for this lab (if left on, the wizard creates a Supervisor with NSX VPC networking, one control plane VM and one vSphere zone, and you must add an NSX Edge cluster afterwards); SSO Domain Name: leave empty to join the instance's SSO, or enter one (for example wld.sso) to create an isolated domain; Password Creation: set the SSO administrator password (8-20 characters, mixed classes, no dictionary words) or choose auto-generation (retrievable via the SDDC Manager API).

General information accepted.
Step 4

vCenter: enter the FQDN vc-wld01-a.site-a.vcf.lab (note the wizard's statement that the workload domain vCenter is deployed in the management domain) and the vCenter root password (15-20 characters, mixed classes). Cluster: name wld01-cl01. Select the cluster image (hosts are remediated to it if their add-ons differ).

vCenter, cluster and image pages accepted.
Step 5

NSX Manager: choose Create new (Deployment Size: Standard single node to save lab resources, or High-Availability three nodes as recommended; Appliance Size Medium) with FQDN nsx-wld01-a.site-a.vcf.lab (and two more FQDNs for HA), or Join existing to share an NSX Manager with another workload domain if one exists. The management domain's NSX Manager cannot be selected. Configure Network Connectivity: Centralized (configure edge clusters afterwards) or Distributed (VLAN, gateway CIDR, external and transit IP blocks for VPCs).

NSX page accepted with a new or shared workload NSX Manager.
Step 6

Storage: vSAN (leave Enable vSAN ESA unticked for OSA hosts). vSAN Storage details: Failures to Tolerate 1 (minimum hosts follow), space efficiency optional. Host selection: pick the three commissioned hosts. Review and Finish.

Workload domain creation task started.
Step 7

Monitor the task in VCF Operations (Fleet Management > Tasks) and in SDDC Manager (Inventory > Workload Domains > wld01 shows Activating). Expect vCenter deployment, NSX Manager deployment (if new), host preparation and cluster creation.

wld01 reaches Active.
Step 8

Record the design facts as you observed them: the workload vCenter and NSX Manager appliances appear as VMs in the management vCenter inventory; the workload cluster is managed by vc-wld01-a; SDDC Manager and VCF Operations manage both domains.

Observation note aligned with Table 2 Types of VCF Domains.

Validation Gate

Check: Wizard completed with vSphere Supervisor off, new vCenter, new or shared NSX Manager, vSAN OSA cluster of three hosts; wld01 Active.

Expected: A VI workload domain with its own vCenter and NSX Manager.

Common Errors

Wizard offers no cluster image
Cause: No vSphere Lifecycle Manager image imported.
Fix: Import an image for the ESX build in use (Managing vSphere Lifecycle Manager Images) and retry.
The management NSX Manager cannot be joined
Cause: By design: workload domains cannot use the management domain's NSX Manager cluster.
Fix: Create a new NSX Manager or share one with another workload domain.
Supervisor activation hangs after domain creation
Cause: Enable vSphere Supervisor left on with Centralized connectivity and no edge cluster.
Fix: Deploy an NSX Edge cluster with an active-standby Tier-0, or recreate the domain with Supervisor off.
Password rejected
Cause: Policy: 8-20 (SSO) or 15-20 (vCenter root) characters with mixed classes and no dictionary words.
Fix: Choose compliant passwords or auto-generate.

Task 3 Validate the workload domain

Availability

Validate in the places where a design review would look: the workload vCenter, the workload NSX Manager, SDDC Manager and VCF Operations, and the HoloRouter's view of the new appliances.

Step 1

Open https://vc-wld01-a.site-a.vcf.lab (administrator@vsphere.local, or administrator@<sso-domain> if isolated). Confirm cluster wld01-cl01 with esx-05a, esx-06a, esx-07a, vSAN healthy, the vSphere Distributed Switch created by the wizard, and the cluster image compliance.

Workload vCenter inventory healthy with three hosts.
Step 2

Open https://nsx-wld01-a.site-a.vcf.lab (admin). System > Fabric > Hosts shows the three workload hosts prepared and Up; System > Appliances shows the manager (cluster) Stable.

Workload NSX fabric healthy.
Step 3

In the management vCenter, find the vc-wld01-a and nsx-wld01-a appliance VMs running on the management cluster (esx-01a..04a).

Workload domain appliances located in the management domain.
Step 4

In SDDC Manager (Inventory > Workload Domains) and VCF Operations (Inventory) confirm wld01 Active with its vCenter, NSX Manager and cluster listed.

Both consoles list the domain consistently.
Step 5

On the HoloRouter: Get-HoloDeckAppNetwork -Site a shows the new FQDNs; Get-HoloDeckDNSConfig -FQDN vc-wld01-a.site-a.vcf.lab resolves. Check Get-HoloDeckSubnet -Site a for the workload VLANs in use.

HoloRouter DNS and subnets consistent with the new domain.
Step 6

Record versions: workload vCenter and NSX builds against the VCF 9.0.2 BOM shown in VCF Operations.

Versions match the BOM.
Step 7

Take the snapshot set holodeck-05-wld-created from the outer layer after Stop-HoloDeckInstance -InstanceID holo (then Start it again).

Snapshot set exists; instance back online.

Validation Gate

Check: Workload vCenter and NSX healthy; appliances located in the management domain; SDDC Manager and VCF Operations consistent; HoloRouter DNS consistent; versions recorded; snapshot taken.

Expected: Validated workload domain with evidence.

Common Errors

Workload vCenter login fails with administrator@vsphere.local
Cause: An isolated SSO domain was chosen.
Fix: Log in as administrator@<the SSO domain you entered>.
Host transport nodes not Up
Cause: TEP IP pool or DHCP missing on the host overlay VLAN.
Fix: Fix the TEP pool and re-run host preparation.
FQDN of the new appliances does not resolve from the workstation
Cause: Workstation DNS cache or record not created.
Fix: Flush DNS; add the record with Set-HoloDeckDNSConfig if absent.

Task 4 Deploy a test workload into the workload domain

Performance

A domain is validated by a workload that uses its compute, storage and NSX networking end to end.

Step 1

In nsx-wld01-a create an overlay segment web-seg (for example 172.16.10.0/24, gateway 172.16.10.1) connected to a Tier-1 gateway. If the domain has no edge cluster, keep the test east-west only, or deploy an NSX Edge cluster first (Configure Centralized Network Connectivity with Edge Clusters) and peer the Tier-0 with the HoloRouter (BGP values from Get-HoloDeckBGPConfig -Site a).

Segment realised and visible as a port group in vc-wld01-a.
Step 2

In vc-wld01-a deploy a small VM (a Linux ISO or an OVA from a content library) on wld01-cl01, vSAN datastore, connected to web-seg, with the vSAN default storage policy.

VM powered on with an IP on web-seg.
Step 3

Test east-west: a second VM on the same or another segment can ping the first. Test north-south if an edge cluster and BGP exist: the VM reaches the HoloRouter and the external network; from the workstation (holodeck-04 routes) reach the VM's overlay IP if the Tier-0 advertises it to the HoloRouter.

East-west connectivity; north-south if the edge/BGP path exists.
Step 4

Check vSAN placement and compliance for the VM (Monitor > vSAN > Physical disk placement) and note the FTT=1 object layout across three hosts (two data components and a witness component).

Objects compliant across the three hosts.
Step 5

Apply a simple DFW rule in nsx-wld01-a (Security > Distributed Firewall) allowing only SSH/HTTP to the VM from the management subnet, with logging; verify the default rule is still Allow and discuss when you would change it to Drop.

Rule applied and tested; default rule action recorded.
Step 6

Record resource consumption of the workload domain on the physical host (CPU, memory, datastore) to see the cost of the domain itself versus the workload.

Consumption figures recorded.
Step 7

Write the validation entry: what the test proved (compute, vSAN, NSX overlay, DFW) and what it did not (performance, HCL, physical NIC redundancy).

Validation entry written.

Validation Gate

Check: Segment, VM, connectivity, vSAN placement, DFW rule and resource figures recorded.

Expected: Workload domain proven end to end in the lab.

Common Errors

VM has no connectivity on the segment
Cause: Segment not realised on the hosts, or Tier-1 not connected.
Fix: Check transport node status and the Tier-1 gateway connection.
No north-south path
Cause: No edge cluster or BGP peering.
Fix: Deploy an edge cluster and peer the Tier-0 with the HoloRouter, or keep tests east-west.
VM creation fails on storage policy
Cause: FTT policy needs more hosts than available.
Fix: Use FTT=1 on three hosts.
DFW rule blocks management access to the VM
Cause: Rule scope or missing allow for your source.
Fix: Correct the source group; keep the default rule Allow while testing.

Task 5 Lifecycle operations: add a cluster, respect vSAN minimums, remove the domain

Manageability

Scale operations have hard limits in VCF: a standard vSAN cluster needs three hosts; a two-host vSAN cluster is only valid with an external witness host. Holodeck adds a documented Day 2 cmdlet for clusters, and removal is a planned, ordered operation.

Step 1

Add a cluster the Holodeck way: Update-HoloDeckInstance -Site a -AdditionalCluster -VIDomain Workload deploys a 3-node vSphere cluster in the workload domain (separate parameter set; cannot be combined with other Day 2 switches). Alternatively add commissioned hosts to the existing cluster from the vSphere Client (cluster > Actions > Add Hosts > Add Unassigned Hosts).

Update-HoloDeckInstance -Site a -AdditionalCluster -VIDomain Workload
A second three-node cluster appears in vc-wld01-a (host capacity permitting), or hosts are added to wld01-cl01.
Step 2

Scale-in rules: write down that a standard vSAN cluster must contain a minimum of three ESX hosts (VCF 9.0.1 documentation), that FTT=1 RAID-1 needs three fault domains (two replicas plus a witness component), and that a two-host vSAN cluster exists only with an external witness host. Therefore do not scale wld01-cl01 below three hosts; if you added a fourth host, remove it to return to three (host in maintenance mode with full data migration, then remove from cluster and decommission to Unassigned Hosts).

Cluster back at three hosts; vSAN healthy; minimum rule recorded.
Step 3

Capacity reasoning: losing one host of three removes one third of the cluster's capacity (not half) and leaves the cluster unable to rebuild FTT=1 until the host returns; record how you would size N+1 in production.

Capacity note written.
Step 4

Decommission: after removing a host from a cluster, decommission it (vSphere Client > Global Inventory Lists > Hosts > Unassigned Hosts > Decommission Selected Hosts). A host that was in a VCF domain must be re-imaged before it is commissioned again; a host that was never in a domain does not.

Decommission rules recorded; host decommissioned if removed.
Step 5

Remove the test workload (VM, segment, DFW rule), delete any NSX edge cluster on wld01 first, then delete the workload domain from VCF Operations (Inventory > Detailed View > wld01 > Actions > Delete Domain) or SDDC Manager. Deletion is irreversible: the domain's clusters, datastores, workload vCenter and NSX Manager (if not shared) are removed, and the hosts return to the free pool in a 'need cleanup' state (VCF 9.0.1 docs p.1529-1530). Network pools are kept.

wld01 removed; appliances deleted; hosts listed in the free pool as 'need cleanup' — decommission them, re-image (in Holodeck, redeploy the nested hosts) and commission again before reuse.
Step 6

Decide whether to keep the three nested hosts for later labs or remove them; record the physical capacity returned.

Decision and capacity recorded.
Step 7

Take the snapshot set holodeck-05-complete (Stop-HoloDeckInstance first, Start after).

Snapshot set exists; instance online.
Step 8

Write the lifecycle entry: operations performed, documented limits applied, time taken for domain creation and deletion.

Lifecycle entry written.

Validation Gate

Check: Cluster added via Update-HoloDeckInstance or hosts added; cluster kept at the three-host minimum; decommission rules applied; domain removed cleanly; snapshot taken; entry written.

Expected: Lifecycle operations executed within the documented limits.

Common Errors

Scaling the vSAN cluster to two hosts
Cause: Ignoring the three-host minimum.
Fix: Keep three hosts; a two-node cluster needs an external witness host and is a different design.
Update-HoloDeckInstance rejects combined switches
Cause: Separate parameter sets.
Fix: Run one Day 2 operation per invocation.
Re-commissioning a host fails
Cause: Host previously in a domain was not re-imaged.
Fix: Re-image (redeploy the nested host) before commissioning.
Delete Domain fails
Cause: Workloads or shared NSX dependencies remain.
Fix: Remove VMs and segments first; a shared NSX Manager stays with the other domain.

Final Validation

A VI workload domain is created on Holodeck 9.0.2 the documented way: nested hosts provisioned and commissioned, the Add Workload Domain wizard in VCF Operations deploying a dedicated vCenter and a new or shared NSX Manager, validation in every console, a test workload on an NSX segment, and lifecycle operations within the vSAN minimums, ending with a clean removal.

✓ Hosts → Three nested hosts from New-HoloDeckESXiNodes, commissioned vSAN HCI with a network pool

✓ Domain → wld01 Active with vc-wld01-a and nsx-wld01-a (new or shared), vSAN OSA cluster of three hosts, Supervisor off

✓ Validation → Workload vCenter and NSX healthy; appliances in the management domain; consoles consistent; versions per BOM

✓ Workload → VM on an NSX segment with east-west (and north-south if edge) connectivity; vSAN FTT=1 placement; DFW rule

✓ Lifecycle → Cluster or hosts added; three-host minimum kept; decommission rules; domain removed; snapshot

Cleanup / Restore

Snapshot: holodeck-05-complete

• Remove the test VM, segment and DFW rule before deleting the domain

• Decommission the three 'need cleanup' hosts; to reuse them for holodeck-06/07, redeploy (re-image) the nested hosts and commission them again

• Record physical capacity before and after

Design Reflection (VCDX)

The workload domain is where VCF's separation of concerns becomes visible: management components in the management domain, each workload domain with its own vCenter (hosted in the management domain) and an NSX Manager that is new or shared with another workload domain, never the management one. Panels will ask why that rule exists (blast radius, lifecycle independence, scale), how you decide between a new and a shared NSX Manager, why Supervisor needs an edge cluster with centralized connectivity, and what the vSAN three-host minimum and FTT maths do to your sizing. Use the lab to practise the wizard's decisions, not to size production.

Requirements

  • Workload domain with its own vCenter deployed into the management domain
  • NSX Manager new or shared with another workload domain, never the management domain's
  • vSAN OSA cluster of at least three hosts with FTT=1
  • Hosts commissioned with the storage type of the cluster and a network pool

Constraints

  • Standard vSAN cluster minimum three hosts; two-host clusters need an external witness
  • vSphere Lifecycle Manager image required for the default cluster
  • Supervisor with centralized connectivity needs an NSX Edge cluster afterwards
  • Password policies (SSO 8-20, vCenter root 15-20 characters)

Assumptions

  • Physical capacity for three more hosts and two appliances
  • holodeck-02 management domain healthy
  • DNS for the new FQDNs on the HoloRouter
  • TEP IP pool or DHCP for the host overlay VLAN

Risks

  • Sharing the management NSX — Impact: not possible by design; a design that assumes it fails — Mitigation: new or shared-with-workload NSX only
  • Scaling below three hosts — Impact: FTT=1 cannot be met — Mitigation: three-host minimum rule
  • Supervisor left on — Impact: activation stuck without edges — Mitigation: decide Supervisor and connectivity before the wizard
  • Capacity exhaustion — Impact: appliance crashes — Mitigation: full-stack sizing row applied

Self-Assessment Discussion Prompts

  1. Why does each workload domain get its own vCenter, and why is it deployed into the management domain rather than into its own cluster?
  2. When would you share an NSX Manager between workload domains, and why can the management NSX Manager never be shared?
  3. What does the vSAN three-host minimum do to your smallest viable workload domain, and when does a two-node-plus-witness design make sense?
  4. Which wizard decisions (SSO domain, Supervisor, connectivity model, NSX size) are design decisions you must defend?
  5. How does the Holodeck full-stack deployment differ from the manual wizard route, and what did the manual route teach you?
  6. How would you present the capacity cost of the domain itself (vCenter, NSX) versus the workloads it hosts?

Extensions

Full-stack deployment comparison

Deploy a second instance with New-HoloDeckInstance without -ManagementOnly (-WorkloadDomainType IsolatedSSO where supported, -NsxEdgeClusterWkldDomain) and compare the automatically created workload domain with your manual one.

harder

Shared NSX Manager

Create a second workload domain that joins the existing nsx-wld01-a and document the shared-NSX implications for lifecycle and failure domains.

harder

Supervisor on the workload domain

Deploy an NSX Edge cluster with an active-standby Tier-0 peered to the HoloRouter, then enable vSphere Supervisor with centralized connectivity (or use Update-HoloDeckInstance -DeploySupervisor where available in your Holodeck version).

harder

vSAN ESA workload cluster

Commission three hosts for vSAN HCI with ESA and build an ESA workload domain; compare with the FAQ guidance on nested ESA.

same

Isolated SSO domain

Create the domain with its own SSO domain and explore the identity implications with VCF SSO (vcp-admin-04).

same

⚠ Known Pitfalls

Expecting the management vCenter to manage the workload cluster COMMON
Problem: Wrong model.
Resolution: Each workload domain has its own vCenter appliance, hosted in the management domain.
Trying to join the management NSX Manager COMMON
Problem: Not allowed by design.
Resolution: Create a new NSX Manager or share one with another workload domain.
Two-host vSAN cluster 'with FTT=1' COMMON
Problem: Impossible without an external witness.
Resolution: Three hosts minimum for a standard vSAN cluster.
Leaving vSphere Supervisor enabled by accident COMMON
Problem: Supervisor waits for an edge cluster.
Resolution: Decide Supervisor and connectivity before the wizard.
Commissioning with the wrong storage type COMMON
Problem: Hosts unusable for the cluster.
Resolution: Match the storage type (ESA/OSA) at commissioning.
Combining Update-HoloDeckInstance switches COMMON
Problem: Cmdlet rejects the call.
Resolution: One Day 2 operation per invocation.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.