VMware Cloud Community
ahmedwaleedmali
Contributor
Contributor

Communication between different VDC

We have hosted a centralised application in one VDC and want to access it using the private IP(not edge gateway) in another VDC. What are the possible options for this? I know that we can create a shared network and attach that to vApps in both these VDCs but we are looking for alternatives.

Reply
0 Kudos
6 Replies
Sreec
VMware Employee
VMware Employee

Kindly provide more insight into how VDC networking is done, and how many edges, routing designs, and subnets that are used in source and destination VDC. 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
ahmedwaleedmali
Contributor
Contributor

Thanks for the reply. I'll simplify the architecture just to explain our use case. Let's say, we have the following setup:


VDC A:
1. An OVDC routed network "routed-a" is connected to edge gateway A with the gateway IP being 192.168.1.1.

2. The routed network is connected to a single vApp.

3. That vApp hosts an application that is accessible at 192.168.1.3:3303 from within the VDC for networks that are connected to edge gateway A.

 

VDC B:
1. An OVDC routed network "routed-b" is connected to edge gateway B with the gateway IP being 192.168.2.1.

2. The routed network is connected to multiple vApps.

How can we access the application hosted in VDC A at "192.168.1.3:3303" from a VM within this VDC?


The solution that we are using right now:
1. Create a direct network in each VDC B that is attached to "routed-a" OVDC network.

2. Attach an additional NIC to each VM to give it access to that network and thus "192.168.1.3:3303". 

The problem with this solution is that this is not scalable. So we are looking for alternatives for this.

 

Currently, we have both NSX-V and NSX-T environments available so we are looking for something that is more generic. I'm assuming that there is no way to do this without involving the edge gateway right? Our environment is supposed to be air-gapped(offline setup) so everything will be done on private IPs and we'd really want to avoid going through the internet; which I suppose is hapeening in our current solution right?

 

Reply
0 Kudos
Sreec
VMware Employee
VMware Employee

Thanks for sharing the detailed update. You can configure Static or Dynamic routes on Each Edge and advertise those networks, this design is fully supported. 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
ahmedwaleedmali
Contributor
Contributor

> You can configure Static or Dynamic routes on Each Edge and advertise those networks


It's not possible to advertise routes(networks) on NSX-V based environments right?  

Reply
0 Kudos
Sreec
VMware Employee
VMware Employee

It is 100% possible 🙂 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
ahmedwaleedmali
Contributor
Contributor

I'm still a bit new to the VDC realm so please don't mind me asking. 

I have attached the screenshots of what I've configured. Is that all we need? Like now I can assign these static routes to my VMs(preferably on primary NIC), let's say assign 192.168.10.1 as the primary IP to my VM and then access it from the VM in the other VDC at 192.168.10.1:3303? 

I'm going through the VMware Cloud Director documentation but this is still a bit unclear for me. I have redacted the gateway IP and interface name in the screenshots but the next hop is configured as the edge gateways gateway IP.

Tags (1)
Reply
0 Kudos