WEBVTT

1
00:00.000 --> 00:03.640
So now that we have verified that our virtual IP address with

2
00:03.640 --> 00:07.560
a virtual service available over here and this network segment is working,

3
00:07.560 --> 00:11.720
I'd like to go ahead and create a second one that's available up here on

4
00:11.720 --> 00:15.840
the 2312 network just north of our Tier 0 gateway.

5
00:15.840 --> 00:18.020
We can tie that virtual IP address and it's

6
00:18.020 --> 00:22.580
associated virtual service with that same set of servers over here on the 1050

7
00:22.580 --> 00:23.160
network.

8
00:23.160 --> 00:24.840
So to create the new virtual service,

9
00:24.840 --> 00:27.720
what we'll do is go ahead and click on Virtual Services.

10
00:27.720 --> 00:31.800
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

10
00:27.720 --> 00:31.800
Then here from this view, we'll click on Create Virtual Service right there.

11
00:31.800 --> 00:34.520
Then last time we did the advanced setup and this time,

12
00:34.520 --> 00:37.840
let's just do the basic setup and then if we need to tweak or modify anything,

13
00:37.840 --> 00:40.320
we can just go into the interface and do exactly that.

14
00:40.320 --> 00:41.800
So for this new virtual service,

15
00:41.800 --> 00:43.960
we want to associate it with our new cloud,

16
00:43.960 --> 00:45.200
the NSX Cloud 4.

17
00:45.200 --> 00:47.560
So we'll select that Cloud and click on Next.

18
00:47.560 --> 00:48.360
Now for the name list,

19
00:48.360 --> 00:50.920
call it VS-23.5,

20
00:50.920 --> 00:53.960
just as a reminder for this virtual service that is going to represent

21
00:53.960 --> 00:58.320
a virtual IP address up here on the 23 1.2 address space.

22
00:58.320 --> 01:00.840
Then for the new virtual service IP address,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:58.320 --> 01:00.840
Then for the new virtual service IP address,

23
01:00.840 --> 01:04.380
we'll click here and we don't want to use the same one because that'd be the

24
01:04.380 --> 01:04.920
same address.

25
01:04.920 --> 01:06.680
But what we want to do is create a new one.

26
01:06.680 --> 01:09.240
So we'll click right here on Create Virtual Services.

27
01:09.240 --> 01:13.320
So we'll click here on Create Virtual Service Virtual IP address and let's call

28
01:13.320 --> 01:15.280
this VIP-23.

29
01:15.280 --> 01:17.720
Then for the actual IP address, we'll click here on Add.

30
01:17.720 --> 01:21.040
We're going to use a static assignment for the virtual IP address and we're

31
01:21.040 --> 01:23.920
going to use 23.1.2.5.

32
01:23.920 --> 01:25.360
Based on our plan.

33
01:25.360 --> 01:29.520
So that part looks good and then we'll scroll down and it's asking about where

34
01:29.520 --> 01:30.560
this is going to be.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.520 --> 01:30.560
this is going to be.

35
01:30.560 --> 01:34.800
So because it's out on the 23 1.2 network, we'll click on Add.

36
01:34.800 --> 01:37.400
And then we'll go ahead and use the dropdown.

37
01:37.400 --> 01:40.880
This is showing us our four networks that are VLAN-based networks

38
01:40.880 --> 01:43.520
because that's what we specify for the data plane for this cloud.

39
01:43.520 --> 01:48.160
And there are the associated IP subnets because we added those as well.

40
01:48.160 --> 01:51.120
So for external 23, we'll choose this one right here.

41
01:51.120 --> 01:55.120
And then for the subnet, we use the dropdown and it's the 23.1.2 subnet.

42
01:55.120 --> 01:58.800
So the virtual IP address is going to be appear available off this network.

43
01:58.800 --> 02:01.920
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

43
01:58.800 --> 02:01.920
So we'll scroll down just to make sure we have the right subnet we do and we'll

44
02:01.920 --> 02:02.960
click on Save.

45
02:02.960 --> 02:04.800
And then we'll click on Save again.

46
02:04.800 --> 02:06.960
So here's the name of our virtual service.

47
02:06.960 --> 02:11.760
It's going to use the virtual IP address that we just configured of 23.1.2.5.

48
02:11.760 --> 02:16.340
And for these servers, we already have these servers identified here down in

49
02:16.340 --> 02:17.280
this pool.

50
02:17.280 --> 02:20.720
So I don't want to add them again as a separate pool. I'm going to leave this

51
02:20.720 --> 02:21.360
blank and then we'll

52
02:21.360 --> 02:24.880
just come back in after the wizard's done and we'll simply add it in.

53
02:24.880 --> 02:28.160
Still we'll scroll down and there's nothing else to add. So we'll click on Save

54
02:28.160 --> 02:28.160
.

55
02:28.160 --> 02:31.000
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

55
02:28.160 --> 02:31.000
And here's that new service. So if we want to edit that service, I'm going to

56
02:31.000 --> 02:32.000
go back to the

57
02:32.000 --> 02:35.450
lists of virtual services here. Let me go ahead and move my topology down to

58
02:35.450 --> 02:36.320
the bottom right.

59
02:36.320 --> 02:39.990
I want to go ahead and edit this virtual service and tell it to use our

60
02:39.990 --> 02:41.040
existing pool.

61
02:41.040 --> 02:45.680
So I just created this empty pool for us. It named it VS 23.5 pool.

62
02:45.680 --> 02:49.040
And what we want to do is use the existing pool right here.

63
02:49.040 --> 02:51.600
So to do that, let's go back to our virtual service.

64
02:51.600 --> 02:54.880
And what we'll do is we'll click on Edit to edit our virtual service.

65
02:54.880 --> 02:57.680
Then we'll scroll down to the pool section right here and say, you know what?

66
02:57.680 --> 02:58.240
We don't want to use

67
02:58.240 --> 03:02.580
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

67
02:58.240 --> 03:02.580
that pool. We want to use the web servers on VLAN 5 pool, which is already

68
03:02.580 --> 03:03.200
defined.

69
03:03.200 --> 03:06.920
And then in the bottom right, we'll click on Save to continue. So we'll click

70
03:06.920 --> 03:07.360
on Save.

71
03:07.360 --> 03:10.550
And then also because we don't need that other empty pool. I'm going to go back

72
03:10.550 --> 03:11.520
to pools

73
03:11.520 --> 03:14.640
and grab that pool and just delete it the one we're not using.

74
03:14.640 --> 03:17.940
And let's go back to virtual services. So here we still have an exclamation

75
03:17.940 --> 03:18.080
mark.

76
03:18.080 --> 03:22.880
We hover there. Oh, check it out. So creating, waiting for service engine,

77
03:22.880 --> 03:28.320
NSX yada yada yada to acquire the IP address. And it is done. Look at that.

78
03:28.320 --> 03:32.640
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

78
03:28.320 --> 03:32.640
So the reason that was fairly quick is because it already had two service

79
03:32.640 --> 03:34.000
engines deployed

80
03:34.000 --> 03:37.600
in vSphere. And so it just took one that was already sitting there and said,

81
03:37.600 --> 03:38.160
you know what?

82
03:38.160 --> 03:41.600
Here's what you get to do. So if we select that new virtual service,

83
03:41.600 --> 03:45.520
and then we hover here over the name for that virtual service is showing us is

84
03:45.520 --> 03:46.160
this

85
03:46.160 --> 03:50.160
SE that is now in charge of that load balancing function on the data plane.

86
03:50.160 --> 03:54.400
So if we went in vSphere client and took a look at this specific service engine

87
03:54.400 --> 03:55.120
, the one ending in

88
03:55.120 --> 03:59.620
XRI, we would see that it has three interfaces. It would have a management

89
03:59.620 --> 04:01.600
interface on VLAN 6.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:59.620 --> 04:01.600
interface on VLAN 6.

90
04:01.600 --> 04:05.760
It would have one interface up here on the 2312 network. It would have yet

91
04:05.760 --> 04:06.640
another interface

92
04:06.640 --> 04:10.940
over here on the 1050 network as is doing the load balancing function between

93
04:10.940 --> 04:12.480
the VIP over here

94
04:12.480 --> 04:15.920
and the pool of servers over here. In fact, let's head over to the vSphere

95
04:15.920 --> 04:16.880
client just for a moment

96
04:16.880 --> 04:22.160
to verify that. So here is that services engine, the one ending in XRI. So with

97
04:22.160 --> 04:23.040
that selected on

98
04:23.040 --> 04:26.160
the summary page, if we scroll down a little bit, here is showing us the

99
04:26.160 --> 04:27.840
networks it's connected to.

100
04:27.840 --> 04:32.400
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

100
04:27.840 --> 04:32.400
So VLAN 6 for management, VLAN 5, because it's providing the load balancing

101
04:32.400 --> 04:33.120
function

102
04:33.120 --> 04:38.320
for that pool of servers and from the virtual IP address up on the 23 network,

103
04:38.320 --> 04:38.720
that's why it has

104
04:38.720 --> 04:43.000
that connection. So we have one of our service engines doing the load balancing

105
04:43.000 --> 04:43.840
from this VIP

106
04:43.840 --> 04:48.230
or this pool and a second service engine doing the load balancing from this

107
04:48.230 --> 04:49.680
virtual IP over the pool.

108
04:49.680 --> 04:53.440
So let's also test this as well actually before we test it. Let me make sure I

109
04:53.440 --> 04:54.800
have logging enabled

110
04:54.800 --> 04:59.560
for this virtual service. So if we go into details for this virtual service and

111
04:59.560 --> 05:00.720
go to analytics,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:59.560 --> 05:00.720
go to analytics,

112
05:00.720 --> 05:04.180
here's where we can make sure that we have logging enabled. And for the lab, I

113
05:04.180 --> 05:04.960
'm going to specify

114
05:04.960 --> 05:09.530
that it should also log non-significant logs. And then we'll go ahead and click

115
05:09.530 --> 05:10.800
on save. Then let's go

116
05:10.800 --> 05:15.910
ahead and put a client up here on the 23 network and verify that we can access

117
05:15.910 --> 05:17.600
that virtual IP address

118
05:17.600 --> 05:21.510
and that it leads down to these three servers in a round robin fashion. So here

119
05:21.510 --> 05:22.640
is a computer we

120
05:22.640 --> 05:27.440
can test for my just moved it up here to this network, the 2312. And let's just

121
05:27.440 --> 05:28.160
verify that

122
05:28.160 --> 05:34.320
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

122
05:28.160 --> 05:34.320
at the CLI. So let's do an I have config press enter and sure enough 23.1.2.79

123
05:34.320 --> 05:35.360
so let's verify

124
05:35.360 --> 05:40.880
that if we go to 23.1.2.5, it's going to proxy us over to one of these three

125
05:40.880 --> 05:41.920
back end servers.

126
05:41.920 --> 05:48.660
So we'll open up a browser to do that and we'll go to 23.1.2.5 press enter and

127
05:48.660 --> 05:49.680
that is working.

128
05:49.680 --> 05:55.360
That's fantastic. So let's do a control shift R and that is doing the round rob

129
05:55.360 --> 05:56.320
in between

130
05:56.320 --> 05:58.320
all three of those servers.