WEBVTT 1 00:00.000 --> 00:04.420 Let's be in a picture of what we're talking about. Let's say that we have a 2 00:04.420 --> 00:05.000 pair 3 00:05.000 --> 00:10.600 of distribution switches which connect to the network core and we have these 4 00:10.600 --> 00:16.040 connecting down to several access closets. So we've got a set of closets each 5 00:16.040 --> 00:21.920 with a switch here ahead and switch and we connect them all out. So maybe this 6 00:21.920 --> 00:27.720 is a stack of switches at each location. So what we're going to do for SDA is 7 00:27.720 --> 00:32.400 we are going to go ahead and build a fabric here. This fabric is actually going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:27.720 --> 00:32.400 we are going to go ahead and build a fabric here. This fabric is actually going 8 00:32.400 --> 00:37.410 to include the distribution switches here in the middle in the underlay. 9 00:37.410 --> 00:37.680 Meaning 10 00:37.680 --> 00:41.200 that these switches here are going to form the overlay with one another by 11 00:41.200 --> 00:46.280 forming the X-land tunnels to one another and that's going to allow them to 12 00:46.280 --> 00:50.160 communicate at layer two. In fact, let's go ahead and draw that just with a 13 00:50.160 --> 00:55.640 different color so we can kind of see the difference here. And then we have 14 00:55.640 --> 01:02.000 SVI's that are going to exist on each one of these switches and that allows us WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:55.640 --> 01:02.000 SVI's that are going to exist on each one of these switches and that allows us 15 01:02.000 --> 01:08.840 to let's say extend VLAN 10 across all of these switches this way and VLAN 20 16 01:08.840 --> 01:14.440 will say is this set of SVI's and notice that they each have an SVI for each 17 01:14.440 --> 01:20.960 one of the VLANs. So VLANs 10 and 20 here, 10 and 20 here, 10 and 20 here. This 18 01:20.960 --> 01:21.040 is 19 01:21.040 --> 01:25.320 the concept known as any cast gateways and we're going to talk about that in 20 01:25.320 --> 01:32.520 more detail later on. Now what we have is we have a set of three fabric edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 01:25.320 --> 01:32.520 more detail later on. Now what we have is we have a set of three fabric edge 21 01:32.520 --> 01:32.960 nodes 22 01:32.960 --> 01:39.000 in this environment. These fabric edge nodes are going to bring traffic in and 23 01:39.000 --> 01:45.800 forward them to each other in order to allow network traffic to propagate. Now 24 01:45.800 --> 01:46.120 if 25 01:46.120 --> 01:52.800 we have a lot of east-west traffic meaning traffic within this access switch 26 01:52.800 --> 01:58.360 domain, VLANs 10 and 20 in our case, then we're going to see a lot of use case 27 01:58.360 --> 02:06.040 with the VX lands. And so a packet let's say comes in here on VLAN 10 and we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 01:58.360 --> 02:06.040 with the VX lands. And so a packet let's say comes in here on VLAN 10 and we 28 02:06.040 --> 02:06.280 are 29 02:06.280 --> 02:10.680 destined for a host that's connected to VLAN 10 but over here on this other 30 02:10.680 --> 02:15.000 switch. What's going to happen? Well as we alluded to earlier we're going to 31 02:15.000 --> 02:15.200 have 32 02:15.200 --> 02:22.560 a control plane node that is part of the network and this control plane 33 02:22.560 --> 02:27.800 node could be maybe an ISR that is hanging off of let's say the distribution 34 02:27.800 --> 02:32.680 switch here. And so this switch, this fabric edge node is going to reach out WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 02:27.800 --> 02:32.680 switch here. And so this switch, this fabric edge node is going to reach out 35 02:32.680 --> 02:33.000 and 36 02:33.000 --> 02:39.880 say hey I need that destination because I'm trying to get to whatever IP 37 02:39.880 --> 02:43.640 addresses out here. This host that I'm trying to communicate with and I don't 38 02:43.640 --> 02:48.080 know which of these other fabric edge nodes afford it to. And so we provide 39 02:48.080 --> 02:52.520 the answer here we're going to send it to let's say switch two in this case and 40 02:52.520 --> 02:57.280 that is the role of the control plane node. And so we encapsulate it in that VX 41 02:57.280 --> 03:02.480 land tunnel and it goes from VLAN 10 on this side through the fabric across WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 02:57.280 --> 03:02.480 land tunnel and it goes from VLAN 10 on this side through the fabric across 42 03:02.480 --> 03:02.920 those 43 03:02.920 --> 03:07.600 layer three boundaries but in a layer two tunnel and it's going to exit out of 44 03:07.600 --> 03:13.720 switch two here and it's going to find its destination. So that is the role of 45 03:13.720 --> 03:17.730 the control plane node and we see the fabric edge nodes that work here. 46 03:17.730 --> 03:18.240 Meanwhile 47 03:18.240 --> 03:22.360 what happens if we are destined for something else? Now we're talking about 48 03:22.360 --> 03:27.760 north or something outside of the SDA fabric. And now we're talking about 49 03:27.760 --> 03:33.160 needing to get to the rest of the network and so this would be the border WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 03:27.760 --> 03:33.160 needing to get to the rest of the network and so this would be the border 50 03:33.160 --> 03:36.600 nodes. Now we could make these distributions which is the border nodes and 51 03:36.600 --> 03:41.800 fact if we're connecting to the network core then we probably wouldn't want to 52 03:41.800 --> 03:45.480 do that. But for now let's say that we've just got a border node here maybe it 53 03:45.480 --> 03:45.760 's a 54 03:45.760 --> 03:51.880 network stack of switches maybe it's a router either way we have this border 55 03:51.880 --> 03:57.040 node. Usually we'll have a pair for redundancy so I'll just say border nodes 56 03:57.040 --> 04:02.040 here. And we've got connectivity through the underlight to the rest of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 03:57.040 --> 04:02.040 here. And we've got connectivity through the underlight to the rest of the 57 04:02.040 --> 04:08.760 fabric and now this is going to connect us out to the network core. So we see 58 04:08.760 --> 04:13.600 that the fabric is within the scope of a single architecture. Maybe this is a 59 04:13.600 --> 04:19.320 single site or a campus network that has a lot of access layer closets but it 60 04:19.320 --> 04:24.160 really is encompassing this domain not the core and not everything that exists 61 04:24.160 --> 04:28.800 that side of the core such as the WAN block and the internet block and all of 62 04:28.800 --> 04:32.640 the other network blocks that are part of our hierarchical network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 04:28.800 --> 04:32.640 the other network blocks that are part of our hierarchical network 63 04:32.640 --> 04:38.240 architecture. Well if a packet comes in and it's destined for something that 64 04:38.240 --> 04:42.760 doesn't exist here in the SDA fabric while the control plane node is not going 65 04:42.760 --> 04:48.200 to know then where that is. And so we're going to use the border node as this 66 04:48.200 --> 04:48.520 sort 67 04:48.520 --> 04:55.630 of default route in our SDA fabric and so we're going to forward that traffic 68 04:55.630 --> 04:56.400 to 69 04:56.400 --> 05:01.400 the border nodes and allow the border nodes to send it out to the non SDA WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 04:56.400 --> 05:01.400 the border nodes and allow the border nodes to send it out to the non SDA 70 05:01.400 --> 05:01.840 domain 71 05:01.840 --> 05:07.160 and we hope that we get to the destination there. So meanwhile all of this is 72 05:07.160 --> 05:12.560 being managed as we've said by our set of controllers over here. We're going to 73 05:12.560 --> 05:17.520 have catalyst center. We're going to have ice integration. That would be the 74 05:17.520 --> 05:23.120 identity services engine and this is going to be pushing our configurations and 75 05:23.120 --> 05:30.160 pushing our policy out to the fabric to let everybody know how all of this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 05:23.120 --> 05:30.160 pushing our policy out to the fabric to let everybody know how all of this 76 05:30.160 --> 05:35.520 traffic is meant to be forwarded and we as the admins we don't actually have to 77 05:35.520 --> 05:40.200 log into all of these devices to make it happen. Instead we simply log into 78 05:40.200 --> 05:46.510 catalyst center in order to add our own definitions for these configurations 79 05:46.510 --> 05:46.680 and 80 05:46.680 --> 05:52.800 policies. So that is a high-level view of how all this comes together. We see 81 05:52.800 --> 05:57.080 that this diagram gets pretty busy when we're talking about all of the 82 05:57.080 --> 06:02.040 different components of an SDA fabric but we also see how all of these node WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 05:57.080 --> 06:02.040 different components of an SDA fabric but we also see how all of these node 83 06:02.040 --> 06:06.320 types come together and how the controllers come together in order to make end 84 06:06.320 --> 06:09.320 and traffic flow happen.