WEBVTT 00:00:00.720 --> 00:00:15.800 Hello everyone and welcome to our next installment of our Cisco Encore Wireless 00:00:15.800 --> 00:00:23.320 section. Now this is something that's going to be down and quick. We're 00:00:23.320 --> 00:00:26.640 going to get this done as fast as possible giving you the information you 00:00:26.640 --> 00:00:31.160 need. One of the things I would recommend is because of the modern day 00:00:31.160 --> 00:00:36.200 and age is to dive into wireless. I mean it's an incredibly fascinating 00:00:36.200 --> 00:00:40.800 technology and it is taking over for your end users, right? They're used to it 00:00:40.800 --> 00:00:46.560 in their home environments, enterprise environments. It does represent a lot of 00:00:46.560 --> 00:00:50.480 risks. There's security issues with it. It's something that you need to pay 00:00:50.480 --> 00:00:54.600 attention to and know a little bit more about. So something I do recommend but 00:00:54.600 --> 00:01:02.520 for this again we are doing a deep dive into the exam topics for Encore that 00:01:02.520 --> 00:01:08.320 include wireless. So a quick easy exam hit, everything you need to know so to 00:01:08.320 --> 00:01:15.000 speak. So let's begin. We're talking about the different types of deployments we 00:01:15.000 --> 00:01:18.920 can see in our environment. The different type of architectures or deployment 00:01:18.920 --> 00:01:23.600 models. What are we looking at or the different types of wireless 00:01:23.600 --> 00:01:27.640 configurations that we can see out in the wild. Now when you're talking about 00:01:27.640 --> 00:01:31.560 an enterprise environment you're not talking about your home environment. 00:01:31.560 --> 00:01:35.920 You're not talking about your little wireless router or your, they call it a 00:01:35.920 --> 00:01:42.580 router slash wireless modem. Like that is not what we're talking about for the 00:01:42.580 --> 00:01:47.680 most part in enterprises. In enterprises we're talking about usually a controller 00:01:47.680 --> 00:01:53.200 based configuration. So what we're going to have are, we advanced too quick there, 00:01:53.320 --> 00:01:59.160 what we're going to have are these controllers that control all the little 00:01:59.160 --> 00:02:03.160 wireless access points. And if you see here I have this lightweight access 00:02:03.160 --> 00:02:07.240 point. I'm going to draw a little antenna here to kind of differentiate it from 00:02:07.240 --> 00:02:12.720 the other pieces of equipment. It throws out these wireless signals, right? 00:02:12.720 --> 00:02:18.160 But how does it understand its configuration? Well in an environment 00:02:18.160 --> 00:02:22.560 such as an enterprise environment usually, and I put the usually there, it 00:02:22.560 --> 00:02:28.080 goes back to what's known as a wireless LAN controller or WLC. And what happens 00:02:28.080 --> 00:02:33.560 is there's control plane traffic or management plane traffic that takes 00:02:33.560 --> 00:02:39.520 place here. It can be both actually. It takes place back and forth between the 00:02:39.520 --> 00:02:43.480 lightweight access point and the wireless LAN controller. And we can form 00:02:43.480 --> 00:02:49.520 even a tunnel across all of this for that traffic to flow directly from the 00:02:49.560 --> 00:02:53.120 lightweight access point to the wireless LAN controller. We'll talk about that a 00:02:53.120 --> 00:02:58.360 little bit later. These are called CAPWAP tunnels. But we want a centralized 00:02:58.360 --> 00:03:02.160 configuration managed. In smaller environments like your home, you may be 00:03:02.160 --> 00:03:09.760 used to having one wireless access point. And you know, you as a user, when you log 00:03:09.760 --> 00:03:14.120 in, you're messing with this either through your mobile phone or maybe a 00:03:14.120 --> 00:03:18.960 device on the local area network, something like that. But in our 00:03:18.960 --> 00:03:23.600 enterprise environments, you may have 10, 15, 20 different access points and you 00:03:23.600 --> 00:03:27.560 definitely want a centralized location so that you can do the configuration and 00:03:27.560 --> 00:03:33.200 let that controller do the heavy lifting for you instead of you having to log in 00:03:33.200 --> 00:03:39.360 to individual access points. So what does this all look like usually? Well here we 00:03:39.360 --> 00:03:44.160 have like a campus-wide, this is a pretty large environment, and here we can see 00:03:44.160 --> 00:03:49.800 the enterprise distribution or the enterprise core. This is your core network. 00:03:49.800 --> 00:03:55.960 So you might have multiple buildings or different floors in a large building or 00:03:55.960 --> 00:04:01.280 even multiple areas in a city, depending on your configuration. And what we have 00:04:01.280 --> 00:04:05.400 are all these lightweight APs. I'll tell you what a lightweight AP is a little 00:04:05.400 --> 00:04:10.400 later, we'll define it. But what we have are these access points that need 00:04:10.480 --> 00:04:17.240 information. And they need information on, hey, what am I doing? It will pull all the 00:04:17.240 --> 00:04:20.920 way up to this wireless LAN controller and the wireless LAN controller will be 00:04:20.920 --> 00:04:28.560 the one that says, okay, you are distributing these SSIDs, these are 00:04:28.560 --> 00:04:34.360 the VLANs. So we form these CAPWAP tunnels that go all the way back, and I'm 00:04:34.360 --> 00:04:38.360 gonna do a horrible job of drawing this just so you know, but we create these 00:04:38.360 --> 00:04:43.480 little tunnels and these tunnels take out all of, you know, the networking stuff 00:04:43.480 --> 00:04:47.000 that you're looking at and creates kind of like a point-to-point connection from 00:04:47.000 --> 00:04:51.120 the AP to the wireless LAN controller. So you can get things like authorization. 00:04:51.120 --> 00:04:57.360 Who's authorized to be on this wireless, this SSID? Well, I know who's 00:04:57.360 --> 00:05:02.120 allowed to do that. The people who are allowed to contact this SSID, the 00:05:02.120 --> 00:05:06.480 wireless LAN controller knows where to go. So this kind of answers all your 00:05:06.520 --> 00:05:11.040 questions for configuration. That's why you need that CAPWAP tunnel that goes 00:05:11.040 --> 00:05:18.160 back and forth. Now, it also is a point where the 802.11 frames on your network 00:05:18.160 --> 00:05:23.880 get transferred at the Lightweight AP into regular networking, 802.3 or 00:05:23.880 --> 00:05:29.000 Ethernet. So remember that in your environment as well. We go from our 00:05:29.000 --> 00:05:34.720 Lightweight AP. Once we hit here, we got to change into an 802.3 frame because 00:05:34.720 --> 00:05:40.280 we're using a different medium to move the devices, all right? So two things to 00:05:40.280 --> 00:05:45.400 remember, CAPWAP tunnels, centralized configuration, and then on the back 00:05:45.400 --> 00:05:50.760 burner, remember we're changing frames as we go from 802.11 to 802.3. There's 00:05:50.760 --> 00:05:54.200 got to be a conversion there. So this is what's called a centralized 00:05:54.200 --> 00:05:58.040 configuration, the one back here that we just saw. So we have an enterprise 00:05:58.040 --> 00:06:02.320 distribution core. Now this is cool because I save money. Wireless LAN 00:06:02.360 --> 00:06:09.880 controllers are expensive. The WLC is money. So if I can get away with having 00:06:09.880 --> 00:06:15.480 one wireless LAN controller in my environment, I'm gonna go ahead 00:06:15.480 --> 00:06:19.560 and do that. I'm gonna do what it takes. And by doing that, I mean I'm gonna set 00:06:19.560 --> 00:06:25.280 up these CAPWAP tunnels to go all the way to a centralized location for my 00:06:25.280 --> 00:06:32.400 organization. So let's call this, oh this is branch office one, and this is branch 00:06:32.400 --> 00:06:39.440 office two, and this is central, okay? And then all the high traffic is going up to 00:06:39.440 --> 00:06:44.600 the central office. Central office is then doing its, getting everything to the 00:06:44.600 --> 00:06:50.600 wireless LAN controller, and all this is taking place in a CAPWAP tunnel. So that 00:06:50.600 --> 00:06:55.000 traffic is not intermingling with your regular VLAN traffic or anything else. 00:06:55.320 --> 00:07:02.520 It's its own traffic. It's separated. Okay, so this is one solution. What does the 00:07:02.520 --> 00:07:06.720 other solution look like? Well the other solution is distributed, and I want you 00:07:06.720 --> 00:07:11.120 to get this out of this conversation right now. This is a more expensive model. 00:07:11.120 --> 00:07:16.840 But if you look at it, it's kind of more efficient because I'm not going all the 00:07:16.840 --> 00:07:21.800 way up into my core anymore for this type of communication. I'm just going 00:07:21.800 --> 00:07:26.000 directly to the top of the stack where I am. There's my wireless LAN controller, 00:07:26.000 --> 00:07:31.440 there's branch office one again, and here's branch office two, but now that I 00:07:31.440 --> 00:07:36.840 have two wireless LAN controllers that control this individually. So what did I 00:07:36.840 --> 00:07:45.240 do? I doubled my costs from last time. So not exactly the cheapest solution, in many 00:07:45.240 --> 00:07:51.680 ways not really super efficient, but if I have something like a paid link here, if 00:07:51.680 --> 00:07:58.040 I have a per packet or traffic based charge on this one, let's say this is 00:07:58.040 --> 00:08:05.360 remote Alaska. I'm in remote Alaska and I have a double satellite bounce, and I've 00:08:05.360 --> 00:08:09.360 actually done this before. Let's say this is a satellite 00:08:09.360 --> 00:08:24.760 bounce, right, and over to Anchorage, and they charge me per megabit that I move 00:08:24.760 --> 00:08:30.840 or per kilobit even based on some of those charges. Do I want to have all my 00:08:30.840 --> 00:08:36.000 wireless LAN controller in my distribution core? No thank you. That 00:08:36.040 --> 00:08:40.040 could get really expensive, especially if I have a ton of users here that are in 00:08:40.040 --> 00:08:46.240 that remote location. So it really depends on your environment if it's 00:08:46.240 --> 00:08:51.280 cost-effective, but for the most part this is a much more expensive model. It 00:08:51.280 --> 00:08:57.720 does save on that traffic moving across different links to the core though. So I 00:08:57.720 --> 00:09:02.800 promised you I would talk a little bit about lightweight APs, and here we go. 00:09:02.800 --> 00:09:07.720 Lightweight APs are used both by distributed and centralized systems, but 00:09:07.720 --> 00:09:14.080 mainly we're looking at an AP that relies on a controller. That's what we're 00:09:14.080 --> 00:09:18.640 really looking at. Oh, I already had this down here. It relies on a controller, and 00:09:18.640 --> 00:09:23.920 the controller is what configures the AP. Now I want to modify a little bit. Does 00:09:23.920 --> 00:09:28.400 it really configure it? Well yes, but you are the one that sets the configuration, 00:09:28.400 --> 00:09:38.600 and then the AP is then told by the wireless LAN controller what to do. So if 00:09:38.600 --> 00:09:45.840 I say I want the SSID that Stormwind rocks, the controller is the one that 00:09:45.840 --> 00:09:49.720 then takes that configuration and replicates it out to the lightweight AP 00:09:49.720 --> 00:09:56.440 and updates dynamically as conditions change. So based on your configuration, if 00:09:56.440 --> 00:10:02.640 something's changing, it's going to make sure that it is in alignment with that 00:10:02.640 --> 00:10:08.920 controller-based configuration that you set up. Now there are two kind of modes 00:10:08.920 --> 00:10:13.560 that we need to look at, and we'll dive way more into this later, and I really 00:10:13.560 --> 00:10:17.680 want you to know this. This is an important part of the exam. FlexConnect 00:10:17.680 --> 00:10:21.400 mode. I'm even going to give you a resource to study outside, but now is not 00:10:21.400 --> 00:10:24.600 the time for that. I want you to understand the definition of these two. 00:10:24.760 --> 00:10:33.720 Local mode. This just requires wireless LAN connectivity always. Okay, if you lose 00:10:33.720 --> 00:10:39.560 wireless LAN connectivity in local mode, you can't have authentication, people 00:10:39.560 --> 00:10:44.000 won't be able to connect because the lightweight APs won't know what to 00:10:44.000 --> 00:10:51.840 do. FlexConnect mode can still function if the wireless LAN controller cannot be 00:10:51.840 --> 00:10:55.920 reached. It's a big difference. That's why it's called FlexConnect mode. Now 00:10:55.920 --> 00:11:01.600 there's caveats there. FlexConnect won't be the solve-all problems because 00:11:01.600 --> 00:11:08.000 remember those APs, this is the main point here, these APs rely on the 00:11:08.000 --> 00:11:11.880 wireless LAN controller. They have a lightweight, they're called lightweight 00:11:11.880 --> 00:11:17.880 because they have a lightweight OS. They don't do a lot. Their function is solely 00:11:17.880 --> 00:11:24.160 to handle the traffic. They rely on the controller for configuration, 00:11:24.160 --> 00:11:31.120 authentication, handoff, SSID, roaming, all sorts of different features in our 00:11:31.120 --> 00:11:36.720 enterprise wireless environments are controlled by the controller. So we have 00:11:36.720 --> 00:11:41.680 to make sure we understand local mode. If you're set in local mode, those 00:11:41.680 --> 00:11:45.640 lightweight APs throw up their hands and say, I have no idea what's going on, I 00:11:45.760 --> 00:11:51.240 can't reach the controller, I'm down basically. FlexConnect mode is like, well 00:11:51.240 --> 00:11:57.240 I'm gonna kind of function on how I was told to react. What I was told to do, I'm 00:11:57.240 --> 00:12:01.720 gonna keep on going and doing that. Now one of the things that's not gonna work 00:12:01.720 --> 00:12:08.040 is any authentication for FlexConnect because it will not be able to reach the 00:12:08.040 --> 00:12:12.680 wireless LAN controller and our wireless LAN controller is the one that handles 00:12:12.680 --> 00:12:17.080 the communication to the RADIUS server or other things that give us that 00:12:17.080 --> 00:12:22.760 authentication. Whatever our identity manager is, that's what the wireless LAN 00:12:22.760 --> 00:12:28.920 controller communicates to, not the lightweight APs directly. 00:12:28.920 --> 00:12:35.680 All right, so AP review. We have autonomous. These are the standalone ones. 00:12:35.680 --> 00:12:42.760 Not gonna see this a lot. Remember, if I'm here, I have to manually configure 00:12:42.760 --> 00:12:49.040 each one. These have full-on OSs. You point these to RADIUS servers, all sorts 00:12:49.040 --> 00:12:53.040 of stuff. So there's a lot going on there. That's a lot of work, but 00:12:53.040 --> 00:12:57.440 each AP has the ability to act on its own. That's kind of good because I don't 00:12:57.440 --> 00:13:01.720 need a wireless LAN controller. So if I don't have a connection to a wireless LAN 00:13:01.720 --> 00:13:05.280 controller, it doesn't matter. I didn't need one to begin with. Everything I need 00:13:05.280 --> 00:13:12.920 is contained within the APs. This is more a non-enterprise solution. 00:13:12.920 --> 00:13:17.440 Can't handle as much traffic. That's not what they're dedicated for. You know, this 00:13:17.440 --> 00:13:21.920 is for your home office. This is for your small office. FlexConnect, we talked about. 00:13:21.920 --> 00:13:27.040 That's the one that I'm gonna go with the configuration I was given. I was 00:13:27.040 --> 00:13:30.640 given the configuration by the wireless LAN controller. I'm gonna keep doing what 00:13:30.640 --> 00:13:34.920 I was told to do. If there's some type of roaming that takes place, if there's 00:13:34.920 --> 00:13:38.800 some type, in some cases I'm gonna fail because I need that verification from 00:13:38.800 --> 00:13:42.720 the wireless LAN controller and I can't reach it, I'm gonna fall apart. But if I 00:13:42.720 --> 00:13:46.560 can reach, if connectivity is good and I can reach the wireless LAN controller, no 00:13:46.560 --> 00:13:55.880 problem. I got it. Centralized local and converged. If I have a centralized local 00:13:55.880 --> 00:14:02.560 device, that means I have one location I'm going to. The wireless LAN controller 00:14:02.600 --> 00:14:07.440 is where? Well, the wireless LAN controller is in my core. Core of my main 00:14:07.440 --> 00:14:14.920 office or central office. And then I can reach that, get my configuration, pull it 00:14:14.920 --> 00:14:20.520 down. Converged. This is a switch and wireless controller one. It does 00:14:20.520 --> 00:14:25.680 everything. And the traffic is distributed at the switch. Instead of 00:14:25.680 --> 00:14:28.640 having to go up to this wireless LAN controller, I'm gonna draw this and erase 00:14:28.640 --> 00:14:34.080 it. Instead of having to go up there, I can just go up here and any local traffic is 00:14:34.080 --> 00:14:39.360 just switched locally. Pretty good. So these are the different kinds of 00:14:39.360 --> 00:14:43.440 autonomous, FlexConnect, centralized, and converged architectures that you can see 00:14:43.440 --> 00:14:50.960 out there in the wild. These are deployment models. So in those standalone 00:14:50.960 --> 00:14:57.040 configurations, what do I need? Well, in a controller-less, when I have no wireless 00:14:57.040 --> 00:15:03.880 LAN controller and I have access points and they need to reach the rest of the 00:15:03.880 --> 00:15:07.600 world, I gotta configure it just like I did with everything else. I have an 00:15:07.600 --> 00:15:14.520 access trunk access link here and then I have a trunk link here. There's a 00:15:14.520 --> 00:15:19.280 controller-less configuration. I have an SSID. It moves across this access point, 00:15:19.280 --> 00:15:26.280 hits this switch, and then it needs to hit the right VLAN. Okay, what's the VLAN 00:15:26.280 --> 00:15:31.640 here? Well, if my wireless, let's say my wireless is VLAN 80. Okay, so I hit 00:15:31.640 --> 00:15:36.440 wireless VLAN 80. This port needs to be in 80 and then this needs to be trunked 00:15:36.440 --> 00:15:40.960 because I not only need to carry 80 to the distribution switch, but I might be 00:15:40.960 --> 00:15:45.200 carrying regular data which might be 90 or 100 or whatever you're using in your 00:15:45.200 --> 00:15:53.560 device. This is okay, but again, controller-less is for small deployments. I don't have a 00:15:53.600 --> 00:15:58.880 wireless LAN controller I'm pushing to. The AP handles all of it. This is not a 00:15:58.880 --> 00:16:03.800 lightweight access point. This is a stand-alone. 00:16:08.600 --> 00:16:13.400 So, like we said, in a controller-less, there's no wireless LAN controller and 00:16:13.400 --> 00:16:22.480 the AP OS handles the request. So everything I need is right here. Those of 00:16:22.480 --> 00:16:28.800 you who think that Meraki is a controller-less configuration, not true. 00:16:28.800 --> 00:16:34.920 Meraki is up here in the cloud. I draw the cloud. Okay, that's how the cloud looks. 00:16:34.920 --> 00:16:38.880 And then you have your wireless LAN controller. Although they don't call it 00:16:38.880 --> 00:16:44.160 that, that's what it is up in the cloud that's helping out. So that's what a 00:16:44.160 --> 00:16:53.160 Meraki is. Your home devices use this, the stand-alone AP, and the OS is strong 00:16:53.160 --> 00:16:57.920 enough here. Lightweight APs are focused on that traffic. All their processing 00:16:57.920 --> 00:17:02.720 power, all of this is focused on traffic so they can handle more traffic than your 00:17:02.720 --> 00:17:08.640 regular home AP can or your small office AP can. That's the difference between the 00:17:08.640 --> 00:17:11.400 two. I know you guys are thinking, well, it's an enterprise solution. Why aren't 00:17:11.440 --> 00:17:17.320 those APs bulkier? They're bulkier, 100%. They're also made to handle 30, 40 users 00:17:17.320 --> 00:17:22.240 at a time. These stand-alone controller-less APs are not meant to handle that much 00:17:22.240 --> 00:17:27.360 traffic and will bog down if you put them under that much stress. You'll just see it. 00:17:27.360 --> 00:17:33.360 The antennas aren't right. The antennas aren't spread right. Consumer deployment 00:17:33.360 --> 00:17:38.280 of APs, while great for four or five people, do not scale up to enterprise 00:17:38.280 --> 00:17:42.560 environments. So if you are sitting there right now in an environment that you've 00:17:42.560 --> 00:17:52.080 actually had consumer-grade APs in there, it's time to upgrade to enterprise APs. 00:17:52.080 --> 00:17:56.080 There's a big difference between the two, especially if you have a lot of people. If 00:17:56.080 --> 00:17:59.440 you have less than 10 people in your office, don't worry about it. It'll handle 00:17:59.440 --> 00:18:04.120 it just fine. So what about a cloud deployment? What does that look like? Well, 00:18:04.120 --> 00:18:08.240 that's kind of what we talked about. Those of you who use Meraki, this is a 00:18:08.240 --> 00:18:16.000 cloud deployment. This is exactly what it is. In fact, I was in the early, I 00:18:16.000 --> 00:18:21.520 wouldn't say it was beta, but before Cisco owned Meraki, we saw the same thing 00:18:21.520 --> 00:18:27.040 here, but I was in Alaska, something I alluded to earlier, and the reason why we 00:18:27.040 --> 00:18:30.480 didn't go with the solution, we were given the option to go for the solution, 00:18:30.480 --> 00:18:35.480 but we didn't, is because of this right here. It goes to your enterprise 00:18:35.480 --> 00:18:40.840 server, but what it has to do is it has to go up into the internet and reach the 00:18:40.840 --> 00:18:47.320 Meraki servers, because that's where your wireless LAN controller is hosted. So 00:18:47.320 --> 00:18:53.600 what happens if you don't reach those servers? I believe it was within 00:18:53.600 --> 00:18:58.920 five minutes. I don't really remember. I think it was five minutes. If you don't 00:18:58.920 --> 00:19:03.120 reach that cloud controller in five minutes, everything goes down. Your 00:19:03.160 --> 00:19:10.760 different devices go down. Now that's not a huge deal here, right? Here in the US, 00:19:10.760 --> 00:19:16.640 or mainland, let me change that, United States, mainland United States, you're not 00:19:16.640 --> 00:19:21.120 going to go down for five minutes a lot in an enterprise environment, one, and two, 00:19:21.120 --> 00:19:26.160 if you're down anyways for your wireless environment, it's not as 00:19:26.160 --> 00:19:32.680 hurtful, because most of my resources are online these days, but in Alaska, I'm 00:19:32.720 --> 00:19:35.920 going to show you something. It's a little different. We have a lot of local 00:19:35.920 --> 00:19:40.480 resources in remote Alaska. That's because we use like a microwave throw. 00:19:40.480 --> 00:19:45.680 Remember I showed you that? We use microwave throws a lot, or not even 00:19:45.680 --> 00:19:50.600 microwave, we use satellite throws a lot. We do use microwave throws as well, 00:19:50.600 --> 00:19:55.800 between sites, and we use satellite throws from, and this not so much anymore, 00:19:55.960 --> 00:20:03.520 but used to be, from like Bethel, Alaska, over to Anchorage, because there was no 00:20:03.520 --> 00:20:08.040 infrastructure in between. There was no fiber back in those days. So this was a 00:20:08.040 --> 00:20:14.520 charged link, right? This cost money, and it was unreliable. It wasn't always up. 00:20:14.520 --> 00:20:18.840 I think we paid a lot of money for 100 megabits back then, but this wasn't 00:20:18.840 --> 00:20:22.320 always up, it would go down. So this Meraki solution, even though we were 00:20:22.320 --> 00:20:26.400 intrigued, and we loved how it worked, and you know, it would be great, for us in 00:20:26.400 --> 00:20:32.560 Alaska, losing this connection to the internet was likely, and it happened 00:20:32.560 --> 00:20:37.320 on a weekly basis. So we couldn't have our network going up and down, because we 00:20:37.320 --> 00:20:42.520 still needed access to these local resources. I had open 00:20:42.520 --> 00:20:47.920 directory here that I needed access to, and then we had all the resources for 00:20:47.960 --> 00:20:52.840 all the employees there. We didn't have anything cloud storage, just 00:20:52.840 --> 00:20:57.800 because of that link. So again, deployments depend a lot on your 00:20:57.800 --> 00:21:02.160 organization, the infrastructure available to you. So Meraki, great 00:21:02.160 --> 00:21:07.000 solution, loved to deploy it myself, and in fact we have it here at Stormwind, but 00:21:07.000 --> 00:21:14.160 in Alaska, was not a good solution for us at the time. So basically, that's what I 00:21:14.240 --> 00:21:20.360 have for this section. I really want you to pay attention to that FlexConnect. 00:21:20.360 --> 00:21:25.240 That's going to be a big part of the test. Understand when FlexConnect is up, 00:21:25.240 --> 00:21:28.360 and when FlexConnect is not going to help you, and we're going to go through 00:21:28.360 --> 00:21:32.000 that through different lessons, okay? So we're not done there. I'll give you more 00:21:32.000 --> 00:21:35.920 resources as we go through, but understand what FlexConnect is about. We 00:21:35.920 --> 00:21:39.800 have that wireless LAN controller. Wireless LAN controller controls 00:21:39.800 --> 00:21:43.800 everything in our enterprise environment. If I can't reach the wireless LAN 00:21:43.800 --> 00:21:50.440 controller, I'm in local mode, nothing's happening. The AP cannot verify who 00:21:50.440 --> 00:21:54.480 needs to be on what SSID, and if they have permissions, or anything like that. 00:21:54.480 --> 00:21:59.360 It can't go out to a RADIUS server or anything for authentication and feed 00:21:59.360 --> 00:22:03.640 that back to the AP, so big trouble. Big trouble if I can't do what I need to 00:22:03.640 --> 00:22:09.320 there. So local mode, you can't reach the wireless LAN controller, the system's 00:22:09.320 --> 00:22:17.000 down. If I'm in Flex mode, and I can't reach the wireless LAN controller, I'll 00:22:17.000 --> 00:22:22.880 try and keep going as an AP. I'll try and make it happen. I'll operate under the 00:22:22.880 --> 00:22:28.120 same settings that I had before. So anybody who's connected in FlexConnect 00:22:28.120 --> 00:22:33.040 mode, when the AP loses access to that wireless LAN controller, will 00:22:33.040 --> 00:22:37.320 continue to be connected. The problem starts to happen when they try and roam, 00:22:37.320 --> 00:22:42.680 or new users want to come online and come into the wireless LAN. 00:22:42.680 --> 00:22:47.680 That's when you'll start to see issues. So that's it for this section. I will see 00:22:47.680 --> 00:22:53.120 you in the next one. Happy wireless everyone. Bye.