WEBVTT 1 00:00.000 --> 00:04.240 The primary takeaway from this conversation is going to be making sure we can 2 00:04.240 --> 00:04.720 identify 3 00:04.720 --> 00:07.000 which features belong at which layer. 4 00:07.000 --> 00:11.600 For example, I would never expect to deploy power over ethernet or QOS tagging 5 00:11.600 --> 00:12.360 into the 6 00:12.360 --> 00:16.230 core or distribution layers, and that's going to apply to a lot of the other 7 00:16.230 --> 00:17.120 conversations 8 00:17.120 --> 00:18.800 that we had here as well. 9 00:18.800 --> 00:21.440 So let's start with one of these matches. 10 00:21.440 --> 00:24.180 Match the feature to its corresponding network layer. 11 00:24.180 --> 00:28.290 For fast layer three switching, that belongs at the core layer every single 12 00:28.290 --> 00:28.800 time. 13 00:28.800 --> 00:31.080 That is our primary care about at the core layer. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:28.800 --> 00:31.080 That is our primary care about at the core layer. 14 00:31.080 --> 00:34.680 In fact, FHRP is these belong at the distribution layer. 15 00:34.680 --> 00:37.880 This would be for redundant gateway access. 16 00:37.880 --> 00:42.170 Ultimately, it's going to allow us to survive a failure of one distribution 17 00:42.170 --> 00:42.880 switch from 18 00:42.880 --> 00:44.680 a gateway perspective. 19 00:44.680 --> 00:49.040 And then QOS and VLAN marking process of elimination would be access layer, but 20 00:49.040 --> 00:49.820 again, it makes 21 00:49.820 --> 00:53.320 sense to have these happening at the edge of our network. 22 00:53.320 --> 00:56.120 Next, we've got power over ethernet. 23 00:56.120 --> 00:59.120 And where do I connect my access points and my phones? 24 00:59.120 --> 01:01.160 They go at the access layer. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:59.120 --> 01:01.160 They go at the access layer. 25 01:01.160 --> 01:05.760 My spanning tree root, that is going to be a layer two concept. 26 01:05.760 --> 01:09.040 Spanning tree does not belong in the network core. 27 01:09.040 --> 01:11.600 And we certainly don't want the root in the access layer. 28 01:11.600 --> 01:14.080 So that means it goes in the distribution layer. 29 01:14.080 --> 01:19.310 And then fully featured routing protocols, that would go into the core layer 30 01:19.310 --> 01:19.440 because we're 31 01:19.440 --> 01:23.600 not going to be running stub, for example, stub areas inside of the network 32 01:23.600 --> 01:24.160 core. 33 01:24.160 --> 01:28.160 And lastly, match the feature, the same question, I suppose. 34 01:28.160 --> 01:32.430 So high bandwidth links and overall throughput, the highest links and the most WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:28.160 --> 01:32.430 So high bandwidth links and overall throughput, the highest links and the most 35 01:32.430 --> 01:33.400 overall throughput 36 01:33.400 --> 01:37.480 is going to go into the core layer, that QOS trust boundary that we mentioned. 37 01:37.480 --> 01:40.960 Remember, we have to decide which devices we trust and which we don't. 38 01:40.960 --> 01:44.680 That is an access layer feature and summary route advertisements. 39 01:44.680 --> 01:49.760 So once more, if we have a bunch of routes at the distribution layer, ideally, 40 01:49.760 --> 01:50.720 we summarize 41 01:50.720 --> 01:56.240 that, we perform summarization at the distribution layer, sending only summar 42 01:56.240 --> 01:57.400 ized routes to the 43 01:57.400 --> 02:01.940 core layer, which will reduce the routing table size of our core and ultimately WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 01:57.400 --> 02:01.940 core layer, which will reduce the routing table size of our core and ultimately 44 02:01.940 --> 02:02.760 of the entire 45 02:02.760 --> 02:04.280 rest of the network. 46 02:04.280 --> 02:07.640 So those are the features and where they belong. 47 02:07.640 --> 02:11.210 Again, we need to make sure that if we are looking at a layer that we can 48 02:11.210 --> 02:12.000 identify the 49 02:12.000 --> 02:15.600 needs of that layer and especially compare that to the needs of the other 50 02:15.600 --> 02:16.520 layers, make sure 51 02:16.520 --> 02:21.930 we understand why does QOS tagging exist at the access layer and why does 52 02:21.930 --> 02:23.200 summarization 53 02:23.200 --> 02:24.880 exist to distribution. 54 02:24.880 --> 02:27.670 The more we understand about the architecture, the more it's going to be very 55 02:27.670 --> 02:28.440 logical where 56 02:28.440 --> 02:31.390 these features belong and that's going to help us to be able to properly WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:28.440 --> 02:31.390 these features belong and that's going to help us to be able to properly 57 02:31.390 --> 02:32.080 identify them 58 02:32.080 --> 02:33.400 when we need to do so. 59 02:33.400 --> 02:36.040 I hope there's been informative for you and I'd like to thank you for viewing.