WEBVTT 1 00:00.000 --> 00:01.020 In this video, I'd like you to do 2 00:01.020 --> 00:04.050 a quick verification of this existing topology 3 00:04.050 --> 00:05.580 where we left off in a previous skill 4 00:05.580 --> 00:09.090 where we have two segments, segment 10, segment 20, 5 00:09.090 --> 00:12.780 and we also have two VMs on segment 10 6 00:12.780 --> 00:15.450 and two VMs on segment 20. 7 00:15.450 --> 00:17.760 So I just wanna verify our existing topology 8 00:17.760 --> 00:21.360 before we start adding onto it and including a new gateway. 9 00:21.360 --> 00:24.210 So here in the vSphere client, let's first of all verify 10 00:24.210 --> 00:25.440 that we have our network segments. 11 00:25.440 --> 00:27.840 We'll click right here on the network tab 12 00:27.840 --> 00:30.000 and then under our distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:30.000 --> 00:31.140 that we're using for NSX. 14 00:31.140 --> 00:32.700 Here we have our two port groups. 15 00:32.700 --> 00:36.240 We have segment 10 yellow and segment 20 pink. 16 00:36.240 --> 00:38.190 So there, right here, they both look good. 17 00:38.190 --> 00:40.950 And then also we can verify which VMs are connected there 18 00:40.950 --> 00:42.660 by clicking on the VMs tab. 19 00:42.660 --> 00:44.910 So with the networking selected, then selecting one 20 00:44.910 --> 00:46.500 of our segments here, we can see 21 00:46.500 --> 00:48.090 what the VMs tab selected up here on the right 22 00:48.090 --> 00:50.940 that we have host A VM on segment 10 23 00:50.940 --> 00:53.430 and also host B VM on segment 10. 24 00:53.430 --> 00:56.100 And those are both on A and B respectively. 25 00:56.100 --> 00:57.390 And let's just peek at our topology 26 00:57.390 --> 00:58.890 to make sure that's what we intended. 27 00:58.890 --> 01:02.100 So here in our topology we have host A VM segment 10 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 00:58.890 --> 01:02.100 So here in our topology we have host A VM segment 10 28 01:02.100 --> 01:05.460 right here and host BVM segment 10 right here. 29 01:05.460 --> 01:06.293 That looks good. 30 01:07.293 --> 01:09.000 So this guy's on host A and this one's on host B. 31 01:09.000 --> 01:12.360 And then we should also have host A VM segment 20 32 01:12.360 --> 01:14.310 running here on ESXi-A. 33 01:14.310 --> 01:16.440 And then here host B VM segment 20 34 01:16.440 --> 01:18.420 should be running on ESXi-B. 35 01:18.420 --> 01:21.540 So let's verify those two as well by looking at this segment 36 01:21.540 --> 01:23.610 and taking a look at the two VMs that are attached. 37 01:23.610 --> 01:26.280 So we'll make a road trip down to segment 20 38 01:26.280 --> 01:29.820 and our first one there is host a VM on segment 20, 39 01:29.820 --> 01:31.830 which is being hosted on ESXi-A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 01:29.820 --> 01:31.830 which is being hosted on ESXi-A, 40 01:31.830 --> 01:34.290 and then host B VM on segment 20, 41 01:34.290 --> 01:36.090 which is being hosted on segment B. 42 01:36.090 --> 01:38.910 Fantastic, so let's go ahead and power those on. 43 01:38.910 --> 01:41.010 Let me go back to the VMs and templates view. 44 01:41.010 --> 01:43.620 Let me click on this folder VMs for testing. 45 01:43.620 --> 01:45.090 We'll go ahead and click on the VMs tab 46 01:45.090 --> 01:47.130 and select 'em all at once and right click 47 01:47.130 --> 01:49.950 and just say power and power on. 48 01:49.950 --> 01:52.260 So because there's DHCP services 49 01:52.260 --> 01:55.920 and those two different segments, segment 10 and segment 20, 50 01:55.920 --> 01:57.390 and the clients are automatically set 51 01:57.390 --> 02:00.690 to get IP addresses via DHCP, they should be good to go. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 01:57.390 --> 02:00.690 to get IP addresses via DHCP, they should be good to go. 52 02:00.690 --> 02:01.523 So let's verify. 53 02:01.523 --> 02:04.020 Let's go to the VMC and host A on segment 10 54 02:04.020 --> 02:06.120 and let's open up a web console there 55 02:06.120 --> 02:09.090 and we'll confirm it's IP address within if config. 56 02:09.090 --> 02:10.050 And that looks good. 57 02:10.050 --> 02:12.360 It's IP address is 10.10.0.11 58 02:12.360 --> 02:14.760 And let's go to host B VM here on segment 10 59 02:14.760 --> 02:16.380 and click on web console. 60 02:16.380 --> 02:18.330 And let's do an if config here, 61 02:18.330 --> 02:19.470 verified its IP address. 62 02:19.470 --> 02:21.690 So this was a 10.10.0.10. 63 02:21.690 --> 02:25.050 The one over at host A is at 10.10.0.11 as we just saw. 64 02:25.050 --> 02:26.490 So let's do a ping real quick. 65 02:26.490 --> 02:28.740 Alright, so we've just done some basic validation 66 02:28.740 --> 02:30.690 that our infrastructure is in place WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 02:28.740 --> 02:30.690 that our infrastructure is in place 67 02:30.690 --> 02:33.420 and that would include that we have these four VMs 68 02:33.420 --> 02:35.670 that are currently running these two over here 69 02:35.670 --> 02:36.870 on two different segments. 70 02:36.870 --> 02:38.760 These two are here on two different segments. 71 02:38.760 --> 02:41.820 So all the devices on segment 10 can talk to each other. 72 02:41.820 --> 02:43.680 All the devices on segment 20 can communicate 73 02:43.680 --> 02:45.930 with each other except they can't get outside 74 02:45.930 --> 02:48.150 of their local segment because two reasons, 75 02:48.150 --> 02:49.950 they don't have a default gateway configured yet. 76 02:49.950 --> 02:53.100 And secondly, we don't have a default gateway yet either 77 02:53.100 --> 02:57.120 that it even exists as a distributed router inside of NSX. 78 02:57.120 --> 02:59.670 Also, as a verification of what we have in place, 79 02:59.670 --> 03:01.380 we could go to several places WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 02:59.670 --> 03:01.380 we could go to several places 80 03:01.380 --> 03:03.900 and ask, we could use the NSX CLI, we could go 81 03:03.900 --> 03:07.110 to the NSX manager, we could go to our transport nodes, 82 03:07.110 --> 03:08.370 we could go to our edge nodes. 83 03:08.370 --> 03:09.210 And pretty much, 84 03:09.210 --> 03:11.250 even though the syntax is slightly different 85 03:11.250 --> 03:13.110 at each of those devices, 86 03:13.110 --> 03:15.120 the information is very useful. 87 03:15.120 --> 03:17.557 And that is, for example, we can ask any of those devices, 88 03:17.557 --> 03:19.830 "Hey, what logical switches do you know about?" 89 03:19.830 --> 03:22.110 That's a fancy way or an older way I should say, 90 03:22.110 --> 03:23.730 of saying a segment. 91 03:23.730 --> 03:26.100 We could also say, "Hey, what logical routers do you have?" 92 03:26.100 --> 03:29.430 Which is a older way of saying which gateways exist. 93 03:29.430 --> 03:33.780 So as NSX continues to migrate to newer and newer versions WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 03:29.430 --> 03:33.780 So as NSX continues to migrate to newer and newer versions 94 03:33.780 --> 03:36.720 and newer code, they are migrating more away from some 95 03:36.720 --> 03:39.840 of the older commands, like get logical router 96 03:39.840 --> 03:41.460 and they're moving forward to the commands. 97 03:41.460 --> 03:43.260 They're gonna be similar to like get gateway. 98 03:43.260 --> 03:46.590 So let's open up an SSH session over here to ESXi-A 99 03:46.590 --> 03:48.450 and do a couple quick verifications 100 03:48.450 --> 03:50.850 and that will give us an opportunity to see before 101 03:50.850 --> 03:53.580 and after look regarding the distributed router 102 03:53.580 --> 03:54.630 that we're gonna be adding. 103 03:54.630 --> 03:56.310 So now that we're SSHed over 104 03:56.310 --> 03:59.040 to the EXI host called ESXi-A, 105 03:59.040 --> 04:01.410 we'll then move over to the NSX CLI WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 03:59.040 --> 04:01.410 we'll then move over to the NSX CLI 106 04:01.410 --> 04:05.100 by typing in NSX CLI and pressing enter. 107 04:05.100 --> 04:06.330 And boom, now we're sitting 108 04:06.330 --> 04:08.730 at the NSX command line interface 109 04:08.730 --> 04:11.610 on this NSX host transport node. 110 04:11.610 --> 04:14.520 So here we can issue commands like get logical switch 111 04:14.520 --> 04:15.750 and no space and a question mark. 112 04:15.750 --> 04:17.186 And that's showing us 113 04:17.186 --> 04:18.540 that we could use the command logical switches 114 04:18.540 --> 04:19.920 or we could do a logical switch. 115 04:19.920 --> 04:21.390 Then put further information 116 04:21.390 --> 04:23.310 about a specific logical switch. 117 04:23.310 --> 04:26.520 So if we do a get logical switches, this command right here, 118 04:26.520 --> 04:30.000 this is showing us the logical layer two broadcast domains WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 119 04:30.000 --> 04:30.990 provided by NSX. 120 04:30.990 --> 04:33.450 So these are also referred to as segments. 121 04:33.450 --> 04:35.940 And the reason that this ESXi host 122 04:35.940 --> 04:37.290 knows about these two segments 123 04:37.290 --> 04:40.740 is because it has been included as part of NSX 124 04:40.740 --> 04:42.000 as a host transport node 125 04:42.000 --> 04:46.270 and it has VMs that are connected to both those segments. 126 04:46.270 --> 04:49.380 So if an ESXi host is not supporting a transport zone, 127 04:49.380 --> 04:50.610 where a segment exists, 128 04:50.610 --> 04:52.350 that logical switch wouldn't show up. 129 04:52.350 --> 04:54.420 And also as NSX moves forward, 130 04:54.420 --> 04:57.540 they're moving towards a new slightly modified command sets. 131 04:57.540 --> 04:59.760 So we could use a get segment command, still do get segment, 132 04:59.760 --> 05:01.350 no space and a question mark. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 04:59.760 --> 05:01.350 no space and a question mark. 133 05:01.350 --> 05:02.580 And this is showing us 134 05:02.580 --> 05:03.413 that we could use the command segments 135 05:03.413 --> 05:04.680 to see a list of segments 136 05:04.680 --> 05:07.110 or we could type in segment and the UUID 137 05:07.110 --> 05:08.700 or the VNI and go further. 138 05:08.700 --> 05:10.620 So if we do a get segments, 139 05:10.620 --> 05:12.780 look at the output here, it's identical. 140 05:12.780 --> 05:14.700 Just think of it as a more current way 141 05:14.700 --> 05:17.460 of issuing the command get logical switches 142 05:17.460 --> 05:19.590 'cause at the end of the day, they're very, very similar. 143 05:19.590 --> 05:20.730 And as time goes forward, 144 05:20.730 --> 05:22.350 they're migrating towards the new commands. 145 05:22.350 --> 05:25.110 So to contrast that, if you do a get logical switches 146 05:25.110 --> 05:28.200 and press enter, if the output looks very, very similar, 147 05:28.200 --> 05:29.610 that's because it is. 148 05:29.610 --> 05:30.930 So those are our two segments. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 148 05:29.610 --> 05:30.930 So those are our two segments. 149 05:30.930 --> 05:33.390 So how do we know if we have a distributed router 150 05:33.390 --> 05:35.880 on this NSX host transport node? 151 05:35.880 --> 05:39.330 Well, we could issue the command get space logical routers. 152 05:39.330 --> 05:40.560 That'd be one option. 153 05:40.560 --> 05:42.690 So currently it's saying you have no logical routers, 154 05:42.690 --> 05:45.180 but a more current way of doing that same output 155 05:45.180 --> 05:48.660 is doing a get gateways, which is also showing us 156 05:48.660 --> 05:52.350 that we have no logical layer three routers set up yet. 157 05:52.350 --> 05:55.500 Again, that was looking here at ESXi-A 158 05:55.500 --> 05:56.430 and also just be aware 159 05:56.430 --> 05:58.560 if we did have a logical layer three gateway set up, 160 05:58.560 --> 06:01.680 but this ESXi host didn't have any segments WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 160 05:58.560 --> 06:01.680 but this ESXi host didn't have any segments 161 06:01.680 --> 06:03.810 that were connected to that logical gateway, 162 06:03.810 --> 06:06.750 NSX wouldn't bother putting a copy 163 06:06.750 --> 06:08.340 or an instance of a distributed router 164 06:08.340 --> 06:11.730 on an ESXi transport node if it didn't need it. 165 06:11.730 --> 06:14.520 However, if we do have a logical gateway set up 166 06:14.520 --> 06:16.560 and it's supporting segment 10 167 06:16.560 --> 06:19.920 and this host transport node has VMs on that segment, 168 06:19.920 --> 06:23.460 it's at that moment, that's what's going to cause NSX 169 06:23.460 --> 06:25.050 to have a copy, if you will, 170 06:25.050 --> 06:27.750 of that distributed router function located 171 06:27.750 --> 06:28.860 on this transport nodes. 172 06:28.860 --> 06:31.770 So this transport node can make its own routing decisions WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 172 06:28.860 --> 06:31.770 So this transport node can make its own routing decisions 173 06:31.770 --> 06:33.153 between those two segments.