And as a quick reminder,
here's what we did in the previous skill.
We deployed this single Tier-1
virtualized routing function in NSX.
We refer to it as a gateway.
And that gateway as a distributed router
lives here on ESXi-A.
That distributed router lives here on ESXi-B
both as transport nodes, so that either one of them
has all the information regarding in the interfaces
and the logical routing
that this Tier-1 Gateway can provide.
And that way if, for example,
this VM here wants to communicate with this VM here,
this local ESXi host can provide WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this local ESXi host can provide
all that logical routing service
between those two VMs on those two different segments,
which again are on two different subnets.
Or in the case of this VM here,
communicating with this VM over here, VM-1 to VM-4,
the local ESXi host having a copy of that distributed router
can go ahead and make the routing decision first
and then forward the traffic
over the GENEVE tunnel over to ESXi-B.
And that way, ESXi-B can forward that traffic over
to the final destination, in this case, VM-4.
And that's all with a single Tier-1 distributed router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's all with a single Tier-1 distributed router
doing East-West traffic routing inside of our topology.
So with that in mind, from our previous skill,
let's build upon that and let's put a plan together
to add some additional distributed routers.
And here is what I propose we do.
Instead of just having one Tier-1 router
for our East to West routing,
let's go ahead and add another one.
So, we currently have our first gateway in place.
It was doing the routing between Segment 10 and Segment 20.
But what I'd like to do is add a second Tier-1 Gateway.
So this one's called Gateway-A.
We'll call this one Gateway-B. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll call this one Gateway-B.
And then to connect it altogether,
let's go ahead and also add a Tier-0 Gateway,
and that's this guy right here.
we'll call it Tier-0 Gateway-0.
And that way whenever we hear zero, we'll know,
"Oh, we're talking about this Tier-0 Gateway here."
Whether I call it the Tier-0 Gateway or the Gateway-0,
we're talking about this guy right here as a Tier-0 Gateway.
So, the big picture is once we create this infrastructure,
we create the additional gateway here
and the other one here, and we link them together,
those three virtual routers will live here
on this transport node ESXi-A WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on this transport node ESXi-A
and they'll also live in the mind
and brains of ESXi-B as well.
So, if I drew the little green one here,
that'll be our Tier-0 router, our distributed router.
And we'd also have our Tier-1 Gateway-A.
I'll put a little A there, and A over here as well,
'cause it's also got a copy.
And also our Tier-1 Gateway-B as well.
So as far as the instances of the distributed router,
we're gonna have sets of those here
for each of these three gateways on ESXi-A and on ESXi-B.
And they will also be here on our edge nodes as well, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And they will also be here on our edge nodes as well,
including Edge-1 and Edge-2.
So, we also draw them up here.
So, Edge-1 will have a copy or an instance
of the distributed router representing Tier-0.
So will Edge-2.
Edge-1 will have an instance
for this Tier-1 Gateway-A as a distributed router.
So, put that here with an A.
Also, Edge-2 same thing.
And for the Tier-1 Gateway-B,
they'll both have a copy of that as well.
So, I'll put that here just as reference.
And up to this point, I'm being very specific
about focusing on just the distributed routing function WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
about focusing on just the distributed routing function
inside of NSX because in addition
to having a distributed router
that's running on multiple nodes here,
we also, as we add additional functionality
for network services,
we are also going to be introducing a services router.
For example, when we deployed our Tier-1 Gateway-A,
if we had said, "Hey, you know what?
Instead of just running as a distributed router,
let's go ahead and use Active Standby or Active Active."
That additional function for fault tolerance
and high availability on our edge nodes,
they would also then have included WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
they would also then have included
the services router component as well
as we start to add our network services.
So, anytime we're implementing network address translation
or VPN or connectivity, for example, from a Tier-0 Gateway
out to the physical world to the physical network,
so I'll put external connectivity.
Any of those options are gonna automatically require
the addition of a services router on the nodes that need it.
So, I wanna give you a heads up
that I'm intentionally to this point designing
and putting network together with just the DR function WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and putting network together with just the DR function
and not the services router function.
And that way we can get comfortable
with where that distributed router shows up.
And then, as we start to connect
to the outside world in a separate skill,
we'll automatically see based on our existing infrastructure
that we're automatically adding
that services router component.
Or I should say, NSX is gonna be adding
that services router component behind the scenes
to the transport nodes that need it.
So for our game plan, let's do this.
We currently have one Tier-1 Gateway-A
that's connected to Segment 10 and Segment 20.
But what I'd like to do is I'd like to recreate or modify WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But what I'd like to do is I'd like to recreate or modify
our existing topology and make it into this one.
So, our first step here would be to create
the new Tier-1 Gateway-B,
and then connect that to the correct segments.
In this case,
we wanna connect Tier-1 Gateway-B to Segment 20,
which means we'll also go ahead and tell Gateway-A
that it's still longer directly connected
over here to Segment 20.
And that way we can get the topology in place.
And then third, let's go ahead and create
our Tier-0 Gateway-0.
And then once we have that gateway connected,
we'll go ahead and we'll link up
the Tier-1 Gateway-B to the Gateway-0. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the Tier-1 Gateway-B to the Gateway-0.
And also we'll link up the Tier-1 Gateway-A
up to the Tier-0 Gateway-0.
So effectively, you're gonna link Tier-1 up to Tier-0.
And one of the cool things when we link these together
is that we don't have to manually come up
with an IP addressing scheme
for these inter gateway communications.
It's automatically gonna use an address base
of something in the range of 100.64 something.
And it will auto assign those,
and it often does that with a /31.
So, when we see the automatic subnetting here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, when we see the automatic subnetting here
and the IP addressing between the Tier-0s and the Tier-1s,
just realize that's an automatic function
that's happening by default
when we link those gateways together.
And one other challenge is this.
We need to make sure that Tier-0,
this Tier-0 Gateway that we're gonna deploy,
we wanna make sure it knows about how to reach
the 10.10 network down here
and the 10.20 network down here.
Because even though it's directly connected
to each of the Tier-1 routers where it will be
once we put that together, it doesn't.
Meaning, the Tier-0 Gateway does not by default
just automatically learn WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just automatically learn
about all the reachable subnets below.
So, we're also gonna need to take a moment
and click a button on Tier-1 Gateway-A,
and also that same button here
on Tier-1 Gateway-B that says,
"Hey, you know what?
Please advertise any directly connected subnets
up to your Tier-0 Logical Gateway."
And that way, then Tier-0 will know about reachability
to the 10.10 address space for Yellow here,
and also the IP address space used on the Segment 20,
which is our 10.20.0/24 network address space.
So, make a note.
We'll tell the Tier-1s to advertise WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll tell the Tier-1s to advertise
their directly connected routes.
Then once we do, we'll have full routing
inside of our NSX environment here.
So, if VM-1 wants to communicate with, for example, VM-2
and here's their IP addresses.
These do happen to be on the same host.
And fortunately, ESXi-A has a copy,
an instance, if you will, of the distributed routers.
And as a result,
it can make all those logical routing decisions internally
and forward the traffic.
Or if VM-1 is gonna communicate over here with VM-4,
once again, ESXi-A having all the information WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
once again, ESXi-A having all the information
on the gateways will make the routing decision.
Then, identify that the layer to address
associated with VM-4 is reachable over at ESXi-B
at which point it'll go ahead and forward
that encapsulated traffic over the tunnel.
ESXi-B will de-encapsulate that and then forward it on
to the final destination.
So, let me clean this up just a little bit
and we'll use this as our game plan.
So with that in mind, in the very next video,
let's turn our attention to our NSX Topology.
And let's start by creating this additional Tier-1 Gateway
and we'll call it Tier-1 Gateway-B. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we'll call it Tier-1 Gateway-B.
So, we'll see you in the next video for exactly that.