Yes, we still require a NSX-v Manager during the new vCenter addition workflow. However, as others stated, one can use dvPG backed Network Pools and essentially use External Networks (and Direct ...
See more...
Yes, we still require a NSX-v Manager during the new vCenter addition workflow. However, as others stated, one can use dvPG backed Network Pools and essentially use External Networks (and Direct from an org). NSX-T can be paired also within a site. If you're in VCPP, NSX DC SP-Base is included in the base bundle.
Hi there - This isn't possible in 10.1, but possible now with 10.2 with DC Groups. We now have the ability to create a shared network between orgVDCs within the same organization.
It is technically possible to connect multiple VCD instances to a vCenter instance, but we do not have an official supported stance on this architecture. This is due to the VCD -> vCenter connect...
See more...
It is technically possible to connect multiple VCD instances to a vCenter instance, but we do not have an official supported stance on this architecture. This is due to the VCD -> vCenter connectivity nature from the cells to vCenter. I highly suggest a dedicated vCenter per Reseller since I presume you'll be dedicating hosts anyway.
Unfortunately, this isn't possible today. You can configure potentially custom orgadmin and tenantadmin rights that might met your requirements, but this is something you'll need to test. I s...
See more...
Unfortunately, this isn't possible today. You can configure potentially custom orgadmin and tenantadmin rights that might met your requirements, but this is something you'll need to test. I suggest putting in a feature request (Contact Us ) to request this specific feature.
I presume you are using a self-signed cert, correct? Click on that link (that is your URL endpoint or tunnel endpoint) and accept the cert. From there, the plugin will populate. This is expected ...
See more...
I presume you are using a self-signed cert, correct? Click on that link (that is your URL endpoint or tunnel endpoint) and accept the cert. From there, the plugin will populate. This is expected behavior when using self-signed certs.
What are the errors you are seeing within the tasks screen? Under one of the cells, please look at the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log file and vcloud-container-info.l...
See more...
What are the errors you are seeing within the tasks screen? Under one of the cells, please look at the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log file and vcloud-container-info.log.
I'm also confused - the third screenshot clearly shows the appliance is being used (I see the VAMI blue screen interface). The script just changes the /etc/ssh/sshd_config file and appends the...
See more...
I'm also confused - the third screenshot clearly shows the appliance is being used (I see the VAMI blue screen interface). The script just changes the /etc/ssh/sshd_config file and appends the "PermitRootLogin" configuration while restarting the service. I can directly see this in my VCD cell appliance config. If you are using a Linux installation, I would follow the process set-forth within that distro for enabling remote root login.
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...
See more...
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 there - could you provide further context here? What kind of org VDC networks and what topology are you trying to achieve? We introduced local Datacenter groups in VCD 10.1 that allows you ...
See more...
Hi there - could you provide further context here? What kind of org VDC networks and what topology are you trying to achieve? We introduced local Datacenter groups in VCD 10.1 that allows you to share a routed org VDC network between two orgVDC's while establishing active/passive or active/active egress points. This is for NSX-V as of today.
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 inst...
See more...
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.
Hi Chris, Are you asking if we could share the same IP across both sites, or the same IP space between both sites? The latter could be possible - split up your Public IP CIDR block between th...
See more...
Hi Chris, Are you asking if we could share the same IP across both sites, or the same IP space between both sites? The latter could be possible - split up your Public IP CIDR block between the two sites within the IP Pool of each External Network and assign accordingly. However, there isn't a way to move an allocated Edge IP from one site to another during a failover/migration.
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-...
See more...
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. ...
See more...
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
Hi Lee, Yes it does. For the IP to be applied, VMware Tools must be running and be part of the guest customization process upon instantiation/creation. What OS are you running?
Hi there - I presume this is via Cross-VDC Networking? You will need to set up a subset of the IP pool on each site. At this time, there's no "unified" IP pool mechanism to carve out IP's across ...
See more...
Hi there - I presume this is via Cross-VDC Networking? You will need to set up a subset of the IP pool on each site. At this time, there's no "unified" IP pool mechanism to carve out IP's across all connected oVDCs within the DC Group. For example, if my CIDR is 192.168.1.1/24 and I wanted to allocate 192.168.1.100-192.168.1.150 across two sites, I would put in 192.168.1.100-125 at Site-A and 192.168.1.126-150 to Site-B. -Daniel
This error typically is due to the endpoint configuration on the tunnel appliance and ensure it matches what's specified in the URL endpoint. Verify this is setup correctly between the Cloud Repl...
See more...
This error typically is due to the endpoint configuration on the tunnel appliance and ensure it matches what's specified in the URL endpoint. Verify this is setup correctly between the Cloud Replication Manager and the Tunnel appliance.
