WEBVTT 1 00:00.000 --> 00:05.280 Alright, this challenge is meant to walk us through the concepts of the border 2 00:05.280 --> 00:06.000 nodes, 3 00:06.000 --> 00:09.880 as well as our fabric access points and fabric wirelessly in controllers. 4 00:09.880 --> 00:13.700 So let's just make sure that we know how these all attach to one another, and 5 00:13.700 --> 00:14.460 also just sort 6 00:14.460 --> 00:18.840 of solidify our concepts around how an SDA fabric operates. 7 00:18.840 --> 00:23.560 So point number one here, or challenge number one, a new endpoint, endpoint one 8 00:23.560 --> 00:23.980 here, has 9 00:23.980 --> 00:26.100 just come online via switch one. 10 00:26.100 --> 00:28.920 How does the fabric become aware of the endpoint? 11 00:28.920 --> 00:31.000 So remember this concept of onboarding. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:28.920 --> 00:31.000 So remember this concept of onboarding. 12 00:31.000 --> 00:36.740 When a new host shows up, the fabric edge node here, so edge node is switch one 13 00:36.740 --> 00:36.960 in this 14 00:36.960 --> 00:41.160 case, is going to perform a registration to the control plane node. 15 00:41.160 --> 00:44.680 So we're going to use that map register message, but ultimately we're just 16 00:44.680 --> 00:45.840 simply registering 17 00:45.840 --> 00:47.840 this via LISP. 18 00:47.840 --> 00:53.300 So LISP is the control plane, the protocol that we're using here, and then when 19 00:53.300 --> 00:53.680 we get 20 00:53.680 --> 00:59.980 into fabric operation, we know that, like let's say here, n.5 cents a packet 21 00:59.980 --> 01:00.680 towards WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 21 00:59.980 --> 01:00.680 towards 22 01:00.680 --> 01:06.000 n.1, switch five can go out to find out where n.1 is. 23 01:06.000 --> 01:10.400 But in order for us to go out and ask where it is, we need that EID to our lock 24 01:10.400 --> 01:11.280 mapping. 25 01:11.280 --> 01:15.840 So that's the endpoint identifier, that slash 32 route to the host. 26 01:15.840 --> 01:19.480 And then the our lock would be essentially saying switch one here. 27 01:19.480 --> 01:26.120 And now we have mapped our endpoint to a particular fabric edge node. 28 01:26.120 --> 01:29.760 Number two, what type of border node is switch two and for that matter, which 29 01:29.760 --> 01:30.480 one is switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:29.760 --> 01:30.480 one is switch 30 01:30.480 --> 01:31.480 three. 31 01:31.480 --> 01:34.940 So when we're looking at what's connected behind the border nodes here, we see 32 01:34.940 --> 01:35.160 that 33 01:35.160 --> 01:40.300 we've got in both cases external networks, networks that are not part of the S 34 01:40.300 --> 01:41.240 DA fabric. 35 01:41.240 --> 01:46.930 So since we are connecting to our other internal routes off of switch two, that 36 01:46.930 --> 01:47.600 makes this 37 01:47.600 --> 01:52.360 an internal border node and switch three is connecting out to the internet, 38 01:52.360 --> 01:53.080 that makes 39 01:53.080 --> 01:57.400 this an external border node. 40 01:57.400 --> 02:01.630 And question number three is going to drill into the differences, where asks, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:57.400 --> 02:01.630 And question number three is going to drill into the differences, where asks, 41 02:01.630 --> 02:02.320 do the border 42 02:02.320 --> 02:06.170 nodes register any endpoint identifiers with the control plane node in the same 43 02:06.170 --> 02:06.560 way that 44 02:06.560 --> 02:08.400 we do over here? 45 02:08.400 --> 02:12.200 And the answer is the internal one does. 46 02:12.200 --> 02:16.240 We are going to register all of the routes that we're learning here. 47 02:16.240 --> 02:19.250 Remember, we're sharing routes back and forth with the rest of the network, and 48 02:19.250 --> 02:19.640 we're going 49 02:19.640 --> 02:21.680 to register those with the fabric. 50 02:21.680 --> 02:24.280 The external does no such registration. 51 02:24.280 --> 02:28.620 We are not registering anything because we are being treated by like a default 52 02:28.620 --> 02:29.240 route. 53 02:29.240 --> 02:31.930 And so if we don't know where to send something, we're just going to send it to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:29.240 --> 02:31.930 And so if we don't know where to send something, we're just going to send it to 54 02:31.930 --> 02:32.480 the nearest 55 02:32.480 --> 02:35.480 external border node. 56 02:35.480 --> 02:38.690 Question number four, where would a fabric access point and for that matter, a 57 02:38.690 --> 02:39.120 fabric 58 02:39.120 --> 02:41.400 wireless LAN controller be physically connected? 59 02:41.400 --> 02:46.240 Well, fabric access points are going to connect to fabric edge nodes. 60 02:46.240 --> 02:49.160 And so we could see access points connecting to both of these. 61 02:49.160 --> 02:54.110 But then our fabric wireless LAN controller is also going to be connected here 62 02:54.110 --> 02:54.440 off of 63 02:54.440 --> 02:56.240 a fabric edge node. 64 02:56.240 --> 03:01.970 And so remember, a wireless LAN controller in a fabric integrated environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 02:56.240 --> 03:01.970 And so remember, a wireless LAN controller in a fabric integrated environment 65 03:01.970 --> 03:02.640 is going 66 03:02.640 --> 03:05.840 to be connected via fabric edge node. 67 03:05.840 --> 03:09.190 What tunnel type is being used between the two, we are going to see that we're 68 03:09.190 --> 03:10.040 still forming 69 03:10.040 --> 03:13.880 capwap tunnels for the sake of the control plane. 70 03:13.880 --> 03:16.840 Just remember that data plane does not use capwap. 71 03:16.840 --> 03:21.760 It's going to form a separate VX LAN tunnel to the upstream fabric edge node. 72 03:21.760 --> 03:25.390 And lastly, if we're using wireless over the top, where does the wireless LAN 73 03:25.390 --> 03:26.040 controller 74 03:26.040 --> 03:27.040 attach? 75 03:27.040 --> 03:32.440 In this case, over the top, wireless LAN controller would be connected here on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 03:27.040 --> 03:32.440 In this case, over the top, wireless LAN controller would be connected here on 76 03:32.440 --> 03:33.520 the other side 77 03:33.520 --> 03:35.920 of the internal border node. 78 03:35.920 --> 03:39.480 So let's make sure that we have down this whole process of what gets registered 79 03:39.480 --> 03:39.760 when 80 03:39.760 --> 03:41.160 things get registered. 81 03:41.160 --> 03:44.450 And from a wireless perspective, where are access points and wireless LAN 82 03:44.450 --> 03:45.040 controllers 83 03:45.040 --> 03:47.440 attached depending on the architecture type? 84 03:47.440 --> 03:49.850 I hope this has been informative for you, and I'd like to thank you for viewing 85 03:49.850 --> 03:50.080 .