All right, so our first step is just to confirm our existing NSX topology.
And what we're going for is the topology that looks like this.
All right, so here in the NSX manager, which is at .21, here on my management
network 192.168.1,
let's check out our topology.
Let's go ahead and make sure all of our nodes are up so we click here on system
.
And then if we expand fabric on the left and go down to hosts,
and let me collapse the left-hand side.
Here, it gives us a little more room and here is our cluster.
So those two nodes, ESX I1 and 2 look like they are up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So those two nodes, ESX I1 and 2 look like they are up.
Here it shows for NSX configuration mismatched,
just because they are both using a custom static IP address.
And they're not actually using the template that's applied for the whole
cluster.
But they do show us up, so that's good.
Also, let me go ahead and select both of them and click here on actions.
I just want to confirm they are both supporting all the transport zones that we
're using.
So click here on manage transport zones for ESX I1 and 2.
And currently it's just supporting the red overlay transport zone.
So I'm going to go ahead and add the VLAN backed transport zone as well, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm going to go ahead and add the VLAN backed transport zone as well,
because when I was setting this up earlier, the advanced load balancer had a
huge problem
because the hosts in the cluster didn't support all the transport zones
involved.
So I'm going to make sure that the edge nodes and the host transport nodes both
support these two transport zones.
The VLAN transport zone and the overlay transport zone for lab 3 red.
So these are the two hosts. We'll click on save there.
That looks good.
And then we'll go back on the left-hand side, go down to nodes for edge nodes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll go back on the left-hand side, go down to nodes for edge nodes.
And here for the edge nodes, I'll go ahead and select both of them,
click on actions and from the dropdown, click on manage transport zones,
and they currently support both of them.
Okay, that looks great.
So we'll click on cancel there, no changes.
So we've just confirmed that the two host transport nodes and the two edge
nodes are up and active
and ready to go inside of our NSX environment.
So next, let me check on the network address translation here off the T1 right
gateway
between the 10-103 network and the 192-168-1 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
between the 10-103 network and the 192-168-1 network.
Because I want to make sure that when the advanced load balancer is
communicating with the vCenter
or the NSX manager, I want to make sure that these two devices have a proper
route getting back.
And so if I make this device look like it's coming from the 192-168-1 network
address base with the NAT,
that'll solve that problem.
So let's check out NAT for the tier 1 right gateway.
So to do that, we'll go to the networking tab here in the NSX manager on the
left-hand side.
We'll click on NAT under network services.
And then from the dropdown, we'll go ahead and choose our tier 1 right gateway, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then from the dropdown, we'll go ahead and choose our tier 1 right gateway,
that one right there.
So as far as the NAT is concerned, it's set up as reflexive NAT between 10-10-
3015,
which will be the IP address for our load balancer and mapped out to 192-168-1
15 on the other side there.
Fantastic.
So the NAT is in place just for the benefit of communicating between the
advanced load balancer
and the vCenter and the NSX manager.
So next, let's confirm that we have both of the gateways in place, the tier 1
left and the tier 1 right.
So one way of doing that would be to go to the networking tab up on top and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So one way of doing that would be to go to the networking tab up on top and
then go to network topology.
And that would be a quick way of seeing it.
So here I zoomed in a little bit.
Here's T1 left, this one right here.
And it has a connection to external VLAN 5 and also external VLAN 6.
And it also has an overlay segment connected to the 101 right here, the SEG 101
.
And also not shown on my diagram, but it also has a connection here to SEG 102,
which we won't be using for the demo, but it's there if we need it.
So that looks good for T1 left.
Let's also just take a look at T1 right. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's also just take a look at T1 right.
So here is the T1 right, which is connected to the 192-168-1 network, which it
is.
So I'm using .22 on the interface on this tier 1 right gateway.
And then it's also connected to the SEG 103 ALB management right here using the
IP address 10.103.0.1.
at 1.
[BLANK_AUDIO]