WEBVTT 1 00:00.000 --> 00:04.880 So, as mentioned in the challenge itself, there aren't going to be a lot of 2 00:04.880 --> 00:05.600 wrong answers 3 00:05.600 --> 00:06.600 here. 4 00:06.600 --> 00:09.230 We could probably come up with something that is so outlandish that should 5 00:09.230 --> 00:10.440 never be done. 6 00:10.440 --> 00:13.290 But we want to think back to those deployment models and what we learned about 7 00:13.290 --> 00:14.360 capwap tunnels 8 00:14.360 --> 00:18.330 and lightweight architecture in general and put some thought into where we 9 00:18.330 --> 00:19.000 might put the 10 00:19.000 --> 00:21.080 wireless LAN controllers. 11 00:21.080 --> 00:24.440 And again, I would expect that there could be several valid options here. 12 00:24.440 --> 00:26.480 So let's talk through some of those. 13 00:26.480 --> 00:31.520 So first of all, let's talk about a centralized option. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:26.480 --> 00:31.520 So first of all, let's talk about a centralized option. 14 00:31.520 --> 00:36.090 The centralized option says we're going to deploy a single pair of HA 15 00:36.090 --> 00:37.280 controllers. 16 00:37.280 --> 00:41.020 And we probably want to pick a site that has a lot of access points to be our 17 00:41.020 --> 00:41.800 centralized 18 00:41.800 --> 00:42.800 location. 19 00:42.800 --> 00:47.240 Again, we should never deploy a wireless LAN controller into a layer 3 core. 20 00:47.240 --> 00:50.830 We ideally don't deploy it into a data center, although sometimes it does make 21 00:50.830 --> 00:51.240 the most 22 00:51.240 --> 00:52.800 sense to do so. 23 00:52.800 --> 00:57.670 And so instead, what I would do from an outward design perspective is I would 24 00:57.670 --> 00:58.320 place those 25 00:58.320 --> 01:03.600 controllers here in this distribution block at site 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 00:58.320 --> 01:03.600 controllers here in this distribution block at site 2. 26 01:03.600 --> 01:07.160 And the reason for that is it has a lot of access points. 27 01:07.160 --> 01:10.440 So that would be a purely centralized model. 28 01:10.440 --> 01:13.720 We would put the wireless LAN controller here. 29 01:13.720 --> 01:16.000 And again, it would be an HA pair. 30 01:16.000 --> 01:19.970 Now the upside to that is it's a single wireless LAN controller I have to 31 01:19.970 --> 01:20.720 manage. 32 01:20.720 --> 01:26.880 The downside is we've got everything from remote sites to WAN sites. 33 01:26.880 --> 01:31.680 So I guess sites connected directly via the core versus sites that have to go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:26.880 --> 01:31.680 So I guess sites connected directly via the core versus sites that have to go 34 01:31.680 --> 01:32.240 through 35 01:32.240 --> 01:33.840 the WAN block. 36 01:33.840 --> 01:38.650 And a lot of that is going to potentially cause us some problems, at least as 37 01:38.650 --> 01:39.360 far as WAN 38 01:39.360 --> 01:43.160 sites go down and those kinds of things or WAN links go down. 39 01:43.160 --> 01:47.560 Now we could also look at a distributed model. 40 01:47.560 --> 01:51.320 If we look at the distributed model, then that's right there in the name, 41 01:51.320 --> 01:53.120 distribute distribution. 42 01:53.120 --> 01:57.950 We'd probably want to deploy wireless LAN controllers in all three of these 43 01:57.950 --> 01:58.960 distribution 44 01:58.960 --> 02:00.640 blocks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 01:58.960 --> 02:00.640 blocks. 45 02:00.640 --> 02:05.040 This way the access points only connect locally to a wireless LAN controller. 46 02:05.040 --> 02:10.800 They also live on subnets that are attached to the actual distribution blocks 47 02:10.800 --> 02:10.960 that are 48 02:10.960 --> 02:13.080 associated with their locations. 49 02:13.080 --> 02:15.470 And then we'd have to figure out what to do about these remote sites, whether 50 02:15.470 --> 02:15.880 they're 51 02:15.880 --> 02:20.010 going to come into, well specifically, this wireless LAN controller or this 52 02:20.010 --> 02:21.280 wireless LAN controller 53 02:21.280 --> 02:22.280 pair. 54 02:22.280 --> 02:24.160 And we could have primary and second areas. 55 02:24.160 --> 02:27.280 So we've got a lot of options there. 56 02:27.280 --> 02:30.820 The downside is I have three different wireless LAN controllers that I have to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:27.280 --> 02:30.820 The downside is I have three different wireless LAN controllers that I have to 57 02:30.820 --> 02:31.360 manage, but 58 02:31.360 --> 02:33.040 three is not too bad. 59 02:33.040 --> 02:36.600 And so that would be a perfectly valid option as well. 60 02:36.600 --> 02:41.200 Now we could have also suggested we just go with a cloud architecture. 61 02:41.200 --> 02:45.020 This would mean that we have no wireless LAN controllers in the entire 62 02:45.020 --> 02:46.040 environment. 63 02:46.040 --> 02:49.520 Instead the access points are going to connect out through wherever the 64 02:49.520 --> 02:50.680 internet is to connect 65 02:50.680 --> 02:52.640 to the cloud. 66 02:52.640 --> 02:57.430 The downside to that is if our internet goes down or we have problems with that 67 02:57.430 --> 02:58.880 cloud provider, 68 02:58.880 --> 03:01.960 that we might actually see our wireless network impacted. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 02:58.880 --> 03:01.960 that we might actually see our wireless network impacted. 69 03:01.960 --> 03:06.920 But cloud is a very valid architecture that a lot of organizations rely on. 70 03:06.920 --> 03:12.640 And again, Cisco does have an architecture for that with their Miracchi 71 03:12.640 --> 03:13.760 platform. 72 03:13.760 --> 03:19.260 Now lastly, we could also consider something special over here with these rem 73 03:19.260 --> 03:19.960 otes. 74 03:19.960 --> 03:23.680 And that would be leveraging FlexConnect. 75 03:23.680 --> 03:27.440 I would argue that in all of these, well maybe not cloud because cloud is a 76 03:27.440 --> 03:28.600 little different, 77 03:28.600 --> 03:32.800 both centralized and distributed models, I would argue that FlexConnect should WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 03:28.600 --> 03:32.800 both centralized and distributed models, I would argue that FlexConnect should 78 03:32.800 --> 03:34.480 be used 79 03:34.480 --> 03:36.840 with both of those. 80 03:36.840 --> 03:41.140 Because if I'm centralized here or I'm decentralized either way, there's not a 81 03:41.140 --> 03:42.360 wireless LAN controller 82 03:42.360 --> 03:44.560 out here at the remote sites. 83 03:44.560 --> 03:47.670 Now if you suggested that we put a small wireless LAN controller out here, that 84 03:47.670 --> 03:49.040 's probably fine. 85 03:49.040 --> 03:53.280 The four access points, we do have very small controllers for that. 86 03:53.280 --> 03:55.240 Twenty starts to get a little bit larger. 87 03:55.240 --> 03:58.160 We're going to want to explore an HAPAR. 88 03:58.160 --> 04:04.780 And in a lot of cases, it's pretty clear that it doesn't warrant the expense of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 88 03:58.160 --> 04:04.780 And in a lot of cases, it's pretty clear that it doesn't warrant the expense of 89 04:04.780 --> 04:05.000 taking 90 04:05.000 --> 04:09.550 that distributed model and applying that to the remote sites that are out the W 91 04:09.550 --> 04:10.280 AN links. 92 04:10.280 --> 04:12.920 So instead we can find a happy compromise here. 93 04:12.920 --> 04:18.040 Whether it was centralized or distributed, we can then deploy FlexConnect. 94 04:18.040 --> 04:21.660 And that's going to make sure that our wireless access points stay online in 95 04:21.660 --> 04:22.400 the event of a 96 04:22.400 --> 04:23.600 WAN outage. 97 04:23.600 --> 04:27.680 It also makes it so we don't have to have wireless LAN controllers locally. 98 04:27.680 --> 04:32.370 And even better, the traffic gets dropped off locally, meaning that my wireless WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 04:27.680 --> 04:32.370 And even better, the traffic gets dropped off locally, meaning that my wireless 99 04:32.370 --> 04:32.920 client 100 04:32.920 --> 04:38.120 traffic doesn't have to exist on a subnet that belongs to a different location. 101 04:38.120 --> 04:41.740 So as we see here, we alluded to it earlier, the location of the wireless LAN 102 04:41.740 --> 04:42.400 controller 103 04:42.400 --> 04:43.720 matters greatly. 104 04:43.720 --> 04:48.210 And as everything to do with those KAPWF tunnels, as well as just having a 105 04:48.210 --> 04:49.240 redundant, easy to 106 04:49.240 --> 04:52.670 access location, we need to think about whether we're going to deploy a 107 04:52.670 --> 04:54.440 centralized or distributed 108 04:54.440 --> 04:55.440 model. 109 04:55.440 --> 04:58.680 We need to think about deploying potentially a cloud solution. 110 04:58.680 --> 05:01.840 FlexConnect is a very important part of wireless architecture. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 04:58.680 --> 05:01.840 FlexConnect is a very important part of wireless architecture. 111 05:01.840 --> 05:06.850 And all of this is going to just give us a lot of different things to think 112 05:06.850 --> 05:07.520 about when 113 05:07.520 --> 05:10.320 we're deciding where to deploy wireless LAN controllers, whether we should 114 05:10.320 --> 05:10.840 deploy them 115 05:10.840 --> 05:11.840 at all. 116 05:11.840 --> 05:15.960 And in the end, what are wireless architectures going to look like? 117 05:15.960 --> 05:18.560 I hope this has been informative for you and I'd like to thank you for viewing.