All right, so based on our game plan, I want to use VLAN 23 as my edge segment
and connect
over here to this external router, which is also on VLAN 23, and change my
addressing
scheme on that external segment to be 2312 and .61 for edge one and .62 for
edge two.
So let's head over to the NSX manager and update our configuration regarding
our topology
and gateway zero.
So we'll start off by going to networking, going down to our tier zero gateway
here in
the NSX manager, and I currently over here have a status of down and that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the NSX manager, and I currently over here have a status of down and that's
probably
because I made a few changes in the background.
So let's clean this all up and get the new external segment from VLAN 23.
So to do that, we're going to click on the three dots for our tier zero, click
on edit,
and first of all, I'm going to take off this HA virtual IP address because it's
currently
using the address of 192.1 state 160, which is not going to be correct for our
new subnet.
So I go ahead and delete that and then click on apply.
And now let's go through the step by step.
So let me click on save before we continue. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let me click on save before we continue.
So here I've got two interfaces.
We'll go ahead and click on to there and these two are on the wrong subnets.
And so we'll go ahead and let's go ahead and delete both of those.
So delete that first one, click on delete, then I'll go ahead and click on
refresh,
give me a nice clean view.
We'll delete the second interface there, delete perfect, and then we'll click
on refresh.
Great, great, great.
It'll click on close and scroll down, click on close.
And now we no longer have a virtual interface address in the wrong subnet and
we also have
no interfaces.
So if we want to connect this gateway to the 23 subnet for its external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we want to connect this gateway to the 23 subnet for its external
connection to the
next hop router, we need to have that segment.
So let's go to segments.
So under networking and segments, and there's our current segment, if we expand
that, it's
currently using VLAN zero, no tagging at all.
So we could just edit this or we could just create a new, in fact, let's just
delete the
old one, we'll click on delete, get rid of it, we're not using it anymore.
And let's create a new one.
So we'll click refresh there and there's our two existing segments.
Let's create a VLAN back segment for VLAN 23.
So we'll click on add segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click on add segment.
I'm going to call this VLAN 23 and then just for grands, put 23.1.2.
So when I see it, I'll not exactly where that segment goes and the IP address
associated
with it.
And then I'm not going to specify right here a connected gateway because once
we create
the segment and we specify the transport zone, which is going to be our VLAN
backed transport
zone.
And also right here with a little asterisk says, hey, specify which VLAN this
is going to
support.
So I'm going to go ahead and support just the VLAN 23.
And so now that we have this new VLAN backed segment without a gateway
connected, we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
connected, we'll
scroll down, we'll click on save and then click on no because we're done config
uring
right here that segment.
Then we'll go to our gateway zero and say, hey, let's go ahead and have you
connect to
this segment, VLAN 23, and we'll connect via edge one and edge two.
So to do that, we'll click here on our tier zero gateways, expand this.
And we'll click on the three dots here, click on edit and let's scroll down and
let's go
down to interfaces.
So for external and service interfaces, we'll click on set and we'll click on
add interface.
And for the first one, I'll say it's dot 61 edge one VLAN 23 just to remind WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the first one, I'll say it's dot 61 edge one VLAN 23 just to remind
myself of
what it's for.
So that's going to be this logical interface.
I'm going to copy that because we're going to use that very similar syntax
again.
And then for the actual address of this logical interface, it's going to be 23.
1.2.61 based
on our plan with a 24-bit mask.
And then the segment we're going to connect to is our VLAN 23 segment we just
created.
And then for the edge node, we'll go ahead and choose edge one and that looks
good.
So we'll go ahead and scroll down, click on save, and then we'll click on add WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll go ahead and scroll down, click on save, and then we'll click on add
interface.
We'll do it again.
I'll paste in that name, but this one will be dot 62 and it'll be on edge two.
So then I'll specify for this IP address, we're going to be 23.1.2.62 with a 24
-bit
mask, and for the segment we're connecting to is that same external segment V
LAN 23.
And then for the edge node, we're going to use for that.
We're going to go ahead and use edge two just like that.
That all looks good.
We'll scroll down, click on save, and click on close.
And then before we're done here, while we're sitting here at Gateway Zero, let WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then before we're done here, while we're sitting here at Gateway Zero, let
's also make
sure our OSPF is configured correctly.
So for the interfaces that are set for OSPF, we have none because we deleted
the other
two interfaces on that 192 network.
So let's click on set here and let's click configure interface for OSPF.
And let's choose the interface on edge one.
We'll put it in area zero.
We'll leave all the other defaults, click on save.
And then we'll do it again by clicking on configure interface.
We'll go ahead and add that second interface.
Also put it on area zero and click on save.
So now we have these two interfaces enabled for OSPF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now we have these two interfaces enabled for OSPF.
Click on refresh over there.
Click on close, scroll down, and then we'll click on close editing.
And then we'll just click on refresh here.
So I've already got the OSPF configured on a little external router.
And that's this guy right here.
So if that is configured with OSPF and we just configured the two interfaces
here on
tier zero and we enabled OSPF, we should be able to see that OSPF adjacency
right here.
We can see that from the external router or in our case because we're right
here at
the tier zero device, we could go ahead and look at the OSPF neighbors here as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the tier zero device, we could go ahead and look at the OSPF neighbors here as
well.
So to do that, I also see I have a status of down over here.
We'll take a look at that in just a moment.
So if we expand our tier zero gateway, scroll down and then in the OSPF section
expanded
if it's not already expanded.
So make sure that's expanded.
And then down here under OSPF neighbors, we'll click on view and that looks
pretty good.
So this is edge one, the first two.
First one we're pairing with the edge router and the second one here, we're
pairing with
edge two and then from edge two's perspective, we're pairing with the edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
edge two and then from edge two's perspective, we're pairing with the edge
router and then
this one we're pairing over with edge one.
So we're on the full state with the external router and we're in the two way
state with
each other, meaning edge one and edge two, which looks good.
Oh, this still says down and it says I have an alarm link click on the alarm
and this
shows me for alarms, I have no open alarms.
Hmm.
All right.
So maybe we just need the screen to refresh.
I'll click refresh here.
Oh, that looks better, much better.
And then just to double check, let's go ahead and head over to one of our edge
nodes.
In fact, let's take a look at which one's active.
So good in network topology, we'll double click on gateway zero and here we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So good in network topology, we'll double click on gateway zero and here we
have edge
one that's active.
So let's head over to edge one and take a look at the routing tables for our
distributed
routing and service route environment from the perspective of edge one.
So here is edge one, let's do a gate gateways.
So here is our services router now in VRF six, so we'll type in VRF six.
So now based on our prompt, we are in the services router specifically in VRF
six, fantastic.
And from here, let's do a get route and press enter.
Oh, and this looks great.
So we are dynamically learning a default route and that is coming in from our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we are dynamically learning a default route and that is coming in from our
edge router
at 23.1.2.1.
And there's the default route that it's advertising to us.
Also, we do a get interfaces here on this router.
In fact, let me go ahead and do that again with a pipe and a more.
So we can do one page at a time.
So here in VRF six, I've got some interfaces regarding black hole and CPUs.
I've got an interface here on the back plane from the services router.
If we press enter a few times, here is my logical interface on edge one that
connects
to VLAN 23 with its respective IP address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to VLAN 23 with its respective IP address.
If we press enter a few more times.
But edge one is the active router.
And that's why that's showing up here.
And then I also have a loop back address.
Now in this output, it's now moved on to VRF number one, which is the
distributed router
for tier zero gateway.
So if we scroll down, here's one of our router to router connections between
the tier zero
and tier one, we continue to go down.
Here's our second interface between us and based on the name here, this is
going to gateway
B, fantastic.
And here we have the IP address that we're using on the subnet that
communicates between WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
communicates between
us, in this case, the DR over to the SR.
So the other address on the subnet 169.24.0.2, that was on the services router
port.
So whenever they need to logically communicate back and forth between each
other, this is
the IP subnet they're going to use to do exactly that.
Then as we continue to scroll down, we have one regarding multicast traffic.
And that is it.
So I had Q2 quit.
So once again, if we do a get route, that's going to show us our routing table.
We get us to a get forwarding.
And so we should be able to ping this external router from this VRF right here.
So we type in ping to 23.1.2.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we type in ping to 23.1.2.1.
Oh, that's a very good sign, fantastic.
And if this is the next top address for our service provider, and if we're
using it as
our default route, which we are based on this right here, we should be able to
ping resources
out on the internet.
Let's go into a ping 8, 8, 8, 8, 8.
That looks great.
And just to make sure it's not going somewhere weird, let's go into a trace
route to 8, 8,
8, 8, 8, and press enter.
Let me go ahead and source it from the correct interface here.
So let me go into a trace route space.
I'll go into a trace route to 8, 8, 8, 8, 8, and a space question mark.
I'll say source. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll say source.
I want to source this from my edge one IP address, which is 23.1.2.61.
And we'll probably get some better results by sourcing it from the correct
interface.
So this is showing us the path through the internet getting out to a Google
server.
Then we have the response coming back from 8, 8, 8, 8.
So I just want to verify from our edge that we are really going to the internet
.
Also notice here on my second hop, I'm going back through my management network
.
And that's just for the benefit of me being able to do NAT again.
So I can actually use the 23 address space here in my lab environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I can actually use the 23 address space here in my lab environment.
So from the internet, it doesn't look like I'm really coming from the 23
network.
It looks like I'm coming from whatever I'm doing the NAT on at this hop in the
path right
here.
Awesome.
And also just for grants, let me also add to our tier zero gateway.
Let me add the virtual IP address.
So I'm going to edit our tier zero gateway once again by clicking on three dots
for our
tier zero gateway, clicking on edit, and then for the HAVAP, let's go ahead and
click on
add and let's use 23.1.2.60.
Select that 24-bit mask, and then we'll select the 200 faces on edge one and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Select that 24-bit mask, and then we'll select the 200 faces on edge one and
edge two respectively.
To support that, click on add, click on apply, and click on save.
And then finally, we'll scroll down and click on close editing.
And then we can verify that from the command lane as well.
So back in our VRF for our services router, and we're looking for something
that ends in
60.
We can just go ahead and do a pipe and say find 60.
And then any of the lines in the output that have the number 60 in it, those
are the ones
that will be shown to the screen, and there it is right there.
So on edge one, it has this IP address 23-1-2-61, but we're also supporting WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So on edge one, it has this IP address 23-1-2-61, but we're also supporting
this virtual
IP address of 23.1.2.60.
And again, that's on our services router, tier zero gateway.
And the only reason that output is showing up here is because it just so
happened in
the UUID to also have a 60 in it, which is just the luck of the draw here.
It wasn't actually searching for the UUID, uh, scratch set.
So here in the output, it has a 23.1.2-60 address and this is on edge one.
It also has the actual IP address on edge one of dot 60.
So because edge one is the active gateway, that's why it also shows that IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So because edge one is the active gateway, that's why it also shows that IP
address right
here as well.
All right.
So we are in great striking position because we've just updated our topology.
We've also verified that the gateway zero has access to the public internet.
Fantastic.
So in our next video, let's deploy a couple of additional VMs that we can use
for testing.
I'll see you in the next video in just a minute.