So for our deployment,
we should also just take a moment
and verify a couple of things.
Number one, if we are gonna be using Uplink three
and VLAN 103 for Edge-1 and Uplink three
and VLAN 104 as the transport VLAN, we wanna make sure
that we have Uplink profiles currently in place,
and if we don't, we'd wanna go ahead and create them.
So we'd create an Uplink profile that says
"Hey, please use the VLAN 103 and one for 104".
And we'd also specify in those same Uplink profiles
that we wanna use Uplink three.
So for Edge-1, that'll be Uplink three on Edge-A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for Edge-1, that'll be Uplink three on Edge-A,
and for Edge-2, that'd be Uplink three
over here on ESXI-B.
And then over on the Transport Network, we'd also be wise
to take a moment just to verify
that we have those existing VLANs
and also that we have the routing capability
between the 33 network and the 44 network space.
Because if they have to route between each other,
we wanna make sure we have all those routing services on the
physical network provided by, or through
our top of rack switches.
So to give us a little bias towards success,
let's take a moment right now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's take a moment right now
and verify some of those infrastructure components
and make sure that they're in place.
So let's start with the infrastructure.
This is gonna represent our top of rack switch.
And let's go ahead and just verify
with the Cisco Catalyst switch,
which happens to be a multi-layer switch,
so it can do layer two switching and also routing.
So let's do a show VLAN brief.
There is VLAN 103
and VLAN 104.
They both exist.
So let's also do a show IP interface brief.
Then I'm gonna use a pipe symbol,
say please exclude in the output anything that has the word WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
say please exclude in the output anything that has the word
or the string of text U-N-A-S-S-I
for unassigned and press enter.
And here are logical layer three interfaces.
So I've got routing capabilities
with an IP address
in VLAN 103 of 33, 33, 33.1,
and a VLAN 104
of 44, 44, 44.1.
So if we do a show IP route, I've got routing capability
between those two network address spaces.
So there's my route for the 33 et cetera network.
And here's my route for the 44 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And here's my route for the 44 network.
And on this multilayer switch, it is directly connected
to both networks via its VLAN interfaces.
So I just wanna verify that we have the physical components
ready to go to support our Edge nodes.
So this top of rack switch has not only the VLANs
but also has the routing for the IP subnets
associated with those VLANs.
And I've also got, I believe, DHCP services set up should we
choose to use those as well.
So if we do a show IP DHCP pool and press enter,
I've got a pool for the 33 address base right there, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I've got a pool for the 33 address base right there,
and another one for the 44 address base.
So in the event for our Edge nodes, if we wanna say
"Hey, use a DHCP assigned address",
we have that option as well.
However, for our purposes,
we're gonna hard code the tunnel endpoint addresses
as 3 3, 3 3, 3 3, 3 3
for Edge-1
and 44, 44, 44, 44
for Edge-2.
And that way when we see those IP address,
we'll know exactly what they are.
Next, let's head over to the NSX manager to verify
that we have Uplink profiles that we can use
for Edge-1 and Edge-2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for Edge-1 and Edge-2.
So here in the NSX manager, let's go to the system tab.
And under fabric on the left, we're gonna go down
to profiles.
And so here's a bunch of Uplink profiles
that I made previously and we can just pick one
or two of those and verify they're
correct before we use them.
So for Edge-1 it's gonna be using Uplink three
on its respective host that's running it
and it's gonna use on that Uplink VLAN 103.
So that looks like a winner right there.
If we just click on it to confirm. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If we just click on it to confirm.
So this Uplink profile called V103 vmnic three says
use 103 for the transport VLAN,
and if we scroll down, we're using vmnic three.
Now here it's just a label in NSX,
but we'll wanna map that over
to the corresponding vmnic three on the respective host.
So here for Edge-2 we're also gonna use Uplink three
on its respective host, but we're gonna be using VLAN 104.
So Uplink three right here and VLAN 104.
So here in NSX manager, let's take a peek at these. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here in NSX manager, let's take a peek at these.
We're looking for VLAN 104 and vmnic three,
and that looks, based on the title, like it might be it.
So if we click on it to confirm, sure enough,
that's using Transport VLAN 104.
And the label regarding this Uplink profile says
vmnic three.
So we'd wanna map that correctly, this label called
vmnic three over to the associated Uplink
on the distributed switch that leads out to
vmnic three physically.
In fact, to make that a little more clear, let's go ahead
and edit this Uplink profile.
And instead of calling the Uplink vmnic three, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And instead of calling the Uplink vmnic three,
I'll go ahead and double click here to edit it.
Let's go ahead and call it vmnic dash T-R-E-S,
for three in Espanol.
And that way when we see it,
we'll know exactly where that came from.
It came from this Uplink profile,
and then we'll map it to the appropriate Uplink
over on the distributed switch.
So we'll click on save.
So we verified that we not only have the appropriate
VLANs available on the physical transport network,
but we also verified that we have appropriate
Uplink profiles that we can use.
This one right here for Edge-1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This one right here for Edge-1
and this one right here for Edge-2.
So to deploy an Edge node it's super easy
to do right here from the NSX manager.
We simply go to system where we currently are,
and then on the left we simply go to nodes.
So as time goes on, they may rearrange things a little bit,
but at the moment with the current flavor of NSX,
it is right here.
Now, currently it shows that we have an edge node
called Edge-1 already in place, and I'll tell you why.
This takes about an hour to deploy an Edge node
and part of the time there is gonna deploy the full VM on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and part of the time there is gonna deploy the full VM on
the ESXI host, it's going to initialize that Edge node
and then once it's up and running,
it takes a little longer to get fully baked.
So from start to finish, it probably takes somewhere
between 45 minutes and an hour to deploy an Edge.
So what I did earlier is I deployed this Edge,
ran an errand, and then came back.
And so Edge-1 is already in place, but have no fear,
what we get to do is we're gonna go
through the exact same steps, but for Edge-2,
and that way as we wait for Edge-2 to finish,
we can take the steps of validating our existing Edge node WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we can take the steps of validating our existing Edge node
that's already in place.
So let's go ahead and deploy Edge-2.
And lemme go ahead and arrow this to the left a little bit
so we can have a little more real estate right here.
And let's click on add Edge node and let's add Edge-2.
And just as a reminder about the details for that,
Edge-2 is gonna have the
management address of 192, 168, 1.192.
We're gonna use a static configured IP address
of 44, et cetera for the tunnel endpoint,
we'll use Uplink three over here on ESXIB
and we'll use VLAN 104 for the transport VLAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we'll use VLAN 104 for the transport VLAN.
So with that in mind, let's go back
and do the deployment of Edge-2.
So we'll go ahead and call this Edge-2,
and then it's asking for a fully qualified domain name.
So let me also verify I've got that set up in DNS.
So here is a command prompt,
and I'm gonna be using my lab DNS server,
which is at dot 100,
so we'll go ahead and do an NS lookup.
And there we go.
We're using the DNS server, the same one I'm gonna be
telling this Edge node to use.
And lemme do a lookup for Edge-2.OGIT.local,
and press enter.
And sure enough, it does have a record there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And sure enough, it does have a record there.
And let's also do a reverse lookup
by putting in net address 192.168.1.192 and pressing enter.
So both forward and reverse look-ups are working.
That's fantastic.
So that's the name we're gonna use: Edge-2.OGIT.Local.
So I'm gonna highlight that, press enter to copy it
to my buffer and then go back here,
right click and simply paste it in.
Next, it's asking this for the form factor.
This is a question about how many resources do we wanna
throw at this Edge VM?
And so I'm gonna go ahead and choose medium,
which will chew up four CPUs and eight gigabytes of RAM. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which will chew up four CPUs and eight gigabytes of RAM.
But just be aware, especially in the lab environment,
that by default it's gonna take all the RAM that you give it
as a guarantee, meaning there's gonna be a reservation.
So if we scroll down a little bit,
instead of saying a hundred percent memory reservation,
I'm gonna cut that back to 50.
And that way if push comes to shove,
I can still bring up this Edge VM,
even if there isn't a full quantity of RAM
that I can allocate to it based on
other resources needing that memory.
So I'm gonna just set it up to reserve 50% of that RAM, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm gonna just set it up to reserve 50% of that RAM,
but I'm gonna go for the medium size
and click on "next".
I'll go ahead and supply a password for admin
and also for root.
I'm also gonna say I want to allow SSH logins.
So those passwords have been supplied and confirmed.
We'll scroll down and I'm not too worried about,
for my lab, the audit credentials,
so I'm gonna leave those blank and click on "next".
Now it's asking me about where do you want
to deploy this VM?
So based on our plan, Edge-2 is gonna be placed on ESXIB,
which is under the control of vCenter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is under the control of vCenter,
the vCenter that we identified in NSX manager
as our vCenter.
And then as far as which cluster is that ESXI host in,
it's in the host transport nodes.
And then I don't have a specific resource pool
that I wanna put 'em in, but I do wanna specify the host.
And so I am gonna choose the host
and we're gonna choose ESXIB based on our plan.
And then for the data store for this little VM,
I'm gonna choose the local data store on ESXIB,
and then we'll click on "next".
Now it's asking about the management interface for Edge-2.
So let's take a look at our plan once again. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's take a look at our plan once again.
So in our plan we wanna use 192, 168, 1.192
with a 24 bit mask as the management IP address.
So we'll put that in next.
So we'll click here to say that we want
to have a statically assigned IP address,
and we'll use the address of 192.168.1.1.92
with a 24 bit mask.
And it wants the default gateway,
so in my lab environment on my management network,
it is 192.168.1.1.
And now it's asking me for which interface do we wanna use
for the management network? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for the management network?
So we're gonna select a port group.
So here is a port group that leads off
to my management network.
So I'm gonna choose that for the connection for this VM
to connect to the management network.
And we'll click on "save".
And then for the search domains, I'm in the OGIT.local,
and then the DNS servers can be my
Windows server at 192.168.1.100.
And the same Windows server at 192.168.1.100
is acting as a network time protocol server, as well.
And then down here it's asking if we want to enable UPT mode WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then down here it's asking if we want to enable UPT mode
and I don't have the Smartnicks to support that,
so I'm gonna go ahead and leave that off,
and then we'll click on "next" to continue.
So NSX has been through several iterations
and several versions like two and two x and three
and three x, and now we're at four.
And currently we're at 4.1.1 as of this recording.
So as far as the Edge Switch name,
we don't have to deal with that anymore,
we can just leave that as the default.
And then now we're gonna specify which transport zones we
want this Edge to be able to support.
So again, the transport zone is like the range of
how far a segment can go.
So currently, everywhere else, our host transport nodes WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So currently, everywhere else, our host transport nodes
and also Edge-1, which I already deployed, I specified
that I just wanna support at the moment one transport zone,
and that's the one we created a few skills go,
that's our AB overlay transport zone.
And so we can add more later,
but at the moment I just want this one Edge, Edge-2
to be able to support any segments in
that overlay transport zone.
And next it's asking us about the Uplink profile.
And so we already confirmed earlier
that we have an Uplink profile that we can use.
And based on our plan, we want the Uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And based on our plan, we want the Uplink profile
that's gonna support Uplink three here on
ESXIB once it gets deployed, and VLAN 104.
So we'll grab the appropriate Uplink profile
that does exactly that.
So we'll use the dropdown and we want VLAN 104
and Uplink three, and so we're gonna grab
that one right there.
So there's our Uplink profile
and as a result of that, it's now asking us
to map over the label that we put associated
with that Uplink profile.
There it is, vmnic-tres, and then map it over
to an actual port group on a distributed switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to an actual port group on a distributed switch.
So currently on the distributed switch,
I currently have a port group called this: "DPG leads
to vmnic3".
In fact, let's pause for just a moment
and make a road trip over to the vSphere Client.
And let me show you that port group.
So here on the vSphere Client,
if we go to the network tab here,
and then we open up this DS for NSX,
I have this port group.
Notice there's no end there,
this is just a normal distributed switch port group
that's available to both ESXIA and B.
And if you look at the properties of this, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if you look at the properties of this,
right click and click on "edit settings",
and then I'll take you down to teaming and failover.
So as part of this pork group called "DPG leads
to vmnic3", the only active Uplink we're using
is vmnic three.
So you certainly could add in additional fault tolerance
with standby links, or if you wanna have two taps,
you could go ahead and do two active Uplinks,
based on the Uplink profile you're using.
But I just wanna verify and show you
that this port group called "DPG leads to vmnic3"
is only using the Uplink vmnic three on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is only using the Uplink vmnic three on
the respective host that it's currently running on.
So I'll click on "cancel".
We could also go ahead and click on the parent switch here,
this distributed switch,
and click on "configure" and go to "topology",
and that would also show us the story there.
So this port group right here only uses vmnic three,
and that's what this represents.
And there's Edge-1 that I deployed earlier today
and we're about to deploy Edge-2,
which will also be using this port group
for its transport network.
Except, unlike Edge-1, Edge-2 is gonna be using VLAN 104 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Except, unlike Edge-1, Edge-2 is gonna be using VLAN 104
and Edge-1 is using VLAN 103
as it communicates over the transport network.
And again, you can use the same exact VLAN if you want to,
the same exact subnet,
but for the purpose of education and learning,
I thought having completely separate
IP addresses and separate ranges is gonna make it more clear
about which end of the tunnel goes where.
Alright, so back at the NSX deployment of Edge-2,
we're gonna choose "DPG leads to vmnic3"
as the port group that uses vmnic three that we wanna use.
We'll click on "save" there.
And now it's asking us about the assignment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And now it's asking us about the assignment
of the IP address for the tunnel endpoint.
So we're gonna go ahead and use a static IP list
and then we'll scroll down and go ahead and put that in.
And that's gonna be 44.44.44.44.
And the default gateway is my top of rack switch
or the top of rack infrastructure,
which is 44.44.44.1,
we looked at that earlier, verified that was in place.
And we're using a 24 bit mask,
so we'll put that in, as well.
And I think we have specified all the details here
that we need to for Edge-2.
So we'll click on "finish" and it is on its way. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click on "finish" and it is on its way.
So lemme manage the columns a little bit right here.
Lemme go ahead and remove ID for a moment
and the deployment type,
and the management IP address, I'll remove.
And the host that's running on, I'll remove.
And I'll leave everything else
and that'll make it just a little bit easier to read.
So this Edge-2, which is now being deployed, again,
this takes somewhere between 45 minutes
and an hour to complete.
So here on the vSphere Client,
if we look at the tasks, it's now doing the deployment of
that OVF template, effectively Edge-2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that OVF template, effectively Edge-2,
and it's deploying it now over on ESXIB.
So if we went over to the VM and templates view,
down here we have Edge-1 on it,
that's the one I deployed earlier,
and I'm just gonna drag and drop that
into the folder called "Edge Node VMs" right there
and then Edge-2, I'm not gonna try to move that
until it is completely deployed.
So I'm gonna go ahead and give
that deployment probably another 45 minutes to an hour
to go ahead and finish.