I have a vdSwitch on which I have a port-group that all my management VMs connect to:
General | |
Name | MGMT-VM |
Port binding | Ephemeral - no binding |
Number of ports | 14 |
Network resource pool | (default) |
The infrastructure check:
Available free port check for port group in the given vCenter, data center and cluster.MGMT-VM (static)Check if free port is available in the given vCenter, data center and cluster.
fails when that portgroup is selected but works when this one is:
General | |
Name | MGMT-VM (static) |
Port binding | Static binding |
Port allocation | Elastic |
Number of ports | 8 |
Network resource pool | (default) |
I faced the exact same issue when I was trying to deploy a distributed vROPS in my environment. Pre-check was failing complaining about no free ports available. As a workaround I created a new dvPortgroup and placed it in same VLAN in which my other dvPortgroup was and updated the infrastructure details with name of new portgroup and deployment went fine afterwards.
But I am curious to know that if this has been reported to VMware yet or not.
When I enquired about why we are using the Ephemeral binding, I came to know that environment was provisioned via VVD and this is a prerequisite. Since many customers adopted using VVD for automated deployment of SDDC, ephemeral restriction in vRLCM doesn't make sense.
Absolutely agree, the VVD violation is a bit hilarious
the ephemeral portgroups always seem to have 0 ports free. I think this is where the issue comes from. and ya makes no sense whatsover.
workaround was also ok for me to use temp portgroup (new static created), deploy then reconfig to use the proper one
you have to click on the picture to see what I mean ... (its cut off in my screen)