WEBVTT 1 00:00.000 --> 00:06.400 Well, this is a software defined access fabric, meaning that it's encompassing 2 00:06.400 --> 00:07.440 our access layer. 3 00:07.440 --> 00:10.900 Well, our access layer is more than just wired clients. 4 00:10.900 --> 00:15.760 We happen to have a lot of wireless devices out there these days, and because 5 00:15.760 --> 00:16.100 all of our 6 00:16.100 --> 00:19.900 access points reside at the access layer, it's going to have to be a part of 7 00:19.900 --> 00:21.160 our architecture. 8 00:21.160 --> 00:23.420 Now what we're going to find is that we have two different ways of building 9 00:23.420 --> 00:23.940 wireless. 10 00:23.940 --> 00:27.280 We can integrate it into the fabric, which is what we're going to talk about in 11 00:27.280 --> 00:27.600 this 12 00:27.600 --> 00:31.010 video, and then we can also say, you know what, we just want to deploy a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:27.600 --> 00:31.010 video, and then we can also say, you know what, we just want to deploy a 13 00:31.010 --> 00:32.160 wireless solution 14 00:32.160 --> 00:35.760 independent of the fabric itself. 15 00:35.760 --> 00:41.880 And basically just treat the fabric like it's a network path at that point, 16 00:41.880 --> 00:43.080 just a mechanism 17 00:43.080 --> 00:47.280 for communicating between access point and wireless LAN controller. 18 00:47.280 --> 00:49.680 And so we'll talk about that in the next video. 19 00:49.680 --> 00:54.240 So now let's just focus on how can we integrate our access points and wireless 20 00:54.240 --> 00:55.360 LAN controllers 21 00:55.360 --> 00:57.840 into an SDA fabric? 22 00:57.840 --> 01:02.840 Well as we can imagine, just like with a traditional wireless architecture, our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 00:57.840 --> 01:02.840 Well as we can imagine, just like with a traditional wireless architecture, our 23 01:02.840 --> 01:04.000 access points are 24 01:04.000 --> 01:09.960 going to connect into our access layer switches, and they'll receive power over 25 01:09.960 --> 01:11.000 ethernet. 26 01:11.000 --> 01:14.830 From these connections, remember these fabric edge nodes are just catalyst nine 27 01:14.830 --> 01:15.560 case switches 28 01:15.560 --> 01:16.760 for the most part. 29 01:16.760 --> 01:21.560 We might have some more legacy 3650 3850s in there as well, but especially in 30 01:21.560 --> 01:22.160 the modern 31 01:22.160 --> 01:26.120 network, lots and lots of catalyst nine case. 32 01:26.120 --> 01:30.260 So it's the same switches we'd be deploying into our access layer, even if we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:26.120 --> 01:30.260 So it's the same switches we'd be deploying into our access layer, even if we 33 01:30.260 --> 01:30.760 weren't 34 01:30.760 --> 01:32.720 deploying SDA. 35 01:32.720 --> 01:37.230 So again, access points connecting, getting power over ethernet, all of these 36 01:37.230 --> 01:37.920 things. 37 01:37.920 --> 01:42.970 Well if we're going to integrate it into the fabric, these become known as 38 01:42.970 --> 01:44.000 fabric access 39 01:44.000 --> 01:45.840 points. 40 01:45.840 --> 01:49.450 This is largely a terminology concept, but again, we do have the option of 41 01:49.450 --> 01:50.000 building 42 01:50.000 --> 01:52.520 wireless independent of the fabric. 43 01:52.520 --> 01:57.520 And so it is an important distinction that if we see a conversation around a 44 01:57.520 --> 01:58.520 fabric access 45 01:58.520 --> 02:03.400 point, if we see it listed in the wireless LAN controller as being fabric WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:58.520 --> 02:03.400 point, if we see it listed in the wireless LAN controller as being fabric 46 02:03.400 --> 02:04.520 enabled, then 47 02:04.520 --> 02:08.840 that's an access point that is fully integrated with the fabric. 48 02:08.840 --> 02:14.580 So we're using the fabric word in the same way that we have fabric edge nodes 49 02:14.580 --> 02:15.440 and fabric 50 02:15.440 --> 02:16.440 border nodes. 51 02:16.440 --> 02:21.360 This word fabric is being used very intentionally here. 52 02:21.360 --> 02:25.840 Now let's think through things from an access point architecture perspective. 53 02:25.840 --> 02:31.040 We know that we need a wireless LAN controller somewhere in the network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:25.840 --> 02:31.040 We know that we need a wireless LAN controller somewhere in the network. 54 02:31.040 --> 02:34.920 And that is for the sake of performing lightweight access point operations. 55 02:34.920 --> 02:41.800 And we need to build capwap tunnels to the wireless LAN controller. 56 02:41.800 --> 02:43.320 So how do we get to that point? 57 02:43.320 --> 02:47.470 Well, the access point is going to connect and it's going to receive an IP 58 02:47.470 --> 02:48.280 address via 59 02:48.280 --> 02:50.280 DHCP. 60 02:50.280 --> 02:53.000 This is a benefit to lightweight access points. 61 02:53.000 --> 02:55.400 We don't need to worry about what IP address they have. 62 02:55.400 --> 02:58.760 We don't need to worry about static IP addresses in most situations. 63 02:58.760 --> 03:00.880 So we leverage DHCP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:58.760 --> 03:00.880 So we leverage DHCP. 64 03:00.880 --> 03:07.520 Well now this access point is simply an endpoint identifier to the upstream 65 03:07.520 --> 03:09.640 fabric edge node. 66 03:09.640 --> 03:12.320 And so it's actually going to do the registration. 67 03:12.320 --> 03:15.720 So we've got our control plane node up here. 68 03:15.720 --> 03:18.120 And we register just like we talked about. 69 03:18.120 --> 03:22.840 We register the access point and both of these are going to do that 70 03:22.840 --> 03:24.760 registration for the access 71 03:24.760 --> 03:30.170 point as if it's any other device connecting to the switch, a laptop or a PC or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 03:24.760 --> 03:30.170 point as if it's any other device connecting to the switch, a laptop or a PC or 72 03:30.170 --> 03:30.920 anything 73 03:30.920 --> 03:33.120 along those lines. 74 03:33.120 --> 03:37.420 Meanwhile the access point is going to learn about the wireless LAN controller 75 03:37.420 --> 03:38.400 the traditional 76 03:38.400 --> 03:42.160 way that we learn about the wireless LAN controllers. 77 03:42.160 --> 03:47.780 And usually that involves DHCP option 43 where the DHCP itself delivers the 78 03:47.780 --> 03:49.000 wireless LAN controller 79 03:49.000 --> 03:51.440 IP address to the access point. 80 03:51.440 --> 03:55.780 Either way the access point now knows where the wireless LAN controller is and 81 03:55.780 --> 03:56.240 therefore 82 03:56.240 --> 03:59.600 it can now build a tunnel towards the wireless LAN controller. 83 03:59.600 --> 04:02.800 It can send traffic to this connection. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 03:59.600 --> 04:02.800 It can send traffic to this connection. 84 04:02.800 --> 04:07.510 But here's the question, where is the wireless LAN controller and how do we 85 04:07.510 --> 04:08.600 attach it to the 86 04:08.600 --> 04:09.600 fabric? 87 04:09.600 --> 04:14.760 Well, we are going to attach it through none other than a fabric edge node. 88 04:14.760 --> 04:17.040 So here we have a third fabric edge node. 89 04:17.040 --> 04:19.960 It's another Nexus or catalyst 9k. 90 04:19.960 --> 04:24.910 And so we are connecting in and now we can refer to this as a fabric wireless 91 04:24.910 --> 04:26.360 LAN controller. 92 04:26.360 --> 04:30.460 So in the same way that if an access point is integrated with the fabric, we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 04:26.360 --> 04:30.460 So in the same way that if an access point is integrated with the fabric, we're 93 04:30.460 --> 04:30.880 going 94 04:30.880 --> 04:34.160 to do the same thing with the wireless LAN controller here. 95 04:34.160 --> 04:39.400 And so it will also get registered by the way to the control plane node. 96 04:39.400 --> 04:44.140 So all of these devices at this point are simply endpoint identifiers mapped to 97 04:44.140 --> 04:44.440 the 98 04:44.440 --> 04:48.280 R-locks of the individual fabric edge nodes. 99 04:48.280 --> 04:52.120 And so these are simply endpoints that can communicate with one another. 100 04:52.120 --> 04:55.830 At this point it's going to get a little more integrated but when everything is 101 04:55.830 --> 04:56.440 first coming 102 04:56.440 --> 05:00.800 online they're all just devices that need to communicate with one another. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 04:56.440 --> 05:00.800 online they're all just devices that need to communicate with one another. 103 05:00.800 --> 05:05.600 And so at this point we can form a cab web tunnel. 104 05:05.600 --> 05:11.280 And so we're going to use the actual overlay type of communication. 105 05:11.280 --> 05:15.710 So again if there's a laptop here that's connected to the same switch, I'm also 106 05:15.710 --> 05:16.760 communicating 107 05:16.760 --> 05:21.910 through VX LAN tunnels to get across to another fabric edge node or maybe down 108 05:21.910 --> 05:22.560 here. 109 05:22.560 --> 05:24.480 And so we can think of it the same way. 110 05:24.480 --> 05:29.290 I'm simply extending communications through this fabric edge node destined for 111 05:29.290 --> 05:30.200 this wireless WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 05:29.290 --> 05:30.200 this wireless 112 05:30.200 --> 05:31.520 LAN controller. 113 05:31.520 --> 05:35.440 So I've got to find out where the wireless LAN controller is as an edge node. 114 05:35.440 --> 05:40.810 I send my map request, it gets forwarded down to the appropriate edge node, I 115 05:40.810 --> 05:41.520 get a map 116 05:41.520 --> 05:44.960 reply back and now I know where to send it. 117 05:44.960 --> 05:51.370 Ultimately I'm sending this traffic in the VX LAN tunnel that communicates with 118 05:51.370 --> 05:52.200 that fabric 119 05:52.200 --> 05:55.970 edge node that will connect me to the wireless LAN controller and we build a 120 05:55.970 --> 05:56.880 cap-wap tunnel 121 05:56.880 --> 05:58.200 this way. 122 05:58.200 --> 06:00.320 Now notice what I just said. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 122 05:58.200 --> 06:00.320 Now notice what I just said. 123 06:00.320 --> 06:05.370 We are encapsulating this traffic inside of VX LAN tunnel and the traffic we're 124 06:05.370 --> 06:06.440 encapsulating 125 06:06.440 --> 06:10.240 is a cap-wap tunnel. 126 06:10.240 --> 06:15.080 These are two different tunneling mechanisms operating at the same time. 127 06:15.080 --> 06:22.040 Yes, my cap-wap is inside of a VX LAN tunnel which has MTU implications. 128 06:22.040 --> 06:27.120 We need to increase the MTU already by 50 bytes for the VX LAN like we said and 129 06:27.120 --> 06:27.520 now 130 06:27.520 --> 06:31.780 if we're performing wireless across this we're going to need to increase it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 06:27.520 --> 06:31.780 if we're performing wireless across this we're going to need to increase it 131 06:31.780 --> 06:32.600 again because 132 06:32.600 --> 06:35.280 of the double encapsulation. 133 06:35.280 --> 06:40.520 Now here is just cap-wap going from the access point to the 9K. 134 06:40.520 --> 06:46.870 The 9K then has cap-wap inside of VX LAN going to the other 9K and then we just 135 06:46.870 --> 06:47.680 deliver 136 06:47.680 --> 06:52.680 pure cap-wap communications down to the wireless LAN controller. 137 06:52.680 --> 06:57.100 So the two end devices, the wireless LAN controller and the AP, they don't see 138 06:57.100 --> 06:58.640 the VX LAN, they 139 06:58.640 --> 07:03.800 are just seeing the cap-wap traffic that was carried across the fabric. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 139 06:58.640 --> 07:03.800 are just seeing the cap-wap traffic that was carried across the fabric. 140 07:03.800 --> 07:05.880 At this point everything is fairly normal. 141 07:05.880 --> 07:09.520 We're just using SDA as a transport mechanism. 142 07:09.520 --> 07:16.200 But now here is where we can activate the fabric portions of this architecture. 143 07:16.200 --> 07:20.080 The wireless LAN controller is going to see this access point come online. 144 07:20.080 --> 07:26.030 It's going to register this access point and it is going to be configured with 145 07:26.030 --> 07:26.840 catalyst 146 07:26.840 --> 07:28.320 center integration. 147 07:28.320 --> 07:33.840 So we let it know about catalyst center and therefore it becomes aware of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 147 07:28.320 --> 07:33.840 So we let it know about catalyst center and therefore it becomes aware of the 148 07:33.840 --> 07:34.600 control 149 07:34.600 --> 07:36.080 plane node. 150 07:36.080 --> 07:39.850 So first of all the access point is going to register to the wireless LAN 151 07:39.850 --> 07:40.760 controller. 152 07:40.760 --> 07:46.710 The wireless LAN controller is then going to send a query about this access 153 07:46.710 --> 07:47.480 point to 154 07:47.480 --> 07:49.360 the control plane node. 155 07:49.360 --> 07:57.240 The purpose of this is to find out is the AP fabric attached or not. 156 07:57.240 --> 08:01.730 Because if it is fabric attached then we want to let the fabric become aware WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 156 07:57.240 --> 08:01.730 Because if it is fabric attached then we want to let the fabric become aware 157 08:01.730 --> 08:02.560 that there's 158 08:02.560 --> 08:06.920 this end point out here that happens to be an AP. 159 08:06.920 --> 08:11.990 If the control plane node has a registration for that particular IP address 160 08:11.990 --> 08:12.600 then we're 161 08:12.600 --> 08:17.240 going to know that okay this access point is part of the SDA fabric and it didn 162 08:17.240 --> 08:17.680 't come 163 08:17.680 --> 08:21.800 through a border node or some indirect path or anything like that. 164 08:21.800 --> 08:25.810 If we get a response back from the control plane node saying that yes this is 165 08:25.810 --> 08:26.280 indeed 166 08:26.280 --> 08:32.000 fabric attached then I'm going to register as the wireless LAN controller. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 166 08:26.280 --> 08:32.000 fabric attached then I'm going to register as the wireless LAN controller. 167 08:32.000 --> 08:38.960 I'm going to register to the control plane node to say that I want to register 168 08:38.960 --> 08:39.600 the MAC 169 08:39.600 --> 08:42.320 address for the AP. 170 08:42.320 --> 08:47.970 Keep in mind the AP was registered from an IP perspective because we deal with 171 08:47.970 --> 08:49.040 IP addresses 172 08:49.040 --> 08:53.360 when we're talking about registering devices to the control plane node. 173 08:53.360 --> 08:58.440 So we registered the IP address but now I want to register the MAC address. 174 08:58.440 --> 09:06.620 I'm essentially claiming ownership of the access point and I'm alerting the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 174 08:58.440 --> 09:06.620 I'm essentially claiming ownership of the access point and I'm alerting the 175 09:06.620 --> 09:07.600 control 176 09:07.600 --> 09:14.170 plane node to say that IP address specifically that endpoint identifier is an 177 09:14.170 --> 09:15.400 access point. 178 09:15.400 --> 09:21.570 So now the control plane node is aware that that particular EID that was 179 09:21.570 --> 09:22.840 registered is 180 09:22.840 --> 09:27.160 actually an access point and it should be treated a little bit different. 181 09:27.160 --> 09:30.280 So here's the fascinating fourth part about all of this. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 09:27.160 --> 09:30.280 So here's the fascinating fourth part about all of this. 182 09:30.280 --> 09:35.290 If we say for over here the control plane node is actually going to alert the 183 09:35.290 --> 09:35.840 fabric 184 09:35.840 --> 09:43.180 edge node about the fact that the endpoint identifier is an access point and 185 09:43.180 --> 09:44.000 then the 186 09:44.000 --> 09:50.560 fabric edge node is going to form a VXLAN tunnel to the access point. 187 09:50.560 --> 09:54.240 We're actually forming a VXLAN tunnel to the AP. 188 09:54.240 --> 10:00.010 This is pretty interesting because we know that we've got VXLAN inside of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 188 09:54.240 --> 10:00.010 This is pretty interesting because we know that we've got VXLAN inside of the 189 10:00.010 --> 10:00.640 fabric 190 10:00.640 --> 10:05.420 and all of the tunnels connecting all of the different edge nodes but now on 191 10:05.420 --> 10:06.200 top of saying 192 10:06.200 --> 10:12.490 that we're running capwap inside of all of this I'm now actually going to run 193 10:12.490 --> 10:12.800 not just 194 10:12.800 --> 10:19.360 capwap but I'm also going to extend a VXLAN tunnel to the access point. 195 10:19.360 --> 10:22.730 Meaning that the access point sends some traffic outside of the tunnel 196 10:22.730 --> 10:24.480 specifically the capwap 197 10:24.480 --> 10:30.660 communication still goes outside of the VXLAN tunnel but my wireless devices my WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 197 10:24.480 --> 10:30.660 communication still goes outside of the VXLAN tunnel but my wireless devices my 198 10:30.660 --> 10:31.480 wireless 199 10:31.480 --> 10:36.630 stations, these wireless stations as traffic comes to the access point it is 200 10:36.630 --> 10:37.240 going to be 201 10:37.240 --> 10:42.120 sent out the VXLAN tunnel to the fabric. 202 10:42.120 --> 10:47.120 Now that is a major distinction because if we think about lightweight access 203 10:47.120 --> 10:48.280 points usually 204 10:48.280 --> 10:53.110 we're sending wireless station traffic into the capwap tunnel which means we 205 10:53.110 --> 10:53.760 have to go 206 10:53.760 --> 10:56.760 all the way down to the wireless LAN controller. 207 10:56.760 --> 10:59.320 We don't have to do that with SDA. 208 10:59.320 --> 11:09.860 Our station traffic basically our data plane does not use capwap in this top WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 208 10:59.320 --> 11:09.860 Our station traffic basically our data plane does not use capwap in this top 209 11:09.860 --> 11:11.640 ology, in this 210 11:11.640 --> 11:12.640 architecture. 211 11:12.640 --> 11:17.680 When we're talking about fabric attached access points we are going to build VX 212 11:17.680 --> 11:19.040 LAN tunnels 213 11:19.040 --> 11:24.220 to our upstream devices and we're going to send our wireless station traffic 214 11:24.220 --> 11:24.880 through 215 11:24.880 --> 11:28.760 those VXLAN tunnels directly to the fabric edge node. 216 11:28.760 --> 11:34.020 Meaning that when a wireless station packet shows up, so here's our wireless WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 216 11:28.760 --> 11:34.020 Meaning that when a wireless station packet shows up, so here's our wireless 217 11:34.020 --> 11:34.680 frame it 218 11:34.680 --> 11:36.800 just showed up here. 219 11:36.800 --> 11:38.840 I'm going to treat it as if it was a wired frame. 220 11:38.840 --> 11:42.490 I'm going to check my cache, I'm going to figure out which fabric edge node to 221 11:42.490 --> 11:42.840 send 222 11:42.840 --> 11:47.680 it to and I'm going to encapsulate it into VXLAN and send it directly to my 223 11:47.680 --> 11:48.680 next switch. 224 11:48.680 --> 11:52.800 So I'm not actually sending it to the wireless LAN controller anymore. 225 11:52.800 --> 11:56.200 Now am I still running capwap and mention that I'm still sending some amount of 226 11:56.200 --> 11:56.680 traffic 227 11:56.680 --> 12:00.040 via capwap and the answer is yes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 227 11:56.680 --> 12:00.040 via capwap and the answer is yes. 228 12:00.040 --> 12:04.680 Control plane traffic still gets sent via capwap to the wireless LAN controller 229 12:04.680 --> 12:04.720 . 230 12:04.720 --> 12:09.240 This is how we can do radio resource management such as channel allocation. 231 12:09.240 --> 12:13.680 We can do a lot of registering of information such as registering of wireless 232 12:13.680 --> 12:14.440 stations which 233 12:14.440 --> 12:16.360 helps with roaming. 234 12:16.360 --> 12:20.870 That's all very important and continues to ride via the capwap tunnels for 235 12:20.870 --> 12:21.800 wireless control 236 12:21.800 --> 12:22.800 plane. 237 12:22.800 --> 12:26.350 But the data plane traffic itself not going to be sent to the wireless LAN 238 12:26.350 --> 12:27.280 controller via 239 12:27.280 --> 12:29.000 capwap. 240 12:29.000 --> 12:33.650 Now one last point I'd like to note is the fact that our wireless stations, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 240 12:29.000 --> 12:33.650 Now one last point I'd like to note is the fact that our wireless stations, 241 12:33.650 --> 12:34.480 they do still 242 12:34.480 --> 12:39.210 get registered via that control plane to the wireless LAN controllers and again 243 12:39.210 --> 12:39.720 this is 244 12:39.720 --> 12:43.040 important for the sake of roaming. 245 12:43.040 --> 12:47.730 So if a wireless station roams from one access point connected to one fabric 246 12:47.730 --> 12:48.600 edge node and 247 12:48.600 --> 12:52.560 now all of a sudden I'm on another access point which is on a different fabric 248 12:52.560 --> 12:52.920 edge 249 12:52.920 --> 12:58.920 node we need to update the fabric to the fact that that wireless station has ro 250 12:58.920 --> 12:59.400 amed. 251 12:59.400 --> 13:02.700 Well when we roamed to the new AP it's going to perform that station WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 251 12:59.400 --> 13:02.700 Well when we roamed to the new AP it's going to perform that station 252 13:02.700 --> 13:03.880 registration message 253 13:03.880 --> 13:08.120 to the wireless LAN controller to alert it to the fact that it has this new 254 13:08.120 --> 13:08.840 station and 255 13:08.840 --> 13:12.060 the wireless LAN control is going to say wait a second that was already on a 256 13:12.060 --> 13:12.640 different 257 13:12.640 --> 13:18.220 access point this is now roamed we need to update everyone about the new 258 13:18.220 --> 13:19.360 location. 259 13:19.360 --> 13:26.160 As such it sends an update to the control plane node. 260 13:26.160 --> 13:30.290 So that the control plane node can update its EID to our lock mapping and it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 260 13:26.160 --> 13:30.290 So that the control plane node can update its EID to our lock mapping and it 261 13:30.290 --> 13:30.760 can make 262 13:30.760 --> 13:35.500 sure that it's sending traffic to the appropriate fabric edge node to 263 13:35.500 --> 13:37.140 ultimately land on the 264 13:37.140 --> 13:42.020 correct access point to get sent down to where the wireless station now resides 265 13:42.020 --> 13:42.020 . 266 13:42.020 --> 13:52.020 [BLANK_AUDIO]