So in this video, we're going to set up the cloud connector so this controller
as part of our load balancer can interact and work within our NSX environment.
And so this is referred to as setting up an NSX cloud inside of the advanced
load balancer.
So here it logged on to this load balancer right here to create our cloud
environment.
What we're going to do is click on infrastructure.
It shows us on the left the dashboard showing us all of our service engines.
So currently we have absolutely zero service engines that have been deployed WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So currently we have absolutely zero service engines that have been deployed
anywhere in our topology.
So if we click on clouds, there's one default cloud.
So we can't delete the default cloud.
If we wanted to, we could go in and edit it and specify details here.
However, what I want to do in this demonstration is just create a brand new NSX
based cloud.
And to do that with the infrastructure tab on top selected and clouds on the
left selected,
we're simply going to click right here on create.
And then from the drop down, we're going to choose the cloud connector we want
to use.
So because we want to integrate and use NSX, we're going to go ahead and choose WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So because we want to integrate and use NSX, we're going to go ahead and choose
the NSX cloud right here to create and set the details for the NSX cloud.
So we'll click on NSX cloud.
And so across the top, we have some tabs.
So the general tab, we can just scroll all the way down through it.
If we need to jump to one of the sections, we can just click on that.
It'll take you to that portion inside this window.
So we'll go ahead and scroll the top, let's start off here.
And let's call this our dash NSX dash cloud.
And because from the menu, we selected NSX cloud as the type.
It knows that's the type we want to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It knows that's the type we want to use.
However, if we chose the wrong type, we have another option right here to
choose the correct one.
So we're going to go ahead and stick with the NSX cloud.
I'm going to be using some DHCP services for NSX cloud so that when these
service engines are deployed,
they can be DHCP clients and get IP addresses that way.
We'll scroll down.
And then we're going to put in the details for our connection from the
controller here to our NSX environment.
So we'll click on change credentials right here.
And then we're going to specify the management address for our NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that is at 192.168.1.21.
Also, we could, if we had DNS all set up, we could certainly use DNS names as
well.
But for this set of demos, I wanted to stick with just raw IP addresses.
And that way you can see exactly where we're connecting from and to and
everything else.
And then for the actual credentials, we use the drop down here.
And because we created one set of credentials for NSX, we called it credentials
for NSX at .21.
We'll use that.
And we'll know here in just a few moments whether or not that works because if WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll know here in just a few moments whether or not that works because if
we click here on connect,
if it worked, as we continue on with the configuration, we should then be able
to see our NSX related segments
and so forth in our topology if we now have access to the NSX manager.
So we'll know in a moment if that works.
So here for the management network, and we want to use the 10-103 address base
in this segment 103 ALB management
for our NSX management, for the transport zone, we'll use the drop down.
Oh, great news is there.
So that segment is part of the overlay transport zone called lab 3 red overlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that segment is part of the overlay transport zone called lab 3 red overlay
transport zone.
So we'll select that.
And now it's asking, okay, which gateway do you want to use?
So the tier one logical router that we want to use is tier one right.
So we'll choose that one.
So far so good.
And then for the overlay segment, we want to go ahead and use segment 103.
So from the drop down, there it is right there.
So that's for the management network between the controller and the service
engines that is going to go ahead and deploy.
So the next part, it's asking about are the data networks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Think of that like the data plane.
So if we want to support servers over here on segment 101 off tier one left,
we'd first of all specify the correct transport zone.
So this segment over here is an overlay segment and that's in that same overlay
transport zone that we're using over here at T1 right.
So for the transport zone for the data network, I'll use the drop down.
And once again, I'm going to choose the overlay transport zone.
So if we are supporting servers out here on VLAN 5, for example, for the
transport zone for the data plane,
we would choose the VLAN-backed transport zone that we wanted to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we would choose the VLAN-backed transport zone that we wanted to use.
And then furthermore, the VLAN-backed segments where the servers are.
So for our demo and based on our plan, we're going to support the virtual
servers right here.
So we chose the transport zone that this segment's in and we'll scroll down and
then we're going to add these segments.
So we'll go ahead and click right here on add.
And for the logical router drop down, we're going to go ahead and use T1 left.
This guy right there, fantastic.
And then for the overlay segment, we want segment 101.
So from the drop down, it should show up and there it is, segment 101 web WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So from the drop down, it should show up and there it is, segment 101 web
servers.
That's the actual name of that segment in NSX.
So we'll select that.
And so far, so good.
So the next part of our journey is to specify the vCenter server that we want
to use for the deployment of our service engines.
Because vSphere is not just going to let anybody create VMs, you have to have
permission.
So we're going to train the controller that is able to use this vCenter server
at .35.
So we'll click on add for vCenter servers.
And let's name this our vCSA and NSX cloud. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll click right here on change credentials.
So we'll use the drop down and select the IP address for the vCenter server
right there.
And then for the credentials, we only have one set of credentials for that v
Center.
And that's this credential set right here.
So we'll select that and click on connect.
Now we're also going to know here in a moment if that was successful because if
it is, we'll use the drop down right here under content library.
We should also be able to see the existing content libraries in this vCenter.
So we only have one.
So when we just made in the previous video.
So from the drop down, there it is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So from the drop down, there it is.
All right, that's great news.
That means we are communicating between this controller right here and not only
the NSX that we saw earlier by selecting the various segments, but also now we
're connected to and working with our vCenter because we can see our content
library right there.
Fantastic.
So we'll click on done and let's just make sure we have supplied all the
required information wherever there's an asterisk in red.
So we'll scroll down.
We need a prefix name.
Let's go ahead and use a prefix name of our NSX lab.
And that way as part of this NSX cloud as service engines are being deployed, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that way as part of this NSX cloud as service engines are being deployed,
the VMs will have this as a prefix.
And that way as those VMs show up in vSphere, it'll be very easy to identify
them because they'll have this prefix associated with them.
So let's scroll down.
We have our NSX credentials.
We have our management network, which is right over here, segment 103 off of
the tier right gateway.
The actual data plane network for the load balancing function for the service
engines is going to be this transport zone and then specifically off that
gateway.
This segment.
So that looks good. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the vCenter we're connected to and going to be working with this v
Center.35.
And then here for IP address management and DNS, I'm going to go ahead and
leave those profiles off.
So I believe we've identified everything that's required.
So we'll click on save right here and give that a moment.
So the default cloud has a nice green icon here and for our new cloud that just
went to green.
That's a very good sign.
So if we go down here under cloud resources and we click on service engine.
So currently it's showing us for the default cloud, any service engines that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So currently it's showing us for the default cloud, any service engines that
have been deployed.
And if he's the drop down and choose our NSX cloud also zero service engines.
And the reason for that is that the controller is not going to deploy any
service engines until another reason to.
So until we create a logical virtual service and a virtual IP address with some
service behind it.
That's not really a reason for the controller to deploy any service engines
anywhere.
Because currently we don't have any need for a data plane for the load balancer
.
But that will change once we create a virtual service with a virtual IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But that will change once we create a virtual service with a virtual IP address
and then put in some servers behind the scenes.
That the actual service engine can then use as it load balances traffic coming
in to the virtual IP address.
And then the back end proxying it to one of the available servers.
[BLANK_AUDIO]