So our very first step is to verify our existing topology here in NSX
and also do a little bit of cleanup from the previous NSX cloud
that we implemented as part of the advanced load balancer in the previous skill
.
So for the cleanup, let's start here at the controller for the advanced load
balancer.
So here is our topology down here in the bottom right hand corner,
just for reference and we're currently at the controller for the advanced load
balancer.
So with the applications tab selected here and the dashboard,
currently we have no virtual services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
currently we have no virtual services.
I must have deleted that after the last skill, no problem.
So just to confirm if we go to virtual service VIPs or stuff in there,
no pools of servers, no pool groups, and if we go over here to infrastructure
on the left,
we have three services engines that are currently deployed.
And let's go ahead and under cloud resources, expand that and say,
you know what, for those service engines, and let's also do a drop down and
grab our old cloud there.
Let's just go ahead and delete them.
So just select them all, say delete, and what that will do is in conjunction
with vCenter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with vCenter,
vCenter just got rid of them.
So if we go back to vCenter, those are gone.
It immediately deleted those.
So back to the controller, let's click on clouds, and there's the default cloud
.
There's our NSX cloud.
We'll go ahead and let's delete that and give that a moment to refresh.
So now we're just back to the default and if good to cloud resources,
all of this should be empty.
So no service engines, no service engine groups, no networks.
We have the default service engine group.
We have no networks.
Fantastic.
I also want to take a moment and just verify that in our NSX topology, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I also want to take a moment and just verify that in our NSX topology,
that we currently have connectivity from the tier one left gateway to the 1050
network
and also the 1060 network, because we did not use either of those VLAN back
segments
in our previous skill.
So I just want to take a look real quick and make sure they're up and ready.
So let's go to the NSX manager to verify that.
So here is the NSX manager.
We click on networking.
Let's go down to segments.
And so here is VLAN 5.
There is VLAN 6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There is VLAN 6.
That looks good.
And there is the external network 192, which is not using any VLAN tagging.
So that's why it has a zero there for the VLAN.
But still from the perspective of T1, right, it's an extremely connected
network.
And this segment right here is the segment that our tier zero gateway is
connected
up to the external router.
So that's VLAN 23 up there.
And we took a peek at our network topology.
Let's do that next.
And here we have our T1 left.
And here we have our connections to VLAN 5 and VLAN 6.
And we're using the IP address of 10501 for the VLAN 5 connection and 10601 for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we're using the IP address of 10501 for the VLAN 5 connection and 10601 for
our VLAN 6 connection.
So also I just want to go to my top of rack switch just for a moment
and just validate that I can ping both those addresses from my top of rack
switch,
just to confirm that we really do have access through those VLANs
to those IP addresses.
So here's my top of rack switch.
Let's do a ping to 10501.
And that is looking good.
And let's also do a ping to 106.0.1.
And that's looking good.
Great, great, great. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I just want to validate that we really did have that connectivity in place.
Because if we want to support servers that are on VLAN 5,
we need to make sure that this T1 left really is connected to VLAN 5 right here
,
which it is also on this top of rack switch.
I am providing DHCP services from this top of rack switch to both VLAN 5 and V
LAN 6.
So if we did a show IP DHCP pool on this top of rack switch and hit the space
bar a few times.
So here we have a pool for VLAN 5 and we have yet another pool for VLAN 6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here we have a pool for VLAN 5 and we have yet another pool for VLAN 6.
And that looks great.
So even though the servers here on VLAN 5 are probably not going to be using
DHCP
to get an IP address because they're statically configured,
our service engines, we are going to use DHCP to dynamically assign them an IP
address here
on the 1060 subnet.
And when we do, we should be able to come back to this DHCP server,
which in this case is my top of rack switch, and just validate that they did
get an IP address.
And then the control and management plane between the controller and the
service engines WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
service engines
would be from the controller who's over here on the 10103 address space.
And that traffic would be routed through our NSX environment over to the 10.6.0
network,
which is VLAN 6.
So I also want to take just a moment and confirm in my vCenter environment
that we still have our content library ready to go because we're going to need
that as well.
So here on the vSphere client, let's use the hamburger menu at the top left and
click on content
libraries. And sure enough, there's our content library right there.
So if we open it up, currently there is nothing in it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we open it up, currently there is nothing in it.
So once we create the new cloud and create a virtual service,
once again, the controller is going to go ahead and start populating the
content library with the
template. And then from that template, it can start deploying these service
engines.
Also, one last thing I want to validate at the controller, I just want to
validate that I still
have the credentials in place that we can use when we create the new cloud to
log in and connect
to vCenter and also to the NSX manager. So back here at the controller, let's
go to the administration
tab up on top. And on the left, we'll go down under user credentials and click WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
tab up on top. And on the left, we'll go down under user credentials and click
on user credentials
there. And sure enough, we have our credentials we can use for vCenter and that
vCenter is at dot 35
on my management network here. And we can use the credentials here for the NSX
manager at dot 21.
And those are good to go. So now that we've done the cleanup, we're now in
great striking position
to implement our brand new cloud connector using the advanced load balancer
inside of our NSX
environment. So I'll see you in the next video as we continue this journey
together.
[BLANK_AUDIO]