WEBVTT 1 00:00.000 --> 00:03.800 All right, so our game plan is to implement this. 2 00:03.800 --> 00:06.520 And specifically, the controller is already here. 3 00:06.520 --> 00:08.880 We're currently logged on to the controller interface, 4 00:08.880 --> 00:10.480 as we're seeing here on the screen. 5 00:10.480 --> 00:13.800 And we want the management network for the SEs, 6 00:13.800 --> 00:16.880 for the service engines to be here on VLAN6. 7 00:16.880 --> 00:19.160 And because DHCP services are already present, 8 00:19.160 --> 00:21.920 we can allow them just to get an IP address via DHCP. 9 00:21.920 --> 00:23.600 So that'll be the management network. 10 00:23.600 --> 00:25.480 And then as far as the data plane, 11 00:25.480 --> 00:28.160 for the services engines to do the proxying for, 12 00:28.160 --> 00:31.160 we are also going to go ahead and include VLAN5. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:28.160 --> 00:31.160 we are also going to go ahead and include VLAN5. 13 00:31.160 --> 00:33.120 Because as part of creating the cloud connector, 14 00:33.120 --> 00:34.520 it's going to ask us, what do you want to use 15 00:34.520 --> 00:35.520 for a management network? 16 00:35.520 --> 00:37.520 We're going to say down here, VLAN6. 17 00:37.520 --> 00:40.320 And what do you want to use for the actual data plane? 18 00:40.320 --> 00:41.960 And for that, we're going to use VLAN5. 19 00:41.960 --> 00:42.760 In fact, you know what? 20 00:42.760 --> 00:46.120 Also, because we need to also include over here, 21 00:46.120 --> 00:50.320 the 192.168.1 network, and also the 23.1.2 network. 22 00:50.320 --> 00:51.760 As part of the creation of that cloud, 23 00:51.760 --> 00:55.520 we should also include that segment and this segment as well. 24 00:55.520 --> 00:58.080 Because if we don't, we'll have to go back and add those later. 25 00:58.080 --> 01:00.360 So with that in mind, let's start the process. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 00:58.080 --> 01:00.360 So with that in mind, let's start the process. 26 01:00.360 --> 01:03.520 So to do that here at the interface for the controller, 27 01:03.520 --> 01:05.240 we're going to click on infrastructure. 28 01:05.240 --> 01:07.680 And on the left, we're going to click on clouds. 29 01:07.680 --> 01:09.400 And from here, we have our default cloud. 30 01:09.400 --> 01:11.640 What we're going to do is create a new cloud. 31 01:11.640 --> 01:14.760 So we'll go ahead and click on the create button 32 01:14.760 --> 01:15.920 from the dropdown. 33 01:15.920 --> 01:18.280 We want a cloud connector to our NSX environment. 34 01:18.280 --> 01:20.400 So we'll choose NSX cloud. 35 01:20.400 --> 01:22.240 And then we'll start answering the questions. 36 01:22.240 --> 01:25.080 So let's call this NSX-cloud-4. 37 01:25.080 --> 01:28.240 Based on our plan, we'll be using some DHCP services 38 01:28.240 --> 01:31.320 for the addressing of our service engines down here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:28.240 --> 01:31.320 for the addressing of our service engines down here. 39 01:31.320 --> 01:33.920 Let's scroll down for the prefix name. 40 01:33.920 --> 01:36.040 This is going to be used when those service engines are 41 01:36.040 --> 01:37.440 created in vSphere. 42 01:37.440 --> 01:40.400 It'll have the prefix stuck in front of each of the service 43 01:40.400 --> 01:41.040 engines. 44 01:41.040 --> 01:42.840 And that way, if you have multiple clouds that are being 45 01:42.840 --> 01:46.560 created, you can identify based on the prefix, which clouds 46 01:46.560 --> 01:48.400 those service engines are associated with. 47 01:48.400 --> 01:50.800 So I'm going to call this NSX-4- prefix. 48 01:50.800 --> 01:53.360 And that way, when you see this and it has the word prefix in it, 49 01:53.360 --> 01:54.840 you'll say, oh, that's where it came from. 50 01:54.840 --> 01:57.960 And as we scroll down, let's go ahead and set the credentials 51 01:57.960 --> 02:00.240 we can log into the NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 01:57.960 --> 02:00.240 we can log into the NSX manager. 52 02:00.240 --> 02:03.000 So we'll go ahead and click on change credentials. 53 02:03.000 --> 02:06.440 We'll put in the IP address of our NSX manager, which is .21, 54 02:06.440 --> 02:07.440 right over here. 55 02:07.440 --> 02:11.120 So we'll put that in 192.168.1.21. 56 02:11.120 --> 02:12.440 And then we'll use the dropdown. 57 02:12.440 --> 02:14.800 And we'll choose the credentials we had set up 58 02:14.800 --> 02:16.720 from our previous set of videos, which basically 59 02:16.720 --> 02:19.560 has a username and the password we can use to log on 60 02:19.560 --> 02:21.160 to the NSX manager. 61 02:21.160 --> 02:23.160 Now, we'll know very quickly if that worked or not, 62 02:23.160 --> 02:25.120 meaning we had the right IP address. 63 02:25.120 --> 02:26.760 And we used the right username and password, 64 02:26.760 --> 02:29.960 because if it worked, we should be able to continue down here 65 02:29.960 --> 02:31.280 for the management network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 02:29.960 --> 02:31.280 for the management network. 66 02:31.280 --> 02:35.240 And it should show us everything that the NSX manager knows 67 02:35.240 --> 02:35.760 about. 68 02:35.760 --> 02:39.000 So for the NSX manager, if we use the dropdown here, 69 02:39.000 --> 02:40.280 that's a very good sign. 70 02:40.280 --> 02:43.680 So it's showing us all of the transport zones 71 02:43.680 --> 02:45.120 on the NSX manager. 72 02:45.120 --> 02:47.280 So for the management network, because we want to go ahead 73 02:47.280 --> 02:49.880 and make the management network over here, a VLAN back 74 02:49.880 --> 02:52.680 segment, we're going to go ahead for the management network. 75 02:52.680 --> 02:56.040 And we're going to choose a VLAN-backed transport zone. 76 02:56.040 --> 02:59.360 So I want to use the lab 3-RED VLAN-TZ, which 77 02:59.360 --> 03:01.320 is a VLAN-backed transport zone. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 02:59.360 --> 03:01.320 is a VLAN-backed transport zone. 78 03:01.320 --> 03:02.800 And now that we've selected that, 79 03:02.800 --> 03:05.360 it should be showing us all of the VLAN-backed segments 80 03:05.360 --> 03:07.680 available in the NSX manager. 81 03:07.680 --> 03:08.600 And here they are. 82 03:08.600 --> 03:10.800 So we have external 192. 83 03:10.800 --> 03:12.480 Nope, we want to put them over here on 6. 84 03:12.480 --> 03:14.320 So we want external VLAN 6. 85 03:14.320 --> 03:16.520 So we'll choose that correct external segment 86 03:16.520 --> 03:18.120 and continue scrolling down. 87 03:18.120 --> 03:20.560 So this part right here is for the management network. 88 03:20.560 --> 03:23.600 That's the communication path between the controller 89 03:23.600 --> 03:25.160 and the service engines. 90 03:25.160 --> 03:28.440 And then the next part is asking us about the data plane, 91 03:28.440 --> 03:30.520 what we're going to be doing load balancing force. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:28.440 --> 03:30.520 what we're going to be doing load balancing force. 92 03:30.520 --> 03:32.320 So for the data networks, we're going to go ahead 93 03:32.320 --> 03:33.840 and select a transport zone. 94 03:33.840 --> 03:37.760 And because our data plane here is going to be using VLANs, 95 03:37.760 --> 03:40.880 we're going to go ahead and choose a VLAN-backed transport 96 03:40.880 --> 03:43.920 zone that are edge nodes and our hosts are supporting. 97 03:43.920 --> 03:45.680 So here for the transport zone, we're 98 03:45.680 --> 03:49.240 going to go ahead and use the lab 3-RED VLAN-TZ once again. 99 03:49.240 --> 03:51.760 Then we will click here on the drop down for segments. 100 03:51.760 --> 03:54.080 It'll show us all the VLAN-backed segments. 101 03:54.080 --> 03:56.960 And that's because we chose a VLAN-backed transport zone. 102 03:56.960 --> 03:58.840 So let's start off with VLAN-5. 103 03:58.840 --> 03:59.960 So we'll select that. 104 03:59.960 --> 04:03.680 And I also want to add to that VLAN-23. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 03:59.960 --> 04:03.680 And I also want to add to that VLAN-23. 105 04:03.680 --> 04:07.240 So we'll go ahead and that's the interface right there, 106 04:07.240 --> 04:08.440 off of the T0 gateway. 107 04:08.440 --> 04:09.440 Fantastic. 108 04:09.440 --> 04:12.880 I also want to include this segment over here, the 192.168.1, 109 04:12.880 --> 04:14.600 because we're going to have a virtual IP address over there 110 04:14.600 --> 04:15.400 as well. 111 04:15.400 --> 04:18.240 So we'll go ahead and grab that as well. 112 04:18.240 --> 04:19.440 And let's see if that covers it. 113 04:19.440 --> 04:23.160 So as far as the data plane is concerned, here, up here, 114 04:23.160 --> 04:25.080 and over here, fantastic. 115 04:25.080 --> 04:26.920 So just be aware that for the management network 116 04:26.920 --> 04:30.120 for our service engines, we could have that on overlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 04:26.920 --> 04:30.120 for our service engines, we could have that on overlay 117 04:30.120 --> 04:32.840 transport zone or a VLAN-backed transport zone. 118 04:32.840 --> 04:34.520 And then for the data plane, we also 119 04:34.520 --> 04:35.680 have those same options-- 120 04:35.680 --> 04:39.080 an overlay transport zone or a VLAN-backed transport zone 121 04:39.080 --> 04:40.400 or we could mix and match. 122 04:40.400 --> 04:43.720 So we could have our management on overlay transport zones 123 04:43.720 --> 04:46.600 and our data networks on VLAN-backed transport zones. 124 04:46.600 --> 04:48.280 It boils down to a couple of decisions, 125 04:48.280 --> 04:50.920 including the choice of where you want to have your service 126 04:50.920 --> 04:52.920 engines and also maybe you already 127 04:52.920 --> 04:55.000 have your existing servers on a VLAN. 128 04:55.000 --> 04:58.240 So for the data plane, we'd want to go ahead and specify 129 04:58.240 --> 05:01.120 VLAN-backed because the servers are already in that VLAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 129 04:58.240 --> 05:01.120 VLAN-backed because the servers are already in that VLAN. 130 05:01.120 --> 05:03.360 But again, you can mix and match based on your needs. 131 05:03.360 --> 05:04.880 So with the management network in place 132 05:04.880 --> 05:06.440 and also the data networks in place, 133 05:06.440 --> 05:09.520 let's go ahead and scroll down and let's go ahead and tell 134 05:09.520 --> 05:12.080 the controller about our vCenter. 135 05:12.080 --> 05:14.480 So we'll click here on add for the vCenter. 136 05:14.480 --> 05:16.920 We'll call this our VCSA. 137 05:16.920 --> 05:18.240 And the reason that the controller 138 05:18.240 --> 05:20.520 needs to know about the vCenter is because as it 139 05:20.520 --> 05:22.960 starts to deploy the service engines, 140 05:22.960 --> 05:26.280 it needs to use the vCenter services to do that. 141 05:26.280 --> 05:28.600 So it's a combined effort with the controller 142 05:28.600 --> 05:31.880 using vCenter for the deployment of the actual VMs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 05:28.600 --> 05:31.880 using vCenter for the deployment of the actual VMs, 143 05:31.880 --> 05:33.520 aka the service engines. 144 05:33.520 --> 05:36.880 So we'll specify how the controller can log in to the vCenter. 145 05:36.880 --> 05:38.200 So we'll use the dropdown here. 146 05:38.200 --> 05:41.800 Now, because we already told the controller about the NSX 147 05:41.800 --> 05:45.520 manager and because the NSX manager is using this vCenter, 148 05:45.520 --> 05:47.800 that's why it's already showing up here in the list. 149 05:47.800 --> 05:49.960 And then from the dropdown for the credentials, 150 05:49.960 --> 05:52.400 we'll use the credentials that we had set up previously. 151 05:52.400 --> 05:55.720 So these credentials have the username and the password 152 05:55.720 --> 05:58.680 appropriate to log on to that vCenter at .35. 153 05:58.680 --> 06:00.600 So with that done, we'll click on connect. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 153 05:58.680 --> 06:00.600 So with that done, we'll click on connect. 154 06:00.600 --> 06:03.440 So if that was successful, as far as the connection there, 155 06:03.440 --> 06:06.080 now if we click on the content library, 156 06:06.080 --> 06:07.920 it should show us all the content libraries that 157 06:07.920 --> 06:09.840 are available through that vCenter. 158 06:09.840 --> 06:10.960 So that's a very good sign. 159 06:10.960 --> 06:12.880 We'll choose that content library. 160 06:12.880 --> 06:14.440 And we'll click on done. 161 06:14.440 --> 06:15.920 And let's check our work. 162 06:15.920 --> 06:17.840 So here's the name of our cloud. 163 06:17.840 --> 06:20.840 We're going to use DHCP services for the assignment of IP addresses 164 06:20.840 --> 06:22.520 for our service engines. 165 06:22.520 --> 06:24.200 As we scroll down, here's the credentials 166 06:24.200 --> 06:26.200 to log on to the NSX manager. 167 06:26.200 --> 06:28.080 And then we specified for the management network 168 06:28.080 --> 06:30.520 that we want to use VLAN6 for our service engines. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 168 06:28.080 --> 06:30.520 that we want to use VLAN6 for our service engines. 169 06:30.520 --> 06:32.440 And then for the data playing, the actual load balancing 170 06:32.440 --> 06:35.440 services that the service engines are going to do. 171 06:35.440 --> 06:37.440 We're using a VLAN back transport zone. 172 06:37.440 --> 06:40.040 And then we specified the three VLANs that are going to be 173 06:40.040 --> 06:42.160 involved, one where the servers are, 174 06:42.160 --> 06:44.120 and one up here where a VIP is going to be, 175 06:44.120 --> 06:46.360 and one over here where a VIP is going to be. 176 06:46.360 --> 06:48.960 And then we added the information about the vCenter as well. 177 06:48.960 --> 06:52.400 And we could also add IP address management and DNS profiles. 178 06:52.400 --> 06:54.040 But for the demo, I'm not going to include that. 179 06:54.040 --> 06:55.680 So I'll click on save. 180 06:55.680 --> 07:00.360 And boom, we now have a new cloud called NSX Cloud 4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 180 06:55.680 --> 07:00.360 And boom, we now have a new cloud called NSX Cloud 4. 181 07:00.360 --> 07:03.520 And here in just a moment or two, it should be green. 182 07:03.520 --> 07:07.200 Now, until it goes green, if we go down here to cloud resources 183 07:07.200 --> 07:09.960 and we click on networks, and then from the drop down here, 184 07:09.960 --> 07:12.160 we select NSX Cloud 4. 185 07:12.160 --> 07:14.480 Oh, it must have just finished. 186 07:14.480 --> 07:18.440 Because these won't be populated yet until that cloud 187 07:18.440 --> 07:20.280 connector is all set up and ready to go. 188 07:20.280 --> 07:23.920 So if we go back to clouds here for the NSX Cloud, 189 07:23.920 --> 07:24.680 here is now green. 190 07:24.680 --> 07:26.440 So if you went down to cloud resources 191 07:26.440 --> 07:28.200 and you didn't see your networks yet, 192 07:28.200 --> 07:30.240 just give that a few more moments to complete. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 192 07:28.200 --> 07:30.240 just give that a few more moments to complete. 193 07:30.240 --> 07:32.280 So now that that cloud connector is done, 194 07:32.280 --> 07:34.960 let's also just for a moment go down to cloud resources, 195 07:34.960 --> 07:36.000 go to networks. 196 07:36.000 --> 07:38.880 I'm also going to specify for our cloud. 197 07:38.880 --> 07:40.240 And for the networks there, I'm going 198 07:40.240 --> 07:44.040 to specify the actual subnet ranges for each of these. 199 07:44.040 --> 07:45.280 And that's going to be useful later 200 07:45.280 --> 07:47.840 when we start configuring our virtual IP addresses 201 07:47.840 --> 07:49.800 and specifying where we want them to live 202 07:49.800 --> 07:51.760 and also specifying where our servers are. 203 07:51.760 --> 07:54.160 So for the external net 192, I'm going 204 07:54.160 --> 07:55.920 to click on the little pencil here. 205 07:55.920 --> 07:58.240 And then for subnets, I'm going to click on add. 206 07:58.240 --> 08:00.240 And just going to identify a subnet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 07:58.240 --> 08:00.240 And just going to identify a subnet. 207 08:00.240 --> 08:04.600 So we'll go ahead and say it's 192.168.1.0 with a 24-bit 208 08:04.600 --> 08:07.200 mask, and then scroll down and click on save. 209 08:07.200 --> 08:08.760 Because we're using static IP dressing, 210 08:08.760 --> 08:10.320 I don't even need to set up a pool. 211 08:10.320 --> 08:12.000 And then we'll click on save again. 212 08:12.000 --> 08:13.880 So now if we refer to this external network, 213 08:13.880 --> 08:16.720 it has a clue about what the actual subnet ranges. 214 08:16.720 --> 08:19.280 And I'm going to repeat that process for each of the subnets. 215 08:19.280 --> 08:21.800 So here for external VLAN 23, we'll 216 08:21.800 --> 08:23.440 click on the pencil to edit it. 217 08:23.440 --> 08:25.720 For subnets, we'll click on add. 218 08:25.720 --> 08:28.720 And then for the subnet, for that, it's 23.1.2.0 219 08:28.720 --> 08:30.000 with a 24-bit mask. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 220 08:30.000 --> 08:31.120 Click on save. 221 08:31.120 --> 08:32.400 Click on save again. 222 08:32.400 --> 08:34.200 Now it knows about both of those. 223 08:34.200 --> 08:37.160 Then I'll repeat that process for external VLAN 5 224 08:37.160 --> 08:40.080 with the address base of 10.50 with the 24-bit mask, 225 08:40.080 --> 08:43.280 and also for VLAN 6 with a 10.60. 226 08:43.280 --> 08:45.320 Although for VLAN 6, I may not need the range, 227 08:45.320 --> 08:47.240 because we're only supporting our SEs there. 228 08:47.240 --> 08:49.120 And there's DHCP services already present. 229 08:49.120 --> 08:50.760 But just to make it nice and consistent, 230 08:50.760 --> 08:52.120 I'm going to add those as well. 231 08:52.120 --> 08:54.320 So for VLAN 5, we'll click on the pencil. 232 08:54.320 --> 08:56.840 We'll click right here on add for subnets. 233 08:56.840 --> 09:00.680 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 233 08:56.840 --> 09:00.680 And then we'll put in the prefix of 10.5.0.0 with a 24-bit 234 09:00.680 --> 09:01.240 mask. 235 09:01.240 --> 09:02.280 And click on save. 236 09:02.280 --> 09:03.360 And click on save. 237 09:03.360 --> 09:05.520 And then repeat that one more time for VLAN 6 238 09:05.520 --> 09:07.040 in the address base that we're using there. 239 09:07.040 --> 09:08.200 So we'll click on the pencil. 240 09:08.200 --> 09:09.040 We're going to the subnets. 241 09:09.040 --> 09:10.280 We'll click on add. 242 09:10.280 --> 09:14.120 And then we'll put in the subnet 10.6.0 with a 24-bit mask. 243 09:14.120 --> 09:16.480 And then we'll click on save and save. 244 09:16.480 --> 09:18.120 So now that we have this cloud created, 245 09:18.120 --> 09:19.200 we have a couple problems. 246 09:19.200 --> 09:21.360 Number one is if we click here on service engines 247 09:21.360 --> 09:25.000 and then select our cloud, we have no service engines deployed. 248 09:25.000 --> 09:27.600 We also don't have any virtual services. 249 09:27.600 --> 09:30.000 So by default, the controller is not WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 250 09:30.000 --> 09:33.160 deploying any service engines until it has a reason to. 251 09:33.160 --> 09:34.840 And one of the reasons it would is 252 09:34.840 --> 09:38.000 if we start creating at least one virtual service 253 09:38.000 --> 09:40.120 with an associated virtual IP address, 254 09:40.120 --> 09:41.920 pointing back to a pool of servers. 255 09:41.920 --> 09:44.960 So it'll have a reason to actually deploy a service engine. 256 09:44.960 --> 09:49.360 So even though we don't yet have any service engines created 257 09:49.360 --> 09:51.480 in the background, let me also point out 258 09:51.480 --> 09:53.360 what the controller did. 259 09:53.360 --> 09:56.680 It placed in the content library the template 260 09:56.680 --> 10:00.640 that it can use if it does need to deploy a service engine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 260 09:56.680 --> 10:00.640 that it can use if it does need to deploy a service engine. 261 10:00.640 --> 10:03.240 So if we pop over to the vSphere client for a moment 262 10:03.240 --> 10:05.000 and we go to the content library, 263 10:05.000 --> 10:07.840 so use the hamburger menu there, click on content libraries, 264 10:07.840 --> 10:10.200 we'll go to our content library and check it out. 265 10:10.200 --> 10:13.280 There is one template there and that's the image, 266 10:13.280 --> 10:15.520 it's about four gig, that's the image 267 10:15.520 --> 10:17.080 that the controller is gonna use 268 10:17.080 --> 10:19.760 when it needs to deploy one of its service engines. 269 10:19.760 --> 10:21.920 And again, the process that's gonna kick that off 270 10:21.920 --> 10:26.520 is we need to have at least one virtual service configured. 271 10:26.520 --> 10:28.440 And once we do that, the controller will then use 272 10:28.440 --> 10:31.240 this template in this library to start deploying WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 272 10:28.440 --> 10:31.240 this template in this library to start deploying 273 10:31.240 --> 10:33.400 one or more service engines. 274 10:33.400 --> 10:34.640 So join me in the next videos, 275 10:34.640 --> 10:37.600 we take that next step in creating a virtual service 276 10:37.600 --> 10:39.320 inside the advanced load balancer. 277 10:39.320 --> 10:41.880 So I'll see you in the next video in just a moment.