[Bug]: Portgroup not accessible from this host

[tobiaslindinger-broadcom]

Holorouter Version

9.1

VCF Version

VCF 9.1

Target Type

vCenter Cluster

Describe the bug

Holodeck and VCF version are both 9.1 - drop downs of the bug mask do not allow this to be selected

PortGroup is NSX based as per documentation.

New-HoloDeckConfig -Description "VCF 9.1" -TargetHost [vcenter] -Username administrator@vsphere.local -Password [password]
New-HoloDeckInstance -CIDR 10.3.0.0/20 -vSANMode ESA -Version 9.1.0.0 -DeployVcfAutomation -InstanceID vcf91 -DepotType Online

This runs fine for a while and fails with error:

18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] Site Deployment failed.
18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] 6/18/2026 12:38:24 PM New-VM Portgroup not accessible from this host.
18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] HoloDeck deployment failed. Complete error diagnostics saved to: /holodeck-runtime/logs/holodeck-runtime-errors-site-a_18Jun2026_12_29.log
Exception: Failed to deploy HoloDeck

The cluster selected as an install target has four nodes; all of them are prepared with NSX and can access the NSX trunc portgroup. A holodeck instance with version 9.0.1 runs fine.

Reproduction steps

1. New-HoloDeckConfig -Description "VCF 9.1" -TargetHost [vcenter] -Username administrator@vsphere.local -Password [password]
2. New-HoloDeckInstance -CIDR 10.3.0.0/20 -vSANMode ESA -Version 9.1.0.0 -DeployVcfAutomation -InstanceID vcf91 -DepotType Online

Expected behavior

Create ESXi Host VMs without error

Relevant logs

=== FULL ERROR DIAGNOSTICS (DEPLOYMENT FAILED) ===
Timestamp: 18-06-2026 12:38:24
Total Errors in $Error Variable: 14
Current Function: ESXBuild


--- Error [0] (Most Recent) ---
Message: Exiting Function New-HoloSite
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1
Line: 346
Stack Trace:
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 346
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1


--- Error [1]  ---
Message: 6/18/2026 12:38:24 PM  New-VM          Portgroup not accessible from this host.
Exception Type: VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.VimException.ViError
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1
Line: 358
Stack Trace:
at New-HoloDeckESXi<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1: line 358
at New-HoloDeckESXiNodes<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1: line 615
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 181
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1


--- Error [2]  ---
Message: Failed to deploy HoloDeck
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1
Line: 1208
Stack Trace:
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1208
at <ScriptBlock>, <No file>: line 1


--- Error [3]  ---
Message: Exiting Function New-HoloSite
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1
Line: 346
Stack Trace:
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 346
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1

Additional context

No response

[Kevin-GH-1]

I have exactly the same problem, pretty much the same setup and 9.0.1 deployed just fine.
If you know the solution @tobiaslindinger-broadcom please share and i will do the same.

[tobiaslindinger-broadcom]

I found a bug in
/root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1 - line 331
==> $portGroup = Get-VirtualPortGroup -Name $config.target."networkPortGroup-$site"

In my case the Get-VirtualPortGroup returns mutiple results, because the NSX port group is realized on multiple switches.
I picked the right one there with a manual call - dirty, but this let me install VCF 9.1

[jpurohit92]

I found a bug in /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1 - line 331 ==> $portGroup = Get-VirtualPortGroup -Name $config.target."networkPortGroup-$site"

In my case the Get-VirtualPortGroup returns mutiple results, because the NSX port group is realized on multiple switches. I picked the right one there with a manual call - dirty, but this let me install VCF 9.1

Can you please provide me the output of Get-VirtualPortGroup and also the one you might have selected during the pre-check

[tobiaslindinger-broadcom]

PS /root> Get-VirtualPortGroup -Name $config.target."networkPortGroup-$site"
WARNING: The output of the command produced distributed virtual portgroup objects. This behavior is obsolete and may change in the future. To retrieve distributed portgroups, use Get-VDPortgroup cmdlet in the VDS component. To retrieve standard portgroups, use -Standard.

Name                      Key                            VLanId PortBinding NumPorts
----                      ---                            ------ ----------- --------
Holodeck-Trunk            dvportgroup-64443                     Ephemeral   0
Holodeck-Trunk            dvportgroup-64441                     Ephemeral   49
Holodeck-Trunk            dvportgroup-64442                     Ephemeral   0
Holodeck-Trunk            dvportgroup-66547                     Ephemeral   0

The second one is correct

[tobiaslindinger-broadcom]

Replacing line 331 with this should work:

$portGroup = Get-VirtualPortGroup -Name $config.target."networkPortGroup-$site"
if (($portGroup.Count -gt 1) -and ($portGroup[0].ExtensionData.Config.BackingType -eq "nsx")){
    $portGroup = Get-Cluster -Name $config.target.cluster | Get-VMHost | Get-VirtualPortGroup -Name $config.target."networkPortGroup-$site"
}

[Kevin-GH-1]

Thanks for the reply.
About the code above if i test it and fill $site= "a" then it works when i add a $ to the portGroup[0] part.
Then $portgroup is filled with the portgroup i need and not 3 portgroups from 3 different clusters anymore.
But when i add the code to the esxibuild script it still says; portgroup not accessible from this host.
Version 9.0.1 runs fine here also, and the logs are simular to yours.
Portgroup is NSX based as per documentation.
Any idea?

[tobiaslindinger-broadcom]

You are right regarding the missing $. I have corrected it in the post above.
Since the modlue is loaded into memory on powershell startup, you have to make sure it is reloaded. In my case a reboot of the holodeck router vm was the quickest workaround.

[Kevin-GH-1]

You are right Tobias, thanks again!