nbdk's Posts

It would nice to receive answer to this non-answered question. From my current research's seams Horizon doesn't have any integration with Cloud Director.  Also, it seams advised to deploy dedicated... See more...
It would nice to receive answer to this non-answered question. From my current research's seams Horizon doesn't have any integration with Cloud Director.  Also, it seams advised to deploy dedicated vCenter, ESXi  just for Horizon Services. This is obviously huge waste of resources for current Cloud Providers based on VMware. There is also an old blog post from 2013. about this https://myvirtualcloud.net/how-to-horizon-view-and-vcloud-director-multi-tenant-daas/ but since this is from ten years ago stating there is no integration between Cloud Director and Horizon. However, VMware might did some progress in this matter in last 10 years. Let's hope that someone can shed more light on this matter.    
Hi Dejan, It would be helpful if you have mentioned what version of Cloud Director you are using and if your pvdc is backed by NSX-v or NSX-t. "As system administrator all DPGs are appeared in Prov... See more...
Hi Dejan, It would be helpful if you have mentioned what version of Cloud Director you are using and if your pvdc is backed by NSX-v or NSX-t. "As system administrator all DPGs are appeared in Provide VDC " DPGs shouldn't be listed in PVDC, i think you probably thought External networks. However, as Admin you should see vDS PortGroups in Resources\Infrastructure resources\Port Groups. "but when I want to add network in a OrgVDC with Import DPG only direct/isolated button can be chosen. " You are probably looking for "imported/ Distributed Virtual Port group option". This option should be available to you if you have NSX-T backed organization. I never been in situation to have only "direct/isolated options". It must be some non-standard configuration or a bug. If you previously had mentioned option available you can check with VMware support why you are missing it now. Additional, not sure why you want to import vDS Port Group to Org Network, I guess for some reason you need to have vDS PortGroup backed by physical VLAN. From my experience following options are available while adding Org Network: 1) In case your Organization vDC is backed by NSX-v (VXLAN), options during Org Network creation process are: Routed, Isolated and Direct. 2) In case your Organization vDC is backed by NSX-T (geneve), options during Org Network creation process are: Routed, Isolated, Direct and Imported [NSX-T logical switch and Distributed Virtual Port Group] Option that you are looking for is documented here: https://docs.vmware.com/en/VMware-Cloud-Director/10.5/VMware-Cloud-Director-Tenant-Guide/GUID-6FA096A4-9AE6-4F7E-AE65-C01D12ACA68D.html " User has administrator role on whole vcenter cluster which is used for registering vmware resurces in vCD". This is unusual. Usually User has only access to Cloud Director Org while admin has access to vCenter and Provider CD     
Hello, Recently in my vSphere environment after trying to create new NSX-V backed network I got a following warning: Task Name  Add Distributed Port Group Status  The spec.numPorts exceeds the ... See more...
Hello, Recently in my vSphere environment after trying to create new NSX-V backed network I got a following warning: Task Name  Add Distributed Port Group Status  The spec.numPorts exceeds the limit 2048. Cannot increase the number of ports according to the specification, because total number of ports 2051 after increase will then exceed 2048, maximum number of ports allowed on vDS. Error stack: Cannot increase the number of ports according to the specification, because total number of ports 2051 after increase will then exceed 2048, maximum number of ports allowed on vDS   After checking from vCenter\Distributed Switch\Summary\Switch Details I noticed that current number of ports is 2048.   This number 2048 was very strange to me since distributed switch static (non-ephemeral binding) ports maximus is around 10000.. and for NSX-T default ephemeral binding is only the one lower around 1016.  However when checking with VMware support they mentioned that there is another configuration maximus under https://configmax.esp.vmware.com/ -> NSX \ Layer 2 Networking \ MAC Identifiers per Overlay Logical Switch (VNI) and it is 2048. WIth description: If this number of MAC entries is exceeded then newer MAC entries will not be added until l the older MAC entries expire. This condition can lead to flooding in the logical network. --------------------------- Currently this maximus is only impacting NSX-V and is not impacting NSX-T Port Groups that can be created (they are being created because of migrating from NSX-V). However the same maximus is present for NSX-T. Please note that hosts are using two physical 25G uplinks. What would be a proper way to scale this ?  Creating Additional vDS ?           
In the end VMware support with advice from engineering team managed to solve the issue. Issue was a bad data in cloud director about edge that doesn't exist anymore. This happened because edge was c... See more...
In the end VMware support with advice from engineering team managed to solve the issue. Issue was a bad data in cloud director about edge that doesn't exist anymore. This happened because edge was created and removed by terraform. After bad data was removed from CD database issue was resolved.   This subject can be closed.  
After upgrading Cloud Director from 10.3.3 to 10.4.1 or 10.4.2 we are experiencing issue that "External Networks" are unavailable and also NSX-V network changes are not possible. VMware support info... See more...
After upgrading Cloud Director from 10.3.3 to 10.4.1 or 10.4.2 we are experiencing issue that "External Networks" are unavailable and also NSX-V network changes are not possible. VMware support informed us that currently there is no solution and that bug will be resolved in version Cloud Director 10.5. Does anyone have info when CD 10.5 is expected, approximately ?