WEBVTT 1 00:00.120 --> 00:01.170 So based on our game plan, 2 00:01.170 --> 00:02.880 our first step here is to create 3 00:02.880 --> 00:06.230 this brand new Tier-1 gateway instead of NSX. 4 00:06.230 --> 00:08.880 So to do that we're gonna go over to our NSX manager 5 00:08.880 --> 00:10.380 and create the gateway. 6 00:10.380 --> 00:12.930 So here on the homepage for the NSX manager, 7 00:12.930 --> 00:16.590 it shows us in networking that we have one Tier-1 gateway, 8 00:16.590 --> 00:18.990 and that's the Gateway A that we put in previously 9 00:18.990 --> 00:20.040 in our previous skill. 10 00:20.040 --> 00:21.180 So to create a new gateway, 11 00:21.180 --> 00:24.240 we're gonna click right here on the Networking tab. 12 00:24.240 --> 00:25.980 And with the Networking tab selected, 13 00:25.980 --> 00:27.120 again, it's confirming for us 14 00:27.120 --> 00:28.650 that we have one Tier-1 gateway. 15 00:28.650 --> 00:30.900 It's also fun, I think, to take a look WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:28.650 --> 00:30.900 It's also fun, I think, to take a look 16 00:30.900 --> 00:32.460 at the topology occasionally. 17 00:32.460 --> 00:35.327 So here's our current topology, Gateway A 18 00:35.327 --> 00:37.800 and we have Segment 10, Segment 20, 19 00:37.800 --> 00:40.860 and then inside of that we have two VMs on Segment 10 20 00:40.860 --> 00:42.780 and two VMs on Segment 20. 21 00:42.780 --> 00:44.370 I also took a moment and made sure 22 00:44.370 --> 00:47.160 that VM-1 has the address of 10.10.0.10, 23 00:47.160 --> 00:50.130 and VM-2 has the address of 10.20.0.20. 24 00:50.130 --> 00:51.990 And I'm thinking a moment right here just to confirm 25 00:51.990 --> 00:53.610 that that accurately is reflected here. 26 00:53.610 --> 00:57.990 So VM-1 and VM-2, which are both on ESXi-A, 27 00:57.990 --> 00:59.670 they're in two different segments and subnets. 28 00:59.670 --> 01:01.920 And there are their respective IP addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:59.670 --> 01:01.920 And there are their respective IP addresses. 29 01:01.920 --> 01:03.330 And if they ever need to forward traffic 30 01:03.330 --> 01:04.710 off their local subnet, 31 01:04.710 --> 01:07.290 they're gonna use the default Gateway address of .1 32 01:07.290 --> 01:08.700 on their respective subnet. 33 01:08.700 --> 01:09.540 All right, so that looks good, 34 01:09.540 --> 01:11.220 so let's create our second gateway, 35 01:11.220 --> 01:12.600 our second Tier-1 gateway, 36 01:12.600 --> 01:15.570 and we're gonna call it our Tier-1 Gateway B. 37 01:15.570 --> 01:18.540 So to do that with the Networking tab selected on the left, 38 01:18.540 --> 01:20.640 we'll click right here on Tier-1 gateways. 39 01:20.640 --> 01:23.190 So there's our current one, so I'll collapse that. 40 01:23.190 --> 01:26.400 And let's go ahead and click on add Tier-1 gateway. 41 01:26.400 --> 01:29.460 So let's go ahead and call this our Tier-1 Gateway B. 42 01:29.460 --> 01:31.050 And then for the HA mode, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 01:29.460 --> 01:31.050 And then for the HA mode, 43 01:31.050 --> 01:33.240 here I'm gonna specify distributed only. 44 01:33.240 --> 01:35.100 And the reason for that is that I wanna make sure 45 01:35.100 --> 01:36.570 we're only implementing distributor routers 46 01:36.570 --> 01:39.600 and not adding on top of that service routers as well. 47 01:39.600 --> 01:41.533 So anytime we're doing, for example, 48 01:41.533 --> 01:44.160 a Tier-1 gateways active standby, 49 01:44.160 --> 01:46.410 that's gonna invoke the services router. 50 01:46.410 --> 01:48.900 Or if we start implementing Nat or VPNs 51 01:48.900 --> 01:50.460 or other types of network services, 52 01:50.460 --> 01:51.780 that's also going to invoke 53 01:51.780 --> 01:54.210 an additional logical services router 54 01:54.210 --> 01:56.130 for those specific functions. 55 01:56.130 --> 01:57.870 But for now, I wanna make sure we're just doing 56 01:57.870 --> 02:00.510 distributed routers and not the additional services router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 01:57.870 --> 02:00.510 distributed routers and not the additional services router. 57 02:00.510 --> 02:02.010 And that's the reason for the demo here. 58 02:02.010 --> 02:03.600 I'm gonna choose distributed mode 59 02:03.600 --> 02:06.030 for the second Tier-1 gateway. 60 02:06.030 --> 02:08.370 And so here it has an option to link this 61 02:08.370 --> 02:11.760 to a Tier-0 gateway, but because we don't have one yet, 62 02:11.760 --> 02:12.780 there's nothing to choose. 63 02:12.780 --> 02:15.480 That'll change after we create a Tier-0 gateway 64 02:15.480 --> 02:16.710 and there's nothing else required. 65 02:16.710 --> 02:18.660 So we can go ahead and click on Save 66 02:18.660 --> 02:20.220 and then scroll down a little bit 67 02:20.220 --> 02:21.870 and then it's asking if we wanna continue. 68 02:21.870 --> 02:23.370 So we'll click on No. 69 02:23.370 --> 02:24.757 And sometimes they'll have that option of, 70 02:24.757 --> 02:26.040 "Do you wanna continue, yes or no?" 71 02:26.040 --> 02:27.900 Because they need to create the object first, 72 02:27.900 --> 02:30.690 in this case, the gateway, and then you can go in further WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 02:27.900 --> 02:30.690 in this case, the gateway, and then you can go in further 73 02:30.690 --> 02:32.610 and configure additional features. 74 02:32.610 --> 02:33.480 So we've got this created, 75 02:33.480 --> 02:34.800 I'm gonna go ahead and collapse it. 76 02:34.800 --> 02:37.290 And now we have our two Tier-1 gateways, 77 02:37.290 --> 02:39.150 Gateway A and Gateway B. 78 02:39.150 --> 02:40.950 And if we click on the network topology, 79 02:40.950 --> 02:42.090 it's gonna reflect that as well. 80 02:42.090 --> 02:44.280 So here's our Tier-1 Gateway A 81 02:44.280 --> 02:46.680 connected to our two segments, and here's Gateway B 82 02:46.680 --> 02:48.150 that's not connected to either one. 83 02:48.150 --> 02:50.640 So to make this look like our topology, 84 02:50.640 --> 02:52.350 and let's take a quick peek at that real quick. 85 02:52.350 --> 02:54.840 We wanna make sure that this gateway here, 86 02:54.840 --> 02:57.720 the Tier-1 Gateway B is connected to Segment 20, 87 02:57.720 --> 03:00.480 and we wanna reconfigure Tier-1 Gateway A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 02:57.720 --> 03:00.480 and we wanna reconfigure Tier-1 Gateway A, 88 03:00.480 --> 03:02.310 so it's only connected to Segment 10. 89 03:02.310 --> 03:04.320 So to do that on the Tier-1 gateways, 90 03:04.320 --> 03:06.330 we're gonna go to the segments themselves 91 03:06.330 --> 03:08.370 and specify from the segment perspective 92 03:08.370 --> 03:11.640 which logical gateway they're connected to. 93 03:11.640 --> 03:13.950 So let's do that by going to Segment 20 94 03:13.950 --> 03:14.887 and telling Segment 20, 95 03:14.887 --> 03:17.250 "Hey, you're no longer connected to Gateway A. 96 03:17.250 --> 03:18.690 Instead we want you to be connected 97 03:18.690 --> 03:20.490 and associated with Gateway B." 98 03:20.490 --> 03:22.350 So to do that, we'll go to our segments. 99 03:22.350 --> 03:24.210 So on the networking tab up here, 100 03:24.210 --> 03:25.860 we'll go down to segments on the left 101 03:25.860 --> 03:29.070 and we're gonna go to the Segment 20 Pink 102 03:29.070 --> 03:30.510 and we're gonna edit it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 03:29.070 --> 03:30.510 and we're gonna edit it. 103 03:30.510 --> 03:32.280 So we'll go ahead and click on the three dots, 104 03:32.280 --> 03:33.930 from the menu, we'll click on Edit, 105 03:33.930 --> 03:35.460 and then I'm gonna collapse the left-hand column here 106 03:35.460 --> 03:37.200 to give us a little more room to play with. 107 03:37.200 --> 03:38.820 And so currently Segment 20 108 03:38.820 --> 03:42.210 says it's connected to Tier-1 Gateway A, 109 03:42.210 --> 03:43.657 and what we wanna do is use the dropdown and say, 110 03:43.657 --> 03:45.360 "You know what? We don't want you to connect there. 111 03:45.360 --> 03:46.620 Instead we're gonna connect you over 112 03:46.620 --> 03:50.520 to this second Tier-1 gateway, Tier-1 Gateway B." 113 03:50.520 --> 03:53.430 And check this out, because we had already put in 10.20.0.1 114 03:53.430 --> 03:56.070 as the IP address for this connection, 115 03:56.070 --> 03:58.400 that logical IP address 10.20.0.1 116 03:58.400 --> 04:00.930 is now gonna be associated as the interface address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 03:58.400 --> 04:00.930 is now gonna be associated as the interface address 117 04:00.930 --> 04:03.360 for Gateway B's connection to the Segment 20. 118 04:03.360 --> 04:05.370 So that's the only thing we need to change here. 119 04:05.370 --> 04:07.500 So we'll scroll down, click on save, 120 04:07.500 --> 04:09.480 and then click here on close editing. 121 04:09.480 --> 04:11.220 And then over here it says In Progress, 122 04:11.220 --> 04:13.770 we'll click on the refresh button, and that looks good. 123 04:13.770 --> 04:16.380 So if we expand the left hand column again, 124 04:16.380 --> 04:18.690 and now click here on network topology. 125 04:18.690 --> 04:20.910 It's now showing us that we have Gateway A 126 04:20.910 --> 04:23.520 connected to Segment 10 and we have Gateway B 127 04:23.520 --> 04:25.410 that's now connected to Segment 20. 128 04:25.410 --> 04:26.780 So the service here, if we hover over it, 129 04:26.780 --> 04:28.500 it says we have some default gateway 130 04:28.500 --> 04:29.820 firewall rules are in place. 131 04:29.820 --> 04:32.520 By default they're permitting all traffic, which is fine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 131 04:29.820 --> 04:32.520 By default they're permitting all traffic, which is fine. 132 04:32.520 --> 04:33.990 And then down here on the segments themselves, 133 04:33.990 --> 04:36.360 previously I set up DHCP services 134 04:36.360 --> 04:39.180 to hand out IP addresses to the clients. 135 04:39.180 --> 04:42.330 So VM-1 has the address of 10.10.0.10 136 04:42.330 --> 04:43.890 and VM-3 also on that same segment 137 04:43.890 --> 04:47.040 has the address of 10.10.0.11, while on Segment 20, 138 04:47.040 --> 04:49.740 VM-2 has the address of 10.20.0.20. 139 04:49.740 --> 04:52.710 And VM-4 has the address of 10.20.0.21. 140 04:52.710 --> 04:54.840 So that's what these services are referring to here 141 04:54.840 --> 04:58.020 at the segment level and also here at the gateway level. 142 04:58.020 --> 04:59.700 And behind the scenes, I thought it'd be fun 143 04:59.700 --> 05:03.150 to take a peek at our transport nodes, ESXi-A and B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 143 04:59.700 --> 05:03.150 to take a peek at our transport nodes, ESXi-A and B 144 05:03.150 --> 05:05.400 and also our edge nodes and just verify 145 05:05.400 --> 05:09.120 that all four of those transport nodes have instances 146 05:09.120 --> 05:11.490 of Gateway A and Gateway B. 147 05:11.490 --> 05:13.170 And a pretty direct way of verifying that 148 05:13.170 --> 05:15.240 is to just open up an SSH session. 149 05:15.240 --> 05:18.720 And that way we can look at the three logical routers 150 05:18.720 --> 05:21.150 that are representing our Tier-0 Gateway 0, 151 05:21.150 --> 05:24.180 Tier-1 Gateway A, and our Tier-1 Gateway B. 152 05:24.180 --> 05:26.100 So here on the top half I've got a session over 153 05:26.100 --> 05:29.490 to the ESXi-A host, and down here I've got a connection 154 05:29.490 --> 05:33.510 over to the ESXi-B and to enter the NSX CLI environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 05:29.490 --> 05:33.510 over to the ESXi-B and to enter the NSX CLI environment 155 05:33.510 --> 05:36.360 on both of them, we simply type in nsxcli. 156 05:36.360 --> 05:37.620 So I'm typing that down here 157 05:37.620 --> 05:39.090 and simply gonna send that command 158 05:39.090 --> 05:41.130 to both windows simultaneously. 159 05:41.130 --> 05:43.110 All right, so we are in the NSX CLI 160 05:43.110 --> 05:44.880 for both of these transport nodes. 161 05:44.880 --> 05:48.120 And let's start off with a get gateways, 162 05:48.120 --> 05:51.510 which you could also type in get logical routers, 163 05:51.510 --> 05:54.090 that would also work, same exact results here. 164 05:54.090 --> 05:55.410 Except the command gateways 165 05:55.410 --> 05:57.420 is the direction that NSX is moving to 166 05:57.420 --> 05:59.070 as far as the command line interface. 167 05:59.070 --> 06:02.280 So those up here we have two distributed routers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 167 05:59.070 --> 06:02.280 So those up here we have two distributed routers 168 06:02.280 --> 06:05.490 that ESXi-A knows about and down here on ESXi-B, 169 06:05.490 --> 06:08.880 we have the same exact two distributed routers. 170 06:08.880 --> 06:11.280 So if we use the command get gateway 171 06:11.280 --> 06:12.610 and let's plug in this first UUID, 172 06:12.610 --> 06:15.270 which represents one of our routers. 173 06:15.270 --> 06:16.650 So we use that first one on the list 174 06:16.650 --> 06:17.850 and then let's put in a space 175 06:17.850 --> 06:21.180 and let's go ahead and ask for forwarding and press enter. 176 06:21.180 --> 06:22.740 And that's gonna show us the forwarding table. 177 06:22.740 --> 06:25.530 So based on the results there, we're looking at Gateway B 178 06:25.530 --> 06:28.200 because it is directly connected to the 10.20.0 network, 179 06:28.200 --> 06:29.790 and that's what we're seeing right here. 180 06:29.790 --> 06:31.500 So if we looked at the second entry here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 180 06:29.790 --> 06:31.500 So if we looked at the second entry here, 181 06:31.500 --> 06:33.630 lemme go ahead and copy that into my buffer. 182 06:33.630 --> 06:35.937 So now if we did a get gateway 183 06:35.937 --> 06:38.190 and we'll plug in the UUID with a paste 184 06:38.190 --> 06:40.470 and then we said forwarding and pressed enter, 185 06:40.470 --> 06:42.330 it's gonna show us the routing table 186 06:42.330 --> 06:44.580 effectively for that gateway, 187 06:44.580 --> 06:46.590 which in this case based on the IP address here, 188 06:46.590 --> 06:49.020 that is Gateway A, that's directly connected 189 06:49.020 --> 06:50.580 to the 10.10.0 network. 190 06:50.580 --> 06:52.500 So if we were to look at the interfaces 191 06:52.500 --> 06:54.540 for that virtual router, we could go ahead 192 06:54.540 --> 06:57.120 and type in get gateway, that UUID again 193 06:57.120 --> 06:59.730 and then type in interfaces and press enter. 194 06:59.730 --> 07:01.290 Still there is the command that we issued WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 194 06:59.730 --> 07:01.290 Still there is the command that we issued 195 07:01.290 --> 07:03.480 on both of them simultaneously 196 07:03.480 --> 07:05.010 and both of them have this interface. 197 07:05.010 --> 07:08.070 Here's the UUID associated with this first interface 198 07:08.070 --> 07:10.320 that's showing us and they both have 199 07:10.320 --> 07:11.970 the same exact IP address 200 07:11.970 --> 07:13.680 because it's the same distributed router, 201 07:13.680 --> 07:16.200 they're both supporting for that virtual IP address, 202 07:16.200 --> 07:18.540 associated with that gateway, the same MAC address 203 07:18.540 --> 07:19.680 which is right here, 204 07:19.680 --> 07:22.050 which is associated with this distributed switch 205 07:22.050 --> 07:24.480 called DS for NSX, and it's also associated 206 07:24.480 --> 07:27.630 with this VNI of 68608. 207 07:27.630 --> 07:29.640 And again that information is consistent on both of them 208 07:29.640 --> 07:32.400 because they both have effectively the exact same copy WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 208 07:29.640 --> 07:32.400 because they both have effectively the exact same copy 209 07:32.400 --> 07:33.780 of the distributed router. 210 07:33.780 --> 07:36.840 So again here, to summarize, if we did a get gateways 211 07:36.840 --> 07:39.390 or if we did the older command get logical routers, 212 07:39.390 --> 07:40.530 it's the same exact output. 213 07:40.530 --> 07:43.050 Again, they're migrating towards get gateways 214 07:43.050 --> 07:44.820 instead of the get logical routers. 215 07:44.820 --> 07:47.850 And also at layer two they're migrating to get segments 216 07:47.850 --> 07:50.460 as opposed to get logical switches. 217 07:50.460 --> 07:51.690 All right, so now that we've looked 218 07:51.690 --> 07:53.610 at the distributed routers so far 219 07:53.610 --> 07:57.630 for Gateway A and Gateway B on both ESXi-A and B 220 07:57.630 --> 08:00.150 as transport nodes, let's also take a look WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 220 07:57.630 --> 08:00.150 as transport nodes, let's also take a look 221 08:00.150 --> 08:01.440 at our edge nodes. 222 08:01.440 --> 08:02.760 All right, so here what we're looking at 223 08:02.760 --> 08:05.760 is we have an SSH connection to Edge-1 here at the top 224 08:05.760 --> 08:08.070 and Edge-2 here in the bottom half. 225 08:08.070 --> 08:09.150 And then I've got my command window 226 08:09.150 --> 08:11.820 so I can send commands to both of them simultaneously. 227 08:11.820 --> 08:15.270 So here if we typed in get gateways and press enter, 228 08:15.270 --> 08:17.430 here is showing us the gateway information 229 08:17.430 --> 08:20.340 that these two edge devices know about. 230 08:20.340 --> 08:21.450 Now one of the questions might be, 231 08:21.450 --> 08:24.000 well why is it that the host transport nodes 232 08:24.000 --> 08:26.130 that we just looked at ESXi-A and B, 233 08:26.130 --> 08:27.990 how come they only have two instances 234 08:27.990 --> 08:30.450 of a virtual router and the edge devices, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 234 08:27.990 --> 08:30.450 of a virtual router and the edge devices, 235 08:30.450 --> 08:31.890 Edge-1 and two, they have three? 236 08:31.890 --> 08:34.440 Well the reason is because the actual edge devices 237 08:34.440 --> 08:36.420 are running as a VM, so they also have 238 08:36.420 --> 08:38.820 a routing table just for themselves. 239 08:38.820 --> 08:41.220 And so that's where this first one right here is, 240 08:41.220 --> 08:42.870 where it says VRF zero. 241 08:42.870 --> 08:45.120 Think of that like the the basic routing table 242 08:45.120 --> 08:46.500 for the VM itself. 243 08:46.500 --> 08:48.390 And then for the distributed routers, 244 08:48.390 --> 08:50.430 that would be the second one and third one, 245 08:50.430 --> 08:52.170 it's also showing us right here in the name, 246 08:52.170 --> 08:54.510 exactly which distributed routers those are. 247 08:54.510 --> 08:57.570 So if we were take a look for example at this first one. 248 08:57.570 --> 09:01.530 We could do a get gateway space and then the UUID WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 248 08:57.570 --> 09:01.530 We could do a get gateway space and then the UUID 249 09:01.530 --> 09:03.240 and then I'll go ahead and copy and paste that down here 250 09:03.240 --> 09:04.170 to make it a little bit easier. 251 09:04.170 --> 09:06.330 So I'll paste that in, space 252 09:06.330 --> 09:08.520 and let's type in forwarding and press enter. 253 09:08.520 --> 09:10.740 So what this is showing us is a routing table 254 09:10.740 --> 09:12.030 for the VM itself. 255 09:12.030 --> 09:15.780 And so for Edge-3 it's using VLAN 103 256 09:15.780 --> 09:19.200 and the IP address of 33.33.33.33 257 09:19.200 --> 09:22.440 with a default gateway on the transport network of .1. 258 09:22.440 --> 09:25.140 And over here Edge-2 is using the IP address 259 09:25.140 --> 09:27.000 for its transport network interface, 260 09:27.000 --> 09:30.150 this tunnel endpoint of 44.44.44.44 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 260 09:27.000 --> 09:30.150 this tunnel endpoint of 44.44.44.44 261 09:30.150 --> 09:32.130 with a default gateway of .1. 262 09:32.130 --> 09:34.140 So the routing tables for each 263 09:34.140 --> 09:36.570 of those VMs across the transport network, 264 09:36.570 --> 09:37.530 that should reflect that. 265 09:37.530 --> 09:38.790 So let's confirm that as well. 266 09:38.790 --> 09:40.650 So here on Edge-1 we are directly connected 267 09:40.650 --> 09:42.660 to the 33.33.33 network. 268 09:42.660 --> 09:44.940 Here is our exact IP address 269 09:44.940 --> 09:47.250 and here's our default gateway that we configured 270 09:47.250 --> 09:50.880 for this edge device, this edge VM when we deployed it. 271 09:50.880 --> 09:52.840 And then down here for Edge-2 it has the IP address 272 09:52.840 --> 09:54.990 of 44.44 et cetera. 273 09:54.990 --> 09:56.940 It's a 24-bit network it's connected to, 274 09:56.940 --> 09:59.670 so it's on the 44.44.44 network. 275 09:59.670 --> 10:03.180 And its default gateway is 44.44.44.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 275 09:59.670 --> 10:03.180 And its default gateway is 44.44.44.1. 276 10:03.180 --> 10:04.740 So if we scroll over here to the right, 277 10:04.740 --> 10:06.870 it's also showing us the layer two address 278 10:06.870 --> 10:07.860 associated with that. 279 10:07.860 --> 10:10.473 So if you notice up here for Edge-1, 280 10:10.473 --> 10:15.473 it's default gateway MAC address of 33.33.33.1 is this, 281 10:16.200 --> 10:19.260 and down here on Edge-4 is default Gateway Address 282 10:19.260 --> 10:21.494 of 44.44.44.1 is this, 283 10:21.494 --> 10:24.600 and these are both on my multilayer switches 284 10:24.600 --> 10:25.800 in my transport network 285 10:25.800 --> 10:27.120 that are actually doing the forwarding 286 10:27.120 --> 10:28.440 and the routing of that traffic. 287 10:28.440 --> 10:30.210 All right, so now that we've covered that, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 287 10:28.440 --> 10:30.210 All right, so now that we've covered that, 288 10:30.210 --> 10:33.300 let me also go ahead and show you an easier way 289 10:33.300 --> 10:34.890 to look at this information on our edges. 290 10:34.890 --> 10:36.840 So we type in get gateways, 291 10:36.840 --> 10:39.540 instead of typing in things like get gateway 292 10:39.540 --> 10:41.520 and then the long UUID and so forth, 293 10:41.520 --> 10:42.840 and then the command we wanna issue 294 10:42.840 --> 10:44.160 like forwarding or whatever, 295 10:44.160 --> 10:46.740 instead we could just go into the VRF for that router. 296 10:46.740 --> 10:48.780 So let's take a moment and let's talk about VRFs 297 10:48.780 --> 10:50.670 because I don't think we've talked about that yet. 298 10:50.670 --> 10:51.720 And that was a perfect time. 299 10:51.720 --> 10:54.300 So let's imagine we have a router 300 10:54.300 --> 10:56.940 and by default most routers from most vendors 301 10:56.940 --> 10:59.250 have one default routing table. 302 10:59.250 --> 11:00.600 So if we connect interfaces WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 302 10:59.250 --> 11:00.600 So if we connect interfaces 303 11:00.600 --> 11:04.530 for example like 10.10 here and 10.20 here 304 11:04.530 --> 11:06.540 and that's done when we configure IP addresses 305 11:06.540 --> 11:08.040 and associate with this router, 306 11:08.040 --> 11:09.937 it then in its routing table is gonna say, 307 11:09.937 --> 11:12.090 "Oh, I'm directly connected to the 10.10 network 308 11:12.090 --> 11:14.190 and the 10.20 network, life is good." 309 11:14.190 --> 11:17.790 And that's when we're using a single default routing table. 310 11:17.790 --> 11:19.500 However, when we have a environment 311 11:19.500 --> 11:22.080 where we have a need for a separate routing tables 312 11:22.080 --> 11:23.310 for separate functions, 313 11:23.310 --> 11:25.050 and lemme give you an example of that right here. 314 11:25.050 --> 11:27.330 This distributed router has certain routes 315 11:27.330 --> 11:30.090 and this distributed router has different certain routes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 315 11:27.330 --> 11:30.090 and this distributed router has different certain routes. 316 11:30.090 --> 11:32.670 So instead of having one giant routing table, 317 11:32.670 --> 11:34.740 here's what we can do, we can take that router, 318 11:34.740 --> 11:36.360 so this represents the router 319 11:36.360 --> 11:38.130 and from a routing table perspective, 320 11:38.130 --> 11:41.280 we can create virtual routing and forwarding instances 321 11:41.280 --> 11:42.870 and that's what the VRF represents. 322 11:42.870 --> 11:43.890 It's a separate compartment, 323 11:43.890 --> 11:47.010 think of it like a little mini me section 324 11:47.010 --> 11:48.570 of a routing table. 325 11:48.570 --> 11:50.438 For example, if you have a refrigerator 326 11:50.438 --> 11:52.920 and you have three or four people living in the house 327 11:52.920 --> 11:55.770 and you wanna separate various parts of that refrigerator 328 11:55.770 --> 11:57.390 for different people to use, 329 11:57.390 --> 11:58.627 we could say something like the following, 330 11:58.627 --> 12:01.140 "Okay, for us, we're gonna take the top third WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 330 11:58.627 --> 12:01.140 "Okay, for us, we're gonna take the top third 331 12:01.140 --> 12:03.150 of the refrigerator and that's just for us, 332 12:03.150 --> 12:04.770 so hands off to everybody else." 333 12:04.770 --> 12:06.240 And then for the first person maybe we give them 334 12:06.240 --> 12:07.530 the middle part of the fridge, 335 12:07.530 --> 12:09.330 and let's imagine there's total of three of us 336 12:09.330 --> 12:10.590 and then the third person, 337 12:10.590 --> 12:12.570 we'll go ahead and call that person number two, 338 12:12.570 --> 12:13.920 we can give them the bottom third. 339 12:13.920 --> 12:16.470 So we're compartmentalizing the refrigerator 340 12:16.470 --> 12:18.840 just to make sure the right people get to the right stuff. 341 12:18.840 --> 12:21.630 Well same thing right here in a routed environment. 342 12:21.630 --> 12:24.330 We can create virtual routing and forwarding instances 343 12:24.330 --> 12:27.060 which is simply like different sections of the refrigerator. 344 12:27.060 --> 12:29.310 So let's start off for our section. 345 12:29.310 --> 12:31.110 So if this is us right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 345 12:29.310 --> 12:31.110 So if this is us right here, 346 12:31.110 --> 12:33.690 so we'll say that's our section for our routes 347 12:33.690 --> 12:34.800 in the routing table, 348 12:34.800 --> 12:37.050 and then for this section, in fact let me color code this 349 12:37.050 --> 12:41.190 to match what we're using in our topology for our gateways. 350 12:41.190 --> 12:44.070 So for person one, I'm gonna put that here in orange, 351 12:44.070 --> 12:45.330 for the fridge analogy, 352 12:45.330 --> 12:47.460 and for person two I'm gonna put that in blue. 353 12:47.460 --> 12:49.800 So in our routing table we'll put a little section here 354 12:49.800 --> 12:52.620 for Gateway A and we'll have another little section 355 12:52.620 --> 12:55.170 for Gateway B and regarding us, 356 12:55.170 --> 12:58.740 that we refer to this case for the actual edge device itself 357 12:58.740 --> 13:00.900 for its own routes or the transport network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 357 12:58.740 --> 13:00.900 for its own routes or the transport network. 358 13:00.900 --> 13:02.700 So lemme clean that up just a little bit 359 13:02.700 --> 13:03.540 and I'll put Edge-1 here 360 13:03.540 --> 13:05.400 because we're talking here about Edge-1. 361 13:05.400 --> 13:06.930 It's also showing us right here in the output 362 13:06.930 --> 13:09.270 that this UUID, I'll go ahead 363 13:09.270 --> 13:10.830 and make a little note here in orange. 364 13:10.830 --> 13:14.550 That is the UUID for Gateway A as shown here. 365 13:14.550 --> 13:16.500 And this third one down here, this UUID 366 13:16.500 --> 13:20.880 starting with 7cbeef is the UUID for Gateway B. 367 13:20.880 --> 13:23.730 So think of it like the edge device 368 13:23.730 --> 13:26.580 with three logical routing tables. 369 13:26.580 --> 13:29.520 One's for itself, which in this case is VRF 0. 370 13:29.520 --> 13:33.180 And then one for Gateway A, which here is shown as VRF 2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 370 13:29.520 --> 13:33.180 And then one for Gateway A, which here is shown as VRF 2, 371 13:33.180 --> 13:36.420 and over here at Gateway B is using a logical container 372 13:36.420 --> 13:37.800 or section of the fridge, if you will, 373 13:37.800 --> 13:39.480 from the routing table on this edge device, 374 13:39.480 --> 13:41.700 and that is VRF 3. 375 13:41.700 --> 13:44.460 And again this is all for Edge-1. 376 13:44.460 --> 13:47.250 And the only difference here between the VRFs 377 13:47.250 --> 13:51.390 for Edge-1 and Edge-2 is gonna be the details they have 378 13:51.390 --> 13:52.980 in their VRF 0. 379 13:52.980 --> 13:56.280 Again, we looked at that a moment ago in VRF 0 on the edge. 380 13:56.280 --> 13:57.870 It's gonna have its transport information, 381 13:57.870 --> 14:01.380 so in VRF 0 on Edge-1 it includes information WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 381 13:57.870 --> 14:01.380 so in VRF 0 on Edge-1 it includes information 382 14:01.380 --> 14:03.930 like the 33.33 address space and so forth. 383 14:03.930 --> 14:06.570 While down here on Edge-2 it's VRF 0 384 14:06.570 --> 14:09.210 is gonna have information about the 44.44 network. 385 14:09.210 --> 14:11.070 However, as far as these other two VRFs 386 14:11.070 --> 14:14.130 which represent the other two virtual routers 387 14:14.130 --> 14:15.780 or the other two logical gateways 388 14:15.780 --> 14:16.920 that we just configured as part of 389 14:16.920 --> 14:18.390 a distributed routing environment, 390 14:18.390 --> 14:21.600 VRF 2 and VRF 3 are gonna be identical 391 14:21.600 --> 14:22.980 on both of these edges. 392 14:22.980 --> 14:25.470 So to confirm that, let me show you an easier way 393 14:25.470 --> 14:27.480 of seeing the details for those VRFs 394 14:27.480 --> 14:31.590 rather than typing in get gateway and then the long UUID WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 394 14:27.480 --> 14:31.590 rather than typing in get gateway and then the long UUID 395 14:31.590 --> 14:32.790 and then the syntax you want, 396 14:32.790 --> 14:35.730 what we can do is we can just go directly into those VRFs 397 14:35.730 --> 14:38.850 and issue our commands from within those VRFs. 398 14:38.850 --> 14:40.320 So I'm gonna make a note up here 399 14:40.320 --> 14:43.110 that VRF 0 is the local edge 400 14:43.110 --> 14:44.850 and the routing information for the local edge. 401 14:44.850 --> 14:48.180 And so what we can do is we can take a look at VRF 2 or 3 402 14:48.180 --> 14:49.680 on both of these edge nodes 403 14:49.680 --> 14:51.780 and the information there is going to be identical. 404 14:51.780 --> 14:53.820 So to do that and also to compare and contrast, 405 14:53.820 --> 14:56.040 lemme show you the hard way versus the easy way 406 14:56.040 --> 14:58.980 of looking at the details for those routing instances. 407 14:58.980 --> 15:01.860 So if we said for example, get gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 407 14:58.980 --> 15:01.860 So if we said for example, get gateway 408 15:01.860 --> 15:04.140 and then we plugged in the long UUID, 409 15:04.140 --> 15:07.860 so we'll grab this UUID that's associated with Gateway A, 410 15:07.860 --> 15:09.420 so I'll paste that in down here 411 15:09.420 --> 15:12.390 and then press space, then did forwarding and pressed enter. 412 15:12.390 --> 15:14.370 That's gonna show us the forwarding information 413 15:14.370 --> 15:17.010 for Gateway A effectively, the forwarding information 414 15:17.010 --> 15:20.160 for VRF 2, however, an easier way of doing that 415 15:20.160 --> 15:23.490 is simply by typing in VRF 2, pressing enter 416 15:23.490 --> 15:25.680 and that puts us into the logical router 417 15:25.680 --> 15:27.900 where we can just issue the commands we wanna issue 418 15:27.900 --> 15:31.560 without having to plug in the actual UUID every single time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 418 15:27.900 --> 15:31.560 without having to plug in the actual UUID every single time. 419 15:31.560 --> 15:34.560 And just as a reminder, if we do a get logical routers 420 15:34.560 --> 15:37.320 and press enter, or if we do a get gateways 421 15:37.320 --> 15:39.990 for the time being, both options are gonna work. 422 15:39.990 --> 15:41.640 But just keep in mind that we're moving towards 423 15:41.640 --> 15:43.410 more of the CLI that's going to include 424 15:43.410 --> 15:45.300 just the gateways option as opposed to 425 15:45.300 --> 15:47.310 the syntax of logical dash routers. 426 15:47.310 --> 15:48.930 All right, so here just to confirm, 427 15:48.930 --> 15:53.110 our VRF number for the Gateway A is VRF 2. 428 15:53.110 --> 15:54.240 So what we can do is simply type here 429 15:54.240 --> 15:58.800 at the NSX CLI on our edges, we can simply type in VRF space 430 15:58.800 --> 16:01.740 and the VRF number we want, which is two, and press enter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 430 15:58.800 --> 16:01.740 and the VRF number we want, which is two, and press enter. 431 16:01.740 --> 16:04.050 And that puts us logically into that VRF. 432 16:04.050 --> 16:05.550 See how the prompt changed right there? 433 16:05.550 --> 16:07.620 Indicating that we are in VRF 2. 434 16:07.620 --> 16:09.510 So now if we did a question mark, 435 16:09.510 --> 16:11.430 let's do a question mark and send it in. 436 16:11.430 --> 16:12.960 So now we can do any of these commands 437 16:12.960 --> 16:15.400 directly right here from the VRF. 438 16:15.400 --> 16:17.160 So if we wanna look at forwarding, 439 16:17.160 --> 16:19.050 we can just say get forwarding for example, 440 16:19.050 --> 16:22.230 instead of having to put in the entire UUID. 441 16:22.230 --> 16:24.480 So here on both edge devices, 442 16:24.480 --> 16:26.940 let's do a get forwarding and press enter. 443 16:26.940 --> 16:28.390 And that shows at the routing table, 444 16:28.390 --> 16:30.450 if we do a get interfaces, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 444 16:28.390 --> 16:30.450 if we do a get interfaces, 445 16:30.450 --> 16:31.500 that'll show us the interfaces 446 16:31.500 --> 16:33.090 associated with this virtual router. 447 16:33.090 --> 16:36.660 So for Gateway A, which is using VRF 2 for this interface, 448 16:36.660 --> 16:40.140 the IP address is 10.10.0.1 on each 449 16:40.140 --> 16:41.370 of the distributed routers 450 16:41.370 --> 16:43.320 because they're identical information. 451 16:43.320 --> 16:45.060 For layer three and for layer two. 452 16:45.060 --> 16:46.240 So we're regarding the name and the tail end here, 453 16:46.240 --> 16:50.070 DLRP, DLRP is a a shortcut way of saying 454 16:50.070 --> 16:54.660 Distributed Logical Router Port, DLRP. 455 16:54.660 --> 16:56.370 And the same information is gonna be present 456 16:56.370 --> 16:58.050 on our transport nodes as well. 457 16:58.050 --> 17:00.510 So if we looked at the details regarding the IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 457 16:58.050 --> 17:00.510 So if we looked at the details regarding the IP address 458 17:00.510 --> 17:02.280 and the MAC address associated 459 17:02.280 --> 17:05.700 with the connection from Gateway A to Segment 10, 460 17:05.700 --> 17:07.890 all this information including the IP address, 461 17:07.890 --> 17:10.260 the MAC address, the VNIs associated with, 462 17:10.260 --> 17:11.760 all that would be identical, 463 17:11.760 --> 17:14.430 because once again we are using a distributed router, 464 17:14.430 --> 17:16.350 which is being distributed and is the same, 465 17:16.350 --> 17:19.110 exact same information across all the transport nodes, 466 17:19.110 --> 17:21.630 whether they're edge nodes or host nodes 467 17:21.630 --> 17:23.160 that have that distributed router. 468 17:23.160 --> 17:24.780 So now that we have created 469 17:24.780 --> 17:28.350 this new logical Tier-1 Gateway B, 470 17:28.350 --> 17:31.590 and we've also confirmed that that distributed router exists WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 470 17:28.350 --> 17:31.590 and we've also confirmed that that distributed router exists 471 17:31.590 --> 17:34.320 on ESXi-A as a host transport node 472 17:34.320 --> 17:38.100 and also exists here on our host transport node ESXi-B 473 17:38.100 --> 17:41.250 and also exists on our Edge-1 and Edge-2, 474 17:41.250 --> 17:42.810 our next logical step then is to go ahead 475 17:42.810 --> 17:45.870 and create our Tier-0 and link that up 476 17:45.870 --> 17:48.000 or associate that Tier-0 gateway 477 17:48.000 --> 17:49.890 with Gateway A and Gateway B. 478 17:49.890 --> 17:53.730 'Cause right now as it sits without this Tier-0 gateway 479 17:53.730 --> 17:55.590 connecting these two routers together, 480 17:55.590 --> 17:58.530 clients on Segment 10 over here are not gonna have 481 17:58.530 --> 18:01.260 connectivity from a routing perspective over here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 481 17:58.530 --> 18:01.260 connectivity from a routing perspective over here 482 18:01.260 --> 18:04.080 until we put this Tier-0 Gateway 0 in place. 483 18:04.080 --> 18:06.120 So we'll do that in the very next video. 484 18:06.120 --> 18:07.920 I'll see you there in just a moment.