Configuring NSX-T Federation with NSX-T: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
If you want to rebuild this lab you can find the configuration workbook and diagrams below: | If you want to rebuild this lab you can find the configuration workbook and diagrams below: | ||
{{Download|file=Federation-Diagrams.pdf|Federation-Diagrams.pdf| Drawings for NSX-T Federation Lab)}} | |||
{{Download|file=L11-Config-Workbook.xlsx|L11-Config-Workbook.xlsx | Configuration Workbook for NSX-T Federation Lab)}} | |||
==NSX-T Federation | Part 1 | The (nested) lab environment to build the NSX-T Federation lab== | ==NSX-T Federation | Part 1 | The (nested) lab environment to build the NSX-T Federation lab== | ||
Revision as of 10:02, 21 January 2024
The video's in this article will show you how to configure NSX-T Federation across three sites.
The vSphere (nested) Infrastructure
In this article, I explain to you how you build the (nested lab) infrastructure that you can use as a basis for the NSX-T Federation lab build.
Lab information
If you want to rebuild this lab you can find the configuration workbook and diagrams below:
Drawings for NSX-T Federation Lab)
Configuration Workbook for NSX-T Federation Lab)
NSX-T Federation | Part 1 | The (nested) lab environment to build the NSX-T Federation lab
A few weeks ago, VMware released NSX-T 3.0.0 with a lot of new excellent cool, and shiny features. One of these features is NSX-T Federation, where we have the opportunity to stretch network services across multiple sites, including security services, and with that the preparation for simplified disaster recovery. In the video series that I will be publishing the upcoming week, I am going to show you how to configure NSX-T Federation from scratch and show you all of the routing and security use-cases with traffic flows. I am also going to dive into the supported topologies and what is not supported. But before I am going to that, I am first going to walk you through my (nested) lab environment and show you how the infrastructure looks like so you can better understand the other video's in the series. And maybe you want to replicate this setup as well, and by watching this video, this will be easier.
=NSX-T Federation | Part 2 | The Edge/Host Transport Node Configuration basics (for NSX-T
Federation)= In my previous video (PART 1) I explained the basics of how I am going to deploy NSX-T FEderation in upcoming videos. In this video, I am going to explain how we configure the NSX-T Edge and Host Transport Nodes with respect to NSX-T Federation. Most of the steps re not any different than configuring the NSX-T Edge and Host Transport Nodes in NSX-T version 2.5.x. But for completeness purpose, I added this footage in to get a better understanding of the full NSX-T Federation Architecture.
NSX-T Federation | Part 3 | NSX-T Federation between NSX-T (LM = Local) and (GM = Global) Managers
In my previous video (PART 2) I explained how we configure the NSX-T Edge and Host Transport Nodes with respect to NSX-T Federation. This video will explain how you configure and deploy the NSX-T Federation items, where the configurations are done in PART 2 of this video series is a prerequisite.
NSX-T Federation | Part 4 | Stretched T0/T1 Gateway configuration with full BGP networking
In my previous video (PART 3) I explained how the NSX-T Federation is initially deployed. In this video, I am going to explain how we are going to use NSX-T Federation to deploy and configure a full network with a stretched T0 Gateway and stretched T1 Gateway. I will also include the BGP peering configuration for each site so you can see how this fully works from an end-to-end perspective.