WEBVTT 1 00:00.000 --> 00:03.560 In this video, I'd like to walk you through and give you examples of the nested 2 00:03.560 --> 00:04.000 networking 3 00:04.000 --> 00:07.120 I'm doing inside of the vSphere environment. 4 00:07.120 --> 00:13.880 So as far as the nested ESXi host, we have ESXi A and ESXi B and one called ES 5 00:13.880 --> 00:14.600 Xi something 6 00:14.600 --> 00:15.800 like management. 7 00:15.800 --> 00:20.150 And although I don't need all the networking on all three because of the 8 00:20.150 --> 00:21.400 benefit of vSphere 9 00:21.400 --> 00:26.050 running in this nested environment and using a virtualized distributed switch, 10 00:26.050 --> 00:26.320 it was 11 00:26.320 --> 00:30.460 super easy just to replicate the same virtual switch across all three. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:26.320 --> 00:30.460 super easy just to replicate the same virtual switch across all three. 12 00:30.460 --> 00:34.270 So in each of these hosts, they were each given six network cards, or I should 13 00:34.270 --> 00:34.780 say at 14 00:34.780 --> 00:36.100 least six network cards. 15 00:36.100 --> 00:40.410 I went back and forth a few times, but I would recommend six network cards each 16 00:40.410 --> 00:40.600 and that 17 00:40.600 --> 00:46.000 would represent VMNIC 012345 on each of those ESXi hosts. 18 00:46.000 --> 00:49.730 And on the parent physical host, those are going to be connected to port groups 19 00:49.730 --> 00:49.980 on a 20 00:49.980 --> 00:53.440 virtual distributed switch, each of which is supporting trunking. 21 00:53.440 --> 00:58.070 You already mentioned the requirement of setting up the 9K frame size, which we 22 00:58.070 --> 00:58.400 would 23 00:58.400 --> 01:00.160 also want to do on these switches. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:58.400 --> 01:00.160 also want to do on these switches. 24 01:00.160 --> 01:01.800 So that would be a switch level. 25 01:01.800 --> 01:05.250 We'd also want to make sure as we set up the port groups that were allowing the 26 01:05.250 --> 01:05.720 MACID 27 01:05.720 --> 01:10.460 rust changes and MACID rust learning and also forged transmits for each of the 28 01:10.460 --> 01:11.240 port groups 29 01:11.240 --> 01:13.840 that were going to be creating underneath these switches. 30 01:13.840 --> 01:17.030 And to support the NSX environment, I would recommend creating these two 31 01:17.030 --> 01:18.440 distributed switches. 32 01:18.440 --> 01:21.720 One called something like VDS host and one called VDS edge. 33 01:21.720 --> 01:24.680 And then for the port groups, we want to make a port group for management. 34 01:24.680 --> 01:28.690 And for that management port group, we just associate that with VMNIC's zero 35 01:28.690 --> 01:29.200 and one. 36 01:29.200 --> 01:33.240 We could also create additional port groups that we could use in combination WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:29.200 --> 01:33.240 We could also create additional port groups that we could use in combination 37 01:33.240 --> 01:33.760 with the 38 01:33.760 --> 01:35.960 motion and provisioning and so forth. 39 01:35.960 --> 01:38.710 And for any of those port groups that we're going to set up, I would recommend 40 01:38.710 --> 01:39.560 just using 41 01:39.560 --> 01:42.160 the first two ports, zero and one. 42 01:42.160 --> 01:46.210 So you can set it up with that one being primary, the one being standby, or you 43 01:46.210 --> 01:46.480 can 44 01:46.480 --> 01:48.040 set it up to share those two links. 45 01:48.040 --> 01:50.240 It really doesn't matter too much in an nested environment. 46 01:50.240 --> 01:54.400 But the key is we want to leave ports two and three, the third and fourth upl 47 01:54.400 --> 01:54.880 inks off 48 01:54.880 --> 01:56.440 of the switch called VDS host. 49 01:56.440 --> 02:00.510 And then for this switch here, this distributed switch called VDS edge, we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 01:56.440 --> 02:00.510 And then for this switch here, this distributed switch called VDS edge, we're 50 02:00.510 --> 02:01.240 going to associate 51 02:01.240 --> 02:04.240 two uplinks, VMNIC 4 and VMNIC 5. 52 02:04.240 --> 02:06.360 And over here, we're going to create two port groups. 53 02:06.360 --> 02:09.360 We're going to create a port group that says something like VMNIC 4. 54 02:09.360 --> 02:13.030 And then we'll create another port group that reminds us of VMNIC 5 and then we 55 02:13.030 --> 02:13.280 'll 56 02:13.280 --> 02:16.600 link those port groups to those respective uplinks. 57 02:16.600 --> 02:22.040 One of the challenges in an NSX lab environment is remembering what goes where. 58 02:22.040 --> 02:26.010 And so if we have a port group over here called PG4 off of the switch and we 59 02:26.010 --> 02:26.640 want an edge 60 02:26.640 --> 02:30.010 node to use this uplink, we can simply associate that edge node for its WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 02:26.640 --> 02:30.010 node to use this uplink, we can simply associate that edge node for its 61 02:30.010 --> 02:31.160 transport network with 62 02:31.160 --> 02:33.400 that port group, which leads to that uplink. 63 02:33.400 --> 02:36.320 And same thing for an edge node where we want to use a profile that's 64 02:36.320 --> 02:37.120 associated with the 65 02:37.120 --> 02:41.570 uplink 5, we can simply refer to that port group, which leads off to this upl 66 02:41.570 --> 02:42.040 ink. 67 02:42.040 --> 02:46.130 And although not all three hosts are going to need all those exact uplinks, 68 02:46.130 --> 02:46.440 because the 69 02:46.440 --> 02:50.870 two edge nodes are going to run right here on just the ESXI management VM, it 70 02:50.870 --> 02:51.280 just makes 71 02:51.280 --> 02:55.340 it a lot easier and more consistent if you set this environment up across all 72 02:55.340 --> 02:55.880 three. 73 02:55.880 --> 02:59.150 And that way later, if you want to change roles or anything else, you have all 74 02:59.150 --> 02:59.880 the networking 75 02:59.880 --> 03:01.920 connectivity in place. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 02:59.880 --> 03:01.920 connectivity in place. 76 03:01.920 --> 03:05.720 So with this in mind, let me show you my nested environment. 77 03:05.720 --> 03:07.840 So again, the light mode is my nested environment. 78 03:07.840 --> 03:10.720 There's the single sign on domain, OGIT.lab. 79 03:10.720 --> 03:14.310 So if we were to go to the networking tab here on the vSphere client, let's 80 03:14.310 --> 03:14.680 take a look 81 03:14.680 --> 03:18.600 at first at this distributed switch called lab one NSX hosts. 82 03:18.600 --> 03:21.290 And one of the first things I want to remind you about with these distributed 83 03:21.290 --> 03:21.920 switches are 84 03:21.920 --> 03:22.920 the settings. 85 03:22.920 --> 03:25.980 So if we right click on the switch itself and go down to settings, and then 86 03:25.980 --> 03:26.480 click here 87 03:26.480 --> 03:30.370 and edit settings, we want to make sure under advanced that we have an MTU of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 03:26.480 --> 03:30.370 and edit settings, we want to make sure under advanced that we have an MTU of 88 03:30.370 --> 03:31.840 at least 9,000 89 03:31.840 --> 03:32.840 bytes. 90 03:32.840 --> 03:36.180 And also for this NSX hosts, we were going to specify that there's four uplinks 91 03:36.180 --> 03:36.920 available. 92 03:36.920 --> 03:41.860 And I also found it super convenient to label these uplinks here with the 93 03:41.860 --> 03:42.960 actual VM next 94 03:42.960 --> 03:47.130 you're going to be using them for that way later when we're trying to link NSX 95 03:47.130 --> 03:47.640 uplinks 96 03:47.640 --> 03:50.600 in combination with our virtual distributed switch uplinks. 97 03:50.600 --> 03:53.360 We'll have a really good clue about what goes where. 98 03:53.360 --> 03:57.910 So again, for this distributed switch called NSX host for uplinks and an MTU of 99 03:57.910 --> 03:59.080 9,000. 100 03:59.080 --> 04:00.480 So no changes there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 03:59.080 --> 04:00.480 So no changes there. 101 04:00.480 --> 04:04.640 Let's also take a look at the lab one NSX edges that distributed switch will 102 04:04.640 --> 04:05.760 right click, 103 04:05.760 --> 04:08.560 click on settings and then click on edit settings. 104 04:08.560 --> 04:12.960 Again, under advanced a 9,000 MTU and two uplinks for this. 105 04:12.960 --> 04:16.470 I've also labeled them with the intended uplinks I want to use on the 106 04:16.470 --> 04:17.720 respective hosts. 107 04:17.720 --> 04:20.680 So in the lab environment in the heat of battle, when you're trying to figure 108 04:20.680 --> 04:21.280 out what goes 109 04:21.280 --> 04:23.880 where, this is going to be super helpful. 110 04:23.880 --> 04:24.880 So no changes there. 111 04:24.880 --> 04:28.410 We'll click on cancel and then let's take a look at the rest of the config here 112 04:28.410 --> 04:28.480 . 113 04:28.480 --> 04:30.360 So here on the edges, I have two poor groups. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 04:28.480 --> 04:30.360 So here on the edges, I have two poor groups. 114 04:30.360 --> 04:34.140 In fact, a really great way of looking at this is to select the distributed 115 04:34.140 --> 04:34.760 switch, click 116 04:34.760 --> 04:38.920 on the configure tab here and then go to the topology view, which I love. 117 04:38.920 --> 04:43.040 So here for this poor group called lab one, poor group to VM, Nick four, you'll 118 04:43.040 --> 04:43.400 notice 119 04:43.400 --> 04:47.360 it's mapped just to VM, Nick four on each of the hosts. 120 04:47.360 --> 04:51.090 And here for this poor group called lab one, poor group to VM, Nick five, it's 121 04:51.090 --> 04:51.520 mapped 122 04:51.520 --> 04:54.560 just to VM, Nick five on those three hosts. 123 04:54.560 --> 04:57.250 And currently I have one virtual machine associated with each of those poor 124 04:57.250 --> 04:57.760 groups, 125 04:57.760 --> 04:59.480 but I didn't put in there directly. 126 04:59.480 --> 05:02.760 It was the NSX manager who did it when I deployed edges. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 126 04:59.480 --> 05:02.760 It was the NSX manager who did it when I deployed edges. 127 05:02.760 --> 05:07.420 So edge one is currently associated with VM, Nick four and edge two is 128 05:07.420 --> 05:09.080 currently associated 129 05:09.080 --> 05:10.640 with VM, Nick five. 130 05:10.640 --> 05:14.820 And because those two VMs are running on the management host, that's why they 131 05:14.820 --> 05:15.560 're showing 132 05:15.560 --> 05:17.480 up going over to those respective ports. 133 05:17.480 --> 05:19.800 All right, so that's the NSX edges. 134 05:19.800 --> 05:23.280 And then if you take a look at the NSX host, distribute a switch. 135 05:23.280 --> 05:24.480 I have a poor group. 136 05:24.480 --> 05:28.480 In fact, we can do this also from the configure and topology view here. 137 05:28.480 --> 05:32.170 So for this to show you the switch, I have a poor group called management PG WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 137 05:28.480 --> 05:32.170 So for this to show you the switch, I have a poor group called management PG 138 05:32.170 --> 05:32.440 and for 139 05:32.440 --> 05:34.080 the VLAN ID, it's all left off. 140 05:34.080 --> 05:36.040 So it's not going to do any tagging. 141 05:36.040 --> 05:40.450 This leads straight out through the parent ESX I host through its uplink out to 142 05:40.450 --> 05:41.160 my management 143 05:41.160 --> 05:42.160 network. 144 05:42.160 --> 05:44.560 And that's in my case, the 192 168 one network. 145 05:44.560 --> 05:49.220 And then I also set up one for provisioning, which using VLAN 11 and for ice g 146 05:49.220 --> 05:49.720 uzzy, which 147 05:49.720 --> 05:51.320 is VLAN ID two. 148 05:51.320 --> 05:54.560 And so in your nested lab environment, you don't need to set up additional 149 05:54.560 --> 05:55.360 network connectivity 150 05:55.360 --> 05:59.240 to ice guzzy networking or shared storage if you don't want to. 151 05:59.240 --> 06:03.040 But on the parent network on the physical host, it is important for the benefit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 05:59.240 --> 06:03.040 But on the parent network on the physical host, it is important for the benefit 152 06:03.040 --> 06:04.480 of DRS 153 06:04.480 --> 06:07.000 and V motion to be able to move stuff around very quickly. 154 06:07.000 --> 06:10.090 It's important in the parent physical network to make sure that we have shared 155 06:10.090 --> 06:10.720 storage. 156 06:10.720 --> 06:14.520 So the provisioning and ice guzzy and V motion poor groups aren't too critical. 157 06:14.520 --> 06:18.000 And then down here, I have a couple of NSX created segments that are leveraging 158 06:18.000 --> 06:19.280 my existing 159 06:19.280 --> 06:21.960 distributed switch right here, the NSX hosts. 160 06:21.960 --> 06:27.080 So as we create segments inside of NSX, we're going to be using existing VDSs 161 06:27.080 --> 06:28.040 virtual distributed 162 06:28.040 --> 06:29.880 switches in vSphere. 163 06:29.880 --> 06:31.000 And this is the result of that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 163 06:29.880 --> 06:31.000 And this is the result of that. 164 06:31.000 --> 06:35.200 So these two segments right here are a result of NSX configuration leveraging 165 06:35.200 --> 06:36.080 this existing 166 06:36.080 --> 06:37.080 switch. 167 06:37.080 --> 06:40.480 So the key takeaway here is that for this switch, this NSX host switch, we want 168 06:40.480 --> 06:41.280 four uplinks. 169 06:41.280 --> 06:44.600 We want to name them correctly so we know exactly where they go. 170 06:44.600 --> 06:48.800 And we want to make sure the switch is set for a 9000 byte jumbo frame. 171 06:48.800 --> 06:52.840 And then as we create segments in NSX, they'll show up right here associated 172 06:52.840 --> 06:53.640 with this distributed 173 06:53.640 --> 06:54.640 switch. 174 06:54.640 --> 06:57.690 So now that we've taken a close look to verify our nested networking in the 175 06:57.690 --> 06:58.560 next video, let's 176 06:58.560 --> 07:01.160 take a look at deploying the NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 176 06:58.560 --> 07:01.160 take a look at deploying the NSX manager.