WEBVTT 1 00:00.000 --> 00:03.500 Alright, let's identify these blocks. 2 00:03.500 --> 00:07.280 And if you haven't yet done so, be sure to just pause the video and even if you 3 00:07.280 --> 00:07.700 don't 4 00:07.700 --> 00:11.760 have a pencil and paper available, just sort of mentally check off which of 5 00:11.760 --> 00:12.640 these blocks 6 00:12.640 --> 00:14.240 would serve which functions. 7 00:14.240 --> 00:17.240 But either way, let's go ahead and dive into this. 8 00:17.240 --> 00:19.200 Probably is best to start in the middle. 9 00:19.200 --> 00:24.240 If we have a true core layer, then we can expect to see this block in the 10 00:24.240 --> 00:25.560 middle that connects 11 00:25.560 --> 00:27.560 to many other blocks. 12 00:27.560 --> 00:30.360 And we can move over to this site over here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:27.560 --> 00:30.360 And we can move over to this site over here. 13 00:30.360 --> 00:34.520 And if we have a dedicated site with users connecting in, we're probably going 14 00:34.520 --> 00:34.960 to see 15 00:34.960 --> 00:38.040 a distribution and access block. 16 00:38.040 --> 00:41.630 And because we don't see any users coming into the distribution, it's not 17 00:41.630 --> 00:42.400 collapsed in 18 00:42.400 --> 00:43.400 any way. 19 00:43.400 --> 00:46.780 We're not collapsing the core into the distribution or the access into the 20 00:46.780 --> 00:47.680 distribution. 21 00:47.680 --> 00:50.720 This is a true three-tier design for Site 1. 22 00:50.720 --> 00:53.360 Meanwhile, we have this other small site. 23 00:53.360 --> 00:56.640 And we see that we've got kind of interestingly here. 24 00:56.640 --> 01:01.080 We've got users connecting in to a block that directly connects to the core. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:56.640 --> 01:01.080 We've got users connecting in to a block that directly connects to the core. 25 01:01.080 --> 01:03.740 Well, at this point, we know we don't have a three-tier model. 26 01:03.740 --> 01:05.600 This is a two-tier model. 27 01:05.600 --> 01:10.080 And that second tier is going to consist of both distribution and access 28 01:10.080 --> 01:11.320 functionality. 29 01:11.320 --> 01:14.800 So it's a collapsed distribution access block. 30 01:14.800 --> 01:16.360 Now moving over to the data center. 31 01:16.360 --> 01:20.760 Again, the data center is going to parallel a campus architecture or a campus 32 01:20.760 --> 01:21.360 site. 33 01:21.360 --> 01:26.280 It's just instead of a distribution block, we're going to have an aggregation 34 01:26.280 --> 01:26.880 block. 35 01:26.880 --> 01:30.760 Aggregation has roughly the same role as distribution. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:26.880 --> 01:30.760 Aggregation has roughly the same role as distribution. 36 01:30.760 --> 01:33.800 We're just going to see different protocols that play, especially as we've 37 01:33.800 --> 01:34.480 talked about 38 01:34.480 --> 01:36.080 virtual port channeling. 39 01:36.080 --> 01:39.320 It's something we can expect in the aggregation block. 40 01:39.320 --> 01:42.700 Now outside of that, we're just going to have a standard access layer that 41 01:42.700 --> 01:43.880 connects our 42 01:43.880 --> 01:48.160 data center appliances, servers, storage, whatever is there. 43 01:48.160 --> 01:51.810 And we can refer to this as the data center access block if we so desired to 44 01:51.810 --> 01:52.680 try to distinguish 45 01:52.680 --> 01:55.920 from a campus site access block. 46 01:55.920 --> 01:59.600 Now the other blocks are going to be based on what connects on the other side. 47 01:59.600 --> 02:03.600 We see remote sites are coming in to this block in the upper right. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 01:59.600 --> 02:03.600 We see remote sites are coming in to this block in the upper right. 48 02:03.600 --> 02:07.960 Those would probably be wide area network connected. 49 02:07.960 --> 02:12.630 Anytime we see these lighting bolt zigzag connections in a network diagram, we 50 02:12.630 --> 02:12.920 're usually 51 02:12.920 --> 02:17.290 looking at some kind of circuit to connect out to remote locations where we 52 02:17.290 --> 02:17.960 just can't 53 02:17.960 --> 02:20.480 connect in via the local area network. 54 02:20.480 --> 02:23.600 So that would be wide area network connectivity. 55 02:23.600 --> 02:27.560 And then we also have this block here, which is our internet block. 56 02:27.560 --> 02:30.480 As indicated by the fact that the internet is coming in here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:27.560 --> 02:30.480 As indicated by the fact that the internet is coming in here. 57 02:30.480 --> 02:34.280 So the internet block is probably going to consist of firewalls. 58 02:34.280 --> 02:37.830 And depending on our architecture, and maybe if we have multiple internet 59 02:37.830 --> 02:38.640 circuits coming 60 02:38.640 --> 02:42.720 in, we might also see some routers in here as well. 61 02:42.720 --> 02:48.300 And then we could run BGP to participate in the internet routing or maybe we 62 02:48.300 --> 02:49.080 just receive 63 02:49.080 --> 02:50.080 a default route. 64 02:50.080 --> 02:55.160 Again, it depends on the scope and scale of our internet architecture. 65 02:55.160 --> 02:58.640 But this is how we would build out this model. 66 02:58.640 --> 03:02.690 And again, we want to make sure we understand the functionality that each block WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 02:58.640 --> 03:02.690 And again, we want to make sure we understand the functionality that each block 67 03:02.690 --> 03:03.320 brings to 68 03:03.320 --> 03:03.800 the table.