WEBVTT 1 00:00.240 --> 00:02.880 It's now time for us to introduce two parties 2 00:02.880 --> 00:06.270 that need to work together as part of an NSX-based solution. 3 00:06.270 --> 00:08.940 And that is we need to introduce the NSX Manager 4 00:08.940 --> 00:11.010 to the vCenter that it should be working with. 5 00:11.010 --> 00:11.843 And to do that, 6 00:11.843 --> 00:14.550 we're gonna train the NSX server not only who that is, 7 00:14.550 --> 00:16.109 but also how to log in 8 00:16.109 --> 00:18.780 so it can use the services of vCenter. 9 00:18.780 --> 00:19.613 So to do that, 10 00:19.613 --> 00:23.310 we'll log on to our NSX Manager here at .11 once again, 11 00:23.310 --> 00:25.890 and then using the interface here on NSX Manager, 12 00:25.890 --> 00:27.120 we'll train NSX Manager 13 00:27.120 --> 00:30.270 on how to connect to and log into vCenter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:27.120 --> 00:30.270 on how to connect to and log into vCenter. 14 00:30.270 --> 00:33.240 So back at the NSX Manager interface 15 00:33.240 --> 00:35.580 here on the System tab where we left off, 16 00:35.580 --> 00:37.440 we were looking at the appliance health here. 17 00:37.440 --> 00:38.640 So we were on Appliances. 18 00:38.640 --> 00:40.830 And there's our single NSX Manager 19 00:40.830 --> 00:43.050 as part of this cluster at the moment. 20 00:43.050 --> 00:44.497 Also, it has a big warning here saying, 21 00:44.497 --> 00:45.930 "Hey, you need a compute manager." 22 00:45.930 --> 00:49.770 Effectively, that's saying you need to train the NSX Manager 23 00:49.770 --> 00:51.360 on which vCenter to use, 24 00:51.360 --> 00:52.920 and that's what the compute manager is. 25 00:52.920 --> 00:54.030 It's the vCenter itself. 26 00:54.030 --> 00:56.940 So we can either click right here on Compute Managers 27 00:56.940 --> 00:59.220 or still here on the System tab, 28 00:59.220 --> 01:01.170 we could just expand Fabric, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:59.220 --> 01:01.170 we could just expand Fabric, 29 01:01.170 --> 01:04.230 and right here, we have Compute Managers. 30 01:04.230 --> 01:06.600 Either way, it would've taken us to this section. 31 01:06.600 --> 01:09.510 So we'll simply click on Add a Compute Manager. 32 01:09.510 --> 01:11.340 So we'll click Add Compute Manager, 33 01:11.340 --> 01:13.800 and I'm gonna call us Our vCenter, 34 01:13.800 --> 01:15.150 just the name that we represents 35 01:15.150 --> 01:16.920 our vCenter that we're gonna connect to. 36 01:16.920 --> 01:18.240 And then we're gonna specify 37 01:18.240 --> 01:20.040 how to reach that vCenter server. 38 01:20.040 --> 01:22.290 So if we have name resolution all set up, 39 01:22.290 --> 01:23.430 which I believe we do, 40 01:23.430 --> 01:25.590 we could actually put in the name here, 41 01:25.590 --> 01:26.820 the fully qualified domain name, 42 01:26.820 --> 01:28.800 or we could just put in the IP address. 43 01:28.800 --> 01:31.140 And just to verify things a little bit, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 01:28.800 --> 01:31.140 And just to verify things a little bit, 44 01:31.140 --> 01:32.730 let's bring up a command prompt, 45 01:32.730 --> 01:36.390 and let me verify whether or not I have the names 46 01:36.390 --> 01:37.680 and IP address all mapped up. 47 01:37.680 --> 01:39.510 So let's go into nslookup again here 48 01:39.510 --> 01:40.920 on this Windows computer, 49 01:40.920 --> 01:42.390 we'll go into Interactive mode. 50 01:42.390 --> 01:44.520 So I'm currently using the same DNS server 51 01:44.520 --> 01:47.340 that I trained my NSX environment to use. 52 01:47.340 --> 01:49.710 And let's go ahead and do an interactive lookup 53 01:49.710 --> 01:53.460 for 192.168.1.185, 54 01:53.460 --> 01:57.180 which is the IP address of our vCenter server. 55 01:57.180 --> 01:58.140 And it does have the record. 56 01:58.140 --> 02:00.090 So the fact that it came back with the name here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 01:58.140 --> 02:00.090 So the fact that it came back with the name here 57 02:00.090 --> 02:01.590 represents there's an A record. 58 02:01.590 --> 02:03.450 And the fact that we did a reverse lookup 59 02:03.450 --> 02:04.650 based on the IP address 60 02:04.650 --> 02:06.660 also implies there's a pointer record. 61 02:06.660 --> 02:09.360 So that's the actual fully qualified domain name 62 02:09.360 --> 02:10.770 of our vCenter. 63 02:10.770 --> 02:13.050 And yes, this is a nested environment that I'm working with. 64 02:13.050 --> 02:15.000 So I currently have, behind me in my rack, 65 02:15.000 --> 02:18.030 I've got four physical ESXi hosts. 66 02:18.030 --> 02:19.890 They are Dell Rack servers. 67 02:19.890 --> 02:21.210 And then behind the scenes, 68 02:21.210 --> 02:22.860 each of those is supporting one 69 02:22.860 --> 02:26.640 of the virtualized ESXi A, B, C, and D 70 02:26.640 --> 02:29.430 that we're using as part of this implementation. 71 02:29.430 --> 02:32.220 However, due to the beauty of virtualization, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 02:29.430 --> 02:32.220 However, due to the beauty of virtualization, 72 02:32.220 --> 02:33.450 my little nested environment 73 02:33.450 --> 02:35.670 really doesn't care, or even know, 74 02:35.670 --> 02:37.950 about the fact that it's living in a nested environment. 75 02:37.950 --> 02:39.600 So this is the vCenter server 76 02:39.600 --> 02:42.210 that's currently running on ESXi D. 77 02:42.210 --> 02:45.510 So I'm gonna copy that name, come over here, right-click, 78 02:45.510 --> 02:46.890 and paste it in. 79 02:46.890 --> 02:49.140 And assuming DNS is all working and set up, 80 02:49.140 --> 02:50.400 that should be absolutely no problem. 81 02:50.400 --> 02:51.360 Or in a lab environment, 82 02:51.360 --> 02:53.130 if you're not sure if you have DNS set up, 83 02:53.130 --> 02:55.350 you can just go ahead and put in the IP address there. 84 02:55.350 --> 02:56.610 Then, as we scroll down, 85 02:56.610 --> 02:58.020 we'll go ahead and put our username, 86 02:58.020 --> 02:59.790 and this is the username that we're gonna use 87 02:59.790 --> 03:02.940 to log on to vSphere with the single sign-on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 02:59.790 --> 03:02.940 to log on to vSphere with the single sign-on. 88 03:02.940 --> 03:05.400 So if you have a service account for that purpose, use that. 89 03:05.400 --> 03:06.600 Or in a lab environment, 90 03:06.600 --> 03:09.660 if you're using the King Kong password of administrator, 91 03:09.660 --> 03:10.800 you can use that as well. 92 03:10.800 --> 03:13.650 So I'm gonna log on as administrator@vsphere.local, 93 03:13.650 --> 03:14.700 then also apply the password 94 03:14.700 --> 03:16.380 associated with that administrator account. 95 03:16.380 --> 03:17.820 And then I'm also gonna go ahead 96 03:17.820 --> 03:18.900 and create a service account 97 03:18.900 --> 03:23.100 as part of the connecting the NSX Manager over to vCenter. 98 03:23.100 --> 03:24.600 And I'm also going to enable trust, 99 03:24.600 --> 03:26.700 which means that if I want to in the future, 100 03:26.700 --> 03:30.450 I can use full-blown Kubernetes and Lifecycle Manager, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 03:26.700 --> 03:30.450 I can use full-blown Kubernetes and Lifecycle Manager, 101 03:30.450 --> 03:32.370 which is gonna provide full access to NSX 102 03:32.370 --> 03:34.860 for things like vSphere for Kubernetes 103 03:34.860 --> 03:36.630 and vSphere Lifecycle Manager. 104 03:36.630 --> 03:38.580 So if you don't intend or want to use those, 105 03:38.580 --> 03:40.500 you don't really need to enable that trust for that. 106 03:40.500 --> 03:42.390 But for my lab, in the event that we wanna do that, 107 03:42.390 --> 03:44.100 I'm gonna go ahead and enable it right now. 108 03:44.100 --> 03:45.480 And we'll click on Add. 109 03:45.480 --> 03:47.070 So it's gonna take just a moment. 110 03:47.070 --> 03:49.290 It's asking us if we wanna use this thumbprint, 111 03:49.290 --> 03:51.240 that's the thumbprint for our vCenter. 112 03:51.240 --> 03:52.530 I'll click on Add 113 03:52.530 --> 03:54.750 and then give it a couple moments to complete. 114 03:54.750 --> 03:56.580 It says the Compute Manager Our vCenter 115 03:56.580 --> 03:57.686 was successfully created. 116 03:57.686 --> 04:00.090 Fantastic, I'll dismiss that message. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 03:57.686 --> 04:00.090 Fantastic, I'll dismiss that message. 117 04:00.090 --> 04:00.923 And then right here, 118 04:00.923 --> 04:03.960 it's showing that the registration is currently in progress. 119 04:03.960 --> 04:05.970 So I'm gonna go to my columns here 120 04:05.970 --> 04:08.880 and I'm gonna remove the column for ID 121 04:08.880 --> 04:10.500 to give us a little more space there. 122 04:10.500 --> 04:11.333 And fantastic. 123 04:11.333 --> 04:12.990 So it says registered also in the bottom here, 124 04:12.990 --> 04:14.700 there's an option for a refresh. 125 04:14.700 --> 04:18.150 So that may take a minute or two to fully be registered 126 04:18.150 --> 04:20.730 and also before it shows the connection status as active. 127 04:20.730 --> 04:24.750 So now, NSX has registered with vCenter 128 04:24.750 --> 04:26.730 and the connection status is up. 129 04:26.730 --> 04:27.975 All right, so far so good. 130 04:27.975 --> 04:31.650 So at this point, if we go to System up on the top tab here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 04:27.975 --> 04:31.650 So at this point, if we go to System up on the top tab here, 131 04:31.650 --> 04:33.840 and then the left, we click here on Appliances, 132 04:33.840 --> 04:37.170 currently we've deployed our first NSX Manager. 133 04:37.170 --> 04:38.940 So think of it like a cluster of one. 134 04:38.940 --> 04:41.970 And this is also the point where it's super easy 135 04:41.970 --> 04:45.300 to deploy our second and third appliances 136 04:45.300 --> 04:46.410 as part of this cluster. 137 04:46.410 --> 04:49.830 And so instead of having to go back to the original OVA 138 04:49.830 --> 04:51.450 and deploy it from our workstation, 139 04:51.450 --> 04:55.260 we can actually deploy the second and third NSX Managers 140 04:55.260 --> 04:57.360 as part of our cluster right from here. 141 04:57.360 --> 04:58.890 So if System is selected at the top 142 04:58.890 --> 05:00.330 and Appliances on the left, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 04:58.890 --> 05:00.330 and Appliances on the left, 143 05:00.330 --> 05:02.520 we simply go down to the list of our appliances. 144 05:02.520 --> 05:03.510 So there's our current one, 145 05:03.510 --> 05:05.220 and we'd use this panel right here. 146 05:05.220 --> 05:07.110 This is the Add NSX Appliance. 147 05:07.110 --> 05:08.070 If we click it, 148 05:08.070 --> 05:11.160 it's gonna walk us through specifying the name, 149 05:11.160 --> 05:13.110 where do you wanna put the second appliance, 150 05:13.110 --> 05:15.510 including which ESXi host you wanna run it on, 151 05:15.510 --> 05:17.610 what's the IP address going to be of this device, 152 05:17.610 --> 05:19.050 what's the gateway address, 153 05:19.050 --> 05:21.240 and all the other details for this VM. 154 05:21.240 --> 05:22.770 So once we finish the wizard, 155 05:22.770 --> 05:26.430 it'll deploy the second NSXi manager as part of the cluster. 156 05:26.430 --> 05:28.200 Again, it takes like 30 to 40 minutes. 157 05:28.200 --> 05:29.190 And then when that's done, 158 05:29.190 --> 05:30.600 you simply repeat the process WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 158 05:29.190 --> 05:30.600 you simply repeat the process 159 05:30.600 --> 05:32.190 and you can install the third one. 160 05:32.190 --> 05:33.464 Now, you don't actually have to wait. 161 05:33.464 --> 05:36.159 You can actually start on the second one 162 05:36.159 --> 05:38.790 and then click the tile again to start the third one 163 05:38.790 --> 05:39.840 and have them deploy. 164 05:39.840 --> 05:41.133 Just be aware, though, that you wanna make sure 165 05:41.133 --> 05:44.070 that you have enough resources on the ESXi hosts, 166 05:44.070 --> 05:46.020 especially in the lab environment to support that. 167 05:46.020 --> 05:48.510 So, because here in my home lab environment, 168 05:48.510 --> 05:50.790 even though I have some pretty hefty servers behind me, 169 05:50.790 --> 05:54.210 I'm not gonna bother deploying the second or the third. 170 05:54.210 --> 05:57.030 I'm just gonna use this one NSXi Manager going forward. 171 05:57.030 --> 06:00.870 Now, whether or not you have one NSX Manager in the cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 05:57.030 --> 06:00.870 Now, whether or not you have one NSX Manager in the cluster 172 06:00.870 --> 06:02.040 or three, 173 06:02.040 --> 06:05.610 another option we can do is set up our virtual IP address. 174 06:05.610 --> 06:07.920 And that way, if we set up a virtual IP address, 175 06:07.920 --> 06:09.810 when we connect to that virtual IP address, 176 06:09.810 --> 06:10.643 it's gonna be associated 177 06:10.643 --> 06:13.773 with one of the NSX Managers in our cluster.