WEBVTT 00:00:00.000 --> 00:00:16.700 Hi everyone, I assure you we're nearing the end of our wireless journey here for Encore. 00:00:16.700 --> 00:00:24.320 We are hyper focused on what we might see in the Encore exam for wireless. 00:00:24.320 --> 00:00:28.280 So let's go ahead and dive in to AP modes. 00:00:28.280 --> 00:00:33.520 Now AP modes are how we're going to configure our access points, and this is where we're 00:00:33.520 --> 00:00:38.960 going to dive into FlexConnect, Bridged, and other configurations for our APs that really 00:00:38.960 --> 00:00:43.960 changes the behavior depending on what's happening with our connectivity to our wireless LAN 00:00:43.960 --> 00:00:45.160 controllers. 00:00:45.160 --> 00:00:48.040 So let's dive into some of these solutions. 00:00:48.040 --> 00:00:52.000 Let me move myself to the other side so you can see what we're talking about. 00:00:52.000 --> 00:00:53.720 These are the modes we're going to focus on. 00:00:53.720 --> 00:00:57.320 There's other modes we're going to talk about, but right here, Local. 00:00:57.320 --> 00:01:01.240 Remember Local means that we are 100% reliant on what? 00:01:01.240 --> 00:01:07.160 We're 100% reliant on the wireless LAN controller being reachable. 00:01:07.160 --> 00:01:10.760 I have to be able to connect to it. 00:01:10.760 --> 00:01:11.960 FlexConnect is different. 00:01:11.960 --> 00:01:17.640 FlexConnect means I have the ability to connect to the wireless LAN controller, yes, but if 00:01:17.640 --> 00:01:25.320 it goes down, maybe my APs can work depending on the scenario, and that's a huge depending. 00:01:25.320 --> 00:01:27.440 That's why it's called FlexConnect. 00:01:27.440 --> 00:01:31.080 Sometimes you're connected, maybe your connection is not so reliable, so you want to set up 00:01:31.080 --> 00:01:36.480 FlexConnect to your wireless LAN controller, so if you somehow lose reachability to that 00:01:36.480 --> 00:01:41.280 wireless LAN controller, you want the people who are at least still connected to remain 00:01:41.280 --> 00:01:46.200 connected on their wireless LAN, be able to use it somewhat. 00:01:46.200 --> 00:01:52.520 Now there's some caveats here to whether or not users who are not authenticated and logging 00:01:52.520 --> 00:01:56.320 on for the first time, what will happen in those cases, and I'm going to show you the 00:01:56.320 --> 00:01:57.640 perfect matrix. 00:01:57.640 --> 00:02:02.960 I'm going to give you those websites, and you will have to review those on your own, 00:02:02.960 --> 00:02:05.480 but it's very, very important. 00:02:05.480 --> 00:02:09.800 This is very, very important, and this is very, very important. 00:02:09.800 --> 00:02:11.840 Let me underline those. 00:02:11.840 --> 00:02:12.840 Remember what I said. 00:02:12.840 --> 00:02:15.640 Whenever I underline something, you got to know it. 00:02:15.640 --> 00:02:20.240 Bridge or Mesh mode is when I have an AP connected to another AP. 00:02:20.240 --> 00:02:22.440 Let's put little antennas on a box here. 00:02:22.440 --> 00:02:27.480 That's our AP, and let's put another AP here, but this one's actually connected up. 00:02:27.480 --> 00:02:34.240 Let's say I have a Mesh where this AP is talking to this AP to get to this wireless LAN controller 00:02:34.240 --> 00:02:35.800 over here. 00:02:35.800 --> 00:02:42.760 When I do this, usually, usually, Mesh does not work with FlexConnect. 00:02:42.760 --> 00:02:43.760 Does not happen. 00:02:43.760 --> 00:02:48.560 That is not how this works, but I can use Flex plus Bridge mode, which is kind of like 00:02:48.560 --> 00:02:51.680 a hybrid to make this work, right? 00:02:51.680 --> 00:02:56.920 FlexConnect plus Mesh does not work, but if I change the word to Bridge, there's some 00:02:56.920 --> 00:03:00.160 options to make it happen so that this kind of works. 00:03:00.160 --> 00:03:10.000 Here's why this doesn't work is because I'm stuck on the VLAN that this AP is at, right? 00:03:10.000 --> 00:03:16.320 I'm stuck with whatever configuration that AP has because I'm bridging through wireless. 00:03:16.320 --> 00:03:19.000 I'm going, there's no CAPWAP tunnel here. 00:03:19.000 --> 00:03:25.560 I'm doing a complete transfer Mesh network between one AP and another. 00:03:25.560 --> 00:03:27.320 That's the problem with a Mesh network. 00:03:27.320 --> 00:03:32.400 Now FlexBridge allows us a little bit of a configuration difference that allows this 00:03:32.400 --> 00:03:35.000 Mesh to actually kind of work, okay? 00:03:35.000 --> 00:03:40.160 So we'll go through that in a bit, and I'll show you, I'll give you the actual, I'll give 00:03:40.160 --> 00:03:41.160 you a document. 00:03:41.160 --> 00:03:42.160 That's what we'll do. 00:03:42.160 --> 00:03:49.360 I'll give you a document in your supplemental learning stuff that has these two websites 00:03:49.360 --> 00:03:50.360 on it for you. 00:03:50.360 --> 00:03:52.320 I don't know why I forgot that, but it did. 00:03:52.320 --> 00:03:57.000 These two websites that will give you access to this information, very important for your 00:03:57.000 --> 00:03:58.320 learning process here. 00:03:58.320 --> 00:04:00.080 All right, so let's dive in. 00:04:00.080 --> 00:04:01.080 Local mode. 00:04:01.080 --> 00:04:04.240 This is the default mode for lightweight APs. 00:04:04.240 --> 00:04:07.640 If you don't change any settings, we're going with local mode. 00:04:07.640 --> 00:04:08.920 Why is that? 00:04:08.920 --> 00:04:13.720 Well, FlexConnect isn't something that we usually have to worry about. 00:04:13.720 --> 00:04:16.760 Am I worried about my connection to my wireless LAN controller? 00:04:16.760 --> 00:04:18.200 No, not usually. 00:04:18.200 --> 00:04:23.520 If I have no connection to my wireless LAN controller, I usually have bigger problems 00:04:23.520 --> 00:04:26.120 in a normal enterprise environment. 00:04:26.120 --> 00:04:31.240 The other configurations are for special instances. 00:04:31.240 --> 00:04:37.080 Maybe I have a microwave throw that gives me trouble between two sites and the wireless 00:04:37.080 --> 00:04:41.040 LAN controller isn't always reachable. 00:04:41.040 --> 00:04:46.720 We create two CAPWAP tunnels to the wireless LAN controller in local mode. 00:04:46.720 --> 00:04:49.040 One is for data and one is for management. 00:04:49.040 --> 00:04:53.840 So those management frames, different from the data frames, and they're kept separate. 00:04:53.840 --> 00:04:57.760 AP directly connects to the wireless LAN controller. 00:04:57.760 --> 00:04:59.560 That's what these CAPWAP tunnels are. 00:04:59.560 --> 00:05:03.080 Remember, I told you these are point to point, essentially. 00:05:04.080 --> 00:05:06.400 CAPWAP, do I have enough room? 00:05:06.400 --> 00:05:07.680 I do. 00:05:07.680 --> 00:05:10.800 So it is essentially a point to point connection. 00:05:10.800 --> 00:05:13.600 Physically, no, it isn't. 00:05:13.600 --> 00:05:18.480 Logically, yes, it is directly connected to the wireless LAN controller. 00:05:18.480 --> 00:05:24.280 And this, we already said, this is reliable connectivity to your wireless LAN controller. 00:05:24.280 --> 00:05:27.680 When you have this, you don't have to worry about anything else. 00:05:27.680 --> 00:05:32.680 But the problem is, if it's not reliable, if I have no connection, I have no access 00:05:32.680 --> 00:05:34.400 to the wireless LAN controller. 00:05:34.400 --> 00:05:36.000 No ifs, ands, and buts. 00:05:36.000 --> 00:05:42.080 Even if I'm already connected, and my client's already connected to the AP, if the AP loses 00:05:42.080 --> 00:05:46.160 connectivity to that wireless LAN controller, I'm down. 00:05:46.160 --> 00:05:50.000 That's the end of the story, okay? 00:05:50.000 --> 00:05:51.240 Let's introduce our solution. 00:05:51.240 --> 00:05:57.160 Well, maybe you don't have a super reliable connection to your wireless LAN controller. 00:05:57.280 --> 00:06:04.520 Maybe you're in a microwave throw, and I know they say weather doesn't affect it, but let's 00:06:04.520 --> 00:06:06.120 say there's a lot of scatter in the air. 00:06:06.120 --> 00:06:10.760 Somebody's throwing up aluminum foil into the air between your microwave throw. 00:06:10.760 --> 00:06:12.880 Maybe it's not reliable. 00:06:12.880 --> 00:06:14.920 You need flex connecting bolts. 00:06:14.920 --> 00:06:20.600 This allows the data track to be switched locally, if necessary. 00:06:20.600 --> 00:06:24.280 I do not always need to go back to the controller. 00:06:24.280 --> 00:06:26.880 Now there are special caveats to this. 00:06:26.880 --> 00:06:30.000 I want you to look this up when we get there. 00:06:30.000 --> 00:06:34.440 It allows wireless traffic to egrace the switch port of the access point. 00:06:34.440 --> 00:06:44.560 We're not, notice this, wireless LAN controller does not have to move data. 00:06:44.560 --> 00:06:48.920 I had to look up there for a second. 00:06:48.920 --> 00:06:51.560 And this is the important part. 00:06:51.560 --> 00:06:55.480 We're still managed by the wireless LAN controller, 100%. 00:06:55.480 --> 00:07:01.400 But what I'm telling you is, if I have someone who's connected to that wireless LAN, and 00:07:01.400 --> 00:07:07.160 I lose connectivity to the wireless LAN controller, because I'm locally switched, because I'm 00:07:07.160 --> 00:07:14.960 moving data directly out into the local network, I do not necessarily lose connectivity. 00:07:14.960 --> 00:07:20.680 I don't necessarily need that wireless LAN controller for everything. 00:07:20.680 --> 00:07:23.360 We can still function if not connected. 00:07:23.360 --> 00:07:30.960 Now it's important to understand that this has a huge asterisk next to it. 00:07:30.960 --> 00:07:33.760 Can I do everything? 00:07:33.760 --> 00:07:35.080 Absolutely not. 00:07:35.080 --> 00:07:38.240 You are not going to be able to do everything. 00:07:38.240 --> 00:07:39.240 So let's go ahead. 00:07:39.240 --> 00:07:41.200 I'm going to jump to the website. 00:07:41.200 --> 00:07:45.120 I'm going to give you, apparently I have to move it down. 00:07:45.120 --> 00:07:47.560 Hang on, give me a second here. 00:07:47.560 --> 00:07:50.120 I'll move this down and then pop this up. 00:07:50.120 --> 00:07:51.120 There we go. 00:07:51.720 --> 00:07:54.600 So this is the FlexConnect feature. 00:07:54.600 --> 00:07:56.920 We're going to discuss the matrix. 00:07:56.920 --> 00:08:01.600 I'm going to show, not the actual matrix, we're not going Neo here, but I'm going to 00:08:01.600 --> 00:08:05.920 show you some of the different things that happen. 00:08:05.920 --> 00:08:07.920 I want you to read this. 00:08:07.920 --> 00:08:12.280 When we have WAN up with central switching, can I have open static WEP? 00:08:12.280 --> 00:08:13.280 Will it work? 00:08:13.280 --> 00:08:14.280 Yes. 00:08:14.280 --> 00:08:18.000 WAN up local switching, open static WEP, will it work? 00:08:18.000 --> 00:08:19.000 Yes. 00:08:19.000 --> 00:08:20.000 Yes. 00:08:20.000 --> 00:08:21.000 Yes. 00:08:21.880 --> 00:08:27.120 So here you can go through the different scenarios on if something's up, what happens? 00:08:27.120 --> 00:08:32.040 If my wide area network is up, do I still have this service? 00:08:32.040 --> 00:08:35.600 Let's take a look at where no starts to happen. 00:08:35.600 --> 00:08:41.240 If I have a rogue intrusion detection, yes, yes for WAN. 00:08:41.240 --> 00:08:43.080 If the WAN is up, it works. 00:08:43.080 --> 00:08:48.960 But if the WAN is down, it no longer works. 00:08:48.960 --> 00:08:50.520 So this is important. 00:08:51.040 --> 00:08:57.520 I need you to go through this and understand when FlexConnect is going to be up and when 00:08:57.520 --> 00:09:00.280 FlexConnect is going to be down. 00:09:00.280 --> 00:09:09.080 Some of the stuff I would like you to focus on is the security settings for sure, opportunistic 00:09:09.080 --> 00:09:11.280 fast ROAM right here. 00:09:11.280 --> 00:09:16.840 This is something I would definitely want you to know that when the wireless LAN is 00:09:16.840 --> 00:09:20.680 up, that we can do fast ROAM. 00:09:20.680 --> 00:09:25.560 When the WAN is down, we cannot. 00:09:25.560 --> 00:09:29.080 Important to know, okay? 00:09:29.080 --> 00:09:32.680 Mesh, Mesh LSC, not applicable. 00:09:32.680 --> 00:09:34.880 What did we say FlexConnect didn't work with? 00:09:34.880 --> 00:09:35.880 Mesh. 00:09:35.880 --> 00:09:41.000 It's right there, unless we're working in bridge mode and we'll talk about that in a 00:09:41.000 --> 00:09:42.000 second. 00:09:42.000 --> 00:09:47.680 TLS support, trust sec, identity, pre-shared key, yes, yes, yes, as long as you're on version 00:09:47.680 --> 00:09:49.680 8.5. 00:09:49.680 --> 00:09:52.680 Triple A enforced policy, yes. 00:09:52.680 --> 00:09:57.720 Triple A enforced policy and quota management, yes, including FlexBridge. 00:09:57.720 --> 00:10:03.400 And no, if the WAN is up but local switching and authentication. 00:10:03.400 --> 00:10:04.400 That does not work. 00:10:04.400 --> 00:10:06.840 That's something I would like you to know as well. 00:10:06.840 --> 00:10:09.320 And then no, if the wireless LAN is down. 00:10:09.320 --> 00:10:12.280 Triple A enforced policy and quota management. 00:10:12.280 --> 00:10:17.240 There is a lot here that you will get a ton of questions on FlexConnect. 00:10:17.240 --> 00:10:20.720 I would like you to remember the ones I specifically mentioned. 00:10:20.720 --> 00:10:26.000 And I would like you to go through that at least once and read through it. 00:10:26.000 --> 00:10:30.080 And kind of go through it in your head and understand what's happening. 00:10:30.080 --> 00:10:34.800 Okay, the WAN is down, the WAN area network is down. 00:10:34.800 --> 00:10:37.560 I cannot reach my wireless LAN controller. 00:10:37.560 --> 00:10:39.960 What does that mean for FlexConnect mode? 00:10:39.960 --> 00:10:42.680 What can I do and what can't I do? 00:10:42.680 --> 00:10:45.000 Very important. 00:10:45.000 --> 00:10:49.440 This understanding that we went through will get you through a lot of those questions. 00:10:49.440 --> 00:10:52.560 There's going to be a few on that matrix I showed you. 00:10:52.560 --> 00:10:55.680 Please spend some time there. 00:10:55.680 --> 00:10:58.680 So what about this bridge or mesh mode? 00:10:58.680 --> 00:11:04.600 Now bridge or mesh mode is dedicated point-to-point or multipoint between networks. 00:11:04.600 --> 00:11:05.960 This is to extend a network. 00:11:05.960 --> 00:11:14.320 So let's say I have an AP here and I don't – I need to extend out to here. 00:11:14.320 --> 00:11:15.760 And this is a building. 00:11:15.760 --> 00:11:16.760 This is like a shop. 00:11:16.760 --> 00:11:22.080 Let's say this is my shop and this is the actual office. 00:11:22.080 --> 00:11:25.760 And this is 50 feet. 00:11:25.760 --> 00:11:27.240 And I'm using a Yagi antenna. 00:11:27.240 --> 00:11:30.040 We're going to throw all sorts of scenarios in here. 00:11:30.040 --> 00:11:31.040 Boom, boom. 00:11:31.040 --> 00:11:32.840 That's a mesh network really. 00:11:32.840 --> 00:11:34.000 So that's what we're talking about. 00:11:34.000 --> 00:11:35.920 We're bridging that area. 00:11:35.920 --> 00:11:37.600 You know, switches used to be called bridges. 00:11:37.600 --> 00:11:40.440 That's because they connected two things together. 00:11:40.440 --> 00:11:42.560 Now we're connecting two things together using wireless. 00:11:42.560 --> 00:11:45.080 That's a bridge or mesh connection. 00:11:45.080 --> 00:11:52.800 Remember mesh mode – FlexConnect will not work on that unless we introduce Flex plus 00:11:52.800 --> 00:11:55.160 bridge. 00:11:55.160 --> 00:12:00.800 These are Flex features assigned to mesh APs. 00:12:00.800 --> 00:12:03.080 So this is a different thing. 00:12:03.080 --> 00:12:05.720 I got a website for you here as well. 00:12:06.520 --> 00:12:07.520 So let's go ahead and take a look. 00:12:07.520 --> 00:12:12.360 I'm going to go to my demo environment, drop off the screen for a second. 00:12:12.360 --> 00:12:14.440 And this is the second site I'm going to give you. 00:12:14.440 --> 00:12:18.880 This will be in the supplemental learning assets. 00:12:18.880 --> 00:12:21.560 Please at the very least look through them. 00:12:21.560 --> 00:12:29.160 Now FlexConnect and – FlexConnect and bridge mode work together. 00:12:29.160 --> 00:12:33.440 Bridge mode allows functionality across mesh APs. 00:12:33.440 --> 00:12:34.440 Look at this part. 00:12:34.440 --> 00:12:35.440 This is what I want you to remember. 00:12:35.440 --> 00:12:42.560 Currently, a control and provisioning wireless access CAPWAP AP can be configured and operate 00:12:42.560 --> 00:12:45.800 in two different modes, FlexConnect and bridge. 00:12:45.800 --> 00:12:50.000 Limitations are FlexConnect and mesh modes are incompatible. 00:12:50.000 --> 00:12:51.240 I told you that. 00:12:51.240 --> 00:12:52.760 We talked about that. 00:12:52.760 --> 00:12:58.280 So what's the solution if I have a mesh environment and I still want FlexConnect mode? 00:12:58.280 --> 00:13:03.640 I still want APs to work somewhat when they can't reach the wireless LAN controller. 00:13:03.840 --> 00:13:08.760 Well, what I got to do is do FlexConnect plus bridge. 00:13:08.760 --> 00:13:10.760 That's the configuration I need. 00:13:10.760 --> 00:13:11.760 Okay. 00:13:11.760 --> 00:13:16.720 Now, there are additional limitations here. 00:13:16.720 --> 00:13:22.640 I want you to read through this document up to just right here. 00:13:22.640 --> 00:13:26.760 It's not a big document. 00:13:26.760 --> 00:13:31.240 This will give you an idea of what works and what doesn't work when you're in FlexConnect 00:13:31.240 --> 00:13:35.560 mode and bridge mode because it changes a little bit. 00:13:35.560 --> 00:13:42.000 Remember, we're kind of stuck on that AP's VLAN that we're mesh mode with, and that kind 00:13:42.000 --> 00:13:46.280 of changes the dynamics of what we can do, what we can switch locally. 00:13:46.280 --> 00:13:51.000 Because remember, FlexConnect mode is about switching locally. 00:13:51.000 --> 00:13:57.160 So if I'm switching locally, I have to make sure that I understand that when I'm going 00:13:57.160 --> 00:14:02.200 to that AP over that mesh interface, I'm going to be stuck there. 00:14:02.200 --> 00:14:06.000 So this is a little different from just FlexConnect mode. 00:14:06.000 --> 00:14:11.120 Adding bridge is going to put a little tiny bit more limitations on what you can do. 00:14:11.120 --> 00:14:12.120 All right. 00:14:12.120 --> 00:14:22.400 Let's go back to the slides. 00:14:22.400 --> 00:14:24.200 Network management modes. 00:14:24.200 --> 00:14:25.200 Okay. 00:14:25.240 --> 00:14:32.360 Now, these are the ones that actually do management things, modes that provide utilities for us 00:14:32.360 --> 00:14:33.360 as administrators. 00:14:33.360 --> 00:14:36.200 First, we have monitor. 00:14:36.200 --> 00:14:41.160 Monitor is basically in a passive mode where you're just going to be looking at traffic 00:14:41.160 --> 00:14:42.920 or looking at what's going on. 00:14:42.920 --> 00:14:44.080 There's a rogue detector. 00:14:44.080 --> 00:14:45.480 Rogue detector is pretty fun. 00:14:45.480 --> 00:14:51.560 It allows to specifically analyze traffic to ensure that you don't have any devices 00:14:51.560 --> 00:14:53.720 that shouldn't be on your network. 00:14:53.720 --> 00:14:55.520 We have SEConnect and Sniffer. 00:14:55.520 --> 00:14:57.760 A Sniffer just sniffs the different traffic. 00:14:57.760 --> 00:14:59.680 And we're going to dive into these in detail. 00:14:59.680 --> 00:15:02.880 First, we're going to dive into monitor mode. 00:15:02.880 --> 00:15:08.360 Now monitor mode, when you put an AP in monitor mode, we're not transmitting at all. 00:15:08.360 --> 00:15:11.080 We are simply a receiver. 00:15:11.080 --> 00:15:15.360 I misspelled that. 00:15:15.360 --> 00:15:16.360 Receiver. 00:15:16.360 --> 00:15:20.040 We're going to take traffic in and we're going to look at that traffic. 00:15:20.040 --> 00:15:21.280 Why would we do this? 00:15:21.280 --> 00:15:25.800 We would use this for intrusion detection, rogue access point. 00:15:25.800 --> 00:15:29.960 A lot of people call this a rogue monitoring too. 00:15:29.960 --> 00:15:34.640 If let's say you're on the exam and someone's asking about rogue devices, what would you 00:15:34.640 --> 00:15:36.320 use to monitor them? 00:15:36.320 --> 00:15:41.400 And you're looking for rogue device monitoring and you don't see it, monitor mode is 100% 00:15:41.400 --> 00:15:42.400 accurate. 00:15:42.400 --> 00:15:44.120 It's something I would choose there. 00:15:44.120 --> 00:15:49.920 It is something that is used to monitor your wireless network to ensure that certain types 00:15:49.920 --> 00:15:53.480 of traffic aren't being introduced into your environment. 00:15:53.480 --> 00:15:56.960 Rogue access points and things like that being some of them. 00:15:56.960 --> 00:15:58.760 Location-based services actually use it. 00:15:58.760 --> 00:16:04.880 So if you ever had your device on and it says, oh, please turn on your wireless device for 00:16:04.880 --> 00:16:09.640 a more accurate reading for where you are, this is 100% true. 00:16:09.640 --> 00:16:17.240 They use those APs as kind of a pinpoint to see where you are in the environment. 00:16:17.240 --> 00:16:20.800 This is like your phone and things like that. 00:16:20.800 --> 00:16:22.960 Let's go on to our rogue detector. 00:16:22.960 --> 00:16:25.200 Now this is dedicated rogue detector. 00:16:25.200 --> 00:16:28.560 Remember a monitor, it's basically kind of like a monitor. 00:16:28.560 --> 00:16:31.680 This is for wired and wireless environments. 00:16:31.680 --> 00:16:37.520 The MAC address comparison of what we're expected to have on our network versus what's there. 00:16:37.520 --> 00:16:42.060 AP can still broadcast SSIDs. 00:16:42.060 --> 00:16:46.640 So although a rogue detector is a monitor, it can also move traffic. 00:16:46.640 --> 00:16:52.520 So that's the difference between a monitor and a rogue detector. 00:16:52.520 --> 00:16:54.800 It can still serve clients. 00:16:54.800 --> 00:16:57.760 And all the wireless connections that are made to it are still valid. 00:16:57.760 --> 00:17:02.760 They can move data as long as the AP is configured for it. 00:17:02.760 --> 00:17:08.200 Rogue detectors have become more and more ingrained into our enterprise wireless APs. 00:17:08.200 --> 00:17:09.680 We see it all the time. 00:17:09.680 --> 00:17:15.600 If you use Meraki, the rogue detectors on every single AP you have. 00:17:15.640 --> 00:17:19.800 In this day and age, with everybody pulling out pineapples, if you don't know what a pineapple 00:17:19.800 --> 00:17:21.800 is, look it up. 00:17:21.800 --> 00:17:25.520 Wireless pineapples are used to create rogue access points. 00:17:25.520 --> 00:17:32.400 So this is a very important part of your security infrastructure, being able to detect rogue 00:17:32.400 --> 00:17:37.080 devices in your environment, especially if they're trying to hand out SSIDs and pretend 00:17:37.080 --> 00:17:39.920 to be a part of your enterprise infrastructure. 00:17:39.920 --> 00:17:40.920 Very important. 00:17:40.920 --> 00:17:44.200 SC Connect, this is dedicated connection for clean air. 00:17:44.200 --> 00:17:47.640 So what we're looking at is we're looking at the different frequencies that are in my 00:17:47.640 --> 00:17:48.640 air. 00:17:48.640 --> 00:17:57.080 And I'm trying to make sure that in the spectra analysis, that I have clean channels to work 00:17:57.080 --> 00:17:58.080 with. 00:17:58.080 --> 00:18:03.520 The channels I'm planning to use, the frequencies that are going in the air all around me, I'm 00:18:03.520 --> 00:18:06.760 using channels that do not have a lot of interference. 00:18:06.760 --> 00:18:13.960 So I'm dedicated to trying to create an environment where my data moves cleanly through the air 00:18:14.720 --> 00:18:22.400 and is not running into a bunch of interference, there's no problems or competing signals in 00:18:22.400 --> 00:18:23.400 my area. 00:18:23.400 --> 00:18:26.560 There are several ways we can use this. 00:18:26.560 --> 00:18:30.720 Cisco Spectrum Expert, MetaGeek, we could use that. 00:18:30.720 --> 00:18:36.000 What we're doing is we're using the AP's antenna, let's say that that's the antenna there. 00:18:36.000 --> 00:18:41.920 We're using the AP's antenna to receive the different frequencies and then pipe that into 00:18:41.920 --> 00:18:48.000 one of these applications so then we can look at what is actually going on in the air 00:18:48.000 --> 00:18:49.680 around us. 00:18:49.680 --> 00:18:54.400 And we really are trying to find interference, that's what it's all about. 00:18:54.400 --> 00:19:00.200 Our next mode, our administrative mode we use, and our last one we're going to be discussing 00:19:00.200 --> 00:19:01.760 here is a sniffer. 00:19:01.760 --> 00:19:06.080 A sniffer is dedicated to sniffing traffic. 00:19:06.080 --> 00:19:10.840 Wireshark is absolutely a sniffer, a snorter. 00:19:10.840 --> 00:19:18.920 These different OmniPeak, these are all things that you've used, well maybe you haven't used, 00:19:18.920 --> 00:19:23.920 that you've heard of being used to sniff traffic and that's all we're talking about. 00:19:23.920 --> 00:19:25.880 But AP's can do it as well. 00:19:25.880 --> 00:19:31.660 AP's can be used, just like we were in the last, to take all those signals but this time 00:19:31.660 --> 00:19:36.960 we're not looking for interference, we're looking to take that information, feed it 00:19:36.960 --> 00:19:43.920 down into Wireshark or OmniPeak and take a look at what traffic's being generated. 00:19:43.920 --> 00:19:48.680 This is a great troubleshooting tool, it can be also used in the security sense a hundred 00:19:48.680 --> 00:19:50.080 million percent. 00:19:50.080 --> 00:19:55.840 But what we're trying to do here is analyze what's the traffic going on, what's causing 00:19:55.840 --> 00:20:03.120 traffic disconnect, client disconnects, what's going on in our environment that may be causing 00:20:03.120 --> 00:20:04.120 issues. 00:20:04.720 --> 00:20:08.800 All right, so those are the different modes you're going to see in your environment. 00:20:08.800 --> 00:20:14.240 Remember those two websites I gave you, it'll be in your supplemental learning assets. 00:20:14.240 --> 00:20:21.300 Please, please, please at least read through one time, if not two, to kind of get an idea. 00:20:21.300 --> 00:20:27.640 And if you're ever looking at it and going, well that doesn't make sense, remember that 00:20:27.640 --> 00:20:36.680 like FlexConnect cannot connect back to the wireless LAN controller, there's limited connectivity, 00:20:36.680 --> 00:20:37.680 there's limited functionality. 00:20:37.680 --> 00:20:43.440 If I can't connect back to the wireless LAN controller, there's a lot I can't do, such 00:20:43.440 --> 00:20:48.640 as I cannot authenticate a new user if I can't get back to the wireless LAN controller. 00:20:48.640 --> 00:20:54.240 And then remember this as well when we talk about FlexConnect with BridgeMode, we're taking 00:20:54.240 --> 00:21:01.040 that even further when we have a point-to-point connection, AP-to-AP, then that traffic goes 00:21:01.040 --> 00:21:02.360 back to a wireless LAN controller. 00:21:02.360 --> 00:21:07.480 I just added a level of complexity, so even less features are going to work there. 00:21:07.480 --> 00:21:10.500 All right, that's all I had for this one. 00:21:10.500 --> 00:21:13.200 We have a couple more of these to go. 00:21:13.200 --> 00:21:14.200 Thank you for your time. 00:21:14.200 --> 00:21:15.200 I'll talk to you soon.