WEBVTT 1 00:00.000 --> 00:05.320 Now remember, Cisco has two different types of wireless controllers. 2 00:05.320 --> 00:08.160 AeroS would be the legacy option. 3 00:08.160 --> 00:12.790 We don't really see these being sold proactively anymore and yet we still have 4 00:12.790 --> 00:13.600 a lot of them 5 00:13.600 --> 00:17.020 out in production, which is why Cisco does still want us to understand how to 6 00:17.020 --> 00:17.480 perform 7 00:17.480 --> 00:21.200 AeroS configuration and we'll take a look at that later on. 8 00:21.200 --> 00:25.750 For now, we're going to focus on the new platform, which is Cisco's iOS XE 9 00:25.750 --> 00:26.440 platform 10 00:26.440 --> 00:30.840 built on the Catalyst 9800 series. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:26.440 --> 00:30.840 built on the Catalyst 9800 series. 11 00:30.840 --> 00:34.000 Yeah, Catalyst used to just mean a bunch of switches. 12 00:34.000 --> 00:36.200 Now it means pretty much everything to Cisco. 13 00:36.200 --> 00:41.010 We have wireless LAN controllers, we have access points, and so the wireless 14 00:41.010 --> 00:42.240 LAN controllers, 15 00:42.240 --> 00:48.360 the Catalyst 9800s, but then we have 9100 access points. 16 00:48.360 --> 00:52.500 And then we have Catalyst 8,000s, which are routers and all kinds of things 17 00:52.500 --> 00:53.040 that fall 18 00:53.040 --> 00:55.480 under the Catalyst umbrella these days. 19 00:55.480 --> 00:58.520 But the point is that they're all running iOS XE. 20 00:58.520 --> 01:03.200 AeroS, if we ever went to the CLI, required almost knowing a completely WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:58.520 --> 01:03.200 AeroS, if we ever went to the CLI, required almost knowing a completely 21 01:03.200 --> 01:04.640 different language 22 01:04.640 --> 01:10.720 and whole way of coding or configuring rather, are wireless LAN controllers. 23 01:10.720 --> 01:14.240 Well, iOS XE is going to feel like it's a switch. 24 01:14.240 --> 01:18.370 We get onto the CLI, we can perform configuration commands, and furthermore, 25 01:18.370 --> 01:19.560 architecturally, 26 01:19.560 --> 01:21.520 it's like a switch as well. 27 01:21.520 --> 01:25.810 This becomes clear when we talk about the interfaces that we need to configure 28 01:25.810 --> 01:26.240 on our 29 01:26.240 --> 01:27.840 9800. 30 01:27.840 --> 01:33.560 So we're looking at our 9800, and in my lab environment, I have a 9800-L. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 01:27.840 --> 01:33.560 So we're looking at our 9800, and in my lab environment, I have a 9800-L. 31 01:33.560 --> 01:35.880 Cisco has quite a few different options. 32 01:35.880 --> 01:42.080 For the 9800s, this is intended for very small or lab type of environments. 33 01:42.080 --> 01:46.400 And then they also have the -40 and the -80 referring to throughput here, 40 34 01:46.400 --> 01:47.440 gig and 80 35 01:47.440 --> 01:48.440 gig. 36 01:48.440 --> 01:52.880 And then they also have a -CL, which is a cloud software based controller. 37 01:52.880 --> 01:58.130 But again, for demonstration purposes in my lab, I'm going to be using a 9800-L 38 01:58.130 --> 01:58.400 . 39 01:58.400 --> 02:01.000 Again, architecturally, all of these are the same. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 01:58.400 --> 02:01.000 Again, architecturally, all of these are the same. 40 02:01.000 --> 02:05.860 So it doesn't really matter outside of the number of access points that I want 41 02:05.860 --> 02:06.240 to be 42 02:06.240 --> 02:09.880 able to support as well as the overall throughput of the system. 43 02:09.880 --> 02:14.880 So this 9800 is going to have physical interfaces on the front. 44 02:14.880 --> 02:20.680 And these physical interfaces are going to be able to connect into my switching 45 02:20.680 --> 02:21.240 layer 46 02:21.240 --> 02:23.120 to infrastructure. 47 02:23.120 --> 02:25.280 Now I can connect a couple of these. 48 02:25.280 --> 02:27.440 I could connect all four of these. 49 02:27.440 --> 02:31.160 And then I can also decide if I want to configure port channels. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 02:27.440 --> 02:31.160 And then I can also decide if I want to configure port channels. 50 02:31.160 --> 02:35.370 So this is interesting because in the old ARAOS, it was either all bundled or 51 02:35.370 --> 02:36.360 no bundle. 52 02:36.360 --> 02:41.690 But with our 9800s, because this is basically an iOSXZ switch under the hood, I 53 02:41.690 --> 02:42.280 could create 54 02:42.280 --> 02:45.760 multiple port channels if I so desire, but for the most part, we're just going 55 02:45.760 --> 02:46.320 to bundle 56 02:46.320 --> 02:47.840 all of these together. 57 02:47.840 --> 02:50.280 This should be a trunked connection. 58 02:50.280 --> 02:55.950 And it should contain the VLAN list for all of the wireless VLANs that we want 59 02:55.950 --> 02:57.280 to support. 60 02:57.280 --> 03:01.160 So every time we talk about that concept of the point of presence for our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 02:57.280 --> 03:01.160 So every time we talk about that concept of the point of presence for our 61 03:01.160 --> 03:02.360 wireless stations, 62 03:02.360 --> 03:07.210 remember our wireless stations are out here communicating with access points 63 03:07.210 --> 03:07.800 that could 64 03:07.800 --> 03:11.380 be part of the layer two domain, keep in mind that this could be across a 65 03:11.380 --> 03:12.520 routed boundary. 66 03:12.520 --> 03:18.200 But either way, we recall that these capwap tunnels are going to be formed 67 03:18.200 --> 03:18.920 between the 68 03:18.920 --> 03:22.000 access point and the controller. 69 03:22.000 --> 03:27.720 And so the client gets sort of poredled or warped through this tunnel. 70 03:27.720 --> 03:30.880 And then once it gets to the other side, it gets dropped back onto the network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 03:27.720 --> 03:30.880 And then once it gets to the other side, it gets dropped back onto the network. 71 03:30.880 --> 03:36.730 So this client, if it's on VLAN 10, is actually talking about the VLAN list 72 03:36.730 --> 03:38.000 here that is going 73 03:38.000 --> 03:42.040 to allow me to be dropped off under the layer two network where the wireless 74 03:42.040 --> 03:42.960 LAN controller 75 03:42.960 --> 03:43.960 is. 76 03:43.960 --> 03:50.190 Now, in the next question we have to ask is what interface is terminating this 77 03:50.190 --> 03:51.280 capwap tunnel? 78 03:51.280 --> 03:52.280 This is important. 79 03:52.280 --> 03:55.940 This is going to be a huge part of our access point discovery, because the 80 03:55.940 --> 03:56.640 access point 81 03:56.640 --> 04:02.720 is going to come out and try to find the IP address that it was told, either by WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 81 03:56.640 --> 04:02.720 is going to come out and try to find the IP address that it was told, either by 82 04:02.720 --> 04:03.200 DHCP 83 04:03.200 --> 04:07.380 or DNS, or possibly by layer two broadcast, which is how we'll do it in our lab 84 04:07.380 --> 04:08.400 environment. 85 04:08.400 --> 04:11.960 But it needs to be able to discover this interface. 86 04:11.960 --> 04:19.060 Well this interface in an 9800 is going to be an SVI, just a standard VLAN 87 04:19.060 --> 04:20.400 interface. 88 04:20.400 --> 04:24.800 Again, architecturally, it's like a switch under the hood and running iOS XE. 89 04:24.800 --> 04:29.480 So I can configure an SVI, and by the way, I can do all of this via CLI or via 90 04:29.480 --> 04:30.600 the graphical WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 04:29.480 --> 04:30.600 the graphical 91 04:30.600 --> 04:32.160 user interface. 92 04:32.160 --> 04:37.600 With iOS, most admins would use the graphical user interface, certainly if you 93 04:37.600 --> 04:38.360 were going 94 04:38.360 --> 04:43.040 to go for your wireless CCIE, you'd really want to know the CLI commands. 95 04:43.040 --> 04:44.920 But I'll leave that there. 96 04:44.920 --> 04:49.680 But with iOS XE, we can very comfortably use either one. 97 04:49.680 --> 04:53.460 And because it's using APIs on the back end, we can actually switch back and 98 04:53.460 --> 04:53.960 forth. 99 04:53.960 --> 04:57.470 I could use the CLI one day, and then the graphical user interface the next day 100 04:57.470 --> 04:57.800 if I 101 04:57.800 --> 05:02.960 so desire, because it's all running the same commands under the hood. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 04:57.800 --> 05:02.960 so desire, because it's all running the same commands under the hood. 102 05:02.960 --> 05:05.680 So what we're going to do here is we're going to start to build out our 103 05:05.680 --> 05:07.080 wireless configuration. 104 05:07.080 --> 05:12.560 Again, when I look at my lab environment, I do have this 9800-L. 105 05:12.560 --> 05:14.920 This is going to be across the house for me. 106 05:14.920 --> 05:17.080 It's actually my bedroom closet. 107 05:17.080 --> 05:18.560 That's where I store my lab. 108 05:18.560 --> 05:24.000 So the wireless LAN controller, the 9800-L, is just going to connect through my 109 05:24.000 --> 05:24.960 home network, 110 05:24.960 --> 05:26.280 which is a layer two network. 111 05:26.280 --> 05:31.920 I don't have anything fancy going here, just a couple of switches to get to my WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 05:26.280 --> 05:31.920 I don't have anything fancy going here, just a couple of switches to get to my 112 05:31.920 --> 05:32.040 office, 113 05:32.040 --> 05:34.440 which is where the access point is. 114 05:34.440 --> 05:37.040 If I can draw an access point, there we go. 115 05:37.040 --> 05:43.030 So the AP is hanging out here in my office, and then we'll test the wireless 116 05:43.030 --> 05:44.480 configuration. 117 05:44.480 --> 05:49.760 Eventually, we get to the point that I could attach my laptop to the wireless. 118 05:49.760 --> 05:56.040 So we're going to start simply by making sure that the wireless LAN controller 119 05:56.040 --> 05:56.640 here has 120 05:56.640 --> 06:05.560 an SVI and that the access point is able to form that capwap tunnel. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 120 05:56.640 --> 06:05.560 an SVI and that the access point is able to form that capwap tunnel. 121 06:05.560 --> 06:08.500 We want to make sure that we can discover the access point and get it connected 122 06:08.500 --> 06:08.800 to the 123 06:08.800 --> 06:11.160 wireless LAN controller. 124 06:11.160 --> 06:14.360 It might also be worth noting that wireless LAN controllers have a couple of 125 06:14.360 --> 06:15.000 out-of-band 126 06:15.000 --> 06:16.160 interfaces. 127 06:16.160 --> 06:19.980 The RP or redundancy port is going to allow me to connect to another wireless 128 06:19.980 --> 06:21.040 LAN controller. 129 06:21.040 --> 06:24.820 I don't have that in my environment, but in the real world, we very likely have 130 06:24.820 --> 06:25.400 another 131 06:25.400 --> 06:28.970 wireless LAN controller there because, as we've said, if the wireless LAN 132 06:28.970 --> 06:29.800 controller goes 133 06:29.800 --> 06:32.000 down, I lose my wireless network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 133 06:29.800 --> 06:32.000 down, I lose my wireless network. 134 06:32.000 --> 06:36.560 So having a redundant wireless LAN controller, a hot spare, is going to be 135 06:36.560 --> 06:37.480 heavily advised 136 06:37.480 --> 06:38.480 in production. 137 06:38.480 --> 06:42.280 And again, in most situations, that's exactly what we're going to see. 138 06:42.280 --> 06:47.140 We also have an SP known as a service port, and this is for the sake of 139 06:47.140 --> 06:48.440 management. 140 06:48.440 --> 06:53.650 It's my out-of-band management port, and it's going to also connect into the 141 06:53.650 --> 06:54.120 same layer 142 06:54.120 --> 06:55.600 two environment. 143 06:55.600 --> 07:02.900 And so this is going to be my 192.168.50/24 subnet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 143 06:55.600 --> 07:02.900 And so this is going to be my 192.168.50/24 subnet. 144 07:02.900 --> 07:08.790 We are going to find that we've got a .12 IP address that I used to log into 145 07:08.790 --> 07:09.980 the graphical 146 07:09.980 --> 07:14.020 user interface and possibly do some CLI commands that way as well. 147 07:14.020 --> 07:18.980 But this SVI is going to need to also have an IP address in the same subnet. 148 07:18.980 --> 07:20.980 We'll use .13. 149 07:20.980 --> 07:27.030 So we want to configure this .13 address, and we'll go ahead and put this on V 150 07:27.030 --> 07:27.620 LAN 10 151 07:27.620 --> 07:31.780 as an SVI so that the access point can discover it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 07:27.620 --> 07:31.780 as an SVI so that the access point can discover it. 152 07:31.780 --> 07:35.700 Now just as a little bit of a demonstration, you can see here I've got this 153 07:35.700 --> 07:36.620 access point. 154 07:36.620 --> 07:40.700 This is a .9136 relatively new at the time of this video. 155 07:40.700 --> 07:44.540 Still a couple of years old, Cisco continues to come out with new access points 156 07:44.540 --> 07:44.700 . 157 07:44.700 --> 07:51.470 This happens to be a Wi-Fi 6 enabled access point with 6 GHz, so technically Wi 158 07:51.470 --> 07:53.060 -Fi 6E. 159 07:53.060 --> 07:58.220 But either way, this has got 2.4, dual 5 gig and a 6 gigahertz radio. 160 07:58.220 --> 08:01.500 So this has four different radios in it on top of the RF ASIC. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 160 07:58.220 --> 08:01.500 So this has four different radios in it on top of the RF ASIC. 161 08:01.500 --> 08:03.380 It's a wonderful access point. 162 08:03.380 --> 08:07.300 I've got it plugged in via the network with power over ethernet. 163 08:07.300 --> 08:11.980 And what we can find here is that this light is cycling colors. 164 08:11.980 --> 08:15.420 When we see it cycling colors, it means it's looking for the wireless LAN 165 08:15.420 --> 08:16.260 controller. 166 08:16.260 --> 08:20.340 Now interestingly at this point, we actually have the access point connected to 167 08:20.340 --> 08:20.660 the same 168 08:20.660 --> 08:22.860 layer to network as the wireless LAN controller. 169 08:22.860 --> 08:27.060 You might say, well why is it still looking for the wireless LAN controller? 170 08:27.060 --> 08:29.460 It should be able to find it via broadcast. 171 08:29.460 --> 08:32.340 And that is the plan for it to discover it via broadcast. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 08:29.460 --> 08:32.340 And that is the plan for it to discover it via broadcast. 172 08:32.340 --> 08:36.500 However, it can't discover just a wireless LAN controller. 173 08:36.500 --> 08:39.260 Again, it needs to discover that SVI. 174 08:39.260 --> 08:42.770 And the fact that we don't have an SVI means that we can't actually terminate 175 08:42.770 --> 08:44.020 access points 176 08:44.020 --> 08:46.100 and cap-wep tunnel specifically. 177 08:46.100 --> 08:51.270 The SP, the management interface is not going to be looking to terminate access 178 08:51.270 --> 08:52.820 point connections. 179 08:52.820 --> 08:56.420 Even though technically speaking, it is seeing the broadcast messages from the 180 08:56.420 --> 08:57.100 access point 181 08:57.100 --> 09:00.460 on that SP because it's all part of the same layer to domain. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 08:57.100 --> 09:00.460 on that SP because it's all part of the same layer to domain. 182 09:00.460 --> 09:03.840 It's not going to respond to it to say, hey, here I am, form a cap-wep tunnel 183 09:03.840 --> 09:04.820 with me. 184 09:04.820 --> 09:07.220 We have to configure something that is in band.