paluszekd's Accepted Solutions

Sorry, I'm afraid this isn't possible - a trunk interface must be tied to an external network and subinterfaces are only tied to org VDC networks within that edge. You could, however, create this above VCD and map it as a direct connected External Network inside of a orgVDC network.

Hi diegodco31, in-line - My questions are: 1 – Can I have in one same vCloud one NSX-T and one NSX-V in different vCenters? I can't find any articles to help me. Yes, one can have a VCD instance that has multiple vCenters that mix and match NSX-T and V. We can even have a single provided backed vCenter instance that has NSX-V and NSX-T. 2 - What are the benefits of having a PKS? I saw that I can install CSE in standard mode and I do not need a PKS. PKS, or TKGI, provides the ability to roll out the entire, certified stack for a dedicated organization. As of right now, we can support TKGI/PKS or upstream K8s for CSE. 3 - I saw that the CSE 2.6.1 GA supports only the NSX-T 2.5.1 and the vCenter 7 supports only NSX-T 3. Can I use the CSE with vCenter 7? I don't believe this has been fully certified - CSE 2.6.1 only supports VCD 10.1 while it has not been validated for 10.1.1. 10.1.1 introduced support for NSX-T 3.0.x and vSphere 7. The API calls from VCD to NSX-T are fundamentally different between 2.5.1 and 3.0.x.

Hello, What was the errors you were seeing as it relates to failed connections to vSphere? Note that SSL management changed and if you are using self-signed certs for vSphere/NSX, you must re-accept these certs post-10.1 upgrade. I wrote about this new behavior here: https://www.paluszek.com/wp/2020/04/10/upgrading-to-vmware-cloud-director-10-1-ssl-management-changes/ -Daniel

Yes, please check the interop guide for VMware Tools and the underlying vSphere version for this to work. VCD makes the call to vCenter along with VMware Tools for any in-guest customization. https://www.vmware.com/resources/compatibility/pdf/VMware_GOS_Compatibility_Guide.pdf

Then it sounds like you're fine, but if you plan on offering self-serviceability - just be aware of the above. Also note you could granularly control write privileges for network services too using Rights Bundles/RBAC structure within VCD.

Not possible today with vCD. To achieve this, you would need to utilize a northbound solution like a GLSB or utilize WorkspaceONE that federates each vCD instance and passes the SAML handoff to that respective site.

Your endpoint is not set for proper H5 UI usage. This needs to be set and match your FQDN. Go to the Provider Flex UI -> Administration -> Public Addresses Ensure you set your API and Tenant Portal:

This needs to be removed using the new CloudAPI - it cannot be done via the UI. Please browse the /docs section on your vCD instance, you will find the VdcGroupApi section and shows the deleteVdcGroup option -

Sebastian, Thanks for the comments. Right now, there's no plans on adding this as a configurable option. Only other thing I can think of is provider managed large Edges while exposing the networks as External Networks to each tenant (however this puts the burden on your team to manage). I am putting in the request and will talk to the team about it. Thanks, -Daniel

Yes, all this does is turns on ECMP for any northbound communication. It assumes you have active/active paths northbound for peering. For example, having provider managed edges that are in ECMP mode.

Your endpoint address probably doesn't match or isn't set. This is required for the H5 UI. In Flex, go to System -> Administration -> Public Addresses and ensure it matches your FQDN under the tenant portal -

Therefore is there no other org-vdc that i can group to the vCD org-vdc to use cross vdc-networking. Right? <DCP> Right </DCP> I just want to bind some vdc-org networks to the universal TZ insted of the local TZ (to use it directly in the other cluster). <DCP> You will need to do this from an external network - create the universal LS and expose it to the vCD orgVDC as an External Network. That would be the only available option at this time. </DCP>

Could be permissions on the file - did you do a comparison of the chmod permissions between one of the working cells and the inoperable cell? Your vcloud user should have rw permissions along with vcloud:vcloud as the user/group