Academy/Holodeck Lab Setup & Operations/Troubleshooting Holodeck Deployment Failures
This lab targets VCF 9.0.2

Troubleshooting Holodeck Deployment Failures

VCF 9.0.2Intermediateadminsupportvcdx⏱ 120 min

Troubleshooting methodology applies across VCF 9.0.0-9.0.2 with Holodeck 9.0.2. Paths are those of the HoloRouter (/holodeck-runtime) and of the VCF Installer appliance (/var/log/vmware/vcf). 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

  • Locate and read the Holodeck runtime on the HoloRouter: /holodeck-runtime (templates, config, bin, logs, specs), the per-instance output.json read by Get-HoloDeckInstance, the deployment state file behind idempotency, and the -LogLevel switch
  • Diagnose HoloRouter-side faults with the network cmdlets (Get-HoloDeckSubnet, Get-HoloDeckAppNetwork, Get-HoloDeckBGPConfig, Get-HoloDeckDNSConfig, Get-HolodeckServiceIPPools) and the Set-HoloRouter / Reset-HoloRouter pair
  • Diagnose nested ESX build failures from the documented pre-check errors (binary not found, no trunk port group, NTP not running) and the SSH-not-responding wait
  • Diagnose VCF bring-up failures in the VCF Installer UI and its domainmanager.log, and in the VCF Operations fleet management log
  • Build a personal runbook that maps each symptom to its cause, its documented fix, and the resume action (re-run, Reset-HoloDeckState, Reset-HoloRouter + Set-HoloRouter, or Remove-HoloDeckInstance)

Prerequisites

holodeck-02 complete (or at least attempted): a HoloRouter with a configuration and a deployed or partially deployed instance; outer-layer snapshots available.

Prior labs: holodeck-02

Required skills:

  • Linux shell basics on Photon OS (ls, tail, grep, journalctl, systemctl)
  • PowerShell cmdlet discovery (Get-Help, Get-Command)
  • VCF Installer and NSX Manager navigation
📸 Starting State: S3-9x — Management Domain Deployed (VCF 9.x)

Lab Environment

Same as holodeck-02: HoloRouter plus the nested management domain (or a failed partial deployment). All troubleshooting is done from an SSH session on the HoloRouter (bash and pwsh), the VCF Installer UI and appliance shell, and the outer vSphere layer.

Mermaid source
graph LR
  SSH["SSH root@holorouter"] --> BASH["bash: /holodeck-runtime/logs, journalctl, systemctl"]
  SSH --> PWSH["pwsh: Get-HoloDeck* cmdlets, Reset-HoloDeckState, Set-/Reset-HoloRouter"]
  VI["VCF Installer appliance"] --> LOG["/var/log/vmware/vcf/domainmanager/domainmanager.log"]
  OUTER["Outer vSphere layer"] --> SNAP["nested VM consoles, power state, snapshots"]

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)

Tasks

Task 1 Know the runtime, the logs and the state

Manageability

Everything Holodeck knows about your deployment lives under /holodeck-runtime on the HoloRouter. Reading it in the right order turns a wall of output into a diagnosis.

Step 1

SSH to the HoloRouter and list the runtime: ls -la /holodeck-runtime/ and its folders: templates (the config.json template), config (<config-ID>.json per deployment), bin/<version>/ (staged binaries), logs, specs (JSON API specs written by -ProvisionOnly).

Folder map of /holodeck-runtime recorded.
Step 2

List the logs: ls -lt /holodeck-runtime/logs/ and tail the most recent deployment log with tail -n 200. Identify the phase markers you saw in holodeck-02 (pre-checks, networking setup, nested ESX build, VCF Installer, bundles, bring-up).

Newest log identified; phase markers located.
Step 3

Re-run a deployment with -LogLevel DEBUG (valid values INFO, DEBUG, SUCCESS, WARN, ERROR; default INFO) when you need more detail; record how much louder DEBUG is and when you would use WARN or ERROR to filter.

LogLevel behaviour understood.
Step 4

In pwsh (config imported) run Get-HoloDeckInstance -InstanceID holo: it reads the instance output.json and returns deployed components, networking and deployment state. Find the output.json under /holodeck-runtime and compare.

output.json located; its content matches the cmdlet output.
Step 5

Understand idempotency: Holodeck stores the deployment state on the HoloRouter; re-running the same New-HoloDeckInstance command resumes at the failed step. Reset-HoloDeckState clears that state (irreversible) for a clean restart when the state is corrupted. Do not run it now; note where it fits in your runbook.

Resume vs reset decision rule written: re-run first; reset only for corrupted state.
Step 6

Read the FAQ note on handled errors: messages during deployment that are not in RED text and do not exit the script are handled. Mark in your log excerpt which lines were handled and which (if any) were fatal.

Fatal vs handled lines classified.
Step 7

Open the Holodeck release notes (Known Issues per release) and the GitHub issues page; note the three known issues most relevant to your environment and their workarounds. These are the first places the FAQ sends you for version-specific bugs.

Three known issues and workarounds noted with their release.

Validation Gate

Check: Runtime map, newest log and phases, LogLevel behaviour, output.json vs Get-HoloDeckInstance, resume/reset rule, handled vs fatal classification, known issues noted.

Expected: You can read a failed run from the HoloRouter without guessing.

Common Errors

Looking for logs on a workstation or in a C:\ path
Cause: Older-generation habits.
Fix: All Holodeck logs are under /holodeck-runtime/logs on the HoloRouter; VCF Installer logs are on the installer appliance.
Running Reset-HoloDeckState after every failure
Cause: Not using idempotent resume.
Fix: Re-run the same command first; reset only if the state is corrupted.

Task 2 Diagnose HoloRouter faults: routing, DNS, DHCP, BGP, services

Availability

The HoloRouter provides DNS, DHCP, NTP, L3 routing, firewall, BGP and proxy for the nested estate. When any of them is wrong, every later phase fails in confusing ways. The cmdlets show you what the network manager generated; Set-/Reset-HoloRouter rebuild it.

Step 1

In pwsh list what the network manager generated for Site A: Get-HoloDeckSubnet -Site a | ft -AutoSize (names such as mgmt-a, vmotion-a with VLAN IDs, subnets and gateways), Get-HoloDeckAppNetwork -Site a (hostname, IP, FQDN per appliance), Get-HoloDeckBGPConfig -Site a (router AS, edge AS numbers, BGP password), Get-HoloDeckOverlaySubnet -Site a, Get-HoloDeckAppIpPools -Site a and Get-HolodeckServiceIPPools -Site a.

Full Site A network inventory captured from the cmdlets.
Step 2

Check name resolution on the HoloRouter: Get-HoloDeckDNSConfig (all records; the cmdlet queries the CoreDNS ConfigMap) and Get-HoloDeckDNSConfig -FQDN esx-01a.site-a.vcf.lab. From bash, resolve a nested FQDN against the HoloRouter itself (for example with nslookup or dig if present) and from your console using the HoloRouter external IP as DNS.

Records present for every appliance; resolution works from the HoloRouter and from the console.
Step 3

Check DHCP and routing: from a nested host console or the webtop, confirm the host received the expected management IP and that the gateway for its subnet is the HoloRouter interface listed by Get-HoloDeckSubnet. Trace a path from the console to a nested IP through the HoloRouter external IP.

Nested host IPs and gateways match the subnet table; routing through the HoloRouter works.
Step 4

Check BGP if an edge cluster exists: compare the Tier-0 BGP neighbour state in NSX with Get-HoloDeckBGPConfig; the HoloRouter is the peer (FRR). From bash, inspect the FRR state (vtysh or the FRR service logs) if available on the appliance.

BGP peering established, or the mismatch (AS, password, uplink VLAN) identified.
Step 5

Inspect the HoloRouter's services: the documentation lists DNS, DHCP, NTP, routing, firewall, BGP, proxy, job scheduling and webtop; the command reference notes DNSMASQ for DNS services and FRR for BGP, and that Reset-HoloRouter needs permissions to modify Kubernetes resources. From bash run kubectl get pods -A and systemctl --failed: since Holodeck 9.0.2 DNSMASQ runs in Kubernetes on the HoloRouter (3 DNS pods + 1 DHCP pod, Holodeck official docs), so expect those pods; if kubectl reports localhost:8080 refused, rerun with KUBECONFIG=/etc/kubernetes/admin.conf (github.com/vmware/Holodeck issue #127). Expect only HoloRouter infrastructure services here; SDDC Manager, vCenter and NSX are VMs on the nested hosts, never pods on the HoloRouter.

Infrastructure services healthy (or the failed unit identified). No VCF components on the HoloRouter.
Step 6

Check the proxy if the nested estate reaches the internet through the HoloRouter: confirm the proxy settings given during deployment and that the VCF Installer can reach the depot. Check NTP on the HoloRouter and that nested hosts sync from it.

Outbound path and time source verified.
Step 7

Rebuild if needed: Reset-HoloRouter removes DNSMASQ, FRR, VLANs, VRF tables and custom routing and restores the original DNS configuration (it disables DNS and routing for the environment until Set-HoloRouter runs again); Set-HoloRouter [-dualsite] [-CIDR <array>] reconfigures it. Remove-HoloDeckInstance -ResetHoloRouter removes the instance networking and reboots the HoloRouter; New-HoloDeckInstance configures networking again.

Reset/Set sequence recorded with its impact (service outage for the nested estate while reset).
Step 8

Write the HoloRouter section of your runbook: symptom, cmdlet to confirm, fix, impact.

Runbook section complete.

Validation Gate

Check: Network inventory, DNS, DHCP/routing, BGP, services, proxy/NTP checked with the documented cmdlets; reset/reconfigure sequence recorded.

Expected: HoloRouter faults can be confirmed and repaired without guesswork.

Common Errors

Nested FQDNs do not resolve from the console
Cause: Console DNS not pointed at the HoloRouter.
Fix: Use the HoloRouter external IP as the console DNS server, or use the webtop.
Tier-0 BGP neighbour never establishes
Cause: AS or password mismatch, or edge uplink VLAN wrong.
Fix: Compare with Get-HoloDeckBGPConfig and Get-HoloDeckSubnet; correct the edge uplink.
Routing and DNS vanish after Reset-HoloRouter
Cause: Expected: the reset removes them.
Fix: Run Set-HoloRouter (or re-run New-HoloDeckInstance, which configures networking) to restore.

Task 3 Diagnose nested ESX provisioning failures

Recoverability

The nested host build has a short list of documented failure modes; each has a documented fix in the FAQ.

Step 1

Pre-check: '<Component> binary was not found. Download the binary from the Broadcom support portal and place it in /holodeck-runtime/bin/<version> folder'. Confirm with ls -lh /holodeck-runtime/bin/9.0.2.0/ that both the ESX ISO and the VCF Installer OVA are present and intact.

Both files present in the exact version folder; or the missing file identified.
Step 2

Pre-check: '[ERROR] No trunk port groups found on the connected server. Please create a trunk port group on the Target Host and run the pre-checks script again.' Verify on the target a port group with VLAN 4095 (or multiple VLANs), Promiscuous Mode, MAC Address Changes and Forged Transmits set to Accept; on a vDS do the same on the distributed port group.

Trunk port group present and compliant; or created now.
Step 3

Pre-check: '[ERROR] NTP service is not running on target host <IP>. Enable NTP service before proceeding'. On the ESX host: Manage > System > Time & Date > Edit Settings > NTP with a server, then Start; or via SSH: esxcli network firewall ruleset set -e true -r ntp; esxcli system ntp set -s <server>; esxcli system ntp set -e true; esxcli system ntp start.

esxcli network firewall ruleset set -e true -r ntp
esxcli system ntp set -s pool.ntp.org
esxcli system ntp set -e true
esxcli system ntp start
NTP running on every target host (all hosts in a cluster target).
Step 4

Build phase: 'WARNING: Host key is not being verified since Force switch is used.' and 'CustomIso[...]: [INFO] SSH service on <IP> is not responding, Trying after 10 seconds'. This is expected while the nested host boots; wait 10-15 minutes. Beyond 15 minutes: check the nested ESX VM is powered on and its console shows the DCUI; confirm networking (trunk security settings, VLANs on a cluster target); try ssh root@<nested-ip> yourself.

Hosts come up within the window, or the stuck host and its cause (power, console error, networking) identified.
Step 5

Resource symptoms: nested hosts crash, deployment is slow, or vSAN ESA datastore appears fully consumed. Check the FAQ causes: memory tiering enabled on the physical host (not recommended for nested), nested ESA on non-vSAN physical storage, HDD-backed storage, or a host below the requirement table.

Resource cause identified against the FAQ and the requirement tables.
Step 6

Datastore selection problems: if the deployment cannot place VMs, confirm the datastore chosen at the interactive prompt (or $env:datastore_name in -DeveloperMode) has the capacity from the requirement table and is SSD/NVMe backed.

Datastore capacity confirmed.
Step 7

After fixing any of the above, re-run the same New-HoloDeckInstance command and confirm it resumes at the nested ESX phase rather than starting over.

Resumed run proceeds past the host build.
Step 8

Add each symptom, its documented fix and the resume action to the runbook.

Host-build section of the runbook complete.

Validation Gate

Check: Three pre-check errors and the SSH wait reproduced or confirmed with their fixes; resource causes mapped; resume verified.

Expected: Host provisioning failures are diagnosed from documented messages.

Common Errors

Binary present but still 'not found'
Cause: Wrong version folder or truncated upload.
Fix: Match the folder to -Version exactly; compare sizes to the downloads.
Trunk exists but hosts cannot talk
Cause: Security settings not Accept, or MTU below 9000.
Fix: Set the three Accept settings and MTU 9000.
SSH still not responding after 15 minutes
Cause: Nested VM boot failure or networking.
Fix: Open the nested VM console; check DHCP/VLAN; power-cycle the VM; re-run.

Task 4 Diagnose VCF bring-up failures in the VCF Installer

Recoverability

Once the nested hosts are up, the VCF Installer drives the bring-up. Its UI validation report and the domain manager log on the installer appliance are the documented places to look.

Step 1

Open https://vcfinstaller-a.site-a.vcf.lab (admin@local). Review the deployment validation report: every failed or warning item names the component and the check.

Validation report read; failing checks listed.
Step 2

Bundle download problems: confirm the depot configuration in the installer (online with the Broadcom token through the proxy if configured; or the offline depot IP/port/protocol/credentials). For an offline depot confirm the manifest is the latest from the Broadcom Support Portal.

Depot reachability and credentials confirmed, or the failing element identified.
Step 3

SSH to the VCF Installer appliance and tail the domain manager log: tail -f /var/log/vmware/vcf/domainmanager/domainmanager.log (VCF 9.0.1 documentation, Log Files and Locations: 'If you experience validation or deployment failures, check the log files for the domain manager service on the VCF Installer appliance').

tail -f /var/log/vmware/vcf/domainmanager/domainmanager.log
The failing task and its error are visible in domainmanager.log.
Step 4

If the failure involves VCF Operations or VCF Automation deployment, check /var/log/vrlcm/vmware_vrlcm.log on the VCF Operations fleet management appliance (same documentation page).

Fleet management log inspected where relevant.
Step 5

Check the nested estate's prerequisites the installer validates: DNS forward and reverse for every appliance (Get-HoloDeckDNSConfig), NTP, and host state (all four nested hosts reachable with vSAN-eligible disks). Fix on the HoloRouter side if the network manager output is wrong.

Prerequisite causes isolated to HoloRouter or nested host.
Step 6

Retry: in the installer UI retry the failed task after fixing the cause; or re-run the New-HoloDeckInstance command, which resumes and drives the installer again. Record which worked.

Bring-up continues after the retry.
Step 7

Write the bring-up section of the runbook: validation item, log line pattern, cause, fix, retry path.

Bring-up section complete.

Validation Gate

Check: Installer validation report, depot configuration, domainmanager.log and vmware_vrlcm.log used; retry path exercised.

Expected: Bring-up failures are diagnosed from the documented logs.

Common Errors

Looking for Cloud Builder logs
Cause: VCF 9.x has no Cloud Builder.
Fix: Use the VCF Installer UI and domainmanager.log on the installer appliance.
Bundle download stalls
Cause: Proxy or token problem, or stale offline manifest.
Fix: Fix proxy/token; update the offline depot manifest.
Validation fails on DNS
Cause: HoloRouter DNS records missing or console-side DNS wrong.
Fix: Check Get-HoloDeckDNSConfig; rebuild with Set-HoloRouter if the records are gone.

Task 5 Build the troubleshooting runbook

Manageability

A VCDX candidate shows a repeatable method: symptom, confirming evidence, documented cause, fix, resume action, and the time it costs.

Step 1

Consolidate the four sections (runtime/logs, HoloRouter, host build, bring-up) into one table with columns: Phase, Symptom (exact message), Where to confirm (cmdlet, log path, UI), Documented cause, Fix, Resume action (re-run / Reset-HoloDeckState / Reset-HoloRouter + Set-HoloRouter / Remove-HoloDeckInstance [-ResetHoloRouter] + redeploy), Time cost.

One runbook table with at least 12 rows.
Step 2

Add the escalation path: Holodeck release notes Known Issues, GitHub issues (vmware/Holodeck), and the Broadcom VCF community; note that Holodeck is not a VMware supported product (similar to a Fling) so there is no support case for the toolkit itself.

Escalation path documented with the support-status caveat.
Step 3

Decide the destructive actions and their guard rails: Reset-HoloDeckState (irreversible), Reset-HoloRouter (removes DNS and routing until Set-HoloRouter), Remove-HoloDeckInstance (deletes the nested hosts and installer VM; -ResetHoloRouter also removes networking and reboots the HoloRouter). Require a snapshot check before each.

Guard rails written for the three destructive cmdlets.
Step 4

Test the runbook once: induce a safe failure (for example stop NTP on the target host or rename the trunk port group), run the deployment pre-checks, follow your own table to the fix, and resume.

Runbook row proven end to end; time recorded.
Step 5

Record the lessons as design notes: which failures are design inputs in production (DNS, NTP, trunking, depot access) and which are lab-only.

Design notes added.
Step 6

Revert the induced failure and confirm the environment is healthy (holodeck-02 Tasks 4-5 checks).

Environment healthy.

Validation Gate

Check: Runbook table complete with resume actions and guard rails; one row tested; design notes written; environment healthy.

Expected: A reusable troubleshooting method for Holodeck 9.0.2 deployments.

Common Errors

Runbook lists fixes without the resume action
Cause: Idempotency not understood.
Fix: Every row ends with re-run or the specific reset.
Destructive cmdlets run without a snapshot
Cause: No guard rail.
Fix: Snapshot check before Reset-HoloDeckState, Reset-HoloRouter and Remove-HoloDeckInstance.

Final Validation

The Holodeck runtime, logs and state are understood; HoloRouter, nested host build and VCF bring-up failures are diagnosed with the documented cmdlets, messages and log paths; a tested runbook with resume actions and guard rails exists.

✓ Runtime and logs → /holodeck-runtime map; newest log phases; output.json vs Get-HoloDeckInstance; LogLevel

✓ HoloRouter → Subnet/AppNetwork/BGP/DNS/IP-pool inventories; services; Reset/Set sequence

✓ Host build → Three pre-check errors and SSH wait mapped to fixes; resume verified

✓ Bring-up → Installer validation report, domainmanager.log, vmware_vrlcm.log used

✓ Runbook → 12+ rows, escalation path, guard rails, one row tested

Cleanup / Restore

Snapshot: holodeck-03-complete

• Revert any induced failure

• Keep the runbook with the lab notes

• Confirm the instance is healthy before holodeck-04

Design Reflection (VCDX)

Panels probe method, not memory: when a deployment fails, where do you look first and why, how do you distinguish an infrastructure-service fault (DNS, NTP, routing) from a product fault, and what is your blast radius for each recovery action. Holodeck gives you a compact model: one appliance of infrastructure services, one installer, one state file, one resume rule. Translate it into production language: dependencies, idempotent automation, documented log locations, and guarded destructive operations.

Requirements

  • Every failure is diagnosed from documented messages and log paths
  • Resume via idempotent re-run before any reset
  • Destructive cmdlets guarded by snapshots

Constraints

  • Holodeck is not a VMware supported product
  • Reset-HoloDeckState is irreversible
  • Reset-HoloRouter removes DNS and routing until Set-HoloRouter
  • Remove-HoloDeckInstance -ResetHoloRouter reboots the HoloRouter

Assumptions

  • SSH access to the HoloRouter and the installer appliance
  • Outer-layer snapshots exist
  • Console DNS can point at the HoloRouter
  • Release notes and GitHub issues reachable

Risks

  • Reset instead of resume — Impact: hours lost — Mitigation: runbook rule
  • Reset-HoloRouter during a healthy deployment — Impact: estate loses DNS/routing — Mitigation: guard rail
  • Chasing Cloud Builder in 9.x — Impact: time lost — Mitigation: installer-first runbook
  • Unreported known issue — Impact: repeated failure — Mitigation: release notes check first

Self-Assessment Discussion Prompts

  1. Why does Holodeck put DNS, NTP, routing and BGP on one appliance, and what does that do to your fault-isolation method?
  2. How does an idempotent deployment change the recovery runbook compared with a restart-from-scratch tool?
  3. Which of the documented pre-check errors would be change-management failures in production?
  4. What is the blast radius of Reset-HoloRouter, and how would you express a similar control for a production DNS change?
  5. Where do you look first when the installer's validation fails, and why that log?
  6. What would you tell a panel about using an unsupported toolkit to prepare a supported-platform design?

Extensions

Developer-mode failure injection

Use -DeveloperMode environment variables to script a deployment, inject a wrong datastore_name, and document the failure and resume path.

same

Provision-only diagnosis

Run -ProvisionOnly and perform the VCF Installer bring-up by hand using /holodeck-runtime/specs/, diagnosing each validation failure in domainmanager.log.

harder

Release-notes watch

Set up a weekly check of the Holodeck release notes Known Issues and GitHub issues and fold new items into the runbook.

same

⚠ Known Pitfalls

Searching a Windows console for logs COMMON
Problem: No HoloConsole exists in 9.x.
Resolution: Logs live under /holodeck-runtime/logs on the HoloRouter and under /var/log/vmware/vcf on the VCF Installer.
Resetting state after every failure COMMON
Problem: Loses the idempotent resume.
Resolution: Re-run the same command first.
Running Reset-HoloRouter to 'fix DNS' COMMON
Problem: Removes DNS and routing for the whole estate.
Resolution: Diagnose with Get-HoloDeckDNSConfig first; reset only as a planned rebuild followed by Set-HoloRouter.
Treating handled messages as errors COMMON
Problem: Needless interventions.
Resolution: Only RED text that exits the script is fatal.
Ignoring the release notes COMMON
Problem: Re-discovering known issues.
Resolution: Check Known Issues for the release before troubleshooting.
Expecting VCF components as pods on the HoloRouter COMMON
Problem: Wrong mental model of the architecture.
Resolution: The HoloRouter hosts infrastructure services only; VCF components are VMs on the nested ESX hosts.
Opening a Broadcom support case for the toolkit COMMON
Problem: Holodeck is not a supported product.
Resolution: Use release notes, GitHub issues and the community; support cases cover the VCF products, not the toolkit.

References

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