WEBVTT 1 00:00.210 --> 00:01.680 So it is time to create 2 00:01.680 --> 00:02.940 our first overlay segment, 3 00:02.940 --> 00:05.580 and that is this one right here, Overlay Segment 10. 4 00:05.580 --> 00:07.200 We'll make sure that when we create it, 5 00:07.200 --> 00:10.140 it's included as part of this transport zone 6 00:10.140 --> 00:12.870 called Our A-B overlay Transport Zone. 7 00:12.870 --> 00:15.720 So, with this topology and that idea in mind, 8 00:15.720 --> 00:18.870 let's get to work in creating this new overlay segment. 9 00:18.870 --> 00:21.275 Also, as a quick verification of what is about to change 10 00:21.275 --> 00:23.070 when we create this new segment, 11 00:23.070 --> 00:24.510 let's go to the vSphere Client. 12 00:24.510 --> 00:25.650 We're currently there. 13 00:25.650 --> 00:27.330 Let's go to the Networking tab. 14 00:27.330 --> 00:28.920 And if we click on this distribute switch 15 00:28.920 --> 00:32.100 called DS for NSX, and we click on Configure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:28.920 --> 00:32.100 called DS for NSX, and we click on Configure. 16 00:32.100 --> 00:34.200 And then I love this view, the Topology view 17 00:34.200 --> 00:36.090 that gives a visual representation. 18 00:36.090 --> 00:38.370 We have two uplinks associated with that distributed switch, 19 00:38.370 --> 00:40.050 but there are no port groups 20 00:40.050 --> 00:41.760 that we can use to connect clients to. 21 00:41.760 --> 00:43.920 However, that's gonna change because once we create 22 00:43.920 --> 00:47.668 the NSX segment for Segment 10, it'll show up here, 23 00:47.668 --> 00:50.340 very similar to how a port group would show up. 24 00:50.340 --> 00:52.220 So, let's head over to the graphical user interface 25 00:52.220 --> 00:54.120 for the NSX Manager. 26 00:54.120 --> 00:55.320 So, that is right here. 27 00:55.320 --> 00:56.550 And to create a new segment, 28 00:56.550 --> 00:59.880 what we're gonna do is click on the Networking tab up here. 29 00:59.880 --> 01:02.580 And that provides us a beautiful network overview WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 00:59.880 --> 01:02.580 And that provides us a beautiful network overview 30 01:02.580 --> 01:07.269 with no Tier-O Gateways, no Tier-1 Gateways, no Segments. 31 01:07.269 --> 01:08.820 (chuckles) And we're gonna change 32 01:08.820 --> 01:10.860 that segment thing right now by creating one. 33 01:10.860 --> 01:12.870 So, still with Networking selected 34 01:12.870 --> 01:14.910 on the left hand side under Connectivity, 35 01:14.910 --> 01:17.460 we'll click right here on Segments. 36 01:17.460 --> 01:20.310 And with Segments selected and the tab for NSX selected, 37 01:20.310 --> 01:22.320 we'll click right here on Add Segment. 38 01:22.320 --> 01:26.820 So now, we have the opportunity to add a new NSX segment. 39 01:26.820 --> 01:29.280 Now, we could do an overlay segment, which we're about to. 40 01:29.280 --> 01:31.590 There's also an option for a VLAN-backed segment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:29.280 --> 01:31.590 There's also an option for a VLAN-backed segment, 41 01:31.590 --> 01:33.540 which we'll do in a later set of videos. 42 01:33.540 --> 01:35.940 So for now, with Add Segment selected, 43 01:35.940 --> 01:37.320 let's go ahead and name it. 44 01:37.320 --> 01:39.690 And let's call it Seg 10 45 01:39.690 --> 01:42.180 and I'm also gonna put the label of Yellow on there. 46 01:42.180 --> 01:43.440 And that way when we see it, 47 01:43.440 --> 01:45.960 we can correlate it better to our topology. 48 01:45.960 --> 01:47.220 So, Segment 10 Yellow. 49 01:47.220 --> 01:49.980 Let me also go ahead and move the left hand side 50 01:49.980 --> 01:50.820 outta the way a little bit. 51 01:50.820 --> 01:52.290 It'll give us a little more room here. 52 01:52.290 --> 01:55.050 And currently we don't have any logical gateways set up. 53 01:55.050 --> 01:57.630 So, we're not gonna link this segment to any gateways. 54 01:57.630 --> 01:59.610 It's just gonna be a segment in NSX 55 01:59.610 --> 02:02.100 that our ESXi transport host can use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 01:59.610 --> 02:02.100 that our ESXi transport host can use. 56 02:02.100 --> 02:03.570 And we also need to associate this segment 57 02:03.570 --> 02:06.630 we're about to create with the appropriate transport zone. 58 02:06.630 --> 02:08.940 So, we wanna go ahead and use the dropdown here. 59 02:08.940 --> 02:11.850 And here is our A-B Overlay Transport Zone. 60 02:11.850 --> 02:13.860 And you'll notice that a segment 61 02:13.860 --> 02:15.960 can only be associated with one zone. 62 02:15.960 --> 02:17.580 So if we want a overlay segment, 63 02:17.580 --> 02:19.890 we're gonna make sure we're including that segment. 64 02:19.890 --> 02:23.100 This one we're creating right here in a transport zone 65 02:23.100 --> 02:24.690 that is of type overlay as well. 66 02:24.690 --> 02:27.510 So, here is our A-B Overlay Transport Zone. 67 02:27.510 --> 02:29.490 And really, that's all we need to do at this point. 68 02:29.490 --> 02:32.430 So we can just scroll down a little bit, click on Save. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 02:29.490 --> 02:32.430 So we can just scroll down a little bit, click on Save. 69 02:32.430 --> 02:34.530 And it's asking, "Do you wanna continue editing this?" 70 02:34.530 --> 02:36.090 We'll go ahead and click on No. 71 02:36.090 --> 02:37.530 And then, let's take a look at the details. 72 02:37.530 --> 02:40.290 There's not too much here except for the fact it has a name. 73 02:40.290 --> 02:43.350 It also has a zone that it's a member of. 74 02:43.350 --> 02:44.910 And our two ESXi hosts 75 02:44.910 --> 02:46.980 are both supporting that transport zone. 76 02:46.980 --> 02:48.780 So, that means this segment should be available 77 02:48.780 --> 02:52.890 to be used by VMs on either ESXi-A or ESXi-B. 78 02:52.890 --> 02:54.660 So I'm gonna go ahead and click on Collapse All. 79 02:54.660 --> 02:56.130 So here's our one segment. 80 02:56.130 --> 02:58.110 Also, if we expand the left hand side here, 81 02:58.110 --> 02:59.730 now we go to Network Topology. 82 02:59.730 --> 03:01.500 Check this out. Oh, this is so exciting. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 02:59.730 --> 03:01.500 Check this out. Oh, this is so exciting. 83 03:01.500 --> 03:03.540 I can almost not contain myself. 84 03:03.540 --> 03:05.730 Here, we have a visual representation 85 03:05.730 --> 03:07.560 of our network topology. (chuckles) 86 03:07.560 --> 03:08.940 And so far in NSX, 87 03:08.940 --> 03:12.570 it's just one segment called Seg 10 Yellow. 88 03:12.570 --> 03:15.589 If we zoom in a little bit here, we can drag it around. 89 03:15.589 --> 03:18.750 We can also drag it using this option here. 90 03:18.750 --> 03:20.580 Either way is great. And so, there it is. 91 03:20.580 --> 03:23.160 So, no VMs are connected, but it does exist. 92 03:23.160 --> 03:26.460 So, if we made a road trip over to our vSphere Client. 93 03:26.460 --> 03:30.000 This Seg 10 Yellow segment would show up WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 03:30.000 --> 03:31.603 and it kinda looks like a port group 95 03:31.603 --> 03:33.510 under our distributed switch. 96 03:33.510 --> 03:34.800 In fact, let's go take a look. 97 03:34.800 --> 03:36.180 So, here in the vSphere Client 98 03:36.180 --> 03:38.610 with the Network tab selected here, 99 03:38.610 --> 03:40.860 if we look at our distributed switch for NSX, 100 03:40.860 --> 03:43.650 we now have this new Seg 10 Yellow. 101 03:43.650 --> 03:45.150 So, if we click on the distributed switch 102 03:45.150 --> 03:47.940 and we go to configure and look at the topology, 103 03:47.940 --> 03:50.010 and again, it kinda looks and feels like a port group 104 03:50.010 --> 03:51.660 that you could associate VMs with, 105 03:51.660 --> 03:53.460 except instead of being a normal port group, 106 03:53.460 --> 03:56.280 this is a NSX segment, which is able 107 03:56.280 --> 03:59.880 to span multiple ESXI hosts even on different subnets. 108 03:59.880 --> 04:01.980 And the ESXi hosts supporting the segment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 03:59.880 --> 04:01.980 And the ESXi hosts supporting the segment 109 04:01.980 --> 04:04.350 are able to tunnel back and forth as needed 110 04:04.350 --> 04:05.850 to forward the VM's traffic. 111 04:05.850 --> 04:08.580 So, if we clicked on this Seg 10 Yellow 112 04:08.580 --> 04:09.630 and take a look at the details 113 04:09.630 --> 04:11.160 as far as what uplinks it's using. 114 04:11.160 --> 04:15.630 It's using vmnic2 on both ESXi-A and ESXi-B. 115 04:15.630 --> 04:17.670 And it's not using vmnic3. 116 04:17.670 --> 04:19.350 And that's because the uplink profiles 117 04:19.350 --> 04:22.020 that we associated with ESXi-A and B 118 04:22.020 --> 04:24.360 didn't say to use vmnic3. 119 04:24.360 --> 04:26.460 But instead they're using a single vmnic. 120 04:26.460 --> 04:29.280 And that's vmnic2 on each of their respective hosts. 121 04:29.280 --> 04:30.960 And in association with that, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 04:29.280 --> 04:30.960 And in association with that, 122 04:30.960 --> 04:35.217 ESXi-A is using VLAN101 on its vmnic2, 123 04:35.217 --> 04:38.130 and ESXi-B is using VLAN102 124 04:38.130 --> 04:39.930 as we looked at in the earlier video. 125 04:39.930 --> 04:41.940 Now, if we clicked on this Segment 10 here 126 04:41.940 --> 04:43.380 inside the vSphere Client, 127 04:43.380 --> 04:44.700 let's take a look at a few details here. 128 04:44.700 --> 04:47.040 If we click on the Summary tab, it has this big N, 129 04:47.040 --> 04:49.290 which represents it's an NSX segment. 130 04:49.290 --> 04:53.280 There's also a smaller n right there in the icon. 131 04:53.280 --> 04:54.979 And this is showing us the VNI, 132 04:54.979 --> 04:57.710 that's a Virtual Network Identifier, 133 04:57.710 --> 05:01.800 and that's 68608 that's assigned by NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 133 04:57.710 --> 05:01.800 and that's 68608 that's assigned by NSX. 134 05:01.800 --> 05:03.480 It's also showing us that this segment 135 05:03.480 --> 05:05.550 belongs to this transport zone. 136 05:05.550 --> 05:08.070 It's also showing us that the NSX Manager 137 05:08.070 --> 05:10.800 who is managing and responsible for this segment 138 05:10.800 --> 05:13.247 is reachable at 192.168.1.10. 139 05:13.247 --> 05:15.060 That's the virtual IP address 140 05:15.060 --> 05:17.400 we set up for NSX Management Cluster. 141 05:17.400 --> 05:18.540 Here's the distributed switch 142 05:18.540 --> 05:20.417 that this new segment is associated with. 143 05:20.417 --> 05:22.500 And as we scroll down, it's also showing us 144 05:22.500 --> 05:25.500 how many host transport nodes, effectively, 145 05:25.500 --> 05:28.710 the ESXi hosts would have been enabled for NSX 146 05:28.710 --> 05:32.070 are associated and have access to this new segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 05:28.710 --> 05:32.070 are associated and have access to this new segment. 147 05:32.070 --> 05:33.840 Also, if we go to the Configure tab, 148 05:33.840 --> 05:36.480 unlike a normal distributed port group, 149 05:36.480 --> 05:38.280 there's nothing really we can configure here 150 05:38.280 --> 05:40.680 because all the configuration for this segment 151 05:40.680 --> 05:43.050 is gonna be done over in NSX. 152 05:43.050 --> 05:45.810 But once again, here it's showing the VNI number, 153 05:45.810 --> 05:48.240 it's showing us the transport zone it belongs to, 154 05:48.240 --> 05:50.310 and it's showing us the name of the segment as well. 155 05:50.310 --> 05:51.840 If we clicked on hosts, 156 05:51.840 --> 05:54.900 it would show us all the hosts associated with that segment. 157 05:54.900 --> 05:57.987 So, ESXi-A and B are both host transport nodes 158 05:57.987 --> 06:00.690 that have access to that segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 158 05:57.987 --> 06:00.690 that have access to that segment. 159 06:00.690 --> 06:03.030 So, we could run VMs on those hosts 160 06:03.030 --> 06:05.580 and have those VMs for their network connectivity 161 06:05.580 --> 06:06.810 connect to that segment. 162 06:06.810 --> 06:09.300 And then as far as VMs go, we have no VMs 163 06:09.300 --> 06:11.400 that are yet associated with that segment.