WEBVTT 1 00:00.000 --> 00:04.280 Now, one of the challenges with the NSX application platform in deploying it is 2 00:04.280 --> 00:04.520 that there's 3 00:04.520 --> 00:08.560 so many components involved in getting it up and working. 4 00:08.560 --> 00:12.970 And that's the benefit of using the automation feature to implement the NSX 5 00:12.970 --> 00:14.280 application platform, 6 00:14.280 --> 00:18.110 including the Kubernetes cluster that it's going to be using for its 7 00:18.110 --> 00:19.000 functionality. 8 00:19.000 --> 00:22.840 So to really appreciate this automation component, let's take a look at what 9 00:22.840 --> 00:23.940 the automation brings 10 00:23.940 --> 00:25.080 to the table. 11 00:25.080 --> 00:28.670 And to assist with that, let's bring out the documentation for the application 12 00:28.670 --> 00:29.200 platform 13 00:29.200 --> 00:32.520 automation guide, which is what we want to focus on right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.200 --> 00:32.520 automation guide, which is what we want to focus on right here. 14 00:32.520 --> 00:37.040 So in the big picture, the automation regarding the implementation of the NSX 15 00:37.040 --> 00:38.520 application platform 16 00:38.520 --> 00:44.960 is going to be performed by coordination between the NSX manager and a special 17 00:44.960 --> 00:46.040 VM that's used 18 00:46.040 --> 00:50.000 to automate the process of deploying the NSX application platform. 19 00:50.000 --> 00:54.110 And that's what this VMware NSX application platform automation guide is all 20 00:54.110 --> 00:54.720 about. 21 00:54.720 --> 00:57.870 So if we scroll down a little bit, unless you're in the outline that section 22 00:57.870 --> 00:58.240 six is 23 00:58.240 --> 01:01.680 all about troubleshooting in the event, something doesn't go well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:58.240 --> 01:01.680 all about troubleshooting in the event, something doesn't go well. 24 01:01.680 --> 01:06.130 Now I also want to tell you from experience that what cannot go well would be 25 01:06.130 --> 01:07.160 the underlying 26 01:07.160 --> 01:12.120 infrastructure, including if DNS isn't working or internet connectivity isn't 27 01:12.120 --> 01:12.840 working or 28 01:12.840 --> 01:17.050 reachability between our subnets that are being used by the Kubernetes and as a 29 01:17.050 --> 01:17.680 result, 30 01:17.680 --> 01:19.640 the NSX application platform. 31 01:19.640 --> 01:23.460 I've also experienced the situation where if you're implementing the NSX 32 01:23.460 --> 01:24.760 application platform 33 01:24.760 --> 01:30.440 on top of an NSX implemented network that also often causes problems as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:24.760 --> 01:30.440 on top of an NSX implemented network that also often causes problems as well. 34 01:30.440 --> 01:34.240 And that's why in the previous skill, we took a look at how to implement on 35 01:34.240 --> 01:35.040 real VLANs 36 01:35.040 --> 01:40.200 and real switches and real routers, the infrastructure in a conjunction between 37 01:40.200 --> 01:41.840 our hardware platforms 38 01:41.840 --> 01:46.090 and vSphere as the network infrastructure that we were using for the NSX 39 01:46.090 --> 01:47.920 application platform. 40 01:47.920 --> 01:51.520 So if you have not yet seen that previous set of videos and that previous skill 41 01:51.520 --> 01:52.080 on preparing 42 01:52.080 --> 01:55.920 the network, I would strongly encourage you to take a look at that first. 43 01:55.920 --> 01:58.930 Because most of the issues and problems are going to come up right here are 44 01:58.930 --> 01:59.280 going to be 45 01:59.280 --> 02:03.040 tied to an infrastructure that's not correctly set up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:59.280 --> 02:03.040 tied to an infrastructure that's not correctly set up. 46 02:03.040 --> 02:07.180 So as we continue to scroll down, let's take a big picture look at what the NSX 47 02:07.180 --> 02:07.920 automation 48 02:07.920 --> 02:09.280 is going to do for us. 49 02:09.280 --> 02:12.420 And in another shell here, the two stages that the automation is going to bring 50 02:12.420 --> 02:12.800 to the 51 02:12.800 --> 02:16.680 table for us and getting the NSX application platform up and running. 52 02:16.680 --> 02:20.360 And again, behind the scenes, we're going to be using this NSX automation 53 02:20.360 --> 02:20.880 appliance, 54 02:20.880 --> 02:24.160 a little VM to do most of that heavy lifting for us. 55 02:24.160 --> 02:28.780 So in the big picture, the automation appliance working in conjunction with the 56 02:28.780 --> 02:29.560 NSX manager 57 02:29.560 --> 02:34.040 and our existing vSphere environment is going to do two big stages. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:29.560 --> 02:34.040 and our existing vSphere environment is going to do two big stages. 58 02:34.040 --> 02:35.040 And they are major. 59 02:35.040 --> 02:37.040 The first one here is going to do Pre-JEX. 60 02:37.040 --> 02:41.200 It's going to be a content library that's needed for the images as part of the 61 02:41.200 --> 02:42.160 Kubernetes. 62 02:42.160 --> 02:45.860 It'll deploy a load balancer that's being used as part of the Kubernetes 63 02:45.860 --> 02:46.600 cluster. 64 02:46.600 --> 02:49.800 It'll manage the certificates working in conjunction with vCenter. 65 02:49.800 --> 02:52.240 It'll enable TKGs on the vSphere cluster. 66 02:52.240 --> 02:55.600 So TKGs is the Tanzu Kubernetes grid. 67 02:55.600 --> 02:59.800 Think of that like VMware's method of implementing a Kubernetes cluster. 68 02:59.800 --> 03:02.680 It's going to create the VMs and storage classes associated with that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 02:59.800 --> 03:02.680 It's going to create the VMs and storage classes associated with that. 69 03:02.680 --> 03:06.390 And it'll do some of the prep work in preparation for the NSX application 70 03:06.390 --> 03:07.160 appliance. 71 03:07.160 --> 03:11.460 And it'll also do some other prep work in preparation for the NSX application 72 03:11.460 --> 03:12.320 platform. 73 03:12.320 --> 03:15.490 So this first part here, this first phase is all about getting the Kubernetes 74 03:15.490 --> 03:16.040 side set 75 03:16.040 --> 03:17.080 up and ready. 76 03:17.080 --> 03:20.750 So after stage one is done, stage two, along with some additional prep work 77 03:20.750 --> 03:21.440 here, the bottom 78 03:21.440 --> 03:25.600 line is going to go ahead and deploy the NSX application platform on top of 79 03:25.600 --> 03:26.400 that Kubernetes 80 03:26.400 --> 03:27.640 infrastructure. 81 03:27.640 --> 03:30.720 And as I mentioned earlier, there's a lot that can go wrong. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 81 03:27.640 --> 03:30.720 And as I mentioned earlier, there's a lot that can go wrong. 82 03:30.720 --> 03:34.240 But if you have the network infrastructure in place first, including DNS 83 03:34.240 --> 03:35.000 resolution, 84 03:35.000 --> 03:38.980 time synchronization, routing between all the subnets, and also having a really 85 03:38.980 --> 03:39.280 good 86 03:39.280 --> 03:42.520 plan about what IP dressing scheme you're going to use. 87 03:42.520 --> 03:45.990 Having that correct infrastructure is going to prevent most of the common 88 03:45.990 --> 03:46.720 problems that 89 03:46.720 --> 03:50.340 stop people cold when they're trying to use the automation component in 90 03:50.340 --> 03:51.960 deploying NAP. 91 03:51.960 --> 03:56.530 So as we scroll down through this document, let's go ahead and take a look at a 92 03:56.530 --> 03:57.200 diagram. 93 03:57.200 --> 04:01.230 And I love how it says general requirements because all the nitty gritty WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 03:57.200 --> 04:01.230 And I love how it says general requirements because all the nitty gritty 94 04:01.230 --> 04:02.000 details are 95 04:02.000 --> 04:05.520 actually in the documentation for NAP itself. 96 04:05.520 --> 04:08.970 And this document is specifically aimed at assisting individuals who want to 97 04:08.970 --> 04:09.920 use the automation 98 04:09.920 --> 04:14.440 and getting the NAP deployed, including the Kubernetes cluster setup. 99 04:14.440 --> 04:15.960 So here are some of the critical components. 100 04:15.960 --> 04:19.640 You'll notice here that this represents a router. 101 04:19.640 --> 04:23.080 And in the previous set of videos, we set up our infrastructure. 102 04:23.080 --> 04:26.280 And I have this as my top of rack switch, which is a multi layer switch 103 04:26.280 --> 04:27.080 providing the 104 04:27.080 --> 04:28.640 routing between these three networks. 105 04:28.640 --> 04:31.920 So this network right here in green and the text here is really small. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 04:28.640 --> 04:31.920 So this network right here in green and the text here is really small. 106 04:31.920 --> 04:33.320 I'm going to tell you what these are. 107 04:33.320 --> 04:34.880 This is our management network. 108 04:34.880 --> 04:37.560 So we have our ESXI host connected here. 109 04:37.560 --> 04:40.120 We have our NSX manager connected here. 110 04:40.120 --> 04:42.200 We have our vCenter connected here. 111 04:42.200 --> 04:45.860 And this diagram, they have some fault tolerance with more than just one NSX 112 04:45.860 --> 04:46.960 manager as part 113 04:46.960 --> 04:48.800 of an NSX cluster. 114 04:48.800 --> 04:52.790 So in our topology, this is VLAN 11 that we set up in the previous set of 115 04:52.790 --> 04:53.440 videos. 116 04:53.440 --> 04:58.000 And the addressing space here is 10.11.11 with a slash 24. 117 04:58.000 --> 05:01.000 And then my top of rack switch has the IP address of dot one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 04:58.000 --> 05:01.000 And then my top of rack switch has the IP address of dot one. 118 05:01.000 --> 05:03.960 And we tested that connectivity in our previous sets of videos. 119 05:03.960 --> 05:07.200 So we have that VLAN already in place, ready to go. 120 05:07.200 --> 05:10.960 The next network is showing here is the workload network. 121 05:10.960 --> 05:14.320 So in our topology, that is VLAN 13. 122 05:14.320 --> 05:19.550 Using the IP address space there on VLAN 13 of 10 dot 13 dot 13 with a 24 bit 123 05:19.550 --> 05:20.120 mask and 124 05:20.120 --> 05:24.120 the default gateway is once again, my top of rack switch here at dot one. 125 05:24.120 --> 05:28.520 And then this network right here is the front end network, which in our top 126 05:28.520 --> 05:29.160 ology is VLAN 127 05:29.160 --> 05:33.640 12, which is using the IP addressing space of 10 dot 12 dot 12 dot zero with a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 05:29.160 --> 05:33.640 12, which is using the IP addressing space of 10 dot 12 dot 12 dot zero with a 128 05:33.640 --> 05:34.120 24 bit 129 05:34.120 --> 05:35.120 mask. 130 05:35.120 --> 05:38.000 And once again, my top of rack switch is at dot one. 131 05:38.000 --> 05:41.480 And as part of the automation, it's going to deploy for us a little HA proxy 132 05:41.480 --> 05:42.040 that's going 133 05:42.040 --> 05:44.800 to be used as part of our Kubernetes environment. 134 05:44.800 --> 05:47.740 And so one of the core components in making sure everything is going to work is 135 05:47.740 --> 05:48.080 having 136 05:48.080 --> 05:53.170 a really good plan regarding what IP addresses we're going to use and where and 137 05:53.170 --> 05:53.640 that way, 138 05:53.640 --> 05:56.900 if we're building on top of a already functioning network that we built in the 139 05:56.900 --> 05:57.560 previous set 140 05:57.560 --> 06:00.810 of videos, and then we have a good plan for IP addressing and then we implement WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 140 05:57.560 --> 06:00.810 of videos, and then we have a good plan for IP addressing and then we implement 141 06:00.810 --> 06:01.400 that plan 142 06:01.400 --> 06:05.120 as part of the automation, that's going to go a long way in avoiding most of 143 06:05.120 --> 06:05.800 the problems 144 06:05.800 --> 06:09.390 people are going to have when they implement nap using the automation tool, 145 06:09.390 --> 06:10.200 again, having 146 06:10.200 --> 06:14.160 the correct networks in place that are proven functional and then having a good 147 06:14.160 --> 06:14.640 plan for 148 06:14.640 --> 06:16.280 implementing all the rest. 149 06:16.280 --> 06:18.840 So having said that, let's take this idea here. 150 06:18.840 --> 06:21.850 We are in the network topology, including what we already did in the previous 151 06:21.850 --> 06:22.160 set of 152 06:22.160 --> 06:23.160 videos. 153 06:23.160 --> 06:25.000 And let's lay out a plan. 154 06:25.000 --> 06:29.360 So here is our existing topology, which we verified in the previous skill. 155 06:29.360 --> 06:32.530 And this is also the topology we're now going to be using for the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 155 06:29.360 --> 06:32.530 And this is also the topology we're now going to be using for the actual 156 06:32.530 --> 06:33.720 deployment of the 157 06:33.720 --> 06:38.080 NSX application platform using the automation appliance to do it. 158 06:38.080 --> 06:39.680 So let's confirm a few of our components. 159 06:39.680 --> 06:43.220 I've got DNS up here at 10 dot 10 dot 10 dot 100 and that's going to be 160 06:43.220 --> 06:44.280 important because 161 06:44.280 --> 06:48.330 we are going to need to add a couple specific fully qualified domain names that 162 06:48.330 --> 06:49.600 can be resolved 163 06:49.600 --> 06:52.720 by our Kubernetes and NSX environment. 164 06:52.720 --> 06:55.570 So the fact that we already verified that we're using this DNS server and that 165 06:55.570 --> 06:56.720 's functional, 166 06:56.720 --> 06:57.720 that's really important. 167 06:57.720 --> 07:00.550 Now a few other devices that we want to make sure we know what their IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 167 06:57.720 --> 07:00.550 Now a few other devices that we want to make sure we know what their IP 168 07:00.550 --> 07:01.600 addresses are, 169 07:01.600 --> 07:05.120 as well as their DNS names would be the vCenter. 170 07:05.120 --> 07:09.190 So I've got the vCenter sitting here on this network segment, the VLAN 11 171 07:09.190 --> 07:09.880 network, which 172 07:09.880 --> 07:15.660 is our management network in its IP address is dot 111 and is DNS resolvable 173 07:15.660 --> 07:16.280 name is 174 07:16.280 --> 07:24.800 V C S a dash VLAN dash 11 dot O G I T dot lab. 175 07:24.800 --> 07:28.810 And what I would recommend is that as you're planning out and implementing the 176 07:28.810 --> 07:29.640 NSX application 177 07:29.640 --> 07:33.200 platform using the automation VM, I would make sure that each of the components WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 177 07:29.640 --> 07:33.200 platform using the automation VM, I would make sure that each of the components 178 07:33.200 --> 07:33.520 we're 179 07:33.520 --> 07:39.680 using, including vCenter and the NSX manager, etc, are all correctly resolvable 180 07:39.680 --> 07:40.600 by our DNS 181 07:40.600 --> 07:41.600 server. 182 07:41.600 --> 07:44.210 And again, they're going to save you time and troubleshooting later in the 183 07:44.210 --> 07:44.680 event some 184 07:44.680 --> 07:46.360 of these names are not resolvable. 185 07:46.360 --> 07:49.640 So right now as we're documenting these elements, let me go ahead and also do a 186 07:49.640 --> 07:50.560 quick test just 187 07:50.560 --> 07:55.700 to verify that other devices on these network segments can do the resolution of 188 07:55.700 --> 07:56.440 this name 189 07:56.440 --> 07:58.920 to this IP address using our DNS server. 190 07:58.920 --> 08:02.210 And because we already have a little VM that we tested earlier in our previous WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 190 07:58.920 --> 08:02.210 And because we already have a little VM that we tested earlier in our previous 191 08:02.210 --> 08:02.600 video right 192 08:02.600 --> 08:06.090 here, let's go to that VM right now and just verify that we can do name 193 08:06.090 --> 08:07.520 resolution for this 194 08:07.520 --> 08:10.400 name to that IP address for our vCenter. 195 08:10.400 --> 08:11.720 So let me bring a little VM. 196 08:11.720 --> 08:17.640 So this VM represents this computer sitting on VLAN 12 right here. 197 08:17.640 --> 08:19.320 Let's confirm its IP address. 198 08:19.320 --> 08:22.590 So what the command line will do an IP address, we could also use IF config 199 08:22.590 --> 08:23.320 that would also 200 08:23.320 --> 08:24.320 work. 201 08:24.320 --> 08:29.220 The IP address is 10 dot 12 dot 12 dot three, and if you do a route dash and it 202 08:29.220 --> 08:30.040 'll confirm WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 202 08:29.220 --> 08:30.040 'll confirm 203 08:30.040 --> 08:33.240 that it's default gateway is 10 dot 12 dot 12 dot one. 204 08:33.240 --> 08:36.790 And let's also verify we can ping our DNS server up here at 10 dot 10 dot 10 205 08:36.790 --> 08:37.680 dot 100. 206 08:37.680 --> 08:41.960 So we'll do a ping to 10 dot 10 dot 10 dot 100. 207 08:41.960 --> 08:42.960 And that looks good. 208 08:42.960 --> 08:44.880 So we'll go ahead and stop that. 209 08:44.880 --> 08:45.880 And let's try name resolution. 210 08:45.880 --> 08:47.040 And let's do an NS look up. 211 08:47.040 --> 08:50.270 And there's a couple options here we could use an us look up or another tool 212 08:50.270 --> 08:50.840 that's doing 213 08:50.840 --> 08:52.800 DNS resolution for us. 214 08:52.800 --> 08:56.750 And I also created when I set up all these a records, I also set up reverse 215 08:56.750 --> 08:57.720 lookup records 216 08:57.720 --> 08:58.720 as well. 217 08:58.720 --> 09:01.840 And that's really convenient for verifying names and IP addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 217 08:58.720 --> 09:01.840 And that's really convenient for verifying names and IP addresses. 218 09:01.840 --> 09:06.790 So if we did an NS look up for 10 dot 11 dot 11 dot and we're looking for a 111 219 09:06.790 --> 09:07.600 1 and press 220 09:07.600 --> 09:08.600 enter. 221 09:08.600 --> 09:13.960 Here's coming back to the name for that which is VCS a dash VLAN dash 11 dot O 222 09:13.960 --> 09:14.920 GIT dot lab, 223 09:14.920 --> 09:16.400 which is absolutely correct. 224 09:16.400 --> 09:20.580 So one of the benefits of having reverse lookups enabled and reverse look up 225 09:20.580 --> 09:21.520 records is that 226 09:21.520 --> 09:26.510 we can actually verify names by plugging in the IP address with an NS look up 227 09:26.510 --> 09:27.160 instead 228 09:27.160 --> 09:29.040 of having to type out the full name. 229 09:29.040 --> 09:34.140 So as far as the name resolution for this network infrastructure for VCS a dash WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 229 09:29.040 --> 09:34.140 So as far as the name resolution for this network infrastructure for VCS a dash 230 09:34.140 --> 09:34.520 VLAN 231 09:34.520 --> 09:37.640 dash 11 dot O GIT dot lab, that looks great. 232 09:37.640 --> 09:39.360 So I move that out of the way. 233 09:39.360 --> 09:43.400 And another VM I have up here is the actual NSX manager. 234 09:43.400 --> 09:45.760 And that is at dot 121. 235 09:45.760 --> 09:47.120 And the DNS record I created for it. 236 09:47.120 --> 09:49.240 In fact, let me go ahead and clean this up just a little bit. 237 09:49.240 --> 09:54.520 So everything in this lab environment is in the DNS domain O GIT dot lab. 238 09:54.520 --> 10:00.520 So this NSX manager right here, his name is NSX manager NSX dash MGR to be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 238 09:54.520 --> 10:00.520 So this NSX manager right here, his name is NSX manager NSX dash MGR to be 239 10:00.520 --> 10:01.620 specific dash 240 10:01.620 --> 10:03.400 VLAN dash 11. 241 10:03.400 --> 10:07.000 And before we get too far along, let's go ahead and verify that in DNS as well. 242 10:07.000 --> 10:10.740 So we'll bring back our client and let's set the up arrow key and do a reverse 243 10:10.740 --> 10:11.240 look up 244 10:11.240 --> 10:16.970 for 10 dot 11 dot 11 dot one two one and press enter and just confirm that name 245 10:16.970 --> 10:17.800 as well. 246 10:17.800 --> 10:22.800 NSX dash manager dash VLAN dash 11 dot O GIT dot lab. 247 10:22.800 --> 10:23.800 Perfect. 248 10:23.800 --> 10:26.440 So one of the benefits of actually doing this from a VM inside of this 249 10:26.440 --> 10:27.400 infrastructure is 250 10:27.400 --> 10:32.640 just to verify in real terms that when other clients try to do DNS to this DNS WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 250 10:27.400 --> 10:32.640 just to verify in real terms that when other clients try to do DNS to this DNS 251 10:32.640 --> 10:33.400 server from 252 10:33.400 --> 10:36.710 these networks, it's going to have the same results who are verifying step by 253 10:36.710 --> 10:37.120 step as 254 10:37.120 --> 10:40.200 we go through that name resolution is working in a Zimplace. 255 10:40.200 --> 10:41.880 So let me minimize that. 256 10:41.880 --> 10:46.010 So now that we've verified the IP addresses and the DNS names associated with 257 10:46.010 --> 10:46.760 our vCenter 258 10:46.760 --> 10:50.660 and also with our NSX manager, let's continue taking a look at the automation 259 10:50.660 --> 10:51.280 guide for the 260 10:51.280 --> 10:53.240 NSX application platform. 261 10:53.240 --> 10:57.120 So as we continue to scroll down, here we have some of the requirements 262 10:57.120 --> 10:58.840 regarding connectivity. 263 10:58.840 --> 11:01.740 So from the front end network going to our Kubernetes, we need to make sure we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 263 10:58.840 --> 11:01.740 So from the front end network going to our Kubernetes, we need to make sure we 264 11:01.740 --> 11:02.760 're allowing 265 11:02.760 --> 11:06.690 these protocols and ports and then from the management network over to the DNS 266 11:06.690 --> 11:07.160 server 267 11:07.160 --> 11:10.320 that we're allowing these ports, which is simply DNS here. 268 11:10.320 --> 11:15.130 And here showing us in section three dot two is the protocols and ports needed 269 11:15.130 --> 11:15.800 between source 270 11:15.800 --> 11:16.800 and destination. 271 11:16.800 --> 11:20.190 So between the automation appliance and the front end network, we need to make 272 11:20.190 --> 11:20.600 sure we're 273 11:20.600 --> 11:25.040 allowing TCP on these two ports and between the automation appliance and the 274 11:25.040 --> 11:25.760 management 275 11:25.760 --> 11:27.480 network we need to allow these ports. 276 11:27.480 --> 11:29.080 This basically just DNS. 277 11:29.080 --> 11:32.720 Now in my topology, I also have DNS on a network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 277 11:29.080 --> 11:32.720 Now in my topology, I also have DNS on a network. 278 11:32.720 --> 11:37.760 So I want to make sure that I have access to DNS wherever it is from the nap 279 11:37.760 --> 11:38.720 automation 280 11:38.720 --> 11:39.720 appliance. 281 11:39.720 --> 11:43.170 We also should a game plan together regarding what IP address we want to use 282 11:43.170 --> 11:44.080 for that automation 283 11:44.080 --> 11:45.080 appliance. 284 11:45.080 --> 11:48.740 So what I propose we do for the actual automation VM itself that's going to 285 11:48.740 --> 11:49.720 orchestrate a lot 286 11:49.720 --> 11:54.670 of this work for us is let's go ahead and put that at dot six on the management 287 11:54.670 --> 11:55.240 network 288 11:55.240 --> 11:57.480 of 10 dot 11 dot 11. 289 11:57.480 --> 12:01.880 So that'll be the automation appliance address once we deploy that VM on our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 289 11:57.480 --> 12:01.880 So that'll be the automation appliance address once we deploy that VM on our 290 12:01.880 --> 12:02.600 network. 291 12:02.600 --> 12:06.100 In addition, we want to make sure that between this automation appliance and v 292 12:06.100 --> 12:06.760 Center that 293 12:06.760 --> 12:10.850 we're allowing TCP port 443 now because we're going to be deploying the 294 12:10.850 --> 12:12.160 automation appliance 295 12:12.160 --> 12:15.530 on the same exact management network and we're not setting up any distributed 296 12:15.530 --> 12:17.200 firewall rules. 297 12:17.200 --> 12:19.810 Most of these should not be a problem as long as we have reachability from a 298 12:19.810 --> 12:21.240 routing perspective. 299 12:21.240 --> 12:24.820 And then between the NSX automation appliance and the NSX managers, we also 300 12:24.820 --> 12:25.520 need to allow 301 12:25.520 --> 12:31.490 TCP port 443 as well as TCP port 22 because what's going to happen is this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 301 12:25.520 --> 12:31.490 TCP port 443 as well as TCP port 22 because what's going to happen is this 302 12:31.490 --> 12:32.640 appliance that's 303 12:32.640 --> 12:36.170 going to be doing the automation for us, we can integrate that when we deploy 304 12:36.170 --> 12:36.720 it with the 305 12:36.720 --> 12:38.040 NSX manager. 306 12:38.040 --> 12:42.000 And so to do that is going to be using TCP port 22 to do that. 307 12:42.000 --> 12:45.040 And that's referred to as the NSX UI plugin registration. 308 12:45.040 --> 12:48.590 So we can think of it like this little VM once we deploy it being able to 309 12:48.590 --> 12:49.640 integrate with 310 12:49.640 --> 12:54.440 and communicate with the NSX manager via a little plugin that it can deploy. 311 12:54.440 --> 12:56.950 And when we deploy this automation VM, when we tell it, we want to integrate 312 12:56.950 --> 12:57.280 with the 313 12:57.280 --> 13:02.580 plugin for the NSX manager will actually see the interface on the NSX manager WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 313 12:57.280 --> 13:02.580 plugin for the NSX manager will actually see the interface on the NSX manager 314 13:02.580 --> 13:03.720 change reflecting 315 13:03.720 --> 13:06.960 the fact that this little automation VM has been added. 316 13:06.960 --> 13:11.720 As we scroll down, one of the requirements is a basic license for Tanzu, which 317 13:11.720 --> 13:12.240 by default 318 13:12.240 --> 13:14.480 is going to give you a short eval period. 319 13:14.480 --> 13:19.660 Or if you have VMUG advantage, which is $200 US a year, they also give you one 320 13:19.660 --> 13:20.680 year evaluation 321 13:20.680 --> 13:22.440 licenses that you can use. 322 13:22.440 --> 13:27.010 And not just for Tanzu, but also for other things like vCenter and ESXI host 323 13:27.010 --> 13:27.680 and other 324 13:27.680 --> 13:28.760 products as well. 325 13:28.760 --> 13:32.170 And then as we continue to scroll down, it talks about the actual installation WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 325 13:28.760 --> 13:32.170 And then as we continue to scroll down, it talks about the actual installation 326 13:32.170 --> 13:32.520 of the 327 13:32.520 --> 13:34.000 automation VM. 328 13:34.000 --> 13:38.800 Now before we actually deploy the automation VM and tell it to start its work, 329 13:38.800 --> 13:39.280 we also 330 13:39.280 --> 13:42.960 need to do a little bit of additional planning regarding IP addressing. 331 13:42.960 --> 13:46.420 So let's take a moment with our existing topology here and consider some of the 332 13:46.420 --> 13:47.160 requirements 333 13:47.160 --> 13:50.880 that's going to need for IP addressing and make a plan for what we want to use. 334 13:50.880 --> 13:53.480 So in the automation guide, I'm looking through it. 335 13:53.480 --> 13:59.600 I don't see a nice list of exactly the IP addresses that it would like us to 336 13:59.600 --> 14:00.720 plan for. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 336 13:59.600 --> 14:00.720 plan for. 337 14:00.720 --> 14:04.540 So let me go ahead and go to an additional resource that's available on the 338 14:04.540 --> 14:05.360 internet. 339 14:05.360 --> 14:09.900 And here is a great blog article that's going to help us a lot in setting up 340 14:09.900 --> 14:10.640 our IP addressing. 341 14:10.640 --> 14:14.680 And it's called getting started with NSX application platform. 342 14:14.680 --> 14:18.870 And this is dated November 4th, 2022, which is a while ago, but the information 343 14:18.870 --> 14:19.360 is still 344 14:19.360 --> 14:20.360 valid. 345 14:20.360 --> 14:23.550 So if we scroll down, it's talking about the two ways of installing the NSX 346 14:23.550 --> 14:24.240 application 347 14:24.240 --> 14:28.900 platform manually or doing the automated install using the automation appliance 348 14:28.900 --> 14:29.560 , which is 349 14:29.560 --> 14:30.560 what we're going to do. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 349 14:29.560 --> 14:30.560 what we're going to do. 350 14:30.560 --> 14:34.190 And if we scroll down, this is reinforcing the concepts of the networks 351 14:34.190 --> 14:34.920 involved. 352 14:34.920 --> 14:37.040 So we already know we have that infrastructure in place. 353 14:37.040 --> 14:41.880 And here is the nap, I pan planner that I wanted to show you. 354 14:41.880 --> 14:45.540 So on our management network, in our case, our management network is VLAN 11 355 14:45.540 --> 14:46.040 with the 356 14:46.040 --> 14:50.440 address base of 10.11.11 with a 24 bit mask. 357 14:50.440 --> 14:54.580 We need to plan for an IP address that's going to be used for the HA proxy on 358 14:54.580 --> 14:55.320 that network. 359 14:55.320 --> 14:59.420 So in our network, let's use .5 for the HA proxy everywhere, because the HA 360 14:59.420 --> 15:00.080 proxy is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 360 14:59.420 --> 15:00.080 proxy is going 361 15:00.080 --> 15:02.840 to be up here on the workload network. 362 15:02.840 --> 15:07.980 So in our case, our workload network is VLAN 13 with the address base of 10.13. 363 15:07.980 --> 15:08.480 13. 364 15:08.480 --> 15:11.990 So for the HA proxy VM that is going to deploy, let's use on that network, the 365 15:11.990 --> 15:13.520 10 13 13 network 366 15:13.520 --> 15:16.520 with a six dot five for that HA proxy there as well. 367 15:16.520 --> 15:20.830 And then in our topology for the front end network, we are using VLAN 12, which 368 15:20.830 --> 15:21.280 is using 369 15:21.280 --> 15:24.840 the IP addressing space of 10 12 12 with a 24 bit mask. 370 15:24.840 --> 15:29.710 So on that network, the front end network for HA proxy, let's go ahead and use 371 15:29.710 --> 15:30.920 .5 as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 371 15:29.710 --> 15:30.920 .5 as well. 372 15:30.920 --> 15:35.400 So just as a reminder for the automation VM itself, we're going to put that one 373 15:35.400 --> 15:35.720 on the 374 15:35.720 --> 15:37.840 management network and it'll be at .6. 375 15:37.840 --> 15:41.390 And then for the HA proxy VM, which is going to be deployed as part of the 376 15:41.390 --> 15:42.240 automation, we're 377 15:42.240 --> 15:46.720 going to use .5 for each of its interfaces, the HA proxy's interfaces on each 378 15:46.720 --> 15:48.000 of the networks. 379 15:48.000 --> 15:52.590 And as part of using the auto VM to deploy nap, anytime it asks us about a 380 15:52.590 --> 15:54.280 range of addresses, 381 15:54.280 --> 15:57.240 let's start with .41 on the respective subnet. 382 15:57.240 --> 16:00.430 And then based on how many IP addresses that it needs, it'll go ahead and use WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 382 15:57.240 --> 16:00.430 And then based on how many IP addresses that it needs, it'll go ahead and use 383 16:00.430 --> 16:01.320 for example, 384 16:01.320 --> 16:05.480 five or 16 IP addresses starting off with one we specify. 385 16:05.480 --> 16:08.930 So for our game plan, we'll just specify that we want to use .41 as a starting 386 16:08.930 --> 16:09.560 IP address 387 16:09.560 --> 16:13.800 for any ranges that are needed as part of the deployment of nap. 388 16:13.800 --> 16:18.340 And on the back end, the Cooper Netties cluster that's being used to support 389 16:18.340 --> 16:18.880 nap. 390 16:18.880 --> 16:22.850 Then also here on the front end network, this 10 12 12 network, it's also going 391 16:22.850 --> 16:23.480 to be asking 392 16:23.480 --> 16:26.760 us about two DNS entries. 393 16:26.760 --> 16:30.230 And so when we get to that point in the wizard, we'll make sure that we have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 393 16:26.760 --> 16:30.230 And so when we get to that point in the wizard, we'll make sure that we have 394 16:30.230 --> 16:31.120 the DNS entries 395 16:31.120 --> 16:34.200 mapped to the specific addresses it wants. 396 16:34.200 --> 16:37.900 So those entries, those DNS entries that we need to create will be two entries 397 16:37.900 --> 16:38.280 on the 398 16:38.280 --> 16:39.680 10 12 12 network. 399 16:39.680 --> 16:44.670 It's very likely you can ask us about a resolvable name that goes to .19 and 400 16:44.670 --> 16:46.200 also .20. 401 16:46.200 --> 16:49.400 But again, that could vary based on the IP addresses that we're using and the 402 16:49.400 --> 16:49.960 ranges we've 403 16:49.960 --> 16:50.960 selected. 404 16:50.960 --> 16:54.420 And it comes to that point where it's asking us about the FQDNs, the fully 405 16:54.420 --> 16:55.400 qualified domain 406 16:55.400 --> 16:59.320 names that map to specific IP addresses, we'll head over to our DNS server and 407 16:59.320 --> 16:59.760 make sure 408 16:59.760 --> 17:00.760 those exist. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 408 16:59.760 --> 17:00.760 those exist. 409 17:00.760 --> 17:03.200 And also as part of that, we'd also want to make sure that not only do these 410 17:03.200 --> 17:03.560 entries 411 17:03.560 --> 17:08.690 exist, but we'd want to test them from VMs on those respective networks, just 412 17:08.690 --> 17:09.080 to make 413 17:09.080 --> 17:14.240 sure that DNS is correctly resolving the name to the respective IP addresses. 414 17:14.240 --> 17:17.040 So let's update our topology with this information. 415 17:17.040 --> 17:20.900 So for the HA proxy, this is going to be deployed on each of the networks, the 416 17:20.900 --> 17:21.840 management front 417 17:21.840 --> 17:26.430 end and workload, we're going to be using .5 for the actual automation VM that 418 17:26.430 --> 17:26.840 we're 419 17:26.840 --> 17:30.720 going to deploy to help orchestrate all of this for that automation VM. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 419 17:26.840 --> 17:30.720 going to deploy to help orchestrate all of this for that automation VM. 420 17:30.720 --> 17:35.760 Let's place it on the management network up here at 10.11.11. 421 17:35.760 --> 17:39.560 And let's use six for that IP address for the automation via. 422 17:39.560 --> 17:42.590 So with the HA proxy, that's going to be on the management network, I'll color 423 17:42.590 --> 17:43.040 code that 424 17:43.040 --> 17:44.040 in green. 425 17:44.040 --> 17:45.640 So I'll scoot me on the front end network. 426 17:45.640 --> 17:47.320 I'll color code that in pink. 427 17:47.320 --> 17:49.520 And it's also going to be on the workload network. 428 17:49.520 --> 17:52.400 And I'll color code that with this orange color here. 429 17:52.400 --> 17:55.720 And then whenever it's asking us about who is your DNS server will point to 10, 430 17:55.720 --> 17:56.560 10, 10, 431 17:56.560 --> 17:57.560 100. 432 17:57.560 --> 18:01.480 Whenever it asks us about NTP services for time synchronization, we'll also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 432 17:57.560 --> 18:01.480 Whenever it asks us about NTP services for time synchronization, we'll also 433 18:01.480 --> 18:04.120 point to 10.10.10.100. 434 18:04.120 --> 18:08.070 When the wizard is asking us about the vCenter server, we'll point to this v 435 18:08.070 --> 18:08.880 Center here at 436 18:08.880 --> 18:10.880 .111 or use its name. 437 18:10.880 --> 18:14.600 And I would recommend as you go through using the names as you go through. 438 18:14.600 --> 18:18.030 And that way when it does pre checks, it can help validate that the DNS is 439 18:18.030 --> 18:19.240 working correctly. 440 18:19.240 --> 18:22.650 And whenever it asks us about where your NSX manager is, we'll go ahead and 441 18:22.650 --> 18:23.120 point it 442 18:23.120 --> 18:27.160 to this device at 121 once again using the DNS name for that. 443 18:27.160 --> 18:31.450 And also for ranges of addresses, whenever it asks for those, let's go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 443 18:27.160 --> 18:31.450 And also for ranges of addresses, whenever it asks for those, let's go ahead 444 18:31.450 --> 18:32.040 and we'll 445 18:32.040 --> 18:37.960 start at .41 for IP address ranges that it can use as part of the deployment. 446 18:37.960 --> 18:38.960 All right. 447 18:38.960 --> 18:42.180 So with that game plan in mind using the existing network infrastructure from 448 18:42.180 --> 18:42.960 our previous sets 449 18:42.960 --> 18:47.460 of videos, our next logical step is to go ahead and deploy the actual 450 18:47.460 --> 18:48.480 automation VM 451 18:48.480 --> 18:51.520 which can be used to help orchestrate all of this work. 452 18:51.520 --> 18:54.520 And that's exactly what you and I get to do in the next video. 453 18:54.520 --> 18:56.040 So I'll see you there in just a moment.