Holodeck 9.0.2 Prerequisites, HoloRouter Deployment and Binary Staging
Objectives
- Validate the target host against the Holodeck 9.0.2 prerequisites: vSphere 8.0 U3 or 9.0, NTP running, SSD or NVMe storage, MTU 9000, and a dedicated trunk port group with the documented security settings
- Size the host for the chosen deployment from the documented tables (VCF 9.0 management-only or full stack with VCF Automation, vSAN OSA or ESA; VVF 9.0; VCF 5.2)
- Deploy the HoloRouter OVA from the Broadcom Support Portal download, with SSH enabled, and verify the built-in Holodeck PowerShell module from pwsh
- Stage the two binaries a VCF 9.0.2 deployment needs (ESX ISO and VCF Installer OVA) under /holodeck-runtime/bin/9.0.2.0/ and choose the depot method (online with a Broadcom build token, or offline depot)
- Create a Holodeck configuration with New-HoloDeckConfig, understand the 1:1 config-to-deployment rule and the centralized config.json, and snapshot the HoloRouter as the pre-deployment baseline
Prerequisites
One physical ESX host (vSphere 8.0 U3 or 9.0) or a vSphere cluster with capacity for the chosen Holodeck deployment, SSD or NVMe backing storage, an external management network with one free IP for the HoloRouter, and a Broadcom Support Portal account entitled to VCF 9.0 downloads. A jump host or console with a browser and an SSH client on the external network.
Required skills:
- ESX Host Client or vSphere Client administration (port groups, OVA deployment, snapshots)
- Basic PowerShell and SSH
- VCF 9.0 component names (VCF Installer, SDDC Manager, vCenter, NSX, VCF Operations)
Lab Environment
Physical ESX host (or cluster) with vSwitch0: an External port group for the HoloRouter management interface, and a Trunk port group (VLAN 4095, promiscuous mode, MAC address changes and forged transmits set to Accept, MTU 9000 on the switch) for Site A and Site B. The HoloRouter VM (Photon OS, 4 vCPU, 8 GB RAM from Holodeck 9.0.1, 75 GB) carries the Holodeck PowerShell module, the runtime under /holodeck-runtime, and the infrastructure services (DNS, DHCP, NTP, L3 routing, firewall, BGP, proxy, job scheduling, webtop).
Mermaid source
graph LR JH[Jump host / console] -->|SSH root, webtop :30000| HR[HoloRouter VM: External PG + Trunk PG] HR -->|/holodeck-runtime/bin/9.0.2.0: ESX ISO + VCF Installer OVA| BIN[(binaries)] HR -->|New-HoloDeckConfig -TargetHost| ESX[Physical ESX host or vCenter cluster] ESX --- TPG[Trunk PG VLAN 4095, security Accept x3, MTU 9000]
IP Addressing
| Network | Purpose | VLAN |
|---|---|---|
10.1.0.0/20 | Default 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/20 | Default 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 needs | External port group |
Credentials
| System | Username | Password |
|---|---|---|
| HoloRouter (SSH and pwsh) | root | Set 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 |
| Broadcom Support Portal | your entitled account | Needed to download the HoloRouter OVA, the ESX ISO and the VCF Installer OVA, and for the online-depot build token |
Tasks
Task 1 Validate the target host and prepare the trunk port group
ManageabilityHolodeck's pre-checks fail fast on four things: a missing trunk port group, NTP not running on the target host, missing binaries, and an unreachable target. Getting the host right first saves hours.
Record the target host version and confirm it is one the documentation lists as tested and supported: vSphere 8.0 U3 or vSphere 9.0, either a stand-alone ESX host not managed by vCenter or a vSphere cluster managed by vCenter. Confirm the backing storage is SSD or NVMe.
Confirm NTP is enabled and running on the target host (ESX Host Client > Manage > System > Time & Date, or esxcli system ntp get and esxcli system ntp start). If the target is a vCenter cluster, every host in the cluster must have NTP running and configured.
Set the MTU of the vSwitch (vSS or vDS, or the NSX switch) that will carry the Holodeck trunk to 9000.
Create a dedicated trunk port group for the HoloRouter: VLAN ID 4095, on the vSwitch with the uplink; security policy Promiscuous Mode = Accept, MAC Address Changes = Accept, Forged Transmits = Accept. On a vDS, do the same on a distributed port group. If you use an NSX overlay segment instead, set its type to Overlay, allow VLANs 0-4094 (or at least 0, 10-25 for Site A and 40-58 for Site B), and attach IP Discovery, MAC Discovery and Segment Security profiles as the documentation shows.
If the target is a vCenter cluster, allow VLANs 0, 10-25 and 40-58 (or VLAN 0 plus your custom range) on the physical switch ports so nested hosts on different cluster hosts can talk.
Confirm an External (management) port group exists for the HoloRouter's management interface with one free IP (DHCP or static) and that NTP, DNS and, if used, internet access are reachable from it.
Check that memory tiering is not enabled on the host. The FAQ states memory tiering is not recommended for nested environments like Holodeck: deployments may complete but nested hosts can crash, deployment times grow and performance suffers.
Record the host's free CPU, memory and datastore capacity for Task 2.
Validation Gate
Check: Host version, NTP, MTU 9000, trunk port group with the three Accept settings, external port group and capacity figures recorded.
Expected: The target passes the documented Configuration requirements and Target Host Configuration before the HoloRouter is deployed.
Common Errors
Task 2 Size the host from the documented requirement tables
PerformanceThe requirement tables are the design input for everything that follows; a lab that does not fit the table fails late and expensively.
Copy the Physical Host requirements tables for your choice: VCF 9.0 with VCF Automation and vSAN ESA: 32 CPU, 325 GB RAM, 1.1 TB disk single site (64 / 768 GB / 2.5 TB dual site); VCF 9.0 with VCF Automation and vSAN OSA: 24 CPU, 325 GB, 1.1 TB (48 / 768 GB / 2.5 TB); VVF 9.0: 12 CPU, 256 GB, 1 TB (24 / 512 GB / 2 TB); VCF 5.2: 16 CPU, 384 GB, 2 TB (32 / 1 TB / 4 TB). Add the HoloRouter itself: 4 CPU, 8 GB RAM (9.0.1 and later), 75 GB on SSD/NVMe.
Compare with the free capacity from Task 1 step 8 and decide the deployment shape for holodeck-02: -ManagementOnly (4 nested hosts) is the smallest VCF 9.0 shape; a full stack adds 3 workload hosts; -DeployVcfAutomation and NSX Edge clusters add more.
Note the documented timings for VCF 9.0.0.0 as planning figures: -ManagementOnly about 4-5 hours; with -NsxEdgeClusterMgmtDomain 5-6 hours; full stack with VCF Automation and Supervisor 12+ hours. These depend on the physical environment and network.
Decide the vSAN mode. The FAQ warns that nested vSAN ESA on non-vSAN physical storage shows unexpected datastore consumption and poor efficiency; the documentation recommends running nested ESA on physical infrastructure that also runs vSAN. On a single host with local SSDs, OSA (the default) is the safer choice.
Record the licensing model: Holodeck 9.0 deploys VCF 9.0.x in License Later mode, fully functional for 90 days (60 days for VCF 5.2.x); afterwards redeploy or add licences. Plan the lab calendar around that window.
Download from the Downloads page and the Broadcom Support Portal: the HoloRouter OVA (Holodeck 9.0.2), the ESX ISO and the VCF Installer OVA for VCF 9.0.2.0 (the documentation recommends VCF Installer 9.0.2.0 for 9.0.0.0, 9.0.1.0 and 9.0.2.0; Installer 9.0.0.0 is no longer supported). Record file names and sizes.
Validation Gate
Check: Requirement row, deployment shape, timings, vSAN mode, licence window and the three downloads recorded.
Expected: A sized, scheduled plan for the nested deployment.
Common Errors
Task 3 Deploy the HoloRouter OVA and verify the Holodeck module
ManageabilityThe HoloRouter is the toolkit. Everything you will run in later labs is a cmdlet of the Holodeck PowerShell module shipped inside this appliance, driven from pwsh after SSH.
Stand-alone host: in the ESX Host Client, right-click Virtual Machines > Create/Register VM > Deploy a virtual machine from OVF or OVA file, name the VM (for example holorouter) and select the HoloRouter OVA. vCenter target: right-click the cluster > Deploy OVF Template and select the OVA.
Select the storage and the networks: the External port group for Management, and the Trunk port group for Site A and for Site B (the same trunk port group may serve both with the default sites). Accept the EULA.
Networking properties: leave the fields blank for DHCP (fill in DNS if your DHCP does not provide it), or set a static Management IP, CIDR, Gateway and DNS with access to the rest of your network. This IP is how you reach the HoloRouter and every nested component. Set the HoloRouter password.
Select the SSH checkbox and, if you want the light desktop, the Webtop checkbox. The 9.0.2 documentation notes the webtop on port 30000 has no authentication: do not expose it externally, or leave it unselected.
Click Finish and power on the HoloRouter. From the jump host run ssh root@<holorouter-ip> and log in with the OVA password.
Start PowerShell with pwsh and verify the module: Get-Command -Module Holodeck lists the cmdlets (New-HoloDeckConfig, Import-HoloDeckConfig, Get-HoloDeckConfig, New-HoloDeckInstance, Update-HoloDeckInstance, Get-HoloDeckInstance, New-HoloDeckNetworkConfig, Set-HoloRouter, Reset-HoloRouter, Get-HoloDeckSubnet, Get-HoloDeckAppNetwork, Get-HoloDeckBGPConfig, Get-HoloDeckDNSConfig, Reset-HoloDeckState and others). Run Get-Help New-HoloDeckInstance to see the parameter sets. List the runtime: ls /holodeck-runtime (templates, config, bin, logs, specs).
Validation Gate
Check: HoloRouter deployed on the right port groups with SSH; pwsh opens; Get-Command -Module Holodeck lists the cmdlets; /holodeck-runtime exists.
Expected: The toolkit is reachable and verified on the HoloRouter.
Common Errors
Task 4 Stage the VCF 9.0.2 binaries and choose the depot method
ManageabilityA VCF 9.0.x nested deployment needs exactly two files on the HoloRouter: the ESX ISO and the VCF Installer OVA. The remaining VCF components are downloaded by the VCF Installer from the online depot (Broadcom build token) or from an offline depot you prepare.
Create or confirm the version folder on the HoloRouter: ls /holodeck-runtime/bin/9.0.2.0/ (folders exist for 9.0.2.0, 9.0.1.0, 9.0.0.0, 5.2.2, 5.2.1 and 5.2).
Copy the two binaries from your jump host: scp /<local-path>/<ESX ISO File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/ and scp /<local-path>/<VCF Installer OVA File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/. Alternatively, with the webtop enabled, download them from the Broadcom Support Portal inside the webtop browser straight into that folder.
scp /<local-path>/<ESX ISO File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/
scp /<local-path>/<VCF Installer OVA File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/Decide the depot: Online (default -DepotType) needs internet access from the nested VCF Installer (directly or through the HoloRouter proxy) and a Broadcom support site build token, which the deployment prompts for after the pre-checks. Offline needs the Offline Depot Appliance deployed and populated beforehand (Offline Depot page); the deployment then prompts for the depot IP, port, protocol and credentials. The offline depot applies to VCF 9.x only; VCF 5.2.x uses Cloud Builder and needs no depot.
If your lab uses a proxy for outbound access, note the proxy protocol, IP, port and credentials: the interactive deployment (or the -DeveloperMode environment variables enable_proxy, proxy_protocol, proxy_ip, proxy_port, enable_proxy_auth, proxy_username, proxy_password) will ask for them.
For an offline depot, confirm with the documentation note that the depot manifest is the latest from the Broadcom Support Portal if the depot already held earlier VCF 9 binaries.
Write down the two file names exactly as staged; you will see them referenced by the pre-checks in holodeck-02.
Validation Gate
Check: Both binaries in /holodeck-runtime/bin/9.0.2.0/; depot method and proxy details decided.
Expected: The deployment pre-checks for binaries will pass and the depot prompts can be answered.
Common Errors
Task 5 Create the Holodeck configuration and take the baseline snapshot
ManageabilityHolodeck 9.x is built around a centralized config file created and loaded by cmdlets; you never edit it by hand, and one config maps to exactly one deployment. The HoloRouter snapshot gives you a clean baseline to return to in holodeck-07.
On the HoloRouter in pwsh, create the configuration: New-HoloDeckConfig -Description 'lab01-9.0.2' -TargetHost <target vCenter or ESX IP/FQDN> -Username <username> -Password <password>. The cmdlet copies /holodeck-runtime/templates/config.json to /holodeck-runtime/config/<config-ID>.json with a unique config ID and loads it into $config.
New-HoloDeckConfig -Description 'lab01-9.0.2' -TargetHost <target-host> -Username <username> -Password <password>Inspect the loaded configuration: run $config and read the config ID and description. Then list all configurations with Get-HoloDeckConfig, and retrieve yours with Get-HoloDeckConfig -configID <id>.
Practise re-loading: exit pwsh, start it again, and run Import-HoloDeckConfig -ConfigID <id>. $config is per PowerShell session; a new session always needs the import.
Write down the two rules from the documentation: (a) each configuration maps to a single deployment; create a new config for every new deployment and never reuse one, or state conflicts follow; (b) customers are not expected to interact with the config file directly or edit it; the templates/config.json is a template only.
Review the pre-check list the deployment will run (Built-In PreChecks): binaries present in the right location, target host reachable, trunk port group present, NTP running. Tick each against Tasks 1 and 4.
Power off nothing yet; from the outer layer (ESX Host Client or vSphere Client) take a snapshot of the HoloRouter VM named holodeck-01-baseline. This is the clean, pre-deployment state.
Record the lab's identity data for holodeck-02: config ID, target host, trunk port group name, datastore name, depot method, planned InstanceID and vSANMode.
Validation Gate
Check: Config created and re-imported; the two config rules recorded; pre-check inputs satisfied; HoloRouter snapshot taken; deployment card written.
Expected: Ready to run New-HoloDeckInstance in holodeck-02.
Common Errors
Final Validation
Target host validated and sized from the documented tables, trunk port group with the documented security settings, HoloRouter deployed with SSH and the Holodeck module verified in pwsh, the ESX ISO and VCF Installer OVA staged under /holodeck-runtime/bin/9.0.2.0/, depot method chosen, configuration created with New-HoloDeckConfig, and a baseline snapshot taken.
✓ Host prerequisites → vSphere 8.0 U3 or 9.0; NTP running; SSD/NVMe; MTU 9000; trunk PG VLAN 4095 with Promiscuous/MAC changes/Forged transmits Accept
✓ Sizing → Chosen deployment row recorded with HoloRouter 4 vCPU / 8 GB / 75 GB added; 90-day licence window noted
✓ HoloRouter → Deployed on External + Trunk port groups; SSH works; Get-Command -Module Holodeck lists the cmdlets
✓ Binaries → ESX ISO and VCF Installer OVA in /holodeck-runtime/bin/9.0.2.0/
✓ Depot → Online token or offline depot ready; proxy details recorded
✓ Configuration → New-HoloDeckConfig created; Get/Import-HoloDeckConfig practised; 1:1 rule recorded
✓ Baseline → Snapshot holodeck-01-baseline on the HoloRouter VM
✓ Deployment card → Config ID, target, trunk PG, datastore, depot, InstanceID, vSANMode written
✓ Webtop exposure → Webtop disabled or confined to a private network
Cleanup / Restore
Snapshot: holodeck-01-baseline
• Keep the HoloRouter powered on with the baseline snapshot in place
• Keep the staged binaries; they are reused by every deployment of that version
• Store the Broadcom build token and HoloRouter password in your password manager
Design Reflection (VCDX)
A panel does not test Holodeck itself, but it tests whether you understand what a nested lab can and cannot prove. Be ready to explain the HoloRouter's role (one appliance providing DNS, DHCP, NTP, routing, firewall, BGP and proxy so the lab needs one external IP and no physical VLANs), why isolation at the vSS/vDS trunk level with VLAN tagging works, what the licence window implies for a study plan, and which physical-world constraints (vSAN ESA on non-vSAN storage, memory tiering, 10 Gbps NIC requirements) the nested lab masks. Use the lab to practise VCF 9.0 operations, not to size production.
Requirements
- Target host on vSphere 8.0 U3 or 9.0 with NTP, SSD/NVMe and MTU 9000
- Dedicated trunk port group (VLAN 4095) with Promiscuous Mode, MAC Address Changes and Forged Transmits set to Accept
- HoloRouter deployed with SSH; one external management IP
- ESX ISO and VCF Installer OVA staged in /holodeck-runtime/bin/9.0.2.0/
- A fresh New-HoloDeckConfig per deployment
Constraints
- Resource tables: VCF 9.0 management-only or full stack with Automation needs 24-32 CPU, 325 GB RAM, 1.1 TB (single site)
- HoloRouter 4 vCPU, 8 GB RAM, 75 GB
- Licence Later mode: 90 days for VCF 9.0.x, 60 days for 5.2.x
- Webtop is unauthenticated in 9.0.2
- Config files are created and loaded by cmdlets only; never edited by hand
- Offline depot applies to VCF 9.x only
Assumptions
- Broadcom Support Portal account with VCF 9.0 entitlement
- Jump host with SSH and a browser on the external network
- Physical switch trunking in place for cluster targets
- Internet access or an offline depot for VCF bundle downloads
- Physical storage is SSD/NVMe; OSA chosen unless the physical layer is vSAN
- Memory tiering disabled
- A single Holodeck environment per external IP
- Holodeck is used for testing and training only (not a VMware supported product; similar to a Fling)
Risks
- Undersized host — Impact: bring-up fails late — Mitigation: size from the tables with headroom; start with -ManagementOnly
- Trunk security settings missing — Impact: nested hosts cannot communicate — Mitigation: verify the three Accept settings before deploying
- Webtop exposed — Impact: unauthenticated access to the lab — Mitigation: private network or webtop disabled
- Wrong version folder for binaries — Impact: pre-check failure — Mitigation: ls the exact folder before New-HoloDeckInstance
- Config reuse — Impact: state conflicts — Mitigation: one config per deployment
- Licence window overrun — Impact: lab stops working — Mitigation: calendar the 90-day redeploy
Self-Assessment Discussion Prompts
- Why does Holodeck need only one external IP, and what does the HoloRouter do that a physical VCF design needs the data centre to provide?
- Why must the trunk port group accept promiscuous mode, MAC changes and forged transmits, and what does that tell you about nested networking?
- Which of the documented host requirements would you push back on in a production design, and why?
- What does License Later mode allow you to study, and what can it not show you about a licensed estate?
- Why is the configuration file created by a cmdlet and never edited, and how would you defend a similar 'generated, never hand-edited' rule in a production design?
- Where does nested vSAN ESA mislead you about ESA in production?
Extensions
Deploy the Offline Depot Appliance
Follow the Offline Depot page to deploy and populate the Offline Depot OVA with the VCF 9.0.2 bundles, then record the depot IP, port, protocol and credentials for an offline deployment in holodeck-02.
hardervCenter cluster as the target
Repeat Task 1 against a vSphere cluster target: create the distributed trunk port group, allow the Holodeck VLANs on the physical uplinks, and confirm NTP on every host.
sameNSX overlay segment as the trunk
Instead of a vSS/vDS port group, prepare an NSX overlay segment with the documented IP Discovery, MAC Discovery and Segment Security profiles and VLANs 0-4094 allowed.
harderDeveloper-mode variables
Prepare the -DeveloperMode environment variables (brcm_build_token, enable_proxy, datastore_name, trunk_port_group_name, and cluster_name/dc_name for a vCenter target) so holodeck-02 can run without interactive prompts.
same⚠ Known Pitfalls
References
- Holodeck 9.0.2 documentation (index): Environment Overview, Holorouter Overview, Concepts, Pre-requisites, Deployment, During Deployment, Post Deployment, Day 2 Operations, How ToTier 1 — Official
Primary source for every HoloRouter and toolkit step in this lab. Fetched 1 Oct 2026. - Holodeck 9.0.2 command referenceTier 1 — Official
New-HoloDeckInstance, Update-HoloDeckInstance, Get-HoloDeckInstance, New/Get/Import-HoloDeckConfig, Reset-HoloDeckState, New-HoloDeckNetworkConfig, Set-/Reset-HoloRouter, Get-HoloDeckSubnet/AppNetwork/BGPConfig/DNSConfig/OverlaySubnet/AppIpPools, Get-HolodeckServiceIPPools. - Holodeck 9.0.2 FAQ and troubleshootingTier 1 — Official
Pre-check errors (binary not found, no trunk port group, NTP not running), ESX build SSH wait, memory tiering, nested vSAN ESA. - Holodeck 9.0.2 downloads and release notes (known issues)Tier 1 — Official
HoloRouter OVA and Offline Depot OVA; release notes at /release_notes/ carry the Known Issues per release. - Holodeck GitHub repository: issues and discussionsTier 2 — Supporting source
Where to report bugs; community troubleshooting. The releases page carries no binaries (OVA downloads are on the Broadcom Support Portal).