WEBVTT 1 00:00.210 --> 00:01.230 So in the previous video, 2 00:01.230 --> 00:03.210 we confirmed that those three distributed routers 3 00:03.210 --> 00:05.370 exist on our transport nodes. 4 00:05.370 --> 00:07.920 And now the challenge is that Tier Zero has 5 00:07.920 --> 00:10.620 no idea from a routing perspective how to 6 00:10.620 --> 00:13.080 reach the 10.10 network or the 10.20 network. 7 00:13.080 --> 00:15.150 So to solve that, we're gonna train the tier one level 8 00:15.150 --> 00:18.330 routers to advertise their directly connected networks. 9 00:18.330 --> 00:20.820 So that's what we get to do right now. 10 00:20.820 --> 00:23.610 So to train Gateway A and Gateway B to advertise 11 00:23.610 --> 00:25.683 their directly connected networks, 12 00:25.683 --> 00:27.720 so in Gateway A, it'd be the 10.10.0 address base. 13 00:27.720 --> 00:30.210 And on gateway B, it'd be 10.20.0 address base. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:27.720 --> 00:30.210 And on gateway B, it'd be 10.20.0 address base. 14 00:30.210 --> 00:33.060 To do that, we're gonna go to each of the tier one gateways 15 00:33.060 --> 00:34.740 and tell them please advertise. 16 00:34.740 --> 00:36.930 So with networking selected over on the left, 17 00:36.930 --> 00:38.790 we'll click on our tier one gateways 18 00:38.790 --> 00:40.890 and let's go ahead and begin with Gateway A. 19 00:40.890 --> 00:42.600 So we expand that and we go down 20 00:42.600 --> 00:43.650 here to route advertisement. 21 00:43.650 --> 00:46.590 Currently we are not by default advertising 22 00:46.590 --> 00:48.570 all connected segments, so we wanna do that. 23 00:48.570 --> 00:51.360 So we'll click on the three dots, click on edit 24 00:51.360 --> 00:53.700 and then here in the route advertisement section. 25 00:53.700 --> 00:54.840 And we'll simply tell that we do wanna 26 00:54.840 --> 00:56.430 advertise all connected segments. 27 00:56.430 --> 00:58.560 We'll scroll down and click on save. 28 00:58.560 --> 01:00.570 And then we'll close editing for that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:58.560 --> 01:00.570 And then we'll close editing for that 29 01:00.570 --> 01:03.180 first gateway, Gateway A, we'll collapse that. 30 01:03.180 --> 01:05.220 And then we'll do the same thing for Gateway B, 31 01:05.220 --> 01:07.380 we'll click on edit for Gateway B. 32 01:07.380 --> 01:09.180 And then under route advertisement, 33 01:09.180 --> 01:10.680 we'll tell it that we want to go ahead 34 01:10.680 --> 01:12.870 and advertise all connected segments. 35 01:12.870 --> 01:14.970 Scroll down a little further, click on save 36 01:14.970 --> 01:16.740 and then click on close editing. 37 01:16.740 --> 01:19.470 And now, if we go back to the routing table 38 01:19.470 --> 01:23.280 for this logical Tier Zero Gateway, zero device, 39 01:23.280 --> 01:26.010 what we should see is we should see routes 40 01:26.010 --> 01:28.290 and information in the routing table on how to 41 01:28.290 --> 01:31.530 reach the 10.10 network and also the 10.20 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:28.290 --> 01:31.530 reach the 10.10 network and also the 10.20 network. 42 01:31.530 --> 01:34.080 And to verify that this Tier Zero Gateway now has 43 01:34.080 --> 01:36.480 the routes to 10.10 and also to 10.20, 44 01:36.480 --> 01:39.480 we could go to any one of our transport nodes, 45 01:39.480 --> 01:42.120 the edge nodes or the host transport nodes, 46 01:42.120 --> 01:44.970 all of them because they'll have a copy effectively of 47 01:44.970 --> 01:47.310 that routing instance for Tier Zero Gateway. 48 01:47.310 --> 01:48.540 Any one of them would be able 49 01:48.540 --> 01:49.680 to show us that information. 50 01:49.680 --> 01:51.540 So let's actually do a couple. 51 01:51.540 --> 01:53.880 Let's go to ESXi-A as a transport node 52 01:53.880 --> 01:55.290 and also edge One. 53 01:55.290 --> 01:57.510 And we'll ask both of them to confirm 54 01:57.510 --> 02:00.270 the routing table here on our Tier Zero Gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 01:57.510 --> 02:00.270 the routing table here on our Tier Zero Gateway. 55 02:00.270 --> 02:03.150 So at the top we've got the NSX CLI for edge one, 56 02:03.150 --> 02:06.613 and I've just SSH here to ESXi-A. 57 02:06.613 --> 02:08.460 So here in the window for E ESXi-A, let's go ahead 58 02:08.460 --> 02:11.130 and type in NSX CLI and press enter. 59 02:11.130 --> 02:13.470 That'll take us to the NSX CLI interface. 60 02:13.470 --> 02:14.520 Fantastic. 61 02:14.520 --> 02:16.500 And then from here the commands, even though we can 62 02:16.500 --> 02:18.540 get the same information they're slightly different 63 02:18.540 --> 02:20.880 on an edge node versus a host transport nodes. 64 02:20.880 --> 02:22.620 So a couple of commands might be identical. 65 02:22.620 --> 02:25.020 And then for example, going into VRFs on the edge 66 02:25.020 --> 02:25.853 is slightly different. 67 02:25.853 --> 02:27.810 So let me bring up the command window. 68 02:27.810 --> 02:29.730 We'll click on view, command window. 69 02:29.730 --> 02:30.930 And for the commands that are the same, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 02:29.730 --> 02:30.930 And for the commands that are the same, 70 02:30.930 --> 02:32.610 we can just use the command window to send it 71 02:32.610 --> 02:33.900 to both sessions at the same time. 72 02:33.900 --> 02:36.600 Let's do a get gateways and press enter. 73 02:36.600 --> 02:39.750 So on the edge VRF zero is the transport 74 02:39.750 --> 02:41.730 network information as it works with 75 02:41.730 --> 02:43.140 and interacts with the physical network 76 02:43.140 --> 02:44.400 or the transport network. 77 02:44.400 --> 02:46.290 And then the bottom three represent Gateway A, 78 02:46.290 --> 02:48.540 Gateway B and our Tier Zero Gateway. 79 02:48.540 --> 02:49.650 So we can confirm that as well. 80 02:49.650 --> 02:52.650 So here we have the Gateway A matching up 81 02:52.650 --> 02:54.950 with this one right here down on ESXi-A. 82 02:54.950 --> 02:57.300 So the UUID is exactly the same 83 02:57.300 --> 02:59.280 because it's the same distributed router. 84 02:59.280 --> 03:00.960 And then we go to Gateway B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 02:59.280 --> 03:00.960 And then we go to Gateway B 85 03:00.960 --> 03:03.210 and look at it here on edge one. 86 03:03.210 --> 03:06.153 That's also right here on ESXi-A. 87 03:06.153 --> 03:07.590 And then for the Tier Zero Gateway, 88 03:07.590 --> 03:10.830 and here's that same UUID here on ESXi-A. 89 03:10.830 --> 03:13.860 So here if we did a get gateway space 90 03:13.860 --> 03:15.900 and we plugged in this UUID 91 03:15.900 --> 03:18.570 or let's go ahead and do it for the Tier Zero Gateway. 92 03:18.570 --> 03:22.140 So I'll go ahead and take that UUID and paste it in. 93 03:22.140 --> 03:25.290 Then we did space and let's do forwarding and press enter. 94 03:25.290 --> 03:27.193 So this has both the IPV four 95 03:27.193 --> 03:28.260 and IPV six information. 96 03:28.260 --> 03:30.810 Let me scroll down just a little bit in both windows. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 96 03:28.260 --> 03:30.810 Let me scroll down just a little bit in both windows. 97 03:30.810 --> 03:32.340 And here we have the routing table on both. 98 03:32.340 --> 03:34.650 So here is the 10.10 network from the 99 03:34.650 --> 03:37.920 perspective of edge one for that virtual router. 100 03:37.920 --> 03:39.960 And here's the same route for that logical router. 101 03:39.960 --> 03:43.950 Here on ESXi-A there's the route for the 10.20 network. 102 03:43.950 --> 03:45.990 And that same route here again on 103 03:45.990 --> 03:47.040 two different transport nodes, 104 03:47.040 --> 03:48.360 on the top we have the edge. 105 03:48.360 --> 03:50.280 And at the bottom we have the host transport node. 106 03:50.280 --> 03:51.750 And then for these two subnets right here, 107 03:51.750 --> 03:54.450 the /31s they also exist here, 108 03:54.450 --> 03:56.010 shown here and here. 109 03:56.010 --> 03:58.170 So up on edge one, we have a 32 bit route 110 03:58.170 --> 04:00.150 for an actual interface IP address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 03:58.170 --> 04:00.150 for an actual interface IP address. 111 04:00.150 --> 04:01.380 That's a 32 bit route. 112 04:01.380 --> 04:03.810 While at the same time for that 10.64.0 network, 113 04:03.810 --> 04:07.380 we simply have the network route here on our transport node. 114 04:07.380 --> 04:09.120 And instead of forwarding, we use the option 115 04:09.120 --> 04:11.040 of interfaces and pressed enter. 116 04:11.040 --> 04:12.690 It's now showing us the interfaces 117 04:12.690 --> 04:14.400 associated with that gateway. 118 04:14.400 --> 04:16.200 So we scroll up on each of them. 119 04:16.200 --> 04:17.040 Even though the output is 120 04:17.040 --> 04:18.570 formatted a little bit differently. 121 04:18.570 --> 04:20.790 Here we have the UUID for each interface, which again, 122 04:20.790 --> 04:22.710 is the same on both 'cause we're talking about 123 04:22.710 --> 04:24.660 the same logical router interface. 124 04:24.660 --> 04:28.170 And for the interface, it has this IP address 125 04:28.170 --> 04:30.240 that's one of the interface addresses we're using WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 125 04:28.170 --> 04:30.240 that's one of the interface addresses we're using 126 04:30.240 --> 04:33.390 on the uplink between Tier Zero and T one. 127 04:33.390 --> 04:34.860 Here's the layer two address associated 128 04:34.860 --> 04:36.060 with that IP address. 129 04:36.060 --> 04:38.220 There's the VNI on both of them. 130 04:38.220 --> 04:40.320 Also up here on the edge it's showing the name. 131 04:40.320 --> 04:42.270 So the formatting and the output is slightly different, 132 04:42.270 --> 04:43.770 but the information's the same. 133 04:43.770 --> 04:45.870 So the LRP at the end here simply represents 134 04:45.870 --> 04:48.000 logical router report in the name. 135 04:48.000 --> 04:49.980 So this is the Gateway Zero interface that's connecting 136 04:49.980 --> 04:52.020 based on the name down here to Gateway B. 137 04:52.020 --> 04:53.700 And if we scroll down far enough, we should also have 138 04:53.700 --> 04:56.370 an interface for the connection down to Gateway A, 139 04:56.370 --> 04:57.203 which we do right here. 140 04:57.203 --> 04:59.828 So here is the UUID. 141 04:59.828 --> 05:01.590 This is from the perspective of edge one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 141 04:59.828 --> 05:01.590 This is from the perspective of edge one. 142 05:01.590 --> 05:03.630 And if we find that same interface down here 143 05:03.630 --> 05:06.360 on the transport node, here it is right here, 144 05:06.360 --> 05:10.950 same exact UUID, same exact VNI number as shown on both. 145 05:10.950 --> 05:12.570 Same exact layer three and layer two 146 05:12.570 --> 05:14.040 information shown on both. 147 05:14.040 --> 05:16.260 And one of the differences as far as commands go 148 05:16.260 --> 05:19.530 is that if we do a get gateways and press enter here, 149 05:19.530 --> 05:22.200 the edge is gonna have its own VRF zero, 150 05:22.200 --> 05:24.090 which is all that its own transport routes. 151 05:24.090 --> 05:26.610 And the actual host transport nodes are not going to 152 05:26.610 --> 05:28.440 include that in the output of get gateway. 153 05:28.440 --> 05:30.750 So you might ask, well, how does the ESXi host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 153 05:28.440 --> 05:30.750 So you might ask, well, how does the ESXi host 154 05:30.750 --> 05:32.580 keep traffic with its own routes if the edge 155 05:32.580 --> 05:35.430 is using VRF Zero, what does the host do? 156 05:35.430 --> 05:37.920 And the answer to that is the host has its own default 157 05:37.920 --> 05:40.740 routing set up based on the ESXi host we're sitting at. 158 05:40.740 --> 05:42.990 So if we typed in exit here to exit out 159 05:42.990 --> 05:46.290 of the NSX CLI for ESXi-A, 160 05:46.290 --> 05:48.840 so here out of NSX CLI mode if we use the 161 05:48.840 --> 05:52.380 traditional ESX CLI we use the command ESX CLI 162 05:52.380 --> 05:55.740 network IP route IPV four list, that's a mouthful I know. 163 05:55.740 --> 05:59.370 But that will show us the routing table on this ESXi host. 164 05:59.370 --> 06:02.730 So here it's showing that with my VM kernel zero adapter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 164 05:59.370 --> 06:02.730 So here it's showing that with my VM kernel zero adapter, 165 06:02.730 --> 06:04.980 I'm connected to the 192.168.1 network. 166 06:04.980 --> 06:07.350 And that's for management of this ESXi host. 167 06:07.350 --> 06:10.110 I'm also connected to the 10.4.0 network using the 168 06:10.110 --> 06:12.480 VM kernel adapter of VM Gate One and that's for access 169 06:12.480 --> 06:15.450 to an iSCSI data store on a iSCSI network. 170 06:15.450 --> 06:17.070 Then I have a default route also associated 171 06:17.070 --> 06:18.810 with VM kernel zero that's using a 172 06:18.810 --> 06:22.330 default route next top of 192.168.1.1.