WEBVTT 1 00:00.000 --> 00:04.970 Now I want to be clear, this challenge was intended to give us some amount of 2 00:04.970 --> 00:05.920 flexibility 3 00:05.920 --> 00:09.730 and creativity because there's not necessarily going to be right or wrong 4 00:09.730 --> 00:10.400 answers. 5 00:10.400 --> 00:13.360 Certainly, if we just said, "Hey, we're going to connect all of these access 6 00:13.360 --> 00:14.280 clauses directly 7 00:14.280 --> 00:15.280 to each other." 8 00:15.280 --> 00:17.520 Yeah, that would be a wrong answer. 9 00:17.520 --> 00:21.370 But as far as some of the key points there about collapsed core versus 10 00:21.370 --> 00:23.120 dedicated core, 11 00:23.120 --> 00:26.120 there's probably going to need to be a lot more information provided if we're 12 00:26.120 --> 00:26.680 going to have 13 00:26.680 --> 00:28.720 a right and wrong answer. 14 00:28.720 --> 00:33.320 So instead, I'm more interested in whether we can, first of all, make those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:28.720 --> 00:33.320 So instead, I'm more interested in whether we can, first of all, make those 15 00:33.320 --> 00:34.080 decisions, 16 00:34.080 --> 00:37.420 understand some of the criteria, maybe questions we would ask if this was a 17 00:37.420 --> 00:39.080 real world scenario, 18 00:39.080 --> 00:43.710 and then ultimately, can I justify my decision and that would tie back to maybe 19 00:43.710 --> 00:44.400 making some 20 00:44.400 --> 00:47.200 assumptions about the size of the network. 21 00:47.200 --> 00:50.200 So let's just kind of go through this process together. 22 00:50.200 --> 00:52.960 So we were told to create a basic network design. 23 00:52.960 --> 00:57.240 We've got four different access closets. 24 00:57.240 --> 01:02.680 These are our access closets and a head end closet up here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:57.240 --> 01:02.680 These are our access closets and a head end closet up here. 25 01:02.680 --> 01:08.340 And so here we're going to have, this is where we could deploy distribution and 26 01:08.340 --> 01:08.680 core. 27 01:08.680 --> 01:11.360 And here, down here, these are our access switches. 28 01:11.360 --> 01:15.200 We have fiber connections that go to two other locations. 29 01:15.200 --> 01:24.320 So we'll just call these site two and site three. 30 01:24.320 --> 01:32.320 And we have firewalls that also bring in the internet there and that end. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 01:24.320 --> 01:32.320 And we have firewalls that also bring in the internet there and that end. 31 01:32.320 --> 01:35.400 So for our design, we need to make some decisions here. 32 01:35.400 --> 01:38.960 Well, I guess I didn't include the access switches. 33 01:38.960 --> 01:40.440 So, and that's fine. 34 01:40.440 --> 01:43.600 For the most part, we're not too worried about the access switches. 35 01:43.600 --> 01:47.240 But we've got these access switches. 36 01:47.240 --> 01:52.160 So do we want to deploy a collapsed core or a dedicated core layer? 37 01:52.160 --> 01:59.500 This topology is starting to hit that threshold where we might consider a core 38 01:59.500 --> 02:01.520 dedicated core. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:59.500 --> 02:01.520 dedicated core. 39 02:01.520 --> 02:02.800 Think about the benefits of that. 40 02:02.800 --> 02:07.450 If I have a dedicated core layer and a dedicated distribution layer, my 41 02:07.450 --> 02:08.960 distribution layer now 42 02:08.960 --> 02:13.000 is going to manage all of these access closets, meaning that we're going to 43 02:13.000 --> 02:13.760 have all of the 44 02:13.760 --> 02:16.160 SBI's here. 45 02:16.160 --> 02:20.800 But then we have all of the routing here at the core layer. 46 02:20.800 --> 02:24.180 This means that if we have some kind of major layer to issue and this network 47 02:24.180 --> 02:25.380 goes down, 48 02:25.380 --> 02:30.040 that our other sites can come into the core and still access the internet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:25.380 --> 02:30.040 that our other sites can come into the core and still access the internet. 49 02:30.040 --> 02:32.120 So those are some of the benefits. 50 02:32.120 --> 02:36.680 Now is it really required for site two and site three to come into dedicated 51 02:36.680 --> 02:37.560 switches? 52 02:37.560 --> 02:38.560 No, not at all. 53 02:38.560 --> 02:44.530 If I were to collapse these together and now we just have a pair of switches 54 02:44.530 --> 02:45.360 here that is 55 02:45.360 --> 02:48.280 performing the routing and the SBI's. 56 02:48.280 --> 02:53.530 Well yeah, we might have issues with a failure type of scenario like we talked 57 02:53.530 --> 02:54.840 about, but because 58 02:54.840 --> 03:00.000 we only have a few sites, the performance concerns are probably not there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:00.000 --> 03:05.750 I should be able to expect a lot of performance or not a lot of performance 60 03:05.750 --> 03:06.760 issues. 61 03:06.760 --> 03:12.080 Now next though, we've got to consider the fact that we have some amount of 62 03:12.080 --> 03:13.240 access points 63 03:13.240 --> 03:15.920 and users coming in to this head and site. 64 03:15.920 --> 03:17.600 So we've got access points out here. 65 03:17.600 --> 03:20.520 We have users and they're coming in here. 66 03:20.520 --> 03:24.540 So now things get a little bit more interesting because where do we connect 67 03:24.540 --> 03:25.160 these? 68 03:25.160 --> 03:28.740 With the collapsed core and distribution concept, we probably don't want to 69 03:28.740 --> 03:29.800 collapse our access 70 03:29.800 --> 03:31.040 layer in there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 03:29.800 --> 03:31.040 layer in there. 71 03:31.040 --> 03:35.280 Furthermore, because this is an access point, we're going to require a POE. 72 03:35.280 --> 03:40.760 So we might consider deploying a pair of access switches. 73 03:40.760 --> 03:42.680 And let me just draw those up here, I guess. 74 03:42.680 --> 03:48.360 So we bring them into a pair of access switches and then we connect those into 75 03:48.360 --> 03:49.280 either our distribution 76 03:49.280 --> 03:52.320 layer or our collapsed core and distribution. 77 03:52.320 --> 03:55.590 Now if we hadn't collapsed our core, maybe we could have brought them into the 78 03:55.590 --> 03:56.320 distribution 79 03:56.320 --> 04:00.800 switches, but the conversation, a lot of it's going to revolve around, did WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 03:56.320 --> 04:00.800 switches, but the conversation, a lot of it's going to revolve around, did 80 04:00.800 --> 04:02.000 those distribution 81 04:02.000 --> 04:04.680 switches support power of our ethernet or not. 82 04:04.680 --> 04:08.560 We start to see how we can end up with a lot of different designs here. 83 04:08.560 --> 04:14.500 Now lastly, we were told whether to extend layer 2 or layer 3 out here to the 84 04:14.500 --> 04:16.520 access layer. 85 04:16.520 --> 04:19.760 And for that matter, I suppose, deploying a fabric design. 86 04:19.760 --> 04:22.400 Again, really no right or wrong answer here. 87 04:22.400 --> 04:27.640 I will say that if we were collapsing this together and we're worried about 88 04:27.640 --> 04:28.800 that isolation 89 04:28.800 --> 04:34.040 issue, well, maybe we could just extend layer 3 to the access layer and then we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 04:28.800 --> 04:34.040 issue, well, maybe we could just extend layer 3 to the access layer and then we 90 04:34.040 --> 04:34.600 don't need 91 04:34.600 --> 04:38.080 to worry about any kind of layer 2 failure happening here. 92 04:38.080 --> 04:42.000 If this is layer 3, there won't be a loop, there won't be broadcast storms 93 04:42.000 --> 04:42.700 because it's 94 04:42.700 --> 04:44.720 all layer 3 everywhere. 95 04:44.720 --> 04:48.790 Furthermore, if we're not put off by the idea of deploying a fabric, we could 96 04:48.790 --> 04:50.160 consider a fabric, 97 04:50.160 --> 04:54.870 but I will say for just four closets, we're probably not going to get as much 98 04:54.870 --> 04:55.600 benefit out 99 04:55.600 --> 04:57.320 of that. 100 04:57.320 --> 05:03.270 Extending layer 3 and fabric technology, the more access closets we have, the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 04:57.320 --> 05:03.270 Extending layer 3 and fabric technology, the more access closets we have, the 101 05:03.270 --> 05:04.080 more benefit 102 05:04.080 --> 05:05.440 we're going to get. 103 05:05.440 --> 05:10.100 Because from a layer 2 perspective, just having four closets, it's really not 104 05:10.100 --> 05:10.880 going to create 105 05:10.880 --> 05:13.760 that large of a broadcast domain. 106 05:13.760 --> 05:17.960 So maybe we went with layer 2 because we said that there aren't enough access 107 05:17.960 --> 05:18.480 closets 108 05:18.480 --> 05:19.800 to justify it. 109 05:19.800 --> 05:25.740 Maybe we said layer 3 or fabric because we want to create isolation from the 110 05:25.740 --> 05:26.680 collapsed 111 05:26.680 --> 05:29.600 core distribution that we created. 112 05:29.600 --> 05:31.880 So again, lots and lots of options. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 112 05:29.600 --> 05:31.880 So again, lots and lots of options. 113 05:31.880 --> 05:34.200 Really it's more just about the conversation. 114 05:34.200 --> 05:38.960 Did we come up with some solutions and have good justification for it? 115 05:38.960 --> 05:42.380 Maybe by just sitting here talking about it, maybe there are some ideas you 116 05:42.380 --> 05:43.480 hadn't considered, 117 05:43.480 --> 05:44.480 like the POE thing. 118 05:44.480 --> 05:49.200 Maybe we didn't really consider the fact that we needed POE. 119 05:49.200 --> 05:53.210 And so we plugged them straight into our distribution switches, but no matter 120 05:53.210 --> 05:54.280 what here, as 121 05:54.280 --> 05:57.480 long as we have the underlying principles of what we're trying to accomplish 122 05:57.480 --> 05:57.800 and how 123 05:57.800 --> 06:02.070 we can best accomplish it, it's going to give us the capability of having those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 123 05:57.800 --> 06:02.070 we can best accomplish it, it's going to give us the capability of having those 124 06:02.070 --> 06:02.960 architectural 125 06:02.960 --> 06:08.540 conversations around collapsed design, two tier and three tier models, as well 126 06:08.540 --> 06:09.000 as layer 127 06:09.000 --> 06:12.800 2, layer 3, even fabric, access layer designs. 128 06:12.800 --> 06:15.360 I hope there's been informative for you and I'd like to thank you for viewing.