WEBVTT 1 00:00.210 --> 00:01.920 Hello and welcome. 2 00:01.920 --> 00:03.720 My name is Keith Barker. 3 00:03.720 --> 00:06.660 And up to this point, we've been focusing primarily 4 00:06.660 --> 00:09.990 on the concept of the distributed router inside of NSX 5 00:09.990 --> 00:12.630 that can provide the routing for east west traffic 6 00:12.630 --> 00:16.050 also with a tier-0 and a couple tier-1 gateways. 7 00:16.050 --> 00:18.120 We could also route all the way through them 8 00:18.120 --> 00:20.670 from VMs on one segment over to another. 9 00:20.670 --> 00:21.900 And one of the really cool things 10 00:21.900 --> 00:24.120 about a distributed router, a DR, 11 00:24.120 --> 00:25.200 is that it can exist 12 00:25.200 --> 00:27.210 on all of our transport nodes that need to have it. 13 00:27.210 --> 00:30.420 For example, ESXiA and ESXiB, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:27.210 --> 00:30.420 For example, ESXiA and ESXiB, 14 00:30.420 --> 00:32.490 they've got the distributed router component. 15 00:32.490 --> 00:33.660 Our edge devices, 16 00:33.660 --> 00:35.430 they have copies of that distributed router 17 00:35.430 --> 00:37.500 for T0 and a couple T1s. 18 00:37.500 --> 00:38.610 And again, up to this point, 19 00:38.610 --> 00:40.200 that's been our primary focus 20 00:40.200 --> 00:41.850 about working with and configuring 21 00:41.850 --> 00:45.060 and then verifying those distributed routers. 22 00:45.060 --> 00:47.130 However, there comes a time in every network's life 23 00:47.130 --> 00:49.170 when we need to have some other services. 24 00:49.170 --> 00:52.650 For example, we may wanna set up network address translation 25 00:52.650 --> 00:54.810 at one of our tier-0 gateways. 26 00:54.810 --> 00:56.190 And for those network services, 27 00:56.190 --> 00:58.020 including network address translations, 28 00:58.020 --> 01:00.420 stateful firewall, and VPNs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:58.020 --> 01:00.420 stateful firewall, and VPNs, 29 01:00.420 --> 01:02.520 we need an additional component 30 01:02.520 --> 01:04.410 on those devices providing those services, 31 01:04.410 --> 01:05.940 and that extra component 32 01:05.940 --> 01:07.440 for those additional network services 33 01:07.440 --> 01:10.080 is referred to as a services router. 34 01:10.080 --> 01:11.580 So think of the distributed router 35 01:11.580 --> 01:13.950 as the routing information on how to get places 36 01:13.950 --> 01:15.390 and how to forward traffic. 37 01:15.390 --> 01:17.730 And we can think of the services router component, 38 01:17.730 --> 01:20.400 even if it's on the same logical router, 39 01:20.400 --> 01:22.890 we can give the services router as the component 40 01:22.890 --> 01:24.480 that's gonna provide those services. 41 01:24.480 --> 01:27.390 For example, provide network address translation 42 01:27.390 --> 01:31.290 or provide VPN services or a gateway based firewall. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 01:27.390 --> 01:31.290 or provide VPN services or a gateway based firewall. 43 01:31.290 --> 01:34.080 Another time the services router comes into play 44 01:34.080 --> 01:35.580 is if we're gonna be accessing 45 01:35.580 --> 01:37.320 the actual physical external network. 46 01:37.320 --> 01:39.660 So we may have VMs down here in our segments, 47 01:39.660 --> 01:40.980 and they wanna be able to route 48 01:40.980 --> 01:42.480 with east-west traffic, no problem, 49 01:42.480 --> 01:44.520 but also, they may need to get access 50 01:44.520 --> 01:46.710 out to the physical network in our topology 51 01:46.710 --> 01:48.450 or beyond that to the internet. 52 01:48.450 --> 01:51.840 And anytime we're gonna bridge our NSX routed environment 53 01:51.840 --> 01:53.100 with a physical environment, 54 01:53.100 --> 01:56.910 that also is going to invoke a services router function 55 01:56.910 --> 01:58.530 on that router, on that gateway 56 01:58.530 --> 01:59.970 that's providing that service 57 01:59.970 --> 02:02.430 from the logical NSX routed environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 01:59.970 --> 02:02.430 from the logical NSX routed environment 58 02:02.430 --> 02:04.050 over to the physical network. 59 02:04.050 --> 02:05.250 So in this guild, we're gonna do this. 60 02:05.250 --> 02:06.690 We're gonna take our existing topology, 61 02:06.690 --> 02:07.920 which currently has three routers, 62 02:07.920 --> 02:09.600 two tier-1s and one tier-0, 63 02:09.600 --> 02:10.980 and at the tier-0, 64 02:10.980 --> 02:13.980 we are going to add on top of its responsibilities, 65 02:13.980 --> 02:16.350 connections out to the physical network 66 02:16.350 --> 02:18.330 on behalf of the internal routed environment. 67 02:18.330 --> 02:21.780 That way a VM like VM1, if it needs to or wants to, 68 02:21.780 --> 02:24.540 can get access not just to the NSX routed networks, 69 02:24.540 --> 02:27.000 but also out to the physical network as well. 70 02:27.000 --> 02:27.833 And, again, to do that, 71 02:27.833 --> 02:29.310 when we add that additional functionality 72 02:29.310 --> 02:32.040 for connectivity or bridging out to the physical network, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 02:29.310 --> 02:32.040 for connectivity or bridging out to the physical network, 73 02:32.040 --> 02:35.250 that is going to require a services router component 74 02:35.250 --> 02:36.750 inside of our NSX. 75 02:36.750 --> 02:38.010 So join me in the next video 76 02:38.010 --> 02:40.710 as we take a big picture look at our overall process, 77 02:40.710 --> 02:42.600 we'll follow it up with a game plan, 78 02:42.600 --> 02:43.650 and then what you and I get to do 79 02:43.650 --> 02:46.380 is both implement and verify as we go. 80 02:46.380 --> 02:49.023 So I'll see you, my friend, in the very next video.