So in this video, let's demonstrate putting a quick
topology together, leveraging our nested environment.
So let's create a tier zero gateway.
And let's go ahead and connect a segment there.
And let's use 10.10.0.0, they slash 24.
For the little VM right there, we'll use .1
for the logical interface connected to the 1010.0 segment
by our tier zero gateway.
And let's also leverage our little VioRouter right here,
which is on the 23.1.2 network.
So this is VLAN 23.
And its IP addresses .1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And its IP addresses .1.
So on our tier zero gateway for this interface right here,
let's use a virtual IP address of .11.
And for edge one, let's go ahead and use .12.
And for edge two, let's use .13 with the virtual address
again being here at .11.
Then we'll also make sure we have a default route that says,
hey, Mr. Tier zero gateway, if you don't know how to get out
to the internet or anywhere else for that matter,
go ahead and forward it to the next top of 23.1.2.1.
And then it'll be up for this router
to continue forwarding it on its way.
Let's also set up network address translation.
So the main clients from the 1010 address space WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the main clients from the 1010 address space
are forwarding traffic in this direction
that this tier zero gateway will net it over.
And let's use our virtual IP address again of 23.1.2.11.
And that way this little VioRouter doesn't have to be trained
on how to reach back to the 1010 network
because everything gets going through the T zero gateway
coming from the 1010 zero network.
Well, look like it's coming from 23.1.2.11 due to net.
So this will be a good review by the way
of many of the concepts that we've looked at up to this point.
So for the demonstration, we'll do a speed round WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for the demonstration, we'll do a speed round
of implementing all of this
to get connectivity from this little VM here
out to the internet.
And then once we're done
and we've verified that client can get up to the internet,
I'll then walk you through the graceful shutdown
of our nested environment, including the use of snapshots.
All right, so let's head over to the NSX manager
and let's get to work.
So here we are at the NSX manager
and although we're gonna go through this really quickly,
if you want greater detail on anything
that we're about to implement here,
please check out the respective previous skills
as part of this course here at CBT Nuggets.
So let's start off with the networking tab selected WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's start off with the networking tab selected
and let's create our external segment that we're gonna need
to go ahead and connect to that VLAN 23.
So we'll click on add segment, it's gonna be VLAN backed.
So we'll go ahead and call this VLAN 23.
And for the transport zone,
we'll use our default VLAN backed transport zone
and we'll put VLAN 23 and we'll click on save and boom.
We now have this beautiful logical VLAN backed segment
for VLAN 23.
That looks good.
Next, let's go ahead and let's create our tier zero gateway
by clicking on tier zero gateway, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
by clicking on tier zero gateway,
clicking on add gateway from the dropdown
will create a tier zero gateway
and we'll call it our T zero gateway
and I'm gonna go ahead and do active standby,
select our edge cluster, which is that one right there
for this lab environment.
And then we'll go ahead and scroll down and click on save
and then we'll say yes, we wanna continue configuring.
So we wanna do a few things.
Number one is we wanna add some interfaces here.
So we'll go down to the interfaces section
and click on set.
We'll click on add interface and we'll say E1 for VLAN 23.
And as a note, I'm gonna go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And as a note, I'm gonna go ahead
and just put in the address of .12 here
to remind myself what I'm doing.
And that's 23.1.2.12, the 24-bit mask.
And the segment we're connecting to
is that external VLAN 23 and we'll use edge one for that.
That looks good.
We'll scroll down, click on save
and we'll do it again for edge two at interface
and that'll be .13.
And then we'll put in the IP address there for edge two
and we add a little space there.
And that's gonna be 23.1.2.13 with a 24-bit mask
and we're gonna use edge two for that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we're gonna use edge two for that.
And we'll specify what segment we're connecting to
and that looks good there.
So we'll click on save and click on close.
All right, so we have two interfaces connected
to external VLAN 23, that VLAN back segment
and let's now set our virtual IP address as well.
We'll click on set at HA/VAP configuration
and we wanna use 23.1.2.11 with a 24-bit mask
and we wanna use the two edge nodes to support that,
edge one and edge two, click on add, click on apply
and click on save.
Also, while we're here, let's go ahead
and add our static route that we're gonna need WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and add our static route that we're gonna need
through our service provider.
So in the routing for static routes,
we'll click on set and click on add static route
and we'll name this default and then we'll put in the syntax
for an IPV for default route, just like that.
And the next top is gonna be 23.1.2.1 and click on add
and click on apply and click on save and click on close.
So far that looks pretty good.
We have our routing in place, we have two interfaces.
So let's go ahead and close editing
and click on network topology just to verify.
So that looks pretty good.
Here we have our gateway and it's two interfaces. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Here we have our gateway and it's two interfaces.
So next let's go ahead and set up our DHCP.
So we'll go to networking profiles, click on DHCP
and add DHCP probe.
Oh wait, we could use this right here.
10-1-0-1, that'll work.
We already have a profile.
Let's go back and use that profile
in combination with our gateway.
So we'll go back to tier zero gateways.
We'll edit properties of our gateway
and we'll go to DHCP config, click on set and say,
yep, we wanna act as a DHCP server with that profile,
apply, save.
So that looks good.
So we'll click on close editing and let's create our segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click on close editing and let's create our segment.
So we'll click on segments, add segment.
We'll call this segment 10 and we'll connect this
to our tier zero gateway right there
and we'll select our overlay transport zone
and give it the IP address of 10.10.0.1,
which will be the IP address that the tier zero gateway
is gonna use for its logical connection to this segment.
So far so good, let's click here on set DHCP config
and we'll say we wanna be a gateway DHCP server.
So it's gonna use the DHCP profile
that's associated with that gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's associated with that gateway
and then we'll put in the range of 10.10.0.1-51
through 10.10.0.200, it'll be more than enough for our 1VM
and let's specify lifetime of 1000 seconds for my lab.
I like doing an artificially low lease time for DHCP
just to confirm that it's not gonna hang on
to a whole bunch of addresses.
If my topology all of a sudden has to change
and for DNS servers we'll specify 8888
that's a DNS service out on the internet from Google,
click on apply and we'll scroll down and click on save WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and let's take a look at our topology.
So we'll click here on network topology.
So there's our segment, there's the gateway.
Oh and we don't have NAT services set up yet.
So to set up our NAT services so we can translate people
coming from the 10.10 address space
as they go to the internet,
let's send the left hand side on our networking
go down to NAT and then we'll use the drop down
to choose our T0 gateway.
So the only gateway we have fantastic,
we'll add a NAT rule and we'll call this SNAT
and the type of address translation we're doing
is source of this translation.
So we'll select SNAT there.
And then for the source IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then for the source IP address
we wanna go ahead and qualify anybody
who has the address of 10.10.anything.
So let's go ahead and do a slash 16 there
and then we'll translate that over to 23.1.2.11
which is the virtual IP address that we set up.
Also, we don't have to use that virtual IP address
but since we already have it,
we're gonna go ahead and use it.
And with that specified, we'll scroll down
and click on save.
All right, that looks good, fantastic.
And let's take a look at our topology.
So here in our topology we have three services,
those are gateway firewall rules, DHCP and NAT. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
those are gateway firewall rules, DHCP and NAT.
Fantastic, let's go ahead and put a VM here
on this segment 10.
So to do that, we're gonna go back to the vSphere client.
So back at the vSphere client
and we're logged on to the OGAIT.lab
Single sign on environment.
Let's go find ourselves a VM.
So let's go down here to my port group for management.
And here I have Mint B, which is a little Linux VM.
So because it's currently in this port group right here
called Lab1 Management Pg,
I'll right click on that port group.
From the dropdown, click on migrate VMs to another network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
From the dropdown, click on migrate VMs to another network
and I'm gonna choose segment 10, click on next
and then choose that VM right there, Mint B
and click on next and finish.
And that is one way to move that Mint B over to that segment.
So there it is right there.
Let's go ahead and select that Mint VM
and we'll power it on.
And while it's powering on,
let's also click right here to launch a remote console.
So if all of that is done correctly,
this little VM here, once it powers on all the way,
this little VM here should use the default gateway
of 10, 10, zero, one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of 10, 10, zero, one.
Should go through the T0 gateway,
who has a default route going through the service provider
router, which are a little BIOS router
and who's gonna forward it out to the internet.
And along the way, just so you know,
in the back end, is doing that a couple of additional times
because I don't really own this address space at 23.1.2,
that's owned by somebody else.
So because I'm using it here in my lab,
I'm doing that a couple times before that traffic
actually goes up to the real internet,
going through my home network.
So now that VM has had a moment to come up,
let's bring it in.
So here is that VM right here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here is that VM right here
and let's just confirm it got an IP address
on this 10.10 address space.
So we can do that with an IF config,
press enter and sure enough, 10, 10, zero, one 51.
That looks great.
Let's do a ping out to www.google.com.
If that works, it confirms that DNS is,
oh, it's not working.
So yeah, the DNS part worked,
but the actual ping traffic did not flow.
Let's go troubleshoot.
So I wanna first verify that that little mint VM
is on the right segment, which it is right there.
Being hosted by ESXIB, that looks great. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Being hosted by ESXIB, that looks great.
And let's go over to the NSX manager
and check our work here.
So here's our tier zero gateway.
So the DHCP part of it worked, that's not a problem.
So let's go to the edge that's acting as the active node
for our external VLAN connectivity and take a look.
So one easy way of finding that would be
to go to network topology right here,
double clicking on our T zero gateway to show us the fabric
and that will show us which node is active.
So it's this edge one that's active.
We'll click on the link there
and that confirms its IP address.
So let's open up an SSH session over to 191 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's open up an SSH session over to 191
and verify some basic connectivity.
All right, so here we are connecting over to edge one.
Let's do a gate gateways.
So here's our services router VRF, that's VRF6.
Let's go in there by typing in VRF6, press enter
and let's do a get route, press enter.
So there's our default route and let's do a ping to 8888
and that's working from the perspective
of our services router.
So what's up with our client?
So back at the NSX manager, let's go back down to NAT WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So back at the NSX manager, let's go back down to NAT
and take a look at this NAT rule
and I'm gonna scroll over to the right a little bit,
click on this icon for stats and yeah, it's being hit.
So that NAT rule is being hit.
We'll click on close and 23.1.2.11 is the translated address
which happens to also be the virtual IP address
I set up for the T zero gateway 23.1.211.
That all looks good.
So the community was ping www.google.com and oh no way.
So now it's working. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now it's working.
(laughs)
So it could have been that we just deployed that T zero
and all the config and all the NAT
and it may have taken just a moment or two
for that configuration to be pushed out to the edge nodes
and synced up and everything happy, happy
because it now seems like that's working like a champ.
So if we hit the up arrow key here,
we ping Google, yeah, that's working now.
So I just didn't give it enough moments
between the time I configured it
and the time I tested it.
So let's open up a browser and here from the browser
let's open up a speed test
and that's looking pretty healthy as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that's looking pretty healthy as well.
All right.
So it was a good exercise in reviewing
some of the basic configurations and connectivity.
As we troubleshot a problem with all boil down to it,
just not being enough time
between the time we configured it
and the time we tested it.
Because literally behind the scenes
I made absolutely no additional changes.
All right.
So now that we've implemented this network topology
in this nested lab environment, in the next video
let me walk you through how to gracefully shut all
of this down and then create snapshots WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of this down and then create snapshots
so we can return to this exact point in time
anytime we need to.