So now that we have verified that our virtual IP address with
a virtual service available over here and this network segment is working,
I'd like to go ahead and create a second one that's available up here on
the 2312 network just north of our Tier 0 gateway.
We can tie that virtual IP address and it's
associated virtual service with that same set of servers over here on the 1050
network.
So to create the new virtual service,
what we'll do is go ahead and click on Virtual Services.
Then here from this view, we'll click on Create Virtual Service right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then here from this view, we'll click on Create Virtual Service right there.
Then last time we did the advanced setup and this time,
let's just do the basic setup and then if we need to tweak or modify anything,
we can just go into the interface and do exactly that.
So for this new virtual service,
we want to associate it with our new cloud,
the NSX Cloud 4.
So we'll select that Cloud and click on Next.
Now for the name list,
call it VS-23.5,
just as a reminder for this virtual service that is going to represent
a virtual IP address up here on the 23 1.2 address space.
Then for the new virtual service IP address, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then for the new virtual service IP address,
we'll click here and we don't want to use the same one because that'd be the
same address.
But what we want to do is create a new one.
So we'll click right here on Create Virtual Services.
So we'll click here on Create Virtual Service Virtual IP address and let's call
this VIP-23.
Then for the actual IP address, we'll click here on Add.
We're going to use a static assignment for the virtual IP address and we're
going to use 23.1.2.5.
Based on our plan.
So that part looks good and then we'll scroll down and it's asking about where
this is going to be. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this is going to be.
So because it's out on the 23 1.2 network, we'll click on Add.
And then we'll go ahead and use the dropdown.
This is showing us our four networks that are VLAN-based networks
because that's what we specify for the data plane for this cloud.
And there are the associated IP subnets because we added those as well.
So for external 23, we'll choose this one right here.
And then for the subnet, we use the dropdown and it's the 23.1.2 subnet.
So the virtual IP address is going to be appear available off this network.
So we'll scroll down just to make sure we have the right subnet we do and we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll scroll down just to make sure we have the right subnet we do and we'll
click on Save.
And then we'll click on Save again.
So here's the name of our virtual service.
It's going to use the virtual IP address that we just configured of 23.1.2.5.
And for these servers, we already have these servers identified here down in
this pool.
So I don't want to add them again as a separate pool. I'm going to leave this
blank and then we'll
just come back in after the wizard's done and we'll simply add it in.
Still we'll scroll down and there's nothing else to add. So we'll click on Save
.
And here's that new service. So if we want to edit that service, I'm going to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And here's that new service. So if we want to edit that service, I'm going to
go back to the
lists of virtual services here. Let me go ahead and move my topology down to
the bottom right.
I want to go ahead and edit this virtual service and tell it to use our
existing pool.
So I just created this empty pool for us. It named it VS 23.5 pool.
And what we want to do is use the existing pool right here.
So to do that, let's go back to our virtual service.
And what we'll do is we'll click on Edit to edit our virtual service.
Then we'll scroll down to the pool section right here and say, you know what?
We don't want to use
that pool. We want to use the web servers on VLAN 5 pool, which is already WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that pool. We want to use the web servers on VLAN 5 pool, which is already
defined.
And then in the bottom right, we'll click on Save to continue. So we'll click
on Save.
And then also because we don't need that other empty pool. I'm going to go back
to pools
and grab that pool and just delete it the one we're not using.
And let's go back to virtual services. So here we still have an exclamation
mark.
We hover there. Oh, check it out. So creating, waiting for service engine,
NSX yada yada yada to acquire the IP address. And it is done. Look at that.
So the reason that was fairly quick is because it already had two service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the reason that was fairly quick is because it already had two service
engines deployed
in vSphere. And so it just took one that was already sitting there and said,
you know what?
Here's what you get to do. So if we select that new virtual service,
and then we hover here over the name for that virtual service is showing us is
this
SE that is now in charge of that load balancing function on the data plane.
So if we went in vSphere client and took a look at this specific service engine
, the one ending in
XRI, we would see that it has three interfaces. It would have a management
interface on VLAN 6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
interface on VLAN 6.
It would have one interface up here on the 2312 network. It would have yet
another interface
over here on the 1050 network as is doing the load balancing function between
the VIP over here
and the pool of servers over here. In fact, let's head over to the vSphere
client just for a moment
to verify that. So here is that services engine, the one ending in XRI. So with
that selected on
the summary page, if we scroll down a little bit, here is showing us the
networks it's connected to.
So VLAN 6 for management, VLAN 5, because it's providing the load balancing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So VLAN 6 for management, VLAN 5, because it's providing the load balancing
function
for that pool of servers and from the virtual IP address up on the 23 network,
that's why it has
that connection. So we have one of our service engines doing the load balancing
from this VIP
or this pool and a second service engine doing the load balancing from this
virtual IP over the pool.
So let's also test this as well actually before we test it. Let me make sure I
have logging enabled
for this virtual service. So if we go into details for this virtual service and
go to analytics, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
go to analytics,
here's where we can make sure that we have logging enabled. And for the lab, I
'm going to specify
that it should also log non-significant logs. And then we'll go ahead and click
on save. Then let's go
ahead and put a client up here on the 23 network and verify that we can access
that virtual IP address
and that it leads down to these three servers in a round robin fashion. So here
is a computer we
can test for my just moved it up here to this network, the 2312. And let's just
verify that
at the CLI. So let's do an I have config press enter and sure enough 23.1.2.79 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
at the CLI. So let's do an I have config press enter and sure enough 23.1.2.79
so let's verify
that if we go to 23.1.2.5, it's going to proxy us over to one of these three
back end servers.
So we'll open up a browser to do that and we'll go to 23.1.2.5 press enter and
that is working.
That's fantastic. So let's do a control shift R and that is doing the round rob
in between
all three of those servers.