WEBVTT 1 00:00.000 --> 00:04.950 So these three routers as shown are our distributed router functions for the 2 00:04.950 --> 00:06.700 tier zero and the two tier ones. 3 00:06.700 --> 00:10.650 And then on our edge nodes, which are providing the fault tolerance and the 4 00:10.650 --> 00:12.300 physical access to the network up here, 5 00:12.300 --> 00:18.280 we now have a logical SR, a services router function that's on both edge one 6 00:18.280 --> 00:19.200 and edge two. 7 00:19.200 --> 00:22.320 So edge one as the active router will be doing the actual movement of the 8 00:22.320 --> 00:25.600 traffic from the NSX environment over to the physical network. 9 00:25.600 --> 00:29.000 So I'm going to go ahead and draw some connectivity here as well. 10 00:29.000 --> 00:33.150 And then what I'd like to do right here, I'd like to write out the entire path WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:29.000 --> 00:33.150 And then what I'd like to do right here, I'd like to write out the entire path 11 00:33.150 --> 00:37.740 that would be taken from VM one going out to, for example, this IP address at 12 00:37.740 --> 00:41.000 192.168.1.1, 13 00:41.000 --> 00:43.600 which is my router on my physical network. 14 00:43.600 --> 00:47.400 Actually, in reality, it's actual firewall that also does routing, but it has 15 00:47.400 --> 00:51.700 the IP address of 192.168.1.1 and it is a physical appliance. 16 00:51.700 --> 00:57.580 So I'd like to write out the path here. Let's start with VM one and VM one is 17 00:57.580 --> 01:03.500 at dot 10 and it is connected to this DR and that is gateway A and its IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:57.580 --> 01:03.500 at dot 10 and it is connected to this DR and that is gateway A and its IP 18 01:03.500 --> 01:06.500 address on this network is dot one. 19 01:06.500 --> 01:12.700 And then this is the 10 dot 10 dot zero dot zero slash 24 network. Fantastic. 20 01:12.700 --> 01:16.650 So VM one, if it needs to forward packets off of its local network, it's going 21 01:16.650 --> 01:18.900 to send them over to its default gateway. 22 01:18.900 --> 01:22.890 Now, gateway A being connected to this tier one router automatically gets a 23 01:22.890 --> 01:23.900 default route. 24 01:23.900 --> 01:27.760 So if it doesn't have a more detailed route on how to forward a packet, it's 25 01:27.760 --> 01:30.900 simply going to forward traffic up here to the tier one DR. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:27.760 --> 01:30.900 simply going to forward traffic up here to the tier one DR. 26 01:30.900 --> 01:33.900 So I'm going to put that next as our inter router segment here. 27 01:33.900 --> 01:38.900 So this would represent here gateway zero and then for the IP addresses there. 28 01:38.900 --> 01:41.560 In fact, let's take a moment and let's just document what those IP addresses 29 01:41.560 --> 01:41.900 are. 30 01:41.900 --> 01:45.900 So currently I have a CLI open up to the edge one and also down here to ESXIA. 31 01:45.900 --> 01:49.900 They both have a copy of the distributed router for gateway A. 32 01:49.900 --> 01:53.740 So if we do a get gateways and press enter, but I love about get gateways over 33 01:53.740 --> 01:58.570 here on the edge compared to the ESXIA is that is telling you upfront with 34 01:58.570 --> 01:59.900 names exactly which one it is. 35 01:59.900 --> 02:05.910 So for gateway A, it is this one right here, which is the one that starts with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:59.900 --> 02:05.910 So for gateway A, it is this one right here, which is the one that starts with 36 02:05.910 --> 02:07.900 DB two and ends with FE one to. 37 02:07.900 --> 02:12.570 So that's the UUID for gateway A and also shows here that on the edge, it's 38 02:12.570 --> 02:14.900 using a VRF two to support that. 39 02:14.900 --> 02:18.880 So I'm going to document that as well inside of our notes that way when we see 40 02:18.880 --> 02:22.900 this UUID will know exactly which virtual router we're talking about. 41 02:22.900 --> 02:28.030 It's going to be gateway A. So I'm a little arrow here and then for gateway A, 42 02:28.030 --> 02:33.170 it's UUID begins with DB two whole bunch of other characters and it ends with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 02:28.030 --> 02:33.170 it's UUID begins with DB two whole bunch of other characters and it ends with 43 02:33.170 --> 02:33.900 FE 12. 44 02:33.900 --> 02:39.020 Also on edge one, it happens to be VRF number two. So if we need to go look at 45 02:39.020 --> 02:40.900 there, we can just go into that VRF. 46 02:40.900 --> 02:44.080 All right, so that in mind, let's take a look at this connection between 47 02:44.080 --> 02:46.900 gateway A and gateway zero and identify the network there. 48 02:46.900 --> 02:51.510 So here on the edge, we could just type in VRF two and press enter the prompt 49 02:51.510 --> 02:55.900 changes to reflect that we're in VRF two for that virtual gateway. 50 02:55.900 --> 02:59.940 So if we did a get forwarding and let's look at our options here, let's see, we 51 02:59.940 --> 03:04.450 get forwarding and let's look for the default route of 0, 0, 0, 0, slash zero, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 02:59.940 --> 03:04.450 get forwarding and let's look for the default route of 0, 0, 0, 0, slash zero, 52 03:04.450 --> 03:04.900 press enter. 53 03:04.900 --> 03:09.470 Or that way we can focus on just a single route look at the default route and 54 03:09.470 --> 03:15.130 it says the next hop address is 164, 0, 0, which I got to admit if you're used 55 03:15.130 --> 03:16.900 to working with slash 30s and less. 56 03:16.900 --> 03:21.400 That looks like a weird valid IP address, but because we're using a slash 31, 57 03:21.400 --> 03:25.900 it is. We can also do a get interfaces here for this gateway A and press enter. 58 03:25.900 --> 03:29.680 And that's also showing us what the local address here is. And if we scroll 59 03:29.680 --> 03:33.900 down, this is also showing us the interface we're using on that common network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:29.680 --> 03:33.900 down, this is also showing us the interface we're using on that common network. 60 03:33.900 --> 03:39.040 So here's the name. It's our tier zero to tier one gateway LRP and that's the 61 03:39.040 --> 03:40.900 logical router port. 62 03:40.900 --> 03:46.920 And then the port type is linked and here is the local IP address on gateway A. 63 03:46.920 --> 03:51.900 So the next hop is 164, 0, 0, which is our tier zero gateway the DR there. 64 03:51.900 --> 03:57.800 And the local interface on that common link is 164, 0, 1. So let's add that to 65 03:57.800 --> 04:03.900 our documentation. So this network has 100.64.0.0 slash 31. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 03:57.800 --> 04:03.900 our documentation. So this network has 100.64.0.0 slash 31. 66 04:03.900 --> 04:10.000 And over here is 0 as the next hop and over here, based on what we just saw, 67 04:10.000 --> 04:13.900 this is 164, 0, 1. Again, that's all with a 31 bit mass. 68 04:13.900 --> 04:18.420 All right, so that covers the gateway A. Now, at some point on our tier zero 69 04:18.420 --> 04:22.400 router, we are going to need a default route effectively saying, Hey, if you 70 04:22.400 --> 04:24.900 don't know how to forward a packet, forward it to this next top. 71 04:24.900 --> 04:29.010 So we're going to need a default route that says in our topology here that the 72 04:29.010 --> 04:31.900 next hop should be 192, 168, 1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 04:29.010 --> 04:31.900 next hop should be 192, 168, 1.1. 73 04:31.900 --> 04:35.580 And currently, I don't have that static route in place, but it's super easy to 74 04:35.580 --> 04:37.900 create a static route on a tier zero gateway. 75 04:37.900 --> 04:40.890 You simply click a few buttons, you specify what you want the default route to 76 04:40.890 --> 04:44.900 be, and you're done. So let's take a moment and do that right now. 77 04:44.900 --> 04:50.300 So here on our edge, let's exit out and go back to the main NSX CLI for edge 78 04:50.300 --> 04:52.900 one and let's do a get gateways. 79 04:52.900 --> 04:56.710 And so for the distributed router for our tier zero gateway zero logical router 80 04:56.710 --> 05:00.900 , if we just type in VRF one, that'll take us into the logical routing for that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 04:56.710 --> 05:00.900 , if we just type in VRF one, that'll take us into the logical routing for that 81 05:00.900 --> 05:00.900 specific route. 82 05:00.900 --> 05:05.100 And it's a lot easier than typing out the commands and having to put in the 83 05:05.100 --> 05:05.900 full UUID. 84 05:05.900 --> 05:10.900 So here we do a get and a space question mark. Let's do a get forwarding. 85 05:10.900 --> 05:13.900 So I'll type get forwarding in a space of question mark. 86 05:13.900 --> 05:18.760 And let's also look for the default route. So we'll go ahead and do a zero zero 87 05:18.760 --> 05:20.900 zero zero zero zero and no routes to display. 88 05:20.900 --> 05:23.900 Let's go ahead and do a get forwarding and take a look at everything. 89 05:23.900 --> 05:27.900 And here's everything it knows about. So there's some IPV six routes. 90 05:27.900 --> 05:32.900 And if we scroll up here, we have routes to get down to segment 10 segment 20. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 05:27.900 --> 05:32.900 And if we scroll up here, we have routes to get down to segment 10 segment 20. 91 05:32.900 --> 05:37.100 We have routes for our links between us, the tier zero gateway and our tier one 92 05:37.100 --> 05:37.900 gateways. 93 05:37.900 --> 05:42.110 We also have some really cool one 69 254 routes. And those are the internal 94 05:42.110 --> 05:45.400 networks that we're going to be using and seeing in just a moment for the 95 05:45.400 --> 05:50.550 routing between the DR on the tier zero gateway and the SR on the tier zero 96 05:50.550 --> 05:50.900 gateway. 97 05:50.900 --> 05:54.900 But for now, we don't have a default route. So let's go ahead and add one. 98 05:54.900 --> 05:59.360 So back in the NSX manager, we'll go to networking tab up on top and on the 99 05:59.360 --> 06:03.380 left, we'll click on the tier zero gateways and then we'll edit our tier zero WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 99 05:59.360 --> 06:03.380 left, we'll click on the tier zero gateways and then we'll edit our tier zero 100 06:03.380 --> 06:05.900 gateway and simply tell it, hey, we want to add a static route. 101 06:05.900 --> 06:10.330 So to do that, we'll click on the three dots. We'll click on edit and then we 102 06:10.330 --> 06:13.900 'll scroll down and then down below, we have a section called routing. 103 06:13.900 --> 06:17.540 And then in routing, we have an area for static routes. We'll click here on set 104 06:17.540 --> 06:23.900 and then we'll click on add static route and we'll say default for T zero. 105 06:23.900 --> 06:27.850 And then the route we want to add is 0 0 0 0 0 slash zero, which is how you 106 06:27.850 --> 06:29.900 represent an IPV for a default route. 107 06:29.900 --> 06:33.940 And then we need to tell it with this option right here, what the next top is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 107 06:29.900 --> 06:33.940 And then we need to tell it with this option right here, what the next top is. 108 06:33.940 --> 06:37.900 In our case, it's going to be my physical gateway at 192 168 1.1. 109 06:37.900 --> 06:41.900 So we'll click here on set and then we'll click further on set next tops. 110 06:41.900 --> 06:46.900 And then we'll go ahead and we'll add the next top of 192.168.1.1. 111 06:46.900 --> 06:50.420 Then for the administrative distance, we'll take a closer look at that and some 112 06:50.420 --> 06:52.900 of the options when we have a whole skill on routing. 113 06:52.900 --> 07:03.360 So for now, I'm just going to add this one static default route with a next top WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 06:52.900 --> 07:03.360 So for now, I'm just going to add this one static default route with a next top 114 07:03.360 --> 07:05.490 of 192.168.1.1. We'll click on add, click on apply, click on save and click on 115 07:05.490 --> 07:05.900 close and scroll down and click on close editing. 116 07:05.900 --> 07:09.370 And we'll collapse that. And now let's go take a look at our distributed router 117 07:09.370 --> 07:11.900 gateway zero and take a look at its routing table. 118 07:11.900 --> 07:17.500 So previously, we are looking at VRF 1, which is the VRF 4, our tier zero 119 07:17.500 --> 07:20.900 gateway zero DR, and it did not have a default route. 120 07:20.900 --> 07:25.280 So was this at the upper key? Do a get forwarding again. And this time, we now 121 07:25.280 --> 07:29.900 have our default route with the next top of 192 168.1.1. 122 07:29.900 --> 07:32.710 So now we have that default route. The other thing I'd like to do here is to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 122 07:29.900 --> 07:32.710 So now we have that default route. The other thing I'd like to do here is to 123 07:32.710 --> 07:33.900 get gateways again. 124 07:33.900 --> 07:40.400 And I'd like to document on our topology what the actual UUID is and VRF for 125 07:40.400 --> 07:43.900 our distributed router tier zero gateway zero router. 126 07:43.900 --> 07:47.610 And that way, if we ever need to refer to either the VRF or the UUID, we'll 127 07:47.610 --> 07:48.900 have it documented. 128 07:48.900 --> 07:53.980 So the distributed router for gateway zero, our tier zero gateway, begins with 129 07:53.980 --> 07:57.900 zero four, a whole bunch of additional characters, and it ends up in bed. 130 07:57.900 --> 08:02.570 Maybe it was tired. Anyway, that's a convenient way of remembering that's the U WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 07:57.900 --> 08:02.570 Maybe it was tired. Anyway, that's a convenient way of remembering that's the U 131 08:02.570 --> 08:07.060 UID for gateway zero and in edge one, all that information regarding that DR is 132 08:07.060 --> 08:09.900 being kept in the VRF called VRF number one. 133 08:09.900 --> 08:14.140 And we just set up a default route on our tier zero gateway that said, "Hey, if 134 08:14.140 --> 08:17.190 you need to forward packet, you don't have a more specific route in your 135 08:17.190 --> 08:17.900 routing table. 136 08:17.900 --> 08:24.250 Use the next top over here at this device at dot one." And this is the 192 168 137 08:24.250 --> 08:27.730 10 network, the 24-root mask, and my little gateway slash firewall router thing 138 08:27.730 --> 08:28.900 is right here at dot one. 139 08:28.900 --> 08:32.900 So there's the segment and there's my physical appliance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 139 08:28.900 --> 08:32.900 So there's the segment and there's my physical appliance.