All right, so our game plan is to implement this.
And specifically, the controller is already here.
We're currently logged on to the controller interface,
as we're seeing here on the screen.
And we want the management network for the SEs,
for the service engines to be here on VLAN6.
And because DHCP services are already present,
we can allow them just to get an IP address via DHCP.
So that'll be the management network.
And then as far as the data plane,
for the services engines to do the proxying for,
we are also going to go ahead and include VLAN5. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we are also going to go ahead and include VLAN5.
Because as part of creating the cloud connector,
it's going to ask us, what do you want to use
for a management network?
We're going to say down here, VLAN6.
And what do you want to use for the actual data plane?
And for that, we're going to use VLAN5.
In fact, you know what?
Also, because we need to also include over here,
the 192.168.1 network, and also the 23.1.2 network.
As part of the creation of that cloud,
we should also include that segment and this segment as well.
Because if we don't, we'll have to go back and add those later.
So with that in mind, let's start the process. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So with that in mind, let's start the process.
So to do that here at the interface for the controller,
we're going to click on infrastructure.
And on the left, we're going to click on clouds.
And from here, we have our default cloud.
What we're going to do is create a new cloud.
So we'll go ahead and click on the create button
from the dropdown.
We want a cloud connector to our NSX environment.
So we'll choose NSX cloud.
And then we'll start answering the questions.
So let's call this NSX-cloud-4.
Based on our plan, we'll be using some DHCP services
for the addressing of our service engines down here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for the addressing of our service engines down here.
Let's scroll down for the prefix name.
This is going to be used when those service engines are
created in vSphere.
It'll have the prefix stuck in front of each of the service
engines.
And that way, if you have multiple clouds that are being
created, you can identify based on the prefix, which clouds
those service engines are associated with.
So I'm going to call this NSX-4- prefix.
And that way, when you see this and it has the word prefix in it,
you'll say, oh, that's where it came from.
And as we scroll down, let's go ahead and set the credentials
we can log into the NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we can log into the NSX manager.
So we'll go ahead and click on change credentials.
We'll put in the IP address of our NSX manager, which is .21,
right over here.
So we'll put that in 192.168.1.21.
And then we'll use the dropdown.
And we'll choose the credentials we had set up
from our previous set of videos, which basically
has a username and the password we can use to log on
to the NSX manager.
Now, we'll know very quickly if that worked or not,
meaning we had the right IP address.
And we used the right username and password,
because if it worked, we should be able to continue down here
for the management network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for the management network.
And it should show us everything that the NSX manager knows
about.
So for the NSX manager, if we use the dropdown here,
that's a very good sign.
So it's showing us all of the transport zones
on the NSX manager.
So for the management network, because we want to go ahead
and make the management network over here, a VLAN back
segment, we're going to go ahead for the management network.
And we're going to choose a VLAN-backed transport zone.
So I want to use the lab 3-RED VLAN-TZ, which
is a VLAN-backed transport zone. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is a VLAN-backed transport zone.
And now that we've selected that,
it should be showing us all of the VLAN-backed segments
available in the NSX manager.
And here they are.
So we have external 192.
Nope, we want to put them over here on 6.
So we want external VLAN 6.
So we'll choose that correct external segment
and continue scrolling down.
So this part right here is for the management network.
That's the communication path between the controller
and the service engines.
And then the next part is asking us about the data plane,
what we're going to be doing load balancing force. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
what we're going to be doing load balancing force.
So for the data networks, we're going to go ahead
and select a transport zone.
And because our data plane here is going to be using VLANs,
we're going to go ahead and choose a VLAN-backed transport
zone that are edge nodes and our hosts are supporting.
So here for the transport zone, we're
going to go ahead and use the lab 3-RED VLAN-TZ once again.
Then we will click here on the drop down for segments.
It'll show us all the VLAN-backed segments.
And that's because we chose a VLAN-backed transport zone.
So let's start off with VLAN-5.
So we'll select that.
And I also want to add to that VLAN-23. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I also want to add to that VLAN-23.
So we'll go ahead and that's the interface right there,
off of the T0 gateway.
Fantastic.
I also want to include this segment over here, the 192.168.1,
because we're going to have a virtual IP address over there
as well.
So we'll go ahead and grab that as well.
And let's see if that covers it.
So as far as the data plane is concerned, here, up here,
and over here, fantastic.
So just be aware that for the management network
for our service engines, we could have that on overlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for our service engines, we could have that on overlay
transport zone or a VLAN-backed transport zone.
And then for the data plane, we also
have those same options--
an overlay transport zone or a VLAN-backed transport zone
or we could mix and match.
So we could have our management on overlay transport zones
and our data networks on VLAN-backed transport zones.
It boils down to a couple of decisions,
including the choice of where you want to have your service
engines and also maybe you already
have your existing servers on a VLAN.
So for the data plane, we'd want to go ahead and specify
VLAN-backed because the servers are already in that VLAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
VLAN-backed because the servers are already in that VLAN.
But again, you can mix and match based on your needs.
So with the management network in place
and also the data networks in place,
let's go ahead and scroll down and let's go ahead and tell
the controller about our vCenter.
So we'll click here on add for the vCenter.
We'll call this our VCSA.
And the reason that the controller
needs to know about the vCenter is because as it
starts to deploy the service engines,
it needs to use the vCenter services to do that.
So it's a combined effort with the controller
using vCenter for the deployment of the actual VMs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
using vCenter for the deployment of the actual VMs,
aka the service engines.
So we'll specify how the controller can log in to the vCenter.
So we'll use the dropdown here.
Now, because we already told the controller about the NSX
manager and because the NSX manager is using this vCenter,
that's why it's already showing up here in the list.
And then from the dropdown for the credentials,
we'll use the credentials that we had set up previously.
So these credentials have the username and the password
appropriate to log on to that vCenter at .35.
So with that done, we'll click on connect. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So with that done, we'll click on connect.
So if that was successful, as far as the connection there,
now if we click on the content library,
it should show us all the content libraries that
are available through that vCenter.
So that's a very good sign.
We'll choose that content library.
And we'll click on done.
And let's check our work.
So here's the name of our cloud.
We're going to use DHCP services for the assignment of IP addresses
for our service engines.
As we scroll down, here's the credentials
to log on to the NSX manager.
And then we specified for the management network
that we want to use VLAN6 for our service engines. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that we want to use VLAN6 for our service engines.
And then for the data playing, the actual load balancing
services that the service engines are going to do.
We're using a VLAN back transport zone.
And then we specified the three VLANs that are going to be
involved, one where the servers are,
and one up here where a VIP is going to be,
and one over here where a VIP is going to be.
And then we added the information about the vCenter as well.
And we could also add IP address management and DNS profiles.
But for the demo, I'm not going to include that.
So I'll click on save.
And boom, we now have a new cloud called NSX Cloud 4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And boom, we now have a new cloud called NSX Cloud 4.
And here in just a moment or two, it should be green.
Now, until it goes green, if we go down here to cloud resources
and we click on networks, and then from the drop down here,
we select NSX Cloud 4.
Oh, it must have just finished.
Because these won't be populated yet until that cloud
connector is all set up and ready to go.
So if we go back to clouds here for the NSX Cloud,
here is now green.
So if you went down to cloud resources
and you didn't see your networks yet,
just give that a few more moments to complete. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just give that a few more moments to complete.
So now that that cloud connector is done,
let's also just for a moment go down to cloud resources,
go to networks.
I'm also going to specify for our cloud.
And for the networks there, I'm going
to specify the actual subnet ranges for each of these.
And that's going to be useful later
when we start configuring our virtual IP addresses
and specifying where we want them to live
and also specifying where our servers are.
So for the external net 192, I'm going
to click on the little pencil here.
And then for subnets, I'm going to click on add.
And just going to identify a subnet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And just going to identify a subnet.
So we'll go ahead and say it's 192.168.1.0 with a 24-bit
mask, and then scroll down and click on save.
Because we're using static IP dressing,
I don't even need to set up a pool.
And then we'll click on save again.
So now if we refer to this external network,
it has a clue about what the actual subnet ranges.
And I'm going to repeat that process for each of the subnets.
So here for external VLAN 23, we'll
click on the pencil to edit it.
For subnets, we'll click on add.
And then for the subnet, for that, it's 23.1.2.0
with a 24-bit mask. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Click on save.
Click on save again.
Now it knows about both of those.
Then I'll repeat that process for external VLAN 5
with the address base of 10.50 with the 24-bit mask,
and also for VLAN 6 with a 10.60.
Although for VLAN 6, I may not need the range,
because we're only supporting our SEs there.
And there's DHCP services already present.
But just to make it nice and consistent,
I'm going to add those as well.
So for VLAN 5, we'll click on the pencil.
We'll click right here on add for subnets.
And then we'll put in the prefix of 10.5.0.0 with a 24-bit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll put in the prefix of 10.5.0.0 with a 24-bit
mask.
And click on save.
And then repeat that one more time for VLAN 6
in the address base that we're using there.
So we'll click on the pencil.
We're going to the subnets.
We'll click on add.
And then we'll put in the subnet 10.6.0 with a 24-bit mask.
And then we'll click on save and save.
So now that we have this cloud created,
we have a couple problems.
Number one is if we click here on service engines
and then select our cloud, we have no service engines deployed.
We also don't have any virtual services.
So by default, the controller is not WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
deploying any service engines until it has a reason to.
And one of the reasons it would is
if we start creating at least one virtual service
with an associated virtual IP address,
pointing back to a pool of servers.
So it'll have a reason to actually deploy a service engine.
So even though we don't yet have any service engines created
in the background, let me also point out
what the controller did.
It placed in the content library the template
that it can use if it does need to deploy a service engine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that it can use if it does need to deploy a service engine.
So if we pop over to the vSphere client for a moment
and we go to the content library,
so use the hamburger menu there, click on content libraries,
we'll go to our content library and check it out.
There is one template there and that's the image,
it's about four gig, that's the image
that the controller is gonna use
when it needs to deploy one of its service engines.
And again, the process that's gonna kick that off
is we need to have at least one virtual service configured.
And once we do that, the controller will then use
this template in this library to start deploying WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this template in this library to start deploying
one or more service engines.
So join me in the next videos,
we take that next step in creating a virtual service
inside the advanced load balancer.
So I'll see you in the next video in just a moment.