So these three routers as shown are our distributed router functions for the
tier zero and the two tier ones.
And then on our edge nodes, which are providing the fault tolerance and the
physical access to the network up here,
we now have a logical SR, a services router function that's on both edge one
and edge two.
So edge one as the active router will be doing the actual movement of the
traffic from the NSX environment over to the physical network.
So I'm going to go ahead and draw some connectivity here as well.
And then what I'd like to do right here, I'd like to write out the entire path WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then what I'd like to do right here, I'd like to write out the entire path
that would be taken from VM one going out to, for example, this IP address at
192.168.1.1,
which is my router on my physical network.
Actually, in reality, it's actual firewall that also does routing, but it has
the IP address of 192.168.1.1 and it is a physical appliance.
So I'd like to write out the path here. Let's start with VM one and VM one is
at dot 10 and it is connected to this DR and that is gateway A and its IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
at dot 10 and it is connected to this DR and that is gateway A and its IP
address on this network is dot one.
And then this is the 10 dot 10 dot zero dot zero slash 24 network. Fantastic.
So VM one, if it needs to forward packets off of its local network, it's going
to send them over to its default gateway.
Now, gateway A being connected to this tier one router automatically gets a
default route.
So if it doesn't have a more detailed route on how to forward a packet, it's
simply going to forward traffic up here to the tier one DR. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
simply going to forward traffic up here to the tier one DR.
So I'm going to put that next as our inter router segment here.
So this would represent here gateway zero and then for the IP addresses there.
In fact, let's take a moment and let's just document what those IP addresses
are.
So currently I have a CLI open up to the edge one and also down here to ESXIA.
They both have a copy of the distributed router for gateway A.
So if we do a get gateways and press enter, but I love about get gateways over
here on the edge compared to the ESXIA is that is telling you upfront with
names exactly which one it is.
So for gateway A, it is this one right here, which is the one that starts with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for gateway A, it is this one right here, which is the one that starts with
DB two and ends with FE one to.
So that's the UUID for gateway A and also shows here that on the edge, it's
using a VRF two to support that.
So I'm going to document that as well inside of our notes that way when we see
this UUID will know exactly which virtual router we're talking about.
It's going to be gateway A. So I'm a little arrow here and then for gateway A,
it's UUID begins with DB two whole bunch of other characters and it ends with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it's UUID begins with DB two whole bunch of other characters and it ends with
FE 12.
Also on edge one, it happens to be VRF number two. So if we need to go look at
there, we can just go into that VRF.
All right, so that in mind, let's take a look at this connection between
gateway A and gateway zero and identify the network there.
So here on the edge, we could just type in VRF two and press enter the prompt
changes to reflect that we're in VRF two for that virtual gateway.
So if we did a get forwarding and let's look at our options here, let's see, we
get forwarding and let's look for the default route of 0, 0, 0, 0, slash zero, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
get forwarding and let's look for the default route of 0, 0, 0, 0, slash zero,
press enter.
Or that way we can focus on just a single route look at the default route and
it says the next hop address is 164, 0, 0, which I got to admit if you're used
to working with slash 30s and less.
That looks like a weird valid IP address, but because we're using a slash 31,
it is. We can also do a get interfaces here for this gateway A and press enter.
And that's also showing us what the local address here is. And if we scroll
down, this is also showing us the interface we're using on that common network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
down, this is also showing us the interface we're using on that common network.
So here's the name. It's our tier zero to tier one gateway LRP and that's the
logical router port.
And then the port type is linked and here is the local IP address on gateway A.
So the next hop is 164, 0, 0, which is our tier zero gateway the DR there.
And the local interface on that common link is 164, 0, 1. So let's add that to
our documentation. So this network has 100.64.0.0 slash 31. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
our documentation. So this network has 100.64.0.0 slash 31.
And over here is 0 as the next hop and over here, based on what we just saw,
this is 164, 0, 1. Again, that's all with a 31 bit mass.
All right, so that covers the gateway A. Now, at some point on our tier zero
router, we are going to need a default route effectively saying, Hey, if you
don't know how to forward a packet, forward it to this next top.
So we're going to need a default route that says in our topology here that the
next hop should be 192, 168, 1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
next hop should be 192, 168, 1.1.
And currently, I don't have that static route in place, but it's super easy to
create a static route on a tier zero gateway.
You simply click a few buttons, you specify what you want the default route to
be, and you're done. So let's take a moment and do that right now.
So here on our edge, let's exit out and go back to the main NSX CLI for edge
one and let's do a get gateways.
And so for the distributed router for our tier zero gateway zero logical router
, if we just type in VRF one, that'll take us into the logical routing for that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
, if we just type in VRF one, that'll take us into the logical routing for that
specific route.
And it's a lot easier than typing out the commands and having to put in the
full UUID.
So here we do a get and a space question mark. Let's do a get forwarding.
So I'll type get forwarding in a space of question mark.
And let's also look for the default route. So we'll go ahead and do a zero zero
zero zero zero zero and no routes to display.
Let's go ahead and do a get forwarding and take a look at everything.
And here's everything it knows about. So there's some IPV six routes.
And if we scroll up here, we have routes to get down to segment 10 segment 20. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we scroll up here, we have routes to get down to segment 10 segment 20.
We have routes for our links between us, the tier zero gateway and our tier one
gateways.
We also have some really cool one 69 254 routes. And those are the internal
networks that we're going to be using and seeing in just a moment for the
routing between the DR on the tier zero gateway and the SR on the tier zero
gateway.
But for now, we don't have a default route. So let's go ahead and add one.
So back in the NSX manager, we'll go to networking tab up on top and on the
left, we'll click on the tier zero gateways and then we'll edit our tier zero WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
left, we'll click on the tier zero gateways and then we'll edit our tier zero
gateway and simply tell it, hey, we want to add a static route.
So to do that, we'll click on the three dots. We'll click on edit and then we
'll scroll down and then down below, we have a section called routing.
And then in routing, we have an area for static routes. We'll click here on set
and then we'll click on add static route and we'll say default for T zero.
And then the route we want to add is 0 0 0 0 0 slash zero, which is how you
represent an IPV for a default route.
And then we need to tell it with this option right here, what the next top is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we need to tell it with this option right here, what the next top is.
In our case, it's going to be my physical gateway at 192 168 1.1.
So we'll click here on set and then we'll click further on set next tops.
And then we'll go ahead and we'll add the next top of 192.168.1.1.
Then for the administrative distance, we'll take a closer look at that and some
of the options when we have a whole skill on routing.
So for now, I'm just going to add this one static default route with a next top WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for now, I'm just going to add this one static default route with a next top
of 192.168.1.1. We'll click on add, click on apply, click on save and click on
close and scroll down and click on close editing.
And we'll collapse that. And now let's go take a look at our distributed router
gateway zero and take a look at its routing table.
So previously, we are looking at VRF 1, which is the VRF 4, our tier zero
gateway zero DR, and it did not have a default route.
So was this at the upper key? Do a get forwarding again. And this time, we now
have our default route with the next top of 192 168.1.1.
So now we have that default route. The other thing I'd like to do here is to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now we have that default route. The other thing I'd like to do here is to
get gateways again.
And I'd like to document on our topology what the actual UUID is and VRF for
our distributed router tier zero gateway zero router.
And that way, if we ever need to refer to either the VRF or the UUID, we'll
have it documented.
So the distributed router for gateway zero, our tier zero gateway, begins with
zero four, a whole bunch of additional characters, and it ends up in bed.
Maybe it was tired. Anyway, that's a convenient way of remembering that's the U WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Maybe it was tired. Anyway, that's a convenient way of remembering that's the U
UID for gateway zero and in edge one, all that information regarding that DR is
being kept in the VRF called VRF number one.
And we just set up a default route on our tier zero gateway that said, "Hey, if
you need to forward packet, you don't have a more specific route in your
routing table.
Use the next top over here at this device at dot one." And this is the 192 168
10 network, the 24-root mask, and my little gateway slash firewall router thing
is right here at dot one.
So there's the segment and there's my physical appliance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So there's the segment and there's my physical appliance.