WEBVTT 1 00:00.000 --> 00:02.740 All right, back into the lab we go. 2 00:02.740 --> 00:04.400 We are going to configure a trunk. 3 00:04.400 --> 00:08.500 We're going to leverage DTP to create a dynamic trunk on one side and we're 4 00:08.500 --> 00:09.140 going to create 5 00:09.140 --> 00:12.880 a router on the stick on the other side of switch one. 6 00:12.880 --> 00:16.510 In fact, let's go ahead and start by taking a look at the topology to make sure 7 00:16.510 --> 00:16.920 that we 8 00:16.920 --> 00:19.840 know what it is we're setting out to do. 9 00:19.840 --> 00:24.560 So when we look at the goals for this lab challenge, the first task is to 10 00:24.560 --> 00:25.560 create a trunk 11 00:25.560 --> 00:27.560 between switch one and switch two using DTP. 12 00:27.560 --> 00:32.920 So we're going to use DTP in here and we're told to allow switch one to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:27.560 --> 00:32.920 So we're going to use DTP in here and we're told to allow switch one to 13 00:32.920 --> 00:34.840 initiate a connection 14 00:34.840 --> 00:38.920 and switch two to more or less accept it to wait for the initiation. 15 00:38.920 --> 00:43.610 That means that I'm going to have to configure these for switch mode dynamic, 16 00:43.610 --> 00:44.400 but then also 17 00:44.400 --> 00:50.020 specifically switch one is allowed to be in that desirable state and switch two 18 00:50.020 --> 00:50.520 's gig 19 00:50.520 --> 00:53.880 zero zero interface will have to be in the auto state. 20 00:53.880 --> 00:58.250 We should see that this forms a trunk and we can confirm that with commands 21 00:58.250 --> 00:58.880 like show 22 00:58.880 --> 01:02.280 interface trunk or show interface switch port. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 00:58.880 --> 01:02.280 interface trunk or show interface switch port. 23 01:02.280 --> 01:04.080 So we'll take a look at that. 24 01:04.080 --> 01:08.280 Meanwhile, then from there, we're told that we're going to create a static 25 01:08.280 --> 01:08.960 trunk up to 26 01:08.960 --> 01:09.960 the router. 27 01:09.960 --> 01:13.440 Now this involves two different types of commands because on a switch we're 28 01:13.440 --> 01:14.280 going to use switch 29 01:14.280 --> 01:19.000 port commands and on the router we're going to use sub interface commands. 30 01:19.000 --> 01:23.450 And so what this looks like is that since also the router doesn't run DTP, I'm 31 01:23.450 --> 01:23.760 going 32 01:23.760 --> 01:28.240 to just place this into a static trunk operation. 33 01:28.240 --> 01:32.980 So switch port mode trunk and then on gig zero zero, I'm going to create two WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:28.240 --> 01:32.980 So switch port mode trunk and then on gig zero zero, I'm going to create two 34 01:32.980 --> 01:34.120 sub interfaces. 35 01:34.120 --> 01:42.520 I'm going to create gig zero slash zero dot 10 and gig zero slash zero dot 20. 36 01:42.520 --> 01:46.170 And then from there, we're going to want to create some layer three interfaces 37 01:46.170 --> 01:46.480 and we'll 38 01:46.480 --> 01:51.040 come back to the diagram later to sort of see what it is we're trying to 39 01:51.040 --> 01:52.120 accomplish. 40 01:52.120 --> 01:55.800 So let's flip over to our configuration now and let's start with our switch 41 01:55.800 --> 01:56.840 configurations. 42 01:56.840 --> 02:02.430 So we're going to get on to switch one here and I'm going to do a config T and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 01:56.840 --> 02:02.430 So we're going to get on to switch one here and I'm going to do a config T and 43 02:02.430 --> 02:02.880 get on 44 02:02.880 --> 02:05.440 to interface gig zero zero. 45 02:05.440 --> 02:10.510 I'm going to do switch port not switch port mode trunk, but switch port mode 46 02:10.510 --> 02:10.840 and do a 47 02:10.840 --> 02:13.920 question mark, we see we've got the option for dynamic. 48 02:13.920 --> 02:17.460 So I'm going to do that dynamic and then we see auto and desirable are our 49 02:17.460 --> 02:18.080 options. 50 02:18.080 --> 02:22.240 So I'm going to set this to desirable on this side. 51 02:22.240 --> 02:26.160 And the funny thing is is that switch to now we have to configure this. 52 02:26.160 --> 02:29.720 Oops, I lost my connection to switch to. 53 02:29.720 --> 02:37.040 And when I do a show, run interface on gig zero slash zero, we're going to see WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:29.720 --> 02:37.040 And when I do a show, run interface on gig zero slash zero, we're going to see 54 02:37.040 --> 02:37.600 that there 55 02:37.600 --> 02:41.630 isn't any default configuration there that's listed, but we're actually running 56 02:41.630 --> 02:42.240 in auto. 57 02:42.240 --> 02:46.880 If I do a show interface gig zero slash zero switch port, this is a very 58 02:46.880 --> 02:48.120 powerful command 59 02:48.120 --> 02:51.240 to see all the layer two configurations are happening. 60 02:51.240 --> 02:54.720 And we notice the administrative mode is dynamic auto. 61 02:54.720 --> 03:02.550 So when I do a config T interface gig zero zero and then switch port mode WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 02:54.720 --> 03:02.550 So when I do a config T interface gig zero zero and then switch port mode 62 03:02.550 --> 03:04.600 dynamic auto. 63 03:04.600 --> 03:09.830 Now I can take a look at show, run interface gig zero slash zero and there's 64 03:09.830 --> 03:10.920 nothing there. 65 03:10.920 --> 03:12.000 Why is there nothing there? 66 03:12.000 --> 03:16.460 Well, because that is the default configuration, I didn't change the default 67 03:16.460 --> 03:17.360 configuration 68 03:17.360 --> 03:22.480 and instead we were just going to continue running in the mode in which we were 69 03:22.480 --> 03:23.320 running. 70 03:23.320 --> 03:26.740 So next question, are we running this in a trunk? 71 03:26.740 --> 03:31.760 So I can do a show interface trunk to find out if we're running in a trunk. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 03:26.740 --> 03:31.760 So I can do a show interface trunk to find out if we're running in a trunk. 72 03:31.760 --> 03:35.070 And we do see something pretty interesting here that first of all we are 73 03:35.070 --> 03:35.680 running in a 74 03:35.680 --> 03:39.080 trunk, but notice the encapsulation that we're using. 75 03:39.080 --> 03:42.000 We're actually using that ISL that we talked about. 76 03:42.000 --> 03:44.480 Now in modern switches, this won't happen. 77 03:44.480 --> 03:47.760 We don't need to worry about this on catalyst nine case. 78 03:47.760 --> 03:52.120 But if I come over to switch one and say show interface trunk, we're also going 79 03:52.120 --> 03:52.520 to see 80 03:52.520 --> 03:56.400 that we're running as a negotiated ISL connection. 81 03:56.400 --> 03:57.960 So what's the solution to this? 82 03:57.960 --> 04:02.580 Well, I simply need to get onto my interface here and use a switch port encaps WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 03:57.960 --> 04:02.580 Well, I simply need to get onto my interface here and use a switch port encaps 83 04:02.580 --> 04:03.560 ulation switch 84 04:03.560 --> 04:09.890 port trunk encapsulation and then specify, because I do a question mark here, 85 04:09.890 --> 04:11.160 we'll see 86 04:11.160 --> 04:13.920 that it's .1Q versus ISL. 87 04:13.920 --> 04:16.440 And guess what Cisco has as the default? 88 04:16.440 --> 04:22.760 Well, that's seen the default is ISL and that is just legacy configuration on 89 04:22.760 --> 04:23.320 the more 90 04:23.320 --> 04:26.040 legacy platforms at this point. 91 04:26.040 --> 04:31.960 We can just say .1Q, but on catalyst nine case, this command isn't even WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 04:26.040 --> 04:31.960 We can just say .1Q, but on catalyst nine case, this command isn't even 92 04:31.960 --> 04:33.440 available because 93 04:33.440 --> 04:37.160 ISL has been removed from modern switches. 94 04:37.160 --> 04:41.540 So because I've specified the encapsulation on the initiating side, if I do a 95 04:41.540 --> 04:42.560 show interface 96 04:42.560 --> 04:45.920 trunk, we're going to find that now I'm not negotiating. 97 04:45.920 --> 04:48.160 I'm just hard set to .1Q. 98 04:48.160 --> 04:52.520 I'm still in that desirable state and I am currently trunking. 99 04:52.520 --> 04:56.340 So if I go to switch to now, let's run that same command on switch to and we'll 100 04:56.340 --> 04:56.800 see that 101 04:56.800 --> 04:59.800 we have negotiated to .1Q. 102 04:59.800 --> 05:03.660 I did not have to specify the encapsulation on this side, although I could, but WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 04:59.800 --> 05:03.660 I did not have to specify the encapsulation on this side, although I could, but 103 05:03.660 --> 05:04.440 that N 104 05:04.440 --> 05:09.680 implies or is really saying that we have negotiated 802.1Q. 105 05:09.680 --> 05:15.610 So it's kind of a fun little nuance to using DTP is that it will negotiate the 106 05:15.610 --> 05:16.320 trunking 107 05:16.320 --> 05:21.520 encapsulation type on older platforms where ISL is still an option. 108 05:21.520 --> 05:26.120 Now next, we have to configure our trunk to router one. 109 05:26.120 --> 05:28.600 And so that is once again on switch one. 110 05:28.600 --> 05:32.440 We look at our diagram and we know that we need to perform this configuration WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 05:28.600 --> 05:32.440 We look at our diagram and we know that we need to perform this configuration 111 05:32.440 --> 05:33.160 on interface 112 05:33.160 --> 05:35.160 gig zero slash one. 113 05:35.160 --> 05:39.630 At this point, I'm going to go ahead now watch if I do switch port mode trunk, 114 05:39.630 --> 05:40.040 we're 115 05:40.040 --> 05:45.240 going to find that it's been rejected because we need to first of all specify 116 05:45.240 --> 05:46.560 the encapsulation 117 05:46.560 --> 05:47.560 method. 118 05:47.560 --> 05:51.840 So I'm going to say switch port encapsulation switch. 119 05:51.840 --> 05:53.160 I forgot trunk again. 120 05:53.160 --> 05:57.040 So we're going to support trunk encapsulation dot one Q and now we'll try 121 05:57.040 --> 05:58.160 switch port mode 122 05:58.160 --> 06:00.000 trunk. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 122 05:58.160 --> 06:00.000 trunk. 123 06:00.000 --> 06:05.080 And now we are running in a statically configured trunk operation. 124 06:05.080 --> 06:09.230 Again, on modern platforms, we don't need to worry about specifying the encaps 125 06:09.230 --> 06:09.720 ulation 126 06:09.720 --> 06:13.000 method, but on these older platforms, we absolutely do. 127 06:13.000 --> 06:14.160 So that's something to keep in mind. 128 06:14.160 --> 06:18.220 But at this point, we are not only trunking, but we see that this environment 129 06:18.220 --> 06:18.760 has been 130 06:18.760 --> 06:26.150 prepared for us VLANs 10 and 20 are allowed in forwarding out all of our trunk 131 06:26.150 --> 06:26.840 interfaces. 132 06:26.840 --> 06:30.720 And so let's go ahead and now configure our router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 06:26.840 --> 06:30.720 And so let's go ahead and now configure our router. 133 06:30.720 --> 06:33.960 So we said that we need to create sub interfaces on this router. 134 06:33.960 --> 06:40.000 If I do a show run interface on gig zero zero, this is our interface facing the 135 06:40.000 --> 06:42.120 switch one. 136 06:42.120 --> 06:44.040 And we notice it's in layer three operation. 137 06:44.040 --> 06:48.560 And that's because routers can't run interfaces in layer two. 138 06:48.560 --> 06:52.510 There are some advanced configurations where you can emulate bridge 139 06:52.510 --> 06:53.760 environments using 140 06:53.760 --> 06:56.440 BVI's bridge virtual interfaces. 141 06:56.440 --> 06:57.960 We're not going to go there. 142 06:57.960 --> 07:01.800 But generally speaking, what we need to do here is not try to enable layer two WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 06:57.960 --> 07:01.800 But generally speaking, what we need to do here is not try to enable layer two 143 07:01.800 --> 07:02.120 such 144 07:02.120 --> 07:05.040 that it's somehow turns the router into a switch. 145 07:05.040 --> 07:07.360 Instead, I'm going to create those sub interfaces. 146 07:07.360 --> 07:08.960 So let's go ahead and do that together. 147 07:08.960 --> 07:13.790 I'm going to do a config T. And the way we do that is I act like I'm getting 148 07:13.790 --> 07:14.200 onto the 149 07:14.200 --> 07:15.200 interface. 150 07:15.200 --> 07:20.320 I'm going to get dot and now I can specify whatever ID I want within the 151 07:20.320 --> 07:21.480 massive range 152 07:21.480 --> 07:22.480 that they give us. 153 07:22.480 --> 07:25.600 So usually we like to align this with the VLAN tag we're going to use. 154 07:25.600 --> 07:29.600 So I'm just going to say interface gig zero slash zero dot 10. 155 07:29.600 --> 07:35.320 And then from here, I'm going to map the VLAN ID to the sub interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 155 07:29.600 --> 07:35.320 And then from here, I'm going to map the VLAN ID to the sub interface. 156 07:35.320 --> 07:40.680 This command was provided to us in the command reference here in the skill. 157 07:40.680 --> 07:47.590 And that command is encapsulation encapsulation dot one Q and then I specify 158 07:47.590 --> 07:48.880 the tag ID. 159 07:48.880 --> 07:51.720 So for this, I'm going to call this VLAN 10. 160 07:51.720 --> 07:55.920 And then if VLAN 10 is the native VLAN on the other side of this trunk link, 161 07:55.920 --> 07:56.360 then I 162 07:56.360 --> 07:58.080 can specify that here. 163 07:58.080 --> 08:01.340 But since I didn't configure native VLAN, I'm just going to hit enter and then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 163 07:58.080 --> 08:01.340 But since I didn't configure native VLAN, I'm just going to hit enter and then 164 08:01.340 --> 08:01.880 interface 165 08:01.880 --> 08:06.640 gig zero slash zero dot 20 to create the VLAN 20 side. 166 08:06.640 --> 08:12.040 And once again, encapsulation dot one Q 20. 167 08:12.040 --> 08:14.800 So at this point, I've configured the sub interfaces. 168 08:14.800 --> 08:21.300 Let's go ahead and go back to our topology though, because we are not yet doing 169 08:21.300 --> 08:21.880 any or 170 08:21.880 --> 08:23.880 able to do any kind of pain testing. 171 08:23.880 --> 08:28.180 And the reason for that is we haven't actually created any IP addresses or 172 08:28.180 --> 08:29.360 layer three interfaces 173 08:29.360 --> 08:30.760 on the switches. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 173 08:29.360 --> 08:30.760 on the switches. 174 08:30.760 --> 08:32.520 So what do we have? 175 08:32.520 --> 08:38.720 Well, by creating these sub interfaces, I have created layer three interfaces 176 08:38.720 --> 08:39.280 on this router 177 08:39.280 --> 08:41.520 that are sort of virtual interfaces. 178 08:41.520 --> 08:45.120 We can think of them like VLAN interfaces because they're not physical. 179 08:45.120 --> 08:50.630 They're these virtual sub interfaces that are sort of behind the physical gig 180 08:50.630 --> 08:51.440 zero slash 181 08:51.440 --> 08:53.320 zero interface. 182 08:53.320 --> 08:55.400 And these are fully functioning layer three interfaces. 183 08:55.400 --> 08:57.160 That's why I've drawn them as dots here. 184 08:57.160 --> 09:01.960 So I can place IP addresses onto these interfaces. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 184 08:57.160 --> 09:01.960 So I can place IP addresses onto these interfaces. 185 09:01.960 --> 09:08.200 In fact, we're told to map the dot 100 IP address to each one of these 186 09:08.200 --> 09:09.640 interfaces. 187 09:09.640 --> 09:13.600 So let's go ahead and go back to our topology here. 188 09:13.600 --> 09:20.040 And we will do that interface gig zero slash zero dot 10. 189 09:20.040 --> 09:24.930 And then IP address and the subnet we're using is that 10 dot zero and for VLAN 190 09:24.930 --> 09:25.480 10 191 09:25.480 --> 09:31.920 be dot 10 and then dot 100 and then slash 24. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 191 09:25.480 --> 09:31.920 be dot 10 and then dot 100 and then slash 24. 192 09:31.920 --> 09:37.010 And let's go into a no shut and then into gig zero slash zero dot 20 IP address 193 09:37.010 --> 09:37.920 this time 194 09:37.920 --> 09:43.320 10 zero 20 dot 100 slash 24. 195 09:43.320 --> 09:44.320 No shot. 196 09:44.320 --> 09:46.040 All right. 197 09:46.040 --> 09:49.080 So my layer three interfaces should be online. 198 09:49.080 --> 09:53.610 If I do a show interface gig zero slash zero dot 10, we should see that it's up 199 09:53.610 --> 09:54.000 and up 200 09:54.000 --> 09:57.920 and it is I'll check without 20 and it's also up and up. 201 09:57.920 --> 10:01.890 So once again back to our topology here, I have these two layer three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 201 09:57.920 --> 10:01.890 So once again back to our topology here, I have these two layer three 202 10:01.890 --> 10:02.800 interfaces, but 203 10:02.800 --> 10:03.960 I can't ping anything. 204 10:03.960 --> 10:07.730 There's nothing for me to ping because I don't have any layer three interfaces 205 10:07.730 --> 10:09.160 down here. 206 10:09.160 --> 10:10.600 So what can I do? 207 10:10.600 --> 10:15.800 Well, as the last task indicates, we want to create some SVIs. 208 10:15.800 --> 10:21.840 Now the switch one SVI is kind of interesting compared to the switch to SVI 209 10:21.840 --> 10:22.920 because the 210 10:22.920 --> 10:28.320 switch one SVI is meant to go on VLAN 10. 211 10:28.320 --> 10:37.350 And so I'm going to map this interface to the same subnet so to speak as or the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 211 10:28.320 --> 10:37.350 And so I'm going to map this interface to the same subnet so to speak as or the 212 10:37.350 --> 10:37.760 same 213 10:37.760 --> 10:44.000 VLAN as subnet sub interface gig zero slash zero dot 10. 214 10:44.000 --> 10:48.360 And so naturally I could also connect other hosts into VLAN 10. 215 10:48.360 --> 10:53.480 We can start to create our logical diagram if we want, but gig zero slash zero 216 10:53.480 --> 10:54.440 dot 10 217 10:54.440 --> 10:59.040 should be able to communicate with the SVI for VLAN 10 on switch one. 218 10:59.040 --> 11:06.680 Meanwhile, switch to we're going to create this SVI for VLAN 20 and I should be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 218 10:59.040 --> 11:06.680 Meanwhile, switch to we're going to create this SVI for VLAN 20 and I should be 219 11:06.680 --> 11:07.200 able 220 11:07.200 --> 11:13.210 to ride this trunk all the way up and connect in from a layer three perspective 221 11:13.210 --> 11:14.000 to router 222 11:14.000 --> 11:19.160 ones gig zero slash zero dot 20 interface. 223 11:19.160 --> 11:23.680 And so we're going to map dot one to switch one and dot two to switch to. 224 11:23.680 --> 11:27.320 So let's go ahead and do that and wrap this up. 225 11:27.320 --> 11:34.310 So I'm going to come to switch one, do a config T interface VLAN 10 IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 225 11:27.320 --> 11:34.310 So I'm going to come to switch one, do a config T interface VLAN 10 IP address 226 11:34.310 --> 11:35.700 that same 227 11:35.700 --> 11:44.390 dot zero dot 10 subnet and then this case it's dot one and we'll do a no, no 228 11:44.390 --> 11:45.740 shot there 229 11:45.740 --> 11:52.290 and then on to switch to interface VLAN 20 IP address is going to be the zero 230 11:52.290 --> 11:53.540 dot 20 231 11:53.540 --> 12:00.940 subnet dot two for switch to and then no shot. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 231 11:53.540 --> 12:00.940 subnet dot two for switch to and then no shot. 232 12:00.940 --> 12:05.820 So given that the topology is all online, the song is these interfaces come up, 233 12:05.820 --> 12:06.300 we should 234 12:06.300 --> 12:07.300 be able to ping. 235 12:07.300 --> 12:12.860 So I should be able to ping from switch to router ones interface that's in the 236 12:12.860 --> 12:13.300 same 237 12:13.300 --> 12:14.300 subnet. 238 12:14.300 --> 12:18.580 So that would be 20 dot 100 and there we go. 239 12:18.580 --> 12:22.860 We have our pings from switch one or switch to router one. 240 12:22.860 --> 12:23.940 There we go. 241 12:23.940 --> 12:34.660 And then we'll go and do it from switch one ping 10 dot zero dot 10 dot 100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 241 12:23.940 --> 12:34.660 And then we'll go and do it from switch one ping 10 dot zero dot 10 dot 100. 242 12:34.660 --> 12:35.660 And there we go. 243 12:35.660 --> 12:37.660 Switch one, campaign router one. 244 12:37.660 --> 12:42.350 So again, the topology is really useful to us because it shows us exactly what 245 12:42.350 --> 12:42.980 's happening 246 12:42.980 --> 12:48.500 here and why these individual SVI's that we've created can communicate with 247 12:48.500 --> 12:50.180 router one and 248 12:50.180 --> 12:54.420 how we can leverage again those SVI's either for default gateways, which is 249 12:54.420 --> 12:55.100 usually how 250 12:55.100 --> 12:58.980 we use them, but also for troubleshooting because we might have a situation 251 12:58.980 --> 12:59.700 where I need 252 12:59.700 --> 13:01.420 to do some ping testing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 252 12:59.700 --> 13:01.420 to do some ping testing. 253 13:01.420 --> 13:05.710 And so in this case, not only have I explored that topology, but I've also 254 13:05.710 --> 13:06.740 created a router 255 13:06.740 --> 13:11.050 on a stick topology, which again is is pretty legacy as far as the networking 256 13:11.050 --> 13:12.180 world is concerned, 257 13:12.180 --> 13:15.920 but it's also kind of a classic that now everyone's got a configure at some 258 13:15.920 --> 13:16.500 point. 259 13:16.500 --> 13:19.020 I hope this has been informative for you and I'd like to thank you for viewing.