Create Stretched Networks in VMware NSX-T Federation

First lets create Tier-1 GW to provide connectivity between Location-1 and Location 2 (Dallas/FortWorth) through RTEP

Primary Global Manager Tier-1 Gateways page before creating the Dallas-Fort Worth stretched Tier-1 gateway.

In your primary Global Manager go to Networking > Connectivity > Tier-1 Gateways

Add Tier-1 GW

Tier-1 gateway editor with a stretched gateway name, non-preemptive failover, and edge-pool allocation settings.

Provide a name.  I recommend putting something in the name to indicate this is a stretched T1

Keep failover to Non-Preemptive

In Edges Pool Allocation Size select ROUTING

Stretched Tier-1 gateway location settings assigning the Dallas RTEP edge cluster as the primary location.

Select Primary Location LM and the RTEP Edge Cluster

Keep MODE Primary

ADD LOCATION

Stretched Tier-1 locations showing Dallas as primary and Fort Worth as secondary with their RTEP edge clusters.

Next select the Secondary Location LM and the Secondary site RTEP Pool

Keep mode Secondary

Stretched Tier-1 route-advertisement settings enabling static routes and connected segments and service ports.

Under Route Advertisement enable All Static Routes and All Connected Segments & Service Ports

Click Save

NSX-T confirmation that the Dallas-Fort Worth stretched Tier-1 gateway was created successfully.

No

vSphere network inventory for Fort Worth showing the stretched web segment and local production web segment.

Confirm Status Success

Next we will create a stretched Segment

Global Manager Segments inventory showing segments from Dallas and Fort Worth before adding the stretched segment.

As you can see, we can see the web segment created in FortWorth even though I am logged into Primary Global Manager in Dallas

Add Segment

Segment editor for naming a stretched segment and connecting it to the stretched Tier-1 gateway.

Provide a segment name; once again put something to show it is stretched

Select the stretched T1 GW

Provide a CIDR for the subnet

Stretched segment configuration mapping the Dallas and Fort Worth locations to their respective overlay transport zones.

Confirm your Locations and Transport Zones after attaching the Tier-1 GW

NSX-T segment configuration showing the Save control beneath DHCP Static Bindings.

Save

NSX-T confirmation that the Dallas-Fort Worth stretched web segment was created successfully.

No

Dallas vCenter network inventory showing the existing NSX-T segments before validating the new stretched segment.

Log into the vCenter for your primary site and you should now see the newly created segment

Fort Worth vCenter network inventory showing the Dallas-Fort Worth stretched web segment alongside the local web segment.

Log into the vCenter for your secondary site and you should now see the newly created segment

vCenter settings for the Test-web-01 virtual machine at the secondary site before attaching it to the stretched network.

Attach the test virtual machine to the newly created segment

vCenter virtual-machine settings showing DallasPRD-web-01 connected to the Dallas-Fort Worth stretched segment.

Attach another test VM at your other site to the newly created segment

Linux terminal showing five successful ICMP replies with no packet loss across the stretched network.
Linux terminal showing a successful reverse-direction ping across the stretched network with no packet loss.

Perform a ping test between the two virtual machines at the two different sites

Next we will create and a stretched Tier-0 GW

Keep exploring

Choose your next step

Continue with the path that best matches the architecture or operating challenge in front of you.

Leave a Reply

Discover more from Digital Thought Disruption

Subscribe now to keep reading and get access to the full archive.

Continue reading