The Lonely VGW

-

Gilles Chekroun
Lead VMware Cloud on AWS Solutions Architect
---
Once upon a time in a remote country, there lived a VGW. 
He was lonely and not attached to anything. 
A few SDDCs were sad to see that lonely VGW and decided to establish route-based VPN to him to make some friendship. 
The lonely VGW was very happy to have new friends and decided to propagate all SDDC routes to everyone. 
SDDCs were even more happy because they learned everyone's routes via BGP and were able to communicate freely. 
SDDCs and VGW lived together very happily for ever after.

Background

During my studies on VPN, I saw a very interesting site here that describes how a Virtual private Gateway can propagate BGP routes learned from attached Customer Gateways.
I decided to do a quick test using VMware Cloud on AWS SDDCs as customer gateways and I was really surprised by the results.

Setup

Very straight forward as described in the picture below:

1 - Create a Virtual private Gateway

2 - Create VPN Connections

Note the SDDC VPN public IP from the Networking and Security Overview Tab
and use it as "Customer gateway IP address"

Open the SDDC VPN Tunnel FW rule
Create the Route based VPN in the SDDC

3 - Check AWS connectivity

Check SDDC Advertised routes

4 - Setup the second SDDC

Don't forget to set the Local ASN number
Create the Route based VPN on the second SDDC
Check learned routes from SDDC1

4 - Go back to SDDC1

Check the routes learned from SDDC2

5 - Repeat the process for SDDC3

I will leave it to you ;)

Conclusion

By opening the proper FW rules in both SDDCs, any VM can communicate with any other VM in any other SDDC.


Thanks for reading.

Comments

Post a Comment

Populars

Egress VPC and AWS Transit Gateway (Part1)

-
Image
Gilles Chekroun
 Lead VMware Cloud on AWS Solutions Architect --- Usually my blog posts are customer driven and recently I have been working on a design that would include an Egress VPC and AWS Transit Gateway. This customer is going to use both VMware Managed Transit Gateway and also AWS Transit Gateway. I will split this post in 3 parts: The Egress VPC - this article Adding a VMC SDDC to the Egress VPC here Adding VMware Managed Transit Gateway here Why do we need an Egress VPC? Numerous posts on AWS site  will describe how to build an Egress VPC and the subtleties of the various route tables of the TGW and the Egress VPC itself. The main goal is to have ONE Internet gateway only  that will allow workloads to go out to internet on the Egress VPC. One of the most important point is redundancy and multi-availability zones. Applications usually reside in private subnets, while NAT Gateways reside in a public subnet. NAT Gateways To focus the Internet access to a single point, we can cre
Read more

AWS Transitive routing with Transit Gateways in the same region

-
Image
Gilles Chekroun Lead VMware Cloud on AWS Specialist --- At the AWS Re:invent 2019 conference, the long waited TGW peering functionality was announced and available in a few AWS regions. This is an INTER-REGION peering only meaning that the Transit Gateways need to be in different regions. Hoping that AWS will soon release an INTRA-REGION capability I discussed with a few AWS Solutions Architects in Las Vegas, among them Tom Adamski , about using a VPC as a bridge between two TGWs in the same region. Tom assured me that it is possible opening for the first time the transitive routing capability in AWS networking. Well . . . I needed to test that and see by myself. Test bed For a simple test, I will use 2 TGWs in the same regions with 2 VPCs attached each and another VPC as "bridge" connected to both TGWs. Yes you can connect a VPC up to 5 TGWs . The whole idea is to use this "bridging VPC" and point the default route of the TGWs to it. To do that I c
Read more

Build a VMware Cloud on AWS Content Library using AWS S3

-
Image
Gilles Chekroun Lead NSX Systems Engineer - VMware Europe --- What is a Content Library? DISCLAIMER: External content libraries are not supported by VMware GSS ! vSphere Content Library is a repository where you can store VM templates, vApp templates and other kind of files like ISO.  Administrators can use the templates to deploy VMs and vApps. Each item library can contain multiple files. The basis is  .ovf   together with the description files like .mf and .vmdk If you have .ova files, you can simply un-compress them using the linux command:  tar -xvf SomeFile.ova There are two kind of Libraries: Local and Subscribed. Local Library Local Library stores items in a single vCenter. VM and vApp templates are stored as OVF file format. Subscribed Library You can create a Subscribed Library in the same vCenter and to ensure the content is up-to-date, the library can automatically sync with the source on a regular basis. You can also use the option to download co
Read more