WEBVTT

1
00:00.000 --> 00:04.720
So in this video, we're going to set up the cloud connector so this controller

2
00:04.720 --> 00:10.000
as part of our load balancer can interact and work within our NSX environment.

3
00:10.000 --> 00:13.950
And so this is referred to as setting up an NSX cloud inside of the advanced

4
00:13.950 --> 00:15.000
load balancer.

5
00:15.000 --> 00:18.970
So here it logged on to this load balancer right here to create our cloud

6
00:18.970 --> 00:20.000
environment.

7
00:20.000 --> 00:22.000
What we're going to do is click on infrastructure.

8
00:22.000 --> 00:26.000
It shows us on the left the dashboard showing us all of our service engines.

9
00:26.000 --> 00:31.350
So currently we have absolutely zero service engines that have been deployed
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.000 --> 00:31.350
So currently we have absolutely zero service engines that have been deployed

10
00:31.350 --> 00:33.000
anywhere in our topology.

11
00:33.000 --> 00:37.000
So if we click on clouds, there's one default cloud.

12
00:37.000 --> 00:39.000
So we can't delete the default cloud.

13
00:39.000 --> 00:43.000
If we wanted to, we could go in and edit it and specify details here.

14
00:43.000 --> 00:47.900
However, what I want to do in this demonstration is just create a brand new NSX

15
00:47.900 --> 00:49.000
based cloud.

16
00:49.000 --> 00:52.070
And to do that with the infrastructure tab on top selected and clouds on the

17
00:52.070 --> 00:53.000
left selected,

18
00:53.000 --> 00:56.000
we're simply going to click right here on create.

19
00:56.000 --> 00:58.640
And then from the drop down, we're going to choose the cloud connector we want

20
00:58.640 --> 00:59.000
to use.

21
00:59.000 --> 01:03.430
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

21
00:59.000 --> 01:03.430
So because we want to integrate and use NSX, we're going to go ahead and choose

22
01:03.430 --> 01:08.000
the NSX cloud right here to create and set the details for the NSX cloud.

23
01:08.000 --> 01:10.000
So we'll click on NSX cloud.

24
01:10.000 --> 01:12.000
And so across the top, we have some tabs.

25
01:12.000 --> 01:15.000
So the general tab, we can just scroll all the way down through it.

26
01:15.000 --> 01:17.000
If we need to jump to one of the sections, we can just click on that.

27
01:17.000 --> 01:20.000
It'll take you to that portion inside this window.

28
01:20.000 --> 01:23.000
So we'll go ahead and scroll the top, let's start off here.

29
01:23.000 --> 01:26.000
And let's call this our dash NSX dash cloud.

30
01:26.000 --> 01:29.000
And because from the menu, we selected NSX cloud as the type.

31
01:29.000 --> 01:31.000
It knows that's the type we want to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:29.000 --> 01:31.000
It knows that's the type we want to use.

32
01:31.000 --> 01:33.880
However, if we chose the wrong type, we have another option right here to

33
01:33.880 --> 01:35.000
choose the correct one.

34
01:35.000 --> 01:38.000
So we're going to go ahead and stick with the NSX cloud.

35
01:38.000 --> 01:41.750
I'm going to be using some DHCP services for NSX cloud so that when these

36
01:41.750 --> 01:43.000
service engines are deployed,

37
01:43.000 --> 01:46.000
they can be DHCP clients and get IP addresses that way.

38
01:46.000 --> 01:47.000
We'll scroll down.

39
01:47.000 --> 01:50.330
And then we're going to put in the details for our connection from the

40
01:50.330 --> 01:52.000
controller here to our NSX environment.

41
01:52.000 --> 01:55.000
So we'll click on change credentials right here.

42
01:55.000 --> 02:00.000
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

43
02:00.000 --> 02:03.000
And that is at 192.168.1.21.

44
02:03.000 --> 02:08.380
Also, we could, if we had DNS all set up, we could certainly use DNS names as

45
02:08.380 --> 02:09.000
well.

46
02:09.000 --> 02:12.000
But for this set of demos, I wanted to stick with just raw IP addresses.

47
02:12.000 --> 02:15.320
And that way you can see exactly where we're connecting from and to and

48
02:15.320 --> 02:16.000
everything else.

49
02:16.000 --> 02:19.000
And then for the actual credentials, we use the drop down here.

50
02:19.000 --> 02:23.060
And because we created one set of credentials for NSX, we called it credentials

51
02:23.060 --> 02:24.000
for NSX at .21.

52
02:24.000 --> 02:25.000
We'll use that.

53
02:25.000 --> 02:30.160
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

53
02:25.000 --> 02:30.160
And we'll know here in just a few moments whether or not that works because if

54
02:30.160 --> 02:31.000
we click here on connect,

55
02:31.000 --> 02:37.150
if it worked, as we continue on with the configuration, we should then be able

56
02:37.150 --> 02:39.000
to see our NSX related segments

57
02:39.000 --> 02:44.000
and so forth in our topology if we now have access to the NSX manager.

58
02:44.000 --> 02:46.000
So we'll know in a moment if that works.

59
02:46.000 --> 02:50.150
So here for the management network, and we want to use the 10-103 address base

60
02:50.150 --> 02:52.000
in this segment 103 ALB management

61
02:52.000 --> 02:56.000
for our NSX management, for the transport zone, we'll use the drop down.

62
02:56.000 --> 02:58.000
Oh, great news is there.

63
02:58.000 --> 03:02.740
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

63
02:58.000 --> 03:02.740
So that segment is part of the overlay transport zone called lab 3 red overlay

64
03:02.740 --> 03:04.000
transport zone.

65
03:04.000 --> 03:05.000
So we'll select that.

66
03:05.000 --> 03:08.000
And now it's asking, okay, which gateway do you want to use?

67
03:08.000 --> 03:12.000
So the tier one logical router that we want to use is tier one right.

68
03:12.000 --> 03:13.000
So we'll choose that one.

69
03:13.000 --> 03:14.000
So far so good.

70
03:14.000 --> 03:18.000
And then for the overlay segment, we want to go ahead and use segment 103.

71
03:18.000 --> 03:21.000
So from the drop down, there it is right there.

72
03:21.000 --> 03:24.640
So that's for the management network between the controller and the service

73
03:24.640 --> 03:27.000
engines that is going to go ahead and deploy.

74
03:27.000 --> 03:30.000
So the next part, it's asking about are the data networks.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:30.000 --> 03:32.000
Think of that like the data plane.

76
03:32.000 --> 03:37.000
So if we want to support servers over here on segment 101 off tier one left,

77
03:37.000 --> 03:39.000
we'd first of all specify the correct transport zone.

78
03:39.000 --> 03:44.160
So this segment over here is an overlay segment and that's in that same overlay

79
03:44.160 --> 03:47.000
transport zone that we're using over here at T1 right.

80
03:47.000 --> 03:50.000
So for the transport zone for the data network, I'll use the drop down.

81
03:50.000 --> 03:53.000
And once again, I'm going to choose the overlay transport zone.

82
03:53.000 --> 03:56.370
So if we are supporting servers out here on VLAN 5, for example, for the

83
03:56.370 --> 03:58.000
transport zone for the data plane,

84
03:58.000 --> 04:02.000
we would choose the VLAN-backed transport zone that we wanted to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:58.000 --> 04:02.000
we would choose the VLAN-backed transport zone that we wanted to use.

85
04:02.000 --> 04:06.000
And then furthermore, the VLAN-backed segments where the servers are.

86
04:06.000 --> 04:09.290
So for our demo and based on our plan, we're going to support the virtual

87
04:09.290 --> 04:10.000
servers right here.

88
04:10.000 --> 04:14.150
So we chose the transport zone that this segment's in and we'll scroll down and

89
04:14.150 --> 04:16.000
then we're going to add these segments.

90
04:16.000 --> 04:18.000
So we'll go ahead and click right here on add.

91
04:18.000 --> 04:23.000
And for the logical router drop down, we're going to go ahead and use T1 left.

92
04:23.000 --> 04:25.000
This guy right there, fantastic.

93
04:25.000 --> 04:28.000
And then for the overlay segment, we want segment 101.

94
04:28.000 --> 04:31.710
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

94
04:28.000 --> 04:31.710
So from the drop down, it should show up and there it is, segment 101 web

95
04:31.710 --> 04:32.000
servers.

96
04:32.000 --> 04:35.000
That's the actual name of that segment in NSX.

97
04:35.000 --> 04:36.000
So we'll select that.

98
04:36.000 --> 04:38.000
And so far, so good.

99
04:38.000 --> 04:41.650
So the next part of our journey is to specify the vCenter server that we want

100
04:41.650 --> 04:44.000
to use for the deployment of our service engines.

101
04:44.000 --> 04:48.480
Because vSphere is not just going to let anybody create VMs, you have to have

102
04:48.480 --> 04:49.000
permission.

103
04:49.000 --> 04:53.020
So we're going to train the controller that is able to use this vCenter server

104
04:53.020 --> 04:54.000
at .35.

105
04:54.000 --> 04:57.000
So we'll click on add for vCenter servers.

106
04:57.000 --> 05:00.000
And let's name this our vCSA and NSX cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
05:00.000 --> 05:03.000
And then we'll click right here on change credentials.

108
05:03.000 --> 05:06.220
So we'll use the drop down and select the IP address for the vCenter server

109
05:06.220 --> 05:07.000
right there.

110
05:07.000 --> 05:10.590
And then for the credentials, we only have one set of credentials for that v

111
05:10.590 --> 05:11.000
Center.

112
05:11.000 --> 05:13.000
And that's this credential set right here.

113
05:13.000 --> 05:15.000
So we'll select that and click on connect.

114
05:15.000 --> 05:18.700
Now we're also going to know here in a moment if that was successful because if

115
05:18.700 --> 05:22.000
it is, we'll use the drop down right here under content library.

116
05:22.000 --> 05:26.000
We should also be able to see the existing content libraries in this vCenter.

117
05:26.000 --> 05:27.000
So we only have one.

118
05:27.000 --> 05:29.000
So when we just made in the previous video.

119
05:29.000 --> 05:31.000
So from the drop down, there it is.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
05:29.000 --> 05:31.000
So from the drop down, there it is.

120
05:31.000 --> 05:32.000
All right, that's great news.

121
05:32.000 --> 05:36.610
That means we are communicating between this controller right here and not only

122
05:36.610 --> 05:40.100
the NSX that we saw earlier by selecting the various segments, but also now we

123
05:40.100 --> 05:44.020
're connected to and working with our vCenter because we can see our content

124
05:44.020 --> 05:45.000
library right there.

125
05:45.000 --> 05:46.000
Fantastic.

126
05:46.000 --> 05:49.610
So we'll click on done and let's just make sure we have supplied all the

127
05:49.610 --> 05:53.000
required information wherever there's an asterisk in red.

128
05:53.000 --> 05:54.000
So we'll scroll down.

129
05:54.000 --> 05:55.000
We need a prefix name.

130
05:55.000 --> 05:59.000
Let's go ahead and use a prefix name of our NSX lab.

131
05:59.000 --> 06:03.010
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

131
05:59.000 --> 06:03.010
And that way as part of this NSX cloud as service engines are being deployed,

132
06:03.010 --> 06:06.000
the VMs will have this as a prefix.

133
06:06.000 --> 06:09.130
And that way as those VMs show up in vSphere, it'll be very easy to identify

134
06:09.130 --> 06:12.000
them because they'll have this prefix associated with them.

135
06:12.000 --> 06:13.000
So let's scroll down.

136
06:13.000 --> 06:15.000
We have our NSX credentials.

137
06:15.000 --> 06:18.990
We have our management network, which is right over here, segment 103 off of

138
06:18.990 --> 06:20.000
the tier right gateway.

139
06:20.000 --> 06:23.760
The actual data plane network for the load balancing function for the service

140
06:23.760 --> 06:27.300
engines is going to be this transport zone and then specifically off that

141
06:27.300 --> 06:28.000
gateway.

142
06:28.000 --> 06:29.000
This segment.

143
06:29.000 --> 06:30.000
So that looks good.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
06:30.000 --> 06:33.920
And for the vCenter we're connected to and going to be working with this v

145
06:33.920 --> 06:35.000
Center.35.

146
06:35.000 --> 06:39.330
And then here for IP address management and DNS, I'm going to go ahead and

147
06:39.330 --> 06:41.000
leave those profiles off.

148
06:41.000 --> 06:43.000
So I believe we've identified everything that's required.

149
06:43.000 --> 06:47.000
So we'll click on save right here and give that a moment.

150
06:47.000 --> 06:50.990
So the default cloud has a nice green icon here and for our new cloud that just

151
06:50.990 --> 06:52.000
went to green.

152
06:52.000 --> 06:53.000
That's a very good sign.

153
06:53.000 --> 06:58.000
So if we go down here under cloud resources and we click on service engine.

154
06:58.000 --> 07:01.030
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

154
06:58.000 --> 07:01.030
So currently it's showing us for the default cloud, any service engines that

155
07:01.030 --> 07:02.000
have been deployed.

156
07:02.000 --> 07:08.000
And if he's the drop down and choose our NSX cloud also zero service engines.

157
07:08.000 --> 07:11.110
And the reason for that is that the controller is not going to deploy any

158
07:11.110 --> 07:13.000
service engines until another reason to.

159
07:13.000 --> 07:17.620
So until we create a logical virtual service and a virtual IP address with some

160
07:17.620 --> 07:19.000
service behind it.

161
07:19.000 --> 07:23.760
That's not really a reason for the controller to deploy any service engines

162
07:23.760 --> 07:24.000
anywhere.

163
07:24.000 --> 07:28.720
Because currently we don't have any need for a data plane for the load balancer

164
07:28.720 --> 07:29.000
.

165
07:29.000 --> 07:34.000
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

165
07:29.000 --> 07:34.000
But that will change once we create a virtual service with a virtual IP address

166
07:34.000 --> 07:36.000
and then put in some servers behind the scenes.

167
07:36.000 --> 07:40.760
That the actual service engine can then use as it load balances traffic coming

168
07:40.760 --> 07:43.000
in to the virtual IP address.

169
07:43.000 --> 07:46.000
And then the back end proxying it to one of the available servers.

170
07:46.000 --> 07:54.720
[BLANK_AUDIO]